ETSI TS 132 331-2018 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Notification Log.pdf

1、 ETSI TS 132 331 V15.0.0 (2018-07) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Notification Log (NL) Integration Reference Point (IRP); Requirements (3GPP TS 32.331 version 15.0.0 Release 15) TECHN

2、ICAL SPECIFICATION ETSI ETSI TS 132 331 V15.0.0 (2018-07)13GPP TS 32.331 version 15.0.0 Release 15Reference RTS/TSGS-0532331vf00 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 00017 - NAF 74

3、2 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 electronic an

4、d/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 (PDF) versio

5、n 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/ETSIDeliverableStat

6、us.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, including photoco

7、pying 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, PLUGTESTSTM

8、, 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 are trade

9、marks registered and owned by the GSM Association. ETSI ETSI TS 132 331 V15.0.0 (2018-07)23GPP TS 32.331 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 pertainin

10、g 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 Secretariat

11、. 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 updates on the

12、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 being the pr

13、operty 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 Specification (TS)

14、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. The cross

15、 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 as describe

16、d 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 331 V15.0.0 (2018-07)33GPP TS 32.331 version 15.0.0 Release 15Contents Intellectual Property Ri

17、ghts 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 Notification log Management concept . 6g34.1 Notification Log Management . 6g34.2 Detection of the Notification L

18、og state 7g34.3 Notification Log / Notification Log Record Retrieval . 7g34.4 Notification Log Full Action 7g35 Notification log IRP requirements . 7g35.1 Management of Logging/Log Records . 7g35.2 Information contained in Notification Log / Notification Log Records . 8g35.3 Notifications emitted by

19、 Notification Log IRP 8g35.4 Retrieval of Notification Log Records . 8g35.5 Exporting Notification Log Records 8g35.6 Overview of IRPs related to Notification Log IRP 8g3Annex A (informative): Bibliography . 9g3Annex B (informative): Change history . 10g3History 11g3ETSI ETSI TS 132 331 V15.0.0 (201

20、8-07)43GPP TS 32.331 version 15.0.0 Release 15Foreword This Technical Specification (TS) has been produced for 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

21、 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 for information; 2 presented to TSG for approval; 3 or greater indicates

22、 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 have been incorporated in the document. Introduction The present document

23、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 “Notification Log (NL) Integration Reference Point (IRP); Requirements“. TS 32.332 “Notification Log (NL) (NL

24、) 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 requirements and information model necessary for Telecommunications Management (TM). The TM principles and TM ar

25、chitecture 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 vendors, which inter-operate in a co-ordinated manner in order to satisfy the network users communica

26、tion requirements. The occurrence of faults in an NE may cause deterioration or loss of this NEs function. Fault Management is the functional area, which allows the operator to detect the occurrence of faults in the network in real-time. Configuration Management and Performance Management are two mo

27、re 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 or all notifications from the network is required to provide an ability to perform historical analysis

28、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 IRP requirements definition. ETSI ETSI TS 132 331 V15.0.0 (2018-07)53GPP TS 32.331 version 15.0.0 Relea

29、se 151 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 Notification Logs and the retrieval of notifications selected for logging. Clause 5 of the present document d

30、efines 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 as to connect systems of any vendor to an NM via this interface. 2 References The following documents

31、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 number, etc.) or non-specific. - For a specific reference, subsequent revisions do not apply. - For a

32、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 present document. 1 3GPP TS 32.101: “Telecommunication management

33、; Principles and high level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.302: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)“. 4 3GPP TS 32.662: “Telecommunication m

34、anagement; 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.111-2: “Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point

35、 (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: “Information technology - Open Systems Interconnection - Systems Management: Log control function“. 3 Def

36、initions 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 TS 32.111-1 5. Event: defined in 3GPP TS 32.111-1 5. Fault: defined in 3GPP TS 32.111-1 5. Notific

37、ation: defined in 3GPP TS 32.111-1 5. ETSI ETSI TS 132 331 V15.0.0 (2018-07)63GPP TS 32.331 version 15.0.0 Release 15Notification Log: managed resource in which the notifications are stored Notifications logs contain Notification Log Records. Notification Log may represent a physical or a logical/vi

38、rtual 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 the notification Each Notification Log Record is associated with one notification, where a notif

39、ication 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 Reference Point LM Log Management NE Network ElementNM Network Manager OS Operations System4 Notificati

40、on 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 point in time, be capable of holding fault management alarms, configuration management events, perf

41、ormance 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 Notification Log IRP IS shall be considered as valid requirements for compliance to the standard def

42、ined 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 Logs, query Notification Logs and to delete records. To allow an operator to do this a Notification

43、 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 control service, which will allow selection of Notification Log records that are to be logged by a man

44、agement 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 client system to determine whether the logging characteristics were modified or whether notificatio

45、ns 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 Notification Log records. f) The ability for a client system to create and delete those Notification

46、Logs. g) The ability to log partial notifications. Another aspect is listed below: - Ability to export a log to an industry standard format such as XML. Such an export facility would allow the analysis and reporting of logs to be carried out by COTS tools. ETSI ETSI TS 132 331 V15.0.0 (2018-07)73GPP

47、 TS 32.331 version 15.0.0 Release 154.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 used to update OSs on the current state of the Notification Log. To facilitate the notification of

48、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 may also emit Notification Log creation and log deletion notifications to signal the creation or

49、 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 system 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 by an operator. The system may emit other e