ETSI TS 102 181 V1.3.1 (2020-06)

Emergency Communications (EMTEL); Requirements for communication between authorities/organizations during emergencies

RTS/EMTEL-00049

General Information

• Status: Not Published
• Technical Committee: EMTEL - Emergency Communications
• Current Stage: 12 - Completion
• Due Date: 08-Jul-2020
• Completion Date: 24-Jun-2020

Standards Content (Sample)

TECHNICAL SPECIFICATION
Emergency Communications (EMTEL);
Requirements for communication between
authorities/organizations during emergencies

2 ETSI TS 102 181 V1.3.1 (2020-06)

Reference
RTS/EMTEL-00049
Keywords
emergency
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2020.
All rights reserved.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3 ETSI TS 102 181 V1.3.1 (2020-06)
Contents
Intellectual Property Rights . 6
Foreword . 6
Modal verbs terminology . 6
Introduction . 6
1 Scope . 8
2 References . 8
2.1 Normative references . 8
2.2 Informative references . 9
3 Definition of terms, symbols and abbreviations . 9
3.1 Terms . 9
3.2 Symbols . 11
3.3 Abbreviations . 11
4 Relations between authorities . 12
4.0 Introduction to the functional architecture . 12
4.1 Relation between PSAP and Emergency Control Centres . 14
4.2 Relation between PSAPs . 14
4.3 Relation between Emergency Control Centres . 14
4.4 Relation between Emergency Control Centres and mobile rescue teams/agents . 15
4.5 Relation between mobile rescue teams/agents . 16
4.6 Relation between Special Task Force/Command Centres and permanent entities in special conditions . 16
4.7 Relation between military authorities and civil authorities . 16
5 Emergency services communication requirements . 17
5.0 Introduction . 17
5.1 Methodology to determine the communication requirements . 17
5.2 Actions that require communications . 17
5.3 Required communications services . 18
5.3.1 Speech and conversational voice services . 18
5.3.1.0 General requirements . 18
5.3.1.1 Point to point speech services . 18
5.3.1.2 Group speech services . 19
5.3.1.3 Push To Talk (PTT)/Command and Control (C&C) features . 19
5.3.2 Data services . 20
5.3.2.0 General requirements . 20
5.3.2.1 Paging Services . 21
5.3.2.2 Video Teleconferencing (VTC) . 21
5.3.2.3 Group video and data communications . 21
5.3.2.4 Communications involving IoT devices. 21
5.3.2.5 Location services . 21
5.3.2.6 Sharing incident information . 22
5.4 Interoperability of communication services . 22
5.5 Example application . 22
6 Scalability . 23
6.0 General considerations . 23
6.1 Priority and preference schemes and traffic management . 23
6.1.0 Introduction. 23
6.1.1 Traffic management . 24
6.1.2 Emergency preference schemes . 24
6.1.2.1 User driven solutions. 24
6.1.2.2 PSTN/cellular solutions . 24
6.1.2.3 Professional Mobile Radio (PMR) Networks. 25
6.1.3 Interaction with the emergency call service NG112 . 26
ETSI
4 ETSI TS 102 181 V1.3.1 (2020-06)
7 Requirements applicable to the network and user services, (services to support) and the network
features and capabilities . 27
7.1 Recognition and treatment of emergency services from the view of the service. 27
7.1.1 Transmission quality . 27
7.1.2 Ensuring conveyance of communications . 28
7.1.3 Assignment of inter-authority communications to the appropriate authority . 28
7.1.4 Preventing effects of discrepancies in coverage . 28
7.1.4.1 PSAP routing in mobile networks . 28
7.1.4.2 International cooperation . 28
7.1.4.3 Private networks technologies . 28
7.1.4.4 Interworking of technologies . 29
7.2 Recognition and treatment of emergency services by the originating network . 29
7.2.0 Virtual network consideration. 29
7.2.1 Communication-related information . 29
7.2.1.0 Information forwarding . 29
7.2.1.1 Indication of the (emergency) caller's location . 29
7.2.1.2 Identification of the mobile terminal equipment/subscription . 29
7.2.1.3 Interworking of Technologies . 29
7.2.2 Network identification . 29
7.2.3 Minimum power supply for authority representative user accesses . 29
7.3 Requirements on call handling between networks . 30
7.3.1 Handling of inter-authority calls between networks . 30
7.3.2 Interworking with carrier selection/carrier preselection codes . 30
7.3.3 Inter-authority communications from other countries . 30
7.4 Providing termination of inter-authority calls for the relevant authorities . 30
7.5 Requirements on IoT communications . 31
7.5.1 Networks and connectivity . 31
7.5.2 Interoperability . 31
7.5.3 Data exchange at service and application level. 32
7.5.4 Contribution to the Common Operating Picture (COP) service. 32
7.6 Network management support functions for delivery of inter-authority calls . 32
7.6.1 Priority of inter-authority emergency communication . 32
7.6.2 Monitoring of the communications availability of the authority . 33
7.6.3 Diversion of inter-authority calls . 33
7.6.4 High or resilient availability . 33
7.6.5 Security provisions at the access to authorities . 33
8 Security and privacy . 33
8.1 Role of National Communication Security Authorities (NCSA) . 33
8.2 General security issues . 33
8.3 Interconnection of secure communication systems . 34
Annex A (normative): Basic architecture . 35
Annex B (informative): Organizational related issues for authorities to solve . 37
B.0 Introduction . 37
B.1 Handling of foreign languages . 37
B.2 Mitigating consequences of radio coverage discrepancies . 37
B.3 Definition of priorities (list of beneficiaries, levels, conditions of effective implementation) . 37
B.4 Contingency planning. 37
B.5 Organization of authorities in case of catastrophic event . 38
B.6 Communication between civil authorities and Non-Governmental Organizations (NGOs) . 39
B.7 Communication between civil authorities and press organizations . 39
B.8 Maintenance of IoT devices and platforms . 39
Annex C (informative): Security mechanisms . 41
ETSI
5 ETSI TS 102 181 V1.3.1 (2020-06)
C.0 Introduction . 41
C.1 Symmetric encryption schemes . 41
C.2 Asymmetric encryption schemes . 41
C.3 Hybrid encryption schemes . 41
C.4 Digital signatures . 42
C.5 Authentication methods . 42
C.6 Authorization schemes . 42
C.7 Logging . 42
C.8 Virtual Private Networks (VPNs) . 42
Annex D (informative): Mobile Radio Services . 43
History . 46

