Disertatie Filip Alexandru Giorgi V2 [604448]

“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 -Alexand ru Giorgi ,
Engineer
BUCHAREST
2017

Table of contents

1 Introduction ………………………….. ………………………….. ………………………….. ………………………….. ………. 4
2 Emergency services ………………………….. ………………………….. ………………………….. ………………………… 7
2.1 Main emergency services ………………………….. ………………………….. ………………………….. ………… 7
2.2 Other emergency services ………………………….. ………………………….. ………………………….. ………… 8
2.3 Civil emergency services ………………………….. ………………………….. ………………………….. …………. 9
2.4 Collaboration ………………………….. ………………………….. ………….. Error! Bookmark not defined.
3 North American emergency system ………………………….. ………………………….. ………………………….. … 10
4 European systems and sta ndards ………………………….. ………………………….. ………………………….. …….. 10
4.1 EENA ………………………….. ………………………….. ………………………….. ………………………….. …….. 12
5 Romania ………………………….. ………………………….. ………………………….. ………………………….. …………. 12
5.1 Operating model ………………………….. ………………………….. ………………………….. …………………… 13
5.2 The call handling process ………………………….. ………………………….. ………………………….. ………. 14
5.3 The red plan ………………………….. ………………………….. ………………………….. …………………………. 15
6 Improving the emergen cy management process ………………………….. ………………………….. ……………. 16
6.1 Agency level operational improvement ………………………….. ………………………….. ………………… 17
6.2 Using CAP standard ………………………….. ………………………….. ………………………….. ……………… 21
7 Improving the disaster management process ………………………….. ……. Error! Bookmark not defined.
7.1 Using TSO standard ………………………….. ………………………….. ………………………….. ………………. 23
7.2 Creating local operationa l pictures LOPs ………………………….. ………………………….. ……………… 27
7.3 Creating common operational pictures COPs ………………………….. ………………………….. ………… 28
8 Location and routing key concepts ………………………….. ………………………….. ………………………….. ….. 30
8.1 Acquiring caller location ………………………….. ………………………….. ………………………….. ……….. 30
8.2 Emergency call routing ………………………….. ………………………….. ………………………….. ………….. 32
8.3 PSAP location acquisiti on ………………………….. ………………………….. ………………………….. ……… 32
9 Network based location and routing architecture ………………………….. ………………………….. …………… 34
9.1 Circuit -Switched Emergency Calling Architectures ………………………….. ………………………….. .. 34
9.1.1 Traditional Wireline ………………………….. ………………………….. ………………………….. ……………… 34
9.1.2 3GPP Cellular Network ………………………….. ………………………….. ………………………….. …………. 35
9.2 IMS Emergency Cal ling Architecture ………………………….. ………………………….. ………………….. 36
10 Device based location and routing architecture ………………………….. ………………………….. ……………… 38
10.1 Device based location ………………………….. ………………………….. ………………………….. ……………. 38
10.2 WiFi location solution and architecture ………………………….. ………………………….. ………………… 38
10.3 Routing ………………………….. ………………………….. ………………………….. ………………………….. …… 40
11 Bibliography ………………………….. ………………………….. ………………………….. ………………………….. ……. 43

List of figures

