Adopting SOA for Telecom Workshop Sept. 30 th, 2008 Telecom Member Section

n Telecom Member Section l n Steering Committe l n Current Members l IBM, Orcale, Primeton, Alcatel-Lucent, Avaya, BTplc, CA, Microsoft Corporation, NEC Corporation, Nortel, Progress Software, Verisign, Mitre Corporation, OOS Nokalva, Siemens AG, Telecom Italia S.p.a. n Information including how to become a member l Dee Schur Useful links Orit Levin, Microsoft Stephane Maes, Ph.D., Oracle - Co- chair Tony Nadalin, IBM Abbie Barbir, Ph.D., Nortel - Co- chair Michael Brenner, Alcatel-Lucent Enrico Ronco, Telecom Italia Takashi Egawa, NEC

Workshop Program Committee n Michael Giordano (Avaya) n Abbie Barbir (Nortel) n Hanane Becha (Nortel) n Tony Nadaline (IBM) n Stephane Maes (Oracle) n Sune Jakobsson (Telenor) n Rakesh Radhakrishnan (Sun Microsystems) n Ian Jones (BT) n And Many Many thanks to all the OASIS Staff and our host CA

Closing Remarks Enrico Ronco – Telecom Italia Closing Remarks Enrico Ronco – Telecom Italia

Sessions of this Workshop n Welcome & Opening Keynote (Nortel) l Providers Perspectives on SOA in Telecom (BT) n Panel on Embedding Communications into IT Applications: A Vendor Perspective (Telenor) l Accenture, Avaya, Oracle n S1: Challenges of Telecom Services in SOA Environment: Lessions Learned and Case Studies (Avaya) l SOA Security: Challenges, Patterns and Solutions (IBM) l Digital Identities for Networks and Convergence (NEC Europe) l Operator Perspective: Dealing with Issues & Relationships in a changing eco-system ( Vodafone ) l Service Oriented Architecture and Use of SOA at Telenor Nordic (Telenor) l Overcoming the Deployment Blues: Preparing for Comms Enablement (Nortel) l Elements of SOA in TM Forum’s Service Delivery Framework and its Usecases (Oracle) n S2: SOA Solutions in Telecom Today (Oracle) l Service Oriented Authorisation for Managing Services and Devices in Telecommunication Networks (Axiomatics) l Services Exploiting SOA and Web Service Technology in Modern Telcos (Aepona) l Microsoft Mediaroom as a SOA for IPTV (Microsoft) n S3: Telecom Standards (BT) l OMG Perspective on Standards l OMA Perspective on Standards l TM Forum Perspective on Standards l Towards a SOA/WS Enabled NGN Open Service Envornment: Ongoing Develop. in ITU-T SG13

Highlights of the day n Introduced the OASIS Telecom MS and its main objectives Interesting Keynote: operator ’ s view on SOA Panel: Heard how Vendors are facing specific issues on “ SOA for Telecom ” n S1: Heard of specific Issues currently faced within the Telecom industry n S2: heard of SOA solutions already in place S3: Known what other “ Telecom ” SDOs are currently doing on SOA and viewed some possible concrete links Note: I tried to derive possible implications of exposed presentations on TMS future activities

The OASIS Telecom Member Section n Objectives l Promote the use of SOA in Telecom through the development of profiles of web services stacks optimized for the real-time need of telecom industry l Collect and solve telecommunications related issues within the SOA framework l Bridge between various SDOs applying SOA and WS to the telecom sector Next Steps ( … first steps) Start first TC (January 09) on Gaps – issues – problems on OASIS SOA standards for Telecoms … solve such problems

Messages from the Keynote n Shift from Network Operator to Service Provider Do business within “ the long tail ” l Communication with communities n Need for common capabilities (shift from vertical applications) Agnostic access to networks, common set of “ components for services ” : (profile, messaging, call servers, media servers … ) Convergence between telecom “ platforms ” and enterprise “ applications ” : Network competences now merged with IT competences Common set of standards now available to enable “ web platforms ” l Software Development moving from proprietary monolithic telecom applications to standards-based layered J2EE applications n Be pragmatic in building the application layer (IMS lesson): understand what people want to do with services and select standard network components as mature technology emerges l Focus effort on building applications customers really want (e.g. sales force management) Work to deliver “ service building blocks ” No Killer app. / Yes “ Killer attribute ” : ability to change rapidly

