Escolar Documentos
Profissional Documentos
Cultura Documentos
DIMETRA
DIMETRA IP COMPACT (DIPC)/SCALABLE DIMETRA IP (SDIP)
SYSTEM OVERVIEW
October 2013
68015000701-C
Disclaimer
Please note that certain features, facilities, and capabilities described in this document may not be applicable to
or licensed for use on a particular system, or may be dependent upon the characteristics of a particular mobile
subscriber unit or configuration of certain parameters. Please refer to your Motorola contact for further information.
Trademarks
MOTOROLA, MOTO, MOTOROLA SOLUTIONS, and the Stylized M Logo are trademarks or registered
trademarks of Motorola Trademark Holdings, LLC and are used under license. All other trademarks are the
property of their respective owners.
The European Union's WEEE directive requires that products sold into EU countries must have the crossed out
trash bin label on the product (or the package in some cases).
As defined by the WEEE directive, this cross-out trash bin label means that customers and end-users in EU
countries should not dispose of electronic and electrical equipment or accessories in household waste.
Customers or end-users in EU countries should contact their local equipment supplier representative or service
centre for information about the waste collection system in their country.
i
CMM Labeling and Disclosure Table
The Peoples Republic of China requires that our products comply with China Management Methods (CMM)
environmental regulations. (China Management Methods refers to the Regulation Management Methods for
Controlling Pollution by Electronic Information Products.) Two items are used to demonstrate compliance; the
Label and the Disclosure Table.
The label is placed in a customer visible position on the product. The first of the following examples means that the
product contains no hazardous substances; the second means that the product contains hazardous substances, and
has an Environmental Friendly Use Period (EFUP) of fifty years.
The Environmental Friendly Use Period (EFUP) is the period (in years) during which the Toxic and Hazardous
Substances (T&HS) contained in the Electronic Information Product (EIP) will not leak or mutate causing
environmental pollution, or bodily injury from the use of the EIP.
The Disclosure Table, printed in simplified Chinese, is included with each customer order. An example of
a Disclosure Table (in Chinese) follows:
iii
Service Information
Government Technical Support, EA Solutions Support Centre (ESSC)
The Government Technical Support, EA Solutions Support Centre (ESSC) provides a remote Technical Support
Service to help customers resolve technical issues and quickly restore networks and systems. This team of highly
skilled professionals is available to customers with current service agreements in place that include the Technical
Support Service. The ESSC technical experts may be accessed through the EMEA Integrated Call Center either
electronically or using the telephone numbers listed below. If you are unsure whether your current service
agreement entitles you to benefit from this service, or if you would like more information about the Technical
Support Service, contact your local customer support or account manager for further information.
Contact Details
Email: essc@motorolasolutions.com
v
System Overview
Contact Details
E-Mail: escc.admin@motorolasolutions.com
Telephone: +49 (0) 30 66861404
Telefax: +49 (0) 30 66861426
Monday Friday 08:00 am to 06:00 pm (CET)
Your Input
If you have any comments, corrections, suggestions, ideas for this publication or any other requirements regarding
Motorola publications, send an e-mail to doc.emea@motorolasolutions.com.
vi
Document History
Edition Description Date
68015000701-A Initial Version February 2013
68015000701-B Updated graphics/diagrams. Fixed VPN Gateway model name. March 2013
68015000701-C Updated with changes connected with the introduction of HP October 2013
rp5800
vii
Contents
1 Radio System Concepts............................................................................................................................... 1-1
1.1 What is a Radio System?.................................................................................................................... 1-1
1.1.1 Basic System Components ........................................................................................................ 1-1
1.1.1.1 Radio System Equipment ................................................................................................... 1-1
1.1.1.2 Radio System Range.......................................................................................................... 1-2
1.1.2 Communication Types .............................................................................................................. 1-2
1.1.2.1 Simplex .......................................................................................................................... 1-3
1.1.2.2 Semi-Duplex.................................................................................................................... 1-3
1.1.2.3 Duplex............................................................................................................................ 1-4
1.1.3 Call Types .............................................................................................................................. 1-4
1.1.3.1 Talkgroup Calls ................................................................................................................ 1-4
1.1.3.2 Multigroup Calls............................................................................................................... 1-4
1.1.3.3 Object Calls ..................................................................................................................... 1-4
1.1.3.4 Announcement Calls ......................................................................................................... 1-5
1.1.3.5 Emergency Calls............................................................................................................... 1-5
1.1.3.6 Ruthless Preemption.......................................................................................................... 1-5
1.1.3.7 Direct Mode Operation Calls............................................................................................... 1-5
1.1.3.8 Site Wide Calls................................................................................................................. 1-5
1.1.3.9 Private Calls .................................................................................................................... 1-6
1.1.3.10 Telephone Interconnect Calls............................................................................................. 1-6
1.1.4 Types of Communication Channels ............................................................................................. 1-6
1.1.4.1 Control Channel (CC) ........................................................................................................ 1-6
1.1.4.2 Traffic Channel (TCH) ....................................................................................................... 1-6
1.1.5 Basic Site Components ............................................................................................................. 1-7
1.1.5.1 Site Controller (SC)........................................................................................................... 1-7
1.1.5.2 Base Radio (BR)............................................................................................................... 1-7
1.1.6 Radios ................................................................................................................................... 1-8
1.1.7 Call Processing Basics.............................................................................................................. 1-8
1.1.7.1 Trunked and Conventional Radio Systems ............................................................................. 1-9
1.1.7.1.1 Trunked System Operation ........................................................................................ 1-9
1.1.7.1.2 Conventional System Operation................................................................................ 1-10
1.1.7.2 Radio System Users ........................................................................................................ 1-11
1.1.7.2.1 Radio Users .......................................................................................................... 1-11
1.1.7.2.2 Talkgroups ........................................................................................................... 1-11
1.1.7.2.3 Multigroups .......................................................................................................... 1-12
1.1.8 Tracing a Basic Call ............................................................................................................... 1-13
1.2 Multiple Site Trunked Systems .......................................................................................................... 1-15
1.2.1 RF Sites............................................................................................................................... 1-16
1.2.2 Zone ................................................................................................................................... 1-17
1.2.3 Mobile Switching Office (MSO)............................................................................................... 1-17
1.3 Multizone Systems.......................................................................................................................... 1-18
1.3.1 Conditions for Multizone Communication .................................................................................. 1-19
1.3.1.1 Home Zone Mapping....................................................................................................... 1-19
1.3.1.2 Controlling Zone ............................................................................................................ 1-20
1.3.1.3 Participating Zone........................................................................................................... 1-20
1.3.2 Modes of Operation ............................................................................................................... 1-20
1.3.2.1 Wide Area Trunking with Interzone Trunking....................................................................... 1-21
1.3.2.2 Fall Back Modes............................................................................................................. 1-21
1.3.2.2.1 Zone Isolated Wide Area Trunking............................................................................ 1-21
1.3.2.2.2 Local Site Trunking................................................................................................ 1-22
1.3.2.2.3 Direct Mode Operation (DMO) ................................................................................ 1-22
1.3.3 Interzone Group Service Availability ......................................................................................... 1-22
ix
System Overview
x
Document History
xi
System Overview
xii
Document History
xiii
System Overview
xiv
Document History
xv
System Overview
xvi
List of Figures
Figure 1-1 Basic Radio System ................................................................................................................... 1-1
Figure 1-2 Fixed Equipment....................................................................................................................... 1-2
Figure 1-3 Antenna Height and Coverage ..................................................................................................... 1-2
Figure 1-4 Simplex Communication ............................................................................................................ 1-3
Figure 1-5 Semi-Duplex Communication...................................................................................................... 1-3
Figure 1-6 Radios to Base Station Relationship ............................................................................................. 1-8
Figure 1-7 Example: Trunked Radio System Channel Assignments ................................................................... 1-9
Figure 1-8 Basic Trunked Site .................................................................................................................. 1-10
Figure 1-9 Conventional Radio System Example.......................................................................................... 1-11
Figure 1-10 Example: Organization of Users in a Talkgroup ............................................................................ 1-12
Figure 1-11 Example of Talkgroups in Multigroups........................................................................................ 1-12
Figure 1-12 Trunked Call Initiation ............................................................................................................. 1-13
Figure 1-13 Trunked Call Validation............................................................................................................ 1-14
Figure 1-14 Trunked Call Completion.......................................................................................................... 1-15
Figure 1-15 Multiple Site Trunked System.................................................................................................... 1-16
Figure 1-16 RF Site.................................................................................................................................. 1-17
Figure 1-17 Mobile Switching Office (MSO) ................................................................................................ 1-18
Figure 1-18 Example: Multizone System...................................................................................................... 1-18
Figure 1-19 Multizone System - Conditions for Interzone Trunking................................................................... 1-19
Figure 1-20 Modes of Operation in a Dimetra System..................................................................................... 1-21
Figure 2-1 TETRA defined Air Interface ...................................................................................................... 2-1
Figure 2-2 Pi/4-DQPSK Modulation ............................................................................................................ 2-3
Figure 2-3 ACELP Voice Compression ........................................................................................................ 2-4
Figure 2-4 Time Division Multiple Access - Base Stations ............................................................................... 2-4
Figure 2-5 Time Division Multiple Access - Radio (Full-Duplex Operation)........................................................ 2-5
Figure 2-6 E1 Carrier ................................................................................................................................ 2-8
Figure 2-7 Cooperative WAN Routing - Example ......................................................................................... 2-10
Figure 2-8 Ethernet Site Links- Example .................................................................................................... 2-11
Figure 2-9 Unicast Routing ...................................................................................................................... 2-13
Figure 2-10 Multicast Routing.................................................................................................................... 2-14
Figure 2-11 Call Processing - Multicast Routing of Traffic............................................................................... 2-16
Figure 2-12 Dimetra IP System Logical Traffic Planes .................................................................................... 2-17
Figure 2-13 Basic Secure Voice Operation .................................................................................................... 2-18
Figure 2-14 Voice Transmission.................................................................................................................. 2-19
Figure 3-1 HP DL360p Gen8 Server Front View ............................................................................................ 3-1
Figure 3-2 Network Management Subsystem................................................................................................. 3-3
Figure 3-3 Telephone Interconnect Subsystem ............................................................................................... 3-8
Figure 3-4 Network Time Server ............................................................................................................... 3-11
Figure 3-5 Transport Core with E1 Connections ........................................................................................... 3-12
Figure 3-6 Transport Core with Ethernet Connections ................................................................................... 3-13
Figure 3-7 CWR Patch Panel.................................................................................................................... 3-15
Figure 3-8 MTS LiTE ............................................................................................................................ 3-16
Figure 3-9 MTS 1 .................................................................................................................................. 3-17
Figure 3-10 MTS 2 .................................................................................................................................. 3-18
Figure 3-11 MTS 4 .................................................................................................................................. 3-19
Figure 3-12 Site Controller (SC) ................................................................................................................. 3-20
Figure 3-13 BTS Base Radio...................................................................................................................... 3-21
Figure 3-14 Control Site............................................................................................................................ 3-22
Figure 3-15 Dispatch Subsystem................................................................................................................. 3-23
Figure 3-16 MCC 7500 Dispatch Console Subsystem ..................................................................................... 3-24
Figure 3-17 MCC 7500 Emergency Beacon .................................................................................................. 3-25
Figure 3-18 GGM 8000 used for CCGW ...................................................................................................... 3-27
xvii
System Overview
xviii
List of Tables
List of Telephone Numbers ........................................................................................................... v
Table 3-1 Types of System Server (constellations)......................................................................................... 3-2
Table 3-2 MTM5x00 MTM800 FuG/MTM800 FuG ET Options.................................................................... 3-39
Table 4-1 Summary of Database Administration Functions ............................................................................. 4-4
Table 4-2 Hierarchical Listing of Servers Hosting Databases ........................................................................... 4-5
Table 4-3 Server Interactions.................................................................................................................... 4-6
Table 5-1 Short Subscriber Identity Ranges.................................................................................................. 5-5
Table 5-2 Security Classes ...................................................................................................................... 5-32
Table 5-3 Zone Call Service States ........................................................................................................... 5-37
Table 5-4 Levels of Group Service Availability........................................................................................... 5-37
Table 5-5 Call Processing Behavior During Recovery .................................................................................. 5-43
Table 6-1 Console Priority Levels ............................................................................................................ 6-13
Table 7-1 Air Interface Encryption - Security Features ................................................................................ 7-11
Table 7-2 Motorola PRNM Suite Applications............................................................................................ 7-14
Table 7-3 Other Motorola Applications .................................................................................................... 7-15
Table 7-4 Object Classes in UCM ............................................................................................................ 7-22
Table 7-5 High-Level Objects in ZCM ...................................................................................................... 7-22
Table A-1 ............................................................................................................................................. A-1
................................................................................................................................................. I
xix
List of Processes
1.1.8 Tracing a Basic Call....................................................................................................................................................1-13
2.3.5 Call Model ..................................................................................................................................................................2-14
5.4.1.1.3 Call Grant..............................................................................................................................................................5-14
5.4.1.1.4 Intrazone Talkgroup Call Audio Routing .............................................................................................................5-14
5.4.1.1.5 Talkgroup Call Continuation and Teardown.........................................................................................................5-15
5.5.1.1 Private Call Request Flow .......................................................................................................................................5-21
5.5.1.2 Intrazone Private Call Audio Flow, Call Continuation, and Teardown ...................................................................5-22
5.5.2.2.3.1 Call Setup...........................................................................................................................................................5-26
5.6 Short Data Services........................................................................................................................................................5-29
5.11.3 System Behavior During Automatic Switchover......................................................................................................5-42
xxi
About System Overview
This manual explains radio system concepts and describes the components and functionality of the Dimetra
IP system.
The purpose of this manual is to:
Describe the basic radio system concepts and call processing basics.
Provide an introduction to the various components and processes associated with the Dimetra IP system.
This manual is an introduction to the Dimetra IP system. The information in this manual does not assume any
pre-knowledge of the Dimetra IP system or radio concepts in general.
xxiii
What is Covered In This Manual?
This manual provides information in the following areas:
1 Radio System Concepts, page 1-1 provides an introduction to the basic concepts of conventional radio
systems and Motorola trunked radio systems.
2 Dimetra IP System Technology, page 2-1 discusses technology behind Dimetra IP system.
3 Dimetra IP System Components, page 3-1 discusses the hardware components associated with the
Dimetra IP System.
4 Dimetra IP Data Management, page 4-1 presents an overview of the databases, servers, and Zone
Controllers found in the Dimetra IP system.
5 Dimetra IP Call Processing, page 5-1 presents an overview of call processing, which takes place at the
MSO equipment in a Dimetra IP system.
6 Dimetra IP System Features, page 6-1 lists and explains the features and options available for the Dimetra
IP system.
7 Dimetra IP Network Management, page 7-1 presents an overview of the FCAPS model as described by
the International Organization for Standardization (ISO). It also discusses Private Network Management
(PRNM), its software applications or tools used to manage the Dimetra IP system and Network Management
Software Tools that support the management of the system and its component parts.
A Dimetra IP System Documentation, page A-1 contains information on related Dimetra IP system
documentation, including third-party documentation.
xxv
Helpful Background Information
Motorola offers various courses designed to assist in learning about the system. For information, go to
http://www.motorolasolutions.com/training to view the current course offerings and technology paths.
xxvii
Related Information
See A Dimetra IP System Documentation, page A-1. The appendix includes a full listing of the Dimetra IP system
documentation and related documentation.
xxix
Icon Conventions
The document set is designed to give the reader more visual cues. The following graphic icons are used throughout
the documentation set. These icons and their associated meanings are described below.
SUGGESTION
A Suggestion implies a recommendation or tip from Motorola, which does not require to be followed, but
may be helpful. There is no warning level associated with a Suggestion.
Notes contain information that is more important than the surrounding text, such as exceptions or
preconditions. Also, refer the reader elsewhere for additional information, remind the reader how to
complete an action (when it is not part of the current procedure, for instance), or tell the reader where
information is located on the screen. There is no warning level associated with a Note.
An Important icon indicates information that is crucial to the discussion at hand, but which is not a Caution
or a Warning. There is no warning level associated with the Important icon.
The Caution icon implies information that must be carried out in a certain manner to avoid
problems, procedures that may or may not be necessary as determined by the readers system
configuration, and so on. Although no damage occurs if the reader does not heed the caution, some
steps may need repeating.
The signal word CAUTION may be used without the safety icon to state potential damage or injury
that is not related to the product.
The Warning icon implies potential system damage if the instructions or procedures are not carried
out exactly, or if the warning is not heeded.
The Danger icon implies information that, if disregarded, may result in severe injury or death of
personnel. This is the highest level of warning.
xxxi
Style Conventions
The following style conventions are used:
Convention Description
Bold This typeface is used for names of, for instance, windows, buttons, and
labels when these names appear on the screen (example: the Alarms
Browser window). When it is clear that we are referring to, for instance, a
button, the name is used alone (example: Click OK).
Monospacing font in bold This typeface is used for words to be typed in exactly as they
are shown in the text (example: In the Address field, type
http://ucs01.ucs:9080/)
Monospacing font This typeface is used for messages, prompts, and other text displayed on
the computer screen (example: A new trap destination has
been added).
Monospacing font in bold This typeface is used with angle brackets for words to be substituted
Italic by a specific member of the group that the words represent (example:
<router number>).
xxxiii
1 Radio System Concepts
Radio systems provide a convenient and timely method of communication for people engaged in various public
safety-related, transportation, and service occupations. Radio systems differ in design based on the needs of
the individual users. One radio system may support a towing company with a dispatcher and two tow trucks
communicating back and forth. Another radio system may support the needs of a public utility company with a
network of antenna towers and control sites and field personnel scattered across a wide geographic area. The type
of radio system that you have depends on the needs of your individual organization.
Microphone Antennas
0 0
0
0
0
0
Fixed equipment is located at a central site. A base station is used to transmit the signal generated through the
microphone to portable and mobile equipment located at some distance. The range of the base station depends
on its power, antenna system, terrain, and environmental conditions. The location of the base station control is
known as the Dispatch Centre.
0
0
0
0
Mobile and Portable equipment are the radios that are not fixed. Mobile radios are mounted in vehicles and
portable radios are handheld devices carried by a person.
1.1.2.1 Simplex
The most basic type of radio communication is simplex. Simplex communication consists of radio units operating
on a single frequency. Because everyone transmits and receives on the same frequency, users cannot talk and listen
at the same time. Simplex means transmission in one direction at a time.
Single Frequency
A simplex radio system works well when there are only a few users who are closely located. When additional users
are added to the system, the competition for the one available frequency can make it difficult to get a message
across. In addition, great distances and natural obstacles such as high hills and tall buildings can interfere with the
single frequency.
1.1.2.2 Semi-Duplex
Semi-duplex communication uses two frequencies: one to receive and one to transmit. A radio operating in
semi-duplex mode can only transmit or receive at any time. Radios operating on the Dimetra IP system use
semi-duplex communication to communicate with the base stations during talkgroup and multigroup calls. A
semi-duplex individual call is also supported in the Dimetra IP system.
1.1.2.3 Duplex
Duplex communication uses different frequencies simultaneously, one to transmit and the second to receive. The
transmitter output is isolated and separated in frequency to prevent blocking the input of its companion receiver.
Also called full-duplex, this type of operation is used to indicate that the equipment can receive and transmit at
the same time. Normally, fixed equipment (a base station) operates in full-duplex mode while mobile equipment
typically operates in semi-duplex mode.
Group-based call services Group-based calls are services that provide for group (one-to-many)
communication. The types of group-based calls include:
1.1.3.1 Talkgroup Calls, page 1-4
1.1.3.2 Multigroup Calls, page 1-4
1.1.3.3 Object Calls, page 1-4
1.1.3.4 Announcement Calls, page 1-5
1.1.3.5 Emergency Calls, page 1-5
1.1.3.6 Ruthless Preemption, page 1-5
1.1.3.7 Direct Mode Operation Calls, page 1-5
1.1.3.8 Site Wide Calls, page 1-5
Individual call services Individual calls are services that provide for individual user to user communication.
The types of individual calls include:
1.1.3.9 Private Calls, page 1-6
1.1.3.10 Telephone Interconnect Calls, page 1-6
This feature may be applied in an airport system, where different functions carried out at the airport are linked to
flights (that is objects), resulting in a flight-oriented communication system. When an airplane is arriving at an
airport gate, different resources are necessary to service this flight, and for communication purposes these resources
are grouped following a structure of flights and functional groups.
In a trunked system, the traffic channels can be operated in one of two modes: Transmission Trunking, Message
Trunking or Message Trunking with PTT ID.
Transmission Trunking
The controller reclaims the traffic channel immediately after detecting a disconnect signal from the
transmitting unit. The receiving radios immediately returns to the control channel. The entire request and
assignment procedure is repeated for each PTT from the originator or a radio responding to the original call.
PTT-ID Trunking
This allows a group to retain the assigned traffic channel for some time, after the transmitting unit releases the
PTT. When a message trunked call is in progress, other radio users within the same group are allowed to key
without returning to the control channel for a traffic channel assignment. This mode of operation provides
positive identification of the transmitting radio and must be programmed in both the radio and the system.
The BTS has several channels and these channels can either be designated to Control Channel (CC) or Traffic
Channel (TCH), which are mentioned below.
1.1.6 Radios
Radios are classified as mobile (vehicle-mounted) or portable (carried by a person, usually handheld) radios
which provide users with the ability to make voice calls, send short data messages, or interface with mobile data
equipment. Each radio is assigned a unique identification number that identifies the radio to the system. It also
contains the logic circuitry necessary to perform the following trunking functions:
Generate and transmit requests for service in the form of data words that are then used to modulate the
carrier frequency.
Interpret the signaling messages sent by the central controller.
Generate the frequency of the assigned traffic channel.
Generate tones to advise the radio user of the status of the call request.
Trunked
Conventional
Trunking takes advantage of the fact that people do not talk on their radios continuously for 24 hours a day.
Most radio users need access to a channel several times a day, but their total time on the system may not exceed
five minutes each. Temporary channel assignment helps ensure that a channel is available when a conversation
needs to take place.
Trunking reduces the number of busies and improves the efficiency of the system resources. A call is busied if it has
been placed in a queue due to no channel being available.
Controller
A A B C D D
1.1.7.2.2 Talkgroups
A talkgroup is the basic unit of communication in a trunked system. In most organizations, radio users work in
groups that are based on their functions and responsibilities. In a trunked radio system, these groups of radio users
can be assigned to communication talkgroups that reflect their function or responsibilities. The figure below is an
example of a talkgroup.
Programming of talkgroups in a radio is based on the communication needs of radio users. A radio can be
programmed with only one or with several talkgroups. Radio users selecting a particular talkgroup on their radio
are assigned a traffic channel when someone in the group requests talkgroup call services. Group privacy during
conversations is provided since only one talkgroup is assigned to each traffic channel.
Each talkgroup is configured and identified in the system by a unique talkgroup ID.
1.1.7.2.3 Multigroups
Several talkgroups can be combined to form a multigroup (also called an announcement group). Multigroups are
assigned an ID from the same pool of numbers as the talkgroups. In this example, calls placed to Multigroup A
would be heard by the radio users in Talkgroups 2 and 3.
Ta lkgroup 2 Ta lkgroup 3
Ta lkgroup 1
Multigroup A
1 When a radio user initiates a call, the radio signals to the system via the control channel and requests a traffic
channel.
In the figure below, Radio 1 is requesting a call, and Radio 2 and Radio 3 in Talkgroup B are listening on the
control channel and detect the request for a call. The radios in Talkgroup A are also monitoring the control
channel but ignore the call request because they are in different talkgroup.
In Figure 1-12 Trunked Call Initiation, Figure 1-13 Trunked Call Validation, and Figure 1-14 Trunked
Call Completion, the arrows indicate the direction in which the information flows.
TETRA Carrier
C
T
T
T
1 2 3
Ta lkgroup A Ta lkgroup B
2 The system validates the call request, assigns a traffic channel and signals a traffic channel grant to all radios
of that group. The members of Talkgroup B respond by monitoring the temporarily assigned traffic channel.
Radios in Talkgroup A continue to monitor the control channel as before.
In the figure below, Radio 1 is transmitting on a traffic channel, and Radio 2 and Radio 3 are listening to the call.
TETRA Carrier
C
T
T
T
1 2 3
Ta lkgroup A Ta lkgroup B
3 When the call is finished, all radios in Talkgroup B return to monitoring the control channel. The traffic
channel becomes available for other radios.
TETRA Carrier
C
T
T
T
1 2 3
Ta lkgroup A Ta lkgroup B
Site Controller
trolle r
RF Site
Mobile Switching
S wi
witching
Office
ce
Site Controller Site
S ite Controller
Con
ontrolle r
RF Site RF Site
1.2.1 RF Sites
An RF site is a geographical area within which a two-way radio infrastructure allows communication between
two-way radios. It is the equivalent of a single site trunked system with additional control and audio links to a
central mobile switching office (MSO). Under certain conditions, it can operate independently in local site trunking
mode, but its normal mode of operation is in wide-area trunking with other RF sites. The figure below shows an
example of an RF site.
Site
1.2.2 Zone
A zone consists of sites connected to the master site. The Zone Controller is the central point for all the equipment
necessary to control and manage the sites in a zone.
Zone
Controller
Control
Sites
Mobile Switching
Office
Base
Stations
An active control path is required between any two zones in order to be able to coordinate a call that
involves sites in more than one zone.
Interzone audio paths are needed to route the audio to any zone required by the location of the talkgroup
members.
Site 1 Site 4
Site 2 Site 5
Co ntro l
Co ntro l
Au dio
Au dio
Co l
Site 3 ro Site 6
Au n tro nt
di l C o u d io
o A
Control Control Control
Audio Audio Audio
Ma s te r S ite Ma s te r S ite
Co
Au tro l
Au
n tr
d io
Zone 1 Zone 2
n
Co
ol
d io
Site 7 Co Site 9
ol
n tr n
Au tro l
C o d io Ma s te r S ite d io
Au
Zone 3
Control
Audio
Site 8
Multizone systems contain various hardware devices and software applications that allow the system to exchange
control information between zones, establish audio paths between zones when necessary, track radio movement
across sites or zones, and provide a management subsystem that can be accessed from any one of the zones. The
terminology has expanded to include home zone mapping, controlling zone, and participating zone.
The zone assigned to a particular ID is the home zone of this ID. The home zone to which an ID is assigned has an
impact on how the system operates. Home zone assignment affects system operation in the following ways:
Configuration information is distributed throughout the system based on the home zone assignment
of the ID.
A Zone Controller stores only the configuration information for those individual and group IDs that are
home to that zone.
Local Site
Trunking
Zon e Is ola te d
Wide Are a
Trunking
Direct
Operation
Mode
In the figure, the circles do not represent coverage. In reality, the coverage of base stations overlaps.
Full interzone group service availability: All zones are in a state of interzone trunking with respect to
the home zone of the group.
Reduced interzone group service availability: At least one participating zone is in interzone trunking with
the home zone of the group and at least one zone is not.
Zone isolated group service availability: The zone can provide call services only within its own site
resources.
1.3.4.2 Zone
Calls can take place between multiple sites within a zone. The Zone Controller arranges the necessary sites for the
call, and the Site Controllers (SCs) for each site assign the channel needed for the call.
1.3.4.3 Multizones
In a multizone system, calls can take place between more than one zone. The controllers at the MSO of each zone
communicate with each other to coordinate the assignment of resources.
Infrastructure
The most typical users of a TETRA system include public safety, transportation, utilities, industrial organizations,
government agencies, and private telecommunication agencies.
Ethernet accesses data using Carrier Sense Multiple Access with Collision Detection (CSMA/CD). This method
allows multiple users to access the network through a common cable. All devices attached to the network check for
transmissions in progress, signals are checked at the start of transmission and during transmission. Signals are sent
if no other transmission is detected; otherwise, the transmission is delayed. Collision detection is applied when two
or more devices transmit at the same time. A device knows if a collision occurred when it does not receive its own
transmission back. Each device stops transmission and attempts to retransmit after waiting a certain amount of
time, which is different for each device and determined by an algorithm.
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.
VLAN technology allows a system administrator to assign each port of a switch to members of different Ethernet
segments. The MSOs in a Dimetra IP system use switches that support VLAN technology in an extended stackable
configuration.
The use of intelligent switches instead of passive hubs to form Ethernet networks permits the use of Virtual
LAN (VLAN) technology, IEEE 801.2Q.
Leased lines: Leased lines provide a dedicated single path through an external provider from one location
to another. It is possible to use either E1 or Ethernet (see 2.2.4 Ethernet Site Links, page 2-10). Speeds
range from 56 kbps to 2.048 Mbps in case of E1. In case of Ethernet the speeds vary depending on the
provider. Leased lines provide dedicated service and no call setup time, but the bandwidth is not flexible. A
4-wire analog leased line provides slower speeds, generally up to 33.6 kbps.
Packet-switched networks: Packet-switched networks break messages apart into packets and tag each
packet with source and destination addresses. Packet-switching has several advantages:
Packets can be routed around network problems
They can maximize link efficiency by making optimal use of bandwidth
They can be more cost effective than leased lines.
Frame relay switching provides high-speed packet-switching over Permanent Virtual Circuits (PVCs)
referenced by Data Link Connection Identifiers. Local Management Interface (LMI) extensions provide
additional management capability. Frame relay includes a cyclic redundancy check (CRC) algorithm that
detects corrupted bits. Any needed retransmission is performed at higher protocol layers such as TCP.
Circuit-switching:Circuit-switching provides a dedicated path between a sender and receiver for the
duration of the communication. The advantages of the circuit-switched networks are dedicated circuits for
the call and customers do not pay for idle bandwidth. Disadvantages are call setup time and potential
under-utilization of the communication channel. Circuit-switching is useful for short duration transmissions,
for feeders to main sites or for backup/disaster recovery situations.
2.2.2.1 E1 Carrier
An E1 carrier is a telecommunications facility designed to carry digital information at a bit rate of 2.048 Mbps.
In conventional telecommunications, the most common use for an E1 carrier is to connect central offices within
an individual telephone company. Telephone companies also lease E1 carriers to their customers for their own
private purposes. Most systems use E1 circuits to transmit digitized voice, management, and control traffic between
zones. The Frame Relay protocols provide the means for exchanging information over the E1 communication
facilities that connect remote zones.
Various types of transmission media can be used in implementing a private E1 facility, such as various types of
privately installed cabling or point-to-point microwave circuits.
An E1 circuit is divided into 32 time slots, each of which implements a separate communication channel that can
support a bit rate of 64,000 bps. Each of these individual channels is referred to as a Digital Signal Level zero
(DS0) channel.
The term framing refers to the order in which user bits and other information is transmitted over a physical
transmission medium. An E1 frame comprises a total of 256 bits. Each of the 32 inputs is assigned a fixed time
slot; the E1 uses a time-division multiplexing technique to divide the capacity of the carrier into 32 channels. The
framing bit is used to create a pattern to help synchronize the equipment. The figure below illustrates the format
of the E1 transmission frame.
X.21 links can be used in the Dimetra IP system to support site links to BTS sites and control sites. The Dimetra IP
system uses a 15-pin V.11 physical interface for connection to X.21 links.
Ethernet links are supported over a Layer 2 or Layer 3 of the GBN (Ground Based Network). Each Ethernet link
terminated at the Mobile Switching Office (MSO) is represented by an IP tunnel terminated at MSO routers. IP
tunnels at the zone core are implemented either as all encrypted IPSec tunnels, or all unencrypted IPIP tunnels. A
pair of backhaul switches per MSO are used to aggregate the IPSec and IPIP tunnels for site links and inter-MSO
links.
Ethernet routers support either encrypted or unencrypted tunnels, however a mixed configuration of encrypted and
unencrypted tunnels on the same router is not supported. When a zone core has a mixed configuration of encrypted
and unencrypted tunnels, at least two pairs of Ethernet routers are required. One pair is configured to terminate the
encrypted tunnels, and the other one is configured to terminate the unencrypted tunnels.
Zone core routers with Ethernet-based WAN interfaces are always deployed in pairs. The primary router is
connected to the primary backhaul switch and terminates the primary Ethernet links, and the secondary router is
connected to the secondary backhaul switch and terminates the secondary Ethernet link.
The Ethernet Site Links can be additionally protected by adding Backhaul Firewalls at the Zone core and at
the remote control sites.
Scalable Platform: The transport core supports a number of zones/sites per system. Multizone systems are
formed with max 1 cluster, containing up to 4 zones.
Digital only platform that supports Algebraic Code Excited Linear Prediction (ACELP) for voice
transmission.
The systems support the operation of IP based consoles in a packet-based environment.
The transport core provides the ability to transparently transport vocoded audio. Once voice is vocoded, the
digital information is passed all the way through the network with no conversions required. Conversion
to the original audio format is required only at the destination receiver. The Dimetra IP system supports
air interface encryption.
The transport core consists of a packet transportation network that is not concerned with what is contained
in the packets.
The Dimetra IP system includes an Internet Protocol (IP) based infrastructure that provides IP multicast technology
for dispatch services and RF sites. This technology allows group calls to be set up, processed, and torn down easily
in a packet environment, replacing circuit switched methods.
Most datagrams sent across a typical network use unicast messaging to deliver information between one point
and another.
D D
D RP
Since talkgroup and announcement calls involve routing of audio between a single source and multiple recipients,
multicast routing works well with group-based audio routing. Multicast allows the transmitting radio audio to be
distributed to the appropriate sites by the RP router. Without multicast, the source would have to separately address
multiple copies of each packet to each of the individual recipients across the network.
In the Dimetra IP network, all the devices associated with a particular call are instructed to join a specific multicast
group. After the join messages are received from the devices, the RP propagates the multicast traffic to the
appropriate devices, sites, and zone(s) that are involved in the call and that have sent their join message.
The RP is typically defined as the router located near the receiving end of the multicast traffic, rather than a router
located near the source of the traffic. This allows greater efficiency of network resources, since the higher volumes
of multicast traffic is only spread across the receiving end of the network, rather than spreading all the replicated
packets directly from the source location across the entire network.
Multicast trees for audio traffic are set up as requested and are present only for the duration of the multicast call. A
range of class-D IP addresses (addresses beginning with 224 -239) are designated as multicast group addresses.
Process Steps
1 A radio user presses the PTT button to talk to other users in the talkgroup. The radio transmits a Call Request
on the RF control channel at the site. The Call Request is received by the control channel and forwarded to
the site LAN. Before placing the Call Request packet on the site Ethernet LAN, the base station encapsulates
the Call Request message in a User Datagram Protocol (UDP/IP) datagram with the destination IP address
of the Zone Controller.
UDP is a transport layer protocol that resides on top of the IP. UDP provides a transaction-oriented,
best-effort delivery service. IP is the Internet layer protocol tasked with defining how data is transferred
across the network, how devices are addressed, and how to route data appropriately. IP defines a
universal/global addressing method. It defines how to fragment, transport, and reassemble data packets
2 The IP packet network routes the Call Request packet to the Zone Controller. Upon receiving the Call Request
message, the Zone Controller checks an internal database to determine the location of all members in the
requested talkgroup (such as RF sites and remote dispatch site locations). The Zone Controller then assigns a
multicast group address to the call and sends the assigned multicast group address to all the participating RF sites
and the consoles at the MSO. This message is referred to as a Call Grant message and is sent in an IP datagram.
3 Upon receiving the Call Grant message, the RF and dispatch sites extract the IP multicast address from the
Call Grant. The assigned traffic channels at RF sites and the consoles at the MSO generate a group Join
message. The group Join message is an IP control packet.
4 Upon receiving the IP group Join message, the TETRA Site Controllers and dispatch site routers communicate
with RP routers in the system to set up an IP multicast distribution tree. This tree is used to distribute voice
payload traffic to all sites participating in the call.
5 The radio begins transmitting vocoded audio on the assigned RF traffic channel at its site. The audio is received
by the traffic channel and is placed in an IP datagram destined to the assigned IP multicast address (as assigned
in the Call Grant). The IP multicast packet is placed on the LAN.
6 The IP Multicast audio stream is distributed to all the RF and dispatch sites through the Rendezvous Point
router and IP multicast tree.
7 When the first user dekeys and a second member of the talkgroup transmits while the call is still active (call
hang time has not expired), the same multicast tree is used. Vocoded audio is received by the traffic channel at
the new source site and placed in an IP packet destined for the Rendezvous Point router of the group. The IP
packet flows down the same IP multicast tree generated earlier by the routers.
8 When the call is over (expiration of the message timer), the sites (RF or dispatch) generate an IP group Leave
message. The Leave messages cause the multicast tree to be taken down.
The preferred mode of operation for a Dimetra IP system is message trunking with PTT-ID. This parameter
is programmed in the system, through the User Configuration Manager (UCM), as message trunking, and
in the radios, through their programming software, as PTT-ID.
Audio traffic
Data traffic
Control traffic
Encryption protects the information from being deciphered and understood by anyone outside the system. Without
the proper algorithm and the encryption key, any intercepted traffic is received as a bunch of garbled digital bits
wrapped in packets. If there is no encryption, hobbyists or hostile groups can intercept and decipher traffic.
The Motorola secure voice and data solution uses sophisticated algorithms to protect voice traffic. Depending on
the algorithm used, a radio can be provisioned with a large number of keys. By rotating keys on a regular basis, it
would be nearly impossible for an interceptor to find the correct key and decrypt the traffic.
The figure below shows basic secure voice operation between two radios. The transmitting radio encrypts clear
voice using a particular key (CG456) and transmits the encrypted voice to the transport network. The secure voice
traffic is routed over the network while remaining in an encrypted form, and is transmitted to its intended recipient.
The receiver radio then uses the same key (CG456) to decrypt the traffic and provide clear voice to the user.
Compared to Air Interface Encryption (AIE), the secure voice solution adds an additional level of confidentiality to
the speech traffic and is an enhancement to the system. This service does not replace any of the other standard
TETRA security mechanisms, and can coexist overlaid on AIE.
The main difference between AIE and secure voice is that secure voice provides voice encryption all the way from
one radio to another. AIE only provides security for messages between the base station and the radios and it does
not provide any security for messages that exist within the infrastructure, whereas secure voice provides security
between the end users, even within the infrastructure.
Apart from voice, Motorola has also developed a solution for delivering encrypted data. End-to-End Encryption
for Short Data and Packet Data (E2EE SD/PD) is an overlay service that allows secure (digitally encrypted)
data communications between radios and data applications in the customer enterprise network (CEN).
Encryption/decryption services are provided by the system endpoints: Packet Data Encryption Gateway (PDEG),
Mobile Data Encryption Gateway (MDEG), Short Data Encryption Gateway (SDEG) and radios, so communication
remains secure between the source and the destination. Secure data is a supplementary service located on a
customer premises (the Switching and Managing (SwMI) infrastructure is not encryption aware). The solution
is based on the current key management solution, in other words, a symmetrical key exchanged with the KMF.
Digital encryption converts the digital data, using an encryption key together with an encryption algorithm, into an
encrypted message which is then transmitted. Only an endpoint that shares the same encryption key and encryption
algorithm is able to decrypt the transmission successfully. Other devices that do not have the proper key are not
able to receive intelligible information.
For more information see the Secure Voice, Data and Key Management manual.
One of the master sites (which are physical locations in Dimetra system containing one or more sets of
zone control equipment) in a multizone system is generally designated as the cluster MSO. This MSO
typically includes the cluster-level servers, including the combined User Configuration Server (UCS).
GPS
Server 1 Server 1 Server
Primary Secondary
Zone Server Zone Server NTS
EC
User Configuration Server
Core LAN Switch 1&2 Air Traffic Router
Zone Database Server
KMF NM Client MCC7500 Unified
Voice Logging Replay Event Manager
Station AIS GGSN1
Zone Statistics Server
E1 - VPN
CGE1 Router Router
CWR Panel
VPN
BTS Client
Remote Control Zone
Other Zone Mutually exclusive
The server components of the Network Management subsystem reside on the Primary Management Server
and include User Configuration Server (UCS), Zone Database Server (ZDS), Zone Statistics Server (ZSS),
Unified Event Manager (UEM), System Statistics Server (SSS), and Air Traffic Router (ATR).
Network management provides the tools, commonly known as FCAPS, for fault, configuration, accounting
performance and security management. The network management functions in Dimetra IP are distributed across
several applications and servers that are installed in one of three configurations: system, zone, and remote. The
configurations are designated by the name Operations Support Systems (OSS). The individual network management
building blocks of the Zone OSS and Cluster OSS can be divided into two categories:
Zone OSS: The Zone OSS refers to the network management system for a given Zone. The servers are
always colocated with the MSO equipment. Examples are Zone Database Server (ZDS), Air Traffic Router
(ATR), Zone Statistics Server (ZSS), and Unified Event Manager (UEM).
Cluster OSS: The Cluster OSS manages a cluster of up to four zones from a single location. To accomplish
its task, the Cluster OSS must have a routed path to all supported zones. The Cluster OSS consists of the
combined User Configuration Server (UCS), Unified Event Manager Server, and the Network Transport
Performance Server.
The Unified Event Manager provides the topology map, alarm browser, and MIB browser interface.
The Unified Event Manager application adds network management tools and hierarchical topology maps
specific to Motorola devices.
Traps and MIBs add fault and performance network management tools for the networking devices.
Telnet can be used to access the Command Line Interface (CLI) of the routers and core LAN switch.
A script on the Network Management Client (NM Client) is used to back up and restore the HP core
LAN switch OS and configuration file.
Clusterwide Fault Management on some systems may only refer to Dimetra Radio System managed
objects and not necessarily IP devices (Routers, LAN Switches) depending on network configurations.
GPS
Server 1 Server 1 Server
Primary Secondary
Zone Server Zone Server NTS
EC
VPN
CGE1 Router Router
CWR Panel
VPN
BTS Client
Remote Control Zone
Other Zone Mutually exclusive
MTIG is a general term used for all types of Motorola Telephone Interconnect Gateways. In specific terms, we can
indicate a relevant type of MTIG. MTIG-E1 is an MTIG that uses QSIG signaling towards the PABX. MTIG-IP is
an MTIG that uses SIP signalling towards the PABX. MTIG-E1 and MTIG-IP are mutually exclusive within a
zone, but not within a system.
After a KVL loads keys into a radio, the radio sends a receipt or acknowledge message. When the KVL is
connected with the PrC again, the acknowledge messages are loaded into the PrC and the successful status of
the key loading is maintained by the PrC.
The PrC also outputs authentication material and air interface encryption keys by CD to the Authentication Centre.
The AuC securely stores and uses these keys for authentication and air interface encryption purposes.
The Provisioning Centre is isolated from the network. It includes a client, database server, and PrC server all
integrated into one chassis. The PrC runs the Windows 7 operating system and provides a user interface for key
management operations.
The PrC uses CryptR 2 device for encryption and decryption of the key material.
For more detailed description of Network Time Server, see the Network Time Server manual.
GPS
Server 1 Server 1 Server
Primary Secondary
Zone Server Zone Server NTS
EC
E1 - E1 - Border VPN
CGE1 CGE2 Router Router
CWR Panel
VPN
BTS Client
Remote Control Zone
Other Zone Mutually exclusive
GPS
Server 1 Server 1 Server
Primary Secondary
Zone Server Zone Server NTS
EC
BH BH
Switch 01 Switch 02
VPN
BTS Client
Remote Control Zone
Other Zone Mutually exclusive
3.2.1 Switches
The following functional types of switches are available:
A virtual LAN is set up on each of the core LAN switches. The purpose of these as Transitional LANs (TLAN1
and TLAN2) is to carry traffic between the various core, gateway, and exit routers. The core, gateway and exit
routers connect to both TLANs. If an Ethernet port fails, traffic is transferred to the remaining TLAN. The core
LAN switch is the main Ethernet switch used to interconnect all the Ethernet interfaces for all servers, clients, and
routers. Devices are physically connected into the switch in a way that provides the highest reliability.
3.2.2 Routers
The master site network transport functions in the Dimetra system are provided by S6000 router and GGM 8000
gateway.
Two sets of two 62-pin high-density E1 connectors, each of which supports up to 12 E1 relays, for a total of up to
24 relays for each CWR patch panel. Core and exit routers are connected via the CWR patch panel in pairs of
CWR peers:
The left hand set of high-density E1 connectors on the CWR patch panel attaches to the two 12-port E1
modules on one core or exit router.
The right hand set of high-density E1 connectors on the CWR patch panel attaches to the two 12-port E1
modules on the other core or exit router.
For each pair of CWR peers, one high-density E1 connector (either the right hand or the leviathan connector)
supports the active relays, while the corresponding connector for the CWR peer provides redundancy and failover
protection.
24 RJ48-C connectors, each of which supports channelized connectivity at E1 line rates. These connectors
provide the direct connections to the site and interzone links.
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:
The MTS LiTE is available in the 260, 350, 380-430, 450-470 and 800 MHz frequency bands.
A typical MTS LiTE Site configuration includes four major functional components:
Base Radio
Site Controller (SC)
RF Distribution System (RFDS)
Power Supply
A Radio Frequency Distribution System (RFDS) distributes up to two Receive antennas to the base radio (BR).
The duplexer enables a duplexed Receive/Transmit function on one antenna, which further reduces the total
count on antennas per site.
3.3.1.2 MTS 1
The MTS 1 is a small, single base station designed to be wall mounted for indoor use or mast mounted for outdoor
use in larger systems. For additional capacity, two MTS 1s can be connected to work in a dual configuration for
additional capacity and resilience. The MTS 1 enclosure is dust tight and also protects against other environmental
elements, such as water. The MTS 1 provides up to 4 channels in a single cabinet or up to 8 channels in a dual
MTS 1 configuration. It is available in the 380 - 470 MHz frequency band. A typical MTS 1 site configuration
includes four major functional components:
Base Radio
3.3.1.3 MTS 2
The MTS 2 is a small, very powerful base station designed for indoor working without the requirement for cooling
fans. All modules can easily be accessed through the cabinet front door. Due to its small size a complete MTS 2
cabinet can easily be fitted into a 19" outdoor enclosure with heat exchanger. Note that the standard cabinet has air
convection holes so that it is not environmentally protected against water or heavy dust.
The MTS 2 provides up to 8 channels in a single 61 cm high cabinet. It is available in the 260, 350, 380-430,
450-470 and 800 MHz frequency bands.
A typical MTS 2 Site configuration includes four major functional components:
Base Radio(s)
Site Controller (SC)
RF Distribution System (RFDS)
Power Supply
A Radio Frequency Distribution System (RFDS) combines two transmit channels onto one antenna and distributes
up to three Receive antennas to the base radios (BRs). The duplexer enables a duplexed Receive/Transmit function
on one antenna, which further reduces the total count on antennas per site. The hybrid combiner is a wide band
component and does not need to be tuned on a certain frequency.
For expansions the main modules of the MTS 2 can be re used in an MTS 4. Expansions from MTS 2 to MTS 4 do
not require any modification of the antenna installation. The antenna installation can be re used without any change
and little more floor space is required for increased capacity supported by MTS 4.
3.3.1.4 MTS 4
MTS 4 is a high capacity base station. It provides up to 16 channels in a single 143 cm high cabinet or up to 32
channels in two cabinets. It is available in the 260, 350-370, 380-430, 450-470 and 800 MHz frequency bands.
A typical MTS 4 Site configuration includes four major functional components:
Base Radio(s)
Site Controller (SC)
RF Distribution System (RFDS)
Power Supply
A Radio Frequency Distribution System (RFDS) combines up to eight transmit channels onto just one antenna and
distributes up to three receive antennas to multiple base radios. Duplexers enable a duplexed Receive/Transmit
function, which further reduces the total count on antennas per site. For non-duplexed operation the MTS 4 also
comes optionally with a Tx-postfilter that allows sufficient space for up to three preselectors. This configuration
supports up to triple diversity un-duplexed with one Tx and three Rx antennas.
The MTS 4 prime cabinet is built up out of two card cages above one another and supports up to four base radios.
For expansions up to eight base radios an expansion cabinet of exactly the same size as the prime cabinet can be
added. An MTS 4 card cage with Base Radios power supply and SC is identical to an MTS 2 with the filter
and combiner section removed.
A second SC can be installed at the BTS site to provide active/standby redundancy. Redundant Site Controllers
are linked through a 10/100Base-T Ethernet interface.
The SC also provides frequency reference and timing reference. The SC has a high stability oscillator to provide
frequency reference signaling to the base radios. The SC also includes an internal GPS receiver which connects to a
GPS antenna through an RF feeder to provide timing reference. If redundant SCs are installed at the site, both
SCs require a separate GPS antenna connection. If NTS (Network Time Server) is present, it can be used as a
secondary frequency reference
A logical control path and logical manager path are maintained between the BTS site and the MSO. The control
path delivers control traffic between the BTS site and the Zone Controller. The manager path delivers network
management traffic between the BTS site and the network management servers.
The SC software is loaded through the Software Download (SWDL) application. The configuration parameters for
the SC are defined both through the Zone Configuration Manager and through Dimetra BTS (Base Transceiver
Station) Service Software (TESS).
The base station is able to provide air interface encryption by applying a cipher key and a user-defined offset
variable to the inbound/outbound coded traffic. To provision the base station for encryption, the base radio is loaded
locally with a secret infrastructure key through a Key Variable Loader (KVL). This infrastructure key is used to
decrypt cipher keys which are delivered over the network. The base radio uses the appropriate cipher key (SCK,
DCK, or CCK) to encrypt outbound traffic and decrypt inbound traffic.
The BTS base station software is loaded through the Software Download (SWDL) application. This application
can load software to the entire BTS site over the network, or can load software directly to an isolated base radio
through a direct connection. The configuration parameters for the BTS base station are defined both through the
Zone Configuration Manager and through Dimetra BTS (Base Transceiver Station) Service Software.
GBN
NM Client Dispatch
Console
Logging Re corde r
LAN S witch
Archiving Inte rfa ce
S e rve r
WAN
BTS
Trunking S ite
The MCC 7500-series Dispatch Console is Motorolas high-tier radio dispatch console system. A console dispatch
subsystem consists of the following components:
Archiving
Ethe rne t
Recorder
S witch
Device
Archiving WAN
Interface Route r
Server (AIS)
Desktop Speakers
The Dispatch Console PC supports two speakers through which a dispatch console operator can listen to audio.
Each speaker on a dispatch console contains unique audio; that is, an audio source cannot appear in multiple
speakers at a single dispatch console.
The speaker is designed for use near computer monitors.
Desk Microphone
The Dispatch Console PC supports a single desk microphone. The microphone is the AKG31/AKG33 and
gooseneck GN 30E.
Footswitch
The Dispatch Console PC can support a single footswitch with one pedal. The pedal controls the General Transmit
feature.
The footswitch allows users to operate the feature with their feet so their hands are freed for other tasks. If desired,
the footswitch can be permanently fastened to the floor.
Emergency Beacon
The Dispatch Console PC supports an emergency beacon that notifies the dispatcher with colored light when
an emergency call is received.
The Emergency Beacon feature is implemented as the set of green/yellow/red control lights and the buzzer
served by the dedicated application. It is installed on the Dispatch Console PC. The hardware is connected to
the computer via USB.
Each recorder can be configured to record up to 256 conventional channels or trunking talkgroups or
any combination of the two.
Each recorder can be configured to record a number of individual calls, based on a specific license.
Through the use of agency partitioning, only authorized transmissions may be recorded and/or accessed by
the replay station.
The logging system has replay stations that are permissions-based, allowing users to only listen to
appropriate channels/talkgoups.
The logging system allows users to conduct searches based on criteria such as time of transmission,
channel, and other call data.
Recordings can be copied to transferable media.
The logging system can include multiple logging recorders, MCC 7500 Archiving Interface Servers and
replay stations.
There are three hardware devices within a logging system:
The MCC 7500 Archiving Interface Server provides an interface between Motorolas radio system and the 3rd
party logging solution hardware which allows audio transmissions and radio system events to be recorded together
with associated call data.
The MCC 7500 Archiving Interface Server monitors selected group resources (channels/talkgroups) and individual
resources (radios, consoles) passes call-control information and audio to the recording device via the LAN. The
recording device utilizes a 100 Mb Ethernet port to communicate with the MCC 7500 Archiving Interface Server
and records this information on permanent or transferable media.
The 3rd party logging solution provides a GUI called AIS Administrator that allows an administrator to choose
which channels/talkgroups are to be recorded by each recorder.
The 3rd party logging solution provides a user interface capable of allowing a user to identify actions/calls that
occurred on the radio system, choose the desired call they wish to review, and play back the audio for that call
through a 3rd party logging replay solution. The 3rd party logging solution reconstructs the playback audio from
the vocoded samples that had been sent to the logging subsystem when the call occurred ensuring that the audio
quality is equal to that of the original transmission.
The logging system can be located on a dispatch console site, or on a logging only site without consoles. The
logging site can be either centralized (colocated at the MSO) or decentralized (at remote control site).
Logging Recorder
The 3rd party logging recorder is shipped pre-installed with all the necessary software including a Protocol
Processor licensed to operate with the Motorola MCC 7500 Archiving Interface Server and requires no direct
interaction from a user or dispatcher. The recorder requires an IP address before it can be connected to the LAN.
Once connected, it stores audio transmissions, call data and call events from the selected talkgroups/channels
on specified transferable media.
Recorders can store at least 48 hours worth of audio.
Replay Station
Audio and events which have been recorded by the 3rd party logging recorder(s) are accessed via a 3rd party replay
station. The replay station is a networked PC equipped with a keyboard, mouse, a monitor, and a speaker.
The replay station software displays information such as logged events and call data such as audio/event starting
time and duration of transmission. The replay station software also allows the user to listen to audio call recordings
to the user through a graphical user interface.
A replay station can access recordings on multiple 3rd party logging recorders, even ones which are not being
used with MCC 7500 Archiving Interface Servers. This provides the user with a complete view of everything
being recorded from a single point.
The CCGW allows up to 4 conventional channels to be connected to the console dispatch subsystem. At a small
control site (which is a location where users access dispatch consoles and network management terminals) only the
Conventional Channel Gateway function is performed by the Control Site Router. At all other control sites up to
ten CCGWs may be installed.
Conventional
Users
Conventional
Dispatch Site
CCGW Site
SwMI
MCC7500
Dispatch Site
Dispatch Dispatch
X-zone
Digital Audio
Dispatch PC CryptR Adapter Headset
Site Switch
SB
U
Kinesis Footswitch
Audio USB
Module
Filter Splitter
SB
Card XLR
XLR
XLR
Microphone
LLR Speakers
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.
Voice Logger
Tape Storage
3.4 Radios
Radios communicate with the RF sites using the TETRA standard. These radios support encryption, authentication,
and interfacing for a data terminal.
Providing higher power increases range and in-building performance, and so Motorola has added Class 3L (1.8W)
power output option. Taken together with high receive sensitivity this radio has the capability for maintaining
communications in the most demanding situations.
It has an improved operational effectiveness through:
Update your availability and situation using Status Messaging - monitor the progress of job assignments, or
call for support when needed.
Integrated GPS. Knowing where your resources are enables you to allocate tasks based on up-to-date
information (MTP3250 only).
The safety of MTP3000 Series is improved through:
Improved coverage in DMO operation, ensuring that users can communicate over a wider area or in
buildings or built-up areas.
Silent emergency, hitting the emergency button alerts colleagues to critical situations but sends and updates
your location, without showing any indication on the radio screen.
Rugged side connector. This new side connector with the range of available accessories ensures that
connection is maintained even in the most violent of situations.
The MTH800 features an extensive set of tools designed to enhance the personal safety, security, and efficiency
of both mission-critical and commercial users. Incorporating the latest technologies, it includes support for GPS
Location Services, high-grade encryption, data services and much more enhancing user safety and driving
efficiencies.
Ensuring full customer flexibility, two GPS protocols are supported, including the TETRA Location Information
Protocol (LIP), allowing users to:
Providing higher power increases range and in-building performance, and so Motorola has added Class 3L
(1.8W) power output option. Taken together with high receive sensitivity the MTP850 S/MTP850 FuG maintains
communications in the most demanding situations.
The MTP850 S/MTP850 FuG has an improved operational effectiveness through:
Access to information databases through integrated WAP browser - decide based on the latest information.
Update your availability and situation using Status Messaging - monitor the progress of job assignments, or
call for support when needed.
Integrated GPS. Knowing where your resources are enables you to allocate tasks based on up-to-date
information.
The MTP850 SMTP850 FuG has an improved safety through:
Improved coverage in DMO operation, ensuring that users can communicate over a wider area or in
buildings or built-up areas.
If the radio does not move in a specific time period, the Man Down feature sends an alert to the console
operator.
If the radio tilts more than the programmed angle, the Man Down feature sends an alert to the console
operator.
Silent emergency, hitting the emergency button alerts colleagues to critical situations but sends and updates
your location, without showing any indication on the radio screen.
Rugged side connector. This new side connector with the range of available accessories ensures that
connection is maintained even in the most violent of situations.
Enlarged rotary knob allows better radio glove-friendly functionality, thus allowing easier control talkgroup
and volume settings.
Operating a radio under protective clothing can be challenging. The MTP830 S/MTP830 FuG can safely
inter-operate with a wide range of specialist audio and push-to-talk equipment.
Man Down detector allows an emergency alert signal to be triggered at your control room when the radio exceeds
preset motion timer and tilt angle thresholds.
The MTP830 S/MTP830 FuG can be configured to send location reports when the emergency button is pressed
helping control room staff coordinate a response more efficiently.
The MTP830 S/MTP830 FuG automatically adjust audio settings based on pre-loaded profiles for detected
accessories. It also enables selecting the best audio profile for different working environments.
The combination of a highly sensitive RF receiver and transmission power that is adjustable to 1.8W provides
extended operational range.
The MTP850 Ex/MTP810 Ex ATEX TETRA terminals deliver safe and reliable communications for users with a
powerful set of features to harness the capability of TETRA.
The MTP850 Ex/MTP810 Ex deliver best in class audio performance in the typical noisy environments where
specialist users from industry or public safety operate.
The MTP850 Ex can be used in explosive gas and dust environments due to its high level of protection including
dust Zone 21 and 22.
The MTP810Ex is a low tier solution for use in explosive gas and dust environments dust Zone 22.
Operational safety is further enhanced with a range of features including:
integrated GPS receiver providing the ability to locate personnel, improving user safety and resource
management.
internal Man Down alert - this fully integrated solution triggers an emergency procedure when the carrier of
the radio remains motionless far a set period or falls down.
The simplified keypad with a large button surface makes the MTP850 Ex/MTP810 Ex easy to use with gloves.
Combined with the large scalable display fonts and icons, the MTP850 Ex/MTP810 Ex facilitates operation in
difficult environments with limited visibility.
The integrated WAP browser and Multi-Slot packet data enables rapid access to critical information in the field.
Applications are further enhanced with ability to have simultaneous Short Data Service (SDS) and Multi-Slot
packet data services through the TNP1 protocol.
The Motorola TCR1000 Covert radio is the ideal solution to ensure secure communications in surveillance covert
type operations allowing officers to blend right into the crowd. Motorola TCR1000 Covert TETRA radio delivers
high-quality communication in a light and discrete package for those critical undercover applications.
There are no compromises in the design of the TCR1000. Motorola worked closely with police forces to ensure that
it is intuitive and simple to operate, truly Technology that is Second Nature. The TCR1000 incorporates control
features matched to the needs of officers in covert operations. Its design enables easy hiding inside of light clothing.
A unique portfolio of covert accessories complements the TCR1000 and offer additional flexible options for
undercover officers. This radio operates at 1 watt and the option for a body mounted antenna ensures excellent
coverage and maintains the discreetness of the radio.
A small, easily concealable Remote Control Unit (RCU) controls the radio. The RCU allows the user to answer
or to initiate calls, change talkgroups, and volume. It also allows using special surveillance features such as
whisper mode or communication tones (like PTT Double Push feature). A connector is provided on the RCU to
attach a remote PTT unit.
Developed for organizations where rugged and versatile mobile terminals are essential, Motorola MTM800
Enhanced is ideal for use where the application, location and/or circumstances demand fast, reliable, no-nonsense
solutions.
Ease-of-operation in the most demanding situations unsurpassed audio quality, intuitive keypad, and
high-definition, color display combined with a sleek yet durable design.
Dust and water resistant to IP 54. rain, salt, fog, and dust protection tested to MIL 810 C/D/E/F for the
standard control head.
Motorcycle control head rated IP67 for dust and water resistance
The MTM800 Enhanced also supports the full suite of TETRA security functions, including air interface encryption,
and End-to-End encryption. Users can request assistance by simply hitting the emergency button, which not only
alerts colleagues to critical situations, but also sends an update dispatch on the user location. The radio is able to
switch to covert mode at a press of a button. The radio has an integrated GPS receiver that enables users to locate
their mobiles, and provides location-based services and mapping capabilities.
The radio offers various installation possibilities from typical Dashboard installation to Dual Control Head
installation using an additional junction box. Currently the following options are supported:
Trunnion Installation
Dashboard Installation
Desktop Installation
Remote Mount Installation
Motorcycle Installation
Dual Control Head Installation
Data Box Radio Installation
Figure 3-33 MTM5500MTM800 FuG ET in Mixed Dual Control Head Configuration with eCH and
TSCH
With its best in class RF sensitivity and 10 W transmit power capability, the MTM5400/MTM5500MTM800
FuG/MTM800 FuG ET Series set a new benchmark for TETRA RF performance.
The MTM5400/MTM5500MTM800 FuG ET Series support multiple modes of operation that enable enhanced
workflow management and improved communications in areas where network coverage is weak or unpredictable.
The integrated DMO Repeater is Type 1A compliant, operating on just a single RF carrier for efficient spectrum
usage.
The MTM5400/MTM5500MTM800 FuG ET Series feature an integrated gateway that connects users operating in
Direct Mode with control room staff and other colleagues on the trunked radio network. A comprehensive set of
gateway services is supported, including configurable handling of individual and group calls.
Advanced Remote Terminal Management enabled through software, this ground-breaking capability allows the
MTM5x00MTM800 FuG/MTM800 FuG ET Series to stay live while being programmed and software upgraded.
This feature works to maximize productivity and eliminate radio downtime.
The MTM5200/MTM5400MTM800 FuG mobile offers comprehensive and flexible installation options. The
radio is fully DIN-A compatible and supports a wide range of configurations including customized multiple
control head, desk, and motorcycle install variants.
Do not connect MTM5200, MTM5400, and MTM800 FuG Control Heads to the Enhanced (Ethernet)
MTM5500, MTM800 Fug ET radio (and the other way around). Even though mechanically possible,
it is incorrect and will result in hardware malfunction (broken transceiver).
Use proper Ethernet cables to connect Ethernet Expansion Head with TSCH and eCH. Transceiver
can be broken if not connected properly.
Fixed Portrait
Clockwise Rotation
Historical: these are static reports that cover a specific time interval. The amount of historical information
that can be recovered depends on the specified time interval
Dynamic: These reports are real-time, short term reports that are updated for each interval of time selected
by the user.
10
TNPS UCS
10 1 15 10 10
10 16 5
10 11 2 12 17 10 10
19
10 9 3 4
Dispatch CCGW ZC ATR ZSS
Consoles 8
7 18
14 10 6 13
Interaction Description
Replication/synchronization of database records occurs between the User
Configuration Database (UCS) and each Zone Database. When changes are
made to individual records in the UCM, the UCS replicates the new or changed
information to each of the Zone Databases. The administrator can also run a
1 synchronization command to force the UCS to download its entire database to a
particular Zone Database Server (ZDS). If any problems occur with the integrity
of the User Configuration Database, a full copy of the database can be restored
(promoted) from any of the Zone Database Servers through the Administrator
menu.
Radio (subset of UCS database) and infrastructure database export from the ZDS
to the Zone Controller. The Zone Controller saves this information in its Local
2 Database, and uses the information to create the home location register (HLR) for
the zone. Diagnostic and fault information, including fault information proxied
for other devices, are sent through this link to the ZDS.
Raw call traffic information is passed from the ZC to the ATR which formats the
information and generates the Air Traffic Information Access (ATIA) stream.
3 The ATR generates an ATIA Log, which contains records of the call processing
information that are made available to the ATR. RCM information is passed
from the ATR to the ZC.
Zone statistical data is sent from the ATR to the ZSS to compile statistical
4
information on a per zone perspective.
Zone statistical data is sent from each ATR, within the cluster, to the SSS to
5
compile statistical information on a per cluster perspective.
Site statistical data is sent from the BTS to the ZSS to compile statistical
6
information on a per zone perspective.
Call requests, channel assignments, call terminations, and other call processing
information is passed between the Zone Controller and the BTS sites. When a
7 radio requests a call, the BTS site sends the request information to the ZC, the ZC
determines how to set up the call, and the ZC sets up all the resources needed for
the call.
Call requests, channel assignments, call terminations, and other call processing
8
information is passed between the Zone Controller and the dispatch console.
Call requests, channel assignments, call terminations, and other call processing
9
information is passed between the Zone Controller and the CCGW.
Unified Event Manager derives its listing of system objects from data received
10 from other boxes. Device status information is derived from Simple Network
Management Protocol (SNMP) agents.
The Zone Database Server sends any new or changed configuration information
11
to the dispatch console. Fault information is sent from the consoles to the ZDS.
12 Configuration data is passed from the ZDS to the ATR.
The Network Time Server (NTS) is periodically polled for a time reference
13
packet from other servers and network components.
Interaction Description
Each client workstation runs the Private Radio Network Management (PRNM)
Suite of applications. The following list shows the servers that support PRNM
Suite applications:
Physical, hardware-based component view describes how the system components work together to
move the necessary control and audio signals throughout the system to make calls happen. Using this view,
you can organize the system components hierarchically, or by subsystem.
Logical, software-based system view. describes how the management software (in all the elements
of the fixed infrastructure) and mobile unit software work together to make calls happen. This approach
provides an understanding of how the system is configured, how the system tracks mobile units as they roam
throughout the coverage area, and how the system actually processes call requests made by mobile users.
At the centre of call processing is the equipment at the MSO. This equipment provides the following functions:
The Zone Controller processes requests for registration, individual dispatch calls, group dispatch calls, and
telephone interconnect calls, validates the requests and assigns the necessary resources to set up call services.
The Network Management (NM) subsystem provides the infrastructure, radio and user information
necessary to coordinate the resources necessary for the different types of calls.
The network transport equipment (routers, switches) provides the IP connectivity to set up the paths that
are required for call processing to take place. The network transport equipment makes it possible to send
voice through the system as IP packets.
User Configuration
User configuration information consists of static or fixed user configuration.
Infrastructure Configuration
Infrastructure configuration information defines how the underlying Fixed Network Equipment (FNE)
handles signal flow. For example, this type of configuration determines which MTIG, site, and zone
resources are assigned to a call. In general, this type of configuration is handled by Motorola personnel prior
to and during system installation and will not be described further.
The User Configuration Server (UCS) through the User Configuration Manager (UCM) application. Within
this application, records are built for radios, radio users, dispatch consoles, talkgroups, and multigroups.
Parameters that affect the operations of all radios in the system, such as site access denial, are also entered in
the UCM.
The radios through their specific programming software.
Static configuration information may be divided into four parts:
Valid site settings, in conjunction with the Site Access Denial setting (see 5.1.2 Infrastructure
Configuration, page 5-7) play an important role in mobility management when a radio attempts to
register or a group member attempts to register to a site.
The static user configuration information is referenced by the system each time a radio attempts to register to a site
and/or affiliate with a talkgroup.
Configuration information must be consistent when programming the UCS should be consistent with the
configuration information in the radios.
Default access allows all radio users and talkgroups to access the system with a predefined set of
permissions. Individual control of radio users and talkgroups is not possible. This mode of operation is not
recommended for use under normal operating conditions.
The zone object in the Zone Configuration Manager (ZCM) configures and manages the attributes relating to a
specific zone. The Zone Controllers use these parameters to allocate resources. The zone object configuration
information is replicated from the Zone Database Server (ZDS) to the User Configuration Server (UCS).
Two of the fields in the zone object record determine whether radios are allowed to access the system only if they
have a record in the UCS, or whether they can access the system under default conditions using a default record.
The fields are called Individual Default Access Permission and Talkgroup Default Access Permission.
Using the UCM application, all individual and talkgroup IDs are entered in the UCS.
Using the applicable programming software, each radio is programmed with the system ID, its unique
individual ID, and as many talkgroup IDs as needed.
A system with a single zone requires that all individual and talkgroup IDs be assigned to Zone 1. IDs
mapped to non-existing zones can not be used.
Home Zone mapping requires that all IDs be accounted for in the ranges used to create a map. Whether the map
consists of one range or 2048 ranges, IDs 0 through 16.777.215 must be assigned to the map.
5.1.1.6 Profiles
A profile is a master list of common attributes or capabilities used by radio users, talkgroups, and multigroups.
Creating a profile allows you to enter the information one time and reference the profile from an individual record.
One does not have to enter the information separately into each record. You can create a different profile for each
type of function and group of users in your system, up to a maximum of 2000 profiles.
Using a profile helps to reduce the amount of data that has to flow through the network between the UCM and the
Zone Controller. Profile information includes data that relates to radios, radio users, and talkgroups who perform
the same function. For example, all radio users associated with the Fire Department require the same resources, so
you can use a profile to create a master file for their records.
A record can have a one-to-one relationship with a profile (up to the 2000 profile limit), or many records can
be mapped to the same profile.
You can use a Radio User Capabilities Profile object to define a set of parameters that are common to a specific
group of radio users. Every radio user is assigned a Radio User Capabilities Profile.
5.1.1.7 Templates
A template provides the means to configure a record that can be applied to radio users who need the same set of
system access parameters. Templates consist of a combination of attached profiles and parameters set directly on
the record.
5.1.1.9 Talkgroup
The talkgroup object consists of information that identifies a group of radios that communicate and interact together
on the system. Talkgroup and multigroup IDs are selected from the same range of valid IDs that are available for
the individual IDs.
The total range of identification numbers used by the system is 16.777.218. The IDs are distributed as follows:
ID 0 is reserved by the system and cannot be assigned to a radio, console resource, or group.
1 - 9.999.999 are valid individual or group IDs.
10.000.000 - 13.999.999 is the Dimetra extended range for individual or group IDs.
14.000.000 - 16.777.214 is reserved.
16.777.215 is used for site wide calls for addressing all units.
16.777.216 is assigned to the SZ$INIT record.
16.777.217 is assigned to the SZ$DEF record.
5.1.1.12 Multigroup
The Multigroup object is used to create records that identify a group of talkgroups that are the target of multigroup
announcements.
The type of rejection depends on the valid sites set for each radio and affiliated talkgroup in the corresponding
UCM records. For example, with a site access denial setting of BOTH, if you have a Radio User that is valid at the
site but a talkgroup that is not valid, the radio is allowed to register and stay at the site. The radio is allowed to
make unit-to-unit calls but requests for a talkgroup call are rejected.
Continuing this example, if the mobile user switches to another talkgroup, the radio unit sends another affiliation
request, which is accepted or denied based upon the valid site setting for that group. If it is a valid group, the system
begins to provide both group and individual call services at that site.
Valid site and site access denial are the means by which a system manager can specifically control the operating
sites and individual/talkgroup services for each radio.
System engineers create the new Source Site ACC record when configuring the system initially.
Subsequent users can only open and modify the existing record. You must consider the ramifications
when changing the initial configuration.
In large systems, the radio codeplug may not contain all of the frequencies for adjacent sites to which the radio
may need to roam. Additionally, new sites may be added to the system and it may be impractical to bring all of
the radios in for reprogramming.
Selection and programming of the adjacent sites lists requires detailed knowledge of the systems coverage
characteristics. Random selection of sites can severely impact system operation as radios may experience
problems accessing the system.
Configuration information is distributed throughout the system based on the assignment of the home
zone to a given ID. A Zone Controller stores only the configuration information for those individual and
group IDs that are home to that zone.
For group call services, the home zone of the group is always the controlling zone for the call, regardless of
the zone where the group member is currently registered. Depending on configuration, this can impact the
number of interzone calls versus the number of single-zone calls that take place in the system. This, in turn,
can affect the number of interzone resources that are needed between any two pair of zones.
User configuration information is entered in the appropriate objects in the UCS: Radio and Radio User for
individuals, Talkgroup and Multigroup for groups. Once entered, user configuration information is replicated
automatically to each zone in the cluster, where it is stored in the master database of a zone. The replication
process makes it possible, if needed, to use any zone to promote its copy of the user configuration information
back to the UCS in the cluster.
Next, based on the home zone mapping, each zone transfers the configuration information for its individuals
and groups to the Home Location Register (HLR) in the Zone Controller. The home zone mapping information
is replicated to each zone from the UCS in the form of map tables. There are two map tables: an individual
to home zone map and a group to home zone map.
Whenever any individual or group configuration information is needed by any zone, it gets that information from
the HLR in the home zone of an individual or a group.
UCS
ZDS ZDS
Zone Zone
Controlle r Controlle r
IHLR IHLR
GHLR GHLR
Zone 1 Zone 2
The HLR stores access configuration information for both individuals and groups along with the current site
location of the individual or group member. The VLR is a temporary copy that is placed in the zone where the
radio is also present, and is deleted when the radio is shown up in another zone. When a radio is shown up in
another zone, a new VLR is created again.
There are two VLRs - one for individuals and one for groups. The individual VLR stores the access
configuration information and current site location for each registered individual radio unit in the zone.
The group VLR stores the access configuration information for a group that has affiliated members in the
zone along with the site location of each affiliated member.
UCS
ZDS ZDS
Zone Zone
IHLR IHLR
Controlle r Controlle r
IVLR IVLR
GHLR GHLR
GVLR GVLR
Zone 1 Zone 2
All operator positions monitoring a talkgroup and the logging recorders assigned to a talkgroup affiliate
with the system. Thus, operator positions and logging recorders have entries in an VLR of the zone.
Call request
Call setup
Audio routing
Call continuation
Call teardown
Group-based - Group-based calls are services that provide for effective group (one-to-many)
communication.
Individual Calls - Individual calls are services that provide for effective individual (one-to-one)
communication.
The following describes these five call types using the call processing structure.
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.
When the caller presses the PTT button, the call request, in the form of an Inbound signaling Packet (ISP)
is sent over the control channel to the current site. The information is passed to the Site Controller for
processing and routing to the Zone Controller through the site router.
The Zone Controller, for the zone where the request originates, determines if this is a valid call request by
checking the access configuration information stored in the VLR. If it is a valid request, the Zone Controller
checks its talkgroup-to-home zone map table to see which zone is the home zone of the talkgroup. For group
calls, the home zone of the group becomes the controlling zone for the call, regardless of which zone the
caller is in when the request is made.
When the call request originates from a BTS site, the request is encapsulated as 10Base-T Ethernet packets by
the base station and is sent to the Site Controller. The controller then encapsulates the traffic in Frame Relay
packets and transmits the traffic to the MSO.
LAN Switch
Core
Router
The Zone Controller checks the VLR to determine talkgroup affiliations and radio location. This
information indicates which sites need to participate in the call.
The Zone Controller checks that all needed resources, such as channels at sites and consoles are available to
establish the call. See 5.8 Busy Call Handling, page 5-34 for details.
LAN Switch
Core
Router
Process Steps
1 Routing information is sent to the appropriate MSO and remote site routing equipment.
2 The Home Zone for the call request sets up a core router as the distribution point for the audio information. This
audio focal point is known as the Rendezvous Point (RP) and its router becomes the Rendezvous Point router.
The Rendezvous Point for intrazone audio is the core router.
4 The Site Controllers in the BTS sites broadcast the channel assignment, through the main control channel
(MCCH), to the radios and send the activation message to the assigned traffic channels. The assigned traffic
channels send a join message back to the MSO.
5 The sites cause the activation of the receive and transmit circuits in the designated traffic channels.
6 The receiving radios tune to the assigned traffic channel at their respective sites.
Process Steps
1 When the radio user speaks into the microphone of the radio, the radio converts the speaker's analog audio into
ACELP and transmits the signal to the assigned traffic channel.
2 The audio signal is transmitted by the radio over the assigned frequency to the caller's site and received by the
assigned traffic channel.
3 The traffic channel places the audio into the site's Ethernet LAN as IP packets and routes the audio signal
through the site router to the assigned rendezvous point router (core router) at the MSO.
4 The rendezvous point router forwards the audio to any device that responded with a join message to the Zone
Controller's call grant. The BTS base radios respond with a join message.
5 The talkgroup members already locked on to the traffic channel receive the audio.
Control information flows continually during a call: over the control channel during call setup and
embedded in the digital audio signal during the active call phases.
Process Steps
1 When the speaker releases the PTT button, a message is sent to the controlling Zone Controller. If the call is
message trunked, a message hang time timer starts when the message is received. All system resources,
previously assigned to the call, are held available during the timer's hang time period.
2 If a person responds to the initial caller, by pressing the PTT button within the hang timer period, the call
continues. The message hang timer is reset and the new speaker's audio is routed as the source audio using
the traffic channels and router assignments already allotted for this call.
Notifies the consoles of the talkgroup call and its audio source, if needed. The Zone Controller relays the
audio assignments and the channel assignments to the appropriate remote sites through their site control
paths.
Once the resources are assigned, the rendezvous point router becomes the centre of control for audio
distribution.
At each site the Site Controller:
If resources are available at the new site and the talkgroup call is already active in the new zone (there are
talkgroup members at sites within the zone), the roaming user experiences a short loss of audio while the
call is set up at the new site.
If resources are available in the zone to set up the call but the talkgroup call is not active (there are no
affiliated talkgroup members in that zone), the roaming user experiences a longer loss of audio while the
interzone call setup process takes place. The access control information needs to be transferred from the
home zone HLR to the HLR in the new zone and from there to its VLR, the call request validated in the new
zone, and a channel assigned and activated at the new site.
If resources are not available at the site or in the zone, the call continuation request to the new zone is
placed in its busy queue. When the needed resources become available, the roaming user rejoins the call in
process. A longer loss of audio occurs in this case.
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.
Emergency alarm- A radio to console or Radio Control Manager (RCM) function that is sent over the
control channel.
Emergency call- A radio or console call function.
A value of 3660 disables the message timer for emergency calls. Radio Users have unlimited time between
PTTs.
A console operator can initiate an emergency call on any talkgroup or multigroup being monitored. The system
handles a console emergency call request the same as a radio-generated request, with one exception: a console
generated emergency call has an unlimited hang time, so the call stays active until the operator knocks down the
emergency call at the operator position.
Emergency calls initiated from the console are always processed in Ruthless Preemption mode when
resources are not available to grant the call immediately.
In individual calls, the initial call request goes over the control channel. An audio channel is not assigned
until the target radio responds to the initial request. Audio channel resources are assigned once the target
radio responds to the call request.
Gateway Zone
Router Controller
LAN Switch
Core
Router
A private call begins with a call request. The call request resolution determines whether the call is set up or not.
Requests are rejected if the target radio does not respond to the request or if the target radio is not registered with
the system. Other reasons for a call to be rejected would be configuration-related (one of the radios blocked from
private calls, site not allowed, and so on).
Process Steps
1 A private call request is initiated when the caller selects the appropriate mode on the radio, and then enters the
target radio's ID or selects it from a list.
2 When the caller presses the PTT button (semi-duplex) or presses the send button (full-duplex), the call request is
sent over the control channel to the current site. The information is passed to the Site Controller for processing
and routing to the Zone Controller at the initiator's MSO.
3 The Zone Controller receiving the call request checks its VLR to see if the requesting individual is configured to
make private calls.
4 If the call is allowed, the Zone Controller checks its individual VLR to see if the target radio is currently
registered in the zone, and if it is, at which site.
5 If the target radio is active (registered) in the same zone, the Zone Controller sends it a private call request
over the control channel at its current site.
If the target radio is not in the current zone, the caller's Zone Controller determines the target radio's home
zone by checking its individual-to-home zone map.
6 The caller's Zone Controller sends a message to the target radio's home Zone Controller requesting the current
location of the target radio (which the home Zone Controller gets from its individual HLR).
7 Once the target radio's current zone is known, the receiving Zone Controller sends the call request to the
Zone Controller in that zone.
8 The target radio's Zone Controller checks its individual VLR for the target's site location and sends the call
request to the target radio through the control channel at its current site.
9 If the target radio is not registered with the system, the requester receives a call reject. Otherwise, the requester
hears a ringing tone. If the target radio does not respond within the time-out period, the call request is ended.
10 If the target radio responds to the call request, the private call is set up.
Process Steps
1 Audio is received by the assigned traffic channel at the local site and is routed to the RP at the zone.
2 The RP routes the audio packets through the exit routers where they get encapsulated as Frame Relay packets
for transmission to the participating sites.
3 When the target user responds, the same path is used, but the source and destination of the audio are swapped.
4 For semi-duplex calls, the call is terminated when neither party responds within the defined message hang-time.
Full-duplex calls are terminated when either party presses the end button.
A transmitting radio user in an active individual call cannot roam automatically. When a transmitting
radio fades out (due to moving away from the current site), the system detects the loss and begins the
call termination process.
Dispatch
To PABX
MTIG-E1 Console
Zone Gateway
Controller Router
EC
LAN Switch
Core
Router
Patch
Panel
BTS
The telephone interconnect feature builds upon all of the configuration and infrastructure discussed up to this point.
With talkgroup calls and unit-to-unit calls, all parties to the conversations all reside somewhere on the Dimetra
IP system.
For telephone interconnect calls, one of the parties is outside of the Dimetra IP system and is connected through
landline telephone to the radios in the system.
The Dimetra IP system supports radio-to-landline and landline-to-radio interconnect calls. It does not
support interconnect calls to and from talkgroups.
5.5.2.2 Configuration
Radios must be properly programmed to make and receive telephone interconnect calls.
Each radio is assigned an interconnect profile (the Radio User Interconnect Profile object in the UCM). The profile
is created in the UCM and assigned to the radio user. Your system may have various individual interconnect profiles
available for assignment to radio users.
One of the settings in the individual interconnect profile specify a Priority Level. The system uses priority levels to
determine the assignment of system resources during busy periods. There are ten levels of priority available, levels
1 through 10. The highest priority, level 1, is reserved for emergency calls. A telephone interconnect call can be
assigned a priority level 2 through 10, depending on individual requirements. Level 2 is the highest assignable
priority, while level 10 is the default priority setting.
See 5.8 Busy Call Handling, page 5-34 for more information on how busied calls are handled by the system.
The request for an interconnect call is placed in the busy queue if the radio initiates the call and no channel
resources are available.
If no MTIGs are available, interconnect calls are busied until one becomes available. This means that the
call is placed in a queue and can be active as soon as an MTIG becomes available.
Regardless of the infrastructure configuration, user limitations, or channel availability, programming of the
radio can prevent interconnect calls from being attempted.
If shared service dictates that an interconnect call needs to be placed in the busy queue, the call is placed in
the queue, even if there is a channel available at the site.
Call Setup
When and where to use:
This process describes the events that occur during the setup of a successful radio-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 digits
information.
3 The system verifies that the radio is authorized for telephone interconnect service.
4 The system determines which zone's telephone interconnect is used for the call. The location of the Motorola
Telephone Interconnect Gateway determines the controlling zone for the call, the point where the multicast
addresses originate, and the location of the RP for the call.
5 Radio system resources are assigned to the call. The resources include the site where the radio is located, a
gateway router for distribution to the network, resources in the MTIG for audio conversion between ACELP
and PCM, and for timeslot or speech channel access to the external network.
6 The Zone Controller sends two multicast addresses, one for the receive side of the call and one for the transmit
side. Transmission of the multicast addresses sets up the audio RP.
7 The MTIG and sites send a join message to the RP for the assigned multicast addresses.
8 The system checks the telephone number dialed to verify that the number represents a valid telephone number
and that dialing restrictions allow the radio to initiate calls to the dialed telephone phone number.
13 The caller hears a ringing tone to indicate that the call is being placed.
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.
The Zone Controller determines whether the radio is valid for individual services at the new site, and
that the new site is capable of interconnect service.
If the required resources at the new site are available, the Zone Controller grants the call immediately.
If the required resources at the new site are busy, the Zone Controller places the call in a busy queue. The
landline user is not notified about the busy condition of the call.
Process Steps
1 The radio, remote data terminal, or host creates a message, selects the Short Subscriber Identity (SSI) of
the recipient, and sends the message. If a radio is sending the short data message, the message is delivered
over the control channel.
2 The short data message is delivered to the short data router (SDR) within the cluster.
3 The SDR observes the SSI for the recipient of the message and checks the IHLR/VHLR information to
determine where the recipient is located.
4 The SDR routes the short data message across the network to the intended recipient (host or radio).
Authentication only
Authentication and air interface encryption (using TEA1)
Authentication and air interface encryption (using TEA2)
Authentication and air interface encryption (using TEA3)
If a system includes both authentication and air interface encryption, either service can be enabled or disabled.
The Dimetra IP system allows the following modes of system operation:
5.7.1 Authentication
Authentication is used to verify that a radio accessing the system is valid, and to reject any unauthorized parties
from accessing the system. The Dimetra IP system uses a challenge-response-result protocol to authenticate both
the radio and the infrastructure.
The authentication process begins with the infrastructure sending a challenge to the radio. The radio calculates a
response based on the challenge, and sends the response to the infrastructure. If the response from the radio
equals the expected response by the infrastructure, then the infrastructure indicates that the authentication result is
successful and grants access to the system. If the response is not correct, then the infrastructure indicates that the
authentication result has failed and rejects access to the system.
When the radio provides the response described above, and the radio supports mutual authentication, the radio
also provides a challenge to the infrastructure. The infrastructure generates a calculated response to the radio to
verify that it is genuine. If the infrastructure's result matches the result expected by the radio, then the radio
indicates that the authentication result is successful to the infrastructure. On receipt of this successful indication, the
infrastructure grants access to the system.
MAC He a de r
Cle a r P a yloa d
Ke y
Offs e t
Encrypte d P a yloa d
Enab-
SCK CCK/DCK
Class Authentication OTAR GCK le/Dis-
Encryption Encryption
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 during
cell reselection to a cell of a different security class.
Level 1 = The highest priority. Reserved for emergency calls. Level 1 cannot be assigned to any other
call types.
Level 2-10 = May be assigned to talkgroup, individual, or telephone interconnect calls. Level 2 is the
highest assignable priority, while level 10 is the default priority setting.
AllStart
FastStart
These calling features are assigned to the groups in the User Configuration Manager (UCM) application.
5.8.2.1 AllStart
An AllStart setting for a group indicates that all the available resources for the call must be present for the call to
start. An AllStart call requires the following resources before a call is granted:
If any of the above conditions are not met, the call is placed in the busy queue.
5.8.2.2 FastStart
A FastStart setting for a group call indicates that only mandatory resources (that is, critical sites, critical resources
and requested sites) are required to grant a call. Any other resources available at the time the call is set up are also
included in the call. In FastStart, not all affiliated members in a talkgroup must have a channel available in order
for a call to start. FastStart requires the following resources before a call is granted:
When a group call is busied, the priority that is assigned to the call in the queue is determined by the higher
of the individual priority of the talkgroup or the requestor. For example, if the talkgroup is priority 8 and
the requestor is priority 5, then the call is queued with priority 5.
If any of the above conditions are not met, the call is placed in the busy queue.
When a private call is busied, the priority that is assigned to the call in the queue is determined by the
better of the target or individual priority of the requestor. For example, if the target's priority is 8 and the
priority of the requestor is 5, then the call is queued with priority 5.
Private calls can have a priority level assigned that determines how the call request is serviced in the busy queue,
the higher the priority, the sooner the call gets serviced.
When a radio has been rejected from using a particular service, the Zone Controller sends an abort message to any
resources that need to be released from the service, then sends a reject message to the radio. The following items
are typical reasons why a radio may be rejected during registration or during a call request.
The radio may be sending an individual ID or talkgroup ID that is not loaded in the memory of the Zone
Controller.
The radio may be requesting a service that is restricted or not available to the particular radio.
The system or the receiving radios may not support the call type requested by the initiating radio.
The system may be in a failure situation. Depending on the settings and the situation, the sites may be
in local site trunking and only allow certain types of calls, or the Zone Controller may be using default
access permissions.
The radio may be calling an individual or talkgroup that does not exist or that is not registered with the
system.
The radio may not be configured to make the requested type of call.
For talkgroup calls, a console that should be attached to the call may not able to participate in the call.
The radio is not operating at one of its valid sites.
The zone is not able to communicate with the home zone of the initiating radio.
The zone is not in interzone trunking with the other zones that need to participate in the call. The particular
resources may not be available for the call.
Generally, a service state for a site other than wide area trunking causes the radios at the affected site to
attempt to register at a site that is in wide area trunking mode.
State Definition
Wide-Area Trunking Wide-area trunking is the normal state for a site within a zone. In this state, the site
receives call processing instructions from the Zone Controller. A radio registered at
the site can communicate with any other radio in the system. The basic criteria for
wide area trunking includes an active RF site control path between Zone Controller
and site, an enabled audio rendezvous point in the zone, a control channel and a
traffic channel at a site.
Local Site Trunking Local Site trunking mode is entered when the remote site loses communication
with the Zone Controller. In this mode, the remote site takes over call processing
responsibility. A radio registered at the site can communicate only with other radios
registered at the same site.
Group-based services
Individual-based services
Group-based and individual-based services each have their own level of service availability, based on their
interzone trunking state.
The three levels of group service availability are based on the perspective of a group member from the current zone
to every other zone in the system, and whether the current zone is the assigned home zone of the group.
5.9.2.1.1 Example 1
It is possible for some members of a talkgroup to have zone isolated service for a short interval during loss of
the links between the zones (generally microwave).
In the figure, the link between Zone 1 and Zone 3 is down (interruption of interzone trunking), while the
links between Zones 1 and 2, and between Zones 2 and 3, are intact.
The home zone of the talkgroup A is Zone 1.
A user in Talkgroup A placing a call in Zone 1 or Zone 2 has full interzone service availability.
Talkgroup A members in Zone 3 have zone isolated group service availability for a short period of time
while the master site routers reestablish the call through an alternate IP path, in this case, through Zone 2.
5.9.2.2.2 Example 1
User 1 is in Zone 1, its individual home zone.
User 2 is in Zone 2, its individual home zone.
Zone 1 and Zone 2 are in interzone trunking.
In this case, all criteria are met (see the figure below).
Figure 5-13 Interzone Individual Call with Radios in Their Home Zones
5.9.2.2.3 Example 2
In a less commonly occurring example:
Figure 5-14 Interzone Individual Call with Radios Not in Their Home Zones
Condition Alert Hysteresis. Proportional to the time taken to clear an interference condition, dependent also
on the rate of packets received and the proportion of interference to non-interference packets.
Condition Alert Ratio. Proportional to the frequency of received interference packets that trigger an
interference condition, dependent also on the ratio of interference to non-interference packets.
Received Signal Level Threshold. The minimum received signal strength for corrupt packets to be classified
as interference.
Performing a user initiated switchover from the local user terminal could have adverse affects, like
increased down time, on system operation and should only be used when access through the ZCM
application is not possible.
The following explains what causes an automatic switchover and how the system reacts when an automatic
switchover occurs and when a user-initiated switchover occurs.
For information about performing the user-initiated switchover and Zone Controller redundancy and
switchover, see Configuration Management, Call Processing Subsystem.
Due to the severe system impact of a switchover event, user-initiated switchover should be initiated
ONLY when absolutely necessary.
User-initiated switchover is a feature that gives you the ability to disable the automatic switchover feature
and perform a user-initiated controller switchover. The feature uses the Zone Configuration Manager (ZCM)
application. If the Network Management link is down, and a user-initiated switchover still must be performed,
switchover may be done through the Zone Controller Administration menu through the Local User Terminal. User
initiated switchover is typically used when performing a software upgrade or performing maintenance such as
replacing a faulty Field Replaceable Unit (FRU) that did not cause an automatic switchover.
Verify the health and status of the standby controller subsystem in Unified Event Manager before
performing a user-initiated switchover or take any kind of action that results in a controller switchover.
Process Steps
1 In case of failure of any crucial components causes the standby controller to compare its operational health
against the health of the active controller. An automatic switchover is initiated if the standby controller is
capable of wide area trunking.
2 If the standby controller is capable of wide area trunking, the standby controller informs the active controller,
through the negotiation link, that it is going active and the active must go to standby.
3 All sites in the zone lose connectivity to the controller and subsequently enter local site trunking mode. If the
controller has malfunctioned, the switch to local site trunking has probably already occurred.
4 All active wide area calls are ended including Talkgroup, Multigroup, Interconnect, Private, and Emergency.
BTS sites revert to local site trunking mode.
5 All radios, upon receiving the local site trunking system status Outbound signaling Packet (OSP), leave their
current site and search for a site in wide area trunking. Since all sites are in local site trunking mode, the radios
return to the original site and inform the radio user of the local site trunking mode through audible tone and,
when so equipped, with a visual indication. For more information see 5.11.3.1.1 Radio Scatter, page 5-43.
6 The sites constantly send link requests to the controller. Once the newly active controller is online, it
acknowledges the link requests to bring the sites into wide area trunking.
7 As each site transitions to wide area trunking from local site trunking, they transmit a wide area System Status
Outbound signaling Packet (OSP) to inform the radios of the change.
The time duration to transition from wide area trunking to local site trunking and return to wide area
trunking varies depending on system size and configuration but should take less that two minutes.
8 If the radios ended up on a site other than their starting point during their search for a wide area trunking
site, they transmit an Inbound signaling Packet (ISP).
9 The active controller begins gathering the current location of radios and talkgroup members from the affiliation
tables sent from the sites.
Only limited wide area services are available until the controller receives all of the site affiliation tables.
The time to recover the site affiliation information varies depending on the number of active radios,
talkgroups, and the number of sites in the system, but should be less that twenty minutes.
10 For multizone systems, if the active controller is the controlling zone for an interzone call, it must also receive
talkgroup affiliation information from the other zones before those zones are included in call requests. The time
required varies depending on the number of radios and talkgroups in the system but in general should be less
than 25 minutes. Prior to this being completed, interzone services to other zones may be affected.
11 The newly standby controller resets and if it initializes in service mode, the controller receives infrastructure,
radio, and talkgroup information from the ZDS. This includes all infrastructure, radio user, and talkgroup
configuration information.
Some radios can be registered at more than one site during controller switchover. Multiple registrations
can occur if a radio happens to register to a new site while the radio is also searching the adjacent site list
for a wide-area site. Because connectivity to the controller is temporarily lost during controller switchover,
entries in some of the site registration tables do not get updated to reflect radios who have changed sites.
Normally the controller de-registers radios when they roam out of a site, however, during a controller
switchover the communications path from the controller to the site is temporarily unavailable preventing
the controller from performing deregistration.
The site transitions to wide area trunking mode when the site reestablishes a link with the controller. The site then
notifies the radios of the change through System Status OSP.
The wide area feature called Dynamic Site Assignment requires that the controller have up-to-date affiliation
tables. All sites need to upload the affiliation tables to the controller. After the controller receives all of the
uploads from the sites, it looks through the compiled affiliation table for radios that are registered on more than one
site. If the controller finds duplicate affiliations it requests, through all sites where the radio shows registrations,
that the radio reregister. This must happen before Dynamic Site Assignment can guarantee all intended parties
are included in the call.
The length of time it takes to update the affiliation tables depends on the number of sites, radios, and talkgroups
in the system, but in general it should be less than twenty minutes from the time the first site transitions back to
wide area trunking.
As with radios, console affiliations must also be sent to the controller within the zone. This happens within the fist
few minutes after the switchover occurs.
For a given talkgroup to be monitored by the dispatch subsystem, at lease one console affiliation must be received
for that talkgroup.
Do not switch back to the standby controller until the Infrastructure database has been downloaded from
the Zone Database Server (ZDS) or the system remains in local site trunking until the Infrastructure
database has been downloaded. The download time varies by system configuration, but in general should
take less than 10 minutes.
If for some reason the newly active controller is not functioning properly, you may need to switch the standby
controller back to active. This is considered a double switchover. The following is a description of what occurs
when performing a double switchover before the standby controller has received the user configuration database
from the ZDS.
There is no indication that the download has completed other than the controller state changing to enabled
idle or enabled active.
The controller begins acknowledging the link requests from the sites once the database is downloaded. A link
request contains information such as the site ID. The controller checks the site ID against the information in the
database and requests the site's capabilities. The controller instructs the site to transition to wide area trunking if the
capabilities are normal. The controller then requests the affiliation tables for radios and talkgroups. This operation
is performed for every site in the system. The controller handles multiple sites simultaneously.
Semi-duplex transmission means that only one user can transmit traffic in a call at any time. This is the characteristic
mode for private calls in a PMR/PAMR system. Full-duplex transmission means that each user can transmit and
receive traffic (talk and listen) at the same time. Telephone Interconnect calls are always full-duplex, so duplex
individual calls appear to the user to be similar to telephone calls. The full duplex individual call service allows two
parties in a TETRA system to communicate using full-duplex speech in three different ways:
The system can also be configured so the RCM or Console acknowledges the Emergency Alarm.
Radio to radio
Radio to fixed IP host (the IP host must have an assigned SSI and be registered with the Short Data Router)
Fixed IP host to radio group or broadcast (the destination devices must have assigned SSIs and be registered
with the Short Data Router)
Fixed IP host to Fixed IP host
SDS supports concurrent voice and data operation. Access to the SDTS is via the Peripheral Equipment Interface at
the radios and via an IP connection to the Short Data Router (SDR) in the Dimetra infrastructure. In addition, there
is an internal interface within Motorola radios to the SDTS, used for the Alphanumeric Text Service (ATS).
A message list which allows free text of up to 500 characters in Unicode or 1000 characters in ASCII to
be entered and stored.
An address book which allows the radio name, department and Individual Short Subscriber Identity (ISSI)
of the radio to be entered and stored.
Messages are sent by selecting one or more entries from the address book and either entering the text
message to be sent or selecting a message from the message list.
Sent messages are displayed in the sent list which indicates the time and date the message was sent, whom
the message was sent to and the status of the message.
The user can request notification that a message has been read.
Message broadcast to a stored address list, or to a stored list of sites.
When a message is received this is announced via audible and visual indication. The user is given the
option to read the message immediately, or read the message later.
The radio application shall store up to 8 messages. If a new message arrives while the radio queue is full,
the radio rejects the incoming message and the sender receives indication that delivery failed.
The system provides 10 levels of priority where level 1 is the highest and reserved for emergency group calls. The
NM assigns levels 2-10 to individuals and talkgroups. The priority assigned to a group call is the individual priority
of the calling party or the group priority, whichever is the higher. The priority level is used in the case where a
system is busy and calls are queued. When the systems get busy, calls with higher priority are allocated traffic
channels before calls with lower priority.
In addition, any emergency call signaling is also sent on all the traffic channels at the sites where the emergency
call is being set up.
BIC/BOC is often used with other features, like Object Call. This involves the creation of a Barring Profile
in the User Configuration Manager.
BIC/BOC is also used as a Dimetra IP supplementary service of the Telephone Interconnect Call service.
Each radio user can be barred by the Network Manager from making incoming outgoing telephone
interconnect calls with certain specified numbers or number ranges. The numbers and ranges are specified in
Exclusion Classes in the User Configuration Manager.
For more information see Barring of Incoming/Outgoing Calls and Telephone Interconnect manuals.
For further information on the voice logging system, turn to the MCC 7500 Dispatch Consoles Subsystem
manual.
Redundant components can be added to other parts of the infrastructure for instance to ensure traffic
of short data massages.
Furthermore, the system offers the possibility of geographical redundancy. With geographical redundancy the
functioning and its redundant counterpart are placed in two different locations. This can be done to avoid physical
damage to the system that impacts both the functioning and the redundant component.
0000
0
0
00000
00000
PDR Primary Secondary
Zone Zone Server
0000
0000
Server
0
0
00000
00000
GGSN
Fiber
0000
0
0
00000
00000
EAuC Core Gateway/ Border VPN Core Gateway/ Border VPN
Exit Router(s) Rouer Router Exit Router(s) Rouer Router
0000
0000
0
0
00000
00000
Patch Patch
KMF
Panel Panel
0000
0000
CEN CEN
0
0
00000
00000
Local Gateway Trunking is a disaster recovery feature designed to provide local resource functionality in the event
of an MSO failure or a link failure between the base station and the MSO.
In the event of an MSO or link failure the local MTS and console are able to connect to a local Dimetra IP
Micro/LiTE system and provide full voice and short data functionality within the local coverage area of the
Dimetra IP system.
A Private call may be added to a Console Patch by first setting up the Private call, and then adding it to the patch
configuration.
If enabled, dispatch console operators can make limited changes to the configuration of their dispatch console (such
as adding resources). These changes are temporary and are lost when the user logs out. Permanent changes to
configurations can only be made using Elite Admin.
The features and capacity of a mixed system with coexisting 8.1 and 7.1 clusters are limited to the features
and capacity of the 7.1 system.
Coexistence feature is dependent on hardware used in 7.1 clusters. For example, coexistence is possible for
systems using Netra 240 or G7 as a server platform, while systems using CP1500 are not supported.
Within each cluster the mix of hardware is restricted to the hardware that is ship accepted on that release.
For example, 7.1 cluster may include a Centracom console, but 8.1 cluster cannot.
The interconnected clusters may contain both DIPS and DIPC provided that DSS zones are in the same
type (all E1 or all Ethernet).
Ethernet DSS can connect to E1 DIPS only after adding Ethernet Exit Routers to the DIPS zone. An E1
DSS cannot connect to an Ethernet DIPS because the Ethernet DIPS cannot support E1 Exit Routers and
the E1 DSS cannot support Ethernet Exit Routers.
The features specific to Dimetra IP 8.1, like Object Call or BIC/BOC, are not available in such hybrid
systems.
Fault Management
Configuration Management
Accounting Management
Performance Management
Security Management
The International Organization for Standardization (ISO) refers to this as the FCAPS model. The NM subsystem
offers effective and efficient solutions that address each of the FCAPS requirements.
The NM subsystem supports the following services:
Fault Management - Applications are included for monitoring the status of the transport network and the
individual infrastructure components, displaying fault information, forwarding alert information, and
performing diagnostic procedures.
Configuration Management - Facilities are provided for entering and maintaining the operational
parameters of the infrastructure components and user devices (such as radios).
Accounting Management - NM supports the tracking of radio usage of the system by providing an interface
to third-party accounting and/or billing applications.
Performance Management - Applications are available for monitoring, reporting, controlling, and
optimizing the use of system resources.
Security Management - NM includes features for setting user privileges and controlling their access to
view and/or modify information contained in the configuration databases.
Systems continue to grow in size and technical complexity. Work demands are increasing on system administrators
who are routinely faced with handling multiple tasks. Remote access leverages system administrators' time.
At the same time, the mobile work force increasingly relies on radio communication services to fulfill their
critical missions. Even a brief service interruption or degraded quality of service could impact organizational
effectiveness, productivity, or safety. Rapid fault detection, notification, and repair require sophisticated tools that
are technologically equal to the managed network. Features and benefits are detailed in the following.
7.2 Serviceability
Serviceability for a Dimetra system, at the MSO, is the capability to provide maintenance of the equipment either
locally from a service terminal or remotely through modems or remote LAN connections. To facilitate service
to the remote sites Dimetra BTS (Base Transceiver Station) Service Software (TESS) is available as a remote
terminal (only from within the RNI) so many maintenance functions regarding the BTS sites can be done remotely
via VPN Gateway.
This clause describes the architecture by which the service organizations and other support functions can get
access to elements in a Dimetra system. The maintenance procedures and functions such as fault and performance
management are described in more detail in 7.6.2 Private Radio Network Management Suite Applications,
page 7-16.
Certified solution: connect to the terminal server via a modem connection, either dial-up or direct connected
on leased lines.
Project specific solution: connect to a border router and thus the IP network either via WAN links or via a
modem. The modem can again be directly connected via leased line or a dial-up modem.
The remote access computer is able to monitor the system and gain access to infrastructure products. When
connecting, the remote access computer can gain access to the MSO by:
Console and/or ILOM interface to the MSO devices connected to the terminal server via the terminal
servers menu system
PPP IP connectivity to the MSO devices via the terminal servers LAN connectivity
The remote serviceability access means that a technician is allowed access to elements of the infrastructure for
the following:
Configuration
Diagnostics
Event Log Reporting
Application performance is less dependent on the number of concurrent users and open applications;
Personnel typically responsible for managing a radio system or computer network are already familiar
with, or easily trained to use, the GUI of PRNM applications that conform to Windows operating system
conventions; and,
Remote operation performance over a limited bandwidth link (for example, a telephone line used for
accessing the network remotely through dialup modems) is improved.
ZoneWatch - (1) A Windows application that monitors trunking activity and radio call traffic for an
individual zone in real time. This application is part of the Private Network Management Suite. (2) A
Motorola software application that allows users to monitor activity within a zone
Affiliation Display - Affiliation Display is a Private Radio Network Management (PRNM) Suite
management application that monitors how radio users travel between different sites in a zone and how
they communicate with other members of their assigned talkgroup or even with members outside of their
talkgroup within a particular zone.
Air Traffic Information Access (ATIA) Log Viewer - Data packets that contain talkgroup registration and
site registration and deaffiliation/deregistration information for each radio user in a particular zone. The
Air Traffic Router (ATR) collects this radio traffic information from the Zone Controller and broadcasts an
information stream of these packets on the network.
Dynamic Reports - An application intended for short term monitoring. The display provides zone-level,
real-time charts that illustrate channel utilization for all call types group, private, interconnect, control
channels, and dynamically blocked calls.
Historical Reports - A management application producing reports on radio infrastructure and radio
resource usage within an identified zone.
Fault Manager using Unified Event Manager - The Dimetra IP fault management application. Unified
Event Manager identifies problems rapidly and provides functions and tools for notifying support personnel,
tracking, diagnosing, and correcting faults. It also maintains a data warehouse, storing up to 30 days
of event history.
Radio Control Manager (RCM) - A management application used to issue commands to radios and
monitor events from radios. The Radio Control Manager (RCM) is part of the Motorola PRNM Suite.
Radio Control Manager Reports - The application provides reports of two types of functions of the RCM:
radio commands initiated and radio events displayed.
These applications input to or extract information from one or more of the NM servers where system configuration
parameters are stored, transactional statistics are accumulated, real-time data streams are sourced, and supporting
processes are performed. In addition to these user applications, the NM servers also run several autonomous
processes in the background to support the ongoing operation of the system. Applications and processes are
described later.
Providing the Affiliation Server, the backend of the Affiliation Display application
Processing real-time call transactions, being the information source for ZoneWatch and RCM
Serving as source of the Air Traffic Information Access (ATIA) data stream to third-party applications
Logging to disk ATIA data for viewing or export to a text file
Routing RCM command and status/messages to/from the Zone Controller
Routing call logging information from the Zone Controller to the Zone Statistics Server (ZSS) and System
Statistics Server (SSS)
Hosting the statistics proxy agent for the Zone Controller as a source for dynamic and historical reports
statistics
Identities, including radio serial number, user identifier, and group memberships
Radio user capabilities, such as priority level and the ability to place and receive telephone calls
Group and Multigroup capabilities, such as priority levels, and group memberships in multigroups
Radio user and group access to each site in the system. A network manager can limit a radio user or group
to one site or a group of sites, prohibiting them from using other sites in the system
Operator information, such as privileges, passwords, network access, and identification
Separate, performance applications display real-time communications activity (such as, ZoneWatch) or collect
traffic statistics over predetermined intervals for report generation (such as, dynamic and historical reports).
Historical statistics are aggregated into detailed and summarized reports on both an individual site, zone, and
system wide basis. Statistics are available on an hourly basis for 10 days, daily for 62 days, and monthly for one
year at a zone, site, channel, and user. Other statistics that are useful in troubleshooting, sizing, and monitoring
the system are also collected. The system logs these statistics for a period of 62 days. NM also has archival and
export features for saving reports or offline data analysis.
7.4.4.3 ZoneWatch
ZoneWatch is a performance management tool having customizable displays and grids to monitor real-time
communications activity in a single zone. The information displayed can help system managers be proactive in
making better resource planning decisions, such as when additional channels need to be added to busier sites.
ZoneWatch Grid Screen: Air traffic within a single zone is displayed on a site/channel grid. Real-time call
activity for each channel is displayed in its respective cell.
ZoneWatch Control Display: This display presents call activity messages that can be used to isolate errors, trace
the progress of a call and troubleshoot, or analyze current system activity. It also provides information about
activity occurring on the control channels, such as rejects, emergency alarms, and unit affiliations.
The Affiliation Display provides a dynamic view of the sites to which all operating units are currently registered,
displaying zone, site, and talkgroup details. This feature makes it easy to track and troubleshoot radios in the
system. Affiliation Display is not a vehicle or unit locator in an absolute sense; registration only suggests the area in
which the unit may currently be operating based on the last registration of the unit and the radio coverage of the site.
The focus of the Affiliation Display can be on an individual site, a specific talkgroup, or an individual radio.
Graphing capabilities are also included.
7.4.5.5 Authentication
Authentication prevents hostile or other unauthorized radios from registering with the system. Authentication sends
a challenge to a registering radio. The radio must supply the appropriate response to access the system. If mutual
authentication is being used, then the radio also sends a challenge to the infrastructure, and the infrastructure must
supply a proper response. This ensures that both the infrastructure and the radio are both genuine.
Authentication relies on a separate secret key for each radio provisioned in the cluster. This key is provisioned in
the Provisioning Centre, Authentication Centre, and in the radio. For the Provisioning Centre and Authentication
Centre, each key is stored in a secure form in a database encrypted with a tamper-proof crypto card. The key are
also stored in a secure form in the radio. The Provisioning Centre is isolated from the network.
Air interface encryption relies on Static Cipher Keys (TM-SCK used for encryption in Trunked Mode operation
and DM-SCK used for encryption in Direct Mode operation) which are provisioned in the Provisioning Centre,
Authentication Centre, and the individual radios. For the Provisioning Centre and Authentication Centre, these keys
are stored in a secure form in a database encrypted with a tamper-proof crypto card. The keys are also stored a
secure form in the radios. The Provisioning Centre is isolated from the network.
Neither Static Keys nor Dynamic Keys (DCK, GCK, CCK) are distributed over the air. However, Common
Cipher Keys (CCKs), which are used for group calls, are sealed with a DCK and sent over the air to radios for
group calls as well as MGCK - the combination of GCK and CCK. The typical duration for the use of a CCK and
DCK in the system is 24 hour and for GCK - 3 months.
Multizone fault management can also be arranged through the forwarding of events to a central customer-supplied
fault management system. This central fault management system can receive the forwarded traps from all
zone-level Unified Event Manager servers in the system. The figure below illustrates the event forwarding from
each zone Unified Event Manager server to a customer-supplied fault management platform.
Cluster
Zone
Site
Unit
The table lists the Motorola PRNM Suite applications. These management applications are available through
Application Launcher.
FCAP-
Applications Purpose
S
Application Launcher N/A A launch point for PRNM applications.
Cluster-Level Applications:
Software Download C A tool that provides software upgrades to specific devices.
System Profile P A tool that allows you to track usage at the system level. Shows
the number of applications open, who is using the application,
the number of available licenses, and the processes of the open
applications.
User Configuration Manager CS The primary tool to configure and manage radio network users.
Zone-Level Applications:
Affiliation Display P A tool to monitor radio, talkgroup, and site use. Affiliation
Display spans zone, site, and radio unit levels in the figure above.
ATIA Log Viewer P A tool that allows you to view radio events occurring in the zone
in a raw data format from the Air Traffic Router (ATR).
Dynamic Reports AP A report tool that provides predefined reports using data taken
dynamically from the database.
FCAP-
Applications Purpose
S
Unified Event Manager includes: FPS The primary fault management tool that you can use to monitor
the status of the system. Unified Event Manager spans system
Unified Event Manager and zone-level activity in the figure above.
Administration
Unified Event Manager
Web Browser
Unified Event Manager
Historical Reports AP A reporting tool that uses predefined reports to show data from
archived information. Historical Reports spans zone, site, and
unit levels in the figure above.
Radio Control Manager Reports AP A reporting tool that provides reports on radio activity.
Radio Control Manager CS The primary tool used to control and monitor radio activity. Has
configuration capability in the Dynamic regrouping feature.
Radio Control Manager spans zone, site, and unit levels in the
figure above.
Zone Configuration Manager C The primary tool used to configure infrastructure equipment and
other zone-level parameters.
Zone Profile P A tool to track usage at a zone level. Shows the number of
applications open, who is using the application, the number of
available licenses, and the processes of the open applications.
ZoneWatch FP A tool that monitors call processing resource assignments,
including channels, sites, and any hardware assigned to a call.
ZoneWatch spans zone, site, and unit levels in the figure above.
FCAP-
Application Purpose
S
Dimetra BTS (Base CF A tool used to configure and service the Site Controllers and BTS base
Transceiver Station) radios.
Customer Programming C A tool that programs radios. You can also use it to learn the operating
Software (CPS) parameters, personalities, and modes of radios. This software is
documented in the CPS application for your radio. The CPS Online
Help is available from the Help menu.
Start menu
Windows Explorer window
You can launch applications from the Start menu or an Explorer window that is launched from a desktop
icon. The system manager assigns permissions to each user in the cluster. These permissions determine which
applications, security groups, and objects you can access. These permissions also determine your view of the
system by displaying only the cluster-level applications, zones, and zone-level applications for which you have
access permissions in the Windows Explorer window.
Application Launcher allows you access to the applications that manage and monitor the clusters and zones. It also
allows you to do the following:
View applications available for the cluster and for each zone.
Change and store your password.
Change server access.
Exit Application Launcher in a secure manner so that the next user is prompted to log on.
Monitor affiliation for one or more radios using the Radio Viewer at one or more sites. You can locate
specified radios by ID.
Monitor affiliations by site using the Site Viewer and view a list of talkgroups or radios at a site.
Monitor affiliations by talkgroup using the Talkgroup Viewer. You can view information for sites at
talkgroup or radios at talkgroup.
Monitor selected radios, talkgroups, and sites dynamically using the main window. Monitors affiliation and
deaffiliation information for the location of radios and their current talkgroup at a site within a zone.
Note the radio communication about a site, so you can see how traffic moves within sites in a zone. By
tracking selected talkgroups and radio users through a zone, you can see which sites get the most use.
From the Talkgroup Viewer, create a dynamic graphical display of radio usage at a site. The usage
information is captured in a graph format for talkgroups and sites.
You must first enable ATIA data logging through the ATR server's Administration menu. Otherwise, no
ATIA log data is collected for viewing.
The ATIA Log Viewer is a technician tool that allows you to examine air traffic historical data in a specified zone
for one or more particular time intervals. You can also do the following:
View the radio events occurring in a zone. The information is the same as what you view from ZoneWatch,
but is presented in a raw data format from the ATR server. Shows active sites, channel numbers, and
radio affiliations.
View a log of what occurs on an hourly interval in the zone.
The ATIA Log Viewer allows you to examine historical air traffic data in a specified zone for a particular time
interval or intervals. This feature is normally used to examine data logs when debugging the system. The ATIA Log
Viewer records the last 25 hours of ATIA data packets on the ATR server. The data is displayed on an hourly basis,
and you can select which interval packets you want to view.
The data is displayed in an easy-to-read format and can be printed or saved for future evaluation. Since the
information displayed in the ATIA Log Viewer is a text document, you can format the information, if required
using a third-party application.
The Custom Historical Report features apply only to Historical Reports and not to Dynamic Reports.
The Report Expert wizard from Crystal Report allows you to select from parameters collected by the
ATIA stream or other reports.
Reports may be customized to suit your individual needs. Customization includes:
Group and sorting
Charts (bar, line, 3-D)
Top and bottom X filtering
Calculated values
Cross tab, form, form letter, drill-down reports
Special formulas can be included in Custom Historical Reports to create certain effects.
Use Dynamic Reports to monitor and report usage trends and patterns of activity. You can do the following:
Unified Event Manager allows you to monitor the status of components at zone level, such as servers, Zone
Controllers or sites in the zone.
Submap views show the status of devices by color and the graphical representations of alarm information.
Alarm Categories show different categories of alarms, for the radio system, routers, or other devices.
Alarms Browsers show a record of what devices are sending alarms or events.
Unified Event Manager communicates with managed RF system devices using Simple Network Management
Protocol (SNMP), the industry standard communication protocol.
Unified Event Manager integrates the fault management of Motorola devices and that of approved third-party
devices.
Submit radio commands over the air, select radios to receive the commands, and track the progress of the
commands. After you issue a radio command, you can view the command and its status in the Command
Monitor.
All monitoring displays are updated in near real-time as the information becomes available in the system.
User Application DistributionThe User Application Distribution tab displays a list of cluster-level
applications that are being run on network management clients in the system. The User Application
Distribution tab also shows the login name of the user and the time the application was started.
License Usage The Licence Usage tab shows the purchased licenses for each of the cluster-level applications
and shows the number of licenses that are currently in use.
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.
7.6.2.15 ZoneWatch
ZoneWatch is a PRNM Suite application that lets you monitor radio call traffic for an individual zone in real time.
This application uses different watch windows that allow you to display only the information you need to see.
Examples of trunking activity and radio call traffic displayed in the watch windows include the following:
Radio IDs
Talkgroup IDs
Aliases
Specific call information
Channel assignments
This application monitors all radio call activity by pulling trunking information from the Air Traffic Router (ATR)
server, which receives updates from the Air Traffic Information Access (ATIA) stream distributed by the Zone
Controller.
ZoneWatch uses different types of watch windows to display zone, site, talkgroup, and radio information for a
specific zone. The different window profiles, which contain window definitions and filters, define how to display
the information and how to apply limits to the type of data that you can view. The following are examples of the
types of information that you may choose to view:
Activity in a Zone You can open ZoneWatch to monitor radio call activity within a zone. You can see
constantly updated information on who is using the system, where the radio users are located, what
infrastructure resources are being used, and any significant changes in system usage.
Message Type Information can be selectively displayed by one or any combination of message types.
Raw Data A Raw Data filter allows the selection or exclusion of information. The data that is selected for
inclusion is displayed as raw data (no formatting).
Site Information A site filter object allows you to specify the site that the ZoneWatch user wants to
monitor. The site selection must consist of a site within the same zone as the ZoneWatch. The site filter
essentially limits the view to only a specific site in a zone. You can, however, have other windows open
to show information from other sites in the zone.
Table A-1
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
Glossary The glossary provides a list of abbreviations, acronyms
and terms used in the Dimetra IP system documentation.
Documentation Overview The document provides a list of all documents delivered
with your Dimetra IP system. Its primary purpose is to
help you to find the information you are looking for.
System Overview This manual provides basic radio system concepts, call
processing basics, and an introduction to the various
components and processes associated with the Dimetra
IP system. The manual provides the background needed
to comprehend the theory of operation and it provides
equipment/subsystem functional descriptions. It also
describes the role of the numerous network management
software applications used for managing the system.
Standards and Guidelines This manual provides standards and guidelines to follow
for Communication Sites when setting up a Motorola communications site. Also
known as R56 manual.
Zone Controller This manual describes the Zone Controller which is
responsible for processing calls, managing audio paths,
controlling zone infrastructure, and providing services to
subscribers and console operators.
System LAN Switches This manual describes LAN switches used in the
Dimetra IP system. Included are detailed procedures for
installation, configuration and operation.
S6000 Router This manual describes the S6000 router used in the
Dimetra IP system. The router provides the following
network transport functions for the whole system:
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
Cooperative WAN Routing This manual describes the Cooperative WAN Routing
(CWR) solution that allows core and exit routers to
interface directly with site and interzone links through
a simple, reliable, and passive relay panel. The core
and exit routers are configured in pairs to provide path
redundancy for audio and control packets. With CWR,
the routers work to control an external relay panel to
switch a group of 12 non-redundant E1 links between the
two routers in a pair.
Ethernet Site Links This manual contains information on the Ethernet Site
Links (ESL) feature, which provides a means to establish
Ethernet connections of the following type:
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
Network Time Server This manual describes the Network Time Server (NTS),
which provides a UTC time and date reference to all IP
connected system elements (NTP clients) that support
the Network Time Protocol (NTP). The manual contains
all information necessary to install, configure and use the
server in the system.
Backup and Restore This volume contains the system backup and restoration
Including FRU/FRE procedures and their impact on the services as well as pre
and post-restoration checks. The volume also describes
how to perform FRU/FRE procedures.
Safety Guidelines for This manual describes the general safety guidelines to be
Installation of Hardware followed in connection with installation of hardware and
and Software software. It is a part of Backup and Restore Including
FRU/FRE.
Server Software This manual describes how to perform restoration of all
Restoration application servers. Additionally it contains instructions
for scheduling or creating a backup on-demand. It is a
part of Backup and Restore Including FRU/FRE.
Server Hardware This manual describes how to perform restoration of all
Restoration system servers hosting application servers. The manual
also describes how to perform FRU/FRE procedures
for these servers. It is a part of Backup and Restore
Including FRU/FRE.
Stand-alone Components This manual describes how to backup and restore the
Restoration following components of a new Dimetra IP system:
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
MTS 1 Restoration This manual describes how to backup and restore the
Motorola Transceiver System (MTS) 1. The manual also
describes how to perform FRU/FRE procedures. It is a
part of Backup and Restore Including FRU/FRE.
MTS LiTE, MTS 2 and This manual describes how to backup and restore the
MTS 4 Restoration Motorola Transceiver System (MTS) LiTE, 2 and 4.
The manual also describes how to perform FRU/FRE
procedures. It is a part of Backup and Restore Including
FRU/FRE.
EBTS Restoration This manual describes how to backup and restore the
Enhanced Base Transceiver System (EBTS). The manual
also describes how to perform FRU/FRE procedures. It
is a part of Backup and Restore Including FRU/FRE.
Fault Management This manual provides an overview of Fault Management
features and contains troubleshooting procedures.
Unified Event Manager This manual provides an introduction to the Unified Event
Manager (UEM). Included sections are a comprehensive
introduction, tools used for troubleshooting, and
system-level troubleshooting. UEM is an application
that provides reliable fault management services for the
Dimetra IP system.
ZoneWatch This manual describes ZoneWatch which is a Private
Radio Network Management (PRNM) Suite application
that lets you monitor radio call traffic for an individual
zone in real time. ZoneWatch uses different watch
windows that allow you to display only the information
you need to see.
System and Zone Profile This manual describes the System Profile application and
the Zone Profile application which are both a Private
Radio Network Management (PRNM) Suite application.
The System Profile application displays how system-level
applications are being used by the network management
clients. For instance, you can view information for
applications in the system including the total number
of applications purchased, number of licenses in use,
and who is currently using the application. The Zone
Profile application displays detailed information about
applications that are operating in the zone. You can use
Zone Profile to view the zone-level application usage and
view the zone-level application license usage.
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
System Alarms and Events This manual lists all the possible alarms for the system.
It also covers transient alarm messages, which are known
as technician messages. This manual is intended for
technicians, network management personnel, or any
other engineering personnel with responsibility for
troubleshooting or monitoring the operational status of
the system.
User Configuration This manual describes the User Configuration Manager
Manager (UCM) which is a Windows based, Private Radio
Network Management (PRNM) Suite application. The
UCM is used in the configuration of the system. It is
also the tool used to modify configuration parameters.
To configure a system, both the UCM and the Zone
Configuration Manager (ZCM) are needed.
Zone Configuration This manual describes the Zone Configuration Manager
Manager (ZCM) which is a Private Radio Network Management
(PRMN) Suite application. The ZCM is used to configure
and maintain operational parameters for equipment in a
system. To configure a system, both the ZCM and the
User Configuration Manager (UCM) are needed.
Configuring Features This manual describes radio features and their
configuration. The manual contains a configuration
checklist as well as configuration procedures for the key
features of the system.
Software Download This manual describes the Software Download (SWDL)
Manager which is a Private Radio Network Management
(PRNM) Suite application that can transfer and install
new software in the Dimetra IP Base Transceiver
Systems (BTS).
Radio Management This manual describes the radio features available to
radios in the Dimetra IP system.
Affiliation Display This manual describes Affiliation Display which is a
Private Radio Network Management (PRNM) suite
application. Affiliation Display enables you to view
the association of a radio with a talkgroup and site,
information about conventional channels, console
sites, and consoles and to monitor how radio users
travel between different sites in a zone and how they
communicate with other members of their assigned
talkgroup or even with members outside of their
talkgroup.
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
ATIA Log Viewer This manual describes the Air Traffic Information Access
(ATIA) Log Viewer which is a Private Radio Network
Management (PRNM) Suite application that displays
log files generated by the Air Traffic Router (ATR).
These log files contain records of all recent zone activity,
such as site registrations and calls processed. ATIA Log
Viewer allows you to view the raw ATIA data straight
from the ATIA log.
Radio Control Manager This manual describes the Radio Control Manager
(RCM) which is a Private Radio Network Management
(PRNM) Suite application used primarily by dispatchers
to monitor and manage radio events, issue and monitor
commands, and make informational queries of the system
database.
Radio Control Manager This manual describes the Radio Control Manager
Reports (RCM) Reports which is a Private Radio Network
Management (PRNM) Suite application that is used to
create, view, print, schedule and export standard reports
from RCM. These reports use a common format so the
data can be used in spreadsheets. The report information
reflects the actual RCM server database information
except the Emergency Alarms.
Fleetmapping This manual describes how to properly plan for, set up,
and manage your system. The Motorola engineering
team works with your organization to plan, and set
up your system. Accurate operational requirements
are needed to ensure a successful system plan. By
properly configuring the Dimetra IP system to meet your
operational needs, your organization will have the most
efficient and effective communications system available.
Performance Management This manual provides an overview of Performance
Management features. By monitoring the performance of
the system, you can identify potential problems before
they occur as well as adjust system resources to provide
optimum performance.
Dynamic Reports This manual describes Dynamic Reports which is a
Private Radio Network Management (PRNM) Suite
application that provides predefined report templates you
can use to display statistics for a zone, site or a console
site (but not for a system) in near real time.
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
Historical Reports This manual describes Historical Reports which is a
Private Radio Network Management (PRNM) Suite
application that allows you to generate reports for
system-wide activity and for individual zones. These
reports display data that is stored on the server. The
Historical Reports application generates reports of
statistical data that is gathered at specific, predefined
time intervals. You can then create reports from this data
to monitor and analyze information about zones, sites,
channels, talkgroups, and users.
InfoVista This manual describes InfoVista which is a
customizable performance management application.
InfoVista interfaces with, and gathers data from,
multiple network devices supporting Simple Network
Management Protocol (SNMP) including master site
routers, Ethernet LAN switches, and WAN switches.
The InfoVista client application is used to access server
software and perform administrative tasks such as
starting and stopping existing reports, adding an instance,
or creating a new report.
Security Management This manual provides a security overview for the Dimetra
IP system. Attacks on communications networks
could interrupt mission critical operations, compromise
classified or restricted information, and contribute
indirectly to loss of lives. The manual presents an
overview of the security application users, describes the
security groups and applications, and describes how
to configure and optimize the applications for secure
operation.
Agency Priority Matrix This manual describes the Agency Priority Matrix which
(APM) is a feature used for controlling which talkgroups or radio
users can be assigned to each RF channel resource in the
system. The manual describes how to configure, operate,
maintain, and troubleshoot the Agency Priority Matrix.
Radio User This document describes the Radio User
Assignment/Radio User Assignment/Radio User Identity (RUA/RUI)
Identity (RUA/RUI) feature. The purpose of this manual is to provide a user
with a background knowledge on the feature as well as
enable to install, configure and maintain the Alias Server.
It also describes how to operate RUA/RUI from the Alias
Provisioning Client.
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
Data Subsystem This manual describes the Data Subsystem and its
components. It provides information on how to install,
configure, operate and maintain the equipment and
software including the Packet Data Gateway (PDG),
Short Data Router (SDR), and Gateway GPRS Support
Node (GGSN) Router. The Data Subsystem performs
registration services for packet data users, maintains
user permissions and mobility information, and provides
routing of traffic to the radio network and the Gateway
GPRS Support Node (GGSN) Router.
MultiCADI This manual describes the Computer Aided Dispatch
Interface (CADI) which is an Application Programming
Interface (API) that provides the capability for systems
external to the Dimetra IP SwMI to obtain information
about, and exert some control over, radios. The CADI
API enables third parties to write software applications
called CADI clients that can receive events from,
and submit commands to, the Dimetra IP SwMI.
Multi-Computer Aided Dispatch Interface (MultiCADI)
is a server application and an API, which enables third
parties to develop application programs that can utilize
the facilities provided by the CADI in the Dimetra IP
system. The MultiCADI API builds upon the CADI API,
but provides additional capabilities.
Telephone Interconnect This manual provides the information necessary to
install, configure, operate, and maintain the components
in a Telephone Interconnect subsystem. The Telephone
Interconnect subsystem provides an interface between
the Dimetra IP radio network and an external telephone
network, allowing telephone interconnect calls to be
made between Dimetra IP radios and external telephones.
Active Directory/Domain This manual describes Active Directory (AD) which
Name Services is the service that provides access to enterprise-wide
data and improved integration with the rest of the radio
system. The manual contains procedures for installation
and configuration of software necessary to make Active
Directory operational. It also contains procedures for
adding users and groups, and for backup and restore of
Active Directory.
TESS Software User Guide This manual is an introduction and guide to the use of
the Dimetra BTS (Base Transceiver System) Service
Software. Through the Dimetra BTS Service Software
trained service personnel and systems engineers can
configure and program a BTS.
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
Transport Network Device This manual describes the Transport Network Device
Manager (TNDM) Manager (TNDM), which allows you to deploy
previously prepared configurations to network devices.
It also allows for tasks such as: rebooting devices,
uploading firmware, checking firmware version,
configuration backup and restore, checking device
connectivity.
Alphanumeric Text Service This manual describes the Alphanumeric Text Service
(ATS) (ATS) application, which enables text messages to be
sent between Mobile Stations (MS), Dispatch Consoles
and computers in the fixed network.
Backup/Restore Collector This manual describes the Backup/Restore Collector
Application User Guide application which provides a simple way of fetching
backup files from a group of the Dimetra IP network
elements via FTP. The network elements can be
configured to run scheduled backups and store these
backups on local disk typically during the night when
there is a smaller load of the system. The role of the
Backup/Restore application is to collect these files
and provide a centralized point of storage for them.
The backup files are accessible by FTP for collection
either manually or from a server running an automated
procedure. The files can be restored from their centralized
storage location back to the network elements.
UCS Synchronization Tool This manual describes the User Configuration Server
(UCS) Synchronization Tool, which provides automated
intercluster configuration of some of the UCS objects that
require to be registered in all clusters in a multicluster
system.
Local Gateway Trunking This manual describes the local gateway trunking
functionality, its operational aspects, and its
configuration.
Dimetra Enhanced This manual describes the Dimetra Enhanced Software
Software Update User Update feature, which provides backup and restore
Guide functionality, and upgrade functionality.
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
Authentication and This manual gives an overview of the authentication and
Encryption Overview air interface encryption features in the Dimetra IP system
including:
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
Clear Provisioning Centre This manual describes how to use the Clear Provisioning
(CPrC) User Manual Centre (CPrC) application. The main functions of the
Provisioning Centre are:
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
Network Security This manual describes all necessary actions to install,
configure and maintain the network security feature
within the Dimetra IP system. The intention of the
manual is to enable the reader to deploy the best possible
level of security, which will protect the system against
viruses, unauthorized authentication or attacks of
hackers. The network security feature provides virus
protection, authentication, and firewall protection.
End-to-End Encryption This manual describes how to configure the KVL 3000
KVL3000 Plus User Guide Plus for initial use, and entering and storing encryption
keys in to target devices, such as radios, CryptRs and
Mobile CryptRs.
Air Interface Encryption This manual describes how to configure the KVL 3000
KVL3000 Plus User Guide Plus for initial use, and entering and storing encryption
keys in to target devices, such as radios and others in
connection with Air Interface Encryption.
Dimetra KVL 4000 Air This manual provides instructions for using the KVL
Interface Encryption and 4000 Key Variable Loader to perform Air Interface
Authentication User Guide Encryption and Authentication operations in Motorola
Dimetra systems.
Dimetra KVL 4000 This manual provides instructions for using the KVL
Authentication User Guide 4000 Key Variable Loader to perform Authentication
operations in Motorola Dimetra systems.
Dimetra KVL 4000 This manual provides instructions for upgrading/rein-
FLASHPort Upgrade stalling the KVL application, upgrading the Security
User Guide Adapter software, and applying security settings on the
KVL.
Dimetra KVL 4000 Provides basic information on KVL 4000 for Dimetra
AIEA/Auth Quick Start Air Interface Encryption and Authentication.
Guide
CryptR Instruction Manual This manual covers hardware installation, main end-user
operations and a proper maintenance of a range of
devices based on the CryptR hardware platform.
MCC 7500-series Console This manual describes the hardware and software
Sites components associated with the MCC 7500-series
console sites. It provides overviews of subsystem
functions such as communications with the Zone
Controller, different types of call setups, and descriptions
of status and events.
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
MCC 7500C Dispatch This manual describes the hardware and software
Console components associated with the MCC 7500C Dispatch
Console. It provides operation and troubleshooting
procedures for the Elite Admin and Elite Dispatch
software, and it provides an overview of MCC 7500C
accessories.
MCC 7500 Archiving This manual provides an introduction to the hardware
Interface Server and software components associated with the MCC
7500 Archiving Interface Server. Included are detailed
procedures for installation, configuration and operation
of the server.
MCC 7500 Dispatch This manual describes the MCC 7500 Dispatch
Communications Server Communications Server. Included are detailed
procedures for installation, configuration and operation
of the server.
MCC 7500 Remote This manual provides a high level technical overview
Dispatch Console of the Remote Dispatch Console product and gives
detailed procedures for its installation, configuration and
maintenance.
MCC 7500 Discreet This manual describes Discreet Listening, which is
Listening a feature that enables real-time listening into one to
one calls involving a specific radio user. Listening is
possible for calls inside the Dimetra IP system or through
telephone interconnect to an ordinary telephone. Using
the Discreet Listening feature, a user is able to listen
to calls involving the radio user without either of the
calling parties knowing about it. The manual describes
both the hardware and software used for the Discreet
Listening feature, and contains procedures how to install,
configure, and operate the feature.
MCC 7500 Analog This manual provides an introduction to the hardware
Conventional Operation and software components associated with the analog
conventional feature of the MCC 7500 Dispatch Console.
MCC 7500-series This manual provides an introduction to the bandwidth
Bandwidth Management management, which is necessary in an MCC 7500-series
console subsystem to ensure efficient transport for the
services in your system (voice calls, data service and so
on).
MCC 7500 Console This manual provides a technical overview and
Interoperability troubleshooting information for the interoperability
feature. Console interoperability is the term for a radio
system that supports call traffic involving both the
CENTRACOM Gold Series and Motorola MCC 7500
dispatch consoles.
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
MCC 7500C/MCC 7500S This manual describes the Elite Admin software.
Elite Admin Software User The software creates a virtual desktop on the screen
Guide where resources that are part of the dispatch system
are displayed graphically. Resources are grouped
into folders, and one or more folders are stored as a
configuration. The system administrator uses the Elite
Admin software to set up configurations for the Elite
Dispatch desktops that organize resources to meet
specific user needs.
MCC 7500C/MCC 7500S This manual describes the Elite Dispatch application
Elite Dispatch Software which enables console dispatchers to communicate with
User Guide radio resources.
MCC 7500 Emergency This manual describes how to install, configure, operate,
Beacon User Guide and test an emergency beacon installed on a console.
MCC 7500 This manual describes how to generate the translated
Internationalization text (appropriate to the target country or region) using
Process User Guide the Internationalization Package. The translated text is
generated for the following MCC 7500 products:
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
MTS LiTE, MTS 2, and This manual describes all necessary actions to install,
MTS 4: Installation, configure and maintain the Motorola Transceiver Station
Configuration, and Basic LiTE, 2 and 4 (MTS LiTE, MTS 2 and MTS 4) within
Service Manual the Dimetra IP System.
MTS Man Machine This manual describes the Man-Machine Interface
Interface (MMI) commands used to test and configure MTS sites.
Commands
EBTS: Installation, This manual describes all necessary actions to install,
Configuration, and Basic configure and maintain the Enhanced Base Transceiver
Service Systems (EBTS) within the Dimetra IP System.
MBTS: Installation, This manual describes all necessary actions to install,
Configuration, and Basic configure and maintain the Mini Base Transceiver
Service Systems (MBTS) within the Dimetra IP System.
Customer Specific Manuals
Cluster Hot Standby (CHS) This manual describes installation, configuration, and
Tools usage of the Cluster Hot Standby (CHS) Tools. CHS
Tools are used to synchronize active and fallback clusters
configurations and detect any discrepancies between
them.
Cluster Hot Standby (CHS) Online help for the CHS application.
Tools Online Help
Dimetra IP Compact/Scalable Dimetra IP Specific Manuals
System Reference Guide This manual offers an introduction to the Dimetra IP
Compact/Scalable Dimetra IP system. The information
covers the major components of the system and the
interconnection of components in the Mobile Switching
Office (MSO), as well as troubleshooting information.
Managing Radio Users, This manual describes the most common day to day
Radios, Talkgroup Quick tasks related to the management of radio users, radios,
Reference Guide and talkgroups.
Managing the This manual describes the three most common
Infrastructure Quick applications to use when monitoring and doing basic
Reference Guide troubleshooting of your system: Unified Event Manager
(UEM), ZoneWatch and Radio Control Manager (RCM).
The guide gives a quick overview of the most common
day to day tasks and activities.
Network Configuration This manual describes the Network Configuration Tool
Tool (NCT) Express (NCT) Express, which allows you to deploy previously
prepared configurations to network devices. It also
allows for tasks such as: rebooting devices, uploading
firmware, checking firmware version, configuration
backup and restore, checking device connectivity.
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
DIPC Upgrade Sun This manual contains information and procedures
Fire X4170/HP ProLiant necessary to upgrade a DIPC system from 7.0 to 8.1
DL360 G7 release on Sun Fire X4170 and HP ProLiant DL360 G7
server platforms.
DIPC Upgrade Sun This manual contains information and procedures
Netra 240 necessary to upgrade a DIPC system from 7.0 to 8.1
release on Sun Netra 240 server platform.
Online Help
Application Launcher This online help describes how to operate the Application
Online Help Launcher software.
Unified Event Manager This online help describes how to operate the Unified
(UEM) Online Help Event Manager application. It also covers detailed
information on all system alarms and events.
ZoneWatch Online Help This online help describes how to operate the ZoneWatch
application.
System and Zone Profile This online help describes how to operate the System and
Online Help Zone Profile applications.
User Configuration This online help describes how to operate the User
Manager (UCM) Online Configuration Manager application.
Help
Zone Configuration This online help describes how to operate the Zone
Manager (ZCM) Online Configuration Manager application.
Help
Software Download Online This online help describes how to operate the Software
Help Download application.
Affiliation Display Online This online help describes how to operate the Affiliation
Help Display application.
ATIA Log Viewer Online This online help describes how to operate the ATIA Log
Help Viewer application.
Radio Control Manager This online help describes how to operate the Radio
(RCM) Online Help Control Manager application.
Radio Control Manager This online help describes how to operate the Radio
(RCM) Reports Online Control Manager Reports application.
Help
Dynamic Reports Online This online help describes how to operate the Dynamic
Help Reports application.
Historical Reports Online This online help describes how to operate the Historical
Help Reports application.
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
Authentication Centre This online help describes how to operate the
Online Help Authentication Centre application.
Key Management Facility This online help describes how to operate the Key
(KMF) Online Help Management Facility applications.
BTS Service Software This online help describes how to operate the BTS
(TESS) Online Help Service Software.
MCC 7500 Elite Dispatch This online help describes how to operate the MCC 7500
Software Online Help Elite Dispatch software.
MCC 7500 Elite Admin This online help describes how to operate MCC 7500
Software Online Help Elite Admin software.
MCC 7500 Emergency This online help describes how to operate MCC 7500
Beacon Online Help Emergency Beacon software.
MCC 7500 Discreet This online help describes how to operate the MCC 7500
Listening Online Help Discreet Listening software.
Backup and Restore Including FRU/FRE for Upgrading Customers
Common Hardware and The purpose of this manual is to provide users with
Software Restoration the information necessary to successfully restore the
common hardware platforms (for clients and servers) and
their respective operating systems used in a Dimetra IP
system.
Call Processing, NM This manual provides users with the procedures and
and Data Subsystems FRU/FRE information needed to restore and back up
Restoration - Generation 2 the Zone Controller (ZC), Network Management (NM)
System servers and Data servers in a Generation 2 Dimetra IP
system.
Call Processing, NM This manual provides users with the procedures and
and Data Subsystems FRU/FRE information needed to restore and back up
Restoration - Generation 3 the Zone Controller (ZC), Network Management (NM)
System servers and Data servers in a Generation 3 Dimetra IP
system.
Standalone Subsystems This manual provides users with the procedures and
and Components FRU/FRE information needed to restore and back up
Restoration - Generation 2 standalone servers and components (MTIG, MultiCADI,
System Alias Server, Domain Controller, AuC/PrC and CryptR2)
in a Generation 2 Dimetra IP system.
Standalone Subsystems This manual provides users with the procedures and
and Components FRU/FRE information needed to restore and back up
Restoration - Generation 3 standalone servers and components (MTIG, MultiCADI,
System Alias Server, Domain Controller, AuC/PrC and CryptR2)
in a Generation 3 Dimetra IP system.
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
Backup/Restore Collector This manual describes the Backup/Restore Collector
Application User Guide - application, which provides a simple way of fetching
Generation 2 System backup files from a group of the Dimetra IP network
elements via FTP. The network elements can be
configured to run scheduled backups and store these
backups on local disk typically during the night
when there is a smaller load of the system. The role
of the Backup/Restore application is to collect these
files and provide a centralized point of storage for
them. The backup files are accessible by FTP for
collection either manually or from a server running an
automated procedure. The files can be restored from
their centralized storage location back to the network
elements. This version of the manual is applicable to
Generation 2 systems.
Backup/Restore Collector This manual describes the Backup/Restore Collector
Application User Guide - application, which provides a simple way of fetching
Generation 3 System backup files from a group of the Dimetra IP network
elements via FTP. The network elements can be
configured to run scheduled backups and store these
backups on local disk typically during the night
when there is a smaller load of the system. The role
of the Backup/Restore application is to collect these
files and provide a centralized point of storage for
them. The backup files are accessible by FTP for
collection either manually or from a server running an
automated procedure. The files can be restored from
their centralized storage location back to the network
elements. This version of the manual is applicable to
Generation 3 systems.
(cont'd.)
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
Cooperative WAN Routing This manual describes the Cooperative WAN Routing
(CWR) solution that allows core and exit routers to
interface directly with site and interzone links through
a simple, reliable, and passive relay panel. The core
and exit routers are configured in pairs to provide path
redundancy for audio and control packets. With CWR,
the routers work to control an external relay panel to
switch a group of 12 non-redundant E1 links between the
two routers in a pair.
Ethernet Site Links This manual contains information on the Ethernet Site
Links (ESL) feature, which provides a means to establish
Ethernet connections of the following type:
(cont'd.)
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
Network Time Server This manual describes the Network Time Server (NTS),
which provides a UTC time and date reference to all IP
connected system elements (NTP clients) that support
the Network Time Protocol (NTP). The manual contains
all information necessary to install, configure and use the
server in the system.
Backup and Restore This volume contains the system backup and restoration
Including FRU/FRE procedures and their impact on the services as well as pre
and post-restoration checks. The volume also describes
how to perform FRU/FRE procedures.
Safety Guidelines for This manual describes the general safety guidelines to be
Installation of Hardware followed in connection with installation of hardware and
and Software software. It is a part of Backup and Restore Including
FRU/FRE.
Server Software This manual describes how to perform restoration of all
Restoration application servers. Additionally it contains instructions
for scheduling or creating a backup on-demand. It is a
part of Backup and Restore Including FRU/FRE.
Server Hardware This manual describes how to perform restoration of all
Restoration system servers hosting application servers. The manual
also describes how to perform FRU/FRE procedures
for these servers. It is a part of Backup and Restore
Including FRU/FRE.
Stand-alone Components This manual describes how to backup and restore the
Restoration following components of a new Dimetra IP system:
(cont'd.)
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
MTS 1 Restoration This manual describes how to backup and restore the
Motorola Transceiver System (MTS) 1. The manual also
describes how to perform FRU/FRE procedures. It is a
part of Backup and Restore Including FRU/FRE.
MTS LiTE, MTS 2 and This manual describes how to backup and restore the
MTS 4 Restoration Motorola Transceiver System (MTS) LiTE, 2 and 4.
The manual also describes how to perform FRU/FRE
procedures. It is a part of Backup and Restore Including
FRU/FRE.
EBTS Restoration This manual describes how to backup and restore the
Enhanced Base Transceiver System (EBTS). The manual
also describes how to perform FRU/FRE procedures. It
is a part of Backup and Restore Including FRU/FRE.
Fault Management This manual provides an overview of Fault Management
features and contains troubleshooting procedures.
Unified Event Manager This manual provides an introduction to the Unified Event
Manager (UEM). Included sections are a comprehensive
introduction, tools used for troubleshooting, and
system-level troubleshooting. UEM is an application
that provides reliable fault management services for the
Dimetra IP system.
ZoneWatch This manual describes ZoneWatch which is a Private
Radio Network Management (PRNM) Suite application
that lets you monitor radio call traffic for an individual
zone in real time. ZoneWatch uses different watch
windows that allow you to display only the information
you need to see.
System and Zone Profile This manual describes the System Profile application and
the Zone Profile application which are both a Private
Radio Network Management (PRNM) Suite application.
The System Profile application displays how system-level
applications are being used by the network management
clients. For instance, you can view information for
applications in the system including the total number
of applications purchased, number of licenses in use,
and who is currently using the application. The Zone
Profile application displays detailed information about
applications that are operating in the zone. You can use
Zone Profile to view the zone-level application usage and
view the zone-level application license usage.
(cont'd.)
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
System Alarms and Events This manual lists all the possible alarms for the system.
It also covers transient alarm messages, which are known
as technician messages. This manual is intended for
technicians, network management personnel, or any
other engineering personnel with responsibility for
troubleshooting or monitoring the operational status of
the system.
User Configuration This manual describes the User Configuration Manager
Manager (UCM) which is a Windows based, Private Radio
Network Management (PRNM) Suite application. The
UCM is used in the configuration of the system. It is
also the tool used to modify configuration parameters.
To configure a system, both the UCM and the Zone
Configuration Manager (ZCM) are needed.
Zone Configuration This manual describes the Zone Configuration Manager
Manager (ZCM) which is a Private Radio Network Management
(PRMN) Suite application. The ZCM is used to configure
and maintain operational parameters for equipment in a
system. To configure a system, both the ZCM and the
User Configuration Manager (UCM) are needed.
Configuring Features This manual describes radio features and their
configuration. The manual contains a configuration
checklist as well as configuration procedures for the key
features of the system.
Software Download This manual describes the Software Download (SWDL)
Manager which is a Private Radio Network Management
(PRNM) Suite application that can transfer and install
new software in the Dimetra IP Base Transceiver
Systems (BTS).
Radio Management This manual describes the radio features available to
radios in the Dimetra IP system.
Affiliation Display This manual describes Affiliation Display which is a
Private Radio Network Management (PRNM) suite
application. Affiliation Display enables you to view
the association of a radio with a talkgroup and site,
information about conventional channels, console
sites, and consoles and to monitor how radio users
travel between different sites in a zone and how they
communicate with other members of their assigned
talkgroup or even with members outside of their
talkgroup.
(cont'd.)
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
ATIA Log Viewer This manual describes the Air Traffic Information Access
(ATIA) Log Viewer which is a Private Radio Network
Management (PRNM) Suite application that displays
log files generated by the Air Traffic Router (ATR).
These log files contain records of all recent zone activity,
such as site registrations and calls processed. ATIA Log
Viewer allows you to view the raw ATIA data straight
from the ATIA log.
Radio Control Manager This manual describes the Radio Control Manager
(RCM) which is a Private Radio Network Management
(PRNM) Suite application used primarily by dispatchers
to monitor and manage radio events, issue and monitor
commands, and make informational queries of the system
database.
Radio Control Manager This manual describes the Radio Control Manager
Reports (RCM) Reports which is a Private Radio Network
Management (PRNM) Suite application that is used to
create, view, print, schedule and export standard reports
from RCM. These reports use a common format so the
data can be used in spreadsheets. The report information
reflects the actual RCM server database information
except the Emergency Alarms.
Fleetmapping This manual describes how to properly plan for, set up,
and manage your system. The Motorola engineering
team works with your organization to plan, and set
up your system. Accurate operational requirements
are needed to ensure a successful system plan. By
properly configuring the Dimetra IP system to meet your
operational needs, your organization will have the most
efficient and effective communications system available.
Performance Management This manual provides an overview of Performance
Management features. By monitoring the performance of
the system, you can identify potential problems before
they occur as well as adjust system resources to provide
optimum performance.
Dynamic Reports This manual describes Dynamic Reports which is a
Private Radio Network Management (PRNM) Suite
application that provides predefined report templates you
can use to display statistics for a zone, site or a console
site (but not for a system) in near real time.
(cont'd.)
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
Historical Reports This manual describes Historical Reports which is a
Private Radio Network Management (PRNM) Suite
application that allows you to generate reports for
system-wide activity and for individual zones. These
reports display data that is stored on the server. The
Historical Reports application generates reports of
statistical data that is gathered at specific, predefined
time intervals. You can then create reports from this data
to monitor and analyze information about zones, sites,
channels, talkgroups, and users.
InfoVista This manual describes InfoVista which is a
customizable performance management application.
InfoVista interfaces with, and gathers data from,
multiple network devices supporting Simple Network
Management Protocol (SNMP) including master site
routers, Ethernet LAN switches, and WAN switches.
The InfoVista client application is used to access server
software and perform administrative tasks such as
starting and stopping existing reports, adding an instance,
or creating a new report.
Security Management This manual provides a security overview for the Dimetra
IP system. Attacks on communications networks
could interrupt mission critical operations, compromise
classified or restricted information, and contribute
indirectly to loss of lives. The manual presents an
overview of the security application users, describes the
security groups and applications, and describes how
to configure and optimize the applications for secure
operation.
Agency Priority Matrix This manual describes the Agency Priority Matrix which
(APM) is a feature used for controlling which talkgroups or radio
users can be assigned to each RF channel resource in the
system. The manual describes how to configure, operate,
maintain, and troubleshoot the Agency Priority Matrix.
Radio User This document describes the Radio User
Assignment/Radio User Assignment/Radio User Identity (RUA/RUI)
Identity (RUA/RUI) feature. The purpose of this manual is to provide a user
with a background knowledge on the feature as well as
enable to install, configure and maintain the Alias Server.
It also describes how to operate RUA/RUI from the Alias
Provisioning Client.
(cont'd.)
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
Data Subsystem This manual describes the Data Subsystem and its
components. It provides information on how to install,
configure, operate and maintain the equipment and
software including the Packet Data Gateway (PDG),
Short Data Router (SDR), and Gateway GPRS Support
Node (GGSN) Router. The Data Subsystem performs
registration services for packet data users, maintains
user permissions and mobility information, and provides
routing of traffic to the radio network and the Gateway
GPRS Support Node (GGSN) Router.
MultiCADI This manual describes the Computer Aided Dispatch
Interface (CADI) which is an Application Programming
Interface (API) that provides the capability for systems
external to the Dimetra IP SwMI to obtain information
about, and exert some control over, radios. The CADI
API enables third parties to write software applications
called CADI clients that can receive events from,
and submit commands to, the Dimetra IP SwMI.
Multi-Computer Aided Dispatch Interface (MultiCADI)
is a server application and an API, which enables third
parties to develop application programs that can utilize
the facilities provided by the CADI in the Dimetra IP
system. The MultiCADI API builds upon the CADI API,
but provides additional capabilities.
Telephone Interconnect This manual provides the information necessary to
install, configure, operate, and maintain the components
in a Telephone Interconnect subsystem. The Telephone
Interconnect subsystem provides an interface between
the Dimetra IP radio network and an external telephone
network, allowing telephone interconnect calls to be
made between Dimetra IP radios and external telephones.
Active Directory/Domain This manual describes Active Directory (AD) which
Name Services is the service that provides access to enterprise-wide
data and improved integration with the rest of the radio
system. The manual contains procedures for installation
and configuration of software necessary to make Active
Directory operational. It also contains procedures for
adding users and groups, and for backup and restore of
Active Directory.
TESS Software User Guide This manual is an introduction and guide to the use of
the Dimetra BTS (Base Transceiver System) Service
Software. Through the Dimetra BTS Service Software
trained service personnel and systems engineers can
configure and program a BTS.
(cont'd.)
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
Transport Network Device This manual describes the Transport Network Device
Manager (TNDM) Manager (TNDM), which allows you to deploy
previously prepared configurations to network devices.
It also allows for tasks such as: rebooting devices,
uploading firmware, checking firmware version,
configuration backup and restore, checking device
connectivity.
Alphanumeric Text Service This manual describes the Alphanumeric Text Service
(ATS) (ATS) application, which enables text messages to be
sent between Mobile Stations (MS), Dispatch Consoles
and computers in the fixed network.
Backup/Restore Collector This manual describes the Backup/Restore Collector
Application User Guide application which provides a simple way of fetching
backup files from a group of the Dimetra IP network
elements via FTP. The network elements can be
configured to run scheduled backups and store these
backups on local disk typically during the night when
there is a smaller load of the system. The role of the
Backup/Restore application is to collect these files
and provide a centralized point of storage for them.
The backup files are accessible by FTP for collection
either manually or from a server running an automated
procedure. The files can be restored from their centralized
storage location back to the network elements.
UCS Synchronization Tool This manual describes the User Configuration Server
(UCS) Synchronization Tool, which provides automated
intercluster configuration of some of the UCS objects that
require to be registered in all clusters in a multicluster
system.
Local Gateway Trunking This manual describes the local gateway trunking
functionality, its operational aspects, and its
configuration.
Dimetra Enhanced This manual describes the Dimetra Enhanced Software
Software Update User Update feature, which provides backup and restore
Guide functionality, and upgrade functionality.
(cont'd.)
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
Authentication and This manual gives an overview of the authentication and
Encryption Overview air interface encryption features in the Dimetra IP system
including:
(cont'd.)
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
Clear Provisioning Centre This manual describes how to use the Clear Provisioning
(CPrC) User Manual Centre (CPrC) application. The main functions of the
Provisioning Centre are:
(cont'd.)
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
Network Security This manual describes all necessary actions to install,
configure and maintain the network security feature
within the Dimetra IP system. The intention of the
manual is to enable the reader to deploy the best possible
level of security, which will protect the system against
viruses, unauthorized authentication or attacks of
hackers. The network security feature provides virus
protection, authentication, and firewall protection.
End-to-End Encryption This manual describes how to configure the KVL 3000
KVL3000 Plus User Guide Plus for initial use, and entering and storing encryption
keys in to target devices, such as radios, CryptRs and
Mobile CryptRs.
Air Interface Encryption This manual describes how to configure the KVL 3000
KVL3000 Plus User Guide Plus for initial use, and entering and storing encryption
keys in to target devices, such as radios and others in
connection with Air Interface Encryption.
Dimetra KVL 4000 Air This manual provides instructions for using the KVL
Interface Encryption and 4000 Key Variable Loader to perform Air Interface
Authentication User Guide Encryption and Authentication operations in Motorola
Dimetra systems.
Dimetra KVL 4000 This manual provides instructions for using the KVL
Authentication User Guide 4000 Key Variable Loader to perform Authentication
operations in Motorola Dimetra systems.
Dimetra KVL 4000 This manual provides instructions for upgrading/rein-
FLASHPort Upgrade stalling the KVL application, upgrading the Security
User Guide Adapter software, and applying security settings on the
KVL.
Dimetra KVL 4000 Provides basic information on KVL 4000 for Dimetra
AIEA/Auth Quick Start Air Interface Encryption and Authentication.
Guide
CryptR Instruction Manual This manual covers hardware installation, main end-user
operations and a proper maintenance of a range of
devices based on the CryptR hardware platform.
MCC 7500-series Console This manual describes the hardware and software
Sites components associated with the MCC 7500-series
console sites. It provides overviews of subsystem
functions such as communications with the Zone
Controller, different types of call setups, and descriptions
of status and events.
(cont'd.)
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
MCC 7500C Dispatch This manual describes the hardware and software
Console components associated with the MCC 7500C Dispatch
Console. It provides operation and troubleshooting
procedures for the Elite Admin and Elite Dispatch
software, and it provides an overview of MCC 7500C
accessories.
MCC 7500 Archiving This manual provides an introduction to the hardware
Interface Server and software components associated with the MCC
7500 Archiving Interface Server. Included are detailed
procedures for installation, configuration and operation
of the server.
MCC 7500 Dispatch This manual describes the MCC 7500 Dispatch
Communications Server Communications Server. Included are detailed
procedures for installation, configuration and operation
of the server.
MCC 7500 Remote This manual provides a high level technical overview
Dispatch Console of the Remote Dispatch Console product and gives
detailed procedures for its installation, configuration and
maintenance.
MCC 7500 Discreet This manual describes Discreet Listening, which is
Listening a feature that enables real-time listening into one to
one calls involving a specific radio user. Listening is
possible for calls inside the Dimetra IP system or through
telephone interconnect to an ordinary telephone. Using
the Discreet Listening feature, a user is able to listen
to calls involving the radio user without either of the
calling parties knowing about it. The manual describes
both the hardware and software used for the Discreet
Listening feature, and contains procedures how to install,
configure, and operate the feature.
MCC 7500 Analog This manual provides an introduction to the hardware
Conventional Operation and software components associated with the analog
conventional feature of the MCC 7500 Dispatch Console.
MCC 7500-series This manual provides an introduction to the bandwidth
Bandwidth Management management, which is necessary in an MCC 7500-series
console subsystem to ensure efficient transport for the
services in your system (voice calls, data service and so
on).
MCC 7500 Console This manual provides a technical overview and
Interoperability troubleshooting information for the interoperability
feature. Console interoperability is the term for a radio
system that supports call traffic involving both the
CENTRACOM Gold Series and Motorola MCC 7500
dispatch consoles.
(cont'd.)
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
MCC 7500C/MCC 7500S This manual describes the Elite Admin software.
Elite Admin Software User The software creates a virtual desktop on the screen
Guide where resources that are part of the dispatch system
are displayed graphically. Resources are grouped
into folders, and one or more folders are stored as a
configuration. The system administrator uses the Elite
Admin software to set up configurations for the Elite
Dispatch desktops that organize resources to meet
specific user needs.
MCC 7500C/MCC 7500S This manual describes the Elite Dispatch application
Elite Dispatch Software which enables console dispatchers to communicate with
User Guide radio resources.
MCC 7500 Emergency This manual describes how to install, configure, operate,
Beacon User Guide and test an emergency beacon installed on a console.
MCC 7500 This manual describes how to generate the translated
Internationalization text (appropriate to the target country or region) using
Process User Guide the Internationalization Package. The translated text is
generated for the following MCC 7500 products:
(cont'd.)
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
MTS LiTE, MTS 2, and This manual describes all necessary actions to install,
MTS 4: Installation, configure and maintain the Motorola Transceiver Station
Configuration, and Basic LiTE, 2 and 4 (MTS LiTE, MTS 2 and MTS 4) within
Service Manual the Dimetra IP System.
MTS Man Machine This manual describes the Man-Machine Interface
Interface (MMI) commands used to test and configure MTS sites.
Commands
EBTS: Installation, This manual describes all necessary actions to install,
Configuration, and Basic configure and maintain the Enhanced Base Transceiver
Service Systems (EBTS) within the Dimetra IP System.
MBTS: Installation, This manual describes all necessary actions to install,
Configuration, and Basic configure and maintain the Mini Base Transceiver
Service Systems (MBTS) within the Dimetra IP System.
Customer Specific Manuals
Cluster Hot Standby (CHS) This manual describes installation, configuration, and
Tools usage of the Cluster Hot Standby (CHS) Tools. CHS
Tools are used to synchronize active and fallback clusters
configurations and detect any discrepancies between
them.
Cluster Hot Standby (CHS) Online help for the CHS application.
Tools Online Help
Dimetra IP Compact/Scalable Dimetra IP Specific Manuals
System Reference Guide This manual offers an introduction to the Dimetra IP
Compact/Scalable Dimetra IP system. The information
covers the major components of the system and the
interconnection of components in the Mobile Switching
Office (MSO), as well as troubleshooting information.
Managing Radio Users, This manual describes the most common day to day
Radios, Talkgroup Quick tasks related to the management of radio users, radios,
Reference Guide and talkgroups.
Managing the This manual describes the three most common
Infrastructure Quick applications to use when monitoring and doing basic
Reference Guide troubleshooting of your system: Unified Event Manager
(UEM), ZoneWatch and Radio Control Manager (RCM).
The guide gives a quick overview of the most common
day to day tasks and activities.
Network Configuration This manual describes the Network Configuration Tool
Tool (NCT) Express (NCT) Express, which allows you to deploy previously
prepared configurations to network devices. It also
allows for tasks such as: rebooting devices, uploading
firmware, checking firmware version, configuration
backup and restore, checking device connectivity.
(cont'd.)
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
DIPC Upgrade Sun This manual contains information and procedures
Fire X4170/HP ProLiant necessary to upgrade a DIPC system from 7.0 to 8.1
DL360 G7 release on Sun Fire X4170 and HP ProLiant DL360 G7
server platforms.
DIPC Upgrade Sun This manual contains information and procedures
Netra 240 necessary to upgrade a DIPC system from 7.0 to 8.1
release on Sun Netra 240 server platform.
Online Help
Application Launcher This online help describes how to operate the Application
Online Help Launcher software.
Unified Event Manager This online help describes how to operate the Unified
(UEM) Online Help Event Manager application. It also covers detailed
information on all system alarms and events.
ZoneWatch Online Help This online help describes how to operate the ZoneWatch
application.
System and Zone Profile This online help describes how to operate the System and
Online Help Zone Profile applications.
User Configuration This online help describes how to operate the User
Manager (UCM) Online Configuration Manager application.
Help
Zone Configuration This online help describes how to operate the Zone
Manager (ZCM) Online Configuration Manager application.
Help
Software Download Online This online help describes how to operate the Software
Help Download application.
Affiliation Display Online This online help describes how to operate the Affiliation
Help Display application.
ATIA Log Viewer Online This online help describes how to operate the ATIA Log
Help Viewer application.
Radio Control Manager This online help describes how to operate the Radio
(RCM) Online Help Control Manager application.
Radio Control Manager This online help describes how to operate the Radio
(RCM) Reports Online Control Manager Reports application.
Help
Dynamic Reports Online This online help describes how to operate the Dynamic
Help Reports application.
Historical Reports Online This online help describes how to operate the Historical
Help Reports application.
(cont'd.)
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
Authentication Centre This online help describes how to operate the
Online Help Authentication Centre application.
Key Management Facility This online help describes how to operate the Key
(KMF) Online Help Management Facility applications.
BTS Service Software This online help describes how to operate the BTS
(TESS) Online Help Service Software.
MCC 7500 Elite Dispatch This online help describes how to operate the MCC 7500
Software Online Help Elite Dispatch software.
MCC 7500 Elite Admin This online help describes how to operate MCC 7500
Software Online Help Elite Admin software.
MCC 7500 Emergency This online help describes how to operate MCC 7500
Beacon Online Help Emergency Beacon software.
MCC 7500 Discreet This online help describes how to operate the MCC 7500
Listening Online Help Discreet Listening software.
Backup and Restore Including FRU/FRE for Upgrading Customers
Common Hardware and The purpose of this manual is to provide users with
Software Restoration the information necessary to successfully restore the
common hardware platforms (for clients and servers) and
their respective operating systems used in a Dimetra IP
system.
Call Processing, NM This manual provides users with the procedures and
and Data Subsystems FRU/FRE information needed to restore and back up
Restoration - Generation 2 the Zone Controller (ZC), Network Management (NM)
System servers and Data servers in a Generation 2 Dimetra IP
system.
Call Processing, NM This manual provides users with the procedures and
and Data Subsystems FRU/FRE information needed to restore and back up
Restoration - Generation 3 the Zone Controller (ZC), Network Management (NM)
System servers and Data servers in a Generation 3 Dimetra IP
system.
Standalone Subsystems This manual provides users with the procedures and
and Components FRU/FRE information needed to restore and back up
Restoration - Generation 2 standalone servers and components (MTIG, MultiCADI,
System Alias Server, Domain Controller, AuC/PrC and CryptR2)
in a Generation 2 Dimetra IP system.
Standalone Subsystems This manual provides users with the procedures and
and Components FRU/FRE information needed to restore and back up
Restoration - Generation 3 standalone servers and components (MTIG, MultiCADI,
System Alias Server, Domain Controller, AuC/PrC and CryptR2)
in a Generation 3 Dimetra IP system.
(cont'd.)
Dimetra IP
Dimetra IP Compact/
Document Title Description
Scalable Scalable
Dimetra IP
Backup/Restore Collector This manual describes the Backup/Restore Collector
Application User Guide - application, which provides a simple way of fetching
Generation 2 System backup files from a group of the Dimetra IP network
elements via FTP. The network elements can be
configured to run scheduled backups and store these
backups on local disk typically during the night
when there is a smaller load of the system. The role
of the Backup/Restore application is to collect these
files and provide a centralized point of storage for
them. The backup files are accessible by FTP for
collection either manually or from a server running an
automated procedure. The files can be restored from
their centralized storage location back to the network
elements. This version of the manual is applicable to
Generation 2 systems.
Backup/Restore Collector This manual describes the Backup/Restore Collector
Application User Guide - application, which provides a simple way of fetching
Generation 3 System backup files from a group of the Dimetra IP network
elements via FTP. The network elements can be
configured to run scheduled backups and store these
backups on local disk typically during the night
when there is a smaller load of the system. The role
of the Backup/Restore application is to collect these
files and provide a centralized point of storage for
them. The backup files are accessible by FTP for
collection either manually or from a server running an
automated procedure. The files can be restored from
their centralized storage location back to the network
elements. This version of the manual is applicable to
Generation 3 systems.