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

《ETSI TS 132 667-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Configuration Manageme.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 132 667-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Configuration Manageme.pdf（16页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 132 667 V9.0.0 (2010-01)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Telecommunication management;Configuration Management (CM);Kernel CM Integration Reference Point (IRP);SOAP Solution Set (SS) (3GPP TS

2、32.667 version 9.0.0 Release 9)ETSI ETSI TS 132 667 V9.0.0 (2010-01)13GPP TS 32.667 version 9.0.0 Release 9Reference RTS/TSGS-0532667v900 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 000

3、17 - 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 or in print. In any c

4、ase 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 Secretariat. Users of the p

5、resent 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 your comment to one

6、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 Standards Institute 201

7、0. All rights reserved. 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

8、 ETSI currently being 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 667 V9.0.0 (2010-01)23GPP TS 32.667 version 9.0.0 Release 9Intellectual Property Rights IPRs ess

9、ential or potentially 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 potenti

10、ally Essential, IPRs 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

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

12、Partnership Project (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 ET

13、SI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 132 667 V9.0.0 (2010-01)33GPP TS 32.667 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33

14、.1 Definitions 6g33.2 Abbreviations . 6g34 IRP document version number string . 6g35 Architectural features . 6g35.1 General . 6g35.2 Notifications . 7g35.3 Syntax for Distinguished Names and Versions 7g36 Mapping . 7g36.1 General mappings . 7g36.2 Operation and Notification mapping 8g36.3 Operation

15、 parameter mapping 8g36.3.1 Operation getNRMIRPVersion . 8g36.3.1.1 Input parameters 8g36.3.1.2 Output parameters . 8g36.3.1.3 Fault definition 9g3Annex A (normative): WSDL Specification . 10g3Annex B (informative): Void . 13g3Annex C (informative): Change history . 14g3History 15g3ETSI ETSI TS 132

16、667 V9.0.0 (2010-01)43GPP TS 32.667 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 following formal TSG approval. Should

17、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 for approval; 3 or greater in

18、dicates 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 document. Introduction The present do

19、cument is part of a TS-family covering the 3rdGeneration Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below: 32.661: “Configuration Management (CM); Kernel CM; Requirements“. 32.662: “Configuration Management (CM); Kernel

20、 CM; Information Service (IS)“. 32.663: “Configuration Management (CM); Kernel CM Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)“. 32.665 Configuration Management (CM); Kernel CM Integration Reference Point (IRP): eXtensible Markup Language (XM

21、L) definitions. 32.667: “Configuration Management (CM); Kernel CM Integration Reference Point (IRP): SOAP solution set“. Configuration Management (CM), in general, provides the operator with the ability to assure correct and effective operation of the 3G network as it evolves. CM actions have the ob

22、jective to control and monitor the actual configuration on the Network Elements (NEs) and Network Resources (NRs), and they may be initiated by the operator or by functions in the Operations Systems (OSs) or NEs. CM actions may be requested as part of an implementation programme (e.g. additions and

23、deletions), as part of an optimisation programme (e.g. modifications), and to maintain the overall Quality of Service (QoS). The CM actions are initiated either as single actions on single NEs of the 3G network, or as part of a complex procedure involving actions on many resources/objects in one or

24、several NEs. ETSI ETSI TS 132 667 V9.0.0 (2010-01)53GPP TS 32.667 version 9.0.0 Release 91 Scope The purpose of the present document is to define the mapping of the Kernel CM IRP: IS (3GPP TS 32.662 4) to the protocol specific details necessary for implementation of this IRP in a SOAP/WSDL environme

25、nt. This Solution Set specification is related to 3GPP TS 32.662 V9.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, ve

26、rsion 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), a non-specific reference implicitly refers to the latest version of th

27、at document in the same Release as the present document. 1 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.600: “Telecommunication management; Configuration Management (CM); Concept a

28、nd high-level requirements“. 4 3GPP TS 32.662: “Telecommunication management; Configuration Management (CM); Kernel CM; Information Service (IS)“. 5 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“. 6 3GPP TS 32.311: “Telecommunicatio

29、n management; Generic Integration Reference Point (IRP) management; Information Service (IS)“. 7 3GPP TS 32.172: “Telecommunication management; Subscription Management (SuM) IRP; Network Resources Model (NRM)“ 8 3GPP TS 32.317: “Telecommunication management; Generic Integration Reference Point (IRP)

30、 management; SOAP solution set“. 9 3GPP TS 32.307: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): SOAP solution set“. 10 W3C SOAP 1.1 specification (http:/www.w3.org/TR/2000/NOTE-SOAP-20000508/) 11 W3C WSDL 1.1 specification (http:/www.w

31、3.org/TR/2001/NOTE-wsdl-20010315) 12 W3C XPath 1.0 specification (http:/www.w3.org/TR/1999/REC-xpath-19991116) 13 WS-I Basic Profile Version 1.1 (http:/www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html) 14 W3C SOAP 1.2 specification (http:/www.w3.org/TR/soap12-part1/) 15 3GPP TS 32.665: “Teleco

32、mmunication management; Configuration Management (CM); Kernel CM; eXtensible Markup Language (XML) definition“. ETSI ETSI TS 132 667 V9.0.0 (2010-01)63GPP TS 32.667 version 9.0.0 Release 93 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definiti

33、ons given in 3GPP TS 32.101 1, 3GPP TS 32.102 2, 3GPP TS 32.600 3 and 3GPP TS 32.662 4 apply. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: DN Distinguished Name IRP Integration Reference Point IS Information Service MO Managed Object MOC Managed Obje