Figure 1 – Emergency management process flow ………………………….. ………………………….. ……………………… 16
Figure 2 – Actual agency level process flow ………………………….. ………………………….. ………………………….. ….. 19
Figure 3 – Proposed agency level process flow ………………………….. ………………………….. ………………………….. 20
Figure 4 – CAP standard structure ………………………….. ………………………….. ………………………….. ………………. 23
Figure 5 – The high level TSO standard structure ………………………….. ………………………….. ………………………. 25
Figure 6 – The detailed TSO standard structure ………………………….. ………………………….. …………………………. 27
Figure 7 – Military COP example ………………………….. ………………………….. ………………………….. …………………. 29
Figure 3 – Location value and location reference concepts ………………………….. ………………………….. …………. 30
Figure 4 – Accuracy using uncertainty and c onfidence ………………………….. ………………………….. ……………….. 31
Figure 5 – Traditional wirelines location solution ………………………….. ………………………….. ………………………. 34
Figure 6 – 3GPP Circuit -Switched Emergency Calling ………………………….. ………………………….. ………………….. 35
Figure 7 – Generic IMS emergency calling architecture ………………………….. ………………………….. ………………. 36
Figure 8 – WiFi localization architecture ………………………….. ………………………….. ………………………….. ………. 39
Figure 9 – Location and routing hybrid solution ………………………….. ………………………….. ………………………… 41

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 specific 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 Romania n
emergency system which is considered one of the most technologically advanced in Europe.
The second part of the dissertation co ntains the changes proposed to be implemented
locally, a t national level or globally aiming to im plement new emergency systems by using
cutting -edge technology and knowledge .

FILIP -ALEXANDRU GIOR GI

1 Introduction
An emergency is a sudden, unexpected, or impending situation that poses an
immediate risk to health, life, property or environmen t. 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 smaller incidents require that an observer (or affected party) decide
whether it qualifies as an emergency and he announces the agencies in charge of solving t he
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 contact emergency
services, and thus, be able to ask for help. The knowledge of such number is the firs t 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 Member States of the
European Union and also in other European countries. There are countries where only this
single emergency number is availab le and others that have different national, regional or local
numbers for contacting fire and rescues services, police and emergency medical 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 emergency number to dial. This
is the reason why every single step in the 112 chain is crucial.

NEXT GENERATION EMER GENCY SYSTEMS

Figure 1 – Emergency service task chain

1.1 Knowledge of 112
In an emergency situation, the citizen may not be in a pos ition to search and establish
the appropriate emergency number to call. This number should be previously known so it can
be dialed immediately in case of need. This is the reason why education of citizens and
dissemination of information about the Europea n emergency number is crucial.
The knowledge of the 112 emergency number is not as wide as desirable. The results
of the European Emergency Number 112 Eurobarometer survey speak for themselves: only
50% of the citizens would call 112 in the event o f emergencies in their own country and 76%
would not use 112 in case of an emergency in another EU country.
The European dimension of 112 should be communicated to all citizens. It is
important that travelers are informed about the availability of the Eur opean emergency number.
Most people travelling abroad do not even think about the possibility of being involved in an
emergency situation during their journey. This is why authorities cannot count into travelers’
own initiative to find out what number to use in case of emergency. Campaigns and
dissemination efforts are needed to ensure that travelers know what emergency number to use
in case of distress.

1.2 Device
The first link of the chain is to know the emergency number. Then, the citizen needs
a fully fu nctioning 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 emergency

FILIP -ALEXANDRU GIOR GI

number even if the device is blocked. This way, the person in an emergency situa tion 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 phone
calls. This is the reason why the availability of mobile telephony within range pl ays 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 another 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 available call taker as soon as possible. Resources have
to be optimized to guarantee a min imum 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 line identification, something
that ensures that calling back is possible.

1.6 Dispatch app ropriate 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 locati on of the
incident and assist the citizens who are involved.

NEXT GENERATION EMER GENCY SYSTEMS

2 Emergency services
Emergency services and rescue services are public or private organizations which
ensure public safety and health by addressing dif ferent emergencies. Some of these agencies
exist solely for addressing certain types of emergencies whilst others deal with ad -hoc
emergencies as part of their normal responsibilities. Many of these agencies engage in
community awareness and prevention pro grams to help the public avoid, detect, and report
emergencies effectively.
The availability of emergency services depends very heavily on location, and may in
some cases also rely on the recipient giving payment or holding suitable insurance or other
surety for receiving the service.

2.1 Main emergency services

There are three main emergency service functions:
 Police — providing community safety and acting to reduce crime against
