Compact Tetra System Planner

Compact TETRA System Planner
Compact TETRA
Section 6
System Planner
6866500U03
Issue April 2002

History Chart
Rev. Date Changed Page(s) Cause of Change Implemented
1.0 05. April 2002 All pages New Document W. Liegl
Compact TETRA Section 6 System Planner

COPYRIGHT Motorola 2002 Nr.: 6866500U03 Author: Wolfgang Liegl REV 1.0
Contents
1. Introduction ..........................................................................1-1
1.1. Purpose............................................................................................................ 1-1
1.2. Introduction ...................................................................................................... 1-1
1.3. Referenced Documents.................................................................................... 1-3
1.3.1. Motorola Documents and Tools – all available on Motorola Online................... 1-3
1.3.2. External Documents ......................................................................................... 1-3
2. Summary ..............................................................................2-1
2.1. Overview of Equipment .................................................................................... 2-1
2.1.1. Equipment orderable from Motorola via MOL ................................................... 2-1
2.1.2. Equipment not orderable directly from Motorola via MOL ................................. 2-1
3. System Planning Process ...................................................3-1

3.1. Customer Requirements Analysis .................................................................... 3-2
3.2. Quick check - is Compact TETRA the appropriate system? ............................. 3-3
3.3. System Sizing Process..................................................................................... 3-4
3.4. System Functionality Partitioning...................................................................... 3-4
3.4.1. Roadmap Compact TETRA .............................................................................. 3-5
4. System Overview .................................................................4-1

4.1. System Configuration Overview ....................................................................... 4-1
4.1.1. Stand-alone System ......................................................................................... 4-2
4.1.2. Single-Site System ........................................................................................... 4-3
4.1.3. Multi-Site System ............................................................................................. 4-4
4.2. Components of the System .............................................................................. 4-5
4.2.1. Base stations.................................................................................................... 4-5
4.2.2. CTG-1 Gateway Server .................................................................................... 4-8
4.2.3. CTD-1 Dispatcher Workstation ......................................................................... 4-9
4.2.4. TETRA Mobile Stations .................................................................................. 4-11
4.2.5. Portable Radios.............................................................................................. 4-14
4.2.6. Mobile Radios ................................................................................................ 4-17
5. System Description..............................................................5-1
5.1. System Architecture and Networking................................................................ 5-1
5.1.1. System elements.............................................................................................. 5-1
5.1.2. Real World Object Model.................................................................................. 5-2
5.1.3. System Networking .......................................................................................... 5-3
5.1.4. Distributed Architecture .................................................................................... 5-5
5.1.5. Logging / Tracing Data ..................................................................................... 5-8
5.1.6. Monitoring of System Parameters .................................................................... 5-9
5.1.7. Interfaces ......................................................................................................... 5-9
5.1.8. Actors............................................................................................................. 5-10
5.1.9. Service Matrix ................................................................................................ 5-11
Compact TETRA Section 6 System Planner Page: C-1

5.1.10. System Configurations ................................................................................... 5-12

5.2. System Capacity and Performance ................................................................ 5-14
5.2.1. Dimensions .................................................................................................... 5-14
5.2.2. Speech delay ................................................................................................. 5-15
5.2.3. Echo cancellation ........................................................................................... 5-15
5.2.4. Analogue audio .............................................................................................. 5-15
5.3. System Availability and Resilience ................................................................. 5-16
5.3.1. Failure Tolerance ........................................................................................... 5-16
5.3.2. Other aspects of availability of communication ............................................... 5-17
5.3.3. High availability due ease of maintenance...................................................... 5-18
5.4. System Features ............................................................................................ 5-19
5.4.1. System Features Overview ............................................................................ 5-19
5.4.2. Individual Call................................................................................................. 5-20
5.4.3. Group call....................................................................................................... 5-23
5.4.4. Group Attachment / Group Detachment ......................................................... 5-25
5.4.5. Group Monitoring............................................................................................ 5-26
5.4.6. Pre-emptive Priority Call................................................................................. 5-27
5.4.7. Dispatcher call................................................................................................ 5-29
5.4.8. Telephone call................................................................................................ 5-29
5.4.9. Registration .................................................................................................... 5-29
5.4.10. De-registration................................................................................................ 5-30
5.4.11. Cell re-selection.............................................................................................. 5-32
5.4.12. Call restoration ............................................................................................... 5-32
5.4.13. Transmission Control ..................................................................................... 5-33
5.4.14. Status SDS..................................................................................................... 5-34
5.4.15. Text SDS message ........................................................................................ 5-36
5.4.16. IP connectivity to System Components .......................................................... 5-37
5.4.17. Packet Data (Release 2) ................................................................................ 5-37
5.4.18. CLIP and TPI.................................................................................................. 5-39
5.4.19. Subscriber Management ................................................................................ 5-39
5.4.20. System Configuration ..................................................................................... 5-39
5.4.21. Logging and Tracing....................................................................................... 5-39
5.5. System External Interface .............................................................................. 5-40
5.5.1. TETRA Air Interface AI ................................................................................... 5-40
5.5.2. Subscriber Interfaces ..................................................................................... 5-41
5.5.3. ISDN-IF – Interface to regular networks ......................................................... 5-42
5.5.4. Dispatcher Workstation Interfaces.................................................................. 5-42
5.5.5. System wide parameters ................................................................................ 5-43
5.5.6. Base Station Parameters................................................................................ 5-44
5.5.7. Logging and Tracing Interface L/T-IF.............................................................. 5-45
5.5.8. Packet Data Interface PD-IF (Release 2) ....................................................... 5-46
5.5.9. SDS Transport Service Interface SDTS-IF ..................................................... 5-46
5.6. System internal interface ................................................................................ 5-47
5.6.1. E1-Link - Network Interface ............................................................................ 5-47
5.6.2. Dispatcher Access Interface DA-IF................................................................. 5-47
5.7. Safety............................................................................................................. 5-48
5.8. Security and privacy ....................................................................................... 5-48
5.9. System environment....................................................................................... 5-48
5.9.1. Climatic Environment – Operation .................................................................. 5-48
5.9.2. Technical Environment ................................................................................... 5-48

5.9.3. Transportability............................................................................................... 5-48

5.10. Computer resource......................................................................................... 5-49
5.10.1. Computer hardware........................................................................................ 5-49
5.11. Documentation ............................................................................................... 5-50
5.12. System environmental constraints.................................................................. 5-50
5.13. Packaging of the Base Stations...................................................................... 5-52
5.14. IOP Test......................................................................................................... 5-52
5.15. R&TTE Certificate .......................................................................................... 5-52
6. System Sizing.......................................................................6-1
6.1. Coverage Planning........................................................................................... 6-1
6.1.1. Coverage Planning Process ............................................................................. 6-1
6.1.2. Coverage Planning Tools ............................................................................... 6-13
6.1.3. Frequency Planning ....................................................................................... 6-15
6.1.4. Coverage Acceptance Testing........................................................................ 6-17
6.2. Traffic Planning .............................................................................................. 6-17
6.2.1. Main Control Channel Traffic.......................................................................... 6-18
6.2.2. Voice Traffic Planning .................................................................................... 6-21
6.2.3. Data Traffic Planning...................................................................................... 6-24
6.2.4. Traffic calculation tool available from MOL ..................................................... 6-25
6.2.5. Traffic calculation theoretical samples ............................................................ 6-25
6.3. Component Sizing .......................................................................................... 6-28
6.3.1. Pricing Tool available from MOL..................................................................... 6-28
6.3.2. Cost reduction – initial investment .................................................................. 6-28
6.3.3. Cost reduction – running costs ....................................................................... 6-28
7. Service ..................................................................................7-1
7.1. Definition of Service Level ................................................................................ 7-1
7.2. Escalation Process of Support and Service requirements ................................ 7-2
7.3. Support Solution............................................................................................... 7-3
8. Training.................................................................................8-1
9. Third Party Applications......................................................9-1

10. Equipment List and Ordering Guide.................................10-1
10.1. Base Station Equipment List .......................................................................... 10-1
10.1.1. CTS100 Models.............................................................................................. 10-1
10.1.2. CTS200 Models.............................................................................................. 10-1
10.1.3. CTS300 Models.............................................................................................. 10-1
10.1.4. Orderable Options for the Basestations.......................................................... 10-1
10.1.5. Spare Part Kits for Compact TETRA .............................................................. 10-2
10.1.6. Field Replaceable Units (FRU) Kits for the Basestations ................................ 10-6
10.2. Gateway Server Equipment List ..................................................................... 10-7
10.2.1. CTG-1 Gateway Server Modelling: ................................................................. 10-7
10.2.2. CTG-1 Gateway Server Spare Part Kit: .......................................................... 10-7
10.3. Dispatcher Workstation Equipment List .......................................................... 10-8
10.3.1. CTD-1 Dispatcher Workstation Modelling: ...................................................... 10-8

10.3.2. CTD-1 Dispatcher Workstation Spare Part Kit: ............................................... 10-8

10.4. Ordering Guide for Compact TETRA (via MOL only) ...................................... 10-9
11. Abbreviations .....................................................................11-1

1. Introduction
1.1. Purpose
This document is the System Planner for Motorola Compact TETRA System. It is part of the Compact
TETRA Product Manual.
It is for the use of Motorola Authorized System Partners for Compact TETRA and Motorola internal
use only. It may not be made available for any other party outside the Authorized System Partners
and Motorola.
The System Planner describes the system, internal and external interfaces and specifies the system
behaviour as it can be observed at these interfaces. Additionally it shows various details about the
system’s internal structure and also the hardware and software specifications and limitations of the
system.
The sole purpose of this document is to enable System Partners to design a Compact TETRA system.
More information and technical details of the components of the system are included in the first part of
the Compact TETRA Product Manual
1.2. Introduction
Compact TETRA is designed as a compact Motorola digital radio system solution, conforming to the
European ETSI-TETRA standard. The system is targeted for small to medium size Tetra networks.
In Europe, Middle East and Africa it is sold primarily over Motorola’s indirect distribution channels to
Accredited Compact TETRA System Partners. Other regions in the world may have chosen different
distribution strategies.
The following overview describes the realisation of identified key success criteria:
The system is resilient, flexible and extensible

The system achieves a high degree of resilience through an inherently distributed architecture. The
distributed architecture can tolerate the failure of individual components and links without employing
costly centralised redundancy schemes.
In the maximum system configuration, the system offers 124 simultaneous speech or data channels.
The system uses standard fractional E1 as a wide-area carrier. The required grade of service can be
achieved via a large number of physical media.
The system can be configured for two main modes of operation (see also 5.1.10):
Stand-alone: This mode offers a single base station for TETRA radio communication only. After initial
on-site configuration with an external configuration tool the base station operates stand-alone.
Single/Multisite: This mode offers a full-featured network of 1 to 8 base stations connectable to

a gateway for PABX/PSTN and 0 to 8 dispatcher workstations providing max. 128 channels.
The upgrade from a standalone system to a Single/Multi-site system reuses the existing hardware.
Easy to Sell, Order, Install, Operate and Maintain

The system can be fully set up and configured by System Partners. Pre-tuned Base stations and use
Compact TETRA Section 6 System Planner Page: 1-1

of remote configuration facilities ease initial system set-up and reduce total cost of ownership.
The system offers both on-line monitoring functions and logging and tracing facilities.
The HMI for the on-line monitoring functions is integrated into the Dispatcher Positions, without the
need for additional hardware.
System Partners can add value

System Partners can add value by bundling the system with customer-specific applications using data
gateway facilities like Packet Data and Short Data Service.
The system also keeps extensive logs of health and load information. These can be used by the
System Partners for off-line analysis of the system’s performance.
The system is cost competitive in 1 to 8 site configurations

The system achieves low cost through an extended use of COTS components. Dispatcher
Workstation connections utilise standard LAN cabling.
Cost of ownership is kept low by an efficient use of link bandwidth. The system can employ fractional
E1 links for connecting sites. Full E1 capacity is only required for large systems.
The system employs low-cost GPS receivers for time synchronisation.

1.3. Referenced Documents

1.3.1. Motorola Documents and Tools – all available on Motorola Online
Product Manual, English, comprising of the following sections:
1. Introduction & System Overview
2. Hardware Specifications and Installation
3. System Installation, Configuration and Maintenance
4. System Operation (Dispatcher)
5. Subscriber Management
6. System Planner (this document)
Tools available from MOL:
Quick Price Calculation Sheet
Simple Traffic Calculator
1.3.2. External Documents

Terrestrial Trunked Radio; Voice plus Data; Part2: Air Interface, ETS 300 392-2, version 2.1.1,
December 2000.
TETRA Memorandum of Understanding; TETRA Interoperability Profile; Version 1, TTR 001, ver
1.0.2, September 1999.
TETRA Memorandum of Understanding; TETRA Interoperability Profile; Version 2, TTR 001, ver
2.1.1, March 2000.
TETRA Memorandum of Understanding; TETRA Interoperability Profile; Version 3, Draft version 0.9.3,
June 2000.
Links to download external documents from:
TETRA MOU:
www.tetramou.com
ETSI:
www.etsi.org


2. Summary
Here is a brief overview what equipment can be ordered from Motorola or from another source.
In the second part there is a table of key numbers.
2.1. Overview of Equipment

2.1.1. Equipment orderable from Motorola via MOL
Frequency ranges: 380-400, 410-430, (450-470 later), 805-870 MHz
CTS 100 Base Station up to 2 carriers
CTG-1 Gateway Server incl. 4xISDN card (8 phone lines)
CTD-1 Dispatcher Workstation (up to 8 Workstations possible)
Internal Backup Battery Kit (CTS100 only)
External Battery Connection Kit
Door for the racks
Redundant Power Supply
Redundant Base Station Controller (Release 2)
Carrier Upgrade Kit
Recommended Spare part Kit for the Base Stations
Portable Radio MTP700
Portable Radio MTH500 (from mid 2002)
Mobile Radio MTM700
Accessories for Portable and Mobile Radio
2.1.2. Equipment not orderable directly from Motorola via MOL

rd
Applications from 3 Parties to provide customised solutions – see MOL for more information
Fast EtherNet HUB for the Dispatcher Network
Base Station Antennas for RX, TX and GPS
Antenna Cables


3. System Planning Process

This section describes the tasks that a system planner typical has to undertake as part of the system
design process. In addition, it describes how the other sections of this System Planner may help with
these tasks.
The diagram below shows the tasks involved in the process of designing a Compact TETRA system.
Customer
Requirements
Analysis System Design
System Sizing D i
System
Si i System Functionality
System
Coverage F i li
Planning Functionality
Partitioning
Traffic
Planning
3rd Party Certified Dimetra Compact TETRA

Non -Certified
System
Availability Functionality Functionality Functionality
System Layout &

Networking
Partners and Project Specific
Interfacing Commitment
Component
Sizing
Equipment
List
Costed System Design
Each of the tasks in the above diagram is described in the following sections.

3.1. Customer Requirements Analysis

The requirements for a radio system may be presented in many different ways, ranging from informal
discussions with potential customers, through to a detailed system requirements specification as part
of an Invitation to Tender (ITT). The first task of a system planner is to understand and clarify the
requirements and to determine if the requirements are best satisfied by a Compact TETRA system.
Possible alternative solutions in Motorola’s portfolio included:
Conventional (non-trunked) analogue Repeater Systems – generally low functionality, low

cost
SmartNet - single site analogue trunking
Analogue Smartzone – multisite analogue trunking
APCO25 Smartzone – multisite digital trunking compliant with the US APCO25 standard
Dimetra-IP – multisite digital trunking systems compliant with the ETSI TETRA standard
designed for high and very high capacities with focus on grouping and data communication.
IDEN – multisite digital trunking
Selecting an appropriate technology can be a complex issue with the following factors potentially
influencing this decision:
Coverage and capacity requirements
Functionality
Data Capability
Timeframe
Customer preferences
Spectrum availability
Customer budget
Once it has been determined that a Compact TETRA solution is appropriate the system design
process can commence. There are two primary tasks within this process:
Determining the system size to provide the required radio coverage and capacity
Determining how to provide the functionality required by the customer.

3.2. Quick check - is Compact TETRA the appropriate system?

The set of questions below should be answered “YES” if Compact TETRA is the right solution for a
customer looking for a new communication system.
Coverage:
Not more than 8 sites are required to achieve the expected coverage (approx. area of a City) YES
Capacity:
Not more than 2500 user in Single Site and 10000 users in Multi-site Systems YES
Not more than 256 Talk groups are required YES
Functionality:
User will setup system wide calls from point to point or point to multipoint YES
User will communicate without pressing PTT after initiating MS-MS and Phone calls (Full-Duplex)YES
User will transfer data in several applications YES
User will connect his radio system easily to an own or public telephone system YES
User has requirements for different kind of subscriber (light, small or rugged) YES
User wants to communicate everywhere – on fixed places, mobile in cars or ourside portable YES
User wants to operate the portables just like cellular phones YES
Reliability:
User cannot afford long down times of the radios system and terminals YES
If User wants to transport the system it should be small and light and work plug and play YES
User will not allow others to monitor the communication easily YES
Timeframe:
Customer will be operational within a view days after delivery of the system YES
Spectrum:
There is enough frequency spectrum for digital trunking available at the place of communication YES
Budget:
Customer has got a small to medium size budget (from $100k to $700k) YES
Customer will not pay any airtime for internal communication YES
Customer will not spend much effort to install and maintain a radio system YES
Customer will expand the system later with low effort to precalculated costs YES

3.3. System Sizing Process

The first task in sizing the system is to determine how many base stations (sites) are required in order
to meet the customer’s radio coverage requirements. Therefore special Soft Ware Tools or
Professional Coverage Services should be used.
The next task is to determine the number of channels required at each site in order to meet the
customers grade of service requirements for a given traffic profile. Therefore you can use the Traffic
Calculator available on Motorola Online MOL.
The system may be required to interface to other systems to provide additional functionality.
Paragraphs 5.5 and 5.6 describe the defined interfaces to the Compact TETRA system and how they
are provided.
The Compact TETRA system can be designed with redundant components to increase system
availability. Paragraph 2 describes some of the options to systems planners, which can impact the
system availability and provides information to enable an availability analysis to be performed.
The system design can include a number of physical sites that must be connected together.
Paragraphs 4 and 5 describe the Wide Area Network (WAN) solutions used to link sites and
guidelines on determining the required bandwidth of E1 connection between sites
Once the system architecture has been determined the individual components of the system can be
sized and an equipment list generated. Information on sizing and ordering for each of the system
components can be found in paragraph 6. One method to generate a Compact TETRA equipment list
is using the Simple Price Calculator Tool available from the Resource Center of Motorola Online.
3.4. System Functionality Partitioning

In parallel to the system sizing tasks described above, the system planner has also to determine how
the proposed solution can meet the customer’s functional requirements. The required functionality
can be partitioned into:
Existing Compact TETRA functionality (Certified and shipping)
Future Compact TETRA functionality (planned for later releases)
Other functionalities will be considered by business case

rd
3 party Applications
Please see Roadmap on the next page.
Paragraph 4 of this system planner provides detailed descriptions of the functionality that can be
provided by a Compact TETRA system.
Paragraphs 4 and 5 provide descriptions of the defined interfaces to a Compact TETRA system that
rd
may allow integration with 3 party equipment or applications to provide additional functionality.
The result of completing the tasks outlined above should be a costed Compact TETRA solution that
meets the customer’s requirements. There is a price tool for Compact TETRA on Motorola Online,
which helps to calculate the system price.
The next task for the system planner is often to help sell this solution to the customer via a proposal.
Not included in this system planner, a Sample Tender Template is available through the Resource
Center of Motorola Online.

3.4.1. Roadmap Compact TETRA

All dates and features below are based on the actual planning at the time of the revision of this
System Planner. Details may change to reflect new situations.
Release 1 Release 2 Release 2.1

Launched 3/2002 Planned 10/2002 Planned 12/2002
Call Features Call Features (incremental) Software Maintenance Release

• Individual (FD/HD) • Multi site group calls with
• Group (Late Entry, HD) dynamic paging area System Features (incr.)
• Dispatcher (FD/HD) • Cell Reselection and Call Monitoring API
• Telephone (FD) incl. DDI Restoration Monitoring PC
• Broadcast Call • Dynamic Site assignment Voice Recording (via partner)
• Queue and call back • Pre-Emptive Priority Group SORM (via partner)
Call
Data Features
• SDS type 1 (Status) Data Features (incremental)
• SDS type 4 (Text up to • Single Slot Packet Data with
140 Char) 500kbit/s infrastructure Release 3
• SDS Gateway (SD-IF) capacity Planned Q2/2003
• PD gateway (PD-IF)
System Features Call Features (incremental)
• Single Site / Stand alone System Features (incr.) • Priority call up to 8 level
• E1 / Fractional E1 • Multi Site, up to 8 sites • DTMF Over-dial
• Up to 8 Dispatchers (multi • Remote SW download • Full CLIP & TPI
language support) without interruption of other
• Remote SW download to sites System Features
BSC • 10’000 Subs, 32 carrier total • 30 PABX/PSTN
• 2500 Subs, 8 carrier • 806-870MHz interconnection using 2 MBit
• 380-400, 410-430, (450- • Dispatcher API ISDN
470) MHz • Monitoring capable
• Dual receiver diversity • Static Billings solution Further features are pending on
• 10W to antenna, TMA inputs from the market and
• Partial CLIP & TPI business cases.

4. System Overview
Compact TETRA is Motorola’s TETRA -compliant small digital radio system. The system provides
services to three groups of users:
Radio Users – mobile users in the system that can roam throughout the radio coverage area
provided by the system. The radio users access the system services using Mobile Stations
that communicate with the Base Stations in the infrastructure using the TETRA air-interface
protocol.
Dispatchers – fixed users that have access to advanced features and facilities provided by
the system. These features enable dispatchers to efficiently communicate with and manage
fleets of mobile users.
Network Managers – responsible for managing and maintaining the Compact TETRA
system. The system provides some applications that allow the network managers to
efficiently manage the system.
4.1. System Configuration Overview

The system is flexible and extensible and supports the following basic configurations:
Stand-alone system (w/o telephone interconnect, w/o Data Gateways and w/o dispatcher)
Single site system with up to 31 voice channels, 8 PABX/PSTN channels, Data Gateway
and 1- 8 Dispatchers supporting up to 2.500 subscribers
Multi site network (Release 2) with 1- 8 sites, up to 124 voice channels, 8 PABX/PSTN
channels, Data Gateway and 1-8 Dispatchers supporting up to 10.000 subscribers

4.1.1. Stand-alone System

This system configuration is focused on customer groups needing local coverage without direct
connected System Dispatcher functionality and Gateways to other services. Wireless Dispatcher
rd
solutions offered by 3 Parties can be used.
The Stand-alone Compact TETRA can be configured by a standard PC connected to the Base Station
Controller (BSC). For online monitoring of the system health and load conditions, a PC needs to be
attached permanently to the system.
Because this system configuration requires no supporting infrastructure or networking other than
power supply and antennas this configuration is most suitable for transportable and quick install
applications.
Features:
Individual Call (Full or Half-Duplex)

Group Call - incl. Late Entry- (Semi Duplex)
Short Data Service Type 1 (Status)
Short Data Service Type 4 (Text)
Easy configuration using a standard PC with MS Netmeeting installed
Max. System Configuration:
8 Carriers (32 logical channels – 1 Control + 31 Voice/Data Channels)

