1 / 23

Context-aware management of e-services (Tempura reengineering)

Context-aware management of e-services (Tempura reengineering). Vladimir Valkanov University of Plovdiv. DeLC Project. Main goal : delivering e-services to support e-learning ; DeLC architecture : distributed system, containing fixed and mobile nodes ;

nodin
Télécharger la présentation

Context-aware management of e-services (Tempura reengineering)

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. Context-aware management of e-services(Tempura reengineering) Vladimir Valkanov University of Plovdiv 13th Workshop "SERE" Bansko, 26-31 Aug. 2013

  2. DeLC Project • Main goal: delivering e-services to support e-learning; • DeLC architecture: distributed system, containing fixed and mobile nodes; • Mobile node: providing mobile access to the services, through intelligent wireless network based on InfoStation architecture; 13th Workshop "SERE" Bansko, 26-31 Aug. 2013

  3. Infrastructure of DeLC 13th Workshop "SERE" Bansko, 26-31 Aug. 2013

  4. Mobile node middleware 13th Workshop "SERE" Bansko, 26-31 Aug. 2013

  5. Main goal • To expand the middleware with intelligent agents, which are able to detect and manage time aspects of delivering educational services and content in distributed InfoStation network. 13th Workshop "SERE" Bansko, 26-31 Aug. 2013

  6. Tasks • To investigate and specify time aspects of the mobile node • Choose a proper formalism to manage the time components in the system • To find a proper approach for realisation • To create architecture • To create a prototype • To integrate in DeLC 13th Workshop "SERE" Bansko, 26-31 Aug. 2013

  7. Time aspects • Scenarios • They specify the functionality of our communication environment (InfoStations) • During the execution of a service different local events could happened : • Getting in range of an IS • Getting out of range of an IS • Change the mobile device • The existing middleware could react to various events, but he is unable to represent them in time order. • No management mechanism • In the scenario point of view the problem is to manage scenario change and execution 13th Workshop "SERE" Bansko, 26-31 Aug. 2013

  8. Choosing a proper formalism • Interval Temporal Logic (ITL) • Ben Moszkowski– Computer Laboratory, University of Cambridge • What is ITL: • First order logic with added time dependent operators like “sometimes” , “always”, “next” … • Considering time as a discrete sequence of points in time called intervals • For ITL there is an interpreting mechanism and its program realisation called Tempura. 13th Workshop "SERE" Bansko, 26-31 Aug. 2013

  9. Tempura • Imperative programming language which use subset of ITL: • First interpreter was written in Prolog • Current version: • Roger Hale, Ph.D. thesisin Cambridge , 1984-1985 г., C • Maintenance: Antonio Cau, STRL, De Montfort University • AnaTempura • The centralize surrounding environment of Tempura 13th Workshop "SERE" Bansko, 26-31 Aug. 2013

  10. AnaTempura 13th Workshop "SERE" Bansko, 26-31 Aug. 2013

  11. Approach • Three possible ways: • Wrapping Tempura with I/O Java classes • Creating a complete new Java version of ITL interpreter • Reengineering the existing C-based version of Tempura 13th Workshop "SERE" Bansko, 26-31 Aug. 2013

  12. Why reengineering? • Missing documentation and specification of the basic algorithms used in the interpreter • Homogeneous environment • Using proven system and already prepared test cases 13th Workshop "SERE" Bansko, 26-31 Aug. 2013

  13. Reengineering in steps • Iterative hand-made translation • C to Java without changing the imperative structure of the system • ImperativeJava to OO Java • OO Java to AO Java (JADE) 13th Workshop "SERE" Bansko, 26-31 Aug. 2013

  14. Approach schema 13th Workshop "SERE" Bansko, 26-31 Aug. 2013

  15. Schema of the original Tempura C-code 13th Workshop "SERE" Bansko, 26-31 Aug. 2013

  16. Schema ofOO Java version 13th Workshop "SERE" Bansko, 26-31 Aug. 2013

  17. Prototype • ImperativeJava interpreter • Standard Test Suite • ОО Java interpreter • Extended Test Suite , received from STRL 13th Workshop "SERE" Bansko, 26-31 Aug. 2013

  18. AO Java interpreter • Possibilities • Transform the interpreter in a single agent • Or multi-agent system • InfoStationmiddleware • To substitute AnaTempura • Decentralized delivery of attribute values ​​from the environment • Development framework • JADE • BDI architecture • BDI4JADE plug-in 13th Workshop "SERE" Bansko, 26-31 Aug. 2013

  19. Package suggestion 13th Workshop "SERE" Bansko, 26-31 Aug. 2013

  20. Transform into package structure 13th Workshop "SERE" Bansko, 26-31 Aug. 2013

  21. AO Tempura life-cycle suggestion 13th Workshop "SERE" Bansko, 26-31 Aug. 2013

  22. Next steps • Realisation of an AO Java interpreter prototype • Integration into DeLC agent middleware • Testing in real DeLC environment 13th Workshop "SERE" Bansko, 26-31 Aug. 2013

  23. THANK YOU FOR YOUR ATTENTION 13th Workshop "SERE" Bansko, 26-31 Aug. 2013

More Related