1 / 45

A Sensor-Centric Grid Middleware Management Systems by

ANABAS. A Sensor-Centric Grid Middleware Management Systems by Geoffrey Fox, Alex Ho, Rui Wang, Edward Chu and Isaac Kwan (Anabas, Inc. and Indiana University) In collaboration with Ball Aerospace. ANABAS. Motivation Information Age versus Integration Age

dcraig
Download Presentation

A Sensor-Centric Grid Middleware Management Systems by

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ANABAS A Sensor-Centric Grid Middleware Management Systems by Geoffrey Fox, Alex Ho, Rui Wang, Edward Chu and Isaac Kwan (Anabas, Inc. and Indiana University) In collaboration with Ball Aerospace

  2. ANABAS • Motivation • Information Age versus Integration Age • Need for better intelligence for decision support • Increased use of low cost sensors in commercial • and defense environments • Support the concepts of • User-Defined Operational Pictures (UDOP), and • Common Operational Pictures (COP) • Interoperability through Grid and Cloud middleware

  3. ANABAS • UDOP - User-Defined Operational Pictures • Enables situational awareness and facilitates a user • to easily choose, create, visualize and present • decision-focused views of an operation or mission • COP – Common Operational Pictures • Enables sharing of situational awareness operational • pictures with relevant personnel

  4. ANABAS • An operational environment refers to the environment where • stakeholders of an operation reside. • Making accurate decisions in a stressful operational • environment involves many processes including but • not limited to • * collecting, decomposing, analyzing, • * visualizing, organizing, sharing of information, and • * deriving new information

  5. ANABAS • Objectives • Design and develop an sensor-centric grid middleware • enabling framework to enable easy • development • deployment • management • real-time visualization • organization • presentation • of collaborative geo-coded sensor grid applications with • UDOP/COP capabilities.

  6. ANABAS • Our definition: • A sensor is a time-dependent stream of information with a geo-spatial location. • A static electronic entity is a broken sensor with a broken GPS! i.e. a sensor architecture applies to everything

  7. ANABAS UDOP Architecture

  8. ANABAS • Sensor Layer • Sensors provide raw information which is captured • dynamically in different environments. • Metadata Layer • Describes the properties of sensor; gives meaning to • raw data collected from sensors. Makes information • filtering possible. • Information Management Layer • Transport messages from sensors to applications • Messaging facilities that supports multi-protocol • Facilities for sensor management such as deploying • and disconnecting sensors • Application Layer • UDOP applications

  9. ANABAS SCGMMS – Sensor-Centric Grid Middleware Management System SCGMMS API allows application developers to retrieve sensor data and metadata about sensors. The SCGMMS SSAL facilitates sensor developers to define sensor metadata for application-level filtering and expose sensor services to applications.

  10. ANABAS NaradaBrokering (NB) provides the transport-level messaging support for SCGMMS. NB supports a distributed message-based overlay network with a publish-subscribe messaging model. With the help of NB different components of SCGMMS can be integrated, deployed and works collaboratively in a distributed manner. For NB information, see IU exhibition booth for details.

  11. ANABAS Sneak preview of sample applications developed using the SCGMMS API

  12. Anabas, Inc. Anabas Inc. Alex Ho, (415) 637-4198 alexho@anabas.com or Dr. Geoffrey Fox, (812) 856-7977 gcf@indiana.edu Ball Aerospace & Technologies Corp. Gary Whitted, (937) 320-6022 gwhitted@ball.com or Timothy Choate, (937) 320-7081 tchoate@ball.com

  13. ANABAS Distributed Architecture for Data Access

  14. ANABAS Distributed Architecture for Data Access

  15. ANABAS • Data Model • Sensors in different geo-spatial locations continuously publish data into the distributed brokering network. • SCGMMS routes relevant data to all connected applications according to their UDOP requirements. • Applications are notified for each data arrival through data listeners. • Some sensors are capable of receiving requests from applications and perform some actions in return. These actions are sensor-specific. • Sensors data could be routed to other computational services for further processing.

  16. ANABAS • Data Selection and Filtering • Each UDOP application is only interested in certain • domain-specific information extracted from the large • raw data pool supported by SCGMMS. • Filtering follows the request/response model where • an application user defines a “filter” • the filter is sent to SCGMMS as a request • SCGMMS responds with sensors that match the filter • the application subscribes to data of these sensors • through the SCGMMS API

  17. ANABAS An example of a filter in SCGMMS A decision-maker wants to locate all GPS and RFID sensors in US or UK, the corresponding query looks like:

  18. ANABAS A sample UDOP-capable sensor-centric application provides a GUI to support ease of filtering.

  19. Sensor-Centric Grid Middleware Management System Architecture ANABAS

  20. ANABAS Grid Builder (GB) GB is a sensor management module which provides services for • Defining the properties of sensors • Deploying sensors according to defined properties • Monitoring deployment status of sensors • Remote Management - Allow management irrespective of the location of the sensors • Distributed Management – Allow management irrespective of the location of the manager / user

  21. ANABAS Sensor Grid (SG) • Sensor Grid communicates with • sensors • applications • Grid Builder • to mediate the collaboration of these 3 logical modules. • Primary functions of SG are to manage and broker • sensor message flows.

  22. ANABAS Sensor Grid (SG) • Sensor/Sensor Grid Message Flow • SG keeps track of the status of all sensors when • they are deployed or disconnected so that applications • using the sensors will be notified of changes. • Sensor data normally does not pass through SG except • when it has to be recoded intentionally.

  23. ANABAS Sensor Grid (SG) • Application/Sensor Grid Message Flow • Applications communicates with SCGMMS via API, • which in turn communicates with SG internally. • Applications can define their own filtering criteria, • which will be sent to SG for discovering and linking • appropriate sensors logically. • SG forwards messages among relevant sensors • and applications. • SG updates applications if there are any changes of • relevant sensors.

  24. ANABAS Sensor Grid (SG) • Grid Builder/Sensor Grid Message Flow • Sensor properties are defined in GB. • Applications obtain sensor properties through SG. • SG sends application filtering requests to GB regularly • to obtain updated sensor information.

  25. ANABAS Sensor Grid (SG) • Application/Sensor Message Flow • SG provides each application with information of sensors they need according to the filtering criteria. • Applications communicates with sensors via the SCGMMS API.

  26. ANABAS Sensor Grid (SG)

  27. ANABAS

  28. ANABAS Grid Builder (GB) • GB is originally designed for managing Grid of Grids. • GB is extended to support sensor-centric grid. • The Grid which GB manages is arranged hierarchically • into domains. • Each domain is typically a PC which manages local • sensors. • Sensors can be deployed in any domain and accessible • from any domains.

  29. ANABAS Grid Builder (GB) • Domains have some basic components • Managers and Resources • Each resource is wrapped in a Service Adapter • Bootstrapping Service • Ensures the current domains are up and running. • It periodically spawns a health check manager • that checks the health of the system. • Registry • All data about registered services and SA are • stored in Registry. WS-Context is used for • persistency. • Processes messages for managing SA and update • SA status.

  30. ANABAS Distributed Geospatial Intelligence-Enabled User Defined Operating Pictures & Common Operating Pictures -- An illustrative demo in CTS 2008

  31. Anabas, Inc. Anabas Inc. Alex Ho, (415) 637-4198 alexho@anabas.com or Dr. Geoffrey Fox, (812) 856-7977 gcf@indiana.edu Ball Aerospace & Technologies Corp. Gary Whitted, (937) 320-6022 gwhitted@ball.com or Timothy Choate, (937) 320-7081 tchoate@ball.com

  32. Supported Services • Sensor Services: • RFID • GPS • Wii remote • Webcam video • Lego Mindstorm NXT • Ultrasonic • Sound • Light • Touch • Gyroscope • Compass • Accelerometer • Thermistor • Nokia N800 Internet Tablet • Computational Service • VED (Video Edge Detection) • RFID positioning

  33. ANABAS

  34. ANABAS

  35. ANABAS

  36. ANABAS

  37. ANABAS

  38. ANABAS

  39. ANABAS Acknowledgment We thank Bill McQuay of AFRL, Gary Whitted of Ball Aerospace, Shrideep Pallackara and Marlon Pierce for their advise and support.

  40. ANABAS

  41. ANABAS

  42. ANABAS

More Related