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

1、 ETSI TS 132 302 V14.0.0 (2017-04) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Information Service (IS) (3GPP TS 32.30

2、2 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 132 302 V14.0.0 (2017-04)13GPP TS 32.302 version 14.0.0 Release 14Reference RTS/TSGS-0532302ve00 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

3、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 print

4、. 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 Por

5、table 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 https:/port

6、al.etsi.org/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, electroni

7、c 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 Telecomm

8、unications Standards Institute 2017. 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. oneM2M l

9、ogo is protected for the benefit of its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 302 V14.0.0 (2017-04)23GPP TS 32.302 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present documen

10、t may have been declared to ETSI. The 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 ET

11、SI standards“, which is available from 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 IPR

12、s not referenced in ETSI SR 000 314 (or the updates 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 techni

13、cal 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 reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform

14、.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 described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must

15、not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 132 302 V14.0.0 (2017-04)33GPP TS 32.302 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 7g32 References 7g33 D

16、efinitions and abbreviations . 8g33.1 Definitions 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 Info

17、rmation object classes definition 11g35.3.1 NtfSubscriber 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 definit

18、ions . 13g35.4.1 relation-ntfSubscriber-ntfSubscription (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 Definiti

19、ons and legal values 14g35.5.2 Constraints 14g36 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 paramet

20、ers . 16g36.3.1.4 Pre-condition . 16g36.3.1.5 Post-condition . 17g36.3.1.6 Exceptions . 17g36.3.2 Operation unsubscribe (M). 17g36.3.2.1 Definition 17g3ETSI ETSI TS 132 302 V14.0.0 (2017-04)43GPP TS 32.302 version 14.0.0 Release 146.3.2.2 Input parameters 17g36.3.2.3 Output parameters . 17g36.3.2.4

21、Pre-condition . 18g36.3.2.5 Post-condition . 18g36.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 . 1

22、9g36.4.1.6 Exceptions . 19g36.5 subscriptionStatusOperations 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 sub

23、scriptionFilterOperations Interface (O) . 20g36.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 Inter

24、face (O) 21g36.7.1 Operation suspendSubscription (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

25、 Input parameters 22g36.7.2.3 Output parameters . 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 p

26、arameters . 24g36.8.1.4 Pre-condition . 24g36.8.1.5 Post-condition . 24g36.8.1.6 Exceptions . 24g36.9 NotificationIRPNotification Interface 25g3Annex A (informative): Change history . 27g3History 28g3ETSI ETSI TS 132 302 V14.0.0 (2017-04)53GPP TS 32.302 version 14.0.0 Release 14Foreword This Technic

27、al 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 present document, it will be re-released

28、 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 change control. y the second digit is i

29、ncremented 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 the 3rdGeneration Partnership Projec

30、t; 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 Integration Reference Point (IRP):

31、Information Service (IS) 32.303: Configuration 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)

32、definition 32.307: Configuration Management (CM); 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 capa

33、bilities over this interface. The basic structure 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 in

34、formation. For instance a new alarm as specified 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

35、 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 design on work captured in ITU-

36、T Recommendation X.734 2, OMG Notification Service 4. The central design ideas are: - Separation of notification Consumers (IRPManagers) from Producers (IRPAgents); ETSI ETSI TS 132 302 V14.0.0 (2017-04)63GPP TS 32.302 version 14.0.0 Release 14- Notifications are sent to IRPManagers without the need

37、 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 302 V14.0.0 (2017-04)73GPP TS 32.302 version 14.0.0 Release 141 Scope The purpose of Notification IRP is to define an interface th

38、rough which an IRPManager can subscribe to an IRPAgent 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 sy

39、stems client and it also specifies the semantics of 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 al

40、arms (as specified in Alarm IRP: Information Service 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

41、 categories of notifications IRPAgent should emit 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

42、 life-cycle of a subscription. IRPManager can also 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 IR

43、PAgent is concerned, notifications are sent to multiple “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 info

44、rmation is specified in other IRP ISs involved. For 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 addr

45、ess or reference (so that IRPManager can invoke an 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 refere

46、nce 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 non-specific reference, the latest versi

47、on 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.111-2: “Telecommunication management; Fault Management; Part 2: Alarm Inte

48、gration Reference Point (IRP): Information Service (IS)“. 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 conventi

49、on for Managed Objects“. 4 OMG: “OMG Notification Service“. http:/www.omg.org/technology/documents/ 5 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. ETSI ETSI TS 132 302 V14.0.0 (2017-04)83GPP TS 32.302 version 14.0.0 Release 146 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 Manag