Outline-1 I. INTRODUCTION II. AN OSGI OVERVIEW III. COMPOSITION SCENARIO IV. SPECIFYING OSGI SERVICE COMPOSITION: A BPEL STYLE SOLUTION
Outline-2 V. PROBLEMS REVEALED: A SEMANTIC SOLUTION VI. THE OWL-OS/OSGI FRAMEWORK VII. A SEMANTIC SOLUTION FOR AUTOMATIC SEMANTIC OSGI SERVICE COMPOSITION VIII. DISCUSSION
I. INTRODUCTION (i) the communication among all devices in home is easy because it supports different widespread protocols (ii) it defines a cooperative model where applications can dynamically discover and use services provided by others (iii) it is possible a flexible remote management of these applications and the services they provide
III. COMPOSITION SCENARIO-1 At John's house, equipped with fire and intrusion detectors, there is a Home Security service. (i) In case of fire, the service triggers the ringing alarm, unlocks the doors, calls the fire station and informs John by using the most appropriate device (mobile phone, car navigator, etc.) (ii) In case of intrusion, the service locks the doors, calls the police station and also informs John.
IV. SPECIFYING OSGI SERVICE COMPOSITION: A BPEL STYLE SOLUTION A. Overview of BPEL B. Our proposal: a syntactic approach C. Registering a OSGi composite service D. Invoking a OSGi composite service E. BPEL definition
B. Our proposal: a syntactic approach This composite service is registered in the framework not needing to be implemented by any bundle, i.e. it could be considered a virtual bundle. a particularized BPEL Composition Engine is responsible for registering and executing OSGi composite services.
V. PROBLEMS REVEALED: A SEMANTIC SOLUTION current OSGi specification is not enough to support the required flexibility: (i) to find the most appropriate services and (ii) to know how to interact with them automatically at run-time. defined a semantic OSGi framework, coined OWL-OS/OSGi framework
A. Registering semantic OSGi services B. Semantic discovery of OSGi services C. Invoking OSGi services allows the requester bundle to discover the name of the public method and the parameters in order to construct the invoking primitive
VIII. DISCUSSION-1 Implement Platform- OSCAR ActiveBPEL engine Protégé OWL API We have implemented a semantic version of the OSCAR registry Use Jess and JessTab plug-in
VIII. DISCUSSION-2 propose enriching the OSGi Service Registry with semantic descriptions, i.e. turning OSGi into a Semantic OSGi platform and allowing the semantic composition of service With a semantic description of contexts, the system not only can react to that contexts in a better way, but we can also provide reasoning over contexts which improves the quality of the reacting activities.