CVIS

1
CVIS

• Knut Evensen
• CVIS Chief Architect

2
European RD projects supported by DG INFSO

• Coordinator ERTICO
• Total budget 41 Million
• Consortium 61 partners - 12 countries
• Focus Efficiency V2R services

• Coordinator Fiat Research Centre
• Total budget 38 Million
• Consortium 51 partners - 12 countries
• Focus Safety V2V low latency

• Coordinator Austria tech
• Total budget 16,8 Million
• Consortium 37 partners - 14 countries
• Focus Roadside / Infrastructure

• Co-operating projects also includes SEVECOM,
  COMeSafety, Car-2-Car Communications Consortium
  (C2C-CC), Network on Wheels (NoW), INVENT, ACTIV
  (Germany), CVHS (UK), IVSS (Sweden)

3
CVIS Partners
4
CVIS Project Overview
5
Two unique Features in CVIS

• One common OPEN platform
• Platform is a peer - peer network

6
CVIS Top-level Architecture
7
View Service Architecture
8
CVIS layered architecture


Dangerous Goods
Enhanced Driver Awareness
Coop Area Routing
Applications
Dynamic Bus Lane
Coop Network Mngt.
Travelers Assistance
Coop Traffic Control
Parking Reservation
Access Control
Coop Monitoring
Basic Application Facilities

Domain Facilities
Application Facilities (FOAM, COMO, COMM, POMA)
Data Fusion
(GST) Payment
Directory DDS
HMI
HMCA
Lifecycle
Native Interface
Data Subscribe
Time Position
Local (D) Map
Security
Comms CALM API
Data Tree
Runtime environment (OSGi based)
Middleware
Native / Real-time applications
Platform Core Functions
Computer Hardware and Operating System
9
View Communication Architecture
10
Communications Architecture
GPS
UMTS
M5 IR
The generic Comm Architecture is CALM-based
11
CALM implementation in CVIS
12
View CoreTech Platform Architecture
13
CVIS Vehicle Platform
Antenna
14
Equipment example RSU
15
Equipment example OBU
16
CoreTech timeline (Feb 2007)
CAG
CAG
CAG
CAG
a-developments
b - integration
g - car roadside adaptation
CALM M5 DSRC
GSM/GPRS
IR
CALM M5 DSRC
GSM/GPRS
IR
CALM M5 DSRC
GSM/GPRS
IR
Acceptance testing without applications
Acceptance testing with applications
Acceptance testing Car roadside
Acceptance testing
Router platform
Router platform
Router platform
b test bed
g test bed
Host platform
a test beds
VALIDATION
Validation plan
17
Test Applications
18
CVIS Scenarios
19
CVIS Scenarios
20
5GHz Technology
21
Standardisation at ETSI TC ITShttp//www.etsi.
org
ETSI TC ITS
Soeren Hess (Daimler AG)

ManagementCommittee
WG1User ApplicationRequirements GerardSegar
ra (Renault)
WG2Architecture and Cross Layer Knut
Evensen (Q-Free)
WG3TransportandNetwork Andreas Festag (NEC)
WG4Mediaand Mediumrelated ThomasWeber(BMWi)
WG5Security Scott Cadzow (Cadzow Comm.)
Applications
FrequencyAllocation
22
ITS Spectrum
ITS
Broadband Radio Access (BRAN)
CEN DSRC
V2V (ISM band)
V2R restricted emission
SCH V2R - restricted
SCH GeoRoute Multihop
CCH
Aux channel R2V
Common Control Channel, Broadcast data,
10MHz_at_5900 (ch180) (Used by all)
Service Channel GeoRoute multihopping,
10MHz_at_5880 (ch176) (Safespot/C2C-CC)
Aux Channel for roadside initiated data, 20MHz
_at_5480 (ch96) (CVIS/COOPERS)
Vehicle-Roadside data, 10MHz_at_5890 (ch178)
(Safespot/C2C-CC, not used initially)
NOTE Channel use only valid for test period!
Blue line represent European spectrum mask for
BRAN (conditional use for ITS) Red line
represents European spectrum mask for ITS 5.9
23
CVIS CALM M5 Radio

• Two miniPCI European Atheros radios
• Modified version compared to (most) US tests
• Additionaly includes
• Synchronization to European DSRC Toll Collection
  systems according to ETSI requirements Dont
  go without this even for tests!
• European 5.9GHz spectrum plus 802.11abg
• GPS time-slot sync for performance optimization
• Full P1609.4 stack (US operation compatible)
• Full CALM management for parallel stacks
• Open access to APIs and SAPs, both native code
  LINUX and OSGi/GST based portable services

