160 likes | 306 Views
Data Naming in Vehicle-to-Vehicle Communications. Lucas Wang Ryuji Wakikawa Romain Kuntz Rama Vuyyuru Lixia Zhang Computer Science, University of California, Los Angeles Toyota InfoTechnology Center, USA Mountain View, CA. Outline. Abstract V2V communication
E N D
Data Naming in Vehicle-to-Vehicle Communications Lucas Wang Ryuji Wakikawa Romain Kuntz Rama Vuyyuru Lixia Zhang Computer Science, University of California, Los Angeles Toyota InfoTechnology Center, USA Mountain View, CA
Outline • Abstract • V2V communication • In-vehicle system assumptions • System operation • Requirements on data naming • Naming Design • Interest Packet / Response Packet • Meeting system requirements • Conclusion • 每日一句
Abstract • Today vehicles use TCP/IP to communicate with centralized serversthrough cellular networks. Many vehicular applications desire direct V2V communications which is difficult to achieve using the existing solutions, • This paper explores the named-data approach to address this challenge, use case studies to identify the design requirements and put forth astrawman proposal for the data name design to understand its advantages and limitations.
V2V communication • Dedicated Short Range Communication / Wireless Access in Vehicular Environments (in 5.9Ghz) Several Dozens or hundred Messages in a second In 100 km/h:at least ten 3-Kbit-messages in a second 100~500 Meters
V2V communication • several technical difficulties arise when one attempts to run IP • it is infeasible to assume the availability or dependency on infrastructure support RSU(Road Side Unit )
Requirements on data naming 3. Duplication? 4. Data accuracy? 5. Application Type? 2. When Data Data Data 1. Where Data Data
Naming Design • Traffic: application id. • Geolocation: road ID(link ID)/direction/section number. • Timestamp: UNIX timestamp format • Data type: the meaning of the data itself • Nonce : distinguish data generated by different producers. • EX: • {1323201600,1323205200}:between 12:00 and 13:00 on December 6th, 2011.
Interest Packet • multiple interests: between section {405,415} => • Want to receive traffic data in the specified region generated at any time and regardless of the data type. • => all traffic information on highway 101 regardless of the regions and time
Response Packet with Many Matching Data /traffic/Highway 101/north/{400,410} /{1323201600,1323205200}/speed/19375887 /traffic/Highway 101/north/{400,410} /{1323201600,1323205200}/speed/19375887 /traffic/Highway 101/north/{400,410} /{1323201600,1323205200}/speed/19375887 /traffic/Highway 101/north/{400,410} /{1323201600,1323205200}/speed/19375887 /traffic/Highway 101/north/{400,410} /{1323201600,1323205200}/speed/19375887 /traffic/Highway 101/north/{400,410} /{1323201600,1323205200}/speed/19375887 Interest Packet /traffic/Highway 101/north/{400,410} /{1323201600,1323205200}/speed/19375887 /traffic/Highway 101/north/{400,410} /{1323201600,1323205200}/speed /traffic/Highway 101/north/{400,410} /{1323201600,1323205200}/spee/19375887d /traffic/Highway 101/north/{400,410} /{1323201600,1323205200}/speed /traffic/Highway 101/north/{400,410} /{1323201600,1323205200}/speed/19375887 /traffic/Highway 101/north/{400,410} /{1323201600,1323205200}/speed/19375887
Meeting system requirements • Duplication detection and elimination /traffic/Highway 101/north/{400,410} / {1323201600,1323205200}/Speed/ Interest Packet /traffic/Highway 101/north/{400,410} / {1323201600,1323205200}/Speed/24756335 /traffic/Highway 101/north/{400,410} / {1323201600,1323205200}/Speed/19375887 /traffic/Highway 101/north/{400,410} / {1323201600,1323205200}/Speed/19375887 /traffic/Highway 101/north/{400,410} / {1323201600,1323205200}/Speed/24756335 /traffic/Highway 101/north/{400,410} / {1323201600,1323205200}/Speed/24756335 /traffic/Highway 101/north/{400,410} / {1323201600,1323205200}/Speed/97867572 /traffic/Highway 101/north/{400,410} / {1323201600,1323205200}/Speed/97867572
Meeting system requirements • Data accuracy /traffic/Highway 101/north/{400,410} / {1323201600,1323205200}/Speed/19375887 /traffic/Highway 101/north/{400,410} / {1323201600,1323205200}/Speed/19375887 /traffic/Highway 101/north/{400,410} / {1323201600,1323205200}/Speed/19375887 /traffic/Highway 101/north/{400,410} / {1323201600,1323205200}/Speed/19375887
Conclusion • this paper identified three different roles vehicles may play in traffic data dissemination amd also identified three changes to the NDN forwarding module to make it more suited in a vehicle network. • Instead of using IP addresses, our design allows vehicles to collect and disseminate traffic information among themselves using data names that are defined a priori during application development and understood by all vehicles. • Rather than asserting any specific results, what is the best way to design the data name structure remains an open challenge.
每日一句 • Instead of using IP addresses,our design allows vehicles to collect and disseminate trafficinformation amongthemselves using data names that are defineda priori during application development and understoodby all vehicles. • 相對於IP位置,我們的設計可以藉由使用的經由應用程序開發所演繹過的,以及可以被所有車輛理解的資料名稱,讓車輛收集和廣播這些在各車輛彼此之間的訊息,