1 / 17

Philip Alb

Diplomarbeit im Studiengang Medieninformatik. Remote Configuration Management Conception & Development of a Service Application based on OSGi. Philip Alb. Remote Configuration Management– 1. Agenda. Overview: What and Why How: Key Components Semantic Model A Scenario OSGi and UPnP

merrill-shaw
Download Presentation

Philip Alb

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. Diplomarbeit im Studiengang Medieninformatik Remote Configuration Management Conception & Development of a Service Application based on OSGi Philip Alb Remote Configuration Management– 1

  2. Agenda • Overview: What and Why • How: Key Components • Semantic Model • A Scenario • OSGi and UPnP • Implementation • Conclusion and Outlook

  3. Overview: What and Why Maintain Devices Non-Standard Devices in Remote Networks • Analyze device • Find compatible Software • Update device Growing Home Networks • New „intelligent“ devices • Very heterogeneous complex home networks • Users can‘t do the job • Device Vendors are responsoble for updates 

  4. Home network

  5. Challenges • Little User Involvment • Flexible Technology Integration • Open Solution  Without Open solution • User device might not supported by his favorite Service Provider • Service Provider has to support many solutions instead of concentrating on one

  6. Key Components Semantic Model • Common Language (for people and machines) • Common Understanding About Involved Entities OWL Ontology Self Organizing Network Components • Zero-Configuration UPnP Enabled Devices Protocol Integration OSGi plattform

  7. Semantic Model 1 Ontology • „Model of a specific field of knowledge” (concepts and how they are related together) • Vendor-independant View on RCM Development • Web Ontology Language (OWL) • Protégé + OWL Plugin • Reasoner • Checks consistence

  8. Semantic Model 2 Web Ontology Language (OWL) • XML based • Hierarichal Class Model with Classes, Instances and Properties • Rules define how classes are related together • „Vegetarian pizza can have no other than vegetable toppings“ • Reasoner checks rule

  9. Semantic Model 3 Service Ontology Classes: Person, Organization, Device, Service, Software... • Devices: • Services: • Equivalent Classes „Different name but same meaning“

  10. Semantic Model 4 Inferred Classmodel • Defined Subclasses • Inferred Subclasses Ontology - and now? • Build a knowledge base • Map to other models, e.g. to XMI/UML for better visualization • Use as base for an application • Generate model consistent Java classes

  11. Repair Service Scenario • Owner • Device • Assistant • Analyzes device • Gets compatible Software • Installs it on device • Service Provider • Knows the right Software • Provides Software Repository • Gateway • Central Point of control

  12. UPnP & OSGi • Universal Plug & Play Communication Technology • Based on Open Standards: HTTP, SOAP, XML • Self Discovery of Location and Functionality no network configuration no driver installation • Plug‘n‘Play for local Networks! Open Service Gateway initiative • Java Framework & Software Container • Cooperation Model: Service Registry: • Share functionality through services • Flexible Technology Integration OSGi: UPnP: (how software is running) (how softare is communicating) complementary technologies match perfectly!

  13. OSGi & UPnP 2 • UPnP Base Driver • Import/Export: Automatic Mapping between UPnP and OSGi World • Access of UPnP Services like normal OSGi services 1. Discover a UPnP device 2. Create Object as Proxy 3. Register as OSGi Service Bundles can use UPnP Service 1. Bundle registers Service 2. Base Driver is notified 3. Advertises to UPnP network Control Point can use OSGi Service

  14. Service Application 1 Washing Machine • UPnP Standards for White Goods not published  Simulator • Services: Wash, Information and Update • Update via HTTP Upload (every UPnP device has ist own HTTP Server) Service Application on Gateway • Web Application: Control of update process with Web Browser • Control Point: Access device (and Service Provider)

  15. Application 2 1.Get all updateable devices 2.Get devices from registry 1.GetSoftware ( DeviceID) 2.Get DevInfo from device via BaseDriver 3.Get Software List From SP 1. UpdateDevice ( DeviceID, SoftwareID) 2. Download Software form SP 3. Upload Software to device

  16. Conclusion & Outlook Challenges: Key Components: • Little User Involvment UPnP • Flexible Technology Integration OSGi • Open Solution Common Description Future work: • Continue Ontology development • Service Provider Access, e.g. with JXTA Bundle • Porting of gateway to Embedded Plattform • Bluetooth Bundle • Security: Privacy in OSGi Spec only a footnote!

  17. Thanks for your attention!

More Related