1、 ETSI TS 128 517 V14.0.0 (2017-05) LTE; Telecommunication management; Fault Management (FM) for mobile networks that include virtualized network functions; Stage 2 (3GPP TS 28.517 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 128 517 V14.0.0 (2017-05)13GPP TS 28.517 version 14.0.0
2、Release 14Reference DTS/TSGS-0528517ve00 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 Important
3、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 autho
4、rization 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 should
5、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 follow
6、ing 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 ve
7、rsion 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 regi
8、stered 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. E
9、TSI ETSI TS 128 517 V14.0.0 (2017-05)23GPP TS 28.517 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 member
10、s 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.etsi.o
11、rg/). 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 the p
12、resent 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 being
13、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“, “wil
14、l 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 517 V14.0.0 (2017-05)33GPP TS 28.51
15、7 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 General descriptions . 5g35 Information model definit
16、ion . 6g35.1 Itf-N 6g35.2 Os-Ma-nfvo 6g35.3 Ve-Vnfm-em 6g35.4 Ve-Vnfm-vnf 6g35.5 Mapping rule for alarm information elements 6g35.5.1 For construction of notifyNewAlarm 6g35.5.2 For construction of notifyClearedAlarm . 7g35.5.3 For construction of notifyChangedAlarm . 8g35.5.4 For construction of no
17、tifyAckStateChangedAlarm 8g36 Interface definition . 9g36.1 Itf-N 9g36.2 Ve-Vnfm-em 9g3Annex A (informative): Change history . 10g3History 11g3ETSI ETSI TS 128 517 V14.0.0 (2017-05)43GPP TS 28.517 version 14.0.0 Release 14Foreword This Technical Specification has been produced by the 3rdGeneration P
18、artnership 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 contents of the present document, it will be re-released by the TSG with an identifying change of release date and an
19、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 document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhanc
20、ements, 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-family covering the 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects;
21、 Telecommunication management, as identified 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 Managemen
22、t (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“. ETSI ETSI TS 128 517 V14.0.0 (2017-05)53GPP TS 28.517 version 14.0.0 Release 141 Scope The present document is F
23、ault Management stage 2 specification for mobile networks that include 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. - References are either
24、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 document), a n
25、on-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 32.111-2: “Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP); In
26、formation Service (IS)“. 3 3GPP TS 32.302: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Information Service (IS)“. 4 3GPP TS 28.515: “Telecommunication management; Fault Management (FM) for mobile networks that include virtualized netw
27、ork functions; Requirements“. 5 ETSI GS NFV-IFA 008 (V2.1.1): “Network Functions Virtualisation (NFV); Management and Orchestration; Ve-Vnfm reference point Interface and Information Model Specification“. 6 3GPP TS 28.500: “Telecommunication management; Management concept, architecture and requireme
28、nts for mobile networks that include virtualized 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 6 and the following apply. A term defined in the present document t
29、akes precedence over the definition of the same term, if any, in 3GPP TR 21.905 1 or in 3GPP TS 28.500 6. 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 6 and the following apply. An abbreviation defined in the present do
30、cument takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 1 or in 3GPP TS 28.500 6. 4 General descriptions For VNF Fault Management stage 2 solution over Itf-N, the Alarm IRP IS is applicable. The overall architectural feature of Alarm IRP is specified in TS 32.
31、111-2 2. The Alarm IRP IS defines the semantics of alarms and the interactions visible across the reference point in a protocol neutral way. It defines the semantics of the operations and ETSI ETSI TS 128 517 V14.0.0 (2017-05)63GPP TS 28.517 version 14.0.0 Release 14notifications visible in the Alar
32、m IRP. It does not define the syntax or encoding of the operations, notifications and their parameters. For the purpose of notification, Notification IRP 3 is needed. 5 Information model definition 5.1 Itf-N For Itf-N VNF alarm management, the IOCs defined by AlarmIRP which is specified in clause 5
33、of 3GPP TS 32.111-2 2 shall be used. 5.2 Os-Ma-nfvo None. 5.3 Ve-Vnfm-em For Ve-Vnfm-em alarm management, the information elements and notifications which are specified in subclause 9.3 of IFA 008 5 for VNF alarm management shall be used. 5.4 Ve-Vnfm-vnf None. 5.5 Mapping rule for alarm information
34、elements 5.5.1 For construction of notifyNewAlarm The following table shows the rule on how to construct the various attributes of notifyNewAlarm (see clause 6.8.1 of TS 32.111-2 2). The first column shows the notifyNewAlarm notification attributes. The second column shows the “Attributes of the Ala
35、rm information element“ (see clause 9.3.4.2 of 5) used by AlarmNotification (see clause 9.3.2 of 5) produced by VNFM. ETSI ETSI TS 128 517 V14.0.0 (2017-05)73GPP TS 28.517 version 14.0.0 Release 14Table 5.5.1: Mapping rule for notifyNewAlarm NotifyNewAlarm attributes of TS 32.111-2 2 Attributes of A
36、larm information elements in AlarmNotification of 5 Notes objectClass This and the next 3GPP defined attribute are used for the DN of an MOI (whose attribute vnfInstanceIdList contains one vnfInstanceId). objectInstance See above notificationId See entry in Table 6.8.1.2 of TS 32.111-2 2 eventTime e
37、ventTime systemDN See entry in Table 6.8.1.2 of TS 32.111-2 2 notificationType See entry in Table 6.8.1.2 of TS 32.111-2 2 probableCause probableCause perceivedSeverity perceivedSeverity rootCauseIndicator isRootCause alarmType faultType specificProblem faultDetails correlatedNotifications correlate
38、dAlarmId backedUpStatus Not used backUpObject Not usedtrendIndication Not used thresholdInfo Not usedstateChangeDefinition Not used monitoredAttributes Not used proposedRepairActions Not used additionalText See entry in Table 6.8.1.2 of TS 32.111-2 2 additionalInformation managedObjectId, vnfcId Thi
39、s is a list of two elements (encoded as strings) separatred by a semicolon. The first element is a string “vnfId:abc” where abc is managedObjectId (of second column). The second element is a string “vnfcId:xyz” where xyz is the vnfcid (of second column). alarmId alarmId 5.5.2 For construction of not
40、ifyClearedAlarm The following table shows the rule on how to construct the various attributes of notifyClearedAlarm (see clause 6.8.3 of TS 32.111-2 2). The first column shows the notifyClearedAlarm notification attributes. The second column shows the “Attributes of the AlarmClearedNotification (see
41、 clause 9.3.3.3 of 5) produced by VNFM. Table 5.5.2: Mapping rule for notifyClearedAlarm NotifyClearedAlarm attributes of TS 32.111-2 2 Attributes of Alarm information elements in AlarmNotification of 5 Notes objectClass See Notes of Table 5.5.1 objectInstance See Notes of Table 5.5.1 notificationId
42、 See entry in Table 6.8.1.2 of TS 32.111-2 2 eventTime alarmClearedTime systemDN See entry in Table 6.8.1.2 of TS 32.111-2 2 notificationType See entry in Table 6.8.3.2 of TS 32.111-2 2 probableCause Use the probableCause of the related notifyNewAlarm perceivedSeverity Use the value cleared. alarmTy
43、pe Use the alarmType of the related notifyNewAlarm. correlated Notifications See entry in Table 6.8.3.2 of TS 32.111-2 2 clearUserId Not used. clearSystemId Not usedalarmId alarmId ETSI ETSI TS 128 517 V14.0.0 (2017-05)83GPP TS 28.517 version 14.0.0 Release 145.5.3 For construction of notifyChangedA
44、larm The following table shows the rule on how to construct the various attributes of notifyChangedAlarm (see clause 6.8.1 of TS 32.111-2 2). The first column shows the notifyChangedAlarm notification attributes. The second column shows the “Attributes of the Alarm information element” (see clause 9
45、.3.4.2 of 5) used by AlarmNotification (see clause 9.3.2 of 5) produced by VNFM. Table 5.5.3: Mapping rule for notifyChangedAlarm NotifyChangedAlarm attributes of TS 32.111-2 2 Attributes of Alarm information elements in AlarmNotification of 5 Notes objectClass See Notes of Table 5.5.1 objectInstanc
46、e See Notes of Table 5.5.1 notificationId See entry in Table 6.8.1.2 of TS 32.111-2 2 eventTime alarmChangedTime systemDN See entry in Table 6.8.1.2 of TS 32.111-2 2 notificationType See entry in Table 6.8.1.2 of TS 32.111-2 2 probableCause probableCause perceivedSeverity perceivedSeverity alarmType
47、 faultType alarmId alarmId 5.5.4 For construction of notifyAckStateChangedAlarm The following table shows the rule on how to construct the various attributes of notifyAckStateChangedAlarm (see clause 6.8.2 of TS 32.111-2 2). The first column shows the notifyAckStateChangedAlarm notification attribut
48、es. The second column shows the “Attributes of the Alarm information element” (see clause 9.3.4.2 of 5) used by AlarmNotification (see clause 9.3.2 of 5) produced by VNFM. Table 5.5.4: Mapping rule for notifyAckStateChangedAlarm NotifyAckStateChangedAlarm attributes of 3 Attributes of Alarm informat
49、ion elements in AlarmNotification of 2 Notes objectClass See Notes of Table 5.5.1 objectInstance See Notes of Table 5.5.1 notificationId See entry in Table 6.8.1.2 of TS 32.111-2 2 eventTime eventTime systemDN See above notificationType See entry in Table 6.8.1.2 of TS 32.111-2 2 probableCause probableCause perceived Severity perceivedSeverity alarmType faultType alarmId alarmIdackState ackState ackUserId ackSystemIdETSI ETSI TS 128 517 V14.0.0 (2017-05)93GPP TS 28.517 ve
