wran cm managed object model

7/17/2019 WRAN CM Managed Object Model

http://slidepdf.com/reader/full/wran-cm-managed-object-model 1/252

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 writtenpermission of the copyright owner.

The contents of this document are subject to revision without notice due tocontinued progress in methodology, design and manufacturing.

Ericsson shall have no liability for any error or damage of any kind resulting fromthe use of this document.



LOGICAL VIEW REPORT

TABLE OF CONTENTS

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

I NTRODUCTION ..........................................................................................................................................11 ABSTRACT .................................................................................................................................................11

R EVISION HISTORY ....................................................................................................................................11 PURPOSE ....................................................................................................................................................13 DECISIONS .................................................................................................................................................13 OPEN ISSUES ..............................................................................................................................................14 ASSUMPTIONS............................................................................................................................................14 DOCUMENT OVERVIEW..............................................................................................................................15 LOGICAL VIEW ..........................................................................................................................................15 R ANOS NODE MODEL ................................................................................................................................16 R N 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 R ANAG MIRROR MODEL MAIN VIEW ........................................................................................................21 R BS MIRROR MODEL MAIN VIEW .............................................................................................................22 R NC 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 R ULES .........................................................................................................................30 RANOS_APPLICATION_MODEL.........................................................................................................31 RANOS_RN_APPLICATION_MODEL .................................................................................................31

EulProfile..............................................................................................................................................31 FACHPROFILE ............................................................................................................................................33 HSDSCHPROFILE ........................................................................................................................................35

MBMSCCHPROFILE ....................................................................................................................................35 PCHPROFILE...............................................................................................................................................43 R ACHPROFILE............................................................................................................................................44 R NAPPLICATION ........................................................................................................................................46

RnApplication.......................................................................................................................................46 USER DEFE NTITYLIST ................................................................................................................................46

UserDefEntityList .................................................................................................................................46 UTRANCELLPROFILE .................................................................................................................................46 DATA TYPES, DEFINITIONS AND EXCEPTIONS............................................................................................64

SupportedMeasQuantities.....................................................................................................................64



LOGICAL VIEW REPORT

SupportedReservedStates......................................................................................................................64 RANOS_SUPPORT_APPLICATION_MODEL......................................................................................64 LOGFILTER ................................................................................................................................................64

LogFilter...............................................................................................................................................64 SUPPORTAPPLICATION...............................................................................................................................65

SupportApplication...............................................................................................................................65 USER PREFERENCES....................................................................................................................................65

UserPreferences ...................................................................................................................................65 PLANNEDCONFIG_APPLICATION_MODEL.....................................................................................64 BREAK POINT .............................................................................................................................................64

BreakPoint............................................................................................................................................64 PLANNEDAREAPROPERTIES.......................................................................................................................65

PlannedAreaProperties ........................................................................................................................65 PLANNEDCONFIGAPP ................................................................................................................................65

PlannedConfigApp................................................................................................................................65 DATA TYPES, DEFINITIONS AND EXCEPTIONS............................................................................................98

ActivationInformation...........................................................................................................................98

ActivationScheme..................................................................................................................................98 LastCommit...........................................................................................................................................98

RANOS_SUBNETWORK_MODEL .......................................................................................................69 ALARMIRP ................................................................................................................................................70

AlarmIRP..............................................................................................................................................70 AREAS .......................................................................................................................................................70

Areas.....................................................................................................................................................70 ATMLINK ...................................................................................................................................................71

AtmLink.................................................................................................................................................71 BULK CMIRP..............................................................................................................................................72

BulkCmIRP...........................................................................................................................................72 EXTERNALGSMCELL .................................................................................................................................72

ExternalGsmCell ..................................................................................................................................72 EXTERNALGSMPLMN ................................................................................................................................74

ExternalGsmPlmn.................................................................................................................................74 EXTERNALTRANSPORT NETWORK ..............................................................................................................76

ExternalTransportNetwork...................................................................................................................76 EXTERNALUTRANCELL .............................................................................................................................77

ExternalUtranCell ................................................................................................................................77 EXTERNALUTRANPLMN ............................................................................................................................81

ExternalUtranPlmn...............................................................................................................................81 EXTERNALVIEWABLE NODE.......................................................................................................................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

MANAGEMENT NODE .................................................................................................................................86 ManagementNode.................................................................................................................................86

MBMSSERVICEAREA...........................................................................................................................86 MbmsServiceArea.................................................................................................................................86

NOTIFICATIONIRP .....................................................................................................................................88



LOGICAL VIEW REPORT

NotificationIRP.....................................................................................................................................88 PLMN .........................................................................................................................................................88

Plmn......................................................................................................................................................88 PMIRP .......................................................................................................................................................89

PmIRP...................................................................................................................................................89 R BSGROUP.................................................................................................................................................90

RbsGroup..............................................................................................................................................90 R OUTINGAREA ..........................................................................................................................................90

RoutingArea..........................................................................................................................................90 SEGMENT ...................................................................................................................................................91

Segment.................................................................................................................................................91 SERVICEAREA............................................................................................................................................93

ServiceArea...........................................................................................................................................93 SITE ...........................................................................................................................................................94

Site ........................................................................................................................................................94 SUB NETWORK ...........................................................................................................................................96

SubNetwork...........................................................................................................................................96 T NAPPLICATION ........................................................................................................................................97

TnApplication .......................................................................................................................................97 VirtualPath ...........................................................................................................................................97

DATA TYPES, DEFINITIONS AND EXCEPTIONS............................................................................................98 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 .......................................................................................................Err or! Bookmark not defi ned. Ds0Bundle ..........................................................................................................................................107 E1PhysPathTerm................................................................................................................................107 E1Ttp ..................................................................................................................................................108 E3PhysPathTerm................................................................................................................................108 Equipment...........................................................................................................................................108 EthernetLink .......................................................................................................................................108

EthernetSwitch........................................................................................Err or! Bookmark not defi ned.



LOGICAL VIEW REPORT

EthernetSwitchPort.................................................................................Err or! Bookmark not defi ned. EtMfg ..................................................................................................................................................110 Etm1....................................................................................................................................................110 ExchangeTerminal..............................................................................................................................110

ExchangeTerminalIp...............................................................................Err or! Bookmark not defi ned. FastEthernet .......................................................................................................................................110 GeneralProcessorUnit ........................................................................................................................110 GigaBitEthernet......................................................................................Err or! Bookmark not defi ned.

ImaGroup............................................................................................................................................111 ImaLink...............................................................................................................................................112

InternalEthernetPort...............................................................................Err or! Bookmark not defi ned. 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



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

R ANAG CELLO MOC'S CONTAINING WRAN CM LOCAL ATTRIBUTES.....................................................149 Aal0TpVccTp ......................................................................................................................................149 Aal2PathVccTp...................................................................................................................................150 Aal5TpVccTp ......................................................................................................................................150 AtmCrossConnection ..........................................................................................................................150 AtmPort...............................................................................................................................................150 ManagedElement................................................................................................................................150 TransportNetwork...............................................................................................................................152 VclTp...................................................................................................................................................152 VpcTp..................................................................................................................................................152 VplTp ..................................................................................................................................................152

R EFERENCES TO MOS IN THE RANAG EQUIPMENT VIEW.......................................................................152 RANOS_RBS_MIRROR_MODEL_H...................................................................................................153 NodeBFunction...................................................................................................................................153

MECONTEXT............................................................................................................................................156 MeContext...........................................................................................................................................156

R BS CELLO MOC'S CONTAINING WRAN CM LOCAL ATTRIBUTES ..........................................................161 Aal0TpVccTp ......................................................................................................................................161 Aal2PathVccTp...................................................................................................................................161 Aal5TpVccTp ......................................................................................................................................161 AtmCrossConnection ..........................................................................................................................161



LOGICAL VIEW REPORT

AtmPort...............................................................................................................................................161 ManagedElement................................................................................................................................162 TransportNetwork...............................................................................................................................164 VclTp...................................................................................................................................................164 VpcTp..................................................................................................................................................164 VplTp ..................................................................................................................................................164

R BS ATTRIBUTES MIRRORED IN WRAN CM...........................................................................................164 AntennaBranch...................................................................................................................................164 AntFeederCable..................................................................................................................................165 AuxPlugInUnit....................................................................................................................................165 Carrier................................................................................................................................................165

DbccDevice.............................................................................................Err or! Bookmark not defi ned. DbccDeviceSet........................................................................................Err or! Bookmark not defi ned. Equipment...............................................................................................Err or! Bookmark not defi ned. ExternalTma ...........................................................................................Err or! Bookmark not defi ned. Iub...........................................................................................................Err or! Bookmark not defi ned. IubDataStreams......................................................................................Err or! Bookmark not defi ned. NbapCommon.........................................................................................Err or! Bookmark not defi ned. NbapDedicated.......................................................................................Err or! Bookmark not defi ned. NodeSynchTp..........................................................................................Err or! Bookmark not defi ned. PlugInUnit .............................................................................................. Err or! Bookmark not defi ned. RbsLocalCell ..........................................................................................Err or! Bookmark not defi ned. RetDevice................................................................................................Err or! Bookmark not defi ned. RetDeviceSet.......................................................................................................................................173 RetuDeviceGroup ...............................................................................................................................173 Sector..................................................................................................................................................174 SectorAntenna.....................................................................................................................................174 Slot......................................................................................................................................................175 Subrack ...............................................................................................................................................175 TimDevice...........................................................................................................................................175 TimDeviceSet......................................................................................................................................175 TuDeviceGroup...................................................................................................................................175 TxDeviceGroup...................................................................................................................................175

R EFERENCES TO MOS IN THE RBS EQUIPMENT VIEW .............................................................................176 STANDARDRBS .......................................................................................................................................176 RBS3104.................................................................................................................................................177 RBS 3107, 3206M, 3018, 3418 AND 3518 ...............................................................................................178 RBS BASE MODEL...................................................................................................................................178 R BS 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

GSMR ELATION.........................................................................................................................................196 GsmRelation .......................................................................................................................................196

MECONTEXT............................................................................................................................................197



LOGICAL VIEW REPORT

MeContext...........................................................................................................................................197 UTRANR ELATION.....................................................................................................................................201

UtranRelation.....................................................................................................................................201 R NC CELLO MOC'S CONTAINING WRAN CM LOCAL ATTRIBUTES .........................................................202

Aal0TpVccTp ......................................................................................................................................203 Aal2PathVccTp...................................................................................................................................203 Aal5TpVccTp ......................................................................................................................................203 AtmCrossConnection ..........................................................................................................................203 AtmPort...............................................................................................................................................203 ManagedElement................................................................................................................................203 TransportNetwork...............................................................................................................................205 VclTp...................................................................................................................................................205 VpcTp..................................................................................................................................................205 VplTp ..................................................................................................................................................205

R NC ATTRIBUTES MIRRORED IN WRAN CM ..........................................................................................206 AgpsPositioning..................................................................................................................................206 ArpMap...............................................................................................................................................206

ArpQosClassProfile............................................................................................................................206

CchFrameSynch..................................................................................................................................207 ChannelSwitching...............................................................................................................................207 CnOperator.........................................................................................................................................209 CoverageRelation...............................................................................................................................209

DchFrameSynch .................................................................................................................................209 DchMap ..................................................................................................Err or! Bookmark not defi ned. 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



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.....................................................................................................Err or! Bookmark not defi ned.

TimDevice...........................................................................................................................................228

TimDeviceSet..........................................................................................Err or! Bookmark not defi ned. TnlDchQosClassProfile..........................................................................Err or! Bookmark not defi ned. TnlHspaQosClassProfile ........................................................................Err or! Bookmark not defi ned. TnlIuQosClassProfile .............................................................................Err or! Bookmark not defi ned. TnlQosClass............................................................................................Err or! Bookmark not defi ned. 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

R EFERENCES TO MOS IN THE RNC EQUIPMENT VIEW.............................................................................236 R NCMODULE=1.......................................................................................................................................236 R NCMODULE=2.......................................................................................................................................237 R NCMODULE=3.......................................................................................................................................237 R NCMODULE=4.......................................................................................................................................237 R NCMODULE=5.......................................................................................................................................237 R NCMODULE=6.......................................................................................................................................238 R NCMODULE=7.......................................................................................................................................238 R NCMODULE=8.......................................................................................................................................238

R NCMODULE=9.......................................................................................................................................238 R NCMODULE=10.....................................................................................................................................239 R NCMODULE=11.....................................................................................................................................239 R NCMODULE=12.....................................................................................................................................239 R NCMODULE=13.....................................................................................................................................239 R NCMODULE=14.....................................................................................................................................240 R NCMODULE=15.....................................................................................................................................240 R NCMODULE=16.....................................................................................................................................240 R NCMODULE=17.....................................................................................................................................240 R NCMODULE=18.....................................................................................................................................241



LOGICAL VIEW REPORT

R NCMODULE=19.....................................................................................................................................241 R NCMODULE=20.....................................................................................................................................241 R NCMODULE=21.....................................................................................................................................241 R NCMODULE=22.....................................................................................................................................242 R NCMODULE=23.....................................................................................................................................242 R NCMODULE=24.....................................................................................................................................242 R NCMODULE=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 R EFERENCES ............................................................................................................................................248

TOTALS: ...................................................................................................................................................250

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



LOGICAL VIEW REPORT

LOGICAL VIEW REPORT

Introduction

This MOM document provides information to obtain interoperability to external systemsthrough 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 definethe 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



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 beenincluded:

- 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) WorkItems 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



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:- RNC MOM 15554-AXD10503/1 rev AX

- 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) WorkItems 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:- RNC MOM 15554-AXD10503/1 rev AX

- 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) WorkItems 1.1 and 1.10

Purpose

The purpose of this document is to specify the Managed Objects accessible by WRAN CM

applications.

Decisions



LOGICAL VIEW REPORT

Open Issues

-

Assumptions

1. All management information in the Network Elements are communicated to WRAN CMthrough 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 toWRAN 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.



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 thenetwork 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 InformationModel.

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



LOGICAL VIEW REPORT

Ranos Node Model

RANOS_SUBNETWORK

_MODEL

<<MIM>>

RANOS_RNC_MIRROR

_MODEL_H

<<MIM>>

RANOS_RBS_MIRROR

_MODEL_H

<<MIM>>

RANOS_APPLICATION_

MODEL

<<MIM>>1

1..* 0..*

Selfmanagement

<<MIM>>

RANOS_RANAG_MIRR

OR_MODEL_H

<<MIM>>

0..*

RANOS_ERBS_MIRRO

R_MODEL_H

<<MIM>>

0..*

Rn Application Model Main View

UserDefEntityList

<<MOClass>>

FachProfile

<<MOClass>>

PchProfile

<<MOClass>>

RachProfile

<<MOClass>>

UtranCellProfile

<<MOClass>>

HsdschProfile(from CellAndChannelProfile)

<<MOClass>>

EulProfile(from CellAndChannelProfile)

<<MOClass>>

RnApplication

<<MOClass>>

0..*

1

0..*

1

0..*

1

0..*

1

0..*

1

0..*

1

0..*

1

0..*

1

0..*

1

0..*

1

0..*

1

0..*

1

0..*

1

0..*

1

MbmsCchProfile(from CellAndChannelProfile)

<<MOClass>>

0..*

11

0..*



LOGICAL VIEW REPORT

Support Application Model Main View

LogFilter <<MOClass>>

UserPreferences<<MOClass>>

SupportApplication<<MOClass>>

Planned Configuration Application Model Main View

PlannedConfigurationApp(from PLANNEDCONFIG_APPLICATION_MODEL)

<<MOClass>>

PlannedAreaProperties(from PLANNEDCONFIG_APPLICATION_MODEL)

<<MOClass>>

0..n

BreakPoint(from PLANNEDCONFIG_APPLICATION_MODEL)

<<MOClass>>

0..n

1

0..n

1

0..n



LOGICAL VIEW REPORT

Subnetwork Model Main View

IRPAgent<<MOClass>>

ManagementNode<<MOClass>>

11

Segment<<MOClass>>

Site<<MOClass>>

Link<<MOClass>>

RbsGroup<<MOClass>>

Areas<<MOClass>>

ExternalUtranPlmn<<MOClass>>

ExternalUtranCell<<MOClass>>

0..n

1

0..n

1

<<MOBidirAssoc>>

ExternalGsmCell<<MOClass>>

ExternalGsmPlmn<<MOClass>>

0..n

1

0..n

1

<<MOBidirAssoc>>

ExternalViewableNode<<MOClass>>

SubNetwork<<MOClass>>

11

+subNet 0..n0..n

0..n0..n+subNet

1..n

1

+rns1..n

1<<MOUnidirAssoc>>

0..n0..n

+subNet

0..n0..n

+subNet

0..n

1

0..n

+rns1

11

+subNet

0..n0..n

+subNet

0..n0..n

+subNet

0..n0..n

+subNet

0..n0..n

+subNet

+subNet

0..n0..n

Subnetwork Model IRP View


0..n0..n

ManagedElement<<MOClass>>

NotificationIRP<<MOClass>>

AlarmIRP<<MOClass>>

BulkCmIRP<<MOClass>>

IRATHOMUTRAN<<MOClass>>

ManagementNode<<MOClass>>

1

+subNet

1

+ManagedBy+Manages

MgmtAssociation

<<MOBidirAssoc>>

MimInfo<<MOClass>>

PmIRP<<MOClass>>

IRPAgent<<MOClass>>

0..10..1 0..10..1 0..10..1 0..10..1

11



LOGICAL VIEW REPORT

Subnetwork Model Site View

Subnetwork Model Areas View

SubNetwork

<<MOClass>>

0..n

+theSubNetwork

0..n+theSubNetwork

RoutingArea

<<MOClass>>

ServiceArea

<<MOClass>>

Areas

<<MOClass>>

1

+subNet

+theAreas 1SubNetwork_to_Areas

<<MOContain>>

LocationArea

<<MOClass>>

0..1000

+theRoutingArea

0..1000

+theLocationArea

LocationArea_to_RoutingArea

<<MOContain>>

0..15000

+theServiceArea

0..15000

+theLocationArea

LocationArea_to_ServiceArea

<<MOContain>>

Plmn

<<MOClass>>

0..10+thePlmn 0..10

+theAreas

Areas_to_Plmn

<<MOContain>>

0..300+theLocationArea 0..300

