1、 ETSI TS 128 500 V14.1.0 (2017-04) LTE; Telecommunication management; Management concept, architecture and requirements for mobile networks that include virtualized network functions (3GPP TS 28.500 version 14.1.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 128 500 V14.1.0 (2017-04)13GPP TS 28.
2、500 version 14.1.0 Release 14Reference DTS/TSGS-0528500ve10 Keywords LTE ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N
3、 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the
4、prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the prese
5、nt document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment t
6、o one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The co
7、ntent of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade
8、 Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 128 500 V14.1.0 (2017-04)
9、23GPP TS 28.500 version 14.1.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found i
10、n ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy
11、, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Techni
12、cal Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI
13、deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be
14、interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 128 500 V14.1.0 (2017-04)33GPP TS 28.500 version 14.1.0 Release 14Contents I
15、ntellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Background and concepts . 8g34.1 Background 8g34.2 Concepts . 8g34.2.1 NE and VNF
16、 . 8g34.2.2 The relationship between NE and VNF 9g35 Business level requirements . 9g35.1 Requirements 9g35.1.1 General requirements 9g35.1.2 FM requirements . 10g35.1.3 CM requirements 10g35.1.4 PM requirements . 11g35.1.5 LCM requirements 11g35.2 Actor roles 12g35.3 Telecommunications resources 12
17、g35.4 High-level use cases . 12g35.4.1 FM use cases . 12g35.4.1.1 Use case of VNF Healing triggered by 3GPP management system 12g35.4.1.2 Use case of virtualization-specific aspect failure detection and notification by NFV-MANO . 13g35.4.1.3 Use case of alarms correlation by 3GPP management system 1
18、3g35.4.2 CM use cases 13g35.4.2.1 Use case of adding a MO related to a VNF . 14g35.4.2.2 Use case of associating the MO with a certain VNF instance . 14g35.4.2.3 Use case of configuring the VNF by 3GPP management system . 15g35.4.2.4 Use case of removing the MO of a VNF from managed nodes. 15g35.4.2
19、.5 Modify non-application information and configuration of a VNF instance managed by NFV-MANO 16g35.4.2.6 Retrieve non-application information of a VNF instance managed by NFV-MANO . 16g35.4.3 PM use cases . 17g35.4.3.1 Use case of mitigating the VNF performance bottleneck 17g35.4.3.2 Use case for c
20、ollection of VNF PM data related to virtualized resource from NFV-MANO . 17g35.4.4 LCM use cases 18g35.4.4.1 Use case of NS instance Deployment 18g35.4.4.2 Use case of updating an NS instance to a different NSD version . 19g35.4.4.3 Use cases of NE deployment in the context of NFV . 20g35.4.4.3.1 Us
21、e case of NE deployment in the scenario of Managed Object(s) creation is after the VNF instantiation . 20g35.4.4.4 Use case for notifications about VNF lifecycle changes . 20g35.4.4.5 Use case of VNF instance scaling through operation request by 3GPP management system . 22g35.4.4.6 Use case of enabl
22、ing/disabling the auto-scaling of the corresponding VNF instance(s) . 23g35.4.4.7 Determination on the termination of the corresponding VNF instance(s) 23g36 Management architecture . 24g36.1 Overview 24g3ETSI ETSI TS 128 500 V14.1.0 (2017-04)43GPP TS 28.500 version 14.1.0 Release 146.1.1 Management
23、 architecture 24g36.1.2 Functional blocks in the management architecture . 25g36.1.2.1 NM 25g36.1.2.2 EM/DM . 25g36.1.2.3 NFV-MANO . 25g36.1.2.4 NFVI . 25g36.2 Management interfaces . 26g36.2.1 Overview 26g36.2.2 Itf-N 26g36.2.3 Os-Ma-nfvo. 26g36.2.4 Ve-Vnfm-em and Ve-Vnfm-vnf . 26g3Annex A: Change
24、history 27g3History 28g3ETSI ETSI TS 128 500 V14.1.0 (2017-04)53GPP TS 28.500 version 14.1.0 Release 14Foreword This Technical Specification (TS) has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and
25、may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information;
26、 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorpor
27、ated in the document. Introduction Traditionally, telecommunication equipment is provided as equipment with integrated software and hardware. Virtualization technologies decouple the software and hardware, and the network function software can be executed on COTS hardware. The mobile network will be
28、 composed of virtualized network functions and non-virtualized network elements in the future. Virtualized network functions, like traditional non-virtualized network elements, need also to be managed. Due to the decoupling of network function software and hardware, ETSI ISG NFV introduces the NFV M
29、anagement and Orchestration architecture, which interacts with 3GPP network management system, to realize the management of virtualized network functions lifecycle and resource allocation. 3GPP specifies the management solution of mobile networks that include virtualized network functions and clarif
30、ies the relationship between 3GPP management architecture and ETSI ISG NFV Management and Orchestration architecture. The present document specifies the management concept, requirements and architecture for mobile networks that include virtualized network functions. ETSI ETSI TS 128 500 V14.1.0 (201
31、7-04)63GPP TS 28.500 version 14.1.0 Release 141 Scope The present document specifies the management concepts, the management requirements and use cases from operators perspective for mobile networks that include virtualized network functions which can be part of EPC or IMS, and provides the manageme
32、nt architecture for these mobile networks. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either specific (identified by date of publication, edition number, version number, etc.) or non-s
33、pecific. - For a specific reference, subsequent revisions do not apply. - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
34、Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 ETSI GS NFV-IFA 010: “Network Functions Virtualisation (NFV); Management and Orchestration; Functional Requirements Specification“. 3 ETSI GS NFV-MAN 001 V1.1.1: “Network Function Virtualisation (NFV); Managem
35、ent and Orchestration“. 4 ETSI GS NFV 003 V1.2.1: “Network Functions Virtualisation (NFV); Terminology for Main Concepts in NFV“. 5 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. 6 3GPP TS 32.401: “Telecommunication management; Performance Management (PM); Co
36、ncept and requirements“. 7 3GPP TS 32.111-1: “Telecommunication management; Fault Management; Part 1: 3G fault management requirements“. 8 3GPP TS 32.150: “Telecommunication management; Integration Reference Point (IRP) Concept and definitions“. 9 ETSI GS NFV-IFA 013 v2.1.1: “Network Function Virtua
37、lization (NFV); Management and Orchestration; Os-Ma-nfvo Reference Point - Interface and Information Model Specification“. 10 ETSI GS NFV-IFA 008 v2.1.1: “Network Functions Virtualisation (NFV); Management and Orchestration; Ve-Vnfm Reference Point - Interface and Information Model Specification“. 1
38、1 3GPP TS 28.510: “ Telecommunication management; Configuration Management (CM) for mobile networks that include virtualized network functions; Requirements“. 12 3GPP TS 32.102: “Telecommuncations management; Architecture“ ETSI ETSI TS 128 500 V14.1.0 (2017-04)73GPP TS 28.500 version 14.1.0 Release
39、143 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 1, TS 32.101 5, TS 32.111-1 7, TS 32.150 8, TS 32.401 6 and the following apply. A term defined in the present document takes precedence over the definiti
40、on of the same term, if any, in TR 21.905 1. Consumer Role: See service consumer in clause 5 of 3GPP TS 32.101 5. See consumer in ETSI GS NFV-MAN 001 3). LifeCycle Management (LCM): Defined in ETSI GS NFV 003 4. NOTE 1: How to define the lifecycle management of 3GPP network and entity is FFS. Networ
41、k Functions Virtualisation Infrastructure (NFVI): Defined in ETSI GS NFV 003 4. Network Functions Virtualisation Management and Orchestration (NFV-MANO): Defined in ETSI GS NFV 003 4. Network Functions Virtualisation Orchestrator (NFVO): Defined in ETSI GS NFV 003 4. NS: Network Service defined in E
42、TSI GS NFV 003 4. NOTE 2: The NS defined by ETSI NFV documents is not equivalent to 3GPP services. The latter requires the former for network orchestration in case the network includes virtualized network functions. Physical Network Function (PNF): Defined in ETSI GS NFV 003 4. NOTE 3: From 3GPP per
43、spective, non-virtualized NE is a typical example of PNF. Producer Role: See service producer in clause 5 of 3GPP TS 32.101 5. See producer in ETSI GS NFV-MAN 0013). Scaling: Defined in ETSI GS NFV 003 4. Virtual Machine (VM): Defined in ETSI GS NFV 003 4. Virtualised Infrastructure Manager (VIM): D
44、efined in ETSI GS NFV 003 4. Virtualised Network Function (VNF): Defined in ETSI GS NFV 003 4. NOTE 4: From 3GPP perspective, it corresponds to the application level function of NE, which is defined in 3GPP TS 32.101 5. Virtualised Network Function Manager (VNFM): Defined in ETSI GS NFV 003 4. Virtu
45、alised Network Function Package (VNF Package): Defined in ETSI GS NFV 003 4. VNF Healing: Defined in ETSI GS NFV-IFA010 2. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 1 and the following apply. An abbreviation defined in the present document takes
46、 precedence over the definition of the same abbreviation, if any, in TR 21.905 1. CAPEX CAPital EXpenditure COTS Commercial Off-The-Shelf LCM LifeCycle Management NFV Network Functions Virtualization NFVO Network Functions Virtualization Orchestrator ETSI ETSI TS 128 500 V14.1.0 (2017-04)83GPP TS 28
47、.500 version 14.1.0 Release 14NS Network Service NSD NS DescriptorOPEX OPerating EXpense OSS Operations Support System VIM Virtualized Infrastructure Manager VNF Virtualized Network Function VNFM Virtualized Network Function Manager 4 Background and concepts 4.1 Background It is expected that future
48、 implementation options for the entities of the 3GPP system include various technologies for virtualization. Network and service providers make use of different information in several different ways which also may vary from network to network and from time to time. Hence, entities of the 3GPP system
49、 that have been implemented with virtualization options should be managed in the same manner as entities implemented with non-virtualization options, to the extent possible. Virtualized 3GPP entities still require some underlying hardware resources. One of the NFV business objectives is that VNFs are procured independently from the underlying hardware resources. The underlying hardware resources are expected to be administered independently from the virtualized entities required for the 3GPP system.
