“POLITEHNICA ” UNIVERSITY OF BUCHAREST THE FACULTY OF ENGINEERING IN FOREIGN LANGUAGES BUSINESS ADMINISTRATION AND ENGINEERING NEXT GENERATION… [604449]

“POLITEHNICA ” UNIVERSITY OF BUCHAREST
THE FACULTY OF ENGINEERING IN FOREIGN
LANGUAGES
BUSINESS ADMINISTRATION AND ENGINEERING

NEXT GENERATION EMERGENCY
SYSTEMS

Supervisor :
Bujor Păvăloiu,
Reader, Doctor of Engineering

Author :
Filip -Alexandru Giorgi ,
Engineer
BUCHAREST
2017

2
Table of contents

1 Introduction ………………………….. ………………………….. ………………………….. …………….. 5
1.1 Knowledge of 112 number ………………………….. ………………………….. ……………… 6
1.2 Device ………………………….. ………………………….. ………………………….. ……………… 7
1.3 Network access to 112 ………………………….. ………………………….. ……………………. 7
1.4 Reach an available call -taker ………………………….. ………………………….. …………… 7
1.5 Data collection ………………………….. ………………………….. ………………………….. ….. 7
1.6 Dispatch appropriate resources ………………………….. ………………………….. ………… 8
1.7 Intervention ………………………….. ………………………….. ………………………….. ………. 8
2 Emergency services ………………………….. ………………………….. ………………………….. …. 9
2.1 Main emergency services ………………………….. ………………………….. ……………….. 9
2.2 Other emergency services ………………………….. ………………………….. ……………… 10
2.3 Civil emergency services ………………………….. ………………………….. ………………. 10
2.4 North American emergency system ………………………….. ………………………….. .. 11
2.5 European systems and standards ………………………….. ………………………….. ……. 12
2.5.1 EENA ………………………….. ………………………….. ………………………….. …………. 13
2.6 Romania ………………………….. ………………………….. ………………………….. …………. 13
2.6.1 Operating model ………………………….. ………………………….. ………………………. 14
2.6.2 The call handling process ………………………….. ………………………….. ………….. 15
2.6.3 The red plan ………………………….. ………………………….. ………………………….. … 16
3 Improving the emergency management process model ………………………….. ………… 17
3.1 Common service model ………………………….. ………………………….. ………………… 17
3.2 Agency level operational improvement ………………………….. ……………………….. 18
4 Using standards ………………………….. ………………………….. ………………………….. ……… 23
4.1 CAP st andard ………………………….. ………………………….. ………………………….. ….. 23
4.2 TSO standard ………………………….. ………………………….. ………………………….. ….. 25
4.3 Creating local operational pictures LOPs ………………………….. …………………….. 30
4.4 Creating common operational pictures COPs ………………………….. ………………. 31
5 Advanced Mobile Location (AML) implementation ………………………….. ……………. 33
5.1 Location and routing key concepts ………………………….. ………………………….. …. 33
5.1.1 Acquiring caller location ………………………….. ………………………….. …………… 33
5.1.2 Emergency call routing ………………………….. ………………………….. ……………… 35
5.1.3 PSAP location acquisition ………………………….. ………………………….. …………. 36
5.2 Network based location and routing architecture ………………………….. ………….. 37
5.2.1 Circuit -Switched Emergency Calling Architectures ………………………….. …… 37
5.2.2 IMS Emergency Calling Architecture ………………………….. ……………………… 39
5.3 Device based location and routing architecture ………………………….. …………….. 40
5.3.1 Device based location ………………………….. ………………………….. ……………….. 40
5.3.2 WiFi location solution and architecture ………………………….. ……………………. 41
5.3.3 Routing ………………………….. ………………………….. ………………………….. ……….. 43
6 Bibliograp hy ………………………….. ………………………….. ………………………….. …………. 45

3
List of figures

Figure 1 – Emergency service task chain ………………………….. ………………………….. …………… 6
Figure 2 – Romanian emergency system architecture ………………………….. …………………….. 15
Figure 3 – Emergency management process flow ………………………….. ………………………….. 17
Figure 4 – Actual agency level process flow ………………………….. ………………………….. …….. 21
Figure 5 – Proposed agency level process flow ………………………….. ………………………….. … 22
Figure 6 – CAP standard structure ………………………….. ………………………….. ………………….. 25
Figure 7 – The high level TSO standard structure ………………………….. …………………………. 27
Figure 8 – The detailed TSO standard structure ………………………….. ………………………….. … 30
Figure 9 – Military COP example ………………………….. ………………………….. …………………… 32
Figure 10 – Location value and location reference concepts ………………………….. …………… 34
Figure 11 – Accuracy using uncertainty and confidence ………………………….. ………………… 34
Figure 12 – Traditional wirelines location solution ………………………….. ……………………….. 37
Figure 13 – 3GPP Circuit -Switched Emergency Calling ………………………….. ………………… 38
Figure 14 – Generic IMS emergency calling architecture ………………………….. ……………….. 39
Figure 15 – WiFi localization architecture ………………………….. ………………………….. ……….. 42
Figure 16 – Location and routing hybrid solution ………………………….. ………………………….. 44

Abstract
The purpose of the current dissertation is to demonstrate a series of changes that
could be performed on the actual emergency systems from all over the world in order to
improve the emergency management process. Those changes may affect all the organizational
layers (strategic, tactical and operational) and the results could be proved by analyzing the
layer speci fic KPIs .
In the first part of the paper the global „as -is” situation has been dispalyed focusing
on the most important stakeholders from all over the world and by presenting the Romanian
emergency system which is considered one of the most technologically advanced in Europe.
The second part of the dissertation contains the changes proposed to be implemented
locally, a t national level or globally aiming to implement new emergency systems by using
cutting -edge technology and knowledge.

NEXT GENERATION EMER GENCY SYSTEMS

