TM Forum SDF (Service Delivery Framework): Program overview

1. TM Forum SDF (Service Delivery Framework):Program overview Tony Richardson - TM Forum Jenny Huang – AT&T

2. Covered topics • TM Forum SDF Program • SDF Reference Model • Working with Other Industry Groups • SDF Requirements • Future Work

3. TM Forum SDF Program

4. The TM Forum SDF Program • The TMF SDF program defines the framework that supports and integrates all functions required for the lifecycle of a service delivered to a Customer, across all stakeholders in a Service Provider environment. It unifies under a common logical view service design, creation/composition, deployment, activation, provisioning, sale and campaign management, execution, operations, charging, billing and revenue management, retirement, monitoring and trouble resolution etc. to achieve the overall SDF business objectives.

5. Attempt to position SDF and to illustrate relationship with OSS/BSS Internet / 3rd Parties / Enterprises SDF SDP Application suites Service Layer SCE Application Servers IMS Control Layer SS7 SIP / IMS OSS/BSS Platforms IP / MPLS / PBT SONET / SDH / WDM Transport Layer Wireline: DSL, Cable, FTTx, PSTN Wireless: 2G, 3G WiFi, WIMAX Access Layer Device / Client Layer

6. TM Forum SDF program: tasks for Phase 2 SDF Reference Model specification / enhancement SDF Management Requirements specification SDF positioning respect to related work in other Industry Groups Communication to TM Forum and Industry TM Forum SDF Program Phase 2 SDF Overview TM Forum’s Board strategic indications TR 139 Tool selection Other TM Forum work areas TMF 519 SDF Business Agreement Other Industry Groups contributions TR 141 SDF Industry Groups Positioning Document

7. TM ForumSDF Reference Model TR 139 V1 & 2: “SDF Overview” Jenny Huang

8. Note for the audience • The TM Forum SDF team released TR 139 v1 “SDF Overview” in November 2007 • Provides a first version of the SDF objectives and Reference Model • Currently a revision of such document is in progress • Next slides refer to the Version 1.0 “approved document” but highlight changes in progress

9. TM Forum SDF Reference Model TR139 – V2 High Level Overview Customer, Suppliers, Partner Services Management Services SDF Management Support Services SDF Services Infrastructure Services SDF Infrastructure Support Services Resource Services End-user Services (Draft ! - work in progress)

10. Some basic definitions – in review • Service A Service exposes capabilities via one or more interfaces. • SDF Service A SDF Service is a Service that exposes one or more SDF Service Management Interface(s). • SDF Service Management Interface (SDF Service MI) A SDF Service Management Interface exposes the management capabilities of a SDF Service. • SDF Service Functional Interface(SDF Service FI) A SDF Service Functional Interface exposes capabilities of a SDF Service other than those exposed through its SDF Service Management Interface. • SDF Management Support Service (SDF MSS) A SDF Management Support Service consumes the SDF Service Management Interface of a SDF Service to manage the SDF Service. • SDF Infrastructure Support Service (SDF ISS) A SDF Infrastructure Support Service provides reusable functionalities, exposed via functional interface(s), to support the SDF.

11. Overall context for the “TM Forum SDF Reference Model” for SDF Services and their Management SDF Management Support Service Functional Interface SDF Service Functional Interface Management Services SDF Service Management Interface Consumer SDF Service Management Interface <qualified name> SDF Services SDF Management Support Services (SDF MSS) SDF Infrastructure Support Service Consumer Infrastructure Service Consumer Resource Service Consumer SDF Service Consumer SDF Infrastructure Support Service Functional Interface Infrastructure Service Functional Interface Resource Support Functional Interface SDF Infrastructure Support Services (SDF ISS) Resource Services Infrastructure Services Legend Services in SDF team scope Management Interface in SDF team scope SDF required Consumer Services out of SDF team scope Functional Interface out of SDF team scope Consumer out of SDF team scope Items for further study (Draft ! - work in progress) – May 19, ‘08

12. Example scenario: session based service Coupon Service Service Launch 12 SDF Mgmt Support Service Service Lifecycle Service Enablers Operations Support and Applications SDF Registry/ Repository Find SDF Components Content SP Domain Service Catalog Return Coupon 13 Advertising Service Request Service Information Request Coupons 16 17 10 HTTP Server 19 Request Map/Directions Return Map, Directions, & Discount Coupon 1 14 Map & Directions Service Mapping Service Service request to Web Server Map SDF Session 15 Return Map/Directions 6 Find SDF Components 9 Invoke Directions Service , Lat/Long, Restaurant Return Service Details 18 Return Map, Directions, Coupon Service Lifecycle Service Enablers Operations Support and Applications 4 Network SP Domain Service Orchestration Location Map SDF Session Request Phone Location Service Launch 7 8 Return Lat/Long 2 5 Request Service Details Return Service Details Launch SDF Session 3 1 SDF Infrastructure Centric 11 SDF Registry/ Repository Location enabler 1 SDF Service Centric Service Catalog Network Positioning Service

