“ ” “Panel on Embedding Communications into IT Applications: Oracle Perspective” OASIS SOA for Telecom workshop Stéphane H. Maes CTO & Chief Architect Mobility, Voice and Communications

Agenda n Today’s industry situation n Positioning SOA in SP domain l SDP l OMA OSE l TMF SDF l AIA n SOA and new services/strategies in Telcos n Technology challenges with SOA n Conclusions

Agenda  Today’s industry situation n Positioning SOA in SP domain l SDP l OMA OSE l TMF SDF l AIA n SOA and new services/strategies in Telcos n Technology challenges with SOA n Conclusions

Search Shopping IMWeb iTunes Web 2.0 News / InfoTelecom Telephony Broadband VoIP 2.5G / 3G / LTE WiFi / WiMax IPTV Today’s Silos of Web & Telecom Domains Web lacks Telecom, and Telecom lacks Web 2.0, SOA

Agenda n Today’s industry situation  Positioning SOA in SP domain l SDP l OMA OSE l TMF SDF l AIA n SOA and new services/strategies in Telcos n Technology challenges with SOA n Conclusions

Today’s Market Reality From Simple Voice to Innovative Services Platform Goal for Everybody Service Revenues Low 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”? Service Proliferation Many Services, Fast TTM Few Viable Business Model Besides 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 TTM Viable service providers business models Not necessarily limited to Advertisement

SDP Positioning in Service Providers Domain Parlay/Standard RPs SIP/HTTP/Diameter Standard-Based Service Delivery Platform Standard Networks Interfaces IP Networks PSTN Wireless Standard Interfaces with OSS/BSS Subscribers DB Billing OSS & BSS CRM Expose Network and Services to Partners Revenue Sharing 3 rd Party Service and Content Providers VNOs

SDP: A Carrier Grade IT Platform as evolution of AS + SOA IT DomainNetwork Domain Parlay/Standard RPs SIP/HTTP/Diameter Standard-Based Service Delivery Platform Standard Networks Interfaces IP Networks PSTN Wireless Standard Interfaces with OSS/BSS Subscribers DB Billing OSS & BSS CRM Expose Network and Services to Partners Revenue Sharing 3 rd Party Service and Content Providers VNOs Standard IT Technology made Carrier Grade : (i.e. J2EE Stack, Carrier Grade + SOA) SOA (WS, BPEL, ESB, SCA, …) + Web2.0 Enterprise / ISP Have same need with sometimes a 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 low Latency, High Throughput, …

OSE (OMA Service Environment): A Blueprint for SDP and Service Layer for any SP Other bindings Web service bindings … Parlay API implementation Parlay X implementation Enabler implementation Policy Enforcer (PE) Applications or other resources … Enabler implementation To Resources in Operators, 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 Search for OSE, IMSinOMA and PIOSE + enablers Based on approved specifications – © OMA, endorsed / in cooperation agreement with many other Telco fora

OSE Principles Other bindings Web service bindings … Parlay API implementation Parlay X implementation Enabler implementation Policy Enforcer (PE) Applications or other resources … Enabler implementation To Resources in Operators, 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 Reusable / composable components with intrinsic function Adapters to abstract the network resource and use them Can be implemented on different network and coexist Policy Enforcement on all message: - Factor Business rules - SOA / Orchestration Defines interactions between in domain and 3 rd party applications Parlay JR / X are at same level as enablers and can be realize on SIP, … They form the OSA AS Standard Northbound interfaces OSS/BSS integration + LifeCycle Support (TMF) =SDP SDP = OSE e.g. Realized in J2EE

Other bindings Web service bindings … Parlay API implementation Parlay X implementation Enabler implementation Policy Enforcer (PE) Applications or other resources … Enabler implementation To Resources in Operators, 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 Apps IT 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 Carrier Grade Adapters: SIP, Diameter, IN, Messaging Parlay, … Summary: SDP, SDF and SOA, AIA, … IT-Based Platform (J2EE) Subscribers DB Billing Provisioning OSS CRM / ERP BSS 3 rd Party Content Providers MVNOs Converged ASes +Enablers PSTN Wireless IP Networks Network and Gateway Layer Carrier Grade 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 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 VoIP Virtual PBX Content Delivery ISV1ISV n … … MM Msg.

