ITU-T Y 3012-2014 Requirements of network virtualization for future networks (Study Group 13)《未来网络的网络虚拟化的要求》.pdf

1、 I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T Y.3012 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (04/2014) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Future networks Requirements of network virtualization for

2、 future networks Recommendation ITU-T Y.3012 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS GLOBAL INFORMATION INFRASTRUCTURE General Y.100Y.199 Services, applications and middleware Y.200Y.299 Network aspects Y.300Y.399 Inter

3、faces and protocols Y.400Y.499 Numbering, addressing and naming Y.500Y.599 Operation, administration and maintenance Y.600Y.699 Security Y.700Y.799 Performances Y.800Y.899 INTERNET PROTOCOL ASPECTS General Y.1000Y.1099 Services and applications Y.1100Y.1199 Architecture, access, network capabilities

4、 and resource management Y.1200Y.1299 Transport Y.1300Y.1399 Interworking Y.1400Y.1499 Quality of service and network performance Y.1500Y.1599 Signalling Y.1600Y.1699 Operation, administration and maintenance Y.1700Y.1799 Charging Y.1800Y.1899 IPTV over NGN Y.1900Y.1999 NEXT GENERATION NETWORKS Fram

5、eworks and functional architecture models Y.2000Y.2099 Quality of Service and performance Y.2100Y.2199 Service aspects: Service capabilities and service architecture Y.2200Y.2249 Service aspects: Interoperability of services and networks in NGN Y.2250Y.2299 Enhancements to NGN Y.2300Y.2399 Network m

6、anagement Y.2400Y.2499 Network control architectures and protocols Y.2500Y.2599 Packet-based Networks Y.2600Y.2699 Security Y.2700Y.2799 Generalized mobility Y.2800Y.2899 Carrier grade open environment Y.2900Y.2999 FUTURE NETWORKS Y.3000Y.3499 CLOUD COMPUTING Y.3500Y.3999 For further details, please

7、 refer to the list of ITU-T Recommendations. Rec. ITU-T Y.3012 (04/2014) i Recommendation ITU-T Y.3012 Requirements of network virtualization for future networks Summary Recommendation ITU-T Y.3012 specifies the requirements of network virtualization in future networks, in particular requirements on

8、 physical resource management, virtual resource management, logically isolated network partition (LINP) management, service management, authentication, authorization and accounting of LINP, LINP federation and service mobility. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T

9、 Y.3012 2014-04-13 13 11.1002/1000/12166 Keywords Future networks, logically isolated network partition, network virtualization, resource management. _ * To access the Recommendation, type the URL http:/handle.itu.int/ in the address field of your web browser, followed by the Recommendations unique

10、ID. For example, http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T Y.3012 (04/2014) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunicati

11、on Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (W

12、TSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall

13、 within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Rec

14、ommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language s

15、uch as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTSITU draws attention to the possibility that the practice or implementation of this Recomme

16、ndation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of appro

17、val of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB p

18、atent database at http:/www.itu.int/ITU-T/ipr/. ITU 2014 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T Y.3012 (04/2014) iii Table of Contents Page 1 Scope . 1 2 References . 1 3 Definitions 1 3.1 T

19、erms defined elsewhere 1 3.2 Terms defined in this Recommendation . 1 4 Abbreviations and acronyms 2 5 Conventions 2 6 Overview of network virtualization 2 7 Requirements 2 7.1 Physical resource management . 2 7.2 Virtual resource management . 3 7.3 LINP management 3 7.4 Service management . 4 7.5 A

20、uthentication, authorization and accounting 4 7.6 LINP federation 4 7.7 Service mobility 5 8 Environmental considerations 5 9 Security considerations . 6 Appendix I Resource hierarchical model 7 Bibliography. 8 Rec. ITU-T Y.3012 (04/2014) 1 Recommendation ITU-T Y.3012 Requirements of network virtual

21、ization for future networks 1 Scope The scope of this Recommendation is to provide requirements of network virtualization for future networks. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this

22、 Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other

23、references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T Y.3001 Recommendation ITU-T Y.3001 (2011), Future networks: O

24、bjectives and design goals. ITU-T Y.3011 Recommendation ITU-T Y.3011 (2012), Framework of network virtualization for future networks. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 future network (FN) ITU-T Y.3001: A network able to pr

25、ovide services, capabilities, and facilities difficult to provide using existing network technologies. A future network is either: a) A new component network or an enhanced version of an existing one, or b) A heterogeneous collection of new component networks or of new and existing component network

26、s that is operated as a single network. 3.1.2 logically isolated network partition (LINP) ITU-T Y.3011: A network that is composed of multiple virtual resources which is isolated from other LINPs. 3.1.3 network virtualization ITU-T Y.3011: A technology that enables the creation of logically isolated

27、 network partitions over shared physical networks so that heterogeneous collections of multiple virtual networks can simultaneously coexist over the shared networks. This includes the aggregation of multiple resources in a provider and appearing as a single resource. 3.1.4 virtual resource ITU-T Y.3

