This document proposes an architecture called CONTACT to enable quality of service (QoS) support in vehicular ad hoc networks (VANETs) to enable future applications of autonomous driving and in-vehicle infotainment. The architecture takes a multi-pronged approach using software defined networking for resource scheduling and routing management, content-centric networking to focus on content sharing rather than locations, and context management to continuously estimate available resources and achievable QoS. The goal is to design a system that can support the stringent QoS requirements of applications for autonomous driving coordination and entertainment through improved reliability, efficiency, and capacity over traditional VANET and cellular technologies.

1. Gianluca Rizzo,
Maria Rita Palattella, Thomas Engel
Torsten Braun
CONTACT
CONtext and conTent Aware
CommunicaTions for QoS support in
VANETs
HES SO Valais, Sierre
University of Luxembourg
University of Bern

2. The future of transportation is
autonomous and «smart»
Today: autonomous drive is «fully autonomous»
• No coordination between cars
Communications and coordination between cars improve:
• Safety
• Travel times
• Fuel efficiency

3. Coordinated autonomous drive
requires reliable V2V communications
Car Platooning
Requirements:
• Hard upper bound to delay
• Low delay
• High reliability

4. Infotainment will play a larger role
• Work and entertainment during trip
• Tighter QoS requirements (capacity and performance)

5. Which communication technology will
support these applications?
• In principle, no innovation required
– Autonomous, coordinated driving: Just sensors and
coordination protocols
– Infotainment: 4G, 5G
• But these technologies are inefficient, unreliable
and hence unfit
– Each car has limited view of surroundings:
• Ex: colliding car behind corner
– Comm technologies are not conceived for these
applications: Large margin for improving reliability and
efficiency
– Not enough resources (capacity) as of today

6. An (old) candidate solution is still unfit…
• Vehicular ad hoc communications (VANETS)
– Car-to-car, infrastructure-less exchange of data
• Help building a common view of the environment
– Coordination through message exchanges
• BUT: unreliable
– Only best effort, need critical mass
– Poor quality (high delay and packet loss)
– Ad-Hoc QoS solutions

7. • Characterize QoS requirements of major
families of applications
• Design architecture capable of supporting the
required QoS levels
• Adopt a Multi–pronged approach
– SDN: control layer
– MAC layer
– Network layer/Application layer: content and context
awareness
CONTACT: Enabling QoS in VANETS

8. Main Ingredients
• Software Defined Networks
– Scheduling of resources, routing management
– Improve efficiency of channel allocation
– Improve flexibility and adaptability
• Content Centric Networking
– Focus on content, not on its location
– Extend Dynamic Unicast to multi-hop communications
– Continuous estimation of avalable resources and of achievable
QoS
• Floating Content
– Infrastructure-less distributed content sharing
– Best effort, delay tolerant applications
• Context management
• Performance monitoring and dynamic adaptation

9. Overview of the architecture
MAC Layer
Transport Layer
Network Layer
Overlay Layer
Application Layer A1 A2
Unicast, Broadcast, Multicast,
TCP/UDP IPv4/IPv6 , CCN
WiFi, Bluetooth, D2D, M2M,
Cellular, Ad Hoc
Client/server, P2P
………….
Performance
Monitoring
Context
Awareness
Dynamic
Resources
Management

10. Thanks!