Andrew White Chair, ATIS Cloud Services Forum Principal Consultant, Nokia Siemens Networks. Gary Munson Vice Chair, ATIS Cloud Services Forum

Transcription

1 Moderator Speakers Rich Karpinski Editor-in-Chief Connected Planet Andrew White Chair, ATIS Cloud Services Forum Principal Consultant, Nokia Siemens Networks Gary Munson Vice Chair, ATIS Cloud Services Forum Lead Member of the Technical Staff, AT&T Percy Tarapore Lead Contributor, ATIS Cloud Services Forum Lead Member of the Technical Staff, AT&T

2 Carriers and the Cloud Setting the stage Rich Karpinski Editor-in-Chief Connected Planet

3 Carriers and the Cloud Telecom operators are already knee deep in the cloud Evolution of co-location, Web hosting, enterprise services businesses Acquisitions are accelerating moves into the cloud Verizon/Terremark; CenturyLink/Savvis; Time Warner/Navisite; etc Services from those units encompass hosting, software-as-a-service, and increasingly infrastructure-as-a-service What is unique about telco-in-the-cloud? Long history of delivering services, multi-tenant, SLA-driven, five-nines, etc. Can span SLA from necessary network on-ramp to the infrastructure/service Uniquely communications-based cloud services /collaboration VoIP Unified Communications CDN/content cloud (mobile too)

4 Carriers within the Cloud Ecosystem A conversation with telcos about the cloud is, well.different Startups Amazon, Google, Rackspace see the cloud as virtualized, pay-by-the-drop compute infrastructure they target fellow Web startups IT companies IBM, HP, Microsoft, even Cisco see the cloud as IT infrastructure outsourced.to THEM. They have existing desktop, server, storage, enterprise network businesses they need to defend and extend Telcos talk about SaaS, IaaS, virtualized storage/compute, etc..but also about content delivery (CDNs), service delivery (SDPs), unified communications (UC) and the network as one big cloud Different customers, different history, different vocabulary, different focus but ultimately one big cloud

5 ATIS, Telecom and the Cloud Different take on the cloud requires different technology/standards Had the chance to talk with ATIS last week about CDN/cloud efforts Fittingly, ATIS taking telecom-centric view of the cloud CDN interconnection first; next on the agenda: inter-carrier telepresence, cloud VPNs, cloud service on-boarding etc.

6 Background CSF launched mid-february 2011 with the following objectives: Drive the rapid creation and adoption of implementable standards for cloud-based delivery of services; and Address key Service Provider priorities in a managed network environment using an integrated network and IT approach. Initial set of deliverables identified during inaugural meeting focused on inter-provider telepresence, content distribution and VPNs. In March, it was agreed that the primary focus would be to complete Content Distribution Network Interconnection (CDN-I) work in a short time interval. First output document, CDN Interconnection Use Case Specification and High Level Requirements, (ATIS ), released June Available for free via using the code CSF711. 6

7 CSF Members To date, member companies include: Alcatel-Lucent AT&T Brocade BT CenturyLink Cisco Systems Ericsson Fujitsu Huawei Juniper Microsoft Neustar Nokia Siemens Networks Symmetricom Telcordia Verizon ZTE USA 7

8 Broadening Perspective on Cloud (illustrative) Traditional view: Expanding the view: SaaS PaaS Business apps (e.g., Salesforce apps, NetSuite apps) Computing, Storage (e.g., Google Apps Engine, Rackspace Cloud) Web-based applications (e.g., Telepresence, Facebook, Android Marketplace) Network APIs & Device ( e.g., Parlay X / ParlayREST, Presence, MMS, Content Delivery) IaaS Computing (e.g., Google or IBM managed hosting, Amazon EC2) Inter-Provider networking services (e.g., Control Plane, VPNs) 8

9 CDN-I: Business Drivers Key business drivers: Significant growth in CDN market (increases in broadband penetration, internet usage, and demand for content such as video services). Regional CDNs are well-positioned for interconnection to become a global CDN (a valuable cloud services asset for Content Providers): Redirecting download requests for frequently accessed content to lower cost ( optimized ) CDN caches in other CDN domains (geographic proximity, least cost routing, etc.) improves network efficiency. Addressing content requests in the local access network reduces the impact on core networks and peering points. Possibility of utilizing CDN-I for Network-to-Network Interfaces (NNI) between CDN Providers for other cloud services. 9

10 High Level Functions in a CDN Node Management Customer Portals Content Routing Functions Log Management IP Network Provisioning, Operations, Storage Complex Node Management Server Caching & Streaming 10

11 Inter-connected CDN Delivery Model Between Carriers (Cache based distribution) Carrier-1 Network & CDN Carrier-2 Network & CDN Content Delivery Node. Routing, Back-office, etc. Content Delivery Node. Storage, Origin, etc. Network Peering Content Delivery Node. Routing, Back-office, etc. Storage, Origin, etc. Content Delivery Node. Content Delivery Node. Content Delivery Node. Note: only data path is shown for clarity. Request & back-office path not shown. User is getting content sourced from Carrier 1; delivery node is Carrier 2 s, i.e., local. 11 User Content Data Path Node Cache Fill Data Path

12 CDN-I Document Develops use case specifications for CDN-I that: Describe support for the following functions: on-boarding, active interconnection and termination; and Define success scenarios as well as failure conditions and recovery as appropriate. Lists a set of high level requirements in support of these use cases. Scope: Software content items; Cache delivery model; and Peer-to-peer CDN to CDN. 12

