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.3014 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (02/2016) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Future networks ir Resource control and management functio
2、n for virtual networks for carriers (vRCMF) Recommendation ITU-T Y.3014 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 Netwo
3、rk 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.1099 Services and applications Y.1100Y.1199 Architecture, a
4、ccess, 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.1700Y.1799 Charging Y.1800Y.1899 IPTV over NGN Y.1900Y.1999 NE
5、XT 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 services and networks in NGN Y.2250Y.2299 Enhancements to
6、 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 FUTURE NETWORKS Y.3000Y.3499 CLOUD COMPUTING Y.3500Y.3999
7、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 protocols Y.4400Y.4549 Services, applications, computation
8、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.3014 (02/2016) i Recommendation ITU-T Y.3014 Resource control and management function for vi
9、rtual networks for carriers (vRCMF) Summary Recommendation ITU-T Y.3014 specifies high-level and functional requirements, architectural framework, and procedures necessary to enhance the performance objective of transport-aware carrier virtual network services, such as joint resource optimization, r
10、esponsiveness to quickly changing demands, enhanced service resilience via cooperative recovery techniques between service and transport strata, and quality of experience (QoE) enhancement via better use of existing transport and application resources. History Edition Recommendation Approval Study G
11、roup Unique ID* 1.0 ITU-T Y.3014 2016-02-13 13 11.1002/1000/12711 Keywords VNC, vRCMF. * To access the Recommendation, type the URL http:/handle.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 R
12、ec. ITU-T Y.3014 (02/2016) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. IT
13、U-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 (WTSA), which meets every four years, establishes the topics for st
14、udy 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 within ITU-Ts purview, the necessary standards are prepared on a
15、 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 Recommendation is voluntary. However, the Recommendation may contain
16、 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 such as “must“ and the negative equivalents are used to express re
17、quirements. 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 Recommendation may involve the use of a claimed Intellectual Property Ri
18、ght. 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 approval of this Recommendation, ITU had received notice of intellectu
19、al 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 patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2016 All rights r
20、eserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T Y.3014 (02/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
21、 4 Abbreviations and acronyms 2 5 Conventions 3 6 High-level requirements for vRCMF 3 7 Functional requirements for vRCMF 3 8 Architectural framework for vRCMF . 4 8.1 Functional entities 5 9 Reference Points . 7 9.1 Reference point Vu . 7 9.2 Reference point Vsm 9 9.3 Reference point Va . 11 9.4 Re
22、ference point Vt 12 9.5 Reference point Vtm . 14 9.6 Reference point Vc . 15 10 Procedures . 17 10.1 Procedures for resource information collection . 17 10.2 Procedures for resource reservation . 18 10.3 Procedures for resource failure recovery 20 10.4 Procedures for event notification 21 11 Securit
23、y considerations . 23 Rec. ITU-T Y.3014 (02/2016) 1 Recommendation ITU-T Y.3014 Resource control and management function for virtual networks for carriers (vRCMF) 1 Scope This Recommendation specifies high-level and functional requirements, the architectural framework, and procedures that enable res
24、ource control and management capabilities for virtual network for carriers (VNCs). The resource control and management function for VNCs (vRCMF): deals optimally with highly frequent network changes in the VNC environment; supports various customers policies (e.g., access control, logging, quality o
25、f service (QoS), etc.) elastically and dynamically by considering both service and network resources simultaneously; supports control and management of virtualized resource: optimal control and management of multi-technology and multi-vendor carriers virtualized resource. This Recommendation address
26、es resource control and management issues in VNCs that represent a network aspect of carrier infrastructure (e.g., virtual networks in data centres and virtualized transport networks). 2 References The following ITU-T Recommendations and other references contain provisions which, through reference i
27、n this text, constitute provisions of this 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
28、 edition of the Recommendations and other 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 Q.3316 Recommendati
29、on ITU-T Q.3316 (2016), Interface and Signalling Requirements and Specification for Cross Stratum Optimization. ITU-T T.50 Recommendation ITUT T.50 (1992), International Reference Alphabet (IRA) (Formerly International Alphabet No. 5 or IA5) Information technology 7-bit coded character set for infor
30、mation interchange. ITU-T Y.2701 Recommendation ITU-T Y.2701 (2007), Security requirements for NGN release 1. 3 Definitions 3.1 Terms defined elsewhere None. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 carrier: Infrastructure provider that owns the
31、 physical network resources and provides network as a service over them to their customers. A virtual network provider is a customer to the carrier. 2 Rec. ITU-T Y.3014 (02/2016) 3.2.2 customer: Entity requesting virtual network services. They are provided with an abstract resource view of the netwo
32、rk resource to support their users and applications. Customers can be internal or external trusted parties with respect to the provider. 3.2.3 virtual network provider: Entity that provides virtual network services to its customers. It typically leases resources from single or multiple carriers faci
33、lities to create virtual network services and offer end-to-end services to their customers. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: CRPFE Customer Request Processing Functional Element DNS Domain Name System DoS Denial of Service DWDM Dense Wav
34、elength Division Multiplexing IP Internet Protocol MIB Management Information Base MPLS-TP Multiprotocol Label Switching-Transport Profile NaaS Network as a Service OAM Operation, Administration and Maintenance OTN Optical Transport Network PMFE Profile Mapping Functional Element QoE Quality of Expe
35、rience QoS Quality of Service SDN Software-Defined Networking SRCM Service Resource Control and Management SRCM-FE Service Resource Control and Management-Functional Entity SRCM GFE Service Resource Control and Management Gateway Functional Element TRCM Transport Resource Control and Management TRCM
36、-FE Transport Resource Control and Management-Functional Entity TRCM GFE Transport Resource Control and Management Gateway Functional Element TRMFE Transport Resource Management Functional Element TROFE Transport Resource Optimization Functional Element TRPFE Transport Resource Provisioning Function
37、al Element TRRFE Transport Resource Repository Functional Element VM Virtual Machine VNC Virtual Network for Carriers VPN Virtual Private Network vRCMF Resource Control and Management Function for VNCs VRMFE Virtual Resource Management Functional Element Rec. ITU-T Y.3014 (02/2016) 3 VROFE Virtual R
38、esource Optimization Functional Element VRPFE Virtual Resource Provisioning Functional Element VTRFE Virtual Topology Repository Functional Element WDM Wavelength Division Multiplexing 5 Conventions None. 6 High-level requirements for vRCMF vRCMF is required to: support resource control and manageme
39、nt to handle highly frequent network changes in a VNC environment; support various customers policies (e.g., access control, logging, quality of service (QoS) during the process of its resource control and management; reserve resources such that logically isolated resources for each virtual infrastr
40、ucture environment can be provided; control and manage a large number of resources that may be federated among multiple carriers; provide virtual service resource lifecycle management; provide optimal resource provisioning management; support performance management for both service and transport res
41、ources in order to enable optimal resource determination; support fault management for both service and transport resources in order to enable optimal resource determination; optimize resource control and management by coordinating resource status information acquired from both the service and trans
42、port stratum. 7 Functional requirements for vRCMF Secure remote control and management are required by choosing secure protocols. vRCMF is required to support the following virtual service resource lifecycle management capabilities: creating an instance of, changing, starting, stopping or rebooting,
43、 pausing, unpausing, taking a snapshot, listing snapshots, restoring from a snapshot, removing a snapshot, migration and deletion of a virtual resource; creating, reconfiguring and deleting a virtual network; allocation, backup, restore and release of storage. vRCMF is required to support the follow
44、ing logical resource isolation capabilities: allocation of processor, memory and storage resources without any impact on performance among VNCs; allocation of physical link and bandwidth resources without impact on performance among VNCs. This requirement is optional for interworking networks connec
45、ting multiple carriers. vRCMF is required to support the following service resource control and management (SRCM) capabilities: 4 Rec. ITU-T Y.3014 (02/2016) user request processing capabilities; virtual resource optimal estimation capabilities; SRCM gateway capabilities; virtual resource performanc
46、e and fault status monitoring capabilities. vRCMF is required to support the following transport resource control and management (TRCM) capabilities: TRCM gateway capabilities; service to transport profile mapping capabilities; transport signalling invocation or software-defined networking (SDN) con
47、trol-triggering capabilities; transport resource optimal estimation capabilities; transport resource performance and fault status monitoring capabilities. 8 Architectural framework for vRCMF Figure 8-1 shows a service control and management architecture for VNC. Service resource control and manageme
48、nt-functional entity (SRCM-FE) and transport resource control and managementfunctional entity (TRCM-FE) interact with each other via a reference point Vt ITU-T Q.3316 in order to address the need for transport-aware virtual network services for carriers. For the sake of simplicity, carrier service (
49、e.g., cloud-based network as a service (NaaS), control and resource strata are all lumped together as the carrier service stratum, while the transport stratum represents the underlying transport network that actually carries the application data between users and the resources that offer services among carriers, or within a single carrier, depending on the nature of the application services. Figure 8-1 Resource control and management high-level architectur
