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

1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelTelecommDelta synchronizationSolutio(3GPP TS 32.3TECHNICAL SPECIFICATION132 396 V13.0.0 (2016communications system (Phaelecommunications System (LTE; munication management; ion Integration Reference Pointion Set (SS) definitions .396 version 13.0.

2、0 Release 1316-02) hase 2+); (UMTS); oint (IRP); 13) ETSI ETSI TS 132 396 V13.0.0 (2016-02)13GPP TS 32.396 version 13.0.0 Release 13Reference RTS/TSGS-0532396vd00 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

3、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 versions and/or in print

4、. 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 the print of the Por

5、table 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 available at http:/porta

6、l.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, electronic or mecha

7、nical, 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 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. GSM and the GSM lo

9、go are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 396 V13.0.0 (2016-02)23GPP TS 32.396 version 13.0.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to th

10、ese 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. Lates

11、t 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 ETSI We

12、b 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, UMTS id

13、entities 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“, “sh

14、all 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 in dire

15、ct citation. ETSI ETSI TS 132 396 V13.0.0 (2016-02)33GPP TS 32.396 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 Definitions 7g33.2 Abbreviat

16、ions . 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 Push and Pull Style . 9g3A.1.4 Support multiple notifications in one push operation . 9g3A.1.5 Delta Sync

17、hronization 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 11g3A.2.4 Notification parameter mapping . 13g3A.3 Solution Set definitions 17g3A.3.1 IDL definition structu

18、re 17g3A.3.2 IDL specification (file name “DeltaSynchronizationConstDefs.idl“) . 18g3A.3.3 IDL specification (file name “DeltaSynchronizationSystem.idl“) 28g3A.3.4 IDL specification (file name “DeltaSynchronizationNotifications.idl“) . 33g3Annex B (normative): XML definitions . 37g3B.1 Architectural

19、 Features 37g3B.1.1 Syntax for Distinguished Names 37g3B.1.2 Notification Services 37g3B.1.3 IOC definitions . 37g3B.2 Mapping . 37g3B.3 Solution Set definitions 37g3B.3.1 XML definition structure 37g3B.3.1.1 Global structure 38g3B.3.1.2 XML elements fileHeader and fileFooter . 38g3B.3.1.2.1 XML ele

20、ments fileHeaderForDeltaSynchForCM/AlarmData . 38g3B.3.1.2.2 XML element fileFooter . 41g3B.3.1.3 Delta synchronisation IRP specific XML elements 42g3B.3.1.4 Delta synchronisation IRP XML File Name Conventions 42g3B.3.2 Graphical Representation . 43g3B.3.3 XML Schema . 46g3B.3.3.1 XML Schema “deltaS

21、ynchGeneric.xsd“ . 46g3ETSI ETSI TS 132 396 V13.0.0 (2016-02)43GPP TS 32.396 version 13.0.0 Release 13B.3.3.2 XML Schema “deltaSynchForCMData.xsd“ 49g3B.3.3.3 XML Schema “deltaSynchForAlarms.xsd“ 51g3Annex C (normative): SOAP Solution Set . 53g3C.1 Architectural features . 53g3C.1.1 Syntax for Disti

22、nguished Names 53g3C.1.2 Notification Services 53g3C.1.3 Supported W3C specifications . 53g3C.1.4 Prefixes and namespaces 53g3C.2 Mapping . 54g3C.2.1 Operation and notification mapping . 54g3C.2.2 Operation parameter mapping 54g3C.2.3 Notification parameter mapping . 55g3C.3 Solution Set definitions

23、 55g3C.3.1 WSDL definition structure . 55g3C.3.2 Graphical Representation . 55g3C.3.3 WSDL specification DeltaSynchIRPSystem.wsdl 56g3Annex D (informative): Change history . 70g3History 71g3ETSI ETSI TS 132 396 V13.0.0 (2016-02)53GPP TS 32.396 version 13.0.0 Release 13Foreword This Technical Specifi

24、cation 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 will be re-released by the TSG wit

25、h 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 the second digit is incremented for

26、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 3rdGeneration Partnership Project; Technical Sp

27、ecification 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“ 32.392: “Delta Synchronization Integration Refere

28、nce 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 capabilities over this interface. The basic structure

29、 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 synchronization is lost or not done. This IRP provides f

30、unctionality to significantly reduces the amount of data which needs to be transferred in order to re-establish synchronization. ETSI ETSI TS 132 396 V13.0.0 (2016-02)63GPP TS 32.396 version 13.0.0 Release 131 Scope The present document specifies the Solution Set definitions for the IRP whose semant

31、ics is specified in Delta Synchronization IRP IS (3GPP TS 32.392 5). This Solution Set specification is related to 3GPP TS 32.392 V12.0.X. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are ei

32、ther 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 reference to a 3GPP document (including a GSM document)

33、, 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 high level requirements“. 3 3GPP TS 32.102: “Teleco

34、mmunication 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 (IRP): Information Service (IS)“. 6 3GPP TS 32.391: “

35、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 (IS)“. 8 3GPP TS 32.622: “Telecommunication manag

36、ement; 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 Service (IS)“. 10 3GPP TS 32.602: “Telecommunication ma

37、nagement; 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): Solution Set definitions “. 12 OMG TC Document t

38、elecom/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: “Extensible Markup Language (XML) 1.0 (Second Edition)“. 15

39、 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 V13.0.0 (2016-02)73GPP TS 32.396 version 13.0.0 Release 1317 W3C REC-xmlschema-2-20010502: “XML Schema Part 2: Datatypes“. 18 W3C REC-xml-names-19990114:

40、 “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); Bulk CM Integration Reference Point (IRP): Solution

41、 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 (http:/www.w3.org/TR/1999/REC-xpath-19991116) 24 W3C

42、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 Definitions and abbreviations 3.1 Definitions For the p

43、urposes 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 21.905 1. IRP document version number string (or “I

44、RPVersion“): 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. Delta Synchronisation Point: See 3GPP TS 32.391 6

45、. 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 used, see 14. XML element: has a type, is identifi

46、ed 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 XML element may contain other XML elements, see 14

47、. ETSI ETSI TS 132 396 V13.0.0 (2016-02)83GPP TS 32.396 version 13.0.0 Release 13empty 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 the succession of an XML start-tag directly follo

48、wed 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 its XML start-tag and its XML end-tag, see 14. XML s

49、tart-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 the XML element, see 14. XML attribute specifi