3GPP TS 32.711 V9.0.0 (2009-12)

3GPP TS 32.711 V9.0.0 (2009-12)
Technical Specification
3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Telecommunication management;
 Configuration Management (CM);
 Transport Network (TN) interface Network Resource Model (NRM) Integration Reference Point (IRP);
 Requirements 
(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
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.

©2009, 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 _Toc168481187 \h 4
Introduction	 PAGEREF _Toc168481188 \h 4
1	Scope	 PAGEREF _Toc168481189 \h 5
2	References	 PAGEREF _Toc168481190 \h 5
3	Definitions and abbreviations	 PAGEREF _Toc168481191 \h 5
3.1	Definitions	 PAGEREF _Toc168481192 \h 5
3.2	Abbreviations	 PAGEREF _Toc168481193 \h 6
4	Requirements	 PAGEREF _Toc168481194 \h 7
Annex A (informative):	Change history	 PAGEREF _Toc168481195 \h 8

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.711:	Configuration Management (CM); Transport Network (TN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Requirements
32.712:	Configuration Management (CM); Transport Network (TN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)
32.713:	Configuration Management (CM); Transport Network (TN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
32.715	Configuration Management (CM); Transport Network (TN) interface Network Resource Model (NRM) Integration Reference Point (IRP); 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 defines , in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: Transport Network (TN) interface Network Resource Model (NRM) Integration Reference Point.
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.101: "Telecommunication Management, Principles and high level requirements".
[2]	3GPP TS 32.102: "Telecommunication management; Architecture".
[3]	3GPP TS 32.600: "Telecommunication management; Configuration Management (CM); Concept and high-level requirements".
3	Definitions and abbreviations
3.1	Definitions
For the purposes of the present document, the following terms and definitions apply:
data: any information or set of information required to give software or equipment or combinations thereof a specific state of functionality.
Element Manager (EM): provides a package of end-user functions for management of a set of closely related types of Network Elements (NEs). These functions can be divided into two main categories:
Element Management Functions for management of NEs on an individual basis. These are basically the same functions as supported by the corresponding local terminals;
Sub-Network Management Functions that are related to a network model for a set of NEs constituting a clearly defined sub-network, which may include relations between the NEs. This model enables additional functions on the sub-network level (typically in the areas of network topology presentation, alarm correlation, service impact analysis and circuit provisioning).
IRP: see 3GPP TS 32.101 [1]
IRP Information Model: see 3GPP TS 32.101 [1]
IRP Information Service (IS): see 3GPP TS 32.101 [1]
IRP Solution Set (SS): see 3GPP TS 32.101 [1]
Managed Object (MO): an abstract entity, which may be accessed through an open interface between two or more systems, and representing a Network Resource (NR) for the purpose of management. The Managed Object (MO) is an instance of a Managed Object Class (MOC) as defined in a Management Information Model (MIM). The MIM does not define how the MO or NR is implemented; only what can be seen in the interface.
Managed Object Class (MOC): a description of all the common characteristics for a number of MOs, such as their attributes, operations, notifications and behaviour.
Management Information Model (MIM): also referred to as NRM - see the definition below. There is a slight difference between the meaning of MIM and NRM - the term MIM is generic and can be used to denote any type of management model, while NRM denotes the model of the actual managed telecommunications Network Resources (NRs).
Network Element (NE): is a discrete telecommunications entity, which can be, managed over a specific interface e.g. the RNC.
Network Manager (NM): provides a package of end-user functions with the responsibility for the management of a network, mainly as supported by the EM(s) but it may also involve direct access to the NEs. All communication with the network is based on open and well-standardised interfaces supporting management of multi-vendor and multi-technology NEs.
Network Resource (NR): is a component of a NE, which can be identified as a discrete separate entity and is in an object oriented environment for the purpose of management represented by an abstract entity called Managed Object (MO).
Network Resource Model (NRM): a model representing the actual managed telecommunications Network Resources (NRs) that a System is providing through the subject IRP. An NRM describes Managed Object Classes (MOC), their associations, attributes and operations. The NRM is also referred to as "MIM" (see above) which originates from the ITU-T TMN.
Object Management Group (OMG): see http://www.omg.org
Operations System (OS): indicates a generic management system, independent of its location level within the management hierarchy.
3.2	Abbreviations
For the purposes of the present document, the following abbreviations apply:
CM	Configuration Management
EM	Element Manager
FM	Fault Management
GSM	Global System for Mobile communication
IRP	Integration Reference Point
IS	Information Service (see 3GPP TS 32.101 [1])
ITU-T	International Telecommunication Union, Telecommunication Standardisation Sector 
MIB	Management Information Base
MIM	Management Information Model
MOC	Managed Object Class
MOI	Managed Object Instance
NE	Network Element
NM	Network Manager
NR	Network Resource
NRM	Network Resource Model
OMG	Object Management Group
OS	Operations System
PM	Performance Management
TM	Telecom Management
UML	Unified Modelling Language (OMG)
UMTS	Universal Mobile Telecommunications System
Requirements
The following general and high-level requirements apply for the present IRP:
IRP-related requirements in 3GPP TS 32.101 [1].
IRP-related requirements in 3GPP TS 32.102 [2].
IRP-related requirements in 3GPP TS 32.600 [3].
In addition to the above, the following more specific requirements apply:
The NRM specified by this IRP shall allow for the configuration of the ATM Termination Points of the UTRAN inter element links (Iub-link, Iur-link, Iu-link), which are residing in a Node B or RNC. More specifically, the NRM:
shall allow for the viewing of the physical layer used by the ATM network (e. g. E1);
shall allow for the viewing of parameters of the virtual circuits associated with each link (e.g. VPI/VCI, ATM Service Category, AAL type, Peak Cell Rate, Sustainable Cell Rate, Maximum Burst Size);
shall allow the assigning of a UTRAN interface logical channel (e.g. Iub-NBAP) to a virtual circuit and configuration of parameters of the virtual circuit (e.g. VPI/VCI, ATM Service Category, AAL type, Peak Cell Rate, Sustainable Cell Rate, Maximum Burst Size);
shall allow to relate the ATM Termination Point easily to the associated link;
shall allow to relate the ATM Termination Point easily to the network element and the type of network element it is connected to.
The Network Resource Model defined by this IRP shall be generic in the sense to allow support for multiple transport technologies (e.g. IP) in the future;
The Network Resource Model defined by this IRP shall be generic in the sense to allow support for the management of termination points of other interface links (e. g. links between network elements of the CN) in the future.
Annex A (informative):
Change history
Change history
DateTSG #TSG Doc.CRRevSubject/CommentOldNewSep 2003S_21SP-030428----Submitted to TSG SA#21 for Information1.0.0Sep 2004S_25SP-040596----Submitted to TSG SA#25 for Approval2.0.06.0.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.0.07.0.0Dec 2008SA_42------Upgrade to Release 87.0.08.0.0Dec 2009----Update to Rel-9 version8.0.09.0.0









 STYLEREF ZA 3GPP TS 32.711 V9.0.0 (2009-12)
 PAGE 8
 STYLEREF ZGSM Release 9


Page PAGE8


3GPP