WRAN CM Managed Object Model

WRAN CM Managed Object Model
1/15554-4/AOM 901 046 Uen rev. F1
Generated from model:

/vobs/wran_cm/wran_cm_mom/rosemodel/RanosNode.mdl
ClearCase label:
D5-WRANMOM_ROSEMODEL_R6_RANOS_INC1.3_KI
May 16th, 2008
17:56:26
Prepared: LMI/RO/SD John Heavey

Approved: LMI/RO (Jimmy O’Meara)
© Ericsson AB 2008 - All Rights Reserved
No part of this document may be reproduced in any form without the written
permission of the copyright owner.
The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing.
Ericsson shall have no liability for any error or damage of any kind resulting from
the use of this document.
LOGICAL VIEW REPORT
TABLE OF CONTENTS
LOGICAL VIEW REPORT.......................................................................................................................11

INTRODUCTION ..........................................................................................................................................11
ABSTRACT .................................................................................................................................................11
REVISION HISTORY ....................................................................................................................................11
PURPOSE ....................................................................................................................................................13
DECISIONS .................................................................................................................................................13
OPEN ISSUES ..............................................................................................................................................14
ASSUMPTIONS ............................................................................................................................................14
DOCUMENT OVERVIEW..............................................................................................................................15
LOGICAL VIEW ..........................................................................................................................................15
RANOS NODE MODEL ................................................................................................................................16
RN APPLICATION MODEL MAIN VIEW ......................................................................................................16
SUPPORT APPLICATION MODEL MAIN VIEW .............................................................................................17
PLANNED CONFIGURATION APPLICATION MODEL MAIN VIEW ................................................................17
SUBNETWORK MODEL MAIN VIEW............................................................................................................18
SUBNETWORK MODEL IRP VIEW...............................................................................................................18
SUBNETWORK MODEL SITE VIEW..............................................................................................................19
SUBNETWORK MODEL AREAS VIEW ..........................................................................................................19
SUBNETWORK MODEL EXTERNAL NODE VIEW .........................................................................................20
SUBNETWORK MODEL TN APPLICATION VIEW .........................................................................................20
RANAG MIRROR MODEL MAIN VIEW ........................................................................................................21
RBS MIRROR MODEL MAIN VIEW .............................................................................................................22
RNC MIRROR MODEL MAIN VIEW .............................................................................................................22
RANOS_INTERMIM_MODEL...............................................................................................................22
SUBNETWORK-APPLICATIONS .........................................................................................................23
SUBNETWORK RBS_MIRROR .............................................................................................................24
SUBNETWORK RNC_MIRROR ............................................................................................................25
SUBNETWORK-RANAG_MIRROR......................................................................................................26
MANAGED OBJECT TYPES..........................................................................................................................27
GENERAL ...................................................................................................................................................27
GENERAL OPERATIONS ..............................................................................................................................27
GENERAL ATTRIBUTES ..............................................................................................................................28
ALARMS .....................................................................................................................................................28
GENERAL NOTIFICATIONS..........................................................................................................................29
GENERAL EXCEPTIONS ..............................................................................................................................30
GENERAL NAMING RULES .........................................................................................................................30
RANOS_APPLICATION_MODEL.........................................................................................................31
RANOS_RN_APPLICATION_MODEL .................................................................................................31
EulProfile..............................................................................................................................................31
FACHPROFILE ............................................................................................................................................33
HSDSCHPROFILE ........................................................................................................................................35
MBMSCCHPROFILE ....................................................................................................................................35
PCHPROFILE...............................................................................................................................................43
RACHPROFILE ............................................................................................................................................44
RNAPPLICATION ........................................................................................................................................46
RnApplication .......................................................................................................................................46
USERDEFENTITYLIST ................................................................................................................................46
UserDefEntityList .................................................................................................................................46
UTRANCELLPROFILE .................................................................................................................................46
DATA TYPES, DEFINITIONS AND EXCEPTIONS............................................................................................64
SupportedMeasQuantities.....................................................................................................................64
Page 2
LOGICAL VIEW REPORT
SupportedReservedStates......................................................................................................................64
RANOS_SUPPORT_APPLICATION_MODEL......................................................................................64
LOGFILTER ................................................................................................................................................64
LogFilter...............................................................................................................................................64
SUPPORTAPPLICATION ...............................................................................................................................65
SupportApplication ...............................................................................................................................65
USERPREFERENCES ....................................................................................................................................65
UserPreferences ...................................................................................................................................65
PLANNEDCONFIG_APPLICATION_MODEL .....................................................................................64
BREAKPOINT .............................................................................................................................................64
BreakPoint ............................................................................................................................................64
PLANNEDAREAPROPERTIES .......................................................................................................................65
PlannedAreaProperties ........................................................................................................................65
PLANNEDCONFIGAPP ................................................................................................................................65
PlannedConfigApp................................................................................................................................65
ActivationInformation...........................................................................................................................98
ActivationScheme..................................................................................................................................98
LastCommit...........................................................................................................................................98
RANOS_SUBNETWORK_MODEL .......................................................................................................69
ALARMIRP ................................................................................................................................................70
AlarmIRP ..............................................................................................................................................70
AREAS .......................................................................................................................................................70
Areas.....................................................................................................................................................70
ATMLINK ...................................................................................................................................................71
AtmLink.................................................................................................................................................71
BULKCMIRP..............................................................................................................................................72
BulkCmIRP ...........................................................................................................................................72
EXTERNALGSMCELL .................................................................................................................................72
ExternalGsmCell ..................................................................................................................................72
EXTERNALGSMPLMN ................................................................................................................................74
ExternalGsmPlmn.................................................................................................................................74
EXTERNALTRANSPORTNETWORK ..............................................................................................................76
ExternalTransportNetwork ...................................................................................................................76
EXTERNALUTRANCELL .............................................................................................................................77
ExternalUtranCell ................................................................................................................................77
EXTERNALUTRANPLMN ............................................................................................................................81
ExternalUtranPlmn...............................................................................................................................81
EXTERNALVIEWABLENODE .......................................................................................................................83
ExternalViewableNode .........................................................................................................................83
ExternalTransportNetwork ...................................................................................................................83
ExternalVplTp.......................................................................................................................................83
IRATHOMUTRAN ..................................................................................................................................83
IRATHOMUTRAN ................................................................................................................................83
MimInfo ................................................................................................................................................84
IRPAGENT .................................................................................................................................................84
IRPAgent...............................................................................................................................................84
LINK ..........................................................................................................................................................85
Link .......................................................................................................................................................85
LOCATIONAREA.........................................................................................................................................85
LocationArea ........................................................................................................................................85
MANAGEMENTNODE .................................................................................................................................86
ManagementNode .................................................................................................................................86
MBMSSERVICEAREA ...........................................................................................................................86
MbmsServiceArea .................................................................................................................................86
NOTIFICATIONIRP .....................................................................................................................................88
Page 3
LOGICAL VIEW REPORT
NotificationIRP .....................................................................................................................................88
PLMN .........................................................................................................................................................88
Plmn......................................................................................................................................................88
PMIRP .......................................................................................................................................................89
PmIRP...................................................................................................................................................89
RBSGROUP.................................................................................................................................................90
RbsGroup..............................................................................................................................................90
ROUTINGAREA ..........................................................................................................................................90
RoutingArea..........................................................................................................................................90
SEGMENT ...................................................................................................................................................91
Segment.................................................................................................................................................91
SERVICEAREA............................................................................................................................................93
ServiceArea...........................................................................................................................................93
SITE ...........................................................................................................................................................94
Site ........................................................................................................................................................94
SUBNETWORK ...........................................................................................................................................96
SubNetwork...........................................................................................................................................96
TNAPPLICATION ........................................................................................................................................97
TnApplication .......................................................................................................................................97
VirtualPath ...........................................................................................................................................97
SupportedAtmLinkTypes .......................................................................................................................98
SupportedAtt .........................................................................................................................................98
SupportedNetOpModes.........................................................................................................................98
SupportedBands....................................................................................................................................98
PlmnIdentity..........................................................................................................................................98
SupportedServiceCategory ...................................................................................................................99
CELLO MODEL.......................................................................................................................................99
BASIC CELLO MODEL ................................................................................................................................99
BASICMANAGEDELEMENT ........................................................................................................................99
BasicManagedElement .........................................................................................................................99
CELLO ATTRIBUTES MIRRORED IN WRAN CM .......................................................................................103
Aal0TpVccTp ......................................................................................................................................103
Aal1TpVccTp ......................................................................................................................................103
Aal2Ap ................................................................................................................................................104
Aal2PathDistributionUnit...................................................................................................................104
Aal2PathVccTp ...................................................................................................................................104
Aal2QoSCodePointProfile..................................................................................................................105
Aal2QoSProfile...................................................................................................................................105
Aal2RoutingCase ................................................................................................................................105
Aal2Sp.................................................................................................................................................105
Aal5TpVccTp ......................................................................................................................................105
AtmConfService ..................................................................................................................................106
AtmCrossConnection ..........................................................................................................................106
AtmPort...............................................................................................................................................106
AtmTrafficDescriptor..........................................................................................................................106
Cbu .....................................................................................................................................................107
ConfigurationVersion .........................................................................................................................107
Dhcp ....................................................................................................... Error! Bookmark not defined.
Ds0Bundle ..........................................................................................................................................107
E1PhysPathTerm ................................................................................................................................107
E1Ttp ..................................................................................................................................................108
E3PhysPathTerm ................................................................................................................................108
Equipment...........................................................................................................................................108
EthernetLink .......................................................................................................................................108
EthernetSwitch........................................................................................ Error! Bookmark not defined.
Page 4
LOGICAL VIEW REPORT
EthernetSwitchPort................................................................................. Error! Bookmark not defined.

EtMfg ..................................................................................................................................................110
Etm1....................................................................................................................................................110
ExchangeTerminal..............................................................................................................................110
ExchangeTerminalIp............................................................................... Error! Bookmark not defined.
FastEthernet .......................................................................................................................................110
GeneralProcessorUnit........................................................................................................................110
GigaBitEthernet...................................................................................... Error! Bookmark not defined.
ImaGroup............................................................................................................................................111
ImaLink...............................................................................................................................................112
InternalEthernetPort............................................................................... Error! Bookmark not defined.
Ip.........................................................................................................................................................112
IpAccessAutoConfig............................................................................................................................112
IpAccessHostEt ...................................................................................................................................112
IpAccessHostGpb................................................................................................................................113
IpAccessHostSpb.................................................................................................................................113
IpAtmLink ...........................................................................................................................................114
IpInterface ..........................................................................................................................................114
IpOam .................................................................................................................................................114
IpRoutingTable ...................................................................................................................................115
IpSystem..............................................................................................................................................115
J1PhysPathTerm.................................................................................................................................115
Licensing.............................................................................................................................................115
M3uAssociation ..................................................................................................................................116
ManagedElement ................................................................................................................................116
ManagedElementData ........................................................................................................................118
MediumAccessUnit .............................................................................................................................118
Mspg ...................................................................................................................................................118
Mtp3bAp .............................................................................................................................................119
Mtp3bSlAnsi........................................................................................................................................119
Mtp3bSlChina.....................................................................................................................................119
Mtp3bSlItu ..........................................................................................................................................120
Mtp3bSls .............................................................................................................................................120
Mtp3bSlTtc..........................................................................................................................................120
Mtp3bSpAnsi.......................................................................................................................................120
Mtp3bSpChina ....................................................................................................................................121
Mtp3bSpItu .........................................................................................................................................121
Mtp3bSpTtc.........................................................................................................................................122
Mtp3bSr ..............................................................................................................................................122
Mtp3bSrs.............................................................................................................................................123
NniSaalProfile ....................................................................................................................................123
NniSaalTp ...........................................................................................................................................123
Os155PhysPathTerm ..........................................................................................................................123
Os155SpiTtp .......................................................................................................................................123
Ospf.....................................................................................................................................................123
OspfArea.............................................................................................................................................124
OspfInterface ......................................................................................................................................124
PlugInUnit ..........................................................................................................................................124
PmService ...........................................................................................................................................124
ReliableProgramUniter ......................................................................................................................125
SccLayer .............................................................................................................................................125
SccpAccountingCriteria......................................................................................................................125
SccpAp ................................................................................................................................................125
SccpApLocal .......................................................................................................................................125
SccpApRemote ....................................................................................................................................126
SccpEntitySet ......................................................................................................................................126
Page 5
LOGICAL VIEW REPORT
SccpGlobalTitle ..................................................................................................................................126
SccpPolicing .......................................................................................................................................126
SccpScrc..............................................................................................................................................127
SccpSp.................................................................................................................................................127
Sctp .....................................................................................................................................................127
Slot......................................................................................................................................................128
Sts1SpeTtp ..........................................................................................................................................128
Sts3CspeTtp ........................................................................................................................................128
Subrack ...............................................................................................................................................129
SwitchPortStp .....................................................................................................................................129
SwitchStp ............................................................................................................................................129
SwManagement...................................................................................................................................130
Synchronization ..................................................................................................................................130
SystemFunctions .................................................................................................................................130
T1PhysPathTerm ................................................................................................................................130
T1Ttp...................................................................................................................................................130
T3PhysPathTerm ................................................................................................................................130
TransportNetwork...............................................................................................................................131
UniSaalProfile ....................................................................................................................................131
UniSaalTp...........................................................................................................................................131
UpgradePackage ................................................................................................................................131
Vc12Ttp...............................................................................................................................................132
Vc4Ttp.................................................................................................................................................132
VclTp...................................................................................................................................................132
VpcTp..................................................................................................................................................132
VplTp ..................................................................................................................................................133
Vt15Ttp ...............................................................................................................................................133
CELLO MOS NEEDED FOR SYNCH ............................................................................................................133
Jvm......................................................................................................................................................133
MIRRORED MIMS.................................................................................................................................133
MIRRORED MIM NAME AND VERSION HANDLING ...................................................................................134
RANOS_ERBS_MIRROR_MODEL_H.................................................................................................145
MeContext...........................................................................................................................................145
RANOS_RANAG_MIRROR_MODEL_H ............................................................................................145
MeContext...........................................................................................................................................145
RANAG CELLO MOC'S CONTAINING WRAN CM LOCAL ATTRIBUTES.....................................................149
Aal0TpVccTp ......................................................................................................................................149
Aal2PathVccTp ...................................................................................................................................150
Aal5TpVccTp ......................................................................................................................................150
AtmPort...............................................................................................................................................150
ManagedElement ................................................................................................................................150
VclTp...................................................................................................................................................152
VpcTp..................................................................................................................................................152
VplTp ..................................................................................................................................................152
REFERENCES TO MOS IN THE RANAG EQUIPMENT VIEW .......................................................................152
RANOS_RBS_MIRROR_MODEL_H ...................................................................................................153
NodeBFunction ...................................................................................................................................153
MECONTEXT ............................................................................................................................................156
MeContext...........................................................................................................................................156
RBS CELLO MOC'S CONTAINING WRAN CM LOCAL ATTRIBUTES ..........................................................161
Aal0TpVccTp ......................................................................................................................................161
Aal2PathVccTp ...................................................................................................................................161
Aal5TpVccTp ......................................................................................................................................161
Page 6
LOGICAL VIEW REPORT
AtmPort...............................................................................................................................................161
ManagedElement ................................................................................................................................162
VclTp...................................................................................................................................................164
VpcTp..................................................................................................................................................164
VplTp ..................................................................................................................................................164
RBS ATTRIBUTES MIRRORED IN WRAN CM...........................................................................................164
AntennaBranch ...................................................................................................................................164
AntFeederCable..................................................................................................................................165
AuxPlugInUnit ....................................................................................................................................165
Carrier ................................................................................................................................................165
DbccDevice............................................................................................. Error! Bookmark not defined.
DbccDeviceSet........................................................................................ Error! Bookmark not defined.
Equipment............................................................................................... Error! Bookmark not defined.
ExternalTma ........................................................................................... Error! Bookmark not defined.
Iub........................................................................................................... Error! Bookmark not defined.
IubDataStreams ...................................................................................... Error! Bookmark not defined.
NbapCommon ......................................................................................... Error! Bookmark not defined.
NbapDedicated ....................................................................................... Error! Bookmark not defined.
NodeSynchTp .......................................................................................... Error! Bookmark not defined.
PlugInUnit .............................................................................................. Error! Bookmark not defined.
RbsLocalCell .......................................................................................... Error! Bookmark not defined.
RetDevice................................................................................................ Error! Bookmark not defined.
RetDeviceSet.......................................................................................................................................173
RetuDeviceGroup ...............................................................................................................................173
Sector..................................................................................................................................................174
SectorAntenna.....................................................................................................................................174
Slot......................................................................................................................................................175
Subrack ...............................................................................................................................................175
TimDevice...........................................................................................................................................175
TimDeviceSet ......................................................................................................................................175
TuDeviceGroup...................................................................................................................................175
TxDeviceGroup...................................................................................................................................175
REFERENCES TO MOS IN THE RBS EQUIPMENT VIEW .............................................................................176
STANDARDRBS .......................................................................................................................................176
RBS3104 .................................................................................................................................................177
RBS 3107, 3206M, 3018, 3418 AND 3518 ...............................................................................................178
RBS BASE MODEL ...................................................................................................................................178
RBS MOS NEEDED FOR SYNCH.................................................................................................................179
CuSubrack ..........................................................................................................................................179
McpaSubrack ......................................................................................................................................179
PowerSupplySubrack..........................................................................................................................179
PowerSupplySystem............................................................................................................................179
RbsSlot................................................................................................................................................180
RbsSynchronization ............................................................................................................................180
RANOS_RNC_MIRROR_MODEL_H ..................................................................................................180
ExternalGsmCell ................................................................................................................................180
ExternalGsmNetwork..........................................................................................................................181
ExternalUtranCell ..............................................................................................................................182
IubLink................................................................................................................................................183
IurLink ................................................................................................................................................185
RncFunction........................................................................................................................................186
UtranCell ............................................................................................................................................189
GSMRELATION.........................................................................................................................................196
GsmRelation .......................................................................................................................................196
MECONTEXT ............................................................................................................................................197
Page 7
LOGICAL VIEW REPORT
MeContext...........................................................................................................................................197
UTRANRELATION.....................................................................................................................................201
UtranRelation .....................................................................................................................................201
RNC CELLO MOC'S CONTAINING WRAN CM LOCAL ATTRIBUTES .........................................................202
Aal0TpVccTp ......................................................................................................................................203
Aal2PathVccTp ...................................................................................................................................203
Aal5TpVccTp ......................................................................................................................................203
AtmPort...............................................................................................................................................203
ManagedElement ................................................................................................................................203
VclTp...................................................................................................................................................205
VpcTp..................................................................................................................................................205
VplTp ..................................................................................................................................................205
RNC ATTRIBUTES MIRRORED IN WRAN CM ..........................................................................................206
AgpsPositioning..................................................................................................................................206
ArpMap...............................................................................................................................................206
ArpQosClassProfile............................................................................................................................206
CchFrameSynch..................................................................................................................................207
ChannelSwitching ...............................................................................................................................207
CnOperator.........................................................................................................................................209
CoverageRelation ...............................................................................................................................209
DchFrameSynch .................................................................................................................................209
DchMap .................................................................................................. Error! Bookmark not defined.
Equipment...........................................................................................................................................210
Eul.......................................................................................................................................................210
Fach....................................................................................................................................................211
GpsReceiver........................................................................................................................................211
Handover ............................................................................................................................................211
Hsdsch ................................................................................................................................................212
IpAccessHostPool ...............................................................................................................................213
IpEthPacketDataRouter......................................................................................................................213
IubEdch...............................................................................................................................................214
IuLink..................................................................................................................................................214
LocationArea ......................................................................................................................................215
Mbms ..................................................................................................................................................215
MbmsCch ............................................................................................................................................215
MbmsServiceArea ...............................................................................................................................215
MtchFrameSynch................................................................................................................................215
NbapCommon .....................................................................................................................................217
NbapDedicated ...................................................................................................................................217
NodeSynch ..........................................................................................................................................218
NodeSynchTp ......................................................................................................................................218
PacketDataRouter...............................................................................................................................219
Pcap....................................................................................................................................................219
Paging.................................................................................................................................................219
Pch......................................................................................................................................................220
PdrDevice ...........................................................................................................................................220
PlmnIdentityGroup .............................................................................................................................220
PlugInUnit ..........................................................................................................................................220
PositioningServiceClass .....................................................................................................................221
PowerControl .....................................................................................................................................221
RabHandling.......................................................................................................................................222
Rach....................................................................................................................................................222
Ranap..................................................................................................................................................222
Rcs ......................................................................................................................................................223
Page 8
LOGICAL VIEW REPORT
ResMeasControl .................................................................................................................................223
RncCapacity........................................................................................................................................224
RncFeature .........................................................................................................................................224
RncModule..........................................................................................................................................224
RnlQosClassProfile ............................................................................................................................224
Rnsap ..................................................................................................................................................225
RoutingArea........................................................................................................................................225
Rrc ......................................................................................................................................................225
RttPositioning .....................................................................................................................................225
SasPositioning ....................................................................................................................................225
SecurityHandling ................................................................................................................................226
ServiceArea.........................................................................................................................................227
Sid .......................................................................................................................................................227
SpDevicePool......................................................................................................................................227
SpiQosClass........................................................................................................................................227
Subrack ...............................................................................................................................................228
TcMap..................................................................................................... Error! Bookmark not defined.
TimDevice...........................................................................................................................................228
TimDeviceSet .......................................................................................... Error! Bookmark not defined.
TnlDchQosClassProfile .......................................................................... Error! Bookmark not defined.
TnlHspaQosClassProfile ........................................................................ Error! Bookmark not defined.
TnlIuQosClassProfile ............................................................................. Error! Bookmark not defined.
TnlQosClass............................................................................................ Error! Bookmark not defined.
TrafficClass ........................................................................................................................................228
TuDeviceGroup...................................................................................................................................231
UeMeasControl ..................................................................................................................................231
UePositioning .....................................................................................................................................233
UeRc ...................................................................................................................................................233
UeRcEdchFlow ...................................................................................................................................220
UeRabType .........................................................................................................................................233
UeRcPhyChEdch ................................................................................................................................233
UeRcRab.............................................................................................................................................234
UeRcRrc..............................................................................................................................................234
UeRcTrCh...........................................................................................................................................235
Ura......................................................................................................................................................235
UtranNetwork .....................................................................................................................................235
WcdmaCarrier ....................................................................................................................................235
REFERENCES TO MOS IN THE RNC EQUIPMENT VIEW .............................................................................236
RNCMODULE=1.......................................................................................................................................236
RNCMODULE=2.......................................................................................................................................237
RNCMODULE=3.......................................................................................................................................237
RNCMODULE=4.......................................................................................................................................237
RNCMODULE=5.......................................................................................................................................237
RNCMODULE=6.......................................................................................................................................238
RNCMODULE=7.......................................................................................................................................238
RNCMODULE=8.......................................................................................................................................238
RNCMODULE=9.......................................................................................................................................238
RNCMODULE=10.....................................................................................................................................239
RNCMODULE=11.....................................................................................................................................239
RNCMODULE=12.....................................................................................................................................239
RNCMODULE=13.....................................................................................................................................239
RNCMODULE=14.....................................................................................................................................240
RNCMODULE=15.....................................................................................................................................240
RNCMODULE=16.....................................................................................................................................240
RNCMODULE=17.....................................................................................................................................240
RNCMODULE=18.....................................................................................................................................241
Page 9
LOGICAL VIEW REPORT
RNCMODULE=19.....................................................................................................................................241
RNCMODULE=20.....................................................................................................................................241
RNCMODULE=21.....................................................................................................................................241
RNCMODULE=22.....................................................................................................................................242
RNCMODULE=23.....................................................................................................................................242
RNCMODULE=24.....................................................................................................................................242
RNCMODULE=25.....................................................................................................................................242
SELFMANAGEMENT ..................................................................................................................................242
DATA TYPES, DEFINITIONS AND EXCEPTIONS..........................................................................................243
CellIdAlreadyDefined .........................................................................................................................243
ActionNotSupported............................................................................................................................243
CacheIsSynchronized..........................................................................................................................243
MandatoryAttrMissingAtCreate .........................................................................................................243
PlmnIdAlreadyDefined .......................................................................................................................243
LocationAreaIdAlreadyDefined..........................................................................................................243
RoutingAreaIdAlreadyDefined ...........................................................................................................243
ServiceAreaIdAlreadyDefined ............................................................................................................243
GENERAL DATATYPES, DEFINITIONS AND EXCEPTIONS ..........................................................................243
LogFilterParameters ..........................................................................................................................243
UserPreferencesParameters...............................................................................................................243
MimVersionType.................................................................................................................................243
TimeDiffData ......................................................................................................................................243
AseLoadThresholdUlSpeech...............................................................................................................244
PwrLoadThresholdDlSpeech ..............................................................................................................244
RateSelectionPsInteractive .................................................................................................................245
AreaDataType.....................................................................................................................................245
NotFoundException ............................................................................................................................245
IncompatibleVersionsOfNEMIBAndMirrorMIB.................................................................................245
NEIsNotCONNECTED .......................................................................................................................245
BooleanVals........................................................................................................................................245
CellCapability.....................................................................................................................................245
HcsSib3Config ....................................................................................................................................245
HcsUsage............................................................................................................................................245
OnOffVals ...........................................................................................................................................245
SupportedChannelTypes .....................................................................................................................247
SupportedConnStatus .........................................................................................................................247
SupportedMimSwitchPolicy................................................................................................................247
SupportedMirrorMibSynchStatus .......................................................................................................248
SupportedMirrorMibUpdateStatus .....................................................................................................248
SupportedNeType................................................................................................................................248
SupportedProcType ............................................................................................................................248
TERMINOLOGY .........................................................................................................................................248
REFERENCES ............................................................................................................................................248
TOTALS: ...................................................................................................................................................250
LOGICAL PACKAGE STRUCTURE....................................................................................................250
Page 10
LOGICAL VIEW REPORT
LOGICAL VIEW REPORT
Introduction
This MOM document provides information to obtain interoperability to external systems
through the WRAN CM MO script interface, where WRAN is the WCDMA Radio Access
Network. Note that the MOM reflects an important part of the RAN implementation. This
means that the MOM will change correspondingly with system changes. This means that no
backward compatibility is guaranteed, which in turn means that if MO scripts are used, these
scripts must be controlled and modified accordingly.
Abstract
This document specifies the WRAN CM Managed Object Model (MOM). It does not define
the Managed Objects seen through the Mun interface. The WRAN CM MOM shall be
compliant with the Generic Network Resource IRP [21], UTRAN Network Resources IRP
[22] and GERAN Network Resources IRP [24].
The scope for this document is P6.
Revision History
A 070914 Supersedes 1/15554-4/AOM901038 rev. H. Updated for the first OSS RC R6
release. The following impacts have been included:
- RNC MOM 15554-AXD10503/1 rev AS
- TRs: HI49754
- CRs: -
IPs:
OSS-RC R6- Support for SIB18- Iupc-One PLMN-id per Frequency (4/159 41-4/FCP 103
6749/1 rev A) Work Item 254.1
B 071014 Updated for OSS RC R6 shipment D. The following impacts have been
included:
- RNC MOM 15554-AXD10503/1 rev AT
- RBS MOM 1/15554-CXA104389 rev Y2
- CPP6.1 LSV2-1
- TRs:
- CRs:
69/10918-FCP 103 6502,
80/10918-FCP 103 6502,
185/10918-FCP 103 6502
IPs:
Support WRAN-CM Mirror MIMs, OSS-RC R6 (3/159 41-4/FCP 103 6749/1 rev B) Work
Items 2.1 and 2.5_LTE
RNC Capacity Licensing, OSS-RC R6 (2/159 41-4/FCP 103 6749/1 rev A) Work Item 1.1
C 071130 Updated for OSS RC R6 shipment E. The following impacts have been
included:
- RNC MOM 15554-AXD10503/1 rev AU1
Page 11
LOGICAL VIEW REPORT
- RBS MOM 1/15554-CXA104389 rev Y2

- CPP6.1 LSV5-2
- TRs: HI63002
- CRs:
317/109 18-FCP 103 6011,
918/109 18-FCP 103 6011,
925/109 18-FCP 103 6011
IPs:
Support WRAN-CM Mirror MIMs, OSS-RC R6 (3/159 41-4/FCP 103 6749/1 rev D) Work
Item 3.1
OSS RC 6 Support for Eul 2ms TTi and AMR Rate Selection (6/159 41-4/FCP 103 6749/1
rev A) Work Items 1208.1 and 1
Dual Stack Iub, OSS-RC R6 (5/159 41-4/FCP 103 6749/1 rev A) Work Item 1.1 - 156
Support of Cell Broadcast Service, Load-triggered Access Class Barring, OSS-RC R6 (9/159
41-4/FCP 103 6749/1 rev A) Work Items 1.1 and 2.1
D 080129 Updated for OSS RC R6 shipment F. The following impacts have been
included:
- RNC MOM 15554-AXD10503/1 rev AV
- RBS MOM 1/15554-CXA104389 rev AA
- CPP6.1 LSV6-4
- TRs: -
- CRs:
232/109 18-FCP 103 6011,
IPs:
Support WRAN-CM Mirror MIMs, OSS-RC R6 (3/159 41-4/FCP 103 6749/1 rev H) Work
Items 4.1, 4.1_LTE, 4.15_LTE
Support for RNC 3820, OSS-RC R6 (7/159 41-4/FCP 103 6749/1 rev A) Work Item 1.1
Support of TX Diversity, MIMO, Eul 2ms TTI Phase 2, 64QAM, Enhanced Layer 2, OSS-RC
R6 (10/159 41-4/FCP 103 6749/1 rev A) Work Item 5.1
E 080310 Updated for OSS RC R6 shipment G. The following impacts have been
included:
- RNC MOM 15554-AXD10503/1 rev AX
- RBS MOM 1/15554-CXA104389 rev AC
- CPP7.0 LSV10-3
- TRs: -
- CRs:
226/109 18-FCP 103 6502,
429/109 18-FCP 103 6502,
326/109 18-FCP 103 6502 (deprecated attributes will be made nonPersistent in shipment H).
IPs:
Support WRAN-CM Mirror MIMs, OSS-RC R6 (3/159 41-4/FCP 103 6749/1 rev K) Work
Items 5.1
Support for DL Power Control for Enhanced Uplink, UeRC Model Restructering, No of
HSPA users and Priority Queues, OSS-RC R6 (17/159 41-4/FCP 103 6749/1 rev A) Work
Items 1.1, 2.1 and 3.1
Page 12
LOGICAL VIEW REPORT
OSS RC R6, PCA Improvements (1/159 41-4/FCP 103 6749/2 rev A) Work Item 1.7
F 080407 Updated for OSS RC R6 shipment H. The following impacts have been
included:
- RBS MOM 1/15554-CXA104389 rev AD
- CPP7.0 LSV13-3
- TRs: -
- CRs:
388/109 18-FCP 103 6502,
475/109 18-FCP 103 6502,
473/109 18-FCP 103 6502,
326/109 18-FCP 103 6502 (deprecated attributes are made nonPersistent).
IPs:
Support WRAN-CM Mirror MIMs, OSS-RC R6 (3/159 41-4/FCP 103 6749/1 rev M) Work
Items 6.1, 6.1_LTE, 6.12_PKI
OSS RC R6, Automated Consistency Check of Iub and NSA Improvements (14/159 41-
4/FCP 103 6749/1 rev B) Work Item 1.4
Auto Integration of RBS, OSS-RC R6 (28/159 41-FCP 103 6749 rev B) Work Item 1.1
F1 080516 Updated for OSS RC R6 shipment C2.1. The following impacts have been
included:
- RBS MOM 1/15554-CXA104389 rev AD1
- CPP7.0 LSV17-8
- TRs: HJ28814
- CRs:
484/109 18-FCP 103 6502,
530/109 18-FCP 103 6502,
527/109 18-FCP 103 6502,
524/109 18-FCP 103 6749/1
IPs:
SCTP Port Distribution, ET-IPG, OSS-RC R6 (19/159 41-4/FCP 103 6749/1 rev A) Work
Items 1.1 and 1.10
Purpose
The purpose of this document is to specify the Managed Objects accessible by WRAN CM
applications.
Decisions
Page 13
LOGICAL VIEW REPORT
Open Issues
-
Assumptions
1. All management information in the Network Elements are communicated to WRAN CM
through the NE Mirrored MIMs.
2. The assumption in this document for expressing a reference from a MO to another MO

within the same MIM is by using the following format: moRef<MOTYPE>. For expressing a
reference from an MO to another MO in another MIM, a string type attribute is used,
containing the full Distinguished Name of the referenced MO.
3. Datatypes described for attributes are IDL datatypes.
4. All RBS and RNC writeable attributes used by WRAN CM are stored persistently in the
WRAN CM mirrored MIBs. In addition, attributes "reservedBy" needed by WRAN CM are
stored persistently. Value change notifications keep these attributes updated.
5. The MIMs for selfmanagement of WRAN CM are not linked to the rest of the WRAN CM
MOM.
6. The structure of RNC and RBS MIM’s shall be fully compliant with the Resource Model
stated in [22].
7. Direct containment between SubNetwork and ManagedElement is not supported. (optional

in [21]).
8. Containment between SubNetwork, MeContext and ManagedElement as described in ref.

