1、 ETSI TS 128 516 V14.0.0 (2017-05) LTE; Telecommunication management; Fault Management (FM) for mobile networks that include virtualized network functions; Procedures (3GPP TS 28.516 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 128 516 V14.0.0 (2017-05)13GPP TS 28.516 version 14.0
2、.0 Release 14Reference DTS/TSGS-0528516ve00 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 Importa
3、nt 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 au
4、thorization 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 shou
5、ld 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 fol
6、lowing 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 PDF
7、 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 r
8、egistered 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 Association
9、. ETSI ETSI TS 128 516 V14.0.0 (2017-05)23GPP TS 28.516 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 mem
10、bers 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.ets
11、i.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 th
12、e 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 bei
13、ng 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 516 V14.0.0 (2017-05)33GPP TS 28
15、.516 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 Fault Management procedures . 6g34.1 Introduction
16、6g34.2 NE alarm correlation in the context of NFV 7g34.2.1 NE alarm correlation made by EM in the context of NFV . 7g34.2.2 NE alarm correlation made by NM in the context of NFV . 8g34.3 Virtualization-specific aspect failure detection and notification 9g34.3.1 Virtualization-specific aspect failure
17、 detection and notification by VNFM . 9g34.3.2 Virtualization-specific aspect failure detection and notification by EM . 10g34.4 VNF Healing with operation request to VNFM by EM through Ve-Vnfm-em 11g3Annex A (informative): Change history . 12g3History 13g3ETSI ETSI TS 128 516 V14.0.0 (2017-05)43GPP
18、 TS 28.516 version 14.0.0 Release 14Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the cont
19、ents 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; 2 presented to TSG for approval; 3 or greater indicates TSG approved do
20、cument 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 incorporated in the document. Introduction The present document is part of a TS-
21、family covering the 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management, as identified below: TS 28.515 “Fault Management (FM) for mobile networks that include virtualized network functions; Requirements“. TS 28.516 “Fault Manag
22、ement (FM) for mobile networks that include virtualized network functions; Procedures“. TS 28.517 “Fault Management (FM) for mobile networks that include virtualized network functions; Stage 2“. TS 28.518 “Fault Management (FM) for mobile networks that include virtualized network functions; Stage 3“
23、. ETSI ETSI TS 128 516 V14.0.0 (2017-05)53GPP TS 28.516 version 14.0.0 Release 141 Scope The present document specifies the Fault Management procedures for mobile networks that include virtualized network functions which can be part of EPC or IMS. 2 References The following documents contain provisi
24、ons 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-specific. - For a specific reference, subsequent revisions do not apply. - For a non-specific re
25、ference, 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 Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP
26、 TS 32.111-2: “Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP) Information Service (IS)“. 3 ETSI GS NFV-IFA 008 (V2.1.1): “Network Functions Virtualisation (NFV); Management and Orchestration; Ve-Vnfm Reference Point - Interface and Information Model S
27、pecification“. 4 3GPP TS 28.515: “Telecommunication management; Fault Management (FM) for mobile networks that include virtualized network functions; Requirements“. 5 3GPP TS 28.500: “Telecommunication management; Management concept, architecture and requirements for mobile networks that include vir
28、tualized network functions“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 1 and in 3GPP TS 28.500 5 and the following apply. A term defined in the present document takes precedence over the definition of t
29、he same term, if any, in 3GPP TR 21.905 1 or in 3GPP TS 28.500 5. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 1 and in 3GPP TS 28.500 5 and the following apply. An abbreviation defined in the present document takes precedence over the definit
30、ion of the same abbreviation, if any, in 3GPP TR 21.905 1 or in 3GPP TS 28.500 5. VM Virtual Machine VNFC Virtualized Network Function Component vNIC virtual Network Interface Card vPORT virtual Port ETSI ETSI TS 128 516 V14.0.0 (2017-05)63GPP TS 28.516 version 14.0.0 Release 144 Fault Management pr
31、ocedures 4.1 Introduction The overview of alarm data flow procedures in context of NFV is showed as Figure 4.1-1 3GPP view of FM data flows. OSS NFVOVNFMVIMNFVIEMVNFVe-Vnfm-emVe-Vnfm-vnfVn-NfType 1Itf-NNf-ViVi-VnfmOr-VnfmOr-ViOs-Ma-NfvoNEType 1Figure 4.1-1: 3GPP view of alarm data flows for NE/VNF T
32、he alarm data flow and the alarm mapping of VNF instance application alarm and VNF instance related virtualized resource alarm are described as below: - Flow-1 VIM reports virtualized resources alarm data to VNFM (out of scope of the present document). - Flow-2 VNFM sends VNF alarm data related to v
33、irtualized resources (mapped to VNF instance, correlated or not-correlated) to EM. - Flow-3 VNF reports virtualization-specific alarm data to VNFM. - Flow-X Via 3GPP Type 1 interface VNF instance reports VNF instance application alarm data and virtualization-specific alarm data to EM. - Flow-Z Via 3
34、GPP Type 1 interface non-virtualized NEs report alarm data to EM. - Flow-Y Via 3GPP Itf-N EM sends the following: VNF instance application alarm data and virtualization-specific alarm data (received via Flow-X), VNF alarm data related to virtualized resources (received via Flow-2),non-virtualized NE
35、 alarm data (received via Flow-Z), and/or correlated VNF instance alarm data. EM may make the alarm correlation based on information contained in Flow-X, Flow-Z and Flow-2, using the same VNF/VNFC instance identifier based on the VNF instance alarm data related to virtualized resource and VNF instan
36、ce application alarm data. EM may report the correlated VNF instance alarm data to NM. NM may make the alarm correlation based on information contained in Flow-X, Flow-Y, Flow-Z and Flow-2, using the same VNF/VNFC instance identifier based on the VNF instance alarm data related to virtualized resour
37、ce and VNF instance application alarm data. The procedures listed in clause 4, as some of all the possibilities, are not exhaustive. ETSI ETSI TS 128 516 V14.0.0 (2017-05)73GPP TS 28.516 version 14.0.0 Release 144.2 NE alarm correlation in the context of NFV 4.2.1 NE alarm correlation made by EM in
38、the context of NFV When a new failure occurs from the virtualized resource and it impacts the corresponding NE application, EM can make the alarm correlation based on the virtualized resource failure report sent from VNFM and VNF application alarms. The figure 4.2.1-1 illustrates the procedure of EM
39、 makes NE alarms correlation in a mobile network that includes virtualized network functions. EM VNFM NFVO3.Notify5.Correlates the VNF instance related to virtualized resource with VNF application alarms4.Sends VNF application alarmsNE/VNFVIM2.VNFM received virtualized resource alarms as described i
40、n ETSI NFV ISG1. A new failure occurs from the virtualized resource and it impacts corresponding NE applicationNM6.notifyNewAlarm Figure 4.2.1-1: Procedure of NE alarm correlation made by EM in the context of NFV 1) A new failure occurs from the virtualized resource and it impacts the corresponding
41、NE application. 2) VNFM received virtualized resource alarms as described in ETSI NFV ISG. 3) VNFM sends VNF instance alarms related to virtualized resource to EM. The VNF and/or VNFC alarms related to virtualized resource include AlarmId, affected VNF identifier, affected VNFC identifiers, and Faul
42、tDetails which provides additional information about the virtualized resource fault, for example the resource identifier which causes the fault (e.g. VM identifier, vNIC identifier or vPORT identifier). The Alarm information element see clause 9.3.4 of 3. 4) NE/VNF sends VNF application alarms to EM
43、 through proprietary interface, the corresponding VNF instance identifier and/or VNFC identifier should be included. NOTE: There is no sequence restriction on EM receives VNF instance alarms related virtualized resource and EM receives VNF application alarms. ETSI ETSI TS 128 516 V14.0.0 (2017-05)83
44、GPP TS 28.516 version 14.0.0 Release 145) EM correlates the received VNF instance alarms related to virtualized resource with the received VNF application alarms. 6) EM sends the correlated alarm information to NM over Itf-N. The alarm information that carries correlated alarm information is specifi
45、ed in TS 32.111-2 2. 4.2.2 NE alarm correlation made by NM in the context of NFV When a new failure occurred from the virtualized resource and it impacts corresponding NE application, NM can make the alarm correlation based on the virtualized resource failure report sent from VNFM and VNF applicatio
46、n alarms. The figure 4.2.2-1 illustrates the procedure of NM makes NE alarms correlation in a mobile network that includes virtualized network functions. EM VNFM NFVO3.Notify5.Sends VNF application alarmsNE/VNFVIM2.VNFM received virtualized resource alarms as described in ETSI NFV ISG1. A new failur
47、e occurs from the virtualized resource and it impacts corresponding NE applicationNM4.notifyNewAlarm6.notifyNewAlarm7.Correlates the VNF instance related to virtualized resource with VNF application alarmsFigure 4.2.2-1: Procedure of NE alarm correlation made by NM in the context of NFV 1) A new fai
48、lure occurs from the virtualized resource and it impacts corresponding NE application. 2) VNFM receives virtualized resource alarms as described in 3. 3) VNFM sends VNF instance alarms related to virtualized resource to EM. The VNF and/or VNFC alarms related to virtualized resource include AlarmId,
49、affected VNF identifier, affected VNFC identifiers, and FaultDetails which provides additional information about the virtualized resource fault, for example the resource identifier which causes the fault (e.g. VM identifier, vNIC identifier or vPORT identifier). The Alarm information element see clause 9.3.4 of 3. 4) EM sends VNF instance alarms related to virtualized resource to NM. 5) NE/VNF sends VNF application alarms to EM through proprietary interface, the corresponding VNF instance identifier and/or VNFC identifier should be included.
