1、 ETSI TS 132 121 V15.0.0 (2018-07) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP): Requirements (3GPP TS 32.121 version 15.0.0 Release
2、 15) TECHNICAL SPECIFICATION ETSI ETSI TS 132 121 V15.0.0 (2018-07)13GPP TS 32.121 version 15.0.0 Release 15Reference RTS/TSGS-0532121vf00 Keywords GSM,LTE,UMTS 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 0001
3、7 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 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 ele
4、ctronic and/or print versions of the present document shall not be modified without the 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 (P
5、DF) version kept on a specific network drive within ETSI Secretariat. Users of the present 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/ETSIDeliv
6、erableStatus.aspx If you find errors in the present document, please send your comment to 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, includi
7、ng photocopying and microfilm except as authorized by written permission of ETSI. The content 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. ETSI 2018. All rights reserved. DECTTM, P
8、LUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks 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. GSMand the GSM logo
9、 are trademarks registered and owned by the GSM Association. ETSI ETSI TS 132 121 V15.0.0 (2018-07)23GPP TS 32.121 version 15.0.0 Release 15Intellectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
10、 pertaining to these essential IPRs, if any, is publicly available for ETSI members 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 S
11、ecretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.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 updat
12、es on the ETSI Web server) which are, or may be, or may become, essential to the present document. Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as be
13、ing the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Specifica
14、tion (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 deliverables.
15、 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 interpreted a
16、s 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 132 121 V15.0.0 (2018-07)33GPP TS 32.121 version 15.0.0 Release 15Contents Intellectual P
17、roperty Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 5g34 Requirements for AAM on Itf-N 5g34.1 Concept 5g34.2 General Requirements for AAM on Itf-N 6g3Annex A (i
18、nformative): Change history . 7g3History 8g3ETSI ETSI TS 132 121 V15.0.0 (2018-07)43GPP TS 32.121 version 15.0.0 Release 15Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work with
19、in 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: Version x.y.z where: x the first digit: 1 presented to TSG f
20、or 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 third digit is incremented when editorial only changes hav
21、e been incorporated in the document. Introduction The present document is part of a TS-family covering the 3rdGeneration Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below: 32.121: “Advanced Alarm Management Integration R
22、eference Point (IRP): Requirements“; 32.122: “Advanced Alarm Management Integration Reference Point (IRP): Information Service (IS)“; 32.126: “Advanced Alarm Management (AAM) Integration Reference Point (IRP); Solution Set (SS) definitions“. The Itf-N interface is built up by a number of IRPs and a
23、related Name Convention, which realize the functional capabilities over this interface. The basic structure of the IRPs is defined in 3GPP TS 32.150 1. IRPManagers (typically Network Management Systems) and IRPAgents (typically EMs or NEs) synchronize their data concerning alarms or configuration da
24、ta. In certain scenarios this synchronization is lost or not done. This IRP provides functionality to significantly reduce the amount of data which needs to be transferred in order to re-establish synchronization. ETSI ETSI TS 132 121 V15.0.0 (2018-07)53GPP TS 32.121 version 15.0.0 Release 151 Scope
25、 The purpose of this set of specifications is to provide a mechanism enabling the IRP Manager to improve the information content of alarms, thereby contributing to reduce the time-to-repair. For this configurable rules for advanced alarm filtering are defined to reduce the number of alarms by applyi
26、ng such advanced alarm filtering. The present document contains the Requirements of Advanced Alarm Management (AAM) on Itf-N IRP. It defines, for the purpose of AAM on Itf-N, the basic requirements to be fulfilled on Itf-N. 2 References The following documents contain provisions that, through refere
27、nce 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 reference, the latest versi
28、on 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 TS 32.150: “Telecommunication management; Integration Reference Point (IRP) Conc
29、ept and definitions“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: IRP: See 3GPP TS 32.150 1. IRPAgent: See 3GPP TS 32.150 1. IRPManager: See 3GPP TS 32.150 1. 3.2 Abbreviations For the purposes of the present do
30、cument, the following abbreviations apply: IRP Integration Reference Point IS Information Service Itf-N Interface NNE Network Element 4 Requirements for AAM on Itf-N 4.1 Concept A single network fault may generate a large number of alarms over space and time. In a large and complex network, simultan
31、eous network faults may occur, causing the network operator to be flooded with high volume of alarms. The high volume of alarms, typically the one received by an IRPManager via the getAlarmList or alarm notifications of Alarm IRP specification, greatly inhibits the operator ability to quickly identi
32、fy and locate the responsible network faults. ETSI ETSI TS 132 121 V15.0.0 (2018-07)63GPP TS 32.121 version 15.0.0 Release 15Therefore it is considered advantageous to have methods categorizing network alarms as insignificant or significant. The word insignificant does not imply “low priority“. In t
33、he context of this specification the words significant and insignificant have the following implications: - IRPAgent shall not report alarms categorized as insignificant. - IRPAgent shall report all significant alarms. Reporting only significant alarms and not reporting insignificant alarms would re
34、duce network operators time to locate network faults so that more time can be spent fixing them. When reading the alarmList it can be advantageous to partition alarms in the alarmList into sets of alarms which might be caused by the same network fault. By assigning network operators to locate networ
35、k faults based on alarms in such alarm partitions, rather than based on alarm severity, alarm type or reporting location, duplication of network operator effort (e.g. two network operators work on two different alarms and their resolutions lead to the same network faults) can be reduced or avoided 4
36、.2 General Requirements for AAM on Itf-N 4.2.1 The IRPManager should be able to request the IRPAgent to a) categorize alarms as insignificant or significant and b) to act based on these categories, e.g. to discard if insignificant. The IRPManager should be able to cancel such requests. 4.2.2 The sta
37、ndard should define some alarm categorization rules. The standard should also allow vendor to define their own alarm categorization rules. 4.2.3 Possible alarm categorization rule(s) may depend for example on the type of alarm, the environment, the time of day, the type of network element, the alarm
38、 severity, the location, position in the containment tree and many more. No restriction is imposed in this regard. 4.2.4 The IRPManager should be able to request the IRPAgent for the list of active categorization rules (i.e. standard defined and vendor defined). 4.2.5 The IRP manager should be able
39、to request the IRPAgent to apply the categorization rule(s) and to remove the insignificant alarms in the following situations: + alarm notifications to be sent to any IRPManager + advanced alarm management requests by this IRPManager to read the alarm list Certain types of categorization rules are
40、only to be applied to read the alarm list. The term used for these rules is alarm partitioning rules. ETSI ETSI TS 132 121 V15.0.0 (2018-07)73GPP TS 32.121 version 15.0.0 Release 15Annex A (informative): Change history Change history Date TSG # TSG Doc. CR R Subject/Comment Cat Old New May 2007 SA_3
41、6 SP-070294 - - Submitted to SA#36 for Information - - 1.0.0 Mar 2008 SA_39 SP-080071 - - Submitted to SA#39 for Approval - 2.0.0 8.0.0 Dec 2009 - - - - Update to Rel-9 version (MCC) - 8.0.0 9.0.0 Mar 2011 - - - - Update to Rel-10 version (MCC) - 9.0.0 10.0.0 2012-09 - - - - Update to Rel-11 version
42、 (MCC 10.0.0 11.0.0 2014-10 - - - - Update to Rel-12 version (MCC 11.0.0 12.0.0 2016-01 - - - - Update to Rel-13 version (MCC) 12.0.0 13.0.0 2017-03 SA#75 - - - Promotion to Release 14 without technical change 13.0.0 14.0.0 Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2018-06 Update to Rel-15 version (MCC) 15.0.0 ETSI ETSI TS 132 121 V15.0.0 (2018-07)83GPP TS 32.121 version 15.0.0 Release 15History Document history V15.0.0 July 2018 Publication