[21] is supported.
9. Two level containment for SubNetwork MOC is supported. The top MOC represents a sub-
network and the bottom MOC a RNS.
10. For common WRAN CM and 3GPP attributes, no more restriction than the stated in [21]
and [22] qualifiers shall be applied.
11. WRAN CM shall map 3GPP MOC <moName>Id and the <MoName>Id according to
WRAN CM name convention.
12. The WRAN CM MOM shall be followed according to 3GPP R4.
13. Association MOC’s Supervisor and SiteAssociation will be not implemented.
14. Link MOC will be not implemented.
15. ManagedElement MOC can represent NEs of other type than RBS and RNC.
16. The RANAG MIM is based on the Cello MIM.
17. All Site information will be kept in Site MOC.
18. Location name information in 3GPP ManagedElement MO will be mapped to site

information in Cello ManagedElement MOC.
Page 14
LOGICAL VIEW REPORT
Document Overview
Logical View
WRAN CM consists of a number of MIMs and InterMIMs.
A SubNetwork MIM on the sub-network level. This MIM contains information reflecting the
RNS’s and Segment’s that are contained in a Sub-Network.
WRAN CM Function Application MIMs. MIMs containing functionality information of the

network resources on Sub-Network level, i.e Transport and Radio network profiles.
RNC mirrored MIM. That mirrors in WRAN CM the RNC Managed Information Model.
RBS mirrored MIM. That mirrors in WRAN CM the RBS Managed Information Model.
RANAG mirrored MIM. That mirrors in WRAN CM the RANAG Managed Information
Model.
Selfmanagement of WRAN CM uses MIMs, such that every managed component and
software component have their own MIM.
An InterMIM models the relationship associations between MOC's that belong to different
MIM's.
Four InterMIM models are defined: SubNetwork-Applications, SubNetwork-
RANAG_Mirror, SubNetwork-RBS_Mirror and SubNetwork-RNC_Mirror
Page 15
LOGICAL VIEW REPORT
Ranos Node Model
<<MIM>> <<MIM>>
RANOS_SUBNETWORK 1 RANOS_APPLICATION_
_MODEL MODEL
1..* 0..* 0..*

0..*
<<MIM>> <<MIM>> <<MIM>> <<MIM>>

RANOS_RNC_MIRROR RANOS_RBS_MIRROR RANOS_RANAG_MIRR RANOS_ERBS_MIRRO
_MODEL_H _MODEL_H OR_MODEL_H R_MODEL_H
<<MIM>>
Selfmanagement
Rn Application Model Main View
<<MOClass>>
RnApplication 1
0..*
1 1 <<MOClass>>
1 EulProfile
<<MOClass>> 1 (from CellAndChannelProfil e)
0..* 1 1 1
FachProfile
0..* 0..*
<<MOClass>> <<MOClass>>
PchProfile HsdschProfile
(from CellAndChannelProfil e)
0..* 0..*
RachProfile MbmsCchProfile
(from CellAndChannelProfil e)
0..* 0..*
UtranCellProfile UserDefEntityList
Page 16
LOGICAL VIEW REPORT
Support Application Model Main View

<<MOClass>>
S upp ortApplication
UserPreferences L og Filter
Planned Configuration Application Model Main View
<<MOClass>>
PlannedConfigurationApp
(from PLANNEDCONFIG_APPLICAT ION_MODEL)
0..n
<<MOClass>>
PlannedAreaProperties
1
0..n
<<MOClass>>
BreakPoint
Page 17
LOGICAL VIEW REPORT
Subnetwork Model Main View
<<MOClass>>
ManagementNode
1 <<MOClass>>
1 Areas
+subNet 0..n
+subNet
1 <<MOClass>> 0..n <<MOClass>>
<<MOClass>> +subNet
SubNetwork Segment
IRPAgent +subNet 1..n+rns
<<MOUnidirAssoc>>
1 +subNet 1
+subNet +rns +subNet
+subNet
+subNet +subNet 0..n <<MOClass>>
0..n
<<MOClass>> Site
ExternalViewableNode
0..n 0..n < <MOClass> >

0..n Link
<<MOClass>>
<<MO Class> > ExternalGsmPlmn
ExternalUtranPlmn 0..n
<<MOClass>>
1 RbsGroup
1
<<MOBidirAssoc>> <<MOBidirAssoc>>
0..n 0..n
0..n 0..n
ExternalUtranCell ExternalGsmCell
Subnetwork Model IRP View
<<MOClass>>
SubNetwork
0..n
+subNet
1
<<MOClass>> +Manages <<M OBi dirAs soc>> +ManagedBy <<MOClass>>
Mana gementNod e ManagedElement
M gm tAssociation
1
<<MOClass>>
IRPAgent
<<MOClass>>
MimInfo <<MOClass>>
PmIRP
0..1 0..1 0..1 0..1
<<MOClass>> <<MOClass>> <<MOClass>> <<MOClass>>
No tificatio nIRP AlarmIRP BulkCmIRP IRATHOMUTRAN
Page 18
LOGICAL VIEW REPORT
Subnetwork Model Site View
Subnetwork Model Areas View
+theSubNetwork
+theSubNetwork 0..n
<<MOClass>>
SubNetwork
+subNet <<MOContain>>
SubNetwork _to_Areas
+theAreas 1
<<MOClass>>
Areas
+theAreas <<MOContain>>
Areas_to_Plmn
+thePlmn 0..10
<<MOClass>>
<<MOContain>> Plmn <<MOContain>>
+thePlmn
+thePlmn Plmn_to_MbmsServiceArea
Plmn_to_LocationArea 0..15000 +theMbmsServiceArea
+theLocationArea 0..300 <<MOClass>>
<<MOClass>> MbmsServiceArea
LocationArea (from M bm sServiceArea)
<<MOContain>> <<MOContain>>
+theLocationArea
+theLocationArea
LocationArea_to_RoutingArea LocationArea_to_ServiceArea
+theRoutingArea +theServiceArea
0..1000 0..15000
RoutingArea ServiceArea
Page 19
LOGICAL VIEW REPORT
Subnetwork Model External Node View
<<MOClass>>
SubNetwork
+subNet
0..n
<<MOClass>>
0..n
<<MOClass>>
ExternalTransportNetwork
0..n
<<MOClass>>
E xte rna lV plTp
Subnetwork Model TN Application View
Page 20
LOGICAL VIEW REPORT
<<M OC lass>>
SubN etwork
(f rom SubNetwork)
1
<<M OC lass>>
TnApplication
(f rom T nApplicati on)
0..n
<<M OC lass>>
VirtualPath
(f rom T nApplicati on)
ERbs Mirror Model Main View

The ManagedElement is a local root MO and it is defined in the NE MIM.
Ranag Mirror Model Main View

The ManagedElement is a local root MO and it is defined in the NE MIM, ref [1].
Page 21
LOGICAL VIEW REPORT
Rbs Mirror Model Main View

Rnc Mirror Model Main View

RANOS_INTERMIM_MODEL
Page 22
LOGICAL VIEW REPORT
<<MIM>> <<MIM>>
RANOS_SUBNET RANOS_APPLIC
WORK_MODEL ATION_MODEL
<<InterMIM>>
RANOS_INTER
MIM_MODEL
<<MIM>> <<MIM>> <<MIM>> <<MIM>>

RANOS_RBS_MIRROR RANOS_RNC_MIRROR RANOS_RANAG_MIRR RANOS_ERBS_MIRRO
_MODEL_H _MODEL_H OR_MODEL_H R_MODEL_H
SUBNETWORK-APPLICATIONS
This InterMIM contains the relationship association between the SubNetwork and WRAN
CM Function Application MIM's. It models the containment association between SubNetwork
and RnApplication, TnApplication and SupportApplication MOC's.
Note the all the XXXApplication MOC's are contained on the SubNetwork (Sub-network
level) MOC.
<< MOCl as s >>

SubNetwork
(f rom SubN etwork) 0..n
+s ubNet +s ubN et
<<MOContain>> <<MOContain>>
Sub NetToRnApplication Sub NetTo Su ppApp l
1
1
<<MOClas s >>
<<MOClas s >> SupportApplication
RnApplication (f rom SupportApplication)
(f rom R nApplication)
Page 23
LOGICAL VIEW REPORT
SUBNETWORK ERBS_MIRROR
This InterMIM contains the relationship association between the SubNetwork and the ERBS
Mirrored MIM's. It models the associations between SubNetwork and the MOC's in ERBS
Mirrored MIM's.
<<MOClass>>
Site 0..n
(from Site)
SubNetwork _to_Site
+theSubNetwork
+subNet+theSubNetwork
<<MOContain>>
+theSite
1
<<MOClass>> SubNetwork _to_ManagementNode 0..n
+theManagementNode +subNet<<MOClass>>
ManagementNode +theSite SubNetwork
(from M anagementNode) 1
<<MOContain>> 1..n <<MOContain>>
+theManagementNode +theSubNetwork+subNet
ManagementNode_to_IRPAgent +rns SubNetwork _to_Segment
<<MOContain>> <<MOUnidirAssoc>>
+Manages
SubNetwork _to_MeContext
Segment_to_SubNetwork 0..n
+theIRPAgent 1
<<MOBidirAssoc>> 1
+theSegment
<<MOClass>>
<<MOClass>>
IRPAgent associatedWith <<MOUnidirAssoc>>
+theSegment
(from IRPAgent) +theSegment Segment
<<MOBidirAssoc>> MeContext_to_Segment
MgmtAssociation +theMeContext 0..n
1
+theMeContext
<<MOClass>>
MeContext n
(from MeContext)
+theMeContext
<<MOContain>>
MeContext_to_ManagedElement
+theManagedElement
+ManagedBy1..n
+theManagedElement
<<MOClass>>
ManagedElement
(from<<MOContain>>
ERbs CPP MOCs containing WRAN CM local attributes)
+theManagedElement
ManagedElement_to_ENodeBFunction
+theENodeBFunction
<<MOClass>>
ENodeBFunction
(from RANOS_ERBS_MIRROR_MODEL_H)
SUBNETWORK RBS_MIRROR
This InterMIM contains the relationship association between the SubNetwork and the RBS
Mirrored MIM's. It models the associations between SubNetwork and the MOC's in RBS
Mirrored MIM's.
Note that the local root, MeContext from RBS Mirrored MIM, is contained on the
SubNetwork (RNS) MOC.
Page 24
LOGICAL VIEW REPORT
<<MOClass>>
Site
(from Site)
0..n
+subNet
1
<<MOClass>> 0..n <<MOClas s>>
ManagementNode +subNet <<MOClass>> +rns RbsGroup
SubNetwork
(from ManagementNode) 1 1 0..n (from RbsGroup)
1..n
+subNet 1
+rns
+Manages
1 <<MOBidirAssoc>> 0.. n
<<MOClass>> <<MOUnidirAssoc>>
associatedWith <<MOContain>> 1
IRPAgent
<<MOClass>>
(from IRPAgent) SubNet work ToMeCont ext <<MOBidirAs soc>> Segment
<<MOBidirAssoc>>
RbsGroupToMecontext 1
MgmtAssociation <<MOUnidirAssoc>>
MeCont ext ToSegment
0..n 0..n n
<<MOClass>>
MeCont ext
+ManagedBy
1..n
<<MOClass>>
ManagedElement
0..n
0..1
<<MOClass>>
NodeBFunction
0..1
+nodeBFunct ionIubLink
<<MOBidirAssoc>>
ConnectedTo
+iubLink NodeBFunction
0..1
<<MOClass>>
IubLink
(f rom RA NOS_RNC_ MI RRO R_ MODEL_F)
SUBNETWORK RNC_MIRROR
This InterMIM contains the relationship association between the SubNetwork and the RNC
Mirrored MIM's. It models the association between SubNetwork and the MOC's in RNC
Mirrored MIM's.
Note that the local root, MeContext from RNC Mirrored MIM, is contained on the
SubNetwork (RNS) MOC.
Page 25
LOGICAL VIEW REPORT
<<MOClass>> 0.. n
+subNet <<MOClass>> +subNet <<MOClass>>
ManagementNode SubNetwork Site
(from ManagementNode) +subNet
+rns
1 +subNet(from S ubNetwork) +subNet 0..n (f ro m Si te )
1..n 1
0..n +subNet 1 <<MOUnidirAssoc>>
+subNet 0..n
1 +Manages
<<MOClass>> +rns
<<MOClass>> ExternalUt ranPlmn <<MOClass>> <<MOClass>>
ExternalGsmPlmn 0..n
1 Segment
IRPAgent
(f ro m Se gment)
(f rom I RPAgent) 1 1
1
<<MOBidirAssoc>> <<MOContain>>
RnsToMeContextCont <<MOBidirAssoc>>
<<MOUnidirAssoc>>
<<MOBidirAssoc>>
RnsToMeContext <<MOBidirAssoc>>
MgmtAssociation
<<MOUnidirAssoc>>
associatedWithRnc
MeContextToSegment
0.. n
0..n 0.. n
<<MOClass>> 0..n
ExternalUtranCell
<<MOClass>>
(f ro m Ex terna lUt ra nCel l) 1 1..n n ExternalGsmCell
<<MOUnidirAssoc>> (from ExternalGsmCell)
<<MOClass>>
MeContext <<MOUnidirAs soc>>
adjacentCell +rnc
adjacentCell1
+ManagedBy <<MOBidirAssoc >>
1..n neLink Relations

+ranag
<<MOClass>> <<MOClass>> <<MOClass>> <<MOClass>>
UtranRelation ManagedElement GsmRelation MeContext
0..n
(f ro m RANOS _RANAG_MI RROR_MODEL _F)
0.. n 0.. n
0..63 0..n
<<MOUnidirAssoc>> 0.. 32
<<MOUnidirAssoc>>
<<MOUnidirAssoc >> adjacentCell externalGsmCellRef
utranCellRef <<MOUnidirAssoc>> <<MOClass>>
1
RncFunction
<<MOClass>>
utranCellRef1
ExternalGsmCell
0.. 1
<<MOClass>> 0..n
ExternalUtranCell 10..1
0..n 0..1500
1 1 0..n
<<MOClass>>
0..64 UtranCell
IurLink 0..n Ex ternalGsmNetwork
<<MOBidirAssoc>> 0..n
0.. 1
<<MOClass>>
IubLink
0..1
+iubLinkNodeBFunction
<<MOBidirAs soc>>
ConnectedTo
+nodeBFunctionIubLink
0.. 1
<<MOClass>>
NodeBFunction
(f rom RA NOS_RBS_MI RROR_MODE L_F)
SUBNETWORK-RANAG_MIRROR
This InterMIM contains the relationship association between the SubNetwork and the
RANAG Mirrored MIM's. It models the association between SubNetwork and the MOC's in
RANAG Mirrored MIM's.
Note that the local root, MeContext from RANAG Mirrored MIM, is contained in the global
root SubNetwork MOC.
Page 26
LOGICAL VIEW REPORT
Managed Object Types
General
Each MO is described in a separate chapter, except for selfmanagement MOs, which are
described in [8].
The "Sub" column indicates which WRAN CM Subsystem that is responsible for setting the
attribute.
General Operations
create
The create operation is supported by all MO Types that can be created through a management
request.
Pre-condition for creation is that the parent MO instance has been created.
NOTE: Parameters for the create action are specified in the attributes table of each MO. For
each attribute is specified if it is Mandatory, Optional or "-" not applicable at create.
delete
The delete operation is supported by all MO Types that can be deleted through a management
request.
Post-condition is that all configuration data for the concerned MO has been deleted.
Furthermore all resources controlled by the MO instance has been released.
How an MO is deleted and possible special conditions is described for each MO.
get <attribute>
This operation is used to get the current value of any attribute. Each attribute has it’s own get
method.
set <attribute>
This operation is used to assign a value to any settable attribute. Settable attributes are marked
"get & set" or "set" in the Attributes tables. Each settable attribute has its own set method.
Page 27
LOGICAL VIEW REPORT
actions
Some MOs have actions other than the general create, delete, get and set. Such actions are
described, if applicable, for each MO. For each action its parameters and the returned result is
specified.
General Attributes
NOTE 1: Attributes having an empty string as default value, shall never be set to NULL.
NULL shall be replaced by an empty string, e.g "".
NOTE 2: Sequence attributes having a default value defined as "empty", shall have the value
"sequence with zero elements" in the XML file. It is not allowed to set the default value to
"undefined type".
Id
Each MO has a string attribute named <MoName>Id
NOTE 1: capital first letter!.
NOTE 2: No capital first letter in 3GPP!. WRAN CM shall map 3GPP <moName>Id in order
to be compliant with WRAN CM <MoName>Id convention. I.e subNetworkId will be
SubNetworkId.
Example: RadioNetworkId
This attribute is the Id-part of the Relative Distinguished Name (RDN) of the MO instance. It
is always the first attribute in the MO. The attribute value is set at MO creation and cannot be
changed.
RDN has the form "<moType>=<name>".
EXAMPLE: RadioNetwork=1
The <name> part is an optional parameter to the create operation. In this case the input value
is checked for uniqueness, i.e. the value must be unique among all instances that have the
same parent.
The < name> can be set by the Operator according to the design rules described in the ref.
[25].
If the MO is created automatically or if the <name> is omitted from the create command then
the value of this attribute is generated by the system. The system will in this case use an
instance number that is unique within all instances that have the same parent. The lowest
unique number, starting with 1 (one) will be used.
User Label.
Some MOs have an attribute called userLabel.
This is a string attribute that can be used to identify a certain MO instance. The value of the
attribute is not used by the system.
See the design rules in ref. [20] for more information.
Alarms
Alarms generated from WRAN CM Managed Objects and Managed Componets contain the
fields as defined in [18].
Alarms generated by Managed Components in the Self Management MIB:
RSD_DB_Threshold_Passed Alarm
When the amount of data in the database exceeds a certain limit (75% of the total capacity)
this alarm is generated. When the database has exceeded the configured threshold the operator
will have to manually expand the memory and clear the alarm.
Page 28
LOGICAL VIEW REPORT
Since the database is distributed on Segments and a Region the alarming objects also have to
be per respective Segment and Region.
Managed Object Class (MOC): Managed Component (managedComponent MO from

Selfmanagement MIB)
Managed Object Instance (MOI): FDN for the Managed Component
Perceived Severity : Minor
Probable Cause : Storage Capacity Problem
Specific Problem : RSD_DB_Threshold_Passed
Event Type : Processing error
Additional Information : <Format according to SoC>
RSD_DB_Full Alarm
This alarm is generated when the database is actually full.
Since the database is distributed on Segments and a Region the alarming objects also have to
be per respective Segment and Region.

Selfmanagement MIB)
Perceived Severity : Major
Probable Cause : Storage Capacity Problem
Specific Problem : RSD_DB_Full
PSA_Expression_Threshold Alarm
This alarm is generated when the expression set by the PSA application
has crossed the threshold.

Selfmanagement MIB)
Perceived Severity : Major, Minor etc., as set by the user.
Probable Cause: Variable out of range
Specific Problem : Alarm generated through PSA application by MO + "MOI" + using
monitor + "monitorName"
(or)
Alarm generated through PSA application by NE " + "MOI" + using monitor +
"monitorName"
General Notifications
Notifications are sent at topology changes (e.g. MO create, delete) and for attribute value
changes for attributes so specified.
Page 29
LOGICAL VIEW REPORT
General Exceptions
In this document, by exceptions means the strings messages that applications add to the CIF’s
exceptions.
Following exceptions are thrown in all MOC’s in Subnetwork MIB: ActionNotSupported,
CacheIsSynchronized and MandatoryAttrMissingAtCreate.
Following exceptions are thrown in all MOC’s in RBS, RNC and RANAG mirrored MIB’s:
IncompatibleVersionsOfNEMIBAndMirrorMIB and NEIsNotCONNECTED.
General Naming Rules

The following rules taken from [25] are applicable to all managed objects unless an exception
is indicated in the description of a specific MO attribute.
RECOMMENDATIONS
Name_Gen:1
The maximum length of a DN string, including RDN separators and including white spaces,
shall not exceed 400 bytes (8-bit).(ref. 1)
The result of this is that FDN should be < 400 characters.
Comment:
The typical example of WRAN CM budget for DN prefix with for example max 35 characters
in the RDN value component plus the RDN type component:
Subnetwork=, 12+35=47
Subnetwork=, 12+35=47
MeContext= 10+35=45
Total: 139 characters
The DN prefix in WRAN CM then will not be longer than 200 characters even with the
longest name in category 1 and 2 (35 characters). This means that there will always be > 200
characters left for LDN.
Name_Gen:2
The character set supported for FDN/LDN/RDN shall be according to ref. 1. Since ref. 1 does
not specifically state the character set, it shall be noted that the standard to follow is ISO8859-
1, see ref 5., with exception of a short list stated in ref. 1 and "^" which Cello uses for internal
use.
Leading and trailing spaces (" ") are not allowed in accordance with the 3GPP standard. For
more information, see Reference 2.
Name_Gen:10
If a naming design rule is not applied this must not affect the system operation negatively.
RULES
Name_Gen:3
RDN shall be used as the identifier of an MO instance i.e. for system internal purposes, for
presentation purposes and towards the NMS.
Name_Gen:4
The attribute userLabel shall be used freely by the system user and should not be used for any
system internal purposes. userLabel shall be a free text which can be used by the system user
to store additional information that he needs to keep track of. The default value is an empty
string that can be changed at any time. userLabel can be presented in the application i.e.in
tooltips, by adding an extra column or by looking in properties file.
Page 30
LOGICAL VIEW REPORT
Name_Gen:5
The maximum length of the RDN value part for a MO of category 1 and 2 is =< 35 characters.
For certain MO classes, within category 1 and 2, the maximum length of 35 characters is far
to large. For those MO classes the maximum length can be decreased in the GUIs.
Example: UtranCell=TrafalgarSquare_A2
Name_Gen:7
The length of the RDN value part for an MO of category 3 and 4 is =< 5 characters.
Name_Gen:8
If there are no specific rules guiding the naming for a specific MO, on UTRAN and/or node
levels, the MO shall have an identity containing a number only, in a sequenced order.
Example: UeRcRl=2.
Name_Gen:9
In case of several instances of one object, each instance shall have a unique number added in
the end to the name dictated by the rules for that object. The format shall be <name following
rule><number>.
Example: If there are two Extension Subracks, both of which shall be called "ES" according
to for example rule Name_RNC_EQM:1. The first one shall then be named "ES1" (or "ES-1")
and the second one "ES2" (or ES-2).
RANOS_APPLICATION_MODEL
RANOS_RN_APPLICATION_MODEL
This MIM contains classes providing abstractions of the radio network functionality on a
Sub-network level.
EulProfile
This profile represents the profile for Eul radio channels. Several instances of the MO
Type can exist.
Page 31
LOGICAL VIEW REPORT
Attributes:
userLabel : string, Mandatory, NoNotification, Restricted, LengthRange = 0..128
Provides support for a user defined label or name upon an object instance level.
Note this is not a default user label but the user label of the profile object, which is used to identify the
EulProfile managed object in display lists.
Sub: RNH
Ref. [2]
rncMimVersion : string, NoNotification

The version of the RNC MIM for which this profile is created
Sub: RNH
Ref. [2]
numEagchCodes : long, NoNotification

Number of codes used for the E-AGCH.
Changing this attribute may affect traffic.
When the number of codes is increased, all traffic is released from the cell.
When the number is decreased, only Eul traffic is released.
Unit: 1 Code
Resolution: 1
Sub: RNH
Ref. [2]
numEhichErgchCodes : long, NoNotification

Number of codes used for the E-HICH/E-RGCH.
Changing this attribute may affect traffic.
When the number is decreased, only Eul traffic is released.
Unit: 1 Code
Resolution: 1
Sub: RNH
Ref. [2]
eulMaxTargetRtwp : long, NoNotification

Maximum allowed Received Total Wideband Power (RTWP) for the RBS scheduler for EUL.
Unit: 0.1 dB
Resolution: 1 dBm
Sub: RNH
Ref. [2]
Page 32
LOGICAL VIEW REPORT
FachProfile
This MO Type represents the profile for Fach radio channels. Several instances of the
MO Type can exist.
Page 33
LOGICAL VIEW REPORT
Attributes:
CellAndChannelProfile managed object in display lists.
Sub: RNH
Ref. [2]
maxFach1Power : long, NoNotification

Maximum power to be used for transmitting the first FACH channel, relative the primaryCpichPower value.
The first FACH is used for logical channels BCCH, CCCH and DCCH, control signalling.
Resolution: 0.1 dB
-350: -35.0 dB
-349: -34.9 dB
...
150: 15.0 dB
Sub: RNH
Ref. [2]
maxFach2Power : long, NoNotification

Maximum power to be used for transmitting the second FACH channel, relative the primaryCpichPower value.
The second FACH is used for logical channel DTCH traffic signalling.
Resolution: 0.1 dB
-350: -35.0 dB
-349: -34.9 dB
...
150: 15.0 dB
Sub: RNH
Ref. [2]
sccpchOffset : long, NoNotification

Radio timing offset inside a radio frame (SCCPCH parameter)
0: 0 chip
1: 256 chip
149: 38144 chip
A change of this attribute may affect traffic.
Sub: RNH
Ref. [2]

Sub: RNH
Ref. [2]
pOffset1Fach : long, NoNotification

Power offset for the TFCI. This parameter is applied to both FACH and PCH.
Sub: RNH
Ref. [2]
Page 34
LOGICAL VIEW REPORT
pOffset3Fach : long, NoNotification

Power offset for the pilot. This parameter is applied to both FACH and PCH.
Sub: RNH
Ref. [2]
HsdschProfile
This profile represents the profile for Hsdsch radio channels. Several instances of the MO
Type can exist.
Page 35
LOGICAL VIEW REPORT
Attributes:
HsdschProfile managed object in display lists.
Sub: RNH
Ref. [2]
deltaAck1 : long, NoNotification

The power offset for acknowledgement messages on HS-DPCCH for UE Connections using one RLS.
Unit: N/A
Resolution: 1
Sub: RNH
Ref. [2]
deltaNack1 : long, NoNotification

The power offset for non-acknowledgement messages on HS-DPCCH for UE Connections using one RLS.
Unit: N/A
Resolution: 1
Sub: RNH
Ref. [2]
deltaAck2 : long, NoNotification

The power offset for acknowledgement messages on HS-DPCCH for UE Connections using two or more RLSs.
Unit: N/A
Resolution: 1
Sub: RNH
Ref. [2]
deltaNack2 : long, NoNotification

The power offset for non-acknowledgement messages on HS-DPCCH for UE Connections using two or more
RLSs.
Unit: N/A
Resolution: 1
Sub: RNH
Ref. [2]
deltaCqi1 : long, NoNotification

The power offset for CQI report messages on HS-DPCCH for UE Connections using one RLS.
Unit: N/A
Resolution: 1
Sub: RNH
Ref. [2]
deltaCqi2 : long, NoNotification

The power offset for CQI report messages on HS-DPCCH for UE Connections using two or more RLSs.
Unit: N/A
Resolution: 1
Page 36
LOGICAL VIEW REPORT
Sub: RNH
Ref. [2]
initialCqiRepetitionFactor : long, NoNotification

The initial number of repetitions for CQI report messages on HS-DPCCH.
Unit: N/A
Resolution: 1
Sub: RNH
Ref. [2]
initialAckNackRepetitionFactor : long, NoNotification

The initial number of repetitions for ACK/NACK feedback transmissions on HS-DPCCH.
Unit: N/A
Resolution: 1
Sub: RNH
Ref. [2]
cqiFeedbackCycle : long, NoNotification

The duration of the CQI feedback cycle on HS-DPCCH.
Unit: 1 ms
Resolution: N/A
Sub: RNH
Ref. [2]
hsMeasurementPowerOffset : long, NoNotification

The Measurement power offset, also called gamma, sent to the UE and RBS via RRC and NBAP. Used to offset
the CQI in order to utilize the whole CQI range.
Unit: 0.1 dB
Resolution: 5
Sub: RNH
Ref. [2]
numHsPdschCodes : long, NoNotification

Number of codes of SF=16 used for the HS-PDSCH.
When the number is decreased, traffic is not released in the cell, but the Hs-dsch throughput may be affected.
Unit: 1 code
Resolution: 1
Sub: RNH
Ref. [2]

Sub: RNH
Ref. [2]
Page 37
LOGICAL VIEW REPORT
codeThresholdPdu656 : long, NoNotification

Threshold for determining when to use the RLC PDU size = 656 bits for UEs with HS-DSCH physical layer
category 7 to 10.
0 = always used,
15 = never used,
any other value, then
656 bits are used if codeThresholdPdu656 < numHsPdschCodes,
336 bits are used if codeThresholdPdu656 >= numHsPdschCodes
Unit: 1 code
Resolution: 1
Sub: RNH
Ref. [2]
numHsScchCodes : long, NoNotification

Number of codes of SF=128 used for the HS-SCCH.
When the number of codes is increased or decreased, all traffic within the cell is released.
Unit: 1 code
Resolution: 1
MbmsCchProfile
This profile represents the profile for Mbms radio channels. Several instances of the MO
Type can exist.
Page 38
LOGICAL VIEW REPORT
Attributes:
hcsPrioOffset : long, NoNotification
Priority offset added, if HCS is used, by UE to the normal HCS priority level of cells on the MBMS preferred
frequency in order to keep/move the UE to that frequency.
The parameter value is used to set the value of the hcsOffMbms parameter scheduled on MCCH. The parameter
value 7 is the highest priority.
Change take effect: Next MCCH update with preferred frequency information for MBMS services.
Unit: N/A
Resolution: 1
Sub: RNH
Ref. [2]
mbmsDispersion : BooleanVals, NoNotification

Controls whether the UE at MBMS session stop shall perform MBMS Frequency Layer Dispersion (FLD) or
not, i.e. whether the UE shall select a cell on the frequency layer that was used before the MBMS session start
or not.
Change take effect: Next MCCH update where an MBMS service on preffered layer is released.
Unit: N/A
Resolution: N/A
Sub: RNH
Ref. [2]
mcchPowerOffset : long, NoNotification

The power of the S-CPCCH used for MCCH transmission.
The power is set relative to primaryCpichPower in the cell, i.e if CPICH power changes the absolute power of
S-CPCCH used for MCCH will also change. The power needed depends on the number of repetitions on
MCCH and acceptable BLER at cell border.
A consequence of changing the parameter is that all MBMS common channels in the cell are released. The
system will automatically establish the channels again. Operation state for MbmsCch will be set to disabled by
the system and enabled when MCCH and MICH are establish with the changed configuration in RBS.
When deactivation is inititaed, in case of MBMS sessions where this cell is Preferred Line (PL), all MTCH
Radio Bearers (RBs) in the cell are released. In case of MBMS sessions where this cell is a non-PL cell, the
information about the PL cell is removed.
When the control channels MCCH and MICH are activated. For MBMS sessions where this is a Preferred Line
(PL), RNC will try to set up MTCH channels for all ongoing MBMS sessions with no RB established in the
cell. In case of MBMS sessions where this is a non- PL cell, the information about the PL cell is uppdated in
MCCH for ongoing MBMS sessions.
Change take effect: Immediate.
Unit: 0.1 dB
Resolution: 1
Sub: RNH
Ref. [2]
mcchPowerOffsetTfci : long, NoNotification

The power of the TFCI field on the S-CPCCH used for MCCH transmission.
The power is set relative to primaryCpichPower in the cell, i.e. if CPICH power changes the absolute power of
the TFCI field used for MCCH will also change.
Page 39
LOGICAL VIEW REPORT
Unit: 0.01dB
Resolution : 25
Sub: RNH
Ref. [2]
michPowerOffset : long, NoNotification

MICH power .
MICH will also change.
Unit: 1 dB
Resolution: 1
Sub: RNH
Ref. [2]
mtch128PowerOffset : long, NoNotification

The power of the S-CPCCH used for MTCH 129.6 kbps transmission.
S-CPCCH used for MTCH 129.6 kbps will also change.
Change take effect: New MBMS sessions
Unit: 0.1 dB
Resolution: 1
Sub: RNH
Ref. [2]
mtch128PowerOffsetTfci : long, NoNotification

The power of the TFCI field on the S-CPCCH used for MTCH 129.6 kbps transmission.
the TFCI field used for MTCH 129.6 kbps will also change.
Unit: 0.01 dB
Resolution: 25
Page 40
LOGICAL VIEW REPORT
Sub: RNH
Ref. [2]

Unit: 0.1 dB
Resolution: 1
Sub: RNH
Ref. [2]

Unit: 0.01 dB
Resolution: 25
Sub: RNH
Ref. [2]

Unit: 0.1 dB
Resolution: 1
Sub: RNH
Ref. [2]

Unit: 0.01 dB
Resolution: 25
Sub: RNH
Ref. [2]
numNotificationInd : long, NoNotification

The number of notification indicators per MICH frame.
The numbers of notification indicators are provided to RBS at configuration of MCCH/MICH by inclusion of
MICH Mode in NBAP signaling. To minimize MICH power Nn is set to a low value.
Page 41
LOGICAL VIEW REPORT
Reference 3GPP TS 25.433 and 3GPP TS 25.211.
Unit: N/A
Resolution: N/A
Sub: RNH
Ref. [2]
plServiceRestriction : BooleanVals, NoNotification

When set to True that the UE shall consider that UTRAN will not provide any non-MBMS services on the
MBMS preferred frequency and based on this the UE should perform service prioritizing, i.e. select between
MBMS services and non-MBMS services. Otherwise, UE shall consider that UTRAN will provide any non-
MBMS services on the MBMS preferred frequency. If the parameter value is True, the MBMS PL Service
Restriction Information is scheduled on MCCH.
Unit: N/A
Resolution: N/A
Sub: RNH
Ref. [2]
qualityOffset : long, NoNotification

Additional quality offset added, if HCS is not used, by UE to the measured quality of the cells on the MBMS
preferred frequency in order to keep/move the UE to that frequency.
The parameter value is used to set the value of the qOffMbms parameter scheduled on MCCH.
The parameter value -1 implies infinity
Unit: dB
Resolution: N/A
Sub: RNH
Ref. [2]