5
1 Introduction
An emergency is a sudden, unexpected, or impending situation that poses an
immediate risk to health, life, property or environment. Most emergencies require urgent
intervention to prevent a worsening of the situation, although in some situations, mitigation
may not be possible and intervention agencies may only be able to try to reduce the affected
area and the damages.
Part of the emergencies are self -evident (such as a natural phenomenon like a flood or
earthquake), but many smal ler incidents require that an observer (or affected party) decide
whether it qualifies as an emergency and he announces the agencies in charge of solving the
problem.
The agencies involved and the procedures used by those during the intervention, vary
by country to country or maybe by region, and this is usually set by the every country’s
government. Those agencies are responsible for emergency planning and management
(intervention plans).
In an emergency situation, the citizen has to know the number to co ntact emergency
services, and thus, be able to ask for help. The knowledge of such number is the first link of
the emergency service chain. After this emergency number is dialed, emergency services have
to answer the call appropriately following different steps: recepti on of the call, data collection
and classification of the type of incident and, if needed, dispatch of the appropriate intervention
resources.
The European emergency number (112) is available in all the countries that are
members of the Europe an Union and also in other European countries. There are countries
where only this single emergency number is available and others that have different national,
regional or local numbers for contacting fire and rescues services, police and emergency
medica l services.
A call to emergency services starts a sequence of tasks by different stakeholders
taking part in the emergency service chain. However, this sequence will not be initiated if the
person involved in the emergency situation is not aware of the em ergency number to dial. This
is the reason why every single step in the 112 chain is crucial.

NEXT GENERATION EMER GENCY SYSTEMS

6

Figure 1 – Emergency service task chain

1.1 Knowledge of 112 number
In an emergency situation or disaster , the citizen may not be able to search and
establish what the emergency number is . This number should be known previously so it could
be dialed immediately in case of an incident . This is the reason why dissemination of
information and education of citizens about the emergency number is crucial.
The knowledge of the 112 emergency number is not as wide as we think it is . The
results of the European Emergency Number 112 Eurobarometer survey does not look very
optimistic : only 50% of the European citizens would call 112 in case of emergencie s in their
own country and 76% would not call 112 in case of an incident in another EU country.
The European dimension of the emergency number should be communicated to all
citizens. It is important that even travelers are informed about the availability o f the European
emergency number or another numbers available in that country . Most people travelling do not
even think about the situation of being involved in an emergency incident during their journey.
This is why authorities cannot count into travelers’ own initiative to search and find out what
number to use in case of emergency situation . Campaigns and dissemination efforts are needed
to make sure that travelers know what is the emergency number that could be used in case of
need .

NEXT GENERATION EMER GENCY SYSTEMS

7
1.2 Device
The first lin k of the chain is to know the emergency number. Then, the citizen needs
a fully functioning device (e.g. mobile phone, public phone, etc.) which makes possible the
contact with the emergency services. From mobile phones, it is possible to dial the emergenc y
number even if the device is blocked. This way, the person in an emergency situation can use
the device even if its functioning is unknown to him or her.

1.3 Network access to 112
Nowadays, emergency services usually accept to be contacted only through phon e
calls. This is the reason why the availability of mobile telephony within range plays an essential
role. In some locations only one mobile network operator may be available. In these cases
national roaming, i.e. when emergency calls are handled by anothe r mobile network operator,
will ensure that the citizen is able to contact emergency services.

1.4 Reach an available call -taker
Once the citizen has dialed 112 through an accessible network, emergency services
have to ensure that he or she reaches an availab le call taker as soon as possible. Resources have
to be optimized to guarantee a minimum waiting time.

1.5 Data collection
The first task to be achieved by emergency services is data collection. Where is the
caller and what is happening are the most important pieces of information. These data are
decisive in order to establish what resources are needed.
It is worth to mention that it is necessary to be able to establish a permanent link to
the caller. To achieve this, it is crucial that PSAPs receive caller li ne identification, something
that ensures that calling back is possible.

NEXT GENERATION EMER GENCY SYSTEMS

8
1.6 Dispatch appropriate resources
The appropriate resources have to be mobilized depending on where and what is
happening. This information has to arrive to the appropriate resources.

1.7 Intervention
Once the resources have been dispatched, they have to arrive to the location of the
incident and assist the citizens who are involved.

NEXT GENERATION EMER GENCY SYSTEMS

9
2 Emergency services
Emergency services and rescue services are public or private organizations meant to
ensur e public safety and health by addressing different emergency situations . Some of these
agencies exist only for addressing certain types of events (fire, health etc.) whilst others deal
with ad -hoc situations as part of their normal responsibilities. Many o f those agencies engage
in community awareness and prevention campaigns to help the public avoid, detect and
announce emergencies effectively.
The availability of emergency services depends very heavily on the event location,
and may in some cases also depend on the recipient giving payment or holding an insurance or
other surety for receiving the service needed .

2.1 Main emergency services

There are three main emergency service functions around the world :
 Police — providing community safety is acting to reduce crime against
persons and property . Their might also collaborate with gendarmerie in some
countries ;
 Fire department — providing firefighters to deal with fire , flood and rescue
operations. They may also deal with some secondary emergency service
duties;
 Emergency medical services — providing ambulances and specialized staff to
deal with medical emergencies and first aid .
In some countries such as the UK, these functions are performed by three separate
organizations in every given area. Ho wever, there are also many countries where fire and
medical service functions are performed by a single organization. In Romania, there are two
different entities protecting the health and life: The ambulance service – a standalone agency
coordinated by th e Health Ministry and the SMURD (Mobile Emergency Service for
Resuscitation and Extrication) – and agency that is coordinated by the firefighters under the
Ministry of the Interior.

NEXT GENERATION EMER GENCY SYSTEMS

10
Emergency services may have one or more dedicated emergency telephone numbers
reserved for emergency calls. There are some countries where one number is used for all the
emergency services ( 911 in the U.S., 999 in the UK) and other countries, where each
emergency service has its own emergency number.

2.2 Other emergency services
These services could be provided by one of the main emergency services or by a
separate government or private organization .
 Military — provide s specialist services like bomb disposal or supplement s
emergency services at times of major disaster or civil dispute;
 Coastguard — provide s coastal patrols with a security function at sea or ocean ,
as well as involvement in search and rescue activities ;
 Lifeboat — provide s services of rescue lifeboat, usuall y at sea but not only ;
 Mountain rescue — provide s search and rescue services in mountainous areas,
and sometimes in other special wilderness environments;
 Cave rescue — to rescue people in danger during caving explorations;
 Mine rescue — specially trained personnel, equipped proper to rescue miners
trapped by fires, explosions or other incidents ;
 Technical rescue — other types of technical intervention needed during an
emergency situation ;
 Search and rescue — specialized units owning equipment and dogs trai ned for
search and rescue ;

2.3 Civil emergency services

These groups and agencies respond to emergenc y events and provide other safety –
related services as a part of their on -the-job duties, or as part of the m ain mission of their
business , or as part of the ir hobbies.

NEXT GENERATION EMER GENCY SYSTEMS

