1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelTelecommSelf-configuIntegratioSolutio(3GPP TS 32.5TECHNICAL SPECIFICATION132 506 V13.0.0 (2016communications system (Phaelecommunications System (LTE; munication management; guration of network elements tion Reference Point (IRP); tion Set (SS) de
2、finitions .506 version 13.0.0 Release 1316-02) hase 2+); (UMTS); ts 13) ETSI ETSI TS 132 506 V13.0.0 (2016-02)13GPP TS 32.506 version 13.0.0 Release 13Reference RTS/TSGS-0532506vd00 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 506 V13.0.0 (2016-02)23GPP TS 32.506 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 506 V13.0.0 (2016-02)33GPP TS 32.506 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitio
16、ns 7g33.2 Abbreviations . 8g34 Solution Set definitions 9g3Annex A (normative): CORBA Solution Set . 10g3A.1 Architectural features . 10g3A.1.1 Syntax for Distinguished Names 10g3A.1.2 Notification Services 10g3A.1.3 Push and Pull Style . 10g3A.1.4 Support multiple notifications in one push operatio
17、n . 10g3A.2 Mapping . 11g3A.2.1 Operation and Notification mapping 11g3A.2.2 Operation parameter mapping 11g3A.2.3 Notification parameter mapping . 14g3A.3 Solution Set definitions 15g3A.3.1 IDL definition structure 15g3A.3.2 IDL specification (file name “SelfConfIRPConstDefs.idl“) . 16g3A.3.3 IDL s
18、pecification (file name “SelfConfIRPSystem.idl“) 17g3A.3.4 IDL specification (file name “SelfConfIRPNotifications.idl“) . 20g3Annex B (normative): XML definitions . 22g3B.1 Architectural Features 22g3B.1.1 Syntax for Distinguished Names 22g3B.1.2 Notification Services 22g3B.1.3 IOC Definitions 22g3B
19、.2 Mapping . 22g3B.3 Solution Set definitions 22g3B.3.1 XML definition structure 22g3B.3.2 Graphical Representation . 23g3B.3.3 XML Schema scIRPNotif.xsd . 27g3B.3.4 XML Schema scIRPIOCs.xsd . 30g3Annex C (normative): SOAP Solution Set . 32g3C.1 Architectural features . 32g3C.1.1 Syntax for Distingu
20、ished Names 32g3C.1.2 Notification Services 32g3C.1.3 Supported W3C specifications . 32g3C.1.4 Prefixes and namespaces 32g3C.2 Mapping . 33g3C.2.1 Operation and Notification mapping 33g3ETSI ETSI TS 132 506 V13.0.0 (2016-02)43GPP TS 32.506 version 13.0.0 Release 13C.2.2 Operation parameter mapping 3
21、3g3C.2.2.1 Operation listScManagementCapabilities . 34g3C.2.2.1.1 Input parameters 34g3C.2.2.1.2 Output parameters . 34g3C.2.2.1.3 Fault definition 34g3C.2.2.2 Operation listScManagementProfiles . 34g3C.2.2.2.1 Input parameters 34g3C.2.2.2.2 Output parameters . 34g3C.2.2.3 Operation createScManageme
22、ntProfile 35g3C.2.2.3.1 Input parameters 35g3C.2.2.3.2 Output parameters . 35g3C.2.2.4 Operation deleteScManagementProfile 35g3C.2.2.4.1 Input parameters 35g3C.2.2.4.2 Output parameters . 36g3C.2.2.5 Operation listScProcesses . 36g3C.2.2.5.1 Input parameters 36g3C.2.2.5.2 Output parameters . 36g3C.2
23、.2.6 Operation resumeScProcess 36g3C.2.2.6.1 Input parameters 36g3C.2.2.6.2 Output parameters . 36g3C.2.2.7 Operation terminateSctProcess . 37g3C.2.2.7.1 Input parameters 37g3C.2.2.7.2 Output parameters . 37g3C.2.2.8 Operation changeScManagementProfile. 37g3C.2.2.8.1 Input parameters 37g3C.2.2.8.2 O
24、utput parameters . 37g3C.3 Solution Set definitions 38g3C.3.1 WSDL definition structure 38g3C.3.2 Graphical Representation . 38g3C.3.3 WSDL specification ScIRPSystem.wsdl . 38g3Annex D (informative): Change history . 46g3History 47g3ETSI ETSI TS 132 506 V13.0.0 (2016-02)53GPP TS 32.506 version 13.0.
25、0 Release 13Foreword 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 present
26、 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 change
27、 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 the
28、 3rdGeneration Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management, as identified below: 32.501: Self-Configuration of Network Elements; Concepts and Integration Reference Point (IRP) Requirements 32.502: Self-Configuration of Network Elements
29、 Integration Reference Point (IRP); Information Service (IS) 32.506: Self-Configuration of Network Elements Integration Reference Point (IRP): Solution Set (SS) definitions “ The present document is part of a TS-family which describe the requirements and information model necessary for the Telecommu
30、nication Management (TM) of 3G systems. The TM principles and TM architecture are specified in 3GPP TS 32.101 1 and 3GPP TS 32.102 2. For the purpose of Self-Configuration of Network Elements IRP, see TS 32.501 3 ETSI ETSI TS 132 506 V13.0.0 (2016-02)63GPP TS 32.506 version 13.0.0 Release 131 Scope
31、The present document specifies the Solution Set definitions for the IRP whose semantics are specified in Self-Configuration of Network Elements Integration Reference Point (IRP): Information Service (3GPP TS 32.502 4). This Solution Set specification is related to 3GPP TS 32.502 V12.0.X. 2 Reference
32、s 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.) non-specific. For a specific reference, subsequent revisions do
33、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 32.101: “Telecommuni
34、cation management; Principles and high level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.501: “ Technical Specification Group Services and System Aspects; Telecommunication management; Self-Configuration of Network Elements; Concepts and Integration Re
35、ference Point (IRP) Requirements “. 4 3GPP TS 32.502: “ Technical Specification Group Services and System Aspects; Telecommunication management; Self-Configuration of Network Elements Integration Reference Point (IRP); Information Service (IS)“. 5 3GPP TR 32.816: “Telecommunication management; Study
36、 on Management of Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and Evolved Packet Core (EPC)“. 6 OMG TC Document telecom/98-11-01: “OMG Notification Service“. http:/www.omg.org/technology/documents/ 7 3GPP TS 32.531: “Telecommunication management; Software management; Concepts and In
37、tegration Reference Point (IRP) Requirements“. 8 3GPP TS 32.532: “Telecommunication management; Software management Integration Reference Point (IRP); Information Service (IS)“. 9 3GPP TS 32.536: “Telecommunication management; Software management Integration Reference Point (IRP); Solution Set defin
38、itions “. 10 W3C REC-xml-20001006: “Extensible Markup Language (XML) 1.0 (Second Edition)“. 11 W3C REC-xmlschema-0-20010502: “XML Schema Part 0: Primer“. 12 W3C REC-xmlschema-1-20010502: “XML Schema Part 1: Structures“. 13 W3C REC-xmlschema-2-20010502: “XML Schema Part 2: Datatypes“. 14 W3C REC-xml-
39、names-19990114: “Namespaces in XML“. 15 3GPP TS 32.311: “Telecommunication management; Generic Integration Reference Point (IRP) management; Requirements“ ETSI ETSI TS 132 506 V13.0.0 (2016-02)73GPP TS 32.506 version 13.0.0 Release 1316 3GPP TS 32.312: “Telecommunication management; Generic Integrat
40、ion Reference Point (IRP) management; Information Service (IS)“. 17 3GPP TS 32.316: “Telecommunication management; Generic Integration Reference Point (IRP) management; Solution Set definitions “. 18 3GPP TS 32.150: “Telecommunication management; Integration Reference Point (IRP) Concept and definit
41、ions“. 19 3GPP TS 32.306: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Solution Set definitions. 20 W3C SOAP 1.1 specification (http:/www.w3.org/TR/2000/NOTE-SOAP-20000508/) 21 W3C XPath 1.0 specification (http:/www.w3.org/TR/1999/REC-
42、xpath-19991116) 22 W3C WSDL 1.1 specification (http:/www.w3.org/TR/2001/NOTE-wsdl-20010315) 23 W3C SOAP 1.2 specification (http:/www.w3.org/TR/soap12-part1/) 24 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“ 3 Definitions and abbrev
43、iations 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.150 18 and 3GPP TS 32.501 3 and the following apply: IRP document version number string (or “IRPVersion“): See 3GPP TS 32.311 15 IRP: See 3GPP TS 32.150
44、 18. IRPAgent: See 3GPP TS 32.150 18. IRPManager: See 3GPP TS 32.150 18. Self Configuration: The process which brings a network element into service requiring minimal human operator intervention or none at all. XML file: file containing an XML document XML document: composed of the succession of an
45、optional XML declaration followed by a root XML element NOTE: See 10; in the scope of the present document. XML declaration: it specifies the version of XML being used NOTE: See 10. XML element: has a type, is identified by a name, may have a set of XML attribute specifications and is either compose
46、d of the succession of an XML start-tag followed by the XML content of the XML element followed by an XML end-tag, or composed simply of an XML empty-element tag; each XML element may contain other XML elements NOTE: See 10. empty XML element: having an empty XML content; an empty XML element still
47、possibly has a set of XML attribute specifications; an empty XML element is either composed of the succession of an XML start-tag directly followed by an XML end-tag, or composed simply of an XML empty-element tag NOTE: See 10. ETSI ETSI TS 132 506 V13.0.0 (2016-02)83GPP TS 32.506 version 13.0.0 Rel
48、ease 13XML content (of an XML element): empty if the XML element is simply composed of an XML empty-element tag; otherwise the part, possibly empty, of the XML element between its XML start-tag and its XML end-tag XML start-tag: the beginning of a non-empty XML element is marked by an XML start-tag
49、containing the name and the set of XML attribute specifications of the XML element NOTE: See 10. XML end-tag: the end of a non-empty XML element is marked by an XML end-tag containing the name of the XML element NOTE: See 10. XML empty-element tag: composed simply of an empty-element tag containing the name and the set of XML attribute specifications of the XML element. NOTE: See 10. XML attribute specification: has a name and a value NOTE: See 10. DTD: defines structure