Sub: RNH
Ref. [2]

MbmsCchProfile managed object in display lists.
Sub: RNH
Ref. [2]
Page 42
LOGICAL VIEW REPORT
PchProfile
This profile represents the profile for Pch radio channels. Several instances of the MO
Type can exist.
Attributes:
Sub: RNH
Ref. [2]
pchPower : long, NoNotification

Maximum power to be used for transmitting the PCH channel, relative the primaryCpichPower value.
Resolution: 0.1 dB
-350: -35.0 dB
-349: -34.9 dB
...
150: 15.0 dB
Sub: RNH
Ref. [2]
pichPower : long, NoNotification

PICH Power is the power to be used for transmitting on thephysical channelcarrying the paging indicators,
relative to the primary CpichPower value.
Resolution: 0.1 dB
-10: -10.0 dB
-9: -9.0 dB
..
5: 5.0 dB
Sub: RNH
Ref. [2]
sccpchOffset : long, NoNotification

Radio timing offset inside a radio frame (SCCPCH parameter)
0: 0 chip
1: 256 chip
149: 38144 chip
Sub: RNH
Ref. [2]

Sub: RNH
Ref. [2]
Page 43
LOGICAL VIEW REPORT
RachProfile
Thie MO Type represents the profile for Rach radio channels. Several instances of the
MO Type can exist.
Attributes:
Sub: RNH
Ref. [2]
aichTransmissionTiming : long, NoNotification

AICH timing delay parameter.
A Change of this attribute may affect traffic.
0: 3 chip delay
1: 4 chip delay
Sub: RNH
Ref. [2]
aichPower : long, NoNotification

AICH power, to be used for transmitting on AICH, relative to the primaryCpichPower value.
-22: -22.0 dB
-21: -21.0 dB
..
5: 5.0 dB
Sub: RNH
Ref. [2]
scramblingCodeWordNo : long, NoNotification

Scrambling Code for preamble and message part. (PRACH parameter)
The value range is set in a short term to cover both the RRC and NBAP spec.
Sub: RNH
Ref. [2]
powerOffsetPpm : long, NoNotification

Power step in dB between preamble and the message part.
- 5: -5.0 dB
...
10: 10.0 dB
Sub: RNH
Ref. [2]
powerOffsetP0 : long, NoNotification

Power step in dB when no acquisition indicator is received.
Sub: RNH
Ref. [2]
Page 44
LOGICAL VIEW REPORT
constantValueCprach : long, NoNotification

Constant value in dB used by the UE to calculate the initial power on PRACH according to the Open loop
power control procedure.
Sub: RNH
Ref. [2]
spreadingFactor : long, NoNotification

Minimum spreading factor to use for PRACH.
The value 32 corresponds to TTI= 10ms
The value 64 corresponds to TTI= 20ms
A change in this attribute may affect traffic.
Sub: RNH
Ref. [2]
maxPreambleCycle : long, NoNotification

Maximum number of preamble ramping cycle
Sub: RNH
Ref. [2]
preambleRetransMax : long, NoNotification

Maximum number of preambles in one preamble ramping cycle
Sub: RNH
Ref. [2]

Sub: RNH
Ref. [2]
preambleSignatures : long, NoNotification

Preamble signatures for PRACH.
Sub: RNH
Ref. [2]
subChannelNo : long, NoNotification

Sub Channel Number.
Sub: RNH
Ref. [2]
Page 45
LOGICAL VIEW REPORT
RnApplication
RnApplication
SystemCreated
This MO Type represents the Radio Network Application and is the root object of the RN
Application MIB. Only one instance of the MO Type can exist per RN Application MIB.
Attributes:
userLabel : string, NoNotification, LengthRange = 0..128
Provides support for putting a label on the MO instance.
Sub: CMS
Ref. [7]
UserDefEntityList
UserDefEntityList
This MO is used to store a list of entities that the operator will use frequently within the
RNH thin client applications.
Several instances of this MO Class can exist.

Attributes:
Used to name/distinguish the MO instance in the thin client.
Sub: RNH
Ref. [2]
listOfEntities : sequence <string>, Mandatory, NoNotification, Restricted

Sequence of strings which are the FDN's of the entities.
Sub: RNH
Ref. [2]
owner : string, NoNotification

This field may be used to state which operator created this instance.
Sub: RNH
Ref. [2]
UtranCellProfile
This MO Type represents the profile for Cells. Several instances of the MO Type can
exist.
Page 46
LOGICAL VIEW REPORT
Attributes:
Sub: RNH
Ref. [2]
qHyst1 : long, NoNotification

Used in UE functions for cell reselection in idle and connected mod. Value launched by system information
(SBI3).
Resolution:2
Sub: RNH
Ref. [2]
qHyst2 : long, NoNotification

The hysteresis value of the serving cell.
Sub: RNH
Ref. [2]
minPwrRl : long, NoNotification

This parameter describes minimum power per RL.
Resolution 1 (= 0.1dBm)
-350: -35dB
-349: -34.9dB
-348: -34.8dB
..
-200: -20dB
..
150: 15dB
Sub: RNH
Ref. [2]
maxRate : long, NoNotification

This parameter describes maximum rate for max. power mapping.
Resolution 1 (=10bps).
0 : 0 bps
1 : 10 bps
2 : 20 bps
...
40320: 403200 bps
1600000: 16000000 bps
Sub: RNH
Ref. [2]
interRate : long, NoNotification

This parameter describes intermeiate rate for max. power mapping.
Page 47
LOGICAL VIEW REPORT
0 : 0 bps
1: 10 bps
2 : 20 bps
......
7760: 77600 bps
1600000: 16000000 bps
Sub: RNH
Ref. [2]
minimumRate : long, NoNotification

This parameter describes minimum rate for max. power mapping.
0 : 0 bps
1 : 10 bps
2 : 20 bps
......
1220: 1220 bps
......
1600000: 16000000 bps
Sub: RNH
Ref. [2]
maxPwrMax : long, NoNotification

This parameter describes the maximum relative power for max. power mapping.
Resolution1(=0.1dB)
-350 : -35dB
-349 : -34.9dB
-348 : -34.8dB
....
48 : 4.8dB
....
150 : 15dB
Sub: RNH
Ref. [2]
interPwrMax : long, NoNotification

This parameter describes the intermediate relative power for max. power mapping.
Resolution 1(=0.1dB)
-350 : -35dB
-349 : -34.9dB
-348 : -34.8dB
....
38 : 3.8dB
....
150 : 15dB
Sub: RNH
Ref. [2]
minPwrMax : long, NoNotification

This parameter describes the minimum relative power for max. power mapping.
Page 48
LOGICAL VIEW REPORT
Resolution1(=0.1dB)
-350 : -35dB
-349 : -34.9dB
-348 : -34.8dB
....
-200 : -20dB
....
150 : 15dB
Sub: RNH
Ref. [2]
compModeAdm : long, NoNotification

This parameter describes admission limit for #RL in compressed mode in a cell.
Resolution 1.
Sub: RNH
Ref. [2]
iFOffset : long, NoNotification

This parameter describes the triggering level offset for UL congestion measurements.
Resolution 1(0.1dBm).
0 : 0.0dBm
1 : 0.1dBm
2 : 0.2dBm
......
621 : 62.1dBm
Sub: RNH
Ref. [2]
iFHyst : long, NoNotification

This parameter describes hytsterese level for UL congestion measurements.
Resolution 1(10ms).
0 : 0ms
1 : 10ms
2 : 20ms
......
6000 : 60000ms
Sub: RNH
Ref. [2]
iFCong : long, NoNotification

This parameter describes the reset level for UL congestion measurements.
Resolution is 1 (0.1 dB).
0 : -112dBm
1 : -111.9dBm
......
130: (-99dBm)
621 : -50dBm
Sub: RNH
Ref. [2]
interFreqFddMeasIndicator : BooleanVals, NoNotification
Page 49
LOGICAL VIEW REPORT
The inter-frequency FDD measurement indicator.
FALSE = 0
TRUE = 1
Sub: RNH
Ref. [2]
sRatSearch : long, NoNotification

The decision on when measurements on GSM frequencies shall be performed is made using this parameter in
relation with Squal.
If S_qual > this parameter, UE need not perform measurements on GSM cells.
If S_qual <= this paramter, UE shall perform measurment on GSM cells.
-32 : -32dB
-30 : -30dB
......
20 : 20dB
Resolution 2
Sub: RNH
Ref. [2]
sIntraSearch : long, NoNotification

The decision on when measurements on intra frequencies shall be performed.
Initially set by system to 0 (= not sent).
Resolution is 1(=2dBm).
0 : not sent.
1 : -32 dBm
2 : -30 dBm
....
27 : 20 dBm
Sub: RNH
Ref. [2]
sInterSearch : long, NoNotification

The decision on when measurements on inter frequencies shall be performed. Initially set by system to 0 (= not
sent).
Resolution is 1(=2dBm).
0 : not sent.
1 : -32 dBm
2 : -30 dBm
....
27 : 20 dBm
Sub: RNH
Ref. [2]
fachMeasOccaCycLenCoeff : long, NoNotification

Fach Measurement Occasion Cycle Length coefficient is a factor which is used when UE performing inter-
frequency and inter system measurements.
The UE will use this parameter to calculate the interval length to decide the repeating cycle of the measurement.
0 : not broadcasted in SIB 11.
1 : not used.
2 : not used.
3 : used when inter frequency and GSM neighbours.
4 : used when inter freqency or GSM neighbours.
5 - 12 not used.
Page 50
LOGICAL VIEW REPORT
Sub: RNH
Ref. [2]
accessClassNBarred : sequence <BooleanVals,16,nonUnique>, NoNotification

Specifies which access classes are barred.
Each boolean in the sequence represents one access class. The access class is restricted by setting the boolean to
TRUE ('barred'), otherwise the boolean is set to FALSE ('not barred'). First element represent access class 0.
Unit: N/A
Resolution: N/A
Sub: RNH
Ref. [2]
primarySchPower : long, NoNotification

Primary SCH power, relative to the primaryCpichPower value.
-350: -35.0 dB
-349: -34.9 dB
.
.
150: 15.0 dB
Sub: RNH
Ref. [2]
secondarySchPower : long, NoNotification

Secondary SCH power, relative to the primaryCpichPower value.
-350: -35.0 dB
-349: -34.9 dB
.
.
150: 15.0 dB
Sub: RNH
Ref. [2]
primaryCpichPower : long, NoNotification

Primary CPICH power is the power to be used for transmitting the PCPICH.
-100: -10.0 dBm

-99: -99.0 dBm
......
270 : 27dBm
......
500: 50.0 dBm
Sub: RNH
Ref. [2]
maximumTransmissionPower : long, NoNotification

Maximum transmission power is maximum power for all downlink channels added together, that is allowed to
be used simultaniously in a cell.
0: 0 .0 dBm
1: 0.1dBm
....
500: 50 dBm
Page 51
LOGICAL VIEW REPORT
Sub: RNH
Ref. [2]
maxTxPowerUl : long, NoNotification

Used in UE functions for cell selection/reselection in idle mode and connected mode. Also used by UTRAN to
control the maximum TX power level an UE may use. If the current UE uplink transmit power is above the
indicated power value, the UE shall decrease the power to a level below the power value. Value launched by
system information (SB11) for each intra frequency measurement object corresponding to adjacent cells of the
serving cell. Value launched by system information (SIB3) for serving cell.
Sub: RNH
Ref. [2]
bchPower : long, NoNotification

BCH power is the power to be used for transmitting on the BCH, relative to the primaryCpichPower value.
-350: -35.0 dB
-349: -34.9 dB
...
150: 15.0 dB
Sub: RNH
Ref. [2]
cellReserved : SupportedReservedStates, NoNotification

Is cell reserved for operator use only.
RESERVED = 0
NOT_RESERVED = 1
Sub: RNH
Ref. [2]
treSelection : long, NoNotification

Control of cell selection/reselection. Time to trigger for cell reselection in seconds.
Initially set by system to 5. Value launched by system information (SBI3)
Sub: RNH
Ref. [2]
qualMeasQuantity : SupportedMeasQuantities, NoNotification

Used in UI function for cell selection/reselection in idle and connected mode. Cell selection and reselection
quality measure. Value launched by system information (SBI3).
CPICH_RSCP = 1
CPICH_EC_NO = 2
Sub: RNH
Ref. [2]
qQualMin : long, NoNotification

Used in UI functions for Cell selection/reselection in idle and connected mods. Minimum required (acceptable)
quality level in the Cell (dB).
Sub: RNH
Ref. [2]
qRxLevMin : long, NoNotification
Page 52
LOGICAL VIEW REPORT
Used in UE functions for cell selection/reselection in idle and connected modes. Minimum required
(Acceptable) RX level in the cell (dB). Value launched by system information (SB11) for each intrafrequency
measurement object corresponding to adjacent cells of serving cell. Value launched by system information
(SIB3) for serving cell.
Resolution: 2
Sub: RNH
Ref. [2]
Sub: RNH
Ref. [2]
individualOffset : long, NoNotification

Used in UE functionevent reporting. This offset is added to the memeasured quantity before the UE evaluates if
an event has occured.
-100:-10dB
-95: -9.5 dB
...
100: 10.0 dB
Resolution : 5 (= 0.5 dB)
Sub: RNH
Ref. [2]
pwrAdm : long, NoNotification

Used by Congestion Control. Admission limit for DL power in DL cell carrier power.
Resolution: 1%
Initially set by the system to 75.
Sub: RNH
Ref. [2]
pwrAdmOffset : long, NoNotification

Used by Congestion Control. Admission limit for DL power in DL cell carrier power.
Resolution:1%
0: 0%
1: 1%
...
100: 100%
Sub: RNH
Ref. [2]
pwrOffset : long, NoNotification

Used by Congestion Control.
Resolution: 1%
Initially set by the system to 5%.
pwrHyst : long, NoNotification

Measurement Hysteresis Time.
Used by congestion Control.
Resolution: 10mS. Initially set by system to100mS.
0: 0 mS
10: 10 mS
...
60 000: 1min
Sub: RNH
Ref. [2]
Page 53
LOGICAL VIEW REPORT
tmCongAction : long, NoNotification

Interval between Congestion Actions.
Used by congestion Control.
Resolution: 10mS. Initially set by system to100mS.
0: 0 mS
10: 10 mS
...
60 000: 1min
releaseAseDl : long, NoNotification

Amount of ASE to be released in DL at each congestion action.
Resolution: 1 ASE.
Initially set by the system to 10 ASE.
Sub: RNH
Ref. [2]
dlCodeAdm : long, NoNotification

Admission limit for admission on DL channelization code treeusage (fraction of the tree in usage). Used by
Admission Control in subfunctionAdmission Control Handler for non-emergency RRC and RAB.
Resolution: 1
Initially set by system to 200. ???? 70 as default???
aseDlAdm : long, NoNotification

Admission limit for admission on max. capacity (ASE level) in DL.
Used by Admission Control in subfunction Admission Request Handler.
Resolution: 1 ASE.
Sub: RNH
Ref. [2]
beMarginAseDl : long, NoNotification

Relative admission limit for admission on ASE for nonguaranteed bitrate calls (traffic class 'background' or
'interactive') in DL.
Used by Admission Control in subfunction Admission Request Handler for non-emergency RRC or RAB.
Resolution: 1 ASE.
Sub: RNH
Ref. [2]
aseUlAdm : long, NoNotification

Admission limit for admission on ASE in UL.
Used by Admission Control in subfunction Admission Request Handler.
Resolution: 1 ASE.
Sub: RNH
Ref. [2]

Sub: RNH
Ref. [2]
beMarginAseUl : long, NoNotification
Page 54
LOGICAL VIEW REPORT
Relative admission limit for admission on ASE for nonguaranteed bitrate calls (traffic class 'background' or
'interactive') in UL.
Used by Admission Control in subfunction Admission Request Handler for non-emergency RRC or RAB.
Resolution: 1 ASE.
Sub: RNH
Ref. [2]
sf8Adm : long, NoNotification

Admission limit for admission on number of SF=8 none-guarantied bitrate (best effort) connection in a cell in
DL (SF histogram). Used in Admission Control in subfunction in Admission Request for none-emergency RRC
and RAB.
Resolution: 1 connection initially set by the system to 3 connections.
Sub: RNH
Ref. [2]

Admission limit for admission on number of SF=32 none-guaranteed bitrate (best effort) connections in a cell in
DL (SF histogram) Used by Admission Control in subfunction admission request for none-emergency RRC
and RAB.
Resolution: 1 connection
Initially set by the system to 10 connections.
Sub: RNH
Ref. [2]
aseUlAdmOffset : long, NoNotification

Relative admission limit for admission on ASE in UL.Used by Admission Control in subfunction Admission
Request Handler.
Resolution: 1 ASE.
Sub: RNH
Ref. [2]
beMarginDlPwr : long, NoNotification

This parameter describes the admission margin for DL power usage (non-guaranteed requests)
Suib: RNH
Ref. [2]
beMarginDlCode : long, NoNotification

This parameter describes the admission margin for DL code utilization in DL (non-handover, non-compressed
mode RLs only)
Sub: RNH
Ref. [2]

Admission limit for admission on number of SF=16 non-guaranteed bitrate(best-effort) connections in a cell in
DL (SF histogram). Used by Admission Control in subfunction Admission Request Handler. Resolution: 1
connection. Initially set by the system to 3 connections.
Sub: RNH
Ref. [2]
hoType : SupportedHoTypes, NoNotification
Page 55
LOGICAL VIEW REPORT
When a HO from the current WCDMA frequency is triggered by the connection quality monitoring indicating
that the WCDMA quality is low this parameter indicates per cell if GSM HO, IFHO or none shall be attempted.
Sub: RNH
Reference: [2]
usedFreqThresh2dEcno : long, NoNotification

Threshold for event 2d for the used frequency when the measurement quantity is Ec/No (set by measQuantity2).
Unit: 1 dB
Resolution: 1
Sub: RNH
Ref. [2]
usedFreqThresh2dRscp : long, NoNotification

Threshold for event 2d for the used frequency when the measurement quantity is RSCP (set by measQuantity2).
Unit: 1 dBm
Resolution: 1
Sub: RNH
Ref. [2]
nOutSyncInd : long, NoNotification

Number of frames to be considered for out-of-sync detection.
Unit: 1 frame
Resolution: 1
Sub: RNH
Ref. [2]
nInSyncInd : long, NoNotification

Number of frames to be considered for in-sync detection.
(nInSyncInd * 10 ms) < rlFailureT
Unit: 1 frame
Resolution: 1
Sub: RNH
Ref. [2]
rlFailureT : long, NoNotification

Guard period before sending RL Failure.
rlFailureT > (nInSyncInd * 10 ms)
Unit: 0.1 seconds

Resolution: 1
Sub: RNH
Ref. [2]
tmCongActionNg : long, NoNotification

Interval between congestion actions which target non-guaranteed traffic.
Unit: 1 ms
Resolution: 1
Sub: RNH
Page 56
LOGICAL VIEW REPORT
Ref. [2]
releaseAseDlNg : long, NoNotification

Amount of ASE to be released at a congestion action which targets non-guaranteed traffic.
Unit: 1 ASE
Resolution: 1
0 indicates that no ASE is released for non-guaranteed traffic class connections.
Sub: RNH
Ref. [2]
tmInitialG : long, NoNotification

Initial delay for start of congestion actions when targeting only guaranteed traffic.
Unit: 1 ms
Resolution: 1
Sub: RNH
Ref. [2]
loadSharingGsmFraction : long, NoNotification

Defines percentage of the guaranteed non-handover admission limit (pwrAdm) above which Directed Retry
should be invoked.
Unit: 1 %
Resolution: 1
Sub: RNH
Ref. [2]
loadSharingGsmThreshold : long, NoNotification

Defines percentage of Speech calls that can be directed to GSM after the loadSharingGsmThreshold has been
exceeded.
Unite: 1 %
Resolution: 1
Sub: RNH
Ref. [2]
hardIfhoCorr : long, NoNotification

Correction factor to be used in the calculation of initial power for SRB in hard interfrequency handover
situations.
Unit: 1 dB
Resolution: 1
Sub: RNH
Ref. [2]
hsdpaUsersAdm : long, NoNotification

Admission limit for the number of users assigned to the HS-PDSCH/HS-SCCH in the cell. The limit is only
applicable to RAB setup of HSDPA.
Unit: 1 user
Resolution: 1
Sub: RNH
Page 57
LOGICAL VIEW REPORT
Ref. [2]
loadSharingMargin : long, NoNotification

Offset added to the DL power of the cell at inter-frequency load sharing evaluation.
Unit: 1 %
Resolution: 1
Sub: RNH
Ref. [2]
releaseAseDlGhs : long, NoNotification

Amount of ASE in DL to be released with each periodic congestion resolve action targeting guaranteed-hs
traffic class connections in a cell.
0 indicates that no ASE is released for guaranteed-hs traffic class connections. This prevents congestion resolve
actions on the guaranteed-hs traffic class connections in a cell.
Unit: 0.1 ASE

Resolution: 1
Sub: RNH
Ref. [2]
tmCongActionGhs : long, NoNotification

Interval betwen periodic congestion resolve actions on guaranteed-hs traffic class connections in a cell.
Unit: 1 ms
Resolution: 1
Sub: RNH
Ref. [2]
tmInitialGhs : long, NoNotification

Minimum time before congestion resolve actions are initiated on guaranteed-hs traffic class connections in a
cell (after detection of DL cell congestion).
tmInitialGhs <= tmInitialG
Unit: 1 ms.
Resolution: 1
Sub: RNH
Ref. [2]
sf4AdmUl : long, NoNotification

Max. number of simultaneous connections in a cell in UL where each connection's Spreading Factor (SF) = 4
(service class = non-guaranteed/guaranteed-hs, setup type=all).
Unit: 1 RL with SF=4

Resolution: 1
0 indicates that no 384 kbps RLs in UL is allowed
Sub: RNH
Ref. [2]
sf16gAdm : long
Page 58
LOGICAL VIEW REPORT
Admission limit for RLs with Spreading Factor (SF) =16 in DL (guaranteed admission requests).
Unit: 1 RL with SF=16

Resolution: 1
16 means that no 128 kbps RLs in DL is allowed
Sub: RNH
Ref. [2]
sHcsRat : long
RAT specific threshold in the serving cell used in the inter-RAT measurement rules.
This parameter is used by the UE to decide when to start GSM measurements for cell reselection, if the serving
cell is indicated to belong to a Hiearachical Cell Structure (HCS)
GSM measurements in idle mode and state CELL_FACH are started by the UE when RSCP <= qRxLevMin +
sHscRat.
If sHcsRat is set to a negative value, this will be interpreted as 0 by the UE (according to 3GPP TS 25.331).
Unit: 1 dB
Resolution: 2
Sub: RNH
Ref. [2]

Admission limit (traffic class = non-guaranteed/guaranteed-hs, admission class = handover or other) for number
of radio links with UL SF = 16.
Unit: 1 connection
Resolution: 1
Sub: RNH
Ref. [2]

Admission limit (traffic class = non-guaranteed/guaranteed-hs, admission class = handover or other) for number
of radio links with UL SF = 8.
Unit: 1 connection
Resolution: 1
Sub: RNH
Ref. [2]
sf8gAdmUl : long, NoNotification

Admission limit for RLs with spreading factor (SF) = 8 in UL (guaranteed admission requests).
Unit: 1 connection
Resolution: 1
Sub: RNH
Ref. [2]
Page 59
LOGICAL VIEW REPORT
agpsEnabled : BooleanVals, NoNotification

Indicates if A-GPS is enabled or not for a cell.
FALSE = 0
TRUE = 1
Unit: N/A
Resolution: N/A
Sub: RNH
Ref. [2]
codeLoadThresholdDlSf128 : long, NoNotification

Threshold to be used in the initial AMR rate selection algorithm for selecting SF128 or SF256 based AMR
codec modes in setup of speech requests. Only applicable when establishing an AMR-NB multi-rate RAB.
Unit: % of code load

Resolution: 1
Sub: RNH
Ref. [2]
aseLoadThresholdUlSpeech : AseLoadThresholdUlSpeech, NoNotification

Contains all AseUl threshold values used for AMR rate selection.
Unit: N/A
Resolution: N/A
Sub: RNH
Ref. [2]
pwrLoadThresholdDlSpeech : PwrLoadThresholdDlSpeech, NoNotification

Contains all pwrDl threshold values used for AMR rate selection.
Unit: N/A
Resolution: N/A
Sub: RNH
Ref. [2]
eulNonServingCellUsersAdm : long, NoNotification

Admission threshold for the number of E-DCH users having this cell as non-serving cell.
Unit: 1 E-DCH user

Resolution: 1
Sub: RNH
Ref. [2]
eulServingCellUsersAdm : long, NoNotification

Admission threshold for the number of E-DCH users having this cell as serving cell.
Unit: 1 E-DCH user

Resolution: 1
Sub: RNH
Ref. [2]
Page 60
LOGICAL VIEW REPORT
rateSelectionPsInteractive : RateSelectionPsInteractive, NoNotification

Configuration of preferred rate for PS Interactive RABs
Unit: N/A
Resolution: N/A
Sub: RNH
Ref. [2]
Page 61
LOGICAL VIEW REPORT
accessClassesBarredCs : sequence <BooleanVals,16,nonUnique>, NoNotification

Specifies which access classes are barred for CS.
TRUE (’barred’), otherwise the boolean is set to FALSE (’not barred’). First element represent access class 0.
Unit: N/A
Resolution: N/A
Sub: RNH
Ref. [2]
accessClassesBarredPs : sequence <BooleanVals,16,nonUnique>, NoNotification

Specifies which access classes are barred for PS.
TRUE (’barred’), otherwise the boolean is set to FALSE (’not barred’). First element represent access class 0.
Unit: N/A
Resolution: N/A
Sub: RNH
Ref. [2]
hcsUsage : HcsUsage, NoNotification

Specifies the Information Elements "Use of HCS" in System Information Blocks 11 and 12.
Unit: N/A
Resolution: N/A
Sub: RNH
Ref. [2]
hcsSib3Config : HcsSib3Config, NoNotification

Specifies the Hierachical Cell Structure Information Elements in System Information Block 3.
Unit: N/A
Resolution: N/A
Sub: RNH
Ref. [2]
amrWbRateDlMax : long, NoNotification

Maximum AMR-WB rate to be used in DL in the AMR-WB rate selection algorithm for selecting the maximum
rate at setup of an AMR-WB RAB.
Only applicable for requests including AMR-WB.
Unit: 1 bit/s
Resolution: N/A
Sub: RNH
Ref. [2]
amrWbRateUlMax : long, NoNotification

Maximum AMR-WB rate to be used in UL in the AMR-WB rate selection algorithm for selecting the maximum
rate at setup of an AMR-WB RAB.
Only applicable for requests including AMR-WB.
Page 62
LOGICAL VIEW REPORT
Unit: 1 bit/s
Resolution: N/A
Sub: RNH
Ref. [2]
cellBroadcastSac : long, NoNotification

Cell Broadcast Service Area Code within a location area.
Special values:
Not defined is indicated by the value -1.
Change takes effect: Immediately
Sub: RNH
Ref. [2]
ctchOccasionPeriod : long, NoNotification

Period of CTCH allocations on S-CCPCH.
The CTCH occasions are identified by the first radio frame of the TTI that can contain CTCH data. The CTCH
occasions are fixed on the system frame number cycle 0 .. 4095 (i.e. no modulo calculation) and thus repeated
cyclically.
The CTCH occasions are calculated as follows:
SFN = m * ctchOccasionPeriod; m= 1, ..., M
M * ctchOccasionPeriod <= 4095
Unit: 10 ms
Change takes effect: Object disabled/enabled
Disturbances:
Changing this attribute may affect ongoing traffic.
Whenever its value is set, the cell is disabled automatically and then re-enabled.
Sub: RNH
Ref. [2]
amrNbSelector : SupportedAmrNbModes, NoNotification

Defines whether AMR-NB single-rate or AMR-NB multi-rate should be supported in the cell. If any of the cells
in the active set is configured to SINGLE_RATE, AMR-NB single-rate will be selected.
Sub: RNH
Ref. [2]
standAloneSrbSelector : SupportedStandaloneSrbRates, NoNotification

Defines whether SRB 3.4 or SRB 13.6 should be used as Stand-alone SRB in this cell. If any of the cells in the
active set is configured to SRB34, SRB 3.4/3.4 will be selected.
Sub: RNH
Ref. [2]
eulServingCellUsersAdmTti2 : long, NoNotification

Admission threshold for the number of 2 ms TTI E-DCH users having this cell as serving cell. Applicable at
serving cell change, at RAB establishment and at reconfiguration to EUL.
Unit: 1 E-DCH user

Change takes effect: Immediately
Dependencies: If the value of this parameter is greater than the value of eulServingCellUsersAdm, then this
parameter will have no effect.
Sub: RNH
Ref. [2]
Page 63
LOGICAL VIEW REPORT
Data Types, Definitions and Exceptions

SupportedMeasQuantities
Attributes:
CPICH_RSCP : long = 1
CPICH_EC_NO : long = 2
SupportedReservedStates
Attributes:
RESERVED : long = 0
NOT_RESERVED : long = 1
RANOS_SUPPORT_APPLICATION_MODEL_E
This MIM contains classes for network support functions on a Sub-network level.
LogFilter
LogFilter
This Managed Object represents configurable parameters of the RANOS log filters.
Several instances may exist.
Attributes:
Sub: EQH
Ref. [12]
filterParam : sequence <LogFilterParameters>, Mandatory, NoNotification

Configurable parameter types and values.
Sub: EQH
Ref. [12]
Operations:
create () :
This Managed Object is introduced with the create operation when a log new filter is needed.
delete () :
This Managed Object is removed with the delete operation when the log filter is not needed any more.
Page 64
LOGICAL VIEW REPORT
SupportApplication
SupportApplication
SystemCreated
This MO Type represents the Support Application and is the root object of the Support
Application MIB. Only one instance of the MO Type can exist per Support Application
MIB.
Attributes:
Sub: EQH, CMS
Ref. [7]
UserPreferences
UserPreferences
This MO Type represents the WRAN CM Explorer preferences saved for users. As every
user can save their preferences for WRAN CM Explorer, several instances of the MO
Type can exist.
Attributes:
Sub: RAH
Ref. [7]
userId : string, Mandatory, NoNotification

Identifies the user to whom the preferences apply.
Sub: RAH
Ref. [7]
preferences : sequence <UserPreferencesParameters>, Mandatory, NoNotification

Configurable preference names and values.
Sub: RAH
Ref. [7]
Page 65
LOGICAL VIEW REPORT
Operations:
create () : boolean
This MO is created by a create operation the first time a user saves their WRAN CM Explorer preferences.
delete () : boolean
This MO is deleted with a delete operation when it is necessary to remove details specific to the user identified
by the userId attribute or when the user identified by the userId attribute decides to reset all possible user
preferences to their default values.
PLANNEDCONFIG_APPLICATION_MODEL
This MIM captures the 'Activation scheme' for a planned configuration. It is also used to
record break point information in a plan.
BreakPoint
Models a breakpoint in the planned configuration.
Attributes:
reached : BooleanVals, Default = FALSE, NoNotification
Indicates whether the breakpoint is valid or not. Once a breakpoint has been reached the value is set to TRUE.
Initial value is FALSE.
Sub: PCA, RNR
timestamp : longlong, Mandatory, NoNotification

The timestamp information (with nanosecond precision) in the breakpoint. It is used by PCA activation to fetch
and execute planned actions less than or equal to the timestamp of the breakpoint. On reaching a breakpoint the
plan activation will stop.
Sub: PCA, RNR
breakPointName : string, Mandatory, NoNotification, LengthRange = 0..25

Name of the breakpoint.
Sub: PCA, RNR
description : string, NoNotification, LengthRange = 0..256

Description of the breakpoint.
Sub: PCA, RNR
PlannedAreaProperties
Planned Area Properties.
There is an instance of this MO for each planned area in the system. It captures the
activation scheme and breakpoints (if any) associated with the planned configuration. It
indicates whether a plan is partly activated and the timestamp of the last commit.
Page 66
LOGICAL VIEW REPORT
Attributes:
plannedConfigurationName : string, Mandatory, NoNotification, Restricted
Planned Configuration name.
Sub: PCA
activationScheme : ActivationScheme, Default = DEFAULT, NoNotification

Indicates the Activation scheme attached to the plan.
Initial value is DEFAULT.
DEFAULT= 0
INTRA_MIB_ORDERING = 1
INTER_MIB_ORDERING = 2
Sub: PCA
partlyActivated : BooleanVals, Default = FALSE, NoNotification

Indicates if the activation is realised partly for the plan.
Sub: PCA
activationLastCommitRecord : sequence<LastCommit>, NoNotification

Record of last commit time (in ns) of activation elements set and used by the activation algorithms.
Sub: PCA
activationInformationRecord : sequence<ActivationInformation>, NoNotification

A record of activation related information items.
Sub: PCA
overallActivationStatus : ActivationState, Default = NOT_STARTED, NoNotification

Activation status of the planned configuration.
Initial value is NOT_STARTED.

NOT_STARTED = 0
IN_PROGRESS = 1
PARTLY_REALIZED = 2,
FAILED = 3,
COMPLETE = 4,
TERMINATING= 5,
TERMINATED= 6,
SCHEDULED= 7,
TIMED_OUT= 8
Sub: PCA
activationDate : string, NoNotification

