~~NOTOC~~ ====== CVIS: The Collaborative Vehicle Infrastructure System ====== CVIS (Collaborative Vehicle Infrastructure system) is an European project aiming at developing an Intelligent Co-operative System based on Vehicle-to-Vehicle (V2V) and Vehicle to Infrastructure (V2I) communications. ===== Overview ===== The CVIS system has the following objectives: * To create a unified technical solution allowing all Vehicles and infrastructure elements to communicate with each other in a continuous and transparent way using a variety of media and with enhanced localization; * To enable a wide range of potential cooperative services to run on an open application framework in the Vehicle and roadside equipment; * To define and validate an open architecture and system concept for a number of cooperative system applications, and develop common core components to support cooperation models in real-life applications and services for drivers, operators, industry and other key stakeholders; * To address issues such as user acceptance, data privacy and security, system openness and inter-operability, risk and liability, public policy needs, cost/benefit and business models, and roll-out plans for implementation. ===== CVIS subsystems ===== The CVIS framework is composed of three types of CVIS subsystems: Vehicle subsystems, Road-Side subsystems and Central subsystems. The Central subsystem is the back-end infrastructure that a service provider uses to serve applications and interact with remote entities in Vehicle and roadside subsystems. Control center, Traffic management center, application management center and content center are examples of CVIS Central subsystems. The Central subsystem consist of the collection of equipment, software and operators that achieves the center's function in the global CVIS system. The computing infrastructure in Central CVIS subsystems is the same and consists of a host computer where the applications are deployed, a GATEWAY that acts as interface between external data resources such as authority databases, sensors, etc, and applications deployed by the Central CVIS subsystem. And a border ROUTER provides Internet connectivity to the whole computing infrastructure in the Central CVIS subsystem's ingress network. The Vehicle CVIS subsystem is the the networking and computing facilities on-board Vehicles that are part of the CVIS system. It enables Vehicle-to-Vehicle and Vehicle-to-Infrastructure communication and collaborative applications. The Vehicle subsystem allows interaction with on board sensors and actuators through a GATEWAY unit. A HOST unit runs applications and, a ROUTER unit is in charge of assuring network connectivity to the ingress network. The ROUTER may implement the network mobility protocol (NEMO)[rfc3963] for providing session continuity to mobile network nodes. For this purpose, the mobile ROUTER uses a Home Agent managed by a Mobility Service Provider (MSP) that can be seen as a Central CVIS subsystem. {{technotes:v-cvis.jpg?450|}} The Road-Side CVIS subsystem, as its name implies, is is the computing and communication facilities that are responsible for road side CVIS services (Traffic Signaling, Alarms, Internet Access, etc.). It comprises a HOST unit where CVIS applications are deployed, a GATEWAY through which the HOST and other entities can access sensors and actuators deployed on the road-side (Traffic lights, Cameras, etc.). The roadside subsystem has permanent Internet connection through a Border ROUTER. An Access ROUTER on the roadside CVIS subsystem allows Vehicle CVIS subsystems and other mobile units to connect to the Internet and reach central CVIS subsystems or other Internet locations. {{technotes:r-cvis.jpg?450|}} Several communication media may be used in the ingress network. At least wireless 802.11 and wired Ethernet communication should be supported. Details on this and on CVIS to CVIS communication will be covered in a future article. ===== Links ===== * http://www.cvisproject.org {{tag>wireless embedded}} ~~DISCUSSION~~