3. The higher the Abstraction Level, the bigger the
Sourcing Ecosystem
WebServices
REST
Composite Applications
JEE, BPEL, Living Mediation
jBPM
JAIN SLEE, Real-time Orchestration
SIP Servlet
Closed Today
5th International FOKUS IMS Workshop 2009 3
4. What is the Capability context
of the Service Delivery Framework?
Composite Services and 3rd party innovation
• Expose capabilities (to ASP and devices)
• Telco enable WEB 2.0
• Let users generate services
• Enable two-sided platform model
Living Mediation of Telco and other services/enablers
• Facebook status update via SMS
• Notify call on IPTV screen
• Divert call depending on Outlook calendar
• USSD and SMS Applications
Traditional Telecom Services
• MVPN
• Steering of Roaming
• Call Completion
• mobile PBX
5th International FOKUS IMS Workshop 2009 4
5. Service Delivery Framework Overview
3rd parties
ASPs, MVNO, Portals, Enterprise, Terminals, End Users, …
(Parlay X, REST) (WEB UI)
Partner and Service Mgmt
Capability Exposure
Portal
SCE (JEE, JAIN SLEE, jBPM), Load Runner, SOAP UI
Service / Subscriber Profile Data
Governance and Policy Pipeline
SEAM, jBPM
Service Creation and Testing
WS-I framework (implemented on JEE)
Service Management
ESB
BSM, SOA Diagnostics
IMDB
Run-time Service Real-time
BSS GW
(WS-I)
Product Policy Orchestration Orchestration
BSS
ESB
Enabler Protocol
Integration
Abstraction Abstraction
Connectors
Basic Services SLEE Resource
JEE implemented in SLEE Adapters
(JDBC, XML, Socket, MML) (SMPP, MM7, INAP, CAP, MAP)
Other Enablers Telco Enablers
Charging, TermCaps, HMC,
MSC, STP, MMSC, SMSC, GMLC, VMS, …
…
5th International FOKUS IMS Workshop 2009 5
6. Central User Profile and Service Repository
The central repository holds all subscriber info as well
as it holds service and runtime data for the orchestration containers.
5th International FOKUS IMS Workshop 2009 6
7. Abstraction of Service Enablers
and real-time orchestration using JAIN SLEE
Framework SMS Component Model IN
IN
BS Service
Service
USSD LBS MAP
Trace BS BS BS
MMS
MPBX
BS MPBX
Alarm
Timer Event Router
Profile
WS Framework Ressource Adapters JDBC
Times Ten
IMDB
SMPP
MM7
JDBC
INAP
MAP
MLP
CAP
SIP
SOA Platform Event Sources Central
Exposure to 3rd Parties STP, MMSC, SMSC, GMLC Repository
5th International FOKUS IMS Workshop 2009 7
8. Service Orchestration and Policy Enforcement
using JBoss SOA Platform
JBoss ESB – Event based Orchestration
JBoss jBPM [jPDL] JBoss Rules Integration Connectors and
– Process based Orchestration – Rule Engine and BRMS Services…
JBoss Enterprise Application Platform
– Application Server and supporting infrastructure
SOA SCE
5th International FOKUS IMS Workshop 2009 8
9. Service Orchestration - USSD use case
Send Response 6
CHECK DISPATCHER CONFIGURATION, HANDLE EVENT
ASYNCHRONOUSLY DISPATCH FOR DOWNSTREAM ACTION
PROCESSING
2
JBoss SOA Platform 3 CALL APPROPRIATE SOA
APPLICATION
JBoss SOA Platform
ESB + Rules – USSD jBPM – Process
1 & Short Code
Dispatcher/Listener
based Orchestration
CALL APPROPRIATE FUNCTIONAL
SOA LAYER 4 COMPONENTS PER NODE IN THE
FLOW USING ESB
SERVICE
EVENT – WEB SERVICES
ORCHESTRATION JBoss SOA Platform
5 Integration Connectors –
USSD/SHORT CODE
ALARMS
Service Enablement, USSD
CALL APPROPRIATE & Short Code Functional
Send Response
FUNCTIONAL Components
COMPONENT/SERVICE ENABLER
7 PRE-PAID DISPATCHER
SLEE SERVICES BALANCE CONFIGURATION
CHECK
SEND MESSAGE – WEB
SERVICE
TELCO AND IT
LAYER
TELCO LAYER SLEE - USSD IT LAYER / BSS SYSTEMS PROFILE DB
5th International FOKUS IMS Workshop 2009 9
10. Runtime Management of Service Exposure
WS-Intermediary –
Access Gateway
Security Policies -
Access
Management
Contracts Policies
Operations Policies
Monitoring
Subsystem
5th International FOKUS IMS Workshop 2009 10
11. Service Exposure – end to end Messaging use case
3rd PARTY GATEWAY
AUDITS, METRICS,
ALERTS INVOKE SMS, MMS
SERVICES
1
Monitoring Access Management Access Gateway
SOA LAYER
Subsystem RETURN REPSONSE
8 APPLICATIONS
SERVICE
EXPOSURE DISTRIBUTE AND MANAGE
RUNTIME SECURITY POLICY QUERY –
A&A
2 ENFORCE RUNTIME
ALERTS
RUNTIME SECURITY, CONTRACTS
AND OPERATIONS POLICIES INTO 3 DISPATCH REQUEST ON SUCCESS
SECURITY, CONTRACTS
AND OPERATIONS
SERVICE EXPSOURE RUNTIME POLICIES
RETURN
7 REPSONSE
5
JBoss SOA Platform JBoss SOA Platform
SOA LAYER ESB CALL APPROPRIATE RULE SET Rules
SERVICE AS A PART OF THE ACTION SUNRISE SPECIFIC
BUSINESS POLICY
ORCHESTRATION RULES
JBoss SOA Platform
CREATE, DEPLOY Integration
DISTRIBUTE AND MANAGE ALARMS
RUNTIME POLICY RULE CALL APPROPRIATE Connectors
DISPATCH REQUEST TO INTEGRATION
CHAINS AND ASSOCIATED
SMS, MMS TELCO LAYER ON CONNECTOR AS A PART
POLICY DATA
SUCCESSFUL POLICY E OF THE ACTION INTERACT WITH TELCO
VALUATION ELSE GO TO 7
AND/OR IT LAYER –
6 4 PAYMENT, PROFILE
TELCO LAYER SERVICES
DB – SUBSCRIBER
PROFILE, BLACKLIST,
DEVICE CAPABILITIES,,
TELCO AND IT OPSC
LAYER
SOA LAYER ADMIN PORTAL AND
RUNTIME BUSINESS SERVICE Runtime
GOVERNANCE REGISTRY, SOA P RUNTIME POLICY
GOVERNANCE AND
MANAGEMENT
Operations
Administrator
LAYER SCE
5th International FOKUS IMS Workshop 2009 11
12. Runtime Policies - Separation of Concerns
SOA Governance
Handling of northbound 3rd party access
JBoss SOA
Handling of Product specific policies
JAIN SLEE
Handling of southbound Enablers
5th International FOKUS IMS Workshop 2009 12
13. Something we should not forget to also cover…
The GSMA One API project is only covering the technical side, which of course is important,
but we must not forget to also tackle the business side.
Question:
With how many operators does a developer, developing a cool App for mobile phones,
have to sign a contract in order that people, form all over the world, can actually use his App?
(the App of course is using an exposed service through WS)
734?
Update: -> according to Graham Trickey from the GSMA they are actually also starting to cover this aspect.
But In order to make it a success they depend on the participation of the operators. So please make sure you get involved!
5th International FOKUS IMS Workshop 2009 13
14. Open Service Infrastructures
An Operator example
„The telco thing? Well, I think now more than ever it‘s important for operators to open up
their platform, because they have a great suite of under-used assets that outsiders can‘t
access and exploit. You‘ll never be able to sell beauty, passion, or love. But you can do a lot
more to act as an enabler and distributor for those who can and do.”
― — Martin Geddes (Dec. 2007), www.telepocalypse.net
5th International FOKUS IMS Workshop 2009 14
15. Open Service Infrastructures
Contact details
Contact me for any questions: marc.schaer[at]sunrise.net
5th International FOKUS IMS Workshop 2009 15