Configuration Management (CM); GERAN network resources Integration Reference Point (IRP): Bulk CM eXtensible Markup Language (XML) file format definition

3GPP TS 32.655 V9.2.0 (2011-12)
Technical Specification
3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Telecommunication management;
 Configuration Management (CM);
 GERAN network resources Integration Reference Point (IRP); Bulk CM 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
GSM, UMTS, 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.

© 2011, 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 _Toc311845853 \h 4
Introduction	 PAGEREF _Toc311845854 \h 4
1	Scope	 PAGEREF _Toc311845855 \h 5
2	References	 PAGEREF _Toc311845856 \h 5
3	Definitions and abbreviations	 PAGEREF _Toc311845857 \h 5
3.1	Definitions	 PAGEREF _Toc311845858 \h 5
3.2	Abbreviations	 PAGEREF _Toc311845859 \h 7
4	Structure and content of configuration data XML files	 PAGEREF _Toc311845860 \h 7
Annex A (normative):	Configuration data file NRM-specific XML schema (file name "geranNrm.xsd")	 PAGEREF _Toc311845861 \h 8
Annex B (informative):	Void	 PAGEREF _Toc311845862 \h 12
Annex C (informative):	Change history	 PAGEREF _Toc311845863 \h 13

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.651:	Configuration Management (CM); GERAN network resources Integration Reference Point (IRP): Requirements
32.652:	Configuration Management (CM); GERAN network resources Integration Reference Point (IRP): Network Resource Model (NRM)
32.653:	Configuration Management (CM); GERAN network resources Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
32.655:	Configuration Management (CM); GERAN network resources Integration Reference Point (IRP): Bulk CM eXtensible Markup Language (XML) file format definition
Configuration Management (CM), in general, provides the operator with the ability to assure correct and effective 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 requested as part of an implementation programme (e.g. additions and deletions), as part of an optimisation programme (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 procedure involving actions on many resources/objects in one or several NEs.
1	Scope
The present document provides the NRM-specific part related to the GERAN Network Resources IRP NRM [1] of the XML file format definition for the Bulk Configuration Management IRP IS [2].
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] specifications.
This File Format Definition specification is related to 3GPP TS 32.652 V9.2.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 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 TS 32.652: "Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP): Network Resource Models (NRM)".
[2]	3GPP TS 32.612: "Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP); Information Service (IS)".
[3]	3GPP TS 32.615: "Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP); eXtensible Markup Language (XML) file format definition".
[4]	W3C REC-xml-20001006: "Extensible Markup Language (XML) 1.0 (Second Edition)".
[5]	W3C REC-xmlschema-0-20010502: "XML Schema Part 0: Primer".
[6]	W3C REC-xmlschema-1-20010502: "XML Schema Part 1: Structures".
[7]	W3C REC-xmlschema-2-20010502: "XML Schema Part 2: Datatypes".
[8]	W3C REC-xml-names-19990114: "Namespaces in XML".
3	Definitions and abbreviations
3.1	Definitions
For the purposes of the present document, the following terms and definitions apply:
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 [4]; in the scope of the present document.
XML declaration: it specifies the version of XML being used
NOTE:	See [4].
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 [4].
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 [4].
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 [4].
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 [4].
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 [4].
XML attribute specification: has a name and a value
NOTE:	See [4].
DTD: defines structure and content constraints to be respected by an XML document to be valid with regard to this DTD
NOTE:	See [4].
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 [5], [6] and [7].
XML namespace: enables qualifying element and attribute names used in XML documents by associating them with namespaces identified by different XML schemas
NOTE:	See [8], 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 [5], [6] and [7].
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 [5], [6] and [7].
3.2	Abbreviations
For the purposes of the present document, the following abbreviations apply:
CM	Configuration Management
DTD	Document Type Definition
EDGE	Enhanced Data for GSM Evolution
GERAN	GSM/EDGE Radio Access Network
GSM	Global System for Mobile communication
IRP	Integration Reference Point
IS	Information Service
NRM	Network Resource Model
UMTS	Universal Mobile Telecommunications System
UTRAN	Universal Terrestrial Radio Access Network
XML	eXtensible Markup Language
4	Structure and content of configuration data XML files
The overall description of the file format of configuration data XML files is provided by 3GPP TS 32.615 [3].
Annex A of the present document defines the NRM-specific XML schema geranNrm.xsd for the GERAN Network Resources IRP NRM defined in 3GPP TS 32.652 [1].
XML schema geranNrm.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 [3].
Annex A (normative):
Configuration data file NRM-specific XML schema (file name "geranNrm.xsd")
The following XML schema geranNrm.xsd is the NRM-specific schema for the GERAN Network Resources IRP NRM defined in 3GPP TS 32.652 [1]:






  
  
  
  

  

  
    
      
    
  
  
    
      
      
    
  
  
    
      
    
  

  
    
      
        
          
            
              
                
                  
                
              
            
            
              
              
            
          
        
      
    
  

  
    
      
        
          
            
              
                
                  
                  
                  
                  
                
              
            
            
              
              
            
          
        
      
    
  

  
    
      
        
          
            
              
                
                  
                  
                  
                  
                  
                  
                  
                  
                  
                  
                  
                  
                  
                  
                  
                  
                
              
            
            
              
              
              
              
            
          
        
      
    
  

  
    
      
        
          
            
              
                
                  
                  
                  
                  
                  
                  
                  
                
              
            
            
              
            
          
        
      
    
  

  
    
      
        
          
            
              
                
                  
                  
                  
                  
                  
                  
                  
                  
                  
                  
                
              
            
            
              
            
          
        
      
    
  

  
    
      
        
          
            
              
                
                  
                
              
            
            
              
              
            
          
        
      
    
  


