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.3015 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (04/2016) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES Future networks Funct
2、ional architecture of network virtualization for future networks Recommendation ITU-T Y.3015 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES GLOBAL INFORMATION INFRASTRUCTURE General Y.100Y.
3、199 Services, applications and middleware Y.200Y.299 Network aspects Y.300Y.399 Interfaces 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.1
4、099 Services and applications Y.1100Y.1199 Architecture, access, network capabilities 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.1700
5、Y.1799 Charging Y.1800Y.1899 IPTV over NGN Y.1900Y.1999 NEXT GENERATION NETWORKS Frameworks 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
6、 services and networks in NGN Y.2250Y.2299 Enhancements to NGN Y.2300Y.2399 Network management 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
7、FUTURE NETWORKS Y.3000Y.3499 CLOUD COMPUTING Y.3500Y.3999 INTERNET OF THINGS AND SMART CITIES AND COMMUNITIES General Y.4000Y.4049 Definitions and terminologies Y.4050Y.4099 Requirements and use cases Y.4100Y.4249 Infrastructure, connectivity and networks Y.4250Y.4399 Frameworks, architectures and p
8、rotocols Y.4400Y.4549 Services, applications, computation and data processing Y.4550Y.4699 Management, control and performance Y.4700Y.4799 Identification and security Y.4800Y.4899 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Y.3015 (04/2016) i Recommendation IT
9、U-T Y.3015 Functional architecture of network virtualization for future networks Summary Recommendation ITU-T Y.3015 describes the functional architecture of network virtualization for future networks, covering the specification of user roles, resources and LINPs, functions and their mutual relation
10、s, and reference points. An implementation example is also provided. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T Y.3015 2016-04-06 13 11.1002/1000/12712 Keywords Functional architecture, LINP, network virtualization. * To access the Recommendation, type the URL http:/han
11、dle.itu.int/ in the address field of your web browser, followed by the Recommendations unique ID. For example, http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T Y.3015 (04/2016) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of
12、telecommunications, information and communication technologies (ICTs). The ITU Telecommunication 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 te
13、lecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), 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 th
14、e procedure laid down in WTSA Resolution 1. In some areas of information technology which fall 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
15、a telecommunication administration and a recognized operating agency. Compliance with this Recommendation 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 al
16、l of these mandatory provisions are met. The words “shall“ or some other obligatory language such 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 RI
17、GHTSITU draws attention to the possibility that the practice or implementation of this Recommendation 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 IT
18、U members or others outside of the Recommendation development process. As of the date of approval 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
19、may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2016 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
20、Y.3015 (04/2016) iii Table of Contents Page 1 Scope . 1 2 References . 1 3 Definitions 1 3.1 Terms defined elsewhere 1 3.2 Terms defined in this Recommendation . 1 4 Abbreviations and acronyms 1 5 Conventions 2 6 Overview of functional architecture . 2 6.1 User roles 4 6.2 LINP federation without LI
21、NP exchangers 6 7 Resources and LINPs 7 7.2 Virtual resources . 7 7.3 LINPs 7 7.4 Allocation and binding . 7 8 Physical node architecture 8 9 Physical resource management functions . 9 9.1 Physical resource configuration functions 10 9.2 Physical resource monitoring and fault management function 10
22、9.3 Physical resource discovery function . 10 10 Virtual resource management functions . 10 10.1 Virtual resource configuration functions 10 10.2 Virtual resource monitoring and fault management function . 11 10.3 Virtual resource discovery function . 11 11 LINP management functions 11 11.1 Resource
23、 coordination function 11 11.2 LINP configuration functions . 11 11.3 LINP monitoring and fault detection function . 12 11.4 Authorization functions 12 12 LINP operator functions . 12 13 Service deployment functions . 12 14 Service developer functions 13 15 Gateway functions 14 16 User terminal func
24、tions . 15 17 Federation functions . 16 18 Reference points . 16 18.1 User-to-network interface (UNI) 17 18.2 Network-to-network interface (NNI) . 17 iv Rec. ITU-T Y.3015 (04/2016) Page 18.3 Virtual resource management interface (VMI) 17 18.4 LINP management interface (LMI) 17 18.5 Service managemen
25、t interface (SMI) . 17 18.6 Programmer-to-redirector interface (PRI) 17 19 Security considerations . 17 Appendix I Implementation example of network virtualization . 18 Bibliography. 21 Rec. ITU-T Y.3015 (04/2016) 1 Recommendation ITU-T Y.3015 Functional architecture of network virtualization for fu
26、ture networks 1 Scope This Recommendation describes the functional architecture of network virtualization, which enables management and control of logically isolated network partitions (LINPs) over shared physical networks and supports programmability of services on LINPs. It covers the specificatio
27、n of user roles, resources and LINPs, functions and their mutual relations, and reference points. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication,
28、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 references listed below. A list of the curren
29、tly 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: Objectives and design goals. ITU-T Y.3011 Reco
30、mmendation ITU-T Y.3011 (2012), Framework of network virtualization for future networks. ITU-T Y.3012 Recommendation ITU-T Y.3012 (2014), Requirements of network virtualization for future networks. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhe
31、re: 3.1.1 LINP operator ITU-T Y.3012: A network operator that creates, programs, configures, manages, and terminates network services on a given LINP. 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
32、 LINPs. 3.1.3 network virtualization ITU-T Y.3011: A technology that enables the creation of logically isolated network partitions over shared physical networks so that heterogeneous collection of multiple virtual networks can simultaneously coexist over the shared networks. This includes the aggreg
33、ation of multiple resources in a provider and appearing as a single resource. 3.2 Terms defined in this Recommendation None. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: API Application Programming Interface ASIC Application-Specific Integrated Circ
34、uit 2 Rec. ITU-T Y.3015 (04/2016) FPGA Field-Programmable Gate Array GRE Generic Routing Encapsulation ID Identifier IP Internet Protocol LINP Logically Isolated Network Partition LMI LINP Management Interface NFV Network Functions Virtualization NNI Network-to-Network Interface OS Operating System
35、PRI Programmer-to-Redirector Interface QoS Quality of Service SDN Software-Defined Networking SMI Service Management Interface UNI User-to-Network Interface VLAN Virtual Local Area Network VM Virtual Machine VMI Virtual resource Management Interface VNF Virtualized Network Function XML-RPC Extensibl
36、e Markup Language-Remote Procedure Call 5 Conventions None. 6 Overview of functional architecture This clause provides an overview of the functional architecture of network virtualization. Figure 1 shows the components of the architecture classified into the following four categories: user roles, re
37、sources, functions, and reference points. Rec. ITU-T Y.3015 (04/2016) 3 Figure 1 User roles, resources, functions, and reference points in the functional architecture of network virtualization A resource is either a physical or a virtual component of a virtual network that executes specific function
38、ality and is represented with specific attributes. Three types of resources are introduced in the functional architectures: physical resource, virtual resource, and LINP. All the three types of resources are managed with corresponding management functions, which are usually implemented in management
39、 systems. NOTE 1 In Figure 1, end-user data transmission is represented with the blue lines and management and control with the orange lines, as shown in the legend of symbols. Note that the blue lines are applied only to physical resources and functions that manage them. This way of representation
40、makes it clear for which purpose each reference point is specified. For example, the user-to-network interface (UNI) reference point is specified for end-user data transmission, whereas the virtual resource management interface (VMI) is specified for management and control. The same representation i
41、s applied throughout this document. See clause 18 for more information about the reference points. User roles are classified into one of the following four types: end-user, network operator, LINP operator, and service developer. When LINP federation is performed, another type of role, LINP exchanger
42、, may be involved. These user roles are distinguished logically. Different types of user roles could be played by the same party. Each user role executes certain functions for the purpose of fulfilling its own responsibilities. When functions of one user role need to access those of another, the acc
43、esses are done via reference points. NOTE 2 b-ITU-T Y.3502 describes the reference architecture of cloud computing using two different views, i.e. the user view and the functional view. In b-ITU-T Y.3502, parties and roles appear in the user view and functions in the functional view. The functional
44、architecture presented in the present Recommendation can be understood as a combination of the two views in the context of b-ITU-T Y.3502. 4 Rec. ITU-T Y.3015 (04/2016) As such, party as used in the present Recommendation is similar to party as used in b-ITU-T Y.3502 and user roles in the present Re
45、commendation can be regarded as a shortcut to roles in the user view in the context of b-ITU-T Y.3502. NOTE 3 In this Recommendation, LINP operators are treated independently from network operators, while ITU-T Y.3012 describes LINP operators as being network operators. This approach allows for desc
46、ribing individual functions in reference to user roles. In line with ITU-T Y.3012, the party acting as a network operator can also act as an LINP operator and as a service developer. 6.1 User roles 6.1.1 Network operator Network operators are responsible for managing physical resources and their abs
47、tracted sets, or virtual resources. For this purpose, they implement physical resource management functions and virtual resource management functions, respectively, in their individual administrative domains. A LINP is built from virtual resources in an administrative domain of a network operator. A
48、ccordingly, implementing LINP management functions in an administrative domain is a responsibility of the corresponding network operator. LINP management functions use virtual resource management functions of the same administrative domain to allocate appropriate virtual resources to a specific LINP
49、. Likewise, virtual resource management functions use physical resource management functions of the same administrative domain to allocate appropriate physical resources to a specific virtual resource. Gateway functions are also implemented by network operators. Gateway functions are used to control accesses from end-users to specific LINPs. 6.1.2 LINP operator LINP operators activate or deactivate services on LINPs provided by network operators. ALINP operator can also have access to LINP
