This document outlines the design and development timeline of a framework to allow communication between vehicles using different wireless technologies. The timeline shows research starting in October through final testing and completion in May. Key aspects include developing Android and Python applications, setting up WiFi and Bluetooth communication between Raspberry Pis, integrating a database, and testing the security, performance and reliability of the system. Diagrams show the system architecture and communication flows between mobile devices and Pis.

1. Imagine living in a world where
cars could talk

2. Outline
Quick Recap
Overview of the System
Timeline
February
March
April
May
Class Diagrams
Interaction Diagrams
Security
Efficiency
Testing
2

3. 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

4. Operating Environment 4
Communication Module Sensors Processing Module

5. Overview of the System 5
WIFI
Bluetooth Bluetooth
Zigbee
Devices
Sensors
Devices
Sensors

6. Overview of the System 6
Application layer
Phone

7. Timeline 7
Oct Nov Dec Jan Feb Mar Apr May
Research
& review
similar
projects
Finish SRS
Document
Finalizing
Platform
POC
Applications
Finalize
all
Documents
Working
on
network
platform
Testing
Final
Presentation
and Demo
Finished
To do
Legend

8. 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

9. 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

10. 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

11. 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

12. 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

13. May
 Spare time for any backlog
 Receiving applications from CS Students
 Testing the complete framework with the
applications
13

14. System Architecture 14
Application
Framework
R
Raspberry Pi
Abstraction Layer
Comm
Module DB Device
Manager
Operating System
Network interfaces Devices/Sensors
Android
Application
Smart
Phone

15. 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 Bluetooth
MySQL
SQL lite
Oracle

16. Create Connection (PI
and mobile)
16
Mobile Pi
Run App
Turn on Bluetooth Msg
Turn on
Ready
Check Bt
Permissions
Pair
Challenge with pin
Enter pin
Pin No. Pin no.
(challenge Response)
Paired

17. Data exchange between Mobile
and Pi
17
Mobile Pi
Send traffic status
Send Data
Data Base
Store traffic updates
Data
Retrieve data
Notify User
get_hash()
if Data new
then Store

18. Ad-hoc communication
between Pi’s
18
Pi
1
Pi
N
Retrieve data
Send Data
Data Base
N
Check
Validity
Store if Valid
Data base
1
Data hashed

19. ER-Diagram of Traffic app 19
ID Check
Traffic_Updates
Sum
City
Address
Speed
Time Stamp
Longitude
Latitude
Mobile Id
Reported

20. Security
 Bluetooth pairing (static pin)
 Security = CIA
 Integrity
 Encryption
 Availability
 Simple IDS
20

21. Efficiency
 Detecting duplicates
 Approximation using “haversine formula”.
 Hashing using SHA256
 Indexing on the checksum
 Garbage collection
21

22. Testing Strategy 22
Testing Plans
Defect Testing User Testing
Validation
Testing

23. 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.

24. 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

25. 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).

26. 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.

27. Thank you
27