11
 Public utilities — gas, electricity, water etc. ;
 Emergency road service ;
 Civilian Traffic;
 Emergency social services;
 Community emergency response teams;
 Disaster relief;
 Famine relief teams;
 Amateur radio communications;
 Poison Control;
 Animal control .

2.4 North American emergency system
911 is the emergency telephone number for the North American Numbering
Plan (NANP), one of eight N11 codes . This number is intended for use in emergency
circumstances only, and to use it for any other purpose (such as prank calls ) can be a crime .
An N11 code ("N-one-one" code) or N11 number is a three -digit abbreviated
dialing telephone number within the North American Numbering Plan (NANP) which allows
access to specific services.
Usage is listed in the NANP as follows:
 2-1-1: Community services and information (ex: United Way of America );
 3-1-1: Municipal government services, non -emergency number;
 4-1-1: Directory assistance ;
 5-1-1: Traffic information or police non -emergency services;
 6-1-1: Telephone company (telco) customer service and repair;
 7-1-1: TDD and Relay Services for the Deaf and Hard of Hearing ;
 8-1-1: Underground public utility location ,[1] in Canada 8 -1-1 is assigned for
non-emergency health information and services;
 9-1-1: Emergency services (police , fire, ambulance /rescue services).

NEXT GENERATION EMER GENCY SYSTEMS

12
In over 98 percent of locations i n the United States and Canada, dialing "9 -1-1" from
any telephone will link the caller to an emergency dispatch center —called a Public -Safety
Answering Point (PSAP), by the telecom industry —which can send emergency responders to
the c aller's location in an emergency. In approximately 96 percent of the U.S., the Enhanced 9 –
1-1 system automatically pairs caller numbers with a physical address.

2.5 European systems and standards

The 112 is the emergency telephone number that could be dialed for free from all
the mobile telephones and, in several countries, fixed phones in order to reach the emergency
services .
112 number is a part of GSM standard and all the GSM compatible telephone are able
to dial the emergency number even when locked or in some cases with no SIM card present. It
also represents the common emergency number from all member states of the European Union ,
some other countries of Europe and outside Europe . It also happens to be available alongside
other numbers that are traditionally used in the given country with the scope of access ing
emergency services. There are some countries where the calls to 112 are not connected directly
and they are forwarded by the GSM network to the local ly defined emergency numbers.
The 112 emergency number concept was first standardized by a recommendation by
the CEPT (The European Conference of Postal and Telecommunications Administrations) in
1972 and almost 20 years later by a decis ion of the EU Council in 1991 and also subsequently
reaffirmed in 2002 by article 26 from the Universal Service Directive and its subsequent
amen dments.
This choice of the 112 number has several advantages:
 Different digits: considering the numeric keypads used universally today, it is
a must using at least two di fferent digits instead of the same digit repeatedly
because it significantly reduces the risk of accidental emergency calls.
 Low digits: in the past, when rotary dial telephones were still used , maximized
dialing speed.

NEXT GENERATION EMER GENCY SYSTEMS

13
The 112 emergency number is managed and financed in the European Union and by
each Member State which also must decide on the structure of the emergency call centers.

2.5.1 EENA

EENA, the European Emergency Number Association, is a Brussels -based NGO set
up in 1999 dedicated to promoting high -quality emergency services reached by the number 112
throughout the EU. EENA serves as a d iscussion platform for emergency services, public
authorities, decision makers, researchers, international associations and solution providers in
view of improving emergency response in accordance with citizens' requirements. EENA is
also promoting the est ablishment of an efficient system for alerting citizens about imminent or
developing emergencies.
In October 2015, the EENA memberships include over 1100 emergency services
representatives from more than 80 countries world -wide, 75 solution providers, more than 90
researchers, 15 international associations/organizations as well as over 190 Members of
the European Parliament .
EENA is a registered organization in the Transparency registry of the European
Union.

2.6 Romania

The Unique National Emergency Call System (U NECS) is a vital part of the univer sal
service obligations, as speculated in one of the Directives of the EU, which is significant for
policy -making in telecommunications field.
Dialing the emergency number – 112 is a fast way to communicate with the emergency
dispatch centers (Police, Ambulance or Fire Brigade) in case an emergency occurs .
The Emergency System works as a country level service on all fixed or mobile
telecommunication networks.
The 112 system is meant to ensure citizen protection and providing a high level of
assistance, regardless the location. The Unique National Emergency Call System consists of

NEXT GENERATION EMER GENCY SYSTEMS

14
several emergency call answering centers (Public Safety Answering Points) and also of their
associated equipment: a reliable telecommunications system, des igned to notify, process and
transfer the calls to the requested services, all of this in a centralized and unitary mode . The
informatics system also applies to the telecommunications between the emergency agencies
special response systems which are obliga ted by the law to respond in case of emergency. In
the future, it is planned, depending on the developing necessities, to be created new response
agencies that will be gradually encompassed: the Civil Protection , the Gendarmerie, and
Antiterrorism units.
This integrated system is configured with the purpose of ensuring protection of the
citizens’ life and their goods and it will bring forth a state of normality in our country , similar
to that of the other countries in Europe and not only . The efficiency of the system largely
depend s on the prompt response of the emergency first responders (Police, Ambulance, and
Fire Brigade) to the unexpected crisis situations.
The Public Safety Answering Point human resources are composed of professional
dispatchers who re spond to the emergency calls 24 hours per day, 7 days per week . They are
specially trained to assist the callers and help them as soon as possible during the emergency
situations .

The main objective of 112 is to insure the safety of :
 lives
 environment
 property
The Unique System for Emergency Calls provides the contact between the caller that
asks for help during an emergency situation and public safety special agencies (their dispatcher
centers).
2.6.1 Operating model

NEXT GENERATION EMER GENCY SYSTEMS

15
The Public Safety Answering Points have its own database which helps the
emergency call takers to locate the call er’s position and identify the nature of the event and the
adequate response methods . This is possible by using the following identification indicators:
 Automatic Number Identificatio n (ANI) : The caller’s name is automatically
displayed based on its telephone number.
 Automatic Location Identification (ALI) : The caller’s official address, the
place where the call was initiated from and other location information needed
to identify the optimal solution for the intervention units to reach the incident
site in time are displayed.
During the intervention to an emergency, the Automatic Vehicle Location application
is used to identify the position of the units responding to emergency evet, equipped with radio
communications equipment that includes a GPS system.

Figure 2 – Romanian emergency system architecture

