ETSI TR 102 022-1 V1.1.1 (2012-08)

Technical Report
User Requirement Specification;
Mission Critical Broadband Communication Requirements

�
2 ETSI TR 102 022-1 V1.1.1 (2012-08)

Reference
DTR/TETRA-01202
Keywords
broadband, data, TETRA, TETRAPOL, user
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2012.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI TR 102 022-1 V1.1.1 (2012-08)
Contents
Intellectual Property Rights . 4
Foreword . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definitions and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 6
4 Mission Critical Broadband Requirements . 7
4.1 General . 7
4.2 Systems Requirements for Professional Users . 8
4.3 Operational Requirements . 9
4.3.1 Roaming compatibility . 9
4.3.2 Interoperability between present TETRA, Tetrapol or P25,BB MSs and present disp atc hers . 9
4.3.3 Priority . 9
4.3.4 QoS . 9
4.3.5 Data throttling . 10
4.3.6 Video rate. 10
4.3.7 Maintenance . 10
4.4 Application requirements of PPDR . 10
4.4.1 Location data . 10
4.4.2 Multi-media . 11
4.4.3 Office applications . 11
4.4.4 Download operational information . 11
4.4.5 Upload operational information . 11
4.4.6 Online database enquiry . 11
4.4.7 Miscellaneous . 12
4.5 Ranking of the Criticality of Applications. . 12
4.5.1 Highest Priority, "Now" Group . 12
4.5.2 Second Priority, "Short" Group . 12
4.5.3 Third Priority, "Medium" Group . 13
4.5.4 Fourth Priority "Long and Future" Group . 13
4.6 Expected Capability of TEDS . 13
4.7 Applications identified today that cannot be met by TEDS . 15
4.8 Ranking of those Applications by Customer Need . 16
4.9 Requirements during Migration to a New Technology Solution . 16
5 If LTE is chosen . . 17
5.1 Some Blue Sky Applications for the Future. . 17
Annex A: LEWP Matrix of Requirements . 18
Annex B: Transport Requirements . 25
B.1 Rail user requirements . 25
B.2 Transport for London . 25
Annex C: Utilities Requirements . 26
C.1 Electricity . 26
History . 27