ETSI
6 ETSI TS 102 181 V1.3.1 (2020-06)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables 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 (https://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.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This Technical Specification (TS) has been produced by ETSI Special Committee Emergency Communications
(EMTEL).
The present document is one of several deliverables covering the communication needs of citizens and authorities in
emergency situations, as identified below:
• ETSI TR 102 180 [i.1]: "Basis of requirements for communication of individuals with
authorities/organizations in case of distress (Emergency call handling)";
• ETSI TS 102 181 (the present document): "Requirements for communication between
authorities/organizations during emergencies";
• ETSI TS 102 182 [i.3]: "Requirements for communications from authorities/organizations to individuals,
groups or the general public during emergencies";
• ETSI TR 102 410 [i.4]: "Basis of requirements for communications between individuals and between
individuals and authorities whilst emergencies are in progress".
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
Introduction
The present document outlines the requirements for communications between emergency authorities, and the need for
standardization in this area to support these requirements. These communications are considered of three types:
a) speech communications between emergency staff members;
b) data communications allowing them to exchange information such as pictures, schemas, files, videos; and
ETSI
7 ETSI TS 102 181 V1.3.1 (2020-06)
c) IoT communications where physical and virtual "things" have identities, physical attributes, virtual
representation, use interfaces to be integrated into the information network where they support the actions of
the emergency authorities.
Clause 4 describes the relations between authorities in general terms defining each authority. Clause 5 categorizes the
emergency services communications requirements. Clause 6 discusses the scalability and priority issues, including the
dynamic need to employ resources. Clause 7 outlines the requirements applicable to the network(s) and user services,
describing the services and the network features and capabilities. Clause 8 raises a number of security considerations.
The annexes describe additional operational considerations, which may be useful as a background but do not constitute
part of the communication requirements.

