MEC-based Stable Topology Prediction for Vehicular Networks

Use Case Details:

Species Details:

Contributors:

References:

Tasks (for the team):

Task name	Details	Creation date	Completion date	Assignee	Status
Voting for BP	Request and follow up voting process.	21 Sep 2020	22 Sep 2020	MalikAsif
Project Approved: 22 Sep 2020
Request for PTL	Request to initiate the PTL.	01 Oct 2020	01 Oct 2020	MalikAsif
MalikAsifor saqib haleemgot  elected as PTL: 08 Oct 2020
Setup PM	Setup the Physical Machine.	01 Oct 2020	05 Oct 2020	MalikAsif saqib haleem
Setup Jenkins	Setup Jenkins on PM.	06 Oct 2020	06 Oct 2020	MalikAsif saqib haleem
Connect LF Server	Integrate the Linux Foundation Servers.	07 Oct 2020	07 Oct 2020	saqib haleem
Push CICD logs	Confirmation of the CICD logs	08 Oct 2020	09 Oct 2020	saqib haleem
Explore/Research K8s container protocol options in python	Explore the containers inter/cross domain protocol options to enable communication among each other.	01 Oct 2020	09 Oct 2020	saqib haleem MalikAsif
Explore/Research K8s network options	Explore the networking plugin options that can be used in our proposed scenarios of vehicles.	01 Oct 2020	08 Oct 2020	MalikAsif saqib haleem
Create documentation pages & subsections	Architecture - figures/explanation Components - figures/explanation Use-cases/Scenarios - figures/explanation Implementation - plan/approach Ask Questions - toq	01 Oct 2020	13 Oct 2020	MalikAsif saqib haleem
Create vehicle containers	Vehicle Classes	02 Oct 2020	12 Oct 2020	MalikAsif
Maps	Search ways for creating roads, intersection etc Implement roads. intersection etc	08 Oct 2020	31 Oct 2020	MalikAsif

Committers and PTL (Project Technical Lead)

Please enter in all names of the committers for the project.

PTL is done off of self nomination process.  If you wish to be considered for the PTL, please indicate that by putting a Y in the self nomination column (use the slide to move the table left to right).  Per Akraino rules, if there is only one nominee, that person becomes PTL (when confirmed by the Akraino TSC).  If there is more than nominee, we will then have an election.
The election process is open and will go through 7 Oct. 2020 at Noon Pacific time. 

Motivation:

Motivational aspects are:

• The topology in a vehicular network is updated and retrieved frequently
  • This causes path instability
• Vehicular networks are wireless in nature
  • However, Software-defined networking (SDN) is originally designed for wired networks
• Leads to the need for topology stability in vehicular networks

To this end, we introduce:

• Computation at the Edge 
• Topology prediction to proactively stabilize the paths in vehicular network
• Proximity Services

Architecture Overview:

The architectural view of our system is as follows:

Use case Attributes:

1. Stable network topology in IoV
2. Road aware, predictive, and proactive connection

Stable Path Scenarios:

Stable path connectivity scenarios are illustrated as shown below:

• The below figure (shown left side) is a scenario where the devices are under same cell and in coverage, which want to communicate. The below figure (shown right side) is a scenario where the devices are under same cell and one oft them is out of coverage, which want to communicate. 

• The below figure explores the Device to Device communication where a device 1 wants to communicate device-4 and both of them reside under a different Cell node. In this case, the packet is forwarded from one edge vEPC to another. This way the connectivity is provided as follows:

• The below scenario explains the same as immediate previous scenario but the only difference among them is that one of the device is out of coverage and proximity service plays the role of provisioning the location of such devices.

• The below figure shows the direct communication between the devices which reside under different Cells. The below path was provided as a result of proactive approach that we propose in our system. The major difference between the below two scenarios is that in such cases, we don't require the involvement of Edge vEPC in order to forward the packet to another road segment, thus reducing the latency and improving the performance in terms of bandwidth and efficient resource usage of the cellular spectrum. Both the devices are in coverage.

• The below figure also shows the direct communication between the devices which reside under different Cells. The below path was provided as a result of proactive approach that we propose in our system. The difference from previously mentioned scenario is that one of these devices are out of coverage. In this case also, the benefits to reduce the latency and efficient resource usage were achieved.

Recent space activity

Links

• Akraino Website
• Documentation
• Community Meetings & Calendar
• Join LF Edge
• Network Cloud Family Seed Code (Network Cloud Blueprint)