““Panel on Embedding Communications into IT
Applications: Oracle Perspective””
www.oasis-open.org
OASIS SOA for Telecom workshopOASIS SOA for Telecom workshop
Stéphane H. Maes CTO & Chief Architect
Mobility, Voice and [email protected]
Agenda Today’s industry situation Positioning SOA in SP domain
SDP OMA OSE TMF SDF AIA
SOA and new services/strategies in Telcos Technology challenges with SOA Conclusions
Agenda Today’s industry situation Positioning SOA in SP domain
SDP OMA OSE TMF SDF AIA
SOA and new services/strategies in Telcos Technology challenges with SOA Conclusions
Search
Shopping
IM
WebWeb
iTunes
Web 2.0
News / Info
TelecomTelecom
Telephony
Broadband
VoIP
2.5G / 3G / LTE
WiFi / WiMax
IPTV
Today’s Silos of Web & Telecom DomainsWeb lacks Telecom, and Telecom lacks Web 2.0, SOA
Agenda Today’s industry situation Positioning SOA in SP domain
SDP OMA OSE TMF SDF AIA
SOA and new services/strategies in Telcos Technology challenges with SOA Conclusions
Today’s Market RealityFrom Simple Voice to Innovative Services Platform
Goal for Everybody
Service RevenuesLow
Low High
High– Customer Care and service quality– Rapid, efficient customer-centric services– Value curve understood to maximize revenue– Lean operation with Business Agility
Internet Services Domain
Communications Services Domain
Goal: Leverage Existing Revenue Relationship
How to provide “Carrier grade” quality?
How to foster a “leap change in innovation”?
Serv
ice
Pro
life
rati
on
Many Services, Fast TTMFew Viable Business ModelBesides advertisement
Few Services generating lots of (declining) Revenue. Lack of many new services BUT Differentiators to achieve Viable business models (e.g. access to bill, relationship to subscriber, QoS, …
Many Services, Short TTMViable service providers business models Not necessarily limited to Advertisement
SDP Positioning in Service Providers Domain
Parlay/S
tandard R
Ps
SIP
/HT
TP
/Diam
eter
Standard-Based Service Delivery Platform
Standard NetworksInterfaces
IP Networks
PSTN
Wireless
Standard Interfaces
with OSS/BSS
Subscribers DB
BillingOSS & BSS
CRM
Expose Networkand Services to
PartnersRevenueSharing
3rd Party Service and Content Providers
VNOs
SDP: A Carrier Grade IT Platform as evolution of AS + SOA
IT Domain Network Domain
Parlay/S
tandard R
Ps
SIP
/HT
TP
/Diam
eter
Standard-Based Service Delivery Platform
Standard NetworksInterfaces
IP Networks
PSTN
Wireless
Standard Interfaces
with OSS/BSS
Subscribers DB
BillingOSS & BSS
CRM
Expose Networkand Services to
PartnersRevenueSharing
3rd Party Service and Content Providers
VNOs
StandardIT Technology made
Carrier Grade :(i.e. J2EE Stack,
Carrier Grade+ SOA)
SOA (WS, BPEL, ESB, SCA, …) + Web2.0
Enterprise / ISP
Have same need with sometimesa subset of protocols
Enterprise Applications may differ
OSS/BSS/SDP Integration(SOA , AIA,
…)
Adapters:- HTTP, SIP,
Diameter, Others (e.g.
Via JCA 1.5)Carrier Grade:HA, Predictable
lowLatency, High
Throughput, …
OSE (OMA Service Environment): A Blueprint for SDP and Service Layer for any SP
Other bindingsWeb service bindings ……
Parlay APIimplementation
Parlay Ximplementation
Enablerimplementation
Policy Enforcer (PE)
Applications or other
resources
……
Enablerimplementation
To Resources inOperators, terminals, Service Providers
Execution Environment
(Software Life Cycle Mgmt,
Load balancing, caching,
etc.)
Applications or other
resources
Any domain (SP, Terminal)
Parlay / OSA Resources (GW/FW/SCSs)
IMS Non IMS Non Parlay / OSA Resources
OSE
http://www.openmobilealliance.org: Search for OSE, IMSinOMA and PIOSE + enablersBased on approved specifications – © OMA, endorsed / in cooperation agreement with many other Telco fora
OSE Principles
Other bindingsWeb service bindings ……
Parlay APIimplementation
Parlay Ximplementation
Enablerimplementation
Policy Enforcer (PE)
Applications or other
resources
……
Enablerimplementation
To Resources inOperators, terminals, Service Providers
Execution Environment
(Software Life Cycle Mgmt,
Load balancing, caching,
etc.)
Applications or other
resources
Any domain (SP, Terminal)
Parlay / OSA Resources (GW/FW/SCSs)
IMS Non IMS Non Parlay / OSA Resources
OSE
=SDP
SDP = OSE e.g. Realized in J2EE
Other bindingsWeb service bindings ……
Parlay APIimplementation
Parlay Ximplementation
Enablerimplementation
Policy Enforcer (PE)
Applications or other
resources
……
Enablerimplementation
To Resources inOperators, terminals, Service Providers
Execution Environment
(Software Life Cycle Mgmt,
Load balancing, caching,
etc.)
Applications or other
resources
Any domain (SP, Terminal)
Parlay / OSA Resources (GW/FW/SCSs)
IMS Non IMS Non Parlay / OSA Resources
OSE
OSE Principles Mapped to SDP
=SDP
Adapters:- HTTP, SIP, Diameter, Others (e.g. Via JCA 1.5) to NW Resources and OSS/BSS
Carrier Grade: HA, Predictable low Latency, High Throughput, …
SOA Services: Composed AppsIT Tools + SOA
(WS, BPEL, ESB, SCA, …)
SOA Services / Enablers to Expose & abstract NW, OSS and BSS
IT Tools + SOA (WS, BPEL, ESB,
SCA, …) + Policies / Business
Rules
OSS/BSS/SDP
Integration(SOA , AIA,
…)
OSS/BSS
SOA SOA
Carrier Grade Adapters:SIP, Diameter, IN, Messaging
Parlay, …
Summary: SDP, SDF and SOA, AIA, …
IT-Based Platform(J2EE)
Subscribers DB
BillingProvisioning
OSS
CRM / ERPBSS
3rd PartyContent Providers
MVNOs
Converged ASes +Enablers
PSTN Wireless IP Networks
Network and Gateway Layer
CarrierGrade
1. Start with standards-based IT platform (J2EE) and make it Carrier Grade
2. Extend beyond HTTP to SIP, Diameter, Parlay, IN, …
4. IT/SOA to provide revenue generating services: IT skills very rapid and agile deployment:
6. SDF/ AIA for Comms: SOA based integration of OSS/BSS/SDP : Following TMF SDF
3. Provide converged ASes (SIP, HTTP, OSA, …) and Enablers as SOA reusable components that abstract network resources + standard Northbound interfaces ; Following OSE
5. SOA based policies / business rules (e.g. third parties)
Policies
Policies
Pol
icie
s
UUP
7. Common Identity management and view of all info about Subscriber + Subscription Management
Common Identity Management
OSS and BSS and DB footprint for Communications
SOA/Web 2.0
SOA
VoIPVirtual
PBX
ContentDelivery
ISV1 ISV n…
…MMMsg.
TM Forum SDF Reference Model SDF RM contains main concepts
and their relationships needed to support SDF Service Lifecycle Management
SDF Services SMI
SDF ISS SDF MSS
SOA stack
SOA Services
SOA AIA + Business Processes SOA LC
Management
Enrich TransformValidate
Application Business Connector Service
(ABCS)Application Business Objects
Eg Customer
DB
Enterprise Business Objects
Enrich TransformValidate
Application Business Connector Service
(ABCS)Application Business Objecs
• Customer• Product• Price List• Sales Order• Invoice• Payment
BSS
ESB
BPEL
SOA Suite
BusinessServices Repository
Example: A customer record from CRM is translated into a generic Enterprise Business Object (EBO) and then pushed out to billing and revenue management system in the format required.
Application Integration Architecture
SOA Based SDF: AIA Overview
DB
DBOSS
DB
Enterprise Business Services
DB
IT Middleware/BPEL/ESB
TransformCommon
ObjectTransform
Cross Reference Indexing
Common Error Handling
• Processes to support key business activities and flows
• Canonical Object Model
• Orchestrated / composed processes across OSS, BSS and SDP
RMO
Different Design Patterns will be leveraged including request/ reply, synchronous process, asynchronous process, as well as others
Activation
Provisioning
Order MgtCommon Identity Management
IT Mgt
Principle: Using SOA/EDA, Business process are executed by orchestrating applications. Application can delegate functions to other elements or pass the hand (kick a new process)
SOA-Based OSS/BSS/SDP Integration
Agenda Today’s industry situation Positioning SOA in SP domain
SDP OMA OSE TMF SDF AIA
SOA and new services/strategies in Telcos Technology challenges with SOA Conclusions
SOA-based SDP and SDFUnleashing Innovation and Monetization
Serv
ice
Pro
life
rati
on
Service RevenuesLow
Low High
High
BlendWith “Internet Services”
Extend to differentiate as“Communications SPs
Need for Speed
Quick: “At Internet Speed”
SDP, SDF (AIA) + Pragmatic IMS
Core in-domain services, 3rd party (SOA) services and Web 2.0 Mash-ups on a same SDP Core Services:
Developed in SDP container against enabler APIs Long tail services:
customization and usage is driven by loose composition and users: Web 2.0 using widgets and 3rd party applications built on SDP
Plethora of short lived applications to try/deploy, update and retire easily / rapidly. Innovation comes from wide community of developers => Third party services provided by third party as SOA services against enablers APIs (WS/SOA)
Sales Revenue
Services
Trusted Applications in SDP Container requiring high performances and “permissions”
3rd party applications requiring lower level of permissions and capabilities
Mashup of widgets built on SDP by third party with Web 2.0 applications
New services and SOA Any “internet service” is a Telco service possible specialized
/ robustized (carrier grade) for network or simply expose on network
Services can be SOA-based or web 2.0 based Includes customization / built by subscribers
Service are provided by internet service providers or IT developers, less and less by Telco service providers or Telco specialized vendors
Service can be built / customized / integrated by users (e.g. web 2.0 mash-ups)
Advertisement based services (a la internet) + adapted to communications (e.g. ad subsidized communications)
Services specialized for users
Need to be able to target many services offered by widest community (e.g. Internet):
IT / Internet friendly, open and standard mainstream approaches and technology:
• Capture economies of scales• Tap the widest pool of developers and entrepreneurs as developers or
Partners
Need to efficiently and rapidly develop , deploy services, validate, extract revenue and update or retire them:
Rely on common service (i.e. software) development practices Automate with open, standard and customizable ways all business
processes within the service providers an d with partners Need to Provide services in future proof manner over as many
network technologies as possible Need to be Carrier grade!
Requirements
Agenda Today’s industry situatioon Positioning SOA in SP domain
SDP OMA OSE TMF SDF AIA
SOA and new services/strategies in Telcos Technology challenges with SOA Conclusions
Technology challenges with SOA If we defined Carrier Grade (CG) as:
High Availability Predictable low latencies Efficient (e.g. throughput per CPU) / Economically viable Scalable Hot upgradable
MW containers can be carrier grade today SOA CG has some challenges. E.g. (non exhaustive):
Delays, predictable latencies, time to instantiate Throughput QoS, SLA enforcement LC Management like manageability of composed services and web 2.0
mash-ups (see TMF SDF) Dependencies modeling
Distributed SOA and impact on instance selection, catalogs etc… Adoption / endorsement by Telco SP and NEMs
Agenda Today’s industry situation Positioning SOA in SP domain
SDP OMA OSE TMF SDF AIA
SOA and new services/strategies in Telcos Technology challenges with SOA Conclusions
Conclusions: Technology trends Commoditization of core MW CG SOA and web 2.0 CG SOA based Policies consolidated across whole service provider
domain (including network) Service level SCIM and SOA for complex orchestration of services
while simple orchestration may be lower in network Automated business processes CG SOA can implement core Telco services (e.g. even call control
functions) CG SOA may be achievable as SOA + distributed caching / grid
computing Product based services - end to end
“Telco in box except NW” with OSS/BSS/SDP/services SOA integration and SOA business processes extended to market places and web 2.0