2.6.2 The call handling process

The call handling process has several stages:
 the caller dials 112 to report an incident .
 the emergency system identifies the caller’s telephone number
 the name and address of the caller are then identified by the system;

NEXT GENERATION EMER GENCY SYSTEMS

16
 the dispatcher requests incident information;
 all the data registered are transmitt ed to the emergency agencies involved
dispatch ers, depending on the type of event;
 the dispatchers identify the units (response services) that are the most
appropriate for participating in the case resolution. This action is performed
by the help of the AVL application (Automatic Vehicle Location);
 the case -response services relation is displayed on the GIS support .

2.6.3 The red plan

The red plan is the Romanian intervention plan and methodology in case of a large
scale disaster. Its purpose is to ensure a coordinated response of all structures with attributions
in case of accidents or disasters with fast evolution and a considerable effect in a short time,
that produces and could produce a big number of victims.
It also establishes concretely the m ethods and procedures in order to alert all possible
entities (organizations, agencies, private companies) that could help in reducing the effects of
a disaster.
A disaster could evolve from an emergency situation (a fire started in an apartment
that incre ases quickly and affects an entire building) or it can be declared from the beginning
(a powerful earthquake). There are not clear limits that can trigger the transformation of an
emergency situation into a disaster that is why the only person that could d ecide the activation
of the red plan is the head of the county or the chief inspector of the emergency situations
inspectorate.

NEXT GENERATION EMER GENCY SYSTEMS

17
3 Improving the emergency management process model
3.1 Common service model
In the European Union, the EENA is trying to mitigate a unique process model for
treating emergencies. There are two levels of processing the call: the PSAP dispatcher performs
the first interview with the caller and he gathers general information about the emergency and
according to the emergency type he forw ards the call to specific agencies. Here, the specialized
dispatchers performs the agency specific interview and based on the information they create
the response.

Figure 3 – Emergency management process flow

According to their role, the dispatchers must perform certain activities based on a strict
procedure.
The PSAP call taker:
 Identifies caller and emergency type;

NEXT GENERATION EMER GENCY SYSTEMS

18
 Decides, based on protocols, which primary response to send;
 Transmits the data / case file to experts from rel ated agencies.
 Agency experts:
 Follow up case;
 Decide if secondary dispatching of response teams is needed;
 Receive feedback from first team on site;
 Share info with other experts in the room;
 Take further decisions.
3.2 Agency level operational improvement

The actual flow at the agency level implies two different business roles: the call takers
and the dispatchers.
The call taker simply receives the phone call from the PSAP followed by the case file
containing general information. He continues s peaking with the caller for gathering agency
specific information (for example the ambulance service asks the caller information regarding
the health status of the victim and provides first aid advices). After extracting the specific
information, he forwar ds the case file to the dispatcher.
The dispatcher receives the case file and he selects an appropriate available resource
for responding to the situation. He continues by sending the case information to the resource
and he provides support to it during th e intervention.

Independently of who or what organization is in charge of collecting data, the
following information must be gathered:
Automatic caller’s
location data This information shall be provided by telecommunication
operators
Automatic caller lin e
identification It is necessary to be able to establish a permanent link to the
caller. To achieve this, it is crucial that PSAPs receive caller line
identification, something that ensures that calling back is
possible

NEXT GENERATION EMER GENCY SYSTEMS

19
Caller’s phone number It is crucial for emergency services to have the possibility to call
back a caller. In most cases the caller line identification (CLI)
will be the contact number of the caller. Where the caller is not
the person directly involved in the emergency, then contact
details for that person should also be collected if possible. The
CLI of course is often used for locating the caller and is an
integral part of the data that needs to be collected.
Personal details of the
caller (name,
identification number,
address, etc.) This data are not required in some countries. Data from special
types of callers (i.e. deaf or hard of hearing) should be available,
either manually or automatically (through a preregistration
process or through interoperability with other services).
Emergency situation’s
location The location of the caller may not be necessarily the same as the
location of the emergency and therefore the two possibilities
need to be established and treated accordingly. The location of
the emergency needs also to be known using whatever address
information, including the standardized formatting, is capable of
being retrieved, utilized and stored. Moreover, the best access for
responders should also be considered where this is not obvious
particularly where the location may be in a rural area or in a high
density urban building. Indeed the treatment of possible multiple
addresses should also be considered as part of the data collection
procedures.
Description of the
emergency situation The caller describes the emergency situation and the call taker
can also add some information from other sources, e.g. back
ground noises.
Depending on the
emergency situation,
different type of
information has to be The emergency services’ call taker asks the cal ler different type
of information depending on the nature of the emergency, i.e.
information to be gathered in case of a traffic accident will be in
most cases different from a robbery.

NEXT GENERATION EMER GENCY SYSTEMS

20
collected following the
procedures
New information given
by other callers Different calls may be receive d for the same accident. If possible,
all information should be centralized and shared. Care must be
taken to ensure that callers are all talking about the same incident.
Confirmation could be sought of the description of cars involved
in a traffic collisi on, as it will always be possible that there are
two incidents in the same road.
New information given
by emergency services Once emergency services’ resources, or other trusted individuals
are in the location of (or have sight of) the incident, additiona l
information can be added and updates inputted as necessary.

This process flow works appropriate only when the number of cases is low and the
number of resources is high. In this case, most of the time, the appropriate resource is available
for interven tion.

NEXT GENERATION EMER GENCY SYSTEMS

21

Figure 4 – Actual agency level process flow

But there is a problem when the agency has some rare resources and the number of
cases exceeds the number of resources. It could happen that a resource assigned to a case to be
more appropriate for another higher severity case but that resource is already assigned and the
dispatcher of the new case does not even know about its existence.
For treating this situations I propose inserting a new role called coordinator. This role
will take the resource selection responsibility from all the dispatchers in the agency. This way
there will be a single person having the global view of resources allocations and he will be able
to decide resources reallocations.

NEXT GENERATION EMER GENCY SYSTEMS

22
In this case the dispatchers will receive from the coordinator the mission orders (the
link between a case and a resource) and they will be responsible only for sending the mission
orders to the resources and to support their intervention.

Figure 5 – Proposed agency level process flow

NEXT GENERATION EMER GENCY SYSTEMS

23
4 Using standards
4.1 CAP standard