ETSI
8 ETSI TS 102 181 V1.3.1 (2020-06)
1 Scope
The present document addresses the requirements for communications between the authorized representatives who can
be involved in the responses and actions when handling an emergency.
It describes the functional requirements for communications between the authorized representatives involved in the
responses and actions when handling an emergency. The level of precision has been chosen to avoid interaction with the
specific local, regional or national organizations and diagrams of relations between authorized representatives. It
follows from this that adaptations will have to be done when implementing the present document at a local level.
Furthermore, the scope of the present document also encompasses various types of services that can bring an added
value to this basic scenario or add new scenarios, such as the services brought by other technologies e.g. IoT devices
that support communications between authorities during emergencies.
2 References
2.1 Normative 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
https://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.
The following referenced documents are necessary for the application of the present document.
[1] Void.
[2] Recommendation ITU-T E.409 (05/2004): "Incident organization and security incident handling:
Guidelines for telecommunication organizations".
[3] Recommendation ITU-T G.114 (05/2003): "One-way transmission time".
[4] ISO/IEC 15408: "Information technology -- Security techniques -- Evaluation criteria for IT
security".
[5] Void.
[6] Recommendation ITU-T E.106: "International Emergency Preference Scheme (IEPS) for disaster
relief operations".
[7] Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the
protection of natural persons with regard to the processing of personal data and on the free
movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation),
OJ 2016 L 119/1.
[8] ETSI TS 122 179: "LTE; Mission Critical Push to Talk (MCPTT) over LTE; Stage 1 (3GPP
TS 22.179)".
[9] ETSI TS 122 280: "LTE; Mission Critical Services Common Requirements (3GPP TS 22.280)".
ETSI
9 ETSI TS 102 181 V1.3.1 (2020-06)
2.2 Informative 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.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
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 TR 102 180: "Emergency Communications (EMTEL); Basis of requirements for
communication of individuals with authorities/organizations in case of distress (Emergency call
handling)".
[i.2] Directive 2002/22/EC of the European Parliament and of the Council of 7 March 2002 on
universal service and users' rights relating to electronic communications networks and services
(Universal Service Directive).
[i.3] ETSI TS 102 182: "Emergency Communications (EMTEL); Requirements for communications
from authorities/organizations to individuals, groups or the general public during emergencies".
[i.4] ETSI TR 102 410: "Emergency Communications (EMTEL); Basis of requirements for
communications between individuals and between individuals and authorities whilst emergencies
are in progress".
[i.5] ETSI TR 103 582: "EMTEL; Study of use cases and communications involving IoT devices in
provision of emergency situations".
[i.6] ETSI TR 102 299 (V1.4.1): "Emergency Communications (EMTEL); Collection of European
Regulatory Texts and orientations".
[i.7] ETSI TS 103 479: "Emergency Communications (EMTEL); Core elements for network
independent access to emergency services".
th
[i.8] C(2003)2657 Commission Recommendation of 25 July 2003 on the processing of caller location
information in electronic communications networks for the purpose of location-enhanced
emergency call services, published on O.J.E.U. L 189/49 the 29.7.2003.
[i.9] ETSI TS 103 260-1: "Satellite Earth Stations and Systems (SES); Reference scenario for the
deployment of emergency communications; Part 1: Earthquake".
[i.10] ETSI TS 103 260-2: "Satellite Earth Stations and Systems (SES); Reference scenario for the
deployment of emergency communications; Part 2: Mass casualty incident in public
transportation".
[i.11] IETF RFC 3261 (June 2002): "SIP: Session Initiation Protocol", J. Rosenberg, H. Schulzrinne, G.
Camarillo, A. Johnston, J. Peterson, R. Sparks, M. Handley and E. Schooler.
[i.12] IETF RFC 7852 (July 2016): "Additional Data Related to an Emergency Call", R. Gellens, B.
Rosen, H. Tschofenig, R. Marshall, J. Winterbottom.
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI TR 102 180 [i.1], ETSI TR 103 582 [i.5] and the
following apply:
authority: organization within the public services fully or partly responsible for emergency preparedness and handling
of incidents
ETSI
10 ETSI TS 102 181 V1.3.1 (2020-06)
authorized representative: individual officer or institution authorized by public service (fire, police or health) to play a
key role in handling of an emergency case
emergency control centre: facilities used by emergency organizations to handle rescue actions in answer to an
emergency call
NOTE: A PSAP forwards emergency communications to the emergency control centres.
emergency number: special short code(s) or number(s) which is used to contact the PSAP to provide emergency
services
NOTE: The emergency number is used by the emergency caller to request assistance from the emergency
services. There exist two different types of emergency numbers in Europe:
1) European emergency number, 112: unique emergency number for pan-European emergency
services and used, for example, in EU member-states, Switzerland and other European countries.
2) National emergency numbers: each country may also have a specific set of emergency numbers.
emergency response organization: organization providing response to disaster situations, e.g. the police, fire service
and emergency medical services
emergency service: service, recognized as such by the member state, that provides immediate and rapid assistance in
situations where there is a direct risk to life or limb, individual or public health or safety, to private or public property,
or the environment but not necessarily limited to these situations (see Commission Recommendation C(2003)2657 [i.8])
fleetmap: parameter information programmed into the system infrastructure and into the subscriber radios to control
how the radios will behave on the system
incident area: area where the incident occurred, and/or the area which needs communication coverage to manage the
response implemented
Internet of Things (IoT): dynamic global network with (self-)configuring capabilities based on communication
protocols where physical and virtual "things" have identities, physical attributes, and virtual representation, and use
interfaces to be integrated into the information network (from ETSI TR 103 582 [i.5])
NOTE: IoT represents the next step towards digitization where all physical objects, machines, servers, other
devices and people can be interconnected through communication networks, in and across private, public
and industrial spaces, report about their status and/or about the status of the surrounding environment and
exchange data for intelligent applications and services to be developed. The data transmitted over the IoT
can be small in size and frequent or infrequent in transmission. The number of connected IoT devices is
set to exceed the number of conventional devices such as computers, tablets and fixed line/cellular
phones.
IoT device: non-conventional, most often resource-limited, computing device (i.e. not a computer, server, tablet, or
smartphone but comprising e.g. a micro-controller-based embedded system) which is connected to a communication
network and which includes or connects to one or multiple sensors and actuators to interact with its deployment
environment (from ETSI TR 103 582 [i.5])
NOTE: In most cases, an IoT device is a physical object that has been embedded with IoT technology
(i.e. communication, processing, and/or storage capabilities) to turn it into a smart device.
IoT platform: set of IoT servers and gateways deployed by an IoT services platform provider that acts as a service
layer between the IoT devices and the IoT applications. (from ETSI TR 103 582 [i.5])
NOTE: The composition of the IoT service platform may range from one single IoT server and one single IoT
gateway to multiple IoT servers and multiple IoT gateways hierarchically organized.
location information: data processed in a public mobile network indicating the geographic position of a user's mobile
device or of an IoT device, and data in a public fixed network indicating the physical address of the termination point
(see Commission Recommendation C(2003)2657 [i.8])
originating network: network from which the emergency communication was originated
ETSI
11 ETSI TS 102 181 V1.3.1 (2020-06)
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
C&C Command and Control
CBRN Chemical, Biological, Radiological or Nuclear
COP Common Operating Picture
CQI Call Quality Index
D2D Device to Device (communication)
DGNA Dynamic Group Number Assignment
DMO Direct Mode Operation
DMR Digital Mobile Radio
EC European Commission
ECC Emergency Control Centre
EECC European Electronic Communications Code
FIFO First In, First Out
FR First Responders
GDPR General Data Protection Regulation
GoS Grade of Service
GSM Global System for Mobile telecommunications
GSM-R GSM-Railway
IEPS International Emergency Preference Scheme
IoT Internet of Things
IP Internet Protocol
ITSEC Information Technology Security Evaluation Criteria
ITU International Telecommunication Union
LEMA Local Emergency Management Authority
LMR Land Mobile Radio
MCPTT Mission Critical Push To Talk
MCX Mission Critical X
NOTE: With X = PTT / Video / Data.
MTA Mass Transportation Accident
NCSA National Communication Security Authority
NGO Non-Governmental Organization
PLMN Public Land Mobile Network
PMR Professional Mobile Radio
PSAP Public Safety Answering Point
PSTN Public Switched Telephone Network
PTT Push To Talk
QoS Quality of Service
RF Radio Frequency
RP Reference Point
SIP Session Initiation Protocol
TCP/IP Transport Control Protocol/Internet Protocol
TETRA TErrestrial Trunk Radio Access
UAV Unmanned Aerial Vehicle
VHF Very High Frequency
VoIP Voice over IP
VPN Virtual Private Network
VTC Video TeleConferencing
ETSI
12 ETSI TS 102 181 V1.3.1 (2020-06)
4 Relations between authorities
4.0 Introduction to the functional architecture
The type and number of the authorized representatives in a given situation usually directly depend on the nature of the
emergency. In the most frequent cases, only people on duty have to intervene according to a day-to-day routine, but in
some cases, crisis teams or temporary headquarters will be called. In accordance with a plan, the additional resources
will organize a mass action gathering and, if needed, include the resources of several centres, or even include in the
rescue plan additional levels of administrative authority, private operators and associations. These new authorized
representatives will follow instructions or orders from the administrative crisis authority (also called Local Emergency
Management Authority); for example, utilities companies (water supply, transport, energy, etc.) may have to stop the
provision of service, install priority of service schemes or execute a coordinated schedule for the restoration of the
infrastructure and the service, as applicable.
It is recognized that the public authorities keep the responsibility of overall management of actions during the duration
of the crisis, establishment of pre-planned scenarios and, in specific locations e.g. tunnels, underground transports,
plants with high level of risk, organization of field exercises involving all these authorized representatives.
Figure 1 illustrates the relations (or Reference Points, RP) between these authorities illustrated as functional entities,
and shows them when involved in routine and exceptional emergency situations.