+thePlmn

Plmn_to_LocationArea

<<MOContain>>

MbmsServiceArea(from Mbm sServiceArea)

<<MOClass>>

0..15000

<<MOContain>>

0..15000

Plmn_to_MbmsServiceArea

+theMbmsServiceArea

+thePlmn



LOGICAL VIEW REPORT

Subnetwork Model External Node View

ExternalTransportNetwork<<MOClass>>

ExternalVplTp<<MOClass>>

0..n

1

0..n

1

ExternalViewableNode<<MOClass>>

0..n

1

0..n

1


+subNet

0..n0..n

Subnetwork Model TN Application View



LOGICAL VIEW REPORT

SubNetwork

(f rom S ubNe twork)

<<MOClass>>

TnApplication(from TnA pplication)

<<MOClass>>

1

VirtualPath

(from TnA pplication)

<<MOClass>>

0..n

1

0..n

1

1

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].



LOGICAL VIEW REPORT

Rbs Mirror Model Main View


Rnc Mirror Model Main View


RANOS_INTERMIM_MODEL



LOGICAL VIEW REPORT

RANOS_APPLIC

ATION_MODEL

<<MIM>>

RANOS_RBS_MIRROR

_MODEL_H

<<MIM>>RANOS_RNC_MIRROR

_MODEL_H

<<MIM>>

RANOS_SUBNET

WORK_MODEL

<<MIM>>

RANOS_INTER

MIM_MODEL

<<InterMIM>>

RANOS_RANAG_MIRR

OR_MODEL_H

<<MIM>>RANOS_ERBS_MIRRO

R_MODEL_H

<<MIM>>

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.

RnApplication(f rom RnApplication)

<<MOClass>> SupportApplication(f rom SupportApplication)

<<MOClass>>

SubNetwork(from SubNetwork)

<<MOCl ass >>

0..n0..n

11

+subNet

SubNetToRnApplication

<<MOContain>>

11

+s ubNet

SubNetToSuppAppl

<<MOContain>>



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 ERBSMirrored MIM's.

IRPAgent(from IRPAgent)

<<MOClass>>

ENodeBFunction(from RANOS_ERBS_MIRROR_MODEL_H)

<<MOClass>>

Site(from Site)

<<MOClass>>

ManagementNode(from ManagementNode)

<<MOClass>>

1

+theManagementNode

+theIRPAgent1

ManagementNode_to_IRPAgent

<<MOContain>>

SubNetwork

<<MOClass>>0..n

+theSubNetwork

0..n

+theSubNetwork

0..n

+subNet+theSite

0..nSubNetwork_to_Site

1

+subNet+theManagementNode

1

SubNetwork_to_ManagementNode

<<MOContain>>

Segment

<<MOClass>>

0..n

+subNet

+theSegment

0..n

SubNetwork_to_Segment

<<MOContain>>

1

1..n

+theSegment

1

+rns

1..n

Seg ment_to_SubNetwork

<<MOUnidirAssoc>>

ManagedElement(from ERbs CPP MOCs containi ng WRAN CM local attributes)

<<MOClass>>

+theENodeBFunction

+theManagedElementManagedElement_to_ENodeBFunction

<<MOContain>>

1..n

1

+theManagedElement1..n

+theSite

1

associatedWith

<<MOBidirAssoc>>

+ManagedBy

+Manages

MgmtAssociation

<<MOBidirAssoc>>

MeContext(from MeContext)

<<MOClass>>

0..n+theMeContext

0..n

+theSubNetwork

SubNetwork_to_MeContext

<<MOContain>>

1

n

+theSegment

1+theMeContext

n

MeContext_to_Segment

<<MOUnidirAssoc>>

+theManagedElement

+theMeContext

MeContext_to_ManagedElement

<<MOContain>>

SUBNETWORK RBS_MIRRORThis 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 RBSMirrored MIM's.

Note that the local root, MeContext from RBS Mirrored MIM, is contained on the

SubNetwork (RNS) MOC.



LOGICAL VIEW REPORT

Segment

<<MOClass>>

RbsGroup(from RbsGroup)

<<MOClass>>

IRPAgent(from IRPAgent)

<<MOClass>>


0..n0..n

0..n

+subNet

0..n

1

1..n

1

+rns

1..n

<<MOUnidirAssoc>>

1 0..n

+rns

1 0..n

MeContext

<<MOClass>>

1

n

1

n

MeContextToSegment

<<MOUnidirAssoc>>

1

0..n

1

0..n

RbsGroupToMecontext

<<MOBidirAssoc>>

0..n0..n

SubNet workToMeContext

<<MOContain>>


<<MOClass>>

11

1

+subNet

1

Site(from Si te)

<<MOClass>>

0..n

+subNet

0..n

ManagedElement

<<MOClass>>

+Manages

+ManagedBy

MgmtAssociation

<<MOBidirAssoc>>

1

1..n

1

1..n

assoc iatedWith

<<MOBidirAssoc>>

IubLink

(from RANOS_RNC_ MIRROR_MODEL_F)

<<MOClass>>

NodeBFunction

<<MOClass>>0..1

0..n

0..1

0..n

0..1

0..1

+iubLinkNodeBFunction0..1

+nodeBFunctionIubLink0..1

ConnectedTo

<<MOBidirAssoc>>

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.



LOGICAL VIEW REPORT

IRPAgent

(from IRPAgent)

<<MOClass>>

MeContext(from RANOS_RANAG_M IRROR_MODEL _F)

<<MOClass>>

IurLink

<<MOClass>>

ManagedElement

<<MOClass>>

NodeBFunction(from RANOS_RBS_MIRROR_MODEL_F)

<<MOClass>>

ExternalUtranCell

<<MOClass>>

0..n0..n

ExternalUtranPlmn<<MOClass>>


<<MOClass>>

11

+ManagedBy

+Manages

MgmtAssociation

<<MOBidirAssoc>>

Site(from Si te)

<<MOClass>>

1..n

1

1..n

1

associatedWithRnc

<<MOBidirAssoc>>

Segment(from Se gment)

<<MOClass>>

MeContext

<<MOClass>>

1

n

1

n

MeContextToSegment

<<MOUnidirAssoc>>

+ranag

+rnc

neLinkRelations

<<MOBidirAssoc>>

ExternalUtranCell

(from ExternalUtranCell)

<<MOClass>>

1

0..n

1

0..n

<<MOBidirAssoc>>

ExternalGsmNetwork

<<MOClass>>

RncFunction

<<MOClass>>

0..640..64

0..n0..n

IubLink

<<MOClass>>

0..1

0..1

+nodeBFunctionIubLink

0..1

+iubLinkNodeBFunction0..1

ConnectedTo

<<MOBidirAssoc>>

0..n0..n

UtranRelation

<<MOClass>>

0..n

0..1

0..n

0..1

utranCellRef

<<MOUnidirAssoc>>

adjacentCell

<<MOUnidirAssoc>>

ExternalGsmPlmn

<<MOClass>>

SubNetwork(from SubNetwo rk)

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

0..n

+subNet

0..n0..n

+subNet

0..n

1

+subNet

1 0..n

+subNet

0..n

0..n

+subNet

0..n1

1..n

1

+rns

1..n

<<MOUnidirAssoc>>

1..n1..n

+r ns

RnsToMeContextCont

<<MOContain>>

1

1

1

1

RnsToMeContext

<<MOUnidirAssoc>>

0..n

+subNet

0..n

ExternalGsmCell

<<MOClass>>

0..n0..n

UtranCell

<<MOClass>>

0..15000..1500

0..1

0..n

0..1

0..n<<MOBidirAssoc>>

0..63

1

0..63

1

1

0..n

1

0..n

utranCellRef1

<<MOUnidirAssoc>>

0..n

0..1

0..n

0..1

adjacentCell

<<MOUnidirAssoc>>

ExternalGsmCell

(from ExternalGsmCell)

<<MOClass>>

1

0..n

1

0..n

<<MOBidirAssoc>>

0..n

+subNet

0..n

GsmRelation

<<MOClass>>

0..n

1

0..n

1

externalGsmCellRef

<<MOUnidirAssoc>>0..32

1

0..32

1

adjacentCell1

<<MOUnidirAssoc>>

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 inRANAG Mirrored MIM's.

Note that the local root, MeContext from RANAG Mirrored MIM, is contained in the global

root SubNetwork MOC.



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

createThe 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.



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: RadioNetworkIdThis 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 thesame 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 aninstance 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 theattribute 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.



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 ProblemSpecific 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.

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

Selfmanagement MIB)Managed Object Instance (MOI): FDN for the Managed Component

Perceived Severity : MajorProbable Cause : Storage Capacity Problem

Specific Problem : RSD_DB_Full



PSA_Expression_Threshold Alarm

This alarm is generated when the expression set by the PSA applicationhas crossed the threshold.

Managed Object Class (MOC): Managed Component (managedComponent MO fromSelfmanagement MIB)Managed Object Instance (MOI): FDN for the Managed Component

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" + usingmonitor + "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.



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:1The 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=47MeContext= 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 internaluse.

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 userto 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.



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 nodelevels, 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 inthe 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" accordingto 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.

EulProfileThis profile represents the profile for Eul radio channels. Several instances of the MO

Type can exist.



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, NoNotificationThe 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]



LOGICAL VIEW REPORT

FachProfile

This MO Type represents the profile for Fach radio channels. Several instances of the

MO Type can exist.



LOGICAL VIEW REPORT

Attributes:




CellAndChannelProfile managed object in display lists.

Sub: RNH

Ref. [2]

maxFach1Power : long, NoNotificationMaximum 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, NoNotificationMaximum 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, NoNotificationRadio timing offset inside a radio frame (SCCPCH parameter)

0: 0 chip1: 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]



LOGICAL VIEW REPORT

pOffset3Fach : long, NoNotificationPower 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 MOType can exist.



LOGICAL VIEW REPORT

Attributes:




HsdschProfile managed object in display lists.

Sub: RNH

Ref. [2]

deltaAck1 : long, NoNotificationThe 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, NoNotificationThe 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, NoNotificationThe 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



LOGICAL VIEW REPORT

Sub: RNH

Ref. [2]

initialCqiRepetitionFactor : long, NoNotification

The initial number of repeti tions for CQI report messages on HS-DPCCH.

Unit: N/A

Resolution: 1

Sub: RNH

Ref. [2]

initialAckNackRepetitionFactor : long, NoNotification

The initial number of repetit ions 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, NoNotificationThe 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 dBResolution: 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]



LOGICAL VIEW REPORT

codeThresholdPdu656 : long, NoNotificationThreshold 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, then656 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

MbmsCchProfileThis profile represents the profile for Mbms radio channels. Several instances of the MO

Type can exist.



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 preferredfrequency 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, NoNotificationControls 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/AResolution: N/A

Sub: RNH

Ref. [2]

mcchPowerOffset : long, NoNotificationThe 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, NoNotificationThe 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.

A consequence of changing the parameter is that all MBMS common channels in the cell are released. Thesystem will automatically establish the channels again. Operation state for MbmsCch will be set to disabled by




LOGICAL VIEW REPORT

When deactivation is inititaed, in case of MBMS sessions where this cell is Preferred Line (PL), all MTCHRadio Bearers (RBs) in the cell are released. In case of MBMS sessions where this cell is a non-PL cell, the


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




Unit: 0.01dB

Resolution : 25

Sub: RNH

Ref. [2]

michPowerOffset : long, NoNotification

MICH power .


MICH will also change.

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


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


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




Unit: 1 dB

Resolution: 1

Sub: RNH

Ref. [2]

mtch128PowerOffset : long, NoNotificationThe 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, NoNotificationThe 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



LOGICAL VIEW REPORT

Sub: RNH

Ref. [2]

mtch256PowerOffset : long, NoNotification

The power of the S-CPCCH used for MTCH 259.2 kbps transmission.




Unit: 0.1 dB

Resolution: 1

Sub: RNH

Ref. [2]



the TFCI field used for MTCH 259.2 kbps will also change.


Unit: 0.01 dB

Resolution: 25

Sub: RNH

Ref. [2]

mtch64PowerOffset : long, NoNotificationThe power of the S-CPCCH used for MTCH 64.8 kbps transmission.




Unit: 0.1 dB

Resolution: 1

Sub: RNH

Ref. [2]



the TFCI field used for MTCH 64.8 kbps wil l also change.


Unit: 0.01 dB

Resolution: 25

Sub: RNH

Ref. [2]

numNotificationInd : long, NoNotificationThe 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.



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, NoNotificationWhen 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 ServiceRestriction Information is scheduled on MCCH.


Unit: N/A

Resolution: N/A

Sub: RNH

Ref. [2]

qualityOffset : long, NoNotificationAdditional 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]



LOGICAL VIEW REPORT

PchProfile

This profile represents the profile for Pch radio channels. Several instances of the MO

Type can exist.

Attributes:

userLabel : string, Mandatory, NoNotification, Restricted, LengthRange = 0..128Provides support for a user defined label or name upon an object instance level.



Sub: RNH

Ref. [2]

pchPower : long, NoNotificationMaximum 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, NoNotificationPICH 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, NoNotificationRadio timing offset inside a radio frame (SCCPCH parameter)

0: 0 chip1: 256 chip

149: 38144 chip


Sub: RNH

Ref. [2]


Sub: RNH

Ref. [2]



LOGICAL VIEW REPORT

RachProfile

Thie MO Type represents the profile for Rach radio channels. Several instances of the

MO Type can exist.

Attributes:

userLabel : string, Mandatory, NoNotification, Restricted, LengthRange = 0..128Provides support for a user defined label or name upon an object instance level.



Sub: RNH

Ref. [2]

aichTransmissionTiming : long, NoNotificationAICH 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, NoNotificationAICH 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.A change of this attribute may affect traffic.

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]



LOGICAL VIEW REPORT

constantValueCprach : long, NoNotificationConstant 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]

rncMimVersion : string, NoNotification

The version of the RNC MIM for which this profile is created

Sub: RNH

Ref. [2]

preambleSignatures : long, NoNotificationPreamble signatures for PRACH.

Sub: RNH

Ref. [2]

subChannelNo : long, NoNotificationSub Channel Number.

Sub: RNH

Ref. [2]



LOGICAL VIEW REPORT

RnApplication

RnApplicationSystemCreated

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

UserDefEntityListThis 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:

userLabel : string, Mandatory, NoNotification, Restricted, LengthRange = 0..128Used 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, NoNotificationThis 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.



LOGICAL VIEW REPORT

Attributes:





Sub: RNH

Ref. [2]

qHyst1 : long, NoNotificationUsed 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.

A change of this attribute may affect traffic.Resolution 1 (=10bps).

0 : 0 bps

1 : 10 bps

2 : 20 bps...

40320: 403200 bps1600000: 16000000 bps

Sub: RNH

Ref. [2]

interRate : long, NoNotification

This parameter describes intermeiate rate for max. power mapping.




LOGICAL VIEW REPORT

Resolution 1 (=10bps).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.A change of this attribute may affect traffic.

Resolution 1 (=10bps).

0 : 0 bps

1 : 10 bps2 : 20 bps

......

1220: 1220 bps

......

1600000: 16000000 bps

Sub: RNH

Ref. [2]

maxPwrMax : long, NoNotificationThis 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, NoNotificationThis 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.A change of this attribute may affect traffic.



LOGICAL VIEW REPORT

Resolution1(=0.1dB)-350 : -35dB

-349 : -34.9dB

-348 : -34.8dB

....

-200 : -20dB

....150 : 15dB

Sub: RNH

Ref. [2]

compModeAdm : long, NoNotificationThis parameter describes admission limit for #RL in compressed mode in a cell.

Resolution 1.

Sub: RNH

Ref. [2]

iFOffset : long, NoNotificationThis 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, NoNotificationThis parameter describes hytsterese level for UL congestion measurements.

Resolution 1(10ms).

0 : 0ms

1 : 10ms2 : 20ms

......

6000 : 60000ms

Sub: RNH

Ref. [2]

iFCong : long, NoNotificationThis parameter describes the reset level for UL congestion measurements.

Resolution is 1 (0.1 dB).

0 : -112dBm1 : -111.9dBm......

130: (-99dBm)

621 : -50dBm

Sub: RNH

Ref. [2]

interFreqFddMeasIndicator : BooleanVals, NoNotification



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 inrelation 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, NoNotificationThe 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 dBm2 : -30 dBm

....

27 : 20 dBm

Sub: RNH

Ref. [2]

fachMeasOccaCycLenCoeff : long, NoNotificationFach 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.



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 tocontrol 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 bysystem 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, NoNotificationControl 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 reselectionquality 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



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 ifan 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]



LOGICAL VIEW REPORT

tmCongAction : long, NoNotification

Interval between Congestion Actions.

Used by congestion Control.

Resolution: 10mS. Initially set by system to100mS.

0: 0 mS10: 10 mS

...

60 000: 1min

releaseAseDl : long, NoNotificationAmount of ASE to be released in DL at each congestion action.

Used by Congestion Control.

Resolution: 1 ASE.

Initially set by the system to 10 ASE.

Sub: RNH

Ref. [2]

dlCodeAdm : long, NoNotificationAdmission 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, NoNotificationAdmission limit for admission on max. capacity (ASE level) in DL.

Used by Admission Control in subfunction Admission Request Handler.

Resolution: 1 ASE.Initially set by the system to 240 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]

rncMimVersion : string, NoNotification

The version of the RNC MIM for which this profile is created

Sub: RNH

Ref. [2]

beMarginAseUl : long, NoNotification



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 inDL (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]

sf32Adm : long, NoNotificationAdmission 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 connectionInitially 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, NoNotificationThis parameter describes the admission margin for DL code utilization in DL (non-handover, non-compressed

mode RLs only)

Sub: RNH

Ref. [2]

sf16Adm : long, NoNotificationAdmission limit for admission on number of SF=16 non-guaranteed bitrate(best-effort) connections in a cell inDL (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



LOGICAL VIEW REPORT

When a HO from the current WCDMA frequency is triggered by the connection quality monitoring indicatingthat 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, NoNotificationThreshold for event 2d for the used frequency when the measurement quantity is Ec/No (set by measQuantity2).

Unit: 1 dBResolution: 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, NoNotificationGuard 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



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, NoNotificationInitial delay for start of congestion actions when targeting only guaranteed traffic.


Unit: 1 ms

Resolution: 1

Sub: RNH

Ref. [2]

loadSharingGsmFraction : long, NoNotificationDefines 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, NoNotificationDefines 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, NoNotificationCorrection factor to be used in the calculation of initial power for SRB in hard interfrequency handover

situations.

Unit: 1 dBResolution: 1

Sub: RNH

Ref. [2]

hsdpaUsersAdm : long, NoNotificationAdmission 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



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-hstraffic 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, NoNotificationMinimum 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



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 : longRAT 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 servingcell 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]