ETSI
4 ETSI TR 102 022-1 V1.1.1 (2012-08)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://ipr.etsi.org).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Report (TR) has been produced by ETSI Technical Committee Terrestrial Trunked Radio (TETRA).
The present document is a potential forerunner to a multi-part deliverable covering the User Requirement Specification
(URSs) TETRA Release 3.
The user requirements contained in the present document are described in non-technical terms and are based on
discussions in TC TETRA (WG1 and WG4), LEWP, Project MESA and the TETRA and Critical Communications
Association.
ETSI
5 ETSI TR 102 022-1 V1.1.1 (2012-08)
1 Scope
The present document provides the User Requirement Specifications for Mission Critical Broadband Communications.
The present document describes the functionalities which are most needed by users and the requirements they make on
the technology The present document is applicable to the specification of Mission Critical Broadband equipment.
The URS will support TC TETRA to guide the introduction of broadband features.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are necessary for the application of the present document.
Not applicable.
2.2 Informative references
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI TS 170 001: "Project MESA; Service Specification Group - Services and Applications;
Statement of Requirements (SoR)".
[i.2] ETSI TR 102 021-2 (V1.3.1): "Terrestrial Trunked Radio (TETRA); User Requirement
Specification TETRA Release 2.1; Part 2: High Speed Data".
[i.3] Report for the TETRA Association-Public safety mobile broadband and spectrum needs. Final
th
Report 8 March 2010, Analysys Masons.
[i.4] ETSI TR 102 628: "Electromagnetic compatibility and Radio spectrum Matters (ERM); System
reference document; Land Mobile Service; Additional spectrum requirements for future Public
Safety and Security (PSS) wireless communication systems in the UHF frequency range".
[i.5] Connecting America: "The National Broadband Plan", Chpt. 16 Public Safety, FCC March 2010.
[i.6] The FCC Plan for a Public Safety Broadband Wireless Network, Jennifer A. Manner, Stagg
Newman, Jon M. Peha, 2010, Telecommunications Policy Research Conference.
[i.7] U.S. Department of Homeland Security Public Safety Communications Evolution.
[i.8] U.S. Department of Homeland Security Interoperability Planning for Wireless Broadband.
[i.9] Public Safety Mobile Broadband communications network -Operational requirements, Govt. Of
Canada.
[i.10] Evolution of TETRA To a 4G All-IP Broadband Mission Critical Voice Plus Data Professional
Mobile Radio Technology - Martin Steppler.
ETSI
6 ETSI TR 102 022-1 V1.1.1 (2012-08)
[i.11] LEWP and RECG Matrix.
[i.12] User Requirements -Rail, TCCA Rail Forum, Trans 12-01-01.
[i.13] ETSI TR 102 580: "Terrestrial Trunked Radio (TETRA); Release 2; Designer's Guide; TETRA
High-Speed Data (HSD); TETRA Enhanced Data Service (TEDS)".
[i.14] ETSI TR 102 021-10: "Terrestrial Trunked Radio (TETRA); User Requirement Specification
TETRA Release 2.1; Part 10: Local Mode Broadband".
th
[i.15] Public Safety 700MHz Broadband Statement of Requirements Version 0.6 Nov. 8 2007.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
mission critical broadband: work programme within ETSI Project TETRA to enhance the services and facilities of
TETRA, Tetrapol and P25 in order to meet new user requirements, utilize new technology and meet user needs into the
future within the traditional market domains of PMR and PAMR
P25, Project 25 or APCO -25: suite of standards for digital radio communications mandated for Public Safety in the
US
TETRAPOL: FDMA, professional mobile radio system developed by MATRA/EADS
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ANPR Automatic Number Plate Recognition
API Application Programming Interface
APL Automatic Person Location
AVL Automatic Vehicle Location
AVLS Automatic Vehicle Location System
BB Broad Band solution for PMR
CCC Command & Control Centre
COM COMmunication
CSD Circuit Switched Data
DMO Direct Mode Operation
DQPSK Differential Quadrature Phase Shift Keying
ECG ElectroCardioGram
ERO European Radiocommunications Office
ETSI European Telecommunications Standards Institute
GIS Geo Information Service
GPRS General Packet Radio Services
GSM-R Global system for Mobile Communications-Rail
GTSI Group TETRA Subscriber Identity
HSD High Speed Data
IMSI International Mobile Subscriber Identity
IMT International Mobile Telecommunications
IP Internet Protocol
ITSI Individual TETRA Subscriber Identity
LEWP Law Enforcement Working Party
LTE 3GPP Long Term Evolution (4G)
LTE-Advanced LTE meeting the IMT Advanced Requirements
MCCH Main Control CHannel
MS Mobile Station
ETSI
7 ETSI TR 102 022-1 V1.1.1 (2012-08)
PABX Private Automatic Branch eXchange
PD Packet Data
PDA Personal Digital Assistant
PEI Peripheral Equipment Interface
PIM Personal Information Management
PMR Private Mobile Radio
PPDR Public Protection and Disaster Relief
PSS Public Security and Safety
PTT Push To Talk
QAM Quadrature Amplitude Modulation
QoS Quality of Service
RCEG Radio Committee Expert Group part of the Law Endforcement Working Party
RF Radio Frequency
SAT SATellite
SCADA Supervisory Control And Data Acquisition
SDR Software Defined Radio
SDS Short Data Service
TEDS TETRA Enhanced Data Services
TETRA TErrestrial Trunked RAdio
TR Technical Report
UIC International Union of Railways
URS User Requirement Specification
WAP Wireless Application Protocol
4 Mission Critical Broadband Requirements
4.1 General
With increasing use of data in PPDR, capacity issues for voice and data on existing TETRA 1,TETRAPOL and P25
networks together with the user experience of 3G terminals and applications there has been an increasing demand for
more data throughput on PPDR systems. TEDS goes some way in this direction and requirements for High Speed Data
were captured in [i.2] but with an eye to the long term future users are expecting that they will want a higher data rate
than TEDS offers to support applications such as streaming video. This and more was anticipated in the MESA project
and the requirements in [i.1] are informative about the issues to be addressed as well as detailing operational scenarios
where such applications would be needed.
The wish is to have the benefits of TETRA,TETRAPOL or P25 functionality, robustness and security supported on a
broadband bearer in order to fulfil the operational tasks of the future. In some cases the driver is the capacity to support
applications such as video in others it is to create more capacity for voice traffic alongside data applications that in
themselves do not require particularly high data rates, To give a multi-media capability to PPDR or just to give narrow
band data capability to many users in the same area will both most efficiently be satisfied with broadband.
One way that users can and have responded to the need to provide extra capacity for data is to buy data services from
public operators. These services whilst useful for back office applications are not suitable for PPDR in mission critical
situations as in such situations the service cannot be relied on. To counteract this some arrangements have been made
with operators to give PPDR priority in times of crisis. This can on a temporary basis improve accessibility but does not
guarantee a service.
In the USA it has been mandated that the technology for PPDR data will be LTE (2x5 MHz of dedicated spectrum was
initially allocated for PPDR and a further 2x5 MHz has recently been granted). Originally this was thought to come to
PPDR on a priority call basis from a 10 MHz allocation to public operators. This latter approach for providing capacity
for emergencies had not been shown to work yet. The principle though that PPDR does not need all of its spectrum
capacity all of the time is however recognised. There is a definite need to plan for surge capacity in times of crisis. This
means either overproviding spectrum resource for "normal" usage or having further spectrum needed in particular
locations at time of crisis in a seamless way and with the same priority and access as the dedicated spectrum resource.
ETSI
8 ETSI TR 102 022-1 V1.1.1 (2012-08)
One assumption in Connecting America-The National Broadband Plan and further detailed in The FCC Plan for a
Public Safety Broadband Wireless Network [i.5] and [i.6] is that the LTE terminals for PPDR will be low cost as they
are the same technology as the general public will use but the requirements for functionality and robustness amongst
others that PPDR users have for their terminals will impact this. Nonetheless there is an economic benefit from re-use
of technology and users in Europe might well be interested in using technology that is also use in North America and
elsewhere. The Public Safety Requirements for Broadband in the US are detailed in [i.15] (these were formulated prior
to the D Block auction that failed and are being re-considered. They are nonetheless a good reference).
The way in which data use evolves in PPDR is likely to depend upon investment in infrastructure and Analysis Masons
in their report for the TETRA Association [i.3] identified four possible growth scenarios ranging from steady growth
with limited data services purchased from public operators for non-critical applications to full multi-media reliance for
operations with either dedicated networks or highly upgraded commercial networks. In the current economic climate
investment in infrastructure is likely to be delayed or constrained favouring where possible the use of services from
public operators. Depending on the degree of criticality of the data used on these there will need to be improvements in
the security, access, priority management and resilience of such services even when used as an overlay.
Spectrum availability will impact both the timing and nature of the solution. Clearly any solution has to efficiently use
spectrum but in Europe it may be that large amount of harmonised spectrum cannot be found and therefore small and
different blocks of non-contiguous spectrum may have to be worked with. The amount of spectrum required for PPDR
broadband was estimated in [i.4]. This may need to be re-visited once WG4 has sized the throughput requirements
outlined here and in the LEWP document [i.11].
Other users such as utilities and transport also see a need for more capacity for voice and data with the type of
functionality and security that TETRA,TETRAPOL or P25 offers [i.12]. In particular UIC will need a replacement in
place for GSM-R by 2025 and the replacement process in itself takes 5 years.
Most current users of TETRA,TETRAPOL or P25 would want a seamless migration to such improved capacity. There
is therefore a need to look at emerging requirements, understand which can be met with TETRA (TETRA1 &2) and
which go beyond that. Those that do need detailing sufficiently so that a technical solution can be found for them. This
bottom up approach assists in defining the minimum to be achieved from a solution and helps justify why broadband is
needed. There is also merit in a top down approach that sets out to ensure that any solution adopts the same goals as
those for the public domain so that professional users are offered no less a service. The current IMT targets are 1 Gbps
for stationary elements and 100 Mbps for mobile users. These are adopted in LTE-Advanced.
4.2 Systems Requirements for Professional Users
Analysis Masons concluded in their report for the TETRA Association, now the TETRA and Critical Communications
Association [i.3] that the requirements that PPDR and other users have of their systems today to support their way of
working will be needed for BB too. These are:
• Availability - in time (often) specified as three or four nines of availability (e.g. 99,98 % or better at all times).
Others specify different requirements for different times such as 99,9 %/year, 99,7 %/month and 99 %/24
hours.
• Control (Dedicated)- network control to allow prioritised access, reserved capacity to be guaranteed, queing of
traffic and the dynamic management of queues.
• Low Latency - very short call set up times (< 200 ms) and very limited end to end voice/data transmission
delay (< 1 s)
• Interoperability - between users (e.g. police, fire, ambulance) and across borders
• Coverage (national) - defined by geography rather than population e.g. 99 % of landmass. Also see 99,5 %
(outdoor mobile), 65 % or better (indoor mobile), 99,9 % (air to ground).
• Resilience/Robust Networks - need layers of redundancy. Central network switching to be fully redundant
with geographically distributed switching. Interconnection between bases to be resilient and include back-ups
between key base sites. Need for fallback sites if the primary fails. Backup power supplies required at different
levels depending on criticality.
• Layered Security - authentication, air to air encryption, end to end encryption.
ETSI
9 ETSI TR 102 022-1 V1.1.1 (2012-08)
• Ability to support mixed traffic (voice and data) - integrated network solution supporting transmission of
mixed traffic types to enable the use of the same technology in different environments/operations/missions
• Seamless handover - not in the Masons summary but a general need. For rail use there should be seamless
handover while transmitting in a call; at speeds up to 300 km/h (500 km/h in the future). Seamless is defined
as less than a 300 milliseconds break in connection. Full functionality also has to be supported at these speeds.
In addition TETRA, TETRAPOL and P25 standardisation has only applied to the air interface. Users [i.10] see are
interested in the broadband solution including reference points within the SwIMI so that there can be more competition
for the elements of the system. This is desirable but not critical.
For mobile users it is expected that broadband capability and the applications defined below can be powered by
batteries that have sufficient capacity to support a 10 hour shift.
With increasing pressure on resources it is expected that new technology will bring with it reduced power operating
requirements and increased environmental sustainability. There are a number of opportunities to reduce power using
sleep mode on terminals or base stations during inactive periods and opportunities to extend the life of products and
increase the amount of re-cycle able material in them.
4.3 Operational Requirements
The services required should be built upon that offered in the TETRA, TETRAPOL and P25 standards. These include
for voice:- Group calls, encrypted individual and group calls with authentication, individual calls to command centre
PABX and /or public telephone networks, direct mode operation between terminals, emergency calls and air to ground
calls .For data it includes SDS, packet data, status messaging and WAP support. There are further services that will be
needed for BB and these include the following (clauses 4.3.1 to 4.3.7).
4.3.1 Roaming compatibility
TETRA, TETRAPOL or P25 services in use on a present TETRA, TETRAPOL or P25 cell should continue to work
with minimal interruption and without loss of pre-arranged information (e.g. QoS information) when an MS roams to a
BB cell and vice versa. Voice calls, packet data connections and security should work without significant interruption
or loss of partially-transferred data . We should expect roaming between present TETRA, TETRAPOL or P25 and BB
to be a common occurrence, both during the roll-out of BB and because BB cells will most probably have a shorter
range than present TETRA, TETRAPOL, P25 cells. Authentication, air-interface encryption and end-to-end encryption
should continue to work without interruption.
4.3.2 Interoperability between present TETRA, Tetrapol or P25,BB MSs
and present dispatchers
An MS using a present TETRA, TETRAPOL or P25 cell should be able to communicate (without any special measures
by present MSs) with an MS using a BB cell, and vice versa. MSs using a BB cell should be able to communicate with
present dispatchers. End-to-end encrypted voice calls (individual and group), packet data, SDSs, etc., should work
without intermediate decyphering and re-encyphering).
4.3.3 Priority
There should be a priority mechanism that determines order of access and once access is granted the relative degree of
degradation of services if the system becomes congested.
Data priority in the present TETRA standard is complex and does not work perfectly. A simpler and more effective data
priority mechanism is required for BB. In this it is envisaged that the MS would be able to indicate the data priority of
every reservation requirement.
4.3.4 QoS
The BB solution should be capable of managing applications which have different requirements for QoS such that in a
congested network applications with a low QoS requirement can be slowed to permit those with a higher QoS to be
passed. The solution should support parameters for setting QoS and managing them dynamically.
ETSI
10 ETSI TR 102 022-1 V1.1.1 (2012-08)
4.3.5 Data throttling
It would be useful to provide a means of rapid end-to-end throttling of prolific data sources (e.g. video) when the link
quality drops at the receiving end, to avoid the build up of undeliverable packets in the SwMI or the sending MS;
e.g. when the data recipient moves out of a BB cell into a present QAM cell. This is partly a PEI and application issue,
but the SwMI may have to initiate flow control messages directed at a sending application. Possibly there is already a
protocol for this in the IP domain.
4.3.6 Video rate
It is recognised that some operational situations require high resolution, real time video whilst others do not. The
solution should be able to support restricting the number of high resolution channels to reduce congestion.
4.3.7 Maintenance
There needs to be a way of assuring that the chosen solution can be kept up to date and benefit from economies of scale
wherever possible and on a sustained basis. There will need to be a network management interface and a protocol for
this. It should be possible to manage the end user devices over the air.
There are common elements here with the operational requirements for Public Safety in the US and in Canada [i.8] and
[i.9].
4.4 Application requirements of PPDR
In the Analysis Masons study [i.3] they summarised all of the findings of the TETRA Association, now called the
TETRA and Critical Communications Association and presented case studies and possible scenarios for the evolution of
data that included as an option full multi-media reliance. This is the scenario that is most relevant to broadband. For this
they saw, "A diverse range of mobile broadband applications including high quality imaging and real-time video take
off, with widespread use across the public safety sector. Widespread information sharing improves the establishment of
common operating pictures at incidents, facilitates real time decisions at incidents and enables the introduction of new
video services such as remote medical applications, and personal characteristics recognition."
One of the inputs they used was the ERO summary of current public safety applications to CEPT, FM PT38.
More recently the LEWP and RECG [i.11] met to create a matrix of needs for mobile data. This has considerable
overlap with the Masons report The result is appended. The needs are categorised as:
• Location data
• Multi-media
• Office Applications
• Download operational information
• Upload operational information
• Online database enquiry
• Miscellaneous
4.4.1 Location data
This covers automatic person or vehicle location data being fed back from terminals to the command and control centre
as well as positioning information or directions being fed back to terminals. These applications are available today.
Whilst the package size for such information is small (SDS) the use of high reporting rates can dominate the use of the
MCCH and impact system capacity. As the use of location information increases this will put system capacity under
pressure.
ETSI
11 ETSI TR 102 022-1 V1.1.1 (2012-08)
4.4.2 Multi-media
Included in this is:
• video to and from the command and control centre during pursuit so that other units may be informed and
intervene;
• video for fixed observation of people or other assets (stakeout);
• video at the scene of a disaster or event to inform command and control;
• video conferencing;
• the broadcast of photographs and the sending of photographs to specified groups.
The data rate needed to stream video has been assessed as being about 2 Mb/s whereas the sending of photographs is a
current application that is supported but one that will test capacity/speed of download if it becomes commonplace.
4.4.3 Office applications
The anticipated needs are PDA/PIM synchronisation and mobile workspace including public internet access. These
functions are being satisfied currently by devices such as smartphone but there is a desire to have this functionality in
the same terminal as other communications and within the same secure system.
4.4.4 Download operational information
This envisages:
• the supply of text and image data from the command and control centre to terminals in the field and net centric
working;
• ANPR update hit list;
• the downloading of maps with annotations to field units and the downloading of command and control
information such as task management and briefings.
4.4.5 Upload operational information
This mirrors the category above and includes:
• the sending of incident information to the command and control centre;
• status information tied with location (currently supported), for ANPR/speed control an automatic upload to the
database including picture evidence from temporary fixed cameras and from vehicles;
• the forwarding of scanned documents such as licences, proof of identity;
• the sending of reports with pictures;
• the uploading of maps and schemes with included information;
• patient monitoring data such as ECG and monitoring the status of security workers using data from sensors
such as biometrics, man down, etc.
4.4.6 Online database enquiry
There is a need to make operational searches of own and external databases. Particular cases are:
• remote medical databases;
• number plate checking;
ETSI
12 ETSI TR 102 022-1 V1.1.1 (2012-08)
• biometrics such as fingerprints, cargo data;
• crash recovery (enquiry and updates).
4.4.7 Miscellaneous
This set of requirements include:
• the ability to update firmware, software and device & application settings over the air;
• GIS map updates over the air; automatic telemetry such as remote control and the presentation of information
from static sensors;
• capacity to be able to manage a large amount of communications in and out of a "hot spot" event including that
for a mobile communications centre; front office to back office application support;
• underwater communications to, for example, a scuba diver; alarming or paging (already supported); traffic
information and management systems support;
• radio bearing or tracking of special agent's operations;
• IMSI Catcher information to units and connection of units overseas to their home command and control centre.
4.5 Ranking of the Criticality of Applications.
In the LEWP/RCEG matrix of 40 applications the urgency of availability was rated as "now", "short" (<2 yr),
"medium"(2 yr to 5 yr) and "long"(>5 yr).Not surprisingly of the 12 in the "now" category 11 are reported as partly used
already although the one excluded (AVL) is definitely operational.
4.5.1 Highest Priority, "Now" Group
• Video on location
• Photo broadcast
• Photo to a selected group
• Status Information and location
• Reporting including pictures
• Operational database search
• ANPR-number plate check
• Biometric e.g. fingerprint check
• Alarming/paging
• Tracking
• IMSI Catcher information
• Plus AVL and APL information to command and control centre
4.5.2 Second Priority, "Short" Group
• AVLS data return (data to field units)
• Command and Control information including task management and briefings
• Patient Monitoring
ETSI
13 ETSI TR 102 022-1 V1.1.1 (2012-08)
• Crash Recovery System (download of data)
• Crash Recovery System (uploads of information)
• Connection from units aboard to their home command and control centre
4.5.3 Third Priority, "Medium" Group
• Video from field to command and control centre for following and intervention
• Video for fixed observation
• PDA PIM synchronisation
• Mobile workspace
• Incident information - download to field and Netcentric operation
• ANPR update list
• Download maps with annotation
• Incident information upload to command and control centre
• ANPR/speed control and "fixed" speed cameras
• Forward scanned documents
• Upload of maps with information
• Monitoring status of security worker
• Remote medical database services
• Cargo data
• Software update over the air
• GIS map updates
• Auto telemetry and remote control of devices
• Hot spot on disasters
• Front office/back office applications
• Traffic management systems
4.5.4 Fourth Priority "Long and Future" Group
• Video conferencing of operations
• Under water communications
4.6 Expected Capability of TEDS
The packet data throughput rate (table 1) that is achieved for TEDS is based on the level of QAM modulation and the
bandwidth. The initial bandwidth being offered by manufacturers is 50 kHz. The maximum rate therefore is with the
highest level of 64QAM (coefficient of 1) i.e. about 150 kbit/s. This is not likely to be practicable and 64QAM (2/3) is
more likely giving a data rate of about 100 kbits/s.
ETSI
14 ETSI TR 102 022-1 V1.1.1 (2012-08)
Table 1: Estimated throughput (kbit/s) for different TETRA HSD channels [i.13]
Channel bandwidth (kHz)
Modulation type
25 50 100 150
and coding rate
Uplink Downlink Uplink Downlink Uplink Downlink Uplink Downlink
π/4-DQPSK, r = 2/3 15 15
π/8-D8PSK, r = 2/3 24 24
4-QAM, r = 1/2 10 10 24 26 49 55 77 86
16-QAM, r = 1/2 19 20 47 51 98 110 153 173
64-QAM, r = 1/2 29 30 71 77 146 164 230 259
64-QAM, r = 2/3 39 40 94 103 195 219 306 345
64-QAM, r = 1 58 60 141 154 293 329 459 518

