Copyright 2005 Digital Enterprise Research Institute. All rights reserved.
www.deri.org
Semantic Web Services and Opportunities in Telecommunications
Tomas [email protected]
Presentation to Bell Labs Ireland28th September, Dublin, Ireland
2
• Introduction to DERI• Semantic Web Services• Use Case: Semantic-enabled voice and data integration• Conclusion
Overview
4
500 million user
more than 3 billion pages
Static WWWURI, HTML, HTTP
Semantic Web and Web Services
5
Static WWWURI, HTML, HTTP
Serious Problems inSerious Problems ininformation finding,information finding,information extracting,information extracting,Information representing,Information representing,information interpreting and information interpreting and information maintaining.information maintaining.
Semantic WebRDF, RDF(S), OWL
Semantic Web and Web Services
6
Static WWWURI, HTML, HTTP
Bringing the Bringing the computer back computer back as a device for as a device for computationcomputation
Semantic WebRDF, RDF(S), OWL
Dynamic Web ServicesUDDI, WSDL, SOAP
Semantic Web and Web Services
7
Static WWWURI, HTML, HTTP
Bringing Bringing the Web the Web to its full to its full potentialpotential
Semantic WebRDF, RDF(S), OWL
Dynamic Web ServicesUDDI, WSDL, SOAP
Intelligent WebServices
Semantic Web and Web Services
8
Semantic WebSemantic Web
Web ServicesWeb Services
Knowledge ManagementKnowledge Management
Enterprise Application IntegrationEnterprise Application Integration
eCommerceeCommerce
Semantic Web ServicesSemantic Web Services
DERI – Vision
9
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)
10
DERI – Funding
DERI International € 25 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)
DERI Galway € 16 Mio DERI Innsbruck € 9 MioKnowledge 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
13
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
14
• Introduction to DERI• Semantic Web Services• Use Case: Semantic-enabled voice and data integration• Conclusion
Overview
15
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)
16
SDK Working Groups
WSMO WG
WSMX WGWSML WG
Conceptual Model for SWS
Formal Language for WSMO
Rule-based Language for SW
Execution Environment for WSMO
http://www.wsmo.org/
17
WSMO Top Level Concepts
Objectives that a client may havewhen 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
18
Web Service Modeling Language
• WSMO Elements in WSML– Ontologies, Goals, Web Services
WSML Goal Example
WSML Ontology Example
19
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
20
WSMX
System
Interface
WSMX ManagerWSMX Manager Core
Administration Framework Interface
Da
ta a
nd
Co
mm
un
icatio
n P
roto
cols A
da
pte
rs
Ad
ap
ter 1
Ad
ap
ter 2
Ad
ap
ter n
... Grounding
CM Wrapper
CommunicationManager
Interface
Invoker Receiver
RMWrapper
Resource Manager
Interface
ParserWrapper
Parser
Interface
DiscoveryWrapper
Discovery
Interface
SelectorWrapper
Selector
Interface
DMWrapper
DataMediator
Interface
PMWrapper
ProcessMediator
Interface
ChoreographyWrapper
Choreography
Interface
Reasoner Interface
Reasoner
Resource Manager Interface
WSMO Objects Non WSMO Objects
WSMT – Web Services Modelling Toolkit
Service Providers
Web Service 1
Web Service 2
Web Service p
...
Service Requesters
Back-End Application
Agent acting on behalf of service
requester
WSML EditorWSMX Monitor Choreography EditorWSMX Managment Mediator Editor
ComponentWrapper
New Component
Interface
WSMX Architecture
21
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
22
WSMX Entry Points and Execution Semantics
Legend
CommunicationManager
(Requester Side
Parser
ServiceRepository
Matchmaker
Selector
DataMediator
Editor
CommunicationManager
(Requester Side
Parser
receiveGoalstoreEntity
Adapter
any Data format
ServiceRequester
WSML
WSML
ServiceRepository
WSMX components
External entities
Execution Flow
24
Design-Time Tools• Ontology Mapping Tool• Run-Time Component Tester
Run-Time Mediator• WSMX Component• Stand-alone mediation
service
WSMX Invoker
WSML Editor
WSMX Data MediationMapping Tool
Run-Time TestingWindow
Web Service
Data Mediation Run-Time
Component
Mappings Storage
Web Page
Instances
Instances
Mappings
Instances
Mappings
Mappings
WSMT/Eclipse Plugins
WSMX
Data Mediation Run-Time
Component
Instances
WSMX Data Mediator
25
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
26
• Introduction to DERI• Semantic Web Services• Semantic-enabled voice and data integration• Conclusion
Overview
27
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.
28
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”)
29
Example: Integration Scenario
Internet
VoIP Hub
Jana’sSIP Phone
Asterisk(SIP Proxy) WSMX
Tomas’sPhone
DERI
Telecommunication Network 2
Operator 2
Telecommunication Network 1
Operator 1Voice and Signalling
Data
Jana desires to make a cheapest call with Tomas. She “dials” Tomas name.
2
Resolve-number service is registered with WSMX by DERI
1
Authorize-call service is registered with WSMX by Operator 1 and 2
1
Jana’s desire is transformed to WSMLgoal and is sent to WSMX.
3
Resolve-number and authorize-callservices are discovered, selected,
composed and invoked.
4
Result is received back to SIP Proxy and the call is established
through authorized operator.
6
By invocation, the call is authorized through selected
operator.
5
Tomas phone starts ringing.
7
30
Example: Integration Scenario
can-resolve=yes
SIP trying
SIP INVITE
Asterisk (PBX)WS
resolve-nameDERI Institute
autorize-call1WS
Operator 1
WSautorize-call2
Operator 2Operator 1
Tomas’s Phone
WSML Goal
canResolve(person.company=DERI)
getNumber(person.name=Tomas, person.company=DERI)
callee.userPart=0035391495270
canAuthorize (callee.userPart=0035391495270)
price=0,17,currency=EUR,time-unit=minute
getPrice(callee.userPart=0035391495270)
price=0,004,currency=GBP,tariff=seconds
1. IDC (goal)
4. Engagement (resolve-name)- Contracting
8. Invocation
9. Engagement (authorize-call)- Contracting
- Negotiation
WSMX
authorizeCall(callee.userPart=0035391495270, caller.userPart=jana, caller.domain=voip-hub.ie)
callee.domain=operator1.ie
SIP INVITE sip:[email protected]
SIP trying(PSTN invitation to a call)
SIP ringingSIP ringing
(PSTN ringing)
SIP
2S
WS
authorizeCall([email protected], calleeNum=0035391495270)
can-authorize=yes
canAuthorize (callee.userPart=0035391495270)
can-authorize=yes
getPrice(callee.userPart=0035391495270)
10. Selection
Jana’s Phone
(1)
Dia
llin
g
(2)
Tra
nsf
orm
ing
D
esir
e to
Go
al(3
) A
chie
vin
g G
oal
(4)
Ach
ievi
ng
Des
ire
2. FLC (goal)
3. IDC (sub-goal1)
5. IDC (sub-goal2)
6. Engagement (authorize-call)
7. PLC
11. Invocation
callee.userPart=0035391495270,callee.domain=operator1.ie
31
• 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?
Conclusion