1、 ETSI TS 132 636 V11.0.0 (2012-10) Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP); Solution Set (SS) Definitions (3GPP
2、 TS 32.636 version 11.0.0 Release 11) Technical Specification ETSI ETSI TS 132 636 V11.0.0 (2012-10)13GPP TS 32.636 version 11.0.0 Release 11Reference RTS/TSGS-0532636vb00 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
3、65 47 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 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 electron
4、ic version or 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
5、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/tb/status/status.asp If you find errors in the present document,
6、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 except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommun
7、ications Standards 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 th
8、e GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 636 V11.0.0 (2012-10)23GPP TS 32.636 version 11.0.0 Release 11Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaini
9、ng 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 ETSI standards“, which is available from the ETSI Secretaria
10、t. Latest updates 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 E
11、TSI 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 technical specifications or reports using their 3GPP identities, U
12、MTS 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/queryform.asp. ETSI ETSI TS 132 636 V11.0.0 (2012-10)33GPP TS 32.636
13、version 11.0.0 Release 11Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 8g3Solution Set definitions 8g3Annex A (normative): CORBA Solution Set . 9 g3A.1 Archit
14、ectural features . 9g3A.1.1 Syntax for Distinguished Names 9g3A.1.2 Allowed extensions 9g3A.1.3 Extensions not allowed . 9g3A.2 Mapping . 10g3A.2.1 General mappings . 10g3A.2.2 Information Object Class (IOC) mapping 10g3A.2.2.1 IOC MscServerFunction . 10g3A.2.2.2 IOC HlrFunction . 10g3A.2.2.3 IOC Vl
15、rFunction . 11g3A.2.2.4 IOC AucFunction 11g3A.2.2.5 IOC EirFunction . 11g3A.2.2.6 IOC SmsIwmscFunction . 11g3A.2.2.7 IOC SmsGmscFunction 11g3A.2.2.8 IOC SgsnFunction 12g3A.2.2.9 IOC GgsnFunction 12g3A.2.2.10 IOC BgFunction 12g3A.2.2.11 IOC GmscFunction . 12g3A.2.2.12 IOC SmlcFunction 13g3A.2.2.13 IO
16、C GmlcFunction . 13g3A.2.2.14 IOC ScfFunction . 13g3A.2.2.15 IOC SrfFunction . 13g3A.2.2.16 IOC CbcFunction 13g3A.2.2.17 IOC CgfFunction 13g3A.2.2.18 IOC GmscServerFunction . 14g3A.2.2.19 IOC IwfFunction . 14g3A.2.2.20 IOC MnpSrfFunction 14g3A.2.2.21 IOC NpdbFunction . 14g3A.2.2.22 IOC SgwFunction .
17、 14g3A.2.2.23 IOC SsfFunction . 14g3A.2.2.24 IOC BsFunction 15g3A.2.2.25 IOC IucsLink 15g3A.2.2.26 IOC IupsLink 15g3A.2.2.27 IOC IubcLink 15g3A.2.2.28 IOC ALink 16g3A.2.2.29 IOC GbLink 16g3A.2.2.30 IOC CsMgwFunction 16g3A.2.2.31 IOC BmScFunction. 16g3A.2.2.32 IOC Link_BmSc_Ggsn . 16g3A.2.2.33 IOC Li
18、nk_Ggsn_Sgsn . 16g3ETSI ETSI TS 132 636 V11.0.0 (2012-10)43GPP TS 32.636 version 11.0.0 Release 11A.2.2.34 CircuitEndPointSubgroup . 17g3A.2.2.35 IOC MscPool 17g3A.2.2.36 IOC MscPoolArea 17g3A.2.2.37 IOC SgsnPool . 18g3A.2.2.38 IOC SgsnPoolArea 18g3A.3 Solution Set definitions 19g3A.3.1 IDL definiti
19、on structure 19g3A.3.2 IDL specification “CoreNetworkResourcesNRMDefs.idl“ 19g3Annex B (normative): XML definitions . 25g3B.1 Architectural features . 25g3B.1.1 Syntax for Distinguished Names 25g3B.2 Mapping . 25g3B.3 Solution Set definitions 25g3B.3.1 XML definition structure 25g3B.3.2 XML schema “
20、coreNrm.xsd“ . 25g3Annex C (informative): Change history . 37g3History 38g3ETSI ETSI TS 132 636 V11.0.0 (2012-10)53GPP TS 32.636 version 11.0.0 Release 11Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are
21、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 an increase in version number as follows: Version x.y.z where: x the fi
22、rst 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 enhancements, corrections, updates, etc. z the third digit is incremented
23、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 Aspects; Telecommunication management; as identified below: 32.631: “Configur
24、ation Management (CM); Core network resources Integration Reference Point (IRP); Requirements“. 32.632: “Configuration Management (CM); Core network resources Integration Reference Point (IRP); Network Resource Model (NRM)“. 32.636: “Configuration Management (CM); Core network resources Integration
25、Reference Point (IRP); Solution Set (SS) definitions“. ETSI ETSI TS 132 636 V11.0.0 (2012-10)63GPP TS 32.636 version 11.0.0 Release 111 Scope The purpose of the present document is to define the mapping of the IRP information model (see TS 32.632 3) to the protocol specific details necessary for imp
26、lementation of this IRP in a specific solution set environment. This Solution Set specification is related to 3GPP TS 32.632 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 sp
27、ecific (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 reference to a 3GPP document (including a GSM document), a non-spe
28、cific 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 and high level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.632: “ Telecomm
29、unication management; Configuration Management (CM); Core Network Resources Integration Reference Point (IRP): Network Resource Model (NRM)“. 4 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“. 5 W3C REC-xml-names-19990114: “Namespace
30、s in XML“. 6 3GPP TS 32.626: “Telecommunication management; Configuration Management (CM); Generic Network Resources Integration Reference Point (IRP): Solution Set (SS) definitions“. 7 3GPP TS 32.612: “Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point
31、(IRP); Information Service (IS)“. 8 3GPP TS 32.616: “Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP); Solution Set (SS) definitions“. 9 W3C REC-xml-20001006: “Extensible Markup Language (XML) 1.0 (Second Edition)“. 10 W3C REC-xmlschema-0-2001050
32、2: “XML Schema Part 0: Primer“. 11 W3C REC-xmlschema-1-20010502: “XML Schema Part 1: Structures“. 12 W3C REC-xmlschema-2-20010502: “XML Schema Part 2: Datatypes“. 3 Definitions and abbreviations 3.1 Definitions For terms and definitions please refer to TS 32.101 1, TS 32.102 2 and TS 32.632 3. For t
33、he purposes of the present document, the following terms and definitions apply: XML file: file containing an XML document ETSI ETSI TS 132 636 V11.0.0 (2012-10)73GPP TS 32.636 version 11.0.0 Release 11XML document: composed of the succession of an optional XML declaration followed by a root XML elem
34、ent NOTE: See 9; in the scope of the present document. XML declaration: it specifies the version of XML being used NOTE: See 9. 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 th
35、e 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 elements NOTE: See 9. empty XML element: having an empty XML content; an empty XML element still possibly has a set of XML attribute specifications; an
36、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 tag NOTE: See 9. XML content (of an XML element): empty if the XML element is simply composed of an XML empty-element tag; otherwise the part, po
37、ssibly 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 start-tag containing the name and the set of XML attribute specifications of the XML element NOTE: See 9. XML end-tag: the end of a non-empty XML
38、 element is marked by an XML end-tag containing the name of the XML element NOTE: See 9. XML empty-element tag: an empty XML element is composed simply of an empty-element tag containing the name and the set of XML attribute specifications of the XML element NOTE: See 9. XML attribute specification:
39、 has a name and a value DTD: defines structure and content constraints to be respected by an XML document to be valid with regard to this DTD NOTE: See 9. 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
40、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 that shall conform with the XML schema for XML schemas NOTE: See 10, 11 and 12. XML namespace: enables qualifying element and attribute n
41、ames used in XML documents by associating them with namespaces identified by different XML schemas NOTE: See 5, 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 XM
42、L element type or for another XML complex type; ultimately defines constraints for an XML element on its XML attribute specifications and/or its XML content NOTE: See 10, 11 and 12. XML element type: declared by an XML schema; can be directly used in an XML document; as the concrete type of an XML e
43、lement, directly or indirectly defines constraints on its XML attribute specifications and/or its XML content; can also be the concrete type or the derivation base type for another XML element type ETSI ETSI TS 132 636 V11.0.0 (2012-10)83GPP TS 32.636 version 11.0.0 Release 11NOTE: See 10, 11 and 12
44、. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CM Configuration Management CORBA Common Object Request Broker Architecture DN Distinguished Name DTD Document Type Definition EDGE Enhanced Data for GSM Evolution GERAN GSM/EDGE Radio Access Network GSM
45、 Global System for Mobile communication IDL Interface Definition Language (OMG) IOC Information Object Class IRP Integration Reference Point IS Information Service MGW Media GateWayMO Managed Object MOC Managed Object Class NRM Network Resource Model OMG Object Management Group UMTS Universal Mobile
46、 Telecommunications System UTRAN Universal Terrestrial Radio Access Network XML eXtensible Markup Language Solution Set definitions This specifications defines the following 3GPP Core network resources IRP Solution Set Definitions: 3GPP Core network resources IRP CORBA SS (Annex A) 3GPP Core network
47、 resources IRP XML definitions (Annex B) ETSI ETSI TS 132 636 V11.0.0 (2012-10)93GPP TS 32.636 version 11.0.0 Release 11Annex A (normative): CORBA Solution Set This annex contains the CORBA Solution Set for the IRP whose semantics is specified in Core Network Resources Integration Reference Point (I
48、RP); Network Resource Model (NRM) (TS 32.632 3). A.1 Architectural features The overall architectural feature of Core Network Resources IRP is specified in TS 32.632 3. This clause specifies features that are specific to the CORBA SS. A.1.1 Syntax for Distinguished Names The syntax of a Distinguishe
49、d Name is defined in 3GPP TS 32.300 4. A.1.2 Allowed extensions Vendor-specific MOCs may be supported. The vendor-specific MOCs may support new types of attributes. The 3GPP SA5-specified notifications may be issued referring to the vendor-specific MOCs and vendor-specific attributes. New MOCs shall be distinguishable from 3GPP SA5 MOCs by name. 3GPP SA5-specified and vendor-specific attributes may be used in vendor-specific MOCs. Vendor-specific attribute names shall be distinguishable from e