One of the reasons for selecting 50 kHz initially is the coverage that can be achieved and recognition that TETRA users
are looking for wide area coverage. This is illustrated in the figures 1 and 2.

Figure 1: Coverage footprint
ETSI
15 ETSI TR 102 022-1 V1.1.1 (2012-08)
Relative
Maximum 54 Mbps
3.5 GHz - WiMAX
(802.11g under
Data Rate
ideal conditions)
2.4 GHz - WiFi
400 MHz - TETRA TEDS
4 Mbps @ 5 MHz
100 kbs @ 50 KHz
WiFi
WiMAX
TEDS
4 km radius Less than 1 km radius
Coverage
30 metres
dense urban dense urban
indoors
footprint
Figure 2: Data rates vs coverage footprints of different radio applications
Analysis Masons have grouped a number of applications and mapped them against data rates.
4.7 Applications identified today that cannot be met by TEDS
Table 2 has been used to look at how data requirements may be met with TETRA. This is very general though and does
not consider the use case or the competing requirement for voice. For example if the receiving device for a photograph
is a handheld terminal with a small display then high resolution images may not be very critical and single slot transfer
may be acceptable. If the receiving terminal is a tablet pc then this will not be acceptable as higher resolution images
will be necessary in the same time period and the throughput requirement is increased significantly. Similar cases can
be made elsewhere.
Where voice capacity is already an issue then TEDS or broadband data offers a solution for data.
Table 2: Mapping of data services against TETRA variants
TETRA 1 TEDS
Circuit Data SDS Single Slot PD Multislot PD