Start date and time for the activation. Format: YYYY-MM-DD HH:MM:SS
Sub: PCA
jobID : longlong, NoNotification

CIF AM job id
Sub: PCA
nodeActivationStateRecord : sequence<NodeActivationState>, NoNotification

A record containing planned node name and its activation status.
Sub: PCA
Page 67
LOGICAL VIEW REPORT
abortAtPreCheckFailure : BooleanVals, Default = FALSE, NoNotification

Indicates that the activation will not being if there any pre-check failures in the plan. This attribute will be used
only activations that are scheduled.
Sub: PCA
PlannedConfigurationApp
Planned Configuration Application.
Only one instance of the MO Type can exist per MIB.
Attributes:

ActivationInformation
Attributes:
activationInfoKey : string
Activation information item key.
activationInfoValue : string
Activation information item value.
ActivationScheme
Activation Scheme.
Attributes:
DEFAULT : long = 0
INTRA_MIB_ORDERING : long = 1
INTER_MIB_ORDERING : long = 2
ActivationState
Activation states that a planned configuration can be in.
Attributes:
NOT_STARTED : long = 0
IN_PROGRESS : long = 1
PARTLY_REALIZED : long = 2
FAILED : long = 3
COMPLETE : long = 4
TERMINATING : long = 5
TERMINATED : long = 6
SCHEDULED : long = 7
TIMED_OUT : long = 8
Page 68
LOGICAL VIEW REPORT
LastCommit
Attributes:
commitElement : string
Activation element (Plan or MIB) for which last commit time is recorded.
commitTime : longlong
Last commit time (in ns) set and used by the activation algorithms.
NodeActivationState
Attributes:
mibRootFDN : string
FDN of MIB root.
activationState : NodesActivationState, Default = NOT_STARTED

Current activation state of MIB.
Initial value is NOT_STARTED.

NOT_STARTED = 0
QUEUED = 1
IN_PROGRESS = 2
COMPLETE = 3,
FAILED = 4,
PARTLY_COMPLETED = 5,
TERMINATED= 6,
NEVER_CONNECTED = 7,
TIMED_OUT= 8
FAILED_PRECHECK=9
NodesActivationState
Activation states that a Node can be in.
Attributes:
NOT_STARTED : long = 0
QUEUED : long = 1
IN_PROGRESS : long = 2
PARTLY_COMPLETED : long = 3
FAILED : long = 4
COMPLETE : long = 5
TERMINATED : long = 6
NEVER_CONNECTED : long = 7
TIMED_OUT : long = 8
FAILED_PRECHECK : long = 9
RANOS_SUBNETWORK_MODEL
Contains information reflecting the sub-network, RNS’s and segments that are available in
UTRAN. It also contains the structure information of all supported network resources and
their functionality.
The radio cells that are controlled by external management systems, for example an external
GSM-OSS system or external WRAN CM system are also reflected in this MIM, i.e. to
support inter-system handover. See figure 6.
In order to achieve a smooth migration into the 3GPP Model, a two level containment for the
SubNetwork MOC has been introduced. The top SubNetwork MOC is the root object of the
Page 69
LOGICAL VIEW REPORT
WRAN CM MOM and represents a UTRAN sub-network (region in P1) whereas the
SubNetwork in the bottom, represents the RNS’s.
The rbsGroup MOC is contained in the bottom SubNetwork MOC, all other classes are
contained in the top SubNetwork level. The Segment MOC is also associated with the bottom
SubNetwork (association marked with the role +rns in figure 6).
The Sub-network MIM contains also different interface agents. All interface agents are
contained in the IRPAgent MOC, see figure 7. The NotificationIRP, AlarmIRP, BasicCmIRP
and BulkCmIRP are standards agents and used for communication with an external network
management system, see ref. [21]. The IRATHOMUTRAN agent is used for modelling i.e
GSM-UTRAN and UTRAN-UTRAN handover.
A site view is depicted in figure 8. Site is used for modelling the network resources deployed
in the same geographical area. SiteAssociation is used for modelling the bidirectional
association between a Site and a NE.
Figure 9 shows a view of the areas model. Areas are groups of Utran cells and can be of
different types in WRAN CM i.e. location, routing and service.
The figure 10 shows a simplified example of Sub-network MIM deployment. The subNet1 is
the top object of a UTRAN sub-network, it contains two Radio Network Subsystems, rns1
and rns2. Both RNS’s belongs to the segment1. The relationship between rns1, rns2 and
segment1 are realized using reference attributes.
Note that the rbsGroup objects are contained in the bottom object (rns1 and rns2).
AlarmIRP
AlarmIRP
This MO models the functionality of an alarm IRP agent see ref. [26]. Only one instance
of the MO Type can exist per MIB.
Notifications are sent at topology changes (e.g. MO create, delete). See also ref. [21]
Attributes:
irpVersion : sequence <string>, Mandatory, NoNotification
One or more Alarm IRP version entries
Note: For CORBA users, CommonIRPConstDefs::VersionNumberSet, see ref. [28]
Sub: FMS
Ref. [21]
Areas
Areas
SystemCreated
This MO is a container MO for all "Area" MO’s, i.e. Plmn, LocationArea, RoutingArea
and ServiceArea. Only one instance of this MO Type can exist per MIB.
Attributes:
Page 70
LOGICAL VIEW REPORT
AtmLink
AtmLink
This Managed object type represents an interconnection of ATM ports between Network
Elements. Several instances of the Managed Object may exist.
Notifications are sent at topology changes (MO create and delete).
Attributes:
userLabel : string, LengthRange = 0..128
Sub: TNH
Ref. [6]
atmPortNE1Ref : string, Mandatory, NoNotification

Full Distinguished Name of NE1 MeContext MO.
Sub: TNH
Ref. [6]
atmPort1Ref : string, Mandatory, NoNotification

Local Distinguished Name of the ATM port at the endpoint of the link which is terminated in NE1
Sub: TNH
Ref. [6]
atmPortNE2Ref : string, Mandatory, NoNotification

Full Distinguished Name of NE2 MeContext MO.
Sub: TNH
Ref. []
atmPort2Ref : string, Mandatory, NoNotification

Local Distinguished Name of the ATM port at the endpoint of the link which is terminated in NE1
Sub: TNH
Ref. [6]
linkType : SupportedAtmLinkTypes, Mandatory, NoNotification

Indicates whether or not this ATM Link terminates in an RBS.
RBS_LINK = 1
NON_RBS_LINK = 2
Sub: TNH
Ref. []
Page 71
LOGICAL VIEW REPORT
Operations:
Create () :
This Managed Object is created with a create operation when a new ATM link is added to the system.
Delete () :
This Managed object is deleted with a delete operation when a ATM Link is removed from the system.
BulkCmIRP
BulkCmIRP
This MO models the functionality of a Bulk CM IRP agent, see ref. [26]. Only one
instance of the MO Type can exist per MIB.
Attributes:
One or more Bulk CM IRP version entries.
Sub: RAH
Ref. [21]
ExternalGsmCell
ExternalGsmCell
This MO models a cell controlled by an external GSM system.
Several instances of this MO Type can exist per MIB. See also ref. [24]
Notifications are sent at topology changes (e.g. MO create, delete). See also ref. [24].
Note: According to Corba SS, cellIdentity, bcchFrequency, ncc, bcc, lac, rac and racc are
of type "integer".
Naming RULE
Value part of RDN is User-defined.
Recommendation to system user is to assign the same identity as the original cell has.
Page 72
LOGICAL VIEW REPORT
Attributes:
cellIdentity : long, Mandatory, Range = 0..65535
Cell Identity
Note1: For CORBA users, Integer, see ref. [29]
Sub: RNH, I/E, CMS
Ref. [24]

a user friendly (and user assigned) name of the association object
Sub: RNH, I/E, CMS
Ref. [24]
bcchFrequency : long, Mandatory, Range = 0..1023

Absolute radio frequency channel number of the BCCH channel of the GSM cell.
Note: Integer, for CORBA users, see ref. [29]
Sub: RNH, I/E, CMS
Ref. [24]
ncc : long, Mandatory, Range = 0..7

Network Color Code
Sub: RNH, I/E, CMS
Ref. [24]
bcc : long, Mandatory, Range = 0..7

Base Station Color Code
Sub: RNH, I/E, CMS
Ref. [24]
lac : long, Mandatory, Range = 1..65533, 65535

Location Area Code
Sub: RNH, I/E, CMS
Ref. [24]
maxTxPowerUl : long, Default = 100, Range = -50..33, 100

Maximun allowed UL transmitted power in the GSM cell.
Sub: RNH, I/E, CMS
Ref. [2]
qRxLevMin : long, Default = 100, Range = -115..-25, 100

Minimum received GSM level in the GSM cell.
Page 73
LOGICAL VIEW REPORT
Sub: RNH, I/E, CMS
Ref. [2]
individualOffset : long, Default = 0, Range = -50..50

Offset that is used to deal with differences between minimum received GSM level in the cell and the common
value.
Sub: RNH, I/E, CMS
Ref. [2]
parentSystem : ExternalGsmPlmn, Mandatory, Restricted

Reference to ExternalGsmPlmn instance
Sub: RNH, I/E, CMS
Ref. []
mcc : long, Mandatory, Restricted, Range = 0..999

The MCC part of the PLMN identity used in Gsm radio network.
Sub: RNH, I/E, CMS
Ref. [22]
mnc : long, Mandatory, Restricted, Range = 0..999

The MNC part of the PLMN identity used in the radio network
Sub: RNH, I/E, CMS
Ref. [22]
mncLength : long, Mandatory, Restricted, Range = 2..3

Length of the MNC part of the PLMN identity used in Gsm radio network
Sub: RNH, I/E, CMS
Ref. [22]
bandIndicator : SupportedBands, Default = DCS1800

This parameter is used to indicate the frequency of the external GSM cell. The ARFCN is unique for all GSM
bands except the two GSM bands DCS1800 and PCS1900, so the band indicator is needed to disciminate
between the two.
Sub: RNH, I/E, CMS
Ref. [22]
ExternalGsmPlmn
ExternalGsmPlmn
This MO models a neighbouring GSM PLMN. Note that the
plmnid(mcc,mnc,mnclength) of this MO is to be unique with respect to other
Page 74
LOGICAL VIEW REPORT
ExternalGsmPlmn MO's. However it can be the same as the plmnid(mcc,mnc,mnclength)

of a Plmn MO. Multiple instances of this MO Type can exist per MIB.
Notifications are sent at topology changes (e.g. MO create, delete).
Naming RULE
Recommendation to system user is to assign the same identity as the original system it
represents.
Page 75
LOGICAL VIEW REPORT
Attributes:
Sub: RNH, I/E, CMS
Ref.[]
reservedBy : sequence <ExternalGsmCell>, NoNotification, ReadOnly

Sequence of ExternalGsmCell defined in WRAN CM subnetwork MIB which uses the ExternalGsmPlmn
FDN according to [9] and [20]
Sub: CMS
Ref. [ ]
mcc : long, Mandatory, NoNotification, Restricted, Range = 0..999

The MCC part of the PLMN identity used in Gsm radio network.
Sub: RNH, I/E, CMS
Ref. [22]
mnc : long, Mandatory, NoNotification, Restricted, Range = 0..999

The MNC part of the PLMN identity used in the radio network
Sub: RNH, I/E, CMS
Ref. [22]
mncLength : long, Mandatory, NoNotification, Restricted, Range = 2..3

Length of the MNC part of the PLMN identity used in Gsm radio network
Sub: RNH, I/E, CMS
Ref. [22]
aliasPlmnIdentities : sequence <PlmnIdentity>

Sequence of max 30 PlmnIdentities.
Sub: RNH, I/E, CMS
Ref. [ ]
This MO is the root MO for transport information in a viewable (not managed) external
NE.
Page 76
LOGICAL VIEW REPORT
Attributes:
userLabel : string, NoNotification
Sub: TNH
Ref.[]
ExternalUtranCell
ExternalUtranCell
This MO models a cell controlled by an external UTRAN system. Several instances of
this MO Type can exist per MIB. See also ref. [22]
Note: According to Corba SS cId, mcc, mnc, rncId, uarfcnUl , uarfcnDl,

primaryScramblingCode, primaryCpichPower, lac and rac are of type "integer".
Naming RULE
Recommendation to system user is to assign the same identity as the original cell has.
Page 77
LOGICAL VIEW REPORT
Attributes:
A user-friendly (and user assigned) name of the associated object
Sub: RNH, I/E, CMS
Ref. [22]
cId : long, Mandatory, Range = 0..65535

Cid is the identifier of a cell in one RNC
Sub: RNH, I/E, CMS
Ref. [22]
mcc : long, Mandatory, Restricted, Range = 0..999

Mobile Contry Code
The set operation will be rejected if there exists UtranRelation instances
Sub: RNH, I/E, CMS
Ref. [22]
mnc : long, Mandatory, Restricted, Range = 0..999

Mobile Network Code
Sub: RNH, I/E, CMS
Ref. [22]
rncId : long, Mandatory, Restricted, Range = 0..4095

Unique RNC ID for the drift RNC
Sub: RNH, I/E, CMS
Ref. [22]
uarfcnUl : long, Mandatory, Range = 0..16383

The UL UTRA absolute Radio Frequency Radio Channel number, UARFCN
Sub: RNH, I/E, CMS
Ref. [22]
uarfcnDl : long, Mandatory, Range = 0..16383

The DL UTRA absolute Radio Frequency Radio Channel number, UARFCN¨
Page 78
LOGICAL VIEW REPORT
Sub: RNH, I/E, CMS
Ref. [22]
primaryScramblingCode : long, Mandatory, Range = 0..511

The primary DL scrambling code used by the cell
Sub: RNH, I/E, CMS
Ref. [22]
primaryCpichPower : long, Default = 300, Range = -100..500

The power of the primary CPICH channel in the cell
Sub: RNH, I/E, CMS
Ref. [22]
lac : long, Mandatory, Range = 1..65533, 65535

Location Area Code
Sub: RNH, I/E, CMS
Ref. [22]
rac : long, Mandatory, Range = 0..255

Routing Area Code
Sub: RNH, I/E, CMS
Ref. [22]
mncLength : long, Mandatory, Restricted, Range = 2..3

The length of the attribute "mnc"
Sub: RNH, I/E, CMS
Ref. [2]
parentSystem : ExternalUtranPlmn
Reference to ExternalUtranPlmn instance.
Sub: RNH, I/E, CMS
Ref. [22]
individualOffset : long, Default = 0, Range = -100..100

Used in UE function event-reporting. This offset is added to the measured quantity before the UE evaluates if
an event has occured.
-100: -10,0 dB
Page 79
LOGICAL VIEW REPORT
- 95: - 9,5 dB
...
100: 10,0 dB
Resolution: 5 (=0,5 dB)
Sub: RNH, CMS, I/E
Ref. []
maxTxPowerUl : long, Default = 100, Range = -50..33, 100

Used in UE functions for cell selection/reselection in idle mode and connected mode. Also used by UTRAN to
control the maximum TX power level an UE may use. If the current UE uplink transmit power is above the
indicated power value, the UE shall decrease the power to a level below the power value. Value launched by
System information (SIB11) for each intra-frequency measurement object corresponding to adjacent cells of
serving cell. Value launched by System information (SIB3) for serving cell. Unit dBm
Step size is 1dBm.
-50 : -50dBm
-49 : -49dBm
......
33 : 33dBm
100: Default value. The value for the parameter is unspecified by the operator when this value is set. The
parameter will then not be present in SIB11 for this neighbour, the UE will then use the serving cells value
(UtranCell MO value).
Sub: RNH, CMS, I/E
Ref. []
qQualMin : long, Default = 100, Range = -24..0, 100

Used in UE functions for cell selection/reselection in idle mode and connected mode. Minimum required
(acceptable) quality level in the cell (dB).
parameter will then not be present in SIB11 for this neighbour, meaning that the UE will use the serving cells
value (UtranCell MO value).
Sub: RNH, CMS, I/E
Ref. []
qRxLevMin : long, Default = 100, Range = -119..-25, 100

Used in UE functions for cell selection/reselection in idle mode and connected mode. Minimum required
(acceptable) RX level in the cell. (dBm). Value launched by System information (SIB11) for each intra-
frequency measurement object corresponding to adjacent cells of serving cell. Value launched by System
information (SIB3) for serving cell and (SIB11) for adjacent cell. Resolution: 2
parameter will then not be present in SIB11 for this neighbour, the UE will then use the serving cells value
(UtranCell MO value).
Sub: RNH, CMS, I/E
Ref. []
agpsEnabled : BooleanVals, Default = TRUE

Indicates if A-GPS is enabled or not for a cell.
FALSE = 0
TRUE = 1
Unit: N/A
Resolution: N/A
Sub: RNH
Page 80
LOGICAL VIEW REPORT
Ref. [2]
cellCapability : CellCapability
Indicates the capabilities of the inter-RNS cell. Note that if OSS-RC is used, configured value will be subject to
consistency check and may be overridden if inconsistent. In case of Ericsson only system not using OSS-RC, or
multi-vendor system not using OSS-RC operator needs to configure the cell capability of external border cells.
Unit: N/A
Resolution: N/A
Sub: RNH
Ref. [2]
ExternalUtranPlmn
ExternalUtranPlmn
This MO models a neighbouring UTRAN PLMN. Note that the
plmnid(mcc,mnc,mnclength) of this MO is to be unique with respect to other
ExternalUtranPlmn MO's. However it can be the same as the
plmnid(mcc,mnc,mnclength) of a Plmn MO. Multiple instances of this MO Type can
exist per MIB.
Notifications are sent at topology changes (e.g. MO create, delete)
Naming RULE
Recommendation to system user is to assign the same identity as the original system it
represents.
Page 81
LOGICAL VIEW REPORT
Attributes:
Provides support for putting a label on the MO instance
Sub: RNH, I/E, CMS
Ref. []
reservedBy : sequence <ExternalUtranCell>, NoNotification, ReadOnly

Reference to the ExternalUtranCell defined in WRAN CM subnetwork MIB.
Sub: CMS
Ref. []

Mobile Contry Code
Sub: RNH, I/E, CMS
Ref. [22]

Mobile Network Code
Sub: RNH, I/E, CMS
Ref. [22]

Sub: RNH, I/E, CMS
Ref. [2]

Sequence of max 30 PlmnIdentites.
Sub: RNH, I/E, CMS
Ref. [ ]
Page 82
LOGICAL VIEW REPORT
Attributes:
Sub: TNH, I/E, CMS
Ref. []
This MO is the root MO for transport information in a viewable (not managed) external
NE.
Attributes:
Sub: TNH, I/E, CMS
Ref. []
ExternalVplTp
This MO is used to represent the termination of a VP link in a viewable (not managed)
external NE.
Attributes:
Sub: TNH, I/E, CMS
Ref. []
vplTpId : string, NoNotification

Sub: TNH
Ref: []
IRATHOMUTRAN
IRATHOMUTRAN
This MO models the functionality of the IRATHOM interface, UTRAN side. It is used in
UTRAN to GSM and UTRAN to UTRAN handover. See ref. [23]. Only one instance of
the MO Type can exist per MIB.
Page 83
LOGICAL VIEW REPORT
Attributes:
interfaceVersion : string, Mandatory, NoNotification
Version of the interface
Sub: RNH, I/E, CMS
Ref. [23]
versionInformation : sequence <MimInfo>, Mandatory, NoNotification

List of the supported MIM’s and their versions.
Due to UML2XML does not support sequence of sequences, the class MimInfo is introduced.
The MimInfo is a class that has two attributes: mimName that is the name of the supported MIM and
mimVersion that is a sequence of versions of mimName supported by this interface.
MimInfo{ mimName: string, mimVersion: sequence <string>}
Sub: EQH, RNH, I/E, CMS
Ref. [23]
MimInfo
MimInfo is a support MOC and models a MIM and its supported versions.
Note: This MOC is used only for data modelling purposes and does not model any
network resource.
Attributes:
mimName : string, Mandatory, NoNotification
Name of the MIM supported by this interface
mimVersion : sequence <string>, Mandatory, NoNotification

MIM's versions supported by this interface
IRPAgent
IRPAgent
SystemCreated
This MO models the functionality of an IRP agent, see ref. [26]. Only one instance of the
MO Type can exist per MIB.
Attributes:
systemDN : string, Mandatory, NoNotification, Restricted
The Distinguished Name of IRPAgent
Sub: EQH
Ref. [21]
Page 84
LOGICAL VIEW REPORT
Link
Link
Not implemented in Inc3
Attributes:
Sub: EQH
Ref. [7]
linkType : string, NoNotification
Sub: EQH
Ref. [7]
LocationArea
LocationArea
This MO models manageable caracteristics of a Location Area in the subnetwork. A LA
consists of a number of UtranCells and could span over several RNCs. A LA, which
groups a number of UtranCells, is used by UTRAN to page mobiles on request from CS
CN. Several instances of this MO Type can exist.
The maximum number of Location Areas per PLMN is 300.
Naming RULE
The RDN value of LocationArea is set to <lac> by the system as default.
Page 85
LOGICAL VIEW REPORT
Attributes:
Location Area name
Sub: RNH, I/E, CMS
Ref.
lac : long, Mandatory, Restricted, Range = 1..65533, 65535

Location Area code
Sub: RNH, I/E, CMS
Ref. []
t3212 : long, Default = 10, Range = 0..255

Periodic time for LA update 0..255
Sub: RNH, I/E, CMS
Ref.
att : BooleanVals, Default = TRUE

ATT is a flag for attach/detach allowed or not. Some IMSI’s are not allowed in some LA’s.
FALSE = 0 (IMSI attach not allowed)

TRUE = 1
Sub: RNH, I/E, CMS
Ref. []
ManagementNode
ManagementNode
SystemCreated
This MO models the WRAN CM management system. Only one instance of the MO
Type can exist per MIB.
Page 86
LOGICAL VIEW REPORT
Attributes:
A user-friendly name of this object
Sub: EQH
Ref. [21]
vendorName : string, Default = Ericsson, NoNotification, Restricted

The name of the ManagementNode vendor. Defined in XML file
Sub:
Ref. [21]
userDefinedState : string, NoNotification

An operator defined state for operator specific usage
Sub: EQH
Ref. [21]
locationName : string, NoNotification

The physical location of this entity (e.g an address)
Sub: EQH
Ref. [21]
swVersion : string, NoNotification, Restricted

Software version of the managerment node, e.g. R1A, R1B, etc.
Sub: EQH
Ref. [21]
manages : sequence <string>, NoNotification

List of ManagedElement objects
Note: For CORBA users, GenericNRIRPSystem::AttributeTypes::MOReferenceSet, see ref. [28]
Sub: EQH, RAH
Ref. [21]
MbmsServiceArea
MbmsServiceArea
This MO models manageable caracteristics of an MBMS Service Area in the subnetwork.
The maximum number of Mbms Service Areas per Plmn is 15000.
Naming RULE
The RDN value of MbmsServiceArea is set to <sac> by the system as default.
Page 87
LOGICAL VIEW REPORT
Attributes:
sac : long, Mandatory, Restricted, Range = 0..65535
Service area code
Sub: RNH
Ref. []

Sub: RNH
Ref.
NotificationIRP
NotificationIRP
This MO models the functionality of a notification IRP agent, see ref. [26]. Only one
Attributes:
One or more Notification IRP version entries.
Sub: FMS
Ref [21]
Plmn
Plmn
This MO models a UTRAN PLMN(possibly part of) that is managed by this OSSRC.
Note that the plmnid(mcc,mnc,mnclength) of this MO is to be unique with respect to
other Plmn MO's. However it can be the same as the plmnid(mcc,mnc,mnclength) of a
ExternalUtranPlmn & ExternalGsmPlmn MO's. Up to 10 instances of this MO Type can
exist per MIB.
Page 88
LOGICAL VIEW REPORT
Attributes:
Sub: RNH, I/E, CMS
Ref. []

Mobile Contry Code
Sub: RNH, I/E, CMS
Ref. [22]

Mobile Network Code
Sub: RNH, I/E, CMS
Ref. [22]

Sub: RNH, I/E, CMS
Ref. [22]

Sequence of max 30 PlmnIdentites.
Sub: RNH, I/E, CMS
Ref. [ ]
PmIRP
PmIRP
This MO models the functionality of the Performance Management IRP agent. Only one
Page 89
LOGICAL VIEW REPORT
Attributes:
One or more PM IRP version entries.
Sub: PMS
Ref. []
RbsGroup
RbsGroup
This MO Type models RBS grouping for the purpose of selectively present only a subset
of the RBSs at a time. Several instances of this MO Type can exist per MIB.
Attributes:
Provides support for putting a label on the MO instance. It is used by WRAN CM application to write the
attribute value into the GUI.
Sub: EQH
Ref. [7]
listOfRbs : sequence <string>, NoNotification

References to RBSs that are included in the group.
The attribute consists of a sequence of the full Distinguished Names of the MeContext’s that represent the
associated RBS’s according to [9] and [20].
Sub: EQH
Ref. [7]
RoutingArea
RoutingArea
This MO models manageable caracteristics of a Routing Area in the subnetwork. A RA
consists of a number of UtranCells and could span over several RNCs. A RA, which
groups a number of UtranCells, is used by UTRAN to page mobiles on request from PS
CN. Several instances of this MO Type can exist per Location Area (i.e. 256).
Changing of this parameter can cause that there is a mismatch between CN configuration
and UTRAN configuration until it has been configured in both places.
The maximum number of Routing Areas per Location Area is 1000.
Naming RULE
The RDN value of RoutingArea is set to <rac> by the system as default.
Page 90
LOGICAL VIEW REPORT
Attributes:
Location Area name
Sub: RNH, I/E, CMS
Ref.
rac : long, Mandatory, Restricted, Range = 0..255

Routing area code
Sub: RNH, I/E, CMS
Ref. [22]
nmo : SupportedNetOpModes, Default = MODE_II

Network operation mode that indicates whether the Gs interface between the SGSN and MSC/VLR is installed.
MODE_I = 0
MODE_II = 1
Sub: RNH, I/E, CMS
Ref. [22]
Segment
Segment
SystemCreated, NotificationTypes = notifyObjectCreation, notifyObjectDeletion
This Managed Object type modells a Segment in WRAN CM. It specifies which RNS's
that the segment contains. One instance of this Managed Object type exists per MIB.
Notifications are sent at topology changes (Create and Delete)
Attribute value change notification is sent for attributes connectionStatus and rnsRefs.
ALARMS of Utran Segment.
PMS CONNECTION TO SEGMENT FAILED
Region Server failed failed to connect to PM Interface on Segment Managed Object that
failed to Respond.
The Managed Object generationg this alarm is the FMS Alarm Administration Segment.
Event Type: ET_COMMUNICATIONS_ALARM

Probable Cause: PC_COMMUNICATION_SUBSYSTEM_FAIURE
Persieved Sevirity: MAJOR
Specific Problem: SegmentPMS_CONNECTION_SEGMENT_FAILED
Additional Text:.........
Additional Info..........
PMS SEGMENT VOLUME FULL
Segment Server failed to write PM data due to volume full error.
Event Type: ET_ENVIRONMENTAL_ALARM

Probable Cause: PC_DISK_PROBLEM
Page 91
LOGICAL VIEW REPORT

Specific Problem: SegmentPMS_SEGMENT_VOLUME_FULL
PMS SEGMENT WRITE ACCESS ALARM
Segment Server failed to write data or create directory du to denied file permission.
Event Type: ET_ENVIRONMENTAL_ALARM

Probable Cause: PC_DISK_PROBLEM
Specific Problem: SegmentPMS_SEGMENT_WRITE_ACCESS_ALARM
Page 92
LOGICAL VIEW REPORT
Attributes:
Sub: EQH
Ref. [7]
ipAddress : string, Mandatory, NoNotification

The IP address where the Segment can be reached from a management point of view.
Sub: EQH
Ref. [7]
rnsRefs : sequence<string>
A list of DNs of the SubNetwork MOs for all RNSs associated to the Segment.
The DNs consist of the full Distinguished Names according to [9] and [20].
Sub: EQH
Ref. [7]
pmStorageDirectory : string, Mandatory, NoNotification

Path to PMS storage directory on Segment.
Sub: PMS
Ref. [7]
connectionStatus : SupportedConnStatus, Default = NEVER_CONNECTED

Status of the instance.
"NeverConnected" is set at instance creation, after that the value is controlled by FMS. "Connected" is set to
indicate that the Segment is connected. If connection with the Segment is lost, "Disconnected" is set.
NEVER_CONNECTED = 1
CONNECTED = 2
DISCONNECTED = 3
Sub: FMS
Ref. [7]
ServiceArea
ServiceArea
This MO models manageable caracteristics of a Service Area in the subnetwork. A SA
consists of a number of UtranCells and could span over several RNCs. A SA, which
groups a number of UtranCells, is used by UTRAN to indicate the location of a mobile to
the CN. It is also used by the CN to indicate to UTRAN in which area to broadcast CN
information. Several instances of this MO Type can exist per Location Area (i.e. 1500).
The maximum number of Service Areas per Loaction Area is 15000.
Naming RULE
The RDN value of ServiceArea is set to <sac> by the system as default.
Page 93
LOGICAL VIEW REPORT
Attributes:
Location Area name
Sub: RNH
Ref.
sac : long, Mandatory, Restricted, Range = 0..65535

Service area code
Sub: RNH
Ref. []
Site
Site
This MO Type models the physical location of the network resources, e.g RBS’s, RNC’s
and RANAG’s. Resources, deployed in the same geographical area are associated to the
same Site MOC instance. Several instances of this MO Type can exist per MIB.
Page 94
LOGICAL VIEW REPORT
Attributes:
Sub: EQH
Ref. []
location : string, NoNotification

The postal address to a geographical location.
Sub: EQH
Ref. []
latitude : long, Default = 0, NoNotification

The value must be given in seconds and composed by the formula
3600*D + 60*M + S (D: degrees, M: minutes, S: seconds). Positive degree values (0 o - 90 o ) correspond to
north
latitude values whereas negative degree values (-0 o - -90 o ) correspond to south latitude values. The precision
is
0.1 second.
Sub: EQH
Ref. []
longitude : long, Default = 0, NoNotification

The value must be given in seconds and composed by the formula
3600*D + 60*M + S (D: degrees, M: minutes, S: seconds). Positive degree values (0 o - 180 o ) correspond to
east longitude
values.
Negative degree values (-0 o - -180 o ) correspond to west longitude values.
The precision is 0.1 second.
Sub: EQH
Ref. []
altitude : short, Default = 0, NoNotification

Positive values represents meter above the ground whereas negative represents meters below the ground. The
precision is 0.1 m
Sub: EQH
Ref. []
timeZone : string, Default = UTC, NoNotification

The timeZone the site exists in.
Sub: EQH
Ref.[]
freeText : string, NoNotification

Operator's choice of information
Sub: EQH
Page 95
LOGICAL VIEW REPORT
Ref. []
listOfNe : sequence <string>, NoNotification

List of ManagedElement MO instances that belong this Site.
FDN according [9] and [20]
Sub: EQH
Ref. []
datum : string, Default = wgs84, NoNotification

This gives the geographical information a context.
Sub: EQH
Ref.[]
SubNetwork
SubNetwork
SystemCreated, NotificationTypes = notifyObjectCreation, notifyObjectDeletion
This MO Type is used to model a sub-network and RNS’s. It is the root object of the
WRAN CM MOM when it represents a sub-network. This MO contains RNS objects that
are of the same class type, see the example in figure 10. MOC’s of type MeContext that
represents RANAG’s are also contained in this MOC.
The Sub-network instance handles several Segment’s and RNS’s. The RNS instance
handles exactly one RNC and several RbsGroups. Several instances of the MO Type can
exist.
The SubNetwork instance will be created automatically by the system.
RNS instances will be created with a create operation when a new Rns is added. One or
several instances are created.
Alarms:
Moved to general alarms chapter.
Naming RULE
SubNetwork [Global]
User-defined in WRAN CM Configuration File
SubNetwork [RNS]
User-defined, taken from MeContext.userLabel of the RNC
Page 96
LOGICAL VIEW REPORT
Attributes:
dnPrefix : string, NoNotification, Restricted
DN Prefix information. Specified only if the instance of the SubNetwork MO is a local root instance of the
MIB, otherwise it is set to NULL, see ref. [9]
Sub: EQH
Ref. [21]

Can be set by EQH in Sub-network and RNS level.
Can be set by RAH in RNS level.
Sub: EQH, RAH
Ref. [21]
userDefinedNetworkType : string, Default = UTRAN, NoNotification

Type of network e.g. UTRAN
For RNS = NULL
Sub: EQH
Ref. [21]
rncRef : string, NoNotification

Reference to the MeContext that represent the associated RNC.
The attribute consists of the FDN of the MeContext according to [9] and [20]. Used only in RNS. For sub-
network = NULL.
Sub: EQH
Ref. [7]
TnApplication
TnApplication
SystemCreated
This MO Type represents the Transport Network Application. Only one instance of the
MOC can exist per SubNetwork MIB.
Attributes:
Sub: EQH, CMS
Ref. [7]
VirtualPath
This MO models the concept of a link between two directly connected nodes, or between
two nodes that are separated by a node that is cross connecting virtual paths in the ATM
layer.
Page 97
LOGICAL VIEW REPORT
Attributes:
Sub: EQH, CMS
Ref. [7]
vplTpARef : string, Mandatory

The FDN of the first virtual path termination point (VplTp MO or ExternalVplTp MO) for this virtual path.
Sub: TNH
Ref: []
vplTpBRef : string, Mandatory

TThe FDN of the second virtual path termination point (VplTp MO or ExternalVplTp MO) for this virtual path.
Sub: TNH
Ref: []
SupportedAtmLinkTypes
Attributes:
RBS_LINK : long = 1
NON_RBS_LINK : long = 2
SupportedAtt
Attributes:
IMSI_ATTACH_NOT_ALLOWED : long = 0
IMSI_ATTACH_ALLOWED : long = 1
SupportedNetOpModes
Attributes:
MODE_I : long = 0
MODE_II : long = 1
SupportedBands
Attributes:
DCS1800 : long = 0
PCS1900 : long = 1
OTHER_BANDS : long = 2
PlmnIdentity
A structure used to hold the identities of PLMN.
Sub: RNH
Ref: []
Page 98
LOGICAL VIEW REPORT
Attributes:
mcc : long, Range = 0..999
mnc : long, Range = 0..999
mncLength : long, Range = 2..3
SupportedServiceCategory
Attributes:
CBR : long = 1
UBR : long = 2
UBR_PLUS : long = 3
CELLO MODEL
Basic Cello Model
BasicManagedElement
BasicManagedElement
NotificationTypes = notifyObjectCreation, notifyObjectDeletion
This MO models a NE functionality, it can be of type RNC, RBS and RANAG.
The WRAN CM specific attributes models the functionality required by the 3GPP
standard, see ref. [21].
Note: BasicManagedElement is a basic MOC. It does not represent any resource in the
network and is used for modelling purposes. NE's shall inherit this class into
ManagedElement MOC's.
3GPP standard attributes shall be modelled here.
ALARMS of ManagedElement
INCOMPATIBLE MIM VERSION MISMATCH

This alarm is raised when WRAN CM cannot change the MIM version of the mirrored
MIB to follow the version of the network element. The current version of the WRAN CM
mirrored MIB is incompatible with the network element version why the network
element cannot be managed by WRAN CM.
The reason for the alarm can be either that the MIM version is unknown to WRAN CM
or, for an RBS, that a MIB change is inhibited to protect planned data.
The network element (or WRAN CM) must be upgraded or the network element be
removed and recreated in WRAN CM.
Attribute Value
Event Type ET_EQUIPMENT_ALARM
Probable Cause PC_VERSION_MISMATCH[357]
Perceived Severity MAJOR
Specific Problem ManagedElementINCOMPATIBLE_MIM_VERSION_MISMATCH
Additional Text -
Additional Info -
COMPATIBLE MIM VERSION MISMATCH
Page 99
LOGICAL VIEW REPORT
This alarm is raised when WRAN CM cannot change the MIM version of the mirrored
MIB to follow the version of the network element. The current version of the WRAN CM
mirrored MIB is compatible with the network element version. The network element can
still be managed by WRAN CM.
The reason for the alarm can be either that the MIM version is unknown to WRAN CM
or, for an RBS, that a MIB change is inhibited to protect planned data.
The network element (or WRAN CM) should be upgraded or the network element be
removed and recreated in WRAN CM.
Attribute Value
Perceived Severity WARNING
Specific Problem ManagedElementCOMPATIBLE_MIM_VERSION_MISMATCH
Additional Text -
Additional Info -
PMS SEGMENT NE CONNECT ALARM

Segment Server failed to connect to Performance Management interface on NE.
Attribute Value
Event Type ET_COMMUNICATIONS_ALARM
Probable Cause PC_COMMUNICATIONS_PROTOCOL_ERROR[305]
Specific Problem ManagedElementPMS_SEGMENT_NE_CONNECT_ALARM
Additional Text -
Additional Info -
PMS SEGMENT NE FTP ALARM

Segment Server failed to connect to ftp server on NE.
Attribute Value
Probable Cause PC_COMMUNICATIONS_PROTOCOL_ERROR[305]
Specific Problem ManagedElementPMS_SEGMENT_NE_FTP_ALARM
Additional Text -
Additional Info -
SOFTWARE VERSION MISMATCH

Alarm raised when WRAN CM cannot upgrade an RBS to the software version entered
in the Add RBS Wizard. The RBS cannot be managed by WRAN CM.
The reason for the alarm can be either that the wrong upgrade package information has
been entered or that the upgrade has failed.
The RBS must be upgraded manually or be removed and recreated in WRAN CM.
Attribute Value
Specific Problem ManagedElementSOFTWARE_VERSION_MISMATCH
Additional Text -
Additional Info -
UNSYNCHRONIZED NETWORK ELEMENT
Page 100
LOGICAL VIEW REPORT
This alarm is rised when the synchronization of a NE mirrored MIB fails.

Attribute Value
Probable Cause PC_UNAVAILABLE
Specific Problem ManagedElementUNSYNCHRONIZED_NETWORK_ELEMENT
Additional Text -
Additional Info -
Page 101
LOGICAL VIEW REPORT
Attributes:
dnPrefix : string, Local, NoNotification, Restricted
DN prefix information.
Specified only if the instance of the ManagedElement MO is a local root instance of the MIB, otherwise it is set
to NULL, see ref. [9]
Sub: EQH, RAH
Ref. [21]
managedElementType : string, Local, NoNotification, Restricted

Type of ManagedElement i.e RNC, NodeB see ref. [21] and RANAG (Ericsson specific).
Note: For CORBA users, GenericNRIRPSystem::AttributeTypes::StringSet, see ref. [28]
Sub: EQH, RAH
Ref. [21]
vendorName : string, Default = Ericsson, Local, NoNotification, Restricted

Name of the ManagedElement vendor i.e. Ericsson.
Sub: -
Ref. [21]
locationName : string, Local, NoNotification, Restricted, ApplicationTag = site

The physical location of this entity (e.g. an address)
This attribute is mapped to ManagedElement.site in Cello MIB.
Sub: CMS
Ref. []
userDefinedState : string, Local, NoNotification

Operator defined state for operator specific use.
Sub: EQH, RAH
Ref. [21]
swVersion : string, Local, NoNotification, Restricted

The software version of the Managed Node.
Retrieved from ConfigurationVersion.currentUpgradePackage(UpgradePackage.administrativeData) in Cello
MO’s.
Concatenation of productNumber and productRevision in AdminProductData MO.
Sub: CMS
Ref. [21]
managedBy : string, Local, NoNotification, Restricted

The management node that manages this NE.
Full Distinguished Name of the ManagementNode according to [9] and [20].
Sub: EQH, RAH
Page 102
LOGICAL VIEW REPORT
Ref. [21]
sourceType : string, Default = Cello, Local, NoNotification, Restricted

Information about on what platform the network element is running on, i.e. Cello, AXE
Sub: EQH
Ref. []
release : string, Default = P7.0, Local, NoNotification, Restricted

Denotes the latest release which this managed element supports, e.g. P7.0
Sub: -
Ref. []
siteRef : string, Local

FDN of the Site MO instance this ManagedElement belongs to
Sub: EQH
Ref. []
Cello Attributes mirrored in WRAN CM

This package contains the Cello MOC's having attributes that are persistently stored in
WRAN CM.
There is no XML SW code generation for these attributes.
Making these attributes persistent is outside of the scope of this document.
Aal0TpVccTp
Valid for: RBS, RNC.
Attributes:
userLabel, NoNotification
processorId, NoNotification
reservedBy, NoNotification
vclTpId, Mandatory
alarmReport, NoNotification
continuityCheck, NoNotification
nomPmBlkSize, NoNotification
counterMode
counterActivation
[PersistInMirror: P5 onwards]
Aal1TpVccTp
Valid for: All nodes.
Page 103
LOGICAL VIEW REPORT
Attributes:
userLabel
cdvt, NoNotification
continuityCheck
counterMode
ds0BundleId, NoNotification
nomPmBlockSize
vclTpId, Mandatory
partialFill, NoNotification
counterActivation
Aal2Ap
Attributes:
timerErq, NoNotification
timerRel, NoNotification
sigLinkId, NoNotification
secondarySigLinkId, NoNotification
rpuId, NoNotification
reservedBy
aal2QoSCodePointProfileId
allocationMode, NoNotification
Aal2PathDistributionUnit
Attributes:
aal2PathVccTpList, NoNotification
Aal2PathVccTp
Attributes:
vclTpId, Mandatory
administrativeState, NoNotification
reservedBy
counterMode
nomPmBlocksize, NoNotification
timerCu, NoNotification
aal2PathId, NoNotification
aal2PathOwner, NoNotification
aal2QoSAvailableProfiles
aal2QoSProfileId, NoNotification
aal2CacWp
muxResourceId
counterActivation
Page 104
LOGICAL VIEW REPORT
Aal2QoSCodePointProfile
Attributes:
userLabel
qualityOfServiceCodePointA, NoNotification
qualityOfServiceCodePointB, NoNotification
qualityOfServiceCodePointC, NoNotification
qualityOfServiceCodePointD, NoNotification
Aal2QoSProfile
Attributes:
userLabel
profileClassA, NoNotification
profileClassB, NoNotification
profileClassC, NoNotification
profileClassD, NoNotification
Aal2RoutingCase
Attributes:
numberDirection, NoNotification
routeList
routePriorityList
Aal2Sp
Attributes:
a2ea, NoNotification
Aal5TpVccTp
Attributes:
processorId, NoNotification
vclTpId, Mandatory
fromUserMaxSduSize, NoNotification
toUserMaxSduSize, NoNotification
counterMode
counterActivation
Page 105
LOGICAL VIEW REPORT
AtmConfService
Asynchronous Transfer Mode (ATM) Configuration Service

Attributes:
AtmCrossConnection
Attributes:
vclTpAId, NoNotification
vclTpBId, NoNotification
AtmPort
Naming RULE
The RDN value is set by the system to:
<Subrack>-<Slot>-<Line No>*[-SubLineNo]**
*) lineNo: for multiple physical ports per ATM port (in case of IMA), the <lineNo> shall
be the name of the ImaGroup it is connected with.
**) subLineNo: only applicable in case an ATM port is connected with a logical interface
in case of channelization (e.g. a 155 Mbits/s physical interface configured to provide 63
logical E1=2Mbits/s interfaces as supported by ET-MC41).
Example: AtmPort=MS-16-1 or AtmPort=ES1-25-3
Attributes:
physPathTermId, NoNotification
uses, Mandatory, NoNotification
hecCorrectionMode, NoNotification, Restricted
loopbackDetection, NoNotification
AtmTrafficDescriptor
Page 106
LOGICAL VIEW REPORT
Attributes:
ingressAtmPcr, NoNotification
ingressAtmQos, NoNotification
egressAtmPcr, NoNotification
egressAtmQos, NoNotification
egressAtmMcr, NoNotification
ingressAtmMcr, NoNotification
serviceCategory, NoNotification
packetDiscard, NoNotification, Restricted
Cbu
Valid for: RBS only.
Container MOC.
Attributes:
ConfigurationVersion
Attributes:
currentUpgradePackage, NoNotification
Dhcp
Attributes:
dhcpServerAddresses, NoNotification, ReadOnly
Ds0Bundle
Attributes:
listOfTimeSlots, Mandatory, NoNotification, Restricted
tdmMode, Mandatory, NoNotification, Restricted
E1PhysPathTerm
Page 107
LOGICAL VIEW REPORT
Attributes:
lineNo, Mandatory, NoNotification, Restricted
loopback, NoNotification
crc4Mode, NoNotification
idlePattern, NoNotification
degDegM, NoNotification
degDegThr, NoNotification
rdiReporting, NoNotification
aisReporting, NoNotification
shutDownTimeout, NoNotification
E1Ttp
Attributes:
crc4Mode, NoNotification
E3PhysPathTerm
Attributes:
Equipment
Attributes:
EthernetLink
Page 108
LOGICAL VIEW REPORT
Attributes:
userLabel
ipAddress
subnetMask
broadcastAddress, Mandatory
macAddress
mtuSize, NoNotification
metric
interfaceName, NoNotification
EthernetSwitch
Attributes:
enableVlan, NoNotification
pbitQueueMap, NoNotification
untaggedIngressPriority, NoNotification
untaggedIngressVid, NoNotification
vlanMembership, NoNotification
macAddress, NoNotification, ReadOnly
EthernetSwitchFabric
Valid for: RNC.
Attributes:
EthernetSwitchModule
Valid for: RNC.
Attributes:
backPlanePortState, NoNotification, ReadOnly
EthernetSwitchModulePort
Valid for: RNC.
Attributes:
egressUntagVlanRef, NoNotification
externalPort, NoNotification
operatingMode, NoNotification
portNo, Mandatory, NoNotification, Restricted
untaggedIngressVlanRef, NoNotification
vlanRef, NoNotification
Page 109
LOGICAL VIEW REPORT
EthernetSwitchPort
Attributes:
ingressPeakBitrate, NoNotification
operatingMode, Mandatory, NoNotification
portNo, Mandatory, NoNotification, Restricted
systemPort, NoNotification
untaggedIngressVid, NoNotification
vlanMembership, NoNotification
actualSpeedDuplex, NoNotification, ReadOnly
sfpInformation, NoNotification, ReadOnly
sfpPort, NoNotification, ReadOnly
EtMfg
[PersistInMirror: P5, P6, P6FP]
Attributes:
Etm1
Attributes:
boardConfig, NoNotification
ExchangeTerminal
Container MOC.
Attributes:
description, NoNotification
ExchangeTerminalIp
Attributes:
FastEthernet
Page 110
LOGICAL VIEW REPORT
Attributes:
defaultRouter, Mandatory, NoNotification
mtu, NoNotification
networkPrefixLength, Mandatory, NoNotification, Restricted
macAddress, ReadOnly
subnet, ReadOnly
GeneralProcessorUnit
Attributes:
GigaBitEthernet
Attributes:
userLabel
dscpPbitMap, Restricted
autoNegotiation, NoNotification
frameFormat
primaryLink
protectiveMode, NoNotification
statePropagationDelay, NoNotification
switchBackTimer, NoNotification
macAddressLink1, ReadOnly
macAddressLink2, ReadOnly
linkType, NoNotification, Restricted
HgTtp
Container MOC. Needed for Ds0Bundle.
Attributes:
ImaGroup
Attributes:
physicalPortList, Mandatory, NoNotification
requiredNumberOfLinks
activeLinks, NoNotification, ReadOnly
[PersistInMirror: P5, P6]
Page 111
LOGICAL VIEW REPORT
ImaLink
Attributes:
userLabel
uses, Mandatory, NoNotification, Restricted
InternalEthernetPort
Attributes:
dscpPbitMap, NoNotification, Restricted
ethernetSwitchRef, Mandatory, NoNotification, Restricted
frameFormat, NoNotification
Ip
Attributes:
userLabel
isRecursiveSearch, NoNotification
isSubDomainName, NoNotification
dnsServer
retransInterval
noOfRetrans
isDefDomainName
defDomainName
useHostFile
dscp
icmpRedirect
udpChecksumState
connectionAttemptTimer
maxRetransmissionAttempts
workingMode, Mandatory
dnsServerAddresses, NoNotification
IpAccessAutoConfig
Valid for: RNC.
Attributes:
userLabel
nrOfUnusedAdresses
totalNrOfAddresses
minIpAddress, Mandatory, NoNotification, Restricted
maxIpAddress, Mandatory, NoNotification, Restricted
IpAccessHostEt
Page 112
LOGICAL VIEW REPORT
Attributes:
ipAddress, Mandatory
ipDefaultTtl, NoNotification
ipInterfaceMoRef, Mandatory, NoNotification, Restricted
ntpServerMode
ntpDscp, NoNotification
IpAccessHostGpb
Valid for: RNC, RBS.
Attributes:
userLabel
generalProcessorUnitId, Mandatory, NoNotification, Restricted
autoConfig, NoNotification, Restricted
autoConfigIdentity, NoNotification, Restricted
autoConfigIdentity2, NoNotification, Restricted
ipAddress1
ipAddress2
ipDefaultTtl
ipReasmTimeout
interface1, Mandatory, NoNotification, Restricted
interface2, NoNotification, Restricted
IpAccessHostSpb
Valid for: RNC.
Attributes:
userLabel
autoConfig, NoNotification, Restricted
autoConfigIdentity, NoNotification, Restricted
spmId, Mandatory, NoNotification, Restricted
ipAddress
ipInterface, Mandatory, Restricted
ipDefaultTtl
ipReasmTimeout
autoConfigIdentity2, NoNotification, Restricted
interface2, NoNotification, Restricted
ipAddress2
IpAccessSctp
Attributes:
ipAccessHostEtRef1, Mandatory, NoNotification
ipAccessHostEtRef2, Mandatory, NoNotification
Page 113
LOGICAL VIEW REPORT
IpAtmLink
Attributes:
userLabel
interfaceName, NoNotification
ipAddress
subnetMask
metric
monitor
monitorInterval
monitorRetries
mtuSize
aal5TpVccTpId, Mandatory, NoNotification, Restricted
IpInterface
Attributes:
userLabel
vid
vLan
rps
mtu
networkPrefixLength, Mandatory, Restricted
defaultRouter0, Mandatory
defaultRouter1
defaultRouter2
defaultRouterPingInterval
maxWaitForPingReply
maxNoOfFailedPings
noOfPingsBeforeOk
switchBackTimer
ownIpAddressActive, Restricted
ownIpAddressPassive, Restricted
subnet
trafficType, NoNotification
vlanRef, NoNotification
IpOam
Required for: Internet Protocol (IP) for Operation and Maintenance (O&M)
This MO constitutes the top structure level for MOs in IP for O&M.
Attributes:
userLabel
Page 114
LOGICAL VIEW REPORT
IpRoutingTable
Attributes:
userLabel
indexOfDeletableStaticRoutes, NoNotification
staticRoutes, NoNotification, ReadOnly
IpSyncRef
Attributes:
cachedIpAddress, NoNotification, ReadOnly
ntpServerIpAddress
IpSystem
Required for: Ip.
Attributes:
UserLabel
J1PhysPathTerm
Attributes:
physicalLineType, NoNotification
degThreshold, NoNotification
Licensing
Valid for: RNC.
Container MOC.
Attributes:
Page 115
LOGICAL VIEW REPORT
M3uAssociation
Valid for: RNC.
Attributes:
userLabel
role, NoNotification, Restricted
mtp3bSrsId, NoNotification
sctpId, NoNotification
dscp, NoNotification
associationState, NoNotification
localIpMask, NoNotification
localPortNumber, NoNotification, Restricted
autoStartAssociation, NoNotification
remotePortNumber, NoNotification
remoteIpAddress1, NoNotification
remoteIpAddress2, NoNotification
ManagedElement
Attributes:
userLabel
logicalName, NoNotification
productType, NoNotification
productName, NoNotification
productNumber, NoNotification
productRevision, NoNotification
Page 116
LOGICAL VIEW REPORT
Derived from BasicManagedElement

Attributes:
Sub: EQH, RAH
Ref. [21]

Sub: EQH, RAH
Ref. [21]

Sub: -
Ref. [21]

Sub: CMS
Ref. []

Sub: EQH, RAH
Ref. [21]

MO’s.
Sub: CMS
Ref. [21]

Page 117
LOGICAL VIEW REPORT
Sub: EQH, RAH
Ref. [21]

Sub: EQH
Ref. []

Sub: -
Ref. []

Sub: EQH
Ref. []
ManagedElementData
Attributes:
documentServerAddress
logonServerAddress
dhcpServerAddresses
ntpServerAddressPrimary
ntpServerAddressSecondary
performanceDataVolume
[PersistInMirror: P5]
MediumAccessUnit
Attributes:
connectorLabel, NoNotification, Restricted
Mspg
Page 118
LOGICAL VIEW REPORT
Attributes:
degCauseMsp, NoNotification
os155SpiStandbyId, Mandatory, NoNotification, Restricted
os155SpiWorkingId, Mandatory, NoNotification, Restricted
lockout, NoNotification
rdiSecondarySf, NoNotification
MspgExtended
Attributes:
bidirectional, Mandatory, NoNotification
os155SpiProtectionRef, Mandatory, NoNotification, Restricted
os155SpiWorkingRef, Mandatory, NoNotification, Restricted
revertive, NoNotification
waitToRestoreTime, NoNotification
Mtp3bAp
Valid for: RNC.
Attributes:
userLabel
routeSetId, NoNotification
serviceInd, NoNotification
Mtp3bSlAnsi
Valid for: RNC.
Attributes:
userLabel
autoStartLink, NoNotification
linkState, NoNotification
proceduralState, NoNotification
signLinkCode, NoNotification
tpId, NoNotification
usageState, NoNotification
Mtp3bSlChina
Valid for: RNC.
Attributes:
userLabel
prioBeforeSio
Page 119
LOGICAL VIEW REPORT
Mtp3bSlItu
Valid for: RNC.
Attributes:
userLabel
prioBeforeSio
Mtp3bSls
Valid for: RNC.
Attributes:
userLabel
mtp3bSrsId, NoNotification
periodicLinkTestFlag, NoNotification
cLinkAnsi, NoNotification
Mtp3bSlTtc
Valid for: RNC.
Attributes:
userLabel
prioBeforeSio
Mtp3bSpAnsi
Valid for: RNC.
Page 120
LOGICAL VIEW REPORT
Attributes:
userLabel
m3uaNoOfAttempsOfDauds
maxSizeChangeBuf
maxSizeReroutBuf
networkInd, NoNotification
nodeBehaviour, NoNotification
noOfAttempsOfAssociationEstablishment
noOfCongestLevelForNI
resendTfcInterval
spTimer
routeSetCongestTestFlag
sendSltmBefLink
signallingPointCode, NoNotification
sioSpare
spPriority
statusIndInterval
testPatternSltm
transFrHandler
modifiedSlsRotation, NoNotification
Mtp3bSpChina
Valid for: RNC.
Attributes:
userLabel
maxSizeChangeBuf
maxSizeReroutBuf
resendTfcInterval
spTimer
sendSltmBefLink
sioSpare
spPriority
statusIndInterval
testPatternSltm
transFrHandler
version
restartType, NoNotification
Mtp3bSpItu
Valid for: RNC.
Page 121
LOGICAL VIEW REPORT
Attributes:
userLabel
maxSizeChangeBuf
maxSizeReroutBuf
resendTfcInterval
spTimer
sendSltmBefLink
sioSpare
spPriority
statusIndInterval
testPatternSltm
transFrHandler
version
Mtp3bSpTtc
Valid for: RNC.
Attributes:
userLabel
maxSizeChangeBuf
maxSizeReroutBuf
resendTfcInterval
spPriority
spTimer, NoNotification
statusIndInterval
testPatternSltm
m3uaNoOfAttempsOfDauds, NoNotification
noOfAttempsOfAssociationEstablishment, NoNotification
spTimerM3ua, NoNotification
Mtp3bSr
Valid for: RNC.
Attributes:
userLabel
linkSetM3uId, NoNotification
priority
Page 122
LOGICAL VIEW REPORT
Mtp3bSrs
Valid for: RNC.
Attributes:
userLabel
autoReroute, NoNotification
congestedLevel, NoNotification
destPointCode, NoNotification
NniSaalProfile
Valid for: RNC.
Attributes:
userLabel
profileData, NoNotification
NniSaalTp
Valid for: RNC.
Attributes:
userLabel
aal5TpVccTpId, NoNotification
maxSduSize, NoNotification
nniSaalProfileId
Os155PhysPathTerm
Attributes:
lineNo, NoNotification
Os155SpiTtp
Attributes:
standardMode, Mandatory, NoNotification, Restricted
muxMode, Mandatory, NoNotification, Restricted
msDegThreshold, NoNotification
msDegM, NoNotification
msRdiReporting, NoNotification
msAisReporting, NoNotification
loopBack, NoNotification
Ospf
Valid for: RNC, RXI.
Page 123
LOGICAL VIEW REPORT
Attributes:
userLabel
ospfRouterId, NoNotification
ospfASBdrRtrStatus, NoNotification
ospfAreaBdrRtrStatus, NoNotification
recoverTopoDb
topoDbStoreInterv
ipMo, Mandatory, NoNotification, Restricted
OspfArea
Attributes:
userLabel
range0, NoNotification
importExternalLsa, NoNotification
stubArea, NoNotification
stubAreaMetricType, NoNotification
sendAreaSummary, NoNotification
stubAreaMetric, NoNotification
areaId, Mandatory, NoNotification, Restricted
areaLsaChecksum, NoNotification, ReadOnly
OspfInterface
Attributes:
userLabel
helloInterval
interfacePriority
interfaceTransitDelay
lsaTransmissionInterval
ospfAreaRelated
relatedLink, NoNotification
routerDeadInterval
PlugInUnit
Attributes:
allowedSeqRestarts, NoNotification
piuGroupNumber, NoNotification
piuType, Mandatory, NoNotification
productType, NoNotification
PmService
Performance Management Service

Page 124
LOGICAL VIEW REPORT
Attributes:
performanceDataVolume
minorAlarmCeasingDelta
warningAlarmLimitPercent
warningAlarmCeasingDelta
ReliableProgramUniter
Attributes:
admActiveSlot, NoNotification
admPassiveSlot, NoNotification
reliableProgramLabel, NoNotification
normalisation, NoNotification
replication, NoNotification, Restricted
switchOver, NoNotification
SccLayer
Valid for: RNC - Cello 3.
Attributes:
sccpSpId, NoNotification
mtp3bSpId, NoNotification
SccpAccountingCriteria
Valid for: RNC.
Attributes:
userLabel
usageType, NoNotification
ssN, NoNotification
countType, NoNotification
globalTitleId, NoNotification
pointerId, NoNotification
SccpAp
Valid for: RNC - Cello 3.
Attributes:
ssN, NoNotification
maxConn, NoNotification
mp3bApId, NoNotification
addressManipulation, NoNotification
SccpApLocal
Valid for: RNC.
Page 125
LOGICAL VIEW REPORT
Attributes:
userLabel
ssN, NoNotification
maxConn, NoNotification
useS1, NoNotification
SccpApRemote
Valid for: RNC.
Attributes:
userLabel
ssN, NoNotification
mtp3bApId, NoNotification
SccpEntitySet
Valid for: RNC.
Attributes:
userLabel
routeIds, NoNotification
newGlobalTitle, NoNotification
newSubSystemNumber, NoNotification
sharingMode, NoNotification
SccpGlobalTitle
Valid for: RNC.
Attributes:
userLabel
addressInformation, NoNotification
encodingScheme, NoNotification
gtIndicator, NoNotification
natureOfAddress, NoNotification
numberingPlan, NoNotification
sccpEntitySetId
translationType, NoNotification
SccpPolicing
Valid for: RNC.
Attributes:
userLabel
originatingMtp3bSpc, NoNotification
destinationMtp3bSpc, NoNotification
originatingSccpSpId, NoNotification
originatingSccpSsn, NoNotification
destinationSccpSpId, NoNotification
destinationSccpSsn, NoNotification
policingGlobalTitle, NoNotification
Page 126
LOGICAL VIEW REPORT
SccpScrc
Valid for: RNC.
Attributes:
userLabel
SccpSp
Valid for: RNC.
Attributes:
userLabel
accountDateFileOutput
accountPeriodFileOutput
accountTimeFileOutput
hopCounterSclc
hopCounterScoc
lowerConnThres
maxRelayedConn, NoNotification
mtp3bSpId, NoNotification
prioGeneral
prioIT
prioRLSD
prioSST
smiValue
swapUDTPointer
tCong
tconnEst
tconnResp
tIar
tIas
tReass
tRel
tStatInfo
upperConnThres
useSCMG
Sctp
Page 127
LOGICAL VIEW REPORT
Attributes:
userLabel
numberOfAssociations, NoNotification
ipAccessHostGpbId, NoNotification
minimumRto
maximumRto
initialRto
rtoAlphaIndex
rtoBetaIndex
validCookieLife
allowedIncrementCookieLife
keyChangePeriod
associationMaxRtx
pathMaxRtx
maxInitialRtrAtt
maxShutDownRtrAtt
heartbeatInterval
heartbeatStatus
maxIncomingStream, NoNotification
maxOutgoingStream, NoNotification
maxUserDataSize
maxUserDataSize
mBuffer
nThreshold
tSack
maxDataSizeIp
initialAdRecWin
intervalOobPkts
intervalLostUser
maxBurst
nPercentage
bundlingActivated
bundlingTimer
rpuId, Mandatory, NoNotification, Restricted
ipAccessSctpRef, NoNotification
Slot
Attributes:
slotNumber, NoNotification
Sts1SpeTtp
Attributes:
aisPReporting, NoNotification
rdiPReporting, NoNotification
timConsequentAction, NoNotification
expectedPathTrace, NoNotification
transmittedPathTrace, NoNotification
Sts3CspeTtp
Page 128
LOGICAL VIEW REPORT
Attributes:
aisPReporting, NoNotification
rdiPReporting, NoNotification
Subrack
Attributes:
subrackPosition, NoNotification
cabinetPosition, NoNotification
SwitchPortStp
Attributes:
actualPathCost, NoNotification, ReadOnly
configuredPathCost, NoNotification
edgePortBpduGuardTimeOut, NoNotification
edgePortMode, NoNotification
manualPathCost, NoNotification
priority, NoNotification
protocolVersion, NoNotification
remoteBridgeId, NoNotification, ReadOnly
rootPathCost, NoNotification, ReadOnly
stpRole, NoNotification, ReadOnly
stpState, NoNotification, ReadOnly
SwitchStp
Attributes:
bridgeForwardDelay, NoNotification
bridgeHelloTime, NoNotification
bridgeId, NoNotification, ReadOnly
bridgeMaxAge, NoNotification
bridgePriority, NoNotification
mode, NoNotification
rootBridgeId, NoNotification, ReadOnly
rootPortNumber, NoNotification, ReadOnly
Page 129
LOGICAL VIEW REPORT
SwManagement
Attributes:
Synchronization
Attributes:
degradationIsFault
syncRefActivity, NoNotification, ReadOnly
syncReference, NoNotification, ReadOnly
syncRefStatus, ReadOnly
systemClockA, NoNotification, ReadOnly
systemClockB, NoNotification, ReadOnly
syncRefPriority, NoNotification, ReadOnly
SystemFunctions
Attributes:
T1PhysPathTerm
Attributes:
transmissionMode, NoNotification
T1Ttp
Attributes:
T3PhysPathTerm
Page 130
LOGICAL VIEW REPORT
Attributes:
TimingUnit
Attributes:
TransportNetwork
Attributes:
TuSyncRef
Attributes:
UniSaalProfile
Attributes:
profileData, NoNotification
UniSaalTp
Attributes:
uniSaalProfileId, Mandatory
aal5TpVccTpId, NoNotification
maxSduSize
UpgradePackage
Attributes:
administrativeData, NoNotification
actionResult, NoNotification
Page 131
LOGICAL VIEW REPORT
Vc12Ttp
Attributes:
vcDegThreshold, NoNotification
vcDegM, NoNotification
tuAisReporting, NoNotification
vcRdiReporting, NoNotification
Vc4Ttp
Attributes:
pathTraceFormat, NoNotification
vcDegThreshold, NoNotification
vcDegM, NoNotification
auAisReporting, NoNotification
vcRdiReporting, NoNotification
VclTp
Attributes:
externalVci, NoNotification
atmTrafficDescriptorId, Mandatory
counterActivation, NoNotification
Vlan
Valid for: RNC.
Attributes:
vid, Mandatory, NoNotification
vlanType, NoNotification, Restricted
VpcTp
Page 132
LOGICAL VIEW REPORT
Attributes:
counterMode
VplTp
Attributes:
atmTrafficDescriptor
externalVpi, NoNotification
availabilityStatus
Vt15Ttp
Attributes:
aisVreporting, NoNotification
rdiVreporting, NoNotification
shutDownTimer, NoNotification
Cello MOs needed for Synch

Managed object classes listed in this package are necessary for the synching of nodes. This is
because they are a parent of, or in the hierarchy above a MO containing persistent attributes
we mirror.
No XML is generated for these MOs.
Jvm
Required for: TNH
Attributes:
MIRRORED MIMs
Following types of Mirrored MIMs are defined: RNC, RANAG and RBS.
The distinguished names of the objects mirrored in the mirrored MIMs are the same as the
names in the real NE MIMs. They are created in runtime by EQH and NEAD when a new NE
is configured in WRAN CM. The model in the mirror contains all Managed Objects of the
Page 133
LOGICAL VIEW REPORT
NEs. The MO structure, i.e. which MOs that exist and their containment relationships are kept
in WRAN CM. Information (attribute values) are either mirrored in WRAN CM (i.e. stored
persistently) or fetched from the NEs when accessed. All NE writable attributes used by
WRAN CM are stored persistently in the Mirrored MIM. When attribute values are stored in
WRAN CM they are kept updated by configuration change notifications from the NEs. Where
the information is fetched from, is transparent to a user accessing the MIM.
The contents of the RNC and RBS MIMs which are mirrored in WRAN CM, are specified in
ref. [2] and ref. [3].
The Managed Objects of the common Cello platform are described in ref. [1].
There are some cases where the properties of attributes may differ between the node MIM and
the mirror MIM maintained in WRAN CM. The normal case is where an attribute is marked
as mandatory in the node MIM but not mandatory in the mirror. This is necessary so that
CMS can set the attribute's value after creation (but only once). Attributes that require this
mismatch in properties include a comment in the mirror MIM to say that "This attribute is
marked as mandatory in the node MIM".
Mirrored MIM name and Version Handling

The NE Mirrored MIM name and version are set within the MIBInfo structure when a
Mirrored MIB is created and are kept up-to-date in the event that the actual NE MIM version
changes at runtime. These values should be read by WRAN CM applications via MCLIB
MetaInfoCache methods. The values comply with the rules in ref. [20].
NE Mirrored MIM name:
<node>_NODE_MODEL, e.g. RBS_NODE_MODEL
NE Mirrored MIM version:
<x>.<y>.<z>.<a>.<b>.<c> where:
x - complete node-MIM branch
y - complete node-MIM vresion
z - complete node-MIM release
a - WRAN CM mirrored model part branch
b - WRAN CM mirrored model part version
c - WRAN CM mirrored model part release
e.g. A.1.3.B.1.0
Note that the branch can step off not only between projects but also between increments.
RANOS_ERBS_MIRROR_MODEL_H
This MIM contains replicas of all managed objects from the ERBS MIM and additional
WRAN CM MOC and attributes that are only part of the ERBS mirrored MIM not the ERBS
MIM. Following Managed Object Type is a WRAN CM local MOC MeContext.
ENodeBFunction
This MOC is the top-object in the radio network view of the ERBS MOM.
It defines the WRAN CM specific attribute that models the functionality required by the
3GPP standard, see ref. [22].
It defines also the attributes that are persistently stored in WRAN CM
For more information see ERBS MIM.
Page 134
LOGICAL VIEW REPORT
Attributes:
userLabel
cellTraceFileSize, NoNotification
totalCellTraceStorageSize, NoNotification
cellTraceHighPrioReserve, NoNotification
totalEventStorageSize, NoNotification
sctpRef, NoNotification
dnsLookupState, NoNotification
dnsLookupTimer, NoNotification
dscpLabel, NoNotification
reEstSctpTimer, NoNotification
noOfS1ResetSendings, NoNotification
cellTraceDataLevel, NoNotification
ERbs Attributes Mirrored in WRAN CM

All ERBS attributes used by WRAN CM are stored persistently in the RANOS mirrored
MIBs. In addition, attributes "reservedBy" needed by WRAN CM are stored persistently.
Value change notifications keep these attributes updated.
AntennaBranch
This MOC models an antenna branch.
It defines the attributes that are persistently stored in WRAN CM

Attributes:
AntennaFeederCable
This MOC models the cable connected to an Antenna Branch.

Attributes:
antennaBranchRef, Mandatory, NoNotification
connectedToObjectARef, Mandatory, NoNotification
dlAttenuation, Mandatory, NoNotification
electricalDlDelay, Mandatory, NoNotification
electricalUlDelay, Mandatory, NoNotification
objectAConnector, Mandatory, NoNotification
ulAttenuation, Mandatory, NoNotification
AntennaUnit
This MOC models an antenna unit.
Page 135
LOGICAL VIEW REPORT
Attributes:
AntennaUnitGroup
This MOC is a container of references to the antenna and antenna near products
(RET/TMA) serving a Sector.
Attributes:
Equipment
Container MOC
Attributes:
EUtranCellFDD
This MOC models a Cell and contains parameters needed by the cell. It also contains
parameters for the mandatory common channels.

Attributes:
cellId, Mandatory, NoNotification, Restricted
earfcndl, Mandatory, NoNotification
earfcnul, Mandatory, NoNotification
frameStartOffset, NoNotification
physicalLayerCellIdGroup, Mandatory, NoNotification
physicalLayerSubCellId, Mandatory, NoNotification
sectorFunctionRef, Mandatory, NoNotification, Restricted
plmnId, NoNotification
tac, NoNotification
RbsConfiguration
This MO is used for the configuration of the RBS done at site. The MO handles
configuration of O&M access, Site Equipment and Licensing. The MO supports
download of configuration files from a remote site or from a Local Craft Terminal (LCT).
It is an MO creating and modifying other MOs.
Page 136
LOGICAL VIEW REPORT
Attributes:
rbsLogicalName, ReadOnly
configFaultReason
progressLevel, ReadOnly
rbsConfigLevel
SectorFunction
This MOC contains parameters for configuration of antenna and antenna near products.
Attributes:
fqBand, NoNotification, ReadOnly
TermPointToMme
Models the MME termination point of an S1 link between the RBS and the MME node.

Attributes:
gUMMEI, NoNotification, ReadOnly
mmeName, NoNotification, ReadOnly
servedPlmnId, NoNotification, ReadOnly
domainName, NoNotification
ipAddress1, NoNotification
ipAddress2, NoNotification
ERbs CPP MOC's containing WRAN CM local attributes

This package contains the CPP MOC that contains WRAN CM specific local attributes. All
CPP MOC's used in ERBS Mirror Model are specializations of the MOC's defined in
Common Local Cello Model.
Note that CPP MOC's and attributes that are general for all NE's MUST be modelled in the
"Basic Cello Model" package.
ManagedElement
This class is inherited from BasicManagedElement.
NOTE1: Functions that are generall for all NE, shall be modelled in
BasicManagedElement MO.
NOTE2: The value of the MeContext.rbsType attribute should have the same value as the
inherited attribute productName when the element is a RBS.
Page 137
LOGICAL VIEW REPORT
NOTE3: The set of possible values for MeContext.rbsType are also applicable for
managedElementType.
Alarms are defined in BasicManagedElement MO

Attributes:
Page 138
LOGICAL VIEW REPORT

Attributes:
Sub: EQH, RAH
Ref. [21]

Sub: EQH, RAH
Ref. [21]

Sub: -
Ref. [21]

Sub: CMS
Ref. []

Sub: EQH, RAH
Ref. [21]

MO’s.
Sub: CMS
Ref. [21]

Page 139
LOGICAL VIEW REPORT
Sub: EQH, RAH
Ref. [21]

Sub: EQH
Ref. []

Sub: -
Ref. []

Sub: EQH
Ref. []

The ManagedElement is a local root MO and it is defined in the NE MIM.
MeContext
MeContext
This MO models an ERBS. One instance of this MO Type can exist per MIB.
This class is inherited from BasicMeContext.
NOTE: Functions that are generall for all NE, shall be modelled in BasicMeContext MO.
Page 140
LOGICAL VIEW REPORT
Attributes:
rbsIubId : long, Default = 0, NoNotification
The identity of the RNC IubLink MO that corresponds to the RBS this MeContext represents. rbsIubId has the
same value as the attribute rbsId in IubLink MO in RNC and Iub MO in RBS.
If the Iub MO presently does not exist, the value must be 0.
Used only in RBS. For RNCand RANAG = -1
Sub: EQH
Ref. [7]
ftpServerRef : string, NoNotification

Set by ADD RBS Wizard.
A reference to an MO describing FTP-server to use for upgrade and installation.
Used only in RBS. For RNC and RANAG= NULL.
Sub: RAH
Ref. [7]
rbsGroupRef : string, NoNotification

Reference to the RbsGroup this MeContext belongs to.
The attribute consists of the FDN of the RbsGroup according to [9] and [20].
Used only in RBS. For RNC and RANAG = NULL.
NOTE: For instances of RBS type, this attribute shall be Mandatory
Sub: RAH, EQH
Ref. [7]
fdnOfRncIubLink : string, NoNotification

FDN of the associated IubLink MO on the RNC. Set to empty if the IubLink MO does not exist
Sub: RNH
Ref. []
synchronisationProgress : long, Default = 0, NoNotification, ReadOnly

Represents the percentage progress of the node being synchronised. Has 0% when the node is not connected or
unsynchronised and 100% when the node is fully synchronised. Has values in between when then node is
synchronising.
The initial value set at create is 0.
Sub: CMS
Ref. [2]
Page 141
LOGICAL VIEW REPORT
Derived from BasicMeContext

Attributes:
DN Prefix information. Specified only if the instance of the MeContext MO is a local root instance of the MIB,
otherwise it is set to NULL, see ref. [9]
Sub: EQH, RAH
Ref. [21]

Provides support for putting a label on the MO instance. It is used by RANOS application to write the attribute
value into the GUI.
For information about allowed characters, see ref. [9].
Sub: EQH
Ref. [7]
ipAddress : string, Default = Set-At-Create, Mandatory

The IP address of the NE. A DNS name according to ref. [33]
Sub: EQH
Ref. [7]
segmentName : string, Mandatory, NoNotification

The segment to which the NE belongs.
Full Distinguished Name of the segment according to [9] and [20].
Sub: EQH
Ref. [7]
mimSwitchPolicy : SupportedMimSwitchPolicy, Mandatory, NoNotification

Defines how version upgrade for a network element and the mirrored MIB shall be handled.
RANOS_FOLLOWS = 1
NO_SWITCH = 2
NE_FOLLOWS = 3
UPGRADE_ATTEMPTED = 4
Sub: EQH
Ref. []
neMIMversion : string, Restricted

The branch and the version of the NE MIM used by this MeContext, <branch>.<version>.<release>, e.g. B.1.0
(NEAD concatenates the branch part of the MIM name and the version).
Sub: CMS
Ref. [7]
compatibilityOfMIMs : boolean, Default = false, Restricted

Indication whether or not the NE MIM is compatible with the NE mirrored MIM version.
Applications should not perform read operations towards incompatible Mirrored MIMs.
Sub: CMS
Page 142
LOGICAL VIEW REPORT
Ref. [7]
connectionStatus : SupportedConnStatus, Default = NEVER_CONNECTED, Restricted

"NeverConnected" is set at instance creation.
"Connected " is set to indicate that RANOS has contact with the Network Element.
"Disconnect" is set to indicate thet RANOS has lost contact with the Network Element.
NEVER_CONNECTED = 1
CONNECTED = 2
DISCONNECTED = 3
Sub: CMS
Ref. [7]
mirrorMIBsynchStatus : SupportedMirrorMibSynchStatus, Default = UNSYNCHRONIZED, Restricted

Indicates whether or not the Mirrored MIB of this RNC is currently being synchronized with the MIB in the
RNC.
Initial value is unsynchronized.
TOPOLOGY = 1
ATTRIBUTE = 2
SYNCHRONIZED = 3
UNSYNCHRONIZED = 4
Sub: CMS
Ref. [7]
mirrorMIBupdateStatus : SupportedMirrorMibUpdateStatus, Default = IDLE, NoNotification

Indicates whether or not the mirrored MIB the mirrored MIB of this RNC is currently being updated with a
planned configuration.
Initial value is idle.
UPDATING = 1
IDLE = 2
Sub: CMS
Ref. [2]
generationCounter : long, Default = -1, NoNotification

Keeps track of notifications received from the RNC.
The initial value set at create is -1.
Sub: CMS
Ref. [2]
neMIMName : string, NoNotification, Restricted

The NE MIM name represented by this MeContext.
<node>_NODE_MODEL (NEAD removes the branch tag received from the node).
Sub: CMS
Ref. [7]
neType : SupportedNeType, Mandatory, NoNotification

The NE type this MeContext represents.
RNC = 1
Page 143
LOGICAL VIEW REPORT
NODEB = 2
RANAG = 3
ENODEB = 4
Ref. [7]
neCreationComplete : boolean, Default = false, NoNotification

Indicates whether or not the creation of an NE has been completed successfully.
Administered by MOAD
Sub: EQH
Ref. [7]
restartWarning : boolean, Default = false

Indicates that the NE this MeContext represesnts is about to restart due to software upgrade or restore of a
backup. Alarms for disconected NE shall be supressed when restartWarning is TRUE.
Sub: EQH
Ref. []
rollbackMirrorMIBname : string, NoNotification

Name of the old NE mirror MIB to be used for rollback during upgrade.
Sub: EQH
Ref. []
neSecurityStatus : string, Mandatory

Indicates whether security is activated on this NE or not.
Allowed string values are:

ON
OFF
Sub:
Ref. []
bcrLastChange : longlong, Default = -1, NoNotification, ReadOnly

OSS time in ms last BCR related notification was
received from the node. Always reset after node synchronisation.
Sub: CMS, BCR
bctLastChange : longlong, Default = -1, NoNotification, ReadOnly

OSS time in ms last BCT related notification was
Sub: CMS, BCT
telisLastChange : longlong, Default = -1, NoNotification, ReadOnly

Number of Telis related notifications received from the node. Always reset after node synchronisation.
Sub: CMS, Telis
Page 144
LOGICAL VIEW REPORT
lostSynchronisation : string, ReadOnly

The time (YYYY-MM-DD HH:MM:SS) when the OSS lost synchronisation with the node. When the node is
synchronised, the value will be SYNCHRONISED
Sub:
Ref. []
nodeStartTime : string, Default = "", NoNotification, ReadOnly

The time (YYYY-MM-DD HH:MM:SS) when the node last started.
Sub:
Ref. []
pendingRestart : boolean, Default = false

Indicates whether or not a node restart is pending.
RANOS_RANAG_MIRROR_MODEL_H
This MIM contains replicas of all managed objects from the RANAG MIM (Cello MIM) and
additional WRAN CM MOC.
The MeContext of RANAG type is contained in a SubNetwork MOC (Region level, role
+subNet in figure 16). Figure 16 shows also the bidirectional associations between
MeContext instances of type RANAG, RNC and RBS (roles: +ranag, +rnc).
MeContext
This MO models a RANAG. One instance of this MO Type can exist per MIB.
Naming RULE
Example: MeContext=GaredeLyon
Page 145
LOGICAL VIEW REPORT
Attributes:
neLinkRelations : sequence <string>, NoNotification
List of the remote NE’s associate d with this NE.
FDN of MeContext instances
Used to model the RANAG-RNC link relations.
Sub: EQH
Ref. []

synchronising.
Sub: CMS
Ref. [2]

Attributes:
Sub: EQH, RAH
Ref. [21]

Sub: EQH
Ref. [7]

Sub: EQH
Ref. [7]

Sub: EQH
Ref. [7]
mimSwitchPolicy : SupportedMimSwitchPolicy, Mandatory

RANOS_FOLLOWS = 1
Page 146
LOGICAL VIEW REPORT
NO_SWITCH = 2
NE_FOLLOWS = 3
Sub: EQH
Ref. []

Sub: CMS
Ref. [7]

Sub: CMS
Ref. [7]

"Connected " is set to indicate that WRAN CM has contact with the Network Element.
"Disconnect" is set to indicate thet WRAN CM has lost contact with the Network Element
NEVER_CONNECTED = 1
CONNECTED = 2
DISCONNECTED = 3
Sub: CMS
Ref. [7]

RNC.
TOPOLOGY = 1
ATTRIBUTE = 2
SYNCHRONIZED = 3
UNSYNCHRONIZED = 4
Sub: CMS
Ref. [7]

UPDATING = 1
IDLE = 2
Sub: CMS
Page 147
LOGICAL VIEW REPORT
Ref. [2]

Sub: CMS
Ref. [2]

Sub: CMS
Ref. [7]

RNC = 1
NODEB = 2
RANAG = 3
ENODEB = 4
Ref. [7]

Sub: EQH
Ref. [7]

Sub: EQH
Ref. []

Sub: EQH
Ref. []


OFF
ON
Sub:
Page 148
LOGICAL VIEW REPORT
Ref. []

Sub: CMS, BCR

Sub: CMS, BCT

Sub: CMS, Telis

Sub:
Ref. []

Sub:
Ref. []

Ranag Cello MOC's containing WRAN CM local attributes

This package contains the Cello MOC that contains WRAN CM specific local attributes. All
Cello MOC's used in Ranag Mirror Model are specializations of the MOC's defined in
Note that Cello MOC's and attributes that are general for all NE's MUST be modelled in the
Aal0TpVccTp
Attributes:
Page 149
LOGICAL VIEW REPORT
Aal2PathVccTp
Attributes:
Aal5TpVccTp
Attributes:
AtmCrossConnection
Attributes:
AtmPort
A WRAN CM specific attribute models which AtmLinks that terminate in this AtmPort.
Two WRAN CM specific attributes that model the transmission equipment that
implements the transmission bearer (e.g. PDH, SDH).
Naming RULE
Attributes:
ManagedElement
NOTE: Functions that are generall for all NE, shall be modelled in
Page 150
LOGICAL VIEW REPORT
Attributes:

Attributes:
Sub: EQH, RAH
Ref. [21]

Sub: EQH, RAH
Ref. [21]

Sub: -
Ref. [21]

Sub: CMS
Ref. []

Sub: EQH, RAH
Ref. [21]

MO’s.
Sub: CMS
Ref. [21]

Page 151
LOGICAL VIEW REPORT
Sub: EQH, RAH
Ref. [21]

Sub: EQH
Ref. []

Sub: -
Ref. []

Sub: EQH
Ref. []
TransportNetwork
Attributes:
VclTp
Attributes:
VpcTp
Attributes:
VplTp
Attributes:
References to MOs in the RANAG Equipment View

When creating UNI-SAAL and AAL0 connections by WRAN CM, the processor/timing unit
identities in the Network Elements where these connections terminate must be set by WRAN
CM at connection creation time.
As identities in P1, WRAN CM uses hardcoded Local Distinguished Name (LDN) values for
the corresponding Managed Objects. These Managed Objects are created at Network Element
installation by their Element Manager (see [14], [15] and [16]):
Page 152
LOGICAL VIEW REPORT
RANOS_RBS_MIRROR_MODEL_H
This MIM contains replicas of all managed objects from the RBS MIM and additional WRAN
CM MOC and attributes that are only part of the RBS mirrored MIM not the RBS MIM
Following Managed Object Type is a WRAN CM local MOC
MeContext
NodeBFunction
This MOC is the top-object in the radio network view of the RBS MOM.
It defines the WRAN CM specific attribute that models the functionality required by the
It defines also the attributes that are persistently stored in WRAN CM.
For more information see RBS MIM, ref [3].
Page 153
LOGICAL VIEW REPORT
Attributes:
nodeBFunctionIubLink : string, Local
Reference to related IubLink instance.
(Iub instance in RBS)
FDN according to [9] and [20].
For CORBA users, GenericNRIRPSystem::AttributeTypes::MOReference, see ref. [29]
Sub: EQH
Ref. [22]
userLabel, Mandatory
Attribute persistently stored in WRAN CM.
toaeDch, Mandatory
Attribute persistently stored in Ranos.
toaeCch, Mandatory
tpcFilterLength, Mandatory, NoNotification

powerUpThreshold, Mandatory, NoNotification

powerDownThreshold, Mandatory, NoNotification

branchDiffAbsTime
branchDiffMeasTime
countersAlarmThreshold
maxNumberOfCounters
steeredHsAllocation, NoNotification
eulNoReschUsers, NoNotification
eulTargetRate, NoNotification
eulMaxShoRate, NoNotification
eulReservedHwBandwidthSchedDataNonServCell, NoNotification
flexibleSchedulerOn, NoNotification
supportOf16qam, NoNotification
Page 154
LOGICAL VIEW REPORT
analogUlAlignIsActive, NoNotification, ReadOnly

eulNonServHwRate, NoNotification
eulSchedulingWeight, NoNotification
mbmsIubEfficiencyOn, NoNotification
[PersistInMirror: P6, P6FP]
nbapDscp, NoNotification
eulLowRate, NoNotification
featureStateStandardizedRet, NoNotification
featureStateStandardizedTma, NoNotification
dlLicFractBbPool2, NoNotification
ulLicFractBbPool2, NoNotification
sharedEquipmentController, NoNotification
featureStateDualStackIub, NoNotification
[PersistInMirror: P6FP onwards]
featureStateEul2msTti, NoNotification
featureState64Qam, NoNotification
featureStateDlPowerControlEul, NoNotification
featureStateMbmsIubEfficiency, NoNotification
featureState16Qam, NoNotification
featureStateHsdpaFlexibleScheduler, NoNotification
featureStateGrake, NoNotification
eulMaxAllowedSchRate, NoNotification
Page 155
LOGICAL VIEW REPORT
MeContext
MeContext
This MO models a RBS. One instance of this MO Type can exist per MIB.
Naming RULE
Attributes:
rbsIubId : long, Default = 0

The identity of the RNC IubLink MO that corresponds to the RBS this MeContext represents. rbsIubId has the
same value as the attribute rbsId in IubLink MO in RNC and Iub MO in RBS.
If the Iub MO presently does not exist, the value must be 0.
Used only in RBS. For RNCand RANAG = -1
Sub: EQH
Ref. [7]
ftpServerRef : string, NoNotification

Set by ADD RBS Wizard.
A reference to an MO describing FTP-server to use for upgrade and installation.
Sub: RAH
Ref. [7]
rbsGroupRef : string, NoNotification

Reference to the RbsGroup this MeContext belongs to.
The attribute consists of the FDN of the RbsGroup according to [9] and [20].
NOTE: For instances of RBS type, this attribute shall be Mandatory
Sub: RAH, EQH
Ref. [7]
Page 156
LOGICAL VIEW REPORT
fdnOfRncIubLink : string
FDN of the associated IubLink MO on the RNC. Set to empty if the IubLink MO does not exist
Sub: RNH, I/E, CMS
Ref. []

synchronising.
Sub: CMS
Ref. [2]
autoIntegration : AutoIntegrated, Default = NO, NoNotification

Specifies if the RBS is to be Auto-Integrated.
The initial value set at create is NO.
Sub: ARW, AIF
Ref. [2]
Page 157
LOGICAL VIEW REPORT

Attributes:
Sub: EQH, RAH
Ref. [21]

Sub: EQH
Ref. [7]

Sub: EQH
Ref. [7]

Sub: EQH
Ref. [7]

RANOS_FOLLOWS = 1
NO_SWITCH = 2
NE_FOLLOWS = 3
Sub: EQH
Ref. []

Sub: CMS
Ref. [7]

Page 158
LOGICAL VIEW REPORT
Sub: CMS
Ref. [7]

NEVER_CONNECTED = 1
CONNECTED = 2
DISCONNECTED = 3
Sub: CMS
Ref. [7]

Indicates whether or not the Mirrored MIB of this RBS is currently being synchronized with the MIB in the
RBS.
TOPOLOGY = 1
ATTRIBUTE = 2
SYNCHRONIZED = 3
UNSYNCHRONIZED = 4
Sub: CMS
Ref. [7]

Indicates whether or not the mirrored MIB the mirrored MIB of this RBS is currently being updated with a
UPDATING = 1
IDLE = 2
Sub: CMS
Ref. [2]

Sub: CMS
Ref. [2]

Sub: CMS
Ref. [7]

Page 159
LOGICAL VIEW REPORT
RNC = 1
NODEB = 2
RANAG = 3
ENODEB = 4
Ref. [7]

Sub: EQH
Ref. [7]

Sub: EQH
Ref. []

Sub: EQH
Ref. []


OFF
ON
Sub:
Ref. []

Sub: CMS, BCR

Sub: CMS, BCT

Page 160
LOGICAL VIEW REPORT
Sub: CMS, Telis

Sub:
Ref. []

Sub:
Ref. []

Rbs Cello MOC's containing WRAN CM local attributes

Cello MOC's used in Rbs Mirror Model are specializations of the MOC's defined in
Aal0TpVccTp
Attributes:
Aal2PathVccTp
Attributes:
Aal5TpVccTp
Attributes:
AtmCrossConnection
Attributes:
AtmPort
Naming RULE
Page 161
LOGICAL VIEW REPORT
Attributes:
ManagedElement
NOTE1: Functions that are generall for all NE, shall be modelled in
NOTE2: The value of the MeContext.rbsType attribute should have the same value as the
inherited attribute productName when the element is a RBS.
NOTE3: The set of possible values for MeContext.rbsType are also applicable for
managedElementType.
Page 162
LOGICAL VIEW REPORT
Attributes:

Attributes:
Sub: EQH, RAH
Ref. [21]

Sub: EQH, RAH
Ref. [21]

Sub: -
Ref. [21]

Sub: CMS
Ref. []

Sub: EQH, RAH
Ref. [21]

MO’s.
Sub: CMS
Ref. [21]

Page 163
LOGICAL VIEW REPORT
Sub: EQH, RAH
Ref. [21]

Sub: EQH
Ref. []

Sub: -
Ref. []

Sub: EQH
Ref. []
TransportNetwork
Attributes:
VclTp
Attributes:
VpcTp
Attributes:
VplTp
Attributes:
Rbs Attributes Mirrored in WRAN CM

All RBS writeable attributes used by WRAN CM are stored persistently in the WRAN CM
mirrored MIBs. In addition, attributes "reservedBy" needed by WRAN CM are stored
persistently. Value change notifications keep these attributes updated.
AntennaBranch
This MOC models an antenna branch.
Page 164
LOGICAL VIEW REPORT
It defines the attributes that are persistently stored in WRAN CM.
Attributes:
branchName, Mandatory, NoNotification

verticalAntennaTilt, Mandatory, NoNotification
mechanicalAntennaTilt, Mandatory, NoNotification
rxBranchUsage, Mandatory, NoNotification
antennaSupervisionThreshold, NoNotification
fqBandHighEdge, Mandatory, NoNotification, Restricted
fqBandLowEdge, Mandatory, NoNotification, Restricted
AntFeederCable
This MOC models an antenna feeder cable
Attributes:
ulAttenuation, Mandatory, NoNotification

electricalDlDelay, Mandatory, NoNotification
electricalUlDelay, Mandatory, NoNotification
antennaBranchRef, Mandatory, NoNotification, Restricted
connectedToObjectARef, Mandatory, NoNotification
objectAConnector, Mandatory, NoNotification
AuxPlugInUnit
Container MOC
Attributes:
Carrier
This MOC models a carrier.
It defines the attributes that are persistently stored in Ranos.
Page 165
LOGICAL VIEW REPORT
Attributes:
frequencyPlane, Mandatory, NoNotification, Restricted

reservedBy, Mandatory, NoNotification
cqiAdjustmentOn
cqiErrors
cqiErrorsAbsent
hsPowerMargin
hsScchMaxCodePower
queueSelectAlgorithm, NoNotification
hsScchMinCodePower, NoNotification
qualityCheckPower, NoNotification
airRateTypeSelector, NoNotification
schCongPeriodGbr, NoNotification
schCongThreshGbr, NoNotification
schCongThreshNonGbr, NoNotification
schMaxDelay, NoNotification
schMinPowerNonGbrHsUsers, NoNotification
schNoCongPeriodGbr, NoNotification
schNoCongThreshGbr, NoNotification
schPowerDeltaCongGbr, NoNotification
schPrioForAbsResSharing, NoNotification
schWeight, NoNotification
aiDeviceRef, NoNotification, ReadOnly

dbccDeviceRef, NoNotification, ReadOnly

dpclDeviceRef, NoNotification, ReadOnly

tpaDeviceRef, NoNotification, ReadOnly

trDeviceRef, NoNotification, ReadOnly

Page 166
LOGICAL VIEW REPORT
dpclDevicesRef, NoNotification, ReadOnly

DbccDevice
Attributes:
DbccDeviceSet
Container MOC
Attributes:
DeviceGroup
Container MOC
Attributes:
DownlinkBaseBandPool
This MO models a pool of downlink baseband channel devices.
Attributes:
maxNumADchReservation, NoNotification
EDchResources
This MO models the Enhanced uplink Dedicated Channel resources. The E-DCH
resources are set up through Iub.
Attributes:
Equipment
Container MOC
Attributes:
Page 167
LOGICAL VIEW REPORT
ExternalTma
This MO describes an external Tma.

Attributes:
ulGain, Mandatory, NoNotification
dlTrafficDelayA, Mandatory, NoNotification
dlTrafficDelayB, Mandatory, NoNotification
internalPower, Mandatory, NoNotification
ulTrafficDelayA, Mandatory, NoNotification
ulTrafficDelayB, Mandatory, NoNotification
currentHighLimA, NoNotification
currentHighLimB, NoNotification
currentLowLimA, NoNotification
currentLowLimB, NoNotification
tmaDegradedSupported, NoNotification
HsDschResources
This MO models the High-Speed Downlink Shared Channel resources. They are set up
through Iub.
Attributes:
Iub
This MOC models interface between this RBS and the associated RNC.
Page 168
LOGICAL VIEW REPORT
Attributes:
userLabel, Mandatory, NoNotification
rbsId, Mandatory
controlPlaneTransportOption, Mandatory
userPlaneTransportOption, Mandatory, NoNotification

userPlaneIpResourceRef, NoNotification
IubDataStreams
SystemCreated
This MO models all lubDataStreams between RNC and RBS for Common as well as
Dedicated channels.
Attributes:
maxHsRate
maxEDchRate, NoNotification
hsDataFrameDelayThreshold, NoNotification
schHsFlowControlOnOff, NoNotification
McpaDeviceGroup
Container MOC
Attributes:
NbapCommon
This MOC models the manageable characteristics of a signalling link between the RBS
and a RNC.
Page 169
LOGICAL VIEW REPORT
Attributes:
uniSaalTpRef1, NoNotification
l2EstablishReqRetryT, Mandatory, NoNotification
auditRetransmissionT, Mandatory, NoNotification
l2EstablishSupervisionT, Mandatory, NoNotification
NbapDedicated
This MOC models the manageable characteristics of a signalling link between the RBS
and a RNC.

Attributes:
NodeSynchTp
This MOC models the Termination Point in RBS for the Node Synchronization protocol.

Attributes:
aal0TpRef1, NoNotification, Restricted
timDeviceRef, NoNotification, ReadOnly
PauDeviceGroup
Container MOC
Attributes:
PlugInUnit
Conatiner MOC
Attributes:
Page 170
LOGICAL VIEW REPORT
PredefRbsScannerGpeh
This MO models a Predefined RBS Scanner defined for GPEH, General Performance
Event Handling.

Attributes:
maxStorageSize, NoNotification
fileLocation, NoNotification, ReadOnly

RbsConfiguration
This MO is used for the configuration of the RBS done at site, that is, the configuration
performed by the O&M access wizard and the Site equipment configuration wizard.
Information about the progress of the OSS-RC configuration is also recevied. It is an MO
creating and modifying other MOs.
Attributes:
rbsConfigLevel
configFaultReason, NoNotification
unlockRbsAfterIntegration : AutoIntegrated, Default = NO, Local, NoNotification
Indicates if the RBS should be unlocked after activation of Planned Area.
integrationSequence : sequence<IntegrationSequence>, Local, NoNotification

Indicates the Planned Area to be activated as part of the Auto-Integration.
RbsLocalCell
This MOC models a Cell, i.e. a geographical area that can be identified by a UE from a
(Cell) identification broadcasted from one UTRAN Access Point.
Page 171
LOGICAL VIEW REPORT
Attributes:
localCellId, Mandatory
cellRange, Mandatory, NoNotification
carrierRef, Mandatory, NoNotification, Restricted
hsCodeResourceId, NoNotification
dynamicHsPdschCodeAdditionOn, NoNotification
maxNumHsPdschCodes, NoNotification
eulMaxNoSchEDch, NoNotification
eulMaxOwnUuLoad, NoNotification
eulMaxRotCoverage, NoNotification
eulMinMarginCoverage, NoNotification
eulOptimalNoiseFloorLock, NoNotification
eulSlidingWindowTime, NoNotification
eulThermalLevelPrior, NoNotification
maxEAgchPowerDl, NoNotification
maxUserEHichERgchPowerDl, NoNotification
maxNumHsdpaUsers, NoNotification
eulNoERgchGroups, NoNotification
hsdpaCapability, NoNotification, ReadOnly

maxDlPowerCapability, NoNotification, ReadOnly

minDlPowerCapability, NoNotification, ReadOnly

eDchCapability, NoNotification, ReadOnly

hsIncrementalRedundancyOn, NoNotification
minSpreadingFactor, NoNotification, ReadOnly

rbsSynchronizationRef, NoNotification, ReadOnly

eDch2msTtiCapability, NoNotification, ReadOnly
Page 172
LOGICAL VIEW REPORT
maxUserEHichPowerDlTti2, NoNotification
maxEAgchPowerDlTti2, NoNotification
maxNumEulUsers, NoNotification
featureStateEnhancedLayer2
eHichMinCodePower, NoNotification
qualityCheckPowerEHich, NoNotification
featureStateHsdpaDynamicCodeAllocation, NoNotification
featureStateHsdpaIncrementalRedundancy, NoNotification
RetDevice
This MOC defines the attributes that are persistently stored in Ranos.

Attributes:
electricalAntennaTilt, Mandatory
maxTilt, Mandatory, NoNotification
minTilt, Mandatory, NoNotification
RetDeviceSet
Container MOC.
Attributes:
productNumber, NoNotification
revState, NoNotification
retType, NoNotification
RetuDeviceGroup
Container MOC.
Attributes:
RruDeviceGroup
Container MOC
Page 173
LOGICAL VIEW REPORT
Attributes:
RuDeviceGroup
Container MOC
Attributes:
Sector
This MOC models a Sector.
Attributes:
utranCellRef : sequence<string>, Local, NoNotification
DN of the related RNC UtranCell MO.
Sub: RNH, CMS
Ref. [29]
numberOfCarriers, Mandatory, NoNotification

numberOfTxBranches, Mandatory, NoNotification
outputPower, Mandatory, NoNotification
fqBandHighEdge, Mandatory, NoNotification
fqBandLowEdge, Mandatory, NoNotification
latitude, Mandatory
latHemisphere, Mandatory
longitude, Mandatory
longHemisphere, Mandatory, NoNotification
geoDatum, Mandatory, NoNotification
beamDirection, Mandatory, NoNotification
height, Mandatory, NoNotification
sectorAntennaRef, Mandatory, NoNotification
userLabel
maxInternalUlGainOn, NoNotification
proceduralStatus, NoNotification, ReadOnly
retDeviceRef, NoNotification, ReadOnly

tmaDeviceRef, NoNotification, ReadOnly

band, NoNotification, ReadOnly

SectorAntenna
Attributes:
antennaType, Mandatory, NoNotification
Page 174
LOGICAL VIEW REPORT
Slot
Container MOC
Attributes:
Subrack
Container MOC
Attributes:
TimDevice
This MOC models the Device for the Timing Unit.
Attributes:
TimDeviceSet
Container MOC
Attributes:
TpaDevice
This MO models a Transmit Power Amplifier device.
Attributes:
maxTotalOutputPower, NoNotification
TpaDeviceSet
Container MOC
Attributes:
TuDeviceGroup
Container MOC
Attributes:
TxDeviceGroup
This MOC models the Transmission Device Group.
Page 175
LOGICAL VIEW REPORT
Required for: TNH
Attributes:
numHsCodeResources, NoNotification
numEulResources, NoNotification
References to MOs in the RBS Equipment View

