OASIS: Integrating Standards for Web Services, Business Processes ...

563 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
563
On SlideShare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

OASIS: Integrating Standards for Web Services, Business Processes ...

  1. 1. Adopting SOA for Telecom Workshop Sept. 30 th , 2008 Telecom Member Section
  2. 2. <ul><li>Telecom Member Section </li></ul><ul><ul><li>http://www.oasis-telecom.org/ </li></ul></ul><ul><li>Steering Committe </li></ul><ul><ul><li>http://www.oasis-telecom.org/steering-committee </li></ul></ul><ul><li>Current Members </li></ul><ul><ul><li>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. </li></ul></ul><ul><li>Information including how to become a member </li></ul><ul><ul><li>Dee Schur [email_address] </li></ul></ul>Useful links <ul><li>Orit Levin, Microsoft </li></ul><ul><li>Stephane Maes, Ph.D., Oracle - Co-chair </li></ul><ul><li>Tony Nadalin, IBM </li></ul><ul><li>Abbie Barbir, Ph.D., Nortel - Co-chair </li></ul><ul><li>Michael Brenner, Alcatel-Lucent </li></ul><ul><li>Enrico Ronco, Telecom Italia </li></ul><ul><li>Takashi Egawa, NEC </li></ul>
  3. 3. Workshop Program Committee <ul><li>Michael Giordano (Avaya) </li></ul><ul><li>Abbie Barbir (Nortel) </li></ul><ul><li>Hanane Becha (Nortel) </li></ul><ul><li>Tony Nadaline (IBM) </li></ul><ul><li>Stephane Maes (Oracle) </li></ul><ul><li>Sune Jakobsson (Telenor) </li></ul><ul><li>Rakesh Radhakrishnan (Sun Microsystems) </li></ul><ul><li>Ian Jones (BT) </li></ul><ul><li>And Many Many thanks to all the OASIS Staff and our host CA </li></ul>
  4. 4. Closing Remarks Enrico Ronco – Telecom Italia [email_address] www.oasis-open.org
  5. 5. Sessions of this Workshop <ul><li>Welcome & Opening Keynote (Nortel) </li></ul><ul><ul><li>Providers Perspectives on SOA in Telecom (BT) </li></ul></ul><ul><li>Panel on Embedding Communications into IT Applications: A Vendor Perspective (Telenor) </li></ul><ul><ul><li>Accenture, Avaya, Oracle </li></ul></ul><ul><li>S1 : Challenges of Telecom Services in SOA Environment: Lessions Learned and Case Studies (Avaya) </li></ul><ul><ul><li>SOA Security: Challenges, Patterns and Solutions (IBM) </li></ul></ul><ul><ul><li>Digital Identities for Networks and Convergence (NEC Europe) </li></ul></ul><ul><ul><li>Operator Perspective: Dealing with Issues & Relationships in a changing eco-system ( Vodafone ) </li></ul></ul><ul><ul><li>Service Oriented Architecture and Use of SOA at Telenor Nordic (Telenor) </li></ul></ul><ul><ul><li>Overcoming the Deployment Blues: Preparing for Comms Enablement (Nortel) </li></ul></ul><ul><ul><li>Elements of SOA in TM Forum’s Service Delivery Framework and its Usecases (Oracle) </li></ul></ul><ul><li>S2 : SOA Solutions in Telecom Today (Oracle) </li></ul><ul><ul><li>Service Oriented Authorisation for Managing Services and Devices in Telecommunication Networks ( Axiomatics) </li></ul></ul><ul><ul><li>Services Exploiting SOA and Web Service Technology in Modern Telcos ( Aepona) </li></ul></ul><ul><ul><li>Microsoft Mediaroom as a SOA for IPTV ( Microsoft) </li></ul></ul><ul><li>S3 : Telecom Standards (BT) </li></ul><ul><ul><li>OMG Perspective on Standards </li></ul></ul><ul><ul><li>OMA Perspective on Standards </li></ul></ul><ul><ul><li>TM Forum Perspective on Standards </li></ul></ul><ul><ul><li>Towards a SOA/WS Enabled NGN Open Service Envornment: Ongoing Develop. in ITU-T SG13 </li></ul></ul>
  6. 6. Highlights of the day <ul><li>Introduced the OASIS Telecom MS and its main objectives </li></ul><ul><li>Interesting Keynote : operator’s view on SOA </li></ul><ul><li>Panel: Heard how Vendors are facing specific issues on “SOA for Telecom” </li></ul><ul><li>S1: Heard of specific Issues currently faced within the Telecom industry </li></ul><ul><li>S2: heard of SOA solutions already in place </li></ul><ul><li>S3: Known what other “Telecom” SDO s are currently doing on SOA and viewed some possible concrete links </li></ul>Note: I tried to derive possible implications of exposed presentations on TMS future activities
  7. 7. The OASIS Telecom Member Section <ul><li>Objectives </li></ul><ul><ul><li>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 </li></ul></ul><ul><ul><li>Collect and solve telecommunications related issues within the SOA framework </li></ul></ul><ul><ul><li>Bridge between various SDOs applying SOA and WS to the telecom sector </li></ul></ul><ul><li>Next Steps (… first steps) </li></ul><ul><ul><li>Start first TC (January 09) on Gaps – issues – problems on OASIS SOA standards for Telecoms </li></ul></ul><ul><ul><li>… solve such problems </li></ul></ul>
  8. 8. Messages from the Keynote <ul><li>Shift from Network Operator to Service Provider </li></ul><ul><ul><li>Do business within “the long tail” </li></ul></ul><ul><ul><li>Communication with communities </li></ul></ul><ul><li>Need for common capabilities (shift from vertical applications) </li></ul><ul><li>Agnostic access to networks, common set of “components for services”: (profile, messaging, call servers, media servers…) </li></ul><ul><li>Convergence between telecom “platforms” and enterprise “applications”: Network competences now merged with IT competences </li></ul><ul><li>Common set of standards now available to enable “web platforms” </li></ul><ul><ul><li>Software Development moving from proprietary monolithic telecom applications to standards-based layered J2EE applications </li></ul></ul><ul><li>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 </li></ul><ul><ul><li>Focus effort on building applications customers really want (e.g. sales force management) </li></ul></ul><ul><li>Work to deliver “service building blocks” </li></ul><ul><li>No Killer app. / Yes “Killer attribute”: ability to change rapidly </li></ul>
  9. 9. Messages from the Panel : vendors perspective <ul><li>Giordano: </li></ul><ul><ul><li>Need for an agile communication creation environment </li></ul></ul><ul><ul><li>Deliver different level of granularity for different customers </li></ul></ul><ul><ul><li>OASIS can help in filling some gaps (i.e. security, manageability, serviceability of “communication platforms”) </li></ul></ul><ul><ul><li>Occasion for a full automation of business processes (incl. manual processes) – gave examples (sales force automation, extension of communication services with enterprise folders </li></ul></ul><ul><li>Sabadotto: </li></ul><ul><ul><li>How to implement SOA in a holistic view? (need for a proper governance capability) </li></ul></ul><ul><ul><li>4 different levels of maturity of SOA adoption in Telcos: (Plan & Organize, Deploy, Architected, Industrialized). Not necessary to run through them in sequence. </li></ul></ul><ul><ul><li>Understand customer need, make a plan, iterate within phases (level 3 is the most difficult) </li></ul></ul><ul><ul><li>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. </li></ul></ul><ul><ul><li>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 … </li></ul></ul><ul><li>Maes: </li></ul><ul><ul><li>Bridge the “Web” world with the “telco” world, and “Traditional Telcos” have goals which are different from the “Internet SP” </li></ul></ul><ul><ul><li>Concept of “Standard-Based Service Delivery Platform”: -  look at the OMA OSE </li></ul></ul><ul><ul><li>Then a “process” is suggested for successful deployment of the “Standard SDP” </li></ul></ul><ul><ul><li>Mention of TM Forum Service Delivery Framework (SDF) </li></ul></ul><ul><ul><li>Mention of Oracle’s Application Integration Architecture </li></ul></ul><ul><ul><li>No particular challenge in making things happen, but SOA is not yet CARRIER GRADE </li></ul></ul><ul><ul><ul><li>High availability, predictable low latencies, efficient, scalable … </li></ul></ul></ul><ul><ul><ul><li>Difficult to guarantee throughput, SLA, QoS, lifecycle management of mash ups </li></ul></ul></ul>
  10. 10. In summary (from Sune Jakobsson) <ul><li>SOA is technically available </li></ul><ul><li>… but the Web is not ready </li></ul><ul><li>The Web is not regulated, opposed to the traditional Telco, that is required to provide carrier-grade </li></ul><ul><li>Catch the “long tail” </li></ul>
  11. 11. Messages from S1 : lessons and case studies (1) <ul><li>Vodafone : real-life experience </li></ul><ul><ul><li>Operators want to use mature technologies o help them solve their problems </li></ul></ul><ul><ul><ul><li>Are WSs easing the integration? </li></ul></ul></ul><ul><ul><ul><li>Is REST applicable to telecoms? </li></ul></ul></ul><ul><ul><ul><li>Mash-ups; exciting, but realistic ? </li></ul></ul></ul><ul><ul><li>Operators are recognizing user data as a corporate asset (not only for liability); NEW Cash flow potential with mobile advertisemet </li></ul></ul><ul><ul><li>SOA Standards must help Operators to manage such asset </li></ul></ul><ul><ul><ul><li>Operators are invited to provide requirements to the SDOs (e.g. OASIS TMS) </li></ul></ul></ul><ul><ul><li>Operators need clear guidance on “minimum interoperable WS-stack” to use </li></ul></ul><ul><li>Telenor : real-life experience </li></ul><ul><ul><li>Presented real-life experience in “ implementing / deploying’ SOA in Telenor </li></ul></ul><ul><ul><li>What is the correct granularity of a SOA Service ? </li></ul></ul><ul><ul><li>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 </li></ul></ul><ul><li>Nortel : lessons learned from 4 key implementations </li></ul><ul><ul><li>Within one case it was required us to go well beyond Parlay X and other telecom standards </li></ul></ul><ul><ul><li>Interfaces need to be kept simple so that non-telecom developers could easily make use of them </li></ul></ul><ul><ul><li>Need of mentality change: difficult not to expose “telecom” capabilities (such as session ids) to the application via APIs </li></ul></ul><ul><ul><li>Many internet developers struggle with the WS-* specifications: they expect REST-style interfaces instead </li></ul></ul><ul><ul><li>Necessity to extend standards for location-setting and presence </li></ul></ul><ul><ul><li>Need to change some BPEL specs? Customers are just beginning to experiment it – 1 more year to know </li></ul></ul>
  12. 12. Messages from S1 : lessons and case studies (2) <ul><li>NEC: identity management </li></ul><ul><ul><li>SWIFT project: solve identity fragmentation of today, develop EU identity architecture </li></ul></ul><ul><ul><li>Analyzed today’s identity management within different providers – project will last until 2010 </li></ul></ul><ul><ul><li>Virtual identities concept: many faces for transactions to separate roles or for privacy roles </li></ul></ul><ul><ul><li>Concept of virtual identity applicable down to the network </li></ul></ul><ul><ul><li>Defined a set of building blocks of an “Identity Architecture” </li></ul></ul><ul><ul><ul><li>Mobility, Security, AAA, Devices … </li></ul></ul></ul><ul><ul><li>Goals to achieve </li></ul></ul><ul><ul><ul><li>Liberate user from device(s) by enabling use of several interchangeable devices </li></ul></ul></ul><ul><ul><ul><li>Network Access automatically made available based on service requested </li></ul></ul></ul><ul><ul><li>Identity becomes a convergence technology: forms the bridge between networks, services, content… </li></ul></ul><ul><ul><li>Objective is to bridge existing solutions together </li></ul></ul><ul><ul><li>Proposal of the “identiNET” … </li></ul></ul><ul><ul><li>Issue: who is accountable on the management of the “federation of identities” ? </li></ul></ul><ul><li>IBM : security </li></ul><ul><ul><li>Challenge emerges on identity and access management </li></ul></ul><ul><ul><li>Need of support of virtual identity and the related trust framework – personalization and virtual identity </li></ul></ul><ul><ul><li>Externalize policies (and security functions) from applications </li></ul></ul><ul><ul><li>Open standards based approach is the way to go </li></ul></ul><ul><ul><li>Need for real time distributed policy negotiation and enforcement : OASIS TMS must take this issue and promote its solution within the appropriate SDO </li></ul></ul><ul><li>TM Forum </li></ul><ul><ul><li>Work for the enablement of lifecycle management of “services”, not only within one SP’s domain </li></ul></ul><ul><ul><li>There may be some modifications to the OASIS SOA RM (SDF Service has > than 1 SI) </li></ul></ul><ul><ul><li>Touch points for OASIS TMS and TM Forum SDF </li></ul></ul>
  13. 13. Messages from S2 : SOA in telecoms today (1) <ul><li>Axiomatics </li></ul><ul><ul><li>How does standardized authorization mnagement support SOA in Telecom Networks (focus on use of XACML, at service and device configuration level) </li></ul></ul><ul><ul><li>Authorization is meant as a service to other applications and services </li></ul></ul><ul><ul><ul><li>As well as location, IPTV … it would be important to provide also Authorization as a “telecom service” </li></ul></ul></ul><ul><ul><ul><li>Operators would like to avoid micro-management of services and features of service providers (avoid micro-management) </li></ul></ul></ul><ul><ul><ul><li>SPs need to control their services themselves </li></ul></ul></ul><ul><ul><li>Gave examples on access permissions (e.g. end user access to service) and on specific services for users (e.g. parking service… different policies) </li></ul></ul><ul><ul><li>Issues: policy enforcement, policy administration, attribute management </li></ul></ul><ul><ul><li>Authorization service shall be provided by Operators to SPs and XACML 3.0 can play an important role </li></ul></ul><ul><li>Aepona: </li></ul><ul><ul><li>Core Telco service enablers: payments, messages, presence, location  they are assets </li></ul></ul><ul><ul><li>SOA is about the interface for 3 rd parties to access such enablers </li></ul></ul><ul><ul><li>3 “killer capabilities”: contextual presence, location – flexible media and conference switching – Intelligent notification services </li></ul></ul><ul><ul><li>WS for telecom exist: Parlay-X: enphasis must be put on refining and making them popular </li></ul></ul><ul><ul><ul><li>Concrete examples of application of WS in Telecom (automated appointment reminder, public sector property maintenance … enhanced) </li></ul></ul></ul><ul><ul><li>Real web services need policy and security control – SDOs must work on this </li></ul></ul>
  14. 14. Messages from S2 : SOA in telecoms today (2) <ul><li>Microsoft Mediaroom </li></ul><ul><ul><li>Brand name for IPTV solution: platform for delivery of video over (reliable) IP network </li></ul></ul><ul><ul><li>Broad view of the End-2-End IPTV solution: content acquisition, content protection, service management, subscriber management, service delivery, service consumption </li></ul></ul><ul><ul><li>Provided high level view o the architecture </li></ul></ul><ul><ul><li>SOA enables highly decoupled, modular and interoperable architecture </li></ul></ul><ul><ul><li>Understood OSS and BSS functionalities applied to the platform </li></ul></ul><ul><ul><li>Use SOAP based web services </li></ul></ul><ul><ul><ul><li>Loosely coupled services </li></ul></ul></ul><ul><ul><li>Lessons learned </li></ul></ul><ul><ul><ul><li>Web services ala RPC increased coupling and reduced agility </li></ul></ul></ul><ul><ul><ul><li>SOAP limitations (exposing/retrieving large resources and low end hardware) </li></ul></ul></ul><ul><ul><ul><li>It is critical adding better control for accessing server resources </li></ul></ul></ul><ul><ul><ul><li>Modeling unknown applications is hard </li></ul></ul></ul><ul><ul><ul><li>Saying “contract first” is not good enough </li></ul></ul></ul><ul><ul><li>Future needs </li></ul></ul><ul><ul><ul><li>Better control of workflow </li></ul></ul></ul><ul><ul><ul><li>Simplify access to resources to facilitate application extensibility </li></ul></ul></ul><ul><ul><ul><li>Emphasis on modeilng (access profiles, layering of interfaces) </li></ul></ul></ul><ul><ul><li>Need standards on SLA management </li></ul></ul>
  15. 15. Messages from S3 - Telecom Standards <ul><li>OMG </li></ul><ul><ul><li>Possible new OASIS WIs </li></ul></ul><ul><ul><ul><li>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 </li></ul></ul></ul><ul><ul><ul><li>Develop lightweight Process-oriented runtime languages (e.g. BPEL) for composing modern time sensitive, context-aware Telecom services </li></ul></ul></ul><ul><ul><ul><li>Harmonize complimentary OMG and OASIS standards such as BPEL with OMG BPMN </li></ul></ul></ul><ul><li>OMA </li></ul><ul><ul><li>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. </li></ul></ul><ul><ul><li>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= </li></ul></ul><ul><li>TM Forum </li></ul><ul><ul><li>SDF initiative </li></ul></ul><ul><ul><ul><li>Bi-lateral collaboration in progress </li></ul></ul></ul><ul><ul><ul><li>Specific issues from SDF as “proposals of improvement / gaps” on OASIS standards </li></ul></ul></ul><ul><ul><li>NGOSS Contracts: proposed for examination by OASIS </li></ul></ul><ul><li>ITU-T SG13 </li></ul><ul><ul><li>Capabilities as service enabling toolkit </li></ul></ul><ul><ul><li>Work Item on Open Service Environment capabilities for NGN: Working on Functional requirements for OSE </li></ul></ul><ul><ul><li>Need to enhance existing collaboration with other SDOs </li></ul></ul>
  16. 16. General takeaways <ul><li>SOA Standards for Security management, policy management, administration management … “ service management” can help the adoption of SOA within the Telecom world </li></ul><ul><li>Operators have concrete requirements on SOA  provide them to TMS </li></ul><ul><li>Coordination between SDOs is necessary to avoid overlaps and over-spendings </li></ul>
  17. 17. Next steps (within the TMS) <ul><li>Finalize Charter of first TC within the TMS </li></ul><ul><ul><li>Ready by end-October ‘08 </li></ul></ul><ul><li>Start technical work on gaps / issues collection – early 2009 </li></ul><ul><ul><li>CONTRIBUTE to the first TC </li></ul></ul><ul><ul><li>Become members of the TMS </li></ul></ul><ul><li>Prepare new edition of SOA Telecom workshop for 2009 … ? </li></ul>
  18. 18. Future references and questions <ul><li>OASIS membership </li></ul><ul><ul><li>[email_address] </li></ul></ul><ul><li>TMS Steering Committee </li></ul><ul><ul><li>Abbie Barbir: [email_address] </li></ul></ul><ul><ul><li>Stephane Maes: [email_address] </li></ul></ul><ul><ul><li>Orit Levin: [email_address] </li></ul></ul><ul><ul><li>Michael Brenner: [email_address] </li></ul></ul><ul><ul><li>Enrico Ronco: [email_address] </li></ul></ul><ul><ul><li>Takashi Egawa: [email_address] </li></ul></ul><ul><ul><li>Anthony Nadalin: [email_address] </li></ul></ul>
  19. 19. (Very) final remark <ul><li>Thanks to all that worked to make this event happen </li></ul><ul><ul><li>CA for the premises </li></ul></ul><ul><ul><li>Organizing committee </li></ul></ul><ul><ul><li>Session chairs and speakers </li></ul></ul><ul><ul><li>OASIS Staff </li></ul></ul><ul><ul><li>… Attendees </li></ul></ul>

×