Finland Introduction
Finland has a single-layered PSAP system, which now has 15 PSAPs (In Finland referred as Emergency Rescue Centres) which all use the same central emergency situation handling system with connections to police and rescue forces systems and databases. So when there is an incident on the road and someone phones to the PSAP/ERC from the scene, it is directed to the nearest PSAP which takes care of dispatching the help to the spot. Currently the location of the incident is either given by the informer (address) or via mobile network cell-id. eCall handling procedure will work in a similar manner; the novelty will be the MSD bringing the exact GNSS coordinates of the location which will speed up the process.
The system for eCall piloting is built to simulate this straight-forward one-number emergency handling. The testing is done in simulated PSAP environment, and the experiences from the test bed are exploited in updating the real PSAP system.
PSAP (Emergency Rescue Centre Administration) is currently renewing its central system, the provider has just been selected and the work has begun. The new system will be functioning by 2015 in the same time as the organisational consolidation from 15 ERCs into 6. eCall will be included in the new system and all eCall related specifications and standards can be taken into account. First modules will be tested by 2013. As for the current system the discussions have begun with the system provider Siemens.
As for MSD mediating, as it is, to other officials’ databases (police, rescue forces, border guard etc.) it will not happen. PSAP/ERC will handle the MSD (extract it) and mediate the location data to other systems if needed. ERC takes care that all relevant information is mediated to the police and rescue forces as in current situation.
eCall pilot system architecture overview
Finnish eCall pilot system includes test bed, clients and IVS which use standardised in-band modem. Flag tests will be done with Finnish MNO’s (at least one) own laboratory.
Pilot testing environment is run completely separated from real PSAP system, but tests are going to be done also in PSAP environment when the necessary upgrading is done in the existing PSAP system.
Figure 2: Pilot System Architecture
The main parts of the system include:
eCall client simulator (eCall IVS)
PSAP simulator, which consists of eCall test bed system, and APIs to related test systems
eCall pilot system control and administrator’s UI.
eCall client simulator (IVS)
The eCall client (IVS) simulator include functionality for generating and combining eCall message data content, encoding the message data for data transfer, opening phone call and using in-band modem for sending eCall messages. It will include a user interface for configuring and generating eCall messages.
The generated MSD data is encoded for the data transfer according to the standard CEN EN 15722 (eCall minimum set of data). The client will use the eCall standardized in-band modem data transfer for sending messages.
The messages (opened voice call) are targeted to the configured phone number of the eCall receiver side (PSAP simulator). For testing purposes, the number is other than 112.
In addition to the client simulator, several client IVS prototypes will be used during the pilot phases (cf. Section 3.1.2.4 and 3.1.3).
The eCall test bed is the eCall message receiver part of the system. It includes functionality for handling incoming eCall phone calls. It receives and decodes eCall message data, includes interfaces for PSAP subsystems, provides logs for analysing results and includes facility for configuring the operation of the system.
A test phone number (other than 112) is configured for test bed to receive eCall phone calls. The test bed uses the standardized in-band modem to extract eCall data from the call.
The test bed decodes and validates incoming MSD messages. For analysing results, there is a log facility included into the system that provides information about received messages and error cases. In particular, it is used to validate the operation of the system as well as eCall clients. The logs generated by the test bed have a particular importance in validation of the system operation.
eCall pilot system control and administrator’s UI
During the tests, a Web user interface for managing the operation of the test bed will be used It provides configurations for the test users, possibility to register the eCall clients (e.g. client phone numbers) used in the tests. Also, the pilot system operation can be managed via the user interface. It will also provide views to result logs.
The log facility of the test bed will provide information about received messages (e.g. call time, modem session, duration, MSD information, warnings) and error cases. In particular, it will be used to validate the operation of the system as well as eCall clients.
eCall clients to be used in the tests, first phase requirements
The clients include functionality for generating and combining eCall message data content, encoding the message data for data transfer, opening phone call and using in-band modem for sending eCall messages to the test number of the eCall test bed. In addition, clients should be able to assign eCall flag for the call.
The minimum requirements for the IVS device prototypes are as follows:
generating eCall message data content (initiation of eCall). The required data content including location data is specified in the MSD specification CEN EN 15722.
encoding the message data for data transfer according to the MSD specification CEN EN 15722
opening voice call and using eCall in-band modem for data transfer according to eCall in-band modem specifications ETSI TS 126 267, ETSI TS 126 268 .
to implement eCall flag, which is specified in ETSI TS 124 008 (eCall Discriminator Table 10.5.135d)
In addition, the generic eCall operating and high level application requirements described in the specifications CEN 16062 and CEN 16072 are to be followed.
Device prototypes could be installed in vehicles. Optionally, they will be configurable to automatically initiate calls and in-band MSD transmission with predefined interval to the predefined number of the test bed.
eCall IVS systems
At least two different domestic IVS prototypes will be tested, and probably couple of foreign.
Gecko systems / www.geckosystems.fi
System description
Tokay is a multi-constellation tracking device compatible with all current and upcoming global navigation satellite systems. It has a quad-frequency GSM modem and support for two SIM cards for flexible cellular connectivity.
Functions supported
32 channel GPS/GLONASS/GALILEO/COMPASS/SBAS and Mobile (Cell ID)
tracking
Quad-band modem with 2 SIM card places, upgraded to standard in-band modem
Customizable firmware (Python)
10 I/O ports for telemetry (analogue/digital)
Internal backup battery (optional)
RS-232 output for NMEA 0183 data
Operating temperature from -40 to +85 °C
Robust aluminium casing
Indagon / www.indagon.fi
Indagon MTT 130A, MTT 130T, MTT 130F are tracking devices compatible with DGPS positioning and UMTS/HDSPA 900/2100 MHz and GSM/GPRS/EDGE 850/900/1800 MHZ mobile communication. They have aluminium casing, Operative temperature -40 to +65 °C. Positioning accuracy is <2 m.
Figure 3: Indagon MTT 130 IVS
Involved parties
Table 1: Involved Parties (Finland)
Name
|
Role
|
HeERO Consortium
|
Ministry of Transport and Communications
|
MS leader
|
Yes
|
Emergency Rescue Centre Administration
|
Responsible of PSAP system development, PSAP training, PSAP test environment
|
Yes
|
VTT
|
Responsible for operating the Finnish National Pilot, test bed functions and tests
|
Yes
|
Gecko Systems
|
IVS vendor
|
subcontractor
|
Indagon
|
IVS vendor
|
subcontractor
|
Digia
|
PSAP software developer
|
subcontractor
|
Elisa
|
MNO flag tests
|
No (National associated partner)
|
Sonera
|
MNO flag tests
|
No (National associated partner)
|
FICORA
|
MNO authority
|
No (National associated partner)
|
Traffic Safety Agency
|
VIN
|
No (National associated partner)
|
Siemens
|
PSAP software vendor (ELS system)
|
No
| 2>
Share with your friends: |