Figure 1: Reference points between functional entities
ETSI
13 ETSI TS 102 181 V1.3.1 (2020-06)
The description of the type of relations provided in the next clauses relies on the model illustrated in Figure 1. These
relations correspond to the requirements from a user point of view. PSAPs/emergency control centres and rescue
services (First Responders, FR) in the field may be organized differently in different countries, e.g. in Sweden the PSAP
and control centres for medical services and fire are combined, whereas police have their own control centres (to which
calls are transferred from the common PSAP).
NOTE: Relations involving the military agencies (described in clause 4.7) are not shown in Figure 1.
The temporary task force for coordination may be a pre-defined group which is activated according to set of criteria,
e.g. kind of emergency (landslide, earthquake, etc.), number of casualties, need for resources, etc.
Decisions to be taken by the emergency management entities require a comprehensive situation overview which is
known as Common Operating Picture (COP). Enhanced digital technologies such as the Internet of Things (IoT) and
drones are also used by authorities to improve their situational awareness, monitoring and response during incidents.
The IoT includes physical devices, sensors within or attached to these devices, but also smart services and applications.
IoT technologies and drones are thus contributors to the collection, aggregation and distribution of the global COP data.
More details can be found in ETSI TR 103 582 [i.5].
Figure 2 shows how and where IoT can support communications between authorities. IoT allows (near) real-time data
gathering without human interaction. This is especially important in situations where emergency service team members
are busy with critical tasks and additional reporting (e.g. via voice-based radio systems) to the team officer would cause
unwanted distraction or delay. An example is a FR personnel equipped with wearables such as biometrics, audio and
video sensors or supported by a drone. The real-time audio and video transmissions may be used by other team
members or by the emergency control centre in order to collect more data to assess the situation.