2500 Subscribers
256 Workgroups

4.1.2. Single-Site System

The single site system provides the following additional features and functions:
Features:
Individual Call (Full/Half Duplex)

Group Call (Semi Duplex)
Dispatcher Call (Full/Half Duplex)
Basestation PABX/PSTN Call (Full Duplex)
Short Data Service Type 1
(Status)
Short Data Transport Gateway
Packet Data Gateway (Rel.2)

Gateway
Server PSTN/PABX 8 Carriers (32 logical channels)
Interface 8 Dispatcher Workstations
8 PABX/PSTN connections
2500 Subscribers
Packet Data 256 Workgroups
Gateway
+ SDS Transp.
Dispatchers
Workstations
The single-site system is targeted primarily at customers that need local Tetra coverage and
additionally dispatch functionality and/or gateways to Data or/and Telephone.
The connection between the Site and the Gateway is a single fractional E1 link.
The connections from the Gateway Server to the Dispatcher Workstations or the Packet Data and
SDS Transport networks require 100Mbit Ethernet LAN infrastructure.

4.1.3. Multi-Site System

The Multi Site System provides the following additional features and functions:
Basestations Features:
Individual Call (Full/Half Duplex)

Group Call (Semi Duplex)
Pre-emptive Group Call
Dispatcher Call (Full/Semi Duplex)
PABX/PSTN Call (Full Duplex)
Short Data Service Type 1 (Status)
Short Data Transport Gateway
Packet Data Gateway (Rel.2)
Gateway PSTN/PABX
Server Interface
Packet Data 8 Sites / Basestations
+ SDS Transp. 8 Carriers per Basestation
Gateway 32 Carriers in the System
8 Dispatcher Workstations
8 PABX/PSTN connections
10000 Subscribers
256 Workgroups
Dispatchers
Workstations
Multi-site system offers all features of the single-site system and additionally multi-site individual and
group calls, including unannounced cell reselection with call restoration. An intelligent paging strategy
conserves air interface resources, yet ensures that subscribers are reachable for group
communications at all sites.
The multi-site system supports up to 10’000 subscribers. The system tracks the location and group
attachment status of the registered subscribers in a distributed database that allows fast local access
to the information on call set-up.
Every basestation uses a built-in GPS receiver for synchronisation with other sites hence a GPS
antenna has to be connected to the rack
The multi-site system uses a chain of E1 links for interconnecting the sites.
For reduced cost of ownership, smaller system configurations can use fractional E1 using multiplexers
from the E1-link provider. The system can be configured to limit the E1 timeslots used for
communication to a certain range.

4.2. Components of the System

4.2.1. Base stations
More technical details and specs of the Basestations you can find in Part2 + 3 of the Product Manual.
All Base Stations are available in : 380-400, 410-430, (450-470 later), 805-870 MHz.
4.2.1.1. CTS100 Compact TETRA Basestation

Compact base station with up to 7 duplex channels plus 1 control channel
Tower
Mounted
Amplifier
CTS100
1 or 2 TETRA-Carriers/Transceivers
AC/DC power supply including battery charge function
Optional built-in backup battery kit, 48V/7Ah
Optional redundant AC/DC power supply
Internal 2-Way-Hybrid Combiner
Base Station Controller
Optional redundant BSC
Tower Mounted Amplifier (TMA), external
GPS receiver built-in for synchronization
8 HU version
Measures (HxWxD): 476,6x542x520 mm
Weight: 47 kg (fully equipped)
Power Consumption: 280 Watts (fully equipped)


CTS200
1-4 TETRA-Carriers/Transceivers
AC/DC power supply including external battery charge function
Terminal for external backup battery kit
1 4-Way-Cavity Combiner
Base Station Controller BSC
20 HU version
Measures (HxWxD): 1010x542x520 mm


CTS300
1-8 TETRA-Carriers/Transceivers
AC/DC power supply including external battery charge function
Terminal for external backup battery kit
1 or 2 4-Way-Cavity Combiners (1 each for 4 carriers)
1 Base Station Controller BSC
35 HU version
Measures (HxWxD): 1587x542x520 mm

4.2.2. CTG-1 Gateway Server

