its communication architectures: the road towards ipv6 · system management entity (cme) iso...

Thierry Ernst – IPv6 & ITS architectures – VNC Tokyo – October 2009

ITS Communication Architectures:The Road towards IPv6

1st IEEE Vehicular Networking Conference - Tokyo

[email protected]

LaRA (INRIA IMARA project-team & Ecole des Mines Paris)

http://www.lara.prd.fr

http://www.lara.prd.fr/

Thierry Ernst – IPv6 & ITS architectures – VNC Tokyo – October 2009 2

ITS Vision

Communicating vehicleCommunication scenarios diversity (V2V, V2I, I2V, Internet)Communications diversity (WiFi, WiMax, 3G, Satellite, ...)Application diversity (road safety, road efficiency, infotainment, ...)


ITS Vision: Communications and StandardsWe need standards for uniformized exchange of information

In vehicular cooperative systems (V2X)

And also between cooperative systems and anything on the networkNot only in the automotive sector: People & devices in cars, trains, aircrafts, ships, etc need to communicateNot only for ITS: Interoperability between communication systems developed in all sectors must be ensuredThe Internet of Things

The Internet Protocol (IP) is the de facto standardITS communication architectures must interoperate with it


ITS Vision: Why an IP-based communication architecture ?IP provides an unification layer of underlying technologies

2G/3G, 802.11 a/b/g, 802.11p, 802.16, satellite, ...Any application running over IP is media-agnostic

IP ensures interoperabilityIP everywhere: ITS, education, health-care, armyNot limited to dedicated ITS application End-host running in a vehicle can communicate directly with an end-host running at the car manufacturer's HQ, parking lot, emergency crews, driver's home

IP ensures portabilityOrdinary uses of the Internet can be brought to the vehicle (web browsing, video streaming, peer-to-peer, etc)

IP ensures wider deploymentIP equipments are cheaper to developProducts can be updated constantly (security holes, new features)


ITS: IP address requirementsVehicles are connected to the Internet=> Several IP addresses per vehicle

On-board units (OBU / Router) maintaining Internet access through several medias (3G, 802.11p, ...)Application Units (AU / Host) running ITS applicationsHand-held devices running multimedia applicationsOEM: Gateway between IP and CAN

Number of cars worldwide1997: 600 millions2030: 1200 millions (at present trend)

IPv4 is a non-go for ITS deployment232 = = 4,294,967,296 addressesToo many vehicles for NATLimited mechanisms for IP session continuity


from http://xkcd.com/195/

IPv4 Address Depletion: Remaining unallocated blocks


ITS: Why not IPv4 ?Exhaustion prediction: IANA Dec.2009 - 1st RIR: Aug. 2010

http://www.potaroo.net/tools/ipv4/


ITS: What is IPv6 ?IPv6: Internet Protocol version 6

Designed by the IETF since 1995 as a replacement of IPv4IPv6 is an evolution of IP

128 bits instead of 32 (2128 addresses instead of 232)

New IP headerNew features

Between 1 564 & 3 911 873 538 269 506 102 addresses / m2

An address for everything on the networkFully specified, implemented, operational deployment started

IPv6 comprises new features absolutely needed by ITS architectures, e.g.:

Auto-configurationIP session continuity (NEMO,mobile edge multihoming, etc.)


ISO TC204 WG16: CALMISO Technical Committee 204: Currently 12 active WGs

http://www.iso.org/iso/iso_technical_committee.html?commid=54706

WG 16: Wide Area CommunicationsSince Y 2000 / Led by Russell Shields (Ygomi)CALM: Communication Architecture for Land Mobile

Renamed from Communications Air-interface, Long and Medium rangeDocs:

Web: http://www.calm.huCALM Handbook

7 sub-WGs SWG 16.0: CALM ArchitectureSWG 16.1: CALM MediaSWG 16.2: CALM Network SWG 16.3: Probe DataSWG 16.4: Application ManagementSWG 16.5: Emergency notifications (eCall)SWG 16.6: CALM ad-hoc subsystemSWG 16.6: Security

http://www.iso.org/iso/iso_technical_committee.html?commid=54706

http://www.calm.hu/


ISO TC204 WG16: ISO 21217 - CALM ArchitectureApplication and scenario diversity

Safety, non-safety and infotainment applicationsCommunication architecture allows V2V, V2I and continuous Internet access

Media diversityCellular (CALM 2G/3G) – ISO 21212 & 21213Infrared light (IR) – ISO 21214Microwave (CALM M5 => 802.11p) – ISO 21215Millimeter waves (CALM MM) – ISO 21216Microwaves CEN DSRC