Figure 2: Additional services brought by IoT to functional entities
The requirements in the present document cover both public and private networks. However, the implementation of all
the requirements may not be possible in both types of networks.
ETSI
14 ETSI TS 102 181 V1.3.1 (2020-06)
4.1 Relation between PSAP and Emergency Control Centres
PSAP and emergency control centres are two different functionalities that may or may not be integrated.
The PSAP shall, after reception of an emergency call and without delay, communicate with the competent emergency
control centre and transmit the location and nature of the emergency of the calling party, along with any other relevant
information that may be available associated with the call.
4.2 Relation between PSAPs
PSAPs normally work independently from each other, however, there are cases where cooperation would be needed
between two PSAPs, especially in case of cross-border events. In a single country, PSAPs of different regions can be
interconnected. If no operator is available, the communication can be redirected to another PSAP. Across countries, a
PSAP may receive an emergency notification for an event happening in a bordering country.
In cases where communications arrive at a PSAP other than the one responsible for the area where the communication
originated (e.g. mobile phones in the bordering area between different PSAPs), the communication may be transferred
to the other PSAP, together with additional information (e.g. location data).
The requirement depends on operation rules which have been established for these types of situation. Such rules may
state that:
• the communication is handled by the receiving PSAP;
• the communication is immediately transferred to the PSAP appropriate for the incident area; in such a scenario
the location data shall be made available to the PSAP handling the incident, as for any received
communication;
• depending on local procedures, the receiving PSAP may transfer the communication directly to the relevant
ECC, possibly together with information about the correct PSAP that the communication has been transferred
to.
The PSAPs or their organization shall be responsible to pre-define these rules of procedures.
A PSAP-Directory hosted by CEPT-ECO is available to facilitate inter-PSAP communications in Europe, in compliance
with the requirements in the European Electronic Communications Code, EECC) entered into force on 20 December
2018 (see ETSI TR 102 299 [i.6]).
4.3 Relation between Emergency Control Centres
ECCs shall have the facilities to collaborate with other ECCs either within the same service or across services (e.g. fire
and health).
Examples of cases where this is needed:
• Communications are forwarded to an inappropriate ECC: The communication shall be transferred to the
correct ECC together with additional information (e.g. location data).
• Cases involving more than one ECC, e.g. fires with risks for human lives which typically involve fire, health
and police, CBRN incidents (or suspected incidents), terrorism.
• Communication facilities exist to integrate the resources from two or more emergency control centres, in case
of a larger emergency situation (see Figure 1).
Communications between ECCs shall be able to:
• Establish communication connections to support a number of services, including speech and (IoT) data.
• Support (video) conference calls including external resources that may be set up and kept over a substantial
amount of time. In contingencies, calls to external resources may be required.
• Support exchange of data, such as files, images, video, instant messaging, emails.
ETSI
15 ETSI TS 102 181 V1.3.1 (2020-06)
• Support the exchange of IoT data, either manually or automatically (see clause 5.3.2.3).
4.4 Relation between Emergency Control Centres and mobile
rescue teams/agents
Access to permanent bidirectional connections between Emergency Control Centres (ECCs) and their mobile teams is
crucial in the handling of emergencies and shall be available for the duration of the emergency/disaster. The ECC may
also be able to receive data information directly from the mobile teams, their supporting IoT devices, or from drones.
The main speech communication needs of the mobile rescue teams, representing the emergency services can be
categorized as follows:
• specialized functionality in group communications and dispatching, with instant connection and including
appropriate security, dynamic management of talk groups and more generally communication groups,
emergency calls, prioritization of communications, etc.;
• call establishment times; voice call set-up time shall be in the range of 0,3 s to 1 s.
• seamless radio coverage throughout the area affected by the incident itself and the areas of operational
activities associated to the incident (rescue facilities, hospitals, etc.) - including means to maintain
communication during network outage;
• incident capacity; t
...