Cloud Services Forum March 30, 2011 Welcome to the ATIS CSF Tutorial March 30, 2011; 11 AM ET...

Cloud Services ForumMarch 30, 2011

Welcome to the ATIS CSF Tutorial

• March 30, 2011; 11 AM ET• 866-742-2029, passcode 202-662-8663

We appreciate your cooperation in making this a successful call, please:• Introduce yourself and state your company’s name and committee

affiliation before contributing to a discussion• Do Not place the phone bridge on hold• Turn Off other communication devices or Move Them Away from the

phone you are using• Mute Your Phone if you are not speaking, to avoid unnecessary

echoing (*6 to mute, #6 to unmute if your phone is not equipped)• Dial “00” for Operator Assistance

Cloud Services Forum Tutorial

Andrew WhiteCloud Services Forum Chair

Gary MunsonCloud Services Forum Vice Chair

March 30, 2011


3

Tutorial Objectives

• What is Cloud?– How is this relevant to communications?

• What is the Cloud Services Forum?– How did this group come into being?– What are the goals and objectives?

• How can the CSF interact with other ATIS groups to leverage the current work and knowledge base for Cloud Standards?– How can we ensure compatibility in the Cloud across the

related committee standards?


4

The Creation of CSF

• The CSF is the newest ATIS Forum. • The CSF was formulated in part to address how

service providers will leverage core network and service attributes to adopt, advance and deliver Cloud computing services. CSF is emphasizing an integrated network/IT perspective in its approach.

• This CSF work draws heavily on business use cases that demonstrate Cloud services' potential.


5

The Early Cloud

• Uniform addressing plan• Single, automated user interface• Attach anywhere, call anybody• On demand, scalable

Standard UserInterface

CommonPlatform

GlobalCommunications+ =


Broadening Perspective on Cloud (illustrative)

SaaS Business apps (e.g., Salesforce apps, NetSuite apps)

PaaSComputing, Storage (e.g., Google Apps Engine, Rackspace Cloud)

IaaS Computing (e.g., Google or IBM managed hosting, Amazon EC2)

Web-based applications Internet apps

(e.g., Facebook, Android Marketplace)

Network APIs & Device

( e.g., Parlay X / ParlayREST, Presence, MMS, Content Delivery)

Inter-Provider networking services

(e.g., Control Plane, VPNs)

Expanding the view. Examples: Traditional view

6


Applications

Storage andComputing

Networks

Service Enablers

Applications

End Users

User

Service

Reuse

Resource

Service

App App App

Data Data Data

ServiceInteraction

Subscriber

Access & Transport

The Service Enablers expose resources (applications, data, and connectivity) through a defined, reusable interface.

Service Interaction Management is used to blend service enablers into a business application.

End users interact with the business application oblivious of the component parts.

Service Enabler Packaging

7


8

Service Enabler Characterization

Partial Illustration


9

Service Creation in the Cloud

Core Competency

Partner Enablers

Service catalog and service interaction managers speed time to market and improve service enabler reuse

Service InteractionManagement

Service Catalog

Service Enabler Characterization provides key non-functional data to populate

Service Catalog


10

Fast Forward to Today

• Intuitive• Indispensible• Service-oriented• Integrated into your life

Same Concept, More Apps


11

QuizThe most important aspect of cloud is:A. A fast, always available networkB. The most intuitive user experiencesC. The best services infrastructureD. Skilled people to put it all togetherE. All of the above


Inter-Provider Content Distribution Network

• Network Providers cooperate to cache/distribute content into each other’s networks to download content more locally to users.- Reduced consumption of network resources- Reduced download latency

• Consider the arrangement for doing this as cloud service infrastructure.

• General interest/resonance/willingness to have this item be the initial priority focus in CSF.

12


Inter-connected CDN Delivery Model Between Carriers (Cache based distribution)

Storage, Origin, etc.Storage, Origin,

etc.

Content Delivery Node.






Carrier-1 Network & CDN

Network Peering

Note: only data path is shown for clarity. Request & back-office path not shown.

Carrier-2 Network & CDN

User Content Data Path

Node Cache Fill Data Path

Routing, Back-office, etc.

Routing, Back-office, etc.

User is getting content sourced from Carrier 1; delivery node is Carrier 2’s, i.e., local.

13


AMT Relay


Carrier-1 Network

Network Peering

Note: only data path is shown for clarity. Request & back-office path not shown

Multicast content

Tunneled multicast content

Back-office


Carrier-2 Network

Back-office

Multicast Source

AMT GW

Inter-connected CDN Delivery Model Between Carriers (Multicast based distribution)

Users are getting content sourced from Carrier 1; Replication occurs only in Carrier 2’s network.

14


Peer-Peer Inter-connected CDN Model Interface Domains

Network Interconnection

Delivery

Routing

Back-Office

Operations & Customer Care


Delivery

Routing

Back-Office

Access, Security

Features, Capacity reservation, Origin access, multicast sources/groups

Traffic distribution, load management, AMT

Relay addresses

Provisioning, Logs, settlement

SLA/outages/ticketing, Special customer

requests


Carrier-1 Carrier-2

Bi-Lateral Agreement Between Two Carrier CDNs.Assume that each carrier peers with another carrier at the CDN Level

15


CDN Federation Model Interface Domains


Delivery

Routing

Back-Office



Delivery

Routing

Back-Office

Access, Security

Origin access

Traffic distribution, load management, AMT

Relay addresses

Provisioning, Logs,

settlement

SLA/outages/ticketing, Special customer

requests Operations &

Customer Care

Carrier-1 Carrier-2

Federation Exchange: Assume that there is a trusted 3rd party for facilitating federation

3rd Party

Features, Capacity reservation, multicast

sources/groups

16


Inter-Provider Content Distribution Network (Near Term Issue Focus)• Goal is to achieve implementable specifications

quickly.• Initial milestones:

• CSF Issue #011 Cloud Service Framework for CDN (AT&T, ZTE)

• March 31 – Description of Cached & Multicast Models• CSF Issue #013 Cloud Services Network-Network

Interconnect (AT&T, Cisco, Fujitsu)• April 30 – Service Level Functional Requirements for

Peer-Peer NNI

17


18

CSF Issues

• Cloud Service Framework for CDN (AT&T, ZTE)• Cloud-Based Inter-Provider Telepresence: Access Agnostic End to

End Service Flow (Service Architecture Document): In considering Telepresence and VPNs Service Definitions (Cisco, ZTE)

• Cloud Services Network-Network Interconnect (AT&T, Cisco, Fujitsu)• Charging for Cloud Services (AT&T)• Cloud Service Logging and Auditing (ZTE)• Cloud Services Control Plane (Cisco, Huawei, ZTE) • Guidelines for COTS/Third-Party Software Installation in a Cloud

Environment (Qwest, Harris)


19

Cloud Activities in other SDOs

• Cloud Security Alliance• IETF CDNI Birds of a Feather• ITU-T SG 13• NIST• TM Forum• Others…


20

Synergies with other ATIS Committees

• IIF– Security and Identity Management in the Cloud– Reusability of SEs– Content Distribution Concept

• PRQC– Quality of Service in the Cloud

• PTSC– Cloud Interconnection in the NGN– Identity Management


21

Q&A

• How can Cloud Services Forum work with you?


22

Contact Information

• http://www.atis.org/Cloud/index.asp (Future meeting schedule is posted)– Yvonne Reigle, ATIS Director ([email protected]) – Nicole Butler, ATIS Committee Administrator (

[email protected])

http://www.atis.org/Cloud/index.asp

http://www.atis.org/Cloud/index.asp

mailto:[email protected]

mailto:[email protected]

Cloud Services Forum March 30, 2011 Welcome to the ATIS CSF Tutorial March 30, 2011; 11 AM ET...

Documents

Transcript of Cloud Services Forum March 30, 2011 Welcome to the ATIS CSF Tutorial March 30, 2011; 11 AM ET...