1、 ETSI TS 132 301 V15.0.0 (2018-07) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Requirements (3GPP TS 32.301 version 15
2、.0.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 132 301 V15.0.0 (2018-07)13GPP TS 32.301 version 15.0.0 Release 15Reference RTS/TSGS-0532301vf00 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
3、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 conten
4、t 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 Docume
5、nt 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 https:/portal.etsi.org/
6、TB/ETSIDeliverableStatus.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 mechani
7、cal, 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. ETSI 2018. All rights reserve
8、d. DECTTM, PLUGTESTSTM, 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
9、the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TS 132 301 V15.0.0 (2018-07)23GPP TS 32.301 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
10、 information 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 fro
11、m the ETSI Secretariat. 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 (
12、or the updates 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 ind
13、icated as being 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 Technic
14、al 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 identities. These should be interpreted as being references to the corresponding ETSI d
15、eliverables. 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 i
16、nterpreted 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 TS 132 301 V15.0.0 (2018-07)33GPP TS 32.301 version 15.0.0 Release 15Contents In
17、tellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 5g34 Notification management functions over Itf-N 6g34.1 Notification mechanism subscription fun
18、ctions . 6g34.2 Subscription control functions 6g34.3 Notification control functions. 6g34.4 Function to discover notification capabilities . 6g34.5 Generic notification header 6g3Annex A (informative): Change history . 7g3History 8g3ETSI ETSI TS 132 301 V15.0.0 (2018-07)43GPP TS 32.301 version 15.0
19、.0 Release 15Foreword This Technical Specification (TS) has been produced by 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 modify the contents of the presen
20、t 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 TSG approved document under chang
21、e 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 is part of a TS-family covering th
22、e 3rdGeneration Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below: 32.301: Configuration Management (CM); Notification Integration Reference Point (IRP): Requirements. 32.302: Configuration Management (CM); Notification
23、Integration Reference Point (IRP): Information Service (IS). 32.306: Configuration Management (CM); Notification Integration Reference Point (IRP): Solution Set (SS) definitions. The Itf-N interface is built up by a number of Integration Reference Points (IRPs) and a related Name Convention, which r
24、ealise 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 managers generate notifications of events about occurrences within the network. Different kinds of events c
25、arry 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: Information Service 4 is another possible kind of event. Information of an event is carried in notification.
26、 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 through which an IRPManager can subscribe to IRPAgent for receiving notifications. This IRP bases its desig
27、n 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); - Notifications are sent to IRPManagers without the need for IRPManagers to periodically check for new notifi
28、cations. Common characteristics related to notifications in all other IRPs are gathered in one IRP. ETSI ETSI TS 132 301 V15.0.0 (2018-07)53GPP TS 32.301 version 15.0.0 Release 151 Scope The purpose of Notification IRP is to define an interface through which an IRPManager can subscribe to an IRPAgen
29、t 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 requirements that shall be fulfilled on Itf-N. How IRPManager discovers the IRPAgents address or reference (
30、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 provisions of the present document. - References are either specific (identified by date of publication,
31、 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 to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to t
32、he 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 management; Architecture“. 3 3GPP TS 32.111-2: “Telecommunication management; Fault Managemen
33、t; 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): Information Service (IS)“. 5 ITU-T Recommendation X.734: “Information technology - Open Systems I
34、nterconnection - 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 following terms and definitions apply: Element Manager (EM): See 3GPP TS 32.101 1. IRPAgent: See 3G
35、PP TS 32.102 2. IRPManager: See 3GPP TS 32.102 2. Network Manager (NM): See 3GPP TS 32.101 1. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CM Configuration Management CORBA Common Object Request Broker Architecture EM Element Manager FM Fault Managem
36、entIRP Integration Reference Point ITU-T International Telecommunication Union - Telecommunication ETSI ETSI TS 132 301 V15.0.0 (2018-07)63GPP TS 32.301 version 15.0.0 Release 15MIB Management Information Base NE Network Element NR Network ResourceOMG Object Management Group OS Operations System TM
37、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 the capabilities to subscribe and unsubscribe to the notification mechanism. An IRPManager sh
38、all 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 shall be able to subscribe several times in order to include in a subscription different types of
39、 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 Subscription control functions The IRPAgent may provide to IRPManagers capabilities to control its subs
40、criptions. 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. 4.3 Notification control functions In principle, notifications are forwarded to the IRPManager
41、s 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 accordance with ITU-T Recommendation X.734 5 or OMG event/notification service. Any IRPManager may
42、 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 IRPManager may also be able to enable and disable the emission of notifications corresponding to its su
43、bscriptions. 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 notifications through the notification IRP. Those IRPs shall be identified with their version. 4.5 Generic
44、 notification header Notifications are emitted by the notification IRP. Those notifications can be defined in any other IRP (e.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 s
45、upport the same header that contains enough information to identify the type of notification, the resource at the origin of the notification and the time of the notification. ETSI ETSI TS 132 301 V15.0.0 (2018-07)73GPP TS 32.301 version 15.0.0 Release 15Annex A (informative): Change history Change h
46、istory Date TSG # TSG Doc. CR Rev Subject/Comment Old New Jun 2001 S_12 SP-010283 - - Approved at TSG SA #12 and placed under Change 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
47、.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 Jun 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 refere
48、nce 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 - - - - 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
49、 - - - - 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 - - - - Update to Rel-14 version (MCC) 13.0.0 14.0.0 2018-06 - - - - Update to Rel-15 version (MCC) 14.0.0 15.0.0 ETSI ETSI TS 132 301 V15.0.0 (2018-07)83GPP TS 32.301 version 15.0.0 Release 15History Document history V15.0.0 July 2018 Publication
