ETSI TS 132 755-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Evolved Packet Core (E.pdf

1、 ETSI TS 132 755 V9.3.0 (2010-10)Technical Specification 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):eXtensible Markup

2、 Language (XML) definitions (3GPP TS 32.755 version 9.3.0 Release 9)ETSI ETSI TS 132 755 V9.3.0 (2010-10)13GPP TS 32.755 version 9.3.0 Release 9Reference RTS/TSGS-0532755v930 Keywords GSM, LTE, UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33

3、4 93 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 ele

4、ctronic 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 wi

5、thin 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 docum

6、ent, 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 Telec

7、ommunications Standards Institute 2010. 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 Organizati

8、onal Partners. LTE is a Trade Mark of 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 755 V9.3.0 (2010-10)23GPP TS 32.755 version 9.3.0 Release 9

9、Intellectual Property Rights IPRs essential 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

10、 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 available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, includi

11、ng 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, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has

12、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 identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross ref

13、erence between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 132 755 V9.3.0 (2010-10)33GPP TS 32.755 version 9.3.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33

14、 Definitions and abbreviations . 6g33.1 Definitions 6g33.3 Abbreviations . 7g34 Architectural Features 7g35 Mapping . 8g35.1 General mapping 8g35.2 Information Object Class (IOC) mapping 8g3Annex A (normative): XML schema (file name “epcNrm.xsd“) 9g3Annex B (informative): View . 19g3Annex C (informa

15、tive): Change history . 20g3History 21g3ETSI ETSI TS 132 755 V9.3.0 (2010-10)43GPP TS 32.755 version 9.3.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

16、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 first digit: 1 presented to TSG for info

17、rmation; 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 when editorial only changes have been

18、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.751: “Evolved Packet Core (EPC) Network Resource Mode

19、l (NRM) Integration Reference Point (IRP): Requirements“; 32.752: “Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)“; 32.753: “Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP): Common Object Req

20、uest Broker Architecture (CORBA) Solution Set (SS)“; 32.755: “Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP): Bulk CM eXtensible Markup Language (XML) file format definition“. ETSI ETSI TS 132 755 V9.3.0 (2010-10)53GPP TS 32.755 version 9.3.0 Release 91 Scop

21、e The present document provides the XML file format definition for the EPC Network Resource Model IRP IS 2 V9.3.X. An application of these XML definitions is to build a configuration file for transfer with the Bulk CM IRP using either CORBA Solution Set of 3GPP TS 32.613 3 or the SOAP Solution Set o

22、f 3GPP TS 32.617 5. For this application, the basic part of the XML file format definition is provided by 3GPP TS 32.615 4. Other applications of these XML definitions are the SOAP solution sets of other IRPs that perform operations on managed objects, for example the Basic CM IRP SOAP SS of 3GPP TS

23、 32.607 6. 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, version number, etc.) or non-specific. For a specific reference,

24、 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 that document in the same Release as the present document. 1 3GP

25、P 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 Service (IS) (Release 8)”. 3 3GPP TS 32.613: “Telecommunication management; Configuration Manageme

26、nt (CM); Bulk CM Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)“. 4 3GPP TS 32.615: “Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP); eXtensible Markup Language (XML) file format definition

27、“. 5 3GPP TS 32.617: “Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP); SOAP Solution Set (SS)“. 6 3GPP TS 32.607: “Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); SOAP Solution Set (SS)“.

28、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-xml-names-1999011

29、4: “Namespaces in XML“. ETSI ETSI TS 132 755 V9.3.0 (2010-10)63GPP TS 32.755 version 9.3.0 Release 93 Definitions and abbreviations 3.1 Definitions 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

30、 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 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 spec

31、ifies 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 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

32、 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 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 dire

33、ctly 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 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

34、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 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 NOT

35、E: 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 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

36、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 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 togethe

37、r 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 10. ETSI ETSI TS 132 755 V9.3.0 (2010-10)73GPP TS 32.755 version 9.3.0 Release 9XML namespace: enables qualifying element and attribute names used in XML

38、 documents by associating them with namespaces identified by different XML 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

39、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 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

40、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 NOTE: See 8, 9 and 10. 3.2 Symbols For the purposes of the present document, the following symbols apply: Void 3.3 Abbr

41、eviations For the purposes of the present document, the abbreviations given in TR 21.905 1 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 1. CM Configuration Management DTD Document Type Def

42、inition eNodeB evolved NodeB EPC Evolved Packet Core ePDG evolved Packet Data Gateway E-UTRAN Evolved Universal Terrestrial Radio Access Network GPRS General Packet Radio System IRP Integration Reference Point IS Information Service MME Mobility Management Entity NRM Network Resource Model PCRF Poli

43、cy and Charging Rules Function P-GW PDN Gateway S-GW Serving Gateway XML eXtensible Markup Language 4 Architectural Features The overall architectural feature of EPC Network Resource Model IRP is specified in 3GPP TS 32.752 2. This clause specifies features that are specific to the XML definitions S

44、S. The XML definitions of this document specify the schema for configuration content. When using the XML definitions for a configuration file transfer with the Bulk CM IRP, using either CORBA Solution Set of 3GPP TS 32.613 3 or SOAP Solution Set of 3GPP TS 32.617 5, the basic part of the XML file fo

45、rmat ETSI ETSI TS 132 755 V9.3.0 (2010-10)83GPP TS 32.755 version 9.3.0 Release 9definition is provided by 3GPP TS 32.615 4. The XML definitions of this document provide the schema for the configuration content to be included in such a configuration file. When using the XML definitions with a SOAP s

46、olution set of any interface IRP that perform operations on managed objects, for example the Basic CM IRP SOAP SS of 3GPP TS 32.607 6, the XML definitions of this document provides the schema for the configuration content operated on by the interface IRP. Such configuration content can be name of ma

47、naged object and, if applicable, IOC attributes. 5 Mapping 5.1 General mapping An IOC maps to an XML element of the same name as the IOCs name in the IS. An IOC attribute maps to a sub-element of the corresponding IOCs XML element, and the name of this sub-element is the same as the attributes name

48、in the IS. 5.2 Information Object Class (IOC) mapping The overall description of the file format of configuration data XML files is provided by 3GPP TS 32.615 4. Annex A of the present document defines the NRM-specific XML schema epcNrm.xsd for the EPC NRM IRP IS defined in 3GPP TS 32.752 2. XML sch

49、ema epcNrm.xsd explicitly declares NRM-specific XML element types for the related NRM. The definition of those NRM-specific XML element types complies with the generic mapping rules defined in 3GPP TS 32.615 4. ETSI ETSI TS 132 755 V9.3.0 (2010-10)93GPP TS 32.755 version 9.3.0 Release 9Annex A (normative): XML schema (file name “epcNrm.xsd“) The following XML schema epcNrm.xsd is the NRM-specific schema for the EPC Network Resource Model IRP NRM defined in 3GPP TS 32.752