1 / 35

The Web Operating System Towards Wide Area Ubiquitous Computing

The Web Operating System Towards Wide Area Ubiquitous Computing. Joint work of

austin-barry
Download Presentation

The Web Operating System Towards Wide Area Ubiquitous Computing

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. The Web Operating System Towards Wide Area Ubiquitous Computing Joint work of P. Kropf, G. Babin, (University of Laval, Canada)J. Plaice (University of Sydney, Australia)H. Unger (University of Rostock, Germany)A. Mikler (University of North Texas, USA) S. Schubiger (University of Fribourg, Switzerland)O. Krone (Swisscom CT, Switzerland)

  2. Overview • Motivation • The WOS Approach • Resources • Warehouses • Eductive Engine • WOSNode, WOSpace • Web Components (WebComs) • Current Research Issues • Related, and Future Work, Conclusion

  3. Motivation • Success of the WWW is tremendous • Why not using WWW as platform for ubiquitous computing ? • Today: resources found on the Web are information only; interaction is limited • Tomorrow: use WEB as a Service Space: “The network is the computer”

  4. Motivation (cont.)

  5. Motivation (cont.) • Network Applications • WWW, email, video • Computational Applications • number crunching, distributed simulation • Virtual Entities • classrooms, companies • Knowledge based Applications • data mining, databases • Real Time Applications • process control real-time multimedia

  6. The WOS Approach • 5 Universities involved: Laval, Rostock, Texas, Sydney, Fribourg • “Operating System” for the Web • Runs on top of existing OS, Java • Bringing the resource-richness of the Web to the user • Bringing the computational potential of the Web to the user • Distributed and versioned

  7. Web Operating System - Warehouses • Resource database • Resource management • Resource cache • Passive Warehouses • storage for service information • information out of date, must be replaced • Active Warehouses • information obtained from which other warehouse • Adaptive Warehouses • user profiles and access statistics: update of information

  8. Web Operating System - Resources • Versioned Services • Applications • Platforms • Hardware • …

  9. Web Operating System - Eductive Engines • Provides services using a warehouse • Reactive system • Responds to requests • Eduction (Oxford English Dictionary): • “The action of drawing forth, eliciting, or developing from a state of latent, rudimentary, or potential existence; the action of educing (principles, results or calculations) from the data.” ?

  10. Web Operating System - WOS Node Eductive engine + Warehouse ?

  11. ? ? ? ? ? ? ? ? ? ? ? ? Web Operating System - WOSNet Network of WOS Nodes • Eductive engine • Warehouse

  12. ? ? ? ? ? ? ? ? ? ? ? ? Web Operating System - Operation

  13. ? ? ? ? ? ? ? ? ? ? ? Web Operating System - Operation ?

  14. ? ? ? ? ? ? ? ? ? ? Web Operating System - Operation ? ?

  15. ? ? ? ? ? ? ? Web Operating System - Operation ? ? ? ? ?

  16. hello.c ? hello.exe WebComponents (WebComs) • Resource Representation Interaction [Schubiger, Krone] • Based on data flow networks semantic file name path content c-source hello.c = ? semantic file name path content os architecture hello.exe

  17. WebComs (cont.) • Attribute schemes • capture real world representations (concepts) e.g. files, programs, source-code,… • are constructed • by description • set operations (union, intersection,…) • an attribute scheme is either • implicit • native • relation based on other attributes file name path content c-source

  18. file name path content c-source semantic WebComs (cont.) • Passive WebComs • representations for non-executable resources • passive WebComs have an attribute scheme • Active WebComs • representations for executable resources • active WebComs are passive WebComs with an action • an action has two sets of plugs • input plugs • output plugs • each plug has an associated attribute scheme hello.c content semantic c-source compile content semantic o-file = debug optimized

  19. file name path content c-source file name path content c-source WebComs (cont.) compile semantic = semantic semantic debug hello.c optimized = ? semantic hello.exe

  20. WebComs (cont.) compile semantic = semantic semantic true debug hello.c false optimized = link semantic semantic = semantic hello.exe name

  21. content semantic c-source = compile link content semantic o-file content semantic o-file content semantic executable = = debug optimized file name path content c-source semantic hello.c WebComs (cont.) Attribute scheme of a plug has to be equal to attribute scheme of the other plug The attribute scheme of the plug has to be a subset of the attribute scheme of the passive WebCom Ê content semantic c-source compile content semantic o-file = debug optimized

  22. hello.c hello.o Warehouses WebComs (cont.) WebComs = = hello link hello.c compile ServicesResources gcc ld hello • Example: Unified Messaging • input WebCom: message • output WebCom: desired format of the message

  23. Current Research Issues • WOS Node Architecture [Unger] • node is client • and server

  24. t2 Node t1 Current Research Issues (cont.) • Communication Protocols [Babin, Kropf, Unger] • Two level communication protocol discovery/location protocol (WOSRP) location of specific WOS nodes generic Service Protocol (WOSP) * versioned protocol; bind node to appropriate instance of WOSP analyzer * setup, execution, query commands

  25. Current Research Issues (cont.) • Service Search [Unger, Kropf, Babin, Boehme] • information about local and remote services stored in WOS node • broadcast or serial chain mechanism, search trees • combination of both theoretical research performed: 6-10 chainsin parallel result in goodresponse time

  26. Research Issues (cont.) • Fault Tolerance [Babin, Kropf, Unger] • WOS server cannot serve the request after receiving it • Network brake downs • WOS nodes/machines crash Acknowledge protocol developedreceive acknowledgment(RACK)termination acknowledgment(TACK) MSG MSG t t RACK RACK MSG MSG RACK ((n-i-2)+(n-i-2)2/n)*t t RACK TACK TACK TACK node i-1 node i node n-1 node n

  27. Current Research Issues (cont.) • Load Management [Unger, Kropf, Plaice] • global online resource prediction impossible • transmission time: data might be outdated upon arrival • reaction in case of failure of nodes • off line learning and adaptation techniques cannot be used user manager: statistical data of processes started by a specific user machine manager: arranging allocation of local resources

  28. Current Research Issues (cont.) • Resource Representation & Interaction [Krone, Schubiger] • how can resources be manipulated and shareduse desktop metaphor for explicitmanipulation: WebRes* based on RMI;* introduced novel technique (dynamic linking) for runtime linking of objectsimplicit through (WebComs) data-flow driven

  29. Current Research Issues (cont.) WebRes * resource set * user interface * resource servers

  30. rd() in() Linda’s Tuple Space [“Hallo”,12, y] [x,12, y] out() eval() Current Research Issues (cont.) • Coordination Issues (use Linda as inspiration)Manifold, STL, ... • Negotiation Techniquesfor e-commerce • Mobile Agent Technology • Graphical User Interface • Security Issues (!) • Cost Model for Resources

  31. Related Work • Inferno (Lucent Technologies) • IBM’s T-Spaces • Berkeley’s WebOS (part of NOW) • SuperWeb and Charlotte • Microsoft’s Millennium project • and of course SUN’s Jini • …

  32. Related Work (cont.) Lookup Service (2) lookup (1) registration Service ObjectService Attributes Client Service Provider (3) use Service ObjectService Attributes Service Object

  33. Related Work (cont.) • Jini • services as resource encapsulation • lookup service as resource directory • leasing for access control • events for notification • based on JavaSpaces (Linda variant) • WOS • warehouses with versioned services • WOS’ “federations” are dynamically and autonomously created • language independent (protocol)

  34. Future Work • Extend WebRes to be used with WebComs • Definition of the network language • Graphical network builder • Interactive/automated resource selection (Agents/Web robots) • Develop adapters for legacy software (CORBA) • Validate Service Search Techniques • Further investigate CORBA and Jini and her friends • Look at Security Aspects • Consolidation of already developed prototypes

  35. Conclusion • Presented the WOS effort, ongoing research project, 5 Universities • Goals • develop methods, frameworks for future interconnected systems • contribute to future global information infrastructure • Both industry and academia is interested • Version 1.0 is on its way • Conference: Web Communities, June 2000, University of Laval • Info: http://paradis.ift.ulaval.ca/projects/wos

More Related