WP 2.3 Status Review Preliminary architecture and technical feasibility 5/11/2009 Dublin, Ireland GNSS for INnovative Road Applications

06/10/2015Page 2WP2.3 STATUS REVIEW PARTIES INVOLVED

GNSS for Innovative road Applications Company’s logo 06/10/2015Page 3WP2.3 STATUS REVIEW 1.D2.3 Focused on several objectives: 1.The assessment of the technical feasibility of the proposed applications (RUC, VAS, PAYD, traffic information generation, modeling and provision) 2.The definition of the architecture to provide said services 3.The assessment of the required changes on the currently available platforms 4.The definition of the interfaces among the selected elements 2.The analysis was carried out at two different levels: 1.Ideal system 2.Gina demonstrator 1. End to end 2. Exhaustive trials WP 2.3 Work Overview

GNSS for Innovative road Applications Company’s logo 06/10/2015Page 4WP2.3 STATUS REVIEW 1.Sumer break implied a late start of the WP 2.3 activities 1. This was partially taken into account when preparing the schedule 2.Requirements analysis was successfully performed 3.Requirements have been compared with the different modules capabilities 4.Overall architecture definition complete with a slight delay 1. Depended on the definition of some interfaces 2. Depended on which VAS were going to be implemented 5.Analysis of adaptations required complete 6.Discusion of the interfaces among the different elements complete 7.Final report compilation with a slight delay that left little time for internal review 8.Final draft version provided for the MTR WP 2.3 Work Status Overview

GNSS for Innovative road Applications Company’s logo 06/10/2015Page 5WP2.3 STATUS REVIEW 1.Current position in schedule (+3 days): REVIEW OF CURRENT STATUS

GNSS for Innovative road Applications Company’s logo 06/10/2015Page 6WP2.3 STATUS REVIEW 1.Task Plan (Delivered: 20/07/09) 2.Final Report Structure (Delivered: 20/07/09) 3.Preliminary analysis of VAS requirements (Delivered: 27/08/09) 4.Preliminary VAS platform architecture (Delivered: 07/09/09) 5.Final VAS requirements and architecture (Delivered: 23/10/09) 6.Final Data Analysis HUB (Delivered: 26/10/09) 7.Final Draft Deliverable version (Delivered: 05/11/09) DELIVERED ITEMS

RESULTS OF ACTIVITIES FOR DEFINITION OF ARCHITECTURE WP 2.3: Preliminary architecture and technical feasibility

GNSS for Innovative road Applications Company’s logo 06/10/2015Page 8WP2.3 STATUS REVIEW 1.Generic RUC platform: RESULTS OF ACTIVITIES FOR DEFINITION OF ARCHITECTURE

GNSS for Innovative road Applications Company’s logo 06/10/2015Page 9WP2.3 STATUS REVIEW 1.Overall GINA Architecture: RESULTS OF ACTIVITIES FOR DEFINITION OF ARCHITECTURE

GNSS for Innovative road Applications Company’s logo 06/10/2015Page 10WP2.3 STATUS REVIEW Low Cost On-Board Equipment –“Smart-Obu” –Advanced GPS-GPRS functionalities –Carries out Positioning calculations –Provides current GeoObject, time and Integrity information Supports multiple services –Will anonymize PVT information where required for VAS –Will only send non PVT data linked to the identity –eCALL, Fleet Management, PAYD, Accident reconstruction, remote diagnosis, Real-time traffic info, stolen vehicle location & recovery, ETC, ‘green-journey’ determination… Can be configured in several ways –With or without SISNeT –With or without CAN bus connection Several configurations will be tested in post- process during the exhaustive trials CAN Bus connection has liability issues which may void the vehicle guarantee –Some vehicles may be fitted with the CAN bus connection under full responsibility of the end user OBUs

GNSS for Innovative road Applications Company’s logo OBU Architecture 06/10/2015Page 11WP2.3 STATUS REVIEW Navigation manager: Manages the GPS module and the EDAS/SISNeT connection Extracts the info related to Lat, Long, speed and forwards it to other modules Communications manager: Establishes & monitors the GPRS link Local Storage Manager: Generates Log and/or raw data files while the system is working Watchdog Manager: Monitors OBU power source and system correct performance Triggers alarm messages for OBU different failures External Interfaces Manager: Collects data from the different OBU external interfaces