As identities in R3.0, WRAN CM uses hardcoded Local Distinguished Name (LDN) values
for the corresponding Managed Objects. These Managed Objects are created at Network
Element installation by their Element Manager (see [14], [15] and [16]).
Up to 4 GPB boards are suported on RXI's.
StandardRBS
These references are valid for both RBS3101 and RBS3202.
Page 176
LOGICAL VIEW REPORT
RBS3104
These references are valid for RBS3104, RBS3203 and RBS3303.
1:
ManagedElement
1:
Equipment
For MPs 1:
S ubrack
4 : Slot
1:
PlugInUnit
1:
ManagedElement
Referred from 1: Refe rred fro m M O

MO Aal2Ap SwManagement A al2P athDistributio nUnit
ans_aal2ap_11 : ans_aal2cpsrc_11 :
Reliab le Prog ra mUniter Reliab le Prog ra mUniter
Page 177
LOGICAL VIEW REPORT
1:
Mana ge dElement
1:
1: ManagedElement
E quip ment
1:
Equipment
For TUs 1:
Subrack For ETB1 For ETB2
1:
Subrack
2 : Slot
3 : Slot 7 : Slot
1: 1: 1:
PlugInUnit PlugInUnit P lug InUnit
RBS 3107, 3206M, 3018, 3418 and 3518

This Rbs type contains a CBU, which itself contains MP, TU and ET boards. The following
FDNs should be used when configuring software on this RBS type:
RBS 3107, 3206M, 3018, 3418 and 3518

-----------------------------------------------------------------
Aal0TpVccTp.processorId = ManagedElement=1, Equipment=1, Subrack=1, Slot=1,
PlugInUnit=1
Aal5TpVccTp.processorId = ManagedElement=1, Equipment=1, Subrack=1, Slot=1,

PlugInUnit=1
RBS Base Model

The RBS Base Model contains those Managed Objects in the RBS Mirrored MIB that are
created in WRAN CM valid area for an RBS for which an operator wants to create a planned
configuration. See [13].
The Relative Distinguished Names of those Managed Objects in RBS are (see [16]):
ManagedElement=1
TransportNetwork=1
AtmPort=1-<slotid>-<lineno>, ’1’ represents the subrack identity where the ATM port is
included.
NodeBFunction=1
VplTp=1
VpcTp=1
VclTp=32 or 33
Note: there can now be up to 3 instances of AtmPort in the base model.
Page 178
LOGICAL VIEW REPORT
1:
ManagedElement
1: 1:
NodeBFunction TransportNetwork
1_<slotid>_<lineno> :
(AtmPort)
1 : VplTp
1:
VpcTp
32 : 33 :
VclTp VclTp
Rbs MOs needed for Synch

Managed object classes listed in this package are necessary for the synching of nodes. This is
because they are a parent of, or in the hierarchy above a MO containing persistent attributes
we mirror.
No XML is generated for these MOs.
CuSubrack
Required for: AuxPluginUnit.
Attributes:
McpaSubrack
Attributes:
PowerSupplySubrack
Required for: AuxPluginUnit, RbsSlot.
Attributes:
PowerSupplySystem
Required to find: AuxPluginUnit.
Page 179
LOGICAL VIEW REPORT
Attributes:
RbsSlot
Attributes:
RbsSynchronization
Required for: PluginUnit, TimDevice.
Attributes:
masterTu, NoNotification, ReadOnly
plugInUnitRef1, NoNotification, ReadOnly

plugInUnitRef2, NoNotification, ReadOnly

timDeviceRef1, NoNotification, ReadOnly

timDeviceRef2, NoNotification, ReadOnly

RANOS_RNC_MIRROR_MODEL_H
This MIM contains replicas of all managed objects from the RNC MIM and additional
WRAN CM MOC’s and attributes that are only part of the RNC mirrored MIM not the RNC
MIM
Following Managed Object Types are WRAN CM local MOC’s:
MeContext
ExternalGsmCell
ApplicationTag = Contains only RNC cached attributes, NotificationTypes = notifyObjectCreation,
notifyObjectDeletion
This MOC models an external Gsm Cell.
For more information see RNC MIM, ref [2].
Page 180
LOGICAL VIEW REPORT
Attributes:
cellIdentity, Mandatory
ncc, Mandatory
bcc, Mandatory
bcchFrequency, Mandatory
lac, Mandatory

mxTxPowerUl, Mandatory
qRxLevMin, Mandatory
individualOffset, Mandatory
bandIndicator, Mandatory
ExternalGsmNetwork
This MOC models the manageable characteristics of an external Gsm Network.
This MOC defines the attributes that are persistently stored in WRAN CM.
Page 181
LOGICAL VIEW REPORT
Attributes:
mcc, Mandatory
mnc, Mandatory
mncLength, Mandatory
aliasPlmnIdentities
reservedBy, NoNotification, ReadOnly

ExternalUtranCell
ApplicationTag = Contains only RNC cached attributes, NotificationTypes = notifyObjectCreation,
notifyObjectDeletion
This MOC models an external Rnc UtranCell.
Page 182
LOGICAL VIEW REPORT
Attributes:
cId, Mandatory
lac, Mandatory
primaryScramblingCode, Mandatory
primaryCpichPower, Mandatory
maxTxPowerUl, Mandatory
qQualMin, Mandatory
uarfcnDl, Mandatory
uarfcnUl, Mandatory

rac, Mandatory
agpsEnabled
cellCapability
IubLink
This MOC models manageable characteristics of an RBS node that must be known to the
RNC.
It defines WRAN CM specific attributes that models the functionality required by the
This MOC defines also the attributes that are persistently stored in WRAN CM.
Page 183
LOGICAL VIEW REPORT
Attributes:
iubLinkNodeBFunction : string, Local, Mandatory
Reference to related NodeBFunction instance
FDN according to [9] and [20].
Sub: RNH, EQH
Ref. [22]
rbsId, Mandatory
This attribute is Mandatory in the RNC MOM. See ref. [2].

rncModuleRef, NoNotification, ReadOnly

beMarginDlHw
beMarginUlHw
dlHwAdm
ulHwAdm
preferredSubrackRef, Mandatory
Page 184
LOGICAL VIEW REPORT
userPlaneTransportOption, Mandatory
controlPlaneTransportOption, Mandatory
operationalState, ReadOnly
administrativeState
sctpRef, ReadOnly
l2EstReqRetryTimeNbapC
l2EstReqRetryTimeNbapD
remoteCpIpAddress1
remoteCpIpAddress2
userPlaneIpResourceRef
atmUserPlaneTermSubrackRef
cachedRemoteCpIpAddress1, ReadOnly
cachedRemoteCpIpAddress2, ReadOnly
IurLink
The MO IurLink models manageable characteristics of an external Rnc that must be
known to the Rnc.
This MOC defines the attributes that are persistently stored in WRAN CM.
Page 185
LOGICAL VIEW REPORT
Attributes:
rncId, Mandatory
utranNetworkRef, Mandatory, NoNotification, Restricted

Reference to the UTRAN network to which this Iur link belongs.
cellCapabilityControl, NoNotification
hspaPathlossThreshold, NoNotification
userPlaneTransportOption, Mandatory, NoNotification

srncPmReporting, NoNotification
userPlaneIpResourceRef, NoNotification
edchDataFrameDelayThreshold, NoNotification
iurArpGuaranteed, NoNotification
iurArpNonguaranteed, NoNotification
mcc, NoNotification
atmUserPlaneTermSubrackRef, NoNotification
maxMacdPduSizeExtended
RncFunction
This MOC models manageable characteristics that are common to several RNC function
(radio network) objects, including the location-, routing and service areas.
A WRAN CM specific attribute models the references to IurLink MO’s on neighbouring

RNC's.
Page 186
LOGICAL VIEW REPORT
Attributes:
rncId, Mandatory
mcc, Mandatory
mnc, Mandatory
mncLength, Mandatory
aliasPlmnIdentities
emergencyCallRedirect, Mandatory
loadSharingDirRetryEnabled, Mandatory
loadSharingRrcEnabled, Mandatory
hsCellChangeAllowed
hsOnlyBestCell
gpehDataLevel
gpehFileSize
uetrFileSize
ctrFileSize
counterAlarmThreshold
counterAlarmCeaseLimit
counterWarningAlarmCeaseLimit
networkResourceIdentifierLengthCs
Bitmask length of the NRI for CS/MSC. 0 (default) means no Iu Flex active
To be used for Iu Flex.
Page 187
LOGICAL VIEW REPORT
networkResourceIdentifierLengthPs
Bitmask length of the NRI for PS/SGSN. 0 (default) means no Iu Flex active
To be used for Iu Flex.
hsToDchTrigger, NoNotification
Indicates whether triggers leading to a transition from HS-DSCH to a DCH connection are acted upon or not.
ecLocationAttemptUmts, NoNotification
Determines whether a location attempt should be made for the emergency call in the UMTS system. Only valid
if ecCnSbhoRequestIgnore = TRUE
ecCnSbhoRequestIgnore, NoNotification
Determines if a request from the Core Network for Service based handover should be ignored for an Emergency
Call, if positioning using A-GPS is possible.
ecCnPriorityLevel, NoNotification
The priority level received from the Core Network that RNC interprets as the identifier for Emergency Calls.
ecSbhoTimer, NoNotification
Time within which the Service based handover must be completed for Emergency Call. Only valid if
ecCnSbhoRequestIgnore = TRUE and ecLocationAttemptUmts = ON.
harqTransmUlTti10Max, NoNotification
Maximum number of HARQ transmissions for E-DCH when TTI=10 ms.
[PersistInMirror: P5 ]
primaryCnOperatorRef, NoNotification
Reference to the primary CnOperator, used when MOCN is not in use.
Unit: N/A
Resolution: N/A
Page 188
LOGICAL VIEW REPORT
maxPowerOverloadHystTime, NoNotification
nbapDscp, NoNotification
cchDscpEgress, NoNotification
cchDscpIngress, NoNotification
mocnExternalNriMatching, NoNotification
maxAllowedGbrDlPsStream, NoNotification
pcapPositioningMode, NoNotification
highPrioScanReserve, NoNotification
noOfCountersAllowed, NoNotification
nbapAuditInterval, NoNotification
iuSccpConRateMeasPeriod, NoNotification
iuSccpConRateThresh, NoNotification
intraNodeIpResourceRef, NoNotification
UtranCell
This MOC models the manageable characteristics of an Utrancell.
It defines WRAN CM specific attributes that models the functionality required by the
When creating a UtranCell, the name of the UtranCell MO shall equal to

UtranCell.userLabel.
Page 189
LOGICAL VIEW REPORT
Attributes:
lac : long, Local, Mandatory, Range = 1..65533, 65535
Location Area Code
Sub: RNH, CMS, RAH
Ref. [29]
rac : long, Default = 256, Local, Range = 0..256

Routing Area Code. Default is significant for Radio GUIs.
Sub: RNH, CMS, RAH
Ref. [29]
sac : long, Local, Mandatory, Range = 0..65535

Service Area Code
Sub: RNH, CMS, RAH
Ref. [29]
utranCellIubLink : string, Local, Mandatory, Restricted

DN of the related IubLink MO.
Sub: RNH, CMS, RAH
Ref. [29]
snDirectedRetryTarget : string, Local
sectorRef : string, Local, NoNotification

DN of the related RBS Sector MO.
Sub: RNH, CMS
Ref. [29]
Page 190
LOGICAL VIEW REPORT
administrativeState, Mandatory
Attribute persistently stored in RANOS
Attribute persistently stored in WRAN CM
availabilityStatus, ReadOnly
Attribute persistently stored in WRAN CM
localCellId, Mandatory
cId, Mandatory
tCell, Mandatory
uarfcnUl, Mandatory
uarfcnDl, Mandatory
primaryScramblingCode, Mandatory
primarySchPower, Mandatory
secondarySchPower, Mandatory
primaryCpichPower, Mandatory
maximumTransmissionPower, Mandatory
maxTxPowerUl, Mandatory
bchPower, Mandatory
cellReserved, Mandatory
treSelection, Mandatory
qualMeasQuantity, Mandatory
qHyst1, Mandatory
qHyst2, Mandatory
qQualMin, Mandatory
Page 191
LOGICAL VIEW REPORT
pwrAdm, Mandatory
pwrAdmOffset, Mandatory
pwrOffset, Mandatory
pwrHyst, Mandatory
tmCongAction, Mandatory
releaseAseDl, Mandatory
dlCodeAdm, Mandatory
aseDlAdm, Mandatory
beMarginAseDl, Mandatory
Old name: beMarginDl
aseUlAdm, Mandatory
beMarginAseUl, Mandatory
Old name: beMarginUl
Page 192
LOGICAL VIEW REPORT
sf8Adm, Mandatory
sf32Adm, Mandatory
aseUlAdmOffset, Mandatory
iubLinkRef, NoNotification, Restricted

Attribute persistently stored in RANOS.
[PersistInMirror: P5 onwards, notMandatory]
reservedBy, Mandatory
locationAreaRef
serviceAreaRef
routingAreaRef
utranCellPosition, Mandatory
sib1PlmnScopeValueTag, Mandatory
minPwrRl, Mandatory
maxRate, Mandatory
Attribute persistently storedin Ranos.
interRate, Mandatory
minimumRate, Mandatory
maxPwrMax, Mandatory
interPwrMax, Mandatory
minPwrMax, Mandatory
compModeAdm, Mandatory
iFOffset, Mandatory
iFHyst, Mandatory
iFCong, Mandatory
Page 193
LOGICAL VIEW REPORT
interFreqFddMeasIndicator, Mandatory
sRatSearch, Mandatory
sIntraSearch, Mandatory
sInterSearch, Mandatory
fachMeasOccaCycLenCoeff, Mandatory
accessClassNBarred
beMarginDlCode, Mandatory
beMarginDlPwr, Mandatory
sf16Adm, Mandatory
hoType, Mandatory
usedFreqThresh2dEcno, Mandatory
usedFreqThresh2dRscp, Mandatory
nOutSyncInd
nInSyncInd
rlFailureT
tmCongActionNg
releaseAseDlNg
tmInitialG
directedRetryTarget
loadSharingGsmFraction
loadSharingGsmThreshold
hardIfhoCorr
hsdpaUsersAdm
Page 194
LOGICAL VIEW REPORT
loadSharingMargin
releaseAseDlGhs
tmCongActionGhs
tmInitialGhs
sf4AdmUl
sf16gAdm
sHcsRat
sf16AdmUl
sf8AdmUl
sf8gAdmUl
uraRef
agpsEnabled
codeLoadThresholdDlSf128
aseLoadThresholdUlSpeech
pwrLoadThresholdDlSpeech
eulNonServingCellUsersAdm
eulServingCellUsersAdm
Page 195
LOGICAL VIEW REPORT
rateSelectionPsInteractive
accessClassesBarredCs
accessClassesBarredPs
hcsUsage
hcsSib3Config
amrWbRateDlMax
amrWbRateUlMax
antennaPosition
cellBroadcastSac
ctchOccasionPeriod
mocnCellProfileRef
standAloneSrbSelector
amrNbSelector
eulServingCellUsersAdmTti2
GsmRelation
GsmRelation
The WRAN CM specific attributes models the functionality required by the 3GPP
standard, see ref. [24].
Note: According to Corba SS, bcchFrequency, ncc, bcc and lac are of type "integer".
Naming RULE
The RDN value for the referenced adjacent (target) is set by the system as default to:
<MO Id of target GSM cell>
Example: GsmRelation=TraSq_B1
Page 196
LOGICAL VIEW REPORT
Attributes:
adjacentCell : string, Local, Mandatory
Reference to ExternalGsmCell MO which contains the specification of the adjacent cell. Even though this is not
a restricted attribute it can only be set by an operator upon MO creation and cannot be modified to point to a
new ExternalGsmCell.
Attribute value change notification are sent for attributes relationType and adjacentCell.
Sub: CMS, RNH
Ref. [24]
qOffset1sn, Mandatory
externalGsmCellRef, NoNotification, Restricted

mobilityRelationType
selectionPriority
MeContext
MeContext
This MO models a RNC. One instance of this MO Type can exist per MIB.
NOTE: Functions that are general for all NE, shall be modelled in BasicMeContext MO.
Naming RULE
Page 197
LOGICAL VIEW REPORT
Attributes:
neLinkRelations : sequence <string>, NoNotification
List of the remote NE’s associate d with this NE.
FDN of MeContext instances
Used to model the RANAG-RNC link relations.
Sub: EQH
Ref. []
synchronisationProgress : long, Default = 0, ReadOnly

synchronising.
Sub: CMS
Ref. [2]

Attributes:
Sub: EQH, RAH
Ref. [21]

Sub: EQH
Ref. [7]

Sub: EQH
Ref. [7]

Sub: EQH
Ref. [7]

RANOS_FOLLOWS = 1
NO_SWITCH = 2
Page 198
LOGICAL VIEW REPORT
NE_FOLLOWS = 3
Sub: EQH
Ref. []

Sub: CMS
Ref. [7]

Sub: CMS
Ref. [7]

NEVER_CONNECTED = 1
CONNECTED = 2
DISCONNECTED = 3
Sub: CMS
Ref. [7]

RNC.
TOPOLOGY = 1
ATTRIBUTE = 2
SYNCHRONIZED = 3
UNSYNCHRONIZED = 4
Sub: CMS
Ref. [7]

UPDATING = 1
IDLE = 2
Sub: CMS
Ref. [2]
Page 199
LOGICAL VIEW REPORT

Sub: CMS
Ref. [2]

Sub: CMS
Ref. [7]

RNC = 1
NODEB = 2
RANAG = 3
ENODEB = 4
Ref. [7]

Sub: EQH
Ref. [7]

Sub: EQH
Ref. []

Sub: EQH
Ref. []


OFF
ON
Sub:
Ref. []
Page 200
LOGICAL VIEW REPORT

Sub: CMS, BCR

Sub: CMS, BCT

Sub: CMS, Telis

Sub:
Ref. []

Sub:
Ref. []

UtranRelation
UtranRelation
This MOC models the manageable characteristics of the relation to a neighbouring Cell
of type Utran, e.g. MO Utran Cell (intra Rnc handover) or MO ExternalUtranCell (inter
Rnc handover).
It defines the WRAN CM specific attributes that models the functionality required by the
3GPP standard, see ref. [22]
Page 201
LOGICAL VIEW REPORT
Note: According to Corba SS: uarfcnUl, uarfcnDl, primaryScramblingCode,

primaryCpichCode and lac are of type "integer"
Naming RULE
The RDN value for the referenced adjacent (target) cell is set by the system as default to:
<MO Id of target cell>
where target cell is of type UtranCell or ExternalUtranCell.
Example: UtranRelation=TraSq60012
Attributes:
adjacentCell : string, Local, Mandatory
Reference to UtranCell (RNC mirror) or ExternalUtranCell (SubNetwork) which contains the specification of
the adjacent cell. Even though this is not a restricted attribute it can only be set by an operator upon MO
creation and cannot be modified to point to a new UtranCell or ExternalUtranCell.
Full Distinguished Name according to [9] and [20].
Sub: CMS, RNH
Ref. [22]
utranCellRef, NoNotification, Restricted

frequencyRelationType, Mandatory
loadSharingCandidate, Mandatory
selectionPriority
hcsSib11Config
nodeRelationType, NoNotification, ReadOnly

Operations:
setAdjacentCell (AdjacentCell : in string) : void
Action takes a single parameter which is a string value containing the FDN of the new target UtranCell. The
UtranRelation will be deleted and then created again with the same RDN and attribute values except for
adjacentCell which will have the value provided in the parameter.
Rnc Cello MOC's containing WRAN CM local attributes

Cello MOC's used in Rnc Mirror Model are specializations of the MOC's defined in
Page 202
LOGICAL VIEW REPORT
Aal0TpVccTp
Attributes:
Aal2PathVccTp
Attributes:
Aal5TpVccTp
Attributes:
AtmCrossConnection
Attributes:
AtmPort
Naming RULE
Attributes:
ManagedElement
NOTE: Functions that are generall for all NE, shall be modelled in
Page 203
LOGICAL VIEW REPORT
Attributes:

Attributes:
Sub: EQH, RAH
Ref. [21]

Sub: EQH, RAH
Ref. [21]

Sub: -
Ref. [21]

Sub: CMS
Ref. []

Sub: EQH, RAH
Ref. [21]

MO’s.
Sub: CMS
Ref. [21]

Page 204
LOGICAL VIEW REPORT
Sub: EQH, RAH
Ref. [21]

Sub: EQH
Ref. []

Sub: -
Ref. []

Sub: EQH
Ref. []
TransportNetwork
Attributes:
Derived from BasicTransportNetwork

Attributes:
VclTp
Attributes:
VpcTp
Attributes:
VplTp
Attributes:
Page 205
LOGICAL VIEW REPORT
Rnc Attributes Mirrored in WRAN CM

All RNC writeable attributes used by WRAN CM are stored persistently in the WRAN CM
mirrored MIBs. In addition, attributes "reservedBy" needed by WRAN CM are stored
persistently. Value change notifications keep these attributes updated.
AgpsPositioning
Models the manageable characteristics of the UE-based A-GPS positioning feature.
It is not possible to enable A-GPS unless the instance of AgpsPositioning has been
created.
This MOC defines the attributes that are persistently stored in Ranos.
Attributes:
altitudeDirection, Mandatory
altitude, Mandatory
uncertaintyAltitude, Mandatory
confidence, Mandatory
polygonRadiusFactor
utranRnsPosition, Mandatory
utranRnsUncertaintyRadius, Mandatory
utranRnsConfidence
elevationThreshold
ueMeasurementReportCriteria
posQualities, Mandatory
ArpMap
Models the mapping of ARP values.
Attributes:
defaultArpQos, Mandatory, NoNotification
externalArpMapping, Mandatory, NoNotification
systemDefaultArpQos, NoNotification, ReadOnly
ArpQosClassProfile
Models the manageable characteristics of ARP.
Page 206
LOGICAL VIEW REPORT
Attributes:
CchFrameSynch
This MOC models the manageable characteristics for Frame synchronization on the two
FACH transport channels and the PCH channel.

Attributes:
dto, Mandatory
doStep, Mandatory
toAWS, Mandatory
toAWE, Mandatory
toAE, Mandatory
ChannelSwitching
This MO type models manageable characteristics for the channel switching algorithms.
Page 207
LOGICAL VIEW REPORT
Attributes:
dlRlcBufUpswitch, Mandatory, NoNotification
ulRlcBufUpswitch, Mandatory, NoNotification
downswitchThreshold, Mandatory, NoNotification
downswitchTimerThreshold, Mandatory, NoNotification
downswitchTimer, Mandatory, NoNotification
dlRlcBufUpswitchMrab, Mandatory, NoNotification
ulRlcBufUpswitchMrab, Mandatory, NoNotification
upswitchTimer, Mandatory, NoNotification
Sub: BCT
coverageTimer, Mandatory, NoNotification
Sub: BCT
inactivityTimer, Mandatory, NoNotification
Sub: BCT
downswitchPwrMargin, Mandatory, NoNotification
Sub: BCT
reportHysteresis, Mandatory, NoNotification
Sub: BCT
upswitchPwrMargin, Mandatory, NoNotification
Sub: BCT
downswitchTimerSp
Sub: BCT
downswitchTimerUp
Sub: BCT
HsdschInactivityTimer
upswitchTimerUl, NoNotification
bandwidthMarginUl, NoNotification
bandwidthMargin, NoNotification
dlDownswitchBandwidthMargin, NoNotification
dlThroughputAllowUpswitchThreshold, NoNotification
dlThroughputDownswitchTimer, NoNotification
ulDownswitchBandwidthMargin, NoNotification
ulThroughputAllowUpswitchThreshold, NoNotification
ulThroughputDownswitchTimer, NoNotification
inactivityTimerPch, NoNotification
inactivityTimeMultiPsInteractive, NoNotification
Page 208
LOGICAL VIEW REPORT
fachToHsDisabled, NoNotification
CnOperator
Models the manageable characteristics of a Core Network operator.
Attributes:
equivalentPlmnIdentities
iphoNetworkRefsGsm
iphoNetworkRefsUtran
plmnIdentity, Mandatory, Restricted
userLabel
equivalentPlmnIdentityGroupRef
CoverageRelation
Models the manageable characteristics of the relation of an UTRAN cell to a another
UTRAN cell. The source UTRAN cell and the target neighbouring UTRAN cell may
reside at the same or different frequencies but must always reside in the same RNC. The
maximum number of coverage relations for a UtranCell is one.
This MOC defines also the attributes that are persistently stored in Ranos.
Attributes:
utranCellRef, NoNotification, Restricted
This attribute is Mandatory/Restricted in the RNC MOM. See ref. [2].
coverageIndicator
hsPathlossThreshold
DchFrameSynch
This MOC models the manageable characteristics to mirror the transport delay on Iub for
DCH in uplink and downlink.
Page 209
LOGICAL VIEW REPORT
Attributes:
dto, Mandatory
doStep, Mandatory
toAWS, Mandatory
toAWE, Mandatory
toAE, Mandatory
uto, Mandatory
uoStep, Mandatory
toAWSUl, Mandatory
toAWEUl, Mandatory
toAEUl, Mandatory
DchMap
Models the manageable characteristics of RAB parameter mapping to the DCH QoS
settings.
Attributes:
dchDirection, Mandatory, NoNotification
gbrDlRangeEnd, Mandatory, NoNotification
gbrDlRangeStart, Mandatory, NoNotification
internalArp, NoNotification
qosRef, Mandatory, NoNotification
Equipment
Container MOC.
Attributes:
Eul
Models the manageable characteristics of the logical resources representing E-DCH
channels, and their associated physical channels E-AGCH and E-RGCH/E-HICH.
Page 210
LOGICAL VIEW REPORT
Attributes:
administrativeState
numEagchCodes
numEhichErgchCodes
userLabel
eulMaxTargetRtwp
edchTti2Support, ReadOnly
Fach
This MOC models the manageable characteristics of the transport Forward Access
Channels (FACH) of a cell and the logical channels (CCCH, BCCH, DCCH and DTCH).

Attributes:
maxFach1Power, Mandatory
maxFach2Power, Mandatory
sccpchOffset, Mandatory
pOffset1Fach, Mandatory
pOffset3Fach, Mandatory
GpsReceiver
Represents a GPS receiver.
Attributes:
Handover
This MOC models the management characteristics of IRAT and soft handover.
Page 211
LOGICAL VIEW REPORT
Attributes:
maxActiveSet, Mandatory
gsmPropRepeatInterval, Mandatory
timeReleaseIuPs, Mandatory
fddGsmHOSupp, Mandatory
selHoSup, Mandatory
ifhoPropRepeatInterval, Mandatory
ifhoAmountPropRepeat, Mandatory
gsmAmountPropRepeat, Mandatory
fddIfhoSupp, Mandatory
releaseConnOffset, Mandatory
Sub: BCT
maxGsmMonSubset
Sub: BCT
maxIefMonSubset
Sub: BCT
cnhhoSupp
interFreqCnhhoPenaltyEcno
interFreqCnhhoPenaltyRscp
intraFreqCnhhoPenalty
intraFreqCnhhoWeight
tmStopGsmMeas
eulReservedHwBandwidthSchedDataNonServCell
Hsdsch
Models the manageable characteristics of the logical resources representing HS-DSCH
channels, and their associated physical channels HS-SCCH and HS-PDSCH.
Page 212
LOGICAL VIEW REPORT
Attributes:
administrativeState
deltaAck1
deltaNack1
deltaAck2
deltaNack2
deltaCqi1
deltaCqi2
initialAckNackRepetitionFactor
initialCqiRepetitionFactor
cqiFeedbackCycle
hsMeasurementPowerOffset
numHsPdschCodes
codeThresholdPdu656
numHsScchCodes
enhancedL2Support, ReadOnly
qam64Support, ReadOnly
IpAccessHostPool
Models the manageable characteristics of an IP access host pool. The traffic to/from IP
network (segment) is distributed over the IP Access Hosts that belong to the IP Access
Host Pool. Hence all the IP Access Hosts that belong to the IP Access Host Pool have to
provide connectivity to selected network segment.
Attributes:
availabilityStatus, NoNotification, ReadOnly
ipAccessHostRef, NoNotification
operationalState, NoNotification, ReadOnly
IpEthPacketDataRouter
Represents an individual IP link over ethernet in a PdrDevice.
Page 213
LOGICAL VIEW REPORT
Attributes:
userLabel
reservedBy
ipAccessHostSpbRef, Mandatory, Restricted
ipAddressSelection, Restricted
pdrDeviceRef, NoNotification
IpSystem
Container MOC.
Attributes:
IuBcLink
Models the manageable characteristics of the Iu-BC interface between RNC and the Cell
Broadcast Centre (CBC).

Attributes:
administrativeState
cbcIpAddress, Mandatory, NoNotification
sourceIpAddressValidation, NoNotification
IubEdch
Models manageable characteristics of Iub Enhanced Uplink resources.
Attributes:
edchDataFrameDelayThreshold, NoNotification
IuLink
Models the manageable characteristics of a link between core network node and RNC
that includes the Iu user plane resources.
Page 214
LOGICAL VIEW REPORT
Attributes:
packetDataRouterRef
userPlaneTransportOption, Mandatory
userLabel
userPlaneIpResourceRef
atmUserPlaneTermSubrackRef, NoNotification
LocationArea
This MOC models manageable characteristics of a Location Area in the RNC. Note that
this MOC belongs to the RNC MIM.

Attributes:
lac, Mandatory
t3212, Mandatory
att, Mandatory
Mbms
Models the manageable characteristics of the MBMS resources on node level.
Attributes:
inactivityTimer, NoNotification
MbmsCch
Models the manageable characteristics of the resources representing the MBMS common
channels MCCH, MTCH and MICH per cell.
Page 215
LOGICAL VIEW REPORT
Attributes:
nonPlMbmsSac : sequence<long>, Local, Range = 0..65535
List of non-preferred layer Mbms Service Area Codes.
Sub: RNH, CMS, RAH
Ref. [29]
plMbmsSac : sequence<long>, Local, Range = 0..65535

List of preferred layer Mbms Service Area Codes.
Sub: RNH, CMS, RAH
Ref. [29]
administrativeState
availabilityStatus, NoNotification, ReadOnly
hcsPrioOffset
mbmsDispersion
mcchPowerOffset
mcchPowerOffsetTfci
michPowerOffset
mtch128PowerOffset
mtch128PowerOffsetTfci
mtch256PowerOffset
mtch64PowerOffset
numNotificationInd
plServiceRestriction
qualityOffset
nonPlMbmsSaRef
plMbmsSaRef
MbmsServiceArea
Models the manageable characteristics of a MBMS Service Area.
Attributes:
sac, Mandatory
userLabel
MocnCellProfile
Collects common definitions for cell level MOCN.
Page 216
LOGICAL VIEW REPORT
Attributes:
commonPlmnRef, Mandatory, NoNotification
MtchFrameSynch
Models the manageable characteristics of soft combining of MTCH FACHes for MBMS
services.
Attributes:
iubTransportDelayMax, NoNotification
iubTransportDelayOffset, NoNotification
phaseDriftThreshold, NoNotification
toaWindowEndpoint, NoNotification
toaWindowSize, NoNotification
NbapCommon
This MOC models the manageable characteristics of a control signalling link between the
RNC and an RBS, aimed for carrying NBAP common signalling.
Attributes:
activeUniSaalTpRef, Mandatory, NoNotification, Restricted
standbyUniSaalTpRef, NoNotification, Restricted
operationalState, Mandatory, ReadOnly
NbapDedicated
This MOC models the manageable characteristics of a control signalling link aimed for
carrying NBAP dedicated signalling between the RNC and an RBS.
Page 217
LOGICAL VIEW REPORT
Attributes:
activeUniSaalTpRef , Mandatory, NoNotification, Restricted
standbyUniSaalTpRef, NoNotification, Restricted
NodeSynch
This MOC models the configurable parameters for Node Synchronization between the
RNC and an RBS.
Attributes:
noOfSamples, Mandatory, NoNotification
supervisionIntervalT, Mandatory, NoNotification

phaseDiffThreshold, Mandatory, NoNotification

Old name: eventThreshold

phaseMeasurement, Mandatory, NoNotification, ReadOnly

accuracy, NoNotification, ReadOnly
timeStamp, NoNotification, ReadOnly

fixedWindowSizeInit, NoNotification
fixedWindowSizeSup, NoNotification
sampleIntervalInit, NoNotification
sampleIntervalSup, NoNotification
slidingWindowSize, NoNotification
NodeSynchTp
This MOC models the termination point parameters for Node Synchronization between
the RNC and an RBS.
Page 218
LOGICAL VIEW REPORT
Attributes:
nodeSynchRef, Mandatory, NoNotification
aal0TpRefs, Mandatory, NoNotification
timDeviceRef, Mandatory, NoNotification
PacketDataRouter
Represents an indvidual PVC link in a packet data router in a pdrDevice.
Attributes:
rncIpAddress, Mandatory, NoNotification
cnIuLinkIpAddress, Mandatory, NoNotification
timeToLive, Mandatory, NoNotification
pdrDeviceRef, Mandatory, NoNotification
aal5TpRef, Mandatory, NoNotification
Paging
This MO type models manageable characteristics for the paging algorithm.
Attributes:
cnDrxCycleLengthCs, Mandatory, NoNotification
cnDrxCycleLengthPs, Mandatory, NoNotification
noOfPagingRecordTransm, Mandatory, NoNotification
utranDrxCycleLength, NoNotification
Pcap
Models the manageable characteristics of the transport for the Iupc interface.

