Professional Documents
Culture Documents
DIMETRA
Dimetra IP Compact (DIPC)/Scalable Dimetra IP (SDIP)
SYSTEM OVERVIEW
June 2012
*68015000452*
68015000452-C
2012 Motorola Solutions, Inc. All rights Reserved
Copyrights
The Motorola products described in this document may include copyrighted Motorola computer programs. Laws
in the United States and other countries preserve for Motorola certain exclusive rights for copyrighted computer
programs. Accordingly, any copyrighted Motorola computer programs contained in the Motorola products described
in this document may not be copied or reproduced in any manner without the express written permission of Motorola.
2011 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 nonexclusive, 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
trashbin label on the product (or the package in some cases).
As defined by the WEEE directive, this cross-out trashbin 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.
Logo 2 means that the product may contain substances in excess of the
maximum concentration value for materials identified in the China
Management Methods regulation, and has an Environmental Friendly
Use Period (EFUP) in years, fifty years in the example shown.
Logo 1
Logo 2
The Environmental Friendly Use Period (EFUP) is the period (in years) during
which the Toxic and Hazardous Substances (T&HS) contained in the Electronic
Information Product (EIP) will not leak or mutate causing environmental pollution
or bodily injury from the use of the EIP. The EFUP indicated by the Logo 2 label
applies to a product and all its parts. Certain field-replaceable parts, such as
battery modules, can have a different EFUP and are marked separately.
The Disclosure Table is intended only to communicate compliance with China
requirements; it is not intended to communicate compliance with EU RoHS or any
other environmental requirements.
Service Information
EMEA Systems Support Centre (ESSC)
The EMEA Systems Support Centre 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 as to whether or not your current service agreement entitles
you to benefit from this service, or if you would like more information about the Technical Support Service,
please contact your local customer support or account manager for further information.
Contact details:are:
Email:
ESSC@motorolasolutions.com
List of Telephone numbers:
Country
AUSTRIA
DENMARK
FRANCE
GERMANY
ITALY
LITHUANIA
NETHERLANDS
NORWAY
PORTUGAL
RUSSIA
SAUDI ARABIA
SOUTH AFRICA
SPAIN
UNITED KINGDOM
All Other Countries
Your Input
...is much appreciated. If you have any comments, corrections, suggestions or ideas for this publication or any
other requirements regarding Motorola publications, please send an e-mail to
doc.emea@motorolasolutions.com.
Table of Contents
1
System Overview
ii
iii
System Overview
iv
5.5
5.6
5.7
5.8
System Overview
vi
vii
System Overview
viii
ix
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 2-15
Figure 2-16
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
xi
System Overview
Figure 3-17
Figure 3-18
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 5-15
Figure 6-1
Figure 7-1
Figure 7-2
Figure 7-3
xii
List of Tables
Table 2-1
Table 2-2
Table 3-1
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 5-6
Table 6-1
Table 7-1
Table 7-2
Table 7-3
Table 7-4
Table 7-5
Table A-1
xiii
Document History
Edition
Description
Date
68015000502-A
Initial Version
Nov. 2010
68015000502-B
Jun. 2012
xv
xvii
xix
Course Description
You this volume most helpful you have already attended the Dimetra IP
system training to learn the system operating principles.
xxi
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.
xxiii
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.
xxv
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.
xxvii
Microphone
0
Antennas
0
0
0
0
Tra ns mitte r
Receiver
Loudspeaker
- June 2012
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
1-2
- June 2012
Figure 1-3
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.
- June 2012
1-3
System Overview
Figure 1-5
Semi-Duplex Communication
TX 851.0125 MHz
RX 806.0125 MHz
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
- June 2012
- June 2012
1-5
System Overview
1-6
- June 2012
The BTS has several channels and these channels can either be designated to Control Channel (CC) or Traffic
Channel (TCH), which are mentioned below.
- June 2012
1-7
System Overview
1.1.5 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
- June 2012
Channel 1
Channel 2
Channel 3
- June 2012
1-9
System Overview
Figure 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-10
- June 2012
Figure 1-9
Controller
CC
TCH
TCH
Channel 1
Channel 2
Channel 3
TCH
Channel 4
1.1.6.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.
- June 2012
1-11
System Overview
Figure 1-10
Ta lkgroup 1
Ta lkgroup 2
Ta lkgroup 3
1.1.6.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
- June 2012
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
- June 2012
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.
- June 2012
Figure 1-14
TETRA Carrier
C
Ta lkgroup A
Ta lkgroup B
- June 2012
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.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
- June 2012
Figure 1-16
RF Site
Site
Control
Audio
Distribution
Subsystem
Mobile Switching
Office
Management
Subsystem
- June 2012
1-17
System Overview
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-18
- June 2012
- June 2012
1-19
System Overview
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 o
o
C udi
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-three multizone
terms described in the following.
1-20
- June 2012
The zone assigned to a particular ID is the home zone of this ID. The home zone to which an ID is assigned has an
impact on how the system operates. Home zone assignment affects system operation in the following ways:
Configuration information is distributed throughout the system based on the home zone assignment of the ID.
A Zone Controller stores only the configuration information for those individual and group IDs that are
home to that zone.
1.3.3.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.
- June 2012
1-21
System Overview
1.3.3.3 Multizones
In a multizone system, calls can take place between more than one zone. The controllers at the MSO of each zone
communicate with each other to coordinate the assignment of resources.
1-22
- June 2012
Infrastructure
- June 2012
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.
Figure 2-3
2-2
- June 2012
Pi/4-DQPSK Modulation
- June 2012
2-3
System Overview
Figure 2-5
2-4
- June 2012
Figure 2-7
- June 2012
2-5
System Overview
2-6
- June 2012
directly connected to a single receiving computer. The switch acts as the central point of a star topology network.
Therefore, the two computers do not experience collisions, and the full bandwidth of the transmission medium is
available to any two stations that wish to communicate.
Switched Ethernet technologies are used to allow equipment to communicate within a zone. The system uses
LAN transmission to handle the flow of intrazone data. It also uses Wide Area Network (WAN) transmission to
handle the flow of interzone data.
Three basic types of information are exchanged in the system: voice, call control, and network management
traffic. Network management and control information must be exchanged between devices installed within each
individual zone, and between devices installed in different zones. Ethernet and Frame Relay are the primary
communication technologies used to implement high-speed exchanges of management, control, and voice traffic
among the various devices within an individual zone.
Routers are used to implement high-level transport connections between network nodes in the system. Routers make
the LAN connections and WAN transmission facilities transparent to the network nodes that may be communicating
either within the same zone or between one zone and another. Routers also allow alternate paths to be implemented
between interconnected equipment to permit the system to continue operating should specific physical links fail.
2.2.2.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.
- June 2012
2-7
System Overview
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-8
E1 Carrier
2-8
- June 2012
number of the next physical circuit as it passes through each switch along the path. A DLCI is different from a
network address in that it identifies a circuit in both directions, not a particular endpoint. A frame contains only
one DLCI, not a source and destination.
In general, the only DLCI numbers you see are those numbers assigned to the physical circuits on the perimeter of
the Frame Relay cloud. DLCIs only have local significance and represent end-to-end virtual connections that have
a permanently configured switching path to a certain destination. Thus, by having a system with several DLCIs
configured, you can communicate simultaneously with several different sites.
- June 2012
2-9
System Overview
Figure 2-9
2-10
- June 2012
Figure 2-10
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.
- June 2012
2-11
System Overview
2-12
- June 2012
Unicast Routing
Most datagrams sent across a typical network use unicast messaging to deliver information between one point
and another.
Multicast Routing
Since talkgroup and announcement calls involve routing of audio between a single source and multiple recipients,
multicast routing works well with group-based audio routing. Multicast allows the transmitting radio audio to 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.
- June 2012
2-13
System Overview
In the Dimetra IP network, all the devices associated with a particular call are instructed to join a specific multicast
group. After the join messages are received from the devices, the RP propagates the multicast traffic to the
appropriate devices, sites, and zone(s) that are involved in the call and that have sent their join message.
The RP is typically defined as the router located near the receiving end of the multicast traffic, rather than a router
located near the source of the traffic. This allows greater efficiency of network resources, since the higher volumes
of multicast traffic is only spread across the receiving end of the network, rather than spreading all the replicated
packets directly from the source location across the entire network.
Multicast trees for audio traffic are set up as requested and are present only for the duration of the multicast call. A
range of class-D IP addresses (addresses beginning with 224 -239) are designated as multicast group addresses.
Process Steps
1
A radio user presses the PTT button to talk to other users in the talkgroup. The radio transmits a Call Request
on the RF control channel at the site. The Call Request is received by the control channel and forwarded to
the site LAN. Before placing the Call Request packet on the site Ethernet LAN, the base station encapsulates
the Call Request message in a User Datagram Protocol (UDP/IP) datagram with the destination IP address
of the Zone Controller.
UDP is a transport layer protocol that resides on top of the IP. UDP provides a transaction-oriented,
best-effort delivery service. IP is the Internet layer protocol tasked with defining how data is transferred
across the network, how devices are addressed, and how to route data appropriately. IP defines a
universal/global addressing method. It defines how to fragment, transport, and reassemble data packets
2-14
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.
- June 2012
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.
- June 2012
2-15
System Overview
Figure 2-13
2-16
- June 2012
messages to appropriate sites, assigning an IP multicast group address to use for the call. Control communication
from the Zone Controller to the RF sites is accomplished using multicast; unicast is used for transmissions from
the RF sites back to the Zone Controller.
- June 2012
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.
Figure 2-16
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.
2-18
- June 2012
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 Managing Secure Communications manual.
Feature
Support
260-275 MHz
350-470 MHz
806-870 MHz
Digital Codec
The frequency bands provided above may differ based on the local regulations of your country.
Table 2-2
- June 2012
Feature
Support
4 zones
25 sites
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).
- June 2012
3-1
System Overview
Figure 3-1
List of Entities
MTIG-IP01
MTIG-IP01
MTIG-IP02
MTIG-IP02
MTIG-E101
MTIG-E101
MTIG-E102
MTIG-E102
3-2
- June 2012
Two redundant Zone Controllers are connected to the network through the core LAN switch . This switch provides
connections over two separate virtual LANs, used to switch system resources between the Zone Controllers and
provide high availability for call processing and resource management. While both Zone Controllers are powered and
enabled at the same time, only one Zone Controller is actively participating in call processing tasks at any one time.
A Zone Controller may have a redundant state of either active or standby. The Zone Controller responsible
for call processing is in the active state. The Zone Controller that is not actively processing calls in the zone
is in the standby state. The standby controller remains in standby mode until the active Zone Controller fails or
until a switchover command is initiated. System information that is necessary for call processing is downloaded
to both Zone Controllers. The Zone Controllers include hardware for storing data, controlling zone activities,
and communicating with zone resources.
In a non-redundant system the Zone Controller is hosted on the same physical server platform as the NM servers and
in a redundant system one Zone Controller is hosted on the same physical server platform as the NM servers and the
other Zone Controller on a separate server platform.
- June 2012
3-3
System Overview
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
AIS
GGSN1
VPN
Router
CWR Panel
ESL - GBN
BTS
Remote Control Zone
Other Zone
Internet
VPN
Client
Mutually exclusive
The server components of the Network Management subsystem reside on the Primary Management Server
and include User Configuration Server (UCS), Zone Database Server (ZDS), Zone Statistics Server (ZSS),
Unified Event Manager (UEM), System Statistics Server (SSS), and Air Traffic Router (ATR).
Network management provides the tools, commonly known as FCAPS, for fault, configuration, accounting
performance and security management. The network management functions in Dimetra IP are distributed across
several applications and servers that are installed in one of three configurations: system, zone, and remote. The
3-4
- June 2012
configurations are designated by the name Operations Support Systems (OSS). The following describes the
individual network management building blocks of the Zone OSS and Cluster OSS. These building blocks can
be divided into two categories:
Private Radio Network Management (PRNM) client applications such as:
ZoneWatch
Radio Control Manager (RCM)
Zone Configuration Manager (ZCM)
User Configuration Manager (UCM)
Radio Control Manager Reports (RCM Reports)
Historical Reports
Dynamic Reports
ATIA Log Viewer
Affiliation Display
Unified Event Manager (UEM)
Software Download Manager
Network Transport Management (NTM) client applications.
Network Configuration Tool Express (NCT)
Trivial File Transfer Protocol (TFTP)
- June 2012
3-5
System Overview
3-6
- June 2012
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.
- June 2012
3-7
System Overview
WAN links
Core routers
Gateway routers
Exit routers
Although reports are preconfigured for the site routers and their links, they are not enabled unless the user
specifically turns them on. This is to reduce the traffic going across the site links and to reduce the overhead on the
InfoVista server so it can focus on the core LAN switches and routers at the core sites.
InfoVista is configured with integrated MIBs from the managed devices.
3-8
- June 2012
- June 2012
3-9
System Overview
VPN Gateway
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
ESL - GBN
BTS
Remote Control Zone
Other Zone
Internet
VPN
Client
Mutually exclusive
3-10
- June 2012
MTIG-E1
Server 1
Primary
Management
Server
MTIG-IP
Server 1
Primary
Zone Server
Primary Data
Server
GPS
To PABX
Figure 3-4
Secondary
Zone Server
NTS
EC
Core LAN Switch 1&2
KMF
NM Client
CGE1
MCC7500
Router
AIS
GGSN1
VPN
Router
CWR Panel
ESL - GBN
BTS
Remote Control Zone
Other Zone
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.
- June 2012
3-11
System Overview
3-12
- June 2012
For more detailed description of Network Time Server, see Network Time Server manual.
- June 2012
3-13
System Overview
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
E1 CGE1
NM Client
E1 CGE2
MCC7500
Border
Router
AIS
GGSN1
VPN
Router
CWR Panel
ESL - GBN
BTS
Remote Control Zone
Other Zone
3-14
Internet
VPN
Client
Mutually exclusive
- June 2012
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-7
Secondary
Zone Server
NTS
EC
Core LAN Switch 1&2
KMF
NM Client
Eth
CGE1
Eth
CGE2
BH
Switch 01
BH
Switch 02
E1 - 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:
- June 2012
3-15
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.
Figure 3-8
3-16
- June 2012
- June 2012
3-17
System Overview
3-18
- June 2012
3.3.1.2 MTS 1
Figure 3-10
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
Site Controller (SC)
Duplexer with Preselector path
Power Supply Unit
The duplexer enables a duplexed Receive/Transmit function on one antenna, which further reduces the total count
on antennas per site. The MTS 1 comes with several optional accessory kits such as solar shield for sun heat
protection (for outdoor use).
- June 2012
3-19
System Overview
Figure 3-11
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.
Figure 3-12
3-20
MTS 2
- June 2012
3.3.1.4 MTS 4
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
Figure 3-13
- June 2012
MTS 4
3-21
System Overview
A Radio Frequency Distribution System (RFDS) combines up to eight transmit channels onto just one antenna and
distributes up to three receive antennas to multiple base radios. Duplexers enable a duplexed Receive/Transmit
function, which further reduces the total count on antennas per site. For non-duplexed operation the MTS 4 also
comes optionally with a Tx-postfilter that allows sufficient space for up to three preselectors. This configuration
supports up to triple diversity un-duplexed with one Tx and three Rx antennas.
The MTS 4 prime cabinet is built up out of two card cages above one another and supports up to four base radios.
For expansions up to eight base radios an expansion cabinet of exactly the same size as the prime cabinet can
be added. An MTS 4 card cage with Base Radios power supply and SC is identical to an MTS 2 with the filter
and combiner section removed.
A second SC can be installed at the BTS site to provide active/standby redundancy. Redundant Site Controllers
are linked through a 10/100Base-T Ethernet interface.
3-22
- June 2012
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).
- June 2012
3-23
System Overview
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-24
- June 2012
Figure 3-16
Control Site
- June 2012
3-25
System Overview
Figure 3-17
Dispatch Subsystem
The MCC 7500 Dispatch Console is Motorolas high-tier radio dispatch console system. A console dispatch
subsystem consists of the following components:
A Motorola-certified Dispatch Console PC
Accessories, such as headsets, speakers, desk microphone and a foot switch.
A logging system. (The Archiving Interface Server (AIS) and the associated logging recorder and replay
station)
An Analog Conventional Channel Gateway (CCGW) (also known as the conventional base station interface)
The dispatch console equipment connects directly to the radio systems IP transport network. It uses the IP packet
protocols for passing call control data and call audio through the system. The following figure shows a high-level
diagram of how the MCC 7500 equipment fits into the system.
3-26
- June 2012
Figure 3-18
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.
- June 2012
3-27
System Overview
Figure 3-19
3-28
- June 2012
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.
- June 2012
3-29
System Overview
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-21
3-30
- June 2012
3.4 Radios
Figure 3-22
3.4 Radios
Radios communicate with the RF sites using the TETRA standard. These radios support encryption, authentication,
and interfacing for a data terminal.
- June 2012
3-31
System Overview
3.4.1 MTH800
Motorolas MTH800 is built on the experiences of the earlier released MTH650 and is further enhanced with a
new engine and with an extensive range of new features, functions and benefits and offers as such a wide range
of capabilities including, state of the art end-to-end encryption (E2E), a high-resolution color display as well as a
revolutionary Automatic Personal Location Service (APLS) based on GPS.
From a hardware point of view the MTH800 has the same Ergonomics and form factor design as known from the
MTH650, e.g. a rugged magnesium shell and rubber overmould.
With a resolution of 130 x 130 pixels and over 65,000 colors, the display provides accurate reproduction of faces
and other images. Coupled with the latest backlighting technologies, the display provides maximum image
definition in a wide range of lighting conditions.
To harness the power of MTH800 a new easy to use graphical user interface is included including assignable
shortcuts to menu items, more that 3000 talk groups as well as a unified phone book with 1000 phone numbers
and 1000 private call numbers.
The MTH800 comes with a full single chip, low current consumption and high sensitivity - GPS receiver built into
the terminal. Furthermore, the MTH800 uses a new patented GPS antenna integrated into the TETRA antenna to
ensure optimal coverage. The solution includes a full terminal resident software application providing control of
all GPS parameters over the air.
While compact and lightweight the MTH800 introduces full E2E encryption with tamper protection, a choice of
algorithms and Over-the-Air-Keying using Motorolas proven Key Management Facilities. Dependant on security
requirements the MTH800 can be factory fitted with E2E encryption OR it can be retrofitted and provisioned
in-country at a later date.
3-32
- June 2012
3.4.2 MTP850
Figure 3-23
MTH800 Radio
3.4.2 MTP850
The MTP850 is the latest available TETRA Hand portable terminal from Motorola. The terminal shares Software
platform with the MTH800, and as such their features are aligned e.g. in terms of End-to-End Encryption (E2E),
GPS Location Services, WAP interface and usages of Multi Slot Packet Data. The MTP850s Man Machine
Interface is also aligned with the MTH800, so users of the MTH800 recognize the same menu easy-to-handle
structure as of the MTH800, and are able to benefit from the same high quality color display. From a form factor
point of view the MTP850 comes with a new Ergonomic and form factor design, which provides both smaller size
and lower weight compared to the MTH800. A Remote Speaker Microphone (RSM) connector is located on the side
of the terminal. The MTP850 has with a choice of two battery sizes, both of which are designed as one-piece unit to
ensure the firm attachment of the battery to the terminal and to allow one-handed change of battery.
- June 2012
3-33
System Overview
Figure 3-24
MTP850 Radio
3.4.3 MTP850 S
Incorporating all of the features of the field proven MTP850, this terminal incorporates an advanced Man Down
sensor for exceptional user safety together with a new side connector for increased ruggedness. Providing higher
power will increase 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 has the capability for maintaining
communications in the most demanding situations.
Figure 3-25
3-34
MTP850 S Radio
- June 2012
3.4.4 MTP830 S
3.4.4 MTP830 S
Motorolas MTP830 S TETRA portable radio is the ideal choice when working in extreme conditions. This radio
delivers premium performance, whilst combining louder audio and enhanced erogonomics with simplified controls,
allowing fire fighters and other first responders to focus on the task at hand.
Figure 3-26
- June 2012
3-35
System Overview
Figure 3-27
MTP850Ex Radio
3-36
- June 2012
3.4.7 CEP400
Figure 3-28
MTP810Ex Radio
3.4.7 CEP400
Motorolas CEP 400 TETRA portable delivers the high performance and dependability required for enhanced
workforce productivity and assured user safety. Leveraging the best features of a two-way radio and a cellular
phone, the lightweight and robust CEP400 has been engineered to ensure loud and clear communications even in
high noise work environments.
Figure 3-29
- June 2012
CEP400 Radio
3-37
System Overview
3.4.8 TCR1000
The Motorola Discreet TCR1000 secures communications in surveillance covert type operations.
Key features of TCR1000:
Secure Communication for safety and protection of information
Air Interface Encryption
End-End Encryption
Whisper mode for discrete use
Integrated GPS option that allows users to be located in need of assistance
Wide range of covert accessories to give its users flexibility in the way the radio can be worn
Connection to extension battery for increased operational life
Uses the same standard battery as cellular handsets
CPS-Lite facility for changing the talk groups with a TETRA PDA
Unique body worn double-loop antenna option increases range
1W, Class 4 Tx Power
Figure 3-30
TCR1000
3-38
- June 2012
3.4.10 MTM5400
3.4.10 MTM5400
The TEDS Ready MTM5400 TETRA DMO Gateway/Repeater mobile radio provides extended coverage,
exceptional audio performance and high-speed data connectivity to address current and future critical communication
needs of professional users. From advanced Over The Air terminal management capability, to integrated DMO
repeater-gateway and high-speed USB 2.0 interfacing, the rugged MTM5400 TETRA DMO Gateway/Repeater
combines a wide range of advanced features for enhanced usability and improved safety.
Figure 3-32
3.4.11 CM5000
The CM5000 is an advanced TETRA mobile radio terminal which has been designed using the latest digital radio
communication and micro-computer technology. It enhances TETRA radio performance and usability in locations
where coverage is limited.
With its full data capability and proven Motorola user interface, the CM5000 combines three modes of operation a
TETRA Mobile, a DMO Gateway and a DMO Repeater. When configured in Gateway mode, it acts as a bridge
between the trunked radio network and TETRA radios operating outside the network in Direct Mode (DMO). When
configured in Repeater mode, it extends the range of DMO communication by receiving and re-broadcasting
communications from other DMO users.
The following features are provided with the CM5000:
A large screen full dot matrix color display
High reliability design and production by adoption of surface mount technology and LSI devices
Its sophisticated high performance is micro-computer controlled
It has user friendly controls with audio and visual confidence indicators
Multiple facilities and options, such as:
Status Messages
Emergency Call
Multi-Site Roaming
Serial Communication Port for PC Connection
Data Communication Air Interface
Serial Data Port
GPS Receiver Connection
- June 2012
3-39
System Overview
Figure 3-33
CM5000
3-40
- June 2012
Figure 3-34
- June 2012
MTC100 PDA
3-41
- June 2012
4-1
System Overview
4-2
- June 2012
This information is initially entered into the User Configuration Manager (UCM) as a single point of entry to
avoid duplicating effort or generating mismatched databases. Afterwards, the information is replicated to each
zone database.
- June 2012
4-3
System Overview
Table 4-1
Database
Server
Function
UCS Database
Zone Database
RCM Database
Zone Controller
Affiliation Database
Cluster-Level Servers
User Configuration Server
(UCS)
Unified Event Manager Server
(UEM)
Zone-Level Servers
Zone Controller (ZC)
Zone Database Server (ZDS)
Zone Statistics Server (ZSS)
Unified Event Manager Server (UEM)
Air Traffic Router (ATR)
4-4
- June 2012
Server Interactions
Interaction
- June 2012
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.
4-5
System Overview
Table 4-3
Interaction
Description
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.
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
4-6
- June 2012
Table 4-3
- June 2012
Description
16
17
Distribution of the authentication keys and encryption keys from AuC to the
Zone Controller.
18
19
4-7
- June 2012
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
- June 2012
- June 2012
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
- June 2012
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.
- June 2012
5-5
System Overview
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
- June 2012
5.1.1.10 Multigroup
5.1.1.10 Multigroup
The Multigroup object is used to create records that identify a group of talkgroups that are the target of multigroup
announcements.
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.
- June 2012
5-7
System Overview
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
- June 2012
For group call services, the home zone of the group is always the controlling zone for the call, regardless of
the zone where the group member is currently registered. Depending on configuration, this can impact the
number of interzone calls versus the number of single-zone calls that take place in the system. This, in turn,
can affect the number of interzone resources that are needed between any two pair of zones.
User configuration information is entered in the appropriate objects in the UCS: Radio and Radio User for
individuals, Talkgroup and Multigroup for groups. Once entered, user configuration information is replicated
automatically to each zone in the cluster, where it is stored in the master database of a zone. The replication
process makes it possible, if needed, to use any zone to promote its copy of the user configuration information
back to the UCS in the cluster.
Next, based on the home zone mapping, each zone transfers the configuration information for its individuals and
groups to the Home Location Register (HLR) in the Zone Controller. The home zone mapping information is
replicated to each zone from the UCS in the form of map tables. There are two map tables: an individual to home
zone map and a group to home zone map.
Whenever any individual or group configuration information is needed by any zone, it gets that information from the
HLR in the home zone of an individual or a group.
Figure 5-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.
- June 2012
5-9
System Overview
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
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-10
- June 2012
Component
Function
Zone Controller
Gateway routers
- June 2012
Serve as the routing path for call processing control information and become
the RP for Zone Controller to RF site control paths (SCPs). In multizone
systems the gateway routers also serve as the RP for IZCPs. In the ESL
solution the gateway router functionality is colocated with the first core router.
5-11
System Overview
Table 5-2
5-12
Function
Core routers
Act as the distribution point for audio, control information and network
management traffic destined for the same zone sites. The core routers are
deployed in pairs, with each router connecting to the same CWR patch panel
via high-density cables. When a pair of core routers is connected to a CWR
patch panel, the routers are referred to as CWR (cooperative WAN routing)
peers. The core routers become the RP for audio routing in the system due to
the multicast address sent by the Zone Controller. Information is transmitted
within IP packets.
Exit routers
Act as the distribution point for audio, control information and network
management traffic destined for other zones. Like the core routers, the
exit routers are deployed in pairs, with each router connecting to the same
CWR patch panel via high-density cables. When a pair of exit routers is
connected to the CWR patch panel, the routers are referred to as CWR peers.
Information is passed as Frame Relay packets from the exit routers across
the WAN infrastructure to other zones (via CWR patch panels). In the ESL
solution the exit router functionality is colocated with the first core router.
Backhaul switch
A pair of backhaul switches per MSO are used to aggregate the IPSec and
IPIP tunnels for site links and inter-MSO links.
Provides the backbone for the routers within the master site to pass IP traffic.
The Zone Controller communicates over this switch to reach the network
management servers for radio and interzone information, to reach the core
routers and exit routers for intrazone and interzone transmissions, and select
the MTIG resources for audio conversion and distribution to the console
operator and telephone interconnect.
The CWR patch panels provide the connection between the core and exit
routers and the E1 WAN infrastructure. Core and exit routers are configured
in pairs to provide path redundancy for audio and control packets. With
Cooperative WAN Routing (CWR), the pair of routers work cooperatively
to control the CWR patch panel, which switches non-redundant E1 links
between the two routers in groups of 12. Each pair of CWR core or exit
routers is connected to a relay panel via high-density E1 ports. The CWR
patch panels RJ-48C connectors provide the connection to the E1 network.
MTIG
Serves as the site interface to the wide area infrastructure. Receives and
transmits control, audio, and management information. Accomplishes the
Frame Relay - Ethernet conversions.
The BTS base radio provide the RF interface between the radios and the
system.
- June 2012
- June 2012
5-13
System Overview
calls, the home zone of the group becomes the controlling zone for the call, regardless of which zone the
caller is in when the request is made.
When the call request originates from a BTS site, the request is encapsulated as 10Base-T Ethernet packets by the
base station and is sent to the Site Controller. The controller then encapsulates the traffic in Frame Relay packets and
transmits the traffic to the MSO.
Figure 5-4
5-14
- June 2012
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.
- June 2012
5-15
System Overview
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.
Step result:
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.
Step result:
5-16
- June 2012
- June 2012
5-17
System Overview
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-18
- June 2012
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.
- June 2012
5-19
System Overview
emergency alarms", they may receive emergency alarms from radios whose talkgroups or multigroups are outside of
their list of attachments, if there is no other RCM User online to receive the emergency alarm. The radio can be
configured to enter emergency call mode automatically when the emergency button is pressed.
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
- June 2012
Talkgroup Scanning is a best effort service in the radio, where the radio monitors talkgroup activity on a configurable
list of groups at the site where the radio is registered. When no group activity exists for the MSs selected TG or
associated multigroup and the radio is either idle on the MCCH or active on the PDCH and a call is initiated to a
TG defined in the active scan list, speech is heard in the loudspeaker of the radio unit and the call is monitored.
When a radio is active on the PDCH the data transfer is interrupted to join the group call and resumed when the
group call ends. Note that a radio unit only receives call setup request for scanned groups if another radio at the
same site has attached to the TG as its selected TG or if the site is configured as a critical site for the TG. When the
radio is on the PDCH, another radio is required to be active on the PDCH at the same site and attached to one of the
scanned groups as its selected TG before the setup is signaled on the PDCH.
While monitoring a call, the radio unit responds to a new call setup to TGs in the active scan list, to the radios
selected TG and associated multigroup, if the setup is to a group with higher scanning priority than the monitored
call. The group identity of the TG being monitored is displayed in the radio unit's display. Note however that
group calls are only signaled on the TCH of another call, when the new call is configured as a Priority Monitor
group or the group call is an emergency call.
During an active call the monitoring user may wish to participate in the call. When the monitored call is the selected
TG (affiliated group) or associated multigroup of the served user, the operation of PTT results in a transmission
request (normal operation) to this TG. However, for all other monitored calls, operation of PTT only results in a
transmission request to the monitored TG when the radio is configured to "TalkBack" to the current active group call.
Since scanning is always a best effort service at the radio, the end user should make a critical group its selected
group. If groups are critical as far as the system administrator or network operator is concerned, these groups can
be configured as Priority Monitor groups in the UCM and critical sites can be defined in the UCM as required
when setting up the group call.
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.
- June 2012
5-21
System Overview
Figure 5-7
Private Call
A private call begins with a call request. The call request resolution determines whether the call is set up or not.
Requests are rejected if the target radio does not respond to the request or if the target radio is not registered 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-22
- June 2012
5.5.1.2 Intrazone Private Call Audio Flow, Call Continuation, and Teardown
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.5.1.2 Intrazone Private Call Audio Flow, Call Continuation, and Teardown
When and where to use: This process describes the situation in which the private call connection is already
established. See 5.5.1.1 Private Call Request Flow, page 5-22 for details.
- June 2012
5-23
System Overview
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-24
- June 2012
Figure 5-8
The telephone interconnect feature builds upon all of the configuration and infrastructure discussed up to this
point. With talkgroup calls and unit-to-unit calls, all parties to the conversations all reside somewhere on the
Dimetra IP system.
For telephone interconnect calls, one of the parties is outside of the Dimetra IP system and is connected through
landline telephone to the radios in the system.
The Dimetra IP system supports radio-to-landline and landline-to-radio interconnect calls. It does not
support interconnect calls to and from talkgroups.
5.5.2.2 Configuration
Radios must be properly programmed to make and receive telephone interconnect calls.
- June 2012
5-25
System Overview
5-26
- June 2012
Regardless of the infrastructure configuration, user limitations, or channel availability, programming of the
radio can prevent interconnect calls from being attempted.
If shared service dictates that an interconnect call needs to be placed in the busy queue, the call is placed in
the queue, even if there is a channel available at the site.
Call Setup
When and where to use: This process describes the events that occur during the setup of a successful
radio-to-landline call.
- June 2012
5-27
System Overview
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-28
- June 2012
- June 2012
5-29
System Overview
The RNG provides the necessary encapsulation between the radio network and the PDR. The RNG also provides the
logical link connection and any necessary compression to deliver the outbound packet data traffic to the appropriate
destinations. The RNG hosts the packet data visitor location register (PD-VLR). The PD-VLR contains mobility
information and packet data channel assignments (if applicable) for all the packet data users that are currently
registered in the zone. The RNG receives updates to the PD-VLR from the Zone Controller.
The PDR provides encapsulation of traffic between the RNG and GGSN, provides mobility management of all packet
data users that are home to the zone, and provides access control according to the HLR/UCS settings. The PDR
delivers outbound traffic to the RNG with the appropriate destination address. The PDR hosts the packet data home
location register (PD-HLR). The PD-HLR contains all the packet data service permissions and configuration for
packet data users that are home to the zone. The PDR receives updates to the PD-HLR from the zone database server.
5-30
- June 2012
The GGSN provides separation between the infrastructure and the customer enterprise network. The GGSN
provides IP tunneling via a border router to the customer enterprise network.
The border router operates in the DMZ, which is a less secure portion of the network. The border router provides the
direct connection to the CEN.
The data terminal initiates the request for packet data service by establishing a point-to-point protocol (PPP)
connection with the radio. The data terminal sends information including its static IP address (if applicable), the
access point name (APN) for the packet data host, and challenge handshake authentication protocol (CHAP) if
RADIUS authentication is being used.
The radio requests access to a packet data channel (PDCH) at the BTS site. The radio sends the request along
with its assigned resource allocation group (RAG).
The Site Controller evaluates the resource allocation group for the radio and assigns a packet data channel which
is configured to operate with the resource allocation group of the radio.
The radio sends the packet data request information over the PDCH, and the request is received by the radio
network gateway (RNG) in the data gateway. The RNG forwards the request to the Packet Data Router (PDR).
The PDR checks the permissions for the radio according to its locally stored packet data home location register
(PD-HLR). The PD-HLR includes permissions and settings that have been defined through UCM. If packet data
services are permitted for the radio, the PDR forwards the request information over a GTP tunnel to the GGSN.
The GGSN establishes an IP tunnel to the customer enterprise network according to the APN in the request.
This IP tunnel provides delivery of packet data traffic between the Dimetra IP network and the customer
enterprise network. This tunnel originates at the GGSN, runs through the border router, and terminates at the
customer enterprise network.
The packet data host establishes contact with the data terminal and packet data traffic between the data host and
the remote data terminal can flow across the infrastructure.
- June 2012
5-31
System Overview
5-32
- June 2012
- June 2012
5-33
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-34
- June 2012
5.8.1 Authentication
5.8.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-11
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.
- June 2012
Encryption of Traffic
5-35
System Overview
Security Classes
Class
Authentication
OTAR
SCK
Encryption
CCK/DCK
Encryption
GCK
Enable/Disable
O (see note 3)
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-36
- June 2012
- June 2012
5-37
System Overview
5.9.2.1 AllStart
An AllStart setting for a group indicates that all the available resources for the call must be present for the call 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.
If any of the above conditions are not met, the call is placed in the busy queue.
5.9.2.2 FastStart
A FastStart setting for a group call indicates that only mandatory resources (that is, critical sites, critical 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.
5-38
- June 2012
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.
- June 2012
5-39
System Overview
Generally, a service state for a site other than wide area trunking causes the radios at the affected site to
attempt to register at a site that is in wide area trunking mode.
State
Definition
Wide-Area Trunking
Wide-area trunking is the normal state for a site within a zone. In this state, the site
receives call processing instructions from the Zone Controller. A radio registered at
the site can communicate with any other radio in the system. The basic criteria for
wide area trunking includes an active RF site control path between Zone Controller
and site, an enabled audio rendezvous point in the zone, a control channel and a
traffic channel at a site.
Local Site trunking mode is entered when the remote site loses communication
with the Zone Controller. In this mode, the remote site takes over call processing
responsibility. A radio registered at the site can communicate only with other radios
registered at the same site.
5-40
- June 2012
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.
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.10.2.1.1 Example 1
It is possible for some members of a talkgroup to have zone isolated service for a short interval during loss 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.
- June 2012
5-41
System Overview
Figure 5-13
5.10.2.2.2 Example 1
User 1 is in Zone 1, its individual home zone.
User 2 is in Zone 2, its individual home zone.
Zone 1 and Zone 2 are in interzone trunking.
In this case, all criteria are met (see the figure).
5-42
- June 2012
5.10.2.2.3 Example 2
Figure 5-14
5.10.2.2.3 Example 2
In a less commonly occurring example:
User 1 is in Zone 1 but its individual home zone is Zone 4.
User 2 is in Zone 2 but its individual home zone is in Zone 3.
To make an interzone individual call between User 1 and User 2 (See the figure), the following conditions must exist:
Zone 1 and Zone 2 must be in interzone trunking.
Zone 1 must have at least an Interzone Control Path to Zone 3.
Zone 2 must have at least an Interzone Control Path to Zone 4.
- June 2012
5-43
System Overview
Figure 5-15
5-44
- June 2012
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.
- June 2012
5-45
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-46
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.12.3.1.1 Radio Scatter, page 5-47.
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.
- June 2012
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
- June 2012
5-47
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-48
- June 2012
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.
- June 2012
5-49
- June 2012
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
- June 2012
The system can also be configured so the RCM, Console or CADI acknowledges the Emergency Alarm.
- June 2012
6-3
System Overview
Access to the PDS is via the Peripheral Equipment Interface at the radios and via an IP connection to the GGSN in
the infrastructure.
6-4
- June 2012
- June 2012
6-5
System Overview
6-6
- June 2012
When traffic resources are available, PPC calls are set up as normal calls, however, if traffic channels are not
available the Zone Controller preempts the necessary resources from normal calls of lower priority level. The ZC
uses the preempted resources to continue the set-up procedure of the PPC call.
- June 2012
6-7
System Overview
6-8
- June 2012
For further information on the voice logging system, turn to the MCC 7500 Dispatch Consoles Subsystem
manual.
Redundant components can be added to other parts of the infrastructure for instance to ensure traffic
of short data massages.
Furthermore, the system offers the possibility of geographical redundancy. With geographical redundancy the
functioning and its redundant counterpart are placed in two different locations. This can be done to avoid physical
damage to the system that impacts both the functioning and the redundant component.
- June 2012
6-9
System Overview
Figure 6-1
Geographical Location 2
To PABX/PSTN
EC
MTIG-IP
EC
MTIG1
00000
00000
0000
NTS
SDR2
0000
MTIG1
GGSN
MTIG-IP
RNG
To PABX/PSTN
Primary
Zone
Server
Border
Rouer
VPN
Router
0
00000
Core Gateway/
Exit Router(s)
Border
Rouer
VPN
Router
0000
Patch
Panel
CEN
00000
00000
CEN
Transport Element
Application Element
Mutualy Exclusive
Security Element
00
Bas e Stations
Control Rooms
Other Zones
Bas e Stations
Control Rooms
Other Zones
Patch
Panel
0000
KMF
00000
00000
Core Gateway/
Exit Router(s)
0000
EAuC
0000
00000
0000
0000
SDR1
00000
00000
0000
Secondary
Zone Server
Fiber
Primary
Management
Server
0000
PDR
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 system
and provide full voice and short data functionality within the local coverage area of the Dimetra IP system.
6-10
- June 2012
- June 2012
6-11
System Overview
Speaker II monitors the audio from all the (remaining) unselected talkgroups
This lets the dispatch console user monitor the voice activity on all the assigned talkgroups. The volume of Speaker
I and Speaker II can be set independently.
Priority Level
6-12
Audio Source
- June 2012
Table 6-1
Audio Source
Radio Transmit
- June 2012
6-13
System Overview
Optionally, one or more dispatch consoles in the zone can be designated secondary supervisory dispatch consoles.
These dispatch consoles have audio priority over other dispatch console transmissions in a group when using the
instant transmit feature.
6-14
- June 2012
it continues to transmit, although it appears to have been turned off to the user. Ambience listening is always
initiated by the infrastructure, either from a dispatch console or via a third party application interfacing through
the console feature API.
- June 2012
6-15
System Overview
6-16
- June 2012
- June 2012
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-15.
7-2
- June 2012
- June 2012
7-3
System Overview
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
- June 2012
- June 2012
7-5
System Overview
To configure information for users during various stages of the system's life User Configuration Manager is used.
The UCM spans cluster-level and zone-level configuration information. You can configure the following types of
information:
System Configuration - Configuration of cluster-level parameters, such as Adjacent Control Channels
(ACCs).
Radios - Configuration of talkgroups, multigroups, and radio users.
Security - Configuration of records that control cluster management functions
ZoneWatch Configuration - Configuration of zone-level parameters for ZoneWatch, such as filters, watch
window definitions, and watch profiles.
External Configuration - Registration and configuration of all zones, RF sites and call routes that have been
configured in other clusters of the system.
7-6
- June 2012
Unified Event Manager is the fault management application for Dimetra IP systems. Unified Event Manager
provides a centralized view of the operational status of an entire multizone or single zone system by displaying
intuitive, graphical representations (subsystem topology maps) of the system. Problems are identified rapidly when
they occur. Functions and tools also provide the ability to notify support personnel, track, diagnose, and correct
faults in an effective manner. Unified Event Manager also maintains a data warehouse, storing up to 30 days of
event history for report generation.
Unified Event Manager offers a SNMP trap message forwarding capability to pass fault information to a higher level
Enterprise network manager through a separate Network Interface Card (NIC).
- June 2012
7-7
System Overview
Enabling costs to be combined where multiple resources are invoked to achieve a given communication
objective
The NM subsystem provides an optional licensed interface, Air Traffic Information Access (ATIA), to which
third-party applications can interface for the purpose of collecting individual radio unit and talkgroup traffic data.
The ATIA stream provides information on the activity of individual radio users and talkgroups, including number of
calls, total call duration, number of busies, total busy time, and so on. This data can be used as input to an external
accounting or billing package. Both intra- and interzone data is passed through the interface.
7-8
- June 2012
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.
- June 2012
7-9
System Overview
7.4.5.5 Authentication
Authentication prevents hostile or other unauthorized radios from registering with the system. Authentication sends
a challenge to a registering radio. The radio must supply the appropriate response to access the system. If mutual
authentication is being used, then the radio also sends a challenge to the infrastructure, and the infrastructure must
supply a proper response. This ensures that both the infrastructure and the radio are both genuine.
Authentication relies on a separate secret key for each radio provisioned in the cluster. This key is provisioned in
the Provisioning Centre, Authentication Centre, and in the radio. For the Provisioning Centre and Authentication
Centre, each key is stored in a secure form in a database encrypted with a tamper-proof crypto card. The key are also
stored in a secure form in the radio. The Provisioning Centre is isolated from the network.
7-10
- June 2012
The Dimetra IP system offers various air interface security features. See the list of them and the purposes they
serve in the table below.
Table 7-1
Security Feature
Purpose
Air Interface Encryption - Dynamic Keys (DCK, GCK, Encryption of a user and signaling data over the air
CCK).
interface using dynamically generated keys to protect
against eavesdropping.
Air Interface Encryption - Static Keys (TM-SCK,
DM-SCK).
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.
- June 2012
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
Authentication material is managed locally by each AuC, independent of the master AuC.
7-12
- June 2012
- June 2012
7-13
System Overview
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
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
Zone Profile
ZoneWatch
FP
Cluster-Level Applications:
Zone-Level Applications:
7-14
- June 2012
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.
- June 2012
7-15
System Overview
As a radio roams from one site to another or changes talkgroups, Affiliation Display updates and displays the
affiliation and deaffiliation information for a monitored radio.
Affiliation Display enables you to view the association of a radio with a talkgroup and site. This information can
be useful for troubleshooting and tracking of radios in the system and for monitoring the movement of traffic
within a zone.
The affiliation information is displayed in four ways: for the entire zone, by site ID, by talkgroup ID, or by radio ID.
This information is near real-time data and is only available when the application is open.
Specifically Affiliation Display allows you to do the following:
Monitor affiliation for one or more radios using the Radio Viewer at one or more sites. You can locate
specified radios by ID.
Monitor affiliations by site using the Site Viewer and view a list of talkgroups or radios at a site.
Monitor affiliations by talkgroup using the Talkgroup Viewer. You can view information for sites at
talkgroup or radios at talkgroup.
Affiliation Display can be used to perform the following functions:
Monitor selected radios, talkgroups, and sites dynamically using the main window. Monitors affiliation and
deaffiliation information for the location of radios and their current talkgroup at a site within a zone.
Note the radio communication about a site, so you can see how traffic moves within sites in a zone. By
tracking selected talkgroups and radio users through a zone, you can see which sites get the most use.
From the Talkgroup Viewer, create a dynamic graphical display of radio usage at a site. The usage
information is captured in a graph format for talkgroups and sites.
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-16
- June 2012
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.
- June 2012
7-17
System Overview
Use the data to make changes in how radios and talkgroups are managed. You can closely examine what happens
during a shift or set period of time; for example, you can look at the busy count and see if calls are being missed.
Based on your monitoring, you could recommend system expansion or decide to modify your system design to
improve communication.
7-18
- June 2012
All monitoring displays are updated in near real-time as the information becomes available in the system.
- June 2012
7-19
System Overview
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-20
- June 2012
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.
- June 2012
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.
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.
7-21
System Overview
Table 7-5
Description
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.
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
7-22
- June 2012
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.
- June 2012
7-23
- June 2012
Document Title
Description
Glossary
Documentation Overview
System Overview
Zone Controller
Network Management
Servers
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
A-1
System Overview
Table A-1
Document Title
Description
Server Software
Restoration
Server Hardware
Restoration
Stand-alone Components
Restoration
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
A-2
Network Transport
Restoration
Fault Management
- June 2012
Table A-1
Document Title
Description
ZoneWatch
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
System Alarms and Events This manual lists all the possible alarms for the
system. It also covers transient alarm messages,
which are known as technician messages. This
manual is intended for technicians, network
management personnel, or any other engineering
personnel with responsibility for troubleshooting or
monitoring the operational status of the system.
User Configuration
Manager
- June 2012
A-3
System Overview
Table A-1
A-4
Document Title
Description
Zone Configuration
Manager
Configuring Features
Software Download
Radio Management
Affiliation Display
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
- June 2012
Table A-1
- June 2012
Document Title
Description
Fleetmapping
Performance
Management
Dynamic Reports
Historical Reports
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
A-5
System Overview
Table A-1
A-6
Document Title
Description
Security Management
Data Subsystem
Telephone Interconnect
Active Directory/Domain
Name Services
Alphanumeric Text
Service (ATS)
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
- June 2012
Table A-1
Document Title
Description
Backup/Restore Collector
Application User Guide
Dimetra Enhanced
Software Update User
Guide
Authentication and
Provisioning
Managing Authentication,
Encryption and
Provisioning
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
- June 2012
A-7
System Overview
Table A-1
Document Title
Description
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
Clear Provisioning Centre This manual describes how to use the Clear
User Manual
Provisioning Centre (PrC) application. The main
functions of the Provisioning Centre are:
Providing secure (encrypted) storage of radio
keys
Providing secure upload and download
facilities for radio keys and key data
Displaying up-to-date information about the
key status of the radios
Exporting K-Ref data to permanent storage
media
Generating audit trail and radio information.
A-8
- June 2012
Table A-1
Document Title
Description
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
- June 2012
CryptR Instruction
Manual
A-9
System Overview
Table A-1
Document Title
Description
MCC 7500
Internationalization
Process User Guide
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
A-10
- June 2012
Table A-1
Document Title
Description
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
RF Sites
MTS 1: Installation,
Configuration, and Basic
Service Manual
Managing the
Infrastructure Quick
Reference Guide
Network Configuration
Tool (NCT) Express
Online Help
- June 2012
Application Launcher
Online Help
A-11
System Overview
Table A-1
A-12
Document Title
Description
User Configuration
Manager (UCM) Online
Help
Zone Configuration
Manager (ZCM) Online
Help
Software Download
Online Help
Dimetra IP
Scalable
Dimetra IP
Compact/
Scalable
Dimetra IP
- June 2012