CORE ARCHITECTURE GROUP

The Core Architecture Group (CAG) provides central technical coordination and synthesis for the entire CVIS IP. The CAG acts both as a technical project in producing the overall architecture common to all technology and application sub-projects, and also as an IP coordination mechanism for integrating and synchronising the different activities into a coherent work programme.

Objectives

Proposing the methodology and templates to be followed in all work packages across all sub-projects, ensuring consistency across the different sub-projects as well as a seamless transition between work packages
Developing the overall high-level system architecture with which all sub-project architectures must be compliant
Consolidating the sub-project level results and deliverables into IP level results and deliverables
Maintaining a consistent technical approach, and ensuring consistent technical implementation of specifications, across all sub-projects
Realising internal synergy effects by coordinating the work of the sub-project Workpackage Managers
Monitoring progress: each sub-project will have a “godfather” within the CAG who will peer review deliverables and help monitor progress

Key Concepts

The technical development of the CVIS project will work towards a comprehensive and integrated platform that supports cooperative applications. This platform can be configured in a version that is optimised for the in-vehicle environment and a version that is optimised for the roadside infrastructure environment. Each version can be further optimised to allow a light or full deployment depending on platform and cost constraints. The platform will be specified and implemented as an open design that can easily be ported into commercial products.

Benefits of cooperative applications could be analysed or simulated in theory, but bringing them "on the road" requires a suitable set of basic services that provides exactly the seamless and location aware, high definition communication links that are a mandatory requirement for cooperation in the first place! The CVIS platform will be specified and implemented as an open design in a pre-competitive environment that provides for a high level of interoperability during the project, and an easy integration into OEM platforms for commercialisation afterwards.

The CVIS platform that allows to bring cooperative services "on the road", is called the "reference execution platform", comprising components that work closely together and that have been developed and implemented by one of the following technical subprojects:

COMM for components for communication and networking;

FOAM for the open framework for the development, deployment, provisioning and management of end-to-end road management and transport safety applications;

POMA for components for the positioning, map update, location referencing and dynamic local maps of current driving conditions;

COMO for the components for hybridised probe-vehicle and infrastructure-based monitoring data collection, access and fusion

To the top

Main results

Demonstrate the full interoperability of CVIS on-board units (OBU) across vehicles from different suppliers, and between vehicles and roadside equipment of different suppliers
Development of generic open source interfaces and modules for the cooperative exchange of data between vehicles and infrastructure (V2I)
Create open reference platform with pluggable communication interfaces with IPv6 mobile routeing capability
Show that CVIS equipment and services are accepted by the general public as future customers, and that the different applications are perceived by users as providing positive value
Show that a majority of end users of CVIS systems are willing to allow the use of data collected from their vehicle and journey, as input to cooperative monitoring services
Show that users are willing and likely to adopt cooperative driving and travel behaviour in order to realise benefits themselves

Key events and Milestones

Milestone ref. Milestone Planned date

M.CVIS.3 Reference architecture 5

M.CVIS.4 Consolidated system requirements 8

M.CVIS.5 Requirements workshop 9

M.CVIS.6 High-level architecture 11

M.CVIS.7 Architecture workshop 16

M.CVIS.8 Architecture and system specifications 17

M.CVIS.9 Alpha tested components (core technology, CALM) 18

MM.CVIS.10 Validation plan 18

M.CVIS.11 Draft Plan for using and disseminating knowledge 18

M.CVIS.12 Alpha tested components (core technology, non-CALM) 22-24

M.CVIS.13 Beta-tested core technology components 28

M.CVIS.14 Gamma-tested integrated prototypes (with application components) 33

M.CVIS.15 Test bed description 34

M.CVIS.16 Field trial site integration completed 36

M.CVIS.17 Field trial site data collection completed 40

M.CVIS.18 Validation results 46

M.CVIS.19 Validation workshop 46

M.CVIS.20 Final system requirements 48

M.CVIS.21 Final architecture and system specifications 48

M.CVIS.22 Final plan for using and disseminating knowledge 48

M.CVIS.23 IP Final report 48

M.CAG.1 Final Report 46