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

1、 ETSI TS 132 396 V14.0.0 (2017-04) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Delta synchronization Integration Reference Point (IRP); Solution Set (SS) definitions (3GPP TS 32.396 version 14.0.0

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

3、62 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 content of

4、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 Document Fo

5、rmat (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/TB/ET

6、SIDeliverableStatus.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 mechanical,

7、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 Standa

8、rds 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 protected

9、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 396 V14.0.0 (2017-04)23GPP TS 32.396 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been d

10、eclared 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 standards“, wh

11、ich 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 referenced

12、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 specification

13、s 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 verbs

14、 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 NOT allo

15、wed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 132 396 V14.0.0 (2017-04)33GPP TS 32.396 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and ab

16、breviations . 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 Notification Services 9g3A.1.3 Push and Pull Style . 9g3A.1.4 Support multiple notificat

17、ions in one push operation . 9g3A.1.5 Delta Synchronization Notification Interface . 9g3A.1.5.1 Method push (M) 9g3A.2 Mapping . 10g3A.2.1 General mapping 10g3A.2.2 Operation and notification mapping . 10g3A.2.3 Operation parameter mapping 10g3A.2.4 Notification parameter mapping . 13g3A.3 Solution

18、Set definitions 18g3A.3.1 IDL definition structure 18g3A.3.2 IDL specification (file name “DeltaSynchronizationConstDefs.idl“) . 19g3A.3.3 IDL specification (file name “DeltaSynchronizationSystem.idl“) 24g3A.3.4 IDL specification (file name “DeltaSynchronizationNotifications.idl“) . 27g3Annex B (nor

19、mative): XML definitions . 29g3B.1 Architectural Features 29g3B.1.1 Syntax for Distinguished Names 29g3B.1.2 Notification Services 29g3B.1.3 IOC definitions . 29g3B.2 Mapping . 29g3B.3 Solution Set definitions 29g3B.3.1 XML definition structure 29g3B.3.1.1 Global structure 30g3B.3.1.2 XML elements f

20、ileHeader and fileFooter . 30g3B.3.1.2.1 XML elements fileHeaderForDeltaSynchForCM/AlarmData . 30g3B.3.1.2.2 XML element fileFooter . 31g3B.3.1.3 Delta synchronisation IRP specific XML elements 32g3B.3.1.4 Delta synchronisation IRP XML File Name Conventions 32g3B.3.2 Graphical Representation . 33g3B

21、.3.3 XML Schema . 36g3B.3.3.1 XML Schema “deltaSynchGeneric.xsd“ . 36g3B.3.3.2 XML Schema “deltaSynchForCMData.xsd“ 38g3ETSI ETSI TS 132 396 V14.0.0 (2017-04)43GPP TS 32.396 version 14.0.0 Release 14B.3.3.3 XML Schema “deltaSynchForAlarms.xsd“ 39g3Annex C (normative): SOAP Solution Set . 40g3C.1 Arc

22、hitectural features . 40g3C.1.1 Syntax for Distinguished Names 40g3C.1.2 Notification Services 40g3C.1.3 Supported W3C specifications . 40g3C.1.4 Prefixes and namespaces 40g3C.2 Mapping . 41g3C.2.1 Operation and notification mapping . 41g3C.2.2 Operation parameter mapping 41g3C.2.3 Notification para

23、meter mapping . 42g3C.3 Solution Set definitions 42g3C.3.1 WSDL definition structure . 42g3C.3.2 Graphical Representation . 42g3C.3.3 WSDL specification “DeltaSynchIRPSystem.wsdl” 43g3Annex D (informative): Change history . 50g3History 51g3ETSI ETSI TS 132 396 V14.0.0 (2017-04)53GPP TS 32.396 versio

24、n 14.0.0 Release 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 prese

25、nt 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 chan

26、ge 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 t

27、he 3rdGeneration Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Communication Surveillance management Integration Reference Point (IRP), as identified below: 32.391: “Delta Synchronization Integration Reference Point (IRP); Requirements“

28、 32.392: “Delta Synchronization Integration Reference Point (IRP): Information Service (IS)“ 32.396: “Delta Synchronization Integration Reference Point (IRP): Solution Set definitions“ The Itf-N interface is built up by a number of IRPs and a related Name Convention, which realise the functional cap

29、abilities over this interface. The basic structure of the IRPs is defined in 3GPP TS 32.101 2 and 3GPP TS 32.102 3. IRPManagers (typically Network Management Systems) and IRPAgents (typically EMs or NEs) synchronize their data concerning alarms or configuration data. In certain scenarios this synchr

30、onization is lost or not done. This IRP provides functionality to significantly reduces the amount of data which needs to be transferred in order to re-establish synchronization. ETSI ETSI TS 132 396 V14.0.0 (2017-04)63GPP TS 32.396 version 14.0.0 Release 141 Scope The present document specifies the

31、 Solution Set definitions for the IRP whose semantics is specified in Delta Synchronization IRP IS (3GPP TS 32.392 5). This Solution Set specification is related to 3GPP TS 32.392 V13.0.X. 2 References The following documents contain provisions which, through reference in this text, constitute provi

32、sions 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 version applies. In the case of a refer

33、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 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 32.101: “Telecommunication management; Principles and h

34、igh level requirements“. 3 3GPP TS 32.102: “Telecommunication management; Architecture“. 4 3GPP TS 32.150: “Telecommunication management; Integration Reference Point (IRP) Concept and definitions“. 5 3GPP TS 32.392: “Telecommunication management; Delta Synchronization Integration Reference Point (IR

35、P): Information Service (IS)“. 6 3GPP TS 32.391: “Configuration Management (CM); Delta Synchronization Integration Reference Point (IRP): Requirements“. 7 3GPP TS 32.302: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service

36、 (IS)“. 8 3GPP TS 32.622: “Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)“. 9 3GPP TS 32.312: “Telecommunication management; Generic Integration Reference Point (IRP) management; Information Servi

37、ce (IS)“. 10 3GPP TS 32.602: “Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP) management; Information Service (IS)“. 11 3GPP TS 32.306: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP)

