1、 ETSI TS 132 756 V11.0.0 (2012-10) Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) Definitions (3GP
2、P TS 32.756 version 11.0.0 Release 11) Technical Specification ETSI ETSI TS 132 756 V11.0.0 (2012-10)13GPP TS 32.756 version 11.0.0 Release 11Reference RTS/TSGS-0532756vb00 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 electro
4、nic 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 Telecommu
7、nications 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 t
8、he GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 756 V11.0.0 (2012-10)23GPP TS 32.756 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 pertain
9、ing 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 Secretari
10、at. 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
11、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 technical specifications or reports using their 3GPP identities,
12、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/queryform.asp. ETSI ETSI TS 132 756 V11.0.0 (2012-10)33GPP TS 32.756
13、 version 11.0.0 Release 11Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 Solution Set definitions 7g3Annex A (normative): CORBA Solution Set 8g3A.1 Archit
14、ectural features . 8g3A.1.1 Syntax for Distinguished Names 8g3A.2 Mapping . 8g3A.2.1 General mapping 8g3A.2.2 Information Object Class (IOC) mapping 8g3A.2.2.1 IOC MMEFunction . 8g3A.2.2.2 IOC MMEPool 9g3A.2.2.3 IOC MMEPoolArea 9g3A.2.2.4 IOC EP_RP_EPS 9g3A.2.2.5 IOC ExternalMMEFunction . 9g3A.2.2.6
15、 IOC ServingGWFunction . 10g3A.2.2.7 IOC ExternalServingGWFunction 10g3A.2.2.8 IOC QCISet 10g3A.2.2.9 IOC MBMSGWFunction 10g3A.3 Solution Set definitions 11g3A.3.1 IDL definition structure 11g3A.3.2 IDL specification “EPCResourcesNRMDefs.idl“ 11g3Annex B (normative): XML definitions 16g3B.1 Architec
16、tural features . 16g3B.1.1 Syntax for Distinguished Names 16g3B.2 Mapping . 16g3B.2.1 General mapping 16g3B.2.2 Information Object Class (IOC) mapping 16g3B.3 Solution Set definitions 16g3B.3.1 XML definition structure 16g3B.3.2 XML schema “epcNrm.xsd” 17g3Annex C (informative): Change history . 28g
17、3History 29g3ETSI ETSI TS 132 756 V11.0.0 (2012-10)43GPP TS 32.756 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 subject to continuing work within the TSG and may change follo
18、wing 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
19、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 docu
20、ment. 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.751: Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Refe
21、rence Point (IRP): Requirements 32.752: Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS) 32.756: Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions ETSI ETSI TS 132
22、756 V11.0.0 (2012-10)53GPP TS 32.756 version 11.0.0 Release 111 Scope The TS 32.75x-series (EPC NRM IRP) define an Integration Reference Point (IRP) named EPC Network Resource Model (NRM) IRP, through which an “IRPAgent“ (typically an Element Manager or Network Element) can communicate Network Manag
23、ement related information to one or several “IRPManagers“ (typically Network Managers). The present document provides solution set definitions for EPC Network Resources IRP, which define the mapping of the IRP information model (see TS 32.752 2) to the protocol specific details necessary for impleme
24、ntation of this IRP. This Solution Set definitions specification is related to 3GPP TS 32.752 2 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 (identified by date of
25、 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 implicitly re
26、fers to the latest version of that document in the same Release as the present document. 1 3GPP TS 21.905: “Vocabulary for 3GPP Specifications”. 2 3GPP TS 32.752: “Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP): Information Serv
27、ice (IS) (Release 8)”. 3 3GPP TS 32.616: “Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP); Solution Set (SS) definitions“. 4 3GPP TS 32.606: “Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP)
28、; Solution Set (SS) definitions“. 5 W3C REC-xml-names-19990114: “Namespaces in XML“. 6 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“. 7 W3C REC-xml-20001006: “Extensible Markup Language (XML) 1.0 (Second Edition)“. 8 W3C REC-xmlsch
29、ema-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“. ETSI ETSI TS 132 756 V11.0.0 (2012-10)63GPP TS 32.756 version 11.0.0 Release 113 Definitions and abbreviations 3.1 Definition
30、s For the purposes of the present document, the terms and definitions given in TR 21.905 1 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 1. XML file: file containing an XML document XML document: composed o
31、f 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 identified by a name, may have a set of XML attribute specifications
32、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 elements NOTE: See 7. empty XML element: having an empty XML content; an empt
33、y 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 tag NOTE: See 7. XML content (of an XML element): empty if the XML ele
34、ment 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 start-tag containing the name and the set of XML attribute specificati
35、ons 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 containing the name and the set of XML attribute specifications of the XM
36、L 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: more powerful than a DTD, an XML schema defines structure and content
37、 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 that shall conform with the XML schema for XML schemas NOTE: See 8, 9 and
38、 10. ETSI ETSI TS 132 756 V11.0.0 (2012-10)73GPP TS 32.756 version 11.0.0 Release 11XML namespace: enables qualifying element and attribute names 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 compl
39、ex 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 XML element on its XML attribute specifications and/or its XML content NO
40、TE: 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/or its XML content; can also be the concrete type or the derivation ba
41、se 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 Architecture DN Distinguished Name DTD Document Type Definition eNodeB evolved Nod
42、eB EPC Evolved Packet Core EPDG Evolved Packet Data Gateway E-UTRAN Evolved Universal Terrestrial Radio Access Network GPRS General Packet Radio System IS Information Service IDL Interface Definition Language (OMG) IOC Information Object Class IRP Integration Reference Point IS Information Service M
43、ME Mobility Management Entity MO Managed Object MOC Managed Object Class NRM Network Resource Model OMG Object Management Group PCRF Policy and Charging Rules Function P-GW PDN Gateway S-GW Serving Gateway SS Solution Set XML eXtensible Markup Language 4 Solution Set definitions This specifications
44、defines the following 3GPP EPC NRM IRP Solution Set definitions: 3GPP EPC NRM IRP CORBA SS (Annex A) 3GPP EPC NRM IRP XML definitions (Annex B) ETSI ETSI TS 132 756 V11.0.0 (2012-10)83GPP TS 32.756 version 11.0.0 Release 11Annex A (normative): CORBA Solution Set This annex contains the CORBA Solutio
45、n Set for the IRP whose semantics is specified in EPC Network Resource Model (NRM) IRP: Information Service (TS 32.752 2). A.1 Architectural features The overall architectural feature of EPC NRM IRP is specified in 3GPP TS 32.752 2. This clause specifies features that are specific to the CORBA SS. A
46、.1.1 Syntax for Distinguished Names The syntax of a Distinguished Name is defined in 3GPP TS 32.300 6. A.2 Mapping A.2.1 General mapping Attributes modelling associations as defined in the NRM (here also called “reference attributes“) are in this SS mapped to attributes. The names of the reference a
47、ttributes 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 defined as an MOReference. The value of an MO reference contains the distinguished name of the associated MO. When the card
48、inality for an association allows more than one referred MO, the reference attribute will be of type MOReferenceSet, which contains a sequence of MO references. A.2.2 Information Object Class (IOC) mapping This Solution Set supports reference attributes for relations other than containment relations
49、 between objects. Reference attributes are therefore introduced in each MOC where needed. A.2.2.1 IOC MMEFunction Attribute of IOC MMEFunction in 3GPP TS 32.752 2 SS Attribute SS Type Support Qualifier Read Qualifier Write Qualifier id id string M M -pLMNIdList pLMNIdList genericEPCNRMAttributeTypes: AttributeTypes: plmnIdListType M M - mMEC mMEC long M M -mMEPool mMEPool GenericNetworkResourcesIRPSystem: AttributeTypes:MOReference M M - ETSI ETSI TS 132 756 V11.0.0 (2012-10)93GPP TS 32.75