24
CALM M5 IPv6, C2C-CC WAVE
Geoaddressed applications (e.g. active safety)
IP Applications (Deployment)
WAVE Short Message Apps
TCP / UDP
WSMP
IPv6
B
C2C-CC Network Layer
C
A
B
LLC/MAC (IEEE 802.11p)
C2C MAC
P1609.4
PHY (IEEE 802.11p)
25
Simplified Architecture for SAFESPOT CVIS
Geoaddressed applications (e.g. active safety)
Non-IP Applications
IP Applications
CVIS Middleware Non-IP IPv6
LDM
CVIS protocolFAST 29281Connection-orientedmessa
ges
Broadcast Manager
A
C
B
Radio 1
Radio 2
CCH 5.9 GHz
SCH 5.9 GHz (5.4 GHz)
26
Broadcast scenario
Host A JAVA
Host B Native
Host C LDM
Management !
Router
Broadcast pool
Data x, Pri, TimeData y, Pri, TimeData z, Pri,
Time
AID1, (data), IPport AID2, (data), IPport
AID2, (data), IPport
AID6, (data), LocAdrAID6, (data), LocAdr AID7,
(data), LocAdr

• Congestion Redux Strategy
• Reduce data content
• Reduce TX Power
• Reduce repetition rate

Broadcast frame
ID, Time, Position, Multihop Indicator , Data
Payload , FAST services , IPv6 Services
27
Cooperative efforts

• CVIS is cooperating very closely with SAFESPOT on
  the LDM concept
• There is also a cooperation for common
  demonstrators lead by COMeSafety with COOPERS,
  SAFESPOT and CVIS participating.

28
Copy from Abdel Kader Mokaddem - Renault
29
Copy from Abdel Kader Mokaddem - Renault
30
New European Architecture
31
COMeSafety coordination
Political, Social and Economic Interests
European Projects
Harmonization
Standardisation
Convening Stimulation Moderation Editoring Dissemi
nation
ETSI
CEN
Specifications
Group of Experts
IEEE
ITU
Etc.
Combination Clarification
ISO
C2C-CC
IETF
32
Numerous Systems and Standards are under
Construction

• A variety of EU and national projects elaborate
• Protocol Architectures,
• System Architectures,
• High-Level Architectures .......
• Do we really need yet another Communication -
  Architecture ?

Yes, because a comprehensive framework is needed
to enable individually developed components to
cooperate easily
Source Timo Kosch, BMW
33
European Cooperative Systems Architecture

• Draft out for comment now
• Final editorial meeting 18 Sept
• Open release shortly afterwards
• See www.comesafety.org

34

• Proposed European ITS Communication Architecture
• Joint development
• ETSI TC ITS
• COMeSafety RD projects

35
Deployment Architecture Scenarios
36
Vehicle Station
Single box implementationOften called On-Board
Unit
37
Vehicle Station
Mobile Router
Mobile Host
38
Vehicle Station
Mobile Router
Mobile Host
Mobile Gateway
ECU
ECU
39
Roadside Station
Roadside Host
Roadside Gateway
Access Router
Border Router
IPv6 Internet (Tunneled)
40
Access Router
Border Router
IPv6 Internet (Tunneled)
41
Mobile Station
42
Central ITS Station
Central System
Central Host
Central Gateway
Border Router
IPv6 Internet (Tunneled)
43
Handheld/Nomadic/Mobile Station
Central Station
Central ITS Station
Central
Central
Host
Gateway
Border
Router
Central System
IPv6 Internet (Tunneled)
Vehicle Station
Roadside Station
Roadside Station
VMS
VMS
5.9
5.9
Roadside
Roadside
Host
Gateway
Access
Border
Router
Router
SENS
Ctrl
SENS
Ctrl
44
Handheld/Nomadic/Mobile Station 1
Handheld/Nomadic/Mobile Station 2
Ad-hoc network
Vehicle Station 1
Vehicle Station 2
45
Summary

• CVIS provides essential input to the European ITS
  architecture development and standardisation
  effort
• CVIS platform is being extended to include
  SAFESPOT car2car functions for simultaneous
  safety/efficiency service
• Please get in contact to see how you could
  partake in the CVIS platform

46
Proposal

• The idea is to take the set of overlapping
  standards from ISO, IEEE, ETSI and IETF, and
  develop them into a set of standards that are not
  overlapping but still complete ( mutually
  exclusive and collectively exhaustive).
• To achieve this, the meeting proposes the
  following
• The ITS Station Reference Architecture shown
  above and presented by Knut Evensen, should be
  generally accepted as the common reference
  architecture and form the basis for the standards
  consolidation.
• The next task is to decide on who takes the lead
  to develop and maintain the various technical
  standards, e.g. security, radio interfaces,
  geo-referenced protocols.
• One example The revision of the current ETSI,
  ISO and IEEE standards relevant to P1609, will be
  accomplished in an open, joint cooperation
  between ETSI, IEEE and ISO where relevant
  requirements from ISO and ETSI amend and extend
  P1609. Relevant ISO standards, e.g. ISO 21215,
  21217, 24102, 29281, should reference IEEE
  802.11p and P1609 where relevant and vice versa.

47
Way forward
48
Thanks for your attention
Knut Evensen knut.evensen_at_q-free.com www.cvisproj
ect.org