sf16AdmUl : long, NoNotificationAdmission limit (traffic class = non-guaranteed/guaranteed-hs, admission class = handover or other) for number

of radio links with UL SF = 16.

Unit: 1 connectionResolution: 1


Sub: RNH

Ref. [2]

sf8AdmUl : long, NoNotificationAdmission limit (traffic class = non-guaranteed/guaranteed-hs, admission class = handover or other) for number

of radio links with UL SF = 8.

Unit: 1 connectionResolution: 1


Sub: RNH

Ref. [2]

sf8gAdmUl : long, NoNotificationAdmission limit for RLs with spreading factor (SF) = 8 in UL (guaranteed admission requests).

Unit: 1 connection

Resolution: 1

Sub: RNH

Ref. [2]



LOGICAL VIEW REPORT

agpsEnabled : BooleanVals, NoNotificationIndicates 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, NoNotificationThreshold 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 loadResolution: 1

Sub: RNH

Ref. [2]

aseLoadThresholdUlSpeech : AseLoadThresholdUlSpeech, NoNotificationContains all AseUl threshold values used for AMR rate selection.


Sub: RNH

Ref. [2]

pwrLoadThresholdDlSpeech : PwrLoadThresholdDlSpeech, NoNotificationContains 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, NoNotificationAdmission 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]



LOGICAL VIEW REPORT

rateSelectionPsInteractive : RateSelectionPsInteractive, NoNotificationConfiguration of preferred rate for PS Interactive RABs

Unit: N/A

Resolution: N/A

Sub: RNH

Ref. [2]



LOGICAL VIEW REPORT

accessClassesBarredCs : sequence <BooleanVals,16,nonUnique>, NoNotificationSpecifies which access classes are barred for CS.

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.


Sub: RNH

Ref. [2]

accessClassesBarredPs : sequence <BooleanVals,16,nonUnique>, NoNotificationSpecifies which access classes are barred for PS.

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]

hcsUsage : HcsUsage, NoNotificationSpecifies 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.


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 maximumrate 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, NoNotificationMaximum 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.



LOGICAL VIEW REPORT

Unit: 1 bit/sResolution: 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, NoNotificationPeriod 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, ..., MM * 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, NoNotificationDefines 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, NoNotificationDefines 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, NoNotificationAdmission 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 userChange takes effect: ImmediatelyDependencies: If the value of this parameter is greater than the value of eulServingCellUsersAdm, then this

parameter will have no effect.

Sub: RNH

Ref. [2]



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

LogFilterThis Managed Object represents configurable parameters of the RANOS log filters.

Several instances may exist.

Attributes:



Sub: EQH

Ref. [12]

filterParam : sequence <LogFilterParameters>, Mandatory, NoNotificationConfigurable 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.



LOGICAL VIEW REPORT

SupportApplication

SupportApplicationSystemCreated

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 ApplicationMIB.

Attributes:



Sub: EQH, CMS

Ref. [7]

UserPreferences

UserPreferencesThis 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, NoNotificationIdentifies 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]



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 torecord break point information in a plan.

BreakPointModels a breakpoint in the planned configuration.

Attributes:

reached : BooleanVals, Default = FALSE, NoNotificationIndicates 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, NoNotificationThe 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

PlannedAreaPropertiesPlanned 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.



LOGICAL VIEW REPORT

Attributes:

plannedConfigurationName : string, Mandatory, NoNotification, Restricted

Planned Configuration name.

Sub: PCA

activationScheme : ActivationScheme, Default = DEFAULT, NoNotificationIndicates the Activation scheme attached to the plan.

Initial value is DEFAULT.

DEFAULT= 0INTRA_MIB_ORDERING = 1

INTER_MIB_ORDERING = 2

Sub: PCA

partlyActivated : BooleanVals, Default = FALSE, NoNotificationIndicates 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, NoNotificationStart date and time for the activation. Format: YYYY-MM-DD HH:MM:SS

Sub: PCA

jobID : longlong, NoNotificationCIF AM job id

Sub: PCA

nodeActivationStateRecord : sequence<NodeActivationState>, NoNotification

A record containing planned node name and its activation status.

Sub: PCA



LOGICAL VIEW REPORT

abortAtPreCheckFailure : BooleanVals, Default = FALSE, NoNotificationIndicates 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

PlannedConfigurationAppPlanned Configuration Application.

Only one instance of the MO Type can exist per MIB.

Attributes:


ActivationInformation

Attributes:

activationInfoKey : stringActivation information item key.

activationInfoValue : string

Activation information item value.

ActivationSchemeActivation Scheme.

Attributes:

DEFAULT : long = 0

INTRA_MIB_ORDERING : long = 1

INTER_MIB_ORDERING : long = 2

ActivationStateActivation states that a planned configuration can be in.

Attributes:

NOT_STARTED : long = 0

IN_PROGRESS : long = 1

PARTLY_REALIZED : long = 2

FAILED : long = 3COMPLETE : long = 4

TERMINATING : long = 5

TERMINATED : long = 6

SCHEDULED : long = 7

TIMED_OUT : long = 8



LOGICAL VIEW REPORT

LastCommit

Attributes:

commitElement : string

Activation element (Plan or MIB) for which last commit time is recorded.

commitTime : longlongLast commit time (in ns) set and used by the activation algorithms.

NodeActivationState

Attributes:

mibRootFDN : string

FDN of MIB root.

activationState : NodesActivationState, Default = NOT_STARTEDCurrent activation state of MIB.

Initial value is NOT_STARTED.

NOT_STARTED = 0QUEUED = 1

IN_PROGRESS = 2

COMPLETE = 3,

FAILED = 4,

PARTLY_COMPLETED = 5,TERMINATED= 6,

NEVER_CONNECTED = 7,

TIMED_OUT= 8

FAILED_PRECHECK=9

NodesActivationStateActivation states that a Node can be in.

Attributes:

NOT_STARTED : long = 0

QUEUED : long = 1IN_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_MODELContains 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



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 networkmanagement 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 deployedin 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 isthe 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

AlarmIRPThis 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

AreasSystemCreated

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:



LOGICAL VIEW REPORT

AtmLink

AtmLinkThis 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..128Provides support for putting a label on the MO instance.

Sub: TNH

Ref. [6]

atmPortNE1Ref : string, Mandatory, NoNotification

Full Distinguished Name of NE1 MeContext MO.

Sub: TNH

Ref. [6]

atmPort1Ref : string, Mandatory, NoNotificationLocal 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. []



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

BulkCmIRPThis 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:

irpVersion : sequence <string>, Mandatory, NoNotificationOne or more Bulk CM IRP version entries.


Sub: RAH

Ref. [21]

ExternalGsmCell

ExternalGsmCellThis 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 RULEValue part of RDN is User-defined.

Recommendation to system user is to assign the same identity as the original cell has.



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]

userLabel : string, LengthRange = 0..128a 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, 100Minimum received GSM level in the GSM cell.



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 commonvalue.

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..999The MCC part of the PLMN identity used in Gsm radio network.

Sub: RNH, I/E, CMS

Ref. [22]

mnc : long, Mandatory, Restricted, Range = 0..999The 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 = DCS1800This 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

ExternalGsmPlmnThis MO models a neighbouring GSM PLMN. Note that the

plmnid(mcc,mnc,mnclength) of this MO is to be unique with respect to other



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

Value part of RDN is User-defined.

Recommendation to system user is to assign the same identity as the original system it

represents.



LOGICAL VIEW REPORT

Attributes:

userLabel : string, NoNotification


Sub: TNH

Ref.[]

ExternalUtranCell

ExternalUtranCellThis MO models a cell controlled by an external UTRAN system. Several instances ofthis 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".


Recommendation to system user is to assign the same identity as the original cell has.



LOGICAL VIEW REPORT

Attributes:

userLabel : string, LengthRange = 0..128

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¨



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, 65535Location 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



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 tocontrol 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 dBmStep 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, 100Used 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, 100Used 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 cel l. 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 = TRUEIndicates if A-GPS is enabled or not for a cell.

FALSE = 0

TRUE = 1

Unit: N/A

Resolution: N/A

Sub: RNH



LOGICAL VIEW REPORT

Ref. [2]

cellCapability : CellCapabilityIndicates 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

ExternalUtranPlmnThis 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

Value part of RDN is User-defined.

Recommendation to system user is to assign the same identity as the original system it

represents.



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.

FDN according to [9] and [20]

Sub: CMS

Ref. []

mcc : long, Mandatory, NoNotification, Restricted, Range = 0..999

Mobile Contry Code



Sub: RNH, I/E, CMS

Ref. [22]

mnc : long, Mandatory, NoNotification, Restricted, Range = 0..999Mobile Network Code



Sub: RNH, I/E, CMS

Ref. [22]

mncLength : long, Mandatory, NoNotification, Restricted, Range = 2..3The length of the attribute "mnc"


Sub: RNH, I/E, CMS

Ref. [2]

aliasPlmnIdentities : sequence <PlmnIdentity>Sequence of max 30 PlmnIdentites.

Sub: RNH, I/E, CMS

Ref. [ ]



LOGICAL VIEW REPORT

ExternalViewableNode


Attributes:

userLabel : string, NoNotification, LengthRange = 0..128Provides support for putting a label on the MO instance.

Sub: TNH, I/E, CMS

Ref. []

ExternalTransportNetworkThis MO is the root MO for transport information in a viewable (not managed) external

NE.

Attributes:


Sub: TNH, I/E, CMS

Ref. []

ExternalVplTpThis 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 inUTRAN to GSM and UTRAN to UTRAN handover. See ref. [23]. Only one instance of

the MO Type can exist per MIB.



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 andmimVersion 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]

MimInfoMimInfo 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

IRPAgentSystemCreated

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, RestrictedThe Distinguished Name of IRPAgent

Sub: EQH

Ref. [21]



LOGICAL VIEW REPORT

Link

Link Not implemented in Inc3

Attributes:


Sub: EQH

Ref. [7]

linkType : string, NoNotification

Sub: EQH

Ref. [7]

LocationArea

LocationAreaThis MO models manageable caracteristics of a Location Area in the subnetwork. A LAconsists 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 CSCN. 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.



LOGICAL VIEW REPORT

Attributes:


Location Area name

Sub: RNH, I/E, CMS

Ref.

lac : long, Mandatory, Restricted, Range = 1..65533, 65535Location Area code

Sub: RNH, I/E, CMS

Ref. []

t3212 : long, Default = 10, Range = 0..255Periodic 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

ManagementNodeSystemCreated

This MO models the WRAN CM management system. Only one instance of the MOType can exist per MIB.




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, NoNotificationAn 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, RestrictedSoftware version of the managerment node, e.g. R1A, R1B, etc.

Sub: EQH

Ref. [21]

manages : sequence <string>, NoNotificationList of ManagedElement objects


Note: For CORBA users, GenericNRIRPSystem::AttributeTypes::MOReferenceSet, see ref. [28]

Sub: EQH, RAH

Ref. [21]

MbmsServiceArea

MbmsServiceAreaThis 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.



LOGICAL VIEW REPORT

Attributes:

sac : long, Mandatory, Restricted, Range = 0..65535

Service area code

Sub: RNH

Ref. []

userLabel : string, LengthRange = 0..128Provides support for putting a label on the MO instance.

Sub: RNH

Ref.

NotificationIRP

NotificationIRPThis MO models the functionality of a notification IRP agent, see ref. [26]. Only one


Attributes:

irpVersion : sequence <string>, Mandatory, NoNotificationOne or more Notification IRP version entries.


Sub: FMS

Ref [21]

Plmn

PlmnThis 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 aExternalUtranPlmn & ExternalGsmPlmn MO's. Up to 10 instances of this MO Type can

exist per MIB.



LOGICAL VIEW REPORT

Attributes:



Sub: RNH, I/E, CMS

Ref. []

mcc : long, Mandatory, NoNotification, Restricted, Range = 0..999

Mobile Contry Code



Sub: RNH, I/E, CMS

Ref. [22]

mnc : long, Mandatory, NoNotification, Restricted, Range = 0..999

Mobile Network Code



Sub: RNH, I/E, CMS

Ref. [22]

mncLength : long, Mandatory, NoNotification, Restricted, Range = 2..3

The length of the attribute "mnc"


Sub: RNH, I/E, CMS

Ref. [22]

aliasPlmnIdentities : sequence <PlmnIdentity>Sequence of max 30 PlmnIdentites.

Sub: RNH, I/E, CMS

Ref. [ ]

PmIRP

PmIRPThis MO models the functionality of the Performance Management IRP agent. Only one




LOGICAL VIEW REPORT

Attributes:

irpVersion : sequence <string>, Mandatory, NoNotification

One or more PM IRP version entries.

Sub: PMS

Ref. []

RbsGroup

RbsGroupThis 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:

userLabel : string, NoNotification, LengthRange = 0..128Provides 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>, NoNotificationReferences 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

RoutingAreaThis 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, whichgroups 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 configurationand 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.



LOGICAL VIEW REPORT

Attributes:


Location Area name

Sub: RNH, I/E, CMS

Ref.

rac : long, Mandatory, Restricted, Range = 0..255Routing 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

SegmentSystemCreated, NotificationTypes = notifyObjectCreation, notifyObjectDeletion

This Managed Object type modells a Segment in WRAN CM. It specifies which RNS'sthat 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_FAIUREPersieved 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



LOGICAL VIEW REPORT

Persieved Sevirity: MAJOR

Specific Problem: SegmentPMS_SEGMENT_VOLUME_FULL

Additional Text:.........

Additional Info..........

PMS SEGMENT WRITE ACCESS ALARM

Segment Server failed to write data or create directory du to denied file permission.

Event Type: ET_ENVIRONMENTAL_ALARMProbable Cause: PC_DISK_PROBLEM

Persieved Sevirity: MAJOR

Specific Problem: SegmentPMS_SEGMENT_WRITE_ACCESS_ALARM

Additional Text:.........

Additional Info..........



LOGICAL VIEW REPORT

Attributes:



Sub: EQH

Ref. [7]

ipAddress : string, Mandatory, NoNotificationThe 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, NoNotificationPath 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 toindicate 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

ServiceAreaThis 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, whichgroups 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 CNinformation. 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 RULEThe RDN value of ServiceArea is set to <sac> by the system as default.



LOGICAL VIEW REPORT

Attributes:

userLabel : string, LengthRange = 0..128Location Area name

Sub: RNH

Ref.

sac : long, Mandatory, Restricted, Range = 0..65535

Service area code

Sub: RNH

Ref. []

Site

SiteThis 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 thesame Site MOC instance. Several instances of this MO Type can exist per MIB.



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 tonorth

latitude values whereas negative degree values (-0 o - -90 o ) correspond to south latitude values. The precision

is0.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, NoNotificationPositive 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, NoNotificationThe timeZone the site exists in.

Sub: EQH

Ref.[]

freeText : string, NoNotificationOperator's choice of information

Sub: EQH



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

SubNetworkSystemCreated, 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 thatare 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 instancehandles 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



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 theMIB, 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, NoNotificationType of network e.g. UTRAN

For RNS = NULL

Sub: EQH

Ref. [21]

rncRef : string, NoNotificationReference 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

TnApplicationSystemCreated

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]

VirtualPathThis MO models the concept of a link between two directly connected nodes, or betweentwo nodes that are separated by a node that is cross connecting virtual paths in the ATM

layer.



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, MandatoryTThe 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 = 0IMSI_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

PlmnIdentityA structure used to hold the identities of PLMN.

Sub: RNH

Ref: []



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

BasicManagedElementBasicManagedElement

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 3GPPstandard, 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 intoManagedElement 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 mirroredMIB 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 CMor, 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 MAJORSpecific Problem ManagedElementINCOMPATIBLE_MIM_VERSION_MISMATCH

Additional Text -

Additional Info -

COMPATIBLE MIM VERSION MISMATCH



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 CMor, 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

Event Type ET_EQUIPMENT_ALARM

Probable Cause PC_VERSION_MISMATCH[357]Perceived Severity WARNING

Specific Problem ManagedElementCOMPATIBLE_MIM_VERSION_MISMATCH

Additional Text -

Additional Info -

PMS SEGMENT NE CONNECT ALARMSegment Server failed to connect to Performance Management interface on NE.

Attribute ValueEvent Type ET_COMMUNICATIONS_ALARM

Probable Cause PC_COMMUNICATIONS_PROTOCOL_ERROR[305]Perceived Severity MAJOR

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

Event Type ET_COMMUNICATIONS_ALARM

Probable Cause PC_COMMUNICATIONS_PROTOCOL_ERROR[305]Perceived Severity MAJORSpecific 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 enteredin 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 ValueEvent Type ET_EQUIPMENT_ALARM

Probable Cause PC_VERSION_MISMATCH[357]

Perceived Severity MAJOR

Specific Problem ManagedElementSOFTWARE_VERSION_MISMATCHAdditional Text -

Additional Info -

UNSYNCHRONIZED NETWORK ELEMENT



LOGICAL VIEW REPORT

This alarm is rised when the synchronization of a NE mirrored MIB fails.

Attribute Value

Event Type ET_COMMUNICATIONS_ALARM

Probable Cause PC_UNAVAILABLE

Perceived Severity MAJORSpecific Problem ManagedElementUNSYNCHRONIZED_NETWORK_ELEMENT

Additional Text -

Additional Info -



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, RestrictedType 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, NoNotificationOperator 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



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.

Aal0TpVccTpValid for: RBS, RNC.

Attributes:

userLabel, NoNotification

processorId, NoNotification

reservedBy, NoNotification

vclTpId, Mandatory

alarmReport, NoNotification

continuityCheck, NoNotification

nomPmBlkSize, NoNotificationcounterMode

counterActivation[PersistInMirror: P5 onwards]

Aal1TpVccTpValid for: All nodes.



LOGICAL VIEW REPORT

Attributes:

userLabel


