Configuration Management Based on the Telecommunication Management Network (TMN) Architecture
Document Number GR-3010
Issue Number 02
Issue Date Jun 2001
ABSTRACT: Issue 2 of GR-3010, Configuration Management Based on the Telecommunication Management Network (TMN) Architecture, replaces Issue 1.
GR-3010 concerns the functions that support Configuration Management in a telecommunications network and for the interactions
between those functions.
Planning, developing, and supporting operations functions in Network Elements (NEs) and management systems, and linking them
together via well-defined interfaces, are critical steps to introducing new technologies and services into the network. As competition
from multiple sources becomes more prevalent for network operators and service providers, timely and efficient management system
support for new technologies and architectures and the services they enable will prove to be the differentiator and the key to
This GR provides a detailed functional description of Configuration Management based on TMN principles and the Management
Applications Functions (MAFs) defined in GR-2869. It provides requirements for MAFs of the Element Management Layer (EML), the
Network Management Layer, the Service Management Layer (SML) and partial requirements for the Business Management Layer (BML). The MAFs
of the EML are assumed to be capable of interfacing with and managing an administrative domain of Network Elements (NEs) via management
interfaces. Configuration Management receives and processes information from the following sources:
- New and existing customers requesting new services, modifications of services, disconnection of services, or information
about offered services
- Survey responses from existing and prospective customers concerning potential demand for services and service features
- Information about new products and technologies from prospective vendors of telecommunications equipment and OS's
- Changes in rules from regulating bodies concerning such matters as tariffs, service level agreements, the bundling of services,
customization of service products and service features, designation of toll service provider by customer, local number portability,
access by law enforcement, etc.
- Information about competition from advertisements and customers
- Measurements and projections of quantity and quality of service and utilization of resources
- Budgetary constraints.
Configuration Management receives this information and provides critical control, record keeping, validation and scheduling
capabilities. It then carries out three major activities:
- Creation, growth and replacement of the managed telecommunication network
- Provisioning of the network resources to provide services to customers
- Support of databases concerning customers, services, and the structure and states of the network and its components for use by MAFs
of Fault Management, Performance - Management, and other Management Functional Areas.
GR-3010 Issue 1 covered 3 of the 5 function groups of Configuration Management:
- Planning and Engineering
- Status and Control.
GR-3010 Issue 2 completes the coverage of all of Configuration Management by adding
- Service Planning and Negotiation
GR-3010 Issue 2 also clarifies the role of the EML MAFs as having a nodal view of network elements. This is in line with changes made
to ITU-T Recommendation M.3010. Conditional requirements for EML MAFs for managing connectivity between network elements have been
When using GR-3010, you may need to refer to GR-2869. You may also want to refer to GR-836, GR-2963, GR-2915,
GR-2991, GR-3003, FR-439, and certain ANSI Standards and ITU-T Recommendations.
Components of this product are:
Table of Contents:
View Table of Contents