TM Forum SDF Reference Model n SDF RM contains main concepts and their relationships needed to support SDF Service Lifecycle Management l SDF Services n SMI l SDF ISS l SDF MSS SOA stackSOA Services SOA AIA + Business Processes SOA LC Management

EnrichTransformValidate Application Business Connector Service (ABCS) Application Business Objects Eg Customer DB Enterprise Business Objects EnrichTransformValidate Application Business Connector Service (ABCS) Application Business Objecs Customer Product Price List Sales Order Invoice Payment BSS ESB BPEL SOA Suite Business Services 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 OSS DB Enterprise Business Services

DB CRMERP IT Middleware/BPEL/ESB Transform Common Object Transform Cross Reference Indexing Common Error Handling NW Mgt BRM 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 SDP Activation Provisioning Order Mgt Common 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) Data Hubs SOA-Based OSS/BSS/SDP Integration

Agenda n Today’s industry situation n Positioning SOA in SP domain l SDP l OMA OSE l TMF SDF l AIA  SOA and new services/strategies in Telcos n Technology challenges with SOA n Conclusions

SOA-based SDP and SDF Unleashing Innovation and Monetization Service Proliferation Service Revenues Low High BlendWith“InternetServices” Extend to differentiate as “Communications SPs Need for Speed Quick: “At Internet Speed”SDP, SDF (AIA) + Pragmatic IMS

Core in-domain services, 3 rd 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 3 rd 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 n Any “internet service” is a Telco service possible specialized / robustized (carrier grade) for network or simply expose on network n Services can be SOA-based or web 2.0 based l Includes customization / built by subscribers n Service are provided by internet service providers or IT developers, less and less by Telco service providers or Telco specialized vendors n Service can be built / customized / integrated by users (e.g. web 2.0 mash-ups) n Advertisement based services (a la internet) + adapted to communications (e.g. ad subsidized communications) n Services specialized for users

l Need to be able to target many services offered by widest community (e.g. Internet): n 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 l Need to efficiently and rapidly develop, deploy services, validate, extract revenue and update or retire them: n Rely on common service (i.e. software) development practices n Automate with open, standard and customizable ways all business processes within the service providers an d with partners l Need to Provide services in future proof manner over as many network technologies as possible l Need to be Carrier grade! Requirements

Agenda n Today’s industry situatioon n Positioning SOA in SP domain l SDP l OMA OSE l TMF SDF l AIA n SOA and new services/strategies in Telcos  Technology challenges with SOA n Conclusions

Technology challenges with SOA n If we defined Carrier Grade (CG) as: l High Availability l Predictable low latencies l Efficient (e.g. throughput per CPU) / Economically viable l Scalable l Hot upgradable n MW containers can be carrier grade today n SOA CG has some challenges. E.g. (non exhaustive): l Delays, predictable latencies, time to instantiate l Throughput l QoS, SLA enforcement l LC Management like manageability of composed services and web 2.0 mash-ups (see TMF SDF) n Dependencies modeling l Distributed SOA and impact on instance selection, catalogs etc… n Adoption / endorsement by Telco SP and NEMs

Agenda n Today’s industry situation n Positioning SOA in SP domain l SDP l OMA OSE l TMF SDF l AIA n SOA and new services/strategies in Telcos n Technology challenges with SOA  Conclusions

Conclusions: Technology trends n Commoditization of core MW n CG SOA and web 2.0 n CG SOA based Policies consolidated across whole service provider domain (including network) n Service level SCIM and SOA for complex orchestration of services while simple orchestration may be lower in network n Automated business processes n CG SOA can implement core Telco services (e.g. even call control functions) n CG SOA may be achievable as SOA + distributed caching / grid computing n Product based services - end to end l “Telco in box except NW” with OSS/BSS/SDP/services SOA integration and SOA business processes extended to market places and web 2.0