cdvt, NoNotification

continuityCheck

counterMode

ds0BundleId, NoNotification

nomPmBlockSize

vclTpId, Mandatory

partialFill, NoNotification

counterActivation

[PersistInMirror: P5 onwards]

Aal2ApValid for: All nodes.

Attributes:


timerErq, NoNotification

timerRel, NoNotification

sigLinkId, NoNotification

secondarySigLinkId, NoNotificationrpuId, NoNotification

reservedBy

aal2QoSCodePointProfileId

allocationMode, NoNotification


Aal2PathDistributionUnitValid for: All nodes.

Attributes:


rpuId, NoNotificationaal2PathVccTpList, NoNotification

Aal2PathVccTpValid for: All nodes.

Attributes:


vclTpId, Mandatory

administrativeState, NoNotification

reservedBy


counterMode


nomPmBlocksize, NoNotificationtimerCu, NoNotification

aal2PathId, NoNotification

aal2PathOwner, NoNotification

aal2QoSAvailableProfiles

aal2QoSProfileId, NoNotification

aal2CacWp

muxResourceId




LOGICAL VIEW REPORT

Aal2QoSCodePointProfileValid for: All nodes.

Attributes:

userLabel

qualityOfServiceCodePointA, NoNotification

qualityOfServiceCodePointB, NoNotification

qualityOfServiceCodePointC, NoNotification

qualityOfServiceCodePointD, NoNotification


Aal2QoSProfileValid for: All nodes.

Attributes:

userLabel

profileClassA, NoNotification

profileClassB, NoNotification

profileClassC, NoNotification

profileClassD, NoNotification


Aal2RoutingCaseValid for: All nodes.

Attributes:


numberDirection, NoNotification

routeList

routePriorityList

Aal2SpValid for: All nodes.

Attributes:


a2ea, NoNotification

Aal5TpVccTpValid for: All nodes.

Attributes:


processorId, NoNotification

vclTpId, Mandatory

fromUserMaxSduSize, NoNotification

toUserMaxSduSize, NoNotificationreservedBy, NoNotification



nomPmBlkSize, NoNotification

counterMode




LOGICAL VIEW REPORT

AtmConfServiceAsynchronous Transfer Mode (ATM) Configuration Service

Valid for: All nodes.


Attributes:


AtmCrossConnectionValid for: All nodes.

Attributes:


vclTpAId, NoNotification

vclTpBId, NoNotification

AtmPortValid for: All nodes.

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

AtmTrafficDescriptorValid for: All nodes.



LOGICAL VIEW REPORT

Attributes:


ingressAtmPcr, NoNotification

ingressAtmQos, NoNotification

egressAtmPcr, NoNotification

egressAtmQos, NoNotification


egressAtmMcr, NoNotification

ingressAtmMcr, NoNotification

serviceCategory, NoNotification

packetDiscard, NoNotification, Restricted


CbuValid for: RBS only.

Container MOC.

Attributes:


ConfigurationVersion

NotificationTypes = notifyObjectCreation, notifyObjectDeletionValid for: All nodes.

Attributes:

currentUpgradePackage, NoNotification

DhcpValid for: All nodes.


Attributes:


dhcpServerAddresses, NoNotification, ReadOnly

Ds0BundleValid for: All nodes.

Attributes:


listOfTimeSlots, Mandatory, NoNotification, Restricted

tdmMode, Mandatory, NoNotification, Restricted

E1PhysPathTermValid for: All nodes.



LOGICAL VIEW REPORT

Attributes:



lineNo, Mandatory, NoNotification, Restricted

loopback, NoNotification

crc4Mode, NoNotification

idlePattern, NoNotification

degDegM, NoNotification

degDegThr, NoNotification

rdiReporting, NoNotification

aisReporting, NoNotification

shutDownTimeout, NoNotification

E1TtpValid for: All nodes.

Attributes:





rdiReporting, NoNotificationcrc4Mode, NoNotification


E3PhysPathTermValid for: All nodes.

Attributes:






degDegM, NoNotificationdegDegThr, NoNotification



EquipmentValid for: All nodes.

Attributes:


EthernetLinkValid for: All nodes.



LOGICAL VIEW REPORT

Attributes:

userLabel

ipAddress

subnetMask

broadcastAddress, Mandatory

macAddress

mtuSize, NoNotification

metric

interfaceName, NoNotification

EthernetSwitchValid for: All nodes.


Attributes:

enableVlan, NoNotification

pbitQueueMap, NoNotification

untaggedIngressPriority, NoNotification

untaggedIngressVid, NoNotification

vlanMembership, NoNotification


macAddress, NoNotification, ReadOnly[PersistInMirror: P7 onwards]

EthernetSwitchFabricValid for: RNC.[PersistInMirror: P7 onwards]

Attributes:


EthernetSwitchModuleValid for: RNC.


Attributes:

backPlanePortState, NoNotification, ReadOnly

macAddress, NoNotification, ReadOnly


EthernetSwitchModulePortValid for: RNC.


Attributes:administrativeState, NoNotification

egressUntagVlanRef, NoNotification

externalPort, NoNotification

operatingMode, NoNotification


portNo, Mandatory, NoNotification, Restricted


untaggedIngressVlanRef, NoNotification


vlanRef, NoNotification



LOGICAL VIEW REPORT

EthernetSwitchPortValid for: All nodes.[PersistInMirror: P6 onwards]

Attributes:administrativeState, NoNotification

ingressPeakBitrate, NoNotification

operatingMode, Mandatory, NoNotification


portNo, Mandatory, NoNotification, Restricted

systemPort, NoNotification


untaggedIngressVid, NoNotification

vlanMembership, NoNotification

actualSpeedDuplex, NoNotification, ReadOnly

sfpInformation, NoNotification, ReadOnly

sfpPort, NoNotification, ReadOnly


EtMfgValid for: All nodes.[PersistInMirror: P5, P6, P6FP]

Attributes:


Etm1Valid for: All nodes.

Attributes:

boardConfig, NoNotification

ExchangeTerminalValid for: All nodes.

Container MOC.


Attributes:

description, NoNotification


ExchangeTerminalIpValid for: All nodes.


Attributes:


FastEthernetValid for: All nodes.



LOGICAL VIEW REPORT

Attributes:



defaultRouter, Mandatory, NoNotification

mtu, NoNotification

networkPrefixLength, Mandatory, NoNotification, Restricted

macAddress, ReadOnly

subnet, ReadOnly

GeneralProcessorUnitValid for: All nodes.

Attributes:


GigaBitEthernetValid for: All nodes.


Attributes:

userLabel


dscpPbitMap, Restricted

autoNegotiation, NoNotification

frameFormat

primaryLink

protectiveMode, NoNotification


statePropagationDelay, NoNotification

switchBackTimer, NoNotification

macAddressLink1, ReadOnly

macAddressLink2, ReadOnly

linkType, NoNotification, Restricted


HgTtpValid for: All nodes.

Container MOC. Needed for Ds0Bundle.

Attributes:

ImaGroupValid for: All nodes.

Attributes:


physicalPortList, Mandatory, NoNotification

requiredNumberOfLinks

activeLinks, NoNotification, ReadOnly

[PersistInMirror: P5, P6]




LOGICAL VIEW REPORT

ImaLinkValid for: All nodes.

Attributes:

userLabel

uses, Mandatory, NoNotification, Restricted

InternalEthernetPortValid for: All nodes.[PersistInMirror: P6 onwards]

Attributes:

dscpPbitMap, NoNotification, Restricted

ethernetSwitchRef, Mandatory, NoNotification, Restricted

frameFormat, NoNotification

macAddress, NoNotification, ReadOnly


IpValid for: All nodes.

Attributes:

userLabel

isRecursiveSearch, NoNotification

isSubDomainName, NoNotification

dnsServer[PersistInMirror: P5, P6, P6FP]

retransInterval

noOfRetrans

isDefDomainName

defDomainName

useHostFile

dscp

icmpRedirect

udpChecksumState

connectionAttemptTimer

maxRetransmissionAttempts

workingMode, Mandatory

dnsServerAddresses, NoNotification

IpAccessAutoConfigValid for: RNC.


Attributes:

userLabel

nrOfUnusedAdresses

totalNrOfAddresses

minIpAddress, Mandatory, NoNotification, Restricted

maxIpAddress, Mandatory, NoNotification, Restricted

IpAccessHostEtValid for: All nodes.




LOGICAL VIEW REPORT

Attributes:


ipAddress, Mandatory

ipDefaultTtl, NoNotification

ipInterfaceMoRef, Mandatory, NoNotification, Restricted

ntpServerMode


ntpDscp, NoNotification[PersistInMirror: P7 onwards]

IpAccessHostGpbValid for: RNC, RBS.[PersistInMirror: P5 onwards]

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

IpAccessHostSpbValid 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


IpAccessSctpValid for: RNC, RBS.

[PersistInMirror: P7 onwards]Attributes:

ipAccessHostEtRef1, Mandatory, NoNotification

ipAccessHostEtRef2, Mandatory, NoNotification




LOGICAL VIEW REPORT

IpAtmLinkValid for: All nodes.

Attributes:

userLabel

interfaceName, NoNotification

ipAddress

subnetMask

metric

monitor

monitorInterval

monitorRetries

mtuSize


aal5TpVccTpId, Mandatory, NoNotification, Restricted[PersistInMirror: P5 onwards]

IpInterfaceValid for: All nodes.


Attributes:

userLabel

vid

vLan

rps

mtu

networkPrefixLength, Mandatory, Restricted

defaultRouter0, Mandatory

defaultRouter1

defaultRouter2

defaultRouterPingInterval

maxWaitForPingReply

maxNoOfFailedPings

noOfPingsBeforeOk

switchBackTimer

ownIpAddressActive, Restricted

ownIpAddressPassive, Restricted

subnettrafficType, NoNotification

vlanRef, NoNotification


IpOamRequired 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



LOGICAL VIEW REPORT

IpRoutingTableValid for: All nodes.

Attributes:

userLabel

indexOfDeletableStaticRoutes, NoNotification


staticRoutes, NoNotification, ReadOnly

IpSyncRefValid for: RNC, RBS.


Attributes:


cachedIpAddress, NoNotification, ReadOnly

ntpServerIpAddress


IpSystemRequired for: Ip.


Attributes:

UserLabel

J1PhysPathTermValid for: All nodes.

Attributes:




physicalLineType, NoNotification

degThreshold, NoNotification






LicensingValid for: RNC.Container MOC.


Attributes:



LOGICAL VIEW REPORT

Derived from BasicManagedElement

Attributes:




Sub: EQH, RAH

Ref. [21]

managedElementType : string, Local, NoNotification, Restricted

Type of ManagedElement i.e RNC, NodeB see ref. [21] and RANAG (Ericsson specific).


Sub: EQH, RAH

Ref. [21]

vendorName : string, Default = Ericsson, Local, NoNotification, Restricted

Name of the ManagedElement vendor i.e. Ericsson.

Sub: -

Ref. [21]




Sub: CMS

Ref. []


Sub: EQH, RAH

Ref. [21]



MO’s.


Sub: CMS

Ref. [21]







LOGICAL VIEW REPORT

Sub: EQH, RAH

Ref. [21]

sourceType : string, Default = Cello, Local, NoNotification, RestrictedInformation about on what platform the network element is running on, i.e. Cello, AXE

Sub: EQH

Ref. []



Sub: -

Ref. []



Sub: EQH

Ref. []

ManagedElementDataValid for: All nodes.

Attributes:

documentServerAddress

logonServerAddressdhcpServerAddresses

[PersistInMirror: P5, P6, P6FP]

ntpServerAddressPrimary

ntpServerAddressSecondary

performanceDataVolume

[PersistInMirror: P5]

MediumAccessUnitValid for: All nodes.

Attributes:


connectorLabel, NoNotification, Restricted

MspgValid for: All nodes.



LOGICAL VIEW REPORT

Mtp3bSlItuValid for: RNC.

Attributes:

userLabel

autoStartLink, NoNotification

linkState, NoNotification


proceduralState, NoNotification

signLinkCode, NoNotification

tpId, NoNotification

usageState, NoNotification

prioBeforeSio

Mtp3bSlsValid for: RNC.

Attributes:userLabel

mtp3bSrsId, NoNotification

periodicLinkTestFlag, NoNotification



cLinkAnsi, NoNotification[PersistInMirror: P5 onwards]

Mtp3bSlTtcValid for: RNC.

Attributes:

userLabel

autoStartLink, NoNotification

linkState, NoNotification


proceduralState, NoNotification

signLinkCode, NoNotification

tpId, NoNotification


prioBeforeSio

Mtp3bSpAnsiValid for: RNC.



LOGICAL VIEW REPORT

Attributes:

userLabel

m3uaNoOfAttempsOfDauds

maxSizeChangeBuf

maxSizeReroutBuf

networkInd, NoNotification

nodeBehaviour, NoNotification

noOfAttempsOfAssociationEstablishment

noOfCongestLevelForNI

resendTfcInterval

spTimer

routeSetCongestTestFlag

rpuId, NoNotification

sendSltmBefLink


signallingPointCode, NoNotification

sioSpare

spPriority

statusIndInterval

testPatternSltm


transFrHandler

modifiedSlsRotation, NoNotification

Mtp3bSpChinaValid for: RNC.

Attributes:

userLabel


maxSizeChangeBuf

maxSizeReroutBuf





resendTfcInterval

spTimer

routeSetCongestTestFlagrpuId, NoNotification

sendSltmBefLink[PersistInMirror: P5, P6, P6FP]


sioSpare

spPriority

statusIndInterval

testPatternSltm

transFrHandler

version


restartType, NoNotification

Mtp3bSpItu

Valid for: RNC.



LOGICAL VIEW REPORT

Attributes:

userLabel


maxSizeChangeBuf

maxSizeReroutBuf





resendTfcInterval


spTimer


sendSltmBefLink



sioSpare

spPriority

statusIndInterval

testPatternSltm

transFrHandler

version


Mtp3bSpTtcValid for: RNC.

Attributes:

userLabel

maxSizeChangeBuf

maxSizeReroutBuf



resendTfcInterval




spPriorityspTimer, NoNotification

statusIndInterval

testPatternSltm


m3uaNoOfAttempsOfDauds, NoNotification[PersistInMirror: P5 onwards]

noOfAttempsOfAssociationEstablishment, NoNotification


spTimerM3ua, NoNotification[PersistInMirror: P5 onwards]

Mtp3bSrValid for: RNC.

Attributes:

userLabel

linkSetM3uId, NoNotification

priority




LOGICAL VIEW REPORT

Mtp3bSrsValid for: RNC.

Attributes:

userLabel

autoReroute, NoNotification

congestedLevel, NoNotification

destPointCode, NoNotification


NniSaalProfileValid for: RNC.

Attributes:

userLabel

profileData, NoNotification


NniSaalTp

Valid for: RNC.

Attributes:

userLabel

aal5TpVccTpId, NoNotification

maxSduSize, NoNotification

nniSaalProfileId


Os155PhysPathTermValid for: All nodes.

Attributes:

userLabel, NoNotificationlineNo, NoNotification

Os155SpiTtpValid for: All nodes.

Attributes:




standardMode, Mandatory, NoNotification, Restricted


muxMode, Mandatory, NoNotification, Restricted

msDegThreshold, NoNotification

msDegM, NoNotification

msRdiReporting, NoNotificationmsAisReporting, NoNotification

loopBack, NoNotification

OspfValid for: RNC, RXI.



LOGICAL VIEW REPORT

Attributes:

userLabel


ospfRouterId, NoNotification

ospfASBdrRtrStatus, NoNotification

ospfAreaBdrRtrStatus, NoNotification


recoverTopoDb

topoDbStoreInterv

ipMo, Mandatory, NoNotification, Restricted

OspfAreaValid for: RNC, RXI.

Attributes:

userLabel

range0, NoNotification



importExternalLsa, NoNotification

stubArea, NoNotification

stubAreaMetricType, NoNotification

sendAreaSummary, NoNotification

stubAreaMetric, NoNotification


areaId, Mandatory, NoNotification, Restricted

areaLsaChecksum, NoNotification, ReadOnly

OspfInterfaceValid for: RNC, RXI.

Attributes:

userLabel

helloInterval

interfacePriority

interfaceTransitDelay

lsaTransmissionInterval

ospfAreaRelated

relatedLink, NoNotification

routerDeadInterval

PlugInUnitValid for: All nodes.

Attributes:


allowedSeqRestarts, NoNotification


piuGroupNumber, NoNotification

piuType, Mandatory, NoNotification

productType, NoNotification

PmServicePerformance Management Service





LOGICAL VIEW REPORT

Attributes:

performanceDataVolume

minorAlarmCeasingDelta

warningAlarmLimitPercent

warningAlarmCeasingDelta

ReliableProgramUniterValid for: All nodes.

Attributes:

admActiveSlot, NoNotification

admPassiveSlot, NoNotification

reliableProgramLabel, NoNotification


normalisation, NoNotification

replication, NoNotification, Restricted

switchOver, NoNotification

SccLayerValid for: RNC - Cello 3.

Attributes:



sccpSpId, NoNotification

mtp3bSpId, NoNotification

SccpAccountingCriteriaValid for: RNC.

Attributes:

userLabelusageType, NoNotification

ssN, NoNotification

countType, NoNotification

globalTitleId, NoNotification

pointerId, NoNotification

SccpApValid for: RNC - Cello 3.

Attributes:


ssN, NoNotification

maxConn, NoNotification

mp3bApId, NoNotificationaddressManipulation, NoNotification


SccpApLocalValid for: RNC.



LOGICAL VIEW REPORT

Attributes:

userLabel

ssN, NoNotification

maxConn, NoNotification

useS1, NoNotification


SccpApRemoteValid for: RNC.

Attributes:

userLabel

ssN, NoNotification

mtp3bApId, NoNotification


SccpEntitySetValid for: RNC.

Attributes:userLabel

routeIds, NoNotification

newGlobalTitle, NoNotification

newSubSystemNumber, NoNotification

sharingMode, NoNotification


SccpGlobalTitleValid for: RNC.

Attributes:

userLabel

addressInformation, NoNotification

encodingScheme, NoNotificationgtIndicator, NoNotification

natureOfAddress, NoNotification

numberingPlan, NoNotification

sccpEntitySetId

translationType, NoNotification