38、: Solution Set definitions “. 12 OMG TC Document telecom/98-11-01: “OMG Notification Service“. http:/www.omg.org/technology/documents/ 13 3GPP TS 32.342: “Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Information Service (IS)“. 14 W3C REC-xml-20001006: “Extensib

39、le Markup Language (XML) 1.0 (Second Edition)“. 15 W3C REC-xmlschema-0-20010502: “XML Schema Part 0: Primer“. 16 W3C REC-xmlschema-1-20010502: “XML Schema Part 1: Structures“. ETSI ETSI TS 132 396 V14.0.0 (2017-04)73GPP TS 32.396 version 14.0.0 Release 1417 W3C REC-xmlschema-2-20010502: “XML Schema

40、Part 2: Datatypes“. 18 W3C REC-xml-names-19990114: “Namespaces in XML“ 19 3GPP TS 32.111-6: “Telecommunication management; Fault Management; Part 5: Alarm Integration Reference Point (IRP): Solution Set definitions “. 20 3GPP TS 32.616: “Telecommunication management; Configuration Management (CM); B

41、ulk CM Integration Reference Point (IRP): Solution Set definitions “. 21 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“. 22 W3C SOAP 1.1 specification (http:/www.w3.org/TR/2000/NOTE-SOAP-20000508/) 23 W3C XPath 1.0 specification (ht

42、tp:/www.w3.org/TR/1999/REC-xpath-19991116) 24 W3C WSDL 1.1 specification (http:/www.w3.org/TR/2001/NOTE-wsdl-20010315) 25 W3C SOAP 1.2 specification (http:/www.w3.org/TR/soap12-part1/) 26 3GPP TS 32.311: “Telecommunication management; Generic Integration Reference Point (IRP): Requirements“. 3 Defin

43、itions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 1, 3GPP TS 32.101 2, 3GPP TS 32.102 3, 3GPP TS 32.150 4 apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 2

44、1.905 1. IRP document version number string (or “IRPVersion“): see 3GPP TS 32.311 26. IRP: See 3GPP TS 32.101 2. IRPAgent: See 3GPP TS 32.102 3. IRPManager: See 3GPP TS 32.102 3. Changed alarm: See 3GPP TS 32.391 6. Changed instance: See 3GPP TS 32.391 6. Delta Synchronisation: See 3GPP TS 32.391 6.

45、 Delta Synchronisation Point: See 3GPP TS 32.391 6. Full Synchronisation: See 3GPP TS 32.391 6. XML file: file containing an XML document XML document: composed of the succession of an optional XML declaration followed by a root XML element 14. XML declaration: it specifies the version of XML being

46、used, see 14. 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 followed by an XML end-tag, or composed simply of an XML empty-element tag; each

47、XML element may contain other XML elements, see 14. ETSI ETSI TS 132 396 V14.0.0 (2017-04)83GPP TS 32.396 version 14.0.0 Release 14empty 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

48、 the succession of an XML start-tag directly followed by an XML end-tag, or composed simply of an XML empty-element tag, see 14. 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 it

49、s XML start-tag and its XML end-tag, see 14. 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 14. 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, see 14. XML empty-element tag: composed simply of an empty-element tag containing the name and the set of XML attribute specifications of