ETSI TS 132 306-2017 Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Configuration Management (CM) Notification Integration Reference Point (IRP).pdf

1、 ETSI TS 132 306 V14.0.0 (2017-04) Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Solution Set (SS) definitions (3GPP TS 32.306 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETS

2、I ETSI TS 132 306 V14.0.0 (2017-04)13GPP TS 32.306 version 14.0.0 Release 14Reference RTS/TSGS-0532306ve00 Keywords 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 742 C Association but non lu

3、cratif 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 and/or print versions of the

4、 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) version kept on a specific netwo

5、rk 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/ETSIDeliverableStatus.aspx If you find errors

6、 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 photocopying and microfilm except

7、 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 Telecommunications Standards Institute 2017. All rights reserved. DE

8、CTTM, 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 logo is protected for the benefit of its Members GSM and the

9、GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 306 V14.0.0 (2017-04)23GPP TS 32.306 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining

10、 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 E

12、TSI 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, U

13、MTS 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 i

15、n direct citation. ETSI ETSI TS 132 306 V14.0.0 (2017-04)33GPP TS 32.306 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 7g32 References 7g33 Definitions and abbreviations . 8g33.1 Definitions 8g33.2 Abb

16、reviations . 8g34 Solution Set Definitions . 8g3Annex A (normative): CORBA Solution Set . 9 g3A.1 Architectural Features 9g3A.1.1 Syntax for Distinguished Names 9g3A.1.2 Notification Services 9g3A.1.3 Support of Push and Pull Style . 9g3A.1.4 Support of multiple notifications in one push operation .

17、 9g3A.1.5 Support of filterable and non-filterable notification parameters . 10g3A.2 Mapping . 11g3A.2.1 Operation mapping . 11g3A.2.2 Operation parameter mapping 13g3A.2.3 Notification parameter mapping . 16g3A.3 IRPAgents Behaviour 17g3A.3.1 Subscription 17g3A.3.2 IRPAgent supports multiple catego

18、ries of Notifications 17g3A.3.3 IRPAgents integrity risk of attach_push_b Method . 18g3A.3.4 Quality of Service Parameters 18g3A.4 Solution Set definitions 19g3A.4.1 IDL definition structure 19g3A.4.2 IDL specification “ManagedGenericIRPConstDefs.idl“ 20g3A.4.3 IDL specification “ManagedGenericIRPSy

19、stem.idl” . 22g3A.4.4 IDL specification “NotificationIRPConstDefs.idl” 23g3A.4.5 IDL specification “NotificationIRPSystem.idl” . 25g3A.4.6 IDL specification “NotificationIRPNotifications.idl“ 28g3Annex B (normative): XML Definitions 29g3B.1 Architectural Features 29g3B.1.1 Syntax for Distinguished N

20、ames 29g3B.2 Mapping . 29g3B.3 Solution Set definitions 29g3B.3.1 Notification IRP XML notification header Definitions 29g3B.3.2 Graphical Representation . 30g3B.3.3 XML Schema “notification.xsd” 31g3Annex C (normative): SOAP Solution Set . 32g3C.1 Architectural features . 32g3C.1.2 Syntax for Disti

21、nguished Names 33g3ETSI ETSI TS 132 306 V14.0.0 (2017-04)43GPP TS 32.306 version 14.0.0 Release 14C.2 Mapping . 33g3C.2.1 Operation mapping . 33g3C.2.2 Filter language 34g3C.2.3 Common datatype definition 34g3C.2.3.1 NotificationCategorySetType . 34g3C.2.3.2 SubscriptionStateType 34g3C.2.4 Operation

22、 parameter mapping 34g3C.2.4.1 Operation subscribe 35g3C.2.4.1.1 Input parameters 35g3C.2.4.1.2 Output parameters . 35g3C.2.4.1.3 Fault definition 35g3C.2.4.2 Operation unsubscribe . 36g3C.2.4.2.1 Input parameters 36g3C.2.4.2.2 Output parameters . 36g3C.2.4.2.3 Fault definition 36g3C.2.4.3 Operation

23、 getSubscriptionIds 36g3C.2.4.3.1 Input parameters 36g3C.2.4.3.2 Output parameters . 37g3C.2.4.3.3 Fault definition 37g3C.2.4.4 Operation getSubscriptionStatus . 37g3C.2.4.4.1 Input parameters 37g3C.2.4.4.2 Output parameters . 38g3C.2.4.4.3 Fault definition 38g3C.2.4.5 Operation changeSubscriptionFi

24、lter . 38g3C.2.4.5.1 Input parameters 38g3C.2.4.5.2 Output parameters . 39g3C.2.4.5.3 Fault definition 39g3C.2.4.6 Operation suspendSubscription 39g3C.2.4.6.1 Input parameters 39g3C.2.4.6.2 Output parameters . 39g3C.2.4.6.3 Fault definition 39g3C.2.4.7 Operation resumeSubscription 40g3C.2.4.7.1 Inpu

25、t parameters 40g3C.2.4.7.2 Output parameters . 40g3C.2.4.7.3 Fault definition 40g3C.2.4.8 Operation getNotificationCategories 40g3C.2.4.8.1 Input parameters 40g3C.2.4.8.2 Output parameters . 41g3C.2.4.8.3 Fault definition 41g3C.2.5 Parameter mapping . 41g3C.2.6 NotificationIRPNotification Interface