The Gateway Server is the interface between the TETRA network (E1-ring) and the Dispatcher
Workstations, PABX/PSTN and the IP-Network for Packet Data transfer. From the internal network
point of view the Gateway Server is just an additional node in the E1 ring. In addition, the Gateway
Server holds all the log files of the entire system.
Gateway Server
IP Network for:
Packet Data
SDS Transport
Future APIs
(e.g. billing, provisioning…)
Built in Interfaces:
1 or 2 E1-Links to the base stations
ISDN BRI card (4xISDN = 8 Lines) to connect PABX/PSTN subscribers to the network
1 x 100Mbit Ethernet interface to connect 1- 8 Dispatcher Workstations
1 x 100Mbit Ethernet interface to connect IP-based packet data and SDS-Transport
applications to Data LAN (planned to extend to provide further APIs (billing, provisioning etc)

4.2.3. CTD-1 Dispatcher Workstation

The Dispatcher’s work is among others to co-ordinate the communication of people and teams from a
command and control center. To do this, a dispatcher carries out individual calls, group calls and
sends and receives SDS messages.
The Dispatcher video screen provides graphic elements for easy operation:
The Dispatcher workstation comprises the following items and interfaces:
Personal computer including 17”-TFT-monitor and audio accessories for radio

communication.
Ethernet interface 100MBit/sec for connection to the Gateway PC.
Keyboard and mouse to operate the states of the dispatcher application program
Monitor loudspeaker to observe speech communication of monitored groups. The speech is

presented as mixed signal
Headset or handset to communicate to the currently focused call
External PTT

4.2.3.1. Dispatcher Workstation operation modes:

(Please see the user guide for the dispatcher >Section 5< for more information.)
Dispatching
Co-ordination and monitoring of mobile users and groups of mobile users:
Handle several Individual Calls in parallel
Monitor and participate in up to 5 Group Calls in parallel
Send and receive Status SDS messages
Send and receive Text SDS messages
In addition each dispatcher logs the contents of the messages sent and received at the workstation.
The dispatcher application provides a high-level health information about the base stations and the
network connectivity.
Subscriber management
With this application mobile users and groups of mobile users authorization to use the network will be
defined.
Network management and monitor

This task includes the configuration of all the sites, the interfaces to the E1 network, the ISDN and
Packet Data interface. The system management application allows to the software update of the base
stations. The Monitoring window provides detailed information about the operational status of all
system components, the traffic load and displays the system alarm messages.

4.2.4. TETRA Mobile Stations

This paragraph is a brief overview about Motorola TETRA subscribers. More info can be downloaded
via Motorola Online System.
At present Motorola offer the following subscribers for the Compact TETRA System:
MTH300 Small Portable, 410-430Mhz
MTP700 Rugged Portable, 380-430Mhz, 806-870MHz
MTM700 Mobile, 380-430Mhz, 806-870MHz
Planned for mid 2002:
MTH500P Very Small Portable, 380-400Mhz, 410-430MHz and 800Mhz
Common feature of MTM/P700 and MTH500 (same Software Platform and User Interface):
One to one calls Group calls Phone calls
Simplex/duplex TMO – within the network Simplex/duplex

Dial the number DMO – outside the network Dial the number
Search the phonebook High capacity, 700+ groups Search the phonebook
Last dialled Caller Identity Last dialled
Missed calls Scanning with priority Missed calls
Caller Identity
Speakerphone
Note: Not all features offered for subscribers are available in Compact TETRA Systems

4.2.4.1. Cross Reference List Compact TETRA vs. Motorola Subscriber

Some Features available in Subscribers are not supported by Compact TETRA or will be supported in
a future Release of Compact TETRA (R1/2/3)
FEATURES SUPPORTED from Release1 Compact T. Motorola Subs.

Semi Duplex Individual Call
Mobile to mobile R1 available
Mobile to Dispatcher R1 available
Mobile to PSTN N/A N/A
Dispatcher to Mobile R1 available
Dispatcher to Dispatcher R1 available
Dispatcher to PSTN N/A N/A
Ext Subscriber to Mobile R1 available
Ext. Subscriber to Dispatcher R1 available
Ext Subscriber to Ext Subscriber N/A N/A
Full Duplex Individual Call
Mobile to mobile R1 available
Mobile to Dispatcher R1 available
Mobile to PSTN R1 available
Dispatcher to Mobile R1 available
Dispatcher to Dispatcher R1 available
Dispatcher to PSTN R1 available
PSTN to Mobile R1 available
Ext. Subscriber to Dispatcher R1 available
Ext Subscriber to Ext Subscriber N/A N/A
Group Call (always Semi Duplex)
Mobile to mobiles R1 available
Mobile to Dispatchers R1 available
Mobile to PSTN N/A N/A
Dispatcher to Mobiles R1 available
Dispatcher to Dispatchers R1 available
Dispatcher to PSTN N/A N/A
Ext Subscriber to Mobiles N/A N/A
Ext. Subscriber to Dispatchers N/A N/A
Ext Subscriber to Ext Subscribers N/A N/A
Late entry R1 available
SDS Facility
Type 1 R1 available
Type 4 (inbox/Outbox from Display + PEI support) R1 available
TIP V1.0 R1 available
PABX Call R1 available
Dispatcher Call R1 available

FEATURES SUPPORTED LATER Compact T. Motorola Subs.

Cell reselection/Call restoration R2 available
Single Slot Packet Data R2 available
Emergency (Pre-Emptive for group calls only) R2 available
CLIP R3 available
TPI R3 available
DTMF Overdial R3 available
FEATURES NOT SUPPORTED – later implementation on demand Compact T. Motorola Subs.
DGNA Candidate R3/4 available
Static Air Encryption N/A available
Attachment Scanning N/A available
Authentication Candidate R3/4 available
Talk Group Scan Candidate R3/4 available
Radio Enable/Disable (Stun) from Dispatcher Candidate R3/4 available

4.2.5. Portable Radios

4.2.5.1. MTH300
Features:
Designed for Group Calls, Telephony and Data functionality
DMO Mode
Looks and feels like a cellular phone
Small, compact and lightweight
Conveniently located Press To Talk (PTT) switch
Large front mounted 4 x 12 character display (back-lit)
Soft keys for menu driven facilities
Key Specs:
410-430 MHz
1 Watt RF Power
0.5 Watt loudspeaker volume
-112 dBm Receiver sensitivity
Up to approx. 24 hours operational use (depending on battery type)
Approx. 205 g. incl. ultra slim battery
Environmental Protection
-20 to +55ºC operating temperature range

4.2.5.2. MTP700
MTM700 TETRA Portable
General
Dimensions (HxWxD) 138 x 33 39 mm with standard Li Ion Battery
Weight 360 g with standard Li Ion Battery
Battery Options 900 mAh Light Li Ion
1100 mAh Standard Li Ion
1200 mAh NiMH
Usage rate (Tx / Rx / Standby) with standard Li Ion battery
5/5/90 24 hours
5/35/60 15 hours
TMO Talkgroups 512
DMO Talkgroups 208
Individual call list 100
Phone call list 100
Text message list 20
Status list 100
Environmental
Operating temperature -30 - +60 Celsius
Storage temperature -55 - +85 Celsius
Humidity EIA/TIA 603 (95%)
Dust and water IP54
Shock and vibration MIL810 C/D/E
RF specifications
Frequency Bands 380 - 430 MHz 806 - 870 MHz
Transmit Band 380 - 430 MHz 806 - 825 MHz
Receive Band 380 - 430 MHz 851 - 870 MHz
DMO Band 380 - 430 MHz 851 - 870 MHz
RF Channel Bandwidth 25 kHz 25 kHz
Transmitter/receiver separation 10 MHz 45 MHz
Transmitted RF power 1 Watt 1 Watt
RF power control 4 steps of 5 dB 4 steps of 5 dB
RF power accuracy +/- 2 dB +/- 2 dB
Receiver class B B
Receiver static sensitivity -112 -112
Receiver Dynamic sensitivity -103 -103
Controls, switches, interfaces and

buttons
On/off volume knob
16 position or continuous rotary - talk group
knob
Orange top emergency button
Tri colour top LED
PTT button
3 programmable side buttons
2 soft key buttons
4 way navigation key
Menu button
Mode button
Hook on/off button
Full 3*4 keypad
Backlit display with Icons
Side connector for audio accessories
Bottom connector for programming, upgrading, Vehicle adaptor
PEI interface for applications like packet&short –data services.

4.2.5.3. MTH500P
Same software feature as MTP/M700 radios
Key Benefits:
RF of 1 Watt RF Output
Weight : 193g
Slim Ergonomic Design
2 bands planned to be available mid 2002:
–380-400 Mhz
–410-430 Mhz

4.2.6. Mobile Radios

4.2.6.1. MPM700
MTM700 TETRA Mobile
General
Dimensions -Transceiver (HxWxD) 48.5x169.5x155 mm
Weight –Transceiver 1350g
Dimensions -standard control head
(HxWxD) 72x185x53 mm
Weight -Standard Control head 300g
Configurations Dash mount, remote mount,
motorcycle mount, desk top and data
box –configurations
Talk Groups – TMO 512
Talk Groups – DMO 208
Talk group selection Up/down navigation keys
Volume selection On/off -volume knob
Individual call list 100
Phone call list 100
Text message list 20
Status list 100
Environmental
Operating temperature -30 - +60 Celsius
Storage temperature -55 - +85 Celsius
Humidity EIA/TIA 603 (95%)
Dust and water (standard radio) IP54
Dust and water (Motorcycle version) IP57
Shock and vibration MIL810 C/D/E
RF specifications
Frequency Bands 380 - 430 MHz 806 - 870 MHz
Transmit Band 380 - 430 MHz 806 - 825 MHz
Receive Band 380 - 430 MHz 851 - 870 MHz
DMO Band 380 - 430 MHz 851 - 870 MHz
RF Channel Bandwidth 25 kHz 25 kHz
Transmitter/receiver separation 10 MHz 45 MHz
Transmitted RF power 3 Watt 3 Watt
RF power control 4 steps of 5 dB 4 steps of 5 dB
RF power accuracy +/- 2 dB +/- 2 dB
Receiver class B B
Receiver static sensitivity -112 -112
Receiver Dynamic sensitivity -103 -103
Controls, switches and buttons (standard control head)

On/off volume knob
Orange emergency button
3 LEDs
3 programmable buttons
2 soft key buttons
4 way navigation key
Menu button
Mode button
Hook on/off button
Full 3*4 keypad
Backlit display with Icons
PEI interface for applications

5. System Description
This description of the Compact TETRA system is to be read in conjunction with the other sections of
the Product Manual. Please see also the documentation we hand out during the trainings courses.
5.1. System Architecture and Networking

The following chapter provides an overall understanding only. The protocols and other details
of the interfaces are proprietary!
5.1.1. System elements

Transceiver:
It handles one TETRA AI carrier composed of a frequency pair (uplink / downlink).
Base Station:
It handles a single TETRA cell and all layers of the TETRA AI. A BS consists of up to 8 transceivers,
one Base Station Controller, an antenna subsystem, and supporting infrastructure (racks, power
supply, etc)
Gateway Server:
It is the interface between the TETRA network, external networks (PABX/PSTN and data networks)
and Dispatchers. It is responsible for the voice transcoding and interworking at upper network layers.
From the internal network point of view the gateway is just an additional node in the E1 ring.
Dispatcher Workstation:
This is a specially equipped PC that primarily serves the dispatcher user for co-ordinating mobile
users. It provides extended capabilities to:
Monitor and participate in multiple group activities
Voice and SDS access to the TETRA network
Additionally the Dispatcher Workstation provides access to the system management and
subscriber management interfaces:
View and update static and dynamic data of the system
Monitoring and maintenance of system
Standalone Configuration PC:

This can be any PC containing Windows Netmeeting that provides access to the system management
and subscriber management interfaces for standalone systems.

5.1.2. Real World Object Model

The following figure shows the system components and their interfaces. A circle indicates the system
boundary. Objects within the circle are part of the distributed system (some of them are optional).
Objects outside the circle are not part of the system and are referred as actors in system use cases in
the capability section.
Double ended arrows denote logical interfaces whereas physical interfaces are straight connections
between objects. Interfaces that cross the system boundaries are open and committed to Application
Partners or Customer (licensed). The structures of internal interfaces are proprietary.
AI
Mobile
Monitoring or
Transceivers Voice Recorder - IF
S
Transceivers
External
Base Station Subscriber
it E1 link
e
Base Station
E1 link
ISDN T0
or
2Mbit
PSTN or
PABX
Transceivers
s E1 link
SDTS-IF
L
Base Station T -I
F
E1 link PD-IF
L/T- IF
M N -I F -I F Billings - IF
-
IF
MNT
L /T DA Gateway PC External Server

Ethernet
Ethernet Ethernet
Stand-alone
Configuration PC Disp HMI
Dispatcher Dispatcher Dispatcher

Workstation Workstation Workstation
Dispatcher - IF
Real World Object Model and System Interfaces
Paragraphs 5.1.1 to 5.1.9 give a short description of the elements, interfaces and actors of the model.
Paragraph 5.1.10 explains the 3 types of system configurations and outlines the available system
features.

5.1.3. System Networking
5.1.3.1. E1 network
As seen in the Real World Object Model the Base Stations and the Gateway Server are connected by
using 2 MBit E1 links (G703/G704). The specs for the E1 connection and the formula to calculate the
fractions on E1 are detailed in section 5.6.1.
The E1-lines carry:
TETRA-encoded speech within 32kBit/s timeslots (one timeslot contains up to four speech
channels from a single receiver)
Signaling data for internal communication among the processes of the distributed application
(point-to-point & broadcast)
IP-packets
Both speech and data are transmitted redundantly in both ring directions.
Redundant data are filtered at the receiver.
S ite 1 S ite 2 S ite 3
Line break
//
1+2+3
E1 ring – also transports data to each Site

if one Line is broken
E1 Ring
1 2+3

5.1.3.2. Dispatcher network
This is a dedicated Fast Ethernet connection from the Gateway Server to the Dispatcher.
In terms several (up to 8) Dispatcher Workstations are used a hub has to be installed to distribute data
from the Gateway to the Dispatcher Workstations.
As there is also Voice of IP transported via this network only high quality Hubs should be used.
Recommended is the HP Procurve 2512 Hub.
For the cabling standard Ethernet (75/120 Ohm) CAT 5 cables with J45 connector are required.

5.1.4. Distributed Architecture

Compact TETRA does not use a large, centralized Switch but has implemented a Base station
Controller in each Base station. The Gateway Server provides the interfaces to Telephony and
Dispatcher Workstation as well containing an SDS Transport and Packet Data Gateway.
The Base stations and the Gateway are logical nodes connected via E1 highway.
5.1.4.1. Signaling Path through the System
Base Station Base Station Gateway PC
Base Station Applications Gateway Applications
HDLC IP ISDN IP
Tetra Stack
PABX/PSTN
PDG
Dispatcher
Dispatcher
HDLC Applications
IP
AI
E1 100Mbit/s Ethernet

5.1.4.2. Voice Path through the System
Tetra voice packets are expanded to an 8 kBit/s stream in the MAC. They are routed through the base
station, between the base stations and to the Gateway in sub slots of 64 kBit/s channels.
The E1 daisy chain provides a logical highway of 8kbit/s sub-timeslots that have globally unique
names. The sites and the Gateway PC are connected to the highway. Each Tetra AI uplink traffic
channel and each source channel from the Gateway PC is statically switched to one sub-timeslot of
the highway.
The globally unique names of the timeslots are signalled over the inter-site protocol as part of the call
set-up and call maintenance signalling. Each node locally switches the timeslot from the highway to
the AI for speech transmission on the downlink.
For communication with dispatchers and external telephone networks, speech is transcoded into
G.711 format on the Gateway PC.
Between the Gateway PC and the dispatchers voice is exchanged in IP packets.
Over the PABX/PSTN Gateway, speech is transferred in G.711 format in B channels.
Transceiver Transceiver Transceiver
AI MAC AI MAC AI MAC

8bkit/s
8bkit/s
8bkit/s
coded
coded
coded
Tetra
Tetra
Tetra
BSC BSC BSC
E1 E1 E1
MIC LS HS
8kbit/s Tetra coded in E1 sub-timeslots
Gateway PC Dispatcher PC
E1
card
Pentium Pentium
H.100
DSP Analogue
ISDN VoIP VoIP
Tetra I/O
card
codec
Packetized G.711 over Packetized G.711 over

PCI PCI
G.711
Ethernet Ethernet
card card

5.1.4.3. Distributing Configuration Data
System configuration data is based on simple text files that are editable with e.g. the Notepad editor or
Excel for comma separated files. These files shall be placed centrally as master copies at a well-
known directory in the Gateway Server where backups are possible.
The following two mechanisms ensure that the management information is system-wide consistent
after some time and standalone operation of a Base Station is possible when the connection to the
Gateway Server over the Intersite Network is lost at any time. Moreover this enables to change
configurations locally at one Base Station for test purposes:
Each Base Station holds a local copy of the files, which it requires for standalone operation. At start-
up, and in regular intervals during operation, the TETRA Application watches the actuality of its local
copies against the master copies. When it encounters an outdated local copy the TETRA application
updates the local copy with the master copy.
At start-up the TETRA Application reads the information from its local management file copies. During
operation it continuously watches the local file copies. Whenever a local file is changed the TETRA
Application reads in the new information and adapts its internal status accordingly.
Base Station Z
Base Station Y
Base Station X Gateway PC
TETRA Application TETRA Application
File System File System
Configuration Configuration
Data X Data Z
Configuration
(Local Copy) (Master Copy)
Data Y
Configuration
(Master Copy)
Data X
(Master Copy)
Subscriber Data Subscriber Data

(Local Copy) (Master Copy)
Intersite Network

5.1.5. Logging / Tracing Data

Logging / Tracing information is stored in plain text files locally at the system component where the
recorded event occurred.
There are separate files for:
Call Logs, recording information about the establishment of individual and group calls
Mobility Logs, recording information about the registrations and location updates of
subscribers
SDS logs, recording information about the transport of SDS messages
All logged events are recorded with a timestamp of the occurrence.
When events are interrelated over several system components, then they are correlated over a
common identifier, e.g. a system-wide unique call ID.
Log files are rotated in regular intervals to allow deletion of older files.
Rotation may also be triggered on demand by a signal to the logging process.
The log-files in the Base Station are volatile (on a RAM-disk). After a Base Station breakdown or
reboot all log-files are lost if not saved elsewhere.
5.1.5.1. Call Log-Records

Each record contain the following data:
• Establishment time and date

• Calling Party ISSI
• Called Party ISSI
• ESN if a Gateway User is involved in the call
• Call Type {SDIC, FDIC, GC}
• Result {failed, established}
• Call Duration
• Priority
• AI Queuing Time
• Call ID
The Call Mode {single-site, multi-site} attribute can be derived by other means:
The Call Mode can be derived from the existence of log-entries in two or more Base Station log-files
with the same call ID and overlapping duration.
Due to the limited space in the Base Station the maximum number of log-records at the Base Station
is 10 000.
5.1.5.2. Mobility Log-Records

Registering subscriber’s ISSI

Time and date of the registration
Result {rejected, accepted}

The Location can be derived from the file where the record is stored.
5.1.5.3. SDS Log-Records

Sending ISSI
Destination SSI
Time and date of the transmission
SDS Type {status, text}
Size of the SDS in bits
Result {rejected, transmitted}
5.1.5.4. PD Log-Records
Sending ISSI
Destination SSI
Time and date of context activation and deactivation
Number of transferred bytes
5.1.6. Monitoring of System Parameters

The system provides a GUI to access vitality and performance parameters.
5.1.7. Interfaces
Air Interface:
TETRA standard air interface with and partial functionality support.
E1 link:
Each BS may be connected to 1 or 2 other BS or the Gateway Server via 2Mbits E1 links. That means
the topology we use is either ring or Daisy Chain. The structure within the E1 links is proprietary to the
system.
Dispatcher Access Interface:

The Dispatchers are connected to the Gateway Server. The mode of the connection is to be defined in
the design phase.
Configuration Interface:
This is a logical interface that provides the possibility of changing system parameters and static data
Monitoring Interface:
This is a logical interface that provides monitoring the status of the system and its sub elements.
Logging and Tracing Interface:

This is a logical interface through which information about the usage of the system can be obtained:
Call logs, listing calling and called party with timestamp and duration

Mobility logs, listing the movements of mobiles
SDS logs, listing sender and receiver with timestamp for user defined messages
Dispatcher User Interface:

The HMI the human Dispatcher interacts with. It displays the actual states of selected ongoing calls,
the messages addressed to the Dispatcher, etc. It sends instructions given by the Dispatcher to the
system.
Packet Data Interface:

This interface provides IP connectivity from mobiles to an external IP network with access to some
external applications. The interface is equal to Motorola’s Compact TETRA Packet data gateway.
SDS Transport Service Interface:

This interface provides SDS transport to/from mobiles from/to an external server via a TCP
connection. The interface is equal to Motorola’s Compact TETRA SDS Transport gateway.
PSTN/PABX Interface:
This interface links the TETRA network to a public or private telephone network. It provides individual
voice calls between TETRA network subscribers and external subscribers.
5.1.8. Actors
Mobile:
Ordinary TETRA mobile which connects to the system over AI. It can be used for voice
communication, sending status or text SDS messages, or connecting a data application to the system.
Dispatcher:
The user of the Dispatcher workstation. He/She primarily co-ordinates mobile users.
External subscriber:
Everybody who connects to the system via the PSTN/PABX interface of the Gateway Server.
Operator:
He/She collects information about the system health and usage, and does first level troubleshooting.
Maintainer:
He/She configures the system parameters, maintains hardware elements, installs new hard- and
software, and does second level trouble-shooting.
Packet Data Application:

This application uses the system as an IP sub-network to route IP traffic to/from a mobile application.

5.1.9. Service Matrix

This section provides information about the call types possible between different actors. For detailed
specifications, refer to Paragraph 5.2.
1
Calling Actor Called Actor FDIC SDIC UGC CLIP TPI
Mobile Mobile Y Y Y Y Y
Mobile Dispatcher Y Y Y Y Y
Mobile ISDN Y N N Note1 N/A
Dispatcher Mobile Y Y Y Y Y
Dispatcher Dispatcher Y Y Y Y Y
Dispatcher ISDN Y N N Note1 N/A
ISDN Mobile Y N N Note1 N/A
ISDN Dispatcher Y N N Note1 N/A
ISDN ISDN N N N Note1 N/A
Service Matrix for Calls (informative)
FDIC Full Duplex Individual Call
SDIC Semi Duplex Individual Call
UGC Un-Acknowledged Group Call
CLIP Calling Line Identification Presentation
TPI Talking Party Identification
LE Late Entry
Note 1: Calling-Party information is interworked at the gateway. Actual availability

of the information to the end user also depends on capabilities of external
equipment that are outside the scope of this document.
Type of connection LE Call restoration

Mobile-Mobile FDIC N/A Y
Mobile-Mobile SDIC N/A Y
Mobile-Ext.subscr. N/A Y, mobile
Mobile-Dispatcher FDIC N/A Y, mobile
Mobile-Dispatcher SDIC N/A Y mobile
Dispatcher-Dispatcher N/A N
Dispatcher-Ext.subscr. N/A N
Mobile-Group Y, mobile Y, mobile
Dispatcher-Group Y, mobile Y, mobile
Additional Services for Voice Calls (informative)
1
TPI is only available for semi-duplex calls (SDIC and UGC)

Calling Actor Called Actor SDS Packet data (Rel.2)

Mobile Mobile Y Y
Mobile Dispatcher Y N
Mobile SDS gateway Y N
Mobile Group Y N
Dispatcher SDS gateway Y N
Dispatcher Mobile Y N
Dispatcher Group Y N
Dispatcher Dispatcher Y N
SDS gateway Mobile Y N
SDS gateway Dispatcher Y N
SDS gateway Group Y N
Dispatcher PDG N N
Mobile PDG N Y
PDG Group N N
PDG Mobile N Y
PDG Dispatcher N N
Service Matrix for Data (informative)
5.1.10. System Configurations
5.1.10.1. System Configuration Overview

The system is available in three configurations, starting from a small non-redundant single site Stand-
alone system to a fully redundant network of up to eight Base Stations, supporting eight Dispatcher
Stations and a Packet Data Gateway.
The system can grow with customer demands. Customers can start out in one configuration and later
extend the system to meet additional demands. The System Partners can administer this
configuration.
Item Stand-alone Single Site Multi Site, Multi Site,

open chain closed
chain
Transceivers per BS 1–8 1–8 1–8 1–8
BS per system 1 1 2–8 2–8
Transceiver per system 1–8 1–8 max. 32 Max. 32
Gateway Server 0 1 1 1
Dispatcher Workstations 0 0–8 0–8 0–8
Subscribers per system 2.500 2.500 10.000 10.000
4 x 2 B+D ISDN Interface No Yes Yes Yes
provide 8 PABX-channels
Packet Data Interface No 1 1 1
SDS Transport Interface No 1 1 1
Tolerance against Link N/A No No Yes
Failures
Overview of System Configurations
Note: Multi-site capability from Release 2

5.1.10.2. Standalone System

A standalone system offers a single Tetra Base Station with up to 8 carriers that can be operational
without any external equipment. It supports a user base of up to 2,500 subscribers. All 2,500
subscribers can be registered at any one point in time.
This system configuration is envisaged for customer installations needing local Tetra coverage without
dispatch functionality and gateways and has no stringent availability requirements.
For configuration of the system, a configuration terminal can be connected to the Base Station via a
LAN. This configuration terminal provides the monitoring interface, the configuration interface, and the
subscriber management interface.
For on-line monitoring of the system health and load conditions, the configuration terminal needs to be
permanently attached to the system.
All log-files are stored locally at the Base Station. Due to the limited space the files must be
downloaded periodically to avoid a loss of data. The download period depends on the system load
and may be in the range of 30 to 60 minutes. If the configuration terminal is connected to the system,
it will automatically download the log files.
Because this system configuration requires no supporting infrastructure other than a power supply,
the stand-alone system is especially suited for "quick dispatch" applications.
5.1.10.3. Single-Site System

The single-site system offers all the features of the stand-alone system, and additionally offers:
Connection of up to eight Dispatcher Workstations

Speech Gateway for full-duplex individual calls
Packet Data Gateway
SDS Gateway
On-line monitoring and control of system status and health, integrated into the Dispatcher
Workstations.
Integration of the subscriber management user interface into the Dispatcher Workstations.
The single-site system is targeted primarily at customers who need local Tetra coverage and
additionally dispatch functionality and/or gateways. The connection between the Site and the Gateway
Server is a single fractional E1 link. For the maximum of 8 carriers with full-bandwidth packet data
handling, the system needs eight timeslots on a fractional E1 link for packet data. If voice is used too
4 additional time slots are necessary.
5.1.10.4. Multi-Site System

The Multi-site system offers all features of the single-site system and additionally multi-site individual
and group calls, including call restoration of all kinds of individual and group calls. An intelligent
paging strategy conserves air interface resources, yet ensures that subscribers are reachable for
group communications at all sites.
The multi-site system supports up to 10,000 subscribers. All of which can be registered at the system
at any one point in time. The system tracks the location and group attachment status of the registered
subscribers in a distributed database that allows fast local access to the information on call set-up.

The multi-site system uses a chain of E1 links for interconnecting the sites. For reduced cost of
ownership, smaller system configurations can use fractional E1 using multiplexers from the E1-link
provider. The system can be configured to limit the E1 time slots used for communication to a certain
range.
The chain of base stations can either be open, or closed with one additional E1 link. This additional
link affords system fault-tolerance against single link failures: Even when one of the links fails, all
system services will continue unimpaired.
Even in the open-chain configuration, the multi-site system features graceful degradation in the face of
link failures. If the network is partitioned, each of the sub-networks will continue to function and allow
unhindered communication between all subscribers in that sub-network. The speech transmission will
be interrupted for max. 1 second during switchover.
If the network becomes reconnected, the system will automatically recover the status information
within 10 minutes. During that time the base stations stays in operation, but services may fail due to
outdated data.
5.2. System Capacity and Performance
5.2.1. Dimensions
The smallest system consists of 1 Base Station with 1 Transceiver.
From Release 2 the system can operate with up to 8 Base Stations. The number of transceivers may
vary from 1 to 32 but a maximum 8 transceivers can be connected to one Base Station at the same
time.
The maximum number of Dispatcher workstations connected to the system is 8. They can access
operational and management functionality of the system. The system is able to operate in standalone
mode, without any Dispatchers connected.
The system supports 8 simultaneous duplex voice calls over the ISDN-Card including 4x 2B+D ISDN
interfaces.
Dispatcher workstations and regular networks are connected to the system through the sole Gateway
Server.
A single-site system supports a maximum of 2,500 subscribers.
A multi-site system supports up to 10,000.
Each Base Station forms an own location area (LA).
A Base Station provides one MCCH and does not use common secondary control channels (Common
SCCH) for Voice and SDS call. For packet data assigned secondary control channels are used
(Assigned SCCH).

5.2.2. Speech delay

The total speech delay in one call is dependent of the subscriber equipment, the delay on the E1 links
and the delay in the external ISDN network (if applicable for this type of call). In order to define the
design goal the following assumptions are made:
Measurements start when the speech enters the system (either via air interface, ISDN or the
Dispatcher microphone) and ends when the speech leaves the system.
The delay on the E1 links is neglected (such delays could be added by equipment of a provider
network, worst case is 8 times the E1 delay).
The internal one-way speech delay is less than 300 ms for all types of calls within the system.
The internal one-way speech delay is less than 200 ms for all types of single-site calls.
The internal one-way speech delay for PABX/PSTN calls is less than 270 ms.
5.2.3. Echo cancellation

According ITU-T Recommendation G.131 echo cancellation shall be deployed on all connections that
exceed the total one-way echo transmission path time of 25 ms. At the ISDN gateway an echo
cancellation is foreseen. The echo canceller is necessary to attenuate the echo that may be caused
by signal reflections from external equipment connected to the ISDN gateway. The maximum echo
path delay, which the echo canceller expects is 25 ms. The echo loss, is at least 46 dB during single
talk.
5.2.4. Analogue audio

The analogue I/O of the dispatcher has to match the internal level plan (-15 dBm nominal level).
The audio frequency response of the analogue I/O of the dispatcher shall be at all frequencies from
300 Hz to 3400Hz within +1/-3 dB of the response recorded at 800 Hz

5.3. System Availability and Resilience

5.3.1. Failure Tolerance
This section describes the system behaviour for major failure scenarios.
5.3.1.1. Failure of a Traffic Transceiver

The system will free all resources associated with the failed transceiver. The Base Station will not use
the Transceiver in further communication.
The base station remains in operational state and an error log entry is produced.
If the Base Station encounters a missing Transceiver at start-up (checked against configuration data)
an error log-entry is produced.
5.3.1.2. Failure of the MCCH Transceiver

The system will free all resources associated with the failed transceiver. The Base Station will not use
the Transceiver in further communication.
The Base Station will assign the MCCH to one of the remaining Transceivers, reconfigure all
Transceivers accordingly and resume operation. An error log-entry is produced. All local registrations
and all communication at the Base Station are lost due to these actions.
5.3.1.3. Failure of Base Station Controller

nd
In case of failure of the Base Station Controller the TETRA application will start up with the 2 Base
Station Controller and reintegrate into the system without manual intervention. All local registrations
and all communication at the Base Station are lost due to these actions. The switchover shall take
place in less than 5 minutes.
5.3.1.4. Failure of a Power Supply within a Basestation

In this case redundant Power Supply would take over supply of power for the basestation. All Power
Supplies installed in a Basestation always are operational in parallel. If a redundant one is installed it
also would run in parallel and would decrease the power generated from the other Power Supplies.
This leads to a lower risk of failure, as all Power Supplies then do not operate to their maximum
capabilities.
5.3.1.5. Failure of one complete Basestation or part of the E1 network

This means that the network structure changes from a closed chain to an open chain.
All other network nodes (BS) remain in operational state. All communication which involved the failed
node is either continued or terminated depending on rules for valid constellation that are applied by
the remaining nodes:

An individual call is considered valid as long as the peer network node is reachable in the network.
A group call is always considered valid and continues. If the transmitting party was located at the
failing node the transmission permission is withdrawn and the transmission status turns to idle.
For the remaining calls the speech transmission will continue within at least 1 second.
5.3.1.6. Partition of Network

All network nodes (BS) remain in operational state when some other nodes rejoin the network. All
internal databases will converge to a consistent state within finite time after reintegration.
The system will return into a consistent state 10 minutes after the reintegration.
5.3.1.7. Start-up without Connection to Gateway Server

This scenario is also known as “local site fallback”.
A Base Station that has no connection to the Gateway Server at start-up will enter operational state
with local configuration data.
5.3.1.8. Failure of Gateway Server

Failure of the Gateway PC causes unavailability of dispatching, monitoring, and gateway functionality
like access to PABX, Packet Data and SDS Gateway. The sites continue to operate normally and are
able to handle mobile-to-mobile calls without interruption. Also Intersite communication is still possible
as long as the Base Stations are connected via E1 link.
The operator should exchange the Gateway PC with an identically configured stand-by component.
Operators have to restore system configuration and subscriber data from backup media.
5.3.2. Other aspects of availability of communication

5.3.2.1. Direct Mode Operation
Direct Mode Operation (DMO) is a mode of operation, defined in the TETRA standard, which allows
Mobile Stations (MS) communicate directly with each other without using any infrastructure. DMO can
be considered a fallback mode of operation that lets MSs remain in communication in the event of loss
of service from the infrastructure. DMO can be used provided the MSs have been configured for DMO
(that is, channels have been defined in the frequency plan and have been programmed into the MSs)
and the MSs wishing to communicate are close enough to provide adequate signal strength.
Data services (is SDS and PDS) are not available in DMO mode.
5.3.2.2. Multiple Antennas

The antenna is one is the system elements most vulnerable to the environment. High winds, ice and
water can cause antenna failures. Replacement of a defective antenna may be delayed for several
reasons:

Other services on the antenna mast may require turning off before the repairperson is permitted to
climb the mast. This may require significant coordination and may only be possible during certain
maintenance windows
Poor whether conditions may affect access to the antenna (e.g. road impassable, poor visibility for
helicopter–access only sites, high winds for climbing on the mast). There is also some correlation
between these conditions and antenna failure in the fist place.
The receive path will generally have some redundancy because of the Rx antenna diversity. However
the failure of the antenna is not statistically independent for each Rx antenna. For example, ice or a
lightning strike could well affect all of the Rx antennas. The TX antenna is most likely to cause
outages because there is no redundancy.
5.3.3. High availability due ease of maintenance

The design of the Compact TETRA keeps it easy to maintain the system:
The system will autonomously monitor its health status, including the status of the links.
System configuration and monitoring are accessible centrally.
Continued service within sub-networks that result from E1 Link breakdowns. The special case
of one cut-off base station is also known as „ Local Site Fallback“.
Automatic and consistent reintegration of such sub-networks.
Remote software download from the Dispatcher Workstation to the Base Station avoids costly
on-site maintenance.

5.4. System Features

5.4.1. System Features Overview
In the table below features are listed supported by Compact TETRA.
Not all features are available from the beginning. Therefore in the first column the release number of
introduction is displayed.
Rel Feature / Description Details in

Function Paragraph
R1 Individual Call Full duplex and semi-duplex calls from and to mobile 5.4.2
stations, dispatchers and telephone subscribers
R1 Group Call Semi-duplex call from and to mobile stations and 5.4.3
dispatchers
R1 Late Entry Group The D-Setup message of the group call is sent over the 5.4.3.5
call air periodically during the lifetime of the call, users that
were not originally in the group call can join the call as
they become available
R2 Dynamic Paging An intelligent paging strategy activates only those base 5.4.3.6
Area for Group station where the mobile stations are located
Calls
R1 Pre-Emptive Priority Emergency call from a MS to a Group and Dispatcher. In 5.4.6
Group Call case of lack of resources a call with lower priority will be
disconnected
R1 Call Queuing Call will get through without the end-user having to retry 5.4.2.7
if the network is busy - high quality of service
R2 Cell Reselection This system feature of TETRA lets a mobile roam 5.4.11
and Call between cells while engaged in a call without releasing
Restoration the call. 5.4.12
R1 SDS Short Data Services using pre-defined text messages or 5.4.14
alphanumeric text with up to 140 Characters using the
Main Control Channel (MCCH). Text according to 5.4.15
ISO/IEC 8859-1 Latin.
R2 Packet Data Single slot packet data using the traffic channels to 5.4.17
connect the mobile stations to IP based 3rd party
applications
R1 Extended Call If required the call timer can be set to infinite
Timer
R1 CLIP and TPI Calling Line Identification Presentation. The identification 5.4.18
(limited) of the calling party will be shown at the mobile station of
the called party (not via ISDN)
R2 Fractional E1 In order to save cost on smaller systems only a fraction 5.6.1
of the 2 MBit E1 link need to be assigned to the
infrastructure
R2 Remote SW New SW-releases can be downloaded from the
download Dispatcher/Network Mgmt workstation to the base
stations. No need to visit the site for SW upgrades.

5.4.2. Individual Call

An individual call provides point-to-point speech communication between two subscribers.
Communication may be full-duplex or half-duplex depending on the capabilities of involved mobiles.
Actors: Mobile, Dispatcher and PABX/PSTN User
Servicing subsystems: Base Station, Dispatcher Workstation, and Gateway Server
System Mode: Operational
Preconditions: The participating actors are registered at the system.
Post condition: All system resources allocated during the individual call are freed
again. A call-log entry has been produced.
5.4.2.1. Behaviour to a Calling Mobile

At the AI the system provides the individual call set-up procedure as specified in ETSI specs. The
called party is identified by an ISSI – this means that a called dispatcher is also identified by an ISSI.
The system supports half-duplex and full-duplex connections depending on the calling mobiles
choice. In case of a simplex call the first transmission will be granted to the called party.
The system can modify the call from full duplex to half-duplex depending on the called party’s
abilities.
Hook method ’direct through connect’ is not supported.
A telephone call is initiated by sending a U-Setup containing the configured external gateway ISSI
and filled external subscriber number field (ESN).
If the Mobile initiates the telephone call as simplex connection the system modifies the request and
offers duplex. If the Mobile doesn’t support the duplex connection it does disconnect the call.
The system provides DTMF overdial for telephone calls.
5.4.2.2. Behaviour to a Called Mobile

At the AI the system provides the individual call set-up procedure as specified in ETSI specs. The
system supports simplex and duplex connections.
The system will accept a request to modify the call type from duplex to simplex from the called
mobile. The system will then propose that modification to the calling party, which shall decide to
accept it.
The D-Setup is sent out at that cell where the called mobile is located according to location update
procedures. It is broadcasted at those channels where the Mobile could possibly receive the message
(this is necessary because the system does not always know if the Mobile is engaged in a group call).
5.4.2.3. Behaviour to a Calling Dispatcher

For calling a Mobile or another Dispatcher the Dispatcher has to dial the called ISSI or use some

shortcut key. The Dispatcher Workstation HMI will indicate ringing and queuing states. When through
connected the Dispatcher can communicate with the called party via its headset.
For a telephone call the Dispatcher has to select the telephone call feature and dial the external
number. He/She is not required to dial the configured PABX/PSTN SSI.
5.4.2.4. Behaviour to a Called Dispatcher

All incoming individual calls are first put into a queue. The presence of queued calls is indicated
visually and with tones. The Dispatcher may then choose to accept or reject queued calls individually
via the Dispatcher HMI. When the Dispatcher accepted a call it is through connected and can
communicate with the calling party via its headset.
While a call is in the queue of a dispatcher the calling party will receive an alerting indication.
5.4.2.5. Behaviour to a Calling External Subscriber

For inbound calls from the PSTN/PABX, the system supports direct dial, as follows:
The called party number information element of the Setup message contains the T50-character string
representation of the called ISSI in decimal format.
Overlap receiving is not supported by the system’s PSTN/PABX interface.
The system sets up a full-duplex call to the identified network subscriber with the calling party ISSI set
to the configured gateway ISSI. The optionally received calling party information element is forwarded
as external subscriber number.
5.4.2.6. Behaviour to a Called External Subscriber

The system supports only duplex communication over the PSTN/PABX interface.
The calling party number information element is filled with the T50-character string representation of
the calling network subscriber’s ISSI in decimal format. The calling party number is started with the
configured gateway prefix string.
The calling and called party information element’s ‘Numbering Plan ID’ and ‘Type Of Number’ fields
are set to configured values.

5.4.2.7. Resources
The system uses late channel assignment. This means that the traffic channel at the AI is allocated
when the U-Connect message is received.
When there is not enough AI resource for establishing the call at the calling party’s cell, the call is
queued. When resources become available the call establishment proceeds.
When there is not enough AI resource for establishing the call at the called party’s cell, the call is
queued.
Whenever a call is queuing for AI resources this is indicated to the called and calling party according
to ETSI specs.
Queuing for outgoing calls is not supported at the PABX/PSTN gateway.
When an incoming call from the PABX/PSTN gateway to a Mobile is queuing for AI resources it will
resume alerting for the external subscriber.
In case of a semi-duplex call where called and calling party are mobiles that are located at the same
cell, the system allocates only one AI timeslot for the call.
5.4.2.8. Call Release

The call lasts until one of the parties actively releases the call conforming to ETSI specs.
In case of a semi-duplex call the call will be released by the system when the inactivity timer expires
(no transmission requests received by the system for a certain duration).
In case of a full-duplex call the system starts a configurable call timer after through-connect. The
system clears the call on expiry of the timer.
5.4.2.9. Possible failure – exceptions

The called party is unknown or not registered or not reachable.
System internal resources are exhausted.
In case of breakdown of a participating remote system component – like other base stations or the
gateway PC – the system will release the call autonomously.
5.4.2.10. Performance
The time from receiving the initial U-Setup at the base station until the D-Setup is sent out is less than
300 milliseconds for inter-site calls. This presumes an unloaded system and no queuing for AI
resources.
The time from receiving the initial U-Setup at the base station until the D-Setup is sent out is less than
150 milliseconds for intra-site calls. This presumes an unloaded system and no queuing for AI
resources.
In case of high system load the time will not exceed 1 second.

5.4.2.11. Logging / Tracing

For each individual call the system generates a log entry identifying:
• Calling party ISSI

• Called party ISSI
• ESN if a Gateway User is involved in the call
• Call type {semi-duplex, full duplex}
• Setup time
• Connect duration (measures the duration of through connected U-Plane)
5.4.3. Group call

A group call provides point-to-multipoint, half-duplex speech communication among a group of
subscribers. The system is the call owner and uses a hang timer (inactivity timer) to terminate the call.
Actor: Mobile, Dispatcher

Servicing subsystems: Base Station, Dispatcher Workstation
Precondition: Mobile and Dispatcher are registered.
The group is defined in the system.
The Mobile is attached to the group.
The Dispatcher Application monitors the group.
Post condition: All system resources allocated during the group call are freed again.
5.4.3.1. Behaviour to a Calling Mobile

At the AI the system provides the group call set-up procedure as specified in ETSI specs. The called
group is identified by its GSSI.
The first transmission will be granted to the calling mobile when requested. If the calling mobile does
not request to transmit first transmission is granted to none.
Call ownership is assigned to the system.
5.4.3.2. Behaviour to a Called Mobile

At the AI the system provides the group call setup procedure as specified in ETSI specs.
The D-Setup is sent out over the MCCH of those cells where at least one member of the group is
attached to the group.
Called Mobiles can leave the ongoing group call without disconnecting it.
5.4.3.3. Behaviour to a Calling Dispatcher

The Dispatcher selects one group status window and activates the PTT. It there was no group call
associated with that group the system initiates one and the Dispatcher is permitted to talk.

5.4.3.4. Behaviour to a Called Dispatcher

The Dispatcher HMI indicates the group call by presenting the transmitting party in the group status
window and the voice at the output device.
Voice from simultaneous transmissions in different groups is mixed at the output device.
5.4.3.5. Late Entry

If the Subscriber and group and configured to use late entry, the D-Setup message of the group call is
sent over the air periodically during the lifetime of the call. So those members who decide later to
attach the group can join the ongoing call. This behaviour is according to ETSI specs.
Late Entry signalling is sent over the MCCH of every cell where at least one member of the group is
attached to the group.
In case that a Mobile is the first mobile in a cell that attaches to a group with an ongoing group call,
the system starts sending the late entry Set-up message to let the Mobile join the call.
5.4.3.6. Multi Site Group Calls with Dynamic Paging Area

Compact TETRA is a trunked system, which means that system resources are shared between all
users. The system must provide sufficient channels so that resource sharing causes users only
minimal delay. Compact TETRA optimises this resource loading very efficiently by tracking and
recording the site location of each mobile subscriber (MS).
If the group call is queuing for AI resources at the calling mobile’s cell the system indicates this to the
calling mobile and to the group at all cells where a mobile is attached to this group.
The system uses one AI time slot at each cell where the group call is active.
The system may use presence checks according to [TIPv3] to detect that no users are participating in
a group call at a cell, and may free AI resources accordingly.
The system does not consume AI resources at cells where no Mobile is attached to the group.
When a call is set up the system allocates traffic channels only at the sites required to reach all active
talk-group members. This is also known as Dynamic Site Assignment. Traffic channels at other sites
remain free to handle other calls.
Compact TETRA can handle more traffic with a given number of resources, than could be handled by
an equivalently sized system which does not track the location of all talk-group members.
If Mobiles fail to de-register or detach they are still paged and AI resources are used.
5.4.3.7. Call Release

The system has the call ownership and ignores any request from a Mobile to release the call.
The system terminates the call automatically after communication has ceased and the associated
inactivity timer expires.


Group identity is not known by the system.
Access to the group from the calling subscriber is denied by configuration.
In case of breakdown of a participating remote system component – like other base stations or
Gateway PC – the system will release the call autonomously.
The Mobile receives a D-CALL-PROCEEDING message within 60 seconds after sending the U-
SETUP request for a group call if the system should be lack of resources and the call is queued. After
additional 60 seconds the calling party should receive a D-CONNECT message and the call should
start even if that time is not enough to allocate resources to all members of the group.
The time from receiving the initial U-Setup at the base station until the D-Connect is sent out is less
than 300 ms in a multi-site call. This presumes an unloaded system and no queuing for AI resources.
The time from receiving the initial U-Setup at the base station until the D-Connect is sent out is less
than 150 ms in a single-site call. This presumes an unloaded system and no queuing for AI resources.
In case of high system load the time will not exceed 1 second.

For each group call the system generates a log entry identifying:
• Calling party ISSI
• Called group GSSI
• Setup time
• Connect duration (measures the duration of through connected U-Plane)
5.4.4. Group Attachment / Group Detachment

This service allows the user application to either activate or deactivate already defined group identities
in a Mobile. After successful activation of a group identity the Mobile is allowed to participate in
communication related to that group.
The system supports single group mode only.
Actor: Mobile
Servicing subsystems: Base Station

Precondition: The actor is a member of the group and registered into the system.
Post condition: After attachment all group communication is available to the actor.
After detachment no group communication is available to the actor.
5.4.4.1. Behaviour to a Mobile

A Mobile can be attached to only one group at the same time (the selected group).
For attachment of the selected group the Mobile sends an U-Attach/Detach-Group-ID of type
‘attachment’ with the class of usage ‘class of usage 5’ and the group identified by its GSSI. The
system decides whether it accepts or rejects the request for attaching to a group. In case of
acceptance the attachment lifetime ‘attachment for next location update required’ is set in the D-
Attach/Detach-Group-ID-Ack. The procedures for group attachment are according to ETSI specs.
If the Mobile wishes to operate with no selected group, it may attach a null group identity (FFFFFF16).
The null group attachment is always acknowledged positively by the system. The system treats this
equally to sending a detachment message (as proposed in ETSI specs.)
The Mobile may de-activate the attached group by sending a U-Attach/Detach-Group-ID message of
type ‘detachment’. The detachment is always acknowledged positively by the system. The procedures
for group detachment are according to ETSI specs.

Group identity is not known by the system.
Access to the group is restricted by configuration.
The maximum time a Mobile waits for a response to an attachment request is 10 seconds.
The system acknowledges a received U-Attach/Detach-Group-ID message within 1 second in an

unloaded condition.
5.4.5. Group Monitoring

This service allows a Dispatcher to monitor and participate in group-associated communication.
Actor: Dispatcher
Servicing subsystems: Dispatcher Workstation
Precondition: Dispatcher has its Dispatcher GUI running and is registered at the
system.
Post condition: All communication addressed to the group is also routed to the

Dispatcher (Calls and SDS).
The Dispatcher is able to initiate calls to the group.
The Dispatcher is able to talk in group calls.
The Dispatcher is able to send Text SDS messages to the group.
5.4.5.1. Behaviour to a Dispatcher

To start monitoring the Dispatcher selects the group from a list of all configured groups in the system.
After accepting the selected group the Dispatcher GUI will create a new window for displaying the
group status. At each Dispatcher Workstation, a maximum of five groups can be selected for
monitoring.
The group status window reflects the current group status for all group communication after the begin
of monitoring as follows:
• Monitored GSSI
• Currently transmitting party ISSI and its transmission priority (blank when idle)
• Dispatcher’s transmission status (idle, wait for transmission allowance, transmitting,

interrupted). The value is a result of the Dispatcher HMIs PTT pressed state and the system’s
arbitration process.
• Last text SDS addressed to the group
• Last status SDS addressed to the group (in text format)
Any logged-in dispatcher may monitor any group configured in the system.
To stop monitoring the Dispatcher has to close the group’s status window.
Monitoring also stops when the Dispatcher closes the Dispatcher application.
When there is an ongoing group call while the Dispatcher starts monitoring, the status window will
also show the correct status of that call.

Exhausted resources. In that case the system does not allow adding further groups to monitor.
5.4.5.3. Resources
The system supports up to 5 simultaneously monitored groups per Dispatcher Workstation.
5.4.6. Pre-emptive Priority Call

The system supports group pre-emptive priority calls originating from a Mobile to a group. All other

combinations of source and destination subscribers are not supported.
In case of contention at the AI the system will gain the necessary resources by releasing another call.
The pre-empted parties will receive a D-RELEASE with cause “Pre-emptive Use of Resource”. There
will not be any prior indication to the pre-empted subscribers.
The Dispatcher HMI will indicate the presence of pre-emptive priority calls to gain the dispatchers
attention.
The Motorola Compact TETRA Emergency Call functionality is a supplementary service to normal
Group Call. The MS uses its currently attached group in all emergency transactions
NOTE: Non-tactical emergency operation (which allows the MS to set up an emergency group call to
a pre-defined group other than the currently attached group) is not supported.
Whether or not an MS can enter emergency mode is controlled by a configurable parameter in the
MS, which can be modified by the MS RSS.
Emergency mode is activated in the MS by pressing the emergency button for a given period of time.
Emergency mode is de-activated in the MS, which has entered Emergency mode, by pressing the
emergency button for a given period of time.
NOTE: The ongoing call continues until is has been knocked down by the Dispatcher Workstation.
An emergency group call can be initiated by an MS while the MS is in emergency mode.

NOTE: An MS in non-emergency mode receiving an incoming emergency group call will not enter
emergency mode.
The following services additional to those of a normal group is possible while operating an Emergency
Call:
- Emergency Alarm, which is an alarm message depending on provisioning that may be sent to the
Dispatcher Workstation on the group address informing the Dispatcher Workstation that the MS has
entered Emergency Mode
Emergency TX interrupt where an MS in emergency mode shall be able to override another

transmitting MS in the Group Call by setting up a new Emergency Call to the active Group
NOTE: If TX Interrupt (Audio Interrupt in NM) is set never to interrupt, then an emergency mode MS
can still interrupt other emergency MS‚s, i.e. they can interrupt each other on equal basis.
- Ruthless Pre-emption, where the SwMI can be configured to clear down lower priority call in order to
make way for the emergency call
- Top of Queue, where the SwMI can be configured to place the emergency call at the top of the call
queue so that when traffic channel becomes available, the emergency call will be the first call to be
allocated resources
NOTE: Either „Top of Queue” or „Ruthless Pre-emption” intrinsic services are
mutually exclusive

5.4.7. Dispatcher call

It is like an individual call where the calling party is a Mobile and the called party is a Dispatcher. For
more detail of an Individual call see Paragraph 5.4.2.
5.4.8. Telephone call

It is like an individual call where the calling party is either a Mobile or a Dispatcher and the called party
is a Gateway User. For more detail of an Individual call see Paragraph 5.4.2.
5.4.9. Registration
This service shall allow a user to register to the network; the user shall be then informed of the result
of the registration. When a MS roams the user application shall be also informed that the MS is ready
for use or that registration was not possible.
The Dispatcher is identified by an ISSI. Similar to a mobile at power-up the Dispatcher makes
him/herself known to the system at Dispatcher HMI start-up.
Precondition: The Mobile needs to access the system in a cell where it has not been
registered yet.
The Dispatcher has not launched the Dispatcher GUI.
Post condition: If the registration has been successful the location of the Mobile is
recorded.
The Dispatcher is available for other subscribers.
A registration log-entry is generated.
5.4.9.1. Behaviour to a Registering Mobile

The Mobile automatically sends a request to the system for using its services when it is roaming
between cells or has been switched on. The system decides whether using the services of the system
is allowed for the Mobile or not. If it is allowed the system gives the permission to operate otherwise it
rejects the request.
The request may include a request to attach one group e.g. the last group to which the Mobile was
attached. The group is identified by its GSSI. The system can accept the registration and accept or
reject the group attachment with the same message.
The registration procedure is handled according to Tetra Interoperability Profile Version1 Sept 1999

If the Mobile is already registered in that certain cell the system re-sends the registration result.
The system does not support multiple registrations, i.e. the size of the registration area (RA) is always
one LA.
The system does not use identity exchange to assign alias SSIs (ASSI) in a D-Location-Update-
Proceed message.
5.4.9.2. Behaviour to a Registering Dispatcher

When the Dispatcher starts the Dispatcher GUI first he/she must login by entering his/her ISSI. If the
same ISSI is active at another Dispatcher Workstation the system automatically logs out and
terminates the older application. The terminated application will indicate the cause of termination to
the user.
The ISSIs used by dispatchers are different than those used by mobiles.
5.4.9.3. Possible failure-exceptions

The given ISSI is unknown for the system.
The connection of the Dispatcher Workstation to the system is broken.
The system does not support migration, i.e. an U-Location-Update-Demand containing an

unexchanged SSI from a visiting mobile will be rejected.
The maximum time, while Mobile is waiting for response for a registration request is 30 seconds. If
nothing comes back during this time it means the system has internal trouble in that certain cell. The
Mobile may try to register on another cell.
The system answers a registration request in maximum 300 milliseconds in an unloaded system.

For each registration the system generates a log entry with the following information:
• Registering unit’s ISSI
• Time of the registration request reception
• Result {rejected, accepted}
5.4.10. De-registration
This service allows a user to request cancellation of the registration.

System Mode:Operational
Precondition: The Mobile is registered into the system in a certain cell.

Dispatcher is logged on a Dispatcher Workstation, running the
Dispatcher GUI.
Post condition: The Mobile is not registered into the system.
Dispatcher does not have the Dispatcher GUI running on its
Dispatcher Workstation and is not available for other subscribers.
A de-registration log-entry is produced.
5.4.10.1. Behaviour to a De-registering Mobile

The de-registration procedure need not be applied. Examples of where the Mobile may request de-
registration can be:
• When it is switched off, or
• User specific information, including ITSI, is removed from the Mobile, or
• Mobile may optionally inform the system that it leaves trunking mode and goes to direct mode
operation without dual watch operation and in effect will be no more reachable in the trunking
mode.
The de-registration procedure according to Tetra Voice plus Data Pt2 Air interface version 2.1.1
Dec2000
5.4.10.2. Behaviour to a De-registering Dispatcher

When the Dispatcher terminates the Dispatcher GUI application at the Dispatcher Workstation this is
interpreted as de-registration of its associated ISSI. Ongoing calls are cleared; future individual calls
to the ISSI will be redirected to another dispatcher according to a static redirection table.
5.4.10.3. Possible failure-exceptions

Deregistration never fails. A deregistration of an unknown ISSI is ignored but may produce an error
log-entry.

For each de-registration the system generates a log entry with the following information:
• De-registering unit’s ISSI

• Time of the de-registration request reception
5.4.11. Cell re-selection

This system feature lets Mobiles roam between cells and update its current location in the system.
Actor: Mobile
Precondition: The Mobile is registered into the system.
Post condition: The new location of the Mobile is known to the system.

One cell is the range of one site. When the mobile leaves a certain cell and moves into another the
system must be notified about at least the new location of the mobile. The Mobile does it when it
registers itself in the new cell.
The system broadcasts neighbour cell information. Neighbour cell information enquiry is not
supported.
The system provides cell re-selection as specified in ETSI specs.
5.4.11.2. Possible failures – exceptions

In the case of registration failure during cell re-selection the Mobile may retry registration on the
selected cell, try to select another cell or return to the previous serving cell.
Depends on the mobile.
5.4.12. Call restoration

This system feature of TETRA lets a Mobile roam between cells while engaged in a call without
releasing the call.
Actor: Mobile
Precondition: The Mobile is registered into the system and engaged in an ongoing
call.

Post condition: The Mobile resumes the call in the new cell

The Mobile leaves the serving cell then selects the new cell (as it does for cell re-selection) and
performs registration.
The system supports unannounced cell reselection with call restoration as described in ETSI specs for
all kinds of calls.
The system provides the information to the Mobile for call restoration on the MCCH of the new cell.

In the case of registration failure during cell re-selection the Mobile may retry registration on the
selected cell, try to select another cell or return to the previous serving cell.
The call has been cleared during the call restoration procedure.
If the call restoration procedure fails, the call we be cleared by the system on expiry of the call
duration timer or the hang timer.
5.4.12.3. Resources
In case of queuing conditions at the new cell the system inserts the restored call in front of all other
queued calls.
Depends also on the mobile performance, the Base Station will transfer the call from the old Base
Station within 500 ms.
5.4.13. Transmission Control

The system supports Transmission Control for semi-duplex individual calls and group calls.
Transmission requests may come from Mobiles or Dispatchers.
The system will reject transmission requests for duplex calls with transmission request permission set
to ’not allowed to request permission to transmit’.
The system does not support queuing of transmission requests. A Tx-Demand is either immediately
granted or rejected.
Transmission control has the following states:
Idle, this means that no party currently transmits
Transmitting, this means that one party transmits

5.4.13.1. Idle State

On reception of a Tx-Demand the system will grant transmission to the demanding party.
5.4.13.2. Transmitting State

On reception of a Tx-Demand the system will either reject the request or interrupt the currently
transmitting party and grant transmission to the demanding party.
The following table shows the decision matrix for rejecting the request or interrupting the transmitting
party.
TX Prio 0 1 2 3
Req Prio
0 R R R R
1 R R R R
2 I I R R
3 I I I I
TX Prio transmission priority of currently transmitting party
Req Prio transmission priority of TX-Demand
R Reject the TX-Demand
I interrupt the transmitting party
5.4.13.3. Behaviour to a Dispatcher

The dispatcher uses a dedicated keyboard key, mouse button or external PTT switch (e.g. foot
switch) for activating the PTT.
The time from receiving the U-Tx-Demand until the system sends the arbitration result in a D-Tx-
Granted to the demanding Mobile does not exceed 300 milliseconds in an unloaded system.
5.4.14. Status SDS

The system enables a subscriber to send pre-coded status messages to other subscriber(s).

Precondition: Both the sender and the receiver(s) are registered into the system.
Post condition: The message is delivered properly to the recipient(s).
An entry in the status history of the source party has been added.
5.4.14.1. Behaviour to a Sending Mobile

A pre-coded status message is just a number that has meaning only for the user applications of the
system.
The status message can be addressed to an ISSI or GSSI.
The SDS message sending procedures are specified in Tetra Interoperability Profile Version 2 Mar
2000.
5.4.14.2. Behaviour to a Receiving Mobile

The recipient receives the status message as specified in Tetra Interoperability Profile Version 2 Mar
2000.
5.4.14.3. Behaviour to the Sending Dispatcher

The Dispatcher may select a status to send from a configurable list. The status can be addressed to
an ISSI or GSSI.
5.4.14.4. Behaviour to the Receiving Dispatcher

The received status message will be translated to text and displayed at the dispatcher.
5.4.14.5. Resources
Downlink SDS status messages are sent over those channels where the recipient is possibly
reachable. So SDS messages do not require an established channel for their own and exist as part of
signalling. Status SDS messages can be sent or received in parallel with an ongoing speech call.
5.4.14.6. Available values

The messages are carried over by 2 Bytes integers. That means 65535 distinct messages are
available in the system. This range is divided into two categories:
0 to 32767 reserved for system use.
32768 to 65535 available for TETRA network and user specific definitions.
A list of common reserved status values with their meaning can be found in Tetra Interoperability
Profile Version 2 Mar 2000.


• If the receiver’s Mobile is temporarily turned off or unreachable, the system discards the SDS
status message.
• Status value is out of range (some other possible errors can be found in Tetra Interoperability
Profile Version 2 Mar 2000.).
5.4.15. Text SDS message

SDS Type 4 transport is supported with and without SDS-TL.
The system enables a subscriber to send text messages to other subscriber(s).
Actor: Mobile, Dispatcher, External Application
Servicing subsystems: Base Station, Dispatcher Workstation, Gateway PC
Precondition: Both the sender and the receiver(s) are registered into the system.
Post condition: The message is delivered properly to the recipient(s).
5.4.15.1. Behaviour to a Sending Mobile

The mobile sends the text as SDS-TL text message according to the procedures specified in Tetra
Interoperability Profile Version 3 June 2000. “8.2 Text Messaging”.
The message can be addressed to an ISSI or GSSI and shall not contain a timestamp.
When the Mobile requests a message receipt or consumption report the system replies with the
acknowledgement from the destination or a standard SDS-Report acknowledgement.
The system does not store messages for temporarily unreachable subscribers.
5.4.15.2. Behaviour to a Receiving Mobile

The system sends the text as SDS-TL text message according to the procedures specified in Tetra
Interoperability Profile Version 3 June 2000. “8.2 Text Messaging”.
The message received or consumption report is an end-to-end acknowledgement, so the system (the
SwMI) merely forwards any such reports. The system only ensures that the data SDS requesting a
report is successfully sent over the air interface (and will send a report to the sending entity if not)
The system does not insert a timestamp.

5.4.15.3. Behaviour to the Sending Dispatcher

The Dispatcher can type the text message with his/her keyboard. It will be sent as SDS-TL text
message. The text message can be addressed to an ISSI or GSSI.
5.4.15.4. Behaviour to the Receiving Dispatcher

The received text will be displayed at the dispatcher. Messages not sent, as SDS-TL Text Messages
cannot be displayed.
5.4.15.5. Behaviour to the External Application

External applications will be able to send and receive Text SDS using an access protocol specified in
the Dimetra SDTS Programmers Guide (accessible for Motorola TETRA Application Partners only).
5.4.15.6. Resources
Downlink SDS messages are sent over those channels where the recipient is possibly reachable.
SDS messages can be sent or received in parallel with an ongoing speech call.
The text is limited to 140 characters encoded as ISO/IEC 8859-1 Latin.

If the receiver’s Mobile is temporarily unreachable, the system discards the message and sends a
SDS-Report to the sending subscriber.
5.4.16. IP connectivity to System Components

The system provides IP transport to all components connected via the E1 ring. This enables the
system internally to use for instance FTP to download log files from a Base Station.
The Gateway Server additional Ethernet link provides access for external applications.
5.4.17. Packet Data (Release 2)

The Packet Data bearer service is Motorola’s Compact TETRA implementation of IP version 4 on top
of the TETRA Packet Data service, which is terminated at the IP protocol.
Actors: Mobile, PD Gateway

Servicing subsystems: Base Station, Gateway PC
Preconditions: The participating actors have assigned IP address.

Post condition: The data is transferred.

All system resources allocated during the packet data transmission are
freed again.
The system provides single slot symmetric advanced link with a maximum window size of 1.
Single Slot link enables maximal gross data transfer rate of 7,2 KBit/sec.
The limit for the overall packet data transfer rate in the E1-network is 500 Kit/s.

5.4.18. CLIP and TPI

The system provides the identification of the calling party to the called party (CLIP).
The system provides the identification of the talking party in a semi-duplex call to all listening parties
(TPI).
These features are implicitly covered by Tetra Interoperability Profile Version 1 Sept 1999.
Note: The calling party SSI is transferred in the D-SETUP from Phase 1 onward. Mobiles may provide
this information to the users.
Note: For telephone (PABX/PSTN) calls this feature is supported from Release 3.
5.4.19. Subscriber Management

Subscriber management is done via a Subscriber Management HMI at the Dispatcher Workstation. A
description can be found at Part 5 of the Compact TETRA Product Manual.
5.4.20. System Configuration

System Configuration is done via a Configuration HMI at the Dispatcher Workstation.
A description can be found at Part 4 of the Compact TETRA Product Manual.
5.4.21. Logging and Tracing

Logging and tracing data can be accessed by reading the corresponding logging files. The amount of
logging data may be selected by configuring a severity level.

5.5. System External Interface
TETRA Air Interface AI
Data API
Subscriber Interface
•SDS - 68P02400U44B
•SB9600 (radio control) (R1) (Short Data transport Service)
BS
•PEI (Peripheral Equipment Interface -for data) •PDS – 68P02400U93A
•TNP1 (R2) (Packet Data Service)
Industry Standard Dimetra-P Standard
Fractional E1 Application
server
Optional Router
in-place to control
Switching & and limit data volume
MS Management
IP Router
Network LAN (running IP)
(Gateway Server)
PSTN/
Billings Interface (TBD) – R3
PABX
•Static interface to call records
PABX/PSTN Interface E1 •Dynamic interface
Compact TETRA unique likely
•ISDN interface (R1) Dispatch
•E1 Q-sig Interface (R3) Consoles Monitoring Interface (TBD) – R2
Industry standard • SORM legal intercept
Dispatcher API (TBD) – R2
• MMI replacement/integration, • Voice recorder interface
audio via VoIP (TSAPI) Compact TETRA unique
Compact TETRA unique
5.5.1. TETRA Air Interface AI

The TETRA Air Interface is implemented according to Tetra V+D part2 Air Interface version 2.1.1
Dec2000 with the additions of Tetra Interoperability Profile Version 1 Sept 1999.and partly support of
Tetra Interoperability Profile Version 2 Mar 2000.and Tetra Interoperability Profile Version 3 Jun 2000.
The Mobile Stations (MSs) communicate with the Compact TETRA Infrastructure via the TETRA air
interface protocol defined in ETS 300 392-2. The MSs have been type approved as conforming to the
radio aspects of this specification.
The TETRA air interface is a complex, yet flexible interface with many optional features. To ensure
that the MS is able to work with TETRA systems from different manufacturers, the requirements for
InterOPerability (IOP) have, through the TETRA Memorandum of Understanding (MoU) forum, been
captured in a document entitled ’TETRA Interoperability Profile Version 2’.
Testing systems and MSs to the TIP specifications is co-ordinated and conducted by TeleDanmark.

Tetra Interoperability Profile Version 2 Mar 2000 defines a limited, but basic set of features probably
required in all TETRA systems. The interoperability requirements are extended requirements from the
conformance and type approval requirements. However, these requirements are derived from the
TETRA V+D standard with additional constraints on parameter variations for some Protocol Data
Units and mandatory requirements for support on some optional protocol functions.
5.5.2. Subscriber Interfaces

5.5.2.1. SB9600
The SB9600 serial bus is a Motorola proprietary communications protocol that is used within the
MTM300/700 mobile radio. Under certain circumstances it can be licensed to third parties for them to
develop applications and accessories. An example is the development of a desk control unit as a
replacement control head.
An external device can achieve control of the radio in the same way that the radio is controlled by its
keypad. Similarly, an external device is able to decode and use or display any information that
normally appears on the display of the radio.
5.5.2.2. Peripheral Equipment Interface PEI

The Peripheral Equipment Interface (PEI) is a TETRA standard interface defined for Mobile Stations
(MSs). The interface has been defined to enable peripheral equipment to do the following:
Access the TETRA data services
Set-up and control of speech calls
Access general MS and network information, for example, battery status, RSSI and so on
Access user applications with the MS
The Short Data Transport Service and the Packet Data Service bearer services can be accessed via
the PEI. Control of an MS is not currently supported via the PEI but via the proprietary Radio Control
Interface. (I.e. SB9600 for Motorola Subscribers)
Access to the SDS in the MS is via the SDS-TL transport layer protocol defined in ETS 300 392-2
(issue 2). The PEI is a 4-wire RS232 connection. The protocol is an extended AT command set with
the SDS-TL sitting on top. The interface is defined in ETS 300 392-5 and is also described in the
Dimetra Short Data Transport Service Programmers Guide.
Access to the Packet Data Service is via the TETRA enhanced AT protocol (ETS 300 392-5) and the
Point-to-Point Protocol (PPP). The AT protocol is only used to switch the MS into PPP mode. The
interface is described in the Packet Data Programmers Guide.
The physical connections to the Motorola MSs are described in the appropriate service manuals.
Those are available for Motorola Dimetra Systems Application Partner as Compact TETRA is using
the same subscribers as used for Dimetra.

5.5.3. ISDN-IF – Interface to regular networks

The external telephone interface located in the Gateway Server is implemented according to Euro
ISDN interface.
In Release1 a 4 times Basic Rate Euro ISDN T0 (4x2x64kb/s) connections are supported. As each
ISDN line provides 2 PABX/PSTN call capacity in total there are 8 full duplex telephone call possible
at the same time.
From Release 3 it is planned to have a second version of the Gateway Server providing a Primary
Rate (30x64kb/s) telephony interface via E1 (QSIG ETS 300 172).
Echo Canceller
The round trip audio delay from a Mobile Station (MS) to the PABX and back again is significant, and
any echo of the MS users voice, which is generated in the external telephone network, can be
severely distracting. The built in echo canceller suppresses any echo from the telephone network so
that it does not trouble the radio user.
Echo cancellation at PABX/PSTN interface according to ITU-T G.131:
< 25 ms echo path delay

> 46 dB echo loss
More information regarding ISDN will be provided at a later release.
5.5.4. Dispatcher Workstation Interfaces

The Dispatcher Workstation provides access to the system for different tasks. Each of these tasks is
realised as separate application installed on the Dispatcher Workstation:
Dispatching: concerns mainly the co-ordination and monitoring of mobile users and groups of mobile
users.
Subscriber management: concerns the definition and maintenance of mobile users, groups of
mobile users and their rights in the system.
System configuration: concerns the definition of parameters for system operation.
System monitoring: to query the operational status of system components and receive alarms.
All graphical user interfaces perform similar to standard Windows applications regarding the reaction
time and screen update.
Standard Windows NT access privileges are used to control access of individual users to the different
groups of functionality. Users can thus be restricted to a subset of functionality, e.g. dispatching only.
5.5.4.1. DISP-HMI – Dispatcher User Interface

The Dispatcher GUI uses English language for text and formats and is accessible at the Dispatcher
Workstation.
The following requirement enables a basic adaptation of the GUI language:

The GUI design uses a text file as resource for all displayed strings to provide basic provision for
multi-language HMIs.
The GUI is not required to adapt the size of buttons or alike according to the changed text layout
imposed by the change of the string resources.
The Dispatcher HMI will provide high-level health information about the Base Stations and the network
connectivity.
The Dispatcher HMI will produce log files for all SDS (status and text) sent and received at the
Dispatcher. The message content will be logged.
5.5.4.2. SUM-IF – Subscriber Management Interface

The SUM-IF provides a GUI to allow the user to add, delete and change:
Subscribers, collects the attributes associated with a mobile user
Groups, collects the attributes associated with tetra groups
Service classes, collects the services available for associated subscribers
The interface also allows the user to define their inter-relations, assign a service class to a subscriber
and define a subscriber to be member of a group.
After manipulation of the subscriber data the SUM-IF allows the user to initiate the update of system
databases with the modified data.
The Subscriber Management GUI uses English language for text and formats and is accessible at the
Dispatcher Workstation.
5.5.4.3. MNT-IF – Configuration Interface

The Configuration GUI uses English language for text and formats and is accessible at
the Dispatcher Workstation.
5.5.4.4. System Configuration Interface

The system configuration interface allows defining system parameters that are required for operation
and checks them for consistency.
After modification of system parameters the Configuration IF allows to update the system
configuration files with the modified data.
Following is a list of the main configuration parameters:
5.5.5. System wide parameters

The following parameters are configurable for the system.

MCC This is the system’s Mobile Country Code.
MNC This is the system’s Mobile Network Code.
CCK set This is the system’s cipher key set to use.
5.5.6. Base Station Parameters

For each base station the following parameters can be configured.
LA: This is the Base Station’s Location Area.
CCK idx: This is the index to the key to use.
Max MS transmit power: This is the maximum power with which a mobile may transmit to the
Base Station. This value is used in the broadcast channels.
Min RX access level: This Is the minimum receive level with which a Mobile may access the
Base Station. This value is used in the broadcast channels.
Subscriber Class Map: This is the Base Station’s map of allowed subscriber class. This value
is used in the broadcast channels.
BSC IP Address: This is the IP address for each of the BSCs (active and standby)
Transceiver frequency: This is the frequency of the transceiver. The frequency can be
configured for each transceiver.
5.5.6.1. System Monitoring Parameters

Monitoring Parameters:
Number of current individual calls in the system
Number of current individual calls at a Base Station
Number of current group calls in the system
Number of current group calls at a Base Station
Number of current packet data connections at a Base Station
Number of SDS transferred within the last minute at a Base Station
Status of the E1 links (up/down)
Status of the Base Stations (up/down)
Status of the redundant BSCs (main/standby/down)
Status of the Transceivers (up/down)
5.5.6.2. Software Update

A remote update of the application software of the Base Stations is possible. The update is started

from a Dispatcher Workstation. The Base Station is out of operation during the update. After the
successful transfer of the new software, the files are checked for integrity at the BSC. Only after a
successful check, is the new software started. It is possible to upgrade the Soft ware site by site, so
that there is no need to take the whole system out of operation.
5.5.7. Logging and Tracing Interface L/T-IF

The system’s usage by subscribers is recorded in log-files. This enable s System Partners and
maintainers to gain knowledge about the system’s usage, load and performance. Log-files are plain
text files that can be imported to MS Excel for evaluation.
The system’s logging/tracing capabilities have no direct interface to billing systems.
The recorded events are:

• All kinds of Calls
• Subscriber registrations / de-registrations
• SDS transport
• Packet Data Context activations / deactivations
Log-entries are produced at each system component where an event occurs. This means that a multi-
site call produces one log-record in each involved base station.
All log-files from all system components are regularly transferred to a well-known place at the
Gateway PC for permanent storage.
The system does not post-process the files from different components to create e.g. unique call-
records.
Log-files at the Base Station are volatile. This means that in case of a Base Station breakdown all
files that have not been saved to the Gateway PC are lost.
The Dispatcher Workstation has access to the log-files via the dedicated Dispatcher LAN over a
mounted network drive.

5.5.8. Packet Data Interface PD-IF (Release 2)
“Information Acces s
Anytime & Anywhere” Database
Site • Packet Data can be us ed e.g.:

• Databas e enquiry
E1 link
• F ile trans fer
• Work order reporting
WWW • World Wide Web acces s
Gateway
Server PSTN
ISDN
Dispatcher IP Data-
Ethernet Customer
LAN base
NETWORK LAN
Pac
ket
Dat
Dispatchers aG
atew
ay
Host interface access to the Packet Date Service PDS is via an IPv4 100Mbit/s Ethernet connection.
The API for the PD-IF will be implemented from Release2 according to the Motorola guideline Dimetra
PD Programmers Guide. (Accessible for Application Partner, see chapter 8.)
Note: More information to Packet Data will be added to the System Planner at later releases.
5.5.9. SDS Transport Service Interface SDTS-IF

The SDTS-IF provides Text Messaging via the protocol defined in Section 4 “Lan Access Point” of
Dimetra SDTS Programmers Guide. (Accessible for Application Partner, see chapter 8.) The
connection is via the 100 MBit/s network terminal at the Gateway Server similar to Packet Data
Interface PD-IF.
Note: More information to SDS Transport Service will be added to the System Planner at later
releases.

5.6. System internal interface

5.6.1. E1-Link - Network Interface
The connections between Base Stations and the Gateway PC are E1 links. A maximum of 9 nodes (8
Base Stations plus Gateway Server) will be supported.
The connections are bit-transparent for all channels. All parameters of the E1 link must be tested
according to the relevant standards (e.g. BERC) before connecting the links to the system.
The maximum one-way delay per link shall not exceed 3 milliseconds. If the delay exceeds this value,
the signalling and speech performance of the system will be degraded. System operation shall be
possible using links with up to 7.5 ms delay. A higher delay also has impact to the performance of
Packet Data. The Packet Data transfer protocol on the E1-links depends on the response time to
packages sent on the E1 link. If the delay gets higher than 7,5 ms, the protocol will not work in a
reliable way.
The system can be configured to use a fractional E1 lines from a provider. The provider has to set-up
the multiplexers according the needs of the system.
For each E1 link the following parameter can be configured. The configuration supports to define the
usage of fractional E1 by defining some time-slots as unused.
Time-slot Structure: This defines how to use each E1 time-slot
Fractional E1 calculation:
Depending of the size of the system, the number of used time-slots in the E1 links varies. A rough
estimation of the necessary number of time-slots can be found with the following formula:
Time Slots = Carriers/2 + 1 + (Sites-1)/2 + Packet Data Channels/8

Carriers … number of carriers in the system
Sites … number of base stations in the system
Packet data channels … number of AI slots used concurrently for data
The data structure within the E1 links is proprietary to the system.
For more information about the E1 physical connections refer to Product Manual, Section 2.
5.6.2. Dispatcher Access Interface DA-IF

The connection between Dispatcher Workstations and Gateway PC is a
100 MBit Ethernet. The network has to be exclusively designated for this connection.
To connect more than one dispatcher, a dedicated 100 MBit LAN is necessary. The LAN has to be
set-up by no more than one HUB or Switch.
Specific LAN requirements will be added during detailed design. The LAN itself is not part of the
product.

5.7. Safety
The system complies with the EN 60 950 safety standard.
5.8. Security and privacy

System internal files are usually plain text and are not encrypted or otherwise secured.
Access to the system over the Dispatcher Workstation is controlled by the standard
Windows NT 4.0 login procedure only.
Controlled system access over a network connection to the Gateway PC must be done by
a separate firewall that is not part of the delivered system.
5.9. System environment

The environmental requirements for the Base Station are described in the Base Station Description.
5.9.1. Climatic Environment – Operation

The Gateway PC requires office environment for operation.
Altitude: 0 – 3000m; temperature 10°C – 35°C; Humidity 20%-80% rel. non-condensing.
The Dispatcher Workstation requires office environment for operation.
Altitude: 0 – 3000m; temperature 10°C – 35°C; Humidity 20%-80% rel. non-condensing.
5.9.2. Technical Environment

The Gateway PC requires 230/110 VAC input.
The Dispatcher Workstation requires 230/110 VAC input.
5.9.3. Transportability
Transport by international airfreight should be possible.

5.10. Computer resource
5.10.1. Computer hardware
5.10.1.1. Base Station

Beside the RF components it consists of a Base Station Controller and up to 8
Transceivers (actually the Base Station could drive up to 32 Transceivers but our system
confines to 8).
The Transceiver runs the TETRA AI lower layers to upper MAC.
The Base Station Controller is a PC based card. The operating system running on this
card is Windows NT 4.0 Embedded. There are 128 Mbytes RAM on this card and a 160
Mbytes flash memory card is integrated.
The Operating system, the TETRA application and its databases fit into this space. The
initial SW design shall foresee not to use more than 50% of the free resources left after
starting the operating system.
nd
The Base Station may be equipped with a 2 – redundant – Base Station Controller.
5.10.1.2. CTG-1 Gateway Server

This is a standard PC equipped with standard COTS and special hardware, e.g. DSP Card(s)
E1 Card
Ethernet Card
4 way ISDN Card (8 PABX lines)
17” CRT screen with a resolution of 1024 x 768
US keyboard (System Partner can change keyboards to a local type if customer wish)
Mouse
Operating System Microsoft Windows 2000 English version (System Partner can install
Win2000 in local language if they wish)
The PC hardware MTBF is 30.000 hours.
The PC is able to work 24 hours per day.
The PC is CE approved.

5.10.1.3. CTD-1 Dispatcher Workstation

This is a standard PC equipped with standard COTS hardware, e.g.
Ethernet card
2x Sound cards
Mono loudspeaker
Mono head
17” TFT flat screen with a resolution of 1024 x 768
US keyboard (System Partner can change keyboards to a local type if customer wish)
Mouse
Operating System Microsoft Windows 2000 English version (System Partner can install
Win2000 in local language if they wish)
The PC hardware MTBF is 30.000 hours.
The PC is able to work 24 hours per day.
The PC is CE approved.
5.11. Documentation
All documentation is available on Motorola Online (for Compact TETRA System Partners)
Compact TETRA Product Manual consists of 6 Parts:
1. Introduction and System Overview
2. Hardware Specifications and Installation
3. System Installation, Configuration and Maintenance
4. System Operation (Dispatcher)
5. Subscriber Management
6. System Planner (this document)
In addition there are more documents available from the Resource Center on MOL in the sections
Presentations, Marketing, Product and Frequently Asked Questions
5.12. System environmental constraints

The system fulfil the following green requirements:
Halogen type cables are avoided as far as possible.

The Base Station does not use Beryllium Oxide
The Base Station does not use Cadmium
Lead is used in the solder alloy
PCB based on FR4 with Bromide is used.
There are no other dangerous materials used in the system.

5.13. Packaging of the Base Stations

The Base Station standard packing consists of a sealed plastic bag with humidity-absorbers inside.
The BS is then placed in foam shock absorbers inside a wooden box.
The components of the Gateway PC and Dispatcher Workstations are standard COTS and are
shipped in their original packages.
The packaging ensures safe loading, storing and transport to the final destination.
5.14. IOP Test

The system is fully TETRA interoperable as certified according to the TETRA Interoperability Profiles
(TIPs) for the supported features. Certificates are available on MOL.
5.15. R&TTE Certificate

The system conforms to the following standards.
Accredited Test Report EN 45001
Radio tests conforming to ETS 300 394-1
EMC tests conforming to EN 300 827
LVD tests conforming to EN 60 950

6. System Sizing
6.1. Coverage Planning

The first step in sizing a Compact TETRA system is to determine the number of base sites that are
required in order to meet the customer’s radio coverage requirements. This is likely to be an iterative
process, starting with very rough estimates based on limited information and gradually refining these
estimates using more detailed information and customer feedback arriving at a coverage plan using
agreed sites parameters (e.g. location and antenna heights) and an agreed method of determining
when the radio coverage requirements have been satisfied.
The coverage planning work and who performs it may depend on the size, phase and nature of the
individual project concerned, but here are typical scenarios:
The System Partner takes responsibility for coverage planning.
In this case Motorola just provides the quantity of base stations specified by the customer and
accepts no responsibility for the resulting radio coverage. Motorola only needs to
demonstrate that the base stations meet the specified transmitter output power and receiver
sensitivity.
The Customer may use resources within their own organisation to conduct coverage planning
or alternatively they may sub-contract this task to a third-party.
In either case Motorola’s involvement with this task is normally limited to providing
suggestions and advice to the System Partner on the parameters to use when conducting
coverage planning.
The following section of the system planner is intended to provide information to allow a System
Partner to successfully conduct coverage planning or to provide information to third parties to allow
them to perform coverage planning.
6.1.1. Coverage Planning Process

A typical coverage planning process for a PMR system is shown in the Figure below. Descriptions of
the steps shown are given in the following paragraphs. In cellular radio type systems with very high
user densities the starting point in the system design is often traffic planning since the cell size is
limited by the traffic that can be supported at each site. However, in PMR systems it’s usually the
quality of coverage that limits the cell size.

Pre-Sale Initial
Requirements
ROM Site
Estimates
Detailed
Requirements
Traffic Analysis
Create Propagation
Coverage Model
Maps Verification
Frequency Planning
Coverage
Proposal
Contract Agree
Refine
Negotiation Requirements
Coverage
Acceptance
And Design
Procedure
Agree
Coverage
Maps
Implementation
Drive Testing
Installation And
Optimisation
Coverage
Acceptance
Testing
Coverage
Acceptance
Typical Coverage Planning Process

6.1.1.1. Initial Requirements

The main requirements that have an impact of the radio coverage design are as follows:
Area to be covered. The first task that should be undertaken is to establish the customer’s
operational area and the area over which he expects to get radio coverage. This can be done
best by indicating such areas on a suitable map. Ideally this information can then be digitised
and imported into a coverage prediction tool. In addition, areas of particular importance such
as buildings that require coverage can also be indicated on the map.
Type of radio unit and operation. The type of MS operation required must be established.
Which areas need to be designed to provide portable coverage? Which areas for mobile only
coverage? How will the portable be used operationally? e.g. handheld, belt-worn. This has an
impact on the portable antenna efficiency and hence the cell size.
Coverage quality. The ‘quality’ is defined by two parameters the service quality (e.g. call
quality or data transmission delay), and the coverage reliability which is expressed as the
percentage of locations across the coverage area at which the service quality is exceeded
(which because of the nature of radio propagation must be <100%).
Available Sites. Details (e.g. location, antenna height, tower structure) of potential sites must
be available before an accurate prediction of the radio coverage can be made.
In many cases the customer may not have all of the above requirements well defined but typically still
requires to get an understanding of likely system cost and how changes to these requirements are
likely to impact on system cost. Thus it is often necessary to conduct some Rough Order of
Magnitude (ROM) estimates of the number of RF sites required to provide the required coverage.
6.1.1.2. ROM (Rough Order of Magnitude) Site Estimates

There are various methods that can be used to create a rough estimate of the number of sites
required where a customer has vague or incomplete requirements. For smaller systems with only a
few sites a coverage-planning tool can be used to produce these estimates in the same way as if
detail requirements had been available.
6.1.1.3. Detailed Requirements

Producing ROM estimates of the numbers of required sites and giving examples of how these
estimates vary with different coverage requirements could help a customer to refine and determine
their exact requirements. The information that most often varies in detail and quality is information
relating to the candidate base station sites. The level of information provided varies from a detailed
list of potential sites including information on exact location, tower or building structure, antenna
mounting heights, equipment room floor space and facilities (this is most often the case where a
customer owns the potential sites or where they are using an existing radio system), through to no
information at all, where the party responsible for coverage planning is responsible for identifying and
collecting information on potential sites. Not all of the required information may be available, so any
assumptions made when predicting coverage (e.g. antenna heights) must be clearly documented in a
proposal.
6.1.1.4. Create Coverage Maps

Once the customers coverage requirements are clearly defined (for example in a tender document),

detailed coverage planning can commence. A computer based coverage-planning tool that can
display predicted coverage across the required geographic area in the form of a map. The tool should
take into account terrain and Land Use and Land Cover (LULC) variations across the coverage area.
In order the accurately predict radio coverage the tool requires good quality databases of terrain
(height) and LULC for the required area.
Occasionally, these databases may be supplied by the customer as part of a tender (in order that all
bidding parties use the same information), but normally it is the party responsible for coverage
planning that must acquire these databases. The skill of the radio planner is to select sites and
antenna systems that will result in a system that meets the customers radio coverage requirements
while at the same time minimising the number of sites used in the system design. The number of
sites used not only affects Motorola’s equipment costs and hence bid price, but also other site related
costs for the customer such as site rental or maintenance cost and utilities costs and can therefore
have a crucial role in the customer’s selection of a supplier.
6.1.1.5. Propagation Model Verification

Radio propagation is highly dependant on the local environment, for example the type of terrain and
the size and structure of buildings. For this reason a coverage-planning tool will usually have a choice
of radio propagation algorithms and some method for ‘tuning’ these algorithms to measured data to
better match local conditions. Most propagation models predict a signal strength in an “open”
environment and then add an additional “clutter loss” (related to each LULC category) to take account
of the nature of the local environment. Using a clutter loss value inappropriate for the users coverage
area can potentially introduce large errors into the prediction. Because of the nature of radio
propagation, at every location there will be an error between measured and predicted signal strengths.
Experience has shown that these errors tend to follow a lognormal distribution. A margin is normally
added in the coverage-planning tool to take account of this variable error and ensure a high probability
of obtaining coverage at any location. The margin added is usually derived from the standard
deviation of the error between measured and predicted signal strengths. However, the standard
deviation of the error also tends to vary with the local environment. Therefore, unless there is
previous experience of the local environment and with the LULC database, it is often wise to conduct
a field survey to check the accuracy of the propagation model in the environments encountered within
the users coverage area. A selection of typical sites should be chosen representing a cross-section of
the type of site and local environment.
6.1.1.6. Traffic Analysis

Traffic planning and hence frequency planning may have an impact on coverage planning, because if
frequencies have to be re-used in a system, interference may result in loss of coverage. Traffic
information must be obtained from the customer and used to conduct traffic analysis in order to arrive
at the required number of channels per cell. More information on performing traffic analysis is
contained in another section of this system planner.
6.1.1.7. Frequency Planning and Interference Analysis

Once the number of sites required providing coverage and the number of channels required to support
the expected traffic have been determined, the frequency plan for the system can be constructed.
Unfortunately, spectrum is not an infinite resource and the number of frequencies available for the
system may require a compromise either on the number of channels per site or the reliability of
coverage. Geographic re-use of frequencies either within the same system or by other systems will
introduce a probability of experiencing co-channel interference and hence a reduced coverage
reliability.

6.1.1.8. Coverage Proposal

Part of a proposal to a customer will include a description of how the radio coverage requirements
have been met by the system design. This will typically include copies of coverage maps that show
the predicted coverage, a description of how the coverage prediction has been performed, details of
the base sites and antenna systems that are proposed and any assumptions that have been made
because information was not available.
6.1.1.9. Contract Negotiation

If a customer decides to proceed with the System Partner as a supplier, part of the contract
negotiation will often involve further discussions of the coverage requirements and the proposed
solution. The coverage design may need to be refined and updated at this stage before agreement
can be reached on the coverage that will be provided. At this stage it is also necessary to define
precisely the coverage acceptance procedure that will used to determine if the agreed coverage has
indeed been provided.
6.1.1.10. System Installation

As the system gets installed it is possible that assumptions made during the coverage planning
process are not realised during the implementation phase. For example, it may not be possible to
mount antennas at heights that had been assumed or for various reasons it may not be possible to
use a planned site and an alternative may need to be found. If this is the case, coverage predictions
need to be re-running with the new details, and if necessary changes to the contractual coverage
requirements agreed.
6.1.1.11. Drive Testing and Optimisation

Once a system is installed it is reasonable to expect that some optimisation of the coverage will be
required as coverage planning is not an exact science. Drive testing using a test mobile allows the
performance of the system to be recorded. Some areas (or sites) are likely to perform better than
expected and other areas (or sites) worse than expected. This may be due to any number of factors
but the “real” clutter loss and obstructions local to the Base station site are likely to have the greatest
impact. A Base station has configurable parameters that allow the handover region between sites to
be controlled. This, in addition to modification of the antenna system enables some optimisation of the
coverage to be performed. This drive testing and optimisation is conducted prior to formal acceptance
testing to ensure a high probability of passing the acceptance test.
6.1.1.12. Coverage Acceptance Testing

Various methods and tools are available for performing coverage acceptance testing. Coverage
acceptance testing proves that the agreed contractual coverage commitments have been met. The
coverage acceptance testing forms part of the overall system acceptance strategy which is under the
responsibility of the System Partner.
6.1.1.13. Compact TETRA Products

This section describes some of the attributes of the Compact TETRA radio products that are relevant
to coverage planning. The current Mobile Station (MS) products are the MTP700 and MTH300
portable radios, the MTM700 mobile radio. Unless otherwise stated the values listed in the following

sections apply to all of these products. Planned future (MS) products are the MTH500P portable
radios and values may be different for future products.
6.1.1.14. Frequency Bands

In 1996 the European Radiocommunications Committee of the European Conference of Postal and
Telecommunications Administrations (CEPT) published a decision (ERC/DEC/(96)01) requiring
member administrations to make the frequency bands 380-385 and 390-395 MHz available for the
introduction of TETRA systems for emergency services. In addition, they also published a second
decision (ERC/DEC/(96)04) requiring member administrations to make available at least 2x 2MHz
within either the 410-430 MHz band or the 870-876/915-921 MHz bands for the introduction of TETRA
systems for civil users. The first Compact TETRA products therefore address the 380-400 and 410-
430 MHz bands (lower 800 MHz band for other regions).
Information on TETRA channel numbering and duplex spacing in various frequency bands is defined
in Part 15 of the TETRA air interface standard (ETSI TS 100 392-15 V1.1.1 ).
The Compact TETRA Subscribers are (or are planned to be) available in the following frequency
bands:
Model Trunked Mode Trunked Mode Direct Mode

Transmit Receive Transmit & Receive
Frequency Frequency Band Frequency Band
Band (MHz) (MHz) (MHz)
MTH300 410-430 410-430 410-430
MTP/M700 380-430 380-430 380-430
MTP/M700 806-825 851-870 851-870
MTH500P 380-400 380-400 380-400
MTH500P 410-430 410-430 410-430
6.1.1.15. Transmitter Powers

Before discussing the transmit powers of the Compact TETRA products, it is worthwhile describing
how power classes are defined in the TETRA standard.
6.1.1.15.1. TETRA Power Classes

Output power is defined as the average power, measured through TETRA square root raised cosine
filter over the scrambled bits of a transmitted burst. TETRA equipment is classified in terms of power
classes. The defined power classes for base stations and mobile stations and the corresponding
nominal output powers are specified in the tables below. Note that the standard does not defined
"mobiles" or "portables", there both are termed Mobile Station (MS).

Nominal Power of Base Station Transmitters
(Compact TETRA Basestations provide 25 Watts at the Transmitter and min 10 Watts after the
antenna combiners)
Nominal Power of Motorola Subscriber Transmitters
6.1.1.15.2. Motorola Subscriber (MS) Power Classes

The power classes of the Motorola MS products are as follows:
All portables: Class 4 (1 Watt)
All mobiles: Class 3 (3 Watt)
6.1.1.15.3. MS Power Control

Note that TETRA employs a power control mechanism to reduce the MS transmit power (and hence
conserve battery power) when the MS is close to the base site and does not need to transmit at full
power. The possible output power steps are shown in the table below.

Nominal MS Power Control Levels
A Mobile Station determines it’s transmit power from its measured Received Signal Strength
Indication (RSSI) and the values of the parameters ‘MS_TXPWR_MAX_CELL’ and
‘ACCESS_PARAMETER’ which are broadcast by the base station. Where
MS_TXPWR_MAX_CELL = the maximum transmit power allowed in that cell (15 to 45 dBm)
ACCESS_PARAMETER = parameter for transmit power calculation (-53 to –23 dBm)
The MS uses the power control step value closest to PMS up to its maximum output power where
PMS = MIN (MS_TXPWR_MAX_CELL, ACCESS_PARAMETER – RSSI)
The effect of power control for a 3W mobile with ACCESS_PARAMETER set to its default value of –
39dBm is shown in the graph below. As it can be seen from the graph, the mobile will transmit at full
power unless its measured outbound Received Signal Strength Indication (RSSI) is greater than –74
dBm at which point it will begin to decrease its output power.
MS Tx Power
40
35
MS Tx Power (dBm)
30
25
20
15
10
5
0
6
0
4
8
2
6
0
4
8
2
6
0
20
14
08
02
-9
-9
-8
-7
-7
-6
-6
-5
-4
-4
-3
-3
-1
-1
-1
-1
RSSI (dBm)
Effect of MS Power Control with ACCESS_PARAMETER= -39 dBm

6.1.1.16. Receiver Sensitivities

Three different receiver sensitivities are discussed in the following sections and it is important to
understand the differences.
TETRA standard reference sensitivity. This is a reference input signal level that will be used
in radio conformance testing. Radios must have BER’s and MER’s less than specified
maximum values for various logical channels and RF channel conditions with an input signal
equivalent to the reference sensitivity.
Compact TETRA product sensitivity. This is the input signal level at which the Compact
TETRA products actually achieve the performance specified at the TETRA reference
sensitivity. It indicates the typical sensitivity performance margin over the TETRA standard
reference sensitivity.
System Design Sensitivity. This is the minimum input signal level upon which a particular
system design is based. It will vary from system to system depending on the services offered,
the customer requirements and expectations.
Each of these sensitivities is described in more detail in the following sections.
6.1.1.16.1. TETRA Reference Sensitivities

The TETRA standard specifies minimum performance requirements for both static and dynamic
(faded) sensitivity. TETRA also specifies three classes of receiver - A, B, E. The justification for
specifying more than one class of receiver is that receivers optimised for different channel conditions
will perform differently and it was felt that the receiver should only be tested under the channel
conditions in which it was designed to operated. Class B receivers are optimised for operation in
urban areas; hence it is only tested in static and TU50 channel conditions. A Class A receiver is
optimised for operation in hilly or mountainous areas and is tested in static, TU50 and HT200
channels. Compact TETRA System is tested to TU50.
The reference sensitivities defined in the standard are given in the table below.
Equipment Static Dynamic

Mobile Station -112 dBm -103 dBm
Base Station -115 dBm -106 dBm
TETRA Reference Sensitivities
The performance of a particular class of receiver at the appropriate reference sensitivity depends on
the logical channel type and is defined in terms of a Bit Error Rate (BER) or Message Erasure Rate
(MER). Several logical channel types are tested during conformance testing. As an example, at -103
dBm, a class B mobile receiver must have a BER < 2% in a traffic channel (TCH/7.2) and a MER <
11% in the signalling channels (SCH/F, SCH/HD) when tested under TU50 channel conditions.
The performance of the speech channel (TCH/S) is defined in ETS 300 395. The 137 bits, which are
produced by the CODEC for each 30ms of speech, are grouped into three classes depending on their
level of importance. The most sensitive bits (class 2) are given the highest level of error protection
while the least sensitive bits (class 0) are giving the lowest level of error protection (none!). Again, for
a mobile class B receiver at -103 dBm, the MER of the class 2 bits must be < 2.2 % when tested
under TU50 channel conditions.

The BER’s and MER’s defined in the standard were determined through simulation. An ideal non-
coherent receiver with an input symbol energy-to-noise density ratio (Es/No) of 8 dB for static and 17
dB for dynamic conditions was used for these simulations. To determine the reference sensitivity
level an implementation margin of 2 dB was allowed (for non-ideal timing and filtering) together with a
receiver noise figure of 6.4 dB for a BS and 9.4 dB for a MS. Using the equation below, the sensitivity
values given in the table above can be easily calculated.
Receiver Sensitivity (dBm) = Es/No + NF - 131.4
Symbol energy-to-noise density ratio (Es/No) is equivalent to carrier-to-noise ratio (C/N) provided the
receive filter’s equivalent noise bandwidth has the same value as the symbol rate. This can be
considered to be the case for the Compact TETRA receivers (both 18k).
6.1.1.16.2. Motorola Subscriber Sensitivity

The first point to note is that Motorola products are only designed to meet the requirements for a
Class B receiver and are therefore only tested in static and TU50 RF channels. The Motorola
Compact TETRA products are only guaranteed to meet the sensitivity performance defined in the
TETRA standard. However, the products are designed to meet this reference performance with some
margin and may typically perform better than the TETRA standard. When looking at link budgets it is
useful to understand this typical performance improvement over the TETRA standard and the impact
this will have on system performance. The following values are typical measured input signal levels at
which the products meet one of the required TETRA reference sensitivity performance values (BER of
TCH/7.2 <2.2% in TU50)
Equipment TETRA Standard Typical Measured

MTP200/300 -103 dBm -104 dBm
MTM300 -103 dBm -104 dBm
MTH500 -103 dBm -106 dBm
MTP700 -103 dBm -106 dBm
MTM700 -103 dBm -107 dBm
CTSx00 Series -106 dBm -111 dBm
Compact TETRA Product Dynamic Sensitivities
The performance may in some cases considerable better than the TETRA standard (e.g. 5 dB for the
CTSx00 in TU50).
6.1.1.16.3. Compact TETRA System Design Sensitivity

The sensitivity for which a radio system is designed can depend on many factors including:
The services provided by the system. Experience from other digital systems has found that
users of full duplex telephone interconnects voice generally require higher audio quality than
users of half duplex services. In addition, a system designed for predominately data services
may use different design sensitivity than a system designed for predominately voice services.

The expectation of the end users. The audio quality that a user group finds acceptable may
depend on whether they are experienced two-way radio users and the audio quality that are
used to on their current system
The signalling performance that is required.
Initial experience with Compact TETRA systems has shown that it is the signalling performance that
limits the systems’ usable range. Provided the inbound and outbound paths are balanced, if a call can
be set-up reliably, then the audio quality is usually acceptable. Users complain about the inability to
set-up a call or calls being dropped before they complain about unacceptable audio quality.
6.1.1.17. MS Antenna Gains
6.1.1.17.1. Portable Antenna Gain

The way that a hand portable is used and its proximity to other objects such as the body has a great
effect on the radiation efficiency of the hand portable antenna. This therefore needs to be considered
when planning radio coverage to hand portables.
Motorola has conducted extensive research into hand portable antenna efficiency and effective
antenna gains in various frequency bands. Some of this work has been published. Antennas that are
available with Compact TETRA release 1 are a quarter-wave whip, a shorter helical antenna and a
Public Safety Microphone (PSM) with antenna. Currently these antennas have only been tested with
the radio and antenna in isolation and do not take into account the effects of the body in the scenarios
described below. It is not expected that the performance will be significantly different from other hand
portable antenna and therefore, until further testing has been completed, the values given in the
following sections (taken from the Motorola Coverage Standards) should be used.
There are four main scenarios that are often considered when planning coverage for professional
hand portable radio systems:
(a) Hand-held operation. In this scenario the user is expected to communicate with the hand portable
always held in the hand at head height. This is the normal case for radiotelephone systems and other
systems that support mainly individual calls. The antenna gain for both transmission and reception is
taken to be -4.6 dBd for a quarter-wave whip. (-6.1 dBd for a shorter helical antenna).
(b) Belt-worn with hand-held transmission. In this scenario, for the majority of the time users carry
their radios in a carrying case fixed to a belt round the waist or the radio is clipped directly to a belt or
pocket. Users are able to listen to group and dispatch communications without having to hold the
radio. If a user wishes to respond to a communication he removes the radio from the carrying position
and holds the radio at head height so that the microphone is reasonably near to the mouth.
This is a common scenario in radio systems that support group communication especially where there
are large groups and the user is listening to communications for the majority of the time and only
responding occasionally. The antenna gain for transmission is -4.6 dBd (-6.1 dBd) as in (a), but the
gain for reception on the belt is only -13.2 dBd (-17.2 dBd).
(c) Belt-worn with a Remote Speaker Microphone (RSM). In this scenario, the radio is worn
permanently belt-worn as described in (b). However in order that the user can easily respond to a
communication without the need to remove the radio from the carry position a remote microphone is
used. This is normally worn on the label or shoulder. In addition, the received audio is also routed to a
remote speaker in the same unit as the microphone. This allows the received audio to be heard more
easily at lower volume, thus making communications more discreet.
Again this is a common scenario for dispatch type communications, particularly for public safety users
and users who rely on frequent communications throughout their working day to perform their job

function. The antenna is still mounted on the radio at waist level and therefore the gain is thus
-13.2 dBd (-17.2 dBd) for both transmission and reception.
(d) Beltworn with a “Public Safety” Microphone (PSM). This is a similar scenario to (c) with the radio
worn on a belt and with a remote speaker and microphone. However, in order to try and improve the
antenna efficiency the antenna is also mounted with the speaker and microphone. Typically only
helical antennas are used with PSM’s. In this case the antenna gain is taken to be -12.7 dBd for both
transmission and reception.
6.1.1.17.2. Mobile Antenna Gains

Mobile antenna gains are normally referenced to an experimental quarter-wave antenna mounted in
the ideal location of the centre of the roof of a vehicle. Note that this is not the same as an ideal
quarter-wave mounted on a finite ground plane. Typically a value of -1 dBd should be used for a
centre roof mounted quarter-wave.
The following gains are currently recommended for MTM700 antennas mounted on the centre of the
roof.
Model Number Antenna type Antenna Gain (dBd)

FAE5521A Quarter-wave -1
FAE5522A 3 dB antenna 2
6.1.1.18. CTSx00 Antenna Gains

Refer to Section 2 Hardware Specifications and Installation Manual.

6.1.1.19. Nominal Ranges

Typical ranges have bee calculated to give an idea of the expected coverage area in different
environments and are shown in the table below. They may be useful for initial site layout and for
sizing for budgetary proposals before undertaking detailed coverage planning using a computer based
prediction tool. To arrive at these ranges the following assumptions were made:
An antenna height of 30 metres above a perfectly flat terrain.
A 97% area reliability (90% minimum reliability) resulting in a shadow margin of 7 dB.
A frequency of 390 Mhz.
Range Range Range

MS City Town Rural
Centre (Km) (Km)
(Km)
Mobile 8.6 12.7 21.4
Handheld (Quarterwave) 5.2 7.7 13.0
Handheld (Helical) 4.7 7.0 11.8
Handheld Tx, Beltworn Rx 4.2 6.3 10.6
(Quarterwave)
Handheld Tx, Beltworn Rx 3.3 4.8 8.2
(Helical)
Beltworn with RSM 3.0 4.4 7.4
(Quarterwave)
Beltworn with RSM 2.3 3.4 5.7
(Helical)
Beltworn with PSM 3.1 4.5 7.7
(Helical)
6.1.2. Coverage Planning Tools

The nominal ranges given in section 5.3 assumed a base antenna height of 30 m above ground level
(AGL) and no terrain or environment variations across the coverage area. In practice, variations in
elevation and the local environment will have a large impact on the coverage obtained in a particular
area. For this reason, a coverage prediction tool that takes into account these variation needs to be
used when coverage planning.
Compact TETRA is intended to be applicable to many different markets and to systems ranging from
a single site to regional-wide systems with up to 8 sites. The amount of coverage planning work that
has to be done on a project varies from project to project. Below are some typical scenarios in
descending order of effort required.
The System Partner (or consultants employed by the customer or System Partner) takes
responsibility for coverage planning
A specialized Company is responsible for coverage planning
This section presents some options available for the radio coverage planning of Compact TETRA
systems. The option that is most applicable for any particular project will depend on the size of the
system (i.e. the number of sites), the resources that are available and which of the above scenarios
the project falls into.

6.1.2.1. Coverage Planning Tools on the market

There are many alternative coverage-planning tools on the market. Most fall into one of two
categories:
a) Low-cost, PC based tools traditionally used in the PMR arena, examples are:
Aspect from NTL
HTZ from Redifon MEL (Thomsom-CSF)
COVMOD from GEC-Marconi
Romulus from RCC
Signal from EDX Engineering Inc
Mozaik from Motorola
(b) High cost, UNIX based tools designed specifically for the cellular industry, examples are:
• CellCad (formerly known as Anet) from LLC
• CellDesigner from US West
• NetPlan from Motorola
• Planet from MSI
Mozaik from Motorola falls into the first category and provides either better or similar performance and
features to other planning tools of this type. There is therefore unlikely to be any reason for using any
of these tools rather than Mozaik and they will not be considered further.
Many of the cellular planning tools however have got some features that can save time when planning
large systems. For example some of the features not currently available with Mozaik, but typical of
this type of planning tool are:
• Manual or automatic hexagonal cell layout for initial cell plan
• Automatic selection of sites within a user-definable search circle
• Drag-and-drop site placement and coverage recalculation
• Fine tuning of propagation models to give best-fit to measured data
• Multi-carrier interference analysis
• Automatic frequency planning to minimise C/I
• Integrated traffic planning/analysis
• Generation of “hand-off maps”
• Scanned images as backdrops