SccpPolicingValid for: RNC.

Attributes:

userLabel

originatingMtp3bSpc, NoNotification

destinationMtp3bSpc, NoNotificationoriginatingSccpSpId, NoNotification

originatingSccpSsn, NoNotification

destinationSccpSpId, NoNotification

destinationSccpSsn, NoNotification

policingGlobalTitle, NoNotification



LOGICAL VIEW REPORT

SccpScrcValid for: RNC.

Attributes:

userLabel

SccpSpValid 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


SctpValid for: RNC, RBS.



LOGICAL VIEW REPORT

Attributes:


aisPReporting, NoNotification

rdiPReporting, NoNotification

timConsequentAction, NoNotification

expectedPathTrace, NoNotification

transmittedPathTrace, NoNotification

SubrackValid for: All nodes.

Attributes:

subrackPosition, NoNotification

cabinetPosition, NoNotification

SwitchPortStpValid for: All nodes.[PersistInMirror: P6 onwards]

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


SwitchStpValid for: All nodes.[PersistInMirror: P6 onwards]

Attributes:


bridgeForwardDelay, NoNotification

bridgeHelloTime, NoNotification

bridgeId, NoNotification, ReadOnly

bridgeMaxAge, NoNotification

bridgePriority, NoNotification

mode, NoNotificationrootBridgeId, NoNotification, ReadOnly

rootPortNumber, NoNotification, ReadOnly




LOGICAL VIEW REPORT

SwManagementValid for: All nodes.

Attributes:


SynchronizationValid for: All nodes.


Attributes:

degradationIsFault

syncRefActivity, NoNotification, ReadOnly

syncReference, NoNotification, ReadOnly

syncRefStatus, ReadOnly

systemClockA, NoNotification, ReadOnly[PersistInMirror: P5, P6, P6FP]

systemClockB, NoNotification, ReadOnly[PersistInMirror: P5, P6, P6FP]


syncRefPriority, NoNotification, ReadOnly

SystemFunctionsValid for: All nodes.


Attributes:

T1PhysPathTermValid for: All nodes.

Attributes:



lineNo, Mandatory, NoNotification, Restrictedloopback, NoNotification





transmissionMode, NoNotification



T1TtpValid for: All nodes.

Attributes:


aisReporting, NoNotificationrdiReporting, NoNotification




T3PhysPathTermValid for: All nodes.



LOGICAL VIEW REPORT

Attributes:








TimingUnitValid for: All nodes.


Attributes:


TransportNetworkValid for: All nodes.

Attributes:


TuSyncRefValid for: All nodes.


Attributes:



UniSaalProfileValid for: All nodes.

Attributes:



profileData, NoNotification

UniSaalTpValid for: All nodes.

Attributes:


uniSaalProfileId, Mandatory

aal5TpVccTpId, NoNotification


maxSduSize

UpgradePackageValid for: All nodes.

Attributes:

administrativeData, NoNotification

actionResult, NoNotification



LOGICAL VIEW REPORT

Vc12TtpValid for: All nodes.

Attributes:


transmittedPathTrace, NoNotification

expectedPathTrace, NoNotification


vcDegThreshold, NoNotificationvcDegM, NoNotification

tuAisReporting, NoNotification

vcRdiReporting, NoNotification



Vc4TtpValid for: All nodes.

Attributes:


pathTraceFormat, NoNotification

transmittedPathTrace, NoNotificationexpectedPathTrace, NoNotification


vcDegThreshold, NoNotification

vcDegM, NoNotification

auAisReporting, NoNotification

vcRdiReporting, NoNotification

VclTpValid for: All nodes.

Attributes:


externalVci, NoNotification

atmTrafficDescriptorId, MandatoryreservedBy, NoNotification

counterActivation, NoNotification[PersistInMirror: P6 onwards]

VlanValid for: RNC.


Attributes:


vid, Mandatory, NoNotification

vlanType, NoNotification, Restricted

VpcTpValid for: All nodes.



LOGICAL VIEW REPORT

Attributes:




counterMode

nomPmBlkSize, NoNotification

VplTpValid for: All nodes.

Attributes:


atmTrafficDescriptor

externalVpi, NoNotification

availabilityStatus

Vt15TtpValid for: All nodes.

Attributes:

administrativeState, NoNotificationuserLabel, NoNotification

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.

JvmRequired 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



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. Wherethe 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 andthe 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 aMirrored MIB is created and are kept up-to-date in the event that the actual NE MIM versionchanges 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 branchy - 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 releasee.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.

ENodeBFunctionNotificationTypes = notifyObjectCreation, notifyObjectDeletion

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.



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:

AntennaFeederCableThis 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

AntennaUnitThis MOC models an antenna unit.





LOGICAL VIEW REPORT

Attributes:

AntennaUnitGroupThis MOC is a container of references to the antenna and antenna near products(RET/TMA) serving a Sector.



Attributes:

EquipmentContainer MOC

Attributes:

EUtranCellFDDThis 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

RbsConfigurationThis 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.





LOGICAL VIEW REPORT

Attributes:

rbsLogicalName, ReadOnly

configFaultReason

progressLevel, ReadOnly

rbsConfigLevel

SectorFunctionThis MOC contains parameters for configuration of antenna and antenna near products.



Attributes:


fqBand, NoNotification, ReadOnly


TermPointToMmeModels 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. AllCPP 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.

ManagedElementNotificationTypes = notifyObjectCreation, notifyObjectDeletion

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 theinherited attribute productName when the element is a RBS.



LOGICAL VIEW REPORT

NOTE3: The set of possible values for MeContext.rbsType are also applicable for

managedElementType.

Alarms are defined in BasicManagedElement MO

Attributes:



LOGICAL VIEW REPORT


Attributes:




Sub: EQH, RAH

Ref. [21]

managedElementType : string, Local, NoNotification, Restricted

Type of ManagedElement i.e RNC, NodeB see ref. [21] and RANAG (Ericsson specific).


Sub: EQH, RAH

Ref. [21]

vendorName : string, Default = Ericsson, Local, NoNotification, Restricted

Name of the ManagedElement vendor i.e. Ericsson.

Sub: -

Ref. [21]




Sub: CMS

Ref. []


Sub: EQH, RAH

Ref. [21]



MO’s.


Sub: CMS

Ref. [21]







LOGICAL VIEW REPORT

Sub: EQH, RAH

Ref. [21]

sourceType : string, Default = Cello, Local, NoNotification, RestrictedInformation about on what platform the network element is running on, i.e. Cello, AXE

Sub: EQH

Ref. []



Sub: -

Ref. []



Sub: EQH

Ref. []

ERbs Mirror Model Main View

The ManagedElement is a local root MO and it is defined in the NE MIM.

MeContext

MeContextNotificationTypes = notifyObjectCreation, notifyObjectDeletion

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.



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 thesame 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, NoNotificationSet by ADD RBS Wizard.

A reference to an MO describing FTP-server to use for upgrade and installat ion.

Used only in RBS. For RNC and RANAG= NULL.

Sub: RAH

Ref. [7]

rbsGroupRef : string, NoNotificationReference 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, NoNotificationFDN 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, ReadOnlyRepresents 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]



LOGICAL VIEW REPORT

Derived from BasicMeContext

Attributes:

dnPrefix : string, NoNotification, Restricted

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, MandatoryThe 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



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 = 2DISCONNECTED = 3

Sub: CMS

Ref. [7]

mirrorMIBsynchStatus : SupportedMirrorMibSynchStatus, Default = UNSYNCHRONIZED, RestrictedIndicates 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 = 2SYNCHRONIZED = 3

UNSYNCHRONIZED = 4

Sub: CMS

Ref. [7]

mirrorMIBupdateStatus : SupportedMirrorMibUpdateStatus, Default = IDLE, NoNotificationIndicates 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



LOGICAL VIEW REPORT

NODEB = 2RANAG = 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, MandatoryIndicates 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 wasreceived 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

received from the node. Always reset after node synchronisation.The initial value set at create is -1.

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



LOGICAL VIEW REPORT

lostSynchronisation : string, ReadOnlyThe 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) andadditional 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 betweenMeContext instances of type RANAG, RNC and RBS (roles: +ranag, +rnc).


This MO models a RANAG. 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.


Example: MeContext=GaredeLyon



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, NoNotification, ReadOnly

Represents the percentage progress of the node being synchronised. Has 0% when the node is not connected orunsynchronised and 100% when the node is fully synchronised. Has values in between when then node is

synchronising.


Sub: CMS

Ref. [2]


Attributes:

dnPrefix : string, NoNotification, RestrictedDN 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]

userLabel : string, Mandatory, NoNotification, Restricted, LengthRange = 0..128Provides support for putting a label on the MO instance. It is used by WRAN CM application to write the



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, NoNotificationThe segment to which the NE belongs.


Sub: EQH

Ref. [7]

mimSwitchPolicy : SupportedMimSwitchPolicy, MandatoryDefines how version upgrade for a network element and the mirrored MIB shall be handled.

RANOS_FOLLOWS = 1



LOGICAL VIEW REPORT

NO_SWITCH = 2 NE_FOLLOWS = 3

UPGRADE_ATTEMPTED = 4

Sub: EQH

Ref. []


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, RestrictedIndication whether or not the NE MIM is compatible with the NE mirrored MIM version.


Sub: CMS

Ref. [7]


Status of the instance."NeverConnected" is set at instance creation.

"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]

mirrorMIBsynchStatus : SupportedMirrorMibSynchStatus, Default = UNSYNCHRONIZED, RestrictedIndicates whether or not the Mirrored MIB of this RNC is currently being synchronized with the MIB in the

RNC.


TOPOLOGY = 1ATTRIBUTE = 2

SYNCHRONIZED = 3

UNSYNCHRONIZED = 4

Sub: CMS

Ref. [7]




UPDATING = 1

IDLE = 2

Sub: CMS



LOGICAL VIEW REPORT

Ref. [2]

generationCounter : long, Default = -1, NoNotificationKeeps track of notifications received from the RNC.


Sub: CMS

Ref. [2]

neMIMName : string, NoNotification, RestrictedThe NE MIM name represented by this MeContext.


Sub: CMS

Ref. [7]

neType : SupportedNeType, Mandatory, NoNotificationThe NE type this MeContext represents.

RNC = 1

NODEB = 2RANAG = 3

ENODEB = 4

Ref. [7]




Sub: EQH

Ref. [7]

restartWarning : boolean, Default = falseIndicates 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, MandatoryIndicates whether security is activated on this NE or not.

Allowed string values are:OFF

ON

Sub:



LOGICAL VIEW REPORT

Ref. []

bcrLastChange : longlong, Default = -1, NoNotification, ReadOnlyOSS time in ms last BCR related notification was

received from the node. Always reset after node synchronisation.


Sub: CMS, BCR


OSS time in ms last BCT related notification wasreceived from the node. Always reset after node synchronisation.


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



Sub:

Ref. []



Sub:

Ref. []

pendingRestart : boolean, Default = false

Indicates whether or not a node restart is pending.

Ranag Cello MOC's containing WRAN CM local attributes

This package contains the Cello MOC that contains WRAN CM specific local attributes. AllCello 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:



LOGICAL VIEW REPORT

Aal2PathVccTp

Attributes:

Aal5TpVccTp

Attributes:

AtmCrossConnection

Attributes:

AtmPortA 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

The RDN value is set by the system to:

<Subrack>-<Slot>-<Line No>*[-SubLineNo]**




in case of channelization (e.g. a 155 Mbits/s physical interface configured to provide 63



Attributes:



NOTE: Functions that are generall for all NE, shall be modelled in





LOGICAL VIEW REPORT

Attributes:


Attributes:


DN prefix information.

Specified only if the instance of the ManagedElement MO is a local root instance of the MIB, otherwise it is setto NULL, see ref. [9]

Sub: EQH, RAH

Ref. [21]



Sub: EQH, RAH

Ref. [21]


Sub: -

Ref. [21]

locationName : string, Local, NoNotification, Restricted, ApplicationTag = siteThe physical location of this entity (e.g. an address)


Sub: CMS

Ref. []


Sub: EQH, RAH

Ref. [21]



MO’s.Concatenation of productNumber and productRevision in AdminProductData MO.

Sub: CMS

Ref. [21]






LOGICAL VIEW REPORT


Sub: EQH, RAH

Ref. [21]



Sub: EQH

Ref. []



Sub: -

Ref. []

siteRef : string, LocalFDN of the Site MO instance this ManagedElement belongs to

Sub: EQH

Ref. []

TransportNetwork

Attributes:

VclTp

Attributes:

VpcTp

Attributes:

VplTp

Attributes:

References to MOs in the RANAG Equipment ViewWhen creating UNI-SAAL and AAL0 connections by WRAN CM, the processor/timing unitidentities 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]):



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

NodeBFunctionNotificationTypes = notifyObjectCreation, notifyObjectDeletion

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].



LOGICAL VIEW REPORT

analogUlAlignIsActive, NoNotification, ReadOnly[PersistInMirror: P6 onwards]

eulNonServHwRate, NoNotification


eulSchedulingWeight, NoNotification


mbmsIubEfficiencyOn, NoNotification

[PersistInMirror: P6, P6FP]

nbapDscp, NoNotification[PersistInMirror: P6 onwards]

eulLowRate, NoNotification[PersistInMirror: P6 onwards]

featureStateStandardizedRet, NoNotification


featureStateStandardizedTma, NoNotification


dlLicFractBbPool2, NoNotification


ulLicFractBbPool2, NoNotification[PersistInMirror: P5 onwards]

sharedEquipmentController, NoNotification


featureStateDualStackIub, NoNotification

[PersistInMirror: P6FP onwards]

featureStateEul2msTti, NoNotification


featureState64Qam, NoNotification


featureStateDlPowerControlEul, NoNotification[PersistInMirror: P7 onwards]

featureStateMbmsIubEfficiency, NoNotification[PersistInMirror: P7 onwards]

featureState16Qam, NoNotification


featureStateHsdpaFlexibleScheduler, NoNotification[PersistInMirror: P7 onwards]

featureStateGrake, NoNotification


eulMaxAllowedSchRate, NoNotification[PersistInMirror: P7 onwards]



LOGICAL VIEW REPORT

MeContext


This MO models a RBS. 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.



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, NoNotificationSet by ADD RBS Wizard.

A reference to an MO describing FTP-server to use for upgrade and installat ion.

Sub: RAH

Ref. [7]

rbsGroupRef : string, NoNotificationReference 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]



LOGICAL VIEW REPORT

fdnOfRncIubLink : stringFDN of the associated IubLink MO on the RNC. Set to empty if the IubLink MO does not exist

Sub: RNH, I/E, CMS

Ref. []

synchronisationProgress : long, Default = 0, NoNotification, ReadOnly


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]



LOGICAL VIEW REPORT


Attributes:

dnPrefix : string, NoNotification, RestrictedDN Prefix information. Specified only if the instance of the MeContext MO is a local root instance of the MIB,


Sub: EQH, RAH

Ref. [21]

userLabel : string, Mandatory, NoNotification, Restricted, LengthRange = 0..128Provides support for putting a label on the MO instance. It is used by WRAN CM application to write the



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, NoNotificationThe segment to which the NE belongs.


Sub: EQH

Ref. [7]


RANOS_FOLLOWS = 1

NO_SWITCH = 2

NE_FOLLOWS = 3UPGRADE_ATTEMPTED = 4

Sub: EQH

Ref. []

neMIMversion : string, RestrictedThe branch and the version of the NE MIM used by this MeContext, <branch>.<version>.<release>, e.g. B.1.0


Sub: CMS

Ref. [7]





LOGICAL VIEW REPORT


Sub: CMS

Ref. [7]


Status of the instance."NeverConnected" is set at instance creation.

"Connected " is set to indicate that WRAN CM has 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 RBS is currently being synchronized with the MIB in the

RBS.

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 RBS is currently being updated with a planned configuration.

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]




Sub: CMS

Ref. [7]

neType : SupportedNeType, Mandatory, NoNotification

The NE type this MeContext represents.



LOGICAL VIEW REPORT

RNC = 1 NODEB = 2

RANAG = 3

ENODEB = 4

Ref. [7]




Sub: EQH

Ref. [7]

restartWarning : boolean, Default = falseIndicates 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:OFF

ON

Sub:

Ref. []




Sub: CMS, BCR


OSS time in ms last BCT related notification wasreceived from the node. Always reset after node synchronisation.The initial value set at create is -1.

Sub: CMS, BCT

telisLastChange : longlong, Default = -1, NoNotification, ReadOnly Number of Telis related notifications received from the node. Always reset after node synchronisation.




LOGICAL VIEW REPORT

Sub: CMS, Telis



Sub:

Ref. []

nodeStartTime : string, Default = "", NoNotification, ReadOnlyThe time (YYYY-MM-DD HH:MM:SS) when the node last started.

Sub:

Ref. []

pendingRestart : boolean, Default = falseIndicates whether or not a node restart is pending.

Rbs 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 Rbs Mirror Model are specializations of the MOC's defined in




Aal0TpVccTp

Attributes:

Aal2PathVccTp

Attributes:

Aal5TpVccTp

Attributes:

AtmCrossConnection

Attributes:




Naming RULE

The RDN value is set by the system to:




LOGICAL VIEW REPORT



**) subLineNo: only applicable in case an ATM port is connected with a logical interfacein case of channelization (e.g. a 155 Mbits/s physical interface configured to provide 63



Attributes:



NOTE1: Functions that are generall for all NE, shall be modelled inBasicManagedElement 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.

NOTE3: The set of possible values for MeContext.rbsType are also applicable for

managedElementType.




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]




Sub: CMS

Ref. [21]






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 CMmirrored MIBs. In addition, attributes "reservedBy" needed by WRAN CM are stored

persistently. Value change notifications keep these attributes updated.

AntennaBranchThis MOC models an antenna branch.



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


AntFeederCableThis MOC models an antenna feeder cable



Attributes:

ulAttenuation, Mandatory, NoNotification

dlAttenuation, Mandatory, NoNotification

electricalDlDelay, Mandatory, NoNotification

electricalUlDelay, Mandatory, NoNotification

antennaBranchRef, Mandatory, NoNotification, Restricted

connectedToObjectARef, Mandatory, NoNotification

objectAConnector, Mandatory, NoNotification


AuxPlugInUnitContainer MOC

Attributes:

