Semantic Web Services and Opportunities in Telecommunications

1. Semantic Web Services and Opportunities in Telecommunications Tomas Vitvar tomas.vitvar@deri.org Presentation to Bell Labs Ireland 28th September, Dublin, Ireland

2. Overview • Introduction to DERI • Semantic Web Services • Use Case: Semantic-enabled voice and data integration • Conclusion

3. Semantic Web and Web Services 500 million user more than 3 billion pages WWW URI, HTML, HTTP Static

4. Semantic Web and Web Services Serious Problems in information finding, information extracting, Information representing, information interpreting and information maintaining. Semantic Web RDF, RDF(S), OWL WWW URI, HTML, HTTP Static

5. Semantic Web and Web Services Bringing the computer back as a device for computation Web Services UDDI, WSDL, SOAP Dynamic Semantic Web RDF, RDF(S), OWL WWW URI, HTML, HTTP Static

6. Semantic Web and Web Services Bringing the Web to its full potential Intelligent Web Services Web Services UDDI, WSDL, SOAP Dynamic Semantic Web RDF, RDF(S), OWL WWW URI, HTML, HTTP Static

7. DERI – Vision eCommerce Enterprise Application Integration Knowledge Management Web Services Semantic Web Semantic Web Services

8. DERI Structure and Funding Sources • DERI International • DERI Galway, Ireland • DERI Innsbruck, Austria • DERI West, CA USA • DERI East, Korea • Funding Agencies • Science Foundation Ireland (SFI) • Information Society Technologies (EU FP6 Program) • Enterprise Ireland (EI) • Hewlet Packard Galway (HP) • Tiroler Zukunftsstiftung (Austria) • Forschungsförderungsfonds für die gewerbliche Wirtschaft (FFF, Austria) • Cooperate (Austria)

9. DERI – Funding DERI International € 25 Mio DERI Galway € 16 Mio DERI Innsbruck € 9 Mio Knowledge Web € 1.4 Mio DIP € 1 Mio SEKT € 0.7 Mio SWWS € 0.6 Mio Esperonto € 0.2 Mio Austrian projects € 0.8 Mio University € 3 Mio ASG € 1 Mio Lion € 12 Mio DIP € 2 Mio ASG € 0.5 Mio Knowledge Web € 0.5 Mio SWWS € 0.2 Mio M3PE € 0.25 Mio New: SUPER, Nepomuk, SemanticGov, RIDE, SAOR, SWING (€ 6 Mio)

10. DERI – Team

11. DERI Galway • DERI Galway – Research Focus • Semantic Web • Social Networks, Digital Library, Semantic Desktop • Semantic Web Services • Semantic Execution Environment • WSMX Core • Semantic Integration in Business • SWS Applications in areas: e-business, e-government, e-health, telecommunications • Industrial and Scientific Applications of SWS • E-Banking, B2B, Robotics, Biotechnology

12. Overview • Introduction to DERI • Semantic Web Services • Use Case: Semantic-enabled voice and data integration • Conclusion

13. Web Services – Current Problems • Finding, Comparing, Composing Offers of Vendors • Decentralized business services (web, web services, …) • Machine processable semantics of information allows to automate these tasks • Number of Heterogeneous Data Formats • Standards and Ontologies • Mediation, Ontology merging, mapping/aligning • Number of Heterogeneous Business Logics • Process Mediation, • Interaction protocols (Choreography)

14. SDK Working Groups WSMO WG Conceptual Model for SWS WSML WG WSMX WG Formal Language for WSMO Execution Environment for WSMO Rule-based Language for SW http://www.wsmo.org/

15. WSMO Top Level Concepts Objectives that a client may have when consulting a Web Service Provide the formally specified terminology of the information used by all other components Semantic description of Web Services: • Capability (functional) • Interfaces (usage) Connectors between components with mediation facilities for handling heterogeneities WSMO D2, version 1.0, 20 September 2004

16. Web Service Modeling Language WSML Goal Example • WSMO Elements in WSML • Ontologies, Goals, Web Services WSML Ontology Example