Attributes:
localSccpApRef, Mandatory, NoNotification, Restricted
remoteSccpApRef, Mandatory, NoNotification, Restricted
sccpDisabledT, NoNotification
userOutOfServiceT, NoNotification
Page 219
LOGICAL VIEW REPORT
Pch
This MOC models the manageable characteristics of a Paging Channel.
Attributes:
pchPower, Mandatory
pichPower, Mandatory
sccpchOffset, Mandatory
userLabel
PdrDevice
Container MOC.
Attributes:
PlmnIdentityGroup
A group of PLMN identities.
Attributes:
plmn, NoNotification
PlugInUnit
Container MOC
Attributes:
PositioningServiceClass
Models the manageable characteristics of a positioning service class.
Page 220
LOGICAL VIEW REPORT
Attributes:
agpsMeasTimeMax, Mandatory, NoNotification
delayTolerantRespTimeMax, Mandatory, NoNotification
firstAttemptCandidate, Mandatory, NoNotification
firstAttemptResultQosCheck, Mandatory, NoNotification
fixedRespTimeMax, Mandatory, NoNotification
lowDelayRespTimeMax, Mandatory, NoNotification
reportedConfidenceLevel, Mandatory, NoNotification
secondAttemptMethod, Mandatory, NoNotification
secondAttemptResultQosCheck, Mandatory, NoNotification
shapeConversionEa, Mandatory, NoNotification
shapeConversionEp, Mandatory, NoNotification, Restricted
shapeConversionEpa, Mandatory, NoNotification
shapeConversionEpaue, Mandatory, NoNotification
shapeConversionEpuc, Mandatory, NoNotification
shapeConversionEpue, Mandatory, NoNotification
shapeConversionP, Mandatory, NoNotification
thirdAttemptMethod, Mandatory, NoNotification
PowerControl
This MOC models manageable characteristics for the power control algorithm for
dedicated and common channels.

Attributes:
dlPcMethod, Mandatory
pcpichPowerDefault, Mandatory
fixedPowerDl, Mandatory
cPO, Mandatory
pO1, Mandatory
pO2, Mandatory
pO3, Mandatory
cBackOff, Mandatory
ecNoPcpichDefault, Mandatory
ulSirStep, Mandatory
ulOuterLoopRegulator, Mandatory
sirMin, Mandatory
sirMax, Mandatory
dlInitSirTarget, Mandatory
ulInitSirTargetSrb, Mandatory
ulInitSirTargetLow, Mandatory
ulInitSirTargetHigh, Mandatory
cNbifho, Mandatory
fixedRefPower, Mandatory
Sub: BCT.
initShoPowerParam, Mandatory
Sub: BCT.
ulInitSirTargetExtraHigh
transmissionTargetError
ulInitSirTargetEdch
Page 221
LOGICAL VIEW REPORT
transmissionTargetErrorTti2
ulSirStepTti2
ulInitSirTargetEdchTti2
sirMaxTti2
RabHandling
Models manageable characteristics for RAB handling.
Attributes:
psStreamingInactivityTimer
activeQueueMgmt
dscpValuePsStreaming
eulHarqRv, NoNotification
Rach
This MOCmodels the manageable characteristics of a Random Access Channel.

Attributes:
scramblingCodeWordNo, Mandatory
preambleSignatures, Mandatory
maxPreambleCycle, Mandatory
subChannelNo, Mandatory
aichTransmissionTiming, Mandatory
aichPower, Mandatory
powerOffsetP0, Mandatory
powerOffsetPpm, Mandatory
preambleRetransMax, Mandatory
constantValueCprach, Mandatory
spreadingFactor, Mandatory
Ranap
The Ranap MOC models the configurable parameters for the control signalling link
between the RNC and core network (CN).
Page 222
LOGICAL VIEW REPORT
Attributes:
userLabel
cnDomainInd, Mandatory, NoNotification
noOfResetSendings
resetResendT
resetAckGuardT
sccpDisabledT
userOutOfServiceT
localSccpApRef, Mandatory, NoNotification, Restricted
remoteSccpApRef, Mandatory, NoNotification, Restricted
cnId, Mandatory, Restricted
networkResourceIdentifier
packetDataRouterRef
relativeCapacity
cnOperatorRef, Mandatory, NoNotification, Restricted

maxResetResourceMessageSize, NoNotification
Rcs
This MO Type models manageable characteristics for the Radio Connection Supervision
algorithm.
Attributes:
dchRcLostT, Mandatory, NoNotification
cchWaitCuT, Mandatory, NoNotification
hsDschRcLostT
ResMeasControl
Models the manageable characteristics for Radio Environment Statistics measurements
Attributes: [PersistInMirror: P5 onwards]
Page 223
LOGICAL VIEW REPORT
resMeasure1
resMeasure2
resMeasure3
resMeasure4
resMeasure5
resMeasure6
resMeasPeriodSpeech
resMeasPeriodStreaming
resMeasPeriodVideo
resMeasPeriodInteractive
resUeFraction
RncCapacity
Models the manageable characteristics of a licensed capacity.

Attributes:
currentCapacityLimit, NoNotification, ReadOnly
licensedCapacityLimit, NoNotification, ReadOnly
keyId, NoNotification, ReadOnly
isLicensedControlled, NoNotification, ReadOnly
operatorCapacityLimit, NoNotification
capacityUnit, NoNotification, ReadOnly
RncFeature
Models the manageable characteristics of a licensed optional feature.
Attributes:
featureState, NoNotification
isLicenseControlled, NoNotification
keyId, NoNotification
licenseState, NoNotification
serviceState, NoNotification
RncModule
This MOC is used to group together a number of Iubs onto device boards on one Device
MP.
Page 224
LOGICAL VIEW REPORT
Attributes:
rpuRefs, Mandatory, NoNotification
RnlQosClassProfile
Models the manageable characteristics of QoS mappings for HSPA in uplink as well as
downlink.
Attributes:
tcPsBgQosRef, NoNotification
Rnsap
Attributes:
sccpDisabledT, Mandatory, NoNotification
localSccpApRef, Mandatory, NoNotification
remoteSccpApRef, Mandatory, NoNotification
userOutOfServiceT, Mandatory, NoNotification
RoutingArea
This MOC models manageable characteristics of a Routing Area in the RNC. Note that
this MOC belongs to the RNC MIM.
Attributes:
rac, Mandatory
nmo, Mandatory
Rrc
The Rrc MO models manageable characteristics of the Radio Resource Control protocol.
Page 225
LOGICAL VIEW REPORT
Attributes:
t305, Mandatory, NoNotification
cfnOffsetMarginFirstRabEst, NoNotification
RttPositioning
Models the manageable characteristics of the RTT positioning method.
Attributes:
measTimeMaxRbs, Mandatory, NoNotification
measTimeMaxUe, Mandatory, NoNotification
outlierFactor, Mandatory, NoNotification
posQualities, Mandatory, NoNotification
propagationTimeUncertainty, Mandatory, NoNotification
SasPositioning
Models the manageable characteristics of positioning in SAS-centric mode, as opposed to
RNC-centric mode.

Attributes:
enabledSasFeatures, NoNotification
pcapSasRespTime, NoNotification
SecurityHandling
Models manageable characteristics for the security handling algorithm. Only parameters
that are valid for the whole RNC are handled.
Only one instance of this MO class can exist. The singleton instance will be created
automatically by the system at first restart. The RDN of the instance will be
"SecurityHandling=1". The singleton instance cannot be deleted.
For more information see RNC MOM, ref [2].
Attributes:
ciphering
Page 226
LOGICAL VIEW REPORT
ServiceArea
This MOC models manageable characteristics of a Service Area in the RNC.
Attributes:
sac, Mandatory
Sid
This MO Type models manageable characteristics for the system information
Attributes:
updateCellReattsNo, Mandatory, NoNotification
noOfMaxDrxCycles, Mandatory, NoNotification
noOfMibValueTagRetrans, Mandatory, NoNotification
sib1
sib3
sib5
sib7
sib11
sib12
sib7ExpirationTimeFactor
sib2, NoNotification
sb1, NoNotification
schedulingBlockEnabled, NoNotification
sib18, NoNotification
SpDevicePool
Container MOC.
Attributes:
SpiQosClass
Models the manageable characteristics of mapping SPI QoS settings to Flow Control
activities.
Value part of the RDN is the SPI value.
Page 227
LOGICAL VIEW REPORT
Attributes:
flowControl, Mandatory, NoNotification
Subrack
Container MOC.
Attributes:
SystemFunctions
Container MOC.
Attributes:
TcMap
Models the manageable characteristics of RAB parameters mapping to the QoS settings
like SPI.
Attributes:
gbrRangeEnd, Mandatory, NoNotification
gbrRangeStart, Mandatory, NoNotification
qosRef, Mandatory, NoNotification
tdRangeEnd, Mandatory, NoNotification
tdRangeStart, Mandatory, NoNotification
TimDevice
This MO Type represents a device individual of the device type Timing Unit device.
Page 228
LOGICAL VIEW REPORT
Attributes:
administrativeState, Mandatory, NoNotification
TimDeviceSet
Container MOC
Attributes:
TnlCchQosClassProfile
Acts as a container for the instances that model the transport bearer Quality of Service
classes for the common channels.
Under this profile, one instance of the MO TnlQosClass is created by the system. The
TnlQosClass instance contains the Quality of Service settings to use for the common
channels.
Only used if the dual stack feature is configured.
Attributes:
TnlDchQosClassProfile
Acts as a container for the instances that model the mapping from DCH traffic classes to
transport bearer Quality of Service classes.
Attributes:
TnlHspaQosClassProfile
Acts as a container for the instances that model the mapping from HSPA traffic classes to
Page 229
LOGICAL VIEW REPORT
Attributes:
TnlIuQosClassProfile
Acts as a container for the instances that model the mapping from Iu traffic classes to
Attributes:
TnlQosClass
Models manageable characteristics of TNL QoS Class.
Attributes:
aal2QosClass, NoNotification
dscpEgress, NoNotification
dscpIngress, NoNotification
spi, NoNotification, ReadOnly
prefIubUserPlaneTransportOption, Mandatory, NoNotification
TrafficClass
Models the manageable characteristics of QoS Settings for traffic classes, i.e. RABs.
Page 230
LOGICAL VIEW REPORT
Attributes:
cnInd, Mandatory, NoNotification, Restricted
defaultQosRef, NoNotification
serviceInd, Mandatory, NoNotification, Restricted
ssd, Mandatory, NoNotification, Restricted
tcInd, Mandatory, NoNotification, Restricted
TrafficClassPsInt
Models the manageable characteristics of QoS settings for PS Interactive RABs.
Attributes:
qosRef, NoNotification
si, Mandatory, NoNotification, Restricted
thp, Mandatory, NoNotification, Restricted
TuDeviceGroup
Container MOC
Attributes:
UeMeasControl
This MOC models manageable characteristics for
UE measurments.
Page 231
LOGICAL VIEW REPORT
Attributes:
reportingRange1a, Mandatory
reportingRange1b, Mandatory
hysteresis1c, Mandatory
hysteresis1d, Mandatory
hysteresis2d, Mandatory
hysteresis2f, Mandatory
utranRelThresh3aEcno
Old name: utranThresh3a
utranRelThresh3aRscp
gsmThresh3a, Mandatory
hysteresis3a, Mandatory
measQuantity1, Mandatory
ueTxPowerThresh6b, Mandatory
usedFreqRelThresh4_2bEcno, Mandatory
usedFreqRelThresh4_2bRscp, Mandatory
hyst4_2b, Mandatory
nonUsedFreqThresh4_2bEcno
nonUsedFreqThresh4_2bRscp
usedFreqThresh2dEcnoDrnc, Mandatory
usedFreqThresh2dRscpDrnc, Mandatory
usedFreqRelThresh2fEcno, Mandatory
usedFreqRelThresh2fRscp, Mandatory
hysteresis1a, Mandatory
hysteresis1b, Mandatory
reportingInterval1a, Mandatory
reportingInterval1c, Mandatory
timeToTrigger1a, Mandatory
timeToTrigger1b, Mandatory
timeToTrigger1c, Mandatory
timeToTrigger1d, Mandatory
timeToTrigger2dEcno
timeToTrigger2fEcno
timeToTrigger3a, Mandatory
timeTrigg4_2b, Mandatory
timeTrigg6b, Mandatory
hsHysteresis1d
hsQualityEstimate
hsTimeToTrigger1d
filterCoefficient1
filterCoefficient2
utranCoefficient3
gsmCoefficient3
filterCoeff6
filterCoeff4_2b
w1a
w1b
usedFreqW2d
usedFreqW2f
usedFreqW4_2b
utranW3a
nonUsedFreqW4_2b
timeToTrigger2dRscp
timeToTrigger2fRscp
utranRelThreshRscp
gsmFilterCoefficient3
utranFilterCoefficient3
event1dRncThreshold
event1dRncOffset
timeToTrigger6d
txPowerConnQualMonEnabled
Page 232
LOGICAL VIEW REPORT
UePositioning
Models the manageable characteristics for UE positioning.
Attributes:
enabledPositioningFeatures
cellIdPosQualities, Mandatory
clientTypeMapping, Mandatory
UeRc
Models a Radio Connection Configuration corresponding to a combination of 0 or 1
UeRcRrc MO types and 0, 1 or 2 UeRcRab MO types.
Attributes:
userLabel
Sub: BCG
serviceOffset2dEcno
serviceOffset2dRscp
UeRcEdchFlow
Models the manageable characteristics of an E-DCH MAC-d flow.
Attributes:
harqTransmUlMax, Mandatory, NoNotification
UeRabType
The UeRabType MO Type models manageable characteristics for a RAB type that is
supported. This MO type defines the Traffic Descriptor parameters for the connection
between the RNC and CN. The Traffic Descriptor is used at e.g. request of CEP.
Page 233
LOGICAL VIEW REPORT
Attributes:
trBearerQosClass, NoNotification
UeRcPhyChEdch
Models the manageable characteristics of the E-DCH transport channel.
Attributes:
eulHarqRv, NoNotification
UeRcRab
Models manageable characteristics related to a RAB part of a Radio Connection.
Defines the Traffic Descriptor parameters for the AAL2 connection between the RNC
and RBS for the RAB Speech leg. The Traffic Descriptor is used at request of CEP.
Attributes:
fcState, NoNotification
UeRcRrc
Models manageable characteristics related to an RRC part of a Radio Connection.
Defines the Traffic Descriptor parameters for the AAL2 connection between the RNC
and RBS for the RRC leg. The Traffic Descriptor is used at request of CEP.

Attributes:
Page 234
LOGICAL VIEW REPORT
UeRcTrCh
This MO type models manageable characteristics related to a Transport Channel (TrCh)
of a Radio Connection.
Attributes:
blerQualityTargetDl, Mandatory, NoNotification
blerQualityTargetUl, Mandatory, NoNotification
Ura
Models the manageable characteristics for a UTRAN Registration Area (URA) in the
RNC. A URA consists of a number of UtranCells but span only cells within the same
RNC. A URA is used by UTRAN to serve UEs in the URA_PCH state.
Attributes:
userLabel
uraIdentity, Mandatory
UtranNetwork
Models the manageable characteristics of a Utran Network.
Attributes:
aliasPlmnIdentities, Restricted
plmnIdentity, Mandatory
reservedBy, Restricted, ReadOnly
userLabel
WcdmaCarrier
Models the assignment of frequency bands to frequency numbers both in this RNC and in
external RNCs. Preferred HO type for Active Set cells in an external RNC can also be
assigned.
Page 235
LOGICAL VIEW REPORT
Attributes:
defaultHoType
freqBand
sib5bisEnabled
uarfcnDl
userLabel
References to MOs in the RNC Equipment View

As identities in P1, WRAN CM uses hardcoded Local Distinguished Name (LDN) values for
the corresponding Managed Objects. These Managed Objects are created at Network Element
installation by their Element Manager (see [14], [15] and [16]):
For more information see ref. [31]
RncModule=1
Page 236
LOGICAL VIEW REPORT
RncModule=2
RncModule=3
RncModule=4
RncModule=5
Page 237
LOGICAL VIEW REPORT
RncModule=6
RncModule=7
RncModule=8
RncModule=9
Page 238
LOGICAL VIEW REPORT
RncModule=10
RncModule=11
RncModule=12
RncModule=13
Page 239
LOGICAL VIEW REPORT
RncModule=14
RncModule=15
RncModule=16
RncModule=17
Page 240
LOGICAL VIEW REPORT
RncModule=18
RncModule=19
RncModule=20
RncModule=21
Page 241
LOGICAL VIEW REPORT
RncModule=22
RncModule=23
RncModule=24
RncModule=25
Selfmanagement
These MIMs are described in [8] and the delivered XML-file for selfmanagement.
The MO distinguished names for "AdmDomain" and "Admnode" are configurable by ipf-
files.
Page 242
LOGICAL VIEW REPORT

CellIdAlreadyDefined
Thrown by CMS when creating an ExternalUtranCell MO.
ActionNotSupported
CacheIsSynchronized
MandatoryAttrMissingAtCreate
PlmnIdAlreadyDefined
Thrown by CMS when creating an ExternalGsmPlmn MO.
LocationAreaIdAlreadyDefined
Thrown by CMS when creating a LocationArea MO.
RoutingAreaIdAlreadyDefined
Thrown by CMS when creating a RoutingArea MO.
ServiceAreaIdAlreadyDefined
Thrown by CMS when creating a ServiceArea MO.
General DataTypes, Definitions and Exceptions

LogFilterParameters
Attributes:
paramType : string
paramValue : string
UserPreferencesParameters
Attributes:
prefName : string
prefValue : string
MimVersionType
Attributes:
mimVersion : string
TimeDiffData
Structure contains time differance data.
Page 243
LOGICAL VIEW REPORT
Attributes:
referenceTimeDiffToCell : long, Default = 0, Range = 0..38400
This parameter indicates the timing difference between the CPCCH's of the source and the target cells.
This parameter is optional and is only used when the target cell is an external UTRAN cell.
Unit: Chips
Ref. [2]
stepSize : long, Default = 0, Range = 0,40,256,2560

0: not used
Step size: 40, 256 or 2560 chips.
Ref. [2]
AseLoadThresholdUlSpeech
Attributes:
amr12200 : long
Threshold to be used in the initial AMR rate selection algorithm for selecting AMR12.2 speech codec in setup
of speech requests. Only applicable when establishing an AMR-NB multi-rate RAB.
Unit: % of UL Ase load

Resolution: 1
amr7950 : long

Resolution: 1
amr5900 : long
Threshold to be used in the initial AMR rate selection algorithm for selecting AMR5.9 speech codec in setup of
speech requests. Only applicable when establishing an AMR-NB multi-rate RAB.

Resolution: 1
PwrLoadThresholdDlSpeech
Attributes:
amr12200 : long
Unit: % of DL power load

Resolution: 1
amr7950 : long

Resolution: 1
amr5900 : long
Threshold to be used in the initial AMR rate selection algorithm for selecting AMR5.9 speech codec in setup of
speech requests. Only applicable when establishing an AMR-NB multi-rate RAB.

Resolution: 1
Page 244
LOGICAL VIEW REPORT
RateSelectionPsInteractive
Attributes:
channelType : SupportedChannelTypes
Defines whether FACH or DCH is selected.
FACH: PS Interactive RABs are established on a common channel.
DCH: PS Interactive RABs are established on a dedicated channel with a rate set in accordance with the default
rate defined for the attributes ulPrefRate and dlPrefRate.
Unit: N/A
Resolution: N/A
ulPrefRate : long
Preferred UL rate applicable both when setting up a non-EUL PS Interactive RAB, and when increasing the UL
rate of a PS interactive RAB from a lower rate than the preferred rate.
Unit: kbps
Resolution: N/A
dlPrefRate : long
Preferred DL rate applicable both when setting up a non-HSDPA PS Interactive RAB, and when increasing the
DL rate of a PS interactive RAB from a lower rate than the preferred rate.
Unit: kbps
Resolution: N/A
AreaDataType
Attributes:
valid : boolean
planned : boolean
NotFoundException
The specified MO instance has not been found
IncompatibleVersionsOfNEMIBAndMirrorMIB
NEIsNotCONNECTED
AutoIntegrated
Attributes:
NO : long = 0
YES : long = 1
BooleanVals
Attributes:
FALSE : long = 0
TRUE : long = 1
Page 245
LOGICAL VIEW REPORT
CellCapability
Contains capability information for external cells.
Attributes:
hsdschSupport : OnOffVals, Default = OFF
Capability information indicating if HS is supported in the cell.
Unit: N/A
Resolution: N/A
edchSupport : OnOffVals, Default = OFF

Capability information indicating if EUL is supported in the cell
Unit: N/A
Resolution: N/A
edchTti2Support : OnOffVals, Default = OFF

Capability information indicating if 2 ms TTI EUL is supported in the cell
Unit: N/A
Resolution: N/A
enhancedL2Support : OnOffVals, Default = OFF

Indicates whether Enhanced Layer 2 is supported or not.
Unit: N/A
Resolution: N/A
HcsSib3Config
Contains parameters that will be mapped to Hierachical Cell Structure IEs in System
Information Block 3.
Attributes:
hcsPrio : long
Specifies the value of the Information Element HCS_PRIO in System information Block 3. For the description
of this Information Element, see 3GPP TS 25.331.
Unit: N/A
Resolution: 1
qHcs : long
Specifies the value of the Information Element Qhcs in System information Block 3. For the description of this
Information Element, see 3GPP TS 25.331.
Unit: N/A
Resolution: 1
sSearchHcs : long
Specifies the value of the Information Element SsearchHCS in System information Block 3. For the description
of this Information Element, see 3GPP TS 25.331.
Unit: N/A
Resolution: 2
HcsUsage
Contains parameters that will be mapped to IE "Use of HCS" in System Information
Blocks 11 and 12.
Page 246
LOGICAL VIEW REPORT
Attributes:
idleMode : BooleanVals
Specifies the value of the Information Element "Use of HCS" in System information Block 11. For the
description of this Information Element, see 3GPP TS 25.331.
Unit: N/A
Resolution: N/A
connectedMode : BooleanVals
Specifies the value of the Information Element "Use of HCS" in System information Block 12. For the
description of this Information Element, see 3GPP TS 25.331.
Unit: N/A
Resolution: N/A
IntegrationSequence
Attributes:
plannedAreaName : string
The Planned Area Name.
userId : string
The id of the user who specified this Plan to be auto activated.
OnOffVals
Attributes:
OFF : long = 0
ON : long = 1
SupportedAmrNbModes
Attributes:
SINGLE_RATE : long = 0
MULTI_RATE : long = 1
SupportedChannelTypes
Attributes:
DCH : long = 0
FACH : long = 1
SupportedConnStatus
Attributes:
NEVER_CONNECTED : long = 1
CONNECTED : long = 2
DISCONNECTED : long = 3
SupportedMimSwitchPolicy
Attributes:
RANOS_FOLLOWS : long = 1
NO_SWITCH : long = 2
NE_FOLLOWS : long = 3
UPGRADE_ATTEMPTED : long = 4
Page 247
LOGICAL VIEW REPORT
SupportedMirrorMibSynchStatus
Attributes:
TOPOLOGY : long = 1
ATTRIBUTE : long = 2
SYNCHRONIZED : long = 3
UNSYNCHRONIZED : long = 4
SupportedMirrorMibUpdateStatus
Attributes:
UPDATING : long = 1
IDLE : long = 2
SupportedNeType
Attributes:
RNC : long = 1
NODEB : long = 2
RANAG : long = 3
ENODEB : long = 4
SupportedProcType
Attributes:
PRIMARY : long = 1
SECONDARY : long = 2
SupportedStandaloneSrbRates
Attributes:
SRB34 : long = 0
SRB136 : long = 1
Terminology
See Operations Support System (OSS) Glossary, 0033-AOM 901 017/2
References
[1] Cello Managed Object Model 1551-1/CSX 101 09 Uen
[2] RNC Managed Object Model Description, 155 54-AXD 105 03/1 Uen
[3] RBS Managed Object Model Description, 1/15554-CXA 104 389 Uen
[4] UniSaal Profile Managed Object Specification 7/10262-1/CSX10109 Uen
[5] VCL Traffic Descriptor Managed Object Specification 16/10262-1/CSX10109 Uen
[6] Transport Network Configuration, Function Specification, 2/15517-CRA 119 167/1 Uen
[7] Introduction to OSS, 11/1555-AOM 901 017/4 Uen

Programmer’s Guide, Self Management, 198 17-APR 901 64 Uen
[8] Programmer’s Guide, Self Management, 198 17-APR 901 64 Uen
Page 248
LOGICAL VIEW REPORT
[9] 3GPP TS 32.106-8 v4.0.0 Part 8: Name convention for Managed Objects (Release 99)
[12] Function Specification for Log Handling, 8/15517 - CRA 119 168/1
[13] Function description for Model Administration, 1/155 16 - AOM 901 26/1
[14] Node Configuration, 4/15516 - HRB 105102/1

Configuration of RNC, 13/0363-1/FCP 103 2566
[15] Configuration of RNC, 13/0363-1/FCP 103 2566
[16] UTRAN Transport Network Application Information, 1/15518 - HSD 101 02/1
[17] Naming Service Agent, Programmer’s Guide, 198 17 - APR 90171
[18] Alarm IRP Statement Of Compliance (SOC) at Mun Interface, 50/174 02 - HSD 101
02/1
[19] 3GPP TS 32.106-5 v3.1.0 Part 5: Basic Configuration IRP
[20] Managed Object Modelling DR,17/102 60-HSD 101 02/1
[21] 3GPP TS 32.622 v4.0.0 Generic Network Resource IRP.
[22] 3GPP TS 32.642 v4.0.0 UTRAN Network Resources IRP.
[23] Inter Radio Access Technology Handover Management (IRATHOM) Interface between
UTRAN and GSM, 180/15519-HSD10102/1
[24] 3GPP TS 32.652 v4.0.0 GERAN Network Resource IRP
[25] UTRAN Naming DR, 21/102 60-HSD 101 02/1
[26] 3G TS 32.102 v3.2.0 3G Telecom Management Architecture.
[28] 3GPP TS 32.623 v4.0.0 Generic Network Resource IRP: CORBA Solution Set
[29] 3GPP TS 32.643 v4.0.0 UTRAN Network Resources IRP: CORBA Solution Set
[30] 3GPP TS 32.653 v4.0.0 GERAN Network Resource IRP: CORBA Solution Set
[31] RNC Hardware Configuration 3/1551-FAB 102 614
[32] Network Resources IRP’s Statement of Compliance (SOC) at Mun Interface 63/174 02-
HSD 101 02/1
[33]Management of O&M IP Network 26/1551-CSX 101 09
Page 249
LOGICAL VIEW REPORT
TOTALS:
147 Logical Packages
396 Classes
LOGICAL PACKAGE STRUCTURE

Logical View
Ranos Node Model
RANOS_APPLICATION_MODEL
RANOS_RN_APPLICATION_MODEL
Rn Application Model Main View
RnApplication
UserDefEntityList
CellAndChannelProfile
RANOS_SUPPORT_APPLICATION_MODEL
Support Application Model Main View
LogFilter
UserPreferences
SupportApplication
RANOS_SUBNETWORK_MODEL
ManagementNode
SubNetwork
Subnetwork Model Main View
Segment
Site
Link
RbsGroup
IRPAgent
ExternalUtranPlmn
ExternalGsmPlmn
ExternalUtranCell
ExternalGsmCell
NotificationIRP
AlarmIRP
BulkCmIRP
IRATHOMUTRAN
Subnetwork Model IRP View
Subnetwork Model Site View
Areas
LocationArea
RoutingArea
ServiceArea
Subnetwork Model Areas View
PmIRP
Plmn
Subnetwork Model External Node View
Subnetwork Model TN Application View
Page 250
LOGICAL VIEW REPORT
TnApplication
MbmsServiceArea
General DataTypes, Definitions and Exceptions
RANOS COMMON MOC
BasicMeContext
Managed Object Types
General
General Operations
General Attributes
Alarms
General Notifications
General Exceptions
General Naming Rules
RANOS_INTERMIM_MODEL
SUBNETWORK APPLICATIONS
SUBNETWORK RBS_MIRROR
SUBNETWORK RNC_MIRROR
SUBNETWORK RANAG_MIRROR
SUBNETWORK ERBS_MIRROR
CELLO MODEL
Basic Cello Model
BasicManagedElement
Cello Attributes mirrored in Ranos
Cello MOs needed for Synch
MIRRORED MIMs
RANOS_RANAG_MIRROR_MODEL_H
Ranag Mirror Model Main View
Ranag Cello MOC's containing Ranos local attributes
Ranag Mirror and Cello Local View
References to MOs in the RANAG Equipment View
RANOS_RBS_MIRROR_MODEL_H
Rbs Mirror Model Main View
MeContext
Rbs Mirror and Cello Local View
Rbs Cello MOC's containing Ranos local attributes
Rbs Attributes Mirrored in Ranos
References to MOs in the RBS Equipment View
StandardRBS
RBS3104
RBS 3107, 3206M, 3018, 3418 and 3518
RBS Base Model
Rbs MOs needed for Synch
RANOS_RNC_MIRROR_MODEL_H
MeContext
UtranRelation
GsmRelation
Rnc Mirror Model Main View
Rnc Mirror and Cello Local View
Rnc Attributes Mirrored in Ranos
References to MOs in the RNC Equipment View
RncModule=1
RncModule=2
RncModule=3
RncModule=4
RncModule=5
RncModule=6
Page 251
LOGICAL VIEW REPORT
RncModule=7
RncModule=8
RncModule=9
RncModule=10
RncModule=11
RncModule=12
RncModule=13
RncModule=14
RncModule=15
RncModule=16
RncModule=17
RncModule=18
RncModule=19
RncModule=20
RncModule=21
RncModule=22
RncModule=23
RncModule=24
RncModule=25
Rnc Cello MOC's containing Ranos local attributes
Rnc MOs needed for Synch
Mirrored MIM name and Version Handling
RANOS_ERBS_MIRROR_MODEL_H
MeContext
ERbs CPP MOC's containing WRAN CM local attributes
ERbs Attributes Mirrored in WRAN CM
PLANNEDCONFIG_APPLICATION_MODEL
Planned Configuration Application Main View
Introduction
Abstract
Revision History
Purpose
Decisions
Open Issues
Assumptions
Document Overview
GeneralMO
Terminology
References
Selfmanagement
Administrative Domain and Node
System and System Component
Administrative Host
Delivery Module and Load Module
Managed Component
Page 252

WRAN CM Managed Object Model

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WRAN CM Managed Object Model

Uploaded by

Copyright:

Available Formats

WRAN CM Managed Object Model

1/15554-4/AOM 901 046 Uen rev. F1

Generated from model:

May 16th, 2008

Prepared: LMI/RO/SD John Heavey

© Ericsson AB 2008 - All Rights Reserved

LOGICAL VIEW REPORT.......................................................................................................................11

EthernetSwitchPort................................................................................. Error! Bookmark not defined.

LOGICAL PACKAGE STRUCTURE....................................................................................................250

LOGICAL VIEW REPORT

- RBS MOM 1/15554-CXA104389 rev Y2

2. The assumption in this document for expressing a reference from a MO to another MO

3. Datatypes described for attributes are IDL datatypes.

7. Direct containment between SubNetwork and ManagedElement is not supported. (optional

8. Containment between SubNetwork, MeContext and ManagedElement as described in ref.

12. The WRAN CM MOM shall be followed according to 3GPP R4.

13. Association MOC’s Supervisor and SiteAssociation will be not implemented.

14. Link MOC will be not implemented.

16. The RANAG MIM is based on the Cello MIM.

17. All Site information will be kept in Site MOC.

18. Location name information in 3GPP ManagedElement MO will be mapped to site

WRAN CM Function Application MIMs. MIMs containing functionality information of the

Ranos Node Model

1..* 0..* 0..*

<<MIM>> <<MIM>> <<MIM>> <<MIM>>

Rn Application Model Main View

Support Application Model Main View

Planned Configuration Application Model Main View

Subnetwork Model Main View

0..n 0..n < <MOClass> >

Subnetwork Model IRP View

Subnetwork Model Site View

Subnetwork Model Areas View

Subnetwork Model External Node View

Subnetwork Model TN Application View

ERbs Mirror Model Main View

Ranag Mirror Model Main View

Rbs Mirror Model Main View

Rnc Mirror Model Main View

<<MIM>> <<MIM>> <<MIM>> <<MIM>>

<< MOCl as s >>

1..n neLink Relations

Managed Object Types

Alarms generated by Managed Components in the Self Management MIB:

Managed Object Class (MOC): Managed Component (managedComponent MO from

Managed Object Class (MOC): Managed Component (managedComponent MO from

Managed Object Class (MOC): Managed Component (managedComponent MO from

General Naming Rules

rncMimVersion : string, NoNotification

numEagchCodes : long, NoNotification

Changing this attribute may affect traffic.

numEhichErgchCodes : long, NoNotification

Changing this attribute may affect traffic.

eulMaxTargetRtwp : long, NoNotification

maxFach1Power : long, NoNotification

maxFach2Power : long, NoNotification

sccpchOffset : long, NoNotification

A change of this attribute may affect traffic.

rncMimVersion : string, NoNotification

pOffset1Fach : long, NoNotification

pOffset3Fach : long, NoNotification

deltaAck1 : long, NoNotification

deltaNack1 : long, NoNotification