Networking diversityIPv6 (Internet connectivity, mobility management) – ISO 21210Non-IP networking (FAST => time critical applications) – ISO 29281

Medium Selection & SwitchingMedia selection based on availability & application needs – ISO 24102


Single Media (dedicated)Dedicated infrastructure(Tollgate)

Single MediaDedicated infrastructure

IPv6 but no Internet

Single MediaPublic infrastructure (large range)

IPv6 but and InternetNo mobility management

Car-initiated communications

ISO TC204 WG16: Communication Scenarios


Multiple MediaMedia switching and mobility management

Bidirectional communicationsNEMO

IPv6 and multihop

adhoc netwoking

IPv6 Internet and multihop adhoc netwoking

ISO TC204 WG16: Communication Scenarios


ISO TC204 WG16: ISO 21217 - CALM Architecture

CALM ARCHITECTURECALM ARCHITECTURE

- Standards that are outside CALM scope- Standards that are outside CALM scope SAP - Service Access Point –Data Transfer

SAP - Service Access Point –Management

Media Function blocks shown above may be partof a more comprehensive communications device.

2G cellular std by reference

CALM 2G ManagerISO 21212

SAP



SAP

NetworkingManagementISO 21210-3

CALMsystem

ManagementEntity(CME)

ISO 21210-2

NETWORK INTERFACERouting and Media Switching based on IPv6

ISO 21210-1

Non-CALM-awarePoint-to-point APPLICATIONS

Convergence LayerISO 15628/

ISO 21210-5SAP

CALM-AwareAPPLICATIONS

Layer 5-7INTERNET STANDARDS

SAP

SAP SAP

Common Station,PHY, MAC, LLC

Managers ISO 21210-4

SAP

SAP

SAP

SAP

Directory ServicesISO 21210-5 SAP

SAP

Non-CALM-awareIP (Internet)

APPLICATIONS

Convergence LayerIP socket/

ISO 21210-5SAP

SAPSAP

SAP

CALM MM

CALM MM ManagerISO 21216

SAP

CALM MM

CALM MM ManagerISO 21216

SAP

CALM M5

CALM M5 ManagerISO 21215

SAP

CALM M5

CALM M5 ManagerISO 21215

SAP

CALM IR

CALM IR ManagerISO 21214

SAP

CALM IR

CALM IR ManagerISO 21214

SAP



SAP



SAP

In- Vehicle Network

Lower Layers

In-Vehicle NetConvergence

ISO 212??

SAP


ISO TC204 WG16: ISO 21217 - CALM Architecture


ISO TC204 WG16: ISO 21210 - IPv6 NetworkingIPv6 networking

IPv6 suite of protocols & mobility features (NEMO)IPv6 not considered for time critical applications

Roaming requirementsVehicle must be reachable at current location and permanent address

NEMO: IPv6 mobility managementMaintain a permanent address space on board the vehicleMaintain sessions during handovers (horizontal & vertical)Packets are forwarded to the current location of the vehicle

Medium Selection & SwitchingHorizontal handover: between access points using the same mediaVertical handover: heterogeneous handovers Purpose: Continuous communication during handoffSelect the most appropriate media based on application needs


Facilities

Station-ExternalInterfaces

MI-

SA

PIN-SAP

Man

agem

ent

Info

rmat

ion

Ba

se (

MIB

)

Station-InternalInterfaces

ITS Network

IN-SAP

MN

-SA

P

Networking & Transport

Access Technologies (PHY&DLL)

...IPv6 +Mobility

Extensions

NF-SAP

Geo-Routing

MI-

SA

PM

N-S

AP

MF-

SA

P

Ma

na

ge

men

t

Application Support

NF-SAP

MF-

SA

P

ITS Station Reference Architecture

Otherprotocols

e.g.GPS

e.g.2G/3G/...

e.g.BlueTooth

e.g.Ethernet

e.g.5.9GHz

Sec

uri

ty

SI-

SA

P

SI-

SA

P

SN

-SA

P

SN

-SA

P

SF

-SA

P

SF

-SA

P

Sec

urity

Inf

orm

atio

n B

ase

(Id

entit

y, C

rypt

oKe

y an

d C

ert

ifica

te M

anag

men

t)

Session Support

SM-SAP

ITS Transport TCP/UDP

e.g.WiFi

Information Support

ApplicationsTraffic

EfficiencyRoadSafety

OtherApplications

FA-SAP

SA

-SA

P

SA

-SA

P

