v2v design presentation final
TRANSCRIPT
Outline
Quick Recap
Overview of the System
Timeline
February
March
April
May
Class Diagrams
Interaction Diagrams
Security
Efficiency
Testing
2
The Idea
Thesis Statement
“We aim to Design a framework that functions as a platform to allow developers
to build applications on an ad-hoc-vehicle to vehicle network”
3
Timeline 7
Oct Nov Dec Jan Feb Mar Apr May
Research
& review
similar
projects
Finish SRS Document
Finalizing
PlatformPOC
Applications
Finalize
all Documents
Working
on
network
platform
TestingFinal
Presentation
and Demo
Finished
To do
Legend
Timeline 8
Oct Nov Dec Jan Feb Mar May
Research
& review
similar
projects
Finish SRS Document
Working on
networking
modules
Final
Testing
Finalize
all Documents
Practice
Android &
OOP Python
development
Finalizing
Platform &
POC
applications
Finished
To do
Legend
Apr
February
Read about Android developing and developed
simple practice apps.
Application to discover Bluetooth devices via a
Linux based OS and an android phone
Read about different modes of Wi-Fi
OOP in Python
9
March
Developing mobile applications
Traffic app
Challenges
First experience in RF-com
Bluetooth dongle Mac Address “00:15:03:0C:BF:EB”
Solution: bdaddr
Pairing PIN code
Address is null if no internet
Solution: install maps on Pi
Disable plugins Pnat
10
March
Tried different modes of Wi-Fi
Created ad-hoc network between Pi’s
Challenges :
IP address assignment space
Transfer files between Pi’s
Database:
MySQL
Created abstraction Layer using python
Implementing all database function in python
Challenges:
Integrating with Wi-Fi module to send or receive
11
April
Ad-hoc-ed more than one PI via Wi-Fi
Completed a traffic application
Roadmap ahead
Build the mesh network using Zigbee
Developing Mobile application to control Pi
Group talk application
Publish Framework to CS students
12
May
Spare time for any backlog
Receiving applications from CS Students
Testing the complete framework with the
applications
13
System Architecture 14
R
Application
Framework
Comm
Module DBDevice
Manager
Operating System
Raspberry Pi
Abstraction Layer
Devices/SensorsNetwork interfaces
Smart
Phone
Android Application
Class Diagrams 15
Application
Data base
Createtable()
selectmulRows()
Updaterow()
deleteRecord()
Deletetable()
Validate(data)
Garbagecollector(period)
Communication module
Establishconnection()
Send()
Receive()
Broadcast()
Devices
Init()
Senddata()
ReceiveData()
Mobile GPS OBD2
Zigbee Wi-Fi BluetoothMySQL
SQL lite
Oracle
Create Connection (PI
and mobile)16
Mobile Pi
Run App
Turn on Bluetooth Msg
Turn on
Ready
Pair
Challenge with pin
Enter pin
Pin No. Pin no.
(challenge Response)
Paired
Check Bt
Permissions
Data exchange between Mobile
and Pi17
Mobile Pi
Send traffic statusSend Data
Data Base
Store traffic updates
Data
Retrieve data
Notify User
get_hash()
if Data new
then Store
Ad-hoc communication
between Pi’s18
Pi
1
Pi
N
Retrieve data
Send Data
Data Base
N
Store if Valid
Check
Validity
Data base
1
Data hashed
ER-Diagram of Traffic app 19
Traffic_Updates
ID Check
Sum
City
Address
Speed
Latitude
Longitude
Time Stamp
Mobile Id
Reported
Security
Bluetooth pairing (static pin)
Security = CIA
Integrity
Encryption
Availability
Simple IDS
20
Efficiency
Detecting duplicates
Approximation using “haversine formula”.
Hashing using SHA256
Indexing on the checksum
Garbage collection
21
Validation Testing 23
Phase 1: System Inspection
Peer review(At least 2 times).
Time: Interleaving with development.
Phase 2: Requirements testing (In lab)
Generating test cases using “Tester++”.
Time: end of April.
Phase 3: Requirements testing (Deploying
in vehicles)
Deploying the devices in the vehicles.
Time: First week of May.
Defect Testing 24
Phase 1: Performance Testing (In lab)
Test under maximum work load.
“Tester++” will be used in this phase.
End of April.
Phase 2: Security Testing
First week of May.
White-box testing
Code auditing
Black-box testing
Metasploit
Nessus
Defect Testing 25
Phase 3: Reliability Testing
Interleaving with in-vehicles requirements
testing.
Testing in real life environment for 2 weeks
(1st May to 14th May)
The reliability will be measured using MTBF
(Mean Time Between Failures).
User Testing 26
The framework will be released to all CSE students.
A tutorial will be given to all students about the
framework.
The students will be asked to find some ideas and
develop their own applications on top of our framework.
They will rate the different parts of the framework.