6.1.2.2. Motorola Coverage Planning Services

Motorola CGISS has a coverage planning team based in Berlin, Germany. This team is able to
undertake coverage planning work on Compact TETRA projects and further details can be obtained
by contacting TETRA Solutions Planning (TETRASP1@email.mot.com)
6.1.2.3. Alternative Coverage Planning Services

In some circumstances, it may be worth considering using the services of a specialist coverage
planning consultancy. Again, the skills and type of work undertaken by these organisations usually
fall into either the PMR type consultancy or the specialist cellular radio planning consultancy.
Examples, of the former are BBC Transmission or NTL, while examples of the latter are LLC or MSI.
Since, using a third party planning service is only likely to be considered for large frequency re-use
type systems, it is these specialist organisations who have previous experience of planning large
cellular radio systems that are of most interest.
Both LLC and MSI have experience of planning iDEN systems and are two most respected
organisations, but consequently they also command premium rates for their services.
6.1.3. Frequency Planning

6.1.3.1. General
The regulatory authorities have traditionally carried out frequency planning for PMR services. Once a
user has been assigned (and paid for!) a frequency allocation, he has an expectation of exclusive use
of that frequency. However, because the radio spectrum is a limited resource, it has to be used by as
many users as possible. The role of the spectrum regulator has been to ensure that frequencies are
allocated to multiple users in such a way that geographical separation ensures a minimal probability of
interference between these users.
A somewhat more audacious approach to frequency re-use has been adopted with the introduction of
cellular radio systems. Here sites (or cells) are spaced and frequencies allocated in such a way as to
introduce a know amount of interference between them. The coverage obtained from a site is then
interference limited rather than noise limited. Decreasing the site separation can increase the number
of times frequencies can be re-used in a system and hence the coverage obtained from each site.
This obviously impacts the infrastructure cost as more sites are required, but the total capacity of the
system can be increased without additional spectrum.
The frequency management role of the regulatory is greatly simplified compared with the traditional
PMR case, since a cellular operator is assigned exclusive use of a block of spectrum, it is then up to
the operator to use the allocated spectrum as efficiently as possible. However, there are differences
between telephone type systems and dispatch type systems that make cellular frequency re-use less
ideal for dispatch type systems.
a) A user in a telephone system uses only a single communication channel. A group call in a dispatch
system requires a communication channel at every cell at which a member of the talkgroup is
registered. Therefore unlike telephone systems, once the cell size is smaller than the area over which
members of the group are dispersed, there is unlikely to any overall capacity gain by decreasing the
cell size further.
b) As cell sizes are made smaller, the mobility of the users means that radios cross-cell boundaries
more often and thus the amount of registration traffic increases. Telephone systems combat this by
grouping cells together into location areas. Radios only re-register when then they change location

