1 / 18

Kohei OHTA

Monitoring vehicles The potential and the challenge. Kohei OHTA. Introduction. Connect CARs with Internet Seamless connectivity Connect to World Connect to various personal equipments Many new technologies available MIPv6 Auto configuration Ad-hoc networking

kassia
Download Presentation

Kohei OHTA

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Monitoring vehicles The potential and the challenge Kohei OHTA

  2. Introduction • Connect CARs with Internet • Seamless connectivity • Connect to World • Connect to various personal equipments • Many new technologies available • MIPv6 • Auto configuration • Ad-hoc networking • Many NEW mobile applications for CARs • Road service • On-line customer service

  3. Probe Car project • Develop new applications with car related information like • Velocity, Acceleration • GPS information • Winker status • Wiper status • Etc… How to collect these information?

  4. Requirements for information collection from Cars • Security • Protect privacy information • Standardization • Naming • Common scheme and methods the various types of information • Transport protocol • Tough transport protocol under wireless environment • Efficiency • High resolution and row bandwidth transport

  5. Security • There are many privacy sensitive information in cars • Geographical location • Velocity • Passengers • Etc • Strong security mechanism is required • Encryption • Authentication • Access control

  6. Standardization • Naming • To support multi vendor environment, common scheme to specify a information item. • For example, we have to be able to access vehicle velocity from any vendor’s car with SAME method. • Transport • Simple and tough transport protocol is suitable for mobile wireless environment

  7. Efficiency • Mobile wireless environment is worse than wired network • Connectivity is NOT guaranteed at all • There is less chance of stable connectivity • The bandwidth is often narrow • It is difficult to collect high resolution information in such environment • UDP is preferable to TCP • Effective aggregation for high resolution with less bandwidth under unreliable line

  8. Applicability of SNMPv3 [1] • Information collection in TCP/IP is • Basic issue for network management • That is already existing • There are many management information for various networked devices and applications, router, switch, server, printer, and so on • Well standardized

  9. SNMPv3 has • For Privacy • DES/AES encryption support • For authentication • Multiple user support • MD5/SHA1 digital signature • Key management • Different key management with single pass phrase • For access control • Allow access to iitsVehicleVelocity from center ADeny access to iitsLongitude from service center BDeny access to iitsLatude from service center B • Strandardization • Well standardized consistent naming scheme • .1.3.6.1.4.1.282.16.108.1.3.3.3 iitsVehicleVelocity • Transport • Connectionless UDP • Per packet authentication/encryption

  10. Current configurations Information collection center Encrypted A IPv6 Information collection center Velocity B Logitude Latitude Defined as MIB in ASN.1 Winker Wiper status

  11. Polling and Trap • There are two modes in SNMP to collect information • Polling is good to collect periodic data • Trap is good to notify a event

  12. Manager Agent Name-1 Name-1 Name-n Name-n Value-1 Value-n null null Manager Agent 646213932 Response Get 1.3.6.4.1.282.16.107.2.1.1.3 For effectivenessSNMP Packet Payload

  13. 60 MOs/packet Current Method Manager Manager Query and response Query and response time Agent Agent Delay Name-(n-1) Name-2 Name-1 Value-1 Value-2 Value-n Responze Polling at small intervals time PDU SIZE = 60 * (length (Name) + length(Value)) Length(Name) = 12; length (Value) = 6 =60 * (12 + 6 ) = 1.08K bytes !!

  14. Manager Agent Name-A null Manager Agent Vaｌ（t1+(n-2)I) Name-A Val(t1) Val（ｔ１＋I） t1 Vaｌ（t1+(n-1)I Name-A Value-A Response Get Responze t1,Val(t1),Val(t1+I),Val(t1+2I),….Val(t1＋(n-1)I) Time-based (History) Aggregation MO MO: n values of ifInOctets.１ intervalI PDU SIZE ~ 60 * length(Value)) length (Value) = 6 ~60 * 6 = 360 bytes !!

  15. Evaluation - Data Retrieval Time

  16. Evaluation – Management Traffic

  17. Evaluation - CPU Usage

  18. For reliable information collection • Data collection with SNMP has been based on Polling • Mobile node is often disappeared from data collector because of the physical condition and occasional shadowing. • Data collector can not know and control the connectivity to mobile node. • Conventional polling based data collection no longer work well.

More Related