Version number: Version 4 Main author
Download 387.63 Kb.
|
- Navigate this page:
- 3.2.1.1eCall project architectural overview
- 3.2.1.2PSAP testing platform integrates
- 3.2.2 Involved parties
- 3.3.1.2eCall pilot system architecture overview
- 3.3.1.2.1eCall client simulator (IVS)
- 3.3.1.2.2eCall test bed
- 3.3.1.2.3eCall pilot system control and administrator’s UI
- 3.3.1.2.4eCall clients to be used in the tests, first phase requirements
- 3.3.1.3eCall IVS systems
- 3.3.1.3.2Indagon / www.indagon.fi
3.2Czech Republic3.2.1Short descriptionHeERO pilot project in Czech Republic will test IVS from two vendors - Sherlog Trace and Telematix. ECall is transmitted through Telefónica Mobile Network specially adjusted by eCall Flag functionality and eCall reception will be realised in the PSAP “testing platform” which truly simulates the PSAP 112 operating system and is usually used for the new PSAP SW / functions verification. TPS interface as well as data flow towards Traffic management system will be tested. 
Figure : eCall Pilot Site Architecture (Czech Republic) 3.2.1.1eCall project architectural overvieweCall will be in general routed to the appropriate PSAP based on caller location at the time of emergency set up activation - origin dependent routing. Basic routing parameter is so called Network Routing Number (NRN). NRN is generated by origin mobile exchange that handle emergency set up of the caller and it corresponds to the region where the caller is located and appropriate PSAP centre should receive and handle the call. During HeERO project eCall will be routed via mobile and fixed network to the local exchange, where the PSAP testing platform is connected via ISDN 30 link. NRN will be in the future also used by PSAP CCD (Call Centre Distribution) part for automatic call distribution to the call taker in respective region. eCall solution will be integrated to the existing system for reception and handling of E112 in Czech Republic. 3.2.1.2PSAP testing platform integrates:
The PSAP eCall modem is a component designed to be one element of the PSAP system. It is an Application Server (AS) designed to be integrated into the Alcatel SIP Network and run on a Linux platform. This component is connected to the PABX via SIP Trunk. External calls received from IVS through the PSTN network are routed to this external AS. The PABX forwards the call and, if required, converts the voice format using its interval media gateway. The eCall modem accepts incoming calls only in G711 codec format. As soon as the RTP channel is started, an eCall voice dialog with the IVS system starts. The normal issue is the reception of a 140 bytes data frame of MSD. When this reception is OK, the eCall modem initiates a dialog with an external component named CCIVR. The role of the CCIVR is to attach the received data to the call using the Genesys 'Attach Data' concept and routes the call to the agent group – pilot CCD. When operator takes the call, its call taker application is in charge to get attached data – all information provided in the MSD. Then the operator is in audio communication with the occupants of the vehicle. Application superstructure – Call Taker application of Vitkovice IT Solutions, is responsible for:
Functional modules:
3.2.2Involved parties3.3Finland3.3.1Short description3.3.1.1IntroductionFinland 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. 3.3.1.2eCall pilot system architecture overviewFinnish 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 : Pilot System Architecture The main parts of the system include:
3.3.1.2.1eCall 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). 3.3.1.2.2eCall test bedThe 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.
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. 3.3.1.2.4eCall clients to be used in the tests, first phase requirementsThe 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:
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. 3.3.1.3eCall IVS systemsAt least two different domestic IVS prototypes will be tested, and probably couple of foreign. 3.3.1.3.1Gecko systems / www.geckosystems.fiSystem 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
3.3.1.3.2Indagon / www.indagon.fiIndagon 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 : Indagon MTT 130 IVS 3.3.2Involved partiesTable : Involved Parties (Finland)
Directory: docs -> projects -> cnect docs -> From Warfighters to Crimefighters: The Origins of Domestic Police Militarization docs -> Borzoi Club of America Register of Merit Program I. What is a Register Of Merit docs -> Protecting the rights of the child in the context of migration docs -> United Nations E/C. 12/Esp/5 docs -> 9th May 1950 the schuman declaration docs -> Getting To Outcomes® in Services for Homeless Veterans 10 Steps for Achieving Accountability cnect -> Version number: Version 0 Final cnect -> Project acronym: oversee project title: Open Vehicular Secure Platform cnect -> 1 Pilot operation preparation report Version number Download 387.63 Kb. Share with your friends:
|