1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelTelecommNotification Log (NL(3GPP TS 32.3TECHNICAL SPECIFICATION132 331 V13.0.0 (2016communications system (Phaelecommunications System (LTE; munication management; L) Integration Reference PoinRequirements .331 version 13.0.0 Release 1316-02) has
2、e 2+); (UMTS); int (IRP); 13) ETSI ETSI TS 132 331 V13.0.0 (2016-02)13GPP TS 32.331 version 13.0.0 Release 13Reference RTS/TSGS-0532331vd00 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 000
3、17 - 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 el
4、ectronic 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 (
5、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.org/tb/status/st
6、atus.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, including photoc
7、opying 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 Standards Institute 20
8、16. 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 Trade Marks regi
9、stered and owned by the GSM Association. ETSI ETSI TS 132 331 V13.0.0 (2016-02)23GPP TS 32.331 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 essential IPRs, if
10、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 are available
11、 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) which are, or
12、 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 or GSM identit
13、ies. 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“, “should“, “sh
14、ould 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 citation. ETSI ETSI
15、TS 132 331 V13.0.0 (2016-02)33GPP TS 32.331 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 . 6g34 Notificatio
16、n log Management concept . 6g34.1 Notification Log Management . 6g34.2 Detection of the Notification Log state 7g34.3 Notification Log / Notification Log Record Retrieval . 7g34.4 Notification Log Full Action 7g35 Notification log IRP requirements . 8g35.1 Management of Logging/Log Records . 8g35.2
17、Information contained in Notification Log / Notification Log Records . 8g35.3 Notifications emitted by Notification Log IRP 8g35.4 Retrieval of Notification Log Records . 8g35.5 Exporting Notification Log Records 9g35.6 Overview of IRPs related to Notification Log IRP 9g3Annex A (informative): Bibli
18、ography . 10g3Annex B (informative): Change history . 11g3History 12g3ETSI ETSI TS 132 331 V13.0.0 (2016-02)43GPP TS 32.331 version 13.0.0 Release 13Foreword This Technical Specification (TS) has been produced for the 3rdGeneration Partnership Project (3GPP). The contents of the present document are
19、 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: Version x.y.z where: x the f
20、irst 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 third digit is incremented
21、 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 Aspects; Telecommunication management; as identified below: TS 32.331 “Notif
22、ication Log (NL) Integration Reference Point (IRP); Requirements“ TS 32.332 “Notification Log (NL) (NL) Integration Reference Point (IRP); Information Service (IS)“ TS 32.336 “Notification Log (NL) Integration Reference Point (IRP): Solution Sets (SS)“. The present document describes the requirement
23、s and information model necessary for Telecommunications Management (TM). The TM principles and TM architecture are specified in 3GPP TS 32.101 1 and 3GPP TS 32.102 2 respectively. A communications system is composed of a multitude of Network Elements (NE) of various types and, typically, different
24、vendors, which inter-operate in a co-ordinated manner in order to satisfy the network users“ communication requirements. The occurrence of faults in an NE may cause deterioration or loss of this NE“s function. Fault Management is the functional area, which allows the operator to detect the occurrenc
25、e of faults in the network in real-time. Configuration Management and Performance Management are two more functional areas, which require the operator to be alerted to certain conditions in the network. A standard general-purpose mechanism for the management of Notification Logs containing selected
26、or all notifications from the network is required to provide an ability to perform historical analysis on faults and conditions, which occurred in the network. The TS 32.33x-series constituting the Notification Log IRP, sets forth such a mechanism - and the present document contains the concept and
27、IRP requirements definition. ETSI ETSI TS 132 331 V13.0.0 (2016-02)53GPP TS 32.331 version 13.0.0 Release 131 Scope The present document specifies overall requirements for Notification Log Management over Itf-N. Clause 4 provides the Notification Log Management concept for the manipulation of Notifi
28、cation Logs and the retrieval of notifications selected for logging. Clause 5 of the present document defines the functional requirements for the Notification Log IRP, for the purpose of Notification Log Management, as seen from a Network Manager (NM) though Itf-N. The Itf-N is fully standardized so
29、 as to connect systems of any vendor to an NM via this interface. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication, edition number, version n
30、umber, 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 non-specific reference implicitly refers to the latest version of that docu
31、ment in the same Release as the present document. 1 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.302: “Telecommunication management; Configuration Management (CM); Notification Int
32、egration Reference Point (IRP): Information Service (IS)“. 4 3GPP TS 32.662: “Telecommunication management; Configuration Management (CM); Kernel CM Information Service (IS)“. 5 3GPP TS 32.111-1: Telecommunication management; Fault Management; Part 1: 3G fault management requirements“. 6 3GPP TS 32.
33、111-2: “Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)“. 7 3GPP TS 32.342: “Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Information Service (IS)“. 8 ITU-T Recommendation X.735: “Informa
34、tion technology - Open Systems Interconnection - Systems Management: Log control function“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: Alarm: defined in 3GPP TS 32.111-1 5. Alarm Notification: defined in 3GPP T
35、S 32.111-1 5. Event: defined in 3GPP TS 32.111-1 5. ETSI ETSI TS 132 331 V13.0.0 (2016-02)63GPP TS 32.331 version 13.0.0 Release 13Fault: defined in 3GPP TS 32.111-1 5. Notification: defined in 3GPP TS 32.111-1 5. Notification Log: managed resource in which the notifications are stored Notifications
36、 logs contain Notification Log Records. Notification Log may represent a physical or a logical/virtual storage, and which is not apparent to an IRPManager. Notification Log Record: records track information about when a particular notification was entered into the Notification Log and the details of
37、 the notification Each Notification Log Record is associated with one notification, where a notification may be an alarm or an event. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: COTS Commercial Off The Shelf EM Element Manager IRP Integration Refere
38、nce Point LM Log Management NE Network ElementNM Network Manager OS Operations System4 Notification log Management concept A general-purpose Notification Logging mechanism is required to hold notifications related to different functional areas in the network. Any Notification Log must, at any one po
39、int in time, be capable of holding fault management alarms, configuration management events, performance management events, and event log management events. A log is capable of capturing all semantics carried in a notification. Only those requirements covered by clause 5 and as applicable to the Not
40、ification Log IRP IS shall be considered as valid requirements for compliance to the standard defined by the present document. 4.1 Notification Log Management Notification logs are resources in a communications network. An operator needs to be able to create Notification Logs, delete Notification Lo
41、gs, query Notification Logs and to delete records. To allow an operator to do this a Notification Log management framework needs to be in place. The following aspects for Notification Log Management are derived from ITU-T Recommendation X.735 8: a) The definition of a flexible Notification Log contr
42、ol service, which will allow selection of Notification Log records that are to be logged by a management system (NMs or EMs) in a Notification Log or a particular Notification Log. b) The ability for a client system to modify the criteria used in logging notification records. c) The ability for a cl
43、ient system to determine whether the logging characteristics were modified or whether notifications log records has been lost. d) Specification of a mechanism to enable Notification Logging to be suspended and subsequently to be resumed. e) The ability for a client system to retrieve and delete Noti
44、fication Log records. f) The ability for a client system to create and delete those Notification Logs. g) The ability to log partial notifications. ETSI ETSI TS 132 331 V13.0.0 (2016-02)73GPP TS 32.331 version 13.0.0 Release 13Another aspect is listed below: - Ability to export a log to an industry
45、standard format such as XML. Such an export facility would allow the analysis and reporting of logs to be carried out by COTS tools. 4.2 Detection of the Notification Log state The Notification Log management system must notify all interested OS about its current state. An event-based approach is us
46、ed to update OSs on the current state of the Notification Log. To facilitate the notification of attribute or state changes, a Notification Log has the capability to generate such events, which all OSs may subscribe to via the Notification IRP 3GPP TS 32.302 3. The Notification Log management system
47、 may also emit Notification Log creation and log deletion notifications to signal the creation or deletion of a particular log. Again all interested OSs may subscribe via 3GPP TS 32.302 3 to receive such notifications. To notify OSs about the loss or imminent loss of Notification Log records, the sy
48、stem is able to emit capacity threshold alarms that alert the subscribed OSs that a capacity threshold has been crossed in a particular Notification Log. This threshold value may indicate that the Notification Log is full and incoming notifications shall be dealt with in a predetermined manner set b
49、y an operator. The system may emit other events to notify an OS of the completion of an I/O intensive operation, such as deletion of Notification Log records, or the exporting of a Notification Log. 4.3 Notification Log / Notification Log Record Retrieval An OS may retrieve Notification Log records either by querying a particular Notification Log with a filter, or by exporting a Notification Log, or a particular section of a Notification LogNotification Log. Exporting a Notification Log utilizing the File Transfer IRP (3GPP TS 32.342
