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.3515 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (07/2017) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES Cloud Computing Cloud co
2、mputing Functional architecture of Network as a Service Recommendation ITU-T Y.3515 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES GLOBAL INFORMATION INFRASTRUCTURE General Y.100Y.199 Services
3、, 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.1099 Services
4、 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.1700Y.1799 Charg
5、ing 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 services an
6、d 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 FUTURE NETWO
7、RKS 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 protocols Y.4
8、400Y.4549 Services, applications, computation and data processing Y.4550Y.4699 Management, control and performance Y.4700Y.4799 Identification and security Y.4800Y.4899 Evaluation and assessment Y.4900Y.4999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Y.3515 (0
9、7/2017) i Recommendation ITU-T Y.3515 Cloud computing Functional architecture of Network as a Service Summary Recommendation ITU-T Y.3515 provides Network as a Service (NaaS) functional architecture by specifying functionalities and functional components as well as reference points for the operation
10、 support system (OSS). This Recommendation also describes the mapping between functionalities and functional requirements of NaaS, relationship between the NaaS functional architecture and software-defined networking (SDN), and illustrated usage of SDN and network functions virtualization (NFV) in s
11、upport of the NaaS functional architecture. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T Y.3515 2017-07-07 13 11.1002/1000/13255 Keywords NaaS, NaaS functionality, NaaS functional architecture, NaaS functional component, NaaS product, network as a service. * To access the
12、 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 Rec. ITU-T Y.3515 (07/2017) FOREWORD The International Telecommunication Union (ITU) is the United Nati
13、ons 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. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations
14、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 study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of
15、 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 collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is
16、 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 certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with
17、 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 requirements. The use of such words does not suggest that compliance with the Recommendation is required
18、 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 Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual
19、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 not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However
20、, 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 2017 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior
21、 written permission of ITU. Rec. ITU-T Y.3515 (07/2017) iii Table of Contents Page 1 Scope . 1 2 References . 1 3 Definitions 2 3.1 Terms defined elsewhere 2 3.2 Terms defined in this Recommendation . 3 4 Abbreviations and acronyms 3 5 Conventions 4 6 Overview of NaaS functional architecture . 4 6.1
22、 Key NaaS characteristics 4 6.2 NaaS CSC activities . 5 6.3 Virtualization of network functions 7 7 Functionalities for NaaS . 8 7.1 NaaS business related functionalities . 8 7.2 Functionalities for NaaS service instantiation 8 7.3 Functionalities for NaaS service orchestration . 9 7.4 Functionaliti
23、es for network analytics . 9 7.5 Autonomic functionalities 10 7.6 Policy related functionalities 10 7.7 NaaS resource functionalities . 11 7.8 Functionalities for an evolved real-time OSS 11 7.9 Functionalities for the development of NaaS products and NaaS services 15 8 Functional components . 15 8.
24、1 Business support system functional components for NaaS products . 16 8.2 Service layer functional components for NaaS 17 8.3 OSS functional components . 18 8.4 Functional components for NaaS development support . 28 9 Security considerations . 29 Annex A OSS reference points . 30 Annex B Functiona
25、l components on mapping between physical and virtualized networks 34 B.1 Physical network 34 B.2 Virtualized network 35 B.3 Physical-virtualized-networks mapping . 35 Appendix I Mapping among NaaS functional requirements and functionalities 36 I.1 Mapping and derivation of functionality for NaaS ser
26、vice instantiation . 36 I.2 Mapping and derivation of functionality for service orchestration 36 I.3 Mapping and derivation of functionalities for network analytics, policy, and autonomy . 37 iv Rec. ITU-T Y.3515 (07/2017) Page I.4 Mapping and derivation of functionality for mapping between physical
27、 and virtualized networks . 37 I.5 Mapping and derivation of functionalities for an evolved real-time OSS 38 I.6 Mapping and derivation of functionalities for NaaS products and NaaS services development 38 I.7 Mapping and derivation of functionalities related to NaaS business . 38 Appendix II Modell
28、ing usage example of NaaS service, NaaS service operational policy, and NaaS resource model . 39 II.1 Introduction 39 II.2 Modelling usage . 39 Appendix III Relationship between NaaS functional architecture and SDN 41 Appendix IV Example of NFV and SDN usage in support of NaaS architecture 43 Biblio
29、graphy. 45 Rec. ITU-T Y.3515 (07/2017) 1 Recommendation ITU-T Y.3515 Cloud computing Functional architecture of Network as a Service 1 Scope This Recommendation provides the Network as a Service (NaaS) functional architecture by specifying functionalities and functional components as well as referen
30、ce points for the operation support system (OSS). The scope of this Recommendation consists of: Overview of the NaaS functional architecture; NaaS functionalities; NaaS functional components; OSS reference points in the NaaS functional architecture. This Recommendation also provides appendixes descr
31、ibing: The mapping between NaaS functionalities described in this Recommendation and NaaS functional requirements specified in ITU-T Y.3512; The relationship between the NaaS functional architecture and software-defined networking (SDN); An illustrated usage of SDN and network functions virtualizati
32、on (NFV) in support of the NaaS functional architecture. 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, the editions indicated were valid. All Re
33、commendations 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 currently valid ITU-T Recommendations is regula
34、rly 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 X.1601 Recommendation ITU-T X.1601 (2015), Security framework for cloud computing. ITU-T Y.2320 Recommendation ITU-T Y.2320 (2015), Requirements fo
35、r virtualization of control network entities in next generation network evolution. ITU-T Y.3300 Recommendation ITU-T Y.3300 (2014), Framework of software-defined networking. ITU-T Y.3302 Recommendation ITU-T Y.3302 (2017), Functional architecture of software-defined networking (SDN). ITU-T Y.3500 Re
36、commendation ITU-T Y.3500 (2014) | ISO/IEC 17788:2014, Information technology Cloud computing Overview and vocabulary. ITU-T Y.3501 Recommendation ITU-T Y.3501 (2016) | ISO/IEC 17789:2014, Cloud computing Framework and high-level requirements. ITU-T Y.3502 Recommendation ITU-T Y.3502 (2014), Informa
37、tion technology Cloud computing Reference architecture. 2 Rec. ITU-T Y.3515 (07/2017) ITU-T Y.3512 Recommendation ITU-T Y.3512 (2014), Cloud computing Functional requirements of Network as a Service. ITU-T Y.3521 Recommendation ITU-T Y.3521/M.3070 (2016), Overview of end-to-end cloud computing manag
38、ement. ITU-T Y.3522 Recommendation ITU-T Y.3522 (2016), End-to-end cloud service lifecycle management requirements. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 activity ITU-T Y.3502: A specified pursuit or set of tasks. 3.1.2 cloud
39、computing ITU-T Y.3500: Paradigm for enabling network access to a scalable and elastic pool of shareable physical or virtual resources with self-service provisioning and administration on-demand. NOTE Examples of resources include servers, operating systems, networks, software, applications, and sto
40、rage equipment. 3.1.3 cloud service ITU-T Y.3500: One or more capabilities offered via cloud computing invoked using a defined interface. 3.1.4 cloud service customer ITU-T Y.3500: Party which is in a business relationship for the purpose of using cloud services. NOTE A business relationship does no
41、t necessarily imply financial agreements. 3.1.5 cloud service product ITU-T Y.3502: A cloud service, allied to the set of business terms under which the cloud service is offered. NOTE Business terms can include pricing, rating and service levels. 3.1.6 cloud service provider ITU-T Y.3500: Party whic
42、h makes cloud services available. 3.1.7 Network as a Service (NaaS) ITU-T Y.3500: Cloud service category in which the capability provided to the cloud service customer is transport connectivity and related network capabilities. 3.1.8 product catalogue ITU-T Y.3502: A listing of all the cloud service
43、 products which cloud service providers make available to cloud service customers. 3.1.9 role ITU-T Y.3502: A set of activities that serves a common purpose. 3.1.10 service catalogue ITU-T Y.3502: A listing of all the cloud services of a particular cloud service provider. 3.1.11 service chain ITU-T
44、Y.3512: An ordered set of functions that is used to enforce differentiated traffic handling policies for a traffic flow. 3.1.12 service level agreement ITU-T Y.3500: Documented agreement between the service provider and customer that identifies services and service targets. NOTE 1 A service level ag
45、reement can also be established between the service provider and a supplier, an internal group or a customer acting as a supplier. NOTE 2 A service level agreement can be included in a contract or another type of documented agreement. 3.1.13 software-defined networking ITU-T Y.3300: A set of techniq
46、ues that enables to directly program, orchestrate, control and manage network resources, which facilitates the design, delivery and operation of network services in a dynamic and scalable manner. Rec. ITU-T Y.3515 (07/2017) 3 3.1.14 sub-role ITU-T Y.3502: A subset of the activities of a given role.
47、3.1.15 tenant ITU-T Y.3500: One or more cloud service users sharing access to a set of physical and virtual resources. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 NaaS product: A cloud service product for which the cloud service related to that pro
48、duct is of the NaaS cloud service category. 3.2.2 network function: A function of a network infrastructure whose external interfaces and functional behaviour are well specified. NOTE Examples of network functions include network switches and network routers. 3.2.3 network service: A collection of ne
49、twork functions with a well specified behaviour. NOTE Examples of network services include content delivery networks (CDNs) and IP multimedia subsystem (IMS). 3.2.4 physical network function: A network function implemented via a tightly coupled software and hardware system. NOTE Examples of physical network functions include physical network switches and physical routers. 3.2.5 virtualized network function: A networ
