Vehicle GENI Testbed: Challenges and Experiments WINLAB, March27 2007

Vehicle GENI Testbed: Challenges and Experiments

WINLAB, March27 2007

Break out Moderator, Mario Gerla

UCLA

Vehicle/Mobile/DTN Break out session

• Participants

• Mario Gerla, [email protected] (moderator)• Liviu Iftode [email protected]• Marco Gruteser [email protected]• Brian Levine [email protected]• K. Ramachandran [email protected]

Why Vehicles Communications?

• Traditional Internet access:– Web access; File transfers; telcons; Messaging– Opportunistic extension of the internet

• Content/entertainment delivery/sharing:– Music, news, video, TV, etc– Local ads, tourist information, games, etc

• Safe navigation:– Forward Collision Warning, Intersection Collision Warning,

Emergency recovery

• Environment sensing/monitoring: – Traffic monitoring, Pollution probing– Pervasive urban surveillance

Support from the Internet: Functions and Challenges

• Mobility support – Location tracking; Geo Location Service– User profiling

• Vehicle data traffic/routing management– Least Cost Routing: vehicle grid or infrastructure– Inter AP/cell connectivity awareness– Congestion monitoring/protection– Path Quality estimation

• Intermittent vehicle connectivity support (DTN) – Destination temporarily disconnected; – Internet stores/forwards (Cache Forward Net) ;

• Security authentication (PKI) support– Certificate authority; Tracking trouble makers across the continent..

• Vehicle network monitoring/management– When Infrastructure fails (eg. Katrina) switchover to Vehicle Grid standalone

operation

GENI Experiment Examples

• Geo Location Service• Infrastructure Routing Support• Centralized Security• Applications:

– Car torrent

– Urban sensing

– Emergency Urban Evacuation

Supporting Geo Location Service

• Why Geo-routing?– Most scalable (no state needed in routers)– GPS readily available; local coordinates used in blind

areas (tunnels, parking lots, urban canyons)

• Geo Location Service • First option: Infrastructure overlay support• Distributed implementation backup (eg GHT)• Other option: transparent Internet geo route support

in virtualized router

Infrastructure based Overlay Location Service (OLS)

Vehicular ID hashed into overlay DHTMapping: Vehicular ID <=> location

Georouting through the infrastructure

• IPv6 addressing (xy coordinates in header extension)

• How to make the system resilient to failures/attacks? – If access points fail, use GLS implemented in grid

Infrastructure routing support

The trade off: grid short paths vs Internet fast wires

• Baseline: Shortest path routing– Short connections should go grid– Packets to remote destinations on infrastructure

• Enhanced: Access Points and Overlay assist in the decision– Propagation of congestion info from Overlay to

wireless using 3 hop beaconing (say) every second

Security Infrastructure Support

Appl #1: Co-operative Download-Car Torrent

Vehicle-Vehicle Communication

Internet

Exchanging Pieces of File Later

Appl #2 Accident Scenario witnessing

VSN-enabled vehicle

Inter -vehiclecommunications

Vehicle -to-roadsidecommunications

Roadside base station

Vid e o Ch e m.

Sensors

S to ra g e

Systems

P ro c.

Appl #2 Accident Scenario (cont)

• Designated Cars (eg, busses, taxicabs, UPS, police agents, etc): – Continuously collect images on the street (store data locally)– Process the data and detect an event– Classify the event as Meta-data (Type, Option, Location, Vehicle ID)– Post it on distributed index -> Epidemic Dissemination

• Police retrieve data from designated cars

Meta-data : Img, -. (10,10), V10

CRASH

- Sensing - P rocessing

Crash Summary Reporting

Summary Harvesting

Appl#3 Evacuation Scenario

• Dense urban area evacuated because of attack or natural disaster• Infrastructure obliterated - must rely on Car to Car

communications• Evacuation of vehicles and people

– Static evacuation plans will not work in hostile attacks– Distributed sensing of damage and road availability– Distributed, collaborative evacuation strategy computation

GENI Vehicle Testbed - Experiments

Premise: testbed relies on GENI InfrastructureGENI relevant Experiments (a first cut):• Mobility support:

– Mobility support depends on addressing/routing used – Geo Location service– Mobile OSPF

• Routing support• Exploiting different radio media (802.11p,WiFi, Cellular, WiMAX,

etc)• Density/ intermittence monitoring (from AP’s)• Congestion monitoring• Security support - how costly, how fast..• End to end applications involving the Internet

– Entertainment; (eg, content sharing) games; web access

GENI Vehicle Testbed - requirements

How many vehicles:– A few suffice for propagation, geo location service;– Larger numbers for epidemic dissemination; DTN– GENI program will provide 100’s nodes– Added scalability using simulation/emulation

• Vehicle fleet deployment:– Scheduled Public transport; eg DieselNet (predictable, to

some extent)– Unscheduled public transport; eg CarTel (taxicabs); UPS;

Campus facility vehicles - Incentives??– Customized experiments (can specify the route)– Augment the above with stationary nodes– Access to Infrastructure: open access AP’s or coexisting

mesh testbed

GENI Vehicle Testbed - requirements (cont)

• Various applications/mobility patterns– Combination of small scale testbed experiments + simulation– Example: content sharing - must use realistic motion traffic model; – same for epidemic dissemination to handle DTN situations

• Third party participation: – Remote access through web interface– Remote testbed interconnection

• Experiments using multiple providers– Necessary for experiment control (eg GPRS, EVDO, etc)

• Experiment set up/Measurement collection– Control will depend on type of vehicle fleet

• Virtualization/slicing– To support & compare multiple protocols/algorithms

Simulation Support

QuickTime™ and aMicrosoft Video 1 decompressorare needed to see this picture.

CC--VVee TTCampus Vehicular TestbedCampus Vehicular Testbed

E. Giordano, A. Ghosh,

G. Marfia, S. Ho, J.S. Park, PhD

System Design: Giovanni Pau, PhD

Advisor: Mario Gerla, PhD

Vehicle Fleet

• We plan to install our node equipment in:– A dozen private cars: customized experiments– Up to 50 Campus operated vehicles (including shuttles and facility

management trucks). • “on a schedule” and “random” mobility; cross campus via 10 AP’s

– Up to 50 Communing Vans • Measure freeway motion patterns (only tracking equipment installed)

The U-Box Node:

• In the final deployment:– Industrial PC (Linux OS)– 2 x WLAN Interfaces– 1 Software Defined Radio (FPGA based) Interface– 1 Control Channel – 1 GPS

• Current proof of concept:– 1 Dell Latitude Laptop (Windows)– 1 WLAN Interface– 1 GPS– OLSR Used for the Demo

The C2C testbed

6-Car Caravan on CAMPUS communicating via OLSR