areas. This decreases the amount of registration traffic, but increases the call set-up time since a
called mobile has to be paged in each cell in the location area to find his current cell. The increased
call set-up time is unlikely to be acceptable in dispatch type applications.
Thus for dispatch type systems like TETRA offering group call services the best spectrum efficiency
may be obtained by using cells that provide coverage over the entire area over which members of a
talkgroup are normally distributed. Obviously this will not always be possible because of the range
limitations described in section 2.2
6.1.3.2. Intermodulation
The use of TETRA TDMA technology significantly reduces the effects of intermodulation effects
compared to competing FDMA technologies. This is simply due to 4 channels being supported by one
carrier; hence the number of frequencies in use on any site is reduced by a factor of 4.
Intermodulation should also be minimised by choice of frequency blocks such that the spacing
between the blocks is irregular. In other words when a frequency is assigned to a site (including other
radio systems) the distance to any of already assigned frequencies should not be the same as any of
the distances between the already assigned frequencies. This will prevent 2nd order intermodulation.
Other orders of intermodulation might still occur.
In case the site is used by other radio systems care should be taken so that potential intermodulation
products from and between the system do not disturb each other.
When using omni-directional antennas mounted on the side of an antenna mast specific care should
be take to avoid the "rusty bolt" intermodulation effect. Because the antenna mast is exposed to large
electrical fields intermodulation can occur due to non-linear electric properties of corroded metallic
joins. This can be avoided by the use of directional antennas so the mast is not exposed on the cost
of a more complex antenna arrangement.
6.1.3.3. The Frequency Plan

A frequency plan should consider:
• Separate frequencies for airborne coverage
• Communication traffic and numbers of sets
• Sufficient spare frequencies to permit expansion to further individually planned channels if

required
• DMO frequencies
• Adjacent channel optimisation
• Intermodulation optimisation including other radio systems
• Cavity and multicoupler limitations
The plan will be influenced by final choice of sites, depending whether the sites chosen are
acceptable to the operator; and depending on suitable placement of the sites. The plan will also be
influenced by which options for extra capacity and expansion that the operator of the TETRA system
adopts. It will also be influenced by any capacity variations at individual sites that may be required in
the system design phase, for example if additional information is provided that influences the
assumptions that have been made for required system capacity in any areas

6.1.4. Coverage Acceptance Testing

Acceptance testing is performed in order to demonstrate to the customer that the system is operating
as specified and can be accepted. Site Acceptance Testing (SAT) demonstrates that the system is
operating correctly once the installed in the field in its final configuration. In order to demonstrate that
the specified requirements for coverage have been met Coverage Acceptance Testing (CAT) is
performed.
Although CAT cannot be performed until the system is in the field, it is important to establish the
methodology by which the coverage requirements will be measured and accepted early in the
planning process. This is important since the definition of coverage is ultimately the exact method of
measurement.
A user will consider he has radio coverage if the audio quality is acceptable. However, voice quality is
so subjective that it is not practical to base an acceptance test on voice quality. Therefore an
alternative quality measure has to be used.
In analogue radio systems SINAD is often used as an audio quality measure. Through experience it
has been found that in a static environment SINAD can be related to audio quality. However, SINAD
is not easy to measure in a fading environment. Therefore traditionally coverage acceptance tests
have been based on measuring signal strength using a received signal strength indication (RSSI) from
a calibrated radio.
In digital systems, an analogous measure to SINAD is a bit-error-rate (BER). It is possible to measure

