SIST ETS 300 623 E1:2003
(Main)Digital cellular telecommunications system (Phase 2) (GSM); Network Management (NM) procedures and messages on the A-bis interface (GSM 12.21)
- Abstract
This European Telecommunication Standard (ETS) addresses the network management messages and procedures across the A-bis interface, which is defined as Qx in GSM. The information model included here defines the objects and how they are addressed for purposes of operations and maintenance activities. There is a requirement for the A-bis interface to be open to allow interoperation between BTSs of different manufacturers working to the same BSC. This ETS addresses this requirement from O&M point of view, which allows this interworking to take place. It shows the split of NM functions between BSC and BTS. The procedures and coding of the messages are specified in detail. In practice, in addition to this ETS it is necessary that the content of manufacturer-dependent information fields be specified to fulfill the functionality. It is essential for operation that a BSC can handle the functions used by all its BTSs. Therefore, all items in this ETS are considered mandatory unless otherwise indicated in this ETS.
- 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 623 E1:2003 is the Slovenian adoption of ETS 300 623 Edition 1 from ETSI. It specifies Network Management (NM) procedures and messages on the A-bis interface in GSM Phase 2, with the focus on operations and maintenance (O&M) between the Base Station Controller (BSC) and the Base Transceiver Station (BTS).
What does SIST ETS 300 623 E1:2003 specify?
SIST ETS 300 623 E1:2003 defines how NM information is exchanged across the A-bis interface, which GSM identifies as Qx. The standard covers the information model, message procedures, message formats, and field coding needed for O&M interoperability between BSCs and BTSs from different manufacturers.
The document is organized into nine clauses:
| Clause | What it covers |
|---|---|
| 1 | Scope |
| 2 | Normative references |
| 3 | Definitions and abbreviations |
| 4 | Functional split between BSC and BTS |
| 5 | Information model |
| 6 | Elementary procedures |
| 7 | Structured procedures |
| 8 | Message details |
| 9 | Coding |
Clause 1 makes the open A-bis interface requirement explicit: the BSC must be able to work with BTSs from different manufacturers, and the standard treats the listed items as mandatory unless stated otherwise. Clause 5 defines the managed objects and their addressing for operations and maintenance use. Clause 8 and Clause 9 then give the message structures and encodings that implementers need for actual system integration and interoperability.
What are the key requirements of SIST ETS 300 623 E1:2003?
The standard’s main requirement is that the A-bis O&M interface must support interoperable control of BTS equipment through a common NM model. In practice, this means BSC and BTS implementations must agree on object classes, addresses, procedures, and coded parameters so that a BSC can manage all of its BTSs.
Functional split and object model
Clause 4 splits management functions between the BSC and BTS for fault management, configuration management, performance management, administration, and security management. Clause 5 defines the managed objects used on the A-bis interface - Site Manager, BTS, Radio Carrier, Baseband Transceiver, and Channel. For the reader, this is the map of what can be managed and where each function belongs.
Addressing and shared management knowledge
Clause 5.2 says NM messages are addressed by Managed Object Class and Managed Object Instance. The BSC must maintain a layer 2 link description for each object instance, and the object instance number is also used as a layer 3 address. This matters because interoperability depends on both sides agreeing on default TEI assignment, instance numbering, and link configuration as shared management knowledge.
State management
Clause 5.3 defines Administrative State, Operational State, and Availability Status. Administrative State is controlled by the BSC, while Operational State and Availability Status describe whether a resource is enabled, disabled, off line, degraded, failed, or not installed. In practice, this tells operators when traffic may pass, when the resource is blocked, and what condition the BTS should report.
Elementary procedures and message flow
Clause 6 states that elementary procedures are based on formatted O&M messages and are exchanged as Layer 2 I frames. A sender normally waits for an ACK, NACK, or response before starting another elementary procedure for the same object instance, and the default Layer 3 timeout is 10 seconds. This is the basic rule set for avoiding conflicting commands and message overruns.
Software download and activation
Clause 6.2 defines the software download sequence: Load Data Initiate, Load Data Segment, Load Data Abort, Load Data End, SW Activate Request, Activate SW, and SW Activated Report. The window size controls how many Load Data Segment messages may be sent before an ACK is expected. In practice, this is the procedure used to load BTS software safely and confirm completion.
A-bis, transmission, air interface, test, and equipment management
Clauses 6.3 to 6.9 cover the operational commands that make the site work: Establish TEI, connect or disconnect terrestrial signalling and traffic, connect or disconnect multi-drop links, set BTS and Radio Carrier attributes, set Channel attributes, perform and stop tests, report state changes and failures, change administrative state, change over equipment, opstart, reinitialize, set site outputs, get attributes, and set alarm thresholds. These procedures are what engineers use to bring equipment into service, verify it, isolate faults, and change configuration without breaking the management model.
What terms does SIST ETS 300 623 E1:2003 define?
- BSC - Base Station Controller, the GSM node that manages BTS resources and issues most O&M commands.
- BTS - Base Transceiver Station, the radio site equipment controlled through the A-bis interface.
- NM - Network Management, the set of procedures used to configure, supervise, and maintain the network elements.
- O&M - Operations and Maintenance, the management domain covered by this standard.
- TEI - Terminal End-point Identifier, the Layer 2 identity used when establishing and addressing A-bis connections.
- MMI - Man-machine Interface, the local user interface at a BTS site used for certain manual actions.
- SW - Software, especially the BTS software that can be downloaded and activated under this standard.
Who uses SIST ETS 300 623 E1:2003?
SIST ETS 300 623 E1:2003 is used by GSM network operators, BSC and BTS manufacturers, and system integrators who need interoperable O&M behaviour across the A-bis interface. It is also used by operations and maintenance engineers, commissioning teams, and test personnel who configure sites, load software, check state information, handle alarms, and verify radio and transmission settings.
For buyers and quality managers, the standard is relevant when checking whether BTS equipment can interwork with a BSC from another vendor and whether the implementation supports the required management procedures.
Which standards are used with SIST ETS 300 623 E1:2003?
| Reference | What it contributes |
|---|---|
| GSM 01.04 | GSM abbreviations and acronyms |
| GSM 04.06 | MS-BSS data link layer specification |
| GSM 04.08 | Mobile radio interface layer 3 specification |
| GSM 05.02 | Multiplexing, multiple access, and channel combinations |
| GSM 05.05 | Radio transmission and reception parameters |
| GSM 05.08 | Radio subsystem link control and related criteria |
| GSM 08.51 | General aspects of the BSC-BTS interface |
| GSM 08.52 | Interface principles and functional split between BSC and BTS |
| GSM 08.56 | Layer 2 specification for the BSC-BTS interface |
| GSM 08.58 | Layer 3 specification for the BSC-BTS interface |
| GSM 12.00 | Objectives and structure of NM |
| GSM 12.01 | Common aspects of GSM NM |
| GSM 12.06 | Functional requirements supported by this ETS |
| GSM 12.20 | BSS Management Information and object attributes |
| GSM 12.22 | Interworking of GSM NM procedures and messages at the BSC |
These references supply the surrounding GSM framework for addressing, layer behaviour, radio parameters, and the wider NM model.
What does the SIST ETS 300 623 E1:2003 document contain?
The document contains message category definitions, message layouts, and coding rules for all supported NM exchanges. Clause 8 gives the structures for formatted O&M messages, MMI transfer, TRAU O&M messages, and manufacturer-defined O&M messages, while Clause 9 gives the encodings for message types, object classes, object instances, attributes, parameters, state values, and NACK causes.
It also includes the object model figure, the split of management functions between BSC and BTS, and detailed tables for attributes such as administrative state, availability status, ARFCN list, TEI, test identifiers, threshold values, and software descriptions. For implementers, these tables are the practical reference for building or checking message handling, configuration tools, and interoperability tests.
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 623 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) procedures and messages on the A-bis interface (GSM 12.21)". This standard covers: This European Telecommunication Standard (ETS) addresses the network management messages and procedures across the A-bis interface, which is defined as Qx in GSM. The information model included here defines the objects and how they are addressed for purposes of operations and maintenance activities. There is a requirement for the A-bis interface to be open to allow interoperation between BTSs of different manufacturers working to the same BSC. This ETS addresses this requirement from O&M point of view, which allows this interworking to take place. It shows the split of NM functions between BSC and BTS. The procedures and coding of the messages are specified in detail. In practice, in addition to this ETS it is necessary that the content of manufacturer-dependent information fields be specified to fulfill the functionality. It is essential for operation that a BSC can handle the functions used by all its BTSs. Therefore, all items in this ETS are considered mandatory unless otherwise indicated in this ETS.
This European Telecommunication Standard (ETS) addresses the network management messages and procedures across the A-bis interface, which is defined as Qx in GSM. The information model included here defines the objects and how they are addressed for purposes of operations and maintenance activities. There is a requirement for the A-bis interface to be open to allow interoperation between BTSs of different manufacturers working to the same BSC. This ETS addresses this requirement from O&M point of view, which allows this interworking to take place. It shows the split of NM functions between BSC and BTS. The procedures and coding of the messages are specified in detail. In practice, in addition to this ETS it is necessary that the content of manufacturer-dependent information fields be specified to fulfill the functionality. It is essential for operation that a BSC can handle the functions used by all its BTSs. Therefore, all items in this ETS are considered mandatory unless otherwise indicated in this ETS.
SIST ETS 300 623 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 623 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 ¤±3RVWRSNLXSUDYOMDQMDRPUHåMD
10 LQVSRURþLODRYPHVQLNX$ELV *60
Digital cellular telecommunications system (Phase 2) (GSM); Network Management
(NM) procedures and messages on the A-bis interface (GSM 12.21)
Ta slovenski standard je istoveten z: ETS 300 623 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 623
TELECOMMUNICATION June 1996
STANDARD
Source: ETSI TC-SMG Reference: DE/SMG-061221P
ICS: 33.060.50
Key words: Digital cellular telecommunications system, Global System for Mobile Communications (GSM)
Digital cellular telecommunication system (Phase 2);
Network Management (NM) procedures and messages on the
A-bis interface
(GSM 12.21)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: 06921 Sophia Antipolis Cedex - FRANCE
Office address: Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
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 623: June 1996 (GSM 12.21 version 4.5.4)
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 623: June 1996 (GSM 12.21 version 4.5.4)
Contents
Foreword.7
Introduction .7
1. Scope .9
2. Normative References .9
3. Definitions and Abbreviations.10
3.1. Definitions.10
3.2. Abbreviations.10
4. Functional Split between BSC and BTS.11
5. Information Model .12
5.1. Managed Objects.12
5.2. Addressing of Objects .14
5.3. State Management of Objects.15
5.3.1. Administrative State.15
5.3.2. Operational State and Availability Status.16
6. Elementary Procedures .18
6.1. Definition of the Procedures.18
6.2. SW Download Management Procedures.19
6.2.1. Load Data Initiate.19
6.2.2. Load Data Segment .19
6.2.3. Load Data Abort . 19
6.2.4. Load Data End.20
6.2.5. SW Activate Request.20
6.2.6. Activate SW.20
6.2.7. SW Activated Report.20
6.3. A-bis Interface Management Procedures .21
6.3.1. Establish TEI .21
6.3.2. Connect Terrestrial Signalling .21
6.3.3. Disconnect Terrestrial Signalling .21
6.3.4. Connect Terrestrial Traffic .22
6.3.5. Disconnect Terrestrial Traffic .22
6.4. Transmission Management Procedures.22
6.4.1. Connect Multi-drop Link .22
6.4.2. Disconnect Multi-drop Link .22
6.5. Air Interface Management Procedures.23
6.5.1. Set BTS Attributes .23
6.5.2. Set Radio Carrier Attributes .23
6.5.3. Set Channel Attributes .23
6.6. Test Management Procedures .23
6.6.1. Perform Test . 23
6.6.2. Test Report . 24
6.6.3. Send Test Report.24
6.6.4. Stop Test . 24
6.7. State Management and Event Report Procedures .25
6.7.1. State Changed Event Report.25
6.7.2. Failure Event Report.25
6.7.3. Stop Sending Event Reports .25
6.7.4. Restart Sending Event Reports .26
Page 4
ETS 300 623: June 1996 (GSM 12.21 version 4.5.4)
6.7.5. Change Administrative State.26
6.7.6. Change Administrative State Request .26
6.8. Equipment Management Procedures.26
6.8.1. Change-over .26
6.8.2. Opstart.27
6.8.3. Reinitialize.27
6.8.4. Set Site Outputs.27
6.9. Miscellaneous Procedures .28
6.9.1. Get Attributes .28
6.9.2. Set Alarm Threshold.28
7. Structured Procedures.29
8. Message Details .29
8.1. Message Categories .29
8.1.1. Formatted O&M Messages.29
8.1.2. MMI Transfer.30
8.1.3. TRAU O&M Messages .30
8.1.4. Manufacturer-Defined O&M messages.31
8.2. Structure of Formatted O&M Messages.31
8.3. SW Download Management Messages.32
8.3.1. Load Data Initiate.32
8.3.2. Load Data Segment.33
8.3.3. Load Data Abort.33
8.3.4. Load Data End.33
8.3.5. SW Activate Request.33
8.3.6. Activate SW.33
8.3.7. SW Activated Report .34
8.4. A-bis Interface Management Messages.34
8.4.1. Establish TEI.34
8.4.2. Connect Terrestrial Signalling .34
8.4.3. Disconnect Terrestrial Signalling .34
8.4.4. Connect Terrestrial Traffic.34
8.4.5. Disconnect Terrestrial Traffic.35
8.5. Transmission Management Messages .35
8.5.1. Connect Multi-drop link.35
8.5.2. Disconnect Multi-drop link.35
8.6. Air Interface Management Messages.36
8.6.1. Set BTS Attributes.36
8.6.2. Set Radio Carrier Attributes .36
8.6.3. Set Channel Attributes .37
8.7. Test Management Messages.37
8.7.1. Perform Test.37
8.7.2. Test Report .37
8.7.3. Send Test Report.38
8.7.4. Stop Test.38
8.8. State Management and Event Report Messages .38
8.8.1. State Changed Event Report.38
8.8.2. Failure Event Report.38
8.8.3. Stop Sending Event Reports.39
8.8.4. Restart Sending Event Reports.39
8.8.5. Change Administrative State.39
8.8.6. Change Administrative State Request .40
8.9. Equipment Management Messages .40
8.9.1. Changeover .40
8.9.2. Opstart.40
8.9.3. Reinitialize.40
8.9.4. Set Site Outputs.41
8.10. Miscellaneous Messages.41
8.10.1. Get Attributes .41
Page 5
ETS 300 623: June 1996 (GSM 12.21 version 4.5.4)
8.10.2. Set Alarm Threshold.41
9. Coding.42
9.1. Message Type.42
9.2. Object Class.44
9.3. Object Instance.44
9.4. Attributes and Parameters .45
9.4.1. Abis Channel.46
9.4.2. Additional Info .47
9.4.3. Additional Text .47
9.4.4. Administrative State.47
9.4.5. ARFCN List.47
9.4.6. Autonomously Report .48
9.4.7. Availability Status .48
9.4.8. BCCH ARFCN.48
9.4.9. BSIC.48
9.4.10. BTS Air Timer .48
9.4.11. CCCH Load Indication Period.49
9.4.12. CCCH Load Threshold.49
9.4.13. Channel Combination.49
9.4.14. Connection Failure Criterion .49
9.4.15. Destination.50
9.4.16. Event Type .50
9.4.17. File Data.50
9.4.18. File Id.51
9.4.19. File Version.51
9.4.20. GSM Time.51
9.4.21. HSN .51
9.4.22. HW Configuration .51
9.4.23. HW Description.52
9.4.24. Intave Parameter .52
9.4.25. Interference level Boundaries .52
9.4.26. List of Required Attributes. 53
9.4.27. MAIO. 53
9.4.28. Manufacturer Dependent State.53
9.4.29. Manufacturer Dependent Thresholds.53
9.4.30. Manufacturer Id.53
9.4.31. Max Timing Advance.54
9.4.32. Multi-drop BSC Link.54
9.4.33. Multi-drop next BTS Link.55
9.4.34. Nack Causes .55
9.4.35. Ny1.56
9.4.36. Operational State. 56
9.4.37. Overload Period.56
9.4.38. Physical Config .56
9.4.39. Power Class . 56
9.4.40. Power Output Thresholds .57
9.4.41. Probable Cause .57
.9.4.42. RACH Busy Threshold .57
9.4.43. RACH Load Averaging Slots.58
9.4.44. Radio Sub Channel.58
9.4.45. RF Max Power Reduction .58
9.4.46. Site Inputs .58
9.4.47. Site Outputs.59
9.4.48. Source .59
9.4.49. Specific Problems .59
9.4.50. Starting Time .59
9.4.51. T200 .60
9.4.52. TEI.60
9.4.53. Test Duration . 60
Page 6
ETS 300 623: June 1996 (GSM 12.21 version 4.5.4)
9.4.54. Test No .60
9.4.55. Test Report Info.61
9.4.56. VSWR Thresholds.61
9.4.57. Window Size .61
9.4.58. TSC .61
9.4.59. SW Configuration .62
9.4.60. SW Description .62
9.4.61. Perceived Severity.62
History .63
Page 7
ETS 300 623: June 1996 (GSM 12.21 version 4.5.4)
Foreword
This European Telecommunication Standard (ETS) has been produced by the Special Mobile Group
(SMG) Technical Committee of the European Telecommunications Standards Institute (ETSI).
This ETS describes the network management messages and procedures across the A-bis interface within
the Digital cellular telecommunications system. This ETS corresponds to GSM technical specification,
GSM 12.21, version 4.5.4.
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: 06 June 1996
Date of latest announcement of this ETS (doa): 26 September 1996
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 27 March 1997
Date of withdrawal of any conflicting National Standard (dow): 27 March 1997
Introduction
(Background)
The use and general aspects of the A-bis interface are given in specification GSM 08.51. The split of
telecommunications functions and management procedures between BSC and BTS are defined in
specification GSM 08.52. Specification GSM 08.56 defines Layer 2 of the signalling messages.
The general aspects of NM are defined in specification GSM 12.00. Qx interface and protocol stack are
defined in specification GSM 12.01. GSM 12.06 provides the functional requirements supported by this
ETS. The NM procedures and messages to support these operations over the A-bis interface are
specified here. Specification GSM 12.20 provides the information model as seen on the OMC-BSC
interface. Interworking between this model and the NM messages and procedures provided here is
specified in GSM 12.22.
Page 8
ETS 300 623: June 1996 (GSM 12.21 version 4.5.4)
Blank page
Page 9
ETS 300 623: June 1996 (GSM 12.21 version 4.5.4)
1. Scope
This European Telecommunication Standard (ETS) addresses the network management messages and
procedures across the A-bis interface, which is defined as Qx in GSM. The information model included
here defines the objects and how they are addressed for purposes of operations and maintenance
activities.
There is a requirement for the A-bis interface to be open to allow interoperation between BTSs of different
manufacturers working to the same BSC. This ETS addresses this requirement from O&M point of view,
which allows this interworking to take place. It shows the split of NM functions between BSC and BTS. The
procedures and coding of the messages are specified in detail. In practice, in addition to this ETS it is
necessary that the content of manufacturer-dependent information fields be specified to fulfill the
functionality.
It is essential for operation that a BSC can handle the functions used by all its BTSs. Therefore, all items in
this ETS are considered mandatory unless otherwise indicated in this ETS.
2. Normative References
This ETS incorporates by dated or 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] GSM 01.04 (ETR 100): "Digital cellular telecommunication system (Phase 2);
Abbreviations and acronyms".
[2] GSM 04.06 (ETS 300 555): "Digital cellular telecommunication system
(Phase 2); Mobile Station - Base Station System (MS - BSS) interface Data
Link (DL) layer specification".
[3] GSM 04.08 (ETS 300 557): "Digital cellular telecommunication system
(Phase 2); Mobile radio interface layer 3 specification".
[4] GSM 05.02 (ETS 300 574): "Digital cellular telecommunication system
(Phase 2); Multiplexing and multiple access on the radio path".
[5] GSM 05.05 (ETS 300 577): "Digital cellular telecommunication system
(Phase 2); Radio transmission and reception".
[6] GSM 05.08 (ETS 300 578): "Digital cellular telecommunication system
(Phase 2); Radio subsystem link control".
[7] GSM 08.51 (ETS 300 592): "Digital cellular telecommunication system
(Phase 2); Base Station Controller - Base Transceiver Station (BSC - BTS)
interface General aspects".
[8] GSM 08.52 (ETS 300 593): "Digital cellular telecommunication system
(Phase 2); Base Station Controller - Base Transceiver Station (BSC - BTS)
interface Interface principles".
[9] GSM 08.56 (ETS 300 595): "Digital cellular telecommunication system
(Phase 2); Base Station Controller - Base Transceiver Station (BSC - BTS)
interface Layer 2 specification".
[10] GSM 08.58 (ETS 300 596): "Digital cellular telecommunication system
(Phase 2); Base Station Controller - Base Transceiver Station (BSC - BTS)
interface Layer 3 specification".
Page 10
ETS 300 623: June 1996 (GSM 12.21 version 4.5.4)
[11] GSM 12.00 (ETS 300 612-1): "Digital cellular telecommunication system
(Phase 2); Objectives and structure of Network Management (NM)".
[12] GSM 12.01 (ETS 300 612-2): "Digital cellular telecommunication system
(Phase 2); Common aspects of GSM Network Management (NM)".
[13] GSM 12.06 (ETS 300 617): "Digital cellular telecommunication system
(Phase 2); GSM Network Configuration Management and Administration".
[14] GSM 12.20 (ETS 300 622): "Digital cellular telecommunication system
(Phase 2); Base Station System (BSS) Management Information".
[15] 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)".
3. Definitions and Abbreviations
3.1. Definitions
Definitions of terms used within this ETS may be found mostly in clause5 in text context.
3.2. Abbreviations
For the purpose of this ETS the following abbreviations apply.
ASN.1 (CCITT) Abstract Syntax Notation One
BSC Base Station Controller
BSS Base Station System
BTS Base Transceiver Station
HW Hardware
LSB Least Significant Byte
MMI Man-machine Interface
MSB Most Significant Byte
MSC Mobile-services Switching Centre
NE Network Element
NM Network Management
O&M Operations and Maintenance
OMC Operations and Maintenance Centre
RF Radio Frequency
SAPI Service Access Point Indicator
SW Software
TEI Terminal End-point Identifier
TMN Telecommunications Management Network
TSC Training Sequence Code
cont. continued
man. dep. manufacturer dependent (with upper and lower case adjusted as appropriate)
Further GSM related abbreviations may be found in GSM 01.04 (ETR 100)[1].
Page 11
ETS 300 623: June 1996 (GSM 12.21 version 4.5.4)
4. Functional Split between BSC and BTS
Functional split of management functions between BSC and BTS is shown in Table 1.
Table 1/GSM 12.21. Split of management functions between BSC and BTS
BSC BTS
Fault Management
BTS
test request X -
test execution - X
test analysis NS -
fault detection - X
fault localization X (note) X
fault reporting X X
Link
testing (req,ex,rpt) NS -
fault detection X X
fault localization X X
fault reporting X X
Configuration Management
Hardware monitor control
Software control/monitor monitor
State control/monitor control/monitor
Parameters control/monitor monitor
Performance Management
Collection X X (radio path only)
Reporting X X (radio path only)
Administration X -
Security Management (Access Control to BTS)
Control - X
Monitoring - X
NOTE: When fault localisation is not possible at the BTS it must be deduced at the BSC.
Legend: Abbreviations:
NS = Not Specified; req = request;
X = Function exists; ex = execution
- = Function non-exists; rpt = report
Page 12
ETS 300 623: June 1996 (GSM 12.21 version 4.5.4)
5. Information Model
5.1. Managed Objects
The BCF mentioned in GSM 08.52 and GSM 08.56 is the agent at the BTS end of the A-bis O&M
interface. It has four different descriptions depending on the object that is managed: Site Manager, BTS,
Radio Carrier and Baseband Transceiver.
This model describes how objects are managed across A-bis interface, but it doesn't specify how
information is transferred inside the site. That is, the manner of communication between an object and
objects under it is not specified in this ETS.
As shown in Figure 1, the Object Classes used on the A-bis interface are a subset of those found under
Site Manager on the OMC-BSC interface. The Object Classes are listed below and the functionalities that
describe them are found in Table 2.
Site Manager manages common control functions of several BTSs and transceivers on one site. These
can include managing external alarms, front-end switch, etc. This model describes logical sites. There can
be multiple logical sites in one physical site. Communication between entities within a logical site is
manufacturer dependent.
BTS is associated with one cell. BTSs are typically created at installation phase by connecting
transceivers to antennas thus forming cells from the air interface point of view. The BTS can also contain
control functions common to various transceivers. The way BTSs are formed from transceivers and how
corresponding BTS numbers are determined is configuration dependent information, which is stored during
installation.
Radio Carrier represents manageable properties pertaining to radio transmission and reception of one
carrier.
Baseband Transceiver represents functions common to eight radio time slots.
Channel is a physical channel in air interface, which can contain several logical channels depending on
channel combination. A Channel is described with radio time slot and frequency hopping attributes (see
GSM 05.02).
Site Manager
containment
1+ Multiplicity of association:
1+ one or more
BTS
n numerically specified
1+
1+
Baseband Transceiver Radio carrier
Channel
NOTE: Site Manager and BTS don't necessarily require separate equipment. For example, the
Site Manager and a Baseband Transceiver can be associated with the same physical
equipment.
Figure 1/GSM 12.21. Object model seen across A-bis interface
Page 13
ETS 300 623: June 1996 (GSM 12.21 version 4.5.4)
Table 2/GSM 12.21: Objects, attributes and procedures seen across A-bis interface
Object class Attributes Procedures
Site Abis Channel Equipment Management
Manager Availability Status Establish TEI
HW Configuration Get Attributes
Manufacturer Dependent State Set Site Outputs
Manufacturer Id State Management and Event Report
Operational State SW Download Management
Site Inputs Test Management
Site Outputs
SW Configuration
BTS Administrative State Equipment Management
Availability Status Get Attributes
BCCH ARFCN Report Procedures
BSIC Set BTS Attributes
BTS Air Timer State Management and Event Report
CCCH Load Ind. Period SW Download Management
CCCH Load Threshold Test Management
Connection Failure Criterion
GSM Time
HW Configuration
Intave Parameter
Interterference Level Boundaries
Manufacturer Dependent State
Max Timing Advance
Ny1
Operational State
Overload Period
RACH Busy Threshold
RACH Load Averaging Slots
SW Configuration
T200
Radio Carrier Administrative State Equipment Management
ARFCN List Get Attributes
Availability Status Set RadioCarrier Attributes
HW Configuration State Management and Event Report
Manufacturer Dependent State SW Download Management
Manufacturer Id Test Management
Operational State
Power Class
RF Max Power Reduction
SW Configuration
Baseband Abis Channel* Connect Terrestrial Signalling
Transceiver Administrative State Disconnect Terrestrial Signalling
Availability Status Equipment Management
HW Configuration Get Attributes
Manufacturer Dependent State State Management and Event Report
Manufacturer Id SW Download Management
Operational State Test Management
SW Configuration
Page 14
ETS 300 623: June 1996 (GSM 12.21 version 4.5.4)
Table 2/GSM 12.21 (continued): Objects, attributes and procedures seen across A-bis interface
Object class Attributes Procedures
Channel Abis Channel* Connect Terrestrial Traffic
Administrative State Disconnect Terrestrial Traffic
ARFCN List* Equipment Management
Availability Status Get Attributes
Channel Combination Set Channel Attributes
HW Configuration State Management and Event Report
HSN* SW Download Management
MAIO* Test Management
Operational State
SW Configuration
TSC
NOTE: If more than one layer 2 link is defined to handle this information model, the actual
implementation may affect on which layer 2 link attributes concerning frequency hopping and
front-end switch are sent. Equipment used to implement frequency hopping can be common to
several radio carriers or located inside one radio carrier. Front-end switch is handled by Site
Manager, therefore all 'Abis Channel' attributes must be sent to it. Those attributes that need a
link identifier in BSC data structures are marked with an asterisk (*).
5.2. Addressing of Objects
It is a GSM requirement that the BSC is capable of operating with BTSs from different manufacturers. So,
it is necessary that the differences between BTSs, as seen by the BSC, are minimised as much as
possible. This is achieved by addressing NM messages by the Managed Object Class and Managed
Object Instance. There must be in the BSC an object model with a complete layer 2 link description for
each object instance in the BTS (e.g., Baseband Transceiver 1, Baseband Transceiver 2, Baseband
Transceiver 3,.). When a message has to be sent to an object instance this mapping is used to find the
correct link.
The first connection shall be established from the BTS site by using a (semi-) permanently programmed
default TEI. Subsequent to the establishment of the default connection to the site, further initial connections
to other objects shall be established using TEIs provided by procedures in Subclause 6.3.1.
Possible additional TEIs to an object already having an initial TEI are assigned with a GSM 12.21 message
found in Subclause 6.3.1. through an already assigned signalling link.
Object instances also have a layer 3 address. The instance number is used to address the object instance.
Regardless of whether the layer 2 address uniquely identifies the object instance or not, the layer 3
address must also be provided so that it can be used by management agent to determine which object
instance is being addressed. This combination of layer 2 and layer 3 addressing accommodates BTS sites
with either single or multiple physical links.
Specific equipment configuration information is manufacturer dependent. However, for interoperability, link
configuration, default TEI assignment and instance numbering must be known by both manager and agent.
This, as well as supported functions, is considered as Shared Management Knowledge.
Page 15
ETS 300 623: June 1996 (GSM 12.21 version 4.5.4)
5.3. State Management of Objects
State management in this ETS is generally in line with CCITT X.731. How state values are applied is
explained below.
CCITT X.731 states that "the management state of a managed object represents the instantaneous
condition of availability and operability of the associated resources from the point of view of management."
In this ETS there are two different factors (CCITT X.731 defines usage state in addition to these two) that
are considered to affect the management state of a managed object. They are:
- Administration: permission to use or prohibition against using the resource, imposed through the
management services;
- Operability: whether or not the resource is physically installed and working.
This ETS defines the following three state management attributes to represent the management state of a
managed object:
- Administrative state;
- Operational state;
- Availability status (this elaborates the operational state).
5.3.1. Administrative State
Administrative states of the managed objects can be controlled only by the BSC. In fact, the control of
resource usage comes from the MSC).
Setting the administrative state of a Channel to locked means that it has to discontinue all transmission
and reception of information on Air interface and all telecommunication (traffic and signalling) information
transmission on A-bis interface.
Setting the administrative state of a Radio Carrier to locked means that it has to discontinue all RF
emission on Air interface for the frequencies it is responsible.
Setting the administrative state of a Baseband Transceiver to locked means that it has to discontinue all
telecommunication tramissions and the Channels which are affected should indicate that they are Disabled
or Degraded.
Setting the administrative state of a BTS to locked means it has to discontinue all RF emission on all Radio
Carriers and all telecommunication transmissions on all Channels of all Baseband Transceivers, i.e., Radio
Carriers, Channels and Baseband Transceivers are in Disabled, Dependency state.
The administrative state at the BTS site is also used to provide information e.g., for a local MMI user at a
BTS site.
The locked state of a 12.21 managed object means that BSC has disconnected all the calls that go
through the resource that is represented by the managed object. No new traffic is connected through this
resource any more.
The shutting down state means that no new traffic is connected through this resource any more. The
on-going calls remain.
The unlocked state means that new traffic is allowed through the resource represented by the managed
object.
Page 16
ETS 300 623: June 1996 (GSM 12.21 version 4.5.4)
5.3.2. Operational State and Availability Status
CCITT X.731 gives the following definitions for the values of the operational state attribute:
- disabled: the resource is totally inoperable and unable to provide service to the user(s);
- enabled: the resource is partially or fully operable and available for use.
In this ETS the value Disabled represents the following conditions that the resources could have:
- hardware or software is not installed;
- power is turned off;
- failure has occurred;
- radio parameters has not yet been set by elementary procedures, therefore, the resource is off line.
The availability status elaborates the operational state attribute. In this ETS the following values are used
(availability status is a set value):
In test: The resource is undergoing a test procedure.
Failed: The resource has an internal fault that prevents it from operating. The operational state is disabled.
Power off: The resource requires power to be applied and is not powered on. The operational state is
disabled.
Off line: The resource requires some manual and/or automatic operation(s) to be performed to make it
available for the use.
Dependency: The resource cannot operate because some other resource on which it depends is
unavailable. The operational state is disabled.
Degraded: The service available from the resource is degraded in some respect, such as in speed or
operating capacity. The operational state is enabled.
Not installed: The hardware or the software associated with the managed object has not been installed at
the site. Operational state is disabled.
Figure 2 illustrates the operational state and availability status behaviour of GSM 12.21 objects (i.e., Site
Manager, BTS, Radio Carrier, and Baseband Transceiver) during initialization. The initial value of the
administrative state is locked.
Page 17
ETS 300 623: June 1996 (GSM 12.21 version 4.5.4)
HW installed
SW Activation
BTS related object (Site Manager, BTS, Radio Carrier,
not required
and Baseband Transceiver) requests downloading and
SW Activate Request
activation of the running software version.
Software downloading and activation takes place when
Disabled, object is in this state.
Not Installed Operational state = Disabled
Availability status = Not installed
The last file belonging to the running software version
SW Activate
has been downloaded and activated.
Changed State
Event Report
Operational state = Disabled
Disabled,
Availability status = Off line
Off Line
Object doesn't have correct attribute values yet. They
will be received when the unlock procedure is executed.
Operational state = Disabled
Availability status = Off line
Attribute setting
All needed attributes of the managed object are set.
Opstart
Opstart to attempt to put the managed object to
enabled state.
Changed State
Event Report
Operational state = Enabled
Enabled
Availability status = { }
Figure 2/GSM 12.21: GSM 12.21 Objects' Operational state and
availability status behaviour during initialization
Page 18
ETS 300 623: June 1996 (GSM 12.21 version 4.5.4)
6. Elementary Procedures
The operational procedures applicable to the BTS consist of bringing BTS equipment and software into (or
taking them out of) service, initiation of tests at the BTS, collection of test results made at the BTS,
reporting and clearing of any BTS faults, and reporting of any BTS external alarms. Bringing into service of
equipment at the BTS will include manual operations, including turning the switch on, and performing local
testing where relevant at the BTS, followed by an indication of the availability of the equipment to the BTS
via some man-machine interface (MMI terminal, telephone). It is then a BSC function to ensure that
relevant data on the existence of the equipment is resident at the BTS, and to activate (bring into service)
the new equipment. Manual procedur
...