Database Search
AVL
E-Mail
File Transfer e.g Still
images
Small files
Slow Scan video
Streaming video
Legend: Not suitable    Possible   Appropriate

When this table was put together originally it did not include SCADA/Telemetry.
CSD - works for SCADA, Image transfer and Slow scan video. So at least "possible".
SDS - works for SCADA, email and image transfer . So at least "possible".
ETSI
16 ETSI TR 102 022-1 V1.1.1 (2012-08)
Furthermore there are now some working examples of e-mail by SDS so this should also be regarded as possible.
Of the requirements listed for applications the ones that show high throughput and high operational use are video back
to the command and control centre during chases, video at disasters and mobile communication centres at hotspots re).
Whilst TEDS has been demonstrated streaming video it has been only low resolution and on an unloaded cell. It is
certain that this need will only be satisfied with broadband. The need for broadband elsewhere is not driven by a
particular application but by the total loading of the system which will impact response times and therefore ease of use.
It is multi-media support that defines the need for broadband.
4.8 Ranking of those Applications by Customer Need
Of the three applications identified the priorities for the LEWP group based on their urgency of requirement are:
• Video at disasters to inform co-ordinators, managers, etc.
• Video back to the command and control centre during chases to allow intervention.
• Hotspot mobile communication centres.
These examples of urgent communications needs are all likely to be provided by video/imaging devices with access to
PPDR BB, commercial BB, satellite services etc. to cover any eventuality.
4.9 Requirements during Migration to a New Technology
Solution
In a similar way to the migration to TEDS it is desirable to be able to seamlessly move from TETRA, TETRAPOL or
P25 voice and data services into broadband data services initially and then voice. If voice is supported on the broadband
service then the feel and functionality of the services should be the same as for TETRA, TETRAPOL or P25 so that
operational practices do not need to change. The security of the broadband service should be at least the same as that for
TETRA, TETRAPOL or P25 and use the same algorithms and key lengths albeit that preferably these will be an
evolution on those used today with longer key lengths to give sustained protection from interception. The broadband
service should have roaming and compatibility with TETRA, Tetrapol and P25 networks, perhaps not all in one device
(although with a SDR and multiple RF this might be possible).
If the solution to broadband is evolutionary then interfaces need to be developed to the intermediate technologies. For
example GPRS is used for many PPDR data applications today. If the migration strategy uses public services such as
these then multi-bearer terminals will be needed with appropriate protocols to use the correct bearer for any given
application. This protocol will need to select the bearer based on security, priority, size of data package and quality of
service available.
For TETRA users wishing to keep to dedicated networks and the same broad technology it is seen that the first step of
the migration is to TEDS. This can offer capacity to meet a number of the user requirements identified and is
deliverable in the short term. Due to the time taken to agree and clear broadband spectrum for PPDR and other PMR
users it is not expected that dedicated PPDR/PMR broadband will be available before 2021.
There are likely to be significant changes to operational procedures to benefit from broadband and these will need
development. For this reason an evolutionary approach is desired. This is recognised in the US plan [i.7].
ETSI
17 ETSI TR 102 022-1 V1.1.1 (2012-08)
5 If LTE is chosen
LTE defines a high speed radio access for IP, but 3GPP LTE standardisation scope does not define any PMR specific
services (no TETRA like Group or PTT services covered). TETRA voice services may therefore have to be provided
outside of the 3GPP LTE standard and LTE radio access network scope. The most obvious solution to fulfil TETRA
users need would be from a TETRA server; an independent ´TETRA PTT call processing server´ or more favourably
expanding the existing TETRA core network, providing today's TETRA services to the current TETRA1 radios to
support also LTE terminal users. This latter scenario would be best fit for an existing TETRA user/operator, as it would
most easily enable smooth expansion of TETRA services to LTE or other high speed IP radio terminals. Such a joint
core would provid
...