BER in the field and this can be reliability related to audio quality. Therefore, coverage acceptance
testing can be based on RSSI measurements.
6.2. Traffic Planning

Traffic can be consider as:
Voice traffic generated by radio users, Dispatcher Workstation users and telephone users
Data traffic generated by radio and fixed users
Call processing signalling related to the user generated traffic
Mobility and registration traffic generated by the radio users
The resources available at a base station site to support this traffic are:
Main Control Channel (MCCH). This channel carries status messages, short data service
(SDS) traffic, call processing, mobility and registration traffic. Although the TETRA standard
allows secondary control channels (SCCHs) to be assigned.
Speech Traffic Channels (TCH/S). These channels carry voice traffic.
Packet Data Channels (PDCHs) Release2. These are SCCHs assigned exclusively for
carrying packet data traffic (although short data can also be transmitted and received while on
the PDCH).
Compact TETRA is a trunking system, which means that the available resources are shared by all the

users and are only allocated when a user needs to use them.
Thus the goal of traffic planning is to balance the availability of resources when needed (the quality of
service) with the cost of providing the resources. Not enough channels and users may frequently
have to wait to gain access to the system; too many channels and the system costs may be
excessive.
The following sections describe, for each of the channel types listed above, how to determine the
loading and the number of channels required at each site in order to meet the customer’s quality of
service expectations.
6.2.1. Main Control Channel Traffic

The first slot on the main carrier is always used for the Main Control Channel (MCCH). The MCCH is
a resource shared by all the radios at a site and because the system is unaware of when a mobile
requires access to the channel, a random access procedure is used on the uplink.
6.2.1.1. Random Access Procedure

The procedure used is a type of ALOHA protocol called framed slotted ALOHA. Random access
attempts may fail because more than one Mobile Station (MS) attempts to transmit in the same slot.
Essentially, the process is:
When a MS has wants to transmit, it does so at the next random access opportunity
If it doesn’t receive an acknowledgement from the Base Station (BS), then it waits for the start of the
next random access frame (note that the random access frame is nothing to do with the TDMA frame)
It then selects a random slot within the frame to make a re-transmission
If an acknowledgement is still not received the MS continues with steps 2 and 3 until an
acknowledgement is received or it reaches the maximum permitted number of re-tries.
The parameters used by the MS during random access are broadcast by the BS using the Broadcast
Network Channel (BNCH) over the MCCH downlink. Because random access is not required on the
downlink the call set-up capacity of the control channel is normally limited by the uplink and only the
MCCH uplink capacity will be discussed further in this section. [Note that this may not be the case if
there is a lot of downlink short data traffic and downlink traffic is considered when using the data-
planning tool described later].
Each uplink MCCH slot is divided into two sub-slots in order to double the number of opportunities
available for random access opportunities. There are a total of 34 subslots (17 slots) potentially
available for random access every TETRA multiframe (1.02s). It is well known that the maximum
throughput of slotted ALOHA is 37% of the capacity due to collisions of MS transmissions (i.e. the
maximum throughput for Compact TETRA would be around 12 random access attempts per second).
6.2.1.2. Tuning Random Access Performance

The performance of the random access procedure can be controlled to some degree by varying the
broadcast random access parameters. This is discussed below.

IMM [0-15]. This determines when a Mobile Station (MS) makes its first random access attempt. IMM
=15 means that the MS sends its first random access request in the next valid subslot (i.e.
immediately, IMM stands for immediate). IMM=0 means that a MS must also wait for the next random
access frame before attempting the first random access. IMM=1 to 14 means that a MS can make a
random access immediately provided that this occurs within the designated number of TDMA frames.
Compact TETRA uses IMM=15 since this minimises the call set-up time.
WT [1,15]. This is the Waiting Time before a MS makes a retry if it has not received an
acknowledgement from the Base Station (BS). The value 1 to 15 indicates the number random
access opportunities that the MS should wait before retrying. The default for Compact TETRA is 5.
Increasing WT increases the delay experienced for random accesses that require a retry. It can
increase the throughput slightly when the load is high.
Nu [0,15]. This is the maximum number of random access attempts allowed without receiving an
acknowledgement (i.e. Nu-1 is the maximum number of retries allowed). The default value in
Compact TETRA is 5. At low loads, increasing Nu increases the probability of a successful access.
This can be done with little impact on throughput or average delay. However at high loads, increasing
Nu results in more and more retries which can drastically reduce the throughput.
Base Framelength. [1,2,3,4,5,6,8,10,12,16,20,24,32]. This value together with the framelength factor
determines the random access framelength (i.e. the number of opportunities that make up a random
access frame). In making a retry, a MS will wait for the start of the next frame and then select a
subslot at random from within the frame to make the retry. The default value for Compact TETRA is
10. As the framelength is increased the throughput increases, however the delay for random
accesses that require a retry also increases so the average delay increases. This is the parameter
that would most likely be adjusted to optimise control channel performance, since it effects can be
easily predicted.
Framelength Factor [0,1]. Used with the base framelength to determine the framelength. A value of 0
means that the framelength equals the base framelength, a value of 1 means that the framelength is
four times the base framelength. The default value in Compact TETRA is 0.
6.2.1.3. Capture Effect

In a mobile radio environment, it is possible that when two radios transmit in the same slot one of the
messages will be received correctly because one transmission is at a much higher power that the
other. This is known as the ‘capture effect’. Simulations have shown that this can increase the
throughput of slotted ALHOA by up to 30%. Again, through simulations, it can be shown that with the
Compact TETRA default values the actual maximum throughput would be expected to be around 45%
of the ideal channel capacity or 15 successful random access attempts per second.
6.2.1.4. Maximum MCCH Loading

Although the maximum throughput is around 15 successful random access attempts this is achieved
when the load is around 23 random access attempts per second, thus there are a high number of
unsuccessful random access attempts at this throughput. Therefore the maximum random access
throughput should be assumed to be around 30% or 10 per second and usually a system should be
design with a considerable margin so that overloading of the control channel is unlikely to occur even
with instantaneous high loads. Typically a maximum random access load of 5-10% would be a
recommended limit.

6.2.1.5. MCCH Traffic Types

So far we have only considered random accesses on the main control channel. Some control channel
messages require more than a single subslot. In these cases, the random access may request
reserved use of the channel. The total numbers below we discuss the traffic carried on the uplink
MCCH and the number of slots required to support this traffic.
Registration. In order for a Mobile Station (MS) to gain access to the services provided by the system,
the mobile station must first register with the system. This normally happens when the radio is
switched on. The MS sends a registration request, which requires a random access followed by a
reserved subslot. The Base Station (BS) responds with an accept or reject message. The MS then
sends a layer 2 acknowledgement (BL-ACK) in a reserved subslot to confirm that it received the
message. Thus the total number of uplink slots required for a registration is one random access plus
two reserved subslots.
Mobility. As radio users move the MS makes a decision on the best site to use. This is known as cell
reselection. This may take place while the radio is idle on the control channel or while it is in a call. In
most scenarios this requires a random access followed by two reserved subslots.
Group attachment. If a user changes the currently selected group the MS informs the system. This is
known group attachment and requires a random access followed by a reserved subslot.
Group call set-up. A group call request requires a single random access.
Individual and telephone interconnect call set-up. These call set-ups require a random access
followed by a reserved subslot. In addition for individual calls to another MS, the called MS also
requires a reserved subslot followed by a random access when the call is answered.
Status Messages. Status messages and emergency alarms can be sent in a single random access.
Short data service. Compact TETRA supports only type 4 short data messages, which require a
random access followed by 1 to 5 reserved full slots depending on the length of the message.
Packet data service (Release2). MSs that require access to the packet channel (PDCH) must first
request access to this channel via a random access on the MCCH. Note that a random access on the
MCCH may not be required for every packet data transaction. This depends on the setting of the
READY timer for that user.

6.2.1.6. MCCH Loading

Details will be added later
6.2.2. Voice Traffic Planning

The primary purpose of the Speech Traffic Channel (TCH/S) is to channel speech traffic. However, it
is worth noting that the channel can also carry other traffic. The TCH/S carries speech traffic in 17 out
th
of the 18 frames of a TDMA multiframe. The 18 frame is used as a control channel to carry
signalling traffic for users involved in speech calls and is known as the Slow Associated Control
Channel (SACCH). The traffic channel can also carry signalling during pauses in speech. During
these periods the TCH/S is assigned as a control channel known as the Fast Associated Control
Channel (FACCH). The SACCH and FACCH are used in Compact TETRA for call control signalling
and short data delivery to give a simultaneous voice and data capability.
The Main Control Channel (MCCH) is used to request allocation of TCH/Ss to support individual,
group and telephone interconnect calls. The system allocates TCH/Ss as required to support the
requested calls. If channels are not available to support the call, the Compact TETRA system will
queue the call until such time as the appropriate channels are available.
The purpose of voice traffic planning is to ensure that there are sufficient TCH/S available at each site
so that there is only a small probability of a call being queued. What constitutes a ‘small probability’
will be dependent on what is acceptable to a particular customer. A typical value is to design a
system with less than a 5% probability that a call will be queued under the loading expected in the
busy hour. The task is to balance the number of TCH/S provided at each site with the performance
expectations of the customer. Adding channels will increase cost and the total number of TCH/S may
be limited by equipment capacity limitations and by spectrum availability. Using too few channels may
result in queuing times that are unacceptable to the customer.
Traffic modelling for a single site system is straightforward. An analytical model such as ‘Erlang C’,
which has seen widespread use within the telephony industry, can be used. However, modelling
multi-site systems with group calling is much more complex. There are multiple queues in the system,
since each site represents a queue. The Erlang C model is only valid for a single queue and therefore
cannot be used for multi-site systems. Such models can be used to get a rough idea of the number of
channels required at each site, however it is highly recommended the NetCalc simulation tool is used
for conducting traffic planning in Compact TETRA systems.
NetCalc has been developed by a group within Motorola CGISS known as Resource Development
Engineering (RDE). Details of this tool are available at http://rdeserver.comm.mot.com/netcalc/ and
guidelines for using NetCalc can be found in Chapter 27 of the Motorola Coverage Standards (MCS)
which can be downloaded from the RDE website at http://rdeserver.comm.mot.com/. This MCS
chapter also provides an excellent tutorial on voice traffic planning including definitions of common
traffic planning terminology (Grade of Service, Busy hour, etc). This information is not replicated here;
instead, the remainder of this section provides supplementary information that should be considered
when conducting traffic planning for Compact TETRA systems.

6.2.2.1. Voice Traffic Loading

Details will be added later
6.2.2.2. Compact TETRA Voice Capacity

Each RF carrier in a Compact TETRA system supports 4 TDMA slots or channels. Each site can
support up to 8 RF carriers giving a total of 32 channels.
More details will be added later.
The total number of TCH/S in a system is limited by the capacity of the E1 ring. Thus the maximum
possible number channels is 32 Carriers*4 slot = 128 minus 4 MCCH (min. 1 per 8 carriers) is 126
TCH/S.
6.2.2.3. Compact TETRA Features that impact Voice Capacity

This section describes how some of the features supported in Compact TETRA can influence traffic
planning.
6.2.2.3.1. Fast Start/All Start and Critical Sites

The members of a talkgroup may be distributed across many sites. When a group call request is
received for the talkgroup, the system will try to assign a voice channel at each site where there is at
least one member of the talkgroup registered. If a voice channel is not available at any one of these
sites the call will be queued until channels are available at all sites. This operation is known an ‘All
Start’. An alternative operation is to allow the call to proceed at sites that do have channels available
and to add the remaining sites to the call as and when channels become available at those sites. This
operation is known as ‘Fast Start’ and allows the call to be set-up as quickly as possible even though
not all members of the talkgroup may here the start of the call. The network manager can set which
operation is used for each talkgroup.
An additional feature that operates with Fast Start is Critical Sites. This allows the network manager
to set (for each talkgroup) specific ‘critical’ sites that must have a voice channel assigned before the
call can proceed even when the group call is configured for Fast Start operation.
6.2.2.3.2. Announcement Calls

When a Mobile Station (MS) attaches to a multigroup at a site, the SwMI will set-up group calls at the
site, as required, whenever a group call is initiated for any Talkgroups associated with the multigroup.
Calls for the associated Talkgroups will be set up, provided channels are available, even if there are
no members of the Talkgroups attached at the site. (Note that if channels are not available, the
Talkgroups proceeds as normal and is not queued). This multigroup operation allows a user that has
selected the multigroup to hear audio for any of the associated Talkgroups and is sometimes known
as multigroup scanning.
This feature can potentially use up a lot of voice channels and should be used with caution. For this
reason the network manager can select for each multigroup whether or not voice channels allocated
for this multigroup scanning (i.e. where there are no members of the talkgroup at the site) can be pre-
empted for normal talkgroup calls. Allowing these channels to be pre-empted means that the grade of

service for Talkgroups is not effected by talkgroup scanning, but the talkgroup scanning user may not
always received audio for Talkgroups associated with the multigroup.
If it is essential that audio for Talkgroups associated with a multigroup is always heard, then the
system has to be designed with the appropriate number of voice channels to support this.
6.2.2.4. Controlling traffic

There are several methods available that can help to control how traffic is distributed across the
available sites in the system. These features are described below.
6.2.2.4.1. Home Location Area

Compact TETRA Mobile Stations (MSs) can with up to 8 home location areas (in Compact TETRA a
location area = a site). When a MS attempts cell reselection, a home site will always be selected in
preference to another site provided it provides an ‘usable’ signal strength, even if another site
provides a higher signal strength. This feature allows the traffic generated by groups of MSs to be
restricted to certain sites whenever possible. [Note that a MS will only begin looking for alternative
sites when the signal strength from the current serving cells falls below a defined level. This level is
the ‘slow reselect threshold’ + 10dB. The slow reselect threshold is broadcast by the Base Station
and should be set appropriately to ensure that the MS are aware that an adjacent site is a home site].
6.2.2.4.2. Controlling Coverage through Antenna Patterns

In situations where there is significant overlapping coverage, the coverage and hence the traffic on
each site may be tailored by modifying the antenna pattern. For example, several low sites may
provide coverage and capacity in a city. A high site outside of the city may be used to provide
coverage to a wide area surrounding the city and coverage from this site may overlap with the
coverage from the low sites. It may be possible to provide a null in the antenna pattern in the direction
of the city so that the site is not overloaded with traffic that could be carried by the low sites in the city.
6.2.2.4.3. Controlling Coverage Through Cell Reselection Parameters

In situation where there is overlapping coverage and it is desirable to restrict the traffic to certain sites,
it may be possible to modify the coverage provided by each site by changing the cell re-selection
parameters broadcast by the base station. The select reselection parameters are discussed in the
coverage planning section of this planner.

6.2.3. Data Traffic Planning

6.2.3.1. The Packet Data Service

Details will be added later.
6.2.3.2. The Short Data Service

6.2.3.2.1. Application
Applications using SDS must be economic on traffic and tolerant of congestion and coverage
problems. The application behaviour should include:
Identifying when the mobile may be out of coverage and not resending packets during this
time.
Resending data only after the Tetra network been given the time and opportunity the resend
segments.
Grouping of data transmissions where practical.
Relatively high insensitive to data latency.
Possibly some data compression.

6.2.4. Traffic calculation tool available from MOL

There is a simple Traffic calculation tool available through the Resource Center of Motorola Online.
This can be used to calculate traffic in a trunked network and has to apply for each site separately.
6.2.5. Traffic calculation theoretical samples

One site can have a maximum of 8 carriers, with 31 traffic channels + 1 control channel. To achieve a
queuing probability of less than 1.5% on such a site, the traffic load must not exceed 20 Erlang. For
an acceptable queuing probability of less than 20%, the traffic load can increase to 25 Erlang.
For average call duration of 10 seconds, the 25 Erlang correspond to 9000 call attempts per hour.
The switching capacity of the site allows up to 18000 call attempts per hour and is thus not the limiting
factor.
For system throughput, the air interface resources are the limiting factor of system performance.
The following section gives an overview about the expected Grade of Service (GoS) in different traffic
scenarios.
Basic parameters:

10000 subscribers in the database
30% of subscribers are registered at the same time.
Each registered user offers the following traffic:
0,1 calls/h individual mobile to mobile, 30 s duration
0,25 calls/h individual mobile to base, 30 s duration
0,36 calls/h group, 30 s duration, 5 PTT
3,3 registrations/h
5 SDS/h
Kbytes packet data/h
Interpreting the results
Blocking probability on ISDN:
On external ISDN interfaces calls are blocked, if all ISDN channels are busy. The calculated value will
indicate how often a user will face a situation where he gets a busy indication, when he tries to access
the external network.
Queuing probability on Air Interface:
On the AI calls queue for free resources. The calculated values will indicate how often a user will have
to wait for AI resources.
Usage of MCCH:
The calculated value shows how many uplink slots in the Main Control Channel are used for a specific
scenario. As long as this value is below 36,8 % the probability of collisions and resulting retries on the
MCCH can be neglected.
6.2.5.1. Example 1
4 site system, 750 users registered at each site, group calls always on all 4 sites
Results:
Necessary channels per site: 24 channels for voice, 4 channels for packet data therefore 8 carriers
are necessary
Blocking probability on ISDN: 4 x 2B+D: <15%
Queuing probability on Air Interface: < 1%
Usage of MCCH: 35,6 %
6.2.5.2. Example 2
8 site system, 375 users registered at each site, group calls always on 2 sites

Results:
Necessary channels per site: 12 channels for voice, 3 channels for packet data
Therefore 4 carries are necessary
Blocking probability on ISDN: 4 x 2B+D: <0,5%
Usage of MCCH: 17,8 %
6.2.5.3. Example 3
Single site system, 2500 users registered at each site.
Each registered user offers the following traffic:
0,1 calls/h individual mobile to mobile, 30 s duration
0,25 calls/h individual mobile to base, 30 s duration
0,36 calls/h group, 30 s duration, 5 PTT
0,1 registrations/h
1,3 SDS/h
4 Kbytes packet data/h
Results:
Necessary channels: 24 channels for voice, 7 channels for packet data
Therefore 8 carriers are necessary
Blocking probability on ISDN: 4 x 2B+D: <10%
Usage of MCCH: 34,9%

6.3. Component Sizing
6.3.1. Pricing Tool available from MOL

This Pricing Tool allows System Partner a quick rough calculation of the system price.
It can be modified by the System Partner to reflect the individual customer prices definded by the
Partner.
6.3.2. Cost reduction – initial investment

The decentralised system architecture leads to a competitive price for small systems, since the cost
for central components is low. At the same time, the system is able to grow to meet changing
customer demands, with a cost increase proportional to the system size.
The cost of a system is kept low through the following means:
Use of standard COST components for Gateways and Dispatcher Workstations.
Limited functionality to match the target market.
The Tower mounted Amplifier (TMA) allows cheap thin feeder cables from Antenna to site.
Operations and Maintenance Interface is integrated with Dispatcher Workstations, obviating

the need for additional hardware.
6.3.3. Cost reduction – running costs

The system can use fractional E1 links for communication between nodes.
Full E1 links are only required for systems with 32 Tetra carriers. For smaller systems, the number of
timeslots reduces roughly proportionally.
The system can be administered centrally. This includes software updates and changes of
configuration data

7. Service
7.1. Definition of Service Level
The table below shows which task is defined for each level of service.
It states that the System Partner is responsible for Service Level 1.
Motorola is providing Service Level 2+3
Overview of Service Level and Items referring to the respective level
Item Level 1 Level 2 Level 3

(System Partner) (Motorola) (Consortium/
Motorola)
Customer Service Level

Agreement X
Onsite support X
Planned
Maintenance X
Customer Call
Centre X
Customer training X
Installation &
Commisioning X
Remote
Diagnostics X X
Adv.Exchange
Fault simulation X X
H/W & S/W
Engineering X

7.2. Escalation Process of Support and Service requirements
Service resolution Customer

Service Delivery
Customer to operate the system
& call level one for all
Support and service requirements.
80% resolved Level 1 Deliver all Support contractual obligations to the customer.
System Represent the single point of service & support contact to
Partner the customer. Resolve 80% of all questions
20% Escalated
80% Resolved
Level 2 Provide level 2 services to the customer system via request
Motorola from the System Partner.
20% Escalated
Final resolution Provide level 3 services for resolution of faults

Level 3
and provide all engineering and S/W development for the
Consortium
Customer system.
& Motorola

7.3. Support Solution
The standard Warranty includes Board Repair Service within 35 days only.
System Support which is essentially, compliments standard warranty in the first year
and is a comprehensive whole life support to maintain system availability.
Therefore there is an additional fixed charge of 3% related to the Motorola
infrastructure costs (Basestation, Gateway and Dispatcher).
Enhanced Services like Software Subscription Agreement and Advanced Board

Exchange provide additional service by Motorola.
Optional Software Subscription Agreement

Enhanced - Regular software updates to keep the
Services system current
- Minor feature enhancements
Advanced Board Exchange

– 24 hour turnaround time
Delivered System Support

