Documente Academic
Documente Profesional
Documente Cultură
DIMETRA
DIMETRA IP COMPACT (DIPC)/SCALABLE DIMETRA IP (SDIP)
SYSTEM OVERVIEW
October 2013
68015000701-C
Copyrights
The Motorola products described in this document may include copyrighted Motorola computer programs. Laws
in the United States and other countries preserve for Motorola certain exclusive rights for copyrighted computer
programs. Accordingly, any copyrighted Motorola computer programs contained in the Motorola products
described in this document may not be copied or reproduced in any manner without the express written permission
of Motorola.
2013 Motorola Solutions, Inc. All Rights Reserved
No part of this document may be reproduced, transmitted, stored in a retrieval system, or translated into any
language or computer language, in any form or by any means, without the prior written permission of Motorola
Solutions, Inc.
Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication,
estoppel or otherwise, any license under the copyrights, patents or patent applications of Motorola, except for the
normal non-exclusive, royalty-free license to use that arises by operation of law in the sale of a product.
Disclaimer
Please note that certain features, facilities, and capabilities described in this document may not be applicable to
or licensed for use on a particular system, or may be dependent upon the characteristics of a particular mobile
subscriber unit or configuration of certain parameters. Please refer to your Motorola contact for further information.
Trademarks
MOTOROLA, MOTO, MOTOROLA SOLUTIONS, and the Stylized M Logo are trademarks or registered
trademarks of Motorola Trademark Holdings, LLC and are used under license. All other trademarks are the
property of their respective owners.
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.
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
List of Telephone Numbers
Country
AUSTRIA
01206091087
DENMARK
043682114
FRANCE
0157323434
GERMANY
06950070204
ITALY
0291483230
LITHUANIA
NETHERLANDS
0202061404
NORWAY
24159815
PORTUGAL
0217616160
RUSSIA
SAUDI ARABIA
SOUTH AFRICA
0800981900
SPAIN
0912754787
UNITED KINGDOM
02030 277499
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
March 2013
68015000701-C
October 2013
vii
Contents
1
ix
System Overview
1.3.4
Document History
xi
System Overview
4.1
xii
Document History
5.5
5.6
5.7
5.8
xiii
System Overview
5.8.1
5.8.2
xiv
Document History
xv
System Overview
xvi
List of Figures
Figure 1-1
Figure 1-2
Figure 1-3
Figure 1-4
Figure 1-5
Figure 1-6
Figure 1-7
Figure 1-8
Figure 1-9
Figure 1-10
Figure 1-11
Figure 1-12
Figure 1-13
Figure 1-14
Figure 1-15
Figure 1-16
Figure 1-17
Figure 1-18
Figure 1-19
Figure 1-20
Figure 2-1
Figure 2-2
Figure 2-3
Figure 2-4
Figure 2-5
Figure 2-6
Figure 2-7
Figure 2-8
Figure 2-9
Figure 2-10
Figure 2-11
Figure 2-12
Figure 2-13
Figure 2-14
Figure 3-1
Figure 3-2
Figure 3-3
Figure 3-4
Figure 3-5
Figure 3-6
Figure 3-7
Figure 3-8
Figure 3-9
Figure 3-10
Figure 3-11
Figure 3-12
Figure 3-13
Figure 3-14
Figure 3-15
Figure 3-16
Figure 3-17
Figure 3-18
xvii
System Overview
Figure 3-19
Figure 3-20
Figure 3-21
Figure 3-22
Figure 3-23
Figure 3-24
Figure 3-25
Figure 3-26
Figure 3-27
Figure 3-28
Figure 3-29
Figure 3-30
Figure 3-31
Figure 3-32
Figure 3-33
Figure 3-34
Figure 4-1
Figure 5-1
Figure 5-2
Figure 5-3
Figure 5-4
Figure 5-5
Figure 5-6
Figure 5-7
Figure 5-8
Figure 5-9
Figure 5-10
Figure 5-11
Figure 5-12
Figure 5-13
Figure 5-14
Figure 6-1
Figure 7-1
Figure 7-2
Figure 7-3
xviii
List of Tables
Table 3-1
Table 3-2
Table 4-1
Table 4-2
Table 4-3
Table 5-1
Table 5-2
Table 5-3
Table 5-4
Table 5-5
Table 6-1
Table 7-1
Table 7-2
Table 7-3
Table 7-4
Table 7-5
Table A-1
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
xxiii
xxv
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
This typeface is used for messages, prompts, and other text displayed on
the computer screen (example: A new trap destination has
been added).
This typeface is used for keyboard keys (example: Press Y, and then press
Enter).
>
A > (right angle bracket) is used for indicating the menu or tab structure
in instructions on how to select a certain menu item (example: File >
Save) or a certain sub-tab.
xxxiii
Microphone
0
Antennas
0
0
0
0
Tra ns mitte r
Receiver
Loudspeaker
1-1
System Overview
Fixed equipment is located at a central site. A base station is used to transmit the signal generated through the
microphone to portable and mobile equipment located at some distance. The range of the base station depends
on its power, antenna system, terrain, and environmental conditions. The location of the base station control is
known as the Dispatch Centre.
Figure 1-2
Fixed Equipment
0
0
0
0
0
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-2
1.1.2.1 Simplex
1.1.2.1 Simplex
The most basic type of radio communication is simplex. Simplex communication consists of radio units operating
on a single frequency. Because everyone transmits and receives on the same frequency, users cannot talk and listen
at the same time. Simplex means transmission in one direction at a time.
Figure 1-4
Simplex Communication
Single Frequency
A simplex radio system works well when there are only a few users who are closely located. When additional users
are added to the system, the competition for the one available frequency can make it difficult to get a message
across. In addition, great distances and natural obstacles such as high hills and tall buildings can interfere with the
single frequency.
1.1.2.2 Semi-Duplex
Semi-duplex communication uses two frequencies: one to receive and one to transmit. A radio operating in
semi-duplex mode can only transmit or receive at any time. Radios operating on the Dimetra IP system use
semi-duplex communication to communicate with the base stations during talkgroup and multigroup calls. A
semi-duplex individual call is also supported in the Dimetra IP system.
Figure 1-5
Semi-Duplex Communication
TX 851.0125 MHz
RX 806.0125 MHz
1-3
System Overview
1.1.2.3 Duplex
Duplex communication uses different frequencies simultaneously, one to transmit and the second to receive. The
transmitter output is isolated and separated in frequency to prevent blocking the input of its companion receiver.
Also called full-duplex, this type of operation is used to indicate that the equipment can receive and transmit at
the same time. Normally, fixed equipment (a base station) operates in full-duplex mode while mobile equipment
typically operates in semi-duplex mode.
1-4
This feature may be applied in an airport system, where different functions carried out at the airport are linked to
flights (that is objects), resulting in a flight-oriented communication system. When an airplane is arriving at an
airport gate, different resources are necessary to service this flight, and for communication purposes these resources
are grouped following a structure of flights and functional groups.
1-5
System Overview
1-6
In a trunked system, the traffic channels can be operated in one of two modes: Transmission Trunking, Message
Trunking or Message Trunking with PTT ID.
Transmission Trunking
The controller reclaims the traffic channel immediately after detecting a disconnect signal from the
transmitting unit. The receiving radios immediately returns to the control channel. The entire request and
assignment procedure is repeated for each PTT from the originator or a radio responding to the original call.
PTT-ID Trunking
This allows a group to retain the assigned traffic channel for some time, after the transmitting unit releases the
PTT. When a message trunked call is in progress, other radio users within the same group are allowed to key
without returning to the control channel for a traffic channel assignment. This mode of operation provides
positive identification of the transmitting radio and must be programmed in both the radio and the system.
1-7
System Overview
The BTS has several channels and these channels can either be designated to Control Channel (CC) or Traffic
Channel (TCH), which are mentioned below.
1.1.6 Radios
Radios are classified as mobile (vehicle-mounted) or portable (carried by a person, usually handheld) radios
which provide users with the ability to make voice calls, send short data messages, or interface with mobile data
equipment. Each radio is assigned a unique identification number that identifies the radio to the system. It also
contains the logic circuitry necessary to perform the following trunking functions:
Generate and transmit requests for service in the form of data words that are then used to modulate the
carrier frequency.
Interpret the signaling messages sent by the central controller.
Generate the frequency of the assigned traffic channel.
Generate tones to advise the radio user of the status of the call request.
1-8
Channel 1
Channel 2
Channel 3
Trunking takes advantage of the fact that people do not talk on their radios continuously for 24 hours a day.
Most radio users need access to a channel several times a day, but their total time on the system may not exceed
five minutes each. Temporary channel assignment helps ensure that a channel is available when a conversation
needs to take place.
Trunking reduces the number of busies and improves the efficiency of the system resources. A call is busied if it has
been placed in a queue due to no channel being available.
1-9
System Overview
Figure 1-8
Controller
CC
TCH
TCH
Channel 1
Channel 2
Channel 3
TCH
Channel 4
1-10
Figure 1-9
Channel 1
Channel 2
Channel 3
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-11
System Overview
Figure 1-10
Ta lkgroup 1
Ta lkgroup 2
Ta lkgroup 3
1.1.7.2.3 Multigroups
Several talkgroups can be combined to form a multigroup (also called an announcement group). Multigroups are
assigned an ID from the same pool of numbers as the talkgroups. In this example, calls placed to Multigroup A
would be heard by the radio users in Talkgroups 2 and 3.
Figure 1-11
Ta lkgroup 2
Ta lkgroup 3
Ta lkgroup 1
Multigroup A
1-12
When a radio user initiates a call, the radio signals to the system via the control channel and requests a traffic
channel.
In the figure below, Radio 1 is requesting a call, and Radio 2 and Radio 3 in Talkgroup B are listening on the
control channel and detect the request for a call. The radios in Talkgroup A are also monitoring the control
channel but ignore the call request because they are in different talkgroup.
In Figure 1-12 Trunked Call Initiation, Figure 1-13 Trunked Call Validation, and Figure 1-14 Trunked
Call Completion, the arrows indicate the direction in which the information flows.
Figure 1-12
TETRA Carrier
C
Ta lkgroup A
Ta lkgroup B
1-13
System Overview
The system validates the call request, assigns a traffic channel and signals a traffic channel grant to all radios
of that group. The members of Talkgroup B respond by monitoring the temporarily assigned traffic channel.
Radios in Talkgroup A continue to monitor the control channel as before.
In the figure below, Radio 1 is transmitting on a traffic channel, and Radio 2 and Radio 3 are listening to the call.
Figure 1-13
TETRA Carrier
C
Ta lkgroup A
3
1-14
Ta lkgroup B
When the call is finished, all radios in Talkgroup B return to monitoring the control channel. The traffic
channel becomes available for other radios.
Figure 1-14
TETRA Carrier
C
Ta lkgroup A
Ta lkgroup B
1-15
System Overview
Figure 1-15
Site Controller
trolle r
RF Site
Mobile Switching
S wi
witching
Office
ce
Site Controller
RF Site
Site
S
ite Controller
Con
ontrolle r
RF Site
1.2.1 RF Sites
An RF site is a geographical area within which a two-way radio infrastructure allows communication between
two-way radios. It is the equivalent of a single site trunked system with additional control and audio links to a
central mobile switching office (MSO). Under certain conditions, it can operate independently in local site trunking
mode, but its normal mode of operation is in wide-area trunking with other RF sites. The figure below shows an
example of an RF site.
1-16
1.2.2 Zone
Figure 1-16
RF Site
Site
1.2.2 Zone
A zone consists of sites connected to the master site. The Zone Controller is the central point for all the equipment
necessary to control and manage the sites in a zone.
1-17
System Overview
Figure 1-17
Zone
Controller
Control
Sites
Mobile Switching
Office
Base
Stations
1-18
Site 1
Site 4
Site 2
Co
ol
n tr
d io
Au
Ma s te r S ite
Zone 1
ol
n tr
C o d io
Au
Ma s te r S ite
Zone 3
l
ro
nt
C o u d io
A
Control
Audio
Site 6
Ma s te r S ite
Zone 2
Co
n
Au tro l
d io
Site 9
Control
Audio
Site 7
Co ntro l
Au dio
Control
Audio
Co
n
Au tro l
d io
Co
Au n tro
di l
o
Control
Audio
Co ntro l
Au dio
Site 3
Site 5
Site 8
Multizone systems contain various hardware devices and software applications that allow the system to exchange
control information between zones, establish audio paths between zones when necessary, track radio movement
across sites or zones, and provide a management subsystem that can be accessed from any one of the zones. The
terminology has expanded to include home zone mapping, controlling zone, and participating zone.
1-19
System Overview
The zone assigned to a particular ID is the home zone of this ID. The home zone to which an ID is assigned has an
impact on how the system operates. Home zone assignment affects system operation in the following ways:
Configuration information is distributed throughout the system based on the home zone assignment
of the ID.
A Zone Controller stores only the configuration information for those individual and group IDs that are
home to that zone.
1-20
Figure 1-20
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.
1-21
System Overview
1.3.4.2 Zone
Calls can take place between multiple sites within a zone. The Zone Controller arranges the necessary sites for the
call, and the Site Controllers (SCs) for each site assign the channel needed for the call.
1.3.4.3 Multizones
In a multizone system, calls can take place between more than one zone. The controllers at the MSO of each zone
communicate with each other to coordinate the assignment of resources.
1-22
Infrastructure
2-1
System Overview
The most typical users of a TETRA system include public safety, transportation, utilities, industrial organizations,
government agencies, and private telecommunication agencies.
2-2
Figure 2-2
Pi/4-DQPSK Modulation
2-3
System Overview
Figure 2-3
2-4
2-5
System Overview
Ethernet accesses data using Carrier Sense Multiple Access with Collision Detection (CSMA/CD). This method
allows multiple users to access the network through a common cable. All devices attached to the network check for
transmissions in progress, signals are checked at the start of transmission and during transmission. Signals are sent
if no other transmission is detected; otherwise, the transmission is delayed. Collision detection is applied when two
or more devices transmit at the same time. A device knows if a collision occurred when it does not receive its own
transmission back. Each device stops transmission and attempts to retransmit after waiting a certain amount of
time, which is different for each device and determined by an algorithm.
2-6
VLAN technology allows a system administrator to assign each port of a switch to members of different Ethernet
segments. The MSOs in a Dimetra IP system use switches that support VLAN technology in an extended stackable
configuration.
The use of intelligent switches instead of passive hubs to form Ethernet networks permits the use of Virtual
LAN (VLAN) technology, IEEE 801.2Q.
2-7
System Overview
under-utilization of the communication channel. Circuit-switching is useful for short duration transmissions,
for feeders to main sites or for backup/disaster recovery situations.
2.2.2.1 E1 Carrier
An E1 carrier is a telecommunications facility designed to carry digital information at a bit rate of 2.048 Mbps.
In conventional telecommunications, the most common use for an E1 carrier is to connect central offices within
an individual telephone company. Telephone companies also lease E1 carriers to their customers for their own
private purposes. Most systems use E1 circuits to transmit digitized voice, management, and control traffic between
zones. The Frame Relay protocols provide the means for exchanging information over the E1 communication
facilities that connect remote zones.
Various types of transmission media can be used in implementing a private E1 facility, such as various types of
privately installed cabling or point-to-point microwave circuits.
An E1 circuit is divided into 32 time slots, each of which implements a separate communication channel that can
support a bit rate of 64,000 bps. Each of these individual channels is referred to as a Digital Signal Level zero
(DS0) channel.
The term framing refers to the order in which user bits and other information is transmitted over a physical
transmission medium. An E1 frame comprises a total of 256 bits. Each of the 32 inputs is assigned a fixed time
slot; the E1 uses a time-division multiplexing technique to divide the capacity of the carrier into 32 channels. The
framing bit is used to create a pattern to help synchronize the equipment. The figure below illustrates the format
of the E1 transmission frame.
Figure 2-6
E1 Carrier
2-8
2-9
System Overview
Figure 2-7
2-10
Ethernet links are supported over a Layer 2 or Layer 3 of the GBN (Ground Based Network). Each Ethernet link
terminated at the Mobile Switching Office (MSO) is represented by an IP tunnel terminated at MSO routers. IP
tunnels at the zone core are implemented either as all encrypted IPSec tunnels, or all unencrypted IPIP tunnels. A
pair of backhaul switches per MSO are used to aggregate the IPSec and IPIP tunnels for site links and inter-MSO
links.
Figure 2-8
Ethernet 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.
2-11
System Overview
2-12
Unicast Routing
S
Most datagrams sent across a typical network use unicast messaging to deliver information between one point
and another.
2-13
System Overview
Figure 2-10
Multicast Routing
RP
S
Since talkgroup and announcement calls involve routing of audio between a single source and multiple recipients,
multicast routing works well with group-based audio routing. Multicast allows the transmitting radio audio to be
distributed to the appropriate sites by the RP router. Without multicast, the source would have to separately address
multiple copies of each packet to each of the individual recipients across the network.
In the Dimetra IP network, all the devices associated with a particular call are instructed to join a specific multicast
group. After the join messages are received from the devices, the RP propagates the multicast traffic to the
appropriate devices, sites, and zone(s) that are involved in the call and that have sent their join message.
The RP is typically defined as the router located near the receiving end of the multicast traffic, rather than a router
located near the source of the traffic. This allows greater efficiency of network resources, since the higher volumes
of multicast traffic is only spread across the receiving end of the network, rather than spreading all the replicated
packets directly from the source location across the entire network.
Multicast trees for audio traffic are set up as requested and are present only for the duration of the multicast call. A
range of class-D IP addresses (addresses beginning with 224 -239) are designated as multicast group addresses.
Process Steps
2-14
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.
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.
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.
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.
The IP Multicast audio stream is distributed to all the RF and dispatch sites through the Rendezvous Point
router and IP multicast tree.
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.
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.
2-15
System Overview
Figure 2-11
2-16
2-17
System Overview
Encryption protects the information from being deciphered and understood by anyone outside the system. Without
the proper algorithm and the encryption key, any intercepted traffic is received as a bunch of garbled digital bits
wrapped in packets. If there is no encryption, hobbyists or hostile groups can intercept and decipher traffic.
The Motorola secure voice and data solution uses sophisticated algorithms to protect voice traffic. Depending on
the algorithm used, a radio can be provisioned with a large number of keys. By rotating keys on a regular basis, it
would be nearly impossible for an interceptor to find the correct key and decrypt the traffic.
The figure below shows basic secure voice operation between two radios. The transmitting radio encrypts clear
voice using a particular key (CG456) and transmits the encrypted voice to the transport network. The secure voice
traffic is routed over the network while remaining in an encrypted form, and is transmitted to its intended recipient.
The receiver radio then uses the same key (CG456) to decrypt the traffic and provide clear voice to the user.
2-18
Figure 2-14
Voice Transmission
Compared to Air Interface Encryption (AIE), the secure voice solution adds an additional level of confidentiality to
the speech traffic and is an enhancement to the system. This service does not replace any of the other standard
TETRA security mechanisms, and can coexist overlaid on AIE.
The main difference between AIE and secure voice is that secure voice provides voice encryption all the way from
one radio to another. AIE only provides security for messages between the base station and the radios and it does
not provide any security for messages that exist within the infrastructure, whereas secure voice provides security
between the end users, even within the infrastructure.
Apart from voice, Motorola has also developed a solution for delivering encrypted data. End-to-End Encryption
for Short Data and Packet Data (E2EE SD/PD) is an overlay service that allows secure (digitally encrypted)
data communications between radios and data applications in the customer enterprise network (CEN).
Encryption/decryption services are provided by the system endpoints: Packet Data Encryption Gateway (PDEG),
Mobile Data Encryption Gateway (MDEG), Short Data Encryption Gateway (SDEG) and radios, so communication
remains secure between the source and the destination. Secure data is a supplementary service located on a
customer premises (the Switching and Managing (SwMI) infrastructure is not encryption aware). The solution
is based on the current key management solution, in other words, a symmetrical key exchanged with the KMF.
Digital encryption converts the digital data, using an encryption key together with an encryption algorithm, into an
encrypted message which is then transmitted. Only an endpoint that shares the same encryption key and encryption
algorithm is able to decrypt the transmission successfully. Other devices that do not have the proper key are not
able to receive intelligible information.
For more information see the Secure Voice, Data and Key Management manual.
2-19
One of the master sites (which are physical locations in Dimetra system containing one or more sets of
zone control equipment) in a multizone system is generally designated as the cluster MSO. This MSO
typically includes the cluster-level servers, including the combined User Configuration Server (UCS).
3-1
System Overview
List of Entities
MTIG-IP01
MTIG-IP01
MTIG-IP02
MTIG-IP02
MTIG-E101
MTIG-E101
MTIG-E102
MTIG-E102
3-2
MTIG-E1
Server 1
Primary
Management
Server
MTIG-IP
Server 1
Primary
Zone Server
Primary Data
Server
GPS
To PABX
Figure 3-2
Secondary
Zone Server
NTS
EC
KMF
NM Client
E1 CGE1
Router
GGSN1
VPN
Router
CWR Panel
E1 - GBN
BTS
Remote Control Zone
Other Zone
Internet
VPN
Client
Mutually exclusive
3-3
System Overview
The server components of the Network Management subsystem reside on the Primary Management Server
and include User Configuration Server (UCS), Zone Database Server (ZDS), Zone Statistics Server (ZSS),
Unified Event Manager (UEM), System Statistics Server (SSS), and Air Traffic Router (ATR).
Network management provides the tools, commonly known as FCAPS, for fault, configuration, accounting
performance and security management. The network management functions in Dimetra IP are distributed across
several applications and servers that are installed in one of three configurations: system, zone, and remote. The
configurations are designated by the name Operations Support Systems (OSS). The individual network management
building blocks of the Zone OSS and Cluster OSS can be divided into two categories:
Private Radio Network Management (PRNM) client applications such as:
ZoneWatch
Radio Control Manager (RCM)
Zone Configuration Manager (ZCM)
User Configuration Manager (UCM)
Radio Control Manager Reports (RCM Reports)
Historical Reports
Dynamic Reports
ATIA Log Viewer
Affiliation Display
Unified Event Manager (UEM)
Software Download Manager
Network Transport Management (NTM) client applications.
Network Configuration Tool Express (NCT)
Trivial File Transfer Protocol (TFTP)
3-4
3-5
System Overview
Clusterwide Fault Management on some systems may only refer to Dimetra Radio System managed
objects and not necessarily IP devices (Routers, LAN Switches) depending on network configurations.
3-6
3-7
System Overview
MTIG-E1
Server 1
Primary
Management
Server
MTIG-IP
Server 1
Primary
Zone Server
Primary Data
Server
GPS
To PABX
Figure 3-3
Secondary
Zone Server
NTS
EC
Core LAN Switch 1&2
KMF
NM Client
CGE1
MCC7500
Router
AIS
GGSN1
VPN
Router
CWR Panel
E1 - GBN
BTS
Remote Control Zone
Other Zone
3-8
Internet
VPN
Client
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.
3-9
System Overview
After a KVL loads keys into a radio, the radio sends a receipt or acknowledge message. When the KVL is
connected with the PrC again, the acknowledge messages are loaded into the PrC and the successful status of
the key loading is maintained by the PrC.
The PrC also outputs authentication material and air interface encryption keys by CD to the Authentication Centre.
The AuC securely stores and uses these keys for authentication and air interface encryption purposes.
The Provisioning Centre is isolated from the network. It includes a client, database server, and PrC server all
integrated into one chassis. The PrC runs the Windows 7 operating system and provides a user interface for key
management operations.
The PrC uses CryptR 2 device for encryption and decryption of the key material.
3-10
Figure 3-4
For more detailed description of Network Time Server, see the Network Time Server manual.
3-11
System Overview
MTIG-E1
Server 1
Primary
Management
Server
MTIG-IP
Server 1
Primary
Zone Server
Primary Data
Server
GPS
To PABX
Figure 3-5
Secondary
Zone Server
NTS
EC
Core LAN Switch 1&2
KMF
E1 CGE1
NM Client
E1 CGE2
MCC7500
Border
Router
AIS
GGSN1
VPN
Router
CWR Panel
E1 - GBN
BTS
Remote Control Zone
Other Zone
3-12
Internet
VPN
Client
Mutually exclusive
3.2.1 Switches
MTIG-E1
Server 1
Primary
Management
Server
MTIG-IP
Server 1
Primary
Zone Server
Primary Data
Server
GPS
To PABX
Figure 3-6
Secondary
Zone Server
NTS
EC
Core LAN Switch 1&2
KMF
NM Client
Eth
CGE1
Eth
CGE2
BH
Switch 01
BH
Switch 02
ESL - GBN
BTS
Remote Control Zone
Other Zone
MCC7500
Border
Router
AIS
GGSN1
VPN
Router
Internet
VPN
Client
Mutually exclusive
3.2.1 Switches
The following functional types of switches are available:
3-13
System Overview
A virtual LAN is set up on each of the core LAN switches. The purpose of these as Transitional LANs (TLAN1
and TLAN2) is to carry traffic between the various core, gateway, and exit routers. The core, gateway and exit
routers connect to both TLANs. If an Ethernet port fails, traffic is transferred to the remaining TLAN. The core
LAN switch is the main Ethernet switch used to interconnect all the Ethernet interfaces for all servers, clients, and
routers. Devices are physically connected into the switch in a way that provides the highest reliability.
3.2.2 Routers
The master site network transport functions in the Dimetra system are provided by S6000 router and GGM 8000
gateway.
3-14
Figure 3-7
3-15
System Overview
MTS LiTE
The MTS LiTE is available in the 260, 350, 380-430, 450-470 and 800 MHz frequency bands.
A typical MTS LiTE Site configuration includes four major functional components:
Base Radio
Site Controller (SC)
RF Distribution System (RFDS)
Power Supply
A Radio Frequency Distribution System (RFDS) distributes up to two Receive antennas to the base radio (BR).
The duplexer enables a duplexed Receive/Transmit function on one antenna, which further reduces the total
count on antennas per site.
3.3.1.2 MTS 1
The MTS 1 is a small, single base station designed to be wall mounted for indoor use or mast mounted for outdoor
use in larger systems. For additional capacity, two MTS 1s can be connected to work in a dual configuration for
additional capacity and resilience. The MTS 1 enclosure is dust tight and also protects against other environmental
elements, such as water. The MTS 1 provides up to 4 channels in a single cabinet or up to 8 channels in a dual
MTS 1 configuration. It is available in the 380 - 470 MHz frequency band. A typical MTS 1 site configuration
includes four major functional components:
Base Radio
3-16
3.3.1.3 MTS 2
MTS 1
3.3.1.3 MTS 2
The MTS 2 is a small, very powerful base station designed for indoor working without the requirement for cooling
fans. All modules can easily be accessed through the cabinet front door. Due to its small size a complete MTS 2
cabinet can easily be fitted into a 19" outdoor enclosure with heat exchanger. Note that the standard cabinet has air
convection holes so that it is not environmentally protected against water or heavy dust.
3-17
System Overview
Figure 3-10
MTS 2
The MTS 2 provides up to 8 channels in a single 61 cm high cabinet. It is available in the 260, 350, 380-430,
450-470 and 800 MHz frequency bands.
A typical MTS 2 Site configuration includes four major functional components:
Base Radio(s)
Site Controller (SC)
RF Distribution System (RFDS)
Power Supply
A Radio Frequency Distribution System (RFDS) combines two transmit channels onto one antenna and distributes
up to three Receive antennas to the base radios (BRs). The duplexer enables a duplexed Receive/Transmit function
on one antenna, which further reduces the total count on antennas per site. The hybrid combiner is a wide band
component and does not need to be tuned on a certain frequency.
For expansions the main modules of the MTS 2 can be re used in an MTS 4. Expansions from MTS 2 to MTS 4 do
not require any modification of the antenna installation. The antenna installation can be re used without any change
and little more floor space is required for increased capacity supported by MTS 4.
3.3.1.4 MTS 4
MTS 4 is a high capacity base station. It provides up to 16 channels in a single 143 cm high cabinet or up to 32
channels in two cabinets. It is available in the 260, 350-370, 380-430, 450-470 and 800 MHz frequency bands.
A typical MTS 4 Site configuration includes four major functional components:
Base Radio(s)
Site Controller (SC)
RF Distribution System (RFDS)
Power Supply
3-18
Figure 3-11
MTS 4
A Radio Frequency Distribution System (RFDS) combines up to eight transmit channels onto just one antenna and
distributes up to three receive antennas to multiple base radios. Duplexers enable a duplexed Receive/Transmit
function, which further reduces the total count on antennas per site. For non-duplexed operation the MTS 4 also
comes optionally with a Tx-postfilter that allows sufficient space for up to three preselectors. This configuration
supports up to triple diversity un-duplexed with one Tx and three Rx antennas.
The MTS 4 prime cabinet is built up out of two card cages above one another and supports up to four base radios.
For expansions up to eight base radios an expansion cabinet of exactly the same size as the prime cabinet can be
added. An MTS 4 card cage with Base Radios power supply and SC is identical to an MTS 2 with the filter
and combiner section removed.
3-19
System Overview
Figure 3-12
A second SC can be installed at the BTS site to provide active/standby redundancy. Redundant Site Controllers
are linked through a 10/100Base-T Ethernet interface.
The SC also provides frequency reference and timing reference. The SC has a high stability oscillator to provide
frequency reference signaling to the base radios. The SC also includes an internal GPS receiver which connects to a
GPS antenna through an RF feeder to provide timing reference. If redundant SCs are installed at the site, both
SCs require a separate GPS antenna connection. If NTS (Network Time Server) is present, it can be used as a
secondary frequency reference
A logical control path and logical manager path are maintained between the BTS site and the MSO. The control
path delivers control traffic between the BTS site and the Zone Controller. The manager path delivers network
management traffic between the BTS site and the network management servers.
The SC software is loaded through the Software Download (SWDL) application. The configuration parameters for
the SC are defined both through the Zone Configuration Manager and through Dimetra BTS (Base Transceiver
Station) Service Software (TESS).
3-20
Figure 3-13
The base station is able to provide air interface encryption by applying a cipher key and a user-defined offset
variable to the inbound/outbound coded traffic. To provision the base station for encryption, the base radio is loaded
locally with a secret infrastructure key through a Key Variable Loader (KVL). This infrastructure key is used to
decrypt cipher keys which are delivered over the network. The base radio uses the appropriate cipher key (SCK,
DCK, or CCK) to encrypt outbound traffic and decrypt inbound traffic.
The BTS base station software is loaded through the Software Download (SWDL) application. This application
can load software to the entire BTS site over the network, or can load software directly to an isolated base radio
through a direct connection. The configuration parameters for the BTS base station are defined both through the
Zone Configuration Manager and through Dimetra BTS (Base Transceiver Station) Service Software.
3-21
System Overview
Figure 3-14
Control Site
GBN
WAN Link
LAN Switch
NM Client
4-Wire
Dispatch
Console
3-22
Figure 3-15
Dispatch Subsystem
Logging Re corde r
LAN S witch
WAN
BTS
Trunking S ite
Cons ole S ite
Route r
w/ CCGW
Re pla y
S ta tion
Loca l Ana log
Conve ntiona l S ta tions
MCC7500
Cons ole s
LAN S witch
3-23
System Overview
Figure 3-16
Archiving
Replay
Station
MCC7500/
MCC7500S
Cons ole
Archiving
Recorder
Device
Ethe rne t
S witch
Archiving
Interface
Server (AIS)
MCC7500/
MCC7500S
Cons ole
WAN
Route r
Desktop Speakers
The Dispatch Console PC supports two speakers through which a dispatch console operator can listen to audio.
Each speaker on a dispatch console contains unique audio; that is, an audio source cannot appear in multiple
speakers at a single dispatch console.
The speaker is designed for use near computer monitors.
Desk Microphone
The Dispatch Console PC supports a single desk microphone. The microphone is the AKG31/AKG33 and
gooseneck GN 30E.
Footswitch
The Dispatch Console PC can support a single footswitch with one pedal. The pedal controls the General Transmit
feature.
The footswitch allows users to operate the feature with their feet so their hands are freed for other tasks. If desired,
the footswitch can be permanently fastened to the floor.
Emergency Beacon
The Dispatch Console PC supports an emergency beacon that notifies the dispatcher with colored light when
an emergency call is received.
The Emergency Beacon feature is implemented as the set of green/yellow/red control lights and the buzzer
served by the dedicated application. It is installed on the Dispatch Console PC. The hardware is connected to
the computer via USB.
3-24
Figure 3-17
3-25
System Overview
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.
3-26
The CCGW allows up to 4 conventional channels to be connected to the console dispatch subsystem. At a small
control site (which is a location where users access dispatch consoles and network management terminals) only the
Conventional Channel Gateway function is performed by the Control Site Router. At all other control sites up to
ten CCGWs may be installed.
Figure 3-19
Conventional
Users
Conventional
Channel
Conventional
Channel
Dimetra
Users
Conventional
Dispatch
Patch
CCGW
Site
Tie Lines
MCC7500
Dispatch
Site
Dispatch
Site
SwMI
Dispatch
3-27
System Overview
X-zone
Dispatch PC
CryptR
Audio
Module
Footswitch
SB
Filter
Connector
XLR
XLR
LLR
Sound
Card
Kinesis
USB
IRR
Headset
U
SB
Site Switch
Digital Audio
Adapter
Splitter
Cable
XLR
Microphone
Speakers
3-28
3.4 Radios
Voice Logger
Tape Storage
3.4 Radios
Radios communicate with the RF sites using the TETRA standard. These radios support encryption, authentication,
and interfacing for a data terminal.
MTP3100/MTP3200
3-29
System Overview
Figure 3-22
MTP3150MTP3250
Providing higher power increases range and in-building performance, and so Motorola has added Class 3L (1.8W)
power output option. Taken together with high receive sensitivity this radio has the capability for maintaining
communications in the most demanding situations.
It has an improved operational effectiveness through:
Update your availability and situation using Status Messaging - monitor the progress of job assignments, or
call for support when needed.
Integrated GPS. Knowing where your resources are enables you to allocate tasks based on up-to-date
information (MTP3250 only).
The safety of MTP3000 Series is improved through:
Improved coverage in DMO operation, ensuring that users can communicate over a wider area or in
buildings or built-up areas.
Silent emergency, hitting the emergency button alerts colleagues to critical situations but sends and updates
your location, without showing any indication on the radio screen.
Rugged side connector. This new side connector with the range of available accessories ensures that
connection is maintained even in the most violent of situations.
3-30
MTH800 Portable
The MTH800 features an extensive set of tools designed to enhance the personal safety, security, and efficiency
of both mission-critical and commercial users. Incorporating the latest technologies, it includes support for GPS
Location Services, high-grade encryption, data services and much more enhancing user safety and driving
efficiencies.
Ensuring full customer flexibility, two GPS protocols are supported, including the TETRA Location Information
Protocol (LIP), allowing users to:
Control and reconfigure GPS parameters over-the-air.
Define location and event driven position updates.
Set profiles to enable different location update rules in various scenarios, such as emergency situations.
Ensure that location information is only sent to authorized users through innovative authentication processes.
Compact and lightweight, the MTH800 advanced microprocessor and Digital Signaling Processor (DSP) support
Motorola TETRA innovations including WAP, Multi-Slot Packet Data, Short Data Service (SDS), and Predictive
Text Entry (iTAP). Full End-to-End encryption as well as TEA1, TEA2, or TEA3 air encryption may either be
factory fitted, provisioned in-country or, alternatively, retro-fitted at a later date.
Furthermore, the MTH800 65536color, 130 by 130pixel display provides accurate reproduction of faces and
other images. This high quality delivers maximum image definition in a wide range of lighting conditions. An
intuitive graphical user interface complements the high-resolution display. The interface encompasses a range of
customizable features, including scalable fonts, assignable shortcuts to menu items and features. It also provides
access up to 4000 talkgroups and a unified address book facility that can hold 2000 entries. User safety is further
enhanced with the large, easy to use the emergency button, as well as the programmable rotary knob. The rotary
knob with the push-button operation allows fast access to volume and talkgroup control. The 1 Watt speaker
assures audio quality, as well as a 1 Watt class D audio amplifier, which combines to offer exceptional audio
clarity with minimal distortion. Two microphones are also included a top microphone for dispatcher calls, and a
bottom microphone for one-to-one calls.
3-31
System Overview
MTP850 S
Figure 3-25
MTP850 FuG
Providing higher power increases range and in-building performance, and so Motorola has added Class 3L
(1.8W) power output option. Taken together with high receive sensitivity the MTP850 S/MTP850 FuG maintains
communications in the most demanding situations.
The MTP850 S/MTP850 FuG has an improved operational effectiveness through:
Access to information databases through integrated WAP browser - decide based on the latest information.
3-32
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.
MTP830 S
3-33
System Overview
Figure 3-27
MTP830 FuG
Enlarged rotary knob allows better radio glove-friendly functionality, thus allowing easier control talkgroup
and volume settings.
Operating a radio under protective clothing can be challenging. The MTP830 S/MTP830 FuG can safely
inter-operate with a wide range of specialist audio and push-to-talk equipment.
Man Down detector allows an emergency alert signal to be triggered at your control room when the radio exceeds
preset motion timer and tilt angle thresholds.
The MTP830 S/MTP830 FuG can be configured to send location reports when the emergency button is pressed
helping control room staff coordinate a response more efficiently.
The MTP830 S/MTP830 FuG automatically adjust audio settings based on pre-loaded profiles for detected
accessories. It also enables selecting the best audio profile for different working environments.
The combination of a highly sensitive RF receiver and transmission power that is adjustable to 1.8W provides
extended operational range.
3-34
Figure 3-28
MTP850 Ex
Figure 3-29
MTP810 Ex
The MTP850 Ex/MTP810 Ex ATEX TETRA terminals deliver safe and reliable communications for users with a
powerful set of features to harness the capability of TETRA.
The MTP850 Ex/MTP810 Ex deliver best in class audio performance in the typical noisy environments where
specialist users from industry or public safety operate.
The MTP850 Ex can be used in explosive gas and dust environments due to its high level of protection including
dust Zone 21 and 22.
The MTP810Ex is a low tier solution for use in explosive gas and dust environments dust Zone 22.
Operational safety is further enhanced with a range of features including:
integrated GPS receiver providing the ability to locate personnel, improving user safety and resource
management.
3-35
System Overview
internal Man Down alert - this fully integrated solution triggers an emergency procedure when the carrier of
the radio remains motionless far a set period or falls down.
The simplified keypad with a large button surface makes the MTP850 Ex/MTP810 Ex easy to use with gloves.
Combined with the large scalable display fonts and icons, the MTP850 Ex/MTP810 Ex facilitates operation in
difficult environments with limited visibility.
The integrated WAP browser and Multi-Slot packet data enables rapid access to critical information in the field.
Applications are further enhanced with ability to have simultaneous Short Data Service (SDS) and Multi-Slot
packet data services through the TNP1 protocol.
TCR1000
The Motorola TCR1000 Covert radio is the ideal solution to ensure secure communications in surveillance covert
type operations allowing officers to blend right into the crowd. Motorola TCR1000 Covert TETRA radio delivers
high-quality communication in a light and discrete package for those critical undercover applications.
There are no compromises in the design of the TCR1000. Motorola worked closely with police forces to ensure that
it is intuitive and simple to operate, truly Technology that is Second Nature. The TCR1000 incorporates control
features matched to the needs of officers in covert operations. Its design enables easy hiding inside of light clothing.
A unique portfolio of covert accessories complements the TCR1000 and offer additional flexible options for
undercover officers. This radio operates at 1 watt and the option for a body mounted antenna ensures excellent
coverage and maintains the discreetness of the radio.
A small, easily concealable Remote Control Unit (RCU) controls the radio. The RCU allows the user to answer
or to initiate calls, change talkgroups, and volume. It also allows using special surveillance features such as
whisper mode or communication tones (like PTT Double Push feature). A connector is provided on the RCU to
attach a remote PTT unit.
3-36
Figure 3-31
MTM800 Enhanced
Developed for organizations where rugged and versatile mobile terminals are essential, Motorola MTM800
Enhanced is ideal for use where the application, location and/or circumstances demand fast, reliable, no-nonsense
solutions.
Ease-of-operation in the most demanding situations unsurpassed audio quality, intuitive keypad, and
high-definition, color display combined with a sleek yet durable design.
Dust and water resistant to IP 54. rain, salt, fog, and dust protection tested to MIL 810 C/D/E/F for the
standard control head.
Motorcycle control head rated IP67 for dust and water resistance
The MTM800 Enhanced also supports the full suite of TETRA security functions, including air interface encryption,
and End-to-End encryption. Users can request assistance by simply hitting the emergency button, which not only
alerts colleagues to critical situations, but also sends an update dispatch on the user location. The radio is able to
switch to covert mode at a press of a button. The radio has an integrated GPS receiver that enables users to locate
their mobiles, and provides location-based services and mapping capabilities.
The radio offers various installation possibilities from typical Dashboard installation to Dual Control Head
installation using an additional junction box. Currently the following options are supported:
Trunnion Installation
Dashboard Installation
Desktop Installation
Remote Mount Installation
Motorcycle Installation
Dual Control Head Installation
Data Box Radio Installation
3-37
System Overview
Figure 3-33
TSCH
MTM5500MTM800 FuG ET in Mixed Dual Control Head Configuration with eCH and
With its best in class RF sensitivity and 10 W transmit power capability, the MTM5400/MTM5500MTM800
FuG/MTM800 FuG ET Series set a new benchmark for TETRA RF performance.
The MTM5400/MTM5500MTM800 FuG ET Series support multiple modes of operation that enable enhanced
workflow management and improved communications in areas where network coverage is weak or unpredictable.
The integrated DMO Repeater is Type 1A compliant, operating on just a single RF carrier for efficient spectrum
usage.
The MTM5400/MTM5500MTM800 FuG ET Series feature an integrated gateway that connects users operating in
Direct Mode with control room staff and other colleagues on the trunked radio network. A comprehensive set of
gateway services is supported, including configurable handling of individual and group calls.
Advanced Remote Terminal Management enabled through software, this ground-breaking capability allows the
MTM5x00MTM800 FuG/MTM800 FuG ET Series to stay live while being programmed and software upgraded.
This feature works to maximize productivity and eliminate radio downtime.
The MTM5200/MTM5400MTM800 FuG mobile offers comprehensive and flexible installation options. The
radio is fully DIN-A compatible and supports a wide range of configurations including customized multiple
control head, desk, and motorcycle install variants.
Do not connect MTM5200, MTM5400, and MTM800 FuG Control Heads to the Enhanced (Ethernet)
MTM5500, MTM800 Fug ET radio (and the other way around). Even though mechanically possible,
it is incorrect and will result in hardware malfunction (broken transceiver).
3-38
Use proper Ethernet cables to connect Ethernet Expansion Head with TSCH and eCH. Transceiver
can be broken if not connected properly.
MTM5500MTM800 FuG ET
Expansion Head
Options
Control Head
Options
Remote Ethernet
Control Head (eCH)
Telephone Style
Control Head (TSCH)
3-39
System Overview
3-40
4-1
System Overview
4-2
4-3
System Overview
Table 4-1
Database
Server
Function
UCS Database
Zone Database
RCM Database
Zone Controller
Affiliation Database
4-4
Table 4-2
Cluster-Level Servers
Zone-Level Servers
10
TNPS
UCS
10
10
16
UEM
10
10
15
ZDS
11
12
10
17
AUC
SSS
10
10
19
10
Dispatch
Consoles
CCGW
ATR
ZSS
8
7
14
Client PCs
ZC
18
10
BTS
13
NTS
4-5
System Overview
Table 4-3
Server Interactions
Interaction
4-6
Description
Radio (subset of UCS database) and infrastructure database export from the ZDS
to the Zone Controller. The Zone Controller saves this information in its Local
Database, and uses the information to create the home location register (HLR) for
the zone. Diagnostic and fault information, including fault information proxied
for other devices, are sent through this link to the ZDS.
Raw call traffic information is passed from the ZC to the ATR which formats the
information and generates the Air Traffic Information Access (ATIA) stream.
The ATR generates an ATIA Log, which contains records of the call processing
information that are made available to the ATR. RCM information is passed
from the ATR to the ZC.
Zone statistical data is sent from the ATR to the ZSS to compile statistical
information on a per zone perspective.
Zone statistical data is sent from each ATR, within the cluster, to the SSS to
compile statistical information on a per cluster perspective.
Site statistical data is sent from the BTS to the ZSS to compile statistical
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
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
information is passed between the Zone Controller and the dispatch console.
Call requests, channel assignments, call terminations, and other call processing
information is passed between the Zone Controller and the CCGW.
10
Unified Event Manager derives its listing of system objects from data received
from other boxes. Device status information is derived from Simple Network
Management Protocol (SNMP) agents.
11
The Zone Database Server sends any new or changed configuration information
to the dispatch console. Fault information is sent from the consoles to the ZDS.
12
13
The Network Time Server (NTS) is periodically polled for a time reference
packet from other servers and network components.
Table 4-3
Description
Each client workstation runs the Private Radio Network Management (PRNM)
Suite of applications. The following list shows the servers that support PRNM
Suite applications:
UCS - User Configuration Manager, Zone Configuration Manager
ZSS - Zone Historical Reports
14
15
16
17
Distribution of the authentication keys and encryption keys from AuC to the
Zone Controller.
18
19
4-7
5-1
System Overview
Parameters that affect the operations of all radios in the system, such as site access denial, are also entered in
the UCM.
The radios through their specific programming software.
Static configuration information may be divided into four parts:
Home Zone assignment for individual and talkgroup IDs
Identification numbers and aliases for both individuals and talkgroups
Call services and system features allowed for that individual or talkgroup
Valid site settings for each individual and talkgroup
Valid site settings, in conjunction with the Site Access Denial setting (see 5.1.2 Infrastructure
Configuration, page 5-7) play an important role in mobility management when a radio attempts to
register or a group member attempts to register to a site.
The static user configuration information is referenced by the system each time a radio attempts to register to a site
and/or affiliate with a talkgroup.
Configuration information must be consistent when programming the UCS should be consistent with the
configuration information in the radios.
Default access allows all radio users and talkgroups to access the system with a predefined set of
permissions. Individual control of radio users and talkgroups is not possible. This mode of operation is not
recommended for use under normal operating conditions.
The zone object in the Zone Configuration Manager (ZCM) configures and manages the attributes relating to a
specific zone. The Zone Controllers use these parameters to allocate resources. The zone object configuration
information is replicated from the Zone Database Server (ZDS) to the User Configuration Server (UCS).
Two of the fields in the zone object record determine whether radios are allowed to access the system only if they
have a record in the UCS, or whether they can access the system under default conditions using a default record.
The fields are called Individual Default Access Permission and Talkgroup Default Access Permission.
5-2
5-3
System Overview
Figure 5-1
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-4
Table 5-1
ID Type
ID Range
Description
System
Individual or
Group
1 to 13.999.999
Alias
14.000.000 to
14.999.999
Alias or Fleet
15.000.000 to
15.999.999
System
16.000.000 to
16.777.215
5.1.1.6 Profiles
A profile is a master list of common attributes or capabilities used by radio users, talkgroups, and multigroups.
Creating a profile allows you to enter the information one time and reference the profile from an individual record.
One does not have to enter the information separately into each record. You can create a different profile for each
type of function and group of users in your system, up to a maximum of 2000 profiles.
Using a profile helps to reduce the amount of data that has to flow through the network between the UCM and the
Zone Controller. Profile information includes data that relates to radios, radio users, and talkgroups who perform
the same function. For example, all radio users associated with the Fire Department require the same resources, so
you can use a profile to create a master file for their records.
A record can have a one-to-one relationship with a profile (up to the 2000 profile limit), or many records can
be mapped to the same profile.
5-5
System Overview
You can use a Radio User Capabilities Profile object to define a set of parameters that are common to a specific
group of radio users. Every radio user is assigned a Radio User Capabilities Profile.
5.1.1.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-6
5.1.1.12 Multigroup
The Multigroup object is used to create records that identify a group of talkgroups that are the target of multigroup
announcements.
5-7
System Overview
The type of rejection depends on the valid sites set for each radio and affiliated talkgroup in the corresponding
UCM records. For example, with a site access denial setting of BOTH, if you have a Radio User that is valid at the
site but a talkgroup that is not valid, the radio is allowed to register and stay at the site. The radio is allowed to
make unit-to-unit calls but requests for a talkgroup call are rejected.
Continuing this example, if the mobile user switches to another talkgroup, the radio unit sends another affiliation
request, which is accepted or denied based upon the valid site setting for that group. If it is a valid group, the system
begins to provide both group and individual call services at that site.
Valid site and site access denial are the means by which a system manager can specifically control the operating
sites and individual/talkgroup services for each radio.
System engineers create the new Source Site ACC record when configuring the system initially.
Subsequent users can only open and modify the existing record. You must consider the ramifications
when changing the initial configuration.
In large systems, the radio codeplug may not contain all of the frequencies for adjacent sites to which the radio
may need to roam. Additionally, new sites may be added to the system and it may be impractical to bring all of
the radios in for reprogramming.
Selection and programming of the adjacent sites lists requires detailed knowledge of the systems coverage
characteristics. Random selection of sites can severely impact system operation as radios may experience
problems accessing the system.
5-8
5-9
System Overview
Figure 5-2
UCS
ZDS
ZDS
Zone
Controlle r
IHLR
Zone
Controlle r
IHLR
GHLR
GHLR
Zone 1
Zone 2
The HLR stores access configuration information for both individuals and groups along with the current site
location of the individual or group member. The VLR is a temporary copy that is placed in the zone where the
radio is also present, and is deleted when the radio is shown up in another zone. When a radio is shown up in
another zone, a new VLR is created again.
There are two VLRs - one for individuals and one for groups. The individual VLR stores the access
configuration information and current site location for each registered individual radio unit in the zone.
The group VLR stores the access configuration information for a group that has affiliated members in the
zone along with the site location of each affiliated member.
Figure 5-3
UCS
ZDS
ZDS
Zone
Controlle r
IHLR
IVLR
Zone
Controlle r
IHLR
IVLR
GHLR
GVLR
Zone 1
5-10
GHLR
GVLR
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.
5-11
System Overview
5-12
Figure 5-4
Dispatch
Console
Gateway
Router
Zone
Controller
LAN Switch
Core
Router
BTS
Patch Panel
BTS
5-13
System Overview
Dispatch
Console
Gateway
Router
Zone
Controller
LAN Switch
Core
Router
BTS
Patch Panel
BTS
Process Steps
1
Routing information is sent to the appropriate MSO and remote site routing equipment.
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.
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.
The sites cause the activation of the receive and transmit circuits in the designated traffic channels.
The receiving radios tune to the assigned traffic channel at their respective sites.
5-14
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.
The audio signal is transmitted by the radio over the assigned frequency to the caller's site and received by the
assigned traffic channel.
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.
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.
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.
If a person responds to the initial caller, by pressing the PTT button within the hang timer period, the call
continues. The message hang timer is reset and the new speaker's audio is routed as the source audio using
the traffic channels and router assignments already allotted for this call.
5-15
System Overview
Zone 1
Zone 2
Dispatch
Console
Gateway
Router
Zone
Controller
LAN Switch
Core
Router
BTS
Gateway
Router
Zone
Controller
LAN Switch
Exit
Router
Patch Panel
Exit
Router
Core
Router
BTS
5-16
Notifies the consoles of the talkgroup call and its audio source, if needed. The Zone Controller relays the
audio assignments and the channel assignments to the appropriate remote sites through their site control
paths.
Once the resources are assigned, the rendezvous point router becomes the centre of control for audio
distribution.
At each site the Site Controller:
Activates the site assigned as the traffic channel.
Sends the traffic channel assignment to the affiliated radios over the control channel.
The assigned traffic channel at RF sites send a join message to the RP after they receive the multicast address.
As resources are set up in each zone, the radios in the talkgroup in each zone switch to the assigned traffic
channel. The initiating user's radio activates the transmit circuitry and begins sending the audio to the receiver
at the assigned traffic channel.
5-17
System Overview
home zone HLR to the HLR in the new zone and from there to its VLR, the call request validated in the new
zone, and a channel assigned and activated at the new site.
If resources are not available at the site or in the zone, the call continuation request to the new zone is
placed in its busy queue. When the needed resources become available, the roaming user rejoins the call in
process. A longer loss of audio occurs in this case.
The multigroup and all talkgroups in the multigroup must have the same home zone assignment.
All call requests in the busy queue for the affected radios are dropped.
Multigroup information is programmed in two places:
One Multigroup per personality can be programmed in the radios.
Multigroup records must be created in the UCM database identifying the Multigroup itself as well as the
individual talkgroups associated with that Multigroup.
A radio unit with the selector in the Multigroup mode position can monitor talkgroup activity for talkgroups
associated with the selected multigroup if and only if the monitored talkgroups have an affiliated member in the
same zone as the monitoring radio. The system does not pass audio between zones exclusively for a unit that is
scanning talkgroup activity while in multigroup mode.
5-18
5-19
System Overview
A value of 3660 disables the message timer for emergency calls. Radio Users have unlimited time between
PTTs.
A console operator can initiate an emergency call on any talkgroup or multigroup being monitored. The system
handles a console emergency call request the same as a radio-generated request, with one exception: a console
generated emergency call has an unlimited hang time, so the call stays active until the operator knocks down the
emergency call at the operator position.
Emergency calls initiated from the console are always processed in Ruthless Preemption mode when
resources are not available to grant the call immediately.
5-20
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.
Private Call
Gateway
Router
Zone
Controller
LAN Switch
Core
Router
BTS
Patch Panel
BTS
A private call begins with a call request. The call request resolution determines whether the call is set up or not.
Requests are rejected if the target radio does not respond to the request or if the target radio is not registered with
the system. Other reasons for a call to be rejected would be configuration-related (one of the radios blocked from
private calls, site not allowed, and so on).
5-21
System Overview
Process Steps
1
A private call request is initiated when the caller selects the appropriate mode on the radio, and then enters the
target radio's ID or selects it from a list.
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.
The Zone Controller receiving the call request checks its VLR to see if the requesting individual is configured to
make private calls.
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.
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).
Once the target radio's current zone is known, the receiving Zone Controller sends the call request to the
Zone Controller in that zone.
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.
If the target radio is not registered with the system, the requester receives a call reject. Otherwise, the requester
hears a ringing tone. If the target radio does not respond within the time-out period, the call request is ended.
10 If the target radio responds to the call request, the private call is set up.
5-22
Process Steps
1
Audio is received by the assigned traffic channel at the local site and is routed to the RP at the zone.
The RP routes the audio packets through the exit routers where they get encapsulated as Frame Relay packets
for transmission to the participating sites.
When the target user responds, the same path is used, but the source and destination of the audio are swapped.
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.
5-23
System Overview
To PABX
Figure 5-8
Dispatch
Console
MTIG-E1
Zone
Controller
Gateway
Router
EC
LAN Switch
Core
Router
Patch
Panel
BTS
The telephone interconnect feature builds upon all of the configuration and infrastructure discussed up to this point.
With talkgroup calls and unit-to-unit calls, all parties to the conversations all reside somewhere on the Dimetra
IP system.
For telephone interconnect calls, one of the parties is outside of the Dimetra IP system and is connected through
landline telephone to the radios in the system.
The Dimetra IP system supports radio-to-landline and landline-to-radio interconnect calls. It does not
support interconnect calls to and from talkgroups.
5-24
5.5.2.2 Configuration
5.5.2.2 Configuration
Radios must be properly programmed to make and receive telephone interconnect calls.
5-25
System Overview
Call Setup
When and where to use:
This process describes the events that occur during the setup of a successful radio-to-landline call.
5-26
Process Steps
1
The radio user initiates a telephone interconnect call according to how this is done on the specific type of radio.
The radio sends a telephone interconnect service call request over the control channel with the dialed digits
information.
The system verifies that the radio is authorized for telephone interconnect service.
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.
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.
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.
The MTIG and sites send a join message to the RP for the assigned multicast addresses.
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.
5-27
System Overview
5-28
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.
Gateway
Router
Data Gateway
(SDR)
LAN Switch
Core
Router
BTS
Patch Panel
LAN Switch
Exit
Router
Exit
Router
Core
Router
BTS
5-29
System Overview
Process Steps
1
The radio, remote data terminal, or host creates a message, selects the Short Subscriber Identity (SSI) of
the recipient, and sends the message. If a radio is sending the short data message, the message is delivered
over the control channel.
The short data message is delivered to the short data router (SDR) within the cluster.
The SDR observes the SSI for the recipient of the message and checks the IHLR/VHLR information to
determine where the recipient is located.
The SDR routes the short data message across the network to the intended recipient (host or radio).
5-30
5.7.1 Authentication
5.7.1 Authentication
Authentication is used to verify that a radio accessing the system is valid, and to reject any unauthorized parties
from accessing the system. The Dimetra IP system uses a challenge-response-result protocol to authenticate both
the radio and the infrastructure.
The authentication process begins with the infrastructure sending a challenge to the radio. The radio calculates a
response based on the challenge, and sends the response to the infrastructure. If the response from the radio
equals the expected response by the infrastructure, then the infrastructure indicates that the authentication result is
successful and grants access to the system. If the response is not correct, then the infrastructure indicates that the
authentication result has failed and rejects access to the system.
Figure 5-10
Authentication
When the radio provides the response described above, and the radio supports mutual authentication, the radio
also provides a challenge to the infrastructure. The infrastructure generates a calculated response to the radio to
verify that it is genuine. If the infrastructure's result matches the result expected by the radio, then the radio
indicates that the authentication result is successful to the infrastructure. On receipt of this successful indication, the
infrastructure grants access to the system.
5-31
System Overview
Figure 5-11
Encryption of Traffic
MAC He a de r
Cle a r P a yloa d
Ke y
Offs e t
MAC He a de r
Encryption Algorithm
Encrypte d P a yloa d
Security Classes
Class
Authentication
OTAR
SCK
Encryption
CCK/DCK
Encryption
GCK
Enable/Disable
O (see note 3)
O
O
O
M (see note 1)
M (see note 2)
3G
M (see note 1)
M (see note 2)
M = Mandatory
O = Optional
- = Does not apply
= Recommended
NOTE 1: Authentication is required for generation of DCK.
NOTE 2: OTAR for CCK is mandatory, for other keys management OTAR mechanism is optional.
NOTE 3: Required if key material is either distributed in preparation for security class transition, or during
cell reselection to a cell of a different security class.
5-32
5-33
System Overview
5.8.2.1 AllStart
An AllStart setting for a group indicates that all the available resources for the call must be present for the call to
start. An AllStart call requires the following resources before a call is granted:
A traffic channel at all sites that have affiliated group members.
All affiliated consoles and logging recorders to support console calls.
Encryption resources at the console interface if the call is secure.
A traffic channel at all critical sites. Critical sites for a talkgroup are designated in the TG/MG Site Access
Profile record available in the UCM.
5-34
5.8.2.2 FastStart
If any of the above conditions are not met, the call is placed in the busy queue.
5.8.2.2 FastStart
A FastStart setting for a group call indicates that only mandatory resources (that is, critical sites, critical resources
and requested sites) are required to grant a call. Any other resources available at the time the call is set up are also
included in the call. In FastStart, not all affiliated members in a talkgroup must have a channel available in order
for a call to start. FastStart requires the following resources before a call is granted:
A traffic channel at the site of the requestor.
All affiliated consoles and logging recorders to support console calls.
Encryption resources at the console/ICCS interface if the call is secure.
Encryption resources at the console interface if the call is secure.
A traffic channel at all critical sites.
When a group call is busied, the priority that is assigned to the call in the queue is determined by the higher
of the individual priority of the talkgroup or the requestor. For example, if the talkgroup is priority 8 and
the requestor is priority 5, then the call is queued with priority 5.
If any of the above conditions are not met, the call is placed in the busy queue.
When a private call is busied, the priority that is assigned to the call in the queue is determined by the
better of the target or individual priority of the requestor. For example, if the target's priority is 8 and the
priority of the requestor is 5, then the call is queued with priority 5.
Private calls can have a priority level assigned that determines how the call request is serviced in the busy queue,
the higher the priority, the sooner the call gets serviced.
5-35
System Overview
When a radio has been rejected from using a particular service, the Zone Controller sends an abort message to any
resources that need to be released from the service, then sends a reject message to the radio. The following items
are typical reasons why a radio may be rejected during registration or during a call request.
The radio may be sending an individual ID or talkgroup ID that is not loaded in the memory of the Zone
Controller.
The radio may be requesting a service that is restricted or not available to the particular radio.
The system or the receiving radios may not support the call type requested by the initiating radio.
The system may be in a failure situation. Depending on the settings and the situation, the sites may be
in local site trunking and only allow certain types of calls, or the Zone Controller may be using default
access permissions.
The radio may be calling an individual or talkgroup that does not exist or that is not registered with the
system.
The radio may not be configured to make the requested type of call.
For talkgroup calls, a console that should be attached to the call may not able to participate in the call.
The radio is not operating at one of its valid sites.
The zone is not able to communicate with the home zone of the initiating radio.
The zone is not in interzone trunking with the other zones that need to participate in the call. The particular
resources may not be available for the call.
Generally, a service state for a site other than wide area trunking causes the radios at the affected site to
attempt to register at a site that is in wide area trunking mode.
5-36
Table 5-3
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 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.
Service Level
Description
Full Interzone
All zones are in a state of interzone trunking with respect to the home zone of the group.
Reduced Interzone
At least one participating zone is in interzone trunking with the home zone of the group,
and at least one zone is not.
Zone Isolated
The current zone may only process the calls of the group locally within the zone. This
occurs when either the participating zones have no interzone trunking with the home zone
of the group, or when the home zone loses interzone trunking with all the other zones in
the system. In such case the routers establish an alternate IP path.
5-37
System Overview
The three levels of group service availability are based on the perspective of a group member from the current zone
to every other zone in the system, and whether the current zone is the assigned home zone of the group.
5.9.2.1.1 Example 1
It is possible for some members of a talkgroup to have zone isolated service for a short interval during loss of
the links between the zones (generally microwave).
In the figure, the link between Zone 1 and Zone 3 is down (interruption of interzone trunking), while the
links between Zones 1 and 2, and between Zones 2 and 3, are intact.
The home zone of the talkgroup A is Zone 1.
A user in Talkgroup A placing a call in Zone 1 or Zone 2 has full interzone service availability.
Talkgroup A members in Zone 3 have zone isolated group service availability for a short period of time
while the master site routers reestablish the call through an alternate IP path, in this case, through Zone 2.
Figure 5-12
5-38
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
5.9.2.2.3 Example 2
In a less commonly occurring example:
User 1 is in Zone 1 but its individual home zone is Zone 4.
User 2 is in Zone 2 but its individual home zone is in Zone 3.
To make an interzone individual call between User 1 and User 2 (See the figure below), the following conditions
must exist:
Zone 1 and Zone 2 must be in interzone trunking.
Zone 1 must have at least an Interzone Control Path to Zone 3.
Zone 2 must have at least an Interzone Control Path to Zone 4.
5-39
System Overview
Figure 5-14
5-40
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.
5-41
System Overview
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
5-42
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.
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.
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.
All active wide area calls are ended including Talkgroup, Multigroup, Interconnect, Private, and Emergency.
BTS sites revert to local site trunking mode.
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.
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.
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).
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.
Call Type
Possible Disruptions
Private Calls/Telephone
Interconnect Calls
Calls to a target radios whose affiliation is not yet known to the controller
are not successful.
Talkgroup/Announcement Calls
5-43
System Overview
Some radios can be registered at more than one site during controller switchover. Multiple registrations
can occur if a radio happens to register to a new site while the radio is also searching the adjacent site list
for a wide-area site. Because connectivity to the controller is temporarily lost during controller switchover,
entries in some of the site registration tables do not get updated to reflect radios who have changed sites.
Normally the controller de-registers radios when they roam out of a site, however, during a controller
switchover the communications path from the controller to the site is temporarily unavailable preventing
the controller from performing deregistration.
The site transitions to wide area trunking mode when the site reestablishes a link with the controller. The site then
notifies the radios of the change through System Status OSP.
The wide area feature called Dynamic Site Assignment requires that the controller have up-to-date affiliation
tables. All sites need to upload the affiliation tables to the controller. After the controller receives all of the
uploads from the sites, it looks through the compiled affiliation table for radios that are registered on more than one
site. If the controller finds duplicate affiliations it requests, through all sites where the radio shows registrations,
that the radio reregister. This must happen before Dynamic Site Assignment can guarantee all intended parties
are included in the call.
The length of time it takes to update the affiliation tables depends on the number of sites, radios, and talkgroups
in the system, but in general it should be less than twenty minutes from the time the first site transitions back to
wide area trunking.
As with radios, console affiliations must also be sent to the controller within the zone. This happens within the fist
few minutes after the switchover occurs.
For a given talkgroup to be monitored by the dispatch subsystem, at lease one console affiliation must be received
for that talkgroup.
Do not switch back to the standby controller until the Infrastructure database has been downloaded from
the Zone Database Server (ZDS) or the system remains in local site trunking until the Infrastructure
database has been downloaded. The download time varies by system configuration, but in general should
take less than 10 minutes.
If for some reason the newly active controller is not functioning properly, you may need to switch the standby
controller back to active. This is considered a double switchover. The following is a description of what occurs
when performing a double switchover before the standby controller has received the user configuration database
from the ZDS.
5-44
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.
5-45
6-1
System Overview
Semi-duplex transmission means that only one user can transmit traffic in a call at any time. This is the characteristic
mode for private calls in a PMR/PAMR system. Full-duplex transmission means that each user can transmit and
receive traffic (talk and listen) at the same time. Telephone Interconnect calls are always full-duplex, so duplex
individual calls appear to the user to be similar to telephone calls. The full duplex individual call service allows two
parties in a TETRA system to communicate using full-duplex speech in three different ways:
Radio to console: (This call is initiated by an radio to a dispatch console)
Console to radio: (This call is initiated by a dispatch console to a radio)
Radio to radio: (This call is initiated by one radio to another radio)
6-2
The system can also be configured so the RCM or Console acknowledges the Emergency Alarm.
6-3
System Overview
6-4
The system provides 10 levels of priority where level 1 is the highest and reserved for emergency group calls. The
NM assigns levels 2-10 to individuals and talkgroups. The priority assigned to a group call is the individual priority
of the calling party or the group priority, whichever is the higher. The priority level is used in the case where a
system is busy and calls are queued. When the systems get busy, calls with higher priority are allocated traffic
channels before calls with lower priority.
6-5
System Overview
6-6
In addition, any emergency call signaling is also sent on all the traffic channels at the sites where the emergency
call is being set up.
6-7
System Overview
6-8
For further information on the voice logging system, turn to the MCC 7500 Dispatch Consoles Subsystem
manual.
6-9
System Overview
Redundant components can be added to other parts of the infrastructure for instance to ensure traffic
of short data massages.
Furthermore, the system offers the possibility of geographical redundancy. With geographical redundancy the
functioning and its redundant counterpart are placed in two different locations. This can be done to avoid physical
damage to the system that impacts both the functioning and the redundant component.
Figure 6-1
Geographical Location 2
To PABX/PSTN
EC
MTIG-IP
EC
MTIG1
Primary
Zone
Server
00000
0000
Border
Rouer
Patch
Panel
0000
Patch
Panel
0000
KMF
VPN
Router
00000
00000
Core Gateway/
Exit Router(s)
VPN
Router
0000
Border
Rouer
0000
00000
0000
00000
0
00000
GGSN
EAuC
0000
Secondary
Zone Server
Fiber
0000
PDR
00000
00000
0000
NTS
SDR2
0000
MTIG1
SDR1
MTIG-IP
RNG
To PABX/PSTN
CEN
00000
00000
CEN
Bas e Stations
Control Rooms
Other Zones
0
Bas e Stations
Control Rooms
Other Zones
Transport Element
Application Element
Mutualy Exclusive
00
Local Gateway Trunking is a disaster recovery feature designed to provide local resource functionality in the event
of an MSO failure or a link failure between the base station and the MSO.
In the event of an MSO or link failure the local MTS and console are able to connect to a local Dimetra IP
Micro/LiTE system and provide full voice and short data functionality within the local coverage area of the
Dimetra IP system.
6-10
6-11
System Overview
6-12
Priority Level
Audio Source
Radio Transmit
6-13
System Overview
6-14
A Private call may be added to a Console Patch by first setting up the Private call, and then adding it to the patch
configuration.
6-15
System Overview
If enabled, dispatch console operators can make limited changes to the configuration of their dispatch console (such
as adding resources). These changes are temporary and are lost when the user logs out. Permanent changes to
configurations can only be made using Elite Admin.
Ethernet DSS can connect to E1 DIPS only after adding Ethernet Exit Routers to the DIPS zone. An E1
DSS cannot connect to an Ethernet DIPS because the Ethernet DIPS cannot support E1 Exit Routers and
the E1 DSS cannot support Ethernet Exit Routers.
6-16
The features specific to Dimetra IP 8.1, like Object Call or BIC/BOC, are not available in such hybrid
systems.
6-17
7-1
System Overview
7.2 Serviceability
Serviceability for a Dimetra system, at the MSO, is the capability to provide maintenance of the equipment either
locally from a service terminal or remotely through modems or remote LAN connections. To facilitate service
to the remote sites Dimetra BTS (Base Transceiver Station) Service Software (TESS) is available as a remote
terminal (only from within the RNI) so many maintenance functions regarding the BTS sites can be done remotely
via VPN Gateway.
This clause describes the architecture by which the service organizations and other support functions can get
access to elements in a Dimetra system. The maintenance procedures and functions such as fault and performance
management are described in more detail in 7.6.2 Private Radio Network Management Suite Applications,
page 7-16.
7-2
7-3
System Overview
ZoneWatch - (1) A Windows application that monitors trunking activity and radio call traffic for an
individual zone in real time. This application is part of the Private Network Management Suite. (2) A
Motorola software application that allows users to monitor activity within a zone
Affiliation Display - Affiliation Display is a Private Radio Network Management (PRNM) Suite
management application that monitors how radio users travel between different sites in a zone and how
they communicate with other members of their assigned talkgroup or even with members outside of their
talkgroup within a particular zone.
Air Traffic Information Access (ATIA) Log Viewer - Data packets that contain talkgroup registration and
site registration and deaffiliation/deregistration information for each radio user in a particular zone. The
Air Traffic Router (ATR) collects this radio traffic information from the Zone Controller and broadcasts an
information stream of these packets on the network.
Dynamic Reports - An application intended for short term monitoring. The display provides zone-level,
real-time charts that illustrate channel utilization for all call types group, private, interconnect, control
channels, and dynamically blocked calls.
Historical Reports - A management application producing reports on radio infrastructure and radio
resource usage within an identified zone.
Fault Manager using Unified Event Manager - The Dimetra IP fault management application. Unified
Event Manager identifies problems rapidly and provides functions and tools for notifying support personnel,
tracking, diagnosing, and correcting faults. It also maintains a data warehouse, storing up to 30 days
of event history.
Radio Control Manager (RCM) - A management application used to issue commands to radios and
monitor events from radios. The Radio Control Manager (RCM) is part of the Motorola PRNM Suite.
Radio Control Manager Reports - The application provides reports of two types of functions of the RCM:
radio commands initiated and radio events displayed.
These applications input to or extract information from one or more of the NM servers where system configuration
parameters are stored, transactional statistics are accumulated, real-time data streams are sourced, and supporting
processes are performed. In addition to these user applications, the NM servers also run several autonomous
processes in the background to support the ongoing operation of the system. Applications and processes are
described later.
7-4
7-5
System Overview
7-6
7-7
System Overview
7-8
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.
7-9
System Overview
The Affiliation Display provides a dynamic view of the sites to which all operating units are currently registered,
displaying zone, site, and talkgroup details. This feature makes it easy to track and troubleshoot radios in the
system. Affiliation Display is not a vehicle or unit locator in an absolute sense; registration only suggests the area in
which the unit may currently be operating based on the last registration of the unit and the radio coverage of the site.
The focus of the Affiliation Display can be on an individual site, a specific talkgroup, or an individual radio.
Graphing capabilities are also included.
7-10
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.
Security Feature
Purpose
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.
7-11
System Overview
Multizone fault management can also be arranged through the forwarding of events to a central customer-supplied
fault management system. This central fault management system can receive the forwarded traps from all
zone-level Unified Event Manager servers in the system. The figure below illustrates the event forwarding from
each zone Unified Event Manager server to a customer-supplied fault management platform.
Figure 7-2 Multizone Fault Management- Event Forwarding to a Customer-Supplied Fault
Management System
7-12
7-13
System Overview
Figure 7-3
Cluster
Zone
Site
Unit
The table lists the Motorola PRNM Suite applications. These management applications are available through
Application Launcher.
Table 7-2
Applications
FCAPS
Purpose
Application Launcher
N/A
Software Download
System Profile
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.
CS
Affiliation Display
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
Cluster-Level Applications:
Zone-Level Applications:
7-14
Table 7-2
Applications
FCAPS
FPS
The primary fault management tool that you can use to monitor
the status of the system. Unified Event Manager spans system
and zone-level activity in the figure above.
Historical Reports
AP
AP
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 Profile
ZoneWatch
FP
Purpose
Application
FCAPS
Purpose
CF
A tool used to configure and service the Site Controllers and BTS base
radios.
Customer Programming
Software (CPS)
A tool that programs radios. You can also use it to learn the operating
parameters, personalities, and modes of radios. This software is
documented in the CPS application for your radio. The CPS Online
Help is available from the Help menu.
7-15
System Overview
7-16
You must first enable ATIA data logging through the ATR server's Administration menu. Otherwise, no
ATIA log data is collected for viewing.
The ATIA Log Viewer is a technician tool that allows you to examine air traffic historical data in a specified zone
for one or more particular time intervals. You can also do the following:
View the radio events occurring in a zone. The information is the same as what you view from ZoneWatch,
but is presented in a raw data format from the ATR server. Shows active sites, channel numbers, and
radio affiliations.
View a log of what occurs on an hourly interval in the zone.
The ATIA Log Viewer allows you to examine historical air traffic data in a specified zone for a particular time
interval or intervals. This feature is normally used to examine data logs when debugging the system. The ATIA Log
Viewer records the last 25 hours of ATIA data packets on the ATR server. The data is displayed on an hourly basis,
and you can select which interval packets you want to view.
The data is displayed in an easy-to-read format and can be printed or saved for future evaluation. Since the
information displayed in the ATIA Log Viewer is a text document, you can format the information, if required
using a third-party application.
7-17
System Overview
The Custom Historical Report features apply only to Historical Reports and not to Dynamic Reports.
Custom Historical Reports has the following features:
The Report Expert wizard from Crystal Report allows you to select from parameters collected by the
ATIA stream or other reports.
Reports may be customized to suit your individual needs. Customization includes:
Group and sorting
Charts (bar, line, 3-D)
Top and bottom X filtering
Calculated values
Cross tab, form, form letter, drill-down reports
Special formulas can be included in Custom Historical Reports to create certain effects.
7-18
Unified Event Manager allows you to monitor the status of components at zone level, such as servers, Zone
Controllers or sites in the zone.
The zone level submap displays only one zone.
Unified Event Manager is the primary troubleshooting tool that allows you to view alarm information. You use
Unified Event Manager to monitor the status of devices in the zone.
Submap views show the status of devices by color and the graphical representations of alarm information.
Alarm Categories show different categories of alarms, for the radio system, routers, or other devices.
Alarms Browsers show a record of what devices are sending alarms or events.
Unified Event Manager communicates with managed RF system devices using Simple Network Management
Protocol (SNMP), the industry standard communication protocol.
Unified Event Manager integrates the fault management of Motorola devices and that of approved third-party
devices.
7-19
System Overview
All monitoring displays are updated in near real-time as the information becomes available in the system.
7-20
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-21
System Overview
Table 7-4
Object Types
Description
System Configuration
Radios
Security
ZoneWatch Configuration
External Configuration
Registration and configuration of all zones, BTS sites and call routes that have been
configured in other clusters of the system. Not applicable to single-cluster systems.
7-22
Object Types
Description
Zone
Configures the ATR server, which collect statistics on the system and distributes
airtime usage data.
Zone Controller
Represents the Zone Controller for the zone. Provides access to the Rendezvous
Point (RP) routers.
Level of Service
Configures the level of service availability for call requests, such as the number of
interconnect calls allowed or the average maximum busy delay that is acceptable for
group calls or interconnect calls.
Table 7-5
Description
Application Platform
Configures the application platform, which hosts the MTIG application. Provides
access to the MTIG object as well as the voice and line card related objects.
Console Site
BTS Site
Configures the BTS site operations within a zone, setting the parameters for a site so
that it functions correctly in the system.
Switch
Configures the switch within a zone, plus the paths, slots, and cards, and connections
for the switch.
Interconnect Subsystem
References the telephone interconnect equipment in the zone and represents the path
selection for telephone interconnect calls.
7.6.2.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.
7-23
System Overview
Raw Data A Raw Data filter allows the selection or exclusion of information. The data that is selected for
inclusion is displayed as raw data (no formatting).
Site Information A site filter object allows you to specify the site that the ZoneWatch user wants to
monitor. The site selection must consist of a site within the same zone as the ZoneWatch. The site filter
essentially limits the view to only a specific site in a zone. You can, however, have other windows open
to show information from other sites in the zone.
7-24
Document Title
Description
Glossary
Documentation Overview
System Overview
Zone Controller
S6000 Router
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
A-1
System Overview
Table A-1
(cont'd.)
Document Title
Description
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
Network Management
Servers
Network Management
Client
Remote Access
A-2
Table A-1
(cont'd.)
Document Title
Description
Server Software
Restoration
Server Hardware
Restoration
Stand-alone Components
Restoration
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
A-3
System Overview
Table A-1
(cont'd.)
Document Title
Description
MTS 1 Restoration
EBTS Restoration
Fault Management
ZoneWatch
A-4
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
Table A-1
(cont'd.)
Document Title
Description
This manual lists all the possible alarms for the system.
It also covers transient alarm messages, which are known
as technician messages. This manual is intended for
technicians, network management personnel, or any
other engineering personnel with responsibility for
troubleshooting or monitoring the operational status of
the system.
User Configuration
Manager
Zone Configuration
Manager
Configuring Features
Software Download
Radio Management
Affiliation Display
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
A-5
System Overview
Table A-1
(cont'd.)
Document Title
Description
Fleetmapping
Performance Management
Dynamic Reports
A-6
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
Table A-1
(cont'd.)
Document Title
Description
Historical Reports
InfoVista
Security Management
Radio User
Assignment/Radio User
Identity (RUA/RUI)
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
A-7
System Overview
Table A-1
(cont'd.)
Document Title
Description
Data Subsystem
MultiCADI
Telephone Interconnect
Active Directory/Domain
Name Services
A-8
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
Table A-1
(cont'd.)
Document Title
Description
Backup/Restore Collector
Application User Guide
Dimetra Enhanced
Software Update User
Guide
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
A-9
System Overview
Table A-1
(cont'd.)
Document Title
Authentication and
Encryption Overview
Description
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
Authentication Overview
Authentication Centre
(AuC) User Manual
Clear Authentication
Centre (AuC) User Manual
A-10
Table A-1
(cont'd.)
Document Title
Description
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
A-11
System Overview
Table A-1
(cont'd.)
Document Title
Description
Network Security
End-to-End Encryption
KVL3000 Plus User Guide
This manual provides instructions for upgrading/reinstalling the KVL application, upgrading the Security
Adapter software, and applying security settings on the
KVL.
A-12
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
Table A-1
(cont'd.)
Document Title
Description
MCC 7500-series
Bandwidth Management
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
A-13
System Overview
Table A-1
(cont'd.)
Document Title
Description
MCC 7500
Internationalization
Process User Guide
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
Object Call
Barring of Incoming
Calls/Barring of Outgoing
Calls (BIC/BOC)
RF Sites
MTS 1: Installation,
Configuration, and Basic
Service Manual
A-14
Table A-1
(cont'd.)
Document Title
Description
EBTS: Installation,
Configuration, and Basic
Service
MBTS: Installation,
Configuration, and Basic
Service
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
Managing the
Infrastructure Quick
Reference Guide
Network Configuration
Tool (NCT) Express
A-15
System Overview
Table A-1
(cont'd.)
Document Title
Description
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
Online Help
Application Launcher
Online Help
User Configuration
Manager (UCM) Online
Help
Zone Configuration
Manager (ZCM) Online
Help
A-16
Table A-1
(cont'd.)
Document Title
Description
Authentication Centre
Online Help
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
Call Processing, NM
and Data Subsystems
Restoration - Generation 2
System
Call Processing, NM
and Data Subsystems
Restoration - Generation 3
System
Standalone Subsystems
and Components
Restoration - Generation 2
System
Standalone Subsystems
and Components
Restoration - Generation 3
System
A-17
System Overview
Table A-1
(cont'd.)
Document Title
Description
Backup/Restore Collector
Application User Guide Generation 2 System
Backup/Restore Collector
Application User Guide Generation 3 System
A-18
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
Related Information
Document Title
Description
Glossary
Documentation Overview
System Overview
Zone Controller
S6000 Router
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
Related Information
(cont'd.)
Document Title
Description
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
II
Link Encryption
Network Management
Servers
Network Management
Client
Remote Access
Related Information
(cont'd.)
Document Title
Description
Server Software
Restoration
Server Hardware
Restoration
Stand-alone Components
Restoration
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
III
Related Information
(cont'd.)
Document Title
Description
MTS 1 Restoration
EBTS Restoration
Fault Management
ZoneWatch
IV
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
Related Information
(cont'd.)
Document Title
Description
This manual lists all the possible alarms for the system.
It also covers transient alarm messages, which are known
as technician messages. This manual is intended for
technicians, network management personnel, or any
other engineering personnel with responsibility for
troubleshooting or monitoring the operational status of
the system.
User Configuration
Manager
Zone Configuration
Manager
Configuring Features
Software Download
Radio Management
Affiliation Display
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
Related Information
(cont'd.)
Document Title
Description
Fleetmapping
Performance Management
Dynamic Reports
VI
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
Related Information
(cont'd.)
Document Title
Description
Historical Reports
InfoVista
Security Management
Radio User
Assignment/Radio User
Identity (RUA/RUI)
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
VII
Related Information
(cont'd.)
Document Title
Description
Data Subsystem
MultiCADI
Telephone Interconnect
Active Directory/Domain
Name Services
VIII
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
Related Information
(cont'd.)
Document Title
Description
Backup/Restore Collector
Application User Guide
Dimetra Enhanced
Software Update User
Guide
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
IX
Related Information
(cont'd.)
Document Title
Authentication and
Encryption Overview
Description
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
Authentication Overview
Authentication Centre
(AuC) User Manual
Clear Authentication
Centre (AuC) User Manual
Related Information
(cont'd.)
Document Title
Description
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
XI
Related Information
(cont'd.)
Document Title
Description
Network Security
End-to-End Encryption
KVL3000 Plus User Guide
This manual provides instructions for upgrading/reinstalling the KVL application, upgrading the Security
Adapter software, and applying security settings on the
KVL.
XII
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
Related Information
(cont'd.)
Document Title
Description
MCC 7500-series
Bandwidth Management
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
XIII
Related Information
(cont'd.)
Document Title
Description
MCC 7500
Internationalization
Process User Guide
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
Object Call
Barring of Incoming
Calls/Barring of Outgoing
Calls (BIC/BOC)
RF Sites
MTS 1: Installation,
Configuration, and Basic
Service Manual
XIV
Related Information
(cont'd.)
Document Title
Description
EBTS: Installation,
Configuration, and Basic
Service
MBTS: Installation,
Configuration, and Basic
Service
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
Managing the
Infrastructure Quick
Reference Guide
Network Configuration
Tool (NCT) Express
XV
Related Information
(cont'd.)
Document Title
Description
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
Online Help
Application Launcher
Online Help
User Configuration
Manager (UCM) Online
Help
Zone Configuration
Manager (ZCM) Online
Help
XVI
Related Information
(cont'd.)
Document Title
Description
Authentication Centre
Online Help
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
Call Processing, NM
and Data Subsystems
Restoration - Generation 2
System
Call Processing, NM
and Data Subsystems
Restoration - Generation 3
System
Standalone Subsystems
and Components
Restoration - Generation 2
System
Standalone Subsystems
and Components
Restoration - Generation 3
System
XVII
Related Information
(cont'd.)
Document Title
Description
Backup/Restore Collector
Application User Guide Generation 2 System
Backup/Restore Collector
Application User Guide Generation 3 System
XVIII
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP