SIST ETS 300 622 E1:2003

• Abstract:

  This European Telecommunication Standard (ETS) provides the management information model for the Configuration and Fault Management aspects of the GSM Base Station System (BSS) Network Element as seen on the Q3 interface between the OS (e.g. OMC) and the BSS. The information defined in this model is that which is required to manage the BSS Network Element as set forth in the GSM core specifications for telecommunications operation, and as specified in the GSM 12-series Specifications for management requirements. The management information defined in this ETS is primarily related to what is termed configuration and fault management within the CCITT X.701 [7] definition of Management Functional Areas. Additional management information elements of the BSS model for other management areas are defined in other GSM 12-series Specifications. For example, the management information related to the performance Management Functional Area is to be found in GSM 12.04 [27]. See GSM 12.00 [24] for a complete overview of the GSM 12-series specifications. In addition to the formal GDMO definitions, additional information is included to aid in understanding the model and its elements. Summary descriptions, containment and inheritance diagrams, and entity relationship diagrams are provided for this purpose. The general management information contained in the models specified in CCITT M.3100 [3] and CCITT X.7xx Recommendations is referenced in this ETS but the formal definitions are contained in the referenced documents.

• Status: Published
• Publication Date: 30-Nov-2003
• ICS: 33.070.50 - Global System for Mobile Communication (GSM)
• Technical Committee: SS EIT - Technical Board for the electrotechnical, information technology and telecommunications fields
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2003
• Due Date: 01-Dec-2003
• Completion Date: 01-Dec-2003
• Ref Project: ETSI ETS 300 622 ed.1 (1996-06) - Digital cellular telecommunications system (Phase 2) (GSM); Base Station System (BSS) management information (GSM 12.20)

SIST ETS 300 622 E1:2003 is the Slovenian adoption of ETS 300 622 Edition 1 for the GSM Base Station System (BSS) management information model. It specifies the configuration and fault management information for the BSS Network Element on the Q3 interface between the Operations System (OS), such as an Operations and Maintenance Centre (OMC), and the BSS. It is written for people who need to design, implement, test, or operate GSM network management for BSC, BTS, and related equipment.

What does SIST ETS 300 622 E1:2003 specify?

SIST ETS 300 622 E1:2003 defines the management information model for BSS management on the Q3 interface. The scope is configuration and fault management, so the standard is mainly about what can be monitored and controlled in the BSS and how those managed objects are described.

The standard is part of the GSM 12-series network management set. It points performance management to GSM 12.04 and refers readers to GSM 12.00 for the wider view of the GSM network management structure. It also states that the management information exchange for Q3 is specified in GSM 12.01, while this ETS covers the information model itself.

The document is organized as follows: clauses 4 to 13 move from TMN services and functions to the formal managed object definitions and ASN.1 syntaxes. It also includes summary descriptions, containment and inheritance diagrams, and entity relationship diagrams to help readers understand how the model fits together.

Annex	What it covers
Annex A	System feature partitioning and how to use the model for cell, protocol, adjacent cell, power control, handover, frequency, architectural element, software, and equipment management
Annex B	Lists of management functions, managed object classes, packages, actions, notifications, parameters, attributes, and name bindings
Annex C	Index

What are the key requirements of SIST ETS 300 622 E1:2003?

How the model is structured

Clause 4 places SIST ETS 300 622 E1:2003 in the TMN framework defined by CCITT M.3010 and M.3020. In practice, that means the BSS model is not ad hoc: it is built around standardized management services, service components, and management functions.

Clause 5 defines the management information model itself. It uses inheritance, containment, and entity relationships to show how managed object classes fit together, and it distinguishes mandatory and optional attributes, actions, notifications, and parameters at object-class level. That matters for implementation and conformance, because a BSS product may support a package or capability only in some object instances.

Clauses 6 to 13 contain the formal definitions. They cover managed object classes, packages, actions, notifications, parameters, attributes, name bindings, and the ASN.1 syntax definitions used to encode them. For implementers, these clauses are the part that turns the conceptual model into something a manager and agent can actually exchange.

What the BSS model manages

The model covers a defined set of BSS-related managed objects such as bts, bsc, basebandTransceiver, channel, radioCarrier, transcoder, lapdLink, pcmCircuit, frequencyHoppingSystem, handoverControl, powerControl, adjacentCellHandOver, adjacentCellReselection, btsSiteManager, gsmEquipment, and software-related objects. This gives operators a structured way to manage the radio network, transmission links, control functions, and supporting equipment through the same management model.

The bts object is central. Its state and status attributes describe whether the BTS is locked, unlocked, shutting down, under test, failed, powered off, degraded, or busy, and whether alarms are present or pending. In practice, this tells an OMC whether traffic can flow, whether maintenance can proceed, and whether the site is healthy.

Clause 9 defines notifications such as communicationsAlarm, environmentalAlarm, equipmentAlarm, objectCreation, objectDeletion, stateChange, and attributeValueChange. These are the events a management system can subscribe to when it needs alarms, audit trails, or change monitoring.

How radio behavior is controlled

Several packages describe radio and access behavior that operators tune in day-to-day work. The btsCCCHConfigurationPackage and btsTimerPackage cover control-channel broadcasting and air-interface timers, while btsOptionsPackage covers optional BTS behaviors such as IMSI attach/detach, cell barring, call re-establishment, and DTX settings.

These settings matter because they shape how mobiles enter the cell, how paging is repeated, and how access is granted. The same section also includes queue-related settings in btsQueuingPackage, which define how call and handover requests wait for traffic channels.

The model also includes measurement-processing control. The hoMsmtProcessingModePackage and pcMsmtProcessingModePackage let the operator choose where measurement processing, threshold comparison, and related decisions are performed. That matters when a network is split between BSC-side and BTS-side processing.

How handover and power control are handled

The standard gives dedicated support for handover and power control through optional packages and object classes, including handoverControlGSM0508, adjacentCellHandOverGSM0508, internalInterCellHandoverPackage, internalIntraCellHandoverPackage, and the power-control-related classes and packages. These define the parameters used to manage thresholds, priorities, averaging, and the logic behind mobility decisions.

In practice, this is where an operator decides how aggressively the network should hand over calls, how much measurement smoothing to use, and how power-control behavior is configured. Annex A ties those objects back to practical features such as adjacent cell configuration, frequency control, and handover control.

The bts and basebandTransceiver objects also support the forcedHO action. That action is used to clear traffic from a BTS or TRX in a controlled way, which is important for maintenance or graceful shutdown.

How the document supports implementation

Clause 5 includes summary tables and relationship diagrams, while clauses 6 to 12 provide the formal GDMO templates. This lets implementers check not only what objects exist, but also how they are related, what packages they carry, and which attributes are mandatory or optional.

Annex B is especially useful as an implementation checklist. It lists the managed object classes, packages, actions, notifications, parameters, attributes, and name bindings that appear in the model, so a vendor or operator can map support status against the standard quickly.

What terms does SIST ETS 300 622 E1:2003 define?

• Guidelines for the Definition of Managed Objects (GDMO) - The template system used for the formal definition of managed object classes, packages, actions, and notifications.
• Managed Object Class (MOC) - A class of manageable network object, such as bts or bsc, with defined attributes and behavior.
• Operations System (OS) - The manager side of the Q3 interface that exchanges management information with the BSS.
• Operations and Maintenance Centre (OMC) - A common example of an OS used to monitor and control the GSM network.
• Management Functional Area (MFA) - A top-level management category such as fault management or configuration management.
• Protocol Data Unit (PDU) - The encoded unit of information exchanged between management systems.
• Relative Distinguished Name (RDN) - A naming element used to identify managed objects in a structured way.
• System Management Function (SMF) - A management function used within the TMN framework to organize operations behavior.

Who uses SIST ETS 300 622 E1:2003?

GSM network operators use SIST ETS 300 622 E1:2003 to define how BSS equipment is configured, monitored, and fault-managed through the Q3 interface. OMC and NOC teams use it to understand which alarms, states, and control actions should be available for BTS, BSC, and related elements.

Equipment vendors use the standard when they build BSS products that must expose managed object classes, packages, and notifications in a consistent way. System integrators and test teams use it to check interoperability, conformance, and management behavior across different implementations.

What changed in SIST ETS 300 622 E1:2003 from the previous edition?

SIST ETS 300 622 E1:2003 is identified as identical to ETS 300 622 Edition 1.

Which standards are used with SIST ETS 300 622 E1:2003?

• CCITT M.3010 and M.3020 - Provide the TMN principles and the interface specification methodology that frame the whole document.
• CCITT M.3100 - Supplies the generic network information model that the ETS references for general management information.
• CCITT M.3200 and M.3400 - Give the overview of TMN management services and TMN management functions used to organize the model.
• CCITT X.208 - Defines ASN.1, the notation used for the abstract syntax definitions.
• CCITT X.701 - Provides the systems management overview and the management functional area view used in the scope.
• CCITT X.721 and X.722 - Provide the definition and guideline templates for managed object information and GDMO-based object definition.
• CCITT X.730, X.731, X.733, X.734, X.735 - Define object management, state management, alarm reporting, event report management, and log control functions used by the model.
• GSM 12.00, GSM 12.01, GSM 12.04, GSM 12.06, GSM 12.21 - Provide the GSM network management overview, exchange, performance data, configuration management, and A-bis procedures referenced by this ETS.
• GSM 04.06, GSM 04.08, GSM 05.02, GSM 05.05, GSM 05.08, GSM 08.08, GSM 08.58, GSM 08.60 - Supply the radio, signaling, timer, and interface behavior behind many of the managed attributes and actions.
• CCITT Q.821 - Provides the Q3 alarm surveillance context used for alarm handling.

What does the SIST ETS 300 622 E1:2003 document contain?

The document contains the formal BSS management model, including managed object summaries, package definitions, action definitions, notification definitions, parameter definitions, attribute definitions, name binding definitions, and ASN.1 syntax definitions. It also includes diagrams for inheritance, containment, and entity relationships, plus state and status tables for managed objects such as bts.

Annex A reorganizes the model by practical BSS features, which helps during network design and configuration work. Annex B gives the lists that make implementation audits and conformance checks faster, because the reader can trace every class, package, action, notification, parameter, attribute, and name binding in one place.

The ASN.1 module in clause 13 supplies object identifiers, initial values, and type definitions for values such as timers, channel combinations, radio thresholds, frequencies, and identifiers. That part is what software developers and protocol testers use when they build or verify management data encoding.

SLOVENSKI STANDARD
01-december-2003
'LJLWDOQLFHOLþQLWHOHNRPXQLNDFLMVNLVLVWHPID]D¤±8SUDYOMDQMHLQIRUPDFLM
VLVWHPDED]QLKSRVWDM%66*60
Digital cellular telecommunications system (Phase 2) (GSM); Base Station System (BSS)
management information (GSM 12.20)
Ta slovenski standard je istoveten z: ETS 300 622 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 622
TELECOMMUNICATION June 1996
STANDARD
Source: ETSI TC-SMG Reference: DE/SMG-061220P
ICS: 33.060.50
Key words: Digital cellular telecommunications system, Global System for Mobile communications (GSM)
Digital cellular telecommunications system (Phase 2);
Base Station System (BSS) Management Information
(GSM 12.20)
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: [e-mail]
Tel.: [phone] - Fax: [phone]
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 622: June 1996 (GSM 12.20 version 4.2.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 622: June 1996 (GSM 12.20 version 4.2.1)
Contents
Foreword .11
Introduction.11
1 Scope .13
2 Normative references.13
3 Abbreviations.15
4 TMN services and functions.16
4.1 TMN management service.16
4.2 TMN management service components.16
4.3 TMN management functions .17
4.3.1 Alarm surveillance management functions .17
Report Alarm Function.17
Route Alarm Report Function .17
Request Alarm Report Route Function.18
Condition Alarm Reporting Function.18
Request Alarm Report Control Condition Function .18
Allow/Inhibit Alarm Reporting Function.18
Request Alarm Report History Function .18
Delete Alarm Report History Function .18
Allow/Inhibit Logging Function .18
Condition Logging Function.18
Request Log Condition Function .18
4.3.2 Provisioning management functions .19
Grow Configuration Function.19
Prune Configuration Function.19
Condition Configuration Function .19
Request Configuration Function .20
Configuration Report Function.21
Route Configuration Report Function .21
Condition Configuration Reporting Function.21
Request Configuration Report History Function .21
Delete Configuration Report History Function .21
Allow/Inhibit Logging Function .21
Condition Logging Function.21
Request Log Condition Function .22
4.3.3 NE status and control management functions .22
Allow/Inhibit Operation Function .22
Condition Operation Function.23
Request Operation Condition Function.23
Report Operation Condition Function .24
Route Operation Report Function.24
Condition Operation Reporting Function .24
Request Operation Report History Function.24
Delete Operation Report History Function.24
Allow/Inhibit Logging Function .24
Condition Logging Function.24
Request Log Condition Function .25
5 Management information model.26
5.1 Formal description of the model .26
5.2 Basis for the model .26
5.3 Extensions to the model .27
5.4 Relationships to other models .27

Page 4
ETS 300 622: June 1996 (GSM 12.20 version 4.2.1)
5.5 Conformance to the model. 28
5.6 Inheritance relationships . 28
5.7 Containment relationships. 29
5.8 Entity relationships . 29
5.9 BSS related managed object summaries. 34
adjacentCellHandOver. 34
adjacentCellReselection . 35
adjacentCellHandOverGSM0508 . 36
adjacentCellHandOverGSM0508AndReselection . 37
basebandTransceiver . 38
bsc . 41
bts . 45
btsSiteManager . 50
channel . 52
channelModCompleteRecord . 56
frequencyHoppingSystem. 56
handoverControl . 57
handoverControlGSM0508 . 58
lapdLink . 60
pcmCircuit . 62
powerControl . 64
powerControlGSM0508 . 66
radioCarrier . 68
transcoder . 71
5.10 General managed object class summaries. 74
executableSoftwareUnit. 74
gsmEquipment . 75
gsmManagedFunction . 77
operatingSoftwareUnit . 78
replaceableSoftwareUnit. 81
6 Managed object class definitions. 83
6.1 BSS related managed object classes . 83
adjacentCellHandOver. 83
adjacentCellHandOverGSM0508 . 83
adjacentCellHandOverGSM0508AndReselection . 83
adjacentCellReselection . 83
basebandTransceiver . 84
bsc . 84
bssFunction . 84
bts . 85
btsSiteManager . 85
channel . 85
channelModCompleteRecord . 85
frequencyHoppingSystem. 86
handoverControl . 86
handoverControlGSM0508 . 86
lapdLink . 86
pcmCircuit . 86
powerControl . 87
powerControlGSM0508 . 87
radioCarrier . 87
transcoder . 87
6.2 General managed object classes. 88
alarmRecord . 88
attributeValueChangeRecord . 88
eventForwardingDiscriminator. 88
executableSoftwareUnit. 88
gsmEquipment . 88
gsmManagedFunction . 88
log . 89
objectCreationRecord. 89
objectDeletionRecord . 89

Page 5
ETS 300 622: June 1996 (GSM 12.20 version 4.2.1)
operatingSoftwareUnit.89
replaceableSoftwareUnit .89
simpleFileTransferControl .89
stateChangeRecord .89
7 Managed object class package definitions.90
7.1 BSS related packages .90
adjacentCellHandOverGSM0508AndReselectionPackage.90
adjacentCellHandOverGSM0508Package.90
adjacentCellHandOverPackage .91
adjacentCellReselectionPackage.92
adjustExternalTimePackage .92
basebandTransceiverPackage.93
bscBasicPackage.94
bscProcForBTSPowerControlPackage .95
bssMapTimerPackage .95
btsBasicPackage.96
btsCCCHConfigurationPackage.97
btsOptionsPackage .98
btsPowerControlConfigPackage .98
btsQueuingPackage.98
btsSiteManagerBasicPackage .99
btsTimerPackage .99
channelConfigModPackage .100
channelPackage.101
channelModCompleteRecordPackage.102
frequencyHoppingSystemPackage .103
handoverControlGSM0508Package.103
handoverControlPackage.104
hoMsmtProcessingModePackage.104
internalInterCellHandoverPackage.105
internalIntraCellHandoverPackage.105
lapdLinkPackage.106
pcmCircuitPackage .107
pcMsmtProcessingModePackage.108
powerControlGSM0508Package.108
powerControlPackage.109
radioCarrierPackage .110
transcoderMatrixPackage .111
transcoderPackage .112
7.2 General packages.113
equipmentRelatedAlarmPackage.113
executableSoftwareUnitPackage .114
functionalRelatedAlarmPackage .114
gsmEquipmentPackage .115
operatingSoftwareUnitPackage.116
replaceableSoftwareUnitPackage .117
8 Managed object class action definitions.118
8.1 BSS related actions .118
adjustExternalTime .118
channelConfigModification .118
forcedHO .119
8.2 General actions.119
requestTransferDown.119
transferDownComplete.119
9 Managed object class notification definitions .120
9.1 BSS related notifications.120
channelModComplete .120
9.2 General notifications .120
attributeValueChange.120
communicationsAlarm.120

Page 6
ETS 300 622: June 1996 (GSM 12.20 version 4.2.1)
environmentalAlarm. 121
equipmentAlarm. 121
objectCreation . 121
objectDeletion . 121
processingErrorAlarm. 121
qualityofServiceAlarm . 121
stateChange . 121
transferDownReady . 121
10 Managed object class parameter definitions . 122
10.1 BSS related parameters. 122
standard1220CreateErrorInfo. 122
standard1220DeleteErrorInfo . 122
standard1220SpecificErrorInfo . 123
10.2 General parameters . 123
relatedGSMEquipCeaseParam . 123
relatedGSMEquipLabelParam. 124
relatedGSMEquipLocParam. 125
relatedGSMEquipNameParam . 125
relatedGSMEquipObjParam . 126
relatedGSMEquipTimeParam. 126
relatedGSMEquipTypeParam. 127
relatedGSMEquipVersParam . 127
11 Managed object class attribute definitions. 128
11.1 BSS related attributes . 128
abisSigChannel . 128
adjacentCellID . 128
allowIMSIAttachDetach. 128
basebandTransceiverID. 129
bCCHFrequency . 129
bscID . 129
bsIdentityCode . 130
bssMapT1 . 130
bssMapT4 . 130
bssMapT7 . 131
bssMapT8 . 131
bssMapT10 . 131
bssMapT13 . 132
bssMapT17 . 132
bssMapT18 . 132
bssMapT19 . 132
bssMapT20 . 133
btsID . 133
btsSiteManagerID . 133
callReestablishmentAllowed . 134
carrierFrequencyList . 134
cellAllocation . 134
cellBarred . 135
cellGlobalIdentity. 135
cellReselectHysteresis. 135
channelCombination. 136
channelID . 136
channelModCompleteArg . 137
dtxDownlink . 137
dtxUplink . 137
emergencyCallRestricted. 138
enableInternalInterCellHandover . 138
enableInternalIntraCellHandover . 138
enableOptHandoverProcessing. 139
frequencyHoppingSystemID . 139
frequencyUsage. 139
gsmdcsIndicator . 140

Page 7
ETS 300 622: June 1996 (GSM 12.20 version 4.2.1)
handoverControlID .140
handoverReqParam .140
hoAveragingAdjCellParam .141
hoAveragingDistParam .141
hoAveragingLevParam.141
hoAveragingQualParam.142
hoMargin .142
hoMarginDef .142
hoMsmtProcessingMode.143
hoppingSequenceNumber.143
hoPriorityLevel .143
hoThresholdDistParam .144
hoThresholdInterferenceParam .144
hoThresholdLevParam.144
hoThresholdQualParam .145
interferenceAveragingParam.145
lapdLinkID .146
maxNumberRetransmission.146
maxQueueLength.146
mobileAllocation .147
msmtProcParamLoc.147
msPriorityUsedInQueuing .147
mSTxPwrMaxCCH .148
msTxPwrMaxCell .148
msTxPwrMaxCellDef.148
noOfBlocksForAccessGrant.149
noOfMultiframesBetweenPaging.149
notAllowedAccessClasses .149
numberOfSlotsSpreadTrans .150
ny1 .150
pcAveragingLev.150
pcAveragingQual.151
pcLowerThresholdLevParam .152
pcLowerThresholdQualParam .152
pcmCircuitID .152
pcMsmtProcessingMode.153
pcUpperThresholdLevParam .153
pcUpperThresholdQualParam .154
periodCCCHLoadIndication.154
plmnPermitted .154
powerClass .155
powerControlID .155
powerControlInterval .155
powerIncrStepSize .156
powerRedStepSize.156
rACHBusyThreshold.156
rACHLoadAveragingSlots .157
radioCarrierID .157
radioLinkTimeout.157
relatedRadioCarrier .158
relatedOAMLapdLink.158
relatedTelecomLapdLink.158
relatedTranscoder .159
rxLevAccessMin .159
rxLevMinCell .159
rxLevMinCellDef .160
sapi .160
synchronized .160
t200 .161
t31xx .161
tei .161
terrTrafChannel .162
thresholdCCCHLoadIndication.162

Page 8
ETS 300 622: June 1996 (GSM 12.20 version 4.2.1)
timeLimitCall . 162
timeLimitHandover. 163
timerPeriodicUpdateMS. 163
transcoderID . 163
transcoderMatrix. 164
tsc . 164
txPwrMaxReduction. 164
11.2 General attributes. 165
administrativeState . 165
alarmStatus . 165
availabilityStatus . 165
backupESU . 165
controlStatus . 165
equipmentType . 166
fallbackESU . 166
newESU . 166
operatingSoftwareID . 167
operationalState. 167
relatedFiles . 167
relatedGSMEquipment . 167
relatedGSMFunctionalObjects. 168
relatedRSUs . 168
runningESU . 168
unknownStatus . 169
usageState . 169
12 Managed object class name binding definitions . 170
12.1 BSS related name bindings. 170
adjacentCellHandOver-bts Name Binding. 170
adjacentCellReselection-bts Name Binding. 170
basebandTransceiver-bts Name Binding . 171
bsc-bssFunction Name Binding. 171
bssFunction-managedElement Name Binding . 171
bts-btsSiteManager Name Binding. 172
btsSiteManager-bssFunction Name Binding . 172
channel-basebandTransceiver Name Binding. 172
channelModCompleteRecord Name Binding . 172
frequencyHoppingSystem-bts Name Binding. 173
handoverControl-bts Name Binding. 173
lapdLink-bssFunction Name Binding . 173
pcmCircuit-bssFunction Name Binding . 174
powerControl-bts Name Binding. 174
radioCarrier-bts Name Binding. 174
transcoder-bssFunction Name Binding . 175
12.2 General name bindings . 175
executableSoftwareUnit-basebandTransceiver Name Binding . 175
executableSoftwareUnit-bsc Name Binding . 175
executableSoftwareUnit-bts Name Binding . 176
executableSoftwareUnit-btsSiteManager Name Binding. 176
executableSoftwareUnit-channel Name Binding . 176
executableSoftwareUnit-equipment Name Binding . 177
executableSoftwareUnit-managedElement Name Binding. 177
executableSoftwareUnit-pcmCircuit Name Binding. 177
executableSoftwareUnit-radioCarrier Name Binding. 178
executableSoftwareUnit-transcoder Name Binding. 178
gsmEquipment-gsmEquipment Name Binding. 178
gsmEquipment-managedElement Name Binding . 178
operatingSoftwareUnit-basebandTransceiver Name Binding. 178
operatingSoftwareUnit-bsc Name Binding. 179
operatingSoftwareUnit-bts Name Binding. 179
operatingSoftwareUnit-btsSiteManager Name Binding . 179
operatingSoftwareUnit-channel Name Binding. 180
operatingSoftwareUnit-gsmEquipment Name Binding . 180

Page 9
ETS 300 622: June 1996 (GSM 12.20 version 4.2.1)
operatingSoftwareUnit-pcmCircuit Name Binding.180
operatingSoftwareUnit-radioCarrier Name Binding.181
operatingSoftwareUnit-transcoder Name Binding.181
replaceableSoftwareUnit-gsmEquipment Name Binding .181
replaceableSoftwareUnit-managedElement Name Binding .182
replaceableSoftwareUnit-replaceableSoftwareUnit Name Binding .182
13 Abstract syntax definitions.183
Annex A (informative): System feature partitioning - use of the model.191
A.1 Cell configuration management .191
A.2 Protocol configuration management .193
A.3 Adjacent cell configuration management .194
A.4 Power control management .195
A.4.1 MS power control management.195
A.4.2 BTS power control management .196
A.5 Handover control management.197
A.6 Frequency control management .198
A.7 Architectural element management .200
A.8 Software management .202
A.9 Equipment management.204
Annex B (informative): Lists of functions and GDMO definitions .205
B.1 List of Management Functions .205
B.2 List of Managed Object Classes .205
B.3 List of Packages.206
B.4 List of Actions.207
B.5 List of Notifications .207
B.6 List of Parameters .207
B.7 List of Attributes.208
B.8 List of Name Bindings .210
Annex C (informative): Index.211
History.225

Page 10
ETS 300 622: June 1996 (GSM 12.20 version 4.2.1)
Blank page
Page 11
ETS 300 622: June 1996 (GSM 12.20 version 4.2.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 management information model for the Configuration and Fault Management
aspects of the GSM BSS Network Element as seen on the Q3 interface between the OS (e.g. OMC) and
the BSS within the Digital cellular telecommunications system. This ETS corresponds to GSM technical
specification, GSM 12.20, version 4.2.1.
NOTE: TC-SMG has produced documents which give technical specifications for the
implementation of the Digital cellular telecom
...