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

1、 ETSI TS 132 307 V9.2.0 (2011-10) Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); SOAP Solution Set (SS) (3GPP TS 32.307 version

2、 9.2.0 Release 9) Technical Specification ETSI ETSI TS 132 307 V9.2.0 (2011-10)13GPP TS 32.307 version 9.2.0 Release 9Reference RTS/TSGS-0532307v920 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 62

3、3 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print.

4、 In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users

5、 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:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your commen

6、t to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Inst

7、itute 2011. 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 GSM logo are Trade Ma

8、rks registered and owned by the GSM Association. ETSI ETSI TS 132 307 V9.2.0 (2011-10)23GPP TS 32.307 version 9.2.0 Release 9Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs

9、, 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. Latest updates are avai

10、lable on the ETSI Web server (http:/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 ETSI Web server) which are,

11、 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, UMTS identities or GSM iden

12、tities. 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. ETSI ETSI TS 132 307 V9.2.0 (2011-10)33GPP TS 32.307 version 9.2.0 Release 9Cont

13、ents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 5g3Introduction 5g31 Scope 7g32 References 7g33 Definitions and abbreviations . 8g33.1 Definitions 8g33.2 Abbreviations . 8g34 Architectural features . 8g35 Mapping . 10g35.1 Operation mapping . 10g35.2 Filter language 10g35.3 Common data

14、type definition 10g35.3.1 NotificationCategorySetType . 10g35.3.2 SubscriptionStateType 10g35.4 Operation parameter mapping 11g35.4.1 Operation subscribe 11g35.4.1.1 Input parameters 11g35.4.1.2 Output parameters . 11g35.4.1.3 Fault definition 11g35.4.2 Operation unsubscribe . 12g35.4.2.1 Input para

15、meters 12g35.4.2.2 Output parameters . 12g35.4.2.3 Fault definition 12g35.4.3 Operation getSubscriptionIds 13g35.4.3.1 Input parameters 13g35.4.3.2 Output parameters . 13g35.4.3.3 Fault definition 13g35.4.4 Operation getSubscriptionStatus . 14g35.4.4.1 Input parameters 14g35.4.4.2 Output parameters

16、. 14g35.4.4.3 Fault definition 14g35.4.5 Operation changeSubscriptionFilter . 15g35.4.5.1 Input parameters 15g35.4.5.2 Output parameters . 15g35.4.5.3 Fault definition 15g35.4.6 Operation suspendSubscription 15g35.4.6.1 Input parameters 15g35.4.6.2 Output parameters . 16g35.4.6.3 Fault definition 16

17、g35.4.7 Operation resumeSubscription 16g35.4.7.1 Input parameters 16g35.4.7.2 Output parameters . 16g35.4.7.3 Fault definition 17g35.4.8 Operation getNotificationCategories 17g35.4.8.1 Input parameters 17g35.4.8.2 Output parameters . 17g35.4.8.3 Fault definition 17g35.5 Parameter mapping . 17g35.6 N

18、otificationIRPNotification Interface definition 18g35.6.1 Input parameters . 18g3ETSI ETSI TS 132 307 V9.2.0 (2011-10)43GPP TS 32.307 version 9.2.0 Release 95.6.2 Output parameters . 18g36 IRPAgents Behaviour 18g36.1 Subscription 18g3Annex A (normative): WSDL specifications 19g3Annex B (normative):

19、Notification WSDL specifications . 27g3Annex C (informative): Void . 28g3Annex D (informative): Change history . 29g3History 30g3ETSI ETSI TS 132 307 V9.2.0 (2011-10)53GPP TS 32.307 version 9.2.0 Release 9Foreword This Technical Specification (TS) has been produced by the 3rdGeneration Partnership P

20、roject (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 release date and an increase in

21、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. technical enhancements, corr

22、ections, 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 System Aspects; Telecommunic

23、ation 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 Management (CM); Notificati

24、on 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); Notification Integration

25、 Reference Point (IRP); SOAP Solution Set 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

26、 (NEs) 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 m

27、aintain 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 Conven

28、tion, which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in 3GPP TS 32.101 6 and 3GPP TS 32.102 7. Network Elements (NEs) under management and element managers generate notifications of events about occurrences within the network. Different kind

29、s of events carry different kinds of information. For instance a new alarm as specified in 3GPP TS 32.111-2 Alarm IRP: Information Service 5, is one possible kind of event, an object creation as specified in 3GPP TS 32.602 Basic CM IRP: Information Service 15 is another possible kind of event. ETSI

30、ETSI TS 132 307 V9.2.0 (2011-10)63GPP TS 32.307 version 9.2.0 Release 9Information 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 defin

31、e 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, The central design ideas are: Separation of notification Consumers (IRPManagers) from Producers (IRPAgents); Notifications are