13. TM Forum SDF - Working with Other Industry Groups TR 141 v.1: SDF Industry Groups Positioning Document

14. Incorporating Industry Groups input into SDF • Many other Industry Groups involved in activities related to SDF development • Specific SDF work activity aimed at identifying possible Industry Groups contributions / working relationships • TR141 – Industry Group Positioning Document used to capture results • Information captured through F2F workshops, conference calls and direct discussions • TR141 used to put detailed work co-operation agreements in place with other Industry Groups

15. Industry Groups involvement • OMA • OSE / OSPE (open SDP for mobile service providers) • IPsphere • Pan-SP B2B agreements on supply of IP-based services • Parlay / Parlay X • Network Service interfaces • SDP Alliance • Practical best-of-breed SDP component integration • OASIS • IT capabilities for Service Component definition / combination • ETSI / TISPAN • NGN Sub-system components / Management Architecture • ITU-T / NGNMFG • NGN Management Roadmap • IEEE/NGSON • NGN Overlay Network • ATIS / TMOC • IPTV Management, NGS Accounting • CableLabs • Positioning of cable-based services / specifications

16. Industry Group References(partial list) OASIS/W3C/OMG UML Profiles, SOA infrastructure, eBusiness WS based management, appl. Dev. Env. ATIS/TMOC OSS Ref. framework for IPTV & IP acct. mgm OMA (OSPE, CSSM, PEEM, CBCS … ) SDF resource management & policy framework CableLabs Provide mgmt information, Content Metadata, interface protocols required for cable industry TISPAN WG8 NGN OSS Interface Architecture Subscription Mgmt Customer, Supplier, Partner Services IPsphere Pan-provider service activation and assurance IPsphere Pan-provider service activation and assurance SDF Mgmt BSS/OSS SDP Alliance Stds Interoperability Service Enablers & Applications Parlay Network/Service Abstraction Service Lifecycle Support Integration Infrastructure SDF Managed Resources IEEE/NGSON Emerging service architecture Network & IT Resources End-userServices

17. Further Work with IGs • Agreeing contributions / working relationships • Agree positioning of SDF and NGN – and associated Service and Management interfaces • Start detailed joint work with selected IGs (e.g. OMA, OASIS) • Provide Industry awareness

18. TM ForumSDF Requirements TMF 519: SDF Business Agreement

19. TMF 519: SDF Business Agreement - Requirements • Main characteristics • The SDF Business Agreement document contains the Requirements that define the Service Delivery Framework • List of Business Objectives (19) • List of Technical Objectives (12) • SDF requirements are divided in categories (in line with Reference Model): • Requirements on SDF Infrastructure (25) • Requirements on SDF Managed Entities (9) • Requirements on SDF Management (34) • Requirements on SDF Functional Capabilities (10) • Requirements on SDF support for Customer, Supplier and Partner relationships (6) • Some info on the “process” to define the BA • Specific use cases were developed to define scenarios for the SDF and gather requirements • BA document obtained by active team commitment: more than 20 written contributions, ad hoc meetings / calls, debate and synthesis • Important remark: The SDF team employed the usage of a tool (IBM RequisitePro) for execution of the task • Deliverable ready by mid June 2008

20. Examples of SDF Objectives • Business Objectives • The SDF MUST enable reduction of cost and cycle time to translate business ideas to market offerings (in particular by an effective service lifecycle management throughout the entire ecosystem including operation support). • The SDF MUST support efficient lifecycle management of services based on composition and reuse of existing and new services with the ability to provide differentiated services to all stakeholders in a Service Provider environment. • The SDF MUST enable a Service Provider to participate in an open market of SDF Services. • Technical Objectives • The SDF MUST ensure that information associated to the elements that are manipulated by any combination of reprogramming, re-purposing and composition done statically or dynamically, is itself manipulated in ways that are coordinated and consistent with the manipulation. • The SDF MUST NOT normatively specify beyond interoperability purposes. The SDF MUST rely on the most widely used and generic technologies. when multiple alternatives exist. For a comprehensive list of objectives refer to TMF 519. Draft available on SDF CWS – Team plan is to release document by June

21. Examples of SDF Requirements • Requirements on SDF Infrastructure • The SDF Infrastructure MUST enable flexible mash up, composition and reuse of pre-packaged elements. It must be based on standard IT technology as used in other industries to leverage economy of scale and maximize support. • The SDF Infrastructure MUST enable management of services as they are reused, reprogrammed or composed. • The SDF Infrastructure MUST provide SDF Services catalogues and other repositories (e.g. metadata), which contain all the elements (e.g. existing SDF Services, their dependencies, etc.) available to build new SDF services. • Requirements on SDF Managed Resources • Every SDF Service in the SDF MUST provide a “SDF Service Management Interface” to enable exposure of all appropriate operation and management functions (such as, but not limited to: configuration, performance management, retirement, fault handling, versioning, monitoring, usage, etc.) of the SDF Service. • For the SDF to be able to manage a resource that is outside the scope of SDF, that resource MUST be exposed as a SDF Service. • Requirements on SDF Management • The SDF MUST support functionality to enable the management of the lifecycle of SDF Services. • The SDF MUST enable the configuration of specific performance parameters for SDF Services by means of the SDF Service Management Interface (SDF Service MI) (e.g. driven by customer experience). • Requirements on SDF Functional Capabilities • The SDF MUST support an explicit state model which enables the management of the lifecycle of a SDF Service.

