01.11.2017 Vehicular Technology and OpenStack NFV A Word On “The Edge Cloud” PRAKASH RAMCHANDRAN GOKHALE JAYANTHI
Agenda What is VT? How VT uses NFV? Vehicular Technology (VT) addresses part of Intelligent VT fits into using NFV MANO to manage Edge Stack Transportation System (ITS) What are the VT use cases? Using OpenStack Edge for CVA Near-term is Connected Vehicles and long term is Autonomous How do you get OpenStack? Driving and in-between some Entertainment & I-IOT applications What is Openstack’s Edge Stack Conclusion & Q&A’s Openstack Edge Stack using Small & Medium footprints Next Steps- Need Scoping & Blueprints for VT Support at Edge
What is VT? Potential Cost to save using Autonomous Vehicles R&D in USA Vehicular Technology involves : Communication Radar, Lidar, V2X, (Advanced • Freight Cost B$, $100 , 13% driver-assistance systems)ADAS, Autonomous Congestion Cost in B$, Vehicles (AV) , Short Range Data Communication $121 , 15% (SRDC) standards lost lives B$, $75 , 9% Cloud systems and devices to collect and respond • with precise calculations - latency limitations to respond for steering and driving decisions. Location, Maps & Routes Maps and traffic patterns • and various smart transportation Data to store and analyze in Openstack Cloud using interface and Vacation Loss B$, $500 , 63% work with different radio technologies. Openstack existing and evolving edge standards • with strategies to enable local and global decisions along with its IoT, Sensors and efforts to support Congestion Cost in B$ lost lives B$ Vacation Loss B$ Freight Cost B$ devices meeting LTE Release 12-14 PC5 & LTE-V standards.
Intelligent Transportation System and VT Vehicular Technology is part of transportation and logistic enablement for next generation
Sensors Summary Ultrasonic Sensor : low resolution, short distance for parking assist RADAR Sensor: radio wave detection and ranging. Medium resolution to determine obstacle, their distance, their speed Odometer Sensor: to measure the speed of the vehicle Prebuilt Maps : containing road / terrain information Inertial Navigation System : uses gyroscope and accelerometers to determine vehicle’s position, orientation and speed. Works along with GPS. DSRC: Direct Short Range Communication, used for vehicle to vehicle(V2V) and Vehicle to Infrastructure (V2I) communication [road, traffic light etc]. Cameras : Grabbing pictures & video for determining the scene IR Sensor : Used to capture low intensity images in the dark / night GPS : Global Positioning System to determine vehicle’s position (lat – long) LIDAR : Light Detection and ranging. Uses light / laser beam based detection of obstacles and prepares a 3D contour map.
Autonomous Vehicles ➡
Vehicular Ad-hoc Networks(VANET) As vehicles fall out of the signal range and drop out of • the network, other vehicles can join in, connecting vehicles to one another so that a mobile Internet is created. A Vehicular Ad-Hoc Network, or VANET is a • technology that uses moving vehicles as nodes in a network to create a mobile network. VANET turns every participating vehicle into a wireless router or node, allowing vehicles approximately 100 to 300 meters of each other to connect and, in turn, create a network with a wide range. VANET is a subgroup of MANET where the nodes • refer to vehicles.
VANET Environment DN-Central DN1 CN • RN
Principal Components • OBU – Onboard units (for onboard interactions and V2V communication by messages sent directly or through RSU) • RSU – Road Side Units (for V2V and V2I). Receives messages from vehicles and broadcasts them to other vehicles or the Infrastructure • Internet Gateway Infrastructure
Dedicated Short Range Communication (DSRC) 802.11p Add wireless access to vehicular networks • and implements OSI stack Wireless Protocol with Licensed band of 5.9GHz, 7 • channels, Range of 1000m, Data rate 6 to 27Mbps Mainly used in communication of • 1) Vehicle to Vehicle • 2) Vehicle to Roadside Infrastructure •
Communication Types at a Glance
VEHICLE TO VEHICLE COMMUNICATION (V2V) V2V is most suited for short range vehicular networks using DSRC. • It is Fast and Reliable and provides real time safety • It does not need any roadside Infrastructure. • V2V does not have the problem of Vehicle Shadowing in which a smaller • vehicle is shadowed by a larger vehicle preventing it to communicate with the Roadside infrastructure. Location based broadcast and multicast are the proper communication • methods for collision avoidance in V2V Communication Issues: • Stringent response times (Maneuvering Time) • Identification / Addressing of vehicles (use Certificate of Authority and • assign an address tagged the number plate)
(V2I) +ROADSIDE COMMUNICATION (V2R) Vehicle to Infrastructure provides solution to longer-range vehicular networks. • It makes use of preexisting network infrastructure such as wireless access • points (Road-Side Units, RSUs). Communications between vehicles and RSUs are supported by Vehicle-to- • Infrastructure (V2I) protocol and Vehicle-to-Roadside (V2R) protocol. Needs large area coverage and more feature enhancements for Vehicle • Applications using DSRC or other technologies (Bluetooth, WIFI etc.). Roadside infrastructure involves establishing a connectivity to a • communication infrastructure (5G / 4G or otherwise) and hence involves additional installation costs.
Security in DSRC • Scheduler in every OBU • Pre-emptive policy for Higher Priority Messages • Each OBU has a valid certificate issued by CA(Certification Authority) based on unique license plate registration • Based on Digital signature sent by OBU, using Public key decryption message is verified
Routing Methodologies • In V2V communication, the collision warning messages are broadcast from vehicle to vehicle across multiple hops without the involvement of a roadside unit. • In case of V2R the warning messages are first sent to a roadside unit, and then broadcast by the roadside unit to all vehicles in range. • In V2R/V2V Hybrid Model, Vehicles which receive a warning message via V2V communication will send it to a roadside unit if they did not receive a warning message with the same event ID from roadside units.
Connected Vehicle Applications (CVA) Next? open stack @OpenStack openstack OpenStackFoundation
Cloud Infrastructure for Intelligent Vehicles • OBU – On Board Unit Orchestration & Network Management • RSU – Road Side Unit RSUC RSUC I2I • RSUC – Road Side Unit Controller I2I I2I • Edge Cloud RSU RSU BS RSU BS RSU RSU RSU • AU – Application Unit V2I V2I V2I V2I OBU OBU • Connectivity V2I, V2V, I2V, I2I OBU OBU OBU OBU V2V V2V
Road Side Unit Controller (RSCU) • Acts like a local data centre, with virtualized resources. • Cloudlet infrastructure • Runs multiple AUs in VMs • Deploys Aus to the RSUs on demand • Containerised instances for AUs • Hence needs VN, VM, VS (Nova/Neutron/Cinder/Ceph/Swift)
RSU Deployment • Dense Regions: At every intersection. Vehicles with dashboard antenna range is approximately 50 metres. • Normal Regions: 200 meters with an outdoor antenna. Hence RSU can be deployed every 200 m • Sparse Regions: Every 1/2 mile
V2X Connected Vehicle Applications CVA) Low latency, Location Based, Moderate throughput • V2V Safety • V2I Safety • Emergency Electronic Brake Lights (EEBL) • Red Light Violation Warning • Forward Collision Warning (FCW) • Curve Speed Warning • Intersection Movement Assist (IMA) • Stop Sign Gap Assist • Left Turn Assist (LTA) • Spot Weather Impact Warning • Blind Spot/Lane Change Warning (BSW/LCW) • Reduced Speed/Work Zone Warning • Do Not Pass Warning (DNPW) • Pedestrian in Signalized • Vehicle Turning Right in Front of Bus Warning (Transit) • Crosswalk Warning (Transit) http://www.its.dot.gov/pilots 20
Openstack Modules and Resources for “OPEN EDGE STACK” Next? openstack @OpenStack openstack OpenStackFoundation
NFV Infrastructure & Services at the Edge Policy Management for Edge Enabled Applications MANO NFVO Orchestration (ONAP, Mobility & Session Management Transportation Management System OpenBaton, OSM, K8, OPNFV Service Offerings and associated and Location Based Safety CI/Testing) resource requirements Applications (OPA + Congress) (Services/AF) Middleware APIs “OPEN EDGE STACK” MEC/ Access/Metro Ethernet Central Large Data Centers(Public & connectivity Private) Cloudlet, Statelet, Netlet built from Infrastructure IP Multimedia Services (IMS) Microservices User Plane Functions Openstack Lightweight/ Distributed Openstack Distributed “OPEN EDGE NFVI” with VNF/Containers Medium Weight VIM (MPP) Cloud Management SFC/Classifiers Configurations systems In scope of Openstack In Scope for Upstream In Scope common to all
Recommend
More recommend
