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.3110 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (09/2017) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES Future networks IMT-2020
2、 network management and orchestration requirements Recommendation ITU-T Y.3110 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, app
3、lications 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 and
4、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 Charging Y
5、.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 and net
6、works 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 NETWORKS Y
7、.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.4400Y.
8、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.3110 (09/201
9、7) i Recommendation ITU-T Y.3110 IMT-2020 network management and orchestration requirements Summary Recommendation ITU-T Y.3110 describes requirements for network management and orchestration of IMT-2020. It describes high-level and functional requirements. The functional requirements consist of two
10、 levels: a) lifecycle management for all slices and b) instance management pertinent to each slice. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T Y.3110 2017-09-13 13 11.1002/1000/13350 Keywords IMT-2020 network management and orchestration high-level and functional requir
11、ements, IMT-2020 network slice lifecycle management and orchestration requirements, IMT-2020 network slice instance management requirements. * 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 exa
12、mple, http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T Y.3110 (09/2017) 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 Standard
13、ization 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 (WTSA), which
14、 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 within ITU
15、-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 Recommendation
16、 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 such as “mus
17、t“ 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 Recommendation may
18、 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 approval of this
19、 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 patent datab
20、ase 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 written permission of ITU. Rec. ITU-T Y.3110 (09/2017) iii Table of Contents Page 1 Scope . 1 2 References . 1 3 Definitions 1 3.1 Terms define
21、d elsewhere 1 3.2 Terms defined in this Recommendation . 2 4 Abbreviations and acronyms 2 5 Conventions 2 6 Introduction . 2 7 High-level requirements for network management and orchestration of IMT-2020 . 2 8 Functional requirements for network management and orchestration of IMT-2020 . 3 8.1 Funct
22、ional requirements of network slice life cycle management and orchestration . 3 8.2 Functional requirements of network slice instance management . 4 9 Security consideration 5 Bibliography. 6 Rec. ITU-T Y.3110 (09/2017) 1 Recommendation ITU-T Y.3110 IMT-2020 network management and orchestration requ
23、irements 1 Scope This Recommendation specifies high-level and functional management and orchestration requirements for IMT-2020 in consideration of integrated management with existing networks. For the integrated management, only the requirements for a standard interface to the existing network mana
24、gement system are in scope. 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 Recommendations and other refer
25、ences 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 regularly published. The reference
26、to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T M.3010 Recommendation ITU-T M.3010 (2000), Principles for a telecommunications management network. ITU-T Y.3001 Recommendation ITU-T Y.3001 (2011), Future networks: Objectives
27、and design goals. ITU-T Y.3100 Recommendation ITU-T Y.3100 (2017), Terms and definitions for IMT-2020. ITU-R M.2083-0 Recommendation ITU-R M.2083-0 (2015), IMT Vision Framework and overall objectives of the future development of IMT for 2020 and beyond. 3 Definitions 3.1 Terms defined elsewhere This
28、 Recommendation uses the following terms defined elsewhere: 3.1.1 management ITU-T Y.3100: In the context of IMT-2020, the processes aiming at fulfilment, assurance, and billing of services, network functions, and resources in both physical and virtual infrastructure including compute, storage, and
29、network resources. 3.1.2 network slice ITU-T Y.3100: A logical network that provides specific network capabilities and network characteristics. NOTE 1 Network slices enable the creation of customized networks to provide flexible solutions for different market scenarios which have diverse requirement
30、s, with respect to functionalities, performance and resource allocation. NOTE 2 A network slice may have the ability to expose its capabilities. NOTE 3 The behaviour of a network slice is realized via network slice instance(s). 3.1.3 network slice instance ITU-T Y.3100: An instance of network slice,
31、 which is created based on network slice blueprint. NOTE 1 A network slice instance is composed of a set of managed run-time network functions, and physical/logical/virtual resources to run these network functions, forming a complete instantiated logical network to meet certain network characteristi
32、cs required by the service instance(s). 2 Rec. ITU-T Y.3110 (09/2017) NOTE 2 A network slice instance may also be shared across multiple service instances provided by the network operator. A network slice instance may be composed of none, one or more sub-network slice instances which may be shared w
33、ith another network slice instance. 3.1.4 orchestration ITU-T Y.3100: In the context of IMT-2020, the processes aiming at the automated arrangement, coordination, instantiation and use of network functions and resources for both physical and virtual infrastructure by optimization criteria. 3.2 Terms
34、 defined in this Recommendation This Recommendation defines the following term: 3.2.1 IMT-2020: (Based on ITU-R M.2083-0) Systems, system components, and related aspects that support to provide far more enhanced capabilities than those described in b-ITU-R M.1645. 4 Abbreviations and acronyms This R
35、ecommendation uses the following abbreviations and acronyms: CAPEX Capital Expenditure KPI Key Performance Indicator LTE Long-term Evolution NFV Network Function Virtualization OPEX Operational Expenditure SDN Software Defined Network 5 Conventions None. 6 Introduction IMT-2020 network management an
36、d orchestration should support a combination of IMT-2020 network systems and existing systems (e.g., LTE-Advanced, Wi-Fi and fixed network), coupled with new or revolutionary technologies designed to meet new customer demands such as low latency, massive connectivity, and large volume transmission.
37、To meet these new requirements, the cost of deployment and operation will increase enormously. Network operators need to optimize capital expenditure/operational expenditure (CAPEX/OPEX) by strategically interacting with multiple technology ecosystems especially for different radio/fixed access and
38、virtualized core network technologies. Therefore, management and orchestration for IMT-2020 network is required to support both existing networks as well as evolving networks in an integrated manner. This Recommendation specifies such requirements in the following clauses. 7 High-level requirements
39、for network management and orchestration of IMT-2020 The high-level management and orchestration requirements are as follows: IMT-2020 network is required to manage and orchestrate all resources that can be used to instantiate slices. IMT-2020 network is required to provide capabilities to instantia
40、te a slice based on the available resources. IMT-2020 network is required to manage multiple slices (as slice instances) simultaneously and independently along with their lifecycle (including creation, instantiation, assurance, and termination of each slice). Rec. ITU-T Y.3110 (09/2017) 3 IMT-2020 n
41、etwork is required to provide capabilities to manage the total view of all active slice instances and remaining unused but available resources. IMT-2020 network is required to provide management capabilities that are dedicated to each slice instance. The instance management dedicated to a slice is r
42、equired to work independently from the instance management dedicated to another slice. IMT-2020 network is required to support the fulfilment, assurance and billing of each slice instance. IMT-2020 network is required to provide interfaces to support management and orchestration for existing network
43、s in an integrated manner. IMT-2020 network is required to support standard interfaces between capabilities for a) the slice lifecycle management and orchestration and b) the slice instance management. IMT-2020 network is required to support standard interfaces between a) the management and orchestr
44、ation capabilities for IMT-2020 network and b) the management and orchestration capabilities for existing networks. 8 Functional requirements for network management and orchestration of IMT-2020 8.1 Functional requirements of network slice life cycle management and orchestration The IMT-2020 slice l
45、ifecycle management is required to support slice capacity management and optimization to ensure optimal resource usage while maintaining quality. The IMT-2020 slice lifecycle management is required to support provisioning and instantiation of requested slices by the customers. Provisioning may invol
46、ve interactions with external provisioning functional entities such as software defined network/network function virtualization (SDN/NFV) orchestrator and/or controllers. The IMT-2020 slice lifecycle management is required to support inter-slice orchestration (e.g., orchestrated provisioning of mult
47、iple slices and resolving issues on quality, fault, anomaly, and charging among multiple slices). The IMT-2020 slice lifecycle management is required to support a standard interface for the customers and applications to request slice lifecycle management operations and associated information. The IM
48、T-2020 slice lifecycle management is required to support the assurance of the instantiated slices according to the given key performance indicator (KPI). The IMT-2020 slice lifecycle management is required to support the accounting management of the instantiated slices based on resource usage. The I
49、MT-2020 slice lifecycle management is required to store a) the slice-related information from customers request and b) the management information from the slice instance. The IMT-2020 slice lifecycle management is required to support the collection and analysis of the status and events of the instantiated slice resources for the purpose of fault, performance, and security management. The IMT-2020 slice lifecycle management is required to manage the lifecycle of the managem
