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

  • 635 views
Uploaded on

NDN Applicability to V2V and V2R Networks …

NDN Applicability to V2V and V2R Networks
Ryuji Wakikawa, Rama Vuyyuru (Toyota ITC, Mountain View, USA)

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
635
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
17
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Ryuji Wakikawa, Rama VuyyuruToyota Info-Technology Center USA, Mt.view CALucas Wang, Lixia Zhang, Giovanni PauUniversity of California, Los Angeles CA Toyota InfoTechnology Center, U.S.A., Inc. All Rights Reserved.!
  • 2. Internet V2I: Vehicle to InternetV2R: Vehicle to Road-Side Unit V2V: Vehicle to Vehicle Toyota InfoTechnology Center, U.S.A., Inc. All Rights Reserved.!
  • 3. Internet V2I: Vehicle to Internet V2R: Vehicle to Road-Side UnitVehicle to Vehicle (V2V) Vehicle to Road Side Unit(V2R) V2V: Vehicle to Vehicle Toyota InfoTechnology Center, U.S.A., Inc. All Rights Reserved.!
  • 4. (IEEE 1609.2)DSRC Security Message Formats Min. Performance Req. Non-safety Applications (SAE J2735, J2945-1) DSRC WSMP TCP/UDP with safety sub-layer (IEEE 1609.3) IPv6 DSRC Channel switching (IEEE 1609.4) DSRC PHY+MAC (IEEE 802.11p) Toyota InfoTechnology Center, U.S.A., Inc. All Rights Reserved.!
  • 5. Application Infotainment Safety applications Mobility ApplicationsType applications Adaptive TrafficApplication Collision Probing Traffic Social Entertainm Cruise Signaldescription avoidance Information System Information Networking ent ControlMajor Fast connection Always on/Scalability BroadbandRequirement High ReliabilityTechnical Connectivity,Challenges Interference, Scalability, Spectrum Bandwidth, Cost Spectrum IP-based Architecture Non-Safety Information Multimedia Navigation Problem of IP-based V2V/V2R System Safety -  Routing overhead (ad-hoc) -  Destination Identification Internet Protocol (IP) V2I V2V, -  Service Discovery Ethernet/PLC V2R 802.11p -  Lack of Security (Data/Control) 3G/LTE/WiFi 802.15.4/BT/NFC/RFID (DSRC, WAVE) Toyota InfoTechnology Center, U.S.A., Inc. All Rights Reserved.!
  • 6. Traffic Information: Trip Time, Gas/Charging Station Info.: Pricing,Congestion, Route, Accidental Info, etc. Availability, etc.Parking/Restaurant/Shops Ad. info. P $20 P $10 Traffic Useful data can be exchanged locally among vehicles. Toyota InfoTechnology Center, U.S.A., Inc. All Rights Reserved.!
  • 7. Recent Friday afternoon road conditions in Los Angeles area Source California, Dept. of Transportation Toyota InfoTechnology Center, U.S.A., Inc. All Rights Reserved.!
  • 8. Not working Toyota InfoTechnology Center, U.S.A., Inc. All Rights Reserved.!
  • 9. sensor publisher Consumer Road sensors FM RadioVICS IR beacon(in JP) Vics center sensor publisher ConsumerPhone/ •  VICS Internet - SmartPhones 3G/LTE (Google Map)Navigation •  Cab Google HD radio - Portable Navigation •  Road sensors Device (PND) Sensor/publisher Consumer Wifi NDN WifiNDN DSRC DSRC LTE/3G LTE/3G Toyota InfoTechnology Center, U.S.A., Inc. All Rights Reserved.!
  • 10. !  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: !  Vehiclesmay cache data even if there is no pending interest, and serve as data mule for other cars. Toyota InfoTechnology Center, U.S.A., Inc. All Rights Reserved.!
  • 11. 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 /.()#0+*1# 23(&145%+.67(89.1# "&*:.&# !"!#$%&(&)*+,#-+,*+.# FIB Forwarding Information Base DSRC/WAVE/802.11p Network PIT Pending Interests Table Databases Interfaces Contents Cache (data from WiFi Contents built-in sensors, built-in cameras, safety system) Toyota InfoTechnology Center, U.S.A., Inc. All Rights Reserved.!
  • 12.  The data publisher stores  The data mule caches data from sensors, camera any data it can collect. or safety systems. data Data Data Traffic data Mule Publisher data messagevia DSRC RSU ! data data data Road work data New processed data Consumer data 1 + Data 2 + Data 3 Consumer  The data consumer sends interest and receives data.  Head Unit displays the processed information. Toyota InfoTechnology Center, U.S.A., Inc. All Rights Reserved.!
  • 13. !  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 Toyota InfoTechnology Center, U.S.A., Inc. All Rights Reserved.!
  • 14. !  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 Toyota InfoTechnology Center, U.S.A., Inc. All Rights Reserved.!
  • 15. !  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 Toyota InfoTechnology Center, U.S.A., Inc. All Rights Reserved.!
  • 16. 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! Toyota InfoTechnology Center, U.S.A., Inc. All Rights Reserved.!