1、 ETSI TS 1Digital cellular telecUniversal Mobile TeTelecommConfigurNotification Inte(3GPP TS 32.3TECHNICAL SPECIFICATION132 301 V13.0.0 (2016ecommunications system (PhasTelecommunications System (ULTE; mmunication management; uration Management (CM); ntegration Reference Point (IRPRequirements .301
2、version 13.0.0 Release 1316-02) ase 2+); (UMTS); P); 13) ETSI ETSI TS 132 301 V13.0.0 (2016-02)13GPP TS 32.301 version 13.0.0 Release 13Reference RTS/TSGS-0532301vd00 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
3、 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 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 p
4、rint. The content 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
5、 Portable Document 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:/p
6、ortal.etsi.org/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 m
7、echanical, including 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 Telecommunicat
8、ions Standards 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 GS
9、M logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 301 V13.0.0 (2016-02)23GPP TS 32.301 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 t
10、o 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. L
11、atest 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 ETS
12、I Web server) 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, UMT
13、S identities 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“,
14、 “shall not“, “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
15、direct citation. ETSI ETSI TS 132 301 V13.0.0 (2016-02)33GPP TS 32.301 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 Abbre
16、viations . 6g34 Notification management functions over Itf-N 6g34.1 Notification mechanism subscription functions . 6g34.2 Subscription control functions 6g34.3 Notification control functions. 6g34.4 Function to discover notification capabilities . 6g34.5 Generic notification header 7g3Annex A (info
17、rmative): Change history . 8g3History 9g3ETSI ETSI TS 132 301 V13.0.0 (2016-02)43GPP TS 32.301 version 13.0.0 Release 13Foreword This Technical Specification (TS) has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work wi
18、thin 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
19、 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 when editorial only changes h
20、ave 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.301: Configuration Management (CM); Notific
21、ation Integration Reference Point (IRP): Requirements 32.302: Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS) 32.306: Configuration Management (CM); Notification Integration Reference Point (IRP): Solution Set (SS) definitions The Itf-N interfa
22、ce is built up by a number of Integration Reference Points (IRPs) and a related Name Convention, which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in 3GPP TS 32.101 1 and 3GPP TS 32.102 2. Network Elements (NEs) under management and element man
23、agers generate notifications of events about occurrences within the network. Different kinds of events carry different kinds of information. For instance a new alarm as specified in Alarm IRP: Information Service 3, is one possible kind of event, an object creation as specified in Basic CM IRP: Info
24、rmation Service 4 is another possible kind of event. Information of an event is carried in notification. An IRPAgent (typically an EM or a NE) emits notifications. IRPManager (typically a network management system) receives notifications. The purpose of Notification IRP is to define an interface thr
25、ough which an IRPManager can subscribe to IRPAgent for receiving notifications. This IRP bases its design on work captured in ITU-T Recommendation X.734 5, OMG Notification Service 6. The central design ideas are: Separation of notification Consumers (IRPManagers) from Producers (IRPAgents); Notific
26、ations are sent to IRPManagers without the need for IRPManagers to periodically check for new notifications. Common characteristics related to notifications in all other IRPs are gathered in one IRP. ETSI ETSI TS 132 301 V13.0.0 (2016-02)53GPP TS 32.301 version 13.0.0 Release 131 Scope The purpose o
27、f Notification IRP is to define an interface through which an IRPManager can subscribe to an IRPAgent for receiving notifications. The present document is the “Requirements“ of Notification IRP. It defines, for the purpose of subscribing to an IRPAgent for receiving notifications, the basic requirem
28、ents that shall be fulfilled on Itf-N. How IRPManager discovers the IRPAgents address or reference (so that IRPManager can invoke an operation) is outside the scope of the present document. 2 References The following documents contain provisions which, through reference in this text, constitute prov
29、isions 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 version applies. In the case of a reference
30、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; Principles and high level requirements“. 2 3GPP TS 32.102: “Telecommunication
31、 management; Architecture“. 3 3GPP TS 32.111-2: “Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)“. 4 3GPP TS 32.602: “Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP): Inf
32、ormation Service (IS)“. 5 ITU-T Recommendation X.734: “Information technology - Open Systems Interconnection - Systems Management: Event report management function“. 6 OMG: “OMG Notification Service“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the follo
33、wing terms and definitions apply: Element Manager (EM): See 3GPP TS 32.101 1. IRPAgent: See 3GPP TS 32.102 2. IRPManager: See 3GPP TS 32.102 2. Network Manager (NM): See 3GPP TS 32.101 1. ETSI ETSI TS 132 301 V13.0.0 (2016-02)63GPP TS 32.301 version 13.0.0 Release 133.2 Abbreviations For the purpose
34、s of the present document, the following abbreviations apply: CM Configuration Management CORBA Common Object Request Broker Architecture EM Element Manager FM Fault ManagementIRP Integration Reference Point ITU-T International Telecommunication Union - Telecommunication MIB Management Information B
35、ase NE Network Element NR Network ResourceOMG Object Management Group OS Operations System TM Telecom ManagementUMTS Universal Mobile Telecommunications System 4 Notification management functions over Itf-N 4.1 Notification mechanism subscription functions The IRPAgent shall provide IRPManagers with
36、 the capabilities to subscribe and unsubscribe to the notification mechanism. An IRPManager shall be able to specify the types of notifications IRPAgent should emit to IRPManager during subscription, to specify filtering criteria that shall be applied by the notification mechanism. An IRPManager sha
37、ll be able to subscribe several times in order to include in a subscription different types of notifications. An IRPManager shall also be able to request multiple subscriptions, which is equivalent, from the IRPAgent perspective, to multiple IRPManagers each providing one subscription. 4.2 Subscript
38、ion control functions The IRPAgent may provide to IRPManagers capabilities to control its subscriptions. An IRPManager may then be able to check whether its subscription is still active or not, to know the details of a particular subscription and to know the list of all subscriptions it has opened.
39、4.3 Notification control functions In principle, notifications are forwarded to the IRPManagers as soon as they are available. The real-time forwarding of these notifications occurs via appropriate filtering mechanisms (“discriminators“ on CMIP interfaces, “subscription“ on CORBA interfaces) in acco
40、rdance with ITU-T Recommendation X.734 5 or OMG event/notification service. Any IRPManager may be able to set and change filter criteria applicable during the life-cycle of one if its subscriptions in order to ensure that only the notifications which fulfil pre-defined criteria are sent An IRPManage
41、r may also be able to enable and disable the emission of notifications corresponding to its subscriptions. 4.4 Function to discover notification capabilities The IRPAgent may provide IRPManagers with a capability to discover the IRPs supported by the IRPAgent that are capable of sending notification
42、s through the notification IRP. Those IRPs shall be identified with their version. ETSI ETSI TS 132 301 V13.0.0 (2016-02)73GPP TS 32.301 version 13.0.0 Release 134.5 Generic notification header Notifications are emitted by the notification IRP. Those notifications can be defined in any other IRP (e.
43、g. a notification for a new alarm as specified in 3GPP TS 32.111-2 3 Alarm IRP: Information Service). It is required that all notifications emitted by the notification IRP support the same header that contains enough information to identify the type of notification, the resource at the origin of the
44、 notification and the time of the notification. ETSI ETSI TS 132 301 V13.0.0 (2016-02)83GPP TS 32.301 version 13.0.0 Release 13Annex A (informative): Change history Change history Date TSG # TSG Doc. CR Rev Subject/Comment Old New Jun 2001 S_12 SP-010283 - - Approved at TSG SA #12 and placed under C
45、hange Control 2.0.0 4.0.0 Mar 2002 - - - - Cosmetics (changed styles/field codes on cover/page headings) 4.0.0 4.0.1 Mar 2002 S_15 - - - Automatic upgrade to Rel-5 (no CR) 4.0.1 5.0.0 Dec 2002 - - - - Cosmetics 5.0.0 5.0.1 Mar 2004 S_23 SP-040105 - - Automatic upgrade to Rel-6 (no CR) 5.0.1 6.0.0 Ju
46、n 2005 - - - - Introduction update : added 32.305 new TS-family member 6.0.0 6.0.1 Jun 2007 SA_36 - - - Automatic upgrade to Rel-7 (no CR) at freeze of Rel-7. Deleted reference to CMIP SS, discontinued from R7 onwards. 6.0.1 7.0.0 Dec 2008 SA_42 - - - Upgrade to Release 8 7.0.0 8.0.0 Dec 2009 - - -
47、- 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 (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 301 V13.0.0 (2016-02)93GPP TS 32.301 version 13.0.0 Release 13History Document history V13.0.0 February 2016 Publication
