ITU Workshop on Cloud Computing Standards Today

ITU Workshop on “Cloud Computing Standards – Today and the Future” (Geneva, Switzerland 14 November 2014) Naa. S and Iaa. S Functional Requirements Ying Cheng China Unicom chengying 10@chinaunicom. cn Geneva, Switzerland, 14 November 2014 Nan Chen China Telecom chenn@gsta. com

Contents Part I: Functional Requirements of Network as a Service Based on Recommendation ITU-T Y. 3512 (Cloud computing - Functional requirements of Network as a Service) Part II: Functional Requirements of Infrastructure as a Service Based on Recommendation ITU-T Y. 3513 (Cloud computing - Functional requirements of Infrastructure as a Service) Geneva, Switzerland, 14 November 2014 2

Contents Part I: Functional Requirements of Network as a Service Based on Recommendation ITU-T Y. 3512 (Cloud computing - Functional requirements of Network as a Service) Geneva, Switzerland, 14 November 2014 3

Summary of Y. 3512 Scope High level concept of Naa. S; Functional requirements of Naa. S application, Naa. S platform and Naa. S connectivity; Typical Naa. S use cases of Naa. S application, Naa. S platform and Naa. S connectivity. Statistics 61 contributions from 8 sector members: China Unicom, Orange Polska SA, Orange, ETRI, ZTE, Microsoft, Huawei, Alcatel-Lucent Shanghai Bell 8 meetings: 7 physical meetings and 1 e-meeting 13 use cases: 3 in general and 10 in detail 26 functional reqts: 4 for Naa. S application, 5 for Naa. S platform, and 17 for Naa. S connectivity Editors Ying Cheng (China Unicom) and Emil Kowalczyk (Orange Polska SA) Geneva, Switzerland, 14 November 2014 4

Naa. S concept Network as a Service (Naa. S) [Y. 3500]: cloud service category in which the capability provided to the cloud service customer is transport connectivity and related network capabilities Naa. S services are divided into network application service, network platform service, and network connectivity service. In particular, Naa. S connectivity service is an “infrastructure capabilities type” service (limited to networking resources). NOTE – Naa. S can provide any of the three cloud capabilities types. Geneva, Switzerland, 14 November 2014 5

Naa. S Connectivity: infrastructure capabilities type of service where Naa. S CSC can provision and use networking connectivity resources provided by Naa. S CSP. This includes for example flexible and extended virtual private network (VPN), bandwidth on demand (Bo. D), etc. In this category, CSP offers network connections between two or more endpoints, which may include additional network functionalities. Naa. S concept (2) Naa. S Application: application capabilities type of service where Naa. S CSC can use network applications provided by CSP. Examples of Naa. S applications include virtual router, virtual content delivery network (v. CDN), virtualised evolved Naa. S Platform: platform capabilities packet core (v. EPC) and type of service where Naa. S CSC can use virtual firewall (v. FW). the network platform provided by Naa. S CSP. The Naa. S platform offers one or more software execution environments and one or more programming languages to deploy, manage and run customer-created or customer-acquired network applications. High level concept of Naa. S using the layering framework defined in [ITU-T Y. 3502] Geneva, Switzerland, 14 November 2014 6

Development methodology of Naa. S related WIs Considering the standardization methodology and conventional study sequence, the abstractions of functional entities and their mutual interactions are based on the functional requirements and the corresponding use cases analysis, which form a standardization body together. Therefore, it is required to progress Naa. S functional requirements and architecture according to the following steps and priorities. Use Cases Functional Requirements Y. 3512 Functional Architecture Y. CCNaa. S-arch Additionally, it is needed to align with the high level requirements of Naa. S described in the latest edition of Y. 3501 (Cloud computing framework and high-level requirements), whose most recent edition is ITU-T Y. 3501 (2013). Geneva, Switzerland, 14 November 2014 Source: Appendix I of Y. 3512 7

Milestones of Naa. S related WIs Timelines Milestones 2012. 4 First proposal from China Unicom on Naa. S related WI – agreed to be kept in living list of Q 27/13 2012. 6 Agreed to launch Y. CCNaa. S in study period 2013 -2016 2013. 2 Initial draft Rec of Y. CCNaa. S; Use cases and derived reqts on dynamic transport network and flexible and extended VPN; Ying Cheng (China Unicom) and Emil Kowalczyk (Telekomunikacja Polska S. A) are nominated as editors; 2013. 6 Re-organization of use cases and functional requirements into three types; Use cases and derived reqts on Cloud CDN, Application/platform capabilities types Naa. S provision, Bo. D, Optimized traffic engineering, Performance on demand 2013. 11 Excluding architecture clause from the scope of Y. CCNaa. S; New time plan for Y. CCNaa. S consent on Q 3 2014; New use cases and derived functional reqts on virtual router and service chain 2014. 2 Refinement on scope; Modifications on general description including introduction and high level concept of Naa. S; 2014. 5 Addition and modification of detailed functional reqts in clauses 7 -9; Editorial supplements and modifications for the whole document 2014. 7 Consent of Y. 3512 (former Y. CCNaa. S) ; Launch of Naa. S series WI Y. CCNaa. S-arch and Ying Cheng (China Unicom) , Emil Kowalczyk (Orange Polska SA) , and Qian Gu (China Telecom) are nominated as editors 2014. 8 Publishing of Y. 3512 after AAP Geneva, Switzerland, 14 November 2014 8