The Common Alerting Protocol (CAP) is an XML data format for sharing
information about public warnings and emergencies between alerting systems . CAP allows a
warning message to be consistently sent simultaneously over many warning systems to many
software applications. This protocol increases warning effectiveness and successfully
simplifies the task of activating the warning s for responsible officials.
Standardized alerts could be received from many external sources and configure their
informatics systems to process and respond to the alerts as desired by the projecting entities .
For example, the a lerts from the Department of Homeland Security , the Department of the
Interior 's United States Geological Survey , the United States Department of
Commerce 's National Oceanic and Atmospheric Administration (NOAA), and national and
local government agencies can be received in the same structure and format, by the same
application. Th is application can sound different alarms based on the information received from
the source system .
By normalizing the alert data across jurisdictions , threats, and warning systems,
the Common Alerting Protocol is also used to detect trends and patterns in to the warning
activity, such as trends of measurements that might indicate an upcoming hazard or hos tile act.
From a procedural perspective, CAP boosts a research -based template for the effective warning
message structure and content .
The Common Alerting Protocol structure of data is compatible with many of existing
alert formats including the Specific Area Message Encoding (SAME) used
by Weatheradio and also with the broadcast Emergency Alert System as well as new
technology such as the Wireless Emergency Alerts (WEA), while adding capabilities including:
 Flexible geographic location using latitude -longitude “ rectangles ” and other
geospatia l representations in to three dimensions;
 Multilingual or multi -audience messaging;
 Message update and cancel features;

NEXT GENERATION EMER GENCY SYSTEMS

24
 Template that support s framing of complete and effective warning messages;
 Digital encryption and identity capability;
 Facility for digital pictures , sound , and video.

This protocol is already used in North America (USA and Canada) and Australia.
In early 2005, U.S. Department of Homeland Security together with the Association
of Public Television Stations, demonstrated the CAP -based "digital EAS" broadcasts over
public television channel, digital TV transmitters and satellite links in the Washington,
D.C. area and neighborhood .
CAP is the basis technology for the planned "Integrated Public Alert and Warning
System", an all -disaster , all-media national warning architecture that is developed by DHS,
the National Weather Service within NOAA, and the Federal Communications Commission .
In Canada, a team composed of public alerti ng practitioners and government
organizations has developed a CAP Canadian Profile (CAP -CP) which is based on CAP
standard but specialized to solve the needs of Canadian public alerting targets , such as
bilingualism, geolocation for Canada, lists of locati ons and events, etc. The Canadian
government adopted CAP -CP for the National Public Alerting System (NPAS) proj ect. The
CAP -CP working group, with the aid of stakeholders and projects like the Canadian Public
Safety Operations Organization (CanOps) and Net alerts' Sarnia Lambton trial, they are
working with and refining CAP -CP for national application allover of Canada.
The Common Alerting Protocol has been implemented at a small -scale, grassroots
hazard information system in countries like Sri Lanka following the 2004 Indian Ocean
Tsunami . This implementation is part of th e "HazInfo Project", which is funded by Canada's
International Development Research Centre.
The province of Alberta has adopted CAP as part of its Emergency Alert System. In
March 2015, a national public warning system based upon the CAP -CP, has been officially
launched. The p articipation in the system by broadcasters is insured by the Canadian Radio –
television and also by the Telecommunications Commission .

NEXT GENERATION EMER GENCY SYSTEMS

25

Figure 6 – CAP standard structure

4.2 TSO standard

The TSO defines an information structure to record a view of a situation as seen by a
particular observer at a particular time. It is used to transfer this view to another observer. Here
an observer can range through a machine such as transponder, a human with a hand held device,
to a complex computer system providing command, control and planning functions.

NEXT GENERATION EMER GENCY SYSTEMS

26
This information contributes to the situational awareness of the various parties, that
is, their awareness of the current state of the world, the acti ons of the agents involved in the
crisis and the plans of the responding organizations. The message can be used peer -to-peer for
observers at the same level of the command hierarchy, or used to send information up and down
the hierarchy.
The objective of t he specification is to ensure the semantics of an individual message
are unambiguous. It is beyond the scope of the specification to define how data from different
messages is merged. For example, if two messages locate a vehicle in two different places, i t
is a problem for the recipients of the message to decide if the vehicle has moved or if one
message is wrong.
The Tactical Situation Object should contain at least the following information:
 Identification of the TSO and version (this information is provided in the XML
header of each TSO file, as the TSO file refers to the XML schema file name which
includes the TSO version number);
 Identification information:
o The identification of the individual message;
o Identification of its originator;
o The time o f creation;
o The relation to any other TSO;
o The organization level, confidentiality and urgency of the information;
o Links to external information.
 Description of the event:
o A limited assessment of the event;
o The location of the event and associated geograp hical information;
o Enumeration of the casualties found;
o Prediction of future casualties.
 Description of the resources:
o The resources each agency has available for the event;
o The resources in use;

NEXT GENERATION EMER GENCY SYSTEMS

27
o Resource capabilities;
o Resource position.
 Description of t he missions:
o The missions in progress;
o The missions foreseen.

Figure 7 – The high level TSO standard structure
The main entities of this standard are:
 Agency: An agency is an organization whose objectives include responding to
emergencies (ensuring public safety, saving lives, etc.). An agency may operate at
an international level (e.g. UN, Red Cross, etc.) or be limited to national or local
levels. The term in cludes ad hoc agencies, for example, a co -ordination body for a
specific event.

NEXT GENERATION EMER GENCY SYSTEMS

28
 Event: an event is something that takes place which an agency should respond to