MA

-SA

P

MA

-SA

P

FA-SAP

SM-SAP

Hardware Security Module (HSM)

Aut

hent

icat

ion,

Aut

horiz

atio

n, P

rofil

e M

anag

eme

nt

Fire

wal

l and

Intru

sion

Man

agem

ent

Cro

ss-I

nte

rfac

e M

anag

emen

tN

etw

orki

ng M

anag

eme

ntS

tatio

n m

anag

eme

nt

Proposed European ITS Communication ArchitectureJoint development:

ETSI TC ITSCOMeSafety+ R&D projects

COMeSafety: ITS Station


COMeSafety: IPv6 Communication Network



Access Technologies

...

Man

agem

ent

5.9GHz

Sec

uri

ty

Ethernet

5.9GHz

Vehicle Station

Facilities


Access Technologies

...Man

agem

ent

Sec

uri

ty

Applications

Ethernet

Mobile Router Mobile Host

COMeSafety: Vehicle Station – In-vehicle network


Coordinator: Fiat Research CentreTotal budget: € 38 MillionConsortium: 51 partners - 12 countriesFocus: Safety – V2V low latency

• Coordinator: Austria tech• Total budget: € 16,8 Million

• Consortium: 37 partners - 14 countries

• Focus: Roadside / Infrastructure

• Coordinator: ERTICO• Total budget: € 41 Million

• Consortium: 61 partners - 12 countries

• Focus: Efficiency – V2R services

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

Car<->Car

CALM: European R&D Projects supported by DG INFSO

Core Technologies

Car<->Infrastructure


CVIS: FP6 Integrated Project (IP)Cooperative Vehicle-Infrastructure System

http://www.cvisproject.orgFrom Feb. 2006 till Feb. 201061 partners / 12 countries / Total Budget: 41 Millions Euros

ObjectivesDevelop, trial & demonstrate

Inter-operable architecture for vehicular communicationsNovel applications for:

Cooperative traffic and road network monitoringCooperative road & traffic network management & controlCooperative logistics & fleet management

Cooperative public transport & intermodality

VisionUse and extend existing standardsProduce open design and softwareOutput intended to be reused by other EC projects

http://www.cvisproject.org/


CVIS: Scenarios


CVIS: Architecture - ITS Subsystems


CVISHost

CVISRouter

Antenna

OEMGateway

SENS

SENS

CtrlCtrl

CVIS: Vehicle ConfigurationIn-vehicle IPv6 subnet

CVIS Router: Mobile Router maintaining Internet Access through several physical interfacesCVIS Host: run dedicated ITS applicationsOEM Gateway: between IPv6 and CAN


VMS 5.9

SENSCtrl


Access Technologies

...

Managem

ent

Ethernet

Securi

ty

IPv6

BorderRouterFacilities


Access Technologies

...

Man

agem

ent

Ethernet

Security

CAN bus

Facilities


Access Technologies

...

Man

agem

ent

Security

Applications

Ethernet

RoadsideHost


Access Technologies

...

Man

agem

ent

5.9GHz

Sec

urity

Ethernet

AccessRouter

IPv6 Internet(Tunneled)

RoadsideGateway

Roadside Station

Roadside IPv6 subnetRoadside Host: Provides services to the vehicleAccess Router: Relays services to the vehicleBorder Router: Provides Internet access to the roadsideRoadside Gateway: between IPv6 and legacy roadside devices

CVIS: Roadside Configuration


Antenna

Mobile Router Mobile Host

Touch Display

CVIS Sensor & M5 cardGyro

Accelero-meter

20chGPS

OBD-IICAN Bus

CEN DSRC

2.5 / 5 GHz 802.11 radiosmodified for:

- Euro 802.11p- DSRC RT sync- GPS time sync

FPGA: PCI, Serial ports & softcore CPURealtime GPS & DSRC sync, sensor fusion/timestamp

CVIS Reference Antenna

GSM/UMTSAntenna

2-6 GHzAntenna 2

2-6 GHzAntenna 1

GPSAntenna

CEN DSRCAntenna

CVIS: Vehicle Platform

http://lilliput.manufacturer.globalsources.com/si/6008801432124/pdtl/LCD-PC/1003557382/7-Inch-Standalone-Car-PC-Monitor.htm


CVIS: CALM Implementation

Host

Router


GeoNet: IPv6 geonetworkingFP7 European Project (STREP)

Feb. 2008 – Feb. 2010Web: http://www.geonet-project.euBudget: 3 M€/ 1.9 M€ funding