34、ct Class NRM Network Resource Model SS Solution Set WSDL Web Service Description Language WS-I Web Services Interoperability Organization 4 IRP document version number string The IRP document version number (sometimes called “IRPVersion“ or “SS version number“) string is used to identify this specif

35、ication. The string is derived using a rule described in 3GPP TS 32.311 6. The value of this string is defined by a constant in annex A. This string (or sequence of strings, if more than one version is supported) is returned in getIRPVersion method and is carried in the first field of the notificati

36、on header of all notifications related to this IRP. 5 Architectural features 5.1 General The overall architectural feature of Kernel Configuration Management IRP is specified in 3GPP TS 32.662 4. This clause specifies features that are specific to the SOAP SS. The SOAP 1.1 specification 10 and WSDL

37、1.1 specification 13 are supported. The SOAP 1.2 specification 14 is supported optionally. This specification uses “document“ style in WSDL file. This specification uses “literal“ encoding style in WSDL file. This specification uses a number of namespace prefixes throughout that are listed in Table

38、5.1. ETSI ETSI TS 132 667 V9.0.0 (2010-01)73GPP TS 32.667 version 9.0.0 Release 9Table 5.1: Prefixes and Namespaces used in this specification PREFIX NAMESPACE http http:/schemas.xmlsoap.org/wsdl/http/ soap http:/schemas.xmlsoap.org/wsdl/soap/SOAP-ENV http:/schemas.xmlsoap.org/soap/envelope/ SOAP-EN

39、C or soapenc http:/schemas.xmlsoap.org/soap/encoding/ xs or xsd http:/www.w3.org/2001/XMLSchema xsi http:/www.w3.org/2001/XMLSchema-instance kernelCMIRPSystem http:/www.3gpp.org/ftp/Specs/archive/32_series/32.667/schema/32667-800/KernelCMIRPSystem kernelCMIRPData http:/www.3gpp.org/ftp/Specs/archive

40、/32_series/32.667/schema/32667-800/KernelCMIRPData ntfIRPSystem http:/www.3gpp.org/ftp/Specs/archive/32_series/32.307/schema/32307-800/notification/NotificationIRPNtfSystem genericIRPSystem http:/www.3gpp.org/ftp/Specs/archive/32_series/32.317/schema/32317-800/GenericIRPSystem The WSDL structure is

41、like Figure 5.1: Figure 5.1: kernelCM IRP SOAP Solution Set WSDL structure 5.2 Notifications Notifications are sent according to the Notification IRP: SOAP SS (see 3GPP TS 32.307 9). The contents of the Kernel CM IRP notifications are defined in KernelCM IRP XML definition 15. 5.3 Syntax for Disting

42、uished Names and Versions The format of a Distinguished Name is defined in 3GPP TS 32.300 5. The version of this IRP is represented as a string (see also clause 4). 6 Mapping 6.1 General mappings The IS parameter name managedObjectInstance is mapped into DN. Attributes modelling associations as defi

43、ned in the NRM (here also called “reference attributes“) are in this SS mapped to attributes. The names of the reference attributes in the NRM are mapped to the corresponding attribute names in the MOC. When the cardinality for an association is 01 or 11 the datatype for the reference attribute is d

44、efined as an MOReference. The value of an MO reference contains the distinguished name of the associated MO. When the cardinality for an association allows more than one referred MO, the reference attribute will be of type MOReferenceSet, which contains a sequence of MO references. If a reference at

45、tribute is changed, an AttributeValueChange notification is emitted. ETSI ETSI TS 132 667 V9.0.0 (2010-01)83GPP TS 32.667 version 9.0.0 Release 96.2 Operation and Notification mapping The Kernel CM IRP: IS (see 3GPP TS 32.662 4) defines semantics of operation and notification visible across the Kern

46、el Configuration Management IRP. The following table in this subclause indicates mapping of these operations and notifications to their equivalents defined in this SS. Table 6.2: Mapping from IS Notification/Operation to SS equivalents IS Operation/ notification (3GPP TS 32.662 4) SS Operation Quali

47、fier getNRMIRPVersion getNRMIRPVersion MnotifyObjectCreation ntfIRPSystem:notify (note 2) O notifyObjectDeletion ntfIRPSystem:notify (note 2) O notifyAttributeValueChange ntfIRPSystem:notify (note 2) O notifyCMSynchronizationRecommended ntfIRPSystem:notify (note 2) O notifyStateChange ntfIRPSystem:n

48、otify (note 2) O getIRPVersion(see note 1) getIRPVersion M getOperationProfile(see note 1) getOperationProfile O getNotificationProfile(see note 1) getNotificationProfile O NOTE 1: This operation is of IOC ManagedGenericIRP specified in 10. The IOC KernelCmIRP of 4 inherits from it. NOTE 2: The IS e

49、quivalent is mapped into parameters of ntfIRPSystem:notify. 6.3 Operation parameter mapping The Kernel CM IRP: IS (3GPP TS 32.662 4) defines semantics of parameters carried in operations across the Kernel Configuration Management IRP. The tables below show the mapping of these parameters, as per operation, to their equivalents defined in this SS. 6.3.1 Operation getNRMIRPVersion 6.3.1.1 Input parameters None. Here is the XML schema fragment of the getNRMIRPVersion request: 6.3.1.2 Output p