persons and property;
 Fire department (fire and rescue service) — providing fir efighters to deal with
fire and rescue operations, and may also deal with some secondary emergency
service duties;
 Emergency medical services (EMS) — providing ambulances and staff to deal
with medical emergencies.
In some countries such as the UK, these t hree functions are performed by three
separate organizations in a given area. However, there are also many countries where fire,
rescue and ambulance functions are all performed by a single organization. In Romania, there
are two different entities protect ing the health and life: The ambulance service – a standalone
agency coordinated by the Health Ministry and the SMURD (Mobile Emergency Service for
Resuscitation and Extrication) – and agency that is coordinated by the firefighters under the
Ministry of th e Interior.
Emergency services have one or more dedicated emergency telephone numbers
reserved for critical emergency calls. In some countries, one number is used for all the

FILIP -ALEXANDRU GIOR GI

emergency services (e.g. 911 in the U.S., 999 in the UK, 112 in EU). In some cou ntries, each
emergency service has its own emergency number.

2.2 Other emergency services
These services can be provided by one of the core services or by a separate
government or private body.
 Military — to provide specialist services, such as bomb disposal or to
supplement emergency services at times of major disaster, civil dispute or high
demand;
 Coastguard — Provide coastal patrols with a security function at sea, as well
as involvement in search and rescue operations;
 Lifeboat — Dedicated providers of r escue lifeboat services, usually at sea
(such as by the RNLI in the United Kingdom);
 Mountain rescue — to provide search and rescue in mountainous areas, and
sometimes in other wilderness environments;
 Cave rescue — to rescue people injured, trapped, or lo st during caving
explorations;
 Mine rescue — specially trained and equipped to rescue miners trapped by
fires, explosions, toxic gas, flooding, etc.;
 Technical rescue — other types of technical or heavy rescue, but usually
specific to a discipline;
 Search and rescue — can be discipline -specific, such as urban, wildland,
maritime, etc.;
 Wildland fire suppression — to suppress, detect and control fires in forests and
other wildland areas.
 Bomb disposal — to render safe hazardous explosive ordnance, such as
terrorist devices or unexploded wartime bombs;
 Blood/organ transplant supply — to provide organs or blood on an emergency
basis, such as the National Blood Service of the United Kingdom;

NEXT GENERATION EMER GENCY SYSTEMS

 Emergency management — to provide and coordinate resources during large –
scale emergencies;
 Amateur radio emergency communications — to provide communications
support to other emergency services, such as RAYNET in the UK;
 Hazmat — removal of hazardous materials.
 Air search providing aerial spotting for the emergency services, such as the
one conducted by the Civil Air Patrol in the US, or Sky Watch in the UK.

2.3 Civil emergency services

These groups and organizations respond to emergencies and provide other safety –
related services either as a part of their on -the-job duties, as part of the main mission of their
business or concern, or as part of their hobbies.
 Public utilities — safeguarding gas, electricity and water, which are all
potentially hazardous if infrastructure fails;
 Emergency road service — provide repair or recover y for disabled or crashed
vehicles;
 Civilian Traffic Officers — such as operated by the Highways Agency in the
UK to facilitate clear up and traffic flow at road traffic collisions;
 Emergency social services;
 Community emergency response teams — help organ ize facilities such as rest
centers during large emergencies;
 Disaster relief — such as services provided by the Red Cross and Salvation
Army;
 Famine relief teams;
 Amateur radio communications groups — provide communications support
during emergencies;
 Poison Control — providing specialist support for poisoning;
 Animal control — can assist or lead response t o emergencies involving
animals.

