1、 ETSI TS 132 386 V14.0.0 (2017-04) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Partial Suspension of Itf-N Integration Reference Point (IRP); Solution Set (SS) definitions (3GPP TS 32.386 version 1
2、4.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 132 386 V14.0.0 (2017-04)13GPP TS 32.386 version 14.0.0 Release 14Reference RTS/TSGS-0532386ve00 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
3、 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. The conte
4、nt 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 Portable Docum
5、ent 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:/portal.etsi.org
6、/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, electronic or mechan
7、ical, 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 Telecommunications
8、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 logo is prot
9、ected 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 386 V14.0.0 (2017-04)23GPP TS 32.386 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have
10、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 ETSI standard
11、s“, 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 IPRs not refer
12、enced 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 technical specifi
13、cations 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.asp. Modal
14、 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 not“ are NO
15、T allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 132 386 V14.0.0 (2017-04)33GPP TS 32.386 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions,
16、 symbols and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 8g34 Solution Set definitions 8g3Annex A (normative): CORBA Solution Set . 9g3A.1 Architectural features . 9g3A.1.1 Syntax for Distinguished Names 9g3A.1.2 Notifications . 9g3A.2 Mapping . 9g3A.2.1 General mapping 9g3A.2.2 Operat
17、ion and notification mapping . 9g3A.2.3 Operation parameter mapping 10g3A.2.4 Notification parameter mapping . 10g3A.3 Solution Set definitions 11g3A.3.1 IDL definition structure 11g3A.3.2 IDL specification (file name “PartialSuspensionConstDefs.idl“) . 12g3A.3.3 IDL specification (file name “Partia
18、lSuspensionSystem.idl“) 15g3A.3.4 IDL specification (file name “PartialSuspensionOfItfNNotifications.idl“) 17g3Annex B (normative): XML definitions . 19g3B.1 Architectural Features 19g3B.1.1 Syntax for Distinguished Names 19g3B.1.2 Notification Services 19g3B.1.3 IOC definitions . 19g3B.2 Mapping .
19、19g3B.3 Solution Set definitions 19g3B.3.1 XML definition structure 19g3B.3.2 Graphical Representation . 20g3B.3.3 XML Schema “partialSuspensionOfItfN.xsd“ 20g3Annex C (normative): SOAP Solution Set . 21g3C.1 Architectural features . 21g3C.1.1 Syntax for Distinguished Names 21g3C.1.2 Notification Se
20、rvices 21g3C.1.3 Supported W3C specifications . 21g3C.1.4 Prefixes and namespaces 21g3C.2 Mapping . 22g3C.2.1 Operation and notification mapping . 22g3C.2.2 Operation parameter mapping 22g3C.2.3 Notification parameter mapping . 23g3ETSI ETSI TS 132 386 V14.0.0 (2017-04)43GPP TS 32.386 version 14.0.0
21、 Release 14C.3 Solution Set definitions 23g3C.3.1 WSDL definition structure . 23g3C.3.2 Graphical Representation . 23g3C.3.3 WSDL specification “PSINIRPSystem.wsdl” 24g3Annex D (informative): Change history . 28g3History 29g3ETSI ETSI TS 132 386 V14.0.0 (2017-04)53GPP TS 32.386 version 14.0.0 Releas
22、e 14Foreword This Technical Specification 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
23、 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 control. y t
24、he 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 multi-part TS covering the 3rdGener
25、ation Partnership Project: Technical Specification Group Services and System Aspects; Telecommunication Management; Partial Suspension of Itf-N Integration Reference Point (IRP), as identified below: 32.381: “Partial Suspension of Itf-N Integration Reference Point (IRP); Requirements“. 32.382: “Part
26、ial Suspension of Itf-N Integration Reference Point (IRP); Information Service (IS)“ 32.386: “Partial Suspension of Itf-N Integration Reference Point (IRP); Solution Set (SS) definitions“. The present document describes the requirements and information model necessary for Telecommunication Managemen
27、t (TM). The TM principles and TM architecture are specified in 3GPP TS 32.101 2 and 3GPP TS 32.102 3. Information of an event is carried in notification. An IRPAgent (typically an EM or a NE) emits notifications (see 3GPP TS 32.302 16. IRPManager (typically a network management system) receives noti
28、fications. In certain scenarios floods of unwanted notifications including alarms will be sent to the IRP manager by network object instances. Thereby the interface and the management systems bear unnecessary load. Even worse: The operators awareness is drawn away from really urgent events. ETSI ETS
29、I TS 132 386 V14.0.0 (2017-04)63GPP TS 32.386 version 14.0.0 Release 141 Scope The present document specifies the Solution Set definitions for the IRP whose semantics is specified Partial Suspension of Itf-N IRP IS (3GPP TS 32.382 5). This Solution Set specification is related to 3GPP TS 32.382 V13.
30、0.X. 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, s
31、ubsequent 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 3GP
32、P TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. 3 3GPP TS 32.102: “Telecommunication management; Architecture“. 4 3GPP TS 32.150: “Telecommunication management; Integration Reference Point (IRP) Concept and
33、definitions“. 5 3GPP TS 32.382: “Telecommunication management; Partial Suspension of Itf-N Integration Reference Point (IRP); Information Service (IS)“. 6 3GPP TS 32.622: “Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP); Networ
34、k Resource Model (NRM)“. 7 3GPP TS 32.312: “Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)“. 8 W3C REC-xml-20001006: “Extensible Markup Language (XML) 1.0 (Second Edition)“. 9 W3C REC-xmlschema-0-20010502: “XML Schema Part 0: Primer“. 10
35、W3C REC-xmlschema-1-20010502: “XML Schema Part 1: Structures“. 11 W3C REC-xmlschema-2-20010502: “XML Schema Part 2: Datatypes“. 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 sp
36、ecification (http:/www.w3.org/TR/2001/NOTE-wsdl-20010315) 15 W3C SOAP 1.2 specification (http:/www.w3.org/TR/soap12-part1/). 16 3GPP TS 32.302: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)“. 17 3GPP TS 32.306:
37、“Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Solution Set definitions“ 18 3GPP TS 32.616: “Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Solution Set definitions “. ETSI ETSI TS
38、 132 386 V14.0.0 (2017-04)73GPP TS 32.386 version 14.0.0 Release 1419 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and d
39、efinitions given in TR 21.905 1, 3GPP TS 32.101 2, 3GPP TS 32.102 3, 3GPP TS 32.150 4, 3GPP TS 32.382 5 apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 1. IRP: See 3GPP TS 32.101 2. IRPAgent: See 3GPP TS 32.102 3. IRPManager:
40、See 3GPP TS 32.102 3. Suspended notification: See 3GPP TS 32.382 5. Itf-N suspended managed instance: See 3GPP TS 32.382 5. Partial suspension of Itf-N: See 3GPP TS 32.382 5. XML file: file containing an XML document. XML document: composed of the succession of an optional XML declaration followed b
41、y a root XML element 8. XML declaration: it specifies the version of XML being used, see 8. XML element: has a type, is identified by a name, may have a set of XML attribute specifications and is either composed of the succession of an XML start-tag followed by the XML content of the XML element fol
42、lowed by an XML end-tag, or composed simply of an XML empty-element tag; each XML element may contain other XML elements, see 8. empty XML element: having an empty XML content; an empty XML element still possibly has a set of XML attribute specifications; an empty XML element is either composed of t
43、he succession of an XML start-tag directly followed by an XML end-tag, or composed simply of an XML empty-element tag, see 8. XML 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 X
44、ML start-tag and its XML end-tag, see 8. XML start-tag: the beginning of a non-empty XML element is marked by an XML start-tag containing the name and the set of XML attribute specifications of the XML element, see 8. XML end-tag: the end of a non-empty XML element is marked by an XML end-tag contai
45、ning the name of the XML element, see 8. 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, see 8. XML attribute specification: has a name and a value, see 8. DTD: defines structure and content constraint
46、s to be respected by an XML document to be valid with regard to this DTD, see 8. XML schema: more powerful than a DTD, an XML schema defines structure and content constraints to be respected by an XML document to conform with this XML schema; through the use of XML namespaces several XML schemas can
47、 be used together by a single XML document; an XML schema is itself also an XML document that shall conform with the XML schema for XML schemas, see 9, 10 and 11. XML namespace: enables qualifying element and attribute names used in XML documents by associating them with namespaces identified by dif
48、ferent XML schemas, see 9, 10 and 11. ETSI ETSI TS 132 386 V14.0.0 (2017-04)83GPP TS 32.386 version 14.0.0 Release 14XML complex type: defined in an XML schema; cannot be directly used in an XML document; can be the concrete type or the derivation base type for an XML element type or for another XML
49、 complex type; ultimately defines constraints for an XML element on its XML attribute specifications and/or its XML content, see 9, 10 and 11. XML element type: declared by an XML schema; can be directly used in an XML document; as the concrete type of an XML element, directly or indirectly defines constraints on its XML attribute specifications and/or its XML content; can also be the concrete type or the derivation base type for another XML element type, see 9,
