1 / 28

QoS-Aware Publish-Subscribe Service for Real-Time Data Acquisition

QoS-Aware Publish-Subscribe Service for Real-Time Data Acquisition. Xinjie Lv, Xin Li, Tian Yang, Zaifei Liao, Wei Liu, Hongan Wang. Outline. Expression of QoS of Pub-Sub Enforcement of QoS of Pub-Sub Case Study-A simple application with three requirements Conclusion. Related works.

idana
Télécharger la présentation

QoS-Aware Publish-Subscribe Service for Real-Time Data Acquisition

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. QoS-Aware Publish-Subscribe Service for Real-Time Data Acquisition Xinjie Lv, Xin Li, Tian Yang, Zaifei Liao, Wei Liu, Hongan Wang

  2. Outline • Expression of QoS of Pub-Sub • Enforcement of QoS of Pub-Sub • Case Study-A simple application with three requirements • Conclusion • Related works

  3. Publish-Subscribe Service • Applications:

  4. Why Publish-Subscribe Service • Advantages • Space decoupling do not need to know each other. • Time decoupling do not need to be actively participating in the interaction at the same time. • Synchronization decoupling publishers are not blocked and subscribers can get asynchronous notification.

  5. Existing Models and Systems • Models • CORBA Event Service • CORBA Notification Service • Java Message Service (JMS) • Systems • Cambridge Event Architecture (CEA) • Distributed Asynchronous Collections (DAC) • Scalable Internet Event Notification Architectures (SIENA)

  6. Problem • Limited support for the expression of Quality of Service (QoS) parameters • Limited support for the enforcement of QoS parameters • Limited support for the Real-Time and active capabilities

  7. Expression of QoS-DDS • Data Distribution Service • Specification from the Object Management Group (OMG) • Aiming at users requiring data-centric publish-subscribe communications • Enumerating and providing formal definitions for the QoS settings

  8. Outline • Related works • Enforcement of QoS of Pub-Sub • Case Study-A simple application with three requirements • Conclusion • Expression of QoS of Pub-Sub

  9. Expression of QoS-DDS • Data-Centric Publish-Subscribe (DCPS): efficient delivery of the proper information to the proper recipients. • Data Local Reconstruction Layer (DLRL): integration into the application layer. DCPS conceptual model

  10. Expression of QoS-DDS • Supported QoS of DDS

  11. Outline • Related works • Expression of QoS of Pub-Sub • Case Study-A simple application with three requirements • Conclusion • Enforcement of QoS of Pub-Sub

  12. Enforcement of QoS-QRTPS • QoS-aware Real-Time Publish-Subscribe (QRTPS) service based on an active real-time database named Agilor • Overview of Agilor • Real-time Event-Condition-Action (RECA)

  13. Enforcement of QoS-Agilor • kernel modules and critical services in Agilor

  14. Enforcement of QoS-RECA • Primitive events in Agilor: • system events • method events • custom events • Extension of Complicated Temporal Events • Durative event, Durative sequence • Durative conjunction, Durative disconjunction • Durative between

  15. Enforcement of QoS-RECA • Primitive conditions in Agilor: • Selection condition: OP.Gas>20 • Aggregation condition: Max(OP.smog)>100 • Join condition: OP1.Pressure= OP2.Pressure • Transition condition: OP1.Gas> OP1.GetLast (Gas) • Application-specific condition

  16. Enforcement of QoS-RECA • Actions in Agilor: • database operations: deletion, update • external actions: publish data, signal an alarm. • deadline assigned to the action: relative to the occurrence time of the triggering event.

  17. Enforcement of QoS-RECA • Coupling Modes in Agilor: CMEC: Event-Condition; CMCA: Condition-Action CMEA: Event-Action; CMRR: Rule-Rule • Semantic for RECA Rules Rule::=BEGIN RULE <RuleName> VALUE <Value> WHEN <Event> IF <Condition> CMEC [immediate|detached] CMEA [immediate|detached] THEN <Action> WITHIN <Deadline> CMCA [immediate|detached] CMRR [immediate|concurrent] END RULE

  18. Outline • Related works • Expression of QoS of Pub-Sub • Enforcement of QoS of Pub-Sub • Conclusion • Case Study-A simple application with three requirements

  19. Case Study-Overview • Real-Time monitoring in a coal mine

  20. Case Study-Requirements • Three requirements: 1.Late-joining applications shall receive meta information about its sensors automatically; 2.Receiving gas sensor data every 500ms and temperature data every 1000ms; 3.If no data from most-trusted sensor source is received within 4000ms, temperature data shall automatically be received from another Observation Point (OP).

  21. Case Study-Data Structures • Gas : transmitting the sensor readings • GasSensorlnfo :containing meta-information to interpret the sensor data correctly

  22. Case Study-QoS Parameters

  23. Case Study-Expressing inRECA

  24. Case Study-Expressing inRECA

  25. Case Study-Application Screenshot

  26. Outline • Related works • Expression of QoS of Pub-Sub • Enforcement of QoS of Pub-Sub • Case Study-A simple application with three requirements • Conclusion

  27. Conclusions • Expressing QoS with DDS • Enforcing QoS policy with Agilor • Improving Real-time and active capabilities with RECA • Evaluating QRTPS for a Real-time monitoring

  28. Thank you

More Related