Messages from the Panel: vendors perspective n Giordano: l Need for an agile communication creation environment l Deliver different level of granularity for different customers l OASIS can help in filling some gaps (i.e. security, manageability, serviceability of “communication platforms”) l Occasion for a full automation of business processes (incl. manual processes) – gave examples (sales force automation, extension of communication services with enterprise folders n Sabadotto: l How to implement SOA in a holistic view? (need for a proper governance capability) l 4 different levels of maturity of SOA adoption in Telcos: (Plan & Organize, Deploy, Architected, Industrialized). Not necessary to run through them in sequence. l Understand customer need, make a plan, iterate within phases (level 3 is the most difficult) l The whole is difficult: services delivered by consultants, but failure in the achievement of the full business value. Difficult for a department to pay for others. Short term funding. l Gives us a “recipe” for SOA adoption in Telcos: 1) Define governance framework and decide key roles (who should sit in this “board”); 2) define quick goals … n Maes: l Bridge the “Web” world with the “telco” world, and “Traditional Telcos” have goals which are different from the “Internet SP” l Concept of “Standard-Based Service Delivery Platform”: -  look at the OMA OSE l Then a “process” is suggested for successful deployment of the “Standard SDP” l Mention of TM Forum Service Delivery Framework (SDF) l Mention of Oracle’s Application Integration Architecture l No particular challenge in making things happen, but SOA is not yet CARRIER GRADE n High availability, predictable low latencies, efficient, scalable … n Difficult to guarantee throughput, SLA, QoS, lifecycle management of mash ups

In summary (from Sune Jakobsson) n SOA is technically available n …but the Web is not ready n The Web is not regulated, opposed to the traditional Telco, that is required to provide carrier-grade n Catch the “long tail”

Messages from S1: lessons and case studies (1) n Vodafone: real-life experience l Operators want to use mature technologies o help them solve their problems n Are WSs easing the integration? n Is REST applicable to telecoms? n Mash-ups; exciting, but realistic? l Operators are recognizing user data as a corporate asset (not only for liability); NEW Cash flow potential with mobile advertisemet l SOA Standards must help Operators to manage such asset n Operators are invited to provide requirements to the SDOs (e.g. OASIS TMS) Operators need clear guidance on “ minimum interoperable WS-stack ” to use n Telenor : real-life experience Presented real-life experience in “ implementing / deploying ’ SOA in Telenor l What is the correct granularity of a SOA Service ? l SOA Governance assumes key importance: OASIS standards must address this aspect (look at RA for SOA): Run-time (and off-line) SOA governance must be enabled n Nortel: lessons learned from 4 key implementations l Within one case it was required us to go well beyond Parlay X and other telecom standards l Interfaces need to be kept simple so that non-telecom developers could easily make use of them l Need of mentality change: difficult not to expose “telecom” capabilities (such as session ids) to the application via APIs l Many internet developers struggle with the WS-* specifications: they expect REST-style interfaces instead l Necessity to extend standards for location-setting and presence l Need to change some BPEL specs? Customers are just beginning to experiment it – 1 more year to know

Messages from S1: lessons and case studies (2) n NEC: identity management l SWIFT project: solve identity fragmentation of today, develop EU identity architecture Analyzed today ’ s identity management within different providers – project will last until 2010 l Virtual identities concept: many faces for transactions to separate roles or for privacy roles l Concept of virtual identity applicable down to the network Defined a set of building blocks of an “ Identity Architecture ” Mobility, Security, AAA, Devices … l Goals to achieve n Liberate user from device(s) by enabling use of several interchangeable devices n Network Access automatically made available based on service requested Identity becomes a convergence technology: forms the bridge between networks, services, content … l Objective is to bridge existing solutions together Proposal of the “ identiNET ” … Issue: who is accountable on the management of the “ federation of identities ” ? n IBM: security l Challenge emerges on identity and access management Need of support of virtual identity and the related trust framework – personalization and virtual identity l Externalize policies (and security functions) from applications l Open standards based approach is the way to go l Need for real time distributed policy negotiation and enforcement: OASIS TMS must take this issue and promote its solution within the appropriate SDO n TM Forum Work for the enablement of lifecycle management of “ services ”, not only within one SP ’ s domain l There may be some modifications to the OASIS SOA RM (SDF Service has > than 1 SI) l Touch points for OASIS TMS and TM Forum SDF

