SIST ETS 300 612-2 E1:2003
(Main)Digital cellular telecommunications system (Phase 2) (GSM); Network Management (NM); Part 2: Common aspects of GSM/DCS 1800 network management (GSM 12.01)
Digital cellular telecommunications system (Phase 2) (GSM); Network Management (NM); Part 2: Common aspects of GSM/DCS 1800 network management (GSM 12.01)
This European Telecommunication Standard (ETS) provides the survey of the GSM Network Management (NM) interfaces in accordance with the requirements in the GSM standards and with the architectural concept and methodology defined in GSM 12.00 (ETS 300 612-1)[80]. NOTE: The requirements for GSM covers the requirements for a DCS 1800 network as well. The various possibilities for transfer of NM messages between the NM entities and Network Elements (NEs) are outlined in this standard, and the requirements are set up for an OSI protocol stack appropriate for a GSM TMN. This ETS describes the relevant protocol profiles for Q3 and Qx interfaces.
Digitalni celični telekomunikacijski sistem (faza 2) ¬– Upravljanje omrežja (NM) – 2. del: Skupni vidiki upravljanja omrežja GSM/DCS 1800 (GSM 12.01)
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
01-december-2003
'LJLWDOQLFHOLþQLWHOHNRPXQLNDFLMVNLVLVWHP ID]D ¤±8SUDYOMDQMHRPUHåMD 10 ±
GHO 6NXSQLYLGLNLXSUDYOMDQMDRPUHåMD*60'&6 *60
Digital cellular telecommunications system (Phase 2) (GSM); Network Management
(NM); Part 2: Common aspects of GSM/DCS 1800 network management (GSM 12.01)
Ta slovenski standard je istoveten z: ETS 300 612-2 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-2
TELECOMMUNICATION August 1996
STANDARD
Source: ETSI TC-SMG Reference: DE/SMG-061201P
ICS: 33.060.50
Key words: Digital cellular telecommunications system, Global System for Mobile communications (GSM)
R
GLOBAL SYSTEM FOR
MOBILE COMMUNICATIONS
Digital cellular telecommunications system (Phase 2);
Network Management (NM);
Part 2: Common aspects of GSM/DCS 1800
Network Management
(GSM 12.01)
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-2: August 1996 (GSM 12.01 version 4.4.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-2: August 1996 (GSM 12.01 version 4.4.1)
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Abbreviations.12
4 GSM Network Management.14
4.1 General TMN Structural aspects .14
4.1.1 Reference Points versus Interfaces .14
4.1.2 Hierarchical Interworking between Function Blocks.14
4.1.3 Implementation of Interfaces According to M.3010.16
4.2 Implementation requirements .18
4.2.1 GSM Phase 2 implementation requirements for the Q3 Interface .18
4.2.2 GSM Phase 2 implementation requirements for the Qx Interface .20
4.2.3 GSM Phase 2 implementation requirements for interworking between Q3
and Qx Interfaces.20
5 GSM Network Management Interfaces.21
5.1 General .21
5.2 NM Interfaces within a GSM Network.21
5.2.1 Q3 Interface.21
5.2.2 Qx Interface.21
5.3 The Man Machine Interface (MMI).22
6 GSM Network Management protocols and services at the Q3 Interface .23
6.1 General .23
6.2 Communication Model For Management Information Transfer.23
6.2.1 General.23
6.2.2 Common Management Application Services Element (CMISE) .23
6.2.3 Specific Management Application Service Element.25
6.2.4 Description of how CMISE, ACSE, ROSE and OSI Presentation Layer
Interact .25
6.3 Protocol capabilities.27
6.3.1 Naming and addressing capability .27
6.3.1.1 General aspects .27
6.3.1.2 SCCP addressing .27
6.3.1.3 X.25 addressing.27
6.3.1.4 OSI-LAN addressing.27
6.3.1.5 ISDN addressing.27
6.3.1.6 Transport addressing.27
6.3.1.7 Addressing on the application layer.27
6.3.1.8 Implementation example .28
6.3.2 Connection-oriented communication capability.28
6.3.3 Connectionless communication capability.28
6.3.4 File Transfer Capability .28
6.3.5 Remote Operation Handling.28
6.4 Implementation requirements .28
6.4.1 General.28
6.4.2 Layer 1 to 3.28
6.4.2.1 Requirements specific to CCITT Signalling System No.7 .29
6.4.2.2 Requirements specific to the A Interface.29
6.4.2.3 Requirements specific to X.25.29
6.4.2.4 Requirements specific to ISDN.30
6.4.3 Transport layer .30
6.4.4 Session layer.30
Page 4
ETS 300 612-2: August 1996 (GSM 12.01 version 4.4.1)
6.4.5 Presentation layer. 30
6.4.6 Application layer. 31
6.5 The use of QOS parameters in OSI layer services and protocols . 32
6.5.1 General . 32
6.5.2 Quality of Session Service. 33
6.5.3 Quality of Transport Service . 33
6.5.4 Quality of Network Service . 33
6.5.5 Quality of Data Link Service . 33
6.5.6 Quality of Physical Service . 33
7 Implementation requirements for the Qx NM Interface . 34
7.1 General. 34
7.2 Layer 1 . 34
7.3 Layer 2 . 34
7.4 Layer 3 . 34
8 Inter-TMN operation. 35
8.1 General. 35
8.2 Interface to other Management Systems . 35
Annex A (informative): GSM Protocol Conformance Statements (PICS). 36
Annex B (informative): Example for Implementation of an Addressing Scheme. 37
B.1 Network Addresses . 37
B.1.1 X.25. 37
B.1.1.1 Transport layer as subsequent protocol . 37
B.1.1.2 PAD as subsequent protocol . 37
B.1.1.3 X.25-SCCP interworking as subsequent protocol . 37
B.1.2 SCCP . 37
B.2 Upper layer addresses. 37
B.3 Application Entity Title (AET) . 38
History. 39
Page 5
ETS 300 612-2: August 1996 (GSM 12.01 version 4.4.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 a survey of the GSM network management interfaces and describes the relevant
protocol profiles for Q3 and Qx interfaces within the Digital cellular telecommunications system. This ETS
corresponds to GSM technical specification, GSM 12.01, version 4.4.1 and is part 2 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
Page 6
ETS 300 612-2: August 1996 (GSM 12.01 version 4.4.1)
Blank page
Page 7
ETS 300 612-2: August 1996 (GSM 12.01 version 4.4.1)
1 Scope
This European Telecommunication Standard (ETS) provides the survey of the GSM Network
Management (NM) interfaces in accordance with the requirements in the GSM standards and with the
architectural concept and methodology defined in GSM 12.00 (ETS 300 612-1) [80].
NOTE: The requirements for GSM covers the requirements for a DCS 1800 network as well.
The various possibilities for transfer of NM messages between the NM entities and Network Elements
(NEs) are outlined in this standard, and the requirements are set up for an OSI protocol stack appropriate
for a GSM TMN.
This ETS describes the relevant protocol profiles for Q3 and Qx interfaces.
2 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 M.3010 (1988): "Principles for a Telecommunications Management
Network (TMN).
[2] CCITT Draft Q.811 (1992): "Lower Layer Protocol Profiles for the Q3 Interface".
[3] CCITT Draft Q.812 (1992): "Upper Layer Protocol Profiles for the Q3 Interface".
[4] CCITT G.703 (1988): "Physical/Electrical Characteristics of Hierarchical Digital
Interfaces".
[5] ISO DIS 7498-3 (1987): "Information Processing Systems - Open Systems
Interconnection - OSI Reference Model - Part 3: Naming and Addressing".
[6] ISO DIS 7498-4 (1987): "Information Processing Systems - Open Systems
Interconnection - OSI Reference Model - Part 4: Management Framework".(See
also CCITT X.700)
[7] ISO IS 8571-1: "Information Processing Systems - Open Systems
Interconnection - File Transfer, Access and Management - Part 1: General
Introduction".
[8] ISO IS 8571-2: "Information Processing Systems - Open Systems
Interconnection - File Transfer, Access and Management - Part 2: Virtual
Filestore Definition".
[9] ISO IS 8571-3: "Information Processing Systems - Open Systems
Interconnection - File Transfer, Access and Management - Part 3: File Service
Definition".
[10] ISO IS 8571-4: "Information Processing Systems - Open Systems
Interconnection - File Transfer, Access and Management - Part 4: File Protocol
Specification".
[11] ISO/IEC ISP 10607-1: "Information technology - International Standardized
Profiles AFTnn - File Transfer, Access and Management - Part 1: Specification
of ACSE, Presentation and Session Protocols for the use by FTAM".
[12] ISO/IEC ISP 10607-2: "Information technology - International Standardized
Profiles AFTnn - File Transfer, Access and Management - Part 2: Specification
of Document Types, Constraint sets and Syntax's".
Page 8
ETS 300 612-2: August 1996 (GSM 12.01 version 4.4.1)
[13] ISO/IEC ISP 10607-3: "Information technology - International Standardized
Profiles AFTnn - File Transfer, Access and Management - Part 2: Specification
of AFT 11 Simple File Transfer Service (Unstructured)".
[14] ISO/IEC DISP 11183-1: "Information technology - International Standardized
Profiles AOMnn.OSI Management - Management communication protocols -
Part 1: Specification of ACSE, presentation and session protocols for the use by
ROSE and CMISE".
[15] ISO DIS 9545 (1988): "Information Processing Systems - Open Systems
Interconnection - Application Layer Structure".
[16] ISO IEC 9595 (1991): "Information technology - Open Systems Interconnection -
Common Management Information Service Definition". (See also X.710)
[17] ISO IEC 9596-1 (1991): "Information technology - Open Systems
Interconnection - Common Management Information Protocol - Part 1
Specification". (See also X.711)
[18] CCITT E.164 (1988): "Numbering Plan for the ISDN Era".
[19] CCITT Q.700 (1988): "Introduction to CCITT Signalling System No.7".
[20] CCITT Q.701 (1988): "Functional Description of the Message Transfer Part
(MTP) of Signalling System No.7".
[21] CCITT Q.702 (1988): "Signalling Data Link".
[22] CCITT Q.703 (1988): "Signalling Link".
[23] CCITT Q.704 (1988): "Signalling Network Functions and Messages".
[24] CCITT Q.705 (1988): "Signalling Network Structure".
[25] CCITT Q.706 (1988): "Message Transfer Part Signalling Performance".
[26] CCITT Q.707 (1988): "Testing and Maintenance".
[27] CCITT Q.708 (1988): "Numbering of International Signalling Point Codes".
[28] CCITT Q.709 (1988): "Hypothetical Signalling Reference Connection".
[29] CCITT Q.711 (1988): "Functional Description of the Signalling Connection
Control Part".
[30] CCITT Q.712 (1988): "Definition and Function of SCCP Messages".
[31] CCITT Q.713 (1988): "SCCP Formats and Codes".
[32] CCITT Q.714 (1988): "Signalling Connection Control Part Procedures".
[33] CCITT Q.775 (1988): "Guidelines for Using Transaction Capabilities".
[34] CCITT Q.795 (1988): "Operations, Maintenance and Administration Part
(OMAP)".
[35] CCITT X.31 (1988): "Support of Packet Mode Terminal Equipment by an
ISDN".
[36] CCITT X.21: "Interface between data terminal equipment and data circuit-
terminating equipment for synchronous operation on public data networks ".
Page 9
ETS 300 612-2: August 1996 (GSM 12.01 version 4.4.1)
[37] CCITT X.21 bis (1988): "Use on public data networks of data terminal
equipment (DTE) which is designed for interfacing to synchronous V-Series
modems ".
[38] CCITT X.25 (1988): "Interface between Data Terminal Equipment (DTE) and
Data Circuit Terminating (DCE) for Terminals operating in the Packet Mode and
connected to Public Data Networks by Dedicated Circuit".
[39] CCITT X.121 (1988): "International Numbering Plan for Public Data Networks".
[40] CCITT X.200 (1988): "Reference Model of Open Systems Interconnection for
CCITT Applications". (see also ISO 7498)
[41] CCITT X.208 (1988): "Specification of Abstract Syntax Notation One (ASN.1)".
(see also ISO 8824 and ISO 8824-AD1)
[42] CCITT X.209: "Specification of Basic Encoding Rules for Abstract Syntax
Notation One (ASN.1)". (see also ISO 8825 and ISO 8825-AD1)
[43] CCITT X.210 (1988): "Open Systems Interconnection (OSI) Layer Service
Definition Conventions".
[44] CCITT X.211 (1988): "Physical Layer Service Definition for Open System
Interconnection (OSI) for CCITT applications".
[45] CCITT X.212 (1988): "Data Link Service Definition for Open System
Interconnection (OSI) for CCITT applications".
[46] CCITT X.213 (1988): "Network Service Definition for Open System
Interconnection (OSI) for CCITT applications". (see also ISO 8348, ISO
8348/AD2 and ISO 8348/AD3)
[47] CCITT X.223 (1988): "Use of X.25 to provide the OSI Connection-mode network
service for CCITT applications". (see also ISO 8878)
[48] CCITT X.214: "Transport Service Definition for Open System Interconnection
(OSI) for CCITT Applications". (see also ISO 8072)
[49] CCITT X.224: "Transport Protocol Specification for Open System
Interconnection (OSI) for CCITT Applications". (see also ISO 8073)
[50] CCITT X.215 (1988): "Session Service Definition for Open System
Interconnection (OSI) for CCITT Applications". (see also ISO 8326 and ISO
8326-AD2)
[51] CCITT X.225 (1988): "Session Protocol Specification for Open System
Interconnection (OSI) for CCITT Applications". (see also ISO 8327 and ISO
8327-AD2)
[52] CCITT X.216 (1988): "Presentation Service Definition for Open System
Interconnection (ISO) for CCITT Applications". (see also ISO 8822)
[53] CCITT X.226 (1988): "Presentation Protocol Specification for Open System
Interconnection (OSI) for CCITT Applications". (see also ISO 8823)
[54] CCITT X.217 (1988): "Association Control Service Definition for OSI for CCITT
Applications". (see also ISO 8649-2)
[55] CCITT X.227 (1988): "Association Control Protocol Specification for OSI for
CCITT Applications". (see also ISO 8650-2)
Page 10
ETS 300 612-2: August 1996 (GSM 12.01 version 4.4.1)
[56] CCITT X.219 (1988): "Remote Operations: Model, Notation and Service
Definition". (see also ISO 9072-1)
[57] CCITT X.229 (1988): "Remote Operations: Protocol Specification". (see also
ISO 9072-2)
[58] CCITT X.290 (1988): "OSI Conformance Testing Methodology and Framework
for Protocol Recommendations for CCITT Applications".
[59] CCITT X.410 (1984): "Message Handling Systems: Remote Operations and
Reliable Transfer Server".
[60] CCITT I.430 (1988): "Basic User-Network Interface - Layer 1 Specification".
[61] CCITT I.431 (1988): "Primary Rate User-Network Interface - Layer 1
Specification".
[62] ISO 7776: "Information processing systems - Data communication - High-level
data link control procedures - Description of the X.25 LAPB-compatible DTE
data link procedures.
[63] CCITT Q.921 (1988): "ISDN User-Network Interface - Data Link Layer
Specification".
[64] CCITT Q.931 (1988): "ISDN User-Network Interface Layer 3 Specification for
Basic Call Control".
[65] ISO 8208: "information processing systems - Data communications - X.25
Packet Level Protocol for Data Terminal Equipment.
[66] ISO 8878: "Information technology - Telecommunications and information
exchange between systems - Use of X.25 to provide the OSI Connection-mode
Network Service.
[67] CCITT I.320 (1988): "ISDN Protocol Reference Model".
[68] CCITT X.612 (1992): "Information Technology - Provision of the OSI
Connection-mode Network Service by Packet-mode Terminal Equipment
Connected to an Integrated Services Digital Network (ISDN)". (See also
ISO/IEC 9574).
[69] ISO 8473: "Information Processing Systems - Local area networks - Protocol for
providing the connectionless-mode network service.
[70] ISO 8802-2: "Information Processing Systems - Local area networks -Part 2 -
Logical link control.
[71] ISO 8802-3: "Information Processing Systems - Local area networks -Part 3 -
Carrier sense multiple access with collision detection - Access method and
physical layer specifications.
[72] GSM 08.04 (ETS 300 588): "Digital cellular telecommunication system
(Phase 2); Base Station System - Mobile-services Switching Centre (BSS -
MSC) interface Layer 1 specification".
[73] GSM 08.06 (ETS 300 589): "Digital cellular telecommunication system
(Phase 2); Signalling transport mechanism specification for the Base Station
System - Mobile-services Switching Centre (BSS - MSC) interface".
[74] GSM 08.08 (ETS 300 590): "Digital cellular telecommunication system
(Phase 2); Mobile Switching Centre - Base Station System (MSC - BSS)
interface Layer 3 specification".
Page 11
ETS 300 612-2: August 1996 (GSM 12.01 version 4.4.1)
[75] GSM 08.52 (ETS 300 593): "Digital cellular telecommunication system
(Phase 2); Base Station Controller - Base Transceiver Station (BSC - BTS)
interface Interface principles".
[76] GSM 08.54 (ETS 300 594): "Digital cellular telecommunication system
(Phase 2); Base Station Controller - Base Transceiver Station (BSC - BTS)
interface Layer 1 structure of physical circuits".
[77] GSM 08.56 (ETS 300 595): "Digital cellular telecommunication system
(Phase 2); Base Station Controller - Base Transceiver Station (BSC - BTS)
interface Layer 2 specification".
[78] GSM 08.58 (ETS 300 596): "Digital cellular telecommunication system
(Phase 2); Base Station Controller - Base Transceiver Station (BSC - BTS)
interface Layer 3 specification".
[79] GSM 08.60 (ETS 300 597): "Digital cellular telecommunication system
(Phase 2); Inband control of remote transcoders and rate adaptors".
[80] GSM 12.00 (ETS 300 612-1): "Digital cellular telecommunication system
(Phase 2); Objectives and structure of Network Management (NM)".
[81] GSM 12.20 (ETS 300 622): "Digital cellular telecommunication system
(Phase 2); Base Station System (BSS) Management Information".
[82] GSM 12.21 (ETS 300 623): "Digital cellular telecommunication system
(Phase 2); Network Management (NM) procedures and message on the A-bis
interface".
[83] GSM 12.22 (ETS 300 624): "Digital cellular telecommunication system
(Phase 2); Interworking of GSM Network Management (NM) procedures and
messages at the Base Station Controller (BSC)".
An overview of the GSM NM ETS is given in GSM 12.00 (ETS 300 612-1)[80], Objectives and Structure of
Network Management (NM).
Page 12
ETS 300 612-2: August 1996 (GSM 12.01 version 4.4.1)
3 Abbreviations
For the puposes of this ETS the following abbreviations apply.
A Agent
AARE A-ASSOCIATE-RESPONSE
AARQ A-ASSOCIATE-REQUEST
ACPM Association Control Protocol Machine
ACSE Association Control Service Element
AE Application Entity
AEQ Application Entity Qualifier
AET Application Entity Title
AFI Authority and Format Identifier
APDU Application Protocol Data Unit
API Application Programming Interface
APQ Application Process Qualifier
ASE Application Service Element
ASN.1 (CCITT) Abstract Syntax Notation One
AT Application Title
BA Basic Access
BSC Base Station Controller
BSS Base Station System
BSSOMAP BSS Operation and Maintenance Application Part
BTS Base Transceiver Station
CCITT International Telegraph and Telephone Consultative Commitee
CLNS Connectionless-Mode Network Service
CMIP Common Management Information Protocol
CMIP-DU Common Management Information Protocol Data Unit
CMIS Common Management Information Service
CMISE Common Management Information Service Element
CONS Connection-Mode Network Service
CSMA/CD Carrier Sense Multiple Access with Collision Detection
CUG Closed User Group
DAF Destination Address Field
DCE Data Communication Equipment
DCF Data Communication Function
DCS 1800 Digital Cellular System 1800 MHz
DEAF Destination Extended Address Field
DIS Draft International Standard (of ISO)
DISP Draft International Standardized Profile
DSP Domain Specific Part
DTE Data Terminal Equipment
ETSI European Telecommunications Standards Institute
FTAM File Transfer Access and Management
GT Global Title
GSM Global System for Mobile Communication
ICF Information Conversion Function
ID Identifier
IDI Initial Domain Identifier
IP Internet Protocol
IS International Standard (of ISO)
ISDN Integrated Services Digital Network
ISO International Standards Organization
ISP International Standardized Profile
LAN Local Area Network
LAPB Link Access Procedure - Balanced
LAPD Link Access Procedure on the D-channel
LLC Logical Link Control
M Manager
MAC Media Access Control
MAF Management Application Function
MAPDU Management Application Protocol Data Unit
MCF Message Conversion Function
Page 13
ETS 300 612-2: August 1996 (GSM 12.01 version 4.4.1)
MF Mediation Function
MMI Man-machine Interface
MO Managed Object
MSC GSM Mobile-services Switching Centre
MTP Message Transfer Part
MUX Multiplexer
NE Network Element
NEF Network Element Function
NM Network Management
NMC Network Management Centre
NSAP Network Service Access Point
OG Organisation Number
O&M Operations and Maintenance
OMAP (CCITT) Operations, Maintenance and Administration Part
OMC Operations and Maintenance Centre
OS Operation System
OSF Operations System Functions
OSI Open Systems Interconnection
OSINET OSI Network
PAD Packet Assembler and Disassembler
PICS Protocol Implementation Conformance Statement
PRA Pimary Rate Access
PSAP Presentation Service Access Point
PSPDN Packet Switched Public Data Network
QAF Q Adaptor Function
QOS Quality Of Service
ROSE Remote Operation Service Element
SAF Source Address Field
SAPI Service Access Point Indicator
SCCP (CCITT) Signalling Connection Control Part
SEAF Service Extended Address Field
SLP Single Link Procedure
SM ASE Specific Management Application Service Element
SMAE System Management Application Entity
SMAP System Management Application Process
SMG Special Mobile Group
SN Sub Network
SPI Subsequent Protocol Identifier
SS7 (CCITT) Signalling System No.7
SSS Subscriber Switching Subsystem
SW Soft Ware
TMN Telecommunications Management Network
TRAU Transcoder and Rate Adaptation Unit
TS Transport Service
TSAP Transport Service Access Point
VASS Value Added Service Supplier
Page 14
ETS 300 612-2: August 1996 (GSM 12.01 version 4.4.1)
4 GSM Network Management
GSM 12.00 [80] describes the concepts of the Telecommunications Management Network which are
applicable to the management of a GSM network. This clause introduces the techniques which may be
employed in the translation of those concepts into a practical implementation of a TMN.
4.1 General TMN Structural aspects
4.1.1 Reference Points versus Interfaces
The M.3010 [1] defined TMN assists in the definition of functionality required to be supported by the
management network. This functionality is described in terms of discrete function blocks, viz. the OSF,
DCF, MF, QAF, NEF, etc. These function blocks may be structured hierarchically. Between each related
pair of function blocks, the interaction (typically a manager-agent relationship) is represented by a
reference point.
The actual implementation of M.3010 reference points into interfaces may take following forms:
a) Reference points realized across a physical communications link, i.e. the manager and agent
functions are implemented on different hardware devices.
b) Reference points realized in software, i.e. manager and agent functions are implemented on the
same device, and are accessible via a well-defined open API.
The definition of the relationship between the manager and agent functions forms the basis for the context
and standardization of the TMN interfaces described in the 12-series of recommendations.
4.1.2 Hierarchical Interworking between Function Blocks
The function blocks which are defined in draft CCITT M.3010 [1], and described in GSM 12.00 [80], may
exist in hierarchical structures. The levels of the hierarchy can be roughly equated with the layers of the
logically layered architecture. Figure 1 shows some examples of different structures which the TMN
allows. Wherever there is a boundary between two discrete functions there is a reference point defined.
Assuming that the functions contained within each function block at a particular level within the hierarchy,
in terms of its relationship to the serviced reference points, are equivalent, then a function block in one
stack could interact with a function block in any other stack through its adjacent reference points. This is
shown by the oblique lines. Obviously, however, this would also require the object models and instances
thereof on both sides to be supported.
Page 15
ETS 300 612-2: August 1996 (GSM 12.01 version 4.4.1)
Figure 1: Example functional hierarchies Inter-acting through Reference Points
Page 16
ETS 300 612-2: August 1996 (GSM 12.01 version 4.4.1)
4.1.3 Implementation of Interfaces According to M.3010
Figure 2 shows various levels of functionality involved in the management of network element
functionality, implemented in a number of different devices. The devices are shown by enclosing boxes.
Each device, according to M.3010 [1], can adopt a name which reflects the primary function of the device,
but this naming is arbitrary and is an implementation decision. A network element may also contain OS
functions but retain the name of the network element functions. (They will often be called OMCs and
NMCs. As can be seen from the figure, the precise role of an OMC device, as the first OS remote from the
network element, may be more or less complex depending on the specific implementation.)
Figure 2: Example functional groupings
Page 17
ETS 300 612-2: August 1996 (GSM 12.01 version 4.4.1)
Figure 3 shows a decomposition of a general OSF into more specific OSFs which represent different
functional areas. Each OSF contains the management functionality necessary for the specific functional
area, i.e. OSF1 is responsible for managing performance measurements, OSF2 manages the logical
configuration, etc.
Figure 3: Example functional relationship
The managed network element has been designed, in this example, to include certain function blocks of
the conceptual TMN. "OMC" device contains OSFs and a MF.
The external interface of the NE device is, therefore, the sum of the interfaces (Qx + Q3 + Q3) relevant to
the various components, and these may or may not be implemented together. OSF4, which is shown
contained within the NE device, may or may not interface to a higher level management device or
function. QAF3 has been implemented in the NE device to convert an existing non-standard interface to a
standardized interface.
Page 18
ETS 300 612-2: August 1996 (GSM 12.01 version 4.4.1)
4.2 Implementation requirements
The implementation requirements are derived out of GSM 12.00 [80], clause 3.
In this context this document shall specify a suitable subset of a Q3 and Qx profile defined as
- the implemented subset of the layer services profiles;
- the implemented subset of the layer protocols profiles;
- the application service and protocols profiles;
- the conformance requirements of the specified services;
- the conformance requirements of the specified profile.
4.2.1 GSM Phase 2 implementation requirements for the Q3 Interface
The degree of implementation freedom allowed for by the present CCITT M.3010 TMN model [1], as has
been described in the previous paragraphs, is simply too large to come to any significant level of multi-
vendor inter-operability.
For example, in figure 2 the OS in column (a) could interface to the NE in column (b) as they both claim to
support the same Q3 interface, provided that these are supported by the same object model using a
common message set. However, if the reference point contained within the OS in column (a) is not
discernible then it could not interface to the lower layer OS in column (b) without redevelopment for that
purpose.
It is therefore essential to uniquely define the grouping of the different functional areas supporting the
different layers within the logically layered architecture, in order to provide for interoperability in multi-
vendor environments.
The following introduces the requirements for a standardized GSM Phase 2 Q3 interface, as the example
the OMC - BSS interface is described.
The phase 2 target reference model for the BSS is defined as single OSF and BSS NEF, interfacing with
each other via a single accessible q3 reference point/Q3 interface, as depicted in figure 4 below:
Figure 4: BSS Reference Model for Phase 2
Page 19
ETS 300 612-2: August 1996 (GSM 12.01 version 4.4.1)
The BSS can be implemented either as:
1) a single BSS NEF, which directly interacts with the OSF through the Q3 interface
or:
2)
a) the BSC NEF and the BSC MF, which directly interacts with the OSF through the Q3
interface;
and
b) the BTS NEF, which interacts with the BSC MF through the Qx (Abis) interface,
which is depicted in figure 5:
Figure 5: Allowed BSS Context Models for Phase 2
The BSS object model and message set are defined in GSM 12.20 [81], while the O&M application part of
the BTS NEF is described in GSM 12.21 [82]. The Mediation Function, which converts the BTS relevant
parts of the OSF BSS Q3 information model to the BTS Qx information model, is described in GSM 12.22
[83].
Page 20
ETS 300 612-2: August 1996 (GSM 12.01 version 4.4.1)
4.2.2 GSM Phase 2 implementation requirements for the Qx Interface
The GSM TMN model for the second type of BSS implementation, described in the previous subclause
(figure 5), relates as depicted in figure 6 to the CCITT M.3010 model:
Figure 6: GSM Phase 2 Q3/Qx Interface Model
The GSM phase 2 Qx NM interface is a GSM specific standard which supports management of different
manufacturers equipment. However GSM 12.22 [83] is necessary to ensure the interoperability.
Note that the Qx NM interface does not support a full 7 layer OSI/CMIP protocol stack, but uses a simple
LAPD based application protocol for reasons of costs and simplicity.
4.2.3 GSM Phase 2 implementation requirements for interworking between Q3 and Qx
Interfaces
The interworking between the BSC MF and the BTS NEF (see figure 6), as related to CCITT M.3010,
consists of:
a) MF - MAF
These are functions supported to OSF application functions, of which tests and SW
management are specified in GSM 12.22 [83].
b) ICF;
The information conversion, i.e. transformation of the BTS aspects of the OSF - BSC
information model to the information model at the BTS side of the A bis interface, as
described in GSM 12.22 [83].
Page 21
ETS 300 612-2: August 1996 (GSM 12.01 version 4.4.1)
5 GSM Network Management Interfaces
5.1 General
The achievement of network management functions requires information transfers between the GSM
network elements and OS.
The selection and construction of the necessary protocol(s) is based upon the attributes of the functions
and message types.
Consideration should be made of:
- security;
- integrity;
- message volume;
- message length;
- priority;
- dependence;
5.2 NM Interfaces within a GSM Network
5.2.1 Q3 Interface
CCITT Q.811 [2] and Q.812 [3] specify a variety of Q3 interface implementations with the possibility for the
GSM operator to put together those network services necessary for a given GSM network.
For layer 1 - 3 four examples are detailed, i.e.
- SS7 of CCITT;
- X.25 network;
- ISDN;
- OSI-LAN.
The X.25 network can be realized by means of a dedicated network, or the PSPDN in either an open or
closed access mode.
If the Network Management information transfer between the BSS and the OMC utilizes the GSM A
interface as specified in GSM 08.06 [73] and 08.08 [74], then the GSM 08.08 [74] specified protocol stack
shall apply, i.e. MTP, SCCP and BSSOMAP.
The GSM 08.08 [74] specified BSSOMAP is interpreted as layer 4 to 7 according to figure 8.
Theoretically it is possible to use SS7 based BSSOMAP in between the BSS and MSC and use X.25
based BSSOMAP in between the MSC and the OMC. In this case address translation shall take place at
the MSC as described in Annex B.
For ISDN the OSI Connection-Mode Network Service (OSI - CONS2, OSI -CONS3, and OSI CONS4) are
specified according to CCITT Q.811 [2].
For OSI-LAN this ETS specifies the use of OSI Connectionless-Mode Network Service (CLNS1) on top of
the LLC and MAC sublayers. For the MAC sublayer CSMA/CD is used. CSMA/CD is often referred to as
"Ethernet".
5.2.2 Qx Interface
If the A-bis interface is implemented, the NM interface shall be a Qx interface according to M.3010 [1] and
shall be supported as described in GSM 12.21 [82].
For implementation requirements for this Qx interface see clause 5.
Page 22
ETS 300 612-2: August 1996 (GSM 12.01 version 4.4.1)
5.3 The Man Machine Interface (MMI)
Generally CCITT Z.300 series shall apply.
NOTE: A standardized MMI is not prospective. The reference to CCITT Z.300 series reflects
the syntax and semantic part and does not define the actual MMI.
However it is essential that any MMI contains efficient tools. For example MMIs could make use of other
techniques such as macro interpreter and window techniques to facilitate appropriate operation of any NE.
Page 23
ETS 300 612-2: August 1996 (GSM 12.01 version 4.4.1)
6 GSM Network Management protocols and services at the Q3 Interface
6.1 General
The specification of NM and the supporting TMN is based upon the OSI seven layer model and utilizes the
defined protocols, procedures and services. The recommended array is described in figure 8.
6.2 Communication Model For Management Information Transfer
6.2.1 General
In each Network Element the set of functions in charge of Network Management are known as the System
Management Application Processes (SMAPs). The communication between peer management
application processes is achieved using System Management Application Entities (SMAEs).
The SMAE is a set of Application Service Elements (ASE) providing services and protocols for
management information transfer between open systems (see figure 7).
The SMAE includes both management related Application Service Elements and other ASEs required to
support the previous category or providing direct services to the SMAPs.
OSI management Application Service Elements consist of:
- specific Management Application Service Elements, depending on the managed area;
- the Common Management Application Service Element.
Although Signalling System No. 7 is used in a GSM network, the Operation, Maintenance and
Administration Part (OMAP) described in CCITT Q.795 [34] is not considered as part of the GSM SMAP.
All information transfer services for the GSM SMAP can be accommodated using CMIS or FTAM.
NOTE: OMAP may be required to be implemented in GSM Network Elements as part of the
CCITT SS7 implementation.
6.2.2 Common Management Application Services Element (CMISE)
The Common Management Information Service Element (CMISE), version 2, is defined in documents ISO
IS 9595/IS 9596 [16], [17]. See also CCITT X.710 and X.711. This ASE provides services and protocol for
the transfer of Common Management Information Protocol Data Units (CMIP-DUs). It can be regarded as
a means for the exchange of information and commands for management purposes in a common
manner.
Page 24
ETS 300 612-2: August 1996 (GSM 12.01 version 4.4.1)
Figure 7: OSI Framework for Network Management
CMISE provides two types of information transfer service:
a) A management notification service - used to convey management information applicable to
notifications generated by a managed object;
The following service is defined:
1) M-EVENT-REPORT (confirmed/unconfirmed).
b) A management operation service - used to convey management information applicable to
operations directed at a managed object;
Page 25
ETS 300 612-2: August 1996 (GSM 12.01 version 4.4.1)
The following services are defined:
1) M-GET (confirmed);
2) M-SET (confirmed/non confirmed);
3) M-ACTION (confirmed/non confirmed);
4) M-CREATE (confirmed);
5) M-DELETE (confirmed);
6) M-C
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...