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

1、 ETSI TS 132 666 V14.0.0 (2017-05) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Configuration Management (CM); Kernel CM Integration Reference Point (IRP); Solution Set (SS) definitions (3GPP TS 32.

2、666 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 132 666 V14.0.0 (2017-05)13GPP TS 32.666 version 14.0.0 Release 14Reference RTS/TSGS-0532666ve00 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 1

3、6 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 pri

4、nt. 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 P

5、ortable 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 https:/po

6、rtal.etsi.org/TB/ETSIDeliverableStatus.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, electro

7、nic or mechanical, 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 Teleco

8、mmunications Standards 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

9、 logo is protected 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 666 V14.0.0 (2017-05)23GPP TS 32.666 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present docum

10、ent 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, IPRs notified to ETSI in respect of

11、ETSI standards“, which 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 I

12、PRs 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 Project (3GPP). The present document may refer to tech

13、nical 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 be found under http:/webapp.etsi.org/key/queryfo

14、rm.asp. Modal verbs 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 “mus

15、t not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 132 666 V14.0.0 (2017-05)33GPP TS 32.666 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33

16、 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Solution Set definitions 7g3Annex A (normative): CORBA Solution Set . 8g3A.1 Architectural Features 8g3A.1.1 Syntax for Distinguished Names and Versions 8g3A.1.2 Notifications . 8g3A.1.3 Filter language 8g3A.2 Mapping .

17、8g3A.2.1 Operation and Notification mapping 8g3A.2.2 Operation parameter mapping 9g3A.2.3 Notification attribute mapping . 9g3A.3 Use of OMG Structured Event . 11g3A.4 Rules for NRM extensions . 17g3A.4.1 Extensions not allowed . 17g3A.5 Solution Set definitions 17g3A.5.1 IDL definition structure 17

18、g3A.5.2 IDL specification “KernelCmConstDefs.idl” . 18g3A.5.3 IDL specification “KernelCmIRPSystem.idl” 20g3A.5.4 IDL specification “KernelCmIRPNotifications.idl” . 21g3Annex B (normative): XML definitions . 24g3B.1 Architectural features . 24g3B.1.1 Syntax for Distinguished Names 24g3B.2 Mapping .

19、24g3B.3 Solution Set definitions 24g3B.3.1 XML definition structure 24g3B.3.2 Graphical Representation . 24g3B.3.3 XML Schema “kernelNtf.xsd” . 27g3Annex C (normative): SOAP Solution Set 30g3C.1 Architectural Features 30g3C.1.1 Syntax for Distinguished Names and versions . 30g3C.1.2 Notifications .

20、30g3C.1.3 IRP document version number string . 30g3C.2 Mapping . 31g3C.2.1 General mappings . 31g3C.2.2 Operation and Notification mapping 31g3ETSI ETSI TS 132 666 V14.0.0 (2017-05)43GPP TS 32.666 version 14.0.0 Release 14C.2.3 Operation parameter mapping 32g3C.2.3.1 Operation getNRMIRPVersion . 32g

21、3C.2.3.1.1 Input parameters 32g3C.2.3.1.2 Output parameters . 32g3C.2.2.1.3 Fault definition 32g3C.3 Solution Set definitions 33g3C.3.1 WSDL definition structure . 33g3C.3.2 Graphical Representation . 33g3C.3.3 WSDL specification “KernelCMIRPSystem.wsdl” . 34g3Annex D (informative): Change history 3

22、7g3History 38g3ETSI ETSI TS 132 666 V14.0.0 (2017-05)53GPP TS 32.666 version 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 fol

23、lowing 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 t

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

25、cument. Introduction The present document 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: Config

26、uration Management (CM); Kernel CM Information Service (IS). 32.666: Configuration Management (CM); Kernel CM Integration Reference Point (IRP); Solution Set (SS) definitions. Configuration Management (CM), in general, provides the operator with the ability to assure correct and effective operation

27、of the 3G network as it evolves. CM actions have the objective 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 p

28、art of an implementation programme (e.g. additions and 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

29、 involving actions on many resources/objects in one or several NEs. ETSI ETSI TS 132 666 V14.0.0 (2017-05)63GPP TS 32.666 version 14.0.0 Release 141 Scope The present document specifies the Solution Set definitions for the IRP whose semantics is specified in Kernel CM (Configuration Management) IRP:

30、 Information Service 3GPP TS 32.662 7. This Solution Set definitions specification is related to 3GPP TS 32.662 V13.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 (ide

31、ntified 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), a non-specific r

32、eference 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 and high level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.600: “Telecommunicatio

33、n management; Configuration Management (CM); Concept and 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

34、 Managed Objects“. 6 Object Management Group 98 (November 1998): “Notification Service: Joint Revised Submission OMG TC Document telecom/98-11-01“. 7 OMG CORBA Services (November 1996): “Common Object Services Specification“. 8 The Common Object Request Broker: Architecture and Specification (for sp

35、ecification of valid version, see 1). 9 3GPP TS 32.306: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Solution Set (SS) definitions“. 10 3GPP TS 32.111-6: “Telecommunication management; Fault Management; Part 3: Alarm Integration Refere

36、nce Point (IRP): Solution Set (SS) definitions“. 11 3GPP TS 32.312: “Telecommunication management; Generic Integration Reference Point (IRP) management: Information Service (IS)“. 12 3GPP TS 32.676: “Telecommunication management; Configuration Management (CM); State Management Integration Reference

37、Point (IRP): Solution Set (SS) definitions“. 13 3GPP TS 32.311: “Telecommunication management; Generic Integration Reference Point (IRP) management: Requirements“. 14 3GPP TS 32.336: “Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): Solution Set (SS) definitions

38、“. 15 3GPP TS 32.331: “Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): Requirements“. ETSI ETSI TS 132 666 V14.0.0 (2017-05)73GPP TS 32.666 version 14.0.0 Release 1416 3GPP TS 32.172: “Telecommunication management; Subscription Management (SuM) IRP; Network Res