Messages from S2: SOA in telecoms today (1) n Axiomatics l How does standardized authorization mnagement support SOA in Telecom Networks (focus on use of XACML, at service and device configuration level) l Authorization is meant as a service to other applications and services n As well as location, IPTV … it would be important to provide also Authorization as a “telecom service” n Operators would like to avoid micro-management of services and features of service providers (avoid micro-management) n SPs need to control their services themselves l Gave examples on access permissions (e.g. end user access to service) and on specific services for users (e.g. parking service… different policies) l Issues: policy enforcement, policy administration, attribute management l Authorization service shall be provided by Operators to SPs and XACML 3.0 can play an important role n Aepona: l Core Telco service enablers: payments, messages, presence, location  they are assets l SOA is about the interface for 3 rd parties to access such enablers l 3 “killer capabilities”: contextual presence, location – flexible media and conference switching – Intelligent notification services l WS for telecom exist: Parlay-X: enphasis must be put on refining and making them popular n Concrete examples of application of WS in Telecom (automated appointment reminder, public sector property maintenance … enhanced) l Real web services need policy and security control – SDOs must work on this

Messages from S2: SOA in telecoms today (2) n Microsoft Mediaroom l Brand name for IPTV solution: platform for delivery of video over (reliable) IP network l Broad view of the End-2-End IPTV solution: content acquisition, content protection, service management, subscriber management, service delivery, service consumption l Provided high level view o the architecture l SOA enables highly decoupled, modular and interoperable architecture l Understood OSS and BSS functionalities applied to the platform l Use SOAP based web services n Loosely coupled services l Lessons learned n Web services ala RPC increased coupling and reduced agility n SOAP limitations (exposing/retrieving large resources and low end hardware) n It is critical adding better control for accessing server resources n Modeling unknown applications is hard n Saying “contract first” is not good enough l Future needs n Better control of workflow n Simplify access to resources to facilitate application extensibility n Emphasis on modeilng (access profiles, layering of interfaces) l Need standards on SLA management

Messages from S3 - Telecom Standards n OMG l Possible new OASIS WIs n Extend WS protocols to allow the expression of the non-functional properties of services and support their discovery based on their NFP, enable testing …, address OMG resulting work to support SOA push model n Develop lightweight Process-oriented runtime languages (e.g. BPEL) for composing modern time sensitive, context-aware Telecom services n Harmonize complimentary OMG and OASIS standards such as BPEL with OMG BPMN n OMA l There are some concerns in OMA regarding the real-time, carrier-grade performance of BPEL, when policy processing is transparently applied to all requests in the OSE. l For their Web Services related activities, OMA may benefit from the input and WS expertise of the OASIS Telecom Member Section… improvements to OWSER, PEEM= n TM Forum l SDF initiative n Bi-lateral collaboration in progress n Specific issues from SDF as “proposals of improvement / gaps” on OASIS standards l NGOSS Contracts: proposed for examination by OASIS n ITU-T SG13 l Capabilities as service enabling toolkit l Work Item on Open Service Environment capabilities for NGN: Working on Functional requirements for OSE l Need to enhance existing collaboration with other SDOs

General takeaways n SOA Standards for Security management, policy management, administration management … “ service management” can help the adoption of SOA within the Telecom world n Operators have concrete requirements on SOA  provide them to TMS n Coordination between SDOs is necessary to avoid overlaps and over-spendings

Next steps (within the TMS) n Finalize Charter of first TC within the TMS l Ready by end-October ‘08 n Start technical work on gaps / issues collection – early 2009 l CONTRIBUTE to the first TC l Become members of the TMS n Prepare new edition of SOA Telecom workshop for 2009 … ?

Future references and questions n OASIS membership l n TMS Steering Committee l Abbie Barbir: l Stephane Maes: l Orit Levin: l Michael Brenner: l Enrico Ronco: l Takashi Egawa: l Anthony Nadalin:

(Very) final remark n Thanks to all that worked to make this event happen l CA for the premises l Organizing committee l Session chairs and speakers l OASIS Staff l … Attendees