ETSI TS 128 515-2017 LTE Telecommunication management Fault Management (FM) for mobile networks that include virtualized network functions Requirements (V14 1 0 3GPP TS 28 515 vers.pdf

1、 ETSI TS 128 515 V14.0.0 (2017-05) LTE; Telecommunication management; Fault Management (FM) for mobile networks that include virtualized network functions; Requirements (3GPP TS 28.515 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 128 515 V14.0.0 (2017-05)13GPP TS 28.515 version 14

2、.0.0 Release 14Reference DTS/TSGS-0528515ve00 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 7803/88 Impor

3、tant 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 prior written

4、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 present document sh

5、ould 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 to one of the f

6、ollowing 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 content of the P

7、DF 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 Marks of ETSI

8、 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. oneM2M logo is protected for the benefit of its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Associati

9、on. ETSI ETSI TS 128 515 V14.0.0 (2017-05)23GPP TS 28.515 version 14.0.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 m

10、embers and non-members, and can be found in 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.e

11、tsi.org/). Pursuant to the ETSI IPR Policy, 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

12、the present document. Foreword This Technical 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 b

13、eing references to the corresponding ETSI 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“,

14、 “will not“, “can“ and “cannot“ are to be 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 515 V14.0.0 (2017-05)33GPP TS

15、28.515 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 5g34 Concepts and background 6g34.1 Fault Management

16、in the context of NFV 6g35 Business level requirements . 6g35.1 Requirements 6g35.2 Actor roles 6g35.3 Telecommunications resources 6g35.4 High-level use cases . 7g35.4.1 NE alarm correlation in the context of NFV . 7g35.4.2 NFVI Maintenance coordination 7g36 Specification level requirements 8g36.1

17、Requirements 8g36.1.1 Requirements for Itf-N 8g36.1.2 Requirements for Os-Ma-nfvo 8g36.1.3 Requirements for Ve-Vnfm-em 8g36.1.4 Requirements for Ve-Vnfm-vnf 8g36.2 Actor roles 8g36.3 Telecommunications resources 8g36.4 Use cases 9g36.4.1 NE alarm correlation in the context of NFV . 9g36.4.2 VNF Heal

18、ing through operation request to VNFM by EM 9g36.4.3 Virtualization-specific aspect failure detection and notification by VNFM . 10g36.4.4 Virtualization-specific aspect failure detection and notification by EM . 11g36.4.5 NE alarm reporting in the context of NFV . 11g36.4.6 Virtualization-specific

19、aspect failure notification by VNFM . 12g3Annex A (informative): Change history . 13g3History 14g3ETSI ETSI TS 128 515 V14.0.0 (2017-05)43GPP TS 28.515 version 14.0.0 Release 14Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of th

20、e present document are subject to continuing work within the TSG and 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: Versio

21、n x.y.z where: x the first digit: 1 presented to TSG for information; 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 thir

22、d digit is incremented when editorial only changes have been incorporated in the document. Introduction The present document is part of a TS-family covering the 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management, as identified

23、below: TS 28.515 “Fault Management (FM) for mobile networks that include virtualized network functions; Requirements“. TS 28.516 “Fault Management (FM) for mobile networks that include virtualized network functions; Procedures“. TS 28.517 “Fault Management (FM) for mobile networks that include virtu

24、alized network functions; Stage 2“. TS 28.518 “Fault Management (FM) for mobile networks that include virtualized network functions; Stage 3“. ETSI ETSI TS 128 515 V14.0.0 (2017-05)53GPP TS 28.515 version 14.0.0 Release 141 Scope The present document (together with the relevant requirements describe

25、d in 2, 3, 4 and 5) specifies the requirements applicable to Fault Management (FM) of virtualized network functions which can be part of EPC or IMS. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - Referen

26、ces are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. - 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

27、 document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 28.500: “Telecommunication management; Management concept, architecture and requirements for mo

28、bile networks that include virtualized network functions“. 3 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. 4 3GPP TS 32.102: “Telecommunication management; Architecture“. 5 3GPP TS 32.111-1: “Telecommunication management; Fault Management; Part 1: 3G fault m

29、anagement requirements“. 6 ETSI GS NFV-IFA 010 (V2.2.1): “Network Functions Virtualisation (NFV); Management and Orchestration; Functional Requirements Specification“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TR

30、 21.905 1 and in 3GPP TS 28.500 2 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 1 or in 3GPP TS 28.500 2. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TR

31、21.905 1 and in 3GPP TS 28.500 2 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 1 or in 3GPP TS 28.500 2. VM Virtual Machine vNIC virtual Network Interface Card vPORT virtual Port ETSI

32、ETSI TS 128 515 V14.0.0 (2017-05)63GPP TS 28.515 version 14.0.0 Release 144 Concepts and background 4.1 Fault Management in the context of NFV Fault Management functionality traditionally includes fault detection, generation of alarms, clearing of alarms, alarm forwarding and filtering, storage and

33、retrieval of alarms, correlation of alarms and events, alarm root cause analysis and fault recovery. With introduction of virtualized network functions (VNFs) into mobile networks, Fault Management functionality is distributed over different functional blocks. These different functional blocks may b

34、e located at different levels such as NFV Infrastructure (NFVI) level, NE level, NFV Management and Orchestration level and 3GPP network management level. The decoupling of software from hardware by means of virtualization changes the way in which the faults were managed in non-virtualized NE deploy

35、ments: - Physical hardware faults of NFVI are detected by NFVI and corrected jointly with the support from NFV-MANO. Only information about those faults (e.g. faults corresponding to the virtualized resources) that affect the proper functioning of VNF needs to be provided to 3GPP management system.

36、- VNF-related virtualized resource fault information needs to be sent from NFV-MANO to 3GPP management system, and then 3GPP management system can take some necessary actions. - VNF application fault information needs to be sent from the VNF instance to the corresponding 3GPP management system that

37、is responsible for taking some necessary actions. - VNF virtualization-specific fault information is detected by VNF and needs to be sent from the VNF instance to both the VNFM and the corresponding 3GPP management system so that they can take necessary actions accordingly. 5 Business level requirem

38、ents 5.1 Requirements REQ-NFV_FM-CON-1 The faulty virtualization-specific aspect of a virtualized network function shall be able to be recovered. REQ-NFV_FM-CON-2 3GPP management system shall be able to get VNF application fault reports about a faulty NE. REQ-NFV_FM-CON-3 3GPP management system shal

39、l be able to get VNF virtualization-related fault reports from NFV-MANO. REQ-NFV_FM-CON-4 The content of the fault information from VNF application fault reports and VNF virtualization-related fault reports shall enable 3GPP management system to correlate VNF application fault(s) with VNF virtualiza

40、tion-related fault(s). REQ-NFV_FM-CON-5 EM shall be able to send to VNFM a request to recover the faulty virtualization-specific aspect of a virtualized network function. 5.2 Actor roles See actors and roles of each use case in clause 5.4. 5.3 Telecommunications resources See telecom resources of ea

41、ch use case in clause 5.4. ETSI ETSI TS 128 515 V14.0.0 (2017-05)73GPP TS 28.515 version 14.0.0 Release 145.4 High-level use cases 5.4.1 NE alarm correlation in the context of NFV Use Case Stage Evolution / Specification Related use Goal To correlate NE alarms in a mobile network that includes virtu

42、alized network functions. Actors and Roles 3GPP management system (EM, NM) correlates NE alarms. NFV MANO functional entity VNFM notifies virtualized resource alarms to 3GPP management system. Telecom resources VNFM, 3GPP management system (EM, NM) Assumptions - 3GPP management system can get VNF ap

43、plication alarms of the faulty NE, and - VNFM can get virtualized resource alarms and identify the corresponding VNF instance. Pre conditions N/A Begins when There is a new failure which may impact the virtualized resource and the corresponding NE application. Step 1 (M) 3GPP management system gets

44、VNF application alarm(s) of a faulty NE. VNFM gets virtualized resource alarm(s) and notifies the corresponding VNF instance related virtualized resource alarm(s) to 3GPP management system. Step 2 (M) Based on the virtualized resource alarm(s) sent from VNFM and those VNF application alarms reported

45、 from NE, 3GPP management system makes alarm correlation. Ends when Ends when all mandatory steps identified above are successfully completed or when an exception occurs. Exceptions One of the steps identified above fails. Post Conditions The virtualized resource alarm(s) and VNF application alarm(s

46、) are correlated by 3GPP management system. Traceability REQ-MAMO_FM-CON-3, REQ-MAMO_FM-CON-4, REQ-MAMO_FM-CON-5 5.4.2 NFVI Maintenance coordination Use Case Stage Evolution / Specification Related use Goal To avoid the unwanted impact to VNF application from NFVI maintenance Actors and Roles NM, NF

47、VO, VNFM, VIM Telecom resources NFVO, VNFM VIM, NFVI Assumptions There is an agreement that NFV-MANO system should get permission from NM before scheduled NFVI maintenance, managed by NFV-MANO, can start. Pre conditions N/A Begins when NFVO receives a notification from VIM informing about NFVI maint

48、enance impacting the VRs (Virtualised Resources) that are used by a NS instance (e.g. the subordinative VNF instances and Virtual Links). Step 1 (M) NFVO informs NM about the NFVI maintenance. Step 2 (M) NM confirms the NFVI maintenance positively or not positively. Step 3 (M) NFVO acts according to

49、 the response from NM. Ends when Ends when all mandatory steps identified above are successfully completed or when an exception occurs. Exceptions One of the steps identified above fails. Post Conditions NFVI maintenance activity has been coordinated between NM and NFVO. Traceability FFS ETSI ETSI TS 128 515 V14.0.0 (2017-05)83GPP TS 28.515 version 14.0.0 Release 146 Specification level requirements 6.1 Requirements 6.1.1 Requirements for Itf-N REQ-NFV_FM_Itf-N-FUN-1 IRPAgent shall have the capability to send VNF application alarms to IRPM