ETSI TS 132 302-2016 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Configuration Manageme.pdf

1、 ETSI TS 1Digital cellular telecUniversal Mobile TeTelecommConfigurNotification InteInfor(3GPP TS 32.3TECHNICAL SPECIFICATION132 302 V13.0.0 (2016ecommunications system (PhasTelecommunications System (ULTE; mmunication management; uration Management (CM); ntegration Reference Point (IRPformation Ser

2、vice (IS) .302 version 13.0.0 Release 1316-02) ase 2+); (UMTS); P); 13) ETSI ETSI TS 132 302 V13.0.0 (2016-02)13GPP TS 32.302 version 13.0.0 Release 13Reference RTS/TSGS-0532302vd00 Keywords GSM,LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax:

3、 +33 4 93 65 47 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 versi

4、ons and/or in print. 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 t

5、he print of the 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 avail

6、able at http:/portal.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,

7、electronic or mechanical, 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

8、 Telecommunications 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.

9、 GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 302 V13.0.0 (2016-02)23GPP TS 32.302 version 13.0.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The informati

10、on 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 from the ETSI

11、 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 (or the upd

12、ates on the ETSI 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

13、identities, UMTS 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 do

14、cument “shall“, “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 excep

15、t when used in direct citation. ETSI ETSI TS 132 302 V13.0.0 (2016-02)33GPP TS 32.302 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 7g32 References 7g33 Definitions and abbreviations . 8g33.1 Definitio

16、ns 8g33.2 Abbreviations . 8g34 System overview 9g34.1 System Context 9g35 Information Object Classes 10g35.1 Imported information entities and local labels . 10g35.2 Class Diagram 10g35.2.1 Attributes and relationships 10g35.2.2 Inheritance 10g35.3 Information object classes definition 11g35.3.1 Ntf

17、Subscriber 11g35.3.1.1 Definition 11g35.3.1.2 Attributes . 11g35.3.2 NtfSubscription . 11g35.3.2.1 Definition 11g35.3.2.2 Attributes . 11g35.3.2.3 State diagram. 12g35.3.3 NotificationIRP . 12g35.3.3.1 Definition 12g35.4 Information relationship definitions . 13g35.4.1 relation-ntfSubscriber-ntfSubs

18、cription (M) 13g35.4.1.1 Definition 13g35.4.1.2 Roles . 13g35.4.1.3 Constraints 13g35.4.2 relation-ntfIRP-ntfSubscriber (M) 13g35.4.2.1 Definition 13g35.4.2.2 Roles . 13g35.4.2.3 Constraints 13g35.5 Information attribute definitions . 14g35.5.1 Definitions and legal values 14g35.5.2 Constraints 14g3

19、6 Interface Definition 15g36.1 Class diagram representing interfaces 15g36.2 Generic rules 15g36.3 notificationIRPManagement Interface (M) 16g36.3.1 Operation subscribe (M) . 16g36.3.1.1 Definition 16g36.3.1.2 Input parameters 16g36.3.1.3 Output parameters . 16g36.3.1.4 Pre-condition . 16g36.3.1.5 P

20、ost-condition . 17g36.3.1.6 Exceptions . 17g36.3.2 Operation unsubscribe (M). 17g3ETSI ETSI TS 132 302 V13.0.0 (2016-02)43GPP TS 32.302 version 13.0.0 Release 136.3.2.1 Definition 17g36.3.2.2 Input parameters 17g36.3.2.3 Output parameters . 18g36.3.2.4 Pre-condition . 18g36.3.2.5 Post-condition . 18

21、g36.3.2.6 Exceptions . 18g36.4 subscriberManagement Interface (O) . 18g36.4.1 Operation getSubscriptionIds (M) 18g36.4.1.1 Definition 18g36.4.1.2 Input parameters 18g36.4.1.3 Output parameters . 19g36.4.1.4 Pre-condition . 19g36.4.1.5 Post-condition . 19g36.4.1.6 Exceptions . 19g36.5 subscriptionSta

22、tusOperations Interface (O) 19g36.5.1 Operation getSubscriptionStatus (M) . 19g36.5.1.1 Definition 19g36.5.1.2 Input parameters 19g36.5.1.3 Output parameters . 20g36.5.1.4 Pre-condition . 20g36.5.1.5 Post-condition . 20g36.5.1.6 Exceptions . 20g36.6 subscriptionFilterOperations Interface (O) . 20g36

23、.6.1 Operation changeSubscriptionFilter (M) 20g36.6.1.1 Definition 20g36.6.1.2 Input parameters 20g36.6.1.3 Output parameters . 21g36.6.1.4 Pre-condition . 21g36.6.1.5 Post-condition . 21g36.6.1.6 Exceptions . 21g36.7 subscriptionSuspendOperations Interface (O) 21g36.7.1 Operation suspendSubscriptio

24、n (M) . 21g36.7.1.1 Definition 21g36.7.1.2 Input parameters 21g36.7.1.3 Output parameters . 21g36.7.1.4 Pre-condition . 22g36.7.1.5 Post-condition . 22g36.7.1.6 Exceptions . 22g36.7.2 Operation resumeSubscription (M) . 22g36.7.2.1 Definition 22g36.7.2.2 Input parameters 22g36.7.2.3 Output parameters

25、 . 22g36.7.2.4 Pre-condition . 22g36.7.2.5 Post-condition . 23g36.7.2.6 Exceptions . 23g36.8 IRPManagementOperations Interface (O) 24g36.8.1 Operation getNotificationCategories (M) 24g36.8.1.1 Definition 24g36.8.1.2 Input parameters 24g36.8.1.3 Output parameters . 24g36.8.1.4 Pre-condition . 24g36.8

26、.1.5 Post-condition . 24g36.8.1.6 Exceptions . 24g36.9 NotificationIRPNotification Interface 25g3Annex A (informative): Change history . 27g3History 28g3ETSI ETSI TS 132 302 V13.0.0 (2016-02)53GPP TS 32.302 version 13.0.0 Release 13Foreword This Technical Specification (TS) has been produced by the

27、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 present document, it will be re-released by the TSG with an identifying change of relea

28、se 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 change control. y the second digit is incremented for all changes of substance, i.e. t

29、echnical 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 S

30、ystem Aspects; Telecommunication management; as identified below: 32.301: Configuration Management (CM); Notification Integration Reference Point (IRP): Requirements 32.302: Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS) 32.303: Configuration

31、Management (CM); Notification Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) 32.305: Configuration Management (CM); Notification Integration Reference Point (IRP): eXtensible Markup Language (XML) definition 32.307: Configuration Management (CM

32、); Notification Integration Reference Point (IRP): Simple Object Access Protocol (SOAP) Solution Set (SS) The Itf-N interface 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 structu