CarrierThis MOC models a carrier.

It defines the attributes that are persistently stored in Ranos.




LOGICAL VIEW REPORT

Attributes:

frequencyPlane, Mandatory, NoNotification, Restricted

reservedBy, Mandatory, NoNotification

cqiAdjustmentOn

cqiErrors

cqiErrorsAbsent

hsPowerMargin

hsScchMaxCodePower

queueSelectAlgorithm, NoNotification

hsScchMinCodePower, NoNotification


qualityCheckPower, NoNotification[PersistInMirror: P5 onwards]

airRateTypeSelector, NoNotification[PersistInMirror: P5 onwards]

schCongPeriodGbr, NoNotification


schCongThreshGbr, NoNotification[PersistInMirror: P6 onwards]

schCongThreshNonGbr, NoNotification[PersistInMirror: P6 onwards]

schMaxDelay, NoNotification[PersistInMirror: P6 onwards]

schMinPowerNonGbrHsUsers, NoNotification[PersistInMirror: P6 onwards]

schNoCongPeriodGbr, NoNotification


schNoCongThreshGbr, NoNotification[PersistInMirror: P6 onwards]

schPowerDeltaCongGbr, NoNotification[PersistInMirror: P6 onwards]

schPrioForAbsResSharing, NoNotification


schWeight, NoNotification[PersistInMirror: P6 onwards]

aiDeviceRef, NoNotification, ReadOnly


dbccDeviceRef, NoNotification, ReadOnly


dpclDeviceRef, NoNotification, ReadOnly[PersistInMirror: P6, P6FP]

tpaDeviceRef, NoNotification, ReadOnly


trDeviceRef, NoNotification, ReadOnly




LOGICAL VIEW REPORT

dpclDevicesRef, NoNotification, ReadOnly[PersistInMirror: P7 onwards]


DbccDeviceAttributes:

DbccDeviceSetContainer MOC

Attributes:

DeviceGroupContainer MOC


Attributes:

DownlinkBaseBandPoolThis MO models a pool of downlink baseband channel devices.




Attributes:

maxNumADchReservation, NoNotification

EDchResourcesThis MO models the Enhanced uplink Dedicated Channel resources. The E-DCH

resources are set up through Iub.




Attributes:

EquipmentContainer MOC

Attributes:



LOGICAL VIEW REPORT

ExternalTmaThis MO describes an external Tma.



Attributes:dlAttenuation, Mandatory, NoNotification

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[PersistInMirror: P6FP onwards]

tmaDegradedSupported, NoNotification[PersistInMirror: P6FP onwards]

HsDschResourcesThis MO models the High-Speed Downlink Shared Channel resources. They are set upthrough Iub.




Attributes:

IubThis MOC models interface between this RBS and the associated RNC.





LOGICAL VIEW REPORT

Attributes:

userLabel, Mandatory, NoNotification

rbsId, Mandatory

controlPlaneTransportOption, Mandatory[PersistInMirror: P6 onwards]

userPlaneTransportOption, Mandatory, NoNotification[PersistInMirror: P6 onwards]

userPlaneIpResourceRef, NoNotification[PersistInMirror: P6 onwards]

IubDataStreamsSystemCreated

This MO models all lubDataStreams between RNC and RBS for Common as well as

Dedicated channels.



Attributes:

maxHsRate

maxEDchRate, NoNotification


hsDataFrameDelayThreshold, NoNotification


schHsFlowControlOnOff, NoNotification


McpaDeviceGroupContainer MOC


Attributes:

NbapCommonThis MOC models the manageable characteristics of a signalling link between the RBS

and a RNC.





LOGICAL VIEW REPORT

Attributes:

uniSaalTpRef1, NoNotification


l2EstablishReqRetryT, Mandatory, NoNotification

auditRetransmissionT, Mandatory, NoNotification

l2EstablishSupervisionT, Mandatory, NoNotification



NbapDedicatedThis MOC models the manageable characteristics of a signalling link between the RBS

and a RNC.



Attributes:






NodeSynchTpThis MOC models the Termination Point in RBS for the Node Synchronization protocol.



[PersistInMirror: P5, P6, P6FP]Attributes:

aal0TpRef1, NoNotification, Restricted




timDeviceRef, NoNotification, ReadOnly

PauDeviceGroupContainer MOC


Attributes:

PlugInUnitConatiner MOC

Attributes:



LOGICAL VIEW REPORT

PredefRbsScannerGpehThis MO models a Predefined RBS Scanner defined for GPEH, General Performance

Event Handling.


For more information see RBS MIM, ref [3].Attributes:

maxStorageSize, NoNotification[PersistInMirror: P5 onwards]

fileLocation, NoNotification, ReadOnly



RbsConfigurationThis 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, NoNotificationIndicates 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.

RbsLocalCellThis 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.





LOGICAL VIEW REPORT

Attributes:


localCellId, Mandatory

cellRange, Mandatory, NoNotification

carrierRef, Mandatory, NoNotification, Restricted

hsCodeResourceId, NoNotification


dynamicHsPdschCodeAdditionOn, NoNotification[PersistInMirror: P5, P6, P6FP]

maxNumHsPdschCodes, NoNotification[PersistInMirror: P5 onwards]

eulMaxNoSchEDch, NoNotification[PersistInMirror: P5 onwards]

eulMaxOwnUuLoad, NoNotification[PersistInMirror: P5 onwards]

eulMaxRotCoverage, NoNotification


eulMinMarginCoverage, NoNotification


eulOptimalNoiseFloorLock, NoNotification[PersistInMirror: P5 onwards]

eulSlidingWindowTime, NoNotification


eulThermalLevelPrior, NoNotification


maxEAgchPowerDl, NoNotification


maxUserEHichERgchPowerDl, NoNotification


maxNumHsdpaUsers, NoNotification[PersistInMirror: P5 onwards]

eulNoERgchGroups, NoNotification


hsdpaCapability, NoNotification, ReadOnly


maxDlPowerCapability, NoNotification, ReadOnly


minDlPowerCapability, NoNotification, ReadOnly


eDchCapability, NoNotification, ReadOnly


hsIncrementalRedundancyOn, NoNotification[PersistInMirror: P6, P6FP]

minSpreadingFactor, NoNotification, ReadOnly


rbsSynchronizationRef, NoNotification, ReadOnly[PersistInMirror: P5 onwards]

eDch2msTtiCapability, NoNotification, ReadOnly



LOGICAL VIEW REPORT


maxUserEHichPowerDlTti2, NoNotification[PersistInMirror: P6FP onwards]

maxEAgchPowerDlTti2, NoNotification


maxNumEulUsers, NoNotification[PersistInMirror: P6FP onwards]

featureStateEnhancedLayer2[PersistInMirror: P7 onwards]

eHichMinCodePower, NoNotification


qualityCheckPowerEHich, NoNotification


featureStateHsdpaDynamicCodeAllocation, NoNotification[PersistInMirror: P7 onwards]

featureStateHsdpaIncrementalRedundancy, NoNotification


RetDeviceThis MOC defines the attributes that are persistently stored in Ranos.


Attributes:

electricalAntennaTilt, Mandatory

maxTilt, Mandatory, NoNotification

minTilt, Mandatory, NoNotification


RetDeviceSetContainer MOC.

Attributes:

productNumber, NoNotification

revState, NoNotification

retType, NoNotification


RetuDeviceGroupContainer MOC.

Attributes:

RruDeviceGroupContainer MOC




LOGICAL VIEW REPORT

Attributes:

RuDeviceGroupContainer MOC[PersistInMirror: P7 onwards]

Attributes:

SectorThis MOC models a Sector.



Attributes:

utranCellRef : sequence<string>, Local, NoNotification

DN of the related RNC UtranCell MO.FDN according to [9] and [20]

For CORBA users, GenericNRIRPSystem::AttributeTypes::MOReference, see ref. [29]

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[PersistInMirror: P6 onwards]

retDeviceRef, NoNotification, ReadOnly


tmaDeviceRef, NoNotification, ReadOnly[PersistInMirror: P6 onwards]

band, NoNotification, ReadOnly


SectorAntenna

Attributes:

antennaType, Mandatory, NoNotification





LOGICAL VIEW REPORT

SlotContainer MOC

Attributes:

SubrackContainer MOC

Attributes:

TimDeviceThis MOC models the Device for the Timing Unit.



Attributes:

TimDeviceSetContainer MOC

Attributes:

TpaDeviceThis MO models a Transmit Power Amplifier device.




Attributes:

maxTotalOutputPower, NoNotification

TpaDeviceSetContainer MOC


Attributes:

TuDeviceGroupContainer MOC

Attributes:

TxDeviceGroupThis MOC models the Transmission Device Group.



LOGICAL VIEW REPORT



Required for: TNH

Attributes:numHsCodeResources, NoNotification


numEulResources, NoNotification[PersistInMirror: P5 onwards]


References to MOs in the RBS 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 WRANCM at connection creation time.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.



LOGICAL VIEW REPORT

RBS3104

These references are valid for RBS3104, RBS3203 and RBS3303.

1 :ManagedElement

1 :Equipment

1 :Subrack

4 : Slot

1 :PlugInUnit

For MPs

1 :

ManagedElement

1 :SwManagement

ans_aal2cpsrc_11 :ReliableProgramUniter

ans_aal2ap_11 :ReliableProgramUniter

Referred fromMO Aal2Ap

Referred from MO Aal2P athDistributio nUnit



LOGICAL VIEW REPORT

1 :ManagedElement

1 :Equipment

1 :

Subrack

2 : Slot

1 :PlugInUnit

For TUs

1 :ManagedElement

1 :Equipment

1 :Subrack

3 : Slot

1 :PlugInUnit

7 : Slot

1 :PlugInUnit

For ETB1 For ETB2

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 ModelThe 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 isincluded.

NodeBFunction=1

VplTp=1

VpcTp=1VclTp=32 or 33

Note: there can now be up to 3 instances of AtmPort in the base model.



LOGICAL VIEW REPORT

1 :

ManagedElement

1 :TransportNetwork

1_<slotid>_<lineno> :(AtmPort)

1 :NodeBFunction

1 : VplTp

1 :

VpcTp

32 :

VclTp 33 :

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.

CuSubrackRequired for: AuxPluginUnit.

Attributes:

McpaSubrackRequired for: AuxPluginUnit.

Attributes:

PowerSupplySubrackRequired for: AuxPluginUnit, RbsSlot.

Attributes:

PowerSupplySystemRequired to find: AuxPluginUnit.



LOGICAL VIEW REPORT

Attributes:

RbsSlotRequired for: AuxPluginUnit.

Attributes:

RbsSynchronizationRequired for: PluginUnit, TimDevice.

Attributes:

masterTu, NoNotification, ReadOnly


plugInUnitRef1, NoNotification, ReadOnly


plugInUnitRef2, NoNotification, ReadOnly[PersistInMirror: P5 onwards]

timDeviceRef1, NoNotification, ReadOnly


timDeviceRef2, NoNotification, ReadOnly[PersistInMirror: P5 onwards]

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 RNCMIM

Following Managed Object Types are WRAN CM local MOC’s:

MeContext

ExternalGsmCellApplicationTag = Contains only RNC cached attributes, NotificationTypes = notifyObjectCreation,

notifyObjectDeletion

This MOC models an external Gsm Cell.


For more information see RNC MIM, ref [2].



LOGICAL VIEW REPORT

Attributes:

userLabel, Mandatory

Attribute persistently stored in WRAN CM.

cellIdentity, Mandatory


ncc, MandatoryAttribute persistently stored in WRAN CM.

bcc, Mandatory


bcchFrequency, Mandatory


lac, Mandatory




mxTxPowerUl, MandatoryAttribute persistently stored in WRAN CM.

qRxLevMin, Mandatory


individualOffset, Mandatory


bandIndicator, MandatoryAttribute persistently stored in WRAN CM.

ExternalGsmNetworkNotificationTypes = notifyObjectCreation, notifyObjectDeletion

This MOC models the manageable characteristics of an external Gsm Network.

This MOC defines the attributes that are persistently stored in WRAN CM.




LOGICAL VIEW REPORT

Attributes:

mcc, Mandatory


mnc, Mandatory


mncLength, MandatoryAttribute persistently stored in WRAN CM.



aliasPlmnIdentities


reservedBy, NoNotification, ReadOnly

Attribute persistently stored in Ranos.

ExternalUtranCellApplicationTag = Contains only RNC cached attributes, NotificationTypes = notifyObjectCreation,

notifyObjectDeletion

This MOC models an external Rnc UtranCell.





LOGICAL VIEW REPORT

Attributes:



cId, Mandatory


lac, MandatoryAttribute persistently stored in WRAN CM.



primaryScramblingCode, Mandatory


primaryCpichPower, Mandatory


maxTxPowerUl, Mandatory


qQualMin, MandatoryAttribute persistently stored in WRAN CM.



uarfcnDl, Mandatory


uarfcnUl, MandatoryAttribute persistently stored in WRAN CM.



rac, MandatoryAttribute persistently stored in WRAN CM.

agpsEnabled


cellCapability


IubLinkNotificationTypes = notifyObjectCreation, notifyObjectDeletion

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.




LOGICAL VIEW REPORT

Attributes:

iubLinkNodeBFunction : string, Local, Mandatory

Reference to related NodeBFunction instanceFDN according to [9] and [20].


Sub: RNH, EQH

Ref. [22]



rbsId, Mandatory


This attribute is Mandatory in the RNC MOM. See ref. [2].

reservedBy, NoNotification, ReadOnlyAttribute persistently stored in Ranos.

rncModuleRef, NoNotification, ReadOnlyAttribute persistently stored in Ranos.

beMarginDlHw


beMarginUlHw


dlHwAdmAttribute persistently stored in WRAN CM.

ulHwAdm


preferredSubrackRef, Mandatory




LOGICAL VIEW REPORT

userPlaneTransportOption, Mandatory[PersistInMirror: P6 onwards]

controlPlaneTransportOption, Mandatory


operationalState, ReadOnly


administrativeState[PersistInMirror: P6 onwards]

sctpRef, ReadOnly[PersistInMirror: P6 onwards]

l2EstReqRetryTimeNbapC[PersistInMirror: P6 onwards]

l2EstReqRetryTimeNbapD


remoteCpIpAddress1[PersistInMirror: P6 onwards]

remoteCpIpAddress2[PersistInMirror: P6 onwards]

userPlaneIpResourceRef[PersistInMirror: P6 onwards]

atmUserPlaneTermSubrackRef[PersistInMirror: P7 onwards]

cachedRemoteCpIpAddress1, ReadOnly


cachedRemoteCpIpAddress2, ReadOnly[PersistInMirror: P7 onwards]

IurLinkNotificationTypes = notifyObjectCreation, notifyObjectDeletion

The MO IurLink models manageable characteristics of an external Rnc that must beknown to the Rnc.

This MOC defines the attributes that are persistently stored in WRAN CM.




LOGICAL VIEW REPORT

Attributes:

rncId, Mandatory




utranNetworkRef, Mandatory, NoNotification, RestrictedReference to the UTRAN network to which this Iur link belongs.


cellCapabilityControl, NoNotification


hspaPathlossThreshold, NoNotification


userPlaneTransportOption, Mandatory, NoNotification[PersistInMirror: P6 onwards]

srncPmReporting, NoNotification


userPlaneIpResourceRef, NoNotification[PersistInMirror: P6 onwards]

edchDataFrameDelayThreshold, NoNotification


iurArpGuaranteed, NoNotification[PersistInMirror: P6 onwards]

iurArpNonguaranteed, NoNotification[PersistInMirror: P6 onwards]

mcc, NoNotification


atmUserPlaneTermSubrackRef, NoNotification[PersistInMirror: P7 onwards]

maxMacdPduSizeExtended


RncFunctionNotificationTypes = notifyObjectCreation, notifyObjectDeletion

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.





LOGICAL VIEW REPORT

Attributes:

rncId, Mandatory


mcc, Mandatory


mnc, MandatoryAttribute persistently stored in WRAN CM.

mncLength, Mandatory




aliasPlmnIdentities


emergencyCallRedirect, Mandatory


loadSharingDirRetryEnabled, MandatoryAttribute persistently stored in WRAN CM.

loadSharingRrcEnabled, Mandatory


hsCellChangeAllowed


hsOnlyBestCellAttribute persistently stored in WRAN CM.

gpehDataLevel


gpehFileSizeAttribute persistently stored in WRAN CM.

uetrFileSizeAttribute persistently stored in WRAN CM.

ctrFileSizeAttribute persistently stored in WRAN CM.

counterAlarmThreshold[PersistInMirror: P5]

counterAlarmCeaseLimit


counterWarningAlarmCeaseLimit[PersistInMirror: P5]

networkResourceIdentifierLengthCsBitmask length of the NRI for CS/MSC. 0 (default) means no Iu Flex active

To be used for Iu Flex.




LOGICAL VIEW REPORT

networkResourceIdentifierLengthPsBitmask 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 validif 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, NoNotificationThe 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




LOGICAL VIEW REPORT

maxPowerOverloadHystTime, NoNotification[PersistInMirror: P6 onwards]

nbapDscp, NoNotification


cchDscpEgress, NoNotification[PersistInMirror: P6]

cchDscpIngress, NoNotification


mocnExternalNriMatching, NoNotification


maxAllowedGbrDlPsStream, NoNotification[PersistInMirror: P6 onwards]

pcapPositioningMode, NoNotification[PersistInMirror: P6FP onwards]

highPrioScanReserve, NoNotification[PersistInMirror: P5 onwards]

noOfCountersAllowed, NoNotification


nbapAuditInterval, NoNotification


iuSccpConRateMeasPeriod, NoNotification


iuSccpConRateThresh, NoNotification


intraNodeIpResourceRef, NoNotification[PersistInMirror: P7 onwards]

UtranCellNotificationTypes = notifyObjectCreation, notifyObjectDeletion

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.



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, NoNotificationDN of the related RBS Sector MO.

FDN according to [9] and [20]For CORBA users, GenericNRIRPSystem::AttributeTypes::MOReference, see ref. [29]

Sub: RNH, CMS

Ref. [29]



LOGICAL VIEW REPORT

administrativeState, MandatoryAttribute persistently stored in RANOS


Attribute persistently stored in WRAN CM

availabilityStatus, ReadOnlyAttribute persistently stored in WRAN CM