GNSS for Innovative road Applications Company’s logo OBU Architecture (II) 06/10/2015Page 12WP2.3 STATUS REVIEW Geo-Objects Manager: Keeps the tariff structure information Calculates the distance, speed and time within each geo-object Updates geo-object information Reports the data periodically Enforcement Manager Verifies compliance requests against the vehicle identity Verifies the position of the OBU against the compliance request Handles responses to the enforcement system System Core Manager: Start/Stop OBU different modules Gathers information from the different modules Performs Data Fusion of the different info Parse Outgoing messages (e.g. into XML) GINA defined code for specific operations and tasks

GNSS for Innovative road Applications Company’s logo Changes Required in the OBU 06/10/2015Page 13WP2.3 STATUS REVIEW Currently configured to send PVT data periodically to the CI –Not compliant with the ABvM privacy requirements Can only send aggregated data to the CI –Shall perform the geo-object usage calculations –New data types to accomodate for the tariff structure –New Geo-object types –Interface adaptations to update/change the tariff structure

GNSS for Innovative road Applications Company’s logo Toll Service Provider Platform 06/10/2015Page 14WP2.3 STATUS REVIEW Logical Structure of the platform –Middleware handles access to OBUs –Technical layer performs data fusion of the information coming from the OBUs –Technical layer provides access to the data to the core services Aggregated Geo data OBU information reports –Information provided by the core services is available through a Web Services interface Can be processed and formatted to provide added value services

GNSS for Innovative road Applications Company’s logo 06/10/2015Page 15WP2.3 STATUS REVIEW Palview GINA Platform: –Middleware + Back-end + RUC Module –Information provision to other modules –Information Storage –OBE Remote configuration –Communication with the OBUs –OBU software update –Secure access management –Standard Interfaces to VSPs through web services –Tariff information and payment generation –Graphical User Interface –Report and data analysis generation –OBE Remote configuration Toll Service Provider Platform

GNSS for Innovative road Applications Company’s logo 06/10/2015Page 16WP2.3 STATUS REVIEW Palview ® is composed by a Core Infrastructure which gives flexibility for supporting different services –Interface between equipments and Services Providers –Responsible of collecting, processing and centralising location-based information –Guarantees Data Privacy to users Palview ® Main Modules Communications Mngt Database Mngt Cartography/Maps Mngt Administration/Control module Equipment Diagnosis module (incl. Automatic FW updating) Acting as a “LBS-Middleware”: no functionality is directly offered to the final users No PVT information will be retrieved by the system, only reporting for RUC and additional services PALVIEW ARCHITECTURE

GNSS for Innovative road Applications Company’s logo 06/10/2015Page 17WP2.3 STATUS REVIEW Application Manager –Administration of equipment configurations. –Control of equipment software updates. –Administration of automatic system tasks, for example, automatic dumps, anti-theft, etc Equipment (OBU) communications module –Translates between the OBU and the CI data formats Data Storage module –stores all the logs received from the mobile equipment in the database including: Usage of geo-objects by type and hour Km travelled by geo-object type and hour Bytes transferred during communications with the mobile equipment by the mobile equipment. Reports module –Generates reports from the logs on the database GEO (Geographic Object) module –Manages the tariff structure, pricing and timing –Updates the information in the OBUs Web Service API –platform access interface CORE INFRASTRUCTURE (Palview)

GNSS for Innovative road Applications Company’s logo 06/10/2015Page 18WP2.3 STATUS REVIEW CI interface –Web service based interface with the CI Billing module –Get the charge-object usage information from the core platform –Classify the information about the geo-objects usage per OBU –Associate the OBU information with the vehicle where the vehicle is installed –Apply the tariffs in effect in the moment that the usage was incurred: Per km travelled By area/specific road/road class By time of the day/day of the week By vehicle class Add additional fixed charges for crossing cordons/boundaries/gantries –Store the information back in the CI Web interface (CRM) –Manage the security of the online access –Access to the end-user information –Update personal information –Update accounting information –Manage the vehicles of an account –Modify the association between vehicles and OBUs on their account RUC Module (Palview)