FILIP -ALEXANDRU GIOR GI

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 (te lco) 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).
In over 98 percent of locations in the United States and Canada, dialing "9 -1-1" from
any telepho ne 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 caller'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 common emergency telephone number that can be dialed free of charge
from most mobile telephones and, in some countries, fixed telephones in order to
reach emergency services (ambulance, fire an d rescue, police, etc.).
112 is a part of the GSM standard and all GSM -compatible telephone handsets are
able to dial 112 even when locked or with no SIM card present. It is also the common
emergency number in all member states of the European Union as well as several other
countries of Europe and the world. It is often available alongside other numbers traditionally

NEXT GENERATION EMER GENCY SYSTEMS

used in the given country to access emergency se rvices. In some countries, calls to 112 are not
connected directly but forwarded by the GSM network to local emergency numbers.
The 112 concept was first standardized by a recommendation by the CEPT (The
European Conference of Postal and Telecommunications Administrations) in 1972 and later
by a decision of the EU Council in 1991 and subsequently rea ffirmed in 2002 by article 26 of
the Universal Service Directive and its subsequent amendments.
This choice of the 112 number has several advantages:
 Different digits: with the numeric keypads used universally today, using at
least two different digits instead of the same digit repeatedly significantly
reduces the risk of accidental calls. Young children, vibrations, defective keys
and collisions with other objects are muc h more likely to press the same key
repeatedly than a particular sequence of different keys, particularly with a
button -operated keypad. Accidental calls to emergency centers from mobile
phones, which can dial emergency numbers even with locked keypad, are a
particular problem with same -digit numbers, such as the UK's 999.
 Low digits: in the days of rotary dial telephones, using only those digits that
require the least dial rotation (1 and 2) permitted a dial lock in hole 3 to
effectively disable unauthorized access to the telephone network without
preventing access to the emergency number 112. The same choice also
maximized dialing speed.
112 is managed and financed in the European Union by each Member State (country)
which also decide on the organization of the emergency call centers. The number is also
adopted in the candidates for EU accession and members of the EEA (European Economic
Area) agreement .
The International Telecommunications Union recommends that member states that
are selecting a primary or secondary emergency number choose either 911, 112 or both. 112 is
one of two numbers (the other being the region's own emergency number) that can be dialed
on most GSM phones even if the phone is locked.
E112 is a location -enhanced version of 112. The telecom operator transmits the
location information to the emergency center. The EU Directive E112 (2003) requires mobile

FILIP -ALEXANDRU GIOR GI

phone networks to provide emergency services with whatever information they have about the
location a mobile call was made.

2.5.1 EENA

EENA, the European Emergency Number Association, is a Bruss els-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 discussion platform for emergency services, public
authorities, decision makers, researchers, international as sociations and solution providers in
view of improving emergency response in accordance with citizens' requirements. EENA is
also promoting the establishment 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 Single National Emergency Call System (SNECS) is a vital constituent of the
universal service obligations, as laid down in one of the Directives of the EU, significant for
policy -makin g in the telecommunications field.
Dialing 112 is a fast way to communicate with the emergency dispatcher centers
(Police, Fire Brigade, Ambulance) in case of emergency. The 112 Emergency System works
as a countrywide service on all fixed or mobile telepho ne networks.
The 112 system aims at ensuring citizen protection and providing the highest level of
assistance, regardless of their location. The Single National Emergency Call System consists
of emergency call answering centers (Public Safety Answering Po ints) and their associated
equipment – an operative telecommunications system, designed to notify, receive, process and
transfer the emergency calls to the requested services, in a centralized and unitary way. The

NEXT GENERATION EMER GENCY SYSTEMS

system also applies to the communications between the Police, the Fire Brigade, and the
Ambulance special response systems which have the obligation to respond in case of
emergency calls. In the future, depending on the developing necessities, new response agencies
will be gradually encompassed: t he Gendarmerie, the Civil Protection and Antiterrorism units.
This integrated system operation is set up with the purpose of ensuring the protection
of the citizens’ life and goods and will bring forth a state of normality in Romania, similar to
that of th e other European countries. The efficiency of this system will largely depend on the
prompt response of the emergency agencies (Police, Ambulance, Fire Brigade, etc.) to the crisis
situations reported by the emergencies calls.
The Public Safety Answering P oint personnel is composed of professionals who
respond to the emergency calls 24/7. They are trained to assist the callers during the emergency
situations and help them as soon as possible.

The main objective of 112 is to safeguard:
 lives
 property
 environment
The Single System for Emergency Calls establishes the contact between the caller
asking for help in an emergency situation and the public safety agencies (their dispatcher
centers).

2.6.1 Operating model

The Public Safety Answering Points have a datab ase which helps 112 call takers to
locate the call and identify the nature of incident and the adequate response resources. This is
possible by using two identification indicators:
 ANI automatic number identification: The caller’s telephone number is
autom atically displayed.
 ALI automatic location identification:
The caller’s address, the place he calls from and further information needed to find
the optimal solution for the response to reach the incident site in time are displayed.

FILIP -ALEXANDRU GIOR GI

During the response to an emergency, the AVL application (Automatic Vehicle
Location) is also used to identify the position of the vehicles responding to emergency
situations, equipped with (conventional or digital) radio communications equipment, including
a GPS subsystem.
In order to route the data between the mobile terminals and AVL server, the AVL
application uses digital radio and /or analogue (conventional) networks, to locate the response
vehicles and identify the best routes to get to the incident site.

Figure 2 – Romani an emergency sys tem architecture

2.6.2 The call handli ng process

The call handling process has several stages:
 a caller dials 112 to report serious accidents, resulting in human casualties.
 the system identifies the caller’s phone number
 the caller’s name and address are then determined by database automatic
search (the same process applies to the European Union countries, USA and
Canada, too, as a measure needed to confirm call authenticity);
 the call taker requests incident information from the caller;
 all the data are then transmitted to the Police, the Fi re Brigade and the
Ambulance dispatchers, depending on the case type (no longer than 2 -3
seconds time frame);

NEXT GENERATION EMER GENCY SYSTEMS

 the dispatchers rapidly identify the means of response (response services)
participating in the case resolution, using the AVL application (Automa tic
Vehicle Location);
 the case -response services connection is displayed on the map.

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 st ructures 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 methods 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 increases quickly and affects an entire buil ding) 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 decide the activation
of the red plan is the head of the county or the chief inspector of the emergency situations
inspectorate.

