1. Cloud Computing for agentbased Urban transportation
system
 Sujeet Poojari.

2. Index:






Introduction
Modules
UML Diagrams
Implementation
Future Scope
Conclusion

3. Introduction
Analysis 1
1960:
•Time of MainFrames.
•Traffic management shared the resource of one
computer in a centralised model.

4. Analysis 1
• Later,the size minituarised and TRANSYT model
came.
• An example:”SCOOT”

5. Analysis 1
•
•
•
•
•
SCOOT consisted of numerous single control points.
Disadvantage:
Time Consuming
Expensive ,so was Mainframe.
Less Efficient.

6. Analysis 2
• LAN (Ethernet) introduced.
• Hierachical model.
1973:

7. Analysis 2
Internet Era(2000s)+LAN:
Disavantage:
•Internet era caused lot of bandwidth wastage.
•Data space also was wasted as each device had its
independent data stored.

8. Analysis 3
• Agents:
• Agents were introduced.
• Direct communication to Web Server.
• So Communication costs and time reduced.

9. Analysis 4
• Cloud Computing(2010):
• Is a technique where the cloud(web server) stores
all the necessary data and softwares.
• The front-ends are given a virtual interface of
communicating with the data without themselves
containing the data.
• the details of the infrastructure in the “clouds” are
hidden.
• Eg:DropBox,Google Docs in Gmail etc.

10. Cloud Computing for
Traffic management
• Location-based Agents.
• PtMS(Parallel transportation Management System).
• Agents donot have to carry data storage.
• Cloud will contain all the traffic based data and
strategies in its databases.

11. Cloud Computing for
Traffic management
• The commuters (travellers) will be updated with
traffic route choices and Strategies.
• The commuters will also be informed about
temperature.
• Infact , commuters can upload the cloud with
occurences (accidents) and neccessary actions
can be taken.

12. Different modules
1.Agents:
•autonomous, mobile, and adaptive
• Authorized middleware applications.
•Location-based.
2.Commuters:
•Other front-end application.
•Travellers who are mobile.

13. Different modules
3. Strategic Manager:
•Remote based Application at the cloud.
• Handles the agents , adds and deletes agents.
•Checks authenticity of agents.
•Maintains multiple kinds of database for storing
various traffic strategies.

14. Flow Diagrams:
•Activity Diagram
•Sequence Diagram

15. Activity Diagram
C itizen
Subscri be to
traffi c alerts
Agen
t
System
login
select
locati on
update traffic
in
formation
Traffic Strategy
Man
ager
analy
se
traffi c data
alert th
e
su
bscribers
create new
traffi c rou
te
update th
e
subscriber

16. Sequence Diagram:
Citizen
Traffic Strategy
Manager
Agent
System
1: subscribe to traffic alerts
2: check user validity
3: subscription successful
4: login
5: check agent validity
6: login successful
7: update traffic information
8: store the information in db
9: analyse data according to location
10: alert the subscriber
11: create new traffic route
12: update the subscriber

17. Software requirements:
1. Back –end:
Strategic manager :SQL Server with a PHP browser
interface.
Java Database Connectivity(Jdbc driver).
2. Front-end:
• Front-end commuters : Android application
designed by using Eclipse IDE on windows.
•
•
The Agent application will be Android application

18. Applications
• Ambulance
• Hospitals

19. Future Scope
• Smart phones are owned by everyone today.
• Access have become speedy.
• Android is the new popular OS ,and will exist for
years to come.
• A software-controlled traffic management and
Mobile-user friendly application.

20. Conclusion