Detailed use cases and functional reqts of Naa. S application Detailed use case Derived functional reqts Cloud CDN • Monitoring utilization and delivery performance • Providing efficient management solution • Providing mechanisms allowing for the chaining of Naa. S applications Geneva, Switzerland, 14 November 2014 9

Detailed use cases and functional reqts of Naa. S platform Detailed use case Derived functional reqts Service chain • Programmable Naa. S platform; • Dynamic and flexible network service composition and steering; • Isolation of service chains for tenants Platform provision • Flexible scaling of Naa. S platform • Integration of software applications Geneva, Switzerland, 14 November 2014 10

Detailed use cases and functional reqts of Naa. S connectivity (1) Detailed use case Derived functional reqts Dynamic transport • Unified SLA for multiple optimized networks network • Leveraging transport networks dynamically • Unified network control mechanism Flexible and • Elastic network reconfiguration extended VPN Bandwidth on • Seamless and end-to-end solution demand service bandwidth allocation • Symmetric or asymmetric capacity of Optimized traffic • Optimized and fine-grained traffic engineering • Coexistence with legacy network services and functions 11

Detailed use cases and functional reqts of Naa. S connectivity (2) Detailed use case Derived functional reqts Performance on demand • CSC limited control to services • Centralized control view and abstraction view of resources • Logically isolated network partition • Overlay network mechanism • Overlapped private IP addresses • Interworking among different VPN solutions • VPN connection in mobile environment • Connection to Naa. S CSP’s network through public Internet Virtual Router Private IP addresses and VPNs 12 Geneva, Switzerland, 14 November 2014

Contents Part II: Functional Requirements of Infrastructure as a Service Based on Recommendation ITU-T Y. 3513 (Cloud computing - Functional requirements of Infrastructure as a Service) Geneva, Switzerland, 14 November 2014 13

Y. CCIaa. S in Summary Scope of Y. CCIaa. S General description of Iaa. S Functional requirements of Iaa. S Typical Iaa. S use cases 41 related contributions from 7 sector members in 9 meetings Editors CHEN Nan (China Telecom) Peter Tomsu (Cisco) Geneva, Switzerland, 14 November 2014 14

Milestones of Y. 3513 Timelines Milestones 2012. 4 First proposal from China Telecom on Iaa. S related WI – agreed to be kept in living list of Q 27/13 Agreed to launch Y. CCIaa. S in study period 2013 -2016 2012. 6 2013. 2 Initial draft Rec of Y. CCIaa. S CHEN Nan (China Telecom) and Orit Levin (Microsoft) are nominated as the editors 2013. 6 Mr. Peter Tomsu from Cisco is nominated as the co-editor 2014. 2 Excluding architecture clause from the scope of Y. CCIaa. S New time plan for Y. CCIaa. S consent on Q 3 2014 Consented 2014. 7 Geneva, Switzerland, 14 November 2014 15

The definition of Iaa. S Infrastructure as a Service [ITU-T Y. 3500] cloud service category in which the cloud capabilities type provided to the cloud service customer is an infrastructure capabilities type NOTE – The cloud service customer does not manage or control the underlying physical and virtual resources, but does have control over operating systems, storage, and deployed applications that use the physical and virtual resources. The cloud service customer may also have limited ability to control certain networking components (e. g. host firewalls). Geneva, Switzerland, 14 November 2014 16

High level concept of Iaa. S Geneva, Switzerland, 14 November 2014 17

Iaa. S service functions computing service functions allow CSC to provision and use processing resources. CSC can perform operations relevant to processing resources including machine (physical or virtual machine) lifecycle operations and functions such as VM migration, backup, snapshot, clone and reservation. storage service functions allow CSC to use storage resources. CSC can perform operations relevant to storage resources including lifecycle operations and functions such as snapshot, backup, I/O performance, load balance and reservation. network service functions allow CSC to use networking resources. CSC can integrate infrastructure resources using network relevant functions such as IP address, network isolation (e. g. VLAN), virtual networking (e. g. virtual switch), load balance and firewall. Geneva, Switzerland, 14 November 2014 18

Computing service functions migration scaling snapshot clone Physical Computing machine Service Virtual backup machine time synchronization reservation image template Geneva, Switzerland, 14 November 2014 19

Storage service functions Storage migration Storage resource reservation Storage snapshot service I/O Storage performance backup Geneva, Switzerland, 14 November 2014 20

Network service functions Network policy migration Network Qo. S IP address Network Isolation Virtual networking Load balance Network Service Firewall Gateway Network configuration Geneva, Switzerland, 14 November 2014 21

The relationship between Iaa. S and Naa. S Regarding the network connectivity, one important difference between Iaa. S and Naa. S is that Iaa. S is a cloud service category that is offered in only one flavour of cloud capability type, and that is infrastructure capabilities type [ITU-T Y. 3500]. However, Naa. S is a cloud service category that can be offered in all three cloud capabilities types. Geneva, Switzerland, 14 November 2014 22

Thanks for your attention！ Geneva, Switzerland, 14 November 2014 23