13 Key Players & Their Relationships 1 Content Provider Primary CDN Provider Supporting CDN Provider End User Content Provider (CP): The entity that owns or is licensed to distribute and/or sell content or content assets. Although the relevant CDN Provider (Primary or Supporting) delivers content to End Users, a direct logical information flow may be set up between Content Provider and End User (1). Primary CDN Provider: A CDN Provider that has an agreement with a CP to store and deliver content to End Users on the CP s behalf (2). Supporting CDN Provider: A Service Provider who partners with a Primary CDN Provider, to store and distribute content to End Users on behalf of the Primary CDN Provider (3). End Users: Any person or device that is retrieving content from CDN access from S-CDN (4). 13

14 Use Case Areas Content Types and characteristics Off-peak Software Update download Future Work: Peak & on-demand Web, LFD, VOD, etc, Real-time Events Delivery Method Unencrypted HTTP Unicast Cache Distribution, Future Work: Encrypted HTTPS SSL & Multicast Content Provider Life-cycle. (TR Section numbers shown here) Primary & Supporting CDN Life-cycle. (TR Section numbers shown here) On Boarding Capabilities, reservation, trial Certification, capabilities, etc & Presale Postsale On-boarding, Testing Content Delivery Additional & on-demand capabilities, operational management, Performance Active/interconnected Environment End Contr act Purge, etc. Load feedback, log, new capabilities, capacity, price actions, operations outages, notification, etc. Post morte m Root cause, audit Termination Purge, settlements Post mortem 14

15 CDN-I Interface Domains Bi-Lateral agreement between two carrier CDNs. Assume that each carrier peers with another carrier at the CDN Level. Operations & Customer Care Back-Office Routing Delivery Network Interconnection SLA/outages/ticketing, Special customer requests Provisioning, Logs, settlement Traffic distribution, load management, AMT Relay addresses Features, Capacity reservation, Origin access, multicast sources/groups Access, Security Operations & Customer Care Back-Office Routing Delivery Network Interconnection CDN Provider-1 CDN Provider-2 15

16 Life Cycle Interactions & Derived Requirements Primary CDN Provider & Supporting CDN Provider life cycle (P-CDN S-CDN): Use cases describe direct relationships between these two entities. All requirements directly support interactions between them. Content Provider & Primary CDN Provider life cycle (CP P-CDN): Use cases describe what a P-CDN needs to do with S-CDN to support the life cycle with CP. All requirements support necessary P-CDN interactions with S-CDN to support the life cycle with CP. 16

17 Summary of Use Case Requirements Use Case Type Use Case Section # # of Success Scenarios # of Failure Conditions Total # of Requirements P-CDN S-CDN P-CDN S-CDN P-CDN S-CDN N/A 2 P-CDN S-CDN N/A 2 CP P-CDN CP P-CDN CP P-CDN CP P-CDN CP P-CDN N/A 3 CP P-CDN N/A N/A 17

18 Future CDN-I Work Plan Develop use cases & requirements for: Multicast-based content delivery with applicable content types (e.g., live streaming) - Target Possibility of joint work on multicast with ATIS IIF. CDN-I in Federated Environment Target 2011: Multiple CDN Providers with possible 3 rd Party Exchange Entity; and Additional content types (stricter AAA requirements). Charging Target Final objectives: Group comprehensive requirements per applicable interconnection domain; Develop reference architecture for CDN-I NNI with other ATIS Committees such as PTSC; and Enable search for protocols/extensions to support interconnection message exchanges with the IETF CDNi Working Group. 18

19 CSF and Other Cloud Standards Work External collaboration: CSF is evaluating cloud services related work in other SDOs, with special emphasis on content delivery at this time exploring reuse opportunities where appropriate. CSF will look to other SDOs for relevant interface protocols to re-use or extend. Alternative plans to define new if necessary. Internal collaboration Ongoing communications with other ATIS Committees (IIF, OBF, PRQC, PTSC and TMOC) to align work efforts with emphasis on reuse. 19

20 Additional CSF Priority Work Items Develop or adopt cloud services framework; Inter-carrier telepresence; Virtual desktop; Virtual private network; Cloud services lifecycle checklist ; and NNI Reference architecture CSF focus is on inter-operator interaction/interfaces for functioning as one cloud; i.e., cloud infrastructure. 20

21 Service Enabler Approach End users interact with the business application oblivious of the component parts. Subscriber User End Users Service Interaction Management is used to blend service enablers into a business application. Service Interaction Service Applications Reuse Service Service Enablers Resource The Service Enablers expose resources (applications, data, and connectivity) through a defined, reusable interface. App App App Data Data Data Access & Transport Applications Storage and Computing Networks 21

22 Service Creation in the Cloud Service Enabler Characterization provides key non-functional data to populate Service Catalog Service Catalog Core Competency Service Interaction Management Partner Enablers Service catalog and service interaction managers speed time to market and improve service enabler reuse 22

23 Service Enabler Characterization Partial Illustration from ATIS Service Enabler Characterization Technical Report 23

24 Further Information For more information Andrew White, CSF Chair Gary Munson, CSF Vice Chair Next CSF Face to Face Meeting July 18-20, 2011 ATIS Headquarters, Washington, DC 24

25 Visit the ATIS Document Center ( before September 30 th to download your complimentary copy of the CDN Interconnection Use Case Specification and High Level Requirements Standards Document enter promotional code CSF711