ETSI TS 132 397-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Delta synchronization .pdf

1、 ETSI TS 132 397 V9.0.0 (2010-04)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Telecommunication management;Delta synchronization Integration Reference Point (IRP);SOAP Solution Set (SS) (3GPP TS 32.397 version 9.0

2、.0 Release 9)ETSI ETSI TS 132 397 V9.0.0 (2010-04)13GPP TS 32.397 version 9.0.0 Release 9Reference DTS/TSGS-0532397v900 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 562 00017 - NAF 742 C Ass

3、ociation 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 or in print. In any case of existing or

4、 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 Secretariat. Users of the present document sh

5、ould 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 your comment to one of the following s

6、ervices: 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 Standards Institute 2010. All rights rese

7、rved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently be

8、ing registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 397 V9.0.0 (2010-04)23GPP TS 32.397 version 9.0.0 Release 9Intellectual Property Rights IPRs essential or potentia

9、lly essential to the present document may have 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, IP

10、Rs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guara

11、ntee 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) 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 Projec

12、t (3GPP). The present document may refer to technical specifications 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

13、be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 132 397 V9.0.0 (2010-04)33GPP TS 32.397 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions, symbols and abbreviations . 5g33.1 Defini

14、tions 5g33.2 Abbreviations . 6g34 Architectural features . 6g34.1 General . 6g35 Mapping . 7g35.1 Operation and notification mapping . 7g35.2 Operation parameter mapping 7g35.3 Notification parameter mapping . 8g3Annex A (normative): WSDL specifications 9g3Annex B (informative): Change history . 16g

15、3History 17g3ETSI ETSI TS 132 397 V9.0.0 (2010-04)43GPP TS 32.397 version 9.0.0 Release 9Foreword 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 followin

16、g 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 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

17、 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 enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the documen

18、t. Introduction The present document is part of a TS-family covering the 3rdGeneration Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Communication Surveillance management Integration Reference Point (IRP), as identified below: 32.391: “

19、Delta Synchronization Integration Reference Point (IRP); Requirements“ 32.392: “Delta Synchronization Integration Reference Point (IRP): Information Service (IS)“ 32.393: “Delta Synchronization Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)“ 32

20、.395: “Delta Synchronization Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition“ 32.397: “Delta Synchronization Integration Reference Point (IRP): SOAP Solution Set (SS)“ The Itf-N interface is built up by a number of IRPs and a related Name Convention, which

21、realise the functional capabilities 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 cer

22、tain scenarios this synchronization 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 397 V9.0.0 (2010-04)53GPP TS 32.397 version 9.0.0 Release 91 Scope The present

23、 document specifies the SOAP SS 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 V9.0.X. 2 References The following documents contain provisions which, through reference in this text, constitute

24、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 reference, the latest version applies. In the case of a

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

26、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 definitions“. 5 3GPP TS 32.392: “Telecommunication management; Delta Synchronization Integration Reference Poin

27、t (IRP): Information Service (IS)“. 6 3GPP TS 32.395: “Telecommunication management; Delta Synchronization Integration Reference Point (IRP); eXtensible Markup Language (XML) file format definition “. 7 W3C SOAP 1.1 specification (http:/www.w3.org/TR/2000/NOTE-SOAP-20000508/) 8 W3C XPath 1.0 specifi

28、cation (http:/www.w3.org/TR/1999/REC-xpath-19991116) 9 W3C WSDL 1.1 specification (http:/www.w3.org/TR/2001/NOTE-wsdl-20010315) 10 W3C SOAP 1.2 specification (http:/www.w3.org/TR/soap12-part1/) 11 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the

29、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: See 3GPP TS 32.101 2. IRPAgent: See 3GPP TS 32.102 3. IRPManager: See 3GP

30、P TS 32.102 3. ETSI ETSI TS 132 397 V9.0.0 (2010-04)63GPP TS 32.397 version 9.0.0 Release 93.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 1, in 3GPP TS 32.101 2, 3GPP TS 32.102 3, 3GPP TS 32.150 4, and the following apply. An abbreviation defined in

31、the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 1. IRP Integration Reference Point IS Information Service NE Network ElementNM Network Management 4 Architectural features 4.1 General The overall architectural feature of the Delta Synchronisati

32、on IRP is specified in 3GPP TS 32.392 5. This clause specifies features that are specific to the SOAP solution set. The SOAP 1.1 specification 7 and WSDL 1.1 specification 9 are supported. The SOAP 1.2 specification 10 is supported optionally. This specification uses “document“ style in WSDL file. T

33、his specification uses “literal“ encoding style in WSDL file. The filter language used in the SS is the XPath Language (see W3C XPath 1.0 specification 8). IRPAgents may throw a FilterComplexityLimit fault when a given filter is too complex. Relevant definitions are imported from the Delta Synchroni

34、sation IRP XML definitions of 3GPP TS 32.395 6. This specification uses a number of namespace prefixes throughout that are listed in Table 4.1. 1. Table 4.1.1: Prefixes and Namespaces used in this specification PREFIX NAMESPACE (no prefix) http:/schemas.xmlsoap.org/wsdl/ soap http:/schemas.xmlsoap.o