FILIP -ALEXANDRU GIOR GI

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 level s 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 forwards the call to specific agencies. Here, the specialized
dispatche rs 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;
 Decides, based on protocols, which primary response to send;

NEXT GENERATION EMER GENCY SYSTEMS

 Transmits the data / case file to experts from related agencies.
 Agency experts:
 Follow up case;
 Decide if seconda ry 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 bus iness 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 speaking with the caller for gathering agency
specific information (for exa mple 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 forwards 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 the 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 line
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
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)

FILIP -ALEXANDRU GIOR GI

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 caller s (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 th e 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 c apable 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
collected following the
procedures The emergency services’ call taker asks the caller 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.
New information given
by other callers Different calls may be received for the same accident. If possible,
all information should be centralize d and shared. Care must be

NEXT GENERATION EMER GENCY SYSTEMS

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 collision, 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, additional
information can be added and updates inputted as necessary.

This proce ss 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 intervention.

Figure 4 – Actual agency level process fl ow

FILIP -ALEXANDRU GIOR GI

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 alre ady 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 th e 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.
In this case the dispatchers will receive from the coordinator the mission orders (the
link between a ca se 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

4 Using standards
4.1 CAP standard

The Common Alerting Protoc ol (CAP) is an XML -based data format for
exchanging public warnings and emergencies betw een alerting technologies . CAP allows a
warning message to be consistently disseminated simultaneously o ver many warning systems
to many applications. CAP increases warning effectiveness and simplifies the task of activating
a warning for responsible officials.
Standardized alerts can be received from many sources and configure their
applications to process and respond to the alerts as desired. Alerts from the Department of
Homeland Security , the Department of the Interior 's United States Geological Survey , and the
United States Department of Commerce 's National Oceanic and Atmospheric
Administration (NOAA), and state and local government agencies can all be received in the
same format, by the same application. That application can, for example, sound different alarm s
based on the information received.
By normalizing alert data across threats, jurisdictions, and warning systems, CAP also
can be used to detect trends and patterns in warning activity, such as trends that might indicate
an undetected hazard or hostile ac t. From a procedural perspective, CAP reinforces a research –
based template for effective warning message content and structure.
The CAP data structure is backward -compatible with existing alert formats including
the Specific Area Message Encoding (SAME) used in Weatheradio and the
broadcast Emergency Alert System as well as new technology such as the Wireless Emerg ency
Alerts (WEA), while adding capabilities including:
 Flexible geographic targeting using latitude/longitude “boxes” and other
geospatial representations in three dimensions;
 Multilingual and multi -audience messaging;
 Phased and delayed effective times a nd expirations;
 Enhanced message update and cancellation features;
 Template support for framing complete and effective warning messages;
 Digital encryption and signature capability;

FILIP -ALEXANDRU GIOR GI

 Facility for digital images, audio, and video.

This protocol is already u sed in North America (USA and Canada) and Australia.
In early 2005, the U.S. Department of Homeland Security (DHS), in partnership with
the Association of Public Television Stations, demonstrated CAP -based "digital EAS"
broadcasts over public television di gital TV transmitters and satellite links in the Washington,
D.C. area and nationwide.
CAP is the foundation technology for the planned "Integrated Public Alert and
Warnin g System", an all -hazard, all -media national warning architecture being developed by
DHS, the National Weather Service within NOAA, and the Federal Communications
Commission .
In Canada, a working group composed of public alerting practitioners and government
agencies has developed a CAP Can adian Profile (CAP -CP) based on CAP but specialized to
address the needs of Canadian public alerting stakeholders, such as bilingualism, geocoding
for Canada, managed lists of locations and events, etc. The Canadian government has adopted
CAP -CP for its Na tional Public Alerting System (NPAS) project. The CAP -CP working group,
along with stakeholders and projects such as the Canadian Public Safety Operations
Organization (CanOps) and Netalerts' Sarnia Lambton trial, are now working with and refining
CAP -CP for national application in Canada.
CAP has been implemented for a small -scale, grassroots hazard information system
in Sri Lanka following the 2004 Indian Ocean Tsunami . This implementation was part of the
"HazInfo Project", funded by Canada's International Development Research Centre.
The province of Alberta adopted CAP as part of its Alberta Emergency Alert system.
In March 2015, Alert Ready , a national public warning system based upon CAP -CP, was
officially launched. Participation in the system by broadcasters is mandated by the Canadian
Radio -television and Telecommunications Commission .
The A ustralian Government Standard for Common Alerting Protocol (CAP -AU-STD,
2012) was developed by a CAP -AU-STD stakeholder group comprising federal agencies
Emergency Management Australia, the Bureau of Meteorology, GeoScience Australia,
Department of Agricul ture, Fisheries and Forestry and the Department of Health, as well as a
number of State Government authorities and emergency services agencies. The project was

NEXT GENERATION EMER GENCY SYSTEMS

coordinated by the Australian Government Attorney -General's Department (Australian
Emergency Man agement).

Figure 6 – CAP standard structure

4.2 TSO standard

The TSO defines an inform ation 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

FILIP -ALEXANDRU GIOR GI

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.
This information contributes to the situational awareness of the various parties, that
is, their awareness of the current state of the world, the actions of the agents involve d 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 the specification is to en sure 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, it
is a problem for the re cipients 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 of 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 geographical information;
o Enumeratio n 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

o Resource capabilities;
o Resource position.
 Description of the 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 publi c 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 includes ad hoc agencies, for example, a co -ordination body for a
specific event.
 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

FILIP -ALEXANDRU GIOR GI

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 cre ate
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 Tactical 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 th e current missions
controlled by the node creating the TSO, and may also include missions managed
by other nodes.
 Hierarchical levels: While there is no international definition of the various
hierarchical levels for the agencies involved in rescue operati ons, the TSO standard
uses the following convention:
o A strategic command level establishes objectives and overall management
of the operations, ensuring that long -term resources and expertise are
available. In some cases, each agency will have its own stra tegic 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 command
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.
Emergencies responders will generally have one or more mobile control
rooms o n the scene of the incident. Typically, operational commands will
co-ordinate activities with each other at shared boundaries and locations.
The operational command level will co -ordinate the activities of a number

NEXT GENERATION EMER GENCY SYSTEMS

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 provides reports and
requests to operational command. Tactical commands co -ordinate activities
across o ther units at the tactical level where co -working exists.

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 (op erational)
information of the disaster area constructed for local use (inside the agency).

FILIP -ALEXANDRU GIOR GI

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, p osition and status
of important infrastructure such as bridges, roads, etc.) but it could be adapted in order to be
used in disaster management.
The local operational picture can be used during disaster for taking decisions at the agency
level and it can b e 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 same disaster.