32、 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 307 V9.2.0 (2011-10)73GPP TS 32.307 version 9.2.0 Release 91 Scope The present document speci

33、fies the SOAP Solution Set for the IRP whose semantics is specified in Notification IRP: Information Service (3GPP TS 32.302 4). This Solution Set specification is related to 3GPP TS 32.302 V9.0.X. 2 References The following documents contain provisions which, through reference in this text, constit

34、ute provisions of the present document. References are either specific (identified by date of publication, edition number, version number, etc.) 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 refer

35、ence 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 ITU-T Recommendation X.736: “Information technology - Open Systems Interconnection - Systems Management: Security alarm

36、 reporting function“. 2 ITU-T Recommendation X.734 (1992): “Information technology - Open Systems Interconnection - Systems management: Event report management function“. 3 3GPP TS 32.312: “Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)“.

37、 4 3GPP TS 32.302: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)“. 5 3GPP TS 32.111-2: “Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)“.

38、 6 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. 7 3GPP TS 32.102: “Telecommunication management; Architecture“. 8 3GPP TS 32.301: “Telecommunication Management; Configuration Management (CM); Notification Integration Reference Point (IRP): Requirements“. 9

39、3GPP TS 32.317: “Telecommunication management; Generic Integration Reference Point (IRP) management; SOAP solution set“. 10 3GPP TS 32.311: “Telecommunication management; Generic Integration Reference Point (IRP) management; Requirements“. 11 3GPP TS 32.172: “Telecommunication management; Subscripti

40、on Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service“. 12 W3C SOAP 1.1 specification (http:/www.w3.org/TR/2000/NOTE-SOAP-20000508/) 13 W3C XPath 1.0 specification (http:/www.w3.org/TR/1999/REC-xpath-19991116) 14 W3C WSDL 1.1 specification (http:/www

41、.w3.org/TR/2001/NOTE-wsdl-20010315) 15 3GPP TS 32.602: “Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP): Information Service (IS)“. ETSI ETSI TS 132 307 V9.2.0 (2011-10)83GPP TS 32.307 version 9.2.0 Release 916 3GPP TS 32.305: “Telecommunicatio

42、n management; Configuration Management (CM); Notification Integration Reference Point (IRP): eXtensible Markup Language (XML) definition“. 17 WS-I Basic Profile Version 1.1 (http:/www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html) 18 W3C SOAP 1.2 specification (http:/www.w3.org/TR/soap12-part1/

43、) 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 6, 3GPP TS 32.102 7 and 3GPP TS 32.301 8 and the following apply: IRP document version number string (or “IRPVersion“): See 3GPP TS 32.311 10. 3.2 Abbreviatio

44、ns For the purposes of the present document, the following abbreviations apply: CM Configuration Management EM Element Manager IS Information ServiceNE Network Element NV Name and Value pair QoS Quality of Service SS Solution Set WSDL Web Service Description Language WS-I Web Services Interoperabili

45、ty Organization 4 Architectural features The overall architectural feature of Notification IRP is specified in 3GPP TS 32.302 4. This clause specifies features that are specific to the SOAP solution set. The SOAP 1.1 specification 12 and WSDL 1.1 specification 14 are supported. The SOAP 1.2 specific

46、ation 18 is supported optionally. This specification uses “document“ style in WSDL file. This specification uses “literal“ encoding style in WSDL file. The IRPAgent shall support the push interface model that means IRPAgent sends notifications to IRPManager as soon as new events occur. IRPManager do

47、es not need to check (“pull“) for events. The Notification definition is imported from Notification IRP XML Definition 16. This specification uses a number of namespace prefixes throughout that are listed in Table 4.1. ETSI ETSI TS 132 307 V9.2.0 (2011-10)93GPP TS 32.307 version 9.2.0 Release 9Table

48、 4.1: Prefixes and Namespaces used in this specification PREFIX NAMESPACE http http:/schemas.xmlsoap.org/wsdl/http/ soap http:/schemas.xmlsoap.org/wsdl/soap/SOAP-ENV http:/schemas.xmlsoap.org/soap/envelope/ SOAP-ENC or soapenc http:/schemas.xmlsoap.org/soap/encoding/ xs or xsd http:/www.w3.org/2001/

49、XMLSchema xsi http:/www.w3.org/2001/XMLSchema-instance ntfIRPSystem http:/www.3gpp.org/ftp/Specs/archive/32_series/32.307/schema/32307-810/NotificationIRPSystem ntfIRPData http:/www.3gpp.org/ftp/Specs/archive/32_series/32.307/schema/32307-810/NotificationIRPData ntfIRPNtfSystem http:/www.3gpp.org/ftp/Specs/archive/32_series/32.307/schema/32307-810/notification/NotificationIRPNtfSystem ntfIRPNtfData http:/www.3gpp.org/ftp/Specs/archive/32_series/32.307/schema/32307-810/notification/No