35、rg/wsdl/soap/deltaSynchIRPSystem http:/www.3gpp.org/ftp/Specs/archive/32_series/32.397#DeltaSynchIRPSystem deltaSynchIRPData http:/www.3gpp.org/ftp/Specs/archive/32_series/32.397#DeltaSynchIRPData xn http:/www.3gpp.org/ftp/specs/archive/32_series/32.625#genericNrm genericIRPSystem http:/www.3gpp.org

36、/ftp/Specs/archive/32_series/32.317/schema/32317-810/GenericIRPSystem ntfIRPNtfSystem http:/www.3gpp.org/ftp/Specs/archive/32_series/32.307/schema/32307-810/ notification/NotificationIRPNtfSystem The WSDL structure is depicted in Figure 4.1.1 below, depicting port type, binding and service. The port

37、 type contains port type operations, which again contains input, output and fault messages. The binding contains binding operations, which have the same name as the port type operations. The binding connects to a port inside the service. ETSI ETSI TS 132 397 V9.0.0 (2010-04)73GPP TS 32.397 version 9

38、.0.0 Release 9DeltaSynchIRPService NotificationIRPNtfPort GenericIRPPort DeltaSynchGenericPartsPort Port Types Bindings Services GenericIRPBinding (from 32.317) NotificationIRPNtf (from 32.307) DeltaSynchGenericParts manageDeltaSynchronization getAvailableDeltaSynchPoints DeltaSynchGenericParts mana

39、geDeltaSynchronization getAvailableDeltaSynchPoints DeltaSynchOfCMData triggerDeltaSynchOfCMData DeltaSynchOfCMData triggerDeltaSynchOfCMData DeltaSynchOfCMDataPort DeltaSynchOfAlarmData triggerDeltaSynchOfAlarms DeltaSynchOfAlarmData triggerDeltaSynchOfAlarms DeltaSynchOfAlarmDataPort Figure 4.1.1:

40、 Delta Synchronisation IRP SOAP Solution Set WSDL structure 5 Mapping 5.1 Operation and notification mapping The Delta Synchronisation IRP IS (3GPP TS 32.392 5) defines semantics of operation and notification visible across the Itf-N. Table 5.1.1 indicates mapping of these operations and notificatio

41、ns to their equivalents defined in this SS. Table 5.1.1: Mapping from IS Operation to SS Equivalents IS Operation / Notification (3GPP TS 32.392) SS Method SS Port Qualifier manageDeltaSynchronization manageDeltaSynchronization DeltaSynchGenericPartsPort M getAvailableDeltaSynchPoints getAvailableDe

42、ltaSynchPoints DeltaSynchGenericPartsPort O triggerDeltaSynchOfCMData triggerDeltaSynchOfCMData DeltaSynchOfCMDataPort O triggerDeltaSynchOfAlarms triggerDeltaSynchOfAlarms DeltaSynchOfAlarmDataPort O notifyStatusOfDeltaSynchronization notify (note 1) NotificationIRPNtfPort MnotifyNewDeltaSynchPoint

43、 notify (note 1) NotificationIRPNtfPort O NOTE 1: The IS equivalent maps to an XML definition specified in 3GPP TS 32.395 6, and this being an input parameter to the operation notify under the port type ntfIRPNtfSystem:NotificationIRPNtf and under the binding ntfIRPNtfSystem:NotificationIRPNtf of 3G

44、PP TS 32.307 11. 5.2 Operation parameter mapping The Delta Synchronisation IRP IS (3GPP TS 32.392 5) defines semantics of parameters carried in the operations. The tables below show the mapping of these parameters, as per operation, to their equivalents defined in this SS. Table 5.2.1: Mapping from

45、IS manageDeltaSynchronization parameters to SS equivalents IS Operation parameter SS Method parameter Qualifier managerReference managerReference MmanageDeltaSynchForAlarmData manageDeltaSynchForAlarmData CM manageDeltaSynchForCMData manageDeltaSynchForCMData CM status status METSI ETSI TS 132 397 V

46、9.0.0 (2010-04)83GPP TS 32.397 version 9.0.0 Release 9Table 5.2.2: Mapping from IS getAvailableDeltaSynchPoints parameters to SS equivalents IS Operation parameter SS Method parameter Qualifier managerReference managerReference OsynchPointsForCMDataRequested synchPointsForCMDataRequested CM synchPoi

47、ntsForAlarmDataRequested synchPointsForAlarmDataRequested CM synchPointListForAlarms synchPointListForAlarms CMsynchPointListForCMData synchPointListForCMData CM status status MTable 5.2.3: Mapping from IS triggerDeltaSynchOfCMData parameters to SS equivalents IS Operation parameter SS Method parame

48、ter Qualifier managerReference managerReference O dataRequested dataRequested ObaseMOInstance baseMOInstance O scope scope OsynchPoint synchPoint M deltaLists deltaLists CMnewSynchPoint newSynchPoint CM status status MTable 5.2.4: Mapping from IS triggerDeltaSynchOfAlarms parameters to SS equivalent

49、s IS Operation parameter SS Method parameter Qualifier managerReference managerReference M dataRequested dataRequested MbaseMOInstance baseMOInstance O scope scope OsynchPoint synchPoint M deltaLists deltaLists CMnewSynchPoint newSynchPoint CM status status M5.3 Notification parameter mapping The Delta Synchronisation IRP Notifications are defined in 32.395 6. ETSI ETSI TS 132 397 V9.0.0 (2010-04)93GPP TS 32.397 version 9.0.0 Release 9Annex A (normative): WSDL specifications ETSI ETSI TS 13