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

1、 ETSI TS 132 676 V12.0.0 (2014-10) Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP); Solution Set (SS) definitions (3GPP TS 32

2、.676 version 12.0.0 Release 12) TECHNICAL SPECIFICATION ETSI ETSI TS 132 676 V12.0.0 (2014-10)13GPP TS 32.676 version 12.0.0 Release 12Reference RTS/TSGS-0532676vc00 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 4

3、7 16 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 The present document may be made available in electronic versions and/or in print. The conten

4、t 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 Portable Docume

5、nt 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:/portal.etsi.org/t

6、b/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including pho

7、tocopying 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 Standards Institute

8、 2014. 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 are Trade Marks r

9、egistered and owned by the GSM Association. ETSI ETSI TS 132 676 V12.0.0 (2014-10)23GPP TS 32.676 version 12.0.0 Release 12Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs,

10、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 updates are availa

11、ble 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) which are, o

12、r 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 or GSM identi

13、ties. 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“, “shall not“, “should“, “s

14、hould not“, “may“, “may not“, “need“, “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 direct

15、citation. ETSI ETSI TS 132 676 V12.0.0 (2014-10)33GPP TS 32.676 version 12.0.0 Release 12Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviation

16、s . 7g33.3 IRP document version number string . 7g34 Solution Set definitions 7g3Annex A (normative): CORBA Solution Set . 8 g3A.1 Architectural Features 8g3A.1.1 Syntax for Distinguished Names 8g3A.2 Mapping . 8g3A.2.1 IOC Mapping 8g3A.2.2 Mapping of Attributes 8g3A.3 Solution Set definitions 9g3A.

17、3.1 IDL definition structure 9g3A.3.2 IDL specification “StateManagementIRPConstDefs.idl”. 10g3A.3.3 IDL specification “StateManagementIRPOptConstDefs.idl” . 12g3A.3.4 IDL specification “StateManagementIRPCommonConstDefs.idl” 14g3Annex B (normative): XML definitions . 16g3B.1 Architectural features

18、. 16g3B.1.1 Syntax for Distinguished Names 16g3B.2 Mapping . 16g3B.3 Solution Set definitions 16g3B.3.1 XML definition structure 16g3B.3.2 XML schema “stateManagementIRP.xsd” . 17g3Annex C (Informative): Change history . 19g3History 20g3ETSI ETSI TS 132 676 V12.0.0 (2014-10)43GPP TS 32.676 version 1

19、2.0.0 Release 12Foreword This Technical Specification (TS) 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 pre

20、sent 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 indicates TSG approved document under ch

21、ange 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 document is part of a TS-family covering

22、 the 3rdGeneration Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below: 32.671: Configuration Management (CM); State Management Integration Reference Point (IRP); Requirements 32.672: Configuration Management (CM); State M

23、anagement Integration Reference Point (IRP); Information Service (IS) 32.676 Configuration Management (CM); State Management Integration Reference Point (IRP); Solution Set (SS) definitions Configuration Management (CM), in general, provides the operator with the ability to assure correct and effect

24、ive operation 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

25、requested as part of a deployment program (e.g. additions and deletions), as part of an optimisation program (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 proc

26、edure involving actions on many resources/objects in one or several NEs. ETSI ETSI TS 132 676 V12.0.0 (2014-10)53GPP TS 32.676 version 12.0.0 Release 121 Scope The present document specifies the Solution Set (SS) definitions for the IRP whose semantics is specified in State Management IRP: Informati

27、on Service (IS) (3GPP TS 32.672 1). This Solution Set definitions specification is related to 3GPP TS 32.672 V11.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 (identif

28、ied 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 reference

29、 implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TS 32.311: “Telecommunication management; Generic Integration Reference Point (IRP) management; Requirements“. 2 3GPP TS 32.672: “Telecommunication management; Configuration Management (CM);

30、 State Management Integration Reference Point (IRP): Information Service (IS)“. 3 ITU-T Recommendation X.721: “Information technology - Open Systems Interconnection - Structure of management information: Definition of management information“. 4 ITU-T Recommendation M.3100: “Generic network informati

31、on model“. 5 3GPP TS 32.612: “Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP); Information Service (IS)“. 6 3GPP TS 32.616: “Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP); Solution Set (SS

32、) definitions“. 7 W3C REC-xml-20001006: “Extensible Markup Language (XML) 1.0 (Second Edition)“. 8 W3C REC-xmlschema-0-20010502: “XML Schema Part 0: Primer“. 9 W3C REC-xmlschema-1-20010502: “XML Schema Part 1: Structures“. 10 W3C REC-xmlschema-2-20010502: “XML Schema Part 2: Datatypes“. 11 W3C REC-x