PartnersINRIA (Coordinator)HitachiNECEfkonLesswireBroadbitIMDEA networks

Objective: Design the concepts linking geographic addressing and routing with IPv6 mobility mechanisms (IPv6 geonetworking)

http://www.geonet-project.eu/


GeoNet: geo-broadcastPackets are forwarded from the source to all the nodes geo-located within the geographical area.

In GeoNet, we consider geo-flooding mechanism.

Max. Com. RangeDestination

(area)

Source


GeoNet: GeonetworkingGeonetworking: geographic addressing & routing

Distribution of information to all vehicles and roadside subsystems located in a given geographic area

Geo-broadcastPackets are forwarded from the source to all nodes located within a geographical area (geo-flooding)

Geo-unicastPackets are forwarded from the source to a given destination according to its geographical position (greedy forwarding)

Geo-anycastPackets are forwarded from the source to any (single) destination located in a given geographical area (greedy forwarding)

Topo-broadcastPackets are forwarded from the source to all surroundings nodes up to a certain distance in hops (flooding)


GeoNet: Scenarios


GeoNet: ScenariosGeoNet: scenarios requiring both IPv6 and geonetworking

Scenario Type 1: Sender is in the InternetPackets are transmitted in IPv6 until the RSUs serving the geographic area where they are geo-routed through intermediate vehicles to the final destination(s).

Scenario Type 2: Receiver is in the InternetPackets are geo-routed through intermediate vehicles (using geo-unicast) until a RSU where they are transmitted in IPv6 to the final destination.

Scenario Type 3: Sender & receiver(s) are only reachable through the Internet

Combination of Scenarios Type 1 & 2 where source and destination(s) are out of multihop wireless range


Active Safety Application

Traffic Efficiency Application

Infotainment Application

C2C Transport TCP / UDP / Other

IPv6 (NEMO)C2C Network

C2C Network

MAC / LLCIEEE 802.11 a,b,g Other Radio

(e.g UMTS)

MAC / LLCC2C MAC Layer Extension

European IEEE 802.11p

Info

rmat

ion

Con

nect

or

PHYIEEE 802.11 a,b,g

PHY European IEEE 802.11p

GeoNet: IPv6 geonetworking

GeoNet's scope


GeoNet: Functional Modules


GeoNet: IPv6 Links

In-vehicle IPv6 networkC2C-NET IPv6 link (defined according to radius or number of

C2C-NET hops)


GeoNet: IPv6 Forwarding (V2X)


ConclusionsITS systems to be reachable on the Internet must speak IP

IPv6 is necessary for wide development of IP-based ITS applications

IPv6 scales to millions of vehicles, each requiring several IP addresses & provides new functionalitiesIPv6 is currently being deployed (not an utopia) and will be fully operational by the time ITS systems get deployed

ITS community mostly agree that IP means IPv6ISO TC204 WG16 (CALM)C2C-CC's IPv6 adaptation layer (FP7 GeoNet)COMeSafety: European ITS Communication ArchitectureETSI TC ITSWAVE

Concept currently under validationCVIS: proof of concept of CALMGeoNet: combination of IPv6 with C2C-CC architecture


Conclusions: Lessons learned on IPv6 ITS community still lack understanding on what is IPv6 and training of their engineers

how to get trained on IPv6where to get IPv6 access fromhow to adapt IPv6 standards to ITS needs (e.g. geonetworking, addressing, security)

Hands-on experience of the ITS sector largely not sufficient

Urgent to develop IPv6 awareness and know-how within the ITS community

Avoid disruption of business due to bad design and lack of visionConsidering IPv6 at the earlier design stage will further ease the transition from IPv4 to IPv6 and save costsIPv6 compatibility must be ensured now


Links

ISO TC 204 WG 16 (CALM): http://www.calm.huCVIS: http://www.cvisproject.orgGeoNet: http://www.geonet-project.eu/COMeSafety: http://www.comesafety.orgIPv6 for ITS portal: http://lara.inria.fr/ipv6/ (under construction)LaRA: http://www.lara.prd.fr

http://www.calm.hu/

http://www.cvisproject.org/

http://www.geonet-project.eu/

http://www.comesafety.org/

http://lara.inria.fr/ipv6/


Thierry Ernst – IPv6 & ITS architectures – VNC Tokyo – October 2009

ITS Communication Architectures: The Road towards IPv6

[email protected]

LaRA (INRIA IMARA project-team & Ecole des Mines Paris)

http://www.lara.prd.fr


its communication architectures: the road towards ipv6 · system management entity (cme) iso...

Documents