22. Additional Information

23. Focus for SDF Project - Phase 3 • Current view: • TM Forum SDF IA document • RFI / RFQ to Vendors against BA • Detailed Gap Analysis – SDF / TM Forum Standards • Detailed CR to existing TM Forum Standards • Increase linkage with TM Froum Teams • Joint work plans with other IGs • . . . • June Team Action Week will be an important occasion for Phase 3 planning and consolidation • Final remark • Team is active, mailing list has many members … but it is always possible to join the team and contribute in its steering and development

24. Some info on the TM Forum SDF team • More than 320 subscribers to SDF exploder list • Regular weekly teleconferences on Thursdays at 16:00 UK time (around 20 – 25 participants) • Expecting 4 + face to face meetings in 2008: Regular meetings at TM Forum Team Action Weeks + ad hoc meetings • Active SDF Phase 2 contributions from various Companies, among which Alcatel-Lucent, AT&T, BT, CA, CIMI Corp., IBM, Microsoft, NEC Europe, NetCracker, Oracle, Telecom Italia, Telefonica I+D, SquareHoop, TM Forum, … and more • SDF Management team • E. Ronco (Telecom Italia, seconded to TM Forum): SDF Program Manager • J. Huang (AT&T): Co-chair, Service Provider champion • J. Vandenberghe (Alcatel – Lucent): Co-chair, Vendor champion • T. Richardson (TM Forum): Industry Group Coordination, TM Forum staff support

25. Thank you for listening • Participation/Contribution • Web page: http://www.tmforum.org/TechnicalPrograms/ServiceDeliveryFramework/4664/Home.html • Open contribution and open participation • To register go to http://www.tmforum.org/cws • Select Service Delivery Framework team • Number of Web Community discussions on “Work Themes”: http://www.tmforum.org/community/forums/62/ShowForum.aspx • Weekly conference call: • Thursday 16:00 UK, 11:00 EST, 17:00 CET • International dial in number: + 1 6172138002; Participant pass code: 58416317#

26. Backup

27. General Context • Change of Communications Industry Landscape • New providers (e.g. Content) enter in the market and organizations operate using more complex business models. • Delivery of next generation services happens in a framework where the linesbetween Network and IT are blurred. • IT expands its footprint from supporting services to becoming part of the service to customer. • Customers / end Users have greater expectations for: • blending existing and new services • supply of services anywhere, anytime, and through any chosen access means. • Increasing pressure for efficient and effective Service Management. • Necessity for near-zero touch of business processes for delivering “next-gen services” by integrating existing systems (both for Telco / non-Telco SPs). • Need to create composite service marketplace across industry sectors that also need to be managed & monetized. • Service Providers need interoperability and agreed levels of compatibility across Service Delivery Platforms (SDPs).

28. TM Forum’s response: Service Delivery Framework • The TM Forum launched the Service Delivery Framework (SDF) programme to address the industry challenge of producing an environment for the management of Next Generation Services. • SDF supports and integrates all aspects in the lifecycle of “next-gen services” delivered to a customer, across all the stakeholders, in an integrated Service Provider environment. • SDF has the objective to unify under a common logical view all the functions to support the service lifecycle: conceptualization, design, deployment, activation (execution), operation, retirement. • SDF operation is based upon a defined Reference Model, which itself is based upon SOA principles. • SDF impacts • Management specification for SDF will be realised through updates and additions to existing TM Forum artefacts (Business Process Framework, Information Framework etc.). • New specifications will be created by TM Forum (or liaised with other SDOs / Foras) • SDF will have impact on “new” B/OSS systems design and development. • Strong liaisons with other Industry Groups has been established in order to share the SDF vision / link into related work in these Groups.

29. A brief history of SDF within TM Forum • Aug. 2006: Launch of “Landscape Team” by TM Forum Board • Analyze emerging Web 2.0, SDP, content and media convergence environment • Need for “SDF” to “integrate” emerging areas as IMS, web 2.0, SDPs, etc. • Need to focus on Service Management aspects • 1H 07: SDF team set-up • Merge with NGN-M team • Work Chartering • 2H 07: SDF Phase 1 • SDF Reference Model (TR 139) Version 1.0 – Nov. 07 • Industry Group liaisonscommenced • 1H 08: SDF Phase 2 • Current work • … + 320 subscribed to SDF exploder, + 150 companies represented • Active participation on TM Forum CWS • 3 major deliverables developed