Towards Consolidated Presence

1. Manfred Hauswirth, Jerome Euzenat, Owen Friel, Keith Griffin, Pat Hession, Brendan Jennings, Tudor Groza, Siegfried Handschuh, Ivana Podnar Zarko, Axel Polleres and Antoine Zimmermann Towards Consolidated Presence 12 October 2010 CollaborateCom 2010

2. Setting up the stage

3. A Network of Knowledge • Interconnected • Universal • All encompassing • Enable global and local collaboration • The right information for the right people at the right time

4. Semantic Reality

5. Enterprise environments change! Clouds BPEL BPMN Semantics Scale Heterogeneous data Web 2.0 / Mash-ups Context Processes Data Heterogeneous platforms Common abstractions Enterprise Environments Communication Linked Open Data Mobile Phones Time-dependant information Hyper- Connectivity Incomplete information Corporate Social Network Sensors

6. A representative example Presence Management

7. Why is presence relevant? • Communication is essential in today’s enterprise workspaces • Presence • Essential block in delivering communication • Enables status identification and availability • Optimizes communication time => increase productivity, customer satisfaction, etc

8. Financial relevance • Chadwick Martin Bailey (2008) • “On a daily basis 40% of employees are unable to reach co-workers on the first try resulting in more then 20% of their employers experiencing a missed deadline or project delay on a weekly basis.”

9. Financial relevance • Current enterprise IM market • Installed subscriber base of over 140M • Market size in excess of $200M • Expected to grow to over 450M users and market size of over €500M by 2012 (The Radicati Group, 2009) • Current public/consumer IM market • Yahoo, QQ, AIM, GoogleTalk, Skype, etc: 600M users

10. Why is it a hard problem? Virtual availability Actual availability • Tight integration of various sources of virtual and physical presence • No single view on presence • Actors • Policies • Access control • Trust ↑ ↓ ≠

11. Technical challenges • Many forms and interpretations • Complex understanding • Complex reasoning • Heterogeneity of presence information sources • IM, Skype, (IP) phone, calendar, Twitter, … • GPS, mobile phone, sensors, … • No (limited) heterogeneous frameworks • No (limited) heterogeneous standards (SIP, XMPP, …)

12. Consolidated Presence • First-class type of service • “Internet of Services” applications • “Internet of Things” consumption • Open and integrated view of presence • A general concept – extension of the person-associated view • Flexible integration of arbitrary policies • Multi-faceted views of presence • Privacy and protection of sensitive information

13. Enterprise use cases • Check availability • Ad-hoc – phone: suggest alternative communication media, notification to call back, etc • Meeting schedulers – future meeting: prediction of availability of persons • Alternatives – finding alternatives for a given task • Resource management • Resource location, availability, … • Other • Context and action dependent presence • Automatic re-scheduling, geo-notes, …

14. Current Presence views • IETF SIMPLE: XMPP, SIP • RFC 3856: Presence “the ability, willingness or desire to communicate across a set of devices”

15. Presence model Facilitates information flow • Entities • PUA: Presence User Agent • PA: Presence Agent • Subscriptions management + notification Expose presence information Standing interest in presence info

16. Current Presence limitations • Limited types of person-associated availability • Individual or corporate access policies • Not associated to presence • Inflexible use to reveal presence • No clear and open semantics • Current solutions • Custom built-in • Hard to integrate • Presence not externalized as a service

17. Consolidated Presence • Enables the physical world to play a role in the presence management • Dynamic context • Sensor networks • E.g.: physical location, activity • Personalized profiles • Personal or corporate policies • Access control

18. Consolidated Presence • Enables a Watcher to be served a policy-governed, contextualized view on the availability of a Presentity • Physical presence • Virtual presence • Personal policies, governing policies, etc

19. Enterprise Context • RFC 3856 + resources and devices • Presence service • Management of presence information • Rich presence • Physical presence • Sensor technology • Semantic presence • Semantic Web and Intranet Search technologies • Unified, service-oriented manner

20. Federated Architecture • Intra-domain federation • Abstraction from presence service heterogeneity • Underlying information models, policy support, storage and processing • Interchange presence information despite underlying protocols, models or policies • Input: Filtering close to the edge of the network • Reduce load • Support scalability

21. Federated Architecture • Intra-domain federation

22. Federated Architecture • Inter-domain federation • Openness and extensibility • User perspective • Similar to intra-domain federation • Governing policies • Secure and policy controlled information and communication sharing • Pervasive • Throughout the enterprise • At the boundaries between the enterprise and external enterprises or consumer spaces

23. Federated Architecture • Inter-domain federation

24. Requirements • Information integration • Virtual, physical and social presence • People, objects and software entities • Powerful and flexible semantic techniques • Low-level stream processing, sensor middleware and publish/subscribe systems • Enterprise policy management • Fine-grained control of sharing presence information • Within single or across multiple enterprises

25. Development directions • Rawpresence • Data acquisition middleware for personal devices • Publish/subscribe middleware • Digestedpresence • Semantic description of context models and policies • Policy analysis and negotiation

26. Development directions • Data acquisition middleware for personal devices • Integrate broad range of physical and virtual information sources • Support for mobile devices to enable ad-hoc collaboration • Extensible and adaptive filtering

27. Development directions • Publish/subscribe middleware • Content-based solutions • Integrate fast and efficient matching algorithms • Fine-grained filtering of presence information • Distributed solutions with efficient routing algorithms • Minimize the generated traffic • Support mobility across various networks, devices and access points • Integrate policy-driven publish/subscribe matching and routing

28. Development directions • Semantic description of context models and policies • Semantic Web technologies • Expressive and open knowledge representation languages • Dynamic extension of knowledge descriptions • OWL – Web Ontology Language • Standard vocabularies • Axioms governing presence, location, availability, profiles and policies • OPO, Geo, GeoNames, PIMO, …

29. Development directions • Policy analysis and negotiation • Policy-based management of communication in federations of enterprises • Consistency checking between enterprise’s own policies and the policies agreed with other enterprises

30. Conclusion • Consolidated Presence • Combined presence context from both virtual and physical sources • Enforcement of personal and organizational policies • Scenarios • Requirements • Technology roadmap • Sensor technology • Content-based publish/subscribe middleware • Semantic description of context models

31. Conclusion • Consolidated Presence • Combined presence context from both virtual and physical sources • Enforcement of personal and organizational policies Thank you! Contact: Manfred Hauswirth, DERI Galway (manfred.hauswirth@deri.org)