Your SlideShare is downloading. ×
0
Highway Emission Monitoring System using EJB 3.0
Highway Emission Monitoring System using EJB 3.0
Highway Emission Monitoring System using EJB 3.0
Highway Emission Monitoring System using EJB 3.0
Highway Emission Monitoring System using EJB 3.0
Highway Emission Monitoring System using EJB 3.0
Highway Emission Monitoring System using EJB 3.0
Highway Emission Monitoring System using EJB 3.0
Highway Emission Monitoring System using EJB 3.0
Highway Emission Monitoring System using EJB 3.0
Highway Emission Monitoring System using EJB 3.0
Highway Emission Monitoring System using EJB 3.0
Highway Emission Monitoring System using EJB 3.0
Highway Emission Monitoring System using EJB 3.0
Highway Emission Monitoring System using EJB 3.0
Highway Emission Monitoring System using EJB 3.0
Highway Emission Monitoring System using EJB 3.0
Highway Emission Monitoring System using EJB 3.0
Highway Emission Monitoring System using EJB 3.0
Highway Emission Monitoring System using EJB 3.0
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Highway Emission Monitoring System using EJB 3.0

329

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
329
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. CmpE 275 Fall 2009Project 1Highway Emission Monitoring SystemTeam Name:Ants Shivanshu Singh 006488300 Dhaval Patel 006500481 <br />
  • 2. High-level system design<br />
  • 3. High-level system design<br />Measure Materials present in the Air and send this data to the DataRecorder at specific intervals of time.<br />
  • 4. High-level system design<br />Records incoming data from the sensors into a DB<br />
  • 5. High-level system design<br />Sensor Location Management component. It maintains sensor location coordinates.<br />
  • 6. High-level system design<br />Listens to PHS client requests and generates an XML file containing sensor readings for the requested Region and within the requested Timeframe.<br />
  • 7. High-level system design<br />Generates KML files for the snapshot of the entire system at the requested Timestamp.<br />
  • 8. High-level system design<br />Acts as the communication medium, allowing asynchronous communication and Loose Coupling.<br />
  • 9. Deployment<br />Config.java<br />Stores the various configuration parameters which must be set before compiling and deploying.<br />Paths:<br />HOMELOCATION<br />it’s the root of the project location.<br />E.g. if the project name is Project1-Ants and the path of this folder is /Users/shivanshu/LearningSpace/Project1-Ants then<br /> HOMELOCATION=“/Users/shivanshu/LearningSpace/Project1-Ants”<br />KML Templates:<br />For use by CCCListener to generate kml files.<br />Store kml template file for each highway at<br />HOMELOCATION/Templates/KML-files<br />Initialization:<br />Run hems.ant.simulation.SensorConfiguration.java<br />Stores the coordinates of sensors in the databse.<br />Jboss:<br />The system supports Jboss 5.1.0 and can be configured for JBoss4.2.3<br />
  • 10. Sensors<br />Two types:<br />CSU – measuring CO2, CO, NO and SO2<br />ASU – measuring Particulate matter<br />Frequency:<br />Each sensor will send data, which for reasons of modeling the actual system, will be generated in terms of 5 messages per sensor per 0.5 hour.<br />interval of ½ hour is towards giving the server enough time to process requests and persist the data so that an increasing backlog of messages waiting to be processed is not created.<br />can be adjusted accordingly by changing a property in the hems.ant.component.common.Config.java file.<br />Data Packet:<br />TextMessage; format: SensorId,Material,Value,Timestamp<br />System does not verify materialType in the system for flexibility of adding sensors and capabilities of measuring other materials to the sensors and aid adaptability to such changes.<br />SensorId:<br />hhhs-&lt;sensornumber&gt; (case sensitive)<br />sensor<br />sensor<br />sensor<br />sensor<br />
  • 11. Components<br />SCRecorder<br />Main sensor location management component.<br />reads the sensor/location queue for sensor location information<br />TextMessage; format: sensorId,Longitude,Latitude,Altitude<br />Enables the system to be updates on runtime for changes in sensor location.<br />
  • 12. Components<br />SCRecorder<br />
  • 13. Components<br />DataRecorder<br />Records incoming data from the sensor<br />Assumes that the data generation is being done at a set interval of time by all the sensors<br />Timestamp for an instance of data generation will be the same for all the sensors.<br />This is possible if the sensors synchronize their time with a central time sync service.<br />Interval can be set through the SENSORINTERVALMINUTESvariablehems.ant.component.common.Config.java file.<br />
  • 14. Components<br />DataRecorder<br />Checks for Threshold Values.<br />Robust against malformed messages.<br />
  • 15. Components<br />PHSListener<br />Responds to requests (which have to be put into phs/request JMS Queue by the client)<br />Generates XML containing sensor readings for sensors in the given timeframe and region<br />Location: HOMELOCATION/PHS-files/PHS-yyyy-mm-dd-hh-mm-ss.xml<br />Format:&lt;phs_data&gt;<br /> &lt;entry&gt;sensorId,materialType,value,timestamp&lt;/entry&gt;<br /> ….<br /> &lt;/phs_data&gt;<br />
  • 16. Components<br />PHSListener<br />
  • 17. Components<br />CCCListener<br />Responds to requests (which have to be put intoccc/request JMS Queue by the client)<br />Generates KML for each highway for the snapshot of the system at the requested timestamp.<br />Location: HOMELOCATION/CCC-files/highwayname-yyyy-mm-dd-hh-mm-ss.kml<br />Threshold Values<br />Shows if a certain value goes below or above threshold. <br />
  • 18. Components<br />CCCListener<br />Crosses Threshold<br />Within Threshold<br />
  • 19. Future Work<br />PHS & CCC:<br />Asking the client to specify the file location with the desired filename or actually transfer it to the client.<br />CCC:<br />Currently only 101, 680 and 880<br />Future work may include generation of KML files for all the highways for which initial kml files are provided, making it a generic tool.<br />DB tuning / alternate persistence and archiving strategies<br />Clustering<br />Web Client for Sensor Location Management<br />
  • 20. Q ?<br />Thank You<br />Team Name: AntsShivanshu Singh 006488300Dhaval Patel 006500481<br />

×