1、 ETSI TS 132 395 V9.1.0 (2012-01) Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Delta synchronization Integration Reference Point (IRP); eXtensible Markup Language (XML) file format definition (3GPP TS 32.
2、395 version 9.1.0 Release 9) Technical Specification ETSI ETSI TS 132 395 V9.1.0 (2012-01)13GPP TS 32.395 version 9.1.0 Release 9Reference RTS/TSGS-0532395v910 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 Sir
3、et N 348 623 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 o
4、r in print. 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 Secreta
5、riat. 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:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send
6、your comment 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 Sta
7、ndards Institute 2012. 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 a
8、re Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 395 V9.1.0 (2012-01)23GPP TS 32.395 version 9.1.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 ess
9、ential 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. Latest updat
10、es are available 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)
11、 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 identities
12、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. ETSI ETSI TS 132 395 V9.1.0 (2012-01)33GPP TS 32.395 version 9.1.0 Re
13、lease 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 Structure and content of configuration data XML files 7g34.1 Global structure 7g34.2 XML elements fi
14、leHeader and fileFooter . 8g34.2.1 XML elements fileHeaderForDeltaSynchForCM/AlarmData 8g34.2.2 XML element fileFooter . 9g34.3 Delta synchronisation IRP specific XML elements 10g34.4 Delta synchronisation IRP XML File Name Conventions . 10g3Annex A (normative): Delta synchronization specific data f
15、ile XML schemas 11g3A.1 Delta synchronization specific data file XML schemas Generic Part (file name “deltaSynchGeneric.xsd“) 11g3A.2 Delta synchronization specific data file XML schemas for CM data (file name “deltaSynchForCMData.xsd“) . 13g3A.3 Delta synchronization specific data file XML schemas
16、for alarm data (file name “deltaSynchForAlarms.xsd“) . 15g3Annex B (informative): Void . 17g3Annex C (informative): Change history . 18g3History 19g3ETSI ETSI TS 132 395 V9.1.0 (2012-01)43GPP TS 32.395 version 9.1.0 Release 9Foreword This Technical Specification has been produced by the 3rdGeneratio
17、n 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 with an identifying change of release date and
18、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 all changes of substance, i.e. technical enh
19、ancements, 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 Specification Group Services and System Aspect
20、s; Telecommunication management; as identified below: 32.391: Delta Synchronisation Integration Reference Point (IRP); Requirements 32.392: Delta Synchronisation Integration Reference Point (IRP); Information Service (IS) 32.393: Delta Synchronisation Integration Reference Point (IRP); Common Object
21、 Request Broker Architecture (CORBA) Solution Set 32.395: Delta Synchronization Integration Reference Point (IRP); eXtensible Markup Language (XML) file format definition The Itf-N interface is built up by a number of IRPs and a related Name Convention, which realise the functional capabilities over
22、 this interface. The basic structure of the IRPs is defined in TS 32.101 1 and TS 32.102 2. 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
23、 done. This IRP provides functionality to significantly reduce the amount of data which needs to be transferred in order to re-establish synchronisation. ETSI ETSI TS 132 395 V9.1.0 (2012-01)53GPP TS 32.395 version 9.1.0 Release 91 Scope The purpose of Delta Synchronisation IRP is to define an inter
24、face through which an IRPManager can request only those data which changed (i.e. changed, were created or deleted) from a synchronisation point onwards. The present document is the eXtensible Markup Language (XML) file format definition of Delta Synchronisation IRP for the IRP whose semantics is spe
25、cified in Delta Synchronisation IRP: Information Service (3GPP TS 32.392 11). This XML Definitions specification defines the XML syntax of the Delta Synchronisation IRP XML Data File. This XML Definitions specification is related to 3GPP TS 32.392 V9.0.X. 2 References The following documents contain
26、 provisions that, 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, subsequent revisions do not apply. For a non-specific r
27、eference, 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: “Telecommunication management; Principles a
28、nd high level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.342: “Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Information Service (IS)“. 4 W3C REC-xml-20001006: “Extensible Markup Language (XML) 1.0 (Second Edition
29、)“. 5 W3C REC-xmlschema-0-20010502: “XML Schema Part 0: Primer“. 6 W3C REC-xmlschema-1-20010502: “XML Schema Part 1: Structures“. 7 W3C REC-xmlschema-2-20010502: “XML Schema Part 2: Datatypes“. 8 W3C REC-xml-names-19990114: “Namespaces in XML“. 10 3GPP TS 32.391: “Configuration Management (CM); Delt
30、a Synchronisation Integration Reference Point (IRP): Requirements“. 11 3GPP TS 32.392: “Configuration Management (CM); Delta Synchronisation Integration Reference Point (IRP): Information Service (IS)“. 12 3GPP TS 32.305: “Telecommunication management; Configuration Management (CM); Notification Int
31、egration Reference Point (IRP): eXtensible Markup Language (XML) definitions“. 13 3GPP TS 32.111-5: “Telecommunication management; Fault Management; Part 5: Alarm Integration Reference Point (IRP): eXtensible Markup Language (XML) definitions“. 14 3GPP TS 32.615: “Telecommunication management; Confi
32、guration Management (CM); Bulk CM Integration Reference Point (IRP): eXtensible Markup Language (XML) definitions“. 15 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“. ETSI ETSI TS 132 395 V9.1.0 (2012-01)63GPP TS 32.395 version 9.1.
33、0 Release 93 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: Changed alarm: See 3GPP TS 32.391 10. Changed instance: See 3GPP TS 32.391 10. Delta Synchronisation: See 3GPP TS 32.391 10. Delta Synchronisation Point: Se
34、e 3GPP TS 32.391 10. Full Synchronisation: See 3GPP TS 32.391 10. IRP: See 3GPP TS 32.101 1. IRPAgent: See 3GPP TS 32.102 2. IRPManager: See 3GPP TS 32.102 2. XML file: file containing an XML document XML document: composed of the succession of an optional XML declaration followed by a root XML elem
35、ent 4. XML declaration: it specifies the version of XML being used, see 4. 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 e
36、nd-tag, or composed simply of an XML empty-element tag; each XML element may contain other XML elements, see 4. 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 the succession of
37、an XML start-tag directly followed by an XML end-tag, or composed simply of an XML empty-element tag, see 4. 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
38、its XML end-tag, see 4. 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 4. XML end-tag: the end of a non-empty XML element is marked by an XML end-tag containing the name of
39、the XML element, see 4. 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 4. XML attribute specification: has a name and a value, see 4. DTD: defines structure and content constraints to be respected
40、 by an XML document to be valid with regard to this DTD, see 4. 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 be used together
41、 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 5, 6 and 7. XML namespace: enables qualifying element and attribute names used in XML documents by associating them with namespaces identified by different XML schemas,
42、 see 5, 6 and 7. ETSI ETSI TS 132 395 V9.1.0 (2012-01)73GPP TS 32.395 version 9.1.0 Release 9XML 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 complex type; ultimatel
43、y defines constraints for an XML element on its XML attribute specifications and/or its XML content, see 5, 6 and 7. 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 att
44、ribute specifications and/or its XML content; can also be the concrete type or the derivation base type for another XML element type, see 5, 6 and 7. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: EM Element Manager IRP Integration Reference Point IS I
45、nformation Service (see 3GPP TS 32.101 1) Itf-N Interface N NE Network Element XML eXtensible Mark-up Language 4 Structure and content of configuration data XML files Annex A of the present document defines the delta synchronization-specific XML schema and element types in deltaSynchForCMData.xsd /
46、deltaSynchForAlarms.xsd which shall be used for the files of which the locations can be supplied as an option in output of operation triggerDeltaSynchOfCMData or triggerDeltaSynchOfAlarms defined in 3GPP TS 32.392 11. The present schema re-uses the structure and content of 3GPP TS 32.615 14 for delt
47、a synchronization for CM data and those of 3GPP TS 32.111-5 13 for delta synchronization for alarm data. The differences or additions are listed here: For delta synchronization for CM data: The modifier XML attribute specification shall be used as follows: Create for all created NRM instances Update
48、 for all modified NRM instances Delete for all deleted NRM instances For delta synchronization for alarm data: Created alarms shall be indicated by content XML elements of type=“xa:NotifyNewAlarm” Changed alarms shall be indicated by content XML elements of type=“xa:NotifyChangedAlarm” or of type=“x
49、a:NotifyClearedAlarm” or of type=“xa:NotifyComments” Deleted alarms shall be indicated by content XML elements of type=“xa:NotifyAckStateChanged” 4.1 Global structure See 3GPP TS 32.615 14 The following XML namespaces are potentially used in delta synchronisation XML files: delta synchronisation for CM data files are associated with XML schema deltaSynchForCMData.xsd (see Annex A.1); delta synchronisation for alarm data files are associated with XML sc
