CCNxCon2012: Session 3: NDN Applicability to V2V and V2R Networks

Toyota InfoTechnology Center, U.S.A., Inc. All Rights Reserved.!

Ryuji Wakikawa, Rama Vuyyuru Toyota Info-Technology Center USA, Mt.view CA Lucas Wang, Lixia Zhang, Giovanni Pau University of California, Los Angeles CA


Internet

V2I: Vehicle to Internet

V2V: Vehicle to Vehicle

V2R: Vehicle to Road-Side Unit


Internet

V2I: Vehicle to Internet

V2V: Vehicle to Vehicle

V2R: Vehicle to Road-Side Unit Vehicle to Vehicle (V2V) Vehicle to Road Side Unit(V2R)


DSRC PHY+MAC (IEEE 802.11p)

DSRC Channel switching (IEEE 1609.4)

DSRC WSMP with safety sub-layer

(IEEE 1609.3) IPv6

TCP/UDP

Message Formats Min. Performance Req. (SAE J2735, J2945-1)

Non-safety Applications

DSR

C Security

(IEE

E 1609.2)


Internet Protocol (IP) V2V, V2R

802.11p (DSRC, WAVE)

IP-based Architecture

V2I Ethernet/PLC 3G/LTE/WiFi

802.15.4/BT/NFC/RFID

Application Type Safety applications Mobility Applications Infotainment

applications

Application description

Collision avoidance

Adaptive Cruise Control

Traffic Signal

Information

Probing System

Traffic Information

Social Networking

Entertainment

Major Requirement

Fast connection High Reliability Always on/Scalability Broadband

Technical Challenges Interference, Scalability, Spectrum Connectivity,

Spectrum Bandwidth, Cost

Information

Multim

edia

Navigation

System

Non-S

afety

Safety

Problem of IP-based V2V/V2R -  Routing overhead (ad-hoc) -  Destination Identification -  Service Discovery -  Lack of Security (Data/Control)


P $20 P $10

Traffic

Traffic Information: Trip Time, Congestion, Route, Accidental Info, etc.

Parking/Restaurant/Shops Ad. info.

Gas/Charging Station Info.: Pricing, Availability, etc.

Useful data can be exchanged locally among vehicles.


Recent Friday afternoon road conditions in Los Angeles area

Source California, Dept. of Transportation


Not working


sensor Consumer

Internet 3G/LTE HD radio

publisher

•  VICS •  Cab •  Road sensors

Phone/Navigation

Sensor/publisher Consumer

NDN Wifi DSRC LTE/3G

Wifi DSRC LTE/3G

NDN

sensor Consumer

FM Radio

IR beacon

publisher

Road sensors VICS (in JP) Vics center

Google - SmartPhones (Google Map) - Portable Navigation Device (PND)


!  Why NDN? ! Vehicles know the data they need ! Data consumers do not know which vehcile may have the

data

! Differences of vehicular NDN from original design ! No Routing: “No unicasting but broadcasting”

! Vehicular NDN does not use FIB ! Vehicular NDN requires different PIT management schemes, e.g.

broadcasting interests several times before its expiration.

! High Data Propagation: ! Vehicles may cache data even if there is no pending interest, and

serve as data mule for other cars.


FIB

PIT

Contents

DSRC/WAVE/802.11p

WiFi

Network Interfaces Databases

Pending Interests Table

Forwarding Information Base

Contents Cache (data from built-in sensors, built-in cameras, safety system)

!"!#$%&'(&)*+,#-+,*+.#

/.()#0+*1# 23(&145%+.67(89.1#

"&*:.&#

We assume each vehicle embeds a NDN module –  Each vehicle can generate various data, either periodically or in an event-driven

fashion –  Each car has sufficient memory space and transmission power


!

RSU

 The data publisher stores data from sensors, camera or safety systems.

Traffic message

via DSRC

Data

 The data consumer sends interest and receives data.

 The data mule caches any data it can collect.

data

data

data 1

New processed data

data

+ + Road work

Data

 Head Unit displays the processed information.

data

data

data

Data 2 Data 3

data

Publisher

Consumer Consumer

Mule


!  Design goals for data naming !  Should allow data publishers to describe what they have. !  Should allow data consumers to describe what they need

!  Requirements !  Geographical scoping

!  Define location based scope for generated content

!  Temporal scoping !  Define validity time for the content generated

!  Duplication detection and elimination !  Detect duplicate content and eliminate redundancy

!  Data accuracy !  Naming should support estimating accuracy of published content

!  Other requirements specific to application


!  First proposal for naming structure !  /traffic/geolocation/timestamp/data type/nonce

!  “traffic” serves as application id to make naming application specific

!  “geolocation” specifies where the event happens !  “timestamp” shows when the event happens !  “data type” indicates the meaning of data,

!  e.g. closed lane, vehicle speed etc. !  “nonce” is used to uniquely identify each interest

!  Example !  /traffic/Highway 101/north/{400,410}/

{1323201600,1323205200}/speed/19375887 !  {400, 410} is the section number range showing where the event

is generated !  {1323201600,1323205200} is the temporal range showing data is

generated between 12:00 and 13:00 on December 6th, 2011


!  Our activity for NDN-based V2V/V2R !  Investigation of NDN requirements from various use-cases !  Optimization of NDN specification for automotive !  Investigation of naming design for various applications !  Evaluation of vehicular NDN by simulation

!  Publications !  DMND: Collecting Data from Mobiles Using Named Data Jiangzhe

Wang, Ryuji Wakikawa, Lixia Zhang. IEEE VNC 2010 !  Data Naming in Vehicle-to-Vehicle Communications Lucas Wang,

Ryuji Wakikawa, Romain Kuntz, Rama Vuyyuru, Lixia Zhang, IEEE NOMEM 2012

!  Rapid Traffic Information Dissemination Using Named Data Lucas Wang, Alexander Afanasyev, Romain Kuntz, Rama Vuyyuru, Ryuji Wakikawa, Lixia Zhang ACM NOM 2012


Homepage!http://www.us.toyota-itc.com!Headquarters!465 Bernardo Avenue, Mountain View, CA 94043!New York O"ce!156 West 56th Street, Suite 1001, New York, NY 10019!

Documents

CCNxCon2012: Session 3: NDN Applicability to V2V and V2R Networks