NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 1/1
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel .
NMC/9153 OMC-R Q3 Interface:
GDMO Formal Specification
Release B11
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 1/1
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel .
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 1/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
SYSTEM FUNCTIONAL BLOCKS
TABLE OF CONTENTS
1. INTRODUCTION.............................................................................................15
1.1 SCOPE ..................................................................................................15
1.2 NOTATIONS..........................................................................................15
1.3 STRATEGY ...........................................................................................15
2. ANOI INFORMATION MODEL .......................................................................17
2.1 MANAGED OBJECT CLASS DEFINITIONS ........................................17 2.1.1 anoiBasebandTransceiver ...................................................17
2.1.2 anoiBsc........................................................................................17 2.1.3 anoiBssFunction ..........................................................................18 2.1.4 anoiBts.........................................................................................18 2.1.5 anoiBtsSiteManager ....................................................................19 2.1.6 anoiCircuitPack............................................................................19 2.1.7 anoiCoreManagedElement..........................................................20 2.1.8 anoiEquipmentR1 ........................................................................20 2.1.9 anoiGPRSManagedElement .......................................................20 2.1.10 anoiFunctionCoordinator ...................................................21
2.1.11 anoiFunction...........................................................................21
2.1.12 anoiLapdLink ...............................................................................21 2.1.13 anoiManagedElement..................................................................21 2.1.14 anoiPlmnNetwork ........................................................................22 2.1.15 anoiSignLinkSetTp ......................................................................22 2.1.16 anoiSignLinkTp............................................................................23 2.1.17 anoiTerminationPointBidirectional ...............................................24 2.1.18 associationSurveyRecord ............................................................25
2.2 PACKAGE DEFINITIONS .....................................................................25 2.2.1 acknowledgeAlarmsPackage.......................................................25 2.2.2 anoiBasebandTransceiverPackage ....................................25 2.2.3 anoiBscBasicPackage .................................................................26 2.2.4 anoiBtsBasicPackage..................................................................27 2.2.5 anoiCoreManagedElementPackage............................................29 2.2.6 anoiFunctionCoordinatorPackage ....................................30 2.2.7 anoiFunctionPackage............................................................30 2.2.8 anoiGPRSManagedElementPackage..........................................30 2.2.9 anoiLapdLinkPackage .................................................................31 2.2.10 anoiPlmnNetworkPackage...........................................................32 2.2.11 anoiSignLinkSetTpPackage ........................................................32 2.2.12 anoiSignLinkTpPackage..............................................................34 2.2.13 anoiTerminationPointBidirectionalPackage .................................36 2.2.14 associationSurveyNotificationPackage........................................37 2.2.15 associationSurveyRecordPackage ..............................................37 2.2.16 retrieveCurrentAlarmsDataPackage ............................................37
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 2/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
2.3 ATTRIBUTE DEFINITIONS...................................................................37 2.3.1 anoiFunctionCoordinatorId ...............................................37
2.3.2 anoiFunctionId.......................................................................37
2.3.3 anoiTPId ......................................................................................38
2.4 ACTION DEFINITIONS .........................................................................38 2.4.1 acknowledgeAlarms.....................................................................38 2.4.2 retrieveCurrentAlarmsData ..........................................................38
2.5 NOTIFICATION DEFINITIONS..............................................................39 2.5.1 associationSurvey........................................................................39
2.6 NAME BINDING DEFINITIONS.............................................................39 2.6.1 anoi-basebandTransceiver-bts.........................................39
2.6.2 anoi-btsSiteManager-bssFunction ...............................................39 2.6.3 anoi-equipment-equipment..........................................................40 2.6.4 anoi-equipmentHolder-equipmentHolder.....................................40 2.6.5 anoi-functionCoordinator-equipmentR1 .......................40
2.6.6 anoi-function-functionCoordinator ..............................40
2.6.7 anoi-generalDataTsfCtrlFct-network............................................41 2.6.8 anoi-simpleFileTsfCtrl-generalDataTsfCtrlFct..............................41 2.6.9 anoi-system-root ..........................................................................41 2.6.10 anoiBsc-bssFunction ...................................................................41 2.6.11 anoiBts-btsSiteManager ..............................................................42 2.6.12 anoiCircuitPack-equipmentHolder ...............................................42 2.6.13 anoiLapdLink-bssFunction...........................................................42 2.6.14 anoiPlmnNetwork-root .................................................................42 2.6.15 anoiSignLinkSetTp-mtpSignPoint ................................................42 2.6.16 anoiSignLinkTp-anoiSignLinkSetTp.............................................43 2.6.17 anoiTerminationPointBidirectional-equipment .............................43 2.6.18 bssFunction-anoiCoreManagedElement .....................................43 2.6.19 connectionR1-anoiCoreManagedElement...................................43 2.6.20 equipment-anoiCoreManagedElement ........................................44 2.6.21 generalDataTsfCtrlFct-anoiCoreManagedElement......................44 2.6.22 generalDataTsfCtrlFct-anoiGPRSManagedElement ...................44 2.6.23 anoi-managedElement-network...................................................44 2.6.24 mtpSignPoint-anoiCoreManagedElement ...................................45
2.7 COMMON BEHAVIOUR DEFINITIONS ................................................45 2.7.1 anoi-generalDataTsfCtrlFct-managedElementBeh......................45
2.8 ASN1 DEFINITIONS..............................................................................45
3. ACOM PART...................................................................................................47
3.1 PACKAGE DEFINITIONS .....................................................................47 3.1.1 a1353RAInstanceNamePackage ................................................47 3.1.2 alarmStatusPackage ...................................................................47 3.1.3 clientNodeIdentifierPackage........................................................47 3.1.4 controlStatusPackage..................................................................47 3.1.5 proceduralStatusPackage ...........................................................47 3.1.6 qualityofServiceAlarmPackage ....................................................48 3.1.7 relatedGSMEquipmentPackage ..................................................48 3.1.8 supportedByObjectListPackage...................................................48
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 3/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
3.1.9 typeOfFileTransferPackage.........................................................48 3.1.10 unknownStatusPackage ..............................................................48
3.2 ATTRIBUTE DEFINITIONS...................................................................48 3.2.1 a1353RAInstanceName ..............................................................48 3.2.2 clientNodeIdentifier......................................................................49 3.2.3 typeOfFileTransfer.......................................................................49
3.3 PARAMETER DEFINITIONS.................................................................49 3.3.1 alarmAcknowledgementIndication ...............................................49 3.3.2 internalNEAlarmAdditionalInformation.........................................50 3.3.3 internalNEAlarmDescriptionLocation ...........................................50 3.3.4 internalNEAlarmMOIIndication ....................................................51 3.3.5 Parameter behaviours .................................................................51
3.3.5.1 additionalInformationParametersBehaviour ...................................................51
3.4 ASN1 DEFINITIONS..............................................................................52
4. ANOI GSM 12.20 SUBSET ............................................................................54
4.1 MANAGED OBJECT CLASS DEFINITIONS ........................................54 4.1.1 btsSiteManager ...........................................................................54 4.1.2 gsmManagedFunction .................................................................54
4.2 PACKAGE DEFINITIONS .....................................................................54 4.2.1 btsSiteManagerBasicPackage.....................................................54 4.2.2 equipmentRelatedAlarmPackage ................................................55 4.2.3 functionalRelatedAlarmPackage .................................................56
4.3 ATTRIBUTE DEFINITIONS...................................................................56 4.3.1 basebandTransceiverID........................................................56
4.3.2 bscID ...........................................................................................56 4.3.3 btsID ............................................................................................57 4.3.4 btsSiteManagerID........................................................................57 4.3.5 cellGlobalIdentity .........................................................................57 4.3.6 lapdLinkID....................................................................................57 4.3.7 relatedGSMEquipment ................................................................58 4.3.8 relatedOAMLapdLink...................................................................58 4.3.9 sapi ..............................................................................................58 4.3.10 tei.................................................................................................59
4.4 NAME BINDING DEFINITIONS.............................................................59 4.4.1 Name Binding Behaviours ...........................................................59
4.4.1.1 bsc-bssFunctionBehaviour..............................................................................59
4.5 ASN1 DEFINITIONS..............................................................................59
5. ANOI GSM 12.00 SUBSET ............................................................................61
5.1 MANAGED OBJECT CLASS DEFINITIONS ........................................61 5.1.1 bssFunction .................................................................................61 5.1.2 bulkTransferErrorRecord .............................................................61 5.1.3 generalDataTransferControlFunction ..........................................61 5.1.4 simpleFileTransferControl ...........................................................61 5.1.5 transferReadyRecord ..................................................................62
5.2 PACKAGE DEFINITIONS .....................................................................62 5.2.1 bssFunctionPackage ...................................................................62
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 4/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
5.2.2 bulkTransferErrorPackage...........................................................62 5.2.3 dataTransferUploadControlPackage ...........................................62 5.2.4 generalDataTransferControlFunctionPackage ............................63 5.2.5 simpleFileTransferControlBasicPackage.....................................64 5.2.6 transferNotificationArgPackage ...................................................64 5.2.7 Package Behaviours....................................................................65
5.2.7.1 plmnNetworkBehaviour..................................................................................65
5.3 ATTRIBUTE DEFINITIONS...................................................................65 5.3.1 bssFunctionId ..............................................................................65 5.3.2 fileListValues ...............................................................................65 5.3.3 generalDataTransferControlFunctionId .......................................65 5.3.4 linkedTransferIdValue..................................................................66 5.3.5 mcc..............................................................................................66 5.3.6 mnc..............................................................................................66 5.3.7 simpleFileTransferControlId ........................................................67 5.3.8 transferIdValue ............................................................................67
5.4 ACTION DEFINITIONS .........................................................................67 5.4.1 requestTransferUp.......................................................................67 5.4.2 transferUpReceived.....................................................................68
5.5 NOTIFICATION DEFINITIONS..............................................................68 5.5.1 bulkTransferError.........................................................................68 5.5.2 transferUpReady .........................................................................69
5.6 NAME BINDING DEFINITIONS.............................................................70 5.6.1 NAME BINDING BEHAVIOURS..................................................70
5.6.1.1 bssFunction-managedElementBehaviour........................................................70
5.7 ASN1 DEFINITIONS..............................................................................70 5.7.1 GSM1200ATypeModule ..............................................................70 5.7.2 GSM1200BTypeModule ..............................................................71
6. ANOI GSM 12.11 SUBSET ............................................................................74
7. ANOI GSM 12.30 SUBSET ............................................................................78
8. ANOI ETR 091 SUBSET ................................................................................79
9. ANOI Q.751.1 SUBSET..................................................................................80
9.1 MANAGED OBJECT CLASS DEFINITIONS ........................................80 9.1.1 mtpSignPoint ...............................................................................80
9.2 PACKAGE DEFINITIONS .....................................................................80 9.2.1 administrativeStatePackage ........................................................80 9.2.2 communicationsAlarmPackage ...................................................81 9.2.3 mtpSignPointPackage .................................................................81
9.3 ATTRIBUTE DEFINITIONS...................................................................82 9.3.1 adjPc............................................................................................82 9.3.2 mtpSignPointId ............................................................................82 9.3.3 networkIndicator ..........................................................................82 9.3.4 pointCode ....................................................................................82 9.3.5 signLinkSetTpId...........................................................................83
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 5/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
9.3.6 slCode .........................................................................................83 9.3.7 spType.........................................................................................83
9.4 NOTIFICATION DEFINITIONS..............................................................84 9.4.1 mtpRestarting ..............................................................................84
9.5 NAME BINDING DEFINITIONS.............................................................84 9.5.1 NAME BINDING BEHAVIOURS..................................................84
9.5.1.1 managedSwitchingElement-mtpSignPointBehaviour.....................................84 9.5.1.2 mtpSignPoint-signLinkSetTpBehaviour.........................................................84 9.5.1.3 signLinkSetTp-signLinkTpBehaviour ............................................................85
9.6 ASN1 DEFINITIONS..............................................................................85
10. ANOI M.3100 SUBSET...................................................................................87
10.1 MANAGED OBJECT CLASS DEFINITIONS ........................................87 10.1.1 circuitPack .............................................................................87 10.1.2 connectionR1...............................................................................87 10.1.3 equipment....................................................................................87 10.1.4 equipmentHolder .........................................................................88 10.1.5 equipmentR1 ...............................................................................88 10.1.6 managedElement ........................................................................89 10.1.7 network ........................................................................................90 10.1.8 pipe..............................................................................................90 10.1.9 terminationPoint...........................................................................91
10.2 PACKAGE DEFINITIONS .....................................................................91 10.2.1 administrativeOperationalStatesPackage....................................91 10.2.2 affectedObjectListPackage..........................................................91 10.2.3 attributeValueChangeNotificationPackage ..................................92 10.2.4 circuitPackPackage .....................................................................92 10.2.5 connectionPackage .....................................................................92 10.2.6 createDeleteNotificationsPackage...............................................93 10.2.7 currentProblemListPackage.........................................................93 10.2.8 environmentalAlarmPackage.......................................................93 10.2.9 equipmentAlarmEffectOnServicePackage...................................93 10.2.10 equipmentHolderPackage ...........................................................93 10.2.11 equipmentPackage......................................................................94 10.2.12 equipmentR1Package .................................................................95 10.2.13 equipmentsEquipmentAlarmPackage..........................................95 10.2.14 externalTimePackage..................................................................96 10.2.15 locationNamePackage.................................................................96 10.2.16 managedElementPackage ..........................................................96 10.2.17 networkPackage ..........................................................................97 10.2.18 operationalStatePackage ............................................................97 10.2.19 pipePackage................................................................................97 10.2.20 processingErrorAlarmPackage ....................................................98 10.2.21 stateChangeNotificationPackage.................................................98 10.2.22 terminationPointPackage.............................................................98 10.2.23 tmnCommunicationsAlarmInformationPackage...........................99 10.2.24 userLabelPackage.......................................................................99 10.2.25 vendorNamePackage ..................................................................99 10.2.26 versionPackage .........................................................................100
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 6/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
10.3 ATTRIBUTE DEFINITIONS.................................................................100 10.3.1 a-TPInstance .............................................................................100 10.3.2 affectedObjectList......................................................................100 10.3.3 alarmStatus ...............................................................................100 10.3.4 circuitPackType .........................................................................101 10.3.5 connectionId ..............................................................................101 10.3.6 currentProblemList ....................................................................101 10.3.7 directionality...............................................................................102 10.3.8 downstreamConnectivityPointer ................................................102 10.3.9 equipmentHolderAddress ..........................................................102 10.3.10 equipmentHolderType ...............................................................103 10.3.11 equipmentId...............................................................................103 10.3.12 externalTime..............................................................................103 10.3.13 locationName.............................................................................104 10.3.14 managedElementId ...................................................................104 10.3.15 networkId ...................................................................................104 10.3.16 replaceable ................................................................................105 10.3.17 serialNumber .............................................................................105 10.3.18 supportedByObjectList ..............................................................105 10.3.19 tTPId........................................................................................106 10.3.20 upstreamConnectivityPointer.....................................................106 10.3.21 userLabel...................................................................................106 10.3.22 vendorName ..............................................................................106 10.3.23 version .......................................................................................107 10.3.24 z-TPInstance .............................................................................107
10.4 NAME BINDING DEFINITIONS...........................................................107 10.4.1 circuitPack-equipmentHolder-autoCreated ...............107 10.4.2 managedElement-network.........................................................107 10.4.3 Name Binding Behaviours .........................................................108
10.4.3.1 circuitPack-equipmentHolder-autoCreateBeh ............................................108 10.4.3.2 equipmentHolder-equipmentHolderBeh.....................................................108 10.4.3.3 equipmentNameBindingBehaviour.............................................................108
10.5 ASN1 DEFINITIONS............................................................................108
11. ANOI X.721 SUBSET ...................................................................................113
11.1 MANAGED OBJECT CLASS DEFINITIONS ......................................113 11.1.1 alarmRecord ..............................................................................113 11.1.2 attributeValueChangeRecord ....................................................113 11.1.3 discriminator ..............................................................................114 11.1.4 eventForwardingDiscriminator ...................................................114 11.1.5 eventLogRecord ........................................................................115 11.1.6 log..............................................................................................115 11.1.7 logRecord ..................................................................................116 11.1.8 objectCreationRecord................................................................116 11.1.9 objectDeletionRecord ................................................................117 11.1.10 stateChangeRecord...................................................................117 11.1.11 system .......................................................................................117 11.1.12 top..............................................................................................118
11.2 PACKAGE DEFINITIONS ...................................................................118
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 7/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
11.2.1 additionalInformationPackage ...................................................118 11.2.2 additionalTextPackage ..............................................................118 11.2.3 administrativeStatePackage ......................................................118 11.2.4 alarmRecordPackage ................................................................118 11.2.5 attributeIdentifierListPackage ....................................................119 11.2.6 attributeListPackage ..................................................................119 11.2.7 attributeValueChangeRecordPackage ......................................119 11.2.8 availabilityStatusPackage ..........................................................119 11.2.9 backUpDestinationListPackage .................................................120 11.2.10 discriminatorPackage ................................................................120 11.2.11 efdPackage................................................................................121 11.2.12 eventLogRecordPackage ..........................................................121 11.2.13 eventTimePackage....................................................................121 11.2.14 finiteLogSizePackage ................................................................121 11.2.15 logAlarmPackage ......................................................................122 11.2.16 logPackage................................................................................122 11.2.17 logRecordPackage ....................................................................122 11.2.18 modePackage............................................................................123 11.2.19 monitoredAttributesPackage .....................................................123 11.2.20 objectCreationRecordPackage..................................................123 11.2.21 objectDeletionRecordPackage ..................................................123 11.2.22 packagesPackage .....................................................................123 11.2.23 proposedRepairActionsPackage ...............................................124 11.2.24 specificProblemsPackage .........................................................124 11.2.25 stateChangeDefinitionPackage .................................................124 11.2.26 stateChangeRecordPackage.....................................................124 11.2.27 systemPackage .........................................................................124 11.2.28 thresholdInfoPackage................................................................125 11.2.29 topPackage................................................................................125
11.3 ATTRIBUTE DEFINITIONS.................................................................125 11.3.1 activeDestination .......................................................................125 11.3.2 additionalInformation .................................................................125 11.3.3 additionalText ............................................................................126 11.3.4 administrativeState ....................................................................126 11.3.5 attributeIdentifierList ..................................................................126 11.3.6 attributeList ................................................................................126 11.3.7 attributeValueChangeDefinition.................................................127 11.3.8 availabilityStatus........................................................................127 11.3.9 backUpDestinationList ...............................................................127 11.3.10 capacityAlarmThreshold ............................................................127 11.3.11 confirmedMode..........................................................................127 11.3.12 controlStatus..............................................................................127 11.3.13 currentLogSize ..........................................................................128 11.3.14 destination .................................................................................128 11.3.15 discriminatorConstruct ...............................................................128 11.3.16 discriminatorId ...........................................................................128 11.3.17 eventTime..................................................................................128 11.3.18 eventType..................................................................................128 11.3.19 logFullAction ..............................................................................129
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 8/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
11.3.20 loggingTime ...............................................................................129 11.3.21 logId...........................................................................................129 11.3.22 logRecordId ...............................................................................129 11.3.23 managedObjectClass ................................................................129 11.3.24 managedObjectInstance............................................................129 11.3.25 maxLogSize...............................................................................130 11.3.26 monitoredAttributes ...................................................................130 11.3.27 nameBinding..............................................................................130 11.3.28 numberOfRecords .....................................................................130 11.3.29 objectClass ................................................................................130 11.3.30 operationalState ........................................................................130 11.3.31 packages ...................................................................................131 11.3.32 perceivedSeverity ......................................................................131 11.3.33 probableCause ..........................................................................131 11.3.34 proceduralStatus .......................................................................131 11.3.35 proposedRepairActions .............................................................131 11.3.36 specificProblems .......................................................................131 11.3.37 stateChangeDefinition ...............................................................132 11.3.38 systemId ....................................................................................132 11.3.39 systemTitle ................................................................................132 11.3.40 thresholdInfo..............................................................................132 11.3.41 unknownStatus ..........................................................................132 11.3.42 usageState ................................................................................132 11.3.43 Common Attribute Behaviours...................................................133
11.3.43.1 rDNIdBehaviour........................................................................................133 11.3.43.2 timeOrdering .............................................................................................133
11.4 NOTIFICATION DEFINITIONS............................................................133 11.4.1 attributeValueChange................................................................133 11.4.2 communicationsAlarm ...............................................................133 11.4.3 environmentalAlarm...................................................................134 11.4.4 equipmentAlarm ........................................................................134 11.4.5 objectCreation ...........................................................................135 11.4.6 objectDeletion............................................................................135 11.4.7 processingErrorAlarm................................................................136 11.4.8 qualityofServiceAlarm................................................................136 11.4.9 stateChange ..............................................................................137
11.5 NAME BINDING DEFINITIONS...........................................................137 11.5.1 discriminator-system..................................................................137 11.5.2 log-system .................................................................................138 11.5.3 logRecord-log ............................................................................138
11.6 ASN1 DEFINITIONS............................................................................138 11.6.1 ManagedObjectClassesDefinitions............................................138 11.6.2 Attribute-ASN1Module...............................................................138 11.6.3 Notification-ASN1Module ..........................................................145
12. ANOI X.711 SUBSET ...................................................................................147
13. ANOI X.227 SUBSET ...................................................................................149
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 9/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
14. ANOI X.501 SUBSET ...................................................................................150
15. PSEUDO NMD SUBSET FOR ANOI .....................................................151 15.1 MANAGED OBJECT CLASS DEFINITIONS ........................................151
15.1.1 neGroup....................................................................................151 15.1.2 neSupervisionCoordinator ...............................................151 15.1.3 networkElement.....................................................................151
15.2 PACKAGE DEFINITIONS ....................................................................152 15.2.1 neGroupPackage.....................................................................152 15.2.2 neSupervisionCoordinatorPackage ................................152 15.2.3 networkElementPackage......................................................152
15.3 ATTRIBUTE DEFINITIONS................................................................152 15.3.1 neGroupId ...............................................................................152 15.3.2 neSupervisionCoordinatorId...........................................152 15.3.3 networkElementId ................................................................152
15.4 NAME BINDING DEFINITIONS .........................................................152 15.4.1 aGprs2MbTTP-networkElement...........................................152 15.4.2 aGprsBssFunction-networkElement ................................153 15.4.3 aGprsFabric-networkElement...........................................153 15.4.4 aGprsNse-networkElement .................................................153 15.4.5 equipment-networkElement ...............................................153 15.4.6 neGroup-neGroup ..................................................................153 15.4.7 neSupervisionCoordinator-networkElement ...............153 15.4.8 networkElement-neGroup ...................................................153
15.5 ASN1 DEFINITIONS ..........................................................................154
16. PSEUDO AGFR SUBSET FOR ANOI...................................................155 16.1 MANAGED OBJECT CLASS DEFINITIONS ........................................155
16.1.1 aGprsBearerChannel ............................................................155 16.1.2 aGprsPvc .................................................................................155
16.2 PACKAGE DEFINITIONS ....................................................................155 16.2.1 aGprsBearerChannelPackage .............................................155 16.2.2 aGprsPvcPackage ..................................................................155
16.3 ATTRIBUTE DEFINITIONS................................................................155 16.3.1 aGprsBearerChannelId........................................................155 16.3.2 aGprsDlcId .............................................................................156
16.4 NAME BINDING DEFINITIONS .........................................................156 16.4.1 aGprsBearerChannel-aGprs2MbTTP ..................................156 16.4.2 aGprsPvc-aGprsBearerChannel.........................................156
16.5 ASN1 DEFINITIONS ..........................................................................156
17. PSEUDO AATER SUBSET FOR ANOI.................................................158 17.1 MANAGED OBJECT CLASS DEFINITIONS ........................................158
17.1.1 aGprsLapdLink.......................................................................158 17.2 PACKAGE DEFINITIONS ....................................................................158
17.2.1 aGprsLapdLinkPackage........................................................158 17.3 NAME BINDING DEFINITIONS .........................................................158
17.3.1 aGprsLapdLink-aGprs2MbTTP .............................................158
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 10/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
17.4 ASN1 DEFINITIONS ..........................................................................158
18. PSEUDO AMFSME SUBSET FOR ANOI ..............................................160 18.1 MANAGED OBJECT CLASS DEFINITIONS ........................................160
18.1.1 aGprs2MbTTP ...........................................................................160 18.1.2 aGprsFabric ...........................................................................160
18.2 PACKAGE DEFINITIONS ....................................................................160 18.2.1 aGprs2MbTTPPackage ............................................................160 18.2.2 aGprsFabricPackage ............................................................160
18.3 ATTRIBUTE DEFINITIONS................................................................160 18.3.1 aGprsFabricId.......................................................................160
18.4 ASN1 DEFINITIONS ..........................................................................161
19. PSEUDO ABSS SUBSET FOR ANOI...................................................162 19.1 MANAGED OBJECT CLASS DEFINITIONS ........................................162
19.1.1 aGprsBssFunction ................................................................162 19.1.2 aGprsBts .................................................................................162 19.1.3 aGprsBtsSiteManager..........................................................162
19.2 PACKAGE DEFINITIONS ....................................................................162 19.2.1 aGprsBssFunctionPackage .................................................162 19.2.2 aGprsBtsPackage ..................................................................162 19.2.3 aGprsBtsSiteManagerPackage...........................................162
19.3 NAME BINDING DEFINITIONS .........................................................163 19.3.1 aGprsBts-aGprsBtsSiteManager.......................................163 19.3.2 aGprsBts-btsSiteManager .................................................163 19.3.3 aGprsBtsSiteManager-aGprsBssFunction .....................163 19.3.4 btsSiteManager-aGprsBssFunction ................................163
19.4 ASN1 DEFINITIONS ..........................................................................163
20. PSEUDO AGVC SUBSET FOR ANOI...................................................165 20.1 MANAGED OBJECT CLASS DEFINITIONS ........................................165
20.1.1 aGprsNse .................................................................................165 20.1.2 aGprsNsvc ...............................................................................165
20.1.2.1 aGprsSgsnIpEndPoint .................................................................165
20.2 PACKAGE DEFINITIONS ....................................................................165 20.2.1 aGprsNsePackage ..................................................................165 20.2.2 aGprsNsvcPackage ................................................................165 20.2.3 aGprsSgsnIpEndPointPackage...........................................165
20.3 ATTRIBUTE DEFINITIONS................................................................166 20.3.1 aGprsNseId .............................................................................166 20.3.2 aGprsNsvcId ...........................................................................166 20.3.3 aGprsSgsnIpEndpointId......................................................166
20.4 NAME BINDING DEFINITIONS .........................................................166 20.4.1 aGprsNsvc-aGprsNse ............................................................166 20.4.2 aGprsSgsnIpEndPoint-aGprsNse.......................................166
20.5 ASN1 DEFINITIONS ..........................................................................166
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 11/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
21. PSEUDO LAPF SUBSET FOR ANOI...................................................168 21.1 MANAGED OBJECT CLASS DEFINITIONS ........................................168
21.1.1 nectarCircuitPack ..............................................................168 21.2 PACKAGE DEFINITIONS ....................................................................168
21.2.1 nectarCircuitPackPackage ...............................................168 21.3 NAME BINDING DEFINITIONS .........................................................168
21.3.1 nectarCircuitPack-equipmentHolder-autoCreated ..168 21.4 ASN1 DEFINITIONS ..........................................................................168
22. ACRONYMS .....................................................................................................2
02 YYMMDD Update O&M System TD/MRC/OMD Spec
01 090515 First issue O&M System TD/MRC/OMD Spec
ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 12/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
LIST OF FIGURES AND TABLES
None.
HISTORY
Ed. 01
29/04/2009: Creation from 3BK 09707 LAAA PBZZA Ed.02 Released.
General Changes
B10 is replaced by B11
The RELATED DOCUMENTS part is updated for B11
AMFSME Subset
GDMO/ASN1 Definitions Added MOC definition:
aGprsFabric Added Package definition:
aGprsFabricPackage Added Attribute definition:
aGprsFabricId Added ASN1 definition (new imports):
NameType NMD Subset
GDMO/ASN1 Definitions Added Name Binding definition:
aGprsFabric-networkElement 15/05/2009: No technical changes.
Ed. 02
11/03/2010
ANOI Subset
GDMO/ASN1 Definitions Added MOC definition:
AnoiSNMPManagedElement Added Package definition:
AnoiSNMPManagedElementPAckage
REFERENCED DOCUMENTS
[ASN1] Information Processing Systems - Open Systems Interconnection - Specification of Abstract Syntax Notation One (ASN.1) CCITT Rec. X.208 (1988) | ISO/IEC 8824
[GDMO] Information Technology - Open Systems Interconnection- Structure of Management Information: Guidelines for the Definition of Management Information CCITT Recommendation X.722 (ISO/IEC 10165-4), 1992
[X.501] Information Technology - Open Systems Interconnection - The Directory: The Models CCITT Recommendation X.501 (ISO/IEC 9594-2), Blue Book Vol. VIII.8, Geneva 1988
[X.227] Information Technology - Open Systems Interconnection - Connection-
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 13/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
oriented Protocol for the Association Control Service Element: Protocol Specification CCITT Recommendation X.227 (ISO/IEC 8650-1), April 1995
[X.711] Data Communication Networks- Open Systems Interconnection (OSI)- Management Common Management Information Protocol Specification CCITT Recommendation X.711 (ISO/IEC 9596), March 1991
[X.721] Information Technology - Open Systems Interconnection Structure of Management Information - Part 2: Definition of Management Information CCITT Recommendation X.721 (ISO/IEC 10165-2); 1991 with the technical corrigendum 1, 1994
[M.3100] Maintenance: Telecommunications Management Network - Generic Network Information Model; CCITT Recommendation M.3100, July 1995
[Q.821] Specifications of signalling system No. 7 Q3 Interface - Stage 2 and Stage 3 description for the Q3 Interface - Alarm Surveillance
[Q.751.1] Specifications of signalling system No. 7 - Network Element Management Information Model for the Message Transfer Part (MTP) ITU-T Recommendation Q.751.1, October 1995
[ETR 091] ETSI object identifier tree; Common domain Mobile domain ETSI Technical Report (ETR) 091, July 1993
[GSM 12.30] European Digital cellular telecommunications system (Phase 2); ETSI Object Identifier Tree; Common Domain; Mobile domain; Operation and Maintenance (O&M), managed object registration definition GSM 12.30 version 4.2.0, ETR 128, August 1995
[GSM 12.00] Digital cellular telecommunications system (Phase 2); Network Management (NM); Part 1: Objectives and structure of Network Management GSM 12.00 version 4.5.1, ETS 300 612-1, August 1996
[GSM 12.11] Digital cellular telecommunications system (Phase 2+); Fault management of the Base Station System (BSS) GSM 12.11 version 6.1.0, TS 101 251, October 1998
[GSM 12.20] Digital cellular telecommunications system (Phase 2); Base Station System (BSS) Management Information GSM 12.20 version 4.2.1, ETS 300 622, June 1996
RELATED DOCUMENTS
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 14/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
[ANOIprofile] Profile for the NMC/9153 OMC-R Q3 Interface 3BK 09654 MAAA PBZZA
[ANOIappli] NMC/9153 OMC-R Q3 Interface Information Model: Position with respect to standards of the GDMO Formal Specification 3BK 09708 MAAA PBZZA
[ANOIcs-gene] NMC/9153 OMC-R Q3 Interface Information Model: Overview and Conformance Statements 3BK 09709 MAAA PBZZA
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 15/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
1. INTRODUCTION
1.1 SCOPE
This document belongs to the set of documents concerning the NMC/9153 OMC-R Q3 Interface Information Model (see [ANOIcs-gene]). It contains the corresponding GDMO Formal Specification.
1.2 NOTATIONS
This Q3 interface is specified using the notations:
GDMO as defined in [GDMO]
ASN.1 as defined in [ASN1]
Italics are used to highlight parts that are not supported (possibly also commented out). The corresponding positions with respect to the concerned standard are documented in [ANOIappli]. Courrier font with light grey is used to highlight parts enabling to decode the element of the additionalInformation field corresponding to the "ACOM":internalNEAlarmMOIIndication parameter, notably the definitions specified in the so-called ANOI pseudo subsets and the definitions referenced by them.
1.3 STRATEGY
The strategy retained for this GDMO Formal Specification is as follows:
It relies on the versions of the standards specified in the REFERENCED DOCUMENTS part.
It is cleanly defined over these standards:
Standard definitions are used whenever possible.
No non-compliant modifications with respect to standard definitions are performed. In particular,
Peculiarities are documented separately (in [ANOIcs-gene]) and not directly within the GDMO/ASN1 definitions. For example, if an attribute is defined as GET-REPLACE in a standard package but M-SET requests on this attribute are not supported, the standard package is not modified and the corresponding restriction is documented separately, namely as a Conformance Statement in [ANOIcs-gene].
N.B.: The position with respect to standards is described in [ANOIappli].
It is self-contained, i.e. all the definitions and the definitions they actually reference are present in this document. In order for this to be manageable, if a standard definition references another one which is never used, the unused part is commented out (and appears in italics), provided this modification is compliant. For example, if a Managed Object Class definition references a conditional package that is never instantiated, the corresponding part of the Managed Object Class definition is commented out, so that the conditional package need not be defined.
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 16/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
To help find a given definition:
Inlined definitions (i.e. directly included in another definition) are replaced by the equivalent non-inlined one.
When referenced in only one definition, a given Behaviour is placed in the same section as the definition that references it.
The definitions are splitted
per standard,
then per category using the following order:
Managed Object Class definitions (if any)
Package definitions
Attribute Definitions
Action definitions
Notification definitions
Name Binding Definitions
ASN1 Definitions Possible sub-categories are the different modules (when there are several ones).
then per alphabetical order.
ASCII files corresponding to the contents of the document can automatically be generated. This makes it possible to check the contents of this document and to deliver to clients pre-checked files using the HP OpenView GDMO Object Modelling Tool (OvGmt).
The contents of this document correspond to the files delivered to the NMC/9153 OMC-R Q3 Interface clients.
Compiler restrictions are not taken into account except one since it also corresponds to a deprecated ASN1 capability, namely unamed fields in SEQUENCE and CHOICE ASN1 types. The corresponding changes are documented hereafter using the following comment:
CHANGE (unamed ASN1 fields not supported)
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 17/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
2. ANOI INFORMATION MODEL
-- X.721 is used to label definitions from the ANOI X.721 subset -- M.3100 is used to label definitions from the ANOI M.3100 subset -- Q.751.1 is used to label definitions from the ANOI Q.751.1 subset -- GSM 12.00 is used to label definitions from the ANOI GSM 12.00 subset -- GSM 12.20 is used to label definitions from the ANOI GSM 12.20 subset -- ACOM is used to label definitions from the ACOM part -- The OIDs of the proprietary definitions that have a standard counterpart are deduced from -- the latter by adding an offset which is: -- 1000 for GSM 12.20 -- 2000 for GSM 12.00A -- 2500 for GSM 12.00B -- 3000 for Q.751.1 -- 4000 for M.3100 -- 4500 for X.721
2.1 MANAGED OBJECT CLASS DEFINITIONS
2.1.1 anoiBasebandTransceiver
anoiBasebandTransceiver MANAGED OBJECT CLASS
DERIVED FROM X.721:top;
CHARACTERIZED BY anoiBasebandTransceiverPackage;
REGISTERED AS { anoiManagedObjectClass 100};
2.1.2 anoiBsc
anoiBsc MANAGED OBJECT CLASS -- based on GSM 12.20:bsc
DERIVED FROM GSM 12.20:gsmManagedFunction;
CHARACTERIZED BY anoiBscBasicPackage,
-- GSM 12.20:bssMapTimerPackage, GSM 12.20:functionalRelatedAlarmPackage, M.3100:stateChangeNotificationPackage;
CONDITIONAL PACKAGES
-- GSM 12.20:adjustExternalTimePackage PRESENT IF -- the M.3100 externalTimePackage is present in the M.3100 managedElement -- MOC instance containing this object instance and if the instance supports it,
-- GSM 12.20:bscProcForBTSPowerControlPackage PRESENT IF -- an instance supports it,
ACOM:clientNodeIdentifierPackage PRESENT IF the clientNodeIdentifier attribute is supported,
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 18/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
M.3100:currentProblemListPackage PRESENT IF the currentProblemList attribute is supported,
GSM 12.20:equipmentRelatedAlarmPackage PRESENT IF an instance supports it;
-- GSM 12.20:internalIntraCellHandoverPackage PRESENT IF -- an instance supports it,
-- GSM 12.20:internalInterCellHandoverPackage PRESENT IF -- an instance supports it;
REGISTERED AS { anoiManagedObjectClass 1060 };
2.1.3 anoiBssFunction
anoiBssFunction MANAGED OBJECT CLASS
DERIVED FROM GSM 12.00:bssFunction;
CONDITIONAL PACKAGES
X.721:administrativeStatePackage PRESENT IF the administrativeState attribute is supported;
REGISTERED AS { anoiManagedObjectClass 5 };
2.1.4 anoiBts
anoiBts MANAGED OBJECT CLASS -- based on GSM 12.20:bts
DERIVED FROM GSM 12.20:gsmManagedFunction;
CHARACTERIZED BY anoiBtsBasicPackage,
-- GSM 12.20:btsCCCHConfigurationPackage, -- GSM 12.20:btsOptionsPackage, -- GSM 12.20:btsTimerPackage;
GSM 12.20:functionalRelatedAlarmPackage, M.3100:stateChangeNotificationPackage;
CONDITIONAL PACKAGES
-- GSM 12.20:btsPowerControlConfigPackage PRESENT IF -- an instance supports it,
-- GSM 12.20:btsQueuingPackage PRESENT IF -- an instance supports it,
-- GSM 12.20:channelConfigModPackage PRESENT IF -- an instance supports it,
ACOM:clientNodeIdentifierPackage PRESENT IF the clientNodeIdentifier attribute is supported,
M.3100:currentProblemListPackage PRESENT IF the currentProblemList attribute is supported,
GSM 12.20:equipmentRelatedAlarmPackage PRESENT IF an instance supports it;
-- GSM 12.20:hoMsmtProcessingModePackage PRESENT IF -- an instance supports it,
-- GSM 12.20:pcMsmtProcessingModePackage PRESENT IF
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 19/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
-- an instance supports it;
REGISTERED AS { anoiManagedObjectClass 1070 };
2.1.5 anoiBtsSiteManager
anoiBtsSiteManager MANAGED OBJECT CLASS
DERIVED FROM GSM 12.20:btsSiteManager;
CONDITIONAL PACKAGES
M.3100:administrativeOperationalStatesPackage PRESENT IF the administrativeState and operationalState attributes are supported,
ACOM:alarmStatusPackage PRESENT IF the alarmStatus attribute is supported,
X.721:availabilityStatusPackage PRESENT IF the availabilityStatus attribute is supported,
ACOM:clientNodeIdentifierPackage PRESENT IF the clientNodeIdentifier attribute is supported,
ACOM:controlStatusPackage PRESENT IF the controlStatus attribute is supported,
M.3100:currentProblemListPackage PRESENT IF the currentProblemList attribute is supported,
GSM 12.20:functionalRelatedAlarmPackage PRESENT IF an instance supports it,
M.3100:stateChangeNotificationPackage PRESENT IF the stateChange notification is supported,
ACOM:unknownStatusPackage PRESENT IF the unknownStatus attribute is supported;
REGISTERED AS { anoiManagedObjectClass 10 };
2.1.6 anoiCircuitPack
anoiCircuitPack MANAGED OBJECT CLASS -- based on M.3100:circuitPack
DERIVED FROM M.3100:equipmentR1;
CHARACTERIZED BY M.3100:administrativeOperationalStatesPackage,
-- M.3100:alarmSeverityAssignmentPointerPackage, M.3100:circuitPackPackage, M.3100:createDeleteNotificationsPackage, M.3100:currentProblemListPackage,
-- M.3100:equipmentsEquipmentAlarmR1Package, -- M.3100:equipmentAlarmEffectOnServicePackage,
M.3100:stateChangeNotificationPackage;
CONDITIONAL PACKAGES
ACOM:controlStatusPackage PRESENT IF the controlStatus attribute is supported,
ACOM:qualityofServiceAlarmPackage PRESENT IF
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 20/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
the qualityofServiceAlarm notification (as defined in CCITT X.721) is supported by this managed object;
REGISTERED AS { anoiManagedObjectClass 4030 };
2.1.7 anoiCoreManagedElement
anoiCoreManagedElement MANAGED OBJECT CLASS
DERIVED FROM anoiManagedElement;
CHARACTERIZED BY anoiCoreManagedElementPackage;
REGISTERED AS { anoiManagedObjectClass 13 };
2.1.8 anoiEquipmentR1
anoiEquipmentR1 MANAGED OBJECT CLASS
DERIVED FROM M.3100:equipmentR1;
CONDITIONAL PACKAGES
X.721:availabilityStatusPackage PRESENT IF the availabilityStatus attribute is supported,
ACOM:controlStatusPackage PRESENT IF the controlStatus attribute is supported,
ACOM:qualityofServiceAlarmPackage PRESENT IF the qualityofServiceAlarm notification (as defined in CCITT X.721) is supported by this managed object,
ACOM:unknownStatusPackage PRESENT IF the unknownStatus attribute is supported;
REGISTERED AS { anoiManagedObjectClass 15 };
2.1.9 anoiGPRSManagedElement
anoiGPRSManagedElement MANAGED OBJECT CLASS
DERIVED FROM anoiManagedElement;
CHARACTERIZED BY anoiGPRSManagedElementPackage;
CONDITIONAL PACKAGES
ACOM:clientNodeIdentifierPackage PRESENT IF the clientNodeIdentifier attribute is supported,
ACOM:qualityofServiceAlarmPackage PRESENT IF the qualityofServiceAlarm notification (as defined in CCITT X.721) is supported by this managed object;
REGISTERED AS { anoiManagedObjectClass 17 };
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 21/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
anoiSNMPManagedElement MANAGED OBJECT CLASS
DERIVED FROM anoiManagedElement;
CHARACTERIZED BY anoiSNMPManagedElementPackage;
CONDITIONAL PACKAGES
"ACOM":qualityofServiceAlarmPackage PRESENT IF "an instance supports it",
REGISTERED AS { anoiManagedObjectClass 18 };
2.1.10 anoiFunctionCoordinator
anoiFunctionCoordinator MANAGED OBJECT CLASS
DERIVED FROM X.721:top;
CHARACTERIZED BY anoiFunctionCoordinatorPackage;
REGISTERED AS { anoiManagedObjectClass 110};
2.1.11 anoiFunction
anoiFunction MANAGED OBJECT CLASS
DERIVED FROM X.721:top;
CHARACTERIZED BY anoiFunctionPackage;
REGISTERED AS { anoiManagedObjectClass 120};
2.1.12 anoiLapdLink
anoiLapdLink MANAGED OBJECT CLASS -- based on GSM 12.20:lapdLink
DERIVED FROM GSM 12.20:gsmManagedFunction;
CHARACTERIZED BY anoiLapdLinkPackage, GSM 12.20:functionalRelatedAlarmPackage, M.3100:stateChangeNotificationPackage;
CONDITIONAL PACKAGES
M.3100:currentProblemListPackage PRESENT IF the currentProblemList attribute is supported,
ACOM:relatedGSMEquipmentPackage PRESENT IF the relatedGSMEquipment attribute is supported;
REGISTERED AS { anoiManagedObjectClass 1130 };
2.1.13 anoiManagedElement
anoiManagedElement MANAGED OBJECT CLASS
DERIVED FROM M.3100:managedElement;
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 22/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
CONDITIONAL PACKAGES
acknowledgeAlarmsPackage PRESENT IF acknowledgeAlarms is supported by this managed object,
ACOM:proceduralStatusPackage PRESENT IF the proceduralStatus attribute is supported,
retrieveCurrentAlarmsDataPackage PRESENT IF the retrieveCurrentAlarmsData action is supported,
ACOM:unknownStatusPackage PRESENT IF the unknownStatus attribute is supported;
REGISTERED AS { anoiManagedObjectClass 20 };
2.1.14 anoiPlmnNetwork
anoiPlmnNetwork MANAGED OBJECT CLASS -- based on GSM 12.00:plmnNetwork
DERIVED FROM M.3100:network;
CHARACTERIZED BY anoiPlmnNetworkPackage;
CONDITIONAL PACKAGES
ACOM:a1353RAInstanceNamePackage PRESENT IF the a1353RAInstanceName is supported by this managed object,
associationSurveyNotificationPackage PRESENT IF the associationSurvey notification is supported by this managed object,
M.3100:attributeValueChangeNotificationPackage PRESENT IF the attributeValueChange notification (as defined in CCITT X.721) is supported by this managed object,
M.3100:createDeleteNotificationsPackage PRESENT IF the objectCreation and objectDeletion notifications (as defined in CCITT X.721) are supported by this managed object,
M.3100:externalTimePackage PRESENT IF the externalTime attribute is supported by this managed object,
ACOM:proceduralStatusPackage PRESENT IF the proceduralStatus attribute (as defined in CCITT X.721) is supported by this managed object,
M.3100:stateChangeNotificationPackage PRESENT IF the stateChange notification (as defined in CCITT X.721) is supported by this managed object,
ACOM:typeOfFileTransferPackage PRESENT IF the typeOfFileTransfer attribute is supported by this managed object,
ACOM:unknownStatusPackage PRESENT IF the unknownStatus attribute (as defined in CCITT X.721) is supported by this managed object;
REGISTERED AS { anoiManagedObjectClass 2060 };
2.1.15 anoiSignLinkSetTp
anoiSignLinkSetTp MANAGED OBJECT CLASS -- based on Q.751.1:signLinkSetTp
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 23/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
DERIVED FROM X.721:top;
CHARACTERIZED BY anoiSignLinkSetTpPackage;
CONDITIONAL PACKAGES
Q.751.1:administrativeStatePackage PRESENT IF an instance supports it,
-- M.3100:alarmSeverityAssignmentPointerPackage PRESENT IF -- an instance supports it and the communicationsAlarmPackage is present,
ACOM:alarmStatusPackage PRESENT IF the alarmStatus attribute is supported by an instance of this class ,
M.3100:attributeValueChangeNotificationPackage PRESENT IF the attributeValueChangeNotification defined in ITU-T Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992 is supported by an instance of this class,
-- Q.751.1:communicationsAlarmPackage PRESENT IF -- an instance supports it,
M.3100:createDeleteNotificationsPackage PRESENT IF the objectCreation and objectDeletion notifications defined in ITU-T Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992 are supported by an instance of this class,
M.3100:currentProblemListPackage PRESENT IF the currentProblemList attribute is supported,
-- Q.751.1:inLsLoadShareAlgorithmPackage PRESENT IF -- an instance supports it,
-- Q.751.1:lsTimersProfilePointerPackage PRESENT IF -- the instance of superior class mtpSignPoint does not support the conditional -- spTimersPackage,
-- Q.751.1:noBasicLinkAllocationPackage PRESENT IF -- Basic link allocation is not done,
ACOM:qualityofServiceAlarmPackage PRESENT IF the qualityofServiceAlarm notification is supported by an instance of this class ;
-- Q.751.1:signLinkSetTpNamePackage PRESENT IF -- an instance supports it;
REGISTERED AS { anoiManagedObjectClass 3008 };
2.1.16 anoiSignLinkTp
anoiSignLinkTp MANAGED OBJECT CLASS -- based on Q.751.1:signLinkTp
DERIVED FROM X.721:top;
CHARACTERIZED BY anoiSignLinkTpPackage;
CONDITIONAL PACKAGES
-- M.3100:alarmSeverityAssignmentPointerPackage PRESENT IF -- an instance supports it and the (communicationsAlarmPackage or -- ss7OnOccEventPackage) is present,
ACOM:alarmStatusPackage PRESENT IF
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 24/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
the alarmStatus attribute is supported,
M.3100:attributeValueChangeNotificationPackage PRESENT IF the attributeValueChangeNotification defined in ITU-T Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992 is supported by an instance of this class,
X.721:availabilityStatusPackage PRESENT IF the availabilityStatus attribute is supported,
Q.751.1:communicationsAlarmPackage PRESENT IF an instance supports it,
ACOM:controlStatusPackage PRESENT IF the controlStatus attribute is supported,
M.3100:createDeleteNotificationsPackage PRESENT IF the objectCreation and objectDeletion notifications defined in ITU-T Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992 are supported by an instance of this class,
M.3100:currentProblemListPackage PRESENT IF the currentProblemList attribute is supported,
M.3100:equipmentAlarmEffectOnServicePackage PRESENT IF the equipmentAlarm is supported,
-- Q.751.1:linkCongestionLevelPackage PRESENT IF -- the exchange support the operation, management and administration of -- multiple transmission congestion levels (national option),
ACOM:qualityofServiceAlarmPackage PRESENT IF the qualityofServiceAlarm notification is supported,
-- Q.751.1:relatedLinkGroupNumberPackage PRESENT IF -- an instance supports it,
-- Q.751.1:signDataLinkTpListPackage PRESENT IF -- an instance supports it,
-- Q.751.1:signLinkTestPackage PRESENT IF -- the on-demand signalling link test as described in Q.707 is supported,
-- Q.751.1:signLinkTpNamePackage PRESENT IF -- an instance supports it,
-- Q.751.1:signTermListPackage PRESENT IF -- an instance supports it or an instance supports the -- signDataLinkTpListPackage,
-- Q.751.1:slsCodeNormalListPackage PRESENT IF -- an instance supports it,
-- Q.751.1:slTimersProfilePointerPackage PRESENT IF -- the instance of superior class mtpSignPoint does not support the conditional -- spTimersPackage,
-- Q.751.1:ss7OnOccEventPackage PRESENT IF -- an instance supports it;
ACOM:supportedByObjectListPackage PRESENT IF the supportedByObjectList attribute is supported,
M.3100:userLabelPackage PRESENT IF the userLabel attribute is supported;
REGISTERED AS { anoiManagedObjectClass 3009 };
2.1.17 anoiTerminationPointBidirectional
anoiTerminationPointBidirectional MANAGED OBJECT CLASS
DERIVED FROM M.3100:terminationPoint;
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 25/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
CHARACTERIZED BY M.3100:operationalStatePackage, anoiTerminationPointBidirectionalPackage;
CONDITIONAL PACKAGES
X.721:administrativeStatePackage PRESENT IF the resource represented by the managed object is capable of being administratively placed in and out of service,
X.721:availabilityStatusPackage PRESENT IF the availabilityStatus attribute is supported,
ACOM:controlStatusPackage PRESENT IF the controlStatus attribute is supported,
M.3100:equipmentAlarmEffectOnServicePackage PRESENT IF the equipmentAlarm is supported,
M.3100:processingErrorAlarmPackage PRESENT IF the processingErrorAlarm notification is supported,
ACOM:qualityofServiceAlarmPackage PRESENT IF the qualityofServiceAlarm notification is supported,
-- supportableClientListPackage PRESENT IF -- the object class can support more than one type of client,
M.3100:userLabelPackage PRESENT IF the userLabel attribute is supported;
REGISTERED AS { anoiManagedObjectClass 30 };
2.1.18 associationSurveyRecord
associationSurveyRecord MANAGED OBJECT CLASS
DERIVED FROM X.721:eventLogRecord; -- The appropriate object identifier value for the eventType attribute, inherited -- from the eventLogRecord managed object class, is associationSurvey.
CHARACTERIZED BY associationSurveyRecordPackage;
REGISTERED AS {anoiManagedObjectClass 40};
2.2 PACKAGE DEFINITIONS
2.2.1 acknowledgeAlarmsPackage
acknowledgeAlarmsPackage PACKAGE
ACTIONS acknowledgeAlarms;
REGISTERED AS { anoiPackage 5 };
2.2.2 anoiBasebandTransceiverPackage
anoiBasebandTransceiverPackage PACKAGE BEHAVIOUR anoiBasebandTransceiverBehaviour;
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 26/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
ATTRIBUTES GSM 12.20:basebandTransceiverID GET;
REGISTERED AS { anoiPackage 100 }; anoiBasebandTransceiverBehaviour BEHAVIOUR
DEFINED AS
A anoiBasebandTransceiver MOI only serves to represent a
corresponding internal alcatelBasebandTransceiver MOI within
an element of the additionalInformation field corresponding
to the internalNEAlarmMOIIndication parameter for an alarm
emitted by the anoiBts MOI corresponding to the internal
parent(alcatelBts-Sector) MOI.;
2.2.3 anoiBscBasicPackage
anoiBscBasicPackage PACKAGE -- based on GSM 12.20:bscBasicPackage
BEHAVIOUR anoiBscBasicBehaviour;
ATTRIBUTES GSM 12.20:bscID GET,
-- GSM 12.20:handoverReqParam GET-REPLACE, GSM 12.20:relatedGSMEquipment GET,
-- instead of GET-REPLACE X.721:administrativeState GET,
-- instead of GET-REPLACE -- standard1220SpecificErrorInfo,
X.721:controlStatus GET, -- instead of GET-REPLACE -- standard1220SpecificErrorInfo,
M.3100:alarmStatus GET, -- standard1220SpecificErrorInfo,
X.721:operationalState GET, -- standard1220SpecificErrorInfo,
X.721:availabilityStatus GET, -- standard1220SpecificErrorInfo,
X.721:unknownStatus GET, -- standard1220SpecificErrorInfo,
X.721:usageState GET; -- standard1220SpecificErrorInfo;
REGISTERED AS { anoiPackage 1060};
anoiBscBasicBehaviour BEHAVIOUR -- based on GSM 12.20:bscBasicBehaviour
DEFINED AS The bsc MOC is a managed object representing the network component Base Station Controller (BSC) functions of the BSS. An instance of the MOC bsc is identified by the bscID attribute. This package provides the basic attributes for identification and configuration.
-- A CMIP Create command must include all attributes except for the state attributes.
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 27/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Upon creation of this object, the value of the administrative state will be locked. The locked administrative state stops normal operations of the resource (not, for example, operations for test purposes). The attributeList field of the objectCreation notification shall contain all attributes of the created instance. The attributeList field of the objectDeletion notification shall be NULL. The behaviour of the object on Delete will be as if the state were first set to locked.
-- A CMIP Delete command for an instance of this MOC may be refused by an agent -- if the agent requires the manager to take some action such as the explicit removal -- of the instance from some relationship or the locking of the instance. Any such -- error will be indicated by the appropriate GSM 12.20 defined error code being -- returned. Other generally applicable Delete errors also apply. If the agent accepts -- a Delete command and relationships exist, the agent is responsible for adjusting -- the appropriate attributes and reporting such changes to the management system.
-- An attribute Set command may be refused by an agent if the agent requires the -- manager to lock the object prior to changing the attribute value. Any such error will -- be indicated by the appropriate GSM 12.20 defined error code being returned. -- Other generally applicable Set errors also apply.
Attributes that are subject to the attributeValueChange notification are: all except administrativeState, alarmStatus, operationalState.
-- and usageState. Attributes that are subject to the stateChange notification are
administrativeState, operationalState. -- and usageState. All values of the
administrative, operational -- and usage states are supported. The availabilityStatus qualifies in more details the operationalState while the controlStatus provides information to support the test management.
-- The M-SET command changing the administrative state shall not change any -- other attributes.
;
2.2.4 anoiBtsBasicPackage
anoiBtsBasicPackage PACKAGE -- based on GSM 12.20:btsBasicPackage
BEHAVIOUR anoiBtsBasicBehaviour;
ATTRIBUTES -- GSM 12.20:bsIdentityCode GET-REPLACE,
GSM 12.20:btsID GET, -- GSM 12.20:cellAllocation GET-REPLACE, -- GSM 12.20:gsmdcsIndicator GET-REPLACE,
GSM 12.20:cellGlobalIdentity GET, -- instead of GET-REPLACE
-- GSM 12.20:cellReselectHysteresis GET-REPLACE, -- GSM 12.20:ny1 GET-REPLACE,
GSM 12.20:relatedGSMEquipment GET,
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 28/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
-- instead of GET-REPLACE -- GSM 12.20:periodCCCHLoadIndication GET-REPLACE, -- GSM 12.20:plmnPermitted GET-REPLACE, -- GSM 12.20:rACHBusyThreshold GET-REPLACE, -- GSM 12.20:rACHLoadAveragingSlots GET-REPLACE, -- GSM 12.20:radioLinkTimeout GET-REPLACE,
GSM 12.20:relatedOAMLapdLink GET-REPLACE, -- GSM 12.20:relatedTranscoder GET-REPLACE, -- GSM 12.20:rxLevAccessMin GET-REPLACE, -- GSM 12.20:thresholdCCCHLoadIndication GET-REPLACE,
X.721:administrativeState GET, -- instead of GET-REPLACE -- standard1220SpecificErrorInfo,
X.721:controlStatus GET, -- instead of GET-REPLACE -- standard1220SpecificErrorInfo,
M.3100:alarmStatus GET, -- standard1220SpecificErrorInfo,
X.721:operationalState GET, -- standard1220SpecificErrorInfo,
X.721:availabilityStatus GET, -- standard1220SpecificErrorInfo,
X.721:unknownStatus GET, -- standard1220SpecificErrorInfo,
X.721:usageState GET; -- standard1220SpecificErrorInfo;
-- ACTIONS -- forcedHO;
REGISTERED AS { anoiPackage 1080};
anoiBtsBasicBehaviour BEHAVIOUR -- based on GSM 12.20:btsBasicBehaviour
DEFINED AS The bts MOC represents the GSM functional element Base Transceiver Station. An instance of this MOC is associated by containment with a particular bssFunction instance and a particular btsSiteManager instance. Multiple instances of this MOC may be contained within a btsSiteManager instance. The attributes within the package btsBasicPackage describe the basic properties of a BTS that are not related to the Common Control Channels.
-- The attributes bsIdentityCode and cellGlobalIdentity can be modified by the M-SET command only when the administrative state of the bts is locked.
-- A CMIP Create command must include all attributes except for the state attributes. -- Upon creation of this object, the value of the administrative state will be locked.
The attributeList field of the objectCreation notification shall contain all attributes of the created instance. The attributeList field of the objectDeletion notification shall be NULL.
-- The behaviour of the object on Delete will be as if the state were first set to locked. -- A CMIP Delete command for an instance of this object may be refused by an -- agent if the agent requires the manager to take some action such as the explicit
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal Specification
ED 02 Released
9707m21r.doc 09/04/2010
3BK 09707 MAAA PBZZA 29/173
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
-- removal of the instance from some relationship or the locking of the instance. Any -- such error will be indicated by the appropriate GSM 12.20 defined error code being -- returned. Other generally applicable Delete errors also apply. If the agent accepts -- a Delete command and relationships exist, the agent is responsible for adjusting -- the appropriate attributes and reporting such changes to the management system.
-- An attribute Set command may be refused by an agent if the agent requires the -- manager to lock the object prior to changing the attribute value. Any such error will -- be indicated by the appropriate GSM 12.20 defined error code being returned. -- Other generally applicable Set errors also apply.
Attributes that are subject to the attributeValueChange notification are: all except administrativeState, controlStatus, alarmStatus, operationalState, availabilityStatus
-- and usageState. Attributes that are subject to the stateChange notification are
administrativeState, operationalState, availabilityStatus -- and usageState. All values of the
administrative, operational, -- and usage states are supported. The availabilityStatus qualifies in more details the operationalState while the controlStatus provides information to support the test management. The M-SET command changing the administrative state shall not change any other attributes.
The administrative states for the BTS have the following meanings: In the shutting down state, no new traffic is allowed through the BTS. In this state, the BTS is barred (message sent to MS) and no incoming handovers are allowed. If all traffic is cleared, the BTS changes to the locked state. In the locked state, all calls through the BTS are disconnected. The BSC should clear all calls with cause set to O and M intervention. No new traffic is possible on the BTS and no incoming handovers are allowed. In the unlocked state, new traffic is allowed through the BTS and incoming handovers are allowed. The locked administrative state stops normal operations of the resource (not, for example, operations for test p