Annex B (informative):
Void


Annex C (informative):
Change history
Change history
DateTSG #TSG Doc.CRRevSubject/CommentCatOldNewJun 2002SA_16SP-020298----Submitted to TSG SA #16 for Information--1.0.0Sep 2002SA_17SP-020463----Submitted to TSG SA #17 for Approval--2.0.05.0.0Jun 2003SA_20SP-0302830001--Deletion of GERAN attribute relationType in XML Schema.F5.0.05.1.0Jun 2003SA_20SP-0302870002--Correction of GERAN NRM XML schema namespace URIsF5.0.05.1.0Jun 2003SA_20SP-0302880003--Generic NRM XML schema dependencies removalF5.0.05.1.0Sep 2003SA_21SP-0304180004--Inclusion of External BSS Function in GERAN XML Schema - Alignment with 32.652F5.1.05.2.0Oct 2003--------Attached to this TS the normative XML schema electronic files corresponding to Sept 2003 TS 32.655--5.2.05.2.1Dec 2003SA_22SP-0306460005--Correction of the number of possible URAs from 1 to 8F5.2.15.3.0Mar 2004SA_23SP-0401310006--Add the capability to contain instances of VsDataContainer to some MOs - Align with the IS 32.652F5.3.05.4.0Jun 2004SA_24SP-0402590007--Removal of XML schema URI dependenciesF5.4.05.5.0Jun 2004SA_24SP-0402580008--Correction of the annex related to XML schema electronic files publicationF5.4.05.5.0Jun 2004SA_24SP-0402540009--The specification does not support all UMTS frequency bandsF5.4.05.5.0Sep 2004SA_25SP-0405940010--Correction of the XML code – Reinsertion of “targetNamespace=”F5.5.05.6.0Sep 2004SA_25SP-040541----Automatic upgrade to Rel- 6 (no CR) as per request in SP‑040541 SA5_presentation_SA_25.ppt (slide 17)--5.6.06.0.0Dec 2004SA_26SP-0408110011--Add operationalState to the BtsSiteMgr – Align with the IS in 32.652F6.0.06.1.0Dec 2005SA_30SP-0507130012--Correct relationships for External IOCs - Align with IS in 32.652F6.1.06.2.0Jun 2007SA_36------Automatic upgrade to Rel-7 (no CR) at freeze of Rel-7. Deleted reference to CMIP SS, discontinued from R7 onwards.--6.2.07.0.0Dec 2008SA_42------Upgrade to Release 8--7.0.08.0.0Dec 2008SA_46SP-0907190013--Discontinue from Rel-9 onwards the XML schema extraction and storageF8.0.09.0.0Sep 2010SA_49SP-1004880014--Corrections of attribute hoppingSequenceNumber in GsmCell IOCF9.0.09.1.0Dec 2011SA_54SP-1107040016--Add missing management of IRAT ANR from E-UTRAN to GERAN and Neighbour cell Relation towards E-UTRAN - Align with ISA9.1.09.2.0











 STYLEREF ZA 3GPP TS 32.655 V9.2.0 (2011-12)
 PAGE 3
 STYLEREF ZGSM Release 9


3GPP