(as defined by the agency's objectives), for example, a natural disaster or a fire in
a chemical factory. In practice, a major event may be decomposed into sub -events,
and require the response of multiple agencies.
 Node: A node is a facility owned by an agency, and which may provide TSO
messages to other nodes from the same or other agencies in order to share with
them part of the event information held at the node. The facilities which can create
TSO messages include, but are not limited to, fixed control rooms, mobile control
rooms, and co -ordination rooms set up for a specific event.
 TSO: A Tactica l Situation Object (TSO) is collection of information summarizing
an event, as seen by the node creating the TSO.
 Resource: A resource is something which can be used to support or help in the
response to an event.
 Mission: A mission is an activity aimed at reducing the impact of the event. A
mission has a goal and a plan. A TSO should describe all the current missions
controlled by the node creating the TSO, and may also include missions managed
by other nodes.
 Hierarchical levels: While there is no interna tional definition of the various
hierarchical levels for the agencies involved in rescue operations, the TSO standard
uses the following convention:
o A strategic command level establishes objectives and overall management
of the operations, ensuring that lo ng-term resources and expertise are
available. In some cases, each agency will have its own strategic command
level set up in a fixed control room, in others there is a joint common control
room. The strategic command level will interoperate with other com mand
units at the same level. The strategic command level will provide the
interface to Regional and Central Government when required.
o The operational command level determines priorities in obtaining and
allocating resources, monitors and co -ordinates the on-site response.

NEXT GENERATION EMER GENCY SYSTEMS

29
Emergencies responders will generally have one or more mobile control
rooms on the scene of the incident. Typically, operational commands will
co-ordinate activities with each other at shared boundaries and locations.
The operational com mand level will co -ordinate the activities of a number
of tactical command units. Co -ordination with NGOs may also be
undertaken.
o The tactical command level manages front line operations and the on -scene
emergency responders. Tactical command also provide s reports and
requests to operational command. Tactical commands co -ordinate activities
across other units at the tactical level where co -working exists.

NEXT GENERATION EMER GENCY SYSTEMS

30

Figure 8 – The detailed TSO standard structure

4.3 Creating local operational pictures LOPs

A local operational picture (LOP) is a single identical display of relevant (operational)
information of the disaster area constructed for local use (inside the agency).
Originally the LOP was an emerging military concept used to represent the battlespace and
all the elements contained (e.g. position of own troops and enemy troops, position and status
of important infrastructure such as bridges, roads, etc.) but it could be adapted in order to be
used in disaster management.

NEXT GENERATION EMER GENCY SYSTEMS

31
The l ocal operational picture can be used during disaster for taking decisions at the agency
level and it can be shared with other agencies.
Using the TSO standard, an agency could create its own LOP only by merging all the
actual TSO files that refers to the s ame disaster.

4.4 Creating common operational pictures COPs

Various LOPs may be shared electronically and fused into common operational
picture (COP). Ge nerally, sharing the LOP to form a COP implies that the LOP is replaced by
the COP and hence has limited duration.
A common operational picture (COP) is a single identical display of relevant (operational)
information shared by more than one Command . A COP facilitates collaborative planning and
assists all echelons to achieve situational awareness .
A commander's headquarters is typically r esponsible for ensuring that the appropriate
information is presented to the commander, so that he can make the best command decisions.
Traditionally, headquarters prepares maps w ith various symbols to show the locations of
friendly and enemy troops and other relevant information. In the modern military, the COP is
prepared electronically by a command and control battle command system (e.g. Army Battle
Command System ).
During a disaster, the Red plan imposes the reunion of Municipal Committee for
Emergency Situations. This committee represents a superagency that should be able to access
all the information of the other emergency agencies, actually to vie w the common operating
picture.

NEXT GENERATION EMER GENCY SYSTEMS

32

Figure 9 – Military COP example

NEXT GENERATION EMER GENCY SYSTEMS

33
5 Advanced Mobile Location (AML) implementation
5.1 Location and routing key concepts

5.1.1 Acquiring caller location

Acquiring location consists of determining a location and then making it available to some
other entity. Location determination may be done solely by the access network, it may be done
solely by the terminal device, or it may be done using a combination of both. There are pros
and cons to all of these approac hes.
To make routing decisions and to dispatch first responders an actual representation of the
caller’s location must be known. This is referred to as a location -value. Location -values may
be expressed as a civic address (street address) or a geodetic loc ation (latitude, longitude and
uncertainty).
The entities that have the location value, by definition, know where the call is, since this
is sensitive and private information it is not always desirable, or necessary for all entities
involved in the emergen cy call to have it. This leads to another form of location information,
the location reference (often represented as a URI), which can only be accessed by authorized
entities in order to obtain a location value. These two concepts are shown in Figure 3.

NEXT GENERATION EMER GENCY SYSTEMS

34

Figure 10 – Location value and location reference concepts

Geodetic locations are usually used to express location in wireless networks. They are
normally structured such they represent an area in which the caller may be found, t his is
referred to as the uncertainty, and a confidence, how likely the caller is to be in that area.

Figure 11 – Accuracy using uncertainty and confidence
An accurate location is one that has a small uncertainty area and a high confidence. In
general, decreasing the area reduces the confidence while increasing the area increases the
confidence. If the uncertainty area is reduced to a single point then the as sociated confidence
LIS
1. location request
2. location response
value
Service3. location conveyanceAccess Network Internet
Target
LIS
1. location request
2. location response
URI
Service3. location conveyanceAccess Network Internet
Target4. location request5. location responseLocation by value
Location by reference
Size of Area
or Volume
Uncertainty10%90%Likelihood of
Being There
Confidence

NEXT GENERATION EMER GENCY SYSTEMS

35
approaches zero. The IETF Uncertainty and Confidence specification provides a detailed
analysis of the relationship between confidence and uncertainty.
In traditional telecom provider networks, where the core -network is tightly coupled with
the access network, location determination is performed in the access network under instruction
from core -network entities and this is especially true in cellular networks. Location
determination may involve input from the calling device, but the loca tion itself is used by
mapping functions inside the operator’s network.
In contrast to this, conventional over -the-top (OTT) solutions generally rely on the device
providing the location to the service provider. While the location is passed to the service
provider, the location may be acquired in a number of ways including using GNSS, a third –
party Wi -Fi database, or an in -network service such a Location Information Server (LIS). One
of the issues raised with this approach is the trust -worthiness of the lo cation information if
provided by the application, but this can be overcome in some cases with careful engineering.
More recently, a third solution has emerged from ETSI specified in ES 203 187, that has
the voice provider use an access network Location Se rver (LS) to acquire location and
optionally routing information. This solution addresses the location trust issues, however, some
network configurations may pose issues if not correctly engineered.

5.1.2 Emergency call routing

Call routing involves mapping t he location to the PSAP address. This function may occur
at location acquisition time, as it does in most modern traditional telecommunication service
providers where the access and core -switching network are owned by the same entity. This
acquisition and mapping may also be performed simultaneously. Other solutions require an
external publicly accessible mapping function based on the Location to Service Translation
Protocol (LoST). More recently, RFC 6881 has been updated by the HELD routing
specification RFC 7840, so that route determination may be done at location determination
time and requested with the location. This approach, while still requiring a route determination

NEXT GENERATION EMER GENCY SYSTEMS

36
function, does not require that the route determination function be based on LoST a llowing
regions and access providers more flexibility in their choice of solution.

5.1.3 PSAP location acquisition

Acquiring location for routing needs to be a fast operation so that the connection of the
call is not impeded. This requirement for speed generally comes at the expense of accuracy,
while PSAP boundaries are usually quite large this trade -off for routing p urposes is generally
considered acceptable. When dispatching highly specialized equipment and personnel to
someone in a life threatening situation the financial costs, as well as the possible loss of human
life, incurred as a result of inaccurate location are seldom deemed acceptable. Consequently,
PSAPs need the most accurate location information available (smallest uncertainty for highest
confidence). In many cases this information can be determined and provided subsequent to, or
while the call is being d elivered to the PSAP.

The accurate location may be determined on demand from the PSAP, this approach is often
called the pull -method. Alternatively the network may decide when to determine this location
and subsequently push it to the PSAP. Each has its advantages and disadvantages and choice
of which method to implement is often a matter of local policy.
There several standards from the Internet Engineering Task Force (IETF) and Open
Mobile Alliance (OMA) that define how to deliver location to a PSAP and these will be
discussed in subsequent sections as specific architectures are explained in detail.

NEXT GENERATION EMER GENCY SYSTEMS

37

5.2 Network based location and routing architecture
5.2.1 Circuit -Switched Emergency Calling Architectures
5.2.1.1 Traditional Wireline

Figure 12 – Traditional wirelines location solution
In the traditional wireline service model, the operator owns the local access network (local
loop) and the local telephone exchange. All devices that connect to the access network are hard –
wired to the local exchange through a series of street cables, junction boxes and ultimately a
main distribution frame.
When a service is « connected », the telephone number is assigned and the location of the
service is captured. These two pieces of info rmation, along with other information such as the
subscriber’s name, and forwarded to the local PSAP by the local exchange carrier so that they
can be looked up in case of an emergency call. The local exchange is also configured so that
should the number a ssociated with the new service make an emergency call that the call is
directed to the correct PSAP.
Routing of emergency calls therefore is predetermined when the service is activated. Also,
the location of the device is static and is mapped to the subscr iber by the telephone number
both of which are provided to the PSAP when the service is activated.
Access Network
(Local Loop)Emergency
Network
Location
ServerEmergency
Service
GatewayPSAP
Route
Server
Local
ExchangeALI
Telephone
Service312TN Gateway
555-21624 777-12598
555-66634 777-12598
555-52398 777-12598
45
PSTN6
7

NEXT GENERATION EMER GENCY SYSTEMS

38

5.2.1.2 3GPP Cellular Network

Figure 13 – 3GPP Circuit -Switched Emergency Calling
Emergency calling in cellular mobile network if perfor med in a number of different ways.
One of the more common ways is for mobile operators to map cell coverage to PSAP areas and
then configure the MSC to route emergency calls originating from those cells to the pre –
determined PSAP.
Location information is t hen made available to PSAP and there is a great deal of variance
in how this is performed between different operators in different countries. Location procedures
for 3GPP networks are defined in TS 23.271 that also provides procedures for providing the
location of mobile device when an emergency call is initiated. These procedures are further
described in for emergency call in IMS in TS 23.167 and in circuit -switched TDM networks in
TS 29.002.
In the cicruit -swicthed model, the MSC is able trigger internal logic to invoke location
procedures. If the network is equipped with the serving mobile location centre, SMLC for 2G
or SAS for 3G, then more accurate positioning can take place, otherwise the MSC just sends a
Mobile Application Part (MAP) Subscriber Locat ion Report (SLR) to a gateway mobile
Emergency
Network
Gateway
MLCEmergency
Service
GatewayPSAP
Route
Server
MSCALI
2Cell-ID Gateway
555-222-333 777-12598
555-222-111 777-12598
555-222-854 777-12598
45
PSTN8
9
Cell-ID
and AreaCell-ID
and AreaSMLCBSCCallerCell-ID
555-222-333Cell-Id to Loc
Provisioning
31
6710
Access Network
(RAN)

NEXT GENERATION EMER GENCY SYSTEMS

39
location centre (GMLC) indicating the MSISDN of the calling device and the serving cell to
which the device was attached when the call was made.
There are also a variety of other mechanisms that have been implemented in Europe
including providing a pseudo -cell-id in the called -party or charging vectors of the ISUP
signaling.

5.2.2 IMS Emergency Calling Architecture

Figure 14 – Generic IMS emergency calling architecture

For cellular operators, the main location information used is the Location Area Code (LAC)
and the Cell ID. In legacy circuit switched systems, this information is inserted as part of the
call set -up, but this may not be the case for the IMS IP -based calli ng architecture. 3GPP allows
the P -CSCF in the serving access to add UE attachment information into the P -Access –
Network -Info (PANI) header field of the SIP INVITE message, for cellular networks this
information is the serving Cell ID. In addition to this, 3GPP defines a dedicated location
retrieval function (LRF). The LRF may include a route determination function (RDF) for
determining the correct PSAP to handle the call based on the location retrieved by the LRF or
the information contained in the PANI he ader field.
S-CSCFE-CSCF P-CSCF
IBCFLRF
MGCF
MwMw
MwMlMgIMS Network Emergency Network
Legacy
PSAPLe
NG
PSAPMxCS
Access
NetworkGmUE
PSAP Service
Provider
PSAP Service
Provider
Mm/Mx/MwIP

NEXT GENERATION EMER GENCY SYSTEMS

40
The E -CSCF needs to have the PSAP to route the call before forwarding the INVITE
message. The way the E -CSCF obtains this information is not clearly specified, and 3GPP
allows multiple ways to perform this retrieval.
In IMS the location of the UE’s point of attachment to the network is often conveyed in the
PANI header field and is set by the P -CSCF when the emergency call is initiated. The identity
of the user is based on the MSISDN and IMSI and the registration of the MSISDN is verified
by th e P-CSCF against the home subscriber server (HSS). Four common IMS location flows
are described in the subsequent sections.

5.3 Device based location and routing architecture
5.3.1 Device based location

In the previous sections we covered a range of different arch itectures that largely relied on
access network services and infrastructure to provide location and routing information for
emergency calls. Whilst there is little doubt that solutions based on this model provide
emergency services with the most dependabl e location information and the best PSAP address,
they require the access networks to have these services installed and provisioned and the
regulatory requirements for them to do so are not yet ubiquitous across European member
States.
In the absence of th ese network capabilities there has been substantial development and
deployment of wireless emergency calling applications that work on a variety of network types
including 3G, 4G and WiFi.
Device -based location refers to location information, usually a lo cation value, that is,
accessible to applications on the device. Most smartphones, tablets and laptops support
operating system APIs that allow applications the ability to request the location of the device.
Privacy requirements necessitate permission be g ranted by the user to application before the
application can access the location information.
Device -based location solutions can deliver highly -accurate location information, however,
strong trust relationships between entities, such as the application, t he application provider and

NEXT GENERATION EMER GENCY SYSTEMS

41
downstream users of location (PSAPs) must be exist in order for these solutions to be used as
the primary means of providing location for emergency calls.

5.3.2 WiFi location solution and architecture

Using GNSS for location inf ormation is clearly an important upgrade over using cell -d
location info as used today in the majority of national emergency calling systems in Europe.
However, GNSS location might not be good enough when inside buildings, GNSS signals are
attenuated by wa lls and windows that may result in no fix at all, or the accuracy is such that
only the building or set of building can be determined from the provided location. Location of
this quality still makes it hard to find the person or people in need.
Wi-Fi locat ion systems can provide indoor positioning to accuracy of within 3 metres in the
horizontal axis but can also be used to provide accurate floor -level in the vertical axis allowing
callers to be located more quickly. Apply this kind of technology and making the information
available to emergency responders could have a very positive impact for callers requesting
assistance from inside large multi -story buildings.
The WiFi localization architecture is based on a centralized engine that receives information
from WiFi Access Points through the WiFi controllers. The centralized engine then computes
user location based on WiFi Access Points mapping information that had previously measured
and stored.

NEXT GENERATION EMER GENCY SYSTEMS

42

Figure 15 – WiFi localization archi tecture

In order for WiFi localization to work, multiple APs need to receive messages from the
Device. The device, if connected, will use only one WiFi channel for data connection, while
the neighboring APs use different channels. Basic WiFi localization systems r ely on Probe
Requests messages being periodically sent by the Device enabling it to identify neighboring
APs. More advanced WiFi localization systems have smart APs that are able listen to multiple
channels simultaneous enabling them to detect user devices that are not connected to them and
being able to use the user data messages transmitted over the WiFi network to assist in
positioning the device.
The WiFi APs transfer the device and signal information to the WiFi controllers over the
management interfa ce (usually CAPWAP). The main information transferred is the client
MAC and received signal strength indicator (RSSI) (completed with other information if the
Device is associated to the WiFi network: IP address, SSID, etc.). Some more advanced APs
are als o able to determine the angle of arrival of the broadcast leading to a much better location.
The WiFi controllers pass the information aggregated from multiple APs to the location
engine. The location engine has pre -provisioned the maps with the location of each AP and its
antenna configuration (radiation patters, azimuth, and elevation). Using this information and
the data received from APs (RSSI and possible angle of arrival) the engine can compute the
location of the device on the map and export this i nformation.
Wi-Fi networkWi-Fi AP
DeviceWi-Fi AP
Wi-Fi AP
Wi-Fi APWi-Fi
controller
Wi-Fi
controllerLocation
EngineMaps and AP
placement

NEXT GENERATION EMER GENCY SYSTEMS

43

5.3.3 Routing

The emergency applications today are very limited in their reach. They are designed and
developed within a specific region or member state and have strong ties with the PSAPs serving
those areas. For the most part where routing to mo re than one PSAP is possible, the routing
capability is built into the application on the smart device, requiring it to hold or maintain PSAP
routing boundaries. Clearly, such a solution does not scale to a pan -European level, even if the
PSAP boundaries a re significantly reduced in accuracy.
The IETF LoST approach requires a hierarchy of geospatial routing databases each rolling
up service boundaries from a lower -level server which ultimately leads to a local
“authoritative” server, the owner of which is ultimately the organization that determines the
correct PSAP boundary information. Such solutions are expensive and generally require direct
government involvement, regulation and funding. At the time of writing, there are no known
national deployments of such solutions. Even if there was a network of LoST servers from
which a user -device could learn the destination PSAP address, there are trust issues that need
to be resolved between the application and the PSAP before the information can flow.
Information should be routed based on geographic information. For the most part, the call
(voice, video, text) is transferred by, what has thus far been termed the VSP. Ancillary data,
such as device provide location information and user information is conveyed and r outed over
the PEMEA network using progressive hops. This method only requires coarse boundaries in
order to finally deliver the data to the correct PSAP.
There could be another hybrid solution where an application location server, the GeoHub,
can take loc ation information from a device application or subsystem and determine a route to
an emergency gateway for pre -arranged areas. Once the call is through the gateway and into
the emergency network then actual PSAP determination becomes the responsibility of the route
server inside the emergency network.

NEXT GENERATION EMER GENCY SYSTEMS

44

Figure 16 – Location and routing hybrid solution

Access NetworkUE (Caller)OTT Voice
Provider
Route
ServeriaieEmergency
Calling Service
Provider
E-CSCF
x
im
ikLRF
GW-LISicif
igih
PSAPEENA
App
APIInternet

NEXT GENERATION EMER GENCY SYSTEMS

45
6 Bibliography
1) U.S. Department of Homeland Security, National incident management system,
Washington DC, 2008;
2) Jorg Kienzle, Nicolas Guelfi and Sadaf Mustafiz, Crisis Management Systems A Case
Study for Aspect -Oriented Modeling, 2009;
3) Kforce Government Solutions Inc (KGS), Common operational picture (COP)
solutions, brochure;
4) Gary Stoneburner, Alice Goguen, Alexis Feringa, Risk Management Guide for
Information Technology Systems, 2002;
5) Viktoria Hagelstedt, Swedish Emergency Management Agency (SEMA), 2008;
6) http://www.112.ro/index.php
7) ORDIN Nr. 2021/691 din 12 decembrie 2008 pentru aprobarea Normelor metodologice
de aplicare ale ti tlului IV "Sistemul național de asistență medicală de urgență și de prim
ajutor calificat" din Legea nr. 95/2006 privind reforma în domeniul sănătății;
8) ORDIN nr. 203 din 7 septembrie 2010 pentru aprobarea structurii -cadru a Planului rosu
de interventie.
9) Dennis K. Leedom, Ph.D., Evidence Based Research, Inc., NEXT GENERATION
COMMON OPERATING PICTURE;
10) Mikael Korhonen, Morgan Sjöquist, Tactical Situation Object – Enabling joint Crisis
Management Training, 2008;
11) Gary Machado, Tony O’Brien, Advanced Mobile Loc ation in the UK, 2015