33、re of the IRPs is defined in 3GPP TS 32.101 5 and 3GPP TS 32.102 6. Network Elements (NEs) under management and element managers generate notifications of events about occurrences within the network. Different kinds of events carry different kinds of information. For instance a new alarm as specifie

34、d in Alarm IRP: Information Service 1, is one possible kind of event, an object creation as specified in Basic CM IRP: Information Service 8 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 (t

35、ypically 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 design on work captured in ITU-T Recommendation X.734 2, OMG Notification Serv

36、ice 4. The central design ideas are: Separation of notification Consumers (IRPManagers) from Producers (IRPAgents); ETSI ETSI TS 132 302 V13.0.0 (2016-02)63GPP TS 32.302 version 13.0.0 Release 13 Notifications are sent to IRPManagers without the need for IRPManagers to periodically check for new not

37、ifications. Common characteristics related to notifications in all other IRPs are gathered in one IRP. ETSI ETSI TS 132 302 V13.0.0 (2016-02)73GPP TS 32.302 version 13.0.0 Release 131 Scope The purpose of Notification IRP is to define an interface through which an IRPManager can subscribe to an IRPA

38、gent for receiving notifications. The present document is the “Information Service“ of Notification IRP. It defines, for the purpose of subscribing to an IRPAgent for receiving notifications, the information observable and controlled by management systems client and it also specifies the semantics o

39、f the interactions used to carry this information. It also defines the information common to all notifications which is called the notificationHeader. An IRPAgent supporting this IRP IS may emit one or multiple categories of notifications, such as alarms (as specified in Alarm IRP: Information Servi

40、ce 1) and others. This IRP IS defines a mechanism that IRPManager can use to determine the categories of notifications supported by an IRPAgent. It also defines a mechanism (subscribe and unsubscribe operations) that IRPManager can use to specify the categories of notifications IRPAgent should emit

41、to IRPManager during subscription. It also defines a mechanism (getSubscriptionIds operation) that IRPManager can use to check which categories of notifications it has subscribed to. IRPManager can set and change filter criteria applicable during the life-cycle of a subscription. IRPManager can also

42、 exercise flow-control on IRPAgents emission of notifications (suspendSubscription and resumeSubscription operations). Using different managerReference, an IRPManager can subscribe several times. It will result in multiple subscriptions. As far as IRPAgent is concerned, notifications are sent to mul

43、tiple “places“. Using the same managerReference, an IRPManager can subscribe several times specifying different categories of notifications. This IRP IS does not specify information that is carried in some but not all notifications. That kind of information is specified in other IRP ISs involved. Fo

44、r example, perceivedSeverity is a piece of information specific for notifications carrying alarm information. This information is not defined in the present document but in Alarm IRP: Information Service 1. How IRPManager discovers the IRPAgents address or reference (so that IRPManager can invoke an

45、 operation) is outside the scope of the present document. This IRP IS is aligned with ITU-T M.3702 13 in terms of the definitions of operations for Notification management. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the pre

46、sent 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 to a 3GPP documen

47、t (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.111-2: “Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)“

48、. 2 ITU-T Recommendation X.734 (1992): “Information technology - Open Systems Interconnection - Systems management: Event report management function“. 3 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“. 4 OMG: “OMG Notification Servic

49、e“. http:/www.omg.org/technology/documents/ 5 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. ETSI ETSI TS 132 302 V13.0.0 (2016-02)83GPP TS 32.302 version 13.0.0 Release 136 3GPP TS 32.102: “Telecommunication management; Architecture“. 7 3GPP TS 32.301: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Requirements“. 8 3GPP TS 32.602: “Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Poin