26、definition 41g3C.2.6.1 Input parameters . 41g3C.2.6.2 Output parameters . 42g3C.3 IRPAgents Behaviour 43g3C.3.1 Subscription 43g3C.4 Solution Set definitions 44g3C.4.1 WSDL definition structure . 44g3C.4.2 Graphical Representation . 44g3C.4.3 WSDL specification “NotificationIRPSystem” 45g3C.4.4 WSDL

27、 specification “NotificationIRPNtfSystem” 53g3Annex D (informative): Change history . 54g3History 55g3ETSI ETSI TS 132 306 V14.0.0 (2017-04)53GPP TS 32.306 version 14.0.0 Release 14Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents o

28、f 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 release date and an increase in version number as follows: Ve

29、rsion 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. technical enhancements, corrections, updates, etc. z the

30、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 System Aspects; Telecommunication management; as identifi

31、ed 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.306: Configuration Management (CM); Notification Integration Reference Poin

32、t (IRP): Solution Set (SS) definitions Configuration Management (CM), in general, provides the operator with the ability to assure correct and effective operation of the 3G network as it evolves. CM actions have the objective to control and monitor the actual configuration on the Network Elements (N

33、Es) and Network Resources (NRs), and they may be initiated by the operator or by functions in the Operations Systems (OSs) or NEs. CM actions may be requested as part of an implementation programme (e.g. additions and deletions), as part of an optimisation programme (e.g. modifications), and to main

34、tain the overall Quality of Service (QoS). The CM actions are initiated either as a single action on a NE of the 3G network or as part of a complex procedure involving actions on many NEs. The Itf-N interface is built up by a number of Integration Reference Points (IRPs) and a related Name Conventio

35、n, which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in 3GPP TS 32.101 1. Network Elements (NEs) under management and element managers generate notifications of events about occurrences within the network. Different kinds of events carry differ

36、ent kinds of information, e.g. alarms or CM notification. 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 interfac

37、e 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 20, and OMG Notification Service 14. The central design ideas are: - Separation of notification Consumers (IRPManagers) from Producers (IRPAge

38、nts); ETSI ETSI TS 132 306 V14.0.0 (2017-04)63GPP TS 32.306 version 14.0.0 Release 14- Notifications 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 E

39、TSI TS 132 306 V14.0.0 (2017-04)73GPP TS 32.306 version 14.0.0 Release 141 Scope The present document contains the Solution Sets for the IRP whose semantics is specified in Notification IRP: Information Service (TS 32.302 7). These Solution Set specifications are related to 3GPP TS 32.302 V13.0.X 7.

40、 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, edition number, version number, etc.) or non-specific. - For a specific reference, subse

41、quent 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 the latest version of that document in the same Release as the present document. 1 3GPP TS

42、 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 Management; Alarm Integration Reference Point: Information Service (IS)“. 4 3GPP TS 32.111-6: “Tel

43、ecommunication management; Fault Management; Alarm Integration Reference Point (IRP); Solution Set (SS) definitions“. 5 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“. 6 3GPP TS 32.301: “Telecommunication Management; Configuration M

44、anagement (CM); Notification Integration Reference Point (IRP): Requirements“. 7 3GPP TS 32.302: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)“. 8 3GPP TS 32.311: “Telecommunication management; Generic Integrati

45、on Reference Point (IRP) management; Requirements“. 9 3GPP TS 32.312: “Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)“. 10 3GPP TS 32.316: “Telecommunication management; Generic Integration Reference Point (IRP) management; Solution Set (

46、SS) definitions“. 11 3GPP TS 32.331: “Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): Requirements“. 12 3GPP TS 32.336: “Telecommunication management; Notification Log (NL) Integration Reference Point (IRP); Solution Set (SS) definitions“. 13 OMG TC Document te

47、lecom (98-11-01): “Summary of responses to real time survey“. 14 OMG TC Document telecom/98-11-01: “OMG Notification Service“. http:/www.omg.org/technology/documents/ 15 OMG CORBA Services: “Common Object Services Specification, Update: November 22, 1996“ (Clause 4 contains the Event Service specifi

48、cation). http:/www.omg.org/technology/documents/ ETSI ETSI TS 132 306 V14.0.0 (2017-04)83GPP TS 32.306 version 14.0.0 Release 1416 W3C SOAP 1.1 specification (http:/www.w3.org/TR/2000/NOTE-SOAP-20000508/) 17 W3C SOAP 1.2 specification (http:/www.w3.org/TR/soap12-part1/) 18 W3C WSDL 1.1 specification

49、 (http:/www.w3.org/TR/2001/NOTE-wsdl-20010315) 19 W3C XPath 1.0 specification (http:/www.w3.org/TR/1999/REC-xpath-19991116) 20 ITU-T Recommendation X.734 (1992): “Information technology - Open Systems Interconnection - Systems management: Event report management function“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 1, 3GPP TS 32.102 2, 3GPP TS 32.301 6, 3GPP TS 32.302 7, and 3GPP TS 32.331 11 apply. IRP document