4.4 Creating common operational pictures COPs

Various LOPs may be shared electronically and fu sed into common operational
picture (COP). Generally, sharing the LOP to form a COP implies that the LOP is replaced by
the COP and hence has limited d uration.
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 responsible for ensuring that the appropriate
information is presented to the commander, so that he can mak e the best command decisions.
Traditionally, headquarters prepares maps with various symbol s 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 cont rol 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 view the common operating
picture.

NEXT GENERATION EMER GENCY SYSTEMS

Figure 9 – Military COP example

FILIP -ALEXANDRU GIOR GI

5 Location and routing key concepts

5.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 termin al device, or it may be done using a combination of both. There are pros
and cons to all of these approaches.
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 location (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 emergency 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.

Figure 10 – Location value and location reference concepts
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

NEXT GENERATION EMER GENCY SYSTEMS

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

Figure 11 – Accuracy u sing 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 reduc ed to a single point then the associated confidence
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 location 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 l ocation 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 i s the trust -worthiness of the location 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 u se an access network Location Server (LS) to acquire location and
Size of Area
or Volume
Uncertainty10%90%Likelihood of
Being There
Confidence

FILIP -ALEXANDRU GIOR GI

optionally routing information. This solution addresses the location trust issues, however, some
network configurations may pose issues if not correctly engineered.

5.2 Emergency call routin g

Call routing involves mapping the 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
function, does not require that the route determi nation function be based on LoST allowing
regions and access providers more flexibility in their choice of solution.

5.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 purposes 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 (small est uncertainty for highest
confidence). In many cases this information can be determined and provided subsequent to, or
while the call is being delivered to the PSAP.

The accurate location may be determined on demand from the PSAP, this approach is ofte n
called the pull -method. Alternatively the network may decide when to determine this location

NEXT GENERATION EMER GENCY SYSTEMS

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.

FILIP -ALEXANDRU GIOR GI

6 Network ba sed location and routing architecture
6.1 Circuit -Switched Emergency Calling Architectures
6.1.1 Traditional Wireline

Figure 12 – Traditional wirelines location solution
In the traditional wireline service model, the operator owns the lo cal 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 information, along with other information such as the
subscriber’s name, and forwarded to the local PSAP by the local exchange carrier so t hat they
can be looked up in case of an emergency call. The local exchange is also configured so that
should the number associated with the new service make an emergency call that the call is
directed to the correct PSAP.
Routing of emergency calls therefo re is predetermined when the service is activated. Also,
the location of the device is static and is mapped to the subscriber 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

6.1.2 3GPP Cellular Network

Figure 13 – 3GPP Circuit -Switched Emergency Calling
Emergency calling in cellular mobile network if performed 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 con figure the MSC to route emergency calls originating from those cells to the pre –
determined PSAP.
Location information is then made available to PSAP and there is a great deal of variance
in how this is performed between different operators in different cou ntries. 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, th en more accurate positioning can take place, otherwise the MSC just sends a
Mobile Application Part (MAP) Subscriber Location Report (SLR) to a gateway mobile
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.
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)

