Task (todo/done)

Explore the networking plugin options that can be used in our proposed scenarios of vehicles:

• Multus (multiple virtual nics/interfaces)
• OpenShift-SDN CNI
• etc

1. Architecture - figures/explanation
2. Components - figures/explanation
3. Scenarios - figures/explanation
4. Implementation - plan/approach
   1. container vehicles
   2. maps (Jeju/Udo islands)
   3. proximity services
   4. broadcast content
   5. epc on the edge sites
   6. location prediction model
   7. sdn
5. Relevant Blueprints
6. Contributors
7. References
8. Ask Questions - table of questions
9. Tasks

Specifications:

1. Vehicle Class
2. Attributes
   
   1. location [long., lat.]
   2. direction [north/east,west/south]
   3. velocity [m/s]
   4. possible directions [top: north, right: east, left: west, bottom: south]
   5. etc.
3. Methods:

   • turn

     Inputs	Outputs	Actions/Effects	Description
     vehicle id direction	next location	decrease velocity decelerate by some factor while turning update the location#

   • accelerate

     Inputs	Outputs	Actions/Effects	Description
     vehicle id direction acceleration factor	new location	increase velocity update the location#

   • broadcast

     Inputs	Outputs	Description
     vehicle id bits	none	The udp client will be responsible to broadcast the traffic to the gateway. The proximity/other service at the edge node is responsible to decide on which edge nodes does the traffic need to be broadcasted

   • park/stop

     Inputs	Outputs	Actions/Effects	Description
     		decrease velocity to zero update the location#

   • update the location

     Inputs	Outputs	Actions/Effects	Description

   • sync. location to proximity server

     Inputs	Outputs	Actions/Effects	Description
     vehicle id location	response of success/failure	vehicle location must be updated on the proximity server	updates the current location to server after every 2 seconds.

   • etc.

Method details:

1. Turn (to describe)
2. Accelerate (to describe)
3. Broadcast (to describe)
4. Park/Stop (to describe)
5. Update the location
6. Sync. the location to proximity server
7. etc.

1. Downloaded .osm/.mbtile formatted files for Jeju/Udo Island
2. GIS-based maps
   1. set locally
   2. containerize it (Folium-based map server)
   3. find .shp for Jeju/any
   4. use wgs84/epsg4326 format (geojson)
   5. traffic data for vehicles (Jeju/any)
   6. pandas, geopandas, folium
   7. graphical analysis of traffic (map/graphs)
   8. interactive layers (i.e. ___)
3. Setup the OpenStreetMap (PostgreSQL). Steps to setup locally.
   
   1. on local system
   2. containerize it
   3. make it accessible to the cars
4. Analyze/correct the .osm maps for Jeju/Udo Islands
5. Search ways for creating roads, intersection etc
6. Implement roads. intersection etc
7. Explore implementation options to dynamically move container vehicles
8. Consider the RSUs/BSs in this architecture

1. Specify the criteria of updating locations of container vehicles
2. Describe the the selected standard approach for implementing proximity service

1. Explore the OpenShift-SDN CNI
2. Routing logic as a Northbound application
3. Apply routing to:
   1. vehicle container network interfaces
   2. RSU container network interfaces
4. Test the validity of routing