32.106-13GPPConfiguration Management (CM)Part 1: Concept and requirementsRelease 4Telecommunication managementTS
For the purposes of the present document, the following terms and definitions apply.
Data: is 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).
Firmware: is a term used in contrast to software to identify the hard-coded program, which is not downloadable on the system.
Hardware: is each and every tangible item.
IRP Information Model: See 3G TS 32.101 .
IRP Information Service: See 3G TS 32.101 .
IRP Solution Set: See 3G TS 32.101 .
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.
Managed Object Instance (MOI): an instance of a MOC, which is the same as a MO as described above.
Management Information Base (MIB): the set of existing managed objects in a management domain, together with their attributes, constitutes that management domain’s MIB. The MIB may be distributed over several OS/NEs.
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.
Operator: is either
- a human being controlling and managing the network; or
- a company running a network (the 3G network operator).
Optimisation: of the network is each up-date or modification to improve the network handling and/or to enhance subscriber satisfaction. The aim is to maximise the performance of the system.
Re-configuration: is the re-arrangement of the parts, hardware and/or software that make up the 3G network. A re-configuration can be of the parts of a single NE or can be the re-arrangement of the NEs themselves, as the parts of the 3G network. A re-configuration may be triggered by a human operator or by the system itself.
Reversion: is a procedure by which a configuration, which existed before changes were made, is restored.
Software: is a term used in contrast to firmware to refer to all programs which can be loaded to and used in a particular system.
Up-Dates: generally consist of software, firmware, equipment and hardware, designed only to consolidate one or more modifications to counter-act errors. As such, they do not offer new facilities or features and only apply to existing NEs.
Up-Grades: can be of the following types:
- enhancement – the addition of new features or facilities to the 3G network;
- extension – the addition of replicas of existing entities.
For the purposes of the present document, the following abbreviations apply:
CM Configuration Management
CMIP Common Management Information Protocol
CORBA Common Object Request Broker Architecture
EM Element Manager
FM Fault Management
IRP Integration Reference Point
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
OSF Operations System Function
PM Performance Management
RNC Radio Network Controller
TM Telecom Management
UML Unified Modelling Language (OMG)
UMTS Universal Mobile Telecommunications System