1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelTelecommAdvanced AIntegration Refer(3GPP TS 32.1TECHNICAL SPECIFICATION132 121 V13.0.0 (2016communications system (Phaelecommunications System (LTE; munication management; d Alarm Management (AAM) erence Point (IRP): Requireme.121 version 13.0.0 R
2、elease 1316-02) hase 2+); (UMTS); ments 13) ETSI ETSI TS 132 121 V13.0.0 (2016-02)13GPP TS 32.121 version 13.0.0 Release 13Reference RTS/TSGS-0532121vd00 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 3
3、48 623 562 00017 - 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 con
4、tent of any electronic 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 Doc
5、ument Format (PDF) 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 http:/portal.etsi.or
6、g/tb/status/status.asp 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, in
7、cluding 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. European Telecommunications Standard
8、s Institute 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade 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 Tr
9、ade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 121 V13.0.0 (2016-02)23GPP TS 32.121 version 13.0.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essen
10、tial 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 Secretariat. Latest updates
11、 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 updates on the ETSI Web server)
12、 which are, or may be, or may become, essential to 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
13、or GSM identities. These should be interpreted as being 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“,
14、 “should“, “should not“, “may“, “need not“, “will“, “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 citati
15、on. ETSI ETSI TS 132 121 V13.0.0 (2016-02)33GPP TS 32.121 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 5g
16、34 Requirements for AAM on Itf-N 5g34.1 Concept 5g34.2 General Requirements for AAM on Itf-N 6g3Annex A (informative): Change history . 7g3History 8g3ETSI ETSI TS 132 121 V13.0.0 (2016-02)43GPP TS 32.121 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rdGener
17、ation 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 contents of the present document, it will be re-released by the TSG with an identifying change of release date
18、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 document under change control. y the second digit is incremented for all changes of substance, i.e. technical
19、 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-family covering the 3rdGeneration Partnership Project; Technical Specification Group Services and System As
20、pects; Telecommunication management; as identified below: 32.121: “Advanced Alarm Management Integration Reference Point (IRP): Requirements“; 32.122: “Advanced Alarm Management Integration Reference Point (IRP): Information Service (IS)“; 32.126: “Advanced Alarm Management (AAM) Integration Referen
21、ce Point (IRP); Solution Set (SS) definitions“. The Itf-N interface is built up by a number of IRPs and a 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
22、Systems) and IRPAgents (typically EMs or NEs) synchronize their data concerning alarms or configuration data. 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-establi
23、sh synchronization. ETSI ETSI TS 132 121 V13.0.0 (2016-02)53GPP TS 32.121 version 13.0.0 Release 131 Scope 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
24、 this configurable rules for advanced alarm filtering are defined to reduce the number of alarms by applying 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 requireme
25、nts to be fulfilled on Itf-N. 2 References The following documents contain provisions that, 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 s
26、pecific 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 Release as the prese
27、nt document. 1 3GPP TS 32.150: “Telecommunication management; Integration Reference Point (IRP) Concept 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
28、 TS 32.150 1. IRPManager: See 3GPP TS 32.150 1. 3.2 Abbreviations For the purposes of the present document, 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
29、 may generate a large number of alarms over space and time. In a large and complex network, simultaneous network faults may occur, causing the network operator to be flooded with high volume of alarms. ETSI ETSI TS 132 121 V13.0.0 (2016-02)63GPP TS 32.121 version 13.0.0 Release 13The high volume of
30、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 identify and locate the responsible network faults. Therefore it is considered advantageous to have methods categorizing networ
31、k alarms as insignificant or significant. The word insignificant does not imply “low priority“. In the context of this specification the words significant and insignificant have the following implications: square4 IRPAgent shall not report alarms categorized as insignificant. square4 IRPAgent shall
32、report all significant alarms. Reporting only significant alarms and not reporting insignificant alarms would reduce 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
33、 sets of alarms which might be caused by the same network fault. By assigning network operators to locate network 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
34、 work on two different alarms and their resolutions lead to the same network faults) can be reduced or avoided 4.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 ca
35、tegories, e.g. to discard if insignificant. The IRPManager should be able to cancel such requests. 4.2.2 The standard 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 d
36、epend for example on the type of alarm, the environment, the time of day, the type of network element, the alarm 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
37、of active categorization rules (i.e. standard defined and vendor defined). 4.2.5 The IRP manager should be able 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 + advance
38、d alarm management requests by this IRPManager to read the alarm list Certain types of categorization rules are only to be applied to read the alarm list. The term used for these rules is alarm partitioning rules. ETSI ETSI TS 132 121 V13.0.0 (2016-02)73GPP TS 32.121 version 13.0.0 Release 13Annex A
39、 (informative): Change history Change history Date TSG # TSG Doc. CR R Subject/Comment Cat Old New May 2007 SA_36 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
40、.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 (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 ETSI ETSI TS 132 121 V13.0.0 (2016-02)83GPP TS 32.121 version 13.0.0 Release 13History Document history V13.0.0 February 2016 Publication