GNSS for Innovative road Applications Company’s logo Changes Required in the CI Interfaces adaptation to new modules –New Web Services Development Inclusion of Pricing and Tariff Structure Management of geographical information –Aggregated or anonymised to comply with ABvM privacy requirements –Modification of tariff structure uploaded to the OBUs New Reports to be implemented –To suit Data Analysis requirements –To fulfill VSPs requirements Development of the RUC module –Customized user interface for the GINA project –Front-end pricing information calculation 06/10/2015Page 19PRESENTATION TITLE VERDANA (9)

GNSS for Innovative road Applications Company’s logo SERVICE CENTRE (RITA) –Collect and store traffic data Data used for shadow tolling Several traffic indicators: – Traffic Volume – Average speed – Occupation – Intensity – Density –Support for traffic management Fault detection (road equipment faults) Alarm detection – Automatic incident detection – Meteorology – Tunnel events (smoke, fire, CO2 levels, …) Road management Audit management Incident management 06/10/2015Page 20WP2.3 STATUS REVIEW

GNSS for Innovative road Applications Company’s logo SERVICE CENTRE (RITA) 06/10/2015Page 21WP2.3 STATUS REVIEW

GNSS for Innovative road Applications Company’s logo RITA ARCHITECTURE Data Access Layer –RITA –RITA Reports –RITA Reports DW –The GIS DB is quite different, as it is stored in.MXD files used directly by the ArcGIS engine and represent the entire concession roads and equipments. RITA Reports –Data Import Service –Reports Provider (Microsoft Reporting Services) – HTTP access – Export reports in several formats (excel, pdf, …) – RITA server independent – Easily replacable by another reports tool without changing the system arquitecture 06/10/2015Page 22WP2.3 STATUS REVIEW

GNSS for Innovative road Applications Company’s logo RITA ARCHITECTURE User Interface –Multilanguage support –Access based on user profile Divided into 5 components: –Equipment consoles maintenance, general equipament control –Operator Terminal Gives controlled access to all RITA funcionalities –Roap Map GIS map implementation –Video Viewer Up to 4 simultaneous camera views –Tunnel UI 06/10/2015Page 23WP 2.3 STATUS REVIEW

GNSS for Innovative road Applications Company’s logo Value Added Services Pay as You Drive Charging Scheme Tracking of Fleet Vehicles –Display Vehicles Position –Incident Response Time –Validation of Contractual Obligations 06/10/2015Page 24WP2.3 STATUS REVIEW

GNSS for Innovative road Applications Company’s logo Value Added Services Overall Architecture –Equipments Layer Moviloc ANPR –Server Layer Drivers Services Broker –UI Layer Operator UI Reports 06/10/2015Page 25WP2.3 STATUS REVIEW

GNSS for Innovative road Applications Company’s logo Value Added Services OBU Handler Architecture –Information enters the system by a driver and service –Information is handled by the VAS Manager in RITA 06/10/2015Page 26WP2.3 STATUS REVIEW

GNSS for Innovative road Applications Company’s logo Value Added Services VAS Handler Architecture –Data has 2 paths PAYD Data Tracking Data –PAYD data can be processed in batch (end of day) –Tracking Data has a real-time meaning 06/10/2015Page 27WP2.3 STATUS REVIEW

GNSS for Innovative road Applications Company’s logo Enforcement Detects anomalies on the Vehicles OBUs –ANPR Solution for enforcement –A Vehicle is Detected by ANPR solution -> Central System Validates detection with OBU on the vehicle 06/10/2015Page 28WP2.3 STATUS REVIEW

GNSS for Innovative road Applications Company’s logo Enforcement Architecture Overall Architecture –Equipments Layer Moviloc ANPR –Server Layer Drivers Services Broker –UI Layer Operator UI Reports 06/10/2015Page 29WP2.3 STATUS REVIEW

GNSS for Innovative road Applications Company’s logo Enforcement Architecture ANPR Handler Architecture –Information enters the system by a driver and service –Information is handled by the enforcement handler in RITA 06/10/2015Page 30WP2.3 STATUS REVIEW