33、ml-names-19990114: “Namespaces in XML“. 12 ITU-T Recommendation X.721: “Information technology - Open Systems Interconnection - Structure of management information: Definition of management information“. 13 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention

34、 for Managed Objects“. ETSI ETSI TS 132 676 V12.0.0 (2014-10)63GPP TS 32.676 version 12.0.0 Release 123 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions defined in 3GPP TS 32.672 2 apply, and the following XML terms and definitions app

35、ly: XML file: file containing an XML document XML document: composed of the succession of an optional XML declaration followed by a root XML element NOTE: See 7; in the scope of the present document. XML declaration: it specifies the version of XML being used NOTE: See 7. XML element: has a type, is

36、 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 end-tag, or composed simply of an XML empty-element tag; each XML element may contain other XML element

37、s NOTE: See 7. 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 an XML start-tag directly followed by an XML end-tag, or composed simply of an XML empty-element

38、tag NOTE: See 7. 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 XML start-tag: the beginning of a non-empty XML element is marked by an XML

39、start-tag containing the name and the set of XML attribute specifications of the XML element NOTE: See 7. 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 NOTE: See 7. XML empty-element tag: composed simply of an empty-element tag con

40、taining the name and the set of XML attribute specifications of the XML element NOTE: See 7. XML attribute specification: has a name and a value NOTE: See 7. DTD: defines structure and content constraints to be respected by an XML document to be valid with regard to this DTD NOTE: See 7. XML schema:

41、 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 by a single XML document; an XML schema is itself also an XML document tha

42、t shall conform with the XML schema for XML schemas NOTE: See 8, 9 and 10. ETSI ETSI TS 132 676 V12.0.0 (2014-10)73GPP TS 32.676 version 12.0.0 Release 12XML namespace: enables qualifying element and attribute names used in XML documents by associating them with namespaces identified by different XM

43、L schemas NOTE: See 11, in the scope of the present document. XML 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; ultimately defines constraints for an XM

44、L element on its XML attribute specifications and/or its XML content NOTE: See 8, 9 and 10. 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 attribute specifications and

45、/or its XML content; can also be the concrete type or the derivation base type for another XML element type NOTE: See 8, 9 and 10. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CM Configuration Management CORBA Common Object Request Broker Architectur

46、e DTD Document Type Definition EDGE Enhanced Data for GSM Evolution GERAN GSM/EDGE Radio Access Network GSM Global System for Mobile communication IDL Interface Definition Language IOC Information Object Class IRP Integration Reference Point IS Information Service NE Network ElementNRM Network Resou

47、rce Model OMG Object Management Group SS Solution Set UMTS Universal Mobile Telecommunications System UTRAN Universal Terrestrial Radio Access Network XML eXtensible Markup Language 3.3 IRP document version number string The IRP document version number (sometimes called “IRP version“ or “version num

48、ber“) string is used to identify this specification. The definition of “IRP document version number string“ in 3GPP TS 32.311 1 provides the rule to derive such a string. As the State Management IRP IS as defined in 3GPP TS 32.672 2 does not specify operations const string USAGE_STATE = “usageState“

49、; const string ADMINISTRATIVE_STATE = “administrativeState“; const string ALARM_STATUS = “alarmStatus“; const string PROCEDURAL_STATUS = “proceduralStatus“; const string AVAILABILITY_STATUS = “availabilityStatus“; const string CONTROL_STATUS = “controlStatus“; const string STANDBY_STATUS = “standbyStatus“; const string UNKNOWN_STATUS = “unknownStatus“; ; /* The following structures provide the new state value, and the optional old state value The structures are passed in the valu