17. WSMX Architecture and Execution Environment • Reference implementation of WSMO • WSMX Design Principles == SOA Design Principles • Strong Decoupling and Strong Mediation • Autonomous components and mediators for interoperability. • WSMX Core – WSMX Manager • Execution Semantics • WSMX Components • Discovery, Selection, Mediation, Composition, Contracting, … • Well-defined interfaces • Interactions between components is defined by execution semantics

18. WSMX Architecture

19. WSMX Architecture – Layers • Basic Services • Reasoner, Semantic Repository (services, goals, ontologies), Communication • Interoperability Services • Protocol/Syntax Interoperability (Adapters) • Data/Semantic Interoperability (Data Mediation) • Process Interoperability (Process Mediation) • Application Services • Discovery, Selection, Composition, Contracting, Negotiation • User Services • Management Tools (Ontology Editors, Mapping Tools, Monitoring Tools) • Peers (service requester, service provider) • Vertical Services • (Self) management, Security

20. WSMX Entry Points and Execution Semantics

21. WSMX Component Interactions

22. WSMX Data Mediator Design-Time Tools • Ontology Mapping Tool • Run-Time Component Tester Run-Time Mediator • WSMX Component • Stand-alone mediation service

23. WSMX Uptake and Projects • OASIS Semantic Execution Environment TC • Evolved from WSMX WG • Projects • Current: DIP, KW • New: SAOR, SemanticGov, SUPER, SWING, etc. • WSMX – vehicle for partnerships and EU Projects

24. Overview • Introduction to DERI • Semantic Web Services • Semantic-enabled voice and data integration • Conclusion

25. Motivation • Convergence of networks • Voice, data and video services using the same technology/network based on IP • Liberalization of Telecommunication Market • Users can freely choose operators for different services • Increasing number of operators and services • Better services, better deals for users • Integration of voice/video (e.g. make a call, conference call) with data services (e.g. resolve name to number) • Example: Click to Dial - a call will be automatically made by clicking on a user name. The callee number will be resolved and call will be made through predefined/selected operator.

26. Current and Future Problems • A user manually comparing services and prices of more than one operators is nowadays quite usual • A big number of services will be hard to compare, combine and select manually • Automatic discovery of services needed (discover operators which satisfy users’ needs – e.g. “make a (video) call”) • Automatic composition of services needed (composition of services such as “resolve name to number” and “make a call”) • (semi) automatic selection of services needed (selection of the “best” services – e.g. “make a call” service with cheapest rate per minute) • Different services will be using different data formats • Automatic data mediation needed (e.g. operator 1: “time-unit=minute, currency=GBP”, operator 2: “tariff=second, currency=EUR”)

27. Example: Integration Scenario 3 Jana’s desire is transformed to WSML goal and is sent to WSMX. 2 Jana desires to make a cheapest call with Tomas. She “dials” Tomas name. 1 Resolve-number service is registered with WSMX by DERI 4 Resolve-number and authorize-call services are discovered, selected, composed and invoked. 6 Result is received back to SIP Proxy and the call is established through authorized operator. 5 By invocation, the call is authorized through selected operator. 7 Tomas phone starts ringing. 1 Authorize-call service is registered with WSMX by Operator 1 and 2 Jana wants to make a cheapest call with Tomas of who she only knows he works with DERI institute. She doesn’t know Tomas’s phone number. Jana expresses her desire using her standard SIP phone by dialling “tomas#deri#price”.

28. Example: Integration Scenario Jana wants to make a cheapest call with Tomas of who she only knows he works with DERI institute. She doesn’t know Tomas’s phone number. Jana expresses her desire using her standard SIP phone by dialling “tomas#deri#price”.

29. Conclusion • DERI – Research Institute focused on the cutting edge research of the SW and SWS • 100 researchers • DERI Galway Semantic Web Services • WSMO, WSML, WSMX • EU and Irish Funded Projects • WSMX Semantic Execution Environment • SWS Applications to different domains • SWS and Telecommunications • WSMX integration with VoIP systems • Telecommunications Management?