39、ources Model (NRM)“. 17 3GPP TS 32.316: “Telecommunication management; Generic Integration Reference Point (IRP) management; Solution Set (SS) definitions“. 18 W3C SOAP 1.1 specification (http:/www.w3.org/TR/2000/NOTE-SOAP-20000508/) 19 W3C WSDL 1.1 specification (http:/www.w3.org/TR/2001/NOTE-wsdl-

40、20010315) 20 W3C XPath 1.0 specification (http:/www.w3.org/TR/1999/REC-xpath-19991116) 21 WS-I Basic Profile Version 1.1 (http:/www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html) 22 W3C SOAP 1.2 specification (http:/www.w3.org/TR/soap12-part1/) 3 Definitions and abbreviations 3.1 Definitions Fo

41、r the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 1, 3GPP TS 32.102 2, 3GPP TS 32.600 3, 3GPP TS 32.662 4 and 3GPP TS 32.33115 apply. IRP document version number string (or “IRPVersion“): See 3GPP TS 32.311 13. 3.2 Abbreviations For the purposes of the present

42、 document, the following abbreviations apply: CORBA Common Object Request Broker Architecture DN Distinguished Name IDL Interface Definition Language (OMG) IRP Integration Reference Point IS Information Service MO Managed Object MOC Managed Object Class NL Notification LogNRM Network Resource Model

43、OMG Object Management Group SS Solution Set UML Unified Modelling Language VSE Vendor Specific Extensions XML eXtensible Markup Language4 Solution Set definitions This specification defines the following 3GPP Kernel CM IRP Solution Set definitions: - 3GPP Kernel CM IRP CORBA SS (Annex A); - 3GPP Ker

44、nel CM IRP XML definitions (Annex B); - 3GPP Kernel CM IRP SOAP Solution Set (Annex C). ETSI ETSI TS 132 666 V14.0.0 (2017-05)83GPP TS 32.666 version 14.0.0 Release 14Annex A (normative): CORBA Solution Set This annex contains the CORBA Solution Set for the IRP whose semantics is specified in Kernel

45、 CM IRP: Information Service (TS 32.662 4). A.1 Architectural Features 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 CORBA SS. A.1.1 Syntax for Distinguished Names and Versions The sy

46、ntax 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 3.1). A.1.2 Notifications Notifications are sent according to the Notification IRP: CORBA SS (see 3GPP TS 32.303 9). The contents of the Kernel CM IRP notifications are de

47、fined in the present document. A.1.3 Filter language The filter language used in the SS is the Extended Trader Constraint Language (see OMG Notification Service 6). IRPAgents may throw a FilterComplexityLimit exception when a given filter is too complex. A.2 Mapping A.2.1 Operation and Notification

48、mapping The Kernel CM IRP: IS (see 3GPP TS 32.662 4) defines semantics of operation and notification visible across the Kernel Configuration Management IRP. The following table in this subclause indicates mapping of these operations and notifications to their equivalents defined in this SS. Table A.

49、2.1: Mapping from IS Notification/Operation to SS equivalents IS Operation/ notification (3GPP TS 32.662 4) SS Method Qualifier getNRMIRPVersion get_nrm_irp_version MnotifyObjectCreation See Notification IRP: CORBA SS 9 O notifyObjectDeletion See Notification IRP: CORBA SS 9 O notifyAttributeValueChange See Notification IRP: CORBA SS 9 O notifyStateChange See Notification IRP: CORBA SS 9 O getIRPVersion get_kernel_cm_irp_versions MgetOperationProfile get_kernel_cm_irp operations_profile O g