SIST ETS 300 612-1 E1:2003
(Main)Digital cellular telecommunications system (Phase 2) (GSM); Network Management (NM); Part 1: Objectives and structure of network management (GSM 12.00)
- Abstract
This European Telecommunication Standard (ETS) provides the conceptual and methodological framework for the definition of a standardized approach to the management of a PLMN. (This framework is elaborated in the remainder of the 12 series specifications) It introduces concepts developed for the management of telecommunications networks by other standards groups, discusses their use in the context of the management of a PLMN, defines a complete context for PLMN management information and identifies the developments of other management models which can be beneficially employed in the global and integrated management of a PLMN. This ETS also describes the methodology to be employed in the definition of the standardization activity and the scale of the results which are expected to be achieved. PLMN management is described in terms of the objectives for the Operator enterprise. Relationships exist between network management functionality and functionality required to support the enterprise model. While the definition of the enterprise model is outside of the scope of this series of ETSs, an understanding of the requirements is necessary so as to provide the underlying network management procedures.
- Status
- Published
- Publication Date
- 30-Nov-2003
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Dec-2003
- Due Date
- 01-Dec-2003
- Completion Date
- 01-Dec-2003
SIST ETS 300 612-1 E1:2003 is the Slovenian standard identical to ETS 300 612-1 Edition 1. It is a European Telecommunication Standard for Digital cellular telecommunications system (Phase 2) (GSM) Network Management, Part 1: Objectives and structure of network management. The standard sets out the conceptual and methodological framework for managing a Public Land Mobile Network (PLMN) and is written for the people who define, implement, and operate GSM network management.
What does SIST ETS 300 612-1 E1:2003 specify?
SIST ETS 300 612-1 E1:2003 specifies the framework for a standardized approach to PLMN management. It explains the management concepts, the modelling approach, and the structure of the GSM 12-series that develops the subject further.
The scope links network management to the operator enterprise view. In practice, that means the document is about how PLMN management should support operator objectives, service control, maintenance, and information exchange, not about one specific network element in isolation.
The document is organized into five main clauses and two normative annexes:
| Part | What it covers |
|---|---|
| Clause 1 | Scope, normative references, definitions and abbreviations |
| Clause 2 | Objectives of Operations, Administration & Maintenance (OAM) of a PLMN |
| Clause 3 | Application of Telecommunications Management Network (TMN) concepts to the PLMN |
| Clause 4 | The PLMN TMN information model |
| Clause 5 | Introduction to the GSM Operations, Administration and Maintenance ETSs |
| Annex A | GDMO definitions for GSM-specific high level managed objects |
| Annex B | Definition of common management functions |
What are the key requirements of SIST ETS 300 612-1 E1:2003?
SIST ETS 300 612-1 E1:2003 is mainly a framework and methodology standard. Its key content is the set of principles that later GSM management specifications should follow, and the points below are the most useful for implementation and evaluation.
PLMN management should support operator objectives and Quality of Service
Clause 2 says PLMN management should integrate operator activities, support coherent information exchange, and help achieve Quality of Service (QoS) objectives. It also ties management to business areas such as subscriber administration, billing, inter-operator accounting, revenue from network resources, and customer services. For a reader, this means management design is not only technical - it has to support how the operator runs the service.
OAM should be efficient, modular, and easy to supervise
Clause 2.2 describes the target OAM environment: modular hardware, configurable software, simple man-machine interfaces, self-control where possible, low failure rate, and simplified maintenance. In practice, this pushes designs toward systems that are easier to expand, easier to troubleshoot, and cheaper to run over their lifetime.
Maintenance is treated as a process with clear steps
Clause 2.4 describes maintenance as reactive or proactive and gives a clear process: monitor, detect, localize, rectify, restore, and record. This matters because it defines what an operator or maintenance organization should be able to do after alarms, trend changes, or customer complaints. It also links routine maintenance to operating conditions such as temperature, humidity, dust, and busy-hour traffic.
TMN concepts are the basis for GSM network management
Clause 3 adopts the Telecommunications Management Network (TMN) concept as the basis for PLMN management. It uses the object-oriented paradigm and the OSI systems management framework, and it introduces the standard TMN building blocks: Operations Systems Functions (OSF), Data Communication Function (DCF), Mediation Function (MF), Network Element Functions (NEFs), Q Adaptor Functions (QAF), and Work Station Functions (WSFs). For implementers, this is the architectural language used to split functions and interfaces in a controlled way.
The information model is built from managed objects
Clause 4 defines the PLMN management model in terms of managed objects and their relationships such as inheritance and containment. It states that ISO/CCITT GDMO templates are used to specify managed objects, and it discusses top-down, bottom-up, and pragmatic modelling approaches. This is important because it tells designers how management information should be structured before they write protocol or interface details.
The GSM 12-series is organized by management service areas
Clause 5 groups PLMN management into administration and commercial, security, operations and performance, change, and maintenance. It also classifies management services as applicable as is, not applicable, or applicable with extensions or enhancements for mobile services. For a buyer or engineer, this tells you how the family of GSM management standards is split and which parts address which operational topic.
Annex A and Annex B provide the formal object definitions and common functions
Annex A gives the formal GDMO definitions for GSM-specific high level managed objects such as aucFunction, bssFunction, hlrFunction, mscFunction, plmnNetwork, smsGIWFunction, and vlrFunction. Annex B defines common management functions used across multiple services, including event report forwarding, information logging, and bulk data transfer between the Operations System and the Network Element. In practice, these annexes are the technical core for modelling and implementing GSM management information.
What terms does SIST ETS 300 612-1 E1:2003 define?
- Public Land Mobile Network (PLMN) - The mobile network being managed, including the functional units that provide mobile telecommunications services.
- Telecommunications Management Network (TMN) - The management framework used to organize supervision, control, and information exchange across the network.
- Operations, Administration and Maintenance (OAM) - The set of activities used to operate the network, administer service and subscriber aspects, and maintain service quality.
- Operations Systems Functions (OSF) - TMN functions that support management operations, planning, supervision, and related control tasks.
- Network Element Functions (NEFs) - Functions performed in the network elements themselves, including local management-related capabilities.
- Guidelines for the Definition Of Managed Objects (GDMO) - The object definition method used to specify managed objects in the information model.
- Shared Management Knowledge (SMK) - The common management knowledge used to specify standardized management interfaces.
Who uses SIST ETS 300 612-1 E1:2003?
SIST ETS 300 612-1 E1:2003 is used by GSM network operators, standards developers, system integrators, and equipment vendors working on network management. It is especially relevant to people defining OAM architecture, management information models, and standardized interfaces between operations systems and network elements.
In practice, the standard supports tasks such as:
- planning GSM network management architecture
- defining managed objects and object relationships
- structuring subscriber, equipment, and service administration
- organizing fault, performance, configuration, and security-related management work
- designing interfaces for BSS, HLR, VLR, MSC, EIR, AUC, and related functions
- mapping management functions between OS and NE implementations
Which standards are used with SIST ETS 300 612-1 E1:2003?
The document relies on several TMN, OSI, and GSM references to define its management framework:
- CCITT Recommendation M.3010 - gives the general principles for TMN.
- CCITT Recommendation X.701 - provides the Systems Management Functional Areas that frame management services.
- CCITT Recommendation M.3020 - defines the TMN interface specification methodology.
- CCITT Recommendation M.3200 - introduces TMN management services.
- CCITT Recommendation M.3400 - covers TMN management functions.
- CCITT Recommendation M.3100 - provides the Generic Network Information Model.
- CCITT Recommendations X.720, X.721, and X.722 - give the systems management information model, definition rules, and managed object guidelines used for GDMO-based modelling.
- CCITT Recommendations X.730 to X.745 - supply common OSI systems management functions such as alarm reporting, event reporting, logging, accounting meter, workload monitoring, test management, and summarization.
- ETS 300 612-2 to ETS 300 624 and ETR 128 - supply the companion GSM Network Management parts for common aspects, subscriber and equipment administration, security, performance, call and event data, configuration/change control, BSS management, A-bis procedures, BSC interworking, and managed object registration.
What does the SIST ETS 300 612-1 E1:2003 document contain?
SIST ETS 300 612-1 E1:2003 contains a conceptual description of GSM network management, not just a list of interface rules. It includes figures showing the relationship of TMN to the telecommunications network and an example PLMN TMN functional architecture.
It also contains a detailed discussion of object-oriented modelling for PLMN management, including modelling principles, registration of information models, and the high-level object model containment structure.
Annex A provides formal GDMO definitions, package definitions, attributes, name bindings, syntax definitions, and ASN.1 modules for GSM-specific managed objects. Annex B provides the formal definition of common management services and common transfer-related management functions, including actions, notifications, and the related data transfer control packages used between Operations Systems and Network Elements.
Get Certified
Connect with accredited certification bodies for this standard
ANCE
Mexican certification and testing association.
Intertek Slovenia
Intertek testing, inspection, and certification services in Slovenia.
LNE (Laboratoire National de Métrologie et d'Essais)
French national laboratory for metrology and testing.
Sponsored listings
Frequently Asked Questions
SIST ETS 300 612-1 E1:2003 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Digital cellular telecommunications system (Phase 2) (GSM); Network Management (NM); Part 1: Objectives and structure of network management (GSM 12.00)". This standard covers: This European Telecommunication Standard (ETS) provides the conceptual and methodological framework for the definition of a standardized approach to the management of a PLMN. (This framework is elaborated in the remainder of the 12 series specifications) It introduces concepts developed for the management of telecommunications networks by other standards groups, discusses their use in the context of the management of a PLMN, defines a complete context for PLMN management information and identifies the developments of other management models which can be beneficially employed in the global and integrated management of a PLMN. This ETS also describes the methodology to be employed in the definition of the standardization activity and the scale of the results which are expected to be achieved. PLMN management is described in terms of the objectives for the Operator enterprise. Relationships exist between network management functionality and functionality required to support the enterprise model. While the definition of the enterprise model is outside of the scope of this series of ETSs, an understanding of the requirements is necessary so as to provide the underlying network management procedures.
This European Telecommunication Standard (ETS) provides the conceptual and methodological framework for the definition of a standardized approach to the management of a PLMN. (This framework is elaborated in the remainder of the 12 series specifications) It introduces concepts developed for the management of telecommunications networks by other standards groups, discusses their use in the context of the management of a PLMN, defines a complete context for PLMN management information and identifies the developments of other management models which can be beneficially employed in the global and integrated management of a PLMN. This ETS also describes the methodology to be employed in the definition of the standardization activity and the scale of the results which are expected to be achieved. PLMN management is described in terms of the objectives for the Operator enterprise. Relationships exist between network management functionality and functionality required to support the enterprise model. While the definition of the enterprise model is outside of the scope of this series of ETSs, an understanding of the requirements is necessary so as to provide the underlying network management procedures.
SIST ETS 300 612-1 E1:2003 is classified under the following ICS (International Classification for Standards) categories: 33.070.50 - Global System for Mobile Communication (GSM). The ICS classification helps identify the subject area and facilitates finding related standards.
SIST ETS 300 612-1 E1:2003 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
SLOVENSKI STANDARD
01-december-2003
'LJLWDOQLFHOLþQLWHOHNRPXQLNDFLMVNLVLVWHP ID]D ¤±8SUDYOMDQMHRPUHåMD 10 ±
GHO &LOMLLQ]JUDGEDXSUDYOMDQMDRPUHåMD *60
Digital cellular telecommunications system (Phase 2) (GSM); Network Management
(NM); Part 1: Objectives and structure of network management (GSM 12.00)
Ta slovenski standard je istoveten z: ETS 300 612-1 Edition 1
ICS:
33.070.50 Globalni sistem za mobilno Global System for Mobile
telekomunikacijo (GSM) Communication (GSM)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
EUROPEAN ETS 300 612-1
TELECOMMUNICATION August 1996
STANDARD
Source: ETSI TC-SMG Reference: DE/SMG-061200P
ICS: 33.060.50
Key words: Digital cellular telecommunications system, Global System for Mobile Communications (GSM)
Digital cellular telecommunications system (Phase 2);
Network Management (NM);
Part 1: Objectives and structure of Network Management
(GSM 12.00)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.fr
Tel.: +33 92 94 42 00 - Fax: +33 93 65 47 16
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.
© European Telecommunications Standards Institute 1996. All rights reserved.
Page 2
ETS 300 612-1: August 1996 (GSM 12.00 version 4.5.1)
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.
Page 3
ETS 300 612-1: August 1996 (GSM 12.00 version 4.5.1)
Contents
Foreword .7
Introduction.7
1 Scope .9
1.1 Normative references .10
1.2 Definitions and abbreviations.13
2 Objectives of Operations, Administration & Maintenance (OAM) of a PLMN .14
2.1 PLMN requirements for Network Management .14
2.1.1 Standardized OAM functionality .14
2.1.2 Inter-Network operation.15
2.1.3 Quality of Service .15
2.2 Targets of the OAM of a PLMN .15
2.3 The service and business areas of a PLMN.16
2.3.1 Administration of subscribers .16
2.3.2 Billing.16
2.3.3 Inter-operator accounting .16
2.3.4 Maximising revenue from PLMN resources .17
2.3.5 Customer services .17
2.4 The maintenance area of a PLMN.17
2.4.1 Alarms .17
2.4.2 Operating trends.18
2.4.3 Customer complaints .18
2.4.4 Software maintenance.18
2.4.5 Maintenance requirements.18
2.5 Other aspects of the OAM of a PLMN .19
3 The Application of TMN concepts to the PLMN .20
3.1 TMN concept of ETSI and CCITT.20
3.1.1 TMN architecture.23
3.1.2 Functional components of the TMN .23
3.1.2.1 Operations Systems Functions (OSF).23
3.1.2.2 Reference points .24
3.1.2.3 Data Communication Function (DCF) .24
3.1.2.4 Mediation Function (MF).24
3.1.2.5 Network Element Functions (NEFs) .24
3.1.2.6 Q Adaptor Functions (QAF).25
3.1.2.7 Work Station Functions (WSFs).25
3.1.3 TMN standard interfaces.25
3.1.3.1 Specifying Interfaces .25
3.1.3.2 Shared Management Knowledge (SMK) .28
3.2 PLMN Network Management Implementation.29
4 The PLMN TMN Information Model .30
4.1 Towards an Object-Based Management Information Model .30
4.1.1 Modelling techniques and guidelines.30
4.1.2 Key definitions .30
4.1.2.1 Resource .30
4.1.2.2 Object and Managed Object.30
4.1.2.3 Hierarchies.31
4.1.3 Objectives of modelling .31
4.1.4 Benefits and limitations of O-O Modelling .32
4.1.4.1 Benefits.32
4.1.4.2 Limitations.32
4.1.4.3 Constraints.33
4.1.4.4 Support of variants.33
Page 4
ETS 300 612-1: August 1996 (GSM 12.00 version 4.5.1)
4.1.5 Providing different views. 33
4.1.6 Added value functions . 34
4.1.7 Logically Layered Model . 35
4.1.8 Some main difficulties of total management. 36
4.2 Methodology towards an Information Model . 37
4.2.1 Top down . 37
4.2.2 Bottom up . 37
4.2.3 A pragmatic approach. 39
4.2.4 Information model registration . 40
4.2.4.1 The ETSI sub-tree. 40
4.2.4.2 Information Model Identifiers. 41
4.3 Information Models. 41
4.3.1 Types of Information Models . 41
4.3.2 High level object model containment. 42
4.3.2.1 Perspectives. 42
4.3.2.2 Model structure and content . 43
4.3.2.3 Network level object classes. 43
4.3.2.4 Other generic MOCs . 44
4.3.2.5 GSM specific MOCs. 44
4.3.2.6 Management of signalling systems. 45
4.3.2.7 Instantiation example . 45
5 Introduction to the GSM Operations, Administration and Maintenance ETSs. 46
5.1 PLMN Management Functional Areas . 46
5.1.1 Administration and commercial . 46
5.1.2 Security. 46
5.1.3 Operations and performance. 46
5.1.4 Change . 47
5.1.5 Maintenance . 47
5.2 Management services . 48
5.3 Management Service Components. 49
5.4 Structure of the GSM 12-Series . 49
5.4.1 General specifications . 49
5.4.2 Network Management Functions. 50
5.4.3 TMN interface specifications . 52
Annex A (normative): GDMO definitions for GSM-Specific High Level Managed Objects. 55
A.1 Managed Object Classes . 55
A.1.1 aucFunction. 55
A.1.2 bssFunction. 55
A.1.3 callRecordingFunction. 56
A.1.4 eirFunction. 56
A.1.5 hlrFunction. 56
A.1.6 mscFunction. 57
A.1.7 plmnNetwork . 57
A.1.8 smsGIWFunction . 58
A.1.9 vlrFunction. 59
A.2 Package definitions. 60
A.3 ATTRIBUTE DEFINITIONS. 60
A.3.1 aucFunctionId. 60
A.3.2 bssFunctionId. 60
A.3.3 setOfCc . 60
A.3.4 eirFunctionId. 60
A.3.5 eirId . 61
A.3.6 eirNumber . 61
A.3.7 hlrFunctionId. 61
A.3.8 listOfSupportedBS. 61
A.3.9 listOfSupportedSS. 62
A.3.10 mcc. 62
A.3.11 mnc . 62
Page 5
ETS 300 612-1: August 1996 (GSM 12.00 version 4.5.1)
A.3.12 mscFunctionId .62
A.3.13 mscId .63
A.3.14 mscNumber .63
A.3.15 setOfNdc.63
A.3.16 smsGIWFunctionId.63
A.3.17 vlrFunctionId .64
A.3.18 vlrId .64
A.3.19 vlrNumber .64
A.4 Actions.64
A.5 Notifications.64
A.6 Parameters.64
A.7 NAME BINDINGS.65
A.7.1 managedElement-plmnNetwork NAME BINDING.65
A.7.2 hlrFunction-managedElement NAME BINDING .65
A.7.3 aucFunction-managedElement NAME BINDING .65
A.7.4 vlrFunction-managedElement NAME BINDING .65
A.7.5 mscFunction-managedElement NAME BINDING .66
A.7.6 eirFunction-managedElement NAME BINDING .66
A.7.7 bssFunction-managedElement NAME BINDING.66
A.7.8 smsGIWFunction-managedElement NAME BINDING.66
A.8 SYNTAX DEFINITIONS .67
Annex B (normative): Definition of Common Management Functions .69
B.1 Description of Common Management Services.69
B.1.1 Forwarding of Event Reports .69
B.1.2 Information Logging .69
B.1.3 Bulk Data Transfer between the OS and the NE.69
B.1.3.1 Transfer of data from the NE to the OS requested by the OS .70
B.1.3.2 Transfer of Data from the NE to the OS requested by the NE.70
B.1.3.3 Transfer of Data from the OS to the NE requested by the OS.70
B.1.3.4 Error conditions .71
B.2 GDMO definitions for Common Management Functions .73
B.2.1 MANAGED OBJECT CLASSES.73
B.2.1.1 simpleFileTransferControl .73
B.2.1.2 generalDataTransferControlFunction.73
B.2.1.3 Recommendation X.721: 1992 alarmRecord.73
B.2.1.4 Recommendation X.721: 1992 attributeValueChangeRecord .73
B.2.1.5 Recommendation X.721: 1992 eventForwardingDiscriminator.73
B.2.1.6 Recommendation X.721: 1992 log.73
B.2.1.7 Recommendation X.721: 1992 objectCreationRecord.73
B.2.1.8 Recommendation X.721: 1992 objectDeletionRecord .73
B.2.1.9 Recommendation X.721: 1992 stateChangeRecord.73
B.2.1.10 transferReadyRecord .74
B.2.1.11 bulkTransferErrorRecord.74
B.2.2 Package definitions.75
B.2.2.1 dataTransferUploadControlPackage.75
B.2.2.2 dataTransferDownloadControlPackage .75
B.2.2.3 generalDataTransferControlFunctionPackage.75
B.2.2.4 simpleFileTransferControlBasicPackage .76
B.2.2.5 transferNotificationArgPackage.76
B.2.2.6 bulkTransferErrorPackage .76
B.2.3 Attribute Definitions.77
B.2.3.1 generalDataTransferControlFunctionId.77
B.2.3.2 simpleFileTransferControlId .77
B.2.3.3 fileListValues .77
B.2.3.4 linkedTransferIdValue .77
Page 6
ETS 300 612-1: August 1996 (GSM 12.00 version 4.5.1)
B.2.3.5 transferIdValue . 77
B.2.4 ACTIONS . 78
B.2.4.1 requestTransferUp. 78
B.2.4.2 transferUpReceived. 78
B.2.4.3 requestTransferDown . 78
B.2.4.4 transferDownComplete. 79
B.2.5 NOTIFICATIONS .80
B.2.5.1 transferUpReady. 80
B.2.5.2 bulkTransferError. 80
B.2.5.3 transferDownReady . 80
B.2.6 NAME BINDINGS.81
B.2.6.1 generalDataTransferControlFunction-managedElement. 81
B.2.6.2 simplefileTransferControl-generalDataTransferControlFunction. 81
B.2.7 SYNTAX DEFINITIONS . 82
History. 85
Page 7
ETS 300 612-1: August 1996 (GSM 12.00 version 4.5.1)
Foreword
This European Telecommunication Standard (ETS) was produced by the Special Mobile Group (SMG)
Technical Committee of the European Telecommunications Standards Institute (ETSI).
This ETS provides the conceptual and methodological framework for the definition of a standardized
approach to the management of a PLMN within the Digital cellular telecommunications system. This ETS
corresponds to GSM technical specification, GSM 12.00, version 4.5.1 and is part 1 of a 2 part ETS as
described below:
GSM 12.00 ETS 300 612-1: "Digital cellular telecommunication system (Phase 2);
Network Management (NM); Part 1: Objectives and structure of Network
Management".
GSM 12.01 ETS 300 612-2: "Digital cellular telecommunication system (Phase 2); Network
Management (NM); Part 2: Common aspects of GSM Network Management".
NOTE: TC-SMG has produced documents which give technical specifications for the
implementation of the Digital cellular telecommunications system. Historically, these
documents have been identified as GSM Technical Specifications (GSM-TSs). These
specifications may subsequently become I-ETSs (Phase 1), or European
Telecommunication Standards (ETSs)(Phase 2), whilst others may become ETSI
Technical Reports (ETRs). These ETSI-GSM Technical Specifications are, for editorial
reasons, still referred to in this ETS.
Transposition dates
Date of adoption of this ETS: 31 August 1996
Date of latest announcement of this ETS (doa): 30 November 1996
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 May 1997
Date of withdrawal of any conflicting National Standard (dow): 31 May 1997
Introduction
The goals of implementing a Public Land Mobile Network (PLMN) and its continued effective operation,
administration and maintenance are important issues. The creation of a system for the management of a
PLMN, implemented according to the specification series 01 to 11 and the open, multi-vendor
environment, demands a level of standardization of the inter-connectivity of the management components
and their functionality. A system for Operation, Administration and Maintenance (OAM), using concepts of
telecommunications management networks (TMN), potentially provides for a suitable degree of
management integration in achieving these goals.
Page 8
ETS 300 612-1: August 1996 (GSM 12.00 version 4.5.1)
Approach
In order to achieve the above aim, the GSM 12 series of specifications has been devised, taking into
account the following:
- GSM system philosophy, as given by the GSM 01 to 11 series of specifications, which define key
functional areas.
- Relevant standardization work on network management and open systems management (as well
as its realization, Telecommunications Management Network, TMN) already carried out by ISO,
CCITT, ETSI etc.
- Existing operator and manufacturer experience in the management (i.e. operating, maintaining,
administering) of telecommunication networks.
Accordingly, this ETS, and the other specifications of the 12-series, should adhere to the following
guidelines:
- There should be internal consistency of the 12 series with the relevant system aspects given in 01
to 11 series Specifications, so that a commonly agreed view of the realization of a PLMN emerges.
- Avoidance of "re-writing" existing recommendations and specifications, but only referencing those
applicable as far as possible. However, to ensure harmony with any such existing documents, some
general items, such as definitions and figures may be reproduced within the 12 series if they are
deemed important or helpful in establishing a common understanding.
- Analysis of current network management concepts and experience both with a top-down and
bottom-up approach, so that a comprehensive and realistic management concept emerges.
Page 9
ETS 300 612-1: August 1996 (GSM 12.00 version 4.5.1)
1 Scope
This European Telecommunication Standard (ETS) provides the conceptual and methodological
framework for the definition of a standardized approach to the management of a PLMN. (This framework
is elaborated in the remainder of the 12-series specifications) It introduces concepts developed for the
management of telecommunications networks by other standards groups, discusses their use in the
context of the management of a PLMN, defines a complete context for PLMN management information
and identifies the developments of other management models which can be beneficially employed in the
global and integrated management of a PLMN.
This ETS also describes the methodology to be employed in the definition of the standardization activity
and the scale of the results which are expected to be achieved.
PLMN management is described in terms of the objectives for the Operator enterprise. Relationships exist
between network management functionality and functionality required to support the enterprise model.
While the definition of the enterprise model is outside of the scope of this series of ETSs, an
understanding of the requirements is necessary so as to provide the underlying network management
procedures.
Field of application
The concept of the Telecommunications Management Network (TMN) has developed as the result of a
demand for a common management approach to the management of the diversity of equipment types,
functionality and service provision inherent in modern telecommunications networks. This diversity is also
apparent in a PLMN and the adoption of the TMN concept can provide a common management
methodology for:
- public and private networks (including mobile);
- transmission terminals;
- transmission systems;
- restoration systems;
- operations systems and their peripherals;
- digital and analogue exchanges;
- area networks;
- circuit and packet switched networks;
- signalling terminals and systems;
- bearer services and teleservices;
- software provided by or associated with telecommunications services;
- software applications;
- associated support systems;
- the TMN itself.
(For a comprehensive view of the field of application of the TMN, refer to CCITT Recommendation
M.3010 [1])
By extension, the field of application includes radio base station systems and all other components of the
PLMN.
Page 10
ETS 300 612-1: August 1996 (GSM 12.00 version 4.5.1)
Typically a PLMN is a telecommunications system consisting of several functional units necessary to
perform mobile telecommunications services. These functional units include:
- Location Registers (LR);
- Home Location Register(s) (HLR);
- Visitor Location Register(s) (VLR);
- Mobile-services Switching Centre(s) (MSC);
- Base Station Systems (BSS);
- Mobile Stations (MS);
- Equipment Identity Register (EIR);
- Authentication Centre (AUC);
- Inter-working units;
- Transcoders;
- Transmission equipment;
- Echo Suppression equipment.
NOTE: several of the above mentioned functional units may be collocated or even be
accommodated in the same physical implementation.
1.1 Normative references
This ETS incorporates by dated and undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references the latest
edition of the publication referred to applies.
[1] CCITT Recommendation M.3010 (1992): "Principles for a Telecommunications
Management Network (TMN)".
[2] CCITT Recommendation X.701 (ISO IS 10040) (1992): "Information technology
- Open Systems Interconnection - Systems Management Overview".
[3] Draft ETR DTR/NA-043207: "Overview of Telecommunications Management
Network (TMN) standards".
[4] CCITT Recommendation X.200 (1992): " - Information technology - Open
Systems Interconnection - Reference Model of Open Systems Interconnection
for CCITT Applications".
[5] CCITT Recommendation M.3020 (M.meth) (1992): "TMN Interface Specification
Methodology".
[6] CCITT Recommendation M.3200 (M.app) (1992): "TMN Management Services:
Introduction".
[7] CCITT Recommendation M.3400 (M.func) (1992): "TMN Management
Functions".
[8] CCITT Recommendation M.3100 (M.gnm) (1992): "Generic Network Information
Model".
[9] CCITT Recommendation X.720 (ISO 10165-1) (1992): "Information technology -
Open Systems Interconnection - Structure of management information: System
Management Information Model".
[10] CCITT Recommendation X.721 (ISO 10165-2) (1992): "Information technology -
Open Systems Interconnection - Structure of management information:
Definition Of Management Information".
[11] CCITT Recommendation X.722 (ISO 10165-4) (1992): "Information technology -
Open Systems Interconnection - Structure of management information:
Guidelines For The Definition Of Managed Objects".
Page 11
ETS 300 612-1: August 1996 (GSM 12.00 version 4.5.1)
[12] CCITT Recommendation X.730 (ISO 10164-1) (1992): "Information technology -
Open Systems Interconnection - Systems Management: Object management
function".
[13] CCITT Recommendation X.731 (ISO 10164-2) (1992): "Information technology -
Open Systems Interconnection - Systems Management: State Management".
[14] CCITT Recommendation X.732 (ISO 10164-3) (1992): "Information technology -
Open Systems Interconnection - Systems Management: Attributes For
Representing Relationships".
[15] CCITT Recommendation X.733 (ISO 10164-4) (1992): "Information technology -
Open Systems Interconnection - Systems Management: Alarm Reporting".
[16] CCITT Recommendation X.734 (ISO 10164-5) (1992): "Information technology -
Open Systems Interconnection - Systems Management: Event Report
Management Function".
[17] CCITT Recommendation X.735 (ISO 10164-6) (1992): "Information technology -
Open Systems Interconnection - Systems Management: Log Control Function".
[18] CCITT Recommendation X.736 (ISO 10164-7) (1992): "Information technology -
Open Systems Interconnection - Systems Management: Security Alarm
Reporting Function".
[19] CCITT Recommendation X.740 (ISO 10164-8) (1992): "Information technology -
Open Systems Interconnection - Systems Management: Security Audit Trail
Function".
[20] CCITT Recommendation X.741 (ISO DIS 10164-9): "Information technology -
Open Systems Interconnection - Systems Management: Objects And Attributes
For Access Control".
[21] CCITT Recommendation X.742 (ISO CD 10164-10: "Information technology -
Open Systems Interconnection - Systems Management: Accounting Meter
Function".
[22] CCITT Recommendation X.739 (ISO DIS 10164-11) (1994): "Information
technology - Open Systems Interconnection - Systems Management: Workload
Monitoring Function".
[23] CCITT Recommendation X.745 (ISO DIS 10164-12) (1994): "Information
technology - Open Systems Interconnection - Systems Management: Test
Management Function".
[24] CCITT Recommendation X.738 (ISO DIS 10164-13) (1994): "Information
technology - Open Systems Interconnection - Systems Management:
Summarization Function".
[25] CCITT Recommendation E.800 (1988): "Quality of Service; Concepts, Models,
Objectives, Dependability Planning".
[26] ETR 101 (GSM 02.08): "Digital cellular telecommunication system (Phase 2);
Quality of service".
[27] ETR 102 (GSM 03.05): "Digital cellular telecommunication system (Phase 2);
Technical performance objectives".
[28] ETS 300 540 (GSM 03.50): "Digital cellular telecommunication system
(Phase 2); Transmission planning aspects of the speech service in the GSM
Public Land Mobile Network (PLMN) system".
Page 12
ETS 300 612-1: August 1996 (GSM 12.00 version 4.5.1)
[29] ETS 300 577 (GSM 05.05): "Digital cellular telecommunication system
(Phase 2); Radio transmission and reception".
[30] ETS 300 580-6 (GSM 06.32): "Digital cellular telecommunication system (Phase
2); Voice Activity Detection (VAD)".
[31] CCITT Recommendation X.724 (ISO DIS 10165-6): "Information technology -
Open Systems Interconnection - Structure of management information:
Requirements and guidelines for implementation conformance statement
proformas associated with OSI management".
[32] CCITT draft Recommendation Q.821: "Signalling system No. 7 management -
Stage 2 and stage 3 description for the Q3 interface - Alarm Surveillance".
[33] CCITT draft Recommendation Q.822: "Signalling system No. 7 management -
Stage 1, stage 2 and stage 3 description for the Q3 interface -Performance
Measurement".
[34] ISO IS 9596-2: "Information Processing Systems - Open Systems
Interconnection - Management Information Protocol Specification - Part 2:
Common Management Information Protocol (CMIP)".
[35] ETR 128 (GSM 12.30): "Digital cellular telecommunication system (Phase 2);
ETSI object identifier tree; Common domain; Mobile domain Operation and
Maintenance (O & M) managed object registration definition".
[36] ETS 300 612-2 (GSM 12.01): "Digital cellular telecommunication system
(Phase 2); Common aspects of GSM Network Management (NM)".
[37] ETS 300 613 (GSM 12.02): "Digital cellular telecommunication system
(Phase 2); Subscriber, Mobile Equipment (ME) and services data
administration".
[38] ETS 300 614 (GSM 12.03): "Digital cellular telecommunication system
(Phase 2); Security management".
[39] ETS 300 615 (GSM 12.04): "Digital cellular telecommunication system
(Phase 2); Performance data measurements".
[40] ETS 300 616 (GSM 12.05): "Digital cellular telecommunication system
(Phase 2); Subscriber related event and call data".
[41] ETS 300 617 (GSM 12.06): "Digital cellular telecommunication system
(Phase 2); GSM Network Configuration Management and Administration".
[42] ETS 300 619 (GSM 12.11): "Digital cellular telecommunication system
(Phase 2); Fault Management of the Base Station System (BSS)".
[43] ETS 300 622 (GSM 12.20): "Digital cellular telecommunication system
(Phase 2); Base Station System (BSS) Management Information".
[44] ETS 300 623 (GSM 12.21): "Digital cellular telecommunication system
(Phase 2); Network Management (NM) procedures and message on the A-bis
interface".
[45] ETS 300 624 (GSM 12.22): "Digital cellular telecommunication system
(Phase 2); Interworking of GSM Network Management (NM) procedures and
messages at the Base Station Controller (BSC)".
Page 13
ETS 300 612-1: August 1996 (GSM 12.00 version 4.5.1)
1.2 Definitions and abbreviations
Terminology is aligned with ETSI TCR-TR 003 Vocabulary of terms for TMN.
For the purposes of this ETS, the following abbreviations apply:
ADC Administration Centre
AOM Application of Object Management
ASN.1 Abstract Syntax Notation (number) 1
AUC Authentication Centre
bcf base (station) control function
BSC Base Station Controller
BSS Base Station System
BTS Base Transceiver Station
DCF Data Communication Function
DCN Data Communication Network
EIR Equipment Identity Register
EWOS European Workshop on Open Systems
GDMO Guidelines for the Definition Of Managed Objects
HLR Home Location Register
H/W Hardware
IMEI International Mobile station Equipment Identity
IMSI International Mobile Subscriber Identity
ISDN Integrated Services Digital Network
ISO International Standards Organization
ISP International Standard Profile
LLA Logically Layered Architecture
LR Location Register
MCF Message Communication Function
MD Mediation Device
MF Mediation Function
MOCS Managed Object Conformance Statement
MS Mobile Station
MSC Mobile-services Switching Centre
NE Network Element
NEF Network Element Function
NM Network Management
NMC Network Management Centre
NMF OSI Network Management Forum
OAM Operation, Administration and Maintenance
OMC Operations and Maintenance Centre
O-O Object-Oriented
OS Operations System
OSF Operations System Function
OSI Open Systems Interconnection
pcm pulse code modulation
PICS Protocol Implementation Conformance Statement
PLMN Public Land Mobile Network
QA Q (Interface) - Adapter
QAF Q - Adapter Function
QOS Quality of Service
SMK Shared Management Knowledge
S/W Software
TMN Telecommunications Management Network
VLR Visitor Location Register
WS Work Station
WSF Work Station Function
Page 14
ETS 300 612-1: August 1996 (GSM 12.00 version 4.5.1)
2 Objectives of Operations, Administration & Maintenance (OAM) of a PLMN
The OAM of a PLMN will require all aspects of the OAM of existing terrestrial telecommunications with
extensions and enhancements to encompass the particular requirements of mobile telephony.
The management should provide all the capabilities necessary for the integration of all the activities
involved in the operation of a mobile network. These activities can be described in terms of Business and
Service criteria. These functions are distanced from the actual PLMN infrastructure, except for the local
maintenance intervention on a network element. (See figure 2/12.00 for an example functional
architecture.)
The objective of PLMN management is to integrate the spectrum of PLMN Operator activities to achieve
coherent and seamless information exchange, support Quality of Service objectives and assist in
achieving business objectives.
2.1 PLMN requirements for Network Management
The basic requirements for an integrated mobile communications system lead to the following general
objectives for PLMN Management:
- Integrated operation of the elements of a PLMN using standardized functionality;
- Inter-PLMN operation of the mobile system;
- Information on the Quality of Service provided.
2.1.1 Standardized OAM functionality
If Operators wish to make use of the advantages in procurement of a standardized PLMN, there is also a
need for standardization of OAM functions to allow proper inter-working of management for network
elements from different manufacturers.
To restrict neither the Operator nor the manufacturer, the standardization provides a logically structured
framework for the necessary functions with freedom for supplementary additions and room for particular
expansions and future evolution. This can be achieved by a management system, defined by a logical
concept with the goal of true implementation.
The 12-series of Specifications defines a functional architecture with immediate relevance to the
management of a PLMN using a logically structured functional model. Standardization is introduced in
those areas where it is felt to be appropriate (utilizing accepted techniques) with reference to the work of
other TMN and Systems Management standardization groups.
Management functions can be classified in terms of their level of definition, to facilitate the objectives of
GSM. These are described in the following paragraphs.
a) Operational standardization:
Functions included here are those necessary to support inter-PLMN roaming and network inter-
working with other PLMNs or other networks.
b) Multi-vendor environment standardization:
If a PLMN Operator wishes to operate in a multi-vendor environment, management functions and
interfaces should be standardized to allow common modes of operation. This may include
performance data collection, message format standards, security methodologies and consistency of
maintenance approach.
c) PLMN management facilities:
Functional areas within the control of a PLMN Operator are recommended for standardization but
particular Operator requirements will impinge on the extent of the possible definition.
d) Specific PLMN management or national requirements:
These are considered to be outside of the scope of standardization.
Page 15
ETS 300 612-1: August 1996 (GSM 12.00 version 4.5.1)
It is therefore necessary to determine three immediate levels of optional implementation criteria for the
management functions described and defined in this series of specifications:
Mandatory: the implementation of the function shall accord with the definition to allow successful
working and inter-working of the PLMN;
Standard Option: implementation of the function is optional but, if implemented, the definition contained
in the 12-series shall be employed;
Optional: the feature is described but both the use of the feature and the implementation method
are optional.
2.1.2 Inter-Network operation
Inter-Network operations include:
- operation between PLMNs (of the same type) with Operators in different countries;
- (inter-PLMN) operation between PLMN(s) (of the same type) with Operator(s) in the same country;
- operation (inter-working) with
...