GNSS for Innovative road Applications Company’s logo Enforcement Architecture OBU Handler Architecture –Information enters the system by a driver and service –Information is handled by the enforcement handler in RITA 06/10/2015Page 31WP2.3 STATUS REVIEW

GNSS for Innovative road Applications Company’s logo Enforcement Architecture Enforcement Handler Architecture –Receives data from ANPR and OBU –Checks enforcement rules –Publishes results 06/10/2015Page 32WP2.3 STATUS REVIEW

GNSS for Innovative road Applications Company’s logo 06/10/2015Page 33WP2.3 STATUS REVIEW 1.The comunication channel among the obus and the main infrastructure will be done by GPRS/UMTS 2.Reports will be send daily for each vehicle with only the RUC data (smart OBU) 1. This optimizes bandwidth and server usage 3.For Tracking Data the position is sent, at smaller intervals (30seconds) 1. Needs Special users authorization 4.Communication among other elements will be through a secure internet access COMMUNICATIONS

GNSS for Innovative road Applications Company’s logo 06/10/2015Page 34WP2.3 STATUS REVIEW 1.Two reference systems will be used for the exhaustive trials 1. A trajectography + DGPS positioning system provided by GMV 2. A precise receiver providing matching against geo-objects provided by NavTeq 2.The summary of the information collected by the reference equipment was sent to TRL on 08/09/09 1. Position 2. Protection levels 3. Current GeoObject 4. Etc. REFERENCE SYSTEM

GNSS for Innovative road Applications Company’s logo 06/10/2015Page 35WP2.3 STATUS REVIEW DATA ANALYSIS HUB Two Types of Analysis –Exhaustive: Comparing system behavior against known truth –Usage (end-to-end) : Recording usage over time and geography to determine driver behavior Both objectives can be met using the following sample statistics produced by the HUB on a per journey basis Data Analysis platform: –Road Network, Charge Object and Route Data stored in the HUB database. –Information about vehicle, driver and journeys travelled retrieved and stored –The OBU uploads data at an agreed interval to the file system –The HUB services framework monitors for new files and processes them –The HUB services saves the results into the database. –Reporting and statistical analysis tools (e.g. R and BIRT) are used to aggregate the data –The HUB web GUI allows for the dissemination of the analysis

GNSS for Innovative road Applications Company’s logo DATA ANALYSIS HUB Key Elements : –OBUs Provide usage data –Reference system Provides truth data –File System Accepts and stores data files from the devices –Workflow Decides based on the file type the type of data in use (vehicle position, road usage, charge object usage) and forwards it to the relevant processor –Vehicle Position Processor Processes the cross-track and absolute error calculations against the reference device for statistical analysis. –Road Usage Processor Processes the road/segment usage data against underlying truth data as represented by an ordered list of road segments. –Charge Object Usage Processor Uploads the charge object usage data into the database. –HUB Database Stores the results from the processors and the relational representation of the underlying vector mapping. –HUB Web GUI Presents the results of the HUB analysis component. –HUB Analysis Uses open source technologies, e.g. BIRT, R, in order to output stats on the performance of the system in relation to the data processed against truth data. 06/10/2015Page 36WP2.3 STATUS REVIEW

GNSS for Innovative road Applications Company’s logo 06/10/2015Page 37WP2.3 STATUS REVIEW 1.HUB Sample Web Implementation DATA ANALYSIS HUB

GNSS for Innovative road Applications Company’s logo 06/10/2015Page 38WP2.3 STATUS REVIEW 1. Analysis of requirements complete 2.Overall architecture definition complete 3.Interface definition complete 4.Final Draft Delivered 1.Feedback and comments will be incorporated to the draft 5.First feedback by consortium members being integrated in the document 1.Core Infrastructure architecture revision 2.GNSS signal Spoofing discussion to be included in the deliverable DELIVERABLE STATUS

GNSS for Innovative road Applications Company’s logo 06/10/2015Page 39WP2.3 STATUS REVIEW 1.Strict Dutch ABvM privacy requirements 1. Hinders most VAS implementation 2. Hinders enforcement implementation 1.Searching for alternative implementations 2.Interdependance with trial definition 1. Not relevant for final platform 2. Necessary for the demonstrator platform definition 3.Late release of contributions 1. Delayed integration and review process MAIN OBSTACLES

Thank you