Attribute persistently stored in RANOS

localCellId, MandatoryAttribute persistently stored in RANOS

cId, MandatoryAttribute persistently stored in RANOS

tCell, Mandatory


uarfcnUl, MandatoryAttribute persistently stored in RANOS

uarfcnDl, Mandatory


primaryScramblingCode, MandatoryAttribute persistently stored in RANOS

primarySchPower, MandatoryAttribute persistently stored in RANOS

secondarySchPower, Mandatory


primaryCpichPower, MandatoryAttribute persistently stored in RANOS

maximumTransmissionPower, MandatoryAttribute persistently stored in RANOS

maxTxPowerUl, Mandatory


bchPower, Mandatory


cellReserved, Mandatory


treSelection, Mandatory


qualMeasQuantity, MandatoryAttribute persistently stored in RANOS

qHyst1, Mandatory


qHyst2, Mandatory


qQualMin, Mandatory







LOGICAL VIEW REPORT


pwrAdm, MandatoryAttribute persistently stored in RANOS

pwrAdmOffset, Mandatory


pwrOffset, MandatoryAttribute persistently stored in RANOS

pwrHyst, MandatoryAttribute persistently stored in RANOS

tmCongAction, Mandatory


releaseAseDl, Mandatory


dlCodeAdm, MandatoryAttribute persistently stored in RANOS

aseDlAdm, Mandatory


beMarginAseDl, Mandatory

Old name: beMarginDl


aseUlAdm, MandatoryAttribute persistently stored in RANOS

beMarginAseUl, Mandatory

Old name: beMarginUl[PersistInMirror: P5]



LOGICAL VIEW REPORT

sf8Adm, MandatoryAttribute persistently stored in RANOS

sf32Adm, Mandatory


aseUlAdmOffset, Mandatory


iubLinkRef, NoNotification, Restricted

Attribute persistently stored in RANOS.

[PersistInMirror: P5 onwards, notMandatory]

reservedBy, MandatoryAttribute persistently stored in RANOS

locationAreaRef



serviceAreaRef



routingAreaRef


utranCellPosition, Mandatory


sib1PlmnScopeValueTag, MandatoryAttribute persistently stored in RANOS

minPwrRl, MandatoryAttribute persistently stored in Ranos.

maxRate, Mandatory

Attribute persistently storedin Ranos.

interRate, MandatoryAttribute persistently storedin Ranos.

minimumRate, Mandatory


maxPwrMax, MandatoryAttribute persistently storedin Ranos.

interPwrMax, MandatoryAttribute persistently storedin Ranos.

minPwrMax, Mandatory


compModeAdm, MandatoryAttribute persistently storedin Ranos.

iFOffset, Mandatory


iFHyst, MandatoryAttribute persistently storedin Ranos.

iFCong, MandatoryAttribute persistently storedin Ranos.



LOGICAL VIEW REPORT

interFreqFddMeasIndicator, MandatoryAttribute persistently storedin Ranos.

sRatSearch, Mandatory


sIntraSearch, Mandatory


sInterSearch, Mandatory


fachMeasOccaCycLenCoeff, Mandatory


accessClassNBarredAttribute persistently storedin Ranos.

beMarginDlCode, Mandatory[PersistInMirror: P5]

beMarginDlPwr, Mandatory


sf16Adm, MandatoryAttribute persistently storedin Ranos.

hoType, Mandatory


usedFreqThresh2dEcno, MandatoryAttribute persistently stored in Ranos.

usedFreqThresh2dRscp, MandatoryAttribute persistently stored in Ranos.

nOutSyncInd


nInSyncIndAttribute persistently stored in Ranos.

rlFailureT


tmCongActionNgAttribute persistently stored in Ranos.

releaseAseDlNgAttribute persistently stored in Ranos.

tmInitialG


directedRetryTargetAttribute persistently stored in Ranos.

loadSharingGsmFractionAttribute persistently stored in Ranos.

loadSharingGsmThresholdAttribute persistently stored in Ranos.

hardIfhoCorrAttribute persistently stored in WRAN CM.

hsdpaUsersAdmAttribute persistently stored in WRAN CM.



LOGICAL VIEW REPORT

loadSharingMarginAttribute persistently stored in WRAN CM.

releaseAseDlGhs[PersistInMirror: P5]

tmCongActionGhs


tmInitialGhs


sf4AdmUl


sf16gAdm


sHcsRat


sf16AdmUl[PersistInMirror: P5 onwards]

sf8AdmUl[PersistInMirror: P5 onwards]

sf8gAdmUl[PersistInMirror: P5 onwards]

uraRef


agpsEnabled[PersistInMirror: P5 onwards]

codeLoadThresholdDlSf128[PersistInMirror: P5 onwards]

aseLoadThresholdUlSpeech[PersistInMirror: P5 onwards]

pwrLoadThresholdDlSpeech[PersistInMirror: P5 onwards]

eulNonServingCellUsersAdm


eulServingCellUsersAdm




LOGICAL VIEW REPORT

rateSelectionPsInteractive[PersistInMirror: P5 onwards]

accessClassesBarredCs


accessClassesBarredPs[PersistInMirror: P5 onwards]

hcsUsage[PersistInMirror: P6 onwards]

hcsSib3Config


amrWbRateDlMax[PersistInMirror: P6 onwards]

amrWbRateUlMax


antennaPosition[PersistInMirror: P6 onwards]

cellBroadcastSac


ctchOccasionPeriod


mocnCellProfileRef


standAloneSrbSelector


amrNbSelector


eulServingCellUsersAdmTti2[PersistInMirror: P6FP onwards]

GsmRelation

GsmRelationNotificationTypes = notifyObjectCreation, notifyObjectDeletion

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



LOGICAL VIEW REPORT

Attributes:

adjacentCell : string, Local, Mandatory

Reference to ExternalGsmCell MO which contains the specification of the adjacent cell. Even though this is nota 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



mobilityRelationTypeAttribute persistently stored in RANOS.

selectionPriority

MeContext


This MO models a RNC. One instance of this MO Type can exist per MIB.

This class is inherited from BasicMeContext.

NOTE: Functions that are general for all NE, shall be modelled in BasicMeContext MO.





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:dnPrefix : string, NoNotification, Restricted

DN Prefix information. Specified only if the instance of the MeContext MO is a local root instance of the MIB,


Sub: EQH, RAH

Ref. [21]


Provides support for putting a label on the MO instance. It is used by WRAN CM application to write theattribute value into the GUI.


Sub: EQH

Ref. [7]

ipAddress : string, Default = Set-At-Create, MandatoryThe 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]


RANOS_FOLLOWS = 1

NO_SWITCH = 2



LOGICAL VIEW REPORT

NE_FOLLOWS = 3UPGRADE_ATTEMPTED = 4

Sub: EQH

Ref. []


The branch and the version of the NE MIM used by this MeContext, <branch>.<version>.<release>, e.g. B.1.0


Sub: CMS

Ref. [7]




Sub: CMS

Ref. [7]



"NeverConnected" is set at instance creation."Connected " is set to indicate that WRAN CM has contact with the Network Element.


NEVER_CONNECTED = 1CONNECTED = 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 theRNC.


TOPOLOGY = 1

ATTRIBUTE = 2SYNCHRONIZED = 3

UNSYNCHRONIZED = 4

Sub: CMS

Ref. [7]




UPDATING = 1IDLE = 2

Sub: CMS

Ref. [2]



LOGICAL VIEW REPORT

generationCounter : long, Default = -1, NoNotificationKeeps track of notifications received from the RNC.


Sub: CMS

Ref. [2]




Sub: CMS

Ref. [7]

neType : SupportedNeType, Mandatory, NoNotificationThe NE type this MeContext represents.

RNC = 1

NODEB = 2

RANAG = 3ENODEB = 4

Ref. [7]




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:

OFFON

Sub:

Ref. []



LOGICAL VIEW REPORT




Sub: CMS, BCR


OSS time in ms last BCT related notification was

received from the node. Always reset after node synchronisation.The initial value set at create is -1.

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



Sub:

Ref. []



Sub:

Ref. []

pendingRestart : boolean, Default = falseIndicates whether or not a node restart is pending.

UtranRelation

UtranRelationNotificationTypes = notifyObjectCreation, notifyObjectDeletion

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]





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, MandatoryReference 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, RestrictedAttribute persistently stored in RANOS.


frequencyRelationType, MandatoryAttribute persistently stored in RANOS.

loadSharingCandidate, MandatoryAttribute persistently stored in RANOS.

selectionPriority

hcsSib11Config


nodeRelationType, NoNotification, ReadOnly[PersistInMirror: P5 onwards]

Operations:

setAdjacentCell (AdjacentCell : in string) : void

Action takes a single parameter which is a string value containing the FDN of the new target UtranCell. TheUtranRelation 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

This package contains the Cello MOC that contains WRAN CM specific local attributes. All

Cello MOC's used in Rnc Mirror Model are specializations of the MOC's defined inCommon Local Cello Model.



LOGICAL VIEW REPORT



Aal0TpVccTp

Attributes:

Aal2PathVccTp

Attributes:

Aal5TpVccTp

Attributes:

AtmCrossConnection

Attributes:




Naming RULEThe RDN value is set by the system to:





in case of channelization (e.g. a 155 Mbits/s physical interface configured to provide 63logical E1=2Mbits/s interfaces as supported by ET-MC41).


Attributes:



NOTE: Functions that are generall for all NE, shall be modelled in





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]




Sub: CMS

Ref. [21]






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:



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.

AgpsPositioningModels 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 beencreated.

This MOC defines the attributes that are persistently stored in Ranos.


Attributes:

altitudeDirection, Mandatory

altitude, Mandatory

uncertaintyAltitude, Mandatory

confidence, MandatorypolygonRadiusFactor

utranRnsPosition, Mandatory

utranRnsUncertaintyRadius, Mandatory

utranRnsConfidence

elevationThreshold

ueMeasurementReportCriteria[PersistInMirror: P5, P6]

posQualities, Mandatory[PersistInMirror: P6 onwards]

ArpMapModels the mapping of ARP values.




Attributes:

defaultArpQos, Mandatory, NoNotification

externalArpMapping, Mandatory, NoNotification

systemDefaultArpQos, NoNotification, ReadOnly


ArpQosClassProfile

Models the manageable characteristics of ARP.






LOGICAL VIEW REPORT

Attributes:


CchFrameSynchThis MOC models the manageable characteristics for Frame synchronization on the twoFACH transport channels and the PCH channel.



Attributes:

dto, Mandatory

doStep, Mandatory

toAWS, Mandatory

toAWE, Mandatory

toAE, Mandatory

ChannelSwitchingThis MO type models manageable characteristics for the channel switching algorithms.





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, NoNotificationSub: BCT

coverageTimer, Mandatory, NoNotification

Sub: BCT

inactivityTimer, Mandatory, NoNotificationSub: BCT

downswitchPwrMargin, Mandatory, NoNotificationSub: BCT

reportHysteresis, Mandatory, NoNotification

Sub: BCT

upswitchPwrMargin, Mandatory, NoNotificationSub: BCT

downswitchTimerSp

Sub: BCT

downswitchTimerUpSub: BCT

HsdschInactivityTimer

upswitchTimerUl, NoNotification[PersistInMirror: P5 onwards]

bandwidthMarginUl, NoNotification[PersistInMirror: P5 onwards]

bandwidthMargin, NoNotification


dlDownswitchBandwidthMargin, NoNotification


dlThroughputAllowUpswitchThreshold, NoNotification[PersistInMirror: P5 onwards]

dlThroughputDownswitchTimer, NoNotification[PersistInMirror: P5 onwards]

ulDownswitchBandwidthMargin, NoNotification


ulThroughputAllowUpswitchThreshold, NoNotification


ulThroughputDownswitchTimer, NoNotification


inactivityTimerPch, NoNotification


inactivityTimeMultiPsInteractive, NoNotification




LOGICAL VIEW REPORT

fachToHsDisabled, NoNotification[PersistInMirror: P5 onwards]

CnOperatorModels the manageable characteristics of a Core Network operator.




Attributes:

equivalentPlmnIdentities


iphoNetworkRefsGsm

iphoNetworkRefsUtran

plmnIdentity, Mandatory, Restricted

userLabelequivalentPlmnIdentityGroupRef[PersistInMirror: P6 onwards]

CoverageRelationModels 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, RestrictedAttribute persistently stored in RANOS.

This attribute is Mandatory/Restricted in the RNC MOM. See ref. [2].

coverageIndicatorAttribute persistently stored in WRAN CM.

hsPathlossThreshold


DchFrameSynchThis MOC models the manageable characteristics to mirror the transport delay on Iub for

DCH in uplink and downlink.





LOGICAL VIEW REPORT

Attributes:


dto, Mandatory

doStep, Mandatory

toAWS, Mandatory

toAWE, Mandatory

toAE, Mandatory

uto, Mandatory

uoStep, Mandatory

toAWSUl, Mandatory

toAWEUl, Mandatory

toAEUl, Mandatory


DchMapModels 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


EquipmentContainer MOC.

Attributes:

EulModels the manageable characteristics of the logical resources representing E-DCH

channels, and their associated physical channels E-AGCH and E-RGCH/E-HICH.






LOGICAL VIEW REPORT

Attributes:

administrativeState

numEagchCodes

numEhichErgchCodes

userLabel

availabilityStatus, ReadOnly


eulMaxTargetRtwp

edchTti2Support, ReadOnly[PersistInMirror: P6FP onwards]

FachThis 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:administrativeState, Mandatory




maxFach1Power, Mandatory

maxFach2Power, Mandatory

sccpchOffset, Mandatory

pOffset1Fach, Mandatory

pOffset3Fach, Mandatory

GpsReceiverRepresents a GPS receiver.



Attributes:


HandoverThis MOC models the management characteristics of IRAT and soft handover.





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

maxGsmMonSubsetSub: BCT

maxIefMonSubsetSub: BCT

cnhhoSupp[PersistInMirror: P5 onwards]

interFreqCnhhoPenaltyEcno[PersistInMirror: P5 onwards]

interFreqCnhhoPenaltyRscp


intraFreqCnhhoPenalty


intraFreqCnhhoWeight


tmStopGsmMeas[PersistInMirror: P5 onwards]

eulReservedHwBandwidthSchedDataNonServCell[PersistInMirror: P5]

HsdschModels the manageable characteristics of the logical resources representing HS-DSCH

channels, and their associated physical channels HS-SCCH and HS-PDSCH.





LOGICAL VIEW REPORT

Attributes:

administrativeState




deltaAck1

deltaNack1

deltaAck2

deltaNack2

deltaCqi1

deltaCqi2

initialAckNackRepetitionFactor

initialCqiRepetitionFactor

cqiFeedbackCycle

hsMeasurementPowerOffset

numHsPdschCodes

codeThresholdPdu656


numHsScchCodes[PersistInMirror: P5 onwards]

enhancedL2Support, ReadOnly


qam64Support, ReadOnly[PersistInMirror: P7 onwards]

IpAccessHostPoolModels 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.



[PersistInMirror: P6 onwards]Attributes:


availabilityStatus, NoNotification, ReadOnly

ipAccessHostRef, NoNotification

operationalState, NoNotification, ReadOnly



IpEthPacketDataRouterRepresents an individual IP link over ethernet in a PdrDevice.






LOGICAL VIEW REPORT

Attributes:

userLabel


reservedBy

ipAccessHostSpbRef, Mandatory, Restricted

ipAddressSelection, Restricted

pdrDeviceRef, NoNotification[PersistInMirror: P5]

IpSystemContainer MOC.

Attributes:

IuBcLinkModels the manageable characteristics of the Iu-BC interface between RNC and the Cell

Broadcast Centre (CBC).




Attributes:

administrativeState

cbcIpAddress, Mandatory, NoNotification


sourceIpAddressValidation, NoNotification


IubEdchModels manageable characteristics of Iub Enhanced Uplink resources.




Attributes:

edchDataFrameDelayThreshold, NoNotification

userLabel, NoNotification[PersistInMirror: P5 onwards]

IuLinkModels the manageable characteristics of a link between core network node and RNC

that includes the Iu user plane resources.






LOGICAL VIEW REPORT

Attributes:

packetDataRouterRef

userPlaneTransportOption, Mandatory[PersistInMirror: P6 onwards]

userLabel

userPlaneIpResourceRef


atmUserPlaneTermSubrackRef, NoNotification


LocationAreaNotificationTypes = notifyObjectCreation, notifyObjectDeletion

This MOC models manageable characteristics of a Location Area in the RNC. Note thatthis MOC belongs to the RNC MIM.



Attributes:

lac, Mandatory

t3212, Mandatory

att, Mandatory



MbmsModels the manageable characteristics of the MBMS resources on node level.




Attributes:

inactivityTimer, NoNotification

MbmsCchModels the manageable characteristics of the resources representing the MBMS commonchannels MCCH, MTCH and MICH per cell.






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[PersistInMirror: P6, P6FP]

mcchPowerOffset

mcchPowerOffsetTfcimichPowerOffset

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.






LOGICAL VIEW REPORT

Attributes:


commonPlmnRef, Mandatory, NoNotification


MtchFrameSynchModels the manageable characteristics of soft combining of MTCH FACHes for MBMSservices.




Attributes:

iubTransportDelayMax, NoNotification

iubTransportDelayOffset, NoNotificationphaseDriftThreshold, NoNotification

toaWindowEndpoint, NoNotification

toaWindowSize, NoNotification

NbapCommonThis MOC models the manageable characteristics of a control signalling link between the

RNC and an RBS, aimed for carrying NBAP common signalling.



Attributes:

administrativeState, Mandatory




activeUniSaalTpRef, Mandatory, NoNotification, Restricted

standbyUniSaalTpRef, NoNotification, Restricted

operationalState, Mandatory, ReadOnly

NbapDedicatedThis MOC models the manageable characteristics of a control signalling link aimed forcarrying NBAP dedicated signalling between the RNC and an RBS.





LOGICAL VIEW REPORT

Attributes:



l2EstablishReqRetryT, Mandatory, NoNotification[PersistInMirror: P5, P6]

activeUniSaalTpRef , Mandatory, NoNotification, Restricted

standbyUniSaalTpRef, NoNotification, Restricted


NodeSynchThis MOC models the configurable parameters for Node Synchronization between the

RNC and an RBS.



Attributes:


noOfSamples, Mandatory, NoNotification


supervisionIntervalT, Mandatory, NoNotification[PersistInMirror: P5]

phaseDiffThreshold, Mandatory, NoNotificationOld name: eventThreshold

reservedBy, Mandatory, NoNotification[PersistInMirror: P5]

phaseMeasurement, Mandatory, NoNotification, ReadOnly

accuracy, NoNotification, ReadOnly


timeStamp, NoNotification, ReadOnly

fixedWindowSizeInit, NoNotification


fixedWindowSizeSup, NoNotification[PersistInMirror: P6 onwards]

sampleIntervalInit, NoNotification


sampleIntervalSup, NoNotification


slidingWindowSize, NoNotification[PersistInMirror: P6 onwards]

NodeSynchTp

This MOC models the termination point parameters for Node Synchronization betweenthe RNC and an RBS.






LOGICAL VIEW REPORT

Attributes:



nodeSynchRef, Mandatory, NoNotification

aal0TpRefs, Mandatory, NoNotification

timDeviceRef, Mandatory, NoNotification


PacketDataRouterRepresents an indvidual PVC link in a packet data router in a pdrDevice.



Attributes:



rncIpAddress, Mandatory, NoNotification

cnIuLinkIpAddress, Mandatory, NoNotificationtimeToLive, Mandatory, NoNotification

pdrDeviceRef, Mandatory, NoNotification[PersistInMirror: P5]

aal5TpRef, Mandatory, NoNotification

PagingThis MO type models manageable characteristics for the paging algorithm.



Attributes:

cnDrxCycleLengthCs, Mandatory, NoNotification

cnDrxCycleLengthPs, Mandatory, NoNotification

noOfPagingRecordTransm, Mandatory, NoNotification

utranDrxCycleLength, NoNotification


PcapModels the manageable characteristics of the transport for the Iupc interface.




Attributes:

localSccpApRef, Mandatory, NoNotification, Restricted

remoteSccpApRef, Mandatory, NoNotification, Restricted

sccpDisabledT, NoNotification


userOutOfServiceT, NoNotification



LOGICAL VIEW REPORT

PchThis MOC models the manageable characteristics of a Paging Channel.



Attributes:




pchPower, Mandatory

pichPower, Mandatory

sccpchOffset, Mandatory

userLabel

PdrDeviceContainer MOC.



Attributes:


PlmnIdentityGroupA group of PLMN identities.




Attributes:

plmn, NoNotification


PlugInUnitContainer MOC

Attributes:

PositioningServiceClassModels the manageable characteristics of a positioning service class.






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


PowerControlThis 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, MandatoryulOuterLoopRegulator, Mandatory

sirMin, Mandatory

sirMax, Mandatory

dlInitSirTarget, Mandatory

ulInitSirTargetSrb, Mandatory

ulInitSirTargetLow, Mandatory

ulInitSirTargetHigh, Mandatory

cNbifho, Mandatory

fixedRefPower, Mandatory

Sub: BCT.

initShoPowerParam, MandatorySub: BCT.

ulInitSirTargetExtraHigh

transmissionTargetError


ulInitSirTargetEdch[PersistInMirror: P5 onwards]



LOGICAL VIEW REPORT

transmissionTargetErrorTti2[PersistInMirror: P6FP onwards]

ulSirStepTti2


ulInitSirTargetEdchTti2[PersistInMirror: P6FP onwards]

sirMaxTti2


RabHandlingModels manageable characteristics for RAB handling.



Attributes:

psStreamingInactivityTimer

activeQueueMgmt

dscpValuePsStreaming


eulHarqRv, NoNotification


RachThis MOCmodels the manageable characteristics of a Random Access Channel.


For more information see RNC MIM, ref [2].Attributes:





scramblingCodeWordNo, Mandatory

preambleSignatures, Mandatory

maxPreambleCycle, Mandatory

subChannelNo, Mandatory

aichTransmissionTiming, Mandatory

aichPower, Mandatory

powerOffsetP0, Mandatory

powerOffsetPpm, Mandatory

preambleRetransMax, Mandatory

constantValueCprach, Mandatory

spreadingFactor, Mandatory

RanapThe Ranap MOC models the configurable parameters for the control signalling link

between the RNC and core network (CN).



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[PersistInMirror: P5]

relativeCapacity[PersistInMirror: P5 onwards]

cnOperatorRef, Mandatory, NoNotification, Restricted


maxResetResourceMessageSize, NoNotification


RcsThis MO Type models manageable characteristics for the Radio Connection Supervision

algorithm.



Attributes:

dchRcLostT, Mandatory, NoNotification

cchWaitCuT, Mandatory, NoNotification

hsDschRcLostT

ResMeasControlModels the manageable characteristics for Radio Environment Statistics measurements



Attributes: [PersistInMirror: P5 onwards]



LOGICAL VIEW REPORT

resMeasure1

resMeasure2

resMeasure3

resMeasure4

resMeasure5

resMeasure6

resMeasPeriodSpeech

resMeasPeriodStreaming

resMeasPeriodVideo

resMeasPeriodInteractive

resUeFraction

RncCapacityModels 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

RncFeatureModels the manageable characteristics of a licensed optional feature.




Attributes:

featureState, NoNotification

isLicenseControlled, NoNotification

keyId, NoNotification

licenseState, NoNotification

serviceState, NoNotification

RncModuleThis MOC is used to group together a number of Iubs onto device boards on one Device

MP.





LOGICAL VIEW REPORT

Attributes:

t305, Mandatory, NoNotification

cfnOffsetMarginFirstRabEst, NoNotification[PersistInMirror: P6 onwards]

RttPositioningModels the manageable characteristics of the RTT positioning method.




Attributes:

measTimeMaxRbs, Mandatory, NoNotification

measTimeMaxUe, Mandatory, NoNotification

outlierFactor, Mandatory, NoNotification

posQualities, Mandatory, NoNotificationpropagationTimeUncertainty, Mandatory, NoNotification

SasPositioningModels the manageable characteristics of positioning in SAS-centric mode, as opposed to

RNC-centric mode.




Attributes:

enabledSasFeatures, NoNotificationpcapSasRespTime, NoNotification

SecurityHandlingModels 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



LOGICAL VIEW REPORT

ServiceAreaNotificationTypes = notifyObjectCreation, notifyObjectDeletion

This MOC models manageable characteristics of a Service Area in the RNC.



Attributes:

sac, Mandatory



SidThis 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[PersistInMirror: P6 onwards]

schedulingBlockEnabled, NoNotification


sib18, NoNotification[PersistInMirror: P6FP onwards]

SpDevicePoolContainer MOC.



Attributes:

SpiQosClassModels the manageable characteristics of mapping SPI QoS settings to Flow Controlactivities.

Value part of the RDN is the SPI value.




LOGICAL VIEW REPORT



Attributes:

flowControl, Mandatory, NoNotification


SubrackContainer MOC.

Attributes:

SystemFunctions

Container MOC.[PersistInMirror: P5 onwards]

Attributes:

TcMapModels 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


TimDeviceThis MO Type represents a device individual of the device type Timing Unit device.





LOGICAL VIEW REPORT

Attributes:


administrativeState, Mandatory, NoNotification

reservedBy, Mandatory, NoNotification[PersistInMirror: P5]

TimDeviceSetContainer MOC[PersistInMirror: P5]

Attributes:

TnlCchQosClassProfileActs as a container for the instances that model the transport bearer Quality of Serviceclasses for the common channels.

Under this profile, one instance of the MO TnlQosClass is created by the system. TheTnlQosClass instance contains the Quality of Service settings to use for the common

channels.

Only used if the dual stack feature is configured.




Attributes:


TnlDchQosClassProfileActs as a container for the instances that model the mapping from DCH traffic classes to

transport bearer Quality of Service classes.




Attributes:


TnlHspaQosClassProfileActs as a container for the instances that model the mapping from HSPA traffic classes to





LOGICAL VIEW REPORT



Attributes:


TnlIuQosClassProfileActs as a container for the instances that model the mapping from Iu traffic classes to





Attributes:


TnlQosClassModels manageable characteristics of TNL QoS Class.




Attributes:

aal2QosClass, NoNotificationdscpEgress, NoNotification

dscpIngress, NoNotification

spi, NoNotification, ReadOnly


prefIubUserPlaneTransportOption, Mandatory, NoNotification


TrafficClassModels the manageable characteristics of QoS Settings for traffic classes, i.e. RABs.






LOGICAL VIEW REPORT

Attributes:

cnInd, Mandatory, NoNotification, Restricted

defaultQosRef, NoNotification

serviceInd, Mandatory, NoNotification, Restricted

ssd, Mandatory, NoNotification, Restricted

tcInd, Mandatory, NoNotification, Restricted


TrafficClassPsIntModels the manageable characteristics of QoS settings for PS Interactive RABs.




Attributes:

qosRef, NoNotification

si, Mandatory, NoNotification, Restrictedthp, Mandatory, NoNotification, Restricted


TuDeviceGroupContainer MOC[PersistInMirror: P5]

Attributes:

UeMeasControl

This MOC models manageable characteristics forUE measurments.





LOGICAL VIEW REPORT

Attributes:

reportingRange1a, Mandatory

reportingRange1b, Mandatory

hysteresis1c, Mandatory

hysteresis1d, Mandatory

hysteresis2d, Mandatory

hysteresis2f, Mandatory

utranRelThresh3aEcnoOld 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, Mandatoryhysteresis1a, 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

filterCoefficient1filterCoefficient2

utranCoefficient3

gsmCoefficient3

filterCoeff6

filterCoeff4_2b

w1a

w1b

usedFreqW2d

usedFreqW2f

usedFreqW4_2b

utranW3a

nonUsedFreqW4_2b

timeToTrigger2dRscp

timeToTrigger2fRscp

utranRelThreshRscp

gsmFilterCoefficient3utranFilterCoefficient3

event1dRncThreshold[PersistInMirror: P5 onwards]

event1dRncOffset[PersistInMirror: P5 onwards]

timeToTrigger6d


txPowerConnQualMonEnabled




LOGICAL VIEW REPORT

UePositioningModels the manageable characteristics for UE positioning.



Attributes:

enabledPositioningFeatures

cellIdPosQualities, Mandatory[PersistInMirror: P6 onwards]

clientTypeMapping, Mandatory


UeRcModels a Radio Connection Configuration corresponding to a combination of 0 or 1

UeRcRrc MO types and 0, 1 or 2 UeRcRab MO types.



Attributes:

userLabelSub: BCG

serviceOffset2dEcno[PersistInMirror: P5 onwards]

serviceOffset2dRscp[PersistInMirror: P5 onwards]

UeRcEdchFlowModels the manageable characteristics of an E-DCH MAC-d flow.




Attributes:

harqTransmUlMax, Mandatory, NoNotification

UeRabTypeThe 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.




LOGICAL VIEW REPORT



Attributes:

trBearerQosClass, NoNotification[PersistInMirror: P5, P6]

UeRcPhyChEdchModels the manageable characteristics of the E-DCH transport channel.



Attributes:

eulHarqRv, NoNotification

UeRcRabModels 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

trBearerQosClass, NoNotification[PersistInMirror: P5, P6]

UeRcRrcModels 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:

trBearerQosClass, NoNotification



LOGICAL VIEW REPORT

UeRcTrChThis MO type models manageable characteristics related to a Transport Channel (TrCh)

of a Radio Connection.



Attributes:

blerQualityTargetDl, Mandatory, NoNotification

blerQualityTargetUl, Mandatory, NoNotification

UraModels the manageable characteristics for a UTRAN Registration Area (URA) in theRNC. 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

UtranNetworkModels the manageable characteristics of a Utran Network.




Attributes:

aliasPlmnIdentities, Restricted

plmnIdentity, Mandatory

reservedBy, Restricted, ReadOnly

userLabel

WcdmaCarrierModels 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 beassigned.






LOGICAL VIEW REPORT

Attributes:

defaultHoType

freqBand

sib5bisEnabled

uarfcnDl

userLabel

References to MOs in the RNC 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]):

For more information see ref. [31]

RncModule=1



LOGICAL VIEW REPORT

RncModule=2

RncModule=3

RncModule=4

RncModule=5



LOGICAL VIEW REPORT

RncModule=6

RncModule=7

RncModule=8

RncModule=9



LOGICAL VIEW REPORT

RncModule=10

RncModule=11

RncModule=12

RncModule=13



LOGICAL VIEW REPORT

RncModule=14

RncModule=15

RncModule=16

RncModule=17



LOGICAL VIEW REPORT

RncModule=18

RncModule=19

RncModule=20

RncModule=21



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.



LOGICAL VIEW REPORT


CellIdAlreadyDefinedThrown by CMS when creating an ExternalUtranCell MO.

ActionNotSupported

CacheIsSynchronizedMandatoryAttrMissingAtCreate

PlmnIdAlreadyDefinedThrown by CMS when creating an ExternalGsmPlmn MO.

LocationAreaIdAlreadyDefinedThrown by CMS when creating a LocationArea MO.

RoutingAreaIdAlreadyDefinedThrown by CMS when creating a RoutingArea MO.

ServiceAreaIdAlreadyDefinedThrown 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.



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,25600: not used

Step size: 40, 256 or 2560 chips.

Ref. [2]

AseLoadThresholdUlSpeech

Attributes:

amr12200 : longThreshold 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 loadResolution: 1

amr7950 : long

Threshold to be used in the initial AMR rate selection algorithm for selecting AMR7.95 speech codec in setup


Unit: % of UL Ase load

Resolution: 1

amr5900 : long

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

Unit: % of UL Ase load

Resolution: 1

PwrLoadThresholdDlSpeech

Attributes:

amr12200 : longThreshold to be used in the initial AMR rate selection algorithm for selecting AMR12.2 speech codec in setup


Unit: % of DL power load

Resolution: 1

amr7950 : long

Threshold to be used in the initial AMR rate selection algorithm for selecting AMR7.95 speech codec in setupof speech requests. Only applicable when establishing an AMR-NB multi-rate RAB.

Unit: % of DL power load

Resolution: 1

amr5900 : longThreshold 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.

Unit: % of DL power loadResolution: 1



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 defaultrate 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 ULrate of a PS interactive RAB from a lower rate than the preferred rate.

Unit: kbps

Resolution: N/A

dlPrefRate : longPreferred 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



LOGICAL VIEW REPORT

CellCapabilityContains capability information for external cells.

Attributes:

hsdschSupport : OnOffVals, Default = OFFCapability information indicating if HS is supported in the cell.


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

HcsSib3ConfigContains 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 descriptionof 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 thisInformation Element, see 3GPP TS 25.331.

Unit: N/A

Resolution: 1

sSearchHcs : longSpecifies 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/AResolution: 2

HcsUsageContains parameters that will be mapped to IE "Use of HCS" in System Information

Blocks 11 and 12.



LOGICAL VIEW REPORT

Attributes:

idleMode : BooleanVals

Specifies the value of the Information Element "Use of HCS" in System information Block 11. For thedescription of this Information Element, see 3GPP TS 25.331.

Unit: N/A

Resolution: N/A

connectedMode : BooleanValsSpecifies 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

SupportedMimSwitchPolicyAttributes:

RANOS_FOLLOWS : long = 1

NO_SWITCH : long = 2

NE_FOLLOWS : long = 3

UPGRADE_ATTEMPTED : long = 4



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

TerminologySee 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



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/1Configuration 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 betweenUTRAN 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



LOGICAL VIEW REPORT

TOTALS:

147 Logical Packages396 Classes

LOGICAL PACKAGE STRUCTURE

Logical ViewRanos Node Model

RANOS_APPLICATION_MODEL

RANOS_RN_APPLICATION_MODEL

Rn Application Model Main ViewRnApplication

UserDefEntityList


CellAndChannelProfileRANOS_SUPPORT_APPLICATION_MODEL

Support Application Model Main View

LogFilterUserPreferences

SupportApplication

RANOS_SUBNETWORK_MODEL

ManagementNode

SubNetworkSubnetwork Model Main View

Segment

Site

Link

RbsGroupIRPAgent

ExternalUtranPlmnExternalGsmPlmn

ExternalUtranCell

ExternalGsmCell

NotificationIRPAlarmIRP

BulkCmIRP

IRATHOMUTRAN

Subnetwork Model IRP ViewSubnetwork Model Site View

Areas

LocationAreaRoutingArea

ServiceArea

Subnetwork Model Areas View

PmIRP

Data Types, Definitions and ExceptionsPlmn


Subnetwork Model External Node View

Subnetwork Model TN Application View



LOGICAL VIEW REPORT

TnApplication

MbmsServiceArea

General DataTypes, Definitions and Exceptions

RANOS COMMON MOC

BasicMeContextManaged Object Types

General

General OperationsGeneral Attributes

Alarms

General NotificationsGeneral Exceptions

General Naming Rules

RANOS_INTERMIM_MODEL

SUBNETWORK APPLICATIONS

SUBNETWORK RBS_MIRRORSUBNETWORK RNC_MIRROR

SUBNETWORK RANAG_MIRROR

SUBNETWORK ERBS_MIRRORCELLO MODEL

Basic Cello ModelBasicManagedElement

Cello Attributes mirrored in RanosCello MOs needed for Synch

MIRRORED MIMs

RANOS_RANAG_MIRROR_MODEL_H

Ranag Mirror Model Main View

Ranag Cello MOC's containing Ranos local attributesRanag Mirror and Cello Local View

References to MOs in the RANAG Equipment View

RANOS_RBS_MIRROR_MODEL_HRbs Mirror Model Main View

MeContext

Rbs Mirror and Cello Local ViewRbs Cello MOC's containing Ranos local attributesRbs Attributes Mirrored in Ranos

References to MOs in the RBS Equipment View

StandardRBS

RBS3104RBS 3107, 3206M, 3018, 3418 and 3518

RBS Base Model

Rbs MOs needed for SynchRANOS_RNC_MIRROR_MODEL_H

MeContext

UtranRelation

GsmRelation

Rnc Mirror Model Main ViewRnc Mirror and Cello Local View

Rnc Attributes Mirrored in Ranos

References to MOs in the RNC Equipment View

RncModule=1RncModule=2


RncModule=5

RncModule=6



LOGICAL VIEW REPORT

RncModule=7

RncModule=8

RncModule=9

RncModule=10


RncModule=13


wran cm managed object model

Documents