1 / 65

Vision of ubiquitous computing

Service Creation What’s the issue ?? Keynote @ WAWC’07 Dr. Olaf Drögehorn Lappeenranta, August 16th, 2007. Vision of ubiquitous computing. Technologies, markets and users. Market players Licenses and regulation Business models Billing and pricing Competition Operator strategies

august-curry
Download Presentation

Vision of 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. Service CreationWhat’s the issue ??Keynote @ WAWC’07Dr. Olaf Drögehorn Lappeenranta, August 16th, 2007

  2. Vision of ubiquitous computing Dr. Olaf Droegehorn

  3. Technologies, markets and users Market players Licenses and regulation Business models Billing and pricing Competition Operator strategies Fight between standards Standardisation bodies Markets Networks Terminals Software tools Content management Security Technologies Users User needs Service delivery Types of services Cost of services Content Ease of use Personalisation Privacy Security Drivers and barriers! Dr. Olaf Droegehorn

  4. Content management Digital rights Content provider Payment provider Equipment producer Regulator Service provider Content aggregator Network operator Content server (database) Payment Networks Quality- of-service Terminals Networks Software APIs Mobile phones PDAs PCs / Internet Digital TV Security (Mobile) end users Privacy Personalization Services and networks - the big picture • Market players • Telecom operators • Other network operators • Broadcasters • Content providers • Content aggregators • Service providers • Payment providers • Heterogeneous • networks • xDSL • Mobile networks • Bluetooth • IEEE 802.x • Digital TV or radio • … • Devices • User interface • Capabilities • Development platform • Network interface • User needs : • To communicate • To form communities • To be informed • To be entertained • To be efficient • To feel secure • To feel capable • and “in control” • To be educated • Services: Putting technology to work … • Services exist, because they fulfill a need or solve a problem for the end users • A good service must be designed for the target users and the context of use • - and be user-friendly! • How can we make use of present and future networks, terminals and software • to address specific user needs? • Who are the stakeholders of a service? Dr. Olaf Droegehorn

  5. The Challenge for the Future of Communication Service (Creation) So, what shall we do, nowthat we can do everything? Bruce Mau,Author of “S,M,L,XL” Dr. Olaf Droegehorn

  6. Outline • The problem of service (creation) • What might people want (depends on the role) • The vision of Service Creation • The old way of service creation • A new way of service creation • Activity Theory • WWRF WhitePaper on Service Creation • An example how to do user-driven Service Creation • The Service Creation Workbench • Findings from the example • Conclusion Dr. Olaf Droegehorn

  7. What is a Service ? • An application ? • A piece of software ? • An outcome of a process ? => There are many definitions (business, economics, technologies, etc.) => Something, that fulfills a need (for help, for fun, for communication) => Is UMTS fulfilling ANY need at all ?? ;) Dr. Olaf Droegehorn

  8. Things that can make a service fail • There is no need for the service • If nobody uses the service, the whole thing is a failure • The user interface doesn’t work • Bad navigation design, bad graphics • The service is too slow • Content / bandwidth ratio, application doesn’t respond • The service is unreliable • Application crashes! Blank screens, hangs, resets • Data is not up-to-date, e.g. yesterday’s weather • Transactions fail - what happened to my order? • The service is insecure • Personal data compromised, money disappears • The service isn’t used - boring concept Dr. Olaf Droegehorn

  9. Understanding a need • Example: Just want to get out …. • Looking for „EXIT“, or similar • Arriving here, you find: Dr. Olaf Droegehorn

  10. Service Creation challengesJosef: There are no services, why ? • Why is Service Creation so difficult ? • Maybe we are expecting THE service(like the killer-application) • We are NOT developing variations(like product-designers do) • Most services are developed from scratch(Users don‘t recognize elements/widgets, therefore we try to enhance an already available service) • We are not reusing existing codes/technologies/widgets/platforms Dr. Olaf Droegehorn

  11. Service Creation, why do we need to talk about it ? • User needs are not addressed • Software service creation lifecycles are by far too long • Most services are developed from the scratch • Service composition is proprietary, at best • Ease the life of professional software developers • Ease the life of providers/operators • Enable „non-professionals“ to create their services => Each and every user should be able to create services Dr. Olaf Droegehorn

  12. Why should EVERYBODY do that? • Looking to the web: • HTML was for specialists only • Nowadays everybody has a web-page/blog • New hype: • User generated content (for the web) • Flickr, LifeBlog, etc. • Next trend: • User customized services • Google Mash-Ups Dr. Olaf Droegehorn

  13. Why should we do that ? • SMS was never meant to be a product/service • By using it, it formed a hype • Because people like to separate from each other => The idea is to enable everybody to improve/customize and generate services Dr. Olaf Droegehorn

  14. Variations are needed - IKEA (Users like to have the choice) Dr. Olaf Droegehorn

  15. Outline • The problem of service (creation) • What might people want (depends on the role) • The vision of Service Creation • The old way of service creation • A new way of service creation • Activity Theory • WWRF WhitePaper on Service Creation • An example how to do user-driven Service Creation • The Service Creation Workbench • Findings from the example • Conclusion Dr. Olaf Droegehorn

  16. The service creation problemfor Service developers „I wish to concentrate on improving my services functionalities, and not anything else...“ Dr. Olaf Droegehorn

  17. The service creation problemfor Service providers „There must be some simple ways to put all the functionalities together as ready-to-sell services ...“ Dr. Olaf Droegehorn

  18. The service creation problemfor End-users „Is it possible for me to customize service with functionalities that i wish to have?“ Dr. Olaf Droegehorn

  19. Outline • The problem of service (creation) • What might people want (depends on the role) • The vision of Service Creation • The old way of service creation • A new way of service creation • Activity Theory • WWRF WhitePaper on Service Creation • An example how to do user-driven Service Creation • The Service Creation Workbench • Findings from the example • Conclusion Dr. Olaf Droegehorn

  20. Service Creation Vision • A world of services that are… • Easy to create, • Easy to share, • Easy to use, • …and still user-centric! Dr. Olaf Droegehorn

  21. Service Creation Vision (2) • Easy to create  • Creation tools and publishing • Service taxonomies • Reuse of existing services and components • Semantic orchestration of components and loosely coupled approach • Easy to share  • Generalised client-server architecture • « My server in my pocket », « My server at home» • Service deployment in just a few clicks • Semantic based publishing • Easy to use  • Semantic Service discovery • Fine grain semantic-based search • Interoperability, composability of services Dr. Olaf Droegehorn

  22. Outline • The problem of service (creation) • What might people want (depends on the role) • The vision of Service Creation • The old way of service creation • A new way of service creation • Activity Theory • WWRF WhitePaper on Service Creation • An example how to do user-driven Service Creation • The Service Creation Workbench • Findings from the example • Conclusion Dr. Olaf Droegehorn

  23. The classical way to think about services • Domain-Specific Software Architectures (DSSA) • Build a specific „platform“ for a specific domain Dr. Olaf Droegehorn

  24. Domain-Specific Software Architectures (DSSA) • DSSA definition • „a context for patterns of problem elements, solution elements, and situations that define mappings between them“ (Software Engineering Institute, 1990) • Comprises a couple of crucial artifacts • scenarios • domain dictionary • context and entity/relationship diagrams • data flow, state transition, and object models • functional- and non functional requirements • … Problem: DSSA is still driven by technology Dr. Olaf Droegehorn

  25. Service Categorization today with regard to DSSA Source: UMTS Forum, http://www.umts-forum.org A typical DSSA just reflects these typical technical enablers Dr. Olaf Droegehorn

  26. Domain specific platforms • The issues are NOT new • The whole middleware hype was targeted to this • Build once, use everywhere • Why not simply using THE platform ? Dr. Olaf Droegehorn

  27. Middleware supports applications • Middleware provides homogeneous API to applications • By providing services that bridge between homogeneous and heterogeneous API • To shorten time-to-market for applications • To abstract from heterogeneity and allow applications to be executed on future mobile devices Application Middleware Device Device Dr. Olaf Droegehorn

  28. The original goals of platforms & middleware • Masking heterogeneity • networks, end-systems, OSs, programming languages • Providing a useful distributed programming model • simplicity with generality CORBA, Java RMI, etc. have been very successful in this... business applications; wrapping of legacy systems... Dr. Olaf Droegehorn

  29. The concept of middleware is used more widely • Platforms were built for many different domains, like: • Applications • eCommerce, 7x24 back-end servers • eScience • real-time, embedded systems • mobile agent systems • peer to peer platforms • mobile computing applications • telecomms/ programmable networking • Underlying systems • PCs/ workstations • supercomputers • wireless PDAs • embedded devices • network processors • wireless, sensor, infrared etc. networks Dr. Olaf Droegehorn

  30. A victim of its own success? • CORBA tries to cope ... • add asynch., transactions, fault-tolerance, persistence, components, load balancing, logging, real-time/ embedded/ lightweight CORBA, ...  complexity and unmanageability • prototypes arise to fill the gaps & to have smaller solutions • asynchronous platforms (pub-sub, eventing, message queueing) (MSMQ, JMS, JavaSpaces, ...) • Grid middleware (Legion, Globus, OGSA, ...) • web services (SOAP, WSDL, WSFL, ...) • mobility middleware (Rover, MOST, ...) • mobile agent systems (Tacoma, Aglets, ...) • peer-to-peer (JXTA, Jtella, ...) • real-time/ multimedia platforms (ReTINA, DIMMA, ...) • etc. • different assumptions, paradigms, models, implementation environments, ...  incompatible platforms, no cooperation, no reusability! Dr. Olaf Droegehorn

  31. Result: Many platforms for different disciplines Dr. Olaf Droegehorn

  32. Ending up in technology silos Source: UMTS Forum, http://www.umts-forum.org A typical DSSA just reflects these typical technical enablers Dr. Olaf Droegehorn

  33. Outline • The problem of service (creation) • What might people want (depends on the role) • The vision of Service Creation • The old way of service creation • A new way of service creation • Activity Theory • WWRF WhitePaper on Service Creation • An example how to do user-driven Service Creation • The Service Creation Workbench • Findings from the example • Conclusion Dr. Olaf Droegehorn

  34. A better way to think about services ? • Semantic-Driven Software Architectures (SDSA) • Design a service without technology in mind Dr. Olaf Droegehorn

  35. SDSA: Understand Services beyond Technology • No biased interfaces • keyboard/mouse, voice, gestures, touch display • No limiting form factors • mobile phone, notebook, desktop, PDA, smart phone • No usage constraints, i.e. • Unlimited power supply • Bandwidth abundance • Workflow convenience: no/short login, no hardware break-down, full-fledged transparent security, ... • No prejudice about network connection (fixed vs. wireless) … but describe precisely the context, services are being used Dr. Olaf Droegehorn

  36. Domain-Specific vs. Semantics-Driven Software Architectures Dr. Olaf Droegehorn

  37. Outline • The problem of service (creation) • What might people want (depends on the role) • The vision of Service Creation • The old way of service creation • A new way of service creation • Activity Theory • WWRF WhitePaper on Service Creation • An example how to do user-driven Service Creation • The Service Creation Workbench • Findings from the example • Conclusion Dr. Olaf Droegehorn

  38. Activity Theory Dr. Olaf Droegehorn

  39. Tools Object Outcome Rules Community Division of Effort • Icons instead of text • Assembly assistants • IKEA complaints hotline • Assemble • Explain, not assist From individual activities to Activity Systems Subject Understanding a service comprises more than workflow specification Dr. Olaf Droegehorn

  40. Tools Object Subject Outcome Rules Community Division of Effort Activity Systems as a core idea for real-world services (here SMS) • T9 keyboard • Display • Text delivered • Text received • Create & send limited text • Receive text • Sender • Receiver • Register for service • Pay per text • Mobile providers • Possible senders/receivers • Store and forward text • Charge for service SMS acts as a mediating artefact of an Activity System Dr. Olaf Droegehorn

  41. Outline • The problem of service (creation) • What might people want (depends on the role) • The vision of Service Creation • The old way of service creation • A new way of service creation • Activity Theory • WWRF WhitePaper on Service Creation • An example how to do user-driven Service Creation • The Service Creation Workbench • Findings from the example • Conclusion Dr. Olaf Droegehorn

  42. The Wireless World Research Forum • WWRF, founded in 1998 (from WSI & EU-FP5 Project) • Working Groups trying to draft future research issues • Definition of a reference model of User-centered communication (I-centric) • WhitePapers on specific topics Dr. Olaf Droegehorn

  43. Reference Model for I-Centric Communications Communication Space (Contexts & Objects) User Model & Appl. Scenarios Service Semantic Ambient Awareness Personalization Adaptation Service Bundling ServiceControl Service Discovery Service Creation Environment Monitoring Service Deployment ConflictResolution Generic Service Elements for all layers Application Support Layer Service Platform BusinessModel Service Execution Layer Service Support Layer IP based Communication Subsystem Network Control & Management Layer IP Transport Layer Networks Wired or wireless Networks Devices and Communication End Systems Terminals Dr. Olaf Droegehorn

  44. WhitePaper on Service Creation • A WhitePaper to highlight open issues, existing technologies & approaches • Technology driven service designvs. Technology agnostic approaches • Existing Software Development Environments (IDEs) • Business models for Service Creation • Identified need for: • Harmonization of tools & semantics • Technology agnostic/independent way of serivce design/description • Common semantics • Common understanding of technology enablers (like OSA/Parlay, ParlayX, IMS, etc.) Dr. Olaf Droegehorn

  45. Outline • The problem of service (creation) • What might people want (depends on the role) • The vision of Service Creation • The old way of service creation • A new way of service creation • Activity Theory • WWRF WhitePaper on Service Creation • An example how to do user-driven Service Creation • The Service Creation Workbench • Findings from the example • Conclusion Dr. Olaf Droegehorn

  46. One idea for service creation • „Draw a service“ - • Simplified service creation process Everyonecan define own services Technology agnostic Semantic Service Discovery Dr. Olaf Droegehorn

  47. The S4ALL approach • „Draw a service“ - Simplified service creation process Rule Dr. Olaf Droegehorn

  48. State Services Action Services Rule Rule Evaluator Business Rules Dr. Olaf Droegehorn

  49. Service Building Blocks (SBB) • State SBB: Read status to enable reacting on state changes. Also from Context Providers, which enablers to easily create context aware mobile services • Action SBB: Trigger actions on services at mobile device, in the home environment, in the Internet • Rules connect State SBBs and Action SBBs Dr. Olaf Droegehorn

  50. Business Rule Example Time Location Afternoon LasVegas & Start Presentation Icomp_2007.ppt Dr. Olaf Droegehorn

More Related