28、011: An abstraction of physical or logical resource, which may have different characteristics from the physical or logical resource and whose capability may be not bound to the capability of the physical or logical resource. 3.2 Terms defined in this Recommendation This Recommendation defines the fo

29、llowing term: 3.2.1 LINP operator: A network operator that creates, programs, configures, manages and terminates network services on a given LINP. 2 Rec. ITU-T Y.3012 (04/2014) 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: AAA Authentication, Authori

30、zation and Accounting API Application Programming Interface CPU Central Processing Unit LINP Logically Isolated Network Partition VLAN Virtual Local Area Network 5 Conventions The keywords “is required to“ indicate a requirement which must be strictly followed and from which no deviation is permitte

31、d, if conformance to this Recommendation is to be claimed. The keywords “is recommended to“ indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. 6 Overview of network virtualization Network virtualization i

32、s a method that allows multiple virtual networks, called logically isolated network partitions (LINPs), to coexist in a single physical network ITU-T Y.3011. In order to provide LINPs, physical resources are partitioned and abstracted as virtual resources and the virtual resources are interconnected

33、 to create an LINP. These virtual resources can be created on physical resources such as routers, switches and hosts. As such, virtual resources are either allocated to each LINP or multiple virtual resources are aggregated into a single virtual resource. Physical resources are composed of transport

34、 resources, computing resources and storage resources. A transport resource includes a physical node, link, router and switch, all of which are components of a transport network. A computing resource includes a central processing unit (CPU) and memory, which are components of a computing system. A s

35、torage resource includes a device holding a high volume of data. 7 Requirements To operate LINPs and provide network services, both physical and virtual resources need to be controlled and managed effectively and efficiently. Since resources are managed by using different management functions in the

36、 entire cycle of service deployment, requirements for these functions are given in this clause. Realizing authentication, authorization, and accounting (AAA) of LINP, LINP federation and service mobility are also important issues from the viewpoint of flexible service deployment b-Nakao.The requirem

37、ents for these issues are also provided. 7.1 Physical resource management Physical resource management enables effective and consistent use of physical resources which may include heterogeneous types of equipment such as routers and servers developed by different vendors. The requirements for the ph

38、ysical resource management are as follows: The physical resource management is required to provide capabilities for managing, controlling, and monitoring heterogeneous types of physical resources for virtual resource management. The physical resource management is required to provide diagnosis mecha

39、nisms for troubleshooting to help identify the causes of physical resources failures. Rec. ITU-T Y.3012 (04/2014) 3 The physical resource management is recommended to provide information obtained through the diagnosis mechanisms (e.g., expected recovery time) to virtual resource management. The phys

40、ical resource management is recommended to provide recovery mechanisms from physical network failures to improve reliability. The physical resource management is recommended to detect new physical resources automatically as they are added to the network. 7.2 Virtual resource management Virtual resou

41、rce management enables LINPs to bind physical resources and virtual resources. The requirements for the virtual resource management are as follows: The virtual resource management is required to provide LINP identification means, such as LINP identifier (LINP ID), to differentiate LINPs. The virtual

42、 resource management is recommended to provide capability to collaborate with the physical resource management so that virtual resources can be allocated to an LINP effectively and efficiently. The virtual resource management is recommended to abstract an aggregated set of physical and virtual resou

43、rces into a virtual resource in order to enable simplified control of virtual resources by LINP management. The virtual resource management is recommended to provide capabilities for monitoring or control of virtual resources to LINP management. The virtual resource management is recommended to chan

44、ge mapping between physical resources and virtual resources dynamically in the case of events like failures or performance degradations The virtual resource management is recommended to change mapping between physical resources and virtual resources according to requests for reconfiguration of LINPs

45、 from one or more LINP operators. The virtual resource management is recommended to allow LINP operators to configure LINPs quickly without imposing complexities of physical network operation including management of network addresses and domain names. The virtual resource management is recommended t

46、o allow LINP operators to reconfigure virtual resources to optimize performance and/or efficiency of LINPs through a simplified control interface. In this reconfiguration process, service interruption should be minimized to maintain quality of services on the LINPs. The virtual resource management i

47、s recommended to gather physical and virtual resource information, such as bandwidth consumption and CPU utilization. 7.3 LINP management LINP management enables LINP operators to apply management policies to an LINP. The requirements for the LINP management are as follows: The LINP management is re

48、commended to reconfigure an LINP by reallocating virtual resources to the LINP so that the LINP operator can adapt the LINP profile to changes in service properties. The LINP management is recommended to terminate an LINP and release all the virtual resources that are no longer needed. The LINP mana

49、gement is recommended to monitor the status of a running LINP, such as traffic volume, energy consumption and utilization of virtual resources. 4 Rec. ITU-T Y.3012 (04/2014) The LINP management is recommended to optimize an LINP so that the LINP can be controlled and managed efficiently to adapt to environmental changes such as traffic fluctuations and equipment failures. In this optimization process, service interruption should be minimized to maintain quality of servic