FILIP -ALEXANDRU GIOR GI

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.

6.2 IMS Emergency Calling Arc hitecture

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 calling 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 INVI TE 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 header field.
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.
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

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 the P -CSCF against the home subscriber server (HSS). Four common IMS location flows
are described in the subsequent sections.

FILIP -ALEXANDRU GIOR GI

7 Device based location and routing ar chitecture
7.1 Device based location

In the previous sections we covered a range of different architectures that largely relied on
access network services and infrastructure to provide location and routing information for
emergency calls. Whilst there is lit tle doubt that solutions based on this model provide
emergency services with the most dependable location information and the best PSAP address,
they require the access networks to have these services installed and provisioned and the
regulatory requiremen ts for them to do so are not yet ubiquitous across European member
States.
In the absence of these 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 location 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 granted by the user to application before the
application can access the location information.
Device -based location solutions can deliver highly -accurate locatio n information, however,
strong trust relationships between entities, such as the application, the application provider and
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.

7.2 WiFi location solution and architecture

Using GNSS for location information 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, G NSS location might not be good enough when inside buildings, GNSS signals are
attenuated by walls 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.

NEXT GENERATION EMER GENCY SYSTEMS

Wi-Fi location 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 verti cal 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 p reviously measured
and stored.

Figure 15 – WiFi localization architecture

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 f or data connection, while
the neighboring APs use different channels. Basic WiFi localization systems rely on Probe
Requests messages being periodically sent by the Device enabling it to identify neighboring
APs. More advanced WiFi localization systems hav e 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 interface (usually CAPWAP). The main information transferred is the client
MAC and received signal strength indicator (RSSI) (completed with other information i f the
Wi-Fi networkWi-Fi AP
DeviceWi-Fi AP
Wi-Fi AP
Wi-Fi APWi-Fi
controller
Wi-Fi
controllerLocation
EngineMaps and AP
placement

FILIP -ALEXANDRU GIOR GI

Device is associated to the WiFi network: IP address, SSID, etc.). Some more advanced APs
are also able to determine the angle of arrival of the broadcast leading to a much better location.
The WiFi controllers pass the information aggregated from m ultiple 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 po ssible angle of arrival) the engine can compute the
location of the device on the map and export this information.

7.3 Routing

The emergency applications today are very limited in their reach. They are designed and
developed within a specific region or memb er state and have strong ties with the PSAPs serving
those areas. For the most part where routing to more 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 bou ndaries. Clearly, such a solution does not scale to a pan -European level, even if the
PSAP boundaries are significantly reduced in accuracy.
The IETF LoST approach requires a hierarchy of geospatial routing databases each rolling
up service boundaries fro m 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 i nvolvement, 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 tha t 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 routed 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 location information from a device application or subsystem and determine a route to

NEXT GENERATION EMER GENCY SYSTEMS

an emergency gateway for pre -arranged areas. Once the call is through t he gateway and into
the emergency network then actual PSAP determination becomes the responsibility of the route
server inside the emergency network.

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

FILIP -ALEXANDRU GIOR GI

NEXT GENERATION EMER GENCY SYSTEMS

8 Bibliography
1) U.S. Depart ment 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 o perational 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 ?limba=en
7) ORDIN Nr. 2021/691 din 12 decembrie 2008 pentru aprobarea Normelor metodologice
de aplica re ale titlului 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 interv entie.
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;