standard
services - Helpdesk – 24 hour
- Technical support
- SW updates
- Board repair service (warranty) – 35 day

8. Training
Currently, Motorola in Europe Middle East and Africa offers technical training courses.
Who should attend?

Those with an existing understanding of:
•System Installation and Optimisation.
•Subscriber Radio Programming.
•Microsoft NetMeeting application
What does the training consist of?

•Functionality/Application/Configuration Training (total 5 working days)
•Includes 2 days “hands on” training
•Class sizes restricted to maximum of 10 participants (up to 2 places per organisation)
•Delivery & Course material language in English only
Details of the training:
Day 1
• Product Overview.
• Tetra Air Interface.
• System Infrastructure
Day 2
• Features & Functionality.
• Gateway, & Dispatcher
• Management Applications
• System Software Applications.
Day 3
• System Configuration.
• System Data Base Configuration

• O & M Set Up.
• Call Logging.
Day 4 / 5
• Student Hands On – System / Subscribers
Location?
Motorola Technical Training Centre (Basingstoke, UK)
(Other locations for training to special conditions are possible. Please ask your local Motorola
representative for details)
Cost?
Release 1 Training $1166* per delegate
*Excludes travel, accommodation & subsistence
How to apply?
Contact Sandra Butler to register:
Email: Sandra.Butler@motorola.com
Tel: +44(0) 1256 484553
Fax: +44(0) 1256 488140

9. Third Party Applications

Motorola has a programme in place to approve both application developers as Motorola Partners and
specific solutions for use with Compact TETRA.
Note: For Compact TETRA many solutions made for Motorola Dimetra Systems can be used when
connected to the CT system or subscriber via:
PEI interface
SB9600
TAI Tetra Air Interface
SDTS Short Data Transport Service
PDS Packet Data Service
The following table shows a view solutions for Compact TETRA
Partner Product Application

INCA Command and control
system - Advanced
vehicle location

Digital Remote Controller For use with MTM700

model 390 radio, Public safety/
transport and distribution
etc
Unitech Connect Middleware development

TETRA PC-Dispatcher Wireless dispatcher

RFD 100

SmartBilling (already Recording and tracking.

approved for Dimetra P)

For more information please visit our external Internet page:
http://www.motorola.com/cgiss/emea/tetra/home.html
and Motorola Online:

Resource Center / Product and Technical…/Compact TETRA

Motorola actually is working with in excess of more than 80 companies. If you are interested in
developing solutions for Compact TETRA or Dimetra please contact:
Ray Hall, Director Software Solutions & Business CGISS EMEA
E-mail: Ray.Hall@motorola.com

10. Equipment List and Ordering Guide

Ordering equipment from Motorola is possible via Motorola Online System only (see Ordering Guide
at the end of this paragraph)
10.1. Base Station Equipment List

10.1.1. CTS100 Models
CT100402ADAN CTS100 380-400 MHz
CT100422ADAN CTS100 410-430 MHz
CT100472ADAN CTS100 450-470 MHz
CT100872ADAN CTS100 805-870 MHz

CT200402ADAN CTS200 380-400 MHz
CT200422ADAN CTS200 410-430 MHz
CT200472ADAN CTS200 450-470 MHz
CT200872ADAN CTS200 805-870 MHz

CT300402ADAN CTS300 380-400 MHz
CT300422ADAN CTS300 410-430 MHz
CT300472ADAN CTS300 450-470 MHz
CT300872ADAN CTS300 805-870 MHz
10.1.4. Orderable Options for the Basestations

C621BC ADD: One Transceiver (CTS100)
C621BD ADD: One Transceiver (CTS200/300)
C622AL ADD: Two Transceivers (CTS100)
C622AM ADD: Two Transceivers (CTS200/300)
C623AJ ADD: Three Transceivers
C624AJ ADD: Four Transceivers
C625AB ADD: Five Transceivers
C626AB ADD: Six Transceivers
C627AB ADD: Seven Transceivers
C628AB ADD: Eight Transceivers
CA00095AG ADD: Redundant Base Station Controller (Release 2)
X748AH ADD: Redundant Power Supply
C986AC ADD: EXT BATTERY CONNECTION KIT
X551AG ADD: Door Lockable
CA00213AA ADD: BATTERY INTERNAL (Note: for CTS100 only)

10.1.5. Spare Part Kits for Compact TETRA

The following Spare Part Kits are recommended and available via MOL to a special price.
10.1.5.1. Spare Part Kit for CTS100

GM0010A SPARE PART PACKAGE FOR CTS100
Mandatory options for the frequency ranges:
CA00218AA: 380 MHz
CA00219AA: 410 MHz
CA00220AA: 450 MHz
CA00221AA: 800 MHz
Included in the CTS100 Spare Part Kits:
1 TF413 TX Filter
1 TMA412 Tower Mounted Ampl.
1 AI411 Ant. Interface
1 TH412 TX Hybrid Combiner
1 Backplane for 2-ch. BS
1 TR411 Transceiver
1 BSC411 Base Station Controller

CA00218AA: 380 MHz
CA00219AA: 410 MHz
CA00220AA: 450 MHz
CA00221AA: 800 MHz
1 TF411 TX filter 25dB

1 RMD414 Dual 4-way div.
1 TR411 Transceiver
1 RTC414 RF TEST LOOP 4-way Combiner
1 TC411 4-way TX Combiner


CA00218AA: 380 MHz
CA00219AA: 410 MHz
CA00220AA: 450 MHz
CA00221AA: 800 MHz
1 TF411 TX filter 25dB

1 RMD411 Dual 8-way div.
1 TR411 Transceiver
1 RTC411 RF TEST LOOP 8-way Combiner
1 TC411 4-way TX Combiner
10.1.5.4. Expansion Kits for Compact TETRA Base Stations

The kits below are only intended to expand existing Base Stations and includes required software
licences where applicable.
EDN12462AA BAT412 Battery Unit Kit 48V/7Ah (for CTS100 only)
GM0013A Base Station Controller Redundant (Release 2)
EDN124822AA Door 8U with lock
EDN124260AA External Battery Connection Kit (without battery)
EDN124151AA PS411 Power Supply Redundant
Expansion Kits to add Carriers to existing Base Stations:

To expand Base Stations for additional Carriers the following Expansions Kit must be ordered by
MOL. It is not possible to use the Spare Part Transceivers to expand a system to more carriers
because in the Expansion Kits the required Software Licences are included.
Note: For every addition carrier a separate Expansion Kit has to be used.
e.g. to expand from 4 to 6 carriers you have to use 2 Kits:
1. Expansion from 4 to 5 carriers
2. Expansion from 5 to 6 carriers

For CTS100/200/300:
GM0015A Expansion 1 to 2 Carriers

CA00218AE: 380 MHz
CA00219AE: 410 MHz
CA00220AE: 450 MHz
CA00221AE: 800 MHz
The Kit includes:
1 TR411 Tranceiver
Software Licence
For CTS200/300:

CA00218AF: 380 MHz
CA00219AF: 410 MHz
CA00220AF: 450 MHz
CA00221AF: 800 MHz
The Kit includes:
1 TR411 Tranceiver
1 Power Supply
Software Licence

CA00218AG: 380 MHz
CA00219AG: 410 MHz
CA00220AG: 450 MHz
CA00221AG: 800 MHz
The Kit includes:
1 TR411 Tranceiver
Software Licence
For CTS300:

CA00218AH: 380 MHz
CA00219AH: 410 MHz
CA00220AH: 450 MHz
CA00221AH: 800 MHz
Includes:
1 TR411 Tranceiver
1 TC411 4-way TX-Combiner
1 TX Combinger 4-8 Ch. Kit CTS300
Software Licence


CA00218AJ: 380 MHz
CA00219AJ: 410 MHz
CA00220AJ: 450 MHz
CA00221AJ: 800 MHz
Includes:
1 TR411 Tranceiver
1 Power Supply
Software Licence

CA00218AK: 380 MHz
CA00219AK: 410 MHz
CA00220AK: 450 MHz
CA00221AK: 800 MHz
Includes:
1 TR411 Tranceiver
Software Licence

CA00218AL: 380 MHz
CA00219AL: 410 MHz
CA00220AL: 450 MHz
CA00221AL: 800 MHz
Includes:
1 TR411 Tranceiver
Software Licence

10.1.6. Field Replaceable Units (FRU) Kits for the Basestations

This FRU kits are orderable via MOL only. None of the FRU includes any software licences and they
may only be used to purely replace existing components of the system.
EDN124201A BSC411 Base Station Controller

EDN124251A PS411 Power Supply AC/DC
EDN124262A BAT412 Battery Unit 48V/7Ah (for CTS100 only)
EDN124822A Door 8U with lock
EDN124001A TR411 Transceiver 380-400MHz
EDN124511A TMA412 Tower Mounted Amplifier 380-390MHz
EDN124401A AI411 Antenna Interface Unit 380-400 MHz 10MHz
EDN124408A AI411 Antenna Interface Unit 805-935MHz 45MHz
EDN124681A TH412 TX Hybrid Combiner 390-400MHz
EDN124731A TF413 TX Filter 390-400MHz
EDN124441A RMD414 Dual 4-way divider 360-460MHz
EDN124461A RTC414 RF TEST LOOP 4-way combiner 370-470MHz
EDN124601A TC411 4-way TX combiner 390-400MHz
EDN124701A TF411 TX Filter 25dB 390-400MHz
EDN304303A Backplane for CTS100

10.2. Gateway Server Equipment List
10.2.1. CTG-1 Gateway Server Modelling:
GM0004A CTG-1 GATEWAY SERVER, includes:

Tower
PDG Interface Card
Disp. LAN Interface Card
E1 Interface Card
T0 ISDN Interface (4x2B+D) Card
TETRA Codec Card
Windows 2000, English
NMS/SUM Server SW
Monitor 17”, CRT
Keyboard US
Mouse
10.2.2. CTG-1 Gateway Server Spare Part Kit:
XXXXXXX CTG-1 GATEWAY SERVER, Replacement Server includes:

Tower
PDG Interface Card
E1 Interface
T0 ISDN Interface (4x2B+D) Card
TETRA Codec Card
Windows 2000, English
NMS/SUM Server SW

10.3. Dispatcher Workstation Equipment List

10.3.1. CTD-1 Dispatcher Workstation Modelling:
GM0005A CTD-1 DISPATCHER WORKSTATION, includes:

Tower
Audio Ancillary Interface
Dispatcher LAN Interface Card
Windows 2000
NMS/SUM Client SW
Dispatcher SW
Headset
Loudspeaker
TFT Screen 17”
Keyboard US
Mouse
10.3.2. CTD-1 Dispatcher Workstation Spare Part Kit:
XXXXXXX CTD-1 Dispatcher Workstation, includes:

Tower
Audio Ancillary Interface
Windows 2000
NMS/SUM Server SW
Dispatcher Software

10.4. Ordering Guide for Compact TETRA (via MOL only)

Selecting the correct Customer Number for ordering.
When ordering Compact TETRA equipment you may not be ordering using your regular Customer
Number. The Customer Number you will need to order against will have been forwarded you by
email. If you do cannot find it, please contact your regional Motorola Sales Representative.
To change your Customer Number, log into Motorola Online as normal, and select Browse Catalogue
from the Buying Centre. Click on the “change” button at the top right hand corner of the screen. From
here you should select the correct Customer Number for ordering and click the “continue” button to
return to the Browse Catalogue page. In addition, of you wish to buy one of the Compact TETRA
demo packages you should select below the correct Customer
Number before confirming.

Ordering your Compact TETRA system.
Compact TETRA systems components are added to the Shopping Cart in exactly the same way as
other items on Motorola Online. You can use the Quick Buy function if you know all the item numbers
or you can use the Browse Catalogue which has been set up to ordering as easy as possible. Once
you’ve selected the right Customer Number for ordering you will see 4 sections in the Browse
Catalogue that you can use to order Compact TETRA items:
The top 2 items, Contract Packages and Motorola Packages will allow you to buy the pre-configured
demo packages for Compact TETRA. The Contract Packages will be available if you have no
purchased a demo package before and wish to take advantage of a high discount available, whereas
the Motorola Packages section will allow you to purchase additional demo packages at the normal
price.
To order your subscribers select the Tetra Subscriber section and purchase
them in the same way you would order any other Motorola subscriber
through Motorola Online. To order infrastructure items select the Compact
Tetra heading which will take you to the Browse Catalogue screen for the
infrastructure, which has been organised by frequency. Click on any of the
infrastructure components to take you to the detailed product page showing
technical details and the price of the item EXCLUDING any options. As each
of the Base Stations is option and frequency dependant, Motorola Online
requires you to enter the starting frequency of the TX Combiner and all of the
options before you can check out your Shopping Cart. You must therefore
enter each Base Station as a separate line where the frequency or option
configuration is different.

For example, if you require 3 CTS100 Base Stations with 1 Transceiver and 2 of them have a TX
Combiner Frequency starting at 393Mhz with the other starting at 397Mhz you must enter 1 line with a
quantity of 2 and a completely separate line with a quantity of 1.
Once a Base Station is added to your Shopping Cart you will need to configure it before you can
check out. Items that are
not configured will be
displayed with warning
messages in red. To
continue click on the
Configure button. On the
Configure page you will
see all the items in your
Shopping Cart that need either option configurations (denoted by *) or personality configuration
(denoted by #). Clicking on one of these will bring
up its option on the lower half of the screen. Select
the options you want and click to take
you to the personality configuration screen.
Please note that when ordering you must supply the starting frequency for the TX Combiner. All
subsequent TX channel frequencies must be within 5 MHz (14 MHz for 800 MHz band) of this
frequency. You will be asked to enter the lowest TX frequency for your base station. THIS IS THE
STARTING FREQUENCY OF YOUR COMBINER.
Band TX Range Band- Band- Range of Starting Frequencies

with TX- with of Starting definition for higher TX-
Filter TMA Frequency Frequencies
380–400 MHz 390–400 MHz 5 MHz 5 MHz 390–395 MHz 395-400 MHZ = 395 MHz
410–430 MHz 420–430 MHz 5 MHz 5 MHz 420–425 MHz 425-430 MHz = 425 MHz
450–470 MHz 460–470 MHz 5 MHz 5 MHz 460– 465 MHz 465-470 MHz = 465 MHz
805–870 MHz 850–870 MHz 20 MHz 14 MHz 850–854 MHz 854-870 MHz = 854 MHz
Example:
For a Base Station you have got the following frequencies from your frequency authority:
RX 416,025 MHz / TX 426,025 MHz
RX 418,525 MHz / TX 428,525 MHZ
The Starting Frequency to enter into MOL is 425 MHz as the lowest TX frequency in your system
exceeds 425 MHz. This means your window for the TX filter is 425-430 MHz (5 MHz filter bandwith).
You will also be asked to enter the contact details for your system support contract and invoice, which will
be billed separately.
Once you have added all the items to your Shopping Cart you can precede through Checkout in the normal
way.

11. Abbreviations
AI Air Interface, specifically, Tetra Air Interface

AIRM Air Interface Resource Manager (CSU)
ANT Antenna Subsystem (HWCI)
ASCII American Standard Code for Information Interchange
ASSI Assigned Short Subscriber Identity
BLE Base Station Link Entity (CSU)
BS Base Station
BSC Base Station Controller
CI Configuration Item
CLIP Calling Line Identification Presentation
CM Configuration Management
CMCE Circuit-Mode Control Entity
CODEC Coder / Decoder
COTS Commercial Off The Shelf
CSCI Computer Software Configuration Item
CSU Computer Software Unit
DA-IF Dispatcher Access Interface
DD Data Distribution (CSU)
DISPC Dispatcher Client (CSCI)
DISP-GW Dispatcher Gateway
DISPS Dispatcher Server (CSCI)
DSP Digital Signal Processor
DVR Datenverarbeitungsregister
ESN External Subscriber Number
ETS European Telecommunications Standard
ETSI European Telecommunication Standard Institute
FAT Factory Acceptance Test
FDIC Full-Duplex Individual Call
FREDAM Project name for Dimetra-C product development
FTP File Transfer Protocol
GDDB Global Dynamic Database (CSU)
GPS Global Positioning System
GSDB Global Static Database (CSU)
GSSI Group Short Subscriber Identity
GUI Graphical User Interface
GWPC Gateway PC
HDLC High-Level Data Link Control
HMI Human-Machine Interface
HW Hardware
HWCI Hardware Configuration Item
ICMP Internet Control Message Protocol
IF Interface
IOP Interoperability, specifically, Tetra SwMI/MS interoperability

IP Internet Protocol
IPv4 Internet Protocol Version 4
ISDN Integrated Services Digital Network
ISDN-BR ISDN Basic Rate
ISDNGW ISDN Gateway
ISDN-PR ISDN Primary Rate
ISSI Individual Short Subscriber Identity
ITSI Individual Tetra Subscriber Identity
ITU-T International Telecommunications Union
LA Location Area
LAN Local Area Network
LE Late Entry
LLC Logical Link Control (CSU)
MAC Medium Access Control
MCCH Main Control Channel
MLE Mobile Link Entity
MM Mobility Management
MNT Maintenance
MoU Memorandum of Understanding, specifically: Tetra MoU: An organisation
of parties (manufacturers, customers, standardisation bodies) interested in
and promoting the Tetra standard.
MS Mobile Station
MTBF Mean Time Between Failures
NWMC Network Management Client (CSCI)
NWMS Network Management Server (CSCI)
PABX Private Access Branch Exchange
PABX
PABX-GW PABX Gateway
PC Personal Computer
PC Priority Call
PC Personal Computer
PCM Pulse Code Modulation
PD Packet Data
PDCH Packet Data Channel
PDG Packet Data Gateway (CSCI)
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PPC Pre-emptive Priority Call
PABX Private Access Branch Exchange
PSTN Public Switched Telephone Network
PTT Push-To-Talk
RA Registration Area
RAM Random Access Memory
Rev. Revision
RF Radio Frequency
SCCH Secondary Control Channel
SCK Static Cipher Key

SDIC Semi-Duplex Individual Call

SDS Short Data Service
SMCA Subscriber Management Client Application (CSCI)
SMSA Subscriber Management Server Application (CSCI)
SNDCP Subnetwork-Dependent Convergence Protocol
SPCDD Subscriber Profile and Configuration Data Distribution (CSU)
SSDD System/Subsystem Design Document
SSI Short Subscriber Identity
SUM Subscriber Management
SW Software
SwMI Switching and Management Infrastructure
TAI TETRA Air Interface
TCH Traffic Channel
TCP Transmission Control Protocol
TEA2 Tetra Encryption Algorithm 2
TETRA Terrestrial Trunked Radio
TIP Tetra Interoperability Profile
TTR Tetra Technical Report (ETSI)
TS Timeslot
TMA Tower-Mounted Amplifier
TPI Talking Party Identification
TRANS Transceiver
TTR Tetra Technical Report
TX Transmitter, Transmission
UDP User Datagram Protocol
UGC Unacknowledged Group Call
USWITCH U-Plane Switch (CSCI)
VAC Volt Alternating Current
VoIP Voice over IP


Compact Tetra System Planner

Uploaded by

Copyright:

Available Formats

Compact Tetra System Planner

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Compact Tetra System Planner

Uploaded by

Copyright:

Available Formats

Compact TETRA System Planner

Issue April 2002

Rev. Date Changed Page(s) Cause of Change Implemented

1.0 05. April 2002 All pages New Document W. Liegl

Compact TETRA Section 6 System Planner

3. System Planning Process ...................................................3-1

4. System Overview .................................................................4-1

Compact TETRA Section 6 System Planner Page: C-1

5.1.10. System Configurations ................................................................................... 5-12

Compact TETRA Section 6 System Planner Page: C-2

5.9.3. Transportability............................................................................................... 5-48

9. Third Party Applications......................................................9-1

Compact TETRA Section 6 System Planner Page: C-3

10.3.2. CTD-1 Dispatcher Workstation Spare Part Kit: ............................................... 10-8

11. Abbreviations .....................................................................11-1

Compact TETRA Section 6 System Planner Page: C-4

The system is resilient, flexible and extensible

Single/Multisite: This mode offers a full-featured network of 1 to 8 base stations connectable to

Easy to Sell, Order, Install, Operate and Maintain

Compact TETRA Section 6 System Planner Page: 1-1

System Partners can add value

The system is cost competitive in 1 to 8 site configurations

The system employs low-cost GPS receivers for time synchronisation.

Compact TETRA Section 6 System Planner Page: 1-2

1.3. Referenced Documents

1. Introduction & System Overview

2. Hardware Specifications and Installation

3. System Installation, Configuration and Maintenance

4. System Operation (Dispatcher)

6. System Planner (this document)

Tools available from MOL:

Quick Price Calculation Sheet

Simple Traffic Calculator

1.3.2. External Documents

Links to download external documents from:

Compact TETRA Section 6 System Planner Page: 1-3

Compact TETRA Section 6 System Planner Page: 1-4

In the second part there is a table of key numbers.

2.1. Overview of Equipment

CTS 100 Base Station up to 2 carriers

CTS 200 Base Station up to 4 carriers

CTS 300 Base Station up to 8 carriers

CTG-1 Gateway Server incl. 4xISDN card (8 phone lines)

CTD-1 Dispatcher Workstation (up to 8 Workstations possible)

Internal Backup Battery Kit (CTS100 only)

External Battery Connection Kit

Door for the racks

Redundant Power Supply

Redundant Base Station Controller (Release 2)

Carrier Upgrade Kit

Recommended Spare part Kit for the Base Stations

Portable Radio MTP700

Portable Radio MTH500 (from mid 2002)

Mobile Radio MTM700

Accessories for Portable and Mobile Radio

2.1.2. Equipment not orderable directly from Motorola via MOL

Fast EtherNet HUB for the Dispatcher Network

Base Station Antennas for RX, TX and GPS

Compact TETRA Section 6 System Planner Page: 2-1

Compact TETRA Section 6 System Planner Page: 2-2

Conventional (non-trunked) analogue Repeater Systems – generally low functionality, low

SmartNet - single site analogue trunking

Analogue Smartzone – multisite analogue trunking

IDEN – multisite digital trunking

Coverage and capacity requirements

Determining how to provide the functionality required by the customer.

Existing Compact TETRA functionality (Certified and shipping)

Future Compact TETRA functionality (planned for later releases)

Other functionalities will be considered by business case

Individual Call (Full or Half-Duplex)

8 Carriers (32 logical channels – 1 Control + 31 Voice/Data Channels)

Individual Call (Full/Half Duplex)

Individual Call (Full/Half Duplex)

AC/DC power supply including battery charge function

Optional built-in backup battery kit, 48V/7Ah

Optional redundant AC/DC power supply

Internal 2-Way-Hybrid Combiner

Base Station Controller

Optional redundant BSC

Tower Mounted Amplifier (TMA), external

GPS receiver built-in for synchronization

Measures (HxWxD): 476,6x542x520 mm

Weight: 47 kg (fully equipped)

Power Consumption: 280 Watts (fully equipped)

AC/DC power supply including external battery charge function

Terminal for external backup battery kit

Optional redundant AC/DC power supply

Base Station Controller BSC

Optional redundant BSC

Tower Mounted Amplifier (TMA), external

GPS receiver built-in for synchronization

Measures (HxWxD): 1010x542x520 mm

Weight: 93 kg (fully equipped)

Power Consumption: 512 Watts (fully equipped)