Home enhanced Node B (HeNB) Subsystem (HeNS) Network Resource Model (NRM) Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition

3GPP TS 32.785 V9.1.0 (2010-12)
Technical Specification
3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Telecommunication management;
Home enhanced Node B (HeNB) Subsystem (HeNS); 
Network Resource Model (NRM);
 Integration Reference Point (IRP): 
eXtensible Markup Language (XML) file format definition 
(Release 9)
	 EMBED Word.Picture.8  

The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. 
The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.	 
This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.

Keywords
HeNS, HeNB, HeNB-GW, management
3GPP
Postal address

3GPP support office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Internet
http://www.3gpp.org
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.

© 2010, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).
All rights reserved.

UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational 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 registered and owned by the GSM Association
Contents
 TOC \o "1-9" Foreword	 PAGEREF _Toc280349684 \h 4
Introduction	 PAGEREF _Toc280349685 \h 4
1	Scope	 PAGEREF _Toc280349686 \h 5
2	References	 PAGEREF _Toc280349687 \h 5
3	Definitions and abbreviations	 PAGEREF _Toc280349688 \h 6
3.1	Definitions	 PAGEREF _Toc280349689 \h 6
3.2	Abbreviations	 PAGEREF _Toc280349690 \h 7
4	Architectural Features	 PAGEREF _Toc280349691 \h 7
5	Mapping	 PAGEREF _Toc280349692 \h 8
5.1	General mapping	 PAGEREF _Toc280349693 \h 8
5.2	Information Object Class (IOC) mapping	 PAGEREF _Toc280349694 \h 8
Annex A (normative):	XML schema	 PAGEREF _Toc280349695 \h 9
Annex B (informative):	Change history	 PAGEREF _Toc280349696 \h 11

Foreword
This Technical Specification has been produced by the 3rd Generation 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 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 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 document.
Introduction
The present document is part of a TS-family covering the 3rd Generation Partnership Project Technical Specification Group Services and System Aspects, Telecommunication management; as identified below:
32.781:	Telecommunication management; Home eNode B Subsystem (HeNS) Network Resource Model (NRM) Integration Reference Point (IRP): Requirements
32.782:	Telecommunication management; Home eNode B Subsystem (HeNS) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)
32.783:	Telecommunication management; Home eNode B Subsystem (HeNS) Network Resource Model (NRM) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
32.785:	Telecommunication management; Home eNode B Subsystem (HeNS) Network Resource Model (NRM) Integration Reference Point (IRP): Bulk CM eXtensible Markup Language (XML) file format definition
.
1	Scope
The present document provides the XML file format definition for the HeNS Network Resource Model IRP IS [2].
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 of 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 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, 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]	3GPP TR 21.905: “Vocabulary for 3GPP Specifications”.
[2]	3GPP TS 32.782: “Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)”.
[3]	3GPP TS 32.613: "Telecommunication management; Configuration Management (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".
[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)".
[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-19990114: "Namespaces in XML".

3	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 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 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 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 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 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 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 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 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 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 [10].
XML namespace: enables qualifying element and attribute names used in XML 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 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 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	Abbreviations
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 Definition
HeNB	Home enhanced Node B
HeNS	Home enhanced Node B Subsystem
HeNB-GW	Home enhanced Node B Gateway
IRP	Integration Reference Point
IS	Information Service
NRM	Network Resource Model
XML	eXtensible Markup Language

4	Architectural Features
The overall architectural feature of HeNS Network Resource Model IRP is specified in 3GPP TS 32.782 [2].  This clause specifies features that are specific to the XML definitions.
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 format definition 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 solution 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 managed 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 IOC's name in the IS. An IOC attribute maps to a sub-element of the corresponding IOC's XML element, and the name of this sub-element is the same as the attribute's name in the IS.
5.2	Information Object Class (IOC) mapping
Annex A of the present document defines the NRM-specific XML schema hensNrm.xsd for the HeNS Network Resources IRP NRM defined in 3GPP TS 32.782 [2].
XML schema hensNrm.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].
Annex A (normative):
XML schema
The following XML schema hensNrm.xsd is the NRM-specific schema for the HeNS Network Resources IRP NRM defined in 3GPP TS 32.782 [1]:






  
  
  
  

  

  
    
      
        
          
            
              
                
                  
                  
                  
                  
                  
                
              
            
            
              
              
            
          
        
      
    
  

  
    
      
        
          
            
              
                
                  
                  
                  
                
              
            
            
              
            
          
        
      
    
  

  
    
      
        
          
            
              
                
                  
                
              
            
            
              
              
            
          
        
      
    
  





Annex B (informative):
Change history

Change history
DateTSG #TSG Doc.CRRevSubject/CommentOldNewMar 2010SA#47SP-100065----Presentation to SA for information and approval--1.0.0Mar 2010---------Publication of SA approved version1.0.09.0.0Dec 2010SA#50SP-100858001--Correcting the HeNS XML namespace prefix9.0.09.1.0








 STYLEREF ZA 3GPP TS 32.785 V9.1.0 (2010-12)
 PAGE 11
 STYLEREF ZGSM Release 9


3GPP