Anda di halaman 1dari 1166

Managed Object Management

Contents
5.7 Managed Object Management
5.7.1 eNodeB MO Reference
5.7.1.1 Changes in eNodeB MO Reference
5.7.1.2 MOM User Guide
5.7.1.2.1 Overview of MO Models
5.7.1.2.2 MO Attributes
5.7.1.2.2.1 Data Types
5.7.1.2.2.2 Parameter Attributes
5.7.1.2.3 MO Operations
5.7.1.2.4 Relationships Between MOs
5.7.1.2.5 Effective Scenarios
5.7.1.3 Equipment MOM
5.7.1.3.1 BBU MOM Description
5.7.1.3.2 RF Unit MOM Description
5.7.1.3.3 ALD MOM Description
5.7.1.3.4 Electromechanical Device MOM Description
5.7.1.3.5 Clock MOM Description
5.7.1.4 Transport MOM
5.7.1.4.1 IPv4 MOM Description
5.7.1.4.2 IPv6 MOM Description
5.7.1.4.3 Transmission Security MOM Description
5.7.1.4.4 Transmission Maintenance and Detection MOM Description
5.7.1.4.5 Transport Resource Management MOM Description
5.7.1.4.6 PKI MOM Description
5.7.1.5 Radio MOM
5.7.1.5.1 Cell and Channel MOM Description
5.7.1.5.2 Neighboring Cell and Neighbor Relationship MOM Description
5.7.1.5.3 QCI MOM Description
5.7.1.5.4 RAN Sharing MOM Description
5.7.1.5.5 User Steering MOM Description
5.7.1.6 MO
5.7.1.6.1 Transport-tree
5.7.1.6.1.1 ACL
5.7.1.6.1.2 ACL6
5.7.1.6.1.3 ACLRULE
5.7.1.6.1.4 ACLRULE6
5.7.1.6.1.5 APPCERT
5.7.1.6.1.6 BFDSESSION
5.7.1.6.1.7 CA
5.7.1.6.1.8 CERTCHKTSK
5.7.1.6.1.9 CERTDEPLOY
5.7.1.6.1.10 CERTMK
5.7.1.6.1.11 CERTREQ
5.7.1.6.1.12 CFMBNDIP
5.7.1.6.1.13 CFMMA
5.7.1.6.1.14 CFMMD
5.7.1.6.1.15 CFMMEP
5.7.1.6.1.16 CFMRMEP
5.7.1.6.1.17 CPBEARER
5.7.1.6.1.18 CRL
5.7.1.6.1.19 CRLPOLICY
5.7.1.6.1.20 CRLTSK
5.7.1.6.1.21 CROSSCERT
5.7.1.6.1.22 DEVIP
5.7.1.6.1.23 DEVIP6
5.7.1.6.1.24 DHCPRELAYSWITCH
5.7.1.6.1.25 DHCPSVRIP
5.7.1.6.1.26 DHCPSW
5.7.1.6.1.27 DIFPRI
5.7.1.6.1.28 DOT1X
5.7.1.6.1.29 DSCPMAP
5.7.1.6.1.30 E1T1
5.7.1.6.1.31 E1T1BER
5.7.1.6.1.32 EP2RSCGRP
5.7.1.6.1.33 EPGROUP
5.7.1.6.1.34 ETHOAM3AH
5.7.1.6.1.35 ETHPORT
5.7.1.6.1.36 ETHTRK
5.7.1.6.1.37 ETHTRKLNK
5.7.1.6.1.38 FLOODDEFEND
5.7.1.6.1.39 GTPU
5.7.1.6.1.40 GTRANSPARA
5.7.1.6.1.41 HAGRP
5.7.1.6.1.42 IKECFG
5.7.1.6.1.43 IKEPEER
5.7.1.6.1.44 IKEPEER6
5.7.1.6.1.45 IKEPROPOSAL
5.7.1.6.1.46 IP2RSCGRP
5.7.1.6.1.47 IP2RSCGRP6
5.7.1.6.1.48 IPGUARD
5.7.1.6.1.49 IPITF6
5.7.1.6.1.50 IPPATH
5.7.1.6.1.51 IPPATH6
5.7.1.6.1.52 IPPATHRT
5.7.1.6.1.53 IPPMSESSION
5.7.1.6.1.54 IPRT
5.7.1.6.1.55 IPRT6
5.7.1.6.1.56 IPSECBIND
5.7.1.6.1.57 IPSECBIND6
5.7.1.6.1.58 IPSECDTNL
5.7.1.6.1.59 IPSECPOLICY
5.7.1.6.1.60 IPSECPOLICY6
5.7.1.6.1.61 IPSECPROPOSAL
5.7.1.6.1.62 LLDPGLOBAL
5.7.1.6.1.63 LLDPLOCAL
5.7.1.6.1.64 LOCALETHPORT
5.7.1.6.1.65 LOCALIP
5.7.1.6.1.66 LOCALIP6
5.7.1.6.1.67 LR
5.7.1.6.1.68 MPGRP
5.7.1.6.1.69 MPLNK
5.7.1.6.1.70 OMCH
5.7.1.6.1.71 OMCH6
5.7.1.6.1.72 PACKETFILTER
5.7.1.6.1.73 PINGFILTER
5.7.1.6.1.74 PLRTHRESHOLD
5.7.1.6.1.75 PMTUCFG
5.7.1.6.1.76 PORTSECURITY
5.7.1.6.1.77 PPPLNK
5.7.1.6.1.78 PRI2QUE
5.7.1.6.1.79 RSCGRP
5.7.1.6.1.80 RSCGRPALG
5.7.1.6.1.81 SCTPHOST
5.7.1.6.1.82 SCTPLNK
5.7.1.6.1.83 SCTPLNK6
5.7.1.6.1.84 SCTPPEER
5.7.1.6.1.85 SCTPTEMPLATE
5.7.1.6.1.86 SECURITYHOST
5.7.1.6.1.87 SECURITYPEER
5.7.1.6.1.88 SECURITYTEMPLATE
5.7.1.6.1.89 SUBIF
5.7.1.6.1.90 SUBNETVLAN
5.7.1.6.1.91 TACALG
5.7.1.6.1.92 TLDRALG
5.7.1.6.1.93 TLFRSWITCH
5.7.1.6.1.94 TOLCALG
5.7.1.6.1.95 TRANSPORT
5.7.1.6.1.96 TRUSTCERT
5.7.1.6.1.97 TUNNEL
5.7.1.6.1.98 UDPSESSION
5.7.1.6.1.99 UDT
5.7.1.6.1.100 UDTPARAGRP
5.7.1.6.1.101 USERPLANEHOST
5.7.1.6.1.102 USERPLANEPEER
5.7.1.6.1.103 VLANCLASS
5.7.1.6.1.104 VLANMAP
5.7.1.6.1.105 VRF
5.7.1.6.2 Equipments-tree
5.7.1.6.2.1 AAMU
5.7.1.6.2.2 AARU
5.7.1.6.2.3 AAS
5.7.1.6.2.4 ALD
5.7.1.6.2.5 ALMPORT
5.7.1.6.2.6 ANTENNAPORT
5.7.1.6.2.7 APPLICATION
5.7.1.6.2.8 BASEBANDEQM
5.7.1.6.2.9 BATCTPA
5.7.1.6.2.10 BATTERY
5.7.1.6.2.11 BBP
5.7.1.6.2.12 BBPLINK
5.7.1.6.2.13 BBUFAN
5.7.1.6.2.14 BCP
5.7.1.6.2.15 BITS
5.7.1.6.2.16 BRI
5.7.1.6.2.17 CABINET
5.7.1.6.2.18 CARRIERRESOURCE
5.7.1.6.2.19 CASCADEPORT
5.7.1.6.2.20 CCU
5.7.1.6.2.21 CDE
5.7.1.6.2.22 CFGBAK
5.7.1.6.2.23 CFGFILESTAT
5.7.1.6.2.24 CFGSTAT
5.7.1.6.2.25 CHK
5.7.1.6.2.26 CPRILBR
5.7.1.6.2.27 CPRIPORT
5.7.1.6.2.28 CTRLLNK
5.7.1.6.2.29 DIESELGEN
5.7.1.6.2.30 EMU
5.7.1.6.2.31 ENERGYCON
5.7.1.6.2.32 EQUIPMENT
5.7.1.6.2.33 FM
5.7.1.6.2.34 FMU
5.7.1.6.2.35 FTPCLT
5.7.1.6.2.36 FTPCLTPORT
5.7.1.6.2.37 GPS
5.7.1.6.2.38 GTMU
5.7.1.6.2.39 HTCDPA
5.7.1.6.2.40 IPCLKLNK
5.7.1.6.2.41 LINECLK
5.7.1.6.2.42 LOCATION
5.7.1.6.2.43 MAINSALARMBIND
5.7.1.6.2.44 MPT
5.7.1.6.2.45 NE
5.7.1.6.2.46 NODE
5.7.1.6.2.47 NTPCP
5.7.1.6.2.48 OMUCURTIME
5.7.1.6.2.49 OUTPORT
5.7.1.6.2.50 PEERCLK
5.7.1.6.2.51 PEU
5.7.1.6.2.52 PMU
5.7.1.6.2.53 PSU
5.7.1.6.2.54 PSUIS
5.7.1.6.2.55 RCVMODE
5.7.1.6.2.56 RE
5.7.1.6.2.57 RET
5.7.1.6.2.58 RETDEVICEDATA
5.7.1.6.2.59 RETPORT
5.7.1.6.2.60 RETSUBUNIT
5.7.1.6.2.61 RFU
5.7.1.6.2.62 RHUB
5.7.1.6.2.63 RRU
5.7.1.6.2.64 RRUCHAIN
5.7.1.6.2.65 RU
5.7.1.6.2.66 RXBRANCH
5.7.1.6.2.67 SECTOR
5.7.1.6.2.68 SECTOREQM
5.7.1.6.2.69 SES
5.7.1.6.2.70 SFP
5.7.1.6.2.71 SSL
5.7.1.6.2.72 SUBRACK
5.7.1.6.2.73 SYNCETH
5.7.1.6.2.74 TASM
5.7.1.6.2.75 TCU
5.7.1.6.2.76 TIMESRC
5.7.1.6.2.77 TMA
5.7.1.6.2.78 TMADEVICEDATA
5.7.1.6.2.79 TMASUBUNIT
5.7.1.6.2.80 TOD
5.7.1.6.2.81 TRP
5.7.1.6.2.82 TXBRANCH
5.7.1.6.2.83 TZ
5.7.1.6.2.84 UCIU
5.7.1.6.2.85 UEIU
5.7.1.6.2.86 USCU
5.7.1.6.2.87 VANTENNAPORT
5.7.1.6.2.88 VRET
5.7.1.6.2.89 VRETSUBUNIT
5.7.1.6.2.90 WEBLMT
5.7.1.6.3 Radio-tree
5.7.1.6.3.1 AlgoDefaultPara
5.7.1.6.3.2 ANR
5.7.1.6.3.3 BcchCfg
5.7.1.6.3.4 BfAnt
5.7.1.6.3.5 BfMimoAdaptiveParaCfg
5.7.1.6.3.6 CaGroup
5.7.1.6.3.7 CaGroupCell
5.7.1.6.3.8 CaMgtCfg
5.7.1.6.3.9 Cdma20001XrttExtCell
5.7.1.6.3.10 Cdma20001XrttNCell
5.7.1.6.3.11 Cdma20001XrttPreReg
5.7.1.6.3.12 Cdma2000BandClass
5.7.1.6.3.13 Cdma2000BcSCellOp
5.7.1.6.3.14 Cdma2000HrpdExtCell
5.7.1.6.3.15 Cdma2000HrpdNCell
5.7.1.6.3.16 Cdma2000HrpdPreReg
5.7.1.6.3.17 Cdma2000HrpdRefCell
5.7.1.6.3.18 Cdma2000Nfreq
5.7.1.6.3.19 Cell
5.7.1.6.3.20 CellAcBar
5.7.1.6.3.21 CellAccess
5.7.1.6.3.22 CellAlgoSwitch
5.7.1.6.3.23 CellBf
5.7.1.6.3.24 CellChPwrCfg
5.7.1.6.3.25 CellDlCompAlgo
5.7.1.6.3.26 CellDlIcic
5.7.1.6.3.27 CellDLIcicMcPara
5.7.1.6.3.28 CellDlpcPdcch
5.7.1.6.3.29 CellDlpcPdsch
5.7.1.6.3.30 CellDlpcPdschPa
5.7.1.6.3.31 CellDlpcPhich
5.7.1.6.3.32 CellDlschAlgo
5.7.1.6.3.33 CellDrxPara
5.7.1.6.3.34 CellEicic
5.7.1.6.3.35 CellExtendedQci
5.7.1.6.3.36 CellHoParaCfg
5.7.1.6.3.37 CellIdPrdUpt
5.7.1.6.3.38 CellLowPower
5.7.1.6.3.39 CellMLB
5.7.1.6.3.40 CellMro
5.7.1.6.3.41 CellNoAccessAlmPara
5.7.1.6.3.42 CellOp
5.7.1.6.3.43 CellPdcchAlgo
5.7.1.6.3.44 CellPucchAlgo
5.7.1.6.3.45 CellRacThd
5.7.1.6.3.46 CellResel
5.7.1.6.3.47 CellReselCdma2000
5.7.1.6.3.48 CellReselGeran
5.7.1.6.3.49 CellReselUtran
5.7.1.6.3.50 CellRfShutdown
5.7.1.6.3.51 CellRicAlgo
5.7.1.6.3.52 CellSel
5.7.1.6.3.53 CellServiceDiffCfg
5.7.1.6.3.54 CellShutdown
5.7.1.6.3.55 CellSiMap
5.7.1.6.3.56 CellSimuLoad
5.7.1.6.3.57 CellStandardQci
5.7.1.6.3.58 CellUlCompAlgo
5.7.1.6.3.59 CellUlIcic
5.7.1.6.3.60 CellULIcicMcPara
5.7.1.6.3.61 CellUlpcComm
5.7.1.6.3.62 CellUlpcDedic
5.7.1.6.3.63 CellUlschAlgo
5.7.1.6.3.64 CnOperator
5.7.1.6.3.65 CnOperatorExtendedQci
5.7.1.6.3.66 CnOperatorHoCfg
5.7.1.6.3.67 CnOperatorIpPath
5.7.1.6.3.68 CnOperatorSpidCfg
5.7.1.6.3.69 CnOperatorStandardQci
5.7.1.6.3.70 CnOperatorTa
5.7.1.6.3.71 CounterCheckPara
5.7.1.6.3.72 CqiAdaptiveCfg
5.7.1.6.3.73 CSFallBackBlindHoCfg
5.7.1.6.3.74 CSFallBackHo
5.7.1.6.3.75 CSFallBackPolicyCfg
5.7.1.6.3.76 DistBasedHO
5.7.1.6.3.77 Drx
5.7.1.6.3.78 DrxParaGroup
5.7.1.6.3.79 Emc
5.7.1.6.3.80 eNBCellOpRsvdPara
5.7.1.6.3.81 eNBCellQciRsvdPara
5.7.1.6.3.82 eNBCellRsvdPara
5.7.1.6.3.83 eNBCnOpQciRsvdPara
5.7.1.6.3.84 eNBCnOpRsvdPara
5.7.1.6.3.85 eNBLicenseAlmThd
5.7.1.6.3.86 eNBQciRsvdPara
5.7.1.6.3.87 eNBRsvdPara
5.7.1.6.3.88 ENodeBAlgoSwitch
5.7.1.6.3.89 eNodeBAutoPowerOff
5.7.1.6.3.90 eNodeBChrOutputCtrl
5.7.1.6.3.91 ENodeBCipherCap
5.7.1.6.3.92 ENodeBConnStateTimer
5.7.1.6.3.93 eNodeBFlowCtrlPara
5.7.1.6.3.94 eNodeBFunction
5.7.1.6.3.95 ENodeBIntegrityCap
5.7.1.6.3.96 eNodeBPath
5.7.1.6.3.97 ENodeBSharingMode
5.7.1.6.3.98 eUCellSectorEqm
5.7.1.6.3.99 EuSectorEqmGroup
5.7.1.6.3.100 EutranExternalCell
5.7.1.6.3.101 EutranExternalCellPlmn
5.7.1.6.3.102 EutranInterFreqNCell
5.7.1.6.3.103 EutranInterNFreq
5.7.1.6.3.104 EutranIntraFreqNCell
5.7.1.6.3.105 EutranNFreqRanShare
5.7.1.6.3.106 EutranNFreqSCellOp
5.7.1.6.3.107 ExtendedQci
5.7.1.6.3.108 GeranExternalCell
5.7.1.6.3.109 GeranExternalCellPlmn
5.7.1.6.3.110 GeranInterfArfcn
5.7.1.6.3.111 GeranInterfCfg
5.7.1.6.3.112 GeranNcell
5.7.1.6.3.113 GeranNFGroupSCellOp
5.7.1.6.3.114 GeranNfreqGroup
5.7.1.6.3.115 GeranNfreqGroupArfcn
5.7.1.6.3.116 GeranRanShare
5.7.1.6.3.117 GlobalProcSwitch
5.7.1.6.3.118 HoMeasComm
5.7.1.6.3.119 IbdlInfo
5.7.1.6.3.120 InterFreqBlkCell
5.7.1.6.3.121 InterFreqHoGroup
5.7.1.6.3.122 InterPlmnHoList
5.7.1.6.3.123 InterRatCellShutdown
5.7.1.6.3.124 InterRatHoCdma1xRttGroup
5.7.1.6.3.125 InterRatHoCdmaHrpdGroup
5.7.1.6.3.126 InterRatHoComm
5.7.1.6.3.127 InterRatHoCommGroup
5.7.1.6.3.128 InterRatHoGeranGroup
5.7.1.6.3.129 InterRatHoUtranGroup
5.7.1.6.3.130 InterRatPolicyCfgGroup
5.7.1.6.3.131 IntraFreqBlkCell
5.7.1.6.3.132 IntraFreqHoGroup
5.7.1.6.3.133 IntraRatHoComm
5.7.1.6.3.134 LicenseSharingPolicy
5.7.1.6.3.135 LicRatio
5.7.1.6.3.136 LicRatioSharePolicy
5.7.1.6.3.137 MimoAdaptiveParaCfg
5.7.1.6.3.138 MmeFeatureCfg
5.7.1.6.3.139 MRO
5.7.1.6.3.140 PCCHCfg
5.7.1.6.3.141 PdcpRohcPara
5.7.1.6.3.142 PDSCHCfg
5.7.1.6.3.143 PHICHCfg
5.7.1.6.3.144 PUCCHCfg
5.7.1.6.3.145 PUSCHCfg
5.7.1.6.3.146 PuschParam
5.7.1.6.3.147 RACHCfg
5.7.1.6.3.148 RatFreqPriorityGroup
5.7.1.6.3.149 RlcPdcpParaGroup
5.7.1.6.3.150 RlfTimerConstGroup
5.7.1.6.3.151 RrcConnStateTimer
5.7.1.6.3.152 S1
5.7.1.6.3.153 S1Interface
5.7.1.6.3.154 S1ReestTimer
5.7.1.6.3.155 ServiceIfHoCfgGroup
5.7.1.6.3.156 ServiceIrHoCfgGroup
5.7.1.6.3.157 SfnAuxResBind
5.7.1.6.3.158 SfnCellBind
5.7.1.6.3.159 SimuLoad
5.7.1.6.3.160 SpidCfg
5.7.1.6.3.161 SrsAdaptiveCfg
5.7.1.6.3.162 SRSCfg
5.7.1.6.3.163 StandardQci
5.7.1.6.3.164 TceIpMapping
5.7.1.6.3.165 TcpAckCtrlAlgo
5.7.1.6.3.166 TcpMssCtrl
5.7.1.6.3.167 TddFrameOffset
5.7.1.6.3.168 TddResModeSwitch
5.7.1.6.3.169 TimeAlignmentTimer
5.7.1.6.3.170 TpeAlgo
5.7.1.6.3.171 TypDrbBsr
5.7.1.6.3.172 UeTimerConst
5.7.1.6.3.173 UtranExternalCell
5.7.1.6.3.174 UtranExternalCellPlmn
5.7.1.6.3.175 UtranNCell
5.7.1.6.3.176 UtranNFreq
5.7.1.6.3.177 UtranNFreqSCellOp
5.7.1.6.3.178 UtranRanShare
5.7.1.6.3.179 VQMAlgo
5.7.1.6.3.180 X2
5.7.1.6.3.181 X2AutoSetupOperator
5.7.1.6.3.182 X2BlackWhiteList
5.7.1.6.3.183 X2Interface
5.7 Managed Object Management
In a multi-mode base station (MBTS), only LTE configuration management can be designed
based on the managed objects.

Related Document Description

eNodeB MO Reference This document describes managed object


management in terms of model parameters and
MML command.

5.7.1 eNodeB MO Reference


Overview

This document describes managed object models (MOMs), illustrates MOM views, and provides
the corresponding managed objects (MOs).

Product Versions

The following table lists the product versions related to this document.

Product Name Solution Version Product Version

BTS3900 SRAN8.0 V100R008C00


eRAN6.0
BTS3900A

BTS3900L

BTS3900AL

DBS3900 SRAN8.0
eRAN6.0
eRAN TDD 6.0

Intended Audience
This document is intended for:
Field engineers
Network planners
Network operators
System engineers
Shift operators
Site maintainers

Organization

5.7.1.1 Changes in eNodeB MO Reference


This chapter describes the changes about MOMs user guides and MOM descriptions in eNodeB
MO Reference. For details about the changes, see appendix 2 in the corresponding release note.

02 (2013-06-27)

This is the second official release.


Compared with 01 (2013-04-28) of V100R008C00, 02 (2013-06-27) does not add any
information.

Compared with 01 (2013-04-28) of V100R008C00, 02 (2013-06-27) includes the following


changes.

Topic Change History

RAN Sharing MOM Description Changed the name eRAN sharing to RAN sharing, which is
consonant with FPD document.

No information in 01 (2013-04-28) of V100R008C00 is deleted from 02 (2013-06-27).

01 (2013-04-28)

This is the first official release.


Compared with Draft A (2013-2-20) of V100R008C00, 01 (2013-04-28) does not add any
information.
Compared with Draft A (2013-2-20) of V100R008C00, 01 (2013-04-28) does not include any
changes.
No information in Draft A (2013-2-20) of V100R008C00 is deleted from 01 (2013-04-28).

Draft A (2013-2-20)

This is the draft.

5.7.1.2 MOM User Guide


MOM user guide describes managed object models (MOMs) and provides MO configuration
methods.

Overview of MO Models
MOMs comprise the user-oriented management view of system resources. Users can add,
remove, or modify MOs to manage the eNodeB.

MO Attributes
MO attributes, namely, the parameters of the MO. These attributes can be used to configure the
MO.

MO Operations
MO operations are performed to add, remove, modify, and query MOs on an MML client or on
the CME. These operations are described as follows:

Relationships Between MOs


Relationships between MOs are classified into association ,aggregation, composition and
inheritance.

Effective Scenarios
The effective scenario indicates the scenario in which an MO takes effect. The effective scenario
can be after the reset or immediately.

Parent topic: eNodeB MO Reference

5.7.1.2.1 Overview of MO Models


MOMs comprise the user-oriented management view of system resources. Users can add,
remove, or modify MOs to manage the eNodeB.
In the eNodeB, MO stands for a kind of resources, which can be physical entities such as RET,
or logical entities or protocols such as UtranNCell. The entities are associated by parameters.
Users can configure a MO by setting its parameters, and the MO status can be presented by its
parameters.
Parent topic: MOM User Guide

5.7.1.2.2 MO Attributes
MO attributes, namely, the parameters of the MO. These attributes can be used to configure the
MO.

Data Types
The data types of MO attributes can be categorized into basic data types and customized data
types.

Parameter Attributes
Parameter attributes provide users with information that facilitates parameter setting. For details
about the parameter attributes, see parameter reference.

Parent topic: MOM User Guide

5.7.1.2.2.1 Data Types


The data types of MO attributes can be categorized into basic data types and customized data
types.

Basic Data Types

Basic data types are usually used to describe the MO attributes. Table 1 describes basic data types.

Table 1 Basic Data Types

Value Type Example

Interval Type 0 to 31

Compound Type 23333/12/31,02:02:02.02,-1:2

Character String Type NodeB1


NOTE:
The value of a string or password parameter can neither contain the symbols <
> ! ? \ / : ; , = + % * " ' | nor contain the following key characters: two or more %
symbols or spaces, +++ (start character of an MML message), or ---END (end
Table 1 Basic Data Types

Value Type Example

character of an MML message).

Bit Field Type INTER_RAT_CS_OUT_SWITCH

IP Address Type IPV4: 10.10.1.1


IPV6: 031:0000:130F:0000:0000:09C0:876A:130B

Customized Data Types

Customized data types refer to the enumerable values of the LTE MOs.
Based on the definition of the indicators of each value, a sequential collection is defined. The
sequence of these values and the indicators in the enumerable type description are consistent.
Thus, this type of data collection is called enumerable values. The format is (Indicator 1, ...,
Indicator n).
Example: GSM_dcs1800(dcs1800), GSM_pcs1900(pcs1900)

Parent topic: MO Attributes

5.7.1.2.2.2 Parameter Attributes


Parameter attributes provide users with information that facilitates parameter setting. For details
about the parameter attributes, see parameter reference.
Table 1 describes the attributes of each parameter.

Table 1 Parameter attribute description

Parameter Attribute Description

MO Managed object of NE

Parameter ID Simple string for identifying a parameter

Parameter Name Name of the parameter

NE NEs on which the parameter is set


Table 1 Parameter attribute description

Parameter Attribute Description

MML Command Man Machine Language (MML) command related to the parameter

Meaning Definition, purpose, and protocols of the parameter

IsKey Whether the parameter is used to identify an MO instance.

Mandatory Whether the parameter is mandatory for creating an MO instance.

Dynamic Attribute Whether the parameter is dynamic for an MO.


If the parameter is not dynamic, it can be added, modified, or removed; if
the parameter is dynamic, it cannot.

Feature ID ID of the feature that uses the parameter

Feature Name Name of the feature that uses the parameter

Value Type Parameter value type

GUI Value Range Parameter value range displayed on the GUI

Enumeration Number/Bit Enumeration number corresponding to the GUI value of a parameter of the
enumeration type, or bit position corresponding to the GUI value of a
parameter of the bit field type.

Unit Unit for the GUI Value Range

Actual Value Range Actual parameter value range corresponding to the GUI Value Range

Default Value Initial parameter value assigned by the system.


There is no default value for a mandatory parameter.
None indicates that there is no default value.
For a bit field parameter, the value ON of a sub-parameter means that the bit
representing the sub-parameter is set to 1, and the value OFF means that the
bit is set to 0.
Generally, it is displayed on the configuration window of an ADD command
but not displayed on the configuration window of a MOD/RMV/DSP/LST
command.

Recommended Value Parameter values recommended for different scenarios

Initial Value Setting Source for the initial configuration of a parameter. The initial value source
Source can be:
Table 1 Parameter attribute description

Parameter Attribute Description

Radio planning (Internal planning): The parameter value comes from the
radio network plan, facilitating resource management on the NE.
Radio planning (Negotiation with the peer): The parameter value comes
from the radio network plan. The NE negotiates this value with the peer
device to ensure successful interworking.
Transport planning (Internal planning): The parameter value comes from the
transport network plan, facilitating resource management on the NE.
Transport planning (Negotiation with the peer): The parameter value comes
from the transport network plan. The NE negotiates this value with the peer
device to ensure successful interworking.
Equipment planning: The initial value of the parameter comes from
equipment plan.
Engineering design: The initial value of the parameter comes from function
design.
Default/recommended value: The initial value uses the default or
recommended value, where the recommended value is preferential. The
default/recommended value can be used in most scenarios and adjusted for a
specific scenario.
Not involved: The initial value of the parameter is not required.

Impact Parameter impact scope

Parameter Relationship Relationship with other parameters. For example, to use this parameter, you
need to set related switches and parameters.

Access Whether this parameter is Read & Write or Read Only.


If a parameter is not dynamic and is read only, it can be set only when the
MO is created and cannot be modified later.
To modify the parameter, you must delete the MO first and then create it
again.

Service Interrupted After Whether modifying the parameter value interrupts the ongoing services.
Modification

Interruption Scope Possible interruption scope

Interruption Duration Possible interruption duration (unit: minute)


(min)

Caution Cautions to be taken during the modification

Validation of How this parameter takes effect and whether the equipment needs to be
Table 1 Parameter attribute description

Parameter Attribute Description

Modification restarted after the modification.

Impact on Radio Network Impact of the parameter on radio network performance


Performance

Introduced in Version Product version in which the parameter is introduced

Attribute Whether the parameter is a radio parameter, a transport parameter, or an


equipment parameter.

Parent topic: MO Attributes

5.7.1.2.3 MO Operations
MO operations are performed to add, remove, modify, and query MOs on an MML client or on
the CME. These operations are described as follows:

ADD + MO name: is used to add an MO. Before executing this command, ensure that the
mandatory parameters are specified.
RMV + MO name: is used to remove an MO.
MOD + MO name: is used to modify the MO attributes.
LST + MO name: is used to list the static information about an MO.
DSP + MO name: is used to list the dynamic information about an MO.

NOTE:
For details about MO operations, see the description about the related MML commands to each MO in the eNodeB
MO Reference.

Parent topic: MOM User Guide

5.7.1.2.4 Relationships Between MOs


Relationships between MOs are classified into association ,aggregation, composition and
inheritance.

Association

Association is denoted by a line connecting two MO classes. At both ends of a line, an integer or
a value range indicates the number of MOs in the MO class. The value range is expressed by
n..m, where n and m are integers and m is greater than or equal to n.
A solid line without arrows denotes a bidirectional link, whereas a solid line with an arrow
denotes a unidirectional link. For a link with the direction from A to B, one or more attributes in
MO class A uniquely identify a B MO.
Figure 1 shows the link between a TMA MO and an RRU MO.
Figure 1 Example of an association

Aggregation and Composition

Aggregation is a whole-part relationship between MO classes in which the MO classes are


aggregated. Before a child class is added, the parent class must be added. Before a parent class is
removed, all the child classes in it must be removed.
Composition is a whole-part relationship between MO classes in which one MO class is
composed of other MO classes. When a parent class is added, all the child classes in it are
automatically added. When a parent class is removed, all the child classes are automatically
removed. Child classes cannot be added or removed. Only attribute modifications are allowed for
them.
In a sequence diagram in Unified Modeling Language (UML), hollow and filled diamonds
indicate aggregation and composition respectively on the parent class side.
Figure 2 shows aggregation and composition.
Figure 2 Aggregation and composition

Figure 3 shows the aggregation between a PMU MO and a Battery MO.


Figure 3 Example of aggregation

Figure 4 shows the composition between an EMU MO, an OutPort MO, and an AlmPort MO.
Figure 4 Example of composition

Inheritance

Inheritance can be further categorized into base class and child class.
Base classes, abstracted from child classes, have the common attributes of the child classes.
Child classes have all the attributes of base classes. In addition, child classes also have their own
characteristics.
Figure 5 shows the inheritance between a RET MO and an ALD MO.
Figure 5 Example of association

Parent topic: MOM User Guide


5.7.1.2.5 Effective Scenarios
The effective scenario indicates the scenario in which an MO takes effect. The effective scenario
can be after the reset or immediately.

After the reset: indicates that the eNodeB needs to be reset after the addition or removal
of an MO. Otherwise, the addition or removal of the MO does not take effect.
Immediately: indicates that the addition or removal of an MO takes effect immediately. A
reset in the system, such as a cell reset or board reset, is not required.

Parent topic: MOM User Guide

5.7.1.3 Equipment MOM

5.7.1.3.1 BBU MOM Description


This section describes the functions and concepts of baseband units (BBUs). It also illustrates
managed object models (MOMs) and describes the corresponding managed objects (MOs).

Functions and Concepts

A BBU is a baseband processing unit, which can be configured with the following boards:
LMPT/UMPT: LTE main processing and transmission unit/universal main processing and
transmission unit
LBBP: LTE baseband processing unit
UTRP: universal transmission processing unit
USCU: universal satellite card and clock unit
UCIU: Universal inter-Connection Infrastructure Unit
UPEU: universal power and environment interface unit
UEIU: universal environment interface unit
FAN: fan unit
For details about the functions of these boards, see DBS3900 Hardware Description.
Managed Object Model

Figure 1 shows the BBU MOM, which is a subset of the eNodeB MOM.
Figure 1 BBU MOM

The BBU MOs shown in Figure 1 are described as follows:


Equipment defines an equipment root object, which manages equipment-class MOs.
Cabinet defines a physical or virtual cabinet.
A physical cabinet provides various functions such as power distribution,
environment monitoring, and surge protection, depending on the cabinet type.
A virtual cabinet is a container for subracks.
Subrackdefines
the common attributes of boards and related operations. A subrack is a
board container. A subrack can be physical, for example, a BBU or RFU subrack. It can also
be virtual, for example, a PMU or RRU subrack.
defines an RFU for a macro base station. The RFU provides ports for communication
RFU
with an LBBP, and processes uplink and downlink RF signals.
PEUdefines a UPEU. This board converts -48 V DC or +24 V DC power into +12 V DC
power for other boards in the BBU. A UPEU provides the following environment monitoring
ports:
Eight EXT-ALM ports for environment monitoring.
Two MON ports for RS485 signal monitoring.
MPT defines an LMPT. This board performs the functions of main controlling, switching,
timing, and transmission.
BBPdefines an LBBP. This board processes the uplink and downlink baseband signals
and provides CPRI ports for communication with RF units.
TRP defines a UTRP. This board provides eight E1s/T1s to support IP over E1/T1
transmission.
UCIU defines a universal cascading interface unit, which connects two BBUs. It provides
channels for communication and clock signal transfer between the two BBUs, and also
provides the function of BBU topology scanning.
USCUdefines a USCU. This board has the following functions:
Provides a reference clock for the LMPT or UMPT.
Supports the Global Positioning System (GPS) or Global Navigation Satellite
System (GLONASS) satellite card.
Supports external clocks such as the Remote Global Positioning System (RGPS)
and building integrated timing supply (BITS) clocks.
BbuFan defines a FAN. This board dissipates the heat from the BBU.
UEIU defines a UEIU. This board transmits monitoring and alarm signals from external
devices to the LMPT or UMPT. A UEIU provides the following environment monitoring
ports:
Eight EXT-ALM ports for environment monitoring.
Two MON ports for RS485 signal monitoring.
SFP defines an optical or electrical module for optical-to-electrical conversion. This
module transmits signals between the RRU/RFU and other devices through optical fibers.
Information about the module is not configurable, but can be queried.
CpriPort defines a CPRI port on an RRU or RFU. This port is used to communicate with an
LBBP.

5.7.1.3.2 RF Unit MOM Description


This section describes the functions and concepts of radio frequency (RF) units, illustrates the
managed object models (MOMs) and the corresponding managed objects (MOs).

Functions and Concepts

An RF unit can be a remote radio unit (RRU) or a radio frequency unit (RFU).
An RRU is a remote RF processing unit. For details, see the related RRU hardware
description.
An RFU is an indoor RF processing unit. For details, see the related macro base station
hardware description.
An AAS is an active antenna system. An AAS consists of the active antenna management
unit (AAMU) and active antenna radio unit (AARU).
An AAMU is an active antenna management unit. The AAMU manages the
connection link between the AAS and baseband unit (BBU), and manages other boards in
the AAS.
An AARU is an active antenna radio unit. The AARU processes the common
public radio interface (CPRI) signals and the uplink and downlink baseband signals.

Managed Object Model

Figure 1 shows the RRU MOM, which is a subset of the eNodeB MOM.
Figure 1 RRU MOM
The RRU MOs shown in Figure 1 are described as follows:
Equipment defines an equipment root object, which manages equipment-class MOs.
RRU defines an RRU. The RRU provides ports for communication with an LBBP and
processes uplink and downlink RF signals.
RRUCHAIN defines CPRI links between an LBBP and RRUs. RRUs can be connected in
the form of chain or ring. Ring topologies are classified into cold- and hot-backup ring
topologies.
CpriPort defines a port for communication between an LBBP and an RRU. This port is
used to transmit user plane data and control plane data between the LBBP and the RRU.
SFP defines an optical or electrical module for optical-to-electrical conversion. This
module transmits signals between the RRU and other devices through optical fibers.
Information about the module is not configurable, but can be queried.
BBP defines an LBBP. This board processes the uplink and downlink baseband signals
and provides CPRI ports for communication with RF units.
AntennaPort defines a port for connecting an RRU and an antenna line device (ALD).
defines a port for connecting an RRU and a remote electrical tilt (RET) antenna.
RetPort
The RRU controls the RET antenna by exchanging RS485 signals.
TxBranch defines a transmit (TX) channel in an RRU.
RxBranch defines a receive (RX) channel in an RRU.

Figure 2 shows the RFU MOM, which is a subset of the eNodeB MOM.
Figure 2 RFU MOM

The RFU MOs shown in Figure 2 are described as follows:


Equipment defines an equipment root object, which manages equipment-class MOs.
Cabinet defines a physical or virtual cabinet.
A physical cabinet provides various functions such as power distribution,
environment monitoring, and surge protection, depending on the cabinet type.
A virtual cabinet is a container for subracks.
Subrack defines the common attributes of RFUs and related operations.
RFU defines an RFU for a macro base station. The RFU provides ports for communication
with an LBBP, and processes uplink and downlink RF signals.
RRUCHAIN defines CPRI links between an LBBP and RFUs. RFUs can be connected in the
form of chain or ring. Ring topologies are classified into cold- and hot-backup ring
topologies.
defines a port for communication between an LBBP and an RRU. This port is
CpriPort
used to transmit user plane data and control plane data between the LBBP and the RRU.
SFPdefines an optical or electrical module for optical-to-electrical conversion. This
module transmits signals between the RRU and other devices through optical fibers.
Information about the module is not configurable, but can be queried.
defines an LBBP. This board processes the uplink and downlink baseband signals
BBP
and provides CPRI ports for communication with RF units.
AntennaPort defines a port for connecting an RFU and an antenna line device (ALD).
TxBranch defines a transmit (TX) channel in an RFU.
RxBranch defines a receive (RX) channel in an RFU.
AAS MOM

Figure 3 shows the AAS MOM, which is a subset of the eNodeB MOM.
Figure 3 AAS MOM

The AAS MOs shown in Figure 3 are described as follows:


Equipment defines an equipment root object, which manages equipment-class MOs.
defines an active antenna system, which consists of one Active Antenna Management
AAS
Unit (AAMU) and one to three Active Antenna Radio Units (AARUs).
RRUCHAINdefines CPRI links between an LBBP and AASs. AASs can be connected in the
form of chain or ring. Ring topologies are classified into cold- and hot-backup ring
topologies.
defines a port for communication between an LBBP and an AAS. This port is
CpriPort
used to transmit user plane data and control plane data between the LBBP and the AAS.
SFP defines an optical or electrical module for optical-to-electrical conversion. This
module transmits signals between the AAS and other devices through optical fibers.
Information about the module is not configurable, but can be queried.
BBP defines an LBBP. This board processes the uplink and downlink baseband signals
and provides CPRI ports for communication with RF units.
AARU defines an AARU, which provides ports for sending and receiving baseband and RF
signals and processes the uplink and downlink baseband signals.
TxBranch defines a transmit (TX) channel in an AARU.
RxBranch defines a receive (RX) channel in an AARU.
VRET defines a virtual remote electrical tilt (RET) antenna in an AARU. The tilt of the
antenna can be adjusted through remote control.
VRETSubUnit defines a virtual RET subunit. Under this MO, users can specify connection
ports and set polarization types for these ports. All these ports have the same uplink and
downlink tilts.
VAntennaPort defines a virtual antenna port on an AARU. Each port corresponds to an RF
channel, which transmits RF signals.
AAMU defines an AAMU, which manages communication links between the AAS and
BBU and manages AARUs in the AAS.

5.7.1.3.3 ALD MOM Description


This section describes the functions and concepts of antenna line devices (ALDs). It also
provides the managed object model (MOM) view and describes the managed objects (MOs)
related to ALDs.

Functions and Concepts

ALDs consist of remote electrical tilt (RET) antennas, virtual remote tilt (RET) antennas, and
tower mounted amplifiers (TMAs).
RET

The signal coverage of an RET antenna can be changed by adjusting the tilt through remote
electrical control. The structure and classification of RET antennas are described as follows:
An RET antenna consists of a remote control unit (RCU) and some RET subunits:
The RCU is the control unit of the RET antenna.
The RET subunits are antenna devices in independent control of the RCU.
Based on the number of RET subunits, RET antennas are classified into two types:
SINGLE_RET and MULTI_RET.
An RET antenna of the SINGLE_RET type consists of only one RET subunit.
An RET antenna of the MULTI_RET type consists of multiple RET subunits.
Each subunit supports independent download of configuration files and setting of tilts.
Therefore, this type of RET antennas is considered as a set of antennas installed in a
radome.

Connections between the RET antenna and the RRU/RFU are divided into two types:
Based on control principles, the connections vary in two scenarios as follows:
An RRU converts control signals into RS485 signals, and then transfer the RS485
signals over the RS485 control port using a control cable to an RCU. In this scenario, no
Smart Bias-Tee (SBT) is required for the RET antenna. The RRU is directly connected to
the RCU using an Antenna Interface Standards Group (AISG) multi-core cable, as shown
in Figure 1.
Figure 1 Connections between the RET antenna and the RRU/RFU (1)

The internal BT of an RRU or RFU couples on-off-keying (OOK) signals and


direct current (DC) power, and then transfers the coupling signals using a feeder to an SBT
connected to the RET antenna. The SBT modulates the received signals to control signals,
converts the control signals into RS485 signals, and then transfers the RS485 signals to an
RCU. In this scenario, an SBT is required for the RET antenna, as shown in Figure 2.
The SBT can also convert remote electrical signals (control signals) received from a base
station into On-Off Keying (OOK) signals, couples the OOK signals and 12 V DC input
power, and then transfers the signals to the RET antenna using a feeder.
Figure 2 Connections between the RET antenna and the RRU/RFU (2)

Based on installation methods, the connections vary in two scenarios as follows:


In a regular scenario, the RET antenna is directly connected to the RRU/RFU, as
shown in Figure 3.
Figure 3 Regular scenario

In a daisy chain scenario, RET antennas are cascaded, and the upper-level RET
antenna (the left one in Figure 4) provides the power supply and signaling channels to the
lower-level RET antenna, as shown in Figure 4.
Figure 4 Daisy chain scenario

NOTE:
In a multi-mode base station, for example, a GSM+LTE base station, RET antennas are used on
both GSM and LTE sides. In this case, the daisy chain scenario is adopted to support the centralized
management of RET antennas on the GSM or LTE side.
In a single-mode base station, the daisy chain scenario is adopted to reduce cable connections,
simplifying the topology.
In other cases, the normal scenario is adopted.

An RET subunit implements configuration file upload, calibration, and tilt setting independently.
Loading a configuration file
A configuration file describes the relationship between the antenna drive and the RET subunit
tilt. Some RET antennas have been loaded with default configuration files before delivery. For
those without default configuration files, the RET subunits must be loaded with the correct
configuration files before calibration.
If an incorrect configuration file is loaded, the eNodeB reports ALM-26757 RET Antenna
Running Data and Configuration Mismatch.
Calibrating an RET subunit
Calibration must be performed after the RET antenna installation. During the calibration, the
antenna drive works within the allowed tilt range to ensure that RET subunits operate
normally. After an RET antenna is reset or powered off, it does not need to be calibrated
again. If an RET antenna is not calibrated, the eNodeB reports ALM-26753 RET Antenna Not
Calibrated.
Setting the tilt of an RET subunit
After the RET antenna installation, the RET subunit must be tilted based on the network
coverage. The tilt range of the RET subunit varies according to the manufacturer and model.
You can query the allowed tilt range by running the DSP RETDEVICEDATA command.

NOTE:
The RET manufacturers provide RCU software. The eNodeB supports software download and RCU reset. Resetting
the RCU clears all alarms without affecting tilt settings.

VRET
The signal coverage and coverage effect of a VRET antenna can be changed by adjusting
polarization of the virtual antenna ports on the active antenna system (AAS) and the antenna tilt
through remote electrical control.

A VRET subunit of the AAS implements the setting of virtual antenna port polarization, uplink
tilt, and downlink tilt independently.
Setting virtual antenna port polarization: After the AAS installation, the polarization of
virtual antenna ports must be set based on the network coverage.
Setting the uplink and downlink tilts of virtual antenna ports: After the AAS installation,
the virtual antenna ports of VRET subunits must be tilted based on the network coverage. The
tilt range of the virtual antenna ports varies according to the AAS type. Before setting the tilts,
you can query the allowed tilt range by referring to hardware description of corresponding
AAS type.
TMA

A TMA is a low noise amplifier installed near an antenna. It improves the signal-to-noise ratio
(SNR), sensitivity, and uplink coverage of the eNodeB. The TMA provides the following
functions:
Amplifies uplink signals to compensate for attenuation between an RET antenna and an
RRU or RFU.
Balances signal amplification between the uplink and downlink.

A TMA has one or two subunits, which can amplify one or two uplink radio frequency (RF)
signals.

NOTE:
The TMA manufacturers provide TMA software. The eNodeB supports software download and TMA reset.
Resetting the TMA clears all alarms without affecting the gain and working mode of the TMA.
The TMA sends RS485 signals to the RCU to enable the remote adjust of antenna tilt.
The TMA is connected to the RRU/RFU and RET antenna, and is powered by the RRU/RFU.
Figure 5 shows the connections of the TMA.

Figure 5 Connections of the TMA

Managed Object Model

Figure 6 shows the ALD MOM, which is a subset of the eNodeB MOM.
Figure 6 ALD MOM

The MOs shown in Figure 6 are defined as follows:


ALD is a base class. This MO defines the common attributes and operations of the RET
antenna and TMA. The common attributes describe the control ports on the RRU/RFU where
the RET antenna and TMA are connected. This MO supports reset, software download, and
scanning of the RET antenna and TMA.
TMA defines a TMA.
TMASubUnit defines a TMA subunit. The Gain parameter indicates the gain of the TMA
subunit. The tilt of each TMA subunit can be set independently. The MODE parameter indicates
the work mode of the TMASubUnit.
TMADeviceData defines additional parameters of the TMA subunit. These parameters do not
affect the running of the TMA. For details about the additional parameters, see reference
document [1].
defines an RET port on the RRU. The RET port is connected to the RET antenna for
RetPort
power supply and signaling exchange.
AntennaPortdefines an RF port on the RRU/RFU. The RF port is connected to the RET
antenna or TMA for power supply and signaling exchange. The RF port is also connected to the
RET subunit or TMA subunit, providing an RF channel to transmit RF signals.

RET defines an RET antenna.


RETSubUnit defines an RET subunit. The TILT parameter indicates the tilt of the subunit. The
tilt of each RET subunit can be set independently. This MO supports configuration file
download and tilt calibration of the RET subunit.
defines additional parameters of the RET subunit, which contains
RetDeviceData
information about the RET antenna. These parameters do not affect the running of the RET
antenna. For details about the additional parameters, see reference document [1].

Figure 7 shows the VRET MOM, which is a subset of the eNodeB MOM.
Figure 7 ALD MOM

The MOs shown in Figure 6 are defined as follows:


VRET defines a VRET antenna on the AAS.
defines a VRET subunit. Users can specify virtual antenna ports for a VRET
VRETSubUnit
subunit and set polarization for these ports. The virtual antenna ports of a VRET subunit have
the same uplink tilt and the same downlink tilt.
defines a virtual RF port on the AAS. This port provides RF channels to
VAntennaPort
transmit RF signals.

Reference Document

[1] 3GPP TS 25.466 Annex B (normative): Assigned fields for additional data

5.7.1.3.4 Electromechanical Device MOM


Description
This section describes the functions and concepts of Huawei electromechanical devices. It also
provides the managed object model (MOM) view of these devices and describes the related
managed objects (MOs).

Functions and Concepts

Huawei electromechanical devices include the cabinet control unit (CCU), power monitoring
unit (PMU), power supply unit (PSU), environment monitoring unit (EMU), fan monitoring unit
(FMU), temperature control unit (TCU), and storage batteries.
CCU
The CCU is an important component that ensures the proper operation of telecommunication
equipment. It manages other electromechanical devices such as the FMU, EMU, PMU, and
TCU.

The CCU can be configured in the following products:


BTS3900AL
TP48600A
BBS700D
For details about the CCU, see the hardware descriptions of these products.
PMU
The PMU manages the power equipment and storage batteries, monitors the power distribution,
and reports any alarms to the eNodeB.

The PMU can be configured in the following products:


APM30H
PS4890
BTS3900
TP48600A
BTS3900AL
For details about the PMU, see the hardware descriptions of these products.
PSU
The PSU converts 110 V AC, 220 V AC, or 24 V DC power into -48 V DC power.

The PSU can be configured in the following products:


APM30H
PS4890
BTS3900
TP48600A
BTS3900AL
For details about the PSU, see the hardware descriptions of these products.
EMU
The highly reliable EMU provides multiple monitoring signal input ports. It performs functions
such as real-time and remote monitoring, and supports flexible configuration and wide-range
temperature detection.

Two types of EMUs are available for the following products:


One for indoor cabinets such as the BTS3900
The other for outdoor cabinets such as the BTS3900A
For details about the EMU, see EMU User Guide.
FMU
The FMU dissipates heat from a cabinet.

The FMU can be configured in the following products:


BTS3900
BTS3900L
BTS3900AL
For details about the FMU, see the hardware descriptions of these products.
TCU
The TCU monitors and adjusts the cabinet temperature.

The TCU can be configured in the following products:


IBBS200D
IBBS300T
TMC11H
IBBS700D
TP48600A
For details about the TCU, see the hardware descriptions of these products.
Storage Battery
Storage batteries provide backup power for eNodeBs when the mains supply is shut off.

Storage batteries can be configured in the following products:


IBBS200T
IBBS200D
PS4890
IBBS700D
TP48600A
For details about storage batteries, see the hardware descriptions of these products.

Managed Object Model


Figure 1 shows the electromechanical device MOM, a subset of the eNodeB MOM.
Figure 1 Electromechanical device MOM

The MOs shown in Figure 1 are defined as follows:


is a base class. This MO defines the common attributes and operations of
RU
electromechanical devices.
EMUdefines an EMU. The EMU monitors the environment (including humidity,
temperature, water damage, and smoke) and site security (including infrared detection and
door status detection). This MO is the parent object of the OutPort and AlmPort MOs. The OutPort
and AlmPort MOs are created or removed automatically when the EMU MO is created or
removed.
defines a relay output port. The port, supported only by an EMU, is used to connect
OutPort
environment equipment. The output port enables the environment equipment to perform
functions such as refrigerating, humidifying, dehumidifying, fire extinguishing, heating, and
security monitoring.
FMU defines an FMU. The FMU dissipates heat from a cabinet.
defines a TCU. This MO is the parent object of the HtCDPa MO. The HtCDPa MO is
TCU
created automatically when the TCU MO is created.
HtCDPa defines the temperature control parameters related to TCUs that use a breathable
film.
PMU defines a PMU. The PMU monitors the voltage, current, and load of the power
system and manages storage batteries and diesel generators. Before creating the Battery or
DieselGen MO, ensure that the PMU MO has been created.
PSU defines a PSU. The PSU converts 110 V AC, 220 V AC, or 24 V DC power into -48
V DC power. The number of PSUs to be configured depends on the load capacity. PSUs are
managed by the PMU. Therefore, the CN and SRN parameters in each PSU MO must be the
same as those in the PMU MO. Before creating a PSU MO, ensure that the PMU MO has been
created.
defines storage batteries, which provide backup power for eNodeBs when the
Battery
mains power is shut off.
DieselGendefines a diesel generator, which serves as backup for the solar power system in
the solar & D.G. hybrid power system.
BatCTPadefinesthe parameters related to a battery capacity test. This MO is created
automatically when the BatCTPa MO is created.
AlmPort defines an environment signal input port, which connects to external sensors to
monitor the environment. There are two types of environment signal input ports: analog ports
and digital ports.
An analog port, supported only by an EMU, is used to monitor the changing
external environment according to the configured upper and lower measurement limits and
the limits on the current or voltage of output signals.
A digital port is used to monitor the external environment variables that are
measured in Boolean or discrete values. Digital ports can be configured on the EMU, PMU,
TCU, FMU, RRU, PEU and UEIU. The SC48200 PMU does not support environment signal
input ports.
CCUdefines a CCU, which manages other electromechanical devices such as the FMU,
EMU, PMU, TCU.

PSUIS defines a PSUIS, which is used to manage the configuration of the intelligent
shutdown switch for PSUs that supply power to the entire BS. The PSU intelligent shutdown
switch is used to shut down redundant PSUs to improve the power conversion efficiency.

5.7.1.3.5 Clock MOM Description


This section describes the functions and concepts of clocks. It also provides the managed object
model (MOM) view and describes managed objects (MOs) related to clocks.

Functions and Concepts

Roaming and handover services can be ensured only when clock synchronization is achieved
among eNodeBs in the wireless networks. To prevent interference from neighboring frequencies:
In frequency division duplex (FDD) mode, frequency synchronization must be achieved
among eNodeBs.
In time division duplex (FDD) mode, time synchronization must be achieved among
eNodeBs.
The CLK defines the eNodeB clock management module, involving the management of the
system clock and external reference clocks.
Seven reference clocks are available for an eNodeB.
GPS/RGPS

The Global Positioning System (GPS) or Remote Global Positioning System (RGPS)
synchronization requires a GPS or RGPS receiver on each eNodeB. The eNodeBs receive clock
signals through the GPS or RGPS receivers, with the precision to microseconds. GPS and RGPS
clocks support both frequency synchronization and time synchronization.
A GPS receiver connects to an eNodeB through the GPS port on an LTE main processing
and transmission unit (LMPT) or universal main processing and transmission unit (UMPT) on
the eNodeB.
An RGPS receiver connects to an eNodeB through an RGPS port on the universal
satellite card and clock unit (USCU). An eNodeB synchronized with the RGPS clock must be
equipped with the USCU.
IEEE1588 V2
IEEE1588 defines the Precision Time Protocol (PTP), which applies to standard Ethernet. High-
accuracy frequency synchronization or time synchronization between clock servers and eNodeBs
can be achieved. The IEEE1588 V2 clock is selected as the system clock of the eNodeB by
setting the ICPT parameter to PTP(PTP).
1PPS+TOD
An eNodeB implements time synchronization by obtaining 1 pulse per second (1PPS) and time
of day (TOD) signals. 1PPS signals are used for synchronization. TOD signals are used to
transmit time information, and reference clock type and working status.
Clock over IP
Clock over IP is a Huawei proprietary frequency synchronization technology, which carries
frequency synchronization packets over IP. Clock signals are distributed to each eNodeB based
on a server/client architecture. The clock over IP technology supports only frequency
synchronization, with the frequency accuracy that is better than 0.05 ppm.
BITS
An eNodeB can obtain frequency synchronization signals by connecting to the building
integrated timing supply (BITS) through the internal BITS clock card. After phase lock and
frequency division, the main clock module in the eNodeB converts the synchronization signals
into the clock signals required for the eNodeB. Synchronization with the BITS clock requires the
USCUs.
Synchronous Ethernet
Synchronous Ethernet adopts the technology that recovers clock signals from the data bit streams
in Ethernet links. The intermediate transport equipment in the synchronous Ethernet, such as
LAN switches, must be capable of transparent transmission or regeneration of clock signals at
the physical layer.
E1/T1 Line Clock
An eNodeB can extract frequency synchronization signals from E1/T1 links at the physical layer.
If the S1 interface transmits signals through E1/T1 ports, the eNodeB can synchronize with the
E1/T1 clock.

Managed Object Model

Figure 1 shows the CLK MOM, which is a subset of the eNodeB MOM.
Figure 1 CLK MOM

The CLK MOs shown in Figure 1 are described as follows:


Equipment defines the equipment root object, which manages equipment-class MOs.
Tasmdefines the system clock. This MO is automatically created by the system. The
system clock can be automatically switched among available external reference clocks based
on priorities and availability. When the Tasm MO is set, the following settings can be
performed:
eNodeB synchronization mode (time synchronization or frequency
synchronization)
Current reference clock
IP clock algorithm parameters
The status of the system clock
defines a synchronous Ethernet link. The synchronous Ethernet technology has
SyncEth
the same basic principles as the synchronous digital hierarchy (SDH) and plesiochronous
digital hierarchy (PDH) network clock synchronization, where a downstream node obtains
and traces the upstream clock by recovering clock signals from the serial data bit streams
received at the physical layer.
GPSdefines a type of reference clock source. The term GPS is a collective name for all
satellite synchronization systems, including GPS, GLONASS, and COMPASS. A satellite
card is attached to the MPT.
TOD defines a 1PPS+TOD clock link. The 1PPS+TOD clock link must be configured on
the USCUb.
defines a peer reference clock link. In a multi-mode base station (BS), the peer
PeerClk
reference clock is shared by multiple modes. Currently, only one peer reference clock link can
be configured. The cabinet number, subrack number, and slot number are not specified when
this MO is set.
LineClkdefines
an E1/T1 line clock link. The E1/T1 line clock link is generally configured
on a main control board or transmission board. The cabinet number, subrack number, and port
number are specified for the board where the E1/T1 line clock link is configured.
IPCLKLNKdefines
an IP clock link. The IP clock complies with the IEEE1588 V2 standard
and Huawei proprietary IP clock protocol.
BITSdefines
a BITS clock link. The BITS clock link must be configured on the USCU.
The CN, SRN and SNparameters in a BITS MO must be different from CN, SRN and SN in a
GPS or TOD MO.

5.7.1.4 Transport MOM

5.7.1.4.1 IPv4 MOM Description


This section describes the functions and concepts of IPv4 transmission, illustrates managed
object models (MOMs) and the corresponding managed objects (MOs).

Functions and Concepts

Figure 1shows the generic protocol stack for S1 interfaces, X2 interfaces, and OM channels in the
LTE system. On S1 and X2 interfaces, transport protocol layers are divided into the control plane
and user plane for processing signaling and user data, respectively. The control plane uses
Stream Control Transmission Protocol (SCTP) links, and the user plane uses Internet Protocol
(IP) paths.
The fundamental protocol part, control plane, and user plane provide the transport bearer service
for the application layer. For principles of transport protocol layers, see S1/X2/OM Channel
Management Feature Parameter Description.
Figure 1 Generic protocol stack for S1/X2/OM channels

Transmission on the IPv4-based MOs related to the S1/X2/OM channels can be configured in
end-point configuration mode or link configuration mode.
The link configuration mode is traditional. Users set up SCTP links and IP paths for an
S1 or X2 interface, and end point information is negotiated by both ends.
The end-point configuration mode corresponds to the two ends in link configuration
mode, for example, IP addresses. If trasnmission is configured in end-point configuration
mode, the system automatically sets up control plane bearers (SCTP links) and user plane
bearers (IP paths) for the S1 or X2 interface.

Managed Object Model

Figure 2 shows the MOM for the control plane.


Figure 2 Control plane MOM

The MOs shown in Figure 2 are described as follows:


S1, X2, EPGROUP, SCTPHOST, SCTPPEER and SCTPTEMPLATE are used in end point
configuration mode. SCTPLNK and CPBEARER are used in link configuration mode. S1Interface
and X2Interface need to reference SCTPLNK.
The S1, EPGROUP, SCTPHOST, SCTPPEER, SCTPTEMPLATE, S1Interface, CPBEARER and
SCTPLNK are classified into MOs related to an S1 SCTP link.
The X2, EPGROUP, SCTPHOST, SCTPPEER, SCTPTEMPLATE, X2Interface, CPBEARER and
SCTPLNK are classified into MOs related to an X2 SCTP link.

Figure 3 shows the MOM for the user plane.


Figure 3 User plane MOM

The MOs shown in Figure 3 are described as follows:


S1, X2, EPGROUP, USERPLANEHOST and USERPLANEPEER are used in end point
configuration mode.
eNodeBPath and IPPATH are used in link configuration mode.
The S1, EPGROUP, USERPLANEHOST, USERPLANEPEER, eNodeBPath, and IPPATH are
classified into MOs related to an S1 IP path.
The X2, EPGROUP, USERPLANEHOST, USERPLANEPEER, eNodeBPath and IPPATH related to an
X2 IP path.

NOTE:
USERPLANEHOST and USERPLANEPEER automatically set up connections on the user plane.
USERPLANEPEER can be automatically generated during the automatic neighbor relation (ANR) configuration,
and no manual operation is required.

Figure 4 shows the MOM for IPv4 transmission.


Figure 4 IPv4 Transmission MOM

Table 1 describes the MOs related to the S1, X2, and OM channels.

Table 1 IPv4-based MOs related to the S1/X2/OM channel

Protocol Configura
Layer tion Mode MO Description

Data link Both ETHPORT This MO defines an Ethernet port.


layer This MO includes parameters such as the speed,
duplex mode, port attribute, ARP proxy flag, and
maximum transmission unit (MTU).
The duplex mode and port attribute must be
negotiated with the peer device.
Table 1 IPv4-based MOs related to the S1/X2/OM channel

Protocol Configura
Layer tion Mode MO Description

ETHTRK This MO defines an Ethernet trunk. An Ethernet trunk


bundles multiple Ethernet ports into a trunk, achieving
load sharing and enhancing transmission reliability.

VLANMAP This MO is used to attach different VLAN tags to the


data packets according to their next hop IP addresses. The
mapping modes are classified into single VLAN and
VLAN group. In single VLAN mode, the next hop IP
addresses are directly mapped to the VLAN tags. In
VLAN group mode, the next hop IP addresses are
mapped to the VLAN groups and then to the VLAN tags
in the VLAN groups based on the differentiated services
code points (DSCPs) and data types of the data packets.

VLANCLASS This MO is used to map services with different VLAN


tags based on the traffic type. There are two mapping
modes. If the traffic type is user data, VLAN tags are
mapped on the basis of the DSCP. If the traffic type is not
user data, VLAN tags are mapped on the basis of the
traffic type.

DSCPMAP This MO defines the mapping between a DSCP and a


VLAN priority. If no VLAN priority is specified during
the configuration of a VLANMAP MO, the VLAN
priority is specified for user data based on mapping rules
defined in the DSCPMAP MO.

SUBNETVLAN This MO defines a subnet VLAN mapping relationship,


attaching a VLAN tag to the source or destination IP
address of a data packet. For details about the procedures
for dividing VLANs and tagging VLANs, see S1/X2/OM
Channel Management Feature Parameter Description.

Network Both DEVIP This MO defines an IP address for an IP port.


layer Before configuring this MO, ensure that the associated
ETHPORT MO is configured. This MO can configure
the following IP addresses:
Device IP address used by the SCTP link or IP
path on an S1 or X2 interface.
Device IP address of the OM channel.

IPRT This MO defines a static IP route. After this MO


Table 1 IPv4-based MOs related to the S1/X2/OM channel

Protocol Configura
Layer tion Mode MO Description

is configured, data can be forwarded based on a


routing table.
IP routes used for the control plane and user
plane on an S1 or X2 interface are IP routes to peer
devices.
For the configuration of an S1 or X2 interface, IP
routes are required only when an eNodeB is connected
to the EPC or another eNodeB through a layer 3
network.
For the configuration of an OM channel, IP
routes are required when an eNodeB is connected to
the M2000 through a layer 3 network. IP routes are
also required if route binding is disabled for the OM
channel.

RSCGRP This MO defines a transport resource group. If there are


no forwarded data streams, you do not need to add an
RSCGRP MO.

Transport Link SCTPLNK This MO defines an SCTP link for the control plane of an
layer and configuration S1 or X2 interface.
application
layer CPBEARER This MO specifies bearers for the control ports on the
application layer, including the S1 interface and X2
interface.

S1Interface This MO specifies an SCTP link to enable it to carry an


S1 interface and also specifies the operator owning the
interface.

X2Interface This MO specifies an SCTP link to enable it to carry an


X2 interface and also specifies the operator owning the
interface.

IPPATH This MO defines an IP path for the user plane of


an S1 or X2 interface.
If an IP path needs to be added to a user-defined
transport resource group, set the RSCGRPID parameter
in the IPPATH MO to the value of the RSCGRPID
parameter in the RSCGRP MO.

eNodeBPath This MO specifies the application type of an IP path.


Table 1 IPv4-based MOs related to the S1/X2/OM channel

Protocol Configura
Layer tion Mode MO Description

End point EPGROUP This MO specifies resources in transport nodes, including


configuration resources on the control plane or user plane, or both.
mode
SCTPHOST This MO specifies information of the local end of the
SCTP link. On the control plane, the SCTP link between
the local end and peer end is automatically set up. One
local IP address of the SCTP link connects to only one
security local end. When the self-setup function is
enabled in the local end of the SCTP link, security MOs
must be configured in the local end.

SCTPPEER This MO specifies information of the peer end of the


SCTP link. In X2 self-setup scenarios, this MO can be
automatically generated. In other scenarios, you must
manually configure this MO. In scenarios with the
SeGW, if the IPSec address is configured for this MO, the
IPSec negotiation between the local end and the MO is
automatically set up.

USERPLANEHO This MO specifies information of the local end on the


ST user plane. On the user plane, the radio bearers between
the local end and peer end are automatically set up. The
local end and peer end on the user plane can be manually
configured or automatically generated.

USERPLANEPEE This MO specifies information of the peer end on the


R user plane. This MO can be manually configured or
automatically generated.

Both OMCH This MO defines a remote maintenance channel.

NOTE:
1. If only one OM channel is required, configure only the primary OM channel. If primary and secondary OM
channels are required, configure a primary OM channel and a secondary OM channel. In this case, the eNodeB
selects the primary OM channel preferentially. If the primary OM channel is faulty, the eNodeB switches to the
secondary one. The primary/secondary role of an OM channel is specified by the FLAG parameter. For details
about primary and secondary OM channels, see S1/X2/OM Channel Management Feature Parameter
Description.
2. MOs related to VLANs should be configured on VLAN networking.
5.7.1.4.2 IPv6 MOM Description
This section describes the functions and concepts of IP version 6 (IPv6). It illustrates the IPv6-
related managed object models (MOMs) and managed objects (MOs).

Functions and Concepts

IPv4 has a limited number of available IP addresses. IPv6, an improved IP version, has been
introduced to solve the problem of IP address exhaustion.

IPv4/IPv6 dual stack is a technique that supports both IPv4 and IPv6. This technique is used
during an IPv4-to-IPv6 transition. A node that supports IPv4/IPv6 dual stack is called a dual-
stack node. Dual-stack nodes can work in one of the following modes:
IPv6-only mode
IPv4-only mode
IPv4/IPv6 dual-stack mode
The eNodeB type determines MO configurations. If an eNodeB functions as:
an IPv6 node, only IPv6-related MOs need to be configured.
an IPv4 node, only IPv4-related MOs need to be configured.
a dual-stack node, both IPv4- and IPv6-related MOs must be configured.
The MOs related to IPv6-based S1 and X2 interfaces and operation and maintenance (OM)
channels for eNodeBs are different from those related to IPv4-based S1 and X2 interfaces and
OM channels. This document describes IPv6-specific MOs. For details about IPv4-specific MOs
and MOs shared by IPv4 and IPv6, see IPv4 MOM Description and Transmission Maintenance and
Detection MOM Description.

Managed Object Model

Figure 1 shows the IPv6-based S1/X2/OM channel MOM, a subset of the eNodeB MOM.
Figure 1 IPv6-based S1/X2/OM channel MOM

NOTE:
InFigure 1, the MOs in gray are IPv6-specific MOs, and the MOs in white are shared by IPv4 and IPv6.

IPv6-based S1/X2/OM channel MOs are defined as follows:


PMTUCFG defines the global path MTU (PMTU) detection configurations, including the
detection mode, User Datagram Protocol (UDP) port number, detection period, PTMU aging
period, and differentiated services code point (DSCP).
IPRT6defines an IPv6 static route. An associated IPITF6MO must be created before an
IPRT6 MO. The ITFIDX parameter in the IPRT6 MO must be already configured in the IPITF6
MO.
IPITF6 defines an IPv6 interface. It includes the cabinet number, subrack number, slot
number, port number, and interface type. This MO is also used to configure the virtual local
area network (VLAN) where an Ethernet port is located. The ITFIDX parameter specifies an
IPv6 interface.
DEVIP6 defines an IPv6 address for an Ethernet port. The IPv6 address must be a global
unicast address or link-local address. An associated IPITF6 MO must be created before a
DEVIP6 MO. The ITFIDX parameter in the DEVIP6 MO must be already configured in the IPITF6
MO.
OMCH6 defines an IPv6-based remote OM channel between an eNodeB and an M2000.
This MO configures IPv6 addresses for the eNodeB and M2000. An associated DEVIP6 MO
must be created before an OMCH6 MO. The LOCALIP6 parameter in the OMCH6 MO must be
already configured in the DEVIP6 MO.
SCTPLNK6 The MO is used to set parameters of IPv6 packets based on the Stream Control
Transmission Protocol (SCTP). The SCTP link carries signaling, complying with the SCTP.
IPPATH6 This MO defines an IPv6 service transmission channel between the BS and other
NEs. The channel is used to differentiate IPv6 transmission services through parameters such
as IPv6 addresses of both ends of the channel and service quality.

NOTE:
The definition of the other MOs listed in Table 1, seeIPv4 MOM Description.

The MOs configured for the S1/X2/OM channel vary depending on whether an eNodeB
functions as an IPv4 or IPv6 node. Table 1 describes the differences between IPv4- and IPv6-
related MOs for the S1/X2/OM channel.

Table 1 Differences between IPv4- and IPv6-related MOs for the S1/X2/OM channel

Protoc
ol Configuratio
Layer n Mode IPv4 MO IPv6 MO Description

Data End point and ETHPORT ETHPORT These MOs is shared by IPv4 and IPv6.
link link
layer ETHTRK ETHTRK

VLANMAP IPITF6 VLAN configurations for an eNodeB that


functions as an IPv4 node are different from
VLANCLASS NA those for an eNodeB that functions as an IPv6
node.
DSCPMAP NA A VLAN is configured by using the
VLANMAP, DSCPMAP, SUBNETVLAN
SUBNETVLA SUBNETVL
and VLANCLASS MOs when an eNodeB
N AN
functions as an IPv4 node.
A VLAN is configured by using the
IPITF6 and SUBNETVLAN MOs when
an eNodeB functions as an IPv6 node.

Network End point and DEVIP DEVIP6 The device IP address is an IP address of an
layer link Ethernet port on an LTE main processing and
transmission unit (LMPT).

IPRT IPRT6 The IP route is a route from an Ethernet port


on an LMPT to a destination address.
Table 1 Differences between IPv4- and IPv6-related MOs for the S1/X2/OM channel

Protoc
ol Configuratio
Layer n Mode IPv4 MO IPv6 MO Description

RSCGRP RSCGRP This MO defines a transport resource group.


If there are no forwarded data streams, you do
not need to add an RSCGRP MO.

Transpo Link (for S1 and SCTPLNK SCTPLNK6 An IPv4 address is used in the SCTPLNK
rt layer X2 interfaces) MO, and an IPv6 address is used in the
and SCTPLNK6 MO.
applicati
on layer S1Interface S1Interface This MO is shared by IPv4 and IPv6.

X2Interface X2Interface

eNodeBPath eNodeBPath

IPPATH IPPATH6 An IPv4 address is used in the IPPATH MO,


and an IPv6 address is used in the IPPATH6
MO.

End point (for S1 S1 These MOs define end point information


S1 interfaces) about local and peer ends when S1 signaling
EPGROUP EPGROUP links and local links are configured in end
point mode, and these MOs are shared by
SCTPHOST SCTPHOST IPv4 and IPv6.
SCTPPEER SCTPPEER

SCTPTEMPL SCTPTEMP
ATE LATE

End point (for X2 X2 These MOs define end point information


X2 interfaces) about local and peer ends when X2 signaling
EPGROUP EPGROUP links and local links are configured in end
point mode, and these MOs are shared by
SCTPHOST SCTPHOST IPv4 and IPv6.
SCTPPEER SCTPPEER

SCTPTEMPL SCTPTEMP
ATE LATE

End point and OMCH OMCH6 The OMCH or OMCH6 MO defines an OM


link channel between an eNodeB and an M2000.
5.7.1.4.3 Transmission Security MOM Description
This section describes the functions and concepts of IP Security (IPSec) and packet filtering in
transmission security. It illustrates the managed object model (MOM) of and managed objects
(MOs) related to transmission security.

Functions and Concepts

IPSec

IPSec is a security scheme that operators define security policies around. A security policy
specifies a type of packets that need to be protected and how they should be protected. By
sharing security policies, the E-UTRAN NodeB (eNodeB) can communicate with the peer in
secure mode. Concepts related to IPSec are described as follows:
ACL and ACL rule
An access control list (ACL) rule defines a type of IP packets that need to be
protected. The eNodeB determines packets to be protected according to ACL rules.
For easy management, ACL rules are arranged into ACLs. One ACL may contain
multiple ACL rules.
IPSec policy and IPSec SA
An IPSec policy specifies the protection mechanism that should be used to protect
a type of packets.
The eNodeB shares an IPSec policy with the peer by establishing an IPSec
security association (SA) during an Internet Key Exchange (IKE) negotiation. An IPSec
SA is a logical connection and it has a lifetime.
IKE
IKE is a protocol used by the local and peer ends to establish SAs and perform identity
authentication.
IKE SAs support two status detection mechanisms: keep-alive detection and dead
peer detection (DPD). In keep-alive detection, detection messages are sent periodically. In
DPD, detection messages are sent only when there is no IPSec traffic. If an eNodeB is
configured with both keep-alive detection and DPD, only keep-alive detection takes effect.
There are two methods used to authenticate a peer's identity: digital-certificate-
based authentication and PSK-based authentication. PSK is short for preshared key. For
details about digital-certificate-based authentication, see PKI MOM Description. PKI is short
for public key infrastructure. For details about PSK authentication, see Transmission
Security Feature Parameter Description.
Packet Filtering
Packet filtering is a process in which the eNodeB accepts or discards packets according to ACL
rules. This prevents unauthorized users from accessing the eNodeB.

Both IPSec and packet filtering use ACL rules, but for different purposes.
In IPSec, ACL rules are used to determine whether outgoing packets are allowed to enter
the IPSec tunnel. Only the packets allowed to enter the IPSec tunnel are encrypted.
In packet filtering, ACL rules are used to determine whether packets are allowed to
access or exit the eNodeB. If they are not allowed to access or exit the eNodeB, the eNodeB
discards them.
IP Attack Defense Policy

An IP attack defense policy specifies the global configuration related to Address Resolution
Protocol (ARP) spoofing, strict ARP learning, and illegal packet detection:
In ARP spoofing, an attacker maliciously tampers the ARP table on equipment using APR
spoofing packets, and user packets cannot be forwarded.
In strict ARP learning, an eNodeB learns only the ARP request packets sent by itself and
the ARP response packets sent by the peer end.
Illegal packets refer to the packets filtered out in packet filtering.

Managed Object Model

Figure 1 and Figure 2 show the IPv4 and IPv6 transmission security MOMs, respectively.
Figure 1 IPv4 transmission security MOM
Figure 2 IPv6 transmission security MOM

Setting up an IPSec tunnel involves the following MOs, as shown in Figure 3:


MOs related to ACL: ACL/ACL6 and ACLRULE/ACLRULE6.
MOs related to IKE: IKEPROPOSAL, IKEPEER/IKEPEER6, and IKECFG.
MOs related to IPSec SA: IPSECPROPOSAL, IPSECPOLICY/IPSECPOLICY6,
IPSECBIND/IPSECBIND6, and IPSECDTNL

NOTE:
Each slash (/) denotes "or" in the preceding list.
Figure 3 Relationships among MOs related to IPSec

ETHPORT defines an Ethernet port. In this MO, you can set the rate, duplex mode, port attribute,
Address Resolution Protocol (ARP) proxy, and maximum transmission unit. You can also query
the statistics of received and transmitted packets and loopback status. In these parameters, the
duplex mode and port attribute depend on the negotiation with the peer end.
MOs Related to IEEE 802.1X-based Access Control

The details about MOs related to IEEE 802.1X-based access control are as follows:
DOT1X defines the parameters for eNodeB authentication based on IEEE 802.1X. When
an eNodeB accesses a network, IEEE 802.1X-based access control is performed based on the
configured parameters if the network supports IEEE 802.1X protocols.
MOs Related to IPSec

MOs related to ACL define the types of packets that need to be protected. The details are as
follows:
ACLRULE or ACLRULE6 defines an ACL rule for IPv4 or IPv6 transmission, respectively.
Each MO determines a type of packets that need to be protected.
ACL or ACL6 defines an ACL for IPv4 or IPv6 transmission, respectively. An ACL contains
one or multiple ACL rules.

MOs related to IKE define the local eNodeB parameters, interconnection parameters, and
algorithms for IKE interactions. The details are as follows:
IKECFG defines the local eNodeB parameters used in IKE interactions.
IKEPROPOSAL defines an IKE proposal. This MO includes the algorithms used in IKE
interactions.
IKEPEER or IKEPEER6 defines an IKE peer for IPv4 or IPv6 transmission, respectively.
Each MO includes the interconnection parameters between the local eNodeB and the IKE
peer in IKE interactions.

MOs related to IPSec SA define the ACL index, IKE peer index, and IPSec proposal index for an
IPSec tunnel, and the physical port on which a group of IPSec policies take effect. The details are
as follows:
IPSECPROPOSAL defines an IPSec proposal. This MO includes the encapsulation mode,
authentication algorithm, and encryption algorithm used in IPSec interactions.
IPSECPOLICY or IPSECPOLICY6 defines an IPSec policy for IPv4 or IPv6 transmission,
respectively. An IPSec policy specifies the protection mechanism that should be used to
protect a type of packets. Each MO includes an ACL ID, IPSec proposal name, and IKE peer
name, The ACLID, PROPNAME and PEERNAME PEERNAME parameters are used to associate an
IPSec policy with the specified ACL, IPSec proposal, and IKE peer, respectively. The ACL,
IPSec proposal, and IKE peer must be configured before the IPSec policy can be added.
IPSECBIND or IPSECBIND6 defines a binding relationship between an IPSec policy group
and a physical port. Each MO specifies the physical port where an IPSec policy group is to be
used.
IPSECDTNL specifies the IPSec policies and bidirectional forwarding detection (BFD)
sessions for the primary and secondary tunnels in an IPSec tunnel pair. An IPSec tunnel pair
consists of two IPSec tunnels between the eNodeB and SeGWs. The tunnel pair enhances
reliability of secure transmission between the eNodeB and the evolved packet core (EPC), the
M2000, or clock servers. If an IPSec tunnel becomes faulty and the other tunnel works
normally, the eNodeB automatically switches to the normal tunnel to continue secure
transmission with the EPC, the M2000, or the clock servers.
MOs Related to Packet Filtering

MOs related to packet filtering are ACL, ACL6, ACLRULE, ACLRULE6, and
PACKETFILTER.
ACLRULE or ACLRULE6 defines an ACL rule for IPv4 or IPv6 transmission, respectively.
Each MO determines a type of packets that need to be protected.
ACL or ACL6 defines an ACL for IPv4 or IPv6 transmission, respectively. An ACL contains
one or multiple ACL rules.
PACKETFILTER defines an IP packet filtering policy. The eNodeB obtains the header
information about the packets received or to be transmitted, compares the information with
the preset ACL rules, and then forwards or discards the packets according to the packet
filtering policy. The header information includes the upper-layer protocol number, the source
and destination addresses of each packet, and the source and destination ports of each packet.
IP Attack Defense Policy

MO related to IP Attack Defense Policy defines is IPGUARD.


IPGUARD specifies the attack defense policies used at the Media Access Control (MAC)
and IP layers, attack alarm switches, and attack alarm thresholds.
FLOODDEFEND defines the parameters for flood attack defense. It also defines the related
alarm switch and threshold. If the local end receives excessive flood packets from the peer
end, the local end will spend a large amount of resources processing these packets and
therefore cannot provide user services normally.
PINGFILTER defines a ping filter. If the ping filtering mode is set to whitelist mode, the
network segment or hosts specified by this MO can ping the local eNodeB. If the ping
filtering mode is set to whitelist mode, the network segment or hosts specified by this MO
cannot ping the local eNodeB. You can set the ping filtering mode by running the SET
PINGFILTERMODE command.

5.7.1.4.4 Transmission Maintenance and Detection


MOM Description
This section describes the functions and concepts of point-to-point and end-to-end transmission
maintenance and detection. It illustrates managed object models (MOMs) and explains managed
objects (MOs) to the transmission maintenance and detection.

Functions and Concepts

Huawei eNodeBs support point-to-point and end-to-end transmission maintenance and detection.
In point-to-point mode, two network elements (NEs) are directly connected. The eNodeB
supports the following point-to-point maintenance and detection functions:
Ethernet OAM (IEEE 802.3ah). OAM is short for operation, administration and
maintenance.
Single-hop Bidirectional Forwarding Detection (BFD) sessions with the CATLOG
parameter set to MAINTENANCE(Maintenance). This function is used between the
eNodeB and transmission equipment for fault detection at layer 2.
In end-to-end mode, two NEs are connected through one or more NEs. The eNodeB
supports the following end-to-end maintenance and detection functions:
Ethernet OAM (IEEE 802.1ag,Y.1731).
Multi-hop BFD sessions with the CATLOG parameter set to
MAINTENANCE(Maintenance). This function is used between the following NEs for
fault detection at layer 3: eNodeB and eNodeB; eNodeB and serving gateway (S-GW);
eNodeB and remote transmission equipment.
For details, see S1/X2/OM Channel Management Feature Parameter Description.

Managed Object Model

Figure 1 shows the MOM for the transport protocol layers. This MOM is a subset of the eNodeB
MOM.
Figure 1 MOM for the transport protocol layers

MOs related to the maintenance and detection functions shown in Figure 1 are as follows:
The MO related to Ethernet OAM (IEEE 802.3ah) is ETHOAM3AH.
MOs related to Ethernet OAM (IEEE 802.1ag,Y.1731) are CFMMEP, CFMMA,
CFMMD, CFMRMEP and CFMBNDIP.
MOs related to BFD sessions are IPRT and BFDSESSION.

Figure 2 shows the relationships between MOs related to Ethernet OAM (IEEE 802.1ag).
Figure 2 Relationships between MOs related to Ethernet OAM (IEEE 802.1ag)

A maintenance association (MA) for connectivity fault management (CFM) includes a


maintenance association end point (MEP) and multiple remote maintenance association end
points (RMEPs). Route interlock can be implemented by binding an IP address to an RMEP. A
maintenance domain (MD) for the CFM consists of one or multiple MAs.

MOs Related to Point-to-Point Maintenance and Detection


The following describes the MOs related to point-to-point maintenance and detection, which
involves Ethernet OAM (IEEE 802.3ah) and single-hop BFD sessions.

MOs for the data link layer are defined as follows:


ETHPORT defines an Ethernet port. This MO includes parameters such as the speed,
duplex mode, port attribute, Address Resolution Protocol (ARP) proxy flag, and maximum
transmission unit (MTU). It also includes information about the statistics of received and
transmitted packets and loopback status. The duplex mode and port attribute must be
negotiated with the peer device.
ETHOAM3AH is configured to support link monitoring, fault detection, and remote
loopback as defined in IEEE 802.3ah.

The MO for the network layer is defined as follows:


IPRT defines a static IP route, which is used for data forwarding through a route table.
This MO does not need to be configured if BFD sessions are used for point-to-point
maintenance and detection at layer 2. It is configured only if BFD sessions are used for
maintenance and detection at layer 3.

The MO for the transport and application layers is defined as follows:


BFDSESSION consists of parameters related to a BFD session, which is used to quickly
detect faults on a channel between links. Single-hop BFD sessions are used for point-to-point
maintenance and detection at layer 2.
MOs Related to End-to-End Maintenance and Detection
The following describes the MOs related to end-to-end maintenance and detection: Ethernet
OAM (IEEE 802.1ag, and Y.1731) and multi-hop BFD sessions.

MOs for the data link layer are defined as follows:


ETHPORT defines an Ethernet port. This MO includes parameters such as the speed,
duplex mode, port attribute, Address Resolution Protocol (ARP) proxy flag, and maximum
transmission unit (MTU). It also includes information about the statistics of received and
transmitted packets and loopback status. The duplex mode and port attribute must be
negotiated with the peer device.
CFMMD defines an MD for CFM in an Ethernet network. The boundary of each MD is
defined by MEPs on ports. Each MD is identified by an MD name. A CFM MD can be
composed of multiple MAs.
CFMMA defines an MA, which is a collection of maintenance points in an MD. Each MA
is identified by an MD name and MA name.
CFMMEP defines the local MEP and CFMRMEP defines an RMEP. The local MEP and
RMEPs together define the scope and boundary of an MD. The MD and MA to which the
local MEP belongs determine the VLAN ID and VLAN priority of the virtual local area
network (VLAN) through which packets are sent.
CFMBNDIP defines the binding relationship between an RMEP and an IP address. This MO
helps achieve route interlock for the RMEP.

The MO for the network layer is defined as follows:


IPRT defines a static IP route, which is used for data forwarding through a route table.
This MO does not need to be configured if BFD sessions are used for point-to-point
maintenance and detection at layer 2. It is configured only if BFD sessions are used for
maintenance and detection at layer 3.

The MO for the transport and application layers is defined as follows:


BFDSESSION consists of parameters related to a BFD session, which is used to quickly
detect faults on a channel between links. Multi-hop BFD sessions are used for end-to-end
maintenance and detection at layer 3.

NOTE:
IPv6 protocol does not include MO BFDSESSION.

5.7.1.4.5 Transport Resource Management MOM


Description
This document describes the functions and concepts related to transport resource management
algorithms. It illustrates managed object models (MOMs) and describes the corresponding
managed objects (MOs).

Functions and Concepts

QoS in network communications is a mechanism that guarantees a certain level of performance


in packet loss rate, delay, jitter, and bandwidth. To meet different requirements, QoS provides
different service qualities and manages transport resources based on transport resource
management algorithms.
Transport resource management algorithms are used to manage transport resources in the E-
UTRAN based on transmission requirements.

The algorithms are classified into:


Transport resource configurations and mapping
Transport load control
Transport congestion control
The radio resource management (RRM) algorithms that are closely related to the transport
resource management algorithms include radio resource scheduling and mobility load balancing
(MLB). The transport resource management policies need to be consistent with the RRM policies
to the greatest extent. Figure 1 shows the categories of transport resource management algorithms.
Figure 1 Categories of transport resource management algorithms

IP PM: IP Performance Monitoring SAE: System Architecture Evolution

TRM: Transport Resource Management UE: User Equipment

RRM: Radio Resource Management

For details about Transport Resource Management are as follows:


Transport Resource Configurations and Mapping

Transport Resource Configurations and Mapping involves the following functions:


Transport resources include physical ports, transport resource groups, and IP
paths. By properly configuring these transport resources, users can achieve more accurate
management on bandwidths.
This mechanism implements differentiated transmission by mapping traffic types
to differentiated service code points (DSCPs) based on transmission requirements (for
example, requirements for delay, jitter, and packet loss rate).
Transport Load Control
Transport load control applies when transport resources are limited. It aims to:
Provide Differentiated Services (DiffServ).
Ensure fairness among users.
Improve transport bandwidth efficiency and network capacity while not affecting
service quality.
Transport load control involves the following functions:
Transport admission control: Services are admitted based on the transport load.
By allocating transport resources to UEs, the eNodeB manages transport bandwidth and
controls the loads on transport bandwidth.
Transport resource preemption: After the initial admission attempts fail, high-
priority services can access the network by preempting the transport resources for low-
priority services.
Transport overload control: It can be used to rapidly enhance transmission
stability when transport resources are overloaded.
Transport load reporting: When the transport load is higher than a threshold, the
transport layer reports the load status to the MLB module for load balancing on the air
interface, or the eNodeB starts transport overload control.
Transport Congestion Control
The transport network quality may fluctuate frequently. In this situation, transport dynamic
flow control estimates available bandwidth in the transport network and dynamically adjusts
the transmit (TX) bandwidth of eNodeB interface boards based on the network quality
information provided by IP PM. When the quality is good, the eNodeB gradually increases the
bandwidth. When the quality is poor, the eNodeB decreases the bandwidth to prevent
congestion.

The eNodeB implements transport dynamic flow control on each transport resource group by
using the following functions:
Transport differentiated flow control involves traffic shaping of transport resource
groups, queue scheduling of transport resource groups, and back-pressure algorithms. This
function provides users with DiffServ while ensuring fairness. When an eNodeB interface
board is congested, this function can be used to ensure the quality of non-flow-controllable
services by transmitting the services preferentially. In addition, the rates of non-real-time
services are limited to achieve differentiated allocation of bandwidth among services.
This function estimates bandwidth and provides bandwidth information for
transport differentiated flow control and transport admission control. If the dynamic TX
bandwidth adjustment function is enabled, the TX bandwidth is adjusted according to the
automatic bandwidth adjustment parameters (PLRDTH and DDTH). If the traffic exceeds
the configured bandwidth, the bandwidth can be appropriately adjusted to avoid data loss.
This function is a Huawei proprietary function. It performs end-to-end
performance monitoring to obtain network quality information such as the traffic volume,
packet loss rate, delay, and jitter. By performing IP PM, the eNodeB improves system
performance by enhancing system maintainability and testability.

NOTE:
Transport congestion control applies to user plane services.

Managed Object Model

Figure 2 shows the transport resource management MOM, which is a subset of the eNodeB MOM.
Figure 2 Transport resource management MOM

This section describes the MOs related to the transport resource management algorithms. For
details about the MOs related to the data link layer and network layer, see the IPv4 MOM
Description. Table 1describes the mapping between transport resource management algorithms
and MOs.

Table 1 Mapping between transport resource management algorithms and MOs

Algorithm Class Algorithm(Level1) Algorithm(Level2) MO

Traffic Data Processing Transport Differentiated - PRI2QUE


Algorithm Flow Control RSCGRPALG
RSCGRP
Table 1 Mapping between transport resource management algorithms and MOs

Algorithm Class Algorithm(Level1) Algorithm(Level2) MO

LR

Transport Dynamic Dynamic Bandwidth RSCGRPALG


Flow Control Adjustment

IP PM IPPMSESSION

Transport load control DiffServ QoS - DIFPRI

Transport Admission Transport Admission TACALG


Control Control Algorithm

Transport Resource TACALG


Preemption Algorithm

Different Transport TACALG


Paths Based on QoS DIFPRI
Grade

Transport Overbooking TACALG

Transport Load TLDRALG


Reporting

Transport Resource - TOLCALG


Overload Control

This section describes MOs related to Transport Resource Management.


Transport Load Control

The MOs related to transport load control are DIFPRI, TACALG, TLDRALG, and TLDRALG.
DIFPRI defines a mapping from traffic types to DSCPs. This MO supports different
transport paths based on DSCPs. Traffic can be classified into signaling, OM and clock.
TACALG defines the transport admission control algorithm.
TLDRALG defines the transport load threshold of an eNodeB for mobility load
balancing (MLB). The reported transport load status is used for the MLB algorithm.
TOLCALG defines the transport overload control (OLC) algorithm.
Transport Congestion Control
The MOs related to transport congestion control are PRI2QUE, RSCGRP, RSCGRPALG, LR, and
IPPMSESSION.

PRI2QUE defines a mapping from internal scheduling queues to transport bearer


priorities, which can be represented by DSCPs. Queue 0 has the highest priority.
RSCGRP defines a transport resource group. This MO consists of the transport
resource group ID, traffic-related parameters, and other parameters.
RSCGRPALG defines algorithms related to a transport resource group. This MO
consists of the transport resource group ID and algorithm parameters.
LR defines transmission rates on a physical port. This MO consists of the port
number, rate limitation switch, and traffic-related parameters.
IPPMSESSION defines an IP Performance Monitoring (IP PM) session. IP PM
monitors the quality of transport links, such as the delay, jitter, and packet loss rate. The
monitoring results are used as the basis of dynamic flow control.
UDT The MO is used to support the differentiated gold, silver, and bronze user
data types.
UDTPARAGRP The UDTPARAGRP MO is used to support the parameter groups
related to the differentiated Gold-, Silver-, and Bronze-level user data types. Each
parameter group is uniquely identified by the group ID. Other parameters include data
priority,priority rule, activity factor, primary transport resource type, primary port load
threshold, primary-to-secondary port load ratio threshold and flow control type. Effective
Scenario

5.7.1.4.6 PKI MOM Description


This section describes the functions and concepts of the public key infrastructure (PKI) system
architecture, digital certificate classifications, and device certificate management. It also
provides the managed object model (MOM) view and describes managed objects (MOs) related
to device certificates, trust certificates, and certificate revocation lists (CRLs).

Functions and Concepts

PKI System Architecture

PKI is a system that generates, distributes, activates, and revokes digital certificates. A PKI
system consists of eNodeBs, a Certificate Authority (CA), a Registration Authority (RA), and a
certificate & CRL database for storing digital certificates and CRLs. The RA is optional. Figure 1
shows the PKI system architecture.
Figure 1 PKI system architecture

The RA directly interacts with eNodeBs or the operation and maintenance (OM) personnel. It
collects and authenticates information about digital certificate applicants, and decides whether to
issue digital certificates to them. If an applicant is proved qualified, the RA sends the applicant's
digital certificate request to the CA. Then, the CA issues a certificate to the certificate & CRL
database.
Revoked certificates are recorded in a CRL. The CA issues the CRL to a specified certificate &
CRL database. An eNodeB obtains the CRL from the database to check whether a peer digital
certificate has been revoked.
Digital Certificate Classifications

An eNodeB supports three types of digital certificates: device certificates, trust certificates, and
cross-certificates, as shown in Figure 2.
Figure 2 Digital certificates supported by the eNodeBs

For details about Digital certificates are as follows:


Device Certificate
A device certificate identifies a device. Each device certificate is associated with a unique
private key.
Each eNodeB stores a Huawei-issued device certificate named appcert.pem. This device
certificate is issued by Huawei CA and activated automatically before delivery.
Trust Certificate
A trust certificate contains a root certificate and a certificate chain.
The root certificate, issued by a root CA, is a top-most certificate used to verify other
certificates in the certificate chain.

The eNodeB uses trust certificates to authenticate peer devices in the following ways:
Each eNodeB stores a Huawei root certificate named appcert.pem. This root
certificate is issued by Huawei CA and activated automatically before delivery. The
Huawei eNodeB supports mutual authentication of other devices configured with Huawei
device and root certificates.
To authenticate an operator's device, for example, a Security Gateway (SeGW),
the eNodeB must be configured with a root certificate issued by the operator's CA (referred
to as operator's root certificate in this document). Similarly, to authenticate a Huawei
eNodeB, the operator's device must be preconfigured with a trusted Huawei root
certificate.
Cross-Certificate
A cross-certificate is used for cross-certification between CAs or devices of different PKI
systems.
The cross-certificate is issued by a CA in one PKI system to a trusted CA in another PKI
system.
Cross-certificates are an alternative to root certificates in cross-certification between a Huawei
eNodeB and an operator's device.

Certificate Management
Certificate Management Mode

eNodeB device certificates are managed in the following modes: M2000-assisted certificate
management and direct certificate management. After deployment, an eNodeB manages
device certificates in either M2000-assisted certificate management mode or direct certificate
management mode by replacing, updating, or checking a device certificate.
M2000-Assisted Certificate Management

The M2000 communicates with a CA through a standard Certificate Management Protocol


version 2 (CMPv2) interface and communicates with eNodeBs through private man-
machine language (MML) interfaces. The M2000 manages certificate requests, updates,
and revocation. In other words, the M2000 serves as an OM platform and also as a proxy
between eNodeBs and the CA when managing device certificates. Figure 3 shows how the
eNodeB device certificates are managed in M2000-assisted certificate management mode.
Figure 3 M2000-assisted certificate management mode for eNodeB device certificates

M2000-assisted certificate management requires each eNodeB or operator's device be


configured with a Huawei root certificate or an operator's root certificate, respectively.
After the devices access the live network, those preconfigured certificates are updated on
the M2000 manually.
Direct Certificate Management

In direct certificate management mode, both the eNodeBs and the M2000 provide the
CMPv2 interface, and eNodeBs directly communicate with a CA. The eNodeBs manage
certificate requests, updates, and revocation. When managing device certificates, the
eNodeBs communicate with the CA by exchanging CMPv2 messages. The M2000 serves
only as an OM platform. Figure 4 shows how the eNodeB device certificates are managed in
direct certificate management mode.
Figure 4 Direct certificate management mode for eNodeB device certificates

Direct certificate management is an automatic process. In this situation, no preconfigured


certificate is required. The eNodeBs can directly apply for certificates to access the live
network.
Certificate Management Method
Replacing a Certificate

During device certificate replacement, the current device certificate is deactivated and a new
one is activated. Possible scenarios for device certificate replacement are as follows:
The operator deploys a PKI system before deploying an eNodeB. To access a
transport network, the eNodeB requests a device certificate issued by the operator's CA
(referred to as operator-issued device certificate in this document) to replace the
preconfigured Huawei-issued device certificate.
The operator deploys a PKI system after deploying an eNodeB. The eNodeB
requests an operator-issued device certificate to replace the preconfigured Huawei-issued
device certificate.
The device certificate of an eNodeB is revoked before it expires because the
private key is not complex enough or disclosed.
An eNodeB is moved from the management area of one CA to another.
Updating a Certificate
If a device certificate expires or the location of an eNodeB changes, the device certificate of
the eNodeB must be updated to ensure correctness of the certificate.
Checking a Certificate
Before communicating with the peer end, an eNodeB must check whether the device
certificate of the peer end is in the CRL for security concerns. This CRL can be loaded onto
the eNodeB manually by OM personnel on the M2000 or the Local Maintenance Terminal
(LMT). Alternatively, the administrator can create a scheduled task so that the eNodeB
downloads the CRL automatically and periodically from a certificate & CRL database. If the
device certificate of the peer end is found in the CRL, the eNodeB reports an alarm or stops
the communication with the peer end, according to the configuration.
Deploying a Certificate
A device certificate is configured on an LTE main processing and transmission unit (LMPT)
or a universal transmission processing unit (UTRP) where other boards can obtain the
certificate as required.
For details about the PKI system, see Transmission Security Feature Parameter Description.

Managed Object Model

Figure 5 shows the PKI MOM of MOs related to CRLs.


Figure 5 PKI MOM of MOs related to CRLs

MOs related to PKI are classified into three categories: MOs related to device certificates, MOs
related to trust certificates (including root certificates), and MOs related to CRLs.
Figure 6 MOs related to PKI

MOs related to device certificates, trust certificates, and CRLs are as follows:
MOs related to device certificates are CERTREQ, CERTMK, APPCERT, CERTCHKTSK and CA.
Device certificates are used to authenticate the identities of NEs.
MOs related to trust certificates (including root certificates) are TRUSTCERT and
CROSSCERT. Root certificates are the device certificates of root CAs. They are used to check
validity of device certificates issued by the CAs.
MOs related to CRLs are CRL, CRLTSK and CRLPOLICY. A CRL is used to record
certificates that are revoked because of key disclosure or certificate expiry. Using a CRL, an
NE checks validity of certificates and decides to generate alarms or break connections,
depending on users' policies.
This section describes MOs related to PKI shown in Figure 1.
CERTDEPLOY defines the number of the slot where a certificate is to be deployed and
configuration and maintenance commands are to be delivered. Other certificate-related MOs
are dependent on this MO.
MOs Related to Device Certificates

The MOs related to device certificates are defined as follows:


CAdefines a certification authority that provides information required for the
eNodeB to connect to the CA server, including information about the issuing authority of
certificates. This MO is required only when the direct certificate management mode is
adopted. This MO is not required when the M2000-assisted certificate management mode
is adopted.
CERTREQdefines registration information in a device certificate request. The
information includes the common name of the certificate request file, the organization that
owns the device, the location of the device, and the request type.
CERTMKdefines a device certificate that has already been verified by using the
local private key. A device certificate must be verified before it can be activated and used.
APPCERT defines an activated device certificate. Only a certificate that is proved
valid and verified by a trust certificate can be used.
CERTCHKTSK defines a device certificate checking task. If this MO is configured,
the eNodeB automatically checks the validity of its device certificate and updates the
device certificate when it is about to expire.
MOs Related to Trust Certificates

The MOs related to trust certificates are defined as follows:


TRUSTCERT defines a trust certificate, which is used by the eNodeB to verify the
device certificate of the peer end.
CROSSCERT defines a cross-certificate, which is used by the eNodeB to
authenticate a peer device during the cross-certification.
MOs Related to CRLs

The MOs related to CRLs are defined as follows:


CRL defines a CRL, also known as a certificate blacklist. It records all revoked
certificates.
CRLPOLICY defines a policy to use CRLs. It determines whether the eNodeB
checks the local and peer certificates based on the CRL and which action to take if the
check fails.
CRLTSK defines a CRL checking task, in which the eNodeB periodically checks
the validity of its device certificate based on the policy to use CRLs.
5.7.1.5 Radio MOM

5.7.1.5.1 Cell and Channel MOM Description


This section describes the functions and concepts of managed object models (MOMs) and
managed objects (MOs) of cells and channels.

Functions and Concepts

Cells
A cell is a radio coverage area that provides services for users. All the cells joined together
provide coverage for the entire radio network. Coverage is classified into overlapping coverage
and separate coverage. Figure 1 shows the mapping between cells and coverage areas.

NOTE:
The term cell in this document refers to a cell in a local eNodeB, rather than an inter-eNodeB cell, which is called an
external cell.

Figure 1 Mapping between cells and coverage areas

Cell attributes include parameters related to radio services and are used to identify cells in
different types. The transmit (TX) and receive(RX) modes of cells include 1T1R, 1T2R, 2T2R,
2T4R, 4T4R, and 8T8R. 1T2R and 2T2R, 2T4R and 4T4R, and 8T8R are named as two
antennas, four antennas, and eight antennas, respectively. At present, 8T8R applies only to LTE
time division duplex (TDD).
Sector
A sector is a radio area covered by a set of RF antennas with the same coverage.
Sectors are classified into omnidirectional sectors and directional sectors. An omnidirectional
sector covers a circle area of 360 degrees with an omnidirectional antenna at the center.
Omnidirectional sectors are used for low-traffic coverage. Directional sectors are used for high-
traffic coverage. Each directional sector uses directional antennas for coverage. In three-sector
scenarios, each directional antenna covers a sector area of 120 degrees. In six-sector scenarios,
each directional antenna covers a sector area of 60 degrees. The coverage areas of adjacent
sectors overlap each other because the actual azimuth of each sector is slightly larger than 60 or
120 degrees.
Except the scenario of sectors with Multiple RRUs Combined, the number of cells supported by
an eNodeB is calculated as follows: Number of cells supported by an eNodeB = Number of
sectors x Number of carriers

Figure 2shows the mapping between sectors, carriers, and cells. This figure uses a typical 3x2
configuration as an example. Three sectors (sectors 0-2) cover a circle area. Each sector uses two
carriers, and each cell uses one carrier. There are a total of six cells.
Figure 2 Mapping between sectors, carriers, and cells

Mapping Between Sectors and RF Resources


shows the mapping between sectors and radio frequency (RF) resources of an eNodeB.
Figure 3
A sector uses antennas for coverage. To improve the receive quality, each antenna provides
two receive channels that work in receive diversity mode.
Figure 3 Mapping between sectors and RF resources of an eNodeB

Cell Type
Common Cell
The TX and RX modes of common cells include 1T1R, 1T2R, 2T2R, 2T4R, 4T4R, and
8T8R. A common cell can be configured on an LRRU or LRFU. Larger capacity is
provided by a common cell configured on two combined LRRUs or LRFUs. The two
combined LRRUs or LRFUs must be configured to the same LBBP. In LTE TDD, only
2T2R supports the networking of combined LRRUs or LRFUs. In LTE frequency division
duplex (FDD), 2T2R, 2T4R, and 4T4R support the networking of combined LRRUs or
LRFUs.
Sectors with Multiple RRUs Combined
Multiple RRUs can be combined to serve a cell. The transmitter combines uplink signals
and selectively received them at the baseboard. The receiver combines the uplink signals
from multiple RRUs or selectively demodulates them. Multi-RRU combination is also
called multi-carrier combination.

Multi-RRU combination has the following advantages:


Increased cell coverage radius and less UE handovers.
Improved UE performance by reducing the number of cells, the area of
cell boundaries, and interference.
Reduced capacity expansion costs by splitting a cell into multiple cells.

Multi-RRU combination is applicable in the following scenarios:


Ultra-high-speed railway scenarios (as shown in Figure 4): Multi-RRU
combination prevents performance deterioration caused by frequent UE handovers.
Non-ultra-high-speed railway scenarios: The scenarios include wide
coverage scenarios and macro coverage scenarios, as shown in Figure 5 and Figure 6
respectively.
Figure 4 Two RRUs combined back to back in ultra-high-speed railway scenarios
Figure 5 Multi-RRU combination in wide coverage scenarios

Figure 6 Multi-RRU combination in macro coverage scenarios

Channels

In the LTE system, channels are classified into logical channels, transport channels, and physical
channels at the layer level:
Logical channels are defined based on the types of data to be transmitted.
Transport channels are defined based on the formats of transmitted data packets.
Physical channels are defined based on the purposes of time and frequency resources on
the Uu interface.
Table 1 describes the classifications of physical channels, transport channels, and logical channels.
Table 1 Classifications of physical channels, transport channels, and logical channels

Classification Channel

Logical Control BCCH(Broadcast Control CHannel)


channels channels
PCCH(Paging Control CHannel)

CCCH(Common Control CHannel)

MCCH(Multicast Control CHannel)

DCCH(Dedicated Control CHannel)

Traffic channels DTCH(Dedicated Traffic CHannel)

MTCH(Multicast Traffic CHannel)

Transport Downlink BCH(Broadcast CHannel)


channels transport
channels DL-SCH(Downlink Shared CHannel)

PCH(Paging CHannel)

MCH(Multicast CHannel)

Uplink transport UL-SCH(Uplink Shared CHannel)


channels
RACH(Random Access CHannel)

physical Downlink PDSCH(Physical Downlink Shared CHannel)


channels physical
channels PBCH(Physical Broadcast CHannel)

PMCH(Physical Multicast CHannel)

PCFICH(Physical Control Format Indicator CHannel)

PDCCH(Physical Downlink Control CHannel)

PHICH(Physical HARQ Indicator CHannel)


NOTE:
HARQ is short for hybrid automatic repeat request.

Uplink physical PUSCH(Physical Uplink Shared CHannel)


channels
PUCCH(Physical Uplink Control CHannel)
PRACH(Physical Random Access CHannel)

Figure 7and Figure 8 show the mapping between the three types of channels in the downlink and
uplink, respectively.
Figure 7 Mapping between the three types of channels in the downlink

Figure 8 Mapping between the three types of channels in the uplink

NOTE:
eRAN3.0 does not support MCCHs, MTCHs, MCHs, or PMCHs.

Managed Object Model


Figure 9 shows the cell and channel MOM, which is a subset of the eNodeB MOM.
Figure 9 Cell and channel MOM

Figure 10 shows the sector MOM, which is a subset of the eNodeB MOM.
Figure 10 Cell and channel MOM

Cell MOs

Cell MOs are defined as follows:


defines the basic information about a cell. Operators need to plan and design
Cell
parameters such as the E-UTRAN cell global identifier (ECGI), E-UTRA absolute radio
frequency channel number (EARFCN), physical cell identifier (PCI), and tracking area code
(TAC). The number of cells supported by an eNodeB relates to the hardware configuration of
the eNodeB. In eRAN3.0, an eNodeB supports a maximum of 18 cells.
defines the information about the operator of a cell. The number of CellOp MOs set
CellOp
for each cell varies depending on the working mode.
If the ENodeBSharingMode parameter is set to INDEPENDENT, only one CellOp
MO can be set for each cell and the corresponding cell operator must be the primary
operator.
If the ENodeBSharingMode parameter is set to SEPARATED_FREQ, only one
CellOp MO can be set for each cell.

If the ENodeBSharingMode parameter is set to SHARED_FREQ, a maximum of


four CellOp MOs can be set for each cell.
CellAccess defines UE access parameters such as the cell barring status and reservation
status. Operators need to set these parameters, which are then broadcast using system
information.
CellAcBar defines barring parameters for access classes (ACs). Operators need to set these
parameters, which are then broadcast using system information.
CellSiMap defines the transport periods of system information blocks (SIBs) in a cell.
Operators can set the transport period of an SIB. The eNodeB uses the default parameter
values if operators do not set the transport periods of SIBs.
CellSel defines parameters used during cell selection. Operators need to set these
parameters, which are then broadcast using system information.
CellReseldefines intra- and inter-frequency cell reselection parameters in the Evolved
Universal Terrestrial Radio Access Network (E-UTRAN) system. Operators need to set these
parameters, which are then broadcast using system information.
CellReselGeran defines parameters used for UEs to perform reselection from an E-UTRAN
cell to a GSM/EDGE Radio Access Network (GERAN) cell. This MO is set only when
GERANs are deployed around an E-UTRAN.
CellReselUtran defines parameters used for UEs to perform reselection from an E-UTRAN
cell to a Universal Terrestrial Radio Access Network (UTRAN) cell. This MO is set only
when UTRANs are deployed around an E-UTRAN.
CellReselCdma2000defines parameters used for UEs to perform reselection from an E-
UTRAN cell to a CDMA2000 cell. This MO is set only when CDMA2000 networks are
deployed around an E-UTRAN.
UeTimerConst defines UE timer parameters. Operators need to set these parameters, which
are then broadcast using system information. The eNodeB uses the default parameter values if
operators do not set these parameters.
CellChPwrCfg defines transmit power used by downlink channels in a cell.
Sector MOs

Sector MOs are defined as follows:


Cell defines the basic information about a cell. Network planning personnel need to
configure the basic information such as the cell ID and RF information as required.
An eUCellSectorEqm MO consists of parameters related to the sector
eUCellSectorEqm
device and baseband device that serve the cell.
SECTOREQM Sector equipment is a set of RF antennas that can transmit or receive signals.
This set of antennas must belong to a sector.
SECTOR defines a radio area covered by a set of RF antennas with the same coverage.
Channel MOs

Channel MOs are defined as follows:


BcchCfg defines parameters related to a BCCH. The BCCH is a downlink logical channel
that broadcasts system control information.
RACHCfg defines parameters related to an RACH. The RACH is an uplink transport
channel that is used for UEs to initiate initial access.
PCCHCfg defines parameters related to a PCCH. The PCCH is a downlink logical channel
that transmits paging messages and system information update indicators.
PDSCHCfg defines parameters related to a PDSCH. The PDSCH carries downlink shared
transport channels and paging channels. All UEs in a cell share downlink transport channels to
transmit downlink data. Paging channels are used to transmit paging messages.
PUSCHCfg defines parameters related to a PUSCH. The PUSCH carries uplink shared
transport channels. All UEs in a cell share uplink transport channels to transmit uplink data.
PHICHCfg defines parameters related to a PHICH. The PHICH is used to transmit
downlink hybrid automatic repeat request (HARQ) signals.
PUCCHCfg defines parameters related to a PUCCH. The PUCCH is used for UEs to
transmit physical uplink control signals.
SRSCfg defines parameters related to time and frequency resources used by a sounding
reference signal (SRS). The SRS is a physical signal that a UE transmits to the eNodeB to
evaluate uplink channel conditions.

5.7.1.5.2 Neighboring Cell and Neighbor


Relationship MOM Description
This section describes the functions and concepts of neighboring cells and neighbor
relationships. It illustrates managed object models (MOMs) and explains managed objects (MOs)
related to neighboring cells and neighbor relationships.

Functions and Concepts

NCL
A neighboring cell list (NCL) of a cell contains information about inter-eNodeB cells (referred to
as external cells). Each cell has one intra-RAT NCL and multiple inter-RAT NCLs. Based on
radio access technologies (RATs), external cells are classified into evolved terrestrial radio access
network (E-UTRAN) cells, universal terrestrial radio access network (UTRAN) cells,
GSM/EDGE radio access network (GERAN), and CDMA2000 cells.
NRT
A neighboring relation table (NRT) of a cell contains information about the neighbor
relationships of the cell with external cells. Each cell has one intra-RAT NRT and multiple inter-
RAT NRTs. Neighbor relationships are classified into intra-frequency neighbor relationships with
E-UTRAN cells, inter-frequency neighbor relationships with E-UTRAN cells, neighbor
relationships with UTRAN cells, neighbor relationships with GERAN cells, neighbor
relationships with CDMA2000 High Rate Packet Data (HRPD) cells, and neighbor relationships
with CDMA2000 1x Radio Transmission Technology (CDMA2000 1xRTT) cells.
This document deals with neighbor relationships of a local E-UTRAN cell with other cells.

Managed Object Model

This section provides the MOMs for neighboring cells of E-UTRAN cells and also neighbor
relationships of the E-UTRAN cells with other cells. In addition, this section provides definitions
of the MOs in the MOMs.
Managed Object Model for E-UTRAN Cells and Neighbor Relationships with the Cells

Figure 1shows the MOM for E-UTRAN cells and neighbor relationships with the cells. It is a
subset of the eNodeB MOM.
Figure 1 MOM for E-UTRAN cells and neighbor relationships with the cells

The following MOs define E-UTRAN cells and neighbor relationships with the cells:
Cell: For details, see Cell and Channel MOM Description.
defines an external E-UTRAN cell. This MO consists of common
EutranExternalCell
parameters of the cell. EutranExternalCell MOs are used for configuring EutranIntraFreqNCell and
EutranInterFreqNCell MOs for one or more cells in the local eNodeB.

EutranIntraFreqNCell defines the intra-frequency neighbor relationship of the local cell


(defined by a Cell MO) with an external E-UTRAN cell (defined by an EutranExternalCell MO).
This MO consists of parameters for handovers and reselections from the local cell to the
external cell that has the same downlink E-UTRA absolute radio frequency channel number
(EARFCN) as the local cell. The handover parameters and cell reselection parameters are
included in measurement configurations and system information block type 4 (SIB4),
respectively, that are delivered to UEs.
IntraFreqBlkCell defines a blacklisted E-UTRAN cell that has the same downlink EARFCN
as the local cell. Handovers and reselections to blacklisted intra-frequency neighboring E-
UTRAN cells are prohibited.
defines a neighboring E-UTRAN frequency. This MO consists of
EutranInterNFreq
measurement control parameters and parameters in system information block type 5 (SIB5)
for inter-frequency cell reselections.
defines the inter-frequency neighbor relationship of the local cell
EutranInterFreqNCell
(defined by a Cell MO) with an external E-UTRAN cell (defined by an EutranExternalCell MO).
This MO consists of parameters for handovers and reselections from the local cell to the
external cell that has a different downlink EARFCN from that of the local cell. The handover
parameters and cell reselection parameters are included in measurement configurations and
system information block type 5 (SIB5), respectively, that are delivered to UEs.
defines a blacklisted E-UTRAN cell that has a different downlink
InterFreqBlkCell
EARFCN from that of the local cell. Handovers and reselections to blacklisted inter-
frequency neighboring E-UTRAN cells are prohibited.
defines a secondary public land mobile network (PLMN) ID of an
EutranExternalCellPlmn
external E-UTRAN cell. One to five EutranExternalCellPlmn MOs can be configured under an
EutranExternalCell MO that defines a shared external cell.

defines the parameters related to information about an operator that


EutranNFreqRanShare
shares a neighboring E-UTRAN frequency with other operators. In RAN sharing scenarios,
operator-specific neighboring E-UTRAN frequencies can be configured as required.

defines cell reselection dedicated priorities for E-UTRAN frequencies


EutranNFreqSCellOp
based on the PLMN of the local cell.
Managed Object Model for UTRAN Cells and Neighbor Relationships with the Cells

Figure 2shows the MOM for UTRAN cells and neighbor relationships with the cells. It is a subset
of the eNodeB MOM.
Figure 2 MOM for UTRAN cells and neighbor relationships with the cells

The following MOs define UTRAN cells and neighbor relationships with the cells:
Cell: For details, see Cell and Channel MOM Description.
UtranExternalCell defines an external UTRAN cell. This MO consists of common
parameters of the cell. UtranExternalCell MOs are used for configuring UtranNCell MOs for one or
more cells in the local eNodeB.
defines the neighbor relationship of the local cell (defined by a Cell MO) with an
UtranNCell
external UTRAN cell (defined by a UtranExternalCell MO). This MO consists of parameters for
handovers and reselections from the local cell to the external cell. The handover parameters
and cell reselection parameters are included in measurement configurations and system
information block type 6 (SIB6), respectively, that are delivered to UEs.
defines a neighboring UTRAN frequency. This MO consists of measurement
UtranNFreq
control parameters and parameters in SIB6 for inter-RAT cell reselection to UTRAN.
UtranExternalCellPlmn defines a secondary PLMN ID of an external UTRAN cell. One to
three UtranExternalCellPlmn MOs can be configured under a UtranExternalCell MO that defines a
shared external cell.
defines the PLMN IDs of the operators that share a neighboring UTRAN
UtranRanShare
frequency and also the cell reselection priorities of the frequency.
defines cell reselection dedicated priorities for UTRAN frequencies based on
UtranNFreqSCellOp
the PLMN of the local cell.
Managed Object Model for GERAN Cells and Neighbor Relationships with the Cells

Figure 3shows the MOM for GERAN cells and neighbor relationships with the cells. It is a subset
of the eNodeB MOM.
Figure 3 MOM for GERAN cells and neighbor relationships with the cells

The following MOs define GERAN cells and neighbor relationships with the cells:
Cell: For details, see Cell and Channel MOM Description.
GeranExternalCell defines an external GERAN cell. This MO consists of common
parameters of the cell. GeranExternalCell MOs are used for configuring GeranNcell MOs for one
or more cells in the local eNodeB.
GeranNcell defines the neighbor relationship of the local cell (defined by a Cell MO) with
an external GERAN cell (defined by a GeranExternalCell MO). This MO consists of parameters
for handovers from the local cell to the external cell. The cell identified by the GeranCellId
parameter in a GeranNcell MO must already be configured in a GeranExternalCell MO.
GeranNfreqGroup defines a group of neighboring GERAN carrier frequencies. All
frequencies in the group have the same configuration of this MO. The group configuration is
used in measurement control for inter-RAT handovers to GERAN and used for cell
reselections to GERAN.
defines an absolute radio frequency channel number (ARFCN) in a
GeranNfreqGroupArfcn
group of neighboring GERAN carrier frequencies. This MO is used in measurement control
for inter-RAT handovers to GERAN and used for cell reselections to GERAN.
defines a secondary PLMN ID of an external GERAN cell. One to
GeranExternalCellPlmn
three GeranExternalCellPlmn MOs can be configured under a GeranExternalCell MO that defines a
shared external cell.
GeranRanShare defines the PLMN IDs of the operators that share a group of neighboring
GERAN carrier frequencies and also the cell reselection priorities of the group.
GeranNFGroupSCellOp defines cell reselection dedicated priorities for GERAN frequencies
based on the PLMN of the local cell.
Managed Object Model for CDMA2000 Cells and Neighbor Relationships with the Cells

Figure 4shows the MOM for CDMA2000 cells and neighbor relationships with the cells. It is a
subset of the eNodeB MOM.
Figure 4 MOM for CDMA2000 cells and neighbor relationships with the cells

The following MOs define CDMA2000 cells and neighbor relationships with the cells:
CellFor details, see Cell and Channel MOM Description.
Cdma2000HrpdNcell defines parameters related to the neighboring relation with a
CDMA2000 High Rate Packet Data (CDMA2000 HRPD) cell. Neighboring relations with
CDMA2000 HRPD cells are contained in the system information and measurement control
information to facilitate reselection and handover to a neighboring CDMA2000 HRPD cell,
respectively.
Cdma20001XRTTNcell defines parameters related to neighboring CDMA2000 1xRTT cells.
The parameters are used for handover or cell reselection from E-UTRAN to CDMA2000
1xRTT cells.
Cdma2000BandClass defines parameters related to a CDMA2000 band class. It is contained
in system information block type 8 (SIB8) and used in measurement control for handover and
reselection to a CDMA2000 neighboring cell.
Cdma2000Nfreq defines parameters about a CDMA2000 frequency. The parameters are
mainly used for handover and reselection. For details, see 3GPP TS 36.331.
Cdma2000BcSCellOp defines cell reselection dedicated priorities for the CDMA2000 1xRTT
or CDMA2000 HRPD band class based on the PLMN of the local cell.
defines parameters related to an external CDMA2000 1xRTT cell. It
Cdma20001XrttExtCell
provides the common information about neighboring CDMA2000 1xRTT cells. For details,
see 3GPP TS 36.331.
Cdma2000HrpdExtCell defines parameters related to an external CDMA2000 HRPD cell. It
provides the common information about neighboring CDMA2000 HRPD cells. For details,
see 3GPP TS 36.331.
5.7.1.5.3 QCI MOM Description
This section describes the functions and concepts of eNodeB-level QoS class identifies (QCIs),
cell-level QCIs, operator-level QCIs, and parameter groups. It illustrates managed object models
(MOMs) of eNodeB-, cell-, and operator-level QCIs and also explains managed objects (MOs)
related to the QCIs.

Functions and Concepts

QCI is an important parameter used in end-to-end quality of service (QoS) control for evolved
packet system (EPS) bearers. QCIs apply to each network element (NE) that packets travel
through. Managing QCIs is fundamental to fine-grained service classification for network
operation. Huawei E-UTRAN NodeBs (eNodeBs) support QCI-specific configurations of QoS
management parameters and policies. 3GPP specifications define standardized QCIs 1 to 9.
Operators can define extended QCIs 10 to 254 for lean operation.
QCIs are classified into eNodeB-, cell-, and operator-level QCIs.
Cell-Level QCIs
An eNodeB may provide multiple cells with different network plans. For example, the cells may
use different hysteresis and offset values for intra-frequency handovers. Different QoS
management policies can be set for individual cells by setting cell-level QCIs.
eNodeB-Level QCIs
eNodeB-level QCIs are specific to eNodeBs, not to individual cells or operators. For example, an
eNodeB-level QCI is associated with a Radio Link Control (RLC)/Packet Data Convergence
Protocol (PDCP) parameter group and uplink and downlink scheduling parameters. Parameters
indicated by eNodeB-level QCIs apply to the entire eNodeB.
Operator-Level QCIs
In radio access network (RAN) sharing mode, one eNodeB is shared by multiple operators. The
operators may have different feature deployment policies. For example, they use different inter-
RAT handover policies based on their own network plans. Different QoS management policies
can be set for individual operators by setting operator-level QCIs.

NOTE:
RAT stands for radio access technology.

Parameter Groups
A parameter group contains parameters with the same or similar functions. Each parameter group
has a unique ID. Like QCIs, parameter groups are classified into eNodeB-, cell-, and operator-
level parameter groups. A parameter group can be specified for each standardized or extended
QCI to significantly reduce the workload of parameter setting. Different QCIs can reference the
same parameter group so that they indicate the same group of parameters.

Managed Object Model


Cell-Level QCI MOM

Figure 1 and Figure 2show the cell-level QCI MOM, which are subsets of the eNodeB MOM.
Figure 1 Cell-level QCI MOM-a

Figure 2 Cell-level QCI MOM-b

The MOs shown in Figure 1 and Figure 2are defined as follows:


Celldefines a cell. For details, see Cell and Channel MOM Description.
CellStandardQcidefines a cell-level standardized QCI. A CellStandardQci MO consists of a
standardized QCI, a local cell ID, and the IDs of parameter groups, such as intra- and inter-
frequency handover parameter groups. Each cell always has 9 cell-level standardized QCIs.
CellExtendedQcidefines a cell-level extended QCI. A CellExtendedQci MO consists of an
extended QCI, a local cell ID, and the IDs of parameter groups, such as intra- and inter-
frequency handover parameter groups. Each cell can have a maximum of 60 cell-level
extended QCIs.
IntraFreqHoGroupdefines an intra-frequency handover parameter group. Such a group
contains parameters such as the hysteresis and time-to-trigger for intra-frequency handovers.
Each cell can have a maximum of 10 such groups.
InterFreqHoGroupdefines an inter-frequency handover parameter group. Such a group
contains parameters such as the hysteresis and time-to-trigger for inter-frequency
measurement events A1 and A2. Each cell can have a maximum of 10 such groups.
InterRatHoCommGroupdefines a group of common parameters related to inter-RAT
handovers. Such a group contains parameters such as the hysteresis and time-to-trigger for
inter-RAT measurement events A1 and A2. Each cell can have a maximum of 10 such groups.
InterRatHoGeranGroupdefinesa group of parameters related to inter-RAT handovers to
GSM/EDGE radio access network (GERAN). Such a group contains parameters such as the
hysteresis for handovers to GERAN and the threshold for coverage-based handovers to
GERAN. Each cell can have a maximum of 10 such groups.
InterRatHoUtranGroup defines a group of parameters related to inter-RAT handovers to
universal terrestrial radio access network (UTRAN). Such a group contains parameters such
as the hysteresis for handovers to UTRAN and the Ec/No threshold for coverage-based
handovers to UTRAN. Each cell can have a maximum of 10 such groups.
InterRatHoCdma1xRttGroupdefines a group of parameters related to inter-RAT handovers to
CDMA2000 1x Radio Transmission Technology (1xRTT) networks. Such a group contains
parameters such as the hysteresis for handovers to CDMA2000 1xRTT and the threshold for
coverage-based handovers to CDMA2000 1xRTT. Each cell can have a maximum of 10 such
groups.
InterRatHoCdmaHrpdGroupdefines a group of parameters related to inter-RAT handovers to
CDMA2000 High Rate Packet Data (HRPD) networks. Such a group contains parameters
such as the hysteresis for handovers to CDMA2000 HRPD and the threshold for coverage-
based handovers to CDMA2000 HRPD. Each cell can have a maximum of 10 such groups.
DrxParaGroupdefines a discontinuous reception (DRX) parameter group. Such a group
contains parameters such as the long DRX cycle and On Duration timer. Each cell can have a
maximum of 10 such groups. For setting descriptions about DRX parameters, see the
engineering guidelines described in the DRX Feature Parameter Description.
eNodeB-Level QCI MOs

Figure 3shows the eNodeB-level QCI MOM, which is a subset of the eNodeB MOM.
Figure 3 eNodeB-level QCI MOM

The MOs shown in Figure 3 are defined as follows:


StandardQcidefines an eNodeB-level standardized QCI. A StandardQci MO consists of a
standard QCI and parameters such as weight factors used to calculate connection priorities in
uplink and downlink scheduling. An eNodeB always has 9 eNodeB-level standardized QCIs.
Manual addition or removal is prohibited for these QCIs.
ExtendedQcidefines an eNodeB-level extended QCI. An ExtendedQci MO consists of an
extended QCI and parameters such as weight factors used to calculate connection priorities in
uplink and downlink scheduling. An eNodeB can have a maximum of 60 eNodeB-level
extended QCIs.
InterRatPolicyCfgGroupdefinesan inter-RAT handover policy group. Such a group contains
parameters such as policies for handovers to GERAN and UTRAN. An eNodeB can have a
maximum of 40 such groups.
RlcPdcpParaGroup defines an RLC/PDCP parameter group. Such a group contains
parameters such as the RLC mode and PDCP discard timer. An eNodeB can have a maximum
of 40 such groups.
eNodeBFunction Root node of the eNodeB function domain. The eNodeB function is used
for radio access in the LTE system. It mainly performs radio resource management (RRM)
functions such as air interface management, access control, mobility control, and UE resource
allocation.
Operator-Level QCI MOM

Figure 4shows the operator-level QCI MOM, which is a subset of the eNodeB MOM.
Figure 4 Operator-level QCI MOM

The MOs shown in Figure 4 are defined as follows:


CnOperatordefines an operator. For details, see RAN Sharing MOM Description.
CnOperatorStandardQcidefines
an operator-level standardized QCI. A
CnOperatorStandardQci MO consists of a standardized QCI, an operator index, and the ID of
a service-based inter-RAT handover policy group. Each operator always has 9 operator-level
standardized QCIs. These QCIs are added or removed automatically when the operator is
added or removed. Manual addition or removal is prohibited for these QCIs.
CnOperatorExtendedQcidefines
an operator-level extended QCI. A CnOperatorExtendedQci
MO consists of an extended QCI, an operator index, and the ID of a service-based inter-RAT
handover policy group. Each operator can have a maximum of 60 operator-level extended
QCIs.
ServiceIrHoCfgGroupdefines a service-based inter-RAT handover policy group. Such a group
contains the group ID, an operator index, and a handover policy. Each operator can have a
maximum of 10 such groups.

5.7.1.5.4 RAN Sharing MOM Description


This section describes the functions and concepts related to Radio Access Network (RAN)
sharing. In addition to the related managed object model (MOM) view, it also provides the
configuration information of the involved managed objects (MOs).

Functions and Concepts

RAN sharing enables multiple operators to share an eRAN. The sharing of components in a
network by multiple operators is called network sharing. Network sharing has multiple forms,
such as RAN sharing, evolved packet core (EPC) sharing, and transmission sharing. This
document focuses on RAN sharing with independent EPCs.
Sharing Modes

RAN sharing is classified into RAN sharing with common carriers and RAN sharing with
dedicated carriers.
In RAN sharing with common carriers, operators share carrier resources and eNodeB
hardware resources.
In RAN sharing with dedicated carriers, operators have their own carrier resources and
share only eNodeB hardware resources.
Primary and Secondary Operators
The type of an operator is specified by the CnOperatorType parameter in a CnOperator MO.
According to 3GPP TS 36.331, the public land mobile network (PLMN) at the top of the
broadcast PLMN ID list is the primary PLMN. Its operator is called the primary operator, and its
ID can be used together with an eNodeB ID and a cell ID for addressing. The primary and
secondary operators can share eNodeB resources based on specified proportions. The primary
operator does not have any privileges.
License
A license is an authorization agreement between the vendor and the customer in terms of the
application scope and service lifetime of products. Licenses involved in RAN sharing are
classified into feature licenses and capacity licenses.
2.4 Tracking Area
An evolved packet core (EPC) uses tracking areas (TAs) to determine the scope for transmitting
paging messages. A TA may contain one or more cells. When an eNodeB serves multiple
operators, cells under this eNodeB may also serve multiple operators in RAN sharing with a
common carrier mode. Therefore, a cell may belong to TAs of multiple operators, and the
mapping between cells and TAs must be configured.

Managed Object Model

Figure 1 shows the RAN sharing MOM, a subset of the eNodeB MOM.
Figure 1 RAN sharing MOM
The MOs in the RAN sharing MOM are defined as follows:
ENodeBSharingMode defines the eNodeB sharing mode, which can be set to
INDEPENDENT, COMMON_CARRIER_SHARE, or
DEDICATED_CARRIER_SHARE.
CnOperator defines an operator. A maximum of six operators (including one primary
operator) can share RAN resources of each eNodeB.
LicenseSharingPolicy defines a license sharing policy, which includes the proportion of
license performance items and the right to access license function items allocated to each
operator.
Cell defines the basic information about a cell. For details, see Cell and Channel MOM
Description.

CnOperatorTa defines the information about a TA for operators. The information includes
the tracking area identifier (TAI), tracking area code (TAC), and operator index corresponding
to the TAC. An eNodeB supports a maximum of 108 TAs.
CellOp defines operator information for a cell. The number of CellOp MOs configured for
each cell varies depending on the eNodeB sharing mode.
For RAN sharing with dedicated carriers, only one CellOp MO can be configured
for each cell.
For RAN sharing with common carriers, a maximum of six CellOp MOs can be
configured for each cell. The operator specified by one of the CellOp MOs must be
configured as the primary operator.
eNodeBFunction Root node of the eNodeB function domain. The eNodeB function is used
for radio access in the LTE system. It mainly performs radio resource management (RRM)
functions such as air interface management, access control, mobility control, and UE resource
allocation.

5.7.1.5.5 User Steering MOM Description


This section describes the functions and concepts of user steering, illustrates the managed object
model (MOM) of user steering, and explains managed objects (MOs) related to user steering.

Functions and Concepts

By using user steering, the E-UTRAN can provide customized and differentiated services based
on the subscriber profile ID (SPID), meeting the requirements of different types of users.

Managed Object Model

Figure 1 shows the user steering MOM, which is a subset of the eNodeB MOM.
Figure 1 User steering MOM

The MOs shown in Figure 1 are specified as follows:


SpidCfg defines a Subscriber Profile ID (SPID) configuration. An SpidCfg consists of the
parameters associated with a Subscriber Profile ID (SPID). The parameters include the
priority of camping of a UE in idle mode, inter-frequency or inter-RAT handover priority of a
UE in connected mode, support of special DRX, support of preallocation, switch for SPID-
based inter-frequency or inter-RAT load balancing, and switch for SPID-based handover back
to the HPLMN. Special DRX is configured for UEs that do not require power saving.
RatFreqPriorityGroup defines a RAT or frequency priority group.
CnOperatorSpidCfg defines the configuration of an SP ID, and the RAT frequency priority
for an operator.
eNodeBFunction defines Root node of the eNodeB function domain. The eNodeB function
is used for radio access in the LTE system. It mainly performs radio resource management
(RRM) functions such as air interface management, access control, mobility control, and UE
resource allocation.

5.7.1.6 MO
Transport-tree
This chapter describes the MOs related to eNodeB transmission.

Equipments-tree
This chapter describes the MOs related to eNodeB equipment.

Radio-tree
This chapter describes the MOs related to eNodeB radio.

Parent topic: eNodeB MO Reference

5.7.1.6.1 Transport-tree
This chapter describes the MOs related to eNodeB transmission.

ACL

ACL6

ACLRULE

ACLRULE6

APPCERT

BFDSESSION

CA

CERTCHKTSK

CERTDEPLOY

CERTMK

CERTREQ

CFMBNDIP

CFMMA

CFMMD

CFMMEP

CFMRMEP

CPBEARER

CRL

CRLPOLICY

CRLTSK

CROSSCERT

DEVIP

DEVIP6

DHCPRELAYSWITCH

DHCPSVRIP
DHCPSW

DIFPRI

DOT1X

DSCPMAP

E1T1

E1T1BER

EP2RSCGRP

EPGROUP

ETHOAM3AH

ETHPORT

ETHTRK

ETHTRKLNK

FLOODDEFEND

GTPU

GTRANSPARA

HAGRP

IKECFG

IKEPEER

IKEPEER6

IKEPROPOSAL

IP2RSCGRP

IP2RSCGRP6

IPGUARD

IPITF6

IPPATH

IPPATH6
IPPATHRT

IPPMSESSION

IPRT

IPRT6

IPSECBIND

IPSECBIND6

IPSECDTNL

IPSECPOLICY

IPSECPOLICY6

IPSECPROPOSAL

LLDPGLOBAL

LLDPLOCAL

LOCALETHPORT

LOCALIP

LOCALIP6

LR

MPGRP

MPLNK

OMCH

OMCH6

PACKETFILTER

PINGFILTER

PLRTHRESHOLD

PMTUCFG

PORTSECURITY

PPPLNK
PRI2QUE

RSCGRP

RSCGRPALG

SCTPHOST

SCTPLNK

SCTPLNK6

SCTPPEER

SCTPTEMPLATE

SECURITYHOST

SECURITYPEER

SECURITYTEMPLATE

SUBIF

SUBNETVLAN

TACALG

TLDRALG

TLFRSWITCH

TOLCALG

TRANSPORT

TRUSTCERT

TUNNEL

UDPSESSION

UDT

UDTPARAGRP

USERPLANEHOST

USERPLANEPEER

VLANCLASS
VLANMAP

VRF

Parent topic: MO

5.7.1.6.1.1 ACL
TRANSPORT
+-ACL
+-ACLRULE[0~128]

Description

The Access Control List (ACL) is an instruction list for ports on routers and switches, which is
used to control packets received on or transmitted from the port. Applied to all router protocols,
an ACL contains matching relations, conditions, and query commands. The ACL framework is
aimed at access control.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Possible children:
ACLRULE[0~128]

Relation with the IPSECPOLICY6 MO:


- The ACL MO that uses the default VRF instance and corresponds to an IPSECPOLICY6
MO must have been configured.
Relation with the ACL MO:
- On a BS, the total number of IPv4 ACL MOs and IPv6 ACL6 MOs must be smaller than or
equal to 64.
Relation with the VRF MO:
- The VRF instance used by a ACL MO must have been configured.
Relation with the IPSECPOLICY MO:
- VRFIDX in the ACL MO corresponding to an IPSECPOLICY MO must be set to 0.
Relation with the PACKETFILTER MO:
- If PT in a PACKETFILTER MO is set to ETH, ETHTRK, or TUNNEL, the ACL MO
corresponding to ACLID must use the default VRF instance.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD ACL Use this command to add a record of the ACL.

LST ACL Use this command to list the configuration of an Access Control List (ACL).

MOD ACL Use this command to modify the configuration of an ACL.

RMV ACL Use this command to remove an ACL.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

ACL ID Indicates the ID of the Access Control List (ACL) to which the access control
rule belongs. ACL ID in the range from 3000 to 3999 identifies high-level rules
based on the layer 3 and layer 4 information. ACL ID in the range from 4000 to
4999 identifies access control rules based on the MAC layer information.

VRF Index Indicates the index of a VRF instance. The NodeB currently supports default
routes domain only (the VRF index is 0).

Description Indicates the brief description of the ACL.

Control Mode Indicates whether the object can be modified or deleted by the system. The value
MANUAL_MODE means that only the user can modify or delete the object.
The value AUTO_MODE means that both the system and the user can modify or
delete the object.
Table 2 Related parameters

Parameter Description

Auto Config Flag Indicates whether the object is created by the system. MANUAL_CREATED
means that the object is configured by the user manually. AUTO_CREATED
means that the object is created by the system.

5.7.1.6.1.2 ACL6
TRANSPORT
+-ACL6
+-ACLRULE6[0~128]

Description

An Access Control List 6 (ACL6) is an instruction list for ports on routers and switches in IPv6
networks. The list is used to control packets received or transmitted on ports. Applicable to all
router protocols, an ACL contains matching relationships, conditions, and query commands. The
ACL framework is aimed at access control.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Possible children:
ACLRULE6[0~128]

Relation with the IPSECPOLICY6 MO:


- The ACL6 MO corresponding to an IPSECPOLICY6 MO must have been configured.
Relation with the ACL6 MO:
- On a BS, the total number of IPv4 ACL MOs and IPv6 ACL6 MOs must be smaller than or
equal to 64.

Related MML Commands


Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD ACL6 User this command to add an IPv6 Access Control List (ACL).

LST ACL6 Use this command to list the configuration of an IPv6 Access Control List
(ACL).

MOD ACL6 Use this command to modify the configuration of an IPv6 ACL.

RMV ACL6 Use this command to remove an IPv6 ACL.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

IPv6 ACL ID Indicates the ID of the IPv6 Access Control List (ACL) to which the IPv6 access
control rule belongs.

Description Indicates the brief description of an IPv6 ACL.

Control Mode Indicates whether the object can be modified or deleted by the system. The value
MANUAL_MODE means that only the user can modify or delete the object.
The value AUTO_MODE means that both the system and the user can modify or
delete the object.

Auto Config Flag Indicates whether the object is created by the system. MANUAL_CREATED
means that the object is configured by the user manually. AUTO_CREATED
means that the object is created by the system.

5.7.1.6.1.3 ACLRULE
TRANSPORT
+-ACL
+-ACLRULE

Description

This MO is used to define the rules in an Access Control List (ACL). The BS identifies and
classifies the data flow based on the rules.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
ACL

Relation with the IPSECPOLICY6 MO:


- The ACL MO corresponding to an IPSECPOLICY6 MO must have at least one
ACLRULE MO.
Relation with the IPSECBIND,IPSECPOLICY MOs:
- The maximum of ACLRULE which are referenced by IPSECBIND on one board is 128.
Relation with the ACLRULE MO:
- Each ACLRULE MO in one ACL MO must have a unique configuration. Two ACLRULE
MOs have the same configuration if the following values are the same in the two MOs: The
calculation result of SIP and SWC by using a wildcard; the calculation result of DIP and DWC
by using a wildcard; the values of ACTION, PT, SMPT, SOP, SPT1, SPT2, DMPT, DOP,
DPT1, DPT2, MDSCP, DSCP, and MFRG.
- A maximum of 128 ACLRULE MOs can be configured in one ACL MO.
- Each ACLRULE MO in one ACL MO must have a unique configuration.Two ACLRULE
MOs have the same configuration if the following condition is met:The two ACLRULE MOs
have the same combination of ACTION,VLANIDOP,VLANID1,and VLANID2.
- On a BS, the total number of IPv4 ACLRULE MOs and IPv6 ACLRULE6 MOs must be
smaller than or equal to 128.
Relation with the IPSECPOLICY MO:
- Before configuring an IPSECPOLICY MO, ensure that an ACLRULE MO is configured
for the ACL MO referenced by the IPSECPOLICY MO.
Relation with the PACKETFILTER MO:
- If FM in a PACKETFILTER MO is set to ADV_ACL or ADV_AND_L2, at least one
ACLRULE MO which is created manually is included in the ACL MO specified by ACLID.
- If FM in a PACKETFILTER MO is set to L2_ACL or ADV_AND_L2, at least one
ACLRULE MO is included in the ACL MO specified by ACLID2.
Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD ACLRULE Use this command to add a rule to an Access Control List (ACL).

LST ACLRULE Use this command to list the configuration of an Access Control List (ACL)
rule.

MOD ACLRULE User this command to modify an Access Control List (ACL) rule.

RMV ACLRULE Use this command to remove an ACL rule from an ACL.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

ACL ID Indicates the ID of the Access Control List (ACL) to which the ACL rule
belongs.

Rule ID Indicates the ID of the ACL rule.

Action Indicates the action taken on the data that matches the ACL rule. When the ACL
to which the ACL rule belongs is referenced by a packet filter, the BS accepts or
transmits the data that matches the rule if this parameter is set to PERMIT, and
rejects the data if this parameter is set to DENY. When the ACL is referenced by
an IPSec policy, the BS encrypts or decrypts the data that matches the rule if this
parameter is set to PERMIT, and does not perform any encryption or decryption
on the data if this parameter is set to DENY.

Protocol Type Indicates the protocol type of the data to which the ACL rule is applied.

Source IP Address Indicates the source IP address of data to which the ACL rule is applied. To add
an ACL rule that is applicable to data of all source IP addresses, set this
parameter to 0.0.0.0.

Source Wildcard Indicates the wildcard of the source IP address. The wildcard is used to
Table 2 Related parameters

Parameter Description

determine which bits can be neglected when IP address matching is being


performed. Generally, it can be considered as the inverse of the corresponding
subnet mask.

Match Source Port Indicates whether to check the source port number of each data stream before
applying the ACL rule.

Source Port Operate Indicates the filtering condition for the source port. If this parameter is set to
OP_LT, the ACL rule is applied to the data stream whose source port number is
smaller than or equal to the configured port number. If this parameter is set to
OP_GT, the ACL rule is applied to the data stream whose source port number is
larger than or equal to the configured port number. If this parameter is set to
OP_EQ, the ACL rule is applied to the data stream whose source port number is
equal to the configured port number. If this parameter is set to OP_NEQ, the
ACL rule is applied to the data stream whose source port number is not equal to
the configured port number. If this parameter is set to OP_RANGE, the ACL
rule is applied to the data stream whose destination port number is within the
configured range.OP_NEQ is available only on the LMPT,UMPT,UTRPc and
SMPT.

Source Port 1 Indicates the source port number used when SMPT is set to YES. If SOP is set to
OP_RANGE, this parameter indicates the smallest source port number. If SOP is
not set to OP_RANGE, this parameter indicates a specific source port number.

Source Port 2 Indicates the source port number used when SMPT is set to YES. If SOP is set to
OP_RANGE, this parameter indicates the largest source port number. This
parameter is valid only when SOP is set to OP_RANGE.

Destination IP Address Indicates the destination IP address of data to which the ACL rule is applied. To
add an ACL rule that is applicable to data of all destination IP addresses, set this
parameter to 0.0.0.0.

Destination Wildcard Indicates the wildcard of the destination IP address. The wildcard is used to
determine which bits can be neglected when IP address matching is being
performed. Generally, it can be considered as the inverse of the corresponding
subnet mask.

Match Destination Port Indicates whether to check the destination port number of each data stream
before applying the ACL rule.

Destination Port Indicates the filtering condition for the destination port. This parameter is valid
Operate
only when DMPT is set to YES. If this parameter is set to OP_LT, the ACL rule
is applied to the data stream whose destination port number is smaller than or
equal to the configured port number. If this parameter is set to OP_GT, the ACL
Table 2 Related parameters

Parameter Description

rule is applied to the data stream whose destination port number is larger than or
equal to the configured port number. If this parameter is set to OP_EQ, the ACL
rule is applied to the data stream whose destination port number is equal to the
configured port number. If this parameter is set to OP_NEQ, the ACL rule is
applied to the data stream whose destination port number is not equal to the
configured port number. If this parameter is set to OP_RANGE, the ACL rule is
applied to the data stream whose destination port number is within the
configured range.OP_NEQ is available only on the LMPT,UMPT,UTRPc and
SMPT.

Destination Port 1 Indicates the destination port number used when DMPT is set to YES. If DOP is
set to OP_RANGE, this parameter indicates the smallest destination port
number. If DOP is not set to OP_RANGE, this parameter indicates a specific
destination port number.

Destination Port 2 Indicates the destination port number used when DMPT is set to YES. If DOP is
set to OP_RANGE, this parameter indicates the largest destination port number.
This parameter is valid only when DOP is set to OP_RANGE.

Match DSCP Indicates whether to check the DSCP of each data stream before applying the
ACL rule.

DSCP Indicates the Differentiated Services Code Point (DSCP).

Match Fragment Indicates whether to match the fragment message. The ACL rules for matching
Message
fragment messages apply to only packet filtering and does not apply to the IPSec
function.

Control Mode Indicates whether the object can be modified or deleted by the system. The value
MANUAL_MODE means that only the user can modify or delete the object.
The value AUTO_MODE means that both the system and the user can modify or
delete the object.

VLAN ID Operate Indicates the filter criteria for VLAN IDs. This parameter is valid only when
ACLID ranges from 4000 to 4999. When this parameter is set to OP_EQ, only
the VLAN ID specified by VLANID1 is a valid one. When this parameter is set
to OP_RANGE, all the VLAN IDs within the range of VLANID1 to VLANID2
are valid ones. When this parameter is set to OP_NOVLAN, only packets
without VLAN tags are valid ones.

VLAN ID 1 Indicates the ID of a VLAN to which service data belongs. When Source Port
Operate is set to OP_EQ, this parameter specifies the ID of the matching VLAN.
When Source Port Operate is set to OP_RANGE, this parameter specifies the
minimum ID of the matching VLANs.
Table 2 Related parameters

Parameter Description

VLAN ID 2 Indicates the ID of a VLAN to which service data belongs. When Source Port
Operate is set to OP_RANGE, this parameter specifies the maximum ID of the
matching VLANs. This parameter is valid only when Source Port Operate is set
to OP_RANGE.

Auto Config Flag Indicates whether the object is created by the system. MANUAL_CREATED
means that the object is configured by the user manually. AUTO_CREATED
means that the object is created by the system.

5.7.1.6.1.4 ACLRULE6
TRANSPORT
+-ACL6
+-ACLRULE6

Description

This MO is used to define the rules in an IPv6 Access Control List (ACL). The BS identifies and
classifies data flows based on the rules.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
ACL6

Relation with the ACLRULE6 MO:


- Each ACLRULE6 MO in one ACL6 MO must have a unique configuration. Two
ACLRULE6 MOs have the same configuration if all the following conditions are met: SIP and
DIP in one ACLRULE6 MO are on the same network segments as those in the other MO,
respectively. The prefix lengths of SIP and DIP in one ACLRULE6 MO are the same those in
the other MO, respectively. The two ACLRULE6 MOs have the same combination of
ACTION, PT, SMPT, SOP, SPT1, SPT2, DMPT, DOP, DPT1, DPT2, MDSCP, and DSCP.
- A maximum of 128 ACLRULE6 MOs can be configured in an ACL6 MO.
- On a BS, the total number of IPv4 ACLRULE MOs and IPv6 ACLRULE6 MOs must be
smaller than or equal to 128.
Relation with the IPSECPOLICY6 MO:
- The ACL6 MO corresponding to an IPSECPOLICY6 MO must have at least one
ACLRULE6 MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD ACLRULE6 Use this command to add a rule to an IPv6 Access Control List (ACL).

LST ACLRULE6 Use this command to list the configuration of an IPv6 Access Control List
(ACL) rule.

MOD ACLRULE6 User this command to modify an IPv6 Access Control List (ACL) rule.

RMV ACLRULE6 Use this command to remove an ACL rule from an IPv6 ACL.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

IPv6 ACL ID Indicates the ID of the IPv6 Access Control List (ACL) to which the IPv6 access
control rule belongs.

IPv6 Rule ID Indicates the ID of the IPv6 ACL rule.

IPv6 ACL Action Indicates the action taken on the data that matches the IPv6 ACL rule. When the
IPv6 ACL is referenced by an IPv6 IPSec policy, the BS encrypts or decrypts the
data that matches the rule if this parameter is set to PERMIT, and does not
perform any encryption or decryption on the data if this parameter is set to
DENY.

Protocol Type Indicates the protocol type of the data to which the IPv6 ACL rule is applied.
Table 2 Related parameters

Parameter Description

Source IPv6 Address Indicates the source IPv6 address of data to which the IPv6 ACL rule is applied.

Source Address Prefix Indicates the prefix length of the source IPv6 address. The prefix length is used
Length
to determine which bits must be compared for matching when IPv6 address
matching is being performed.

Match Source Port Indicates whether to check the source port number of each data stream before
applying the ACL rule.

Source Port Operate Indicates the filter criteria for the source port. If this parameter is set to OP_LT,
the ACL rule is applied to the data stream whose source port number is smaller
than or equal to the configured port number. If this parameter is set to OP_GT,
the ACL rule is applied to the data stream whose source port number is larger
than or equal to the configured port number. If this parameter is set to OP_EQ,
the ACL rule is applied to the data stream whose source port number is equal to
the configured port number. If this parameter is set to OP_NEQ, the ACL rule is
applied to the data stream whose source port number is not equal to the
configured port number. If this parameter is set to OP_RANGE, the ACL rule is
applied to the data stream whose destination port number is within the
configured range.

Source Port 1 Indicates the source port number used when SMPT is set to YES. If SOP is set to
OP_RANGE, this parameter indicates the smallest source port number. If SOP is
not set to OP_RANGE, this parameter indicates a specific source port number.

Source Port 2 Indicates the source port number used when SMPT is set to YES. If SOP is set to
OP_RANGE, this parameter indicates the largest source port number. This
parameter is valid only when SOP is set to OP_RANGE.

Destination IPv6 Indicates the destination IPv6 address of data to which the IPv6 ACL rule is
Address
applied.

Destination Address Indicates the prefix length of the destination IPv6 address. The prefix length is
Prefix Length
used to determine which bits must be compared for matching when IPv6 address
matching is being performed.

Match Destination Port Indicates whether to check the destination port number of each data stream
before applying the ACL rule.

Destination Port Indicates the filter criteria for the destination port. This parameter is valid only
Operate
when DMPT is set to YES. If this parameter is set to OP_LT, the ACL rule is
applied to the data stream whose destination port number is smaller than or
equal to the configured port number. If this parameter is set to OP_GT, the ACL
rule is applied to the data stream whose destination port number is larger than or
Table 2 Related parameters

Parameter Description

equal to the configured port number. If this parameter is set to OP_EQ, the ACL
rule is applied to the data stream whose destination port number is equal to the
configured port number. If this parameter is set to OP_NEQ, the ACL rule is
applied to the data stream whose destination port number is not equal to the
configured port number. If this parameter is set to OP_RANGE, the ACL rule is
applied to the data stream whose destination port number is within the
configured range.

Destination Port 1 Indicates the destination port number used when DMPT is set to YES. If DOP is
set to OP_RANGE, this parameter indicates the smallest destination port
number. If DOP is not set to OP_RANGE, this parameter indicates a specific
destination port number.

Destination Port 2 Indicates the destination port number used when DMPT is set to YES. If DOP is
set to OP_RANGE, this parameter indicates the largest destination port number.
This parameter is valid only when DOP is set to OP_RANGE.

Match DSCP Indicates whether to check the DSCP of each data stream before applying the
IPv6 ACL rule.

DSCP Indicates the DSCP that complies with an IPv6 ACL rule.

Control Mode Indicates whether the object can be modified or deleted by the system. The value
MANUAL_MODE means that only the user can modify or delete the object.
The value AUTO_MODE means that both the system and the user can modify or
delete the object.

Auto Config Flag Indicates whether the object is created by the system. MANUAL_CREATED
means that the object is configured by the user manually. AUTO_CREATED
means that the object is created by the system.

5.7.1.6.1.5 APPCERT
TRANSPORT
+-APPCERT

Description

An APPCERT MO defines an activated device certificate in use. This device certificate identifies
a BS during negotiation.
Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the APPCERT MO:


- APPCERT in an APPCERT MO must be the same as APPCERT in the associated
CERTMK MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP APPCERT Use this command to query the status of activated device certificates.

LST APPCERT Use this command to list the configurations of activated device certificates.

LST CERTTYPE Use this command to list all BS-supported application types of device
certificates.

MOD APPCERT Use this command to activate a configured device certificate. The device
certificate, if activated, will be used in negotiation for the setup of a security
tunnel to a peer device.

TST APPCERT Use this command to test a device certificate. When a test on a device certificate
starts, the BS attempts to use this device certificate to set up a security channel
to a peer device through negotiation and then returns the negotiation result.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Application Type Indicates the application type of activated device certificate. There are two
types: IKE and SSL.

Certificate File Name Indicates the file name of an activated device certificate. The file name cannot
include any of the following characters: backslashes (\), slashes (/), colons (:),
asterisks (*), question marks (?), double quotation marks ("), left angle brackets
(<), right angle brackets (>), and bars (|).

Issuer Indicates the issuer of an activated device certificate.

Common Name Indicates the common name of an activated device certificate.

Serial Number Indicates the serial number of an activated device certificate.

Expiration Date Indicates the expiration date of an activated device certificate.

IKEPeer Name Indicates the IKE name of the peer device, which is used in IKE negotiation
with the local end to test an activated device certificate. This parameter is used
only in the TST APPCERT command in the current version and will be removed
in later versions.

Effective Date Indicates the date when an activated device certificate begins to take effect.

Status Indicates the loading status of an activated device certificate.

Application Type Indicates the certificate application type supported by a BS.


Supported By NE

5.7.1.6.1.6 BFDSESSION
TRANSPORT
+-BFDSESSION

Description

A BFDSESSION MO consists of the parameters related to a Bidirectional Forwarding Detection


(BFD) session. BFD sessions are used to quickly identify faults on a channel.

Effective Scenario
Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the LOCALIP MO:


- If a BFDSESSION MO and a LOCALIP MO are in the same routing domain, DSTIP in the
BFDSESSION MO must be different from IP in the LOCALIP MO.
Relation with the IPSECDTNL,IPSECPOLICY MOs:
- In an IPSECDTNL MO, SRCIP in the BFDSESSION MOs for the active and standby
tunnels must be the same as LOCALIP in the IKEPEER MOs of the active and standby
IPSECPOLICY MOs, respectively; DSTIP in the BFDSESSION MOs for the active and
standby tunnels must be the same as REMOTEIP in the IKEPEER MOs of the active and
standby IPSECPOLICY MOs, respectively.
Relation with the IPSECDTNL MO:
- Before adding an IPSECDTNL MO, ensure that the BFDSESSION MOs for the active and
standby tunnels of the IPSECDTNL MO have been configured. That is, in the same routing
domain the BFDSESSION MOs whose BFDSN is the same as MBFDSN and SBFDSN in the
IPSECDTNL MO, respectively must have been configured.
Relation with the DEVIP,MPGRP,PPPLNK MOs:
- SRCIP in a BFDSESSION MO to be added must have been configured. That is, for the
BFDSESSION, DEVIP, PPPLNK, and MPGRP MOs configured on the same board, SRCIP
in the BFDSESSION MO must be the same as any of the following : IP in the DEVIP MO in
the same routing domain, LOCALIP in the PPPLNK MO, and LOCALIP in the MPGRP MO.
Relation with the BFDSESSION MO:
- If two BFDSESSION MOs are in the same routing domain, DSTIP in one BFDSESSION
MO must be different from SRCIP or DSTIP in the other BFDSESSION MO.
Relation with the DEVIP MO:
- If a BFDSESSION MO and a DEVIP MO are in the same routing domain, DSTIP in the
BFDSESSION MO must be different from IP in the DEVIP MO.
Relation with the MPGRP MO:
- If a BFDSESSION MO and an MPGRP MO are in the same routing domain, DSTIP in the
BFDSESSION MO must be different from LOCALIP in the MPGRP MO.
Relation with the OMCH MO:
- If a BFDSESSION MO and an OMCH MO are in the same routing domain, DSTIP in the
BFDSESSION MO must be different from IP in the OMCH MO.
Relation with the PPPLNK MO:
- If a BFDSESSION MO and a PPPLNK MO are in the same routing domain, DSTIP in the
BFDSESSION MO must be different from LOCALIP in the PPPLNK MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD BFDSESSION Use this command to add a Bidirectional Forwarding Detection (BFD) session.
BFD provides a low-overhead and short-duration method of detecting link
failures.

DSP BFDSESSION Use this command to query the status of a BFD session.

LST BFDSESSION Use this command to list the BFD session configuration.

MOD BFDSESSION Use this command to modify the configuration of a BFD session.

RMV BFDSESSION Use this command to remove a BFD session.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet No. to which a BFD session belongs.

Subrack No. Indicates the subrack No. to which a BFD session belongs.

Slot No. Indicates the slot No. to which a BFD session belongs.

Session ID Indicates the ID of a BFD session. The session ID plus 1 is the local
discriminator of the BFD session. The local discriminator must be consistent
with the configuration at the peer side.

VRF Index Indicates the index of a VRF instance. The NodeB currently supports default
routes domain only (the VRF index is 0).
Table 2 Related parameters

Parameter Description

Source IP Indicates the source IP address of the BFD session. The source IP address of a
BFD session must be a device IP address of a specified board (for example, the
IP address of an Ethernet port or a port that carries a PPP link or MP group) or a
logical IP address (for example, the IP address of a loopback port), but cannot be
set to the same value as the IP address of a remote maintenance channel or a
negotiated IP address. Note that a BFD session cannot be configured as a single-
hope session if its source IP address is a logical IP address.

Destination IP Indicates the destination IP address of a BFD session. The destination IP address
must be a valid IP address, and cannot be set to 0.0.0.0 or any existing IP
addresses in the system. If Virtual Router Redundancy Protocol (VRRP) is used
in the network, two BFD sessions must be configured with the destination IP
addresses set to the active and standby physical IP addresses of the virtual
router, respectively.

Hop Type Indicates the hop type of the BFD session. The single-hop BFD session is used
to perform point-to-point detection at the data link layer, and often used in layer
2 networking scenarios. The multi-hop BFD session is used to perform end-to-
end connectivity checks at the transport layer, and often used in layer 3
networking scenarios.

Min TX Interval Indicates the minimum interval at which the BFD session transmits control
packets.

Min RX Interval Indicates the minimum interval at which the BFD session receives control
packets.

Detection Multiplier Indicates the detection multiplier of a BFD session.

Session Catalog Indicates the type of the BFD session. If this parameter is set to
MAINTENANCE, this BFD session is used only for continuity check (CC). If
this parameter is set to RELIABILITY, the BFD session is used to trigger route
interlock. Route interlock enables the standby route to take over once the active
route becomes faulty, and therefore prevents service interruption caused by route
failures.

DSCP Indicates the Differentiated Services Code Point (DSCP). The priority has a
positive correlation with the value of this parameter.

Clear Statistic Indicates whether to delete the historical statistics. If this parameter is set to
YES, the historical statistics are deleted and a new round of statistics collecting
starts upon completion of the query.

Session State Indicates the state of a BFD session.


Table 2 Related parameters

Parameter Description

Active Detecting Mode Indicates the effective detection mode through negotiation.

Active Minimum Tx Indicates the effective minimum TX interval through negotiation.


Interval

Active Minimum Rx Indicates the effective minimum RX interval through negotiation.


Interval

Active Detection Time Indicates the detection time when the negotiation takes effect.

My Discriminator Indicates the local discriminator of the BFD session. The value of this parameter
is equal to the session number plus 1.

Your Discriminator Indicates the peer descriminator of a BFD session.

Number of TX PDUs Indicates the number of transmitted packets of a BFD session.

Number of RX PDUs Indicates the number of messages received by the BFD session.

Total Number of Up to Indicates the up-to-down number of a BFD session.


Down Sessions

Session Diagnosis Indicates the diagnostic field of the BFD session, that is, the cause of the latest
failure.

Protocol Version Indicates the protocol version of a BFD session.

5.7.1.6.1.7 CA
TRANSPORT
+-CA

Description

A CA MO consists of the parameters related to a certification authority (CA).

Effective Scenario

Immediately

Relations Between MOs


Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD CA Use this command to add a CA.

LST CA Use this command to list the configurations of CA.

MOD CA Use this command to modify the configuration of a CA.

RMV CA Use this command to remove a CA.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Certificate Authority Indicates the name of the CA.


Name

Certificate Authority Indicates the URL of the CA. The URL can be either an HTTP or HTTPS URL.
URL
The IP address in the URL must be a valid IP address. The default port number
is 80 for HTTP or 443 for HTTPS.

Signature Algorithm Indicates the signature algorithm for message of CMP. The signature algorithm
can be Secure Hash Algorithm 1 (SHA1) or Secure Hash Algorithm 256
(SHA256).

Certificate Fetch Mode Indicates the policy for configuring the following parameters:
-Certificate Update Source IP
-CA URL During Site Deployment
-Source IP for Applying for a Certificate During Site Deployment
When the parameter is set to DEFAULT_MODE, the UPDSIP, INITREQURL,
and INITREQSIP do not need to be configured. When the certificate is obtained
Table 2 Related parameters

Parameter Description

initially during site deployment, the certificate is applied for manually, or the
certificate is updated automatically or manually, the base station uses the OM IP
address as the source address, and the URL as the destination address.When the
parameter is set to CFG_INIT_UPD_ADDR, the base station uses INITREQSIP
and INITREQURL as the source and destination addresses for initially obtaining
a certificate during site deployment and UPDSIP and URL as the source and
destination addresses for updating the certificate automatically and manually
and applying for the certificate manually.When the parameter is set to
CFG_UPD_SIP, the INITREQURL and INITREQSIP do not need to be
configured. When the certificate is obtained initially during site deployment, the
certificate is applied for manually, or the certificate is updated automatically or
manually, the base station uses the UPDSIP and URL address as the source and
destination addresses, respectively.

Certificate Update Indicates the source address for certificate management, such as automatic
Source IP
certificate update, manual certificate update, and manual certificate application.
If the source address for certificate application in site deployment is not
configured, the address will be used as the source address for acquiring the
certificate for the first time.

CA URL During Site Indicates the URL of the CA that is used during site deployment. The URL can
Deployment
be either an HTTP or HTTPS URL. In the URL, the IP address must be a valid
IP address, and the default port number is 80 for HTTP or 443 for HTTPS. This
parameter is mandatory when the CA uses different URLs during site
deployment or certificate update.

Source IP for Applying Indicates the source IP address for the BS to access the CA and to initially obtain
for a Certificate During
Site Deployment a certificate. This parameter is mandatory when the CA uses different URLs in
the following scenarios:
-The BS initially obtains a certificate during site deployment.
-A certificate is updated.

5.7.1.6.1.8 CERTCHKTSK
TRANSPORT
+-CERTCHKTSK

Description
The CERTCHKTSK MO defines a certificate validity checking task, in which a BS periodically
checks whether activated device certificates are valid. If an activated device certificate has
expired or is about to expire, the BS automatically updates the certificate by using proxy or
Certificate Management Protocol (CMP).

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST CERTCHKTSK Use this command to list configuration information about all certificate validity
checking task.

SET CERTCHKTSK Use this command to set the certificate validity checking task.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Certificate Validity Indicates whether a task of certificate validity checking is started.


Period Checking

Checking Period Indicates the interval between certificate validity checking tasks.

Alarm Threshold Indicates the threshold for a certificate expiration alarm. If the eNodeB detects
that the interval between its current time and the expiration date of an activated
device certificate is shorter than the threshold, an Imminent Certificate Expiry
alarm is reported.
Table 2 Related parameters

Parameter Description

Update Method Indicates the method for updating a certificate that has expired or is about to
expire. There are two methods: proxy and CMP. If the proxy method is used, the
BS uses the M2000 as the proxy to update the certificate from the Certificate
Authority (CA). If the CMP method is used, the BS directly updates the
certificate from the CA.

5.7.1.6.1.9 CERTDEPLOY
TRANSPORT
+-CERTDEPLOY

Description

The CERTDEPLOY MO specifies the number of the slot where a certificate is to be deployed
and configuration and maintenance commands should be delivered. Other certificate-related
MOs are dependent on this MO.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the HAGRP MO:


- In one logical protection group, SN in an HAGRP MO must be the same as that in a
CERTDEPLOY MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

DSP CERTSYNCINFO Use this command to query the certificate synchronization information.

DSP DIAGNOSE If the diagnosis type is set to CERT, use this command to query errors generated
during the execution of the ADD CRLTSK and SET CERTCHKTSK commands.If the
diagnosis type is set to IKENEGO, use this command to query IKE/IPSec
negotiation errors in security networking scenarios.If the diagnosis type is set to
SCTP, use this command to query information about disconnected SCTP links.

LST CERTDEPLOY Use this command to list where a certificate is configured.

SET CERTDEPLOY Use this command to set where a certificate is configured.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Certification Deploy Indicates the deployment position of a digital certificate. If this parameter is set
Position Type
to DEFAULT, the certificate is configured on the main control board. If this
parameter is set to SPECIFIC, the certificate is configured on the board in the
specified slot.

Cabinet No. Indicates the number of the cabinet where a board is located.

Subrack No. Indicates the number of the subrack where a board is located.

Slot No. Indicates the number of the slot where a board is located.

5.7.1.6.1.10 CERTMK
TRANSPORT
+-CERTMK

Description
A CERTMK MO defines a verified device certificate. This device certificate identifies a BS
during negotiation.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD CERTMK Use this command to add a device certificate.

DSP CERTMK Use this command to query the status of device certificates.

LST CERTMK Use this command to list the configurations of device certificates.

RMV CERTMK Use this command to remove a device certificate and the corresponding
certificate file.

TST CERT Use this command to test the validity of the certificates that are configured on
the BS before delivery. These certificates are a device certificate named
appcert.pem and a trusted certificate named caroot.pem.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Certificate File Name Indicates the file name of a device certificate. The file name cannot include any
of the following characters: backslashes (\), slashes (/), colons (:), asterisks (*),
question marks (?), double quotation marks ("), left angle brackets (<), right
Table 2 Related parameters

Parameter Description

angle brackets (>), and bars (|).

Status Indicates the status of a device certificate.

Serial Number Indicates the serial number of a device certificate.

Common Name Indicates the common name of a device certificate.

Issuer Indicates the issuer of a device certificate.

Expiration Date Indicates the expiration date of a device certificate.

Effective Date Indicates the date when a device certificate begins to take effect.

5.7.1.6.1.11 CERTREQ
TRANSPORT
+-CERTREQ

Description

The CERTREQ MO consists of the parameters related to the registration information that a BS
uses to apply to the Certificate Authority(CA) for a device certificate.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

CRE CERTREQFILE Use this command to create or update the request file for a device certificate
based on the configured registration information. After the request file is
created, you can run the ULD CERTFILE command to upload the request file to a
specified FTP server.

DSP CMPSESSION Use this command to query the status of CMP sessions. A CMP session is used
by the BS to apply for a new device certificate or to update a device certificate.

LST CERTREQ Use this command to list the registration information used to create the
certificate request.

MOD CERTREQ Use this command to modify the registration information used to create the
certificate request.

REQ DEVCERT Use this command to apply for a new device certificate from a certificate
authority(CA) by starting a Certificate Management Protocol (CMP) session.
After the BS successfully obtains a device certificate, users can list the
configuration or query the status of the certificate by running the LST CERTMK or
DSP CERTMK command, respectively. After a CMP session is started, its status
can be queried by running the DSP CMPSESSION command.

STP CMPSESSION Use this command to stop a pending Certificate Management Protocol (CMP)
session.

UPD DEVCERT Use this command to update a device certificate by starting a Certificate
Management Protocol (CMP) session. After a CMP session is started, its status
can be queried by running the DSP CMPSESSION command.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Common Name Indicates the common name of the certificate request file, which can be the
electronic serial number (ESN), media access control (MAC) address, or IP
address of a board.

Common Name Indicates the additional information about a certificate common name. The
Additional Info.
Table 2 Related parameters

Parameter Description

information will be added behind the value of the COMMNAME parameter to


compose a complete common name for a certificate request file. The default
value is .huawei.com. A space is not supported before the value of this
parameter, that is, a space is not supported before the character string. However,
to meet requirements of consistency checks performed by some CA servers to
the certificate common name in a certificate request packet and that in a Huawei
device certificate, the certificate common name in a certificate request packet is
displayed as "Board ESN"+space+"Common Name Additional Info" only when
the certificate common name in a Huawei device certificate is "Board
ESN"+space+"Common Name Additional Info". For example, when the value of
this parameter is "eNodeB" and the certificate common name in a Huawei
device certificate is "ESN eNodeB", a space is automatically added before
"eNodeB", that is, the certificate common name in a certificate request packet is
displayed as "ESN eNodeB".

Country Indicates the country where a BS is located.

Organization Indicates the organization that owns a BS.

Organizational Unit Indicates the organization unit that owns a BS.

State or Province Indicates the state or province where a BS is located.

Locality Indicates the location of a BS.

Key Usage Indicates the usage for a key, including KEY_AGREEMENT (key negotiation),
DATA_ENCIPHERMENT (data encryption), KEY_ENCIPHERMENT (key
encryption), and DIGITAL_SIGNATURE (digital signature). This parameter can
be set to one or multiple values.

Signature Algorithm Indicates the signature algorithm for a certificate request file. The signature
algorithm can be Secure Hash Algorithm 1 (SHA1), Message-Digest Algorithm
5 (MD5) or Secure Hash Algorithm 256 (SHA256).

Key Size Indicates the length of a key, which can be 1024 bits or 2048 bits.

Local Name Indicates the local name of a BS. This parameter is used to generate the DNS
name of the subject alternative name of a certificate, so as to verify the peer's
identification in IKE negotiation. If this parameter is not configured, the BS
automatically uses the common name and its additional information to generate
the DNS name.

Local IP Indicates the IP address of the subject alternative name of a certificate.


5.7.1.6.1.12 CFMBNDIP
TRANSPORT
+-CFMMD
+-CFMMA
+-CFMRMEP
+-CFMBNDIP

Description

A CFMBNDIP MO indicates the binding between a Remote Maintenance association End Point
(RMEP) and an IP address.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
CFMRMEP

Relation with the CFMBNDIP MO:


- A maximum of 256 CFMBNDIP MOs can be configured on a board.
- A maximum of four IP addresses can be bound to a CFMRMEP MO.
- The BNDIP to any two CFMRMEP MOs which are in the same routing domain in the same
CFMMA MO must be different.
- If MDNAME and MANAME in a CFMMEP MO are the same as MDNAME and
MANAME in a CFMBNDIP MO, respectively, the port configured for the CFMMEP MO
cannot be an ETHPORT MO in an ETHTRK MO.
Relation with the DEVIP MO:
- BNDIP in a CFMBNDIP MO must be different from IP in a DEVIP MO in the same
routing domain.
Relation with the VRF MO:
- The VRF instance used by a CFMBNDIP MO must have been configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD CFMBNDIP Use this command to add a CFM binding IP address. The binding address can
also be used for routes.

LST CFMBNDIP Use this command to list the configuration of the CFM binding IP address.

RMV CFMBNDIP Use this command to remove a CFM binding IP address.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

MD Name Indicates the name of the MD to which the RMEP belongs.

MA Name Indicates the name of the MA to which the RMEP belongs.

RMEP ID Indicates the RMEP ID.

VRF Index Indicates the index of a VRF instance. The NodeB currently supports default
routes domain only (the VRF index is 0).

IP Address Indicates the IP address at the Ethernet port or Ethernet trunk corresponding to
the RMEP. The IP address bound to the remote MEP cannot be the same as the
existing local IP address or any IP address of an effective physical or loopback
port. The bound IP address cannot be the same as the local IP address
dynamically negotiated on the PPP/MLPPP link. When the IP address is bound,
the existing IP address of the system may conflict with the IP address to be
configured, run the LST/DSP (DEVIP, OMCH, PPPLNK, LOCALIP, MPGRP,
or IPRT) command to query the IP address of the system (such as device IP
address, local IP address of the remote maintenance channel, local IP address of
the PPP link, IP address of the local maintenance channel, local IP address of the
MLPPP group, or the next hop IP address) that conflicts with the IP address to
be bound. The fault needs to be cleared manually.

5.7.1.6.1.13 CFMMA
TRANSPORT
+-CFMMD
+-CFMMA
+-CFMMEP[0~1]
+-CFMRMEP[0~64]

Description

The CFMMA MO, a Maintenance Association (MA) for connectivity check (CC), is a set of
maintenance points in a maintenance domain (MD). The MA is identified by MD name and MA
name.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
CFMMD

Possible children:
CFMMEP[0~1];CFMRMEP[0~64]

Relation with the HAGRP MO:


- In one logical protection group, SN in an HAGRP MO must be the same as that in a
CFMMA MO.
Relation with the CFMMA MO:
- In a CFMMA MO, if BNDVLAN is set to YES, VLANID in the CFMMA MO must be
different from that in other CFMMA MOs.
Relation with the GTRANSPARA MO:
- if OAMTYPE of GTRANSPARA is set to ITU_T_Y1731,the length of MANAME in the
CFMMA cannot exceed 13 bytes.
- if OAMTYPE of GTRANSPARA is set to ITU_T_Y1731,MANAME in the CFMMA
must be different from each other.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD CFMMA Use this command to add a connectivity fault management (CFM) maintenance
association (MA).

DSP CFMMA Use this command to query the status of a maintenance association (MA).

LST CFMMA Use this command to list the configuration of an CFM MA.

MOD CFMMA Use this command to modify the configuration of a CFM Maintenance
Association (MA).

RMV CFMMA Use this command to remove a maintenance association (MA).

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

MD Name Indicates the name of the MD to which the MA belongs.

MA Name Indicates the name of the MA.

Cabinet No. Indicates cabinet number of the board to which the MA belongs.

Subrack No. Indicates subrack number of the board to which the MA belongs.

Slot No. Indicates slot number of the board to which the MA belongs.

Binding VLAN Indicates whether the MA is associated with the VLAN.

VLAN ID Indicates the ID of the VLAN with which the MA is associated.

VLAN Priority Indicates the priority of the VLAN with which the MA is associated.

CCM TX Interval Indicates the interval at which the CFM MA transmits continuity check
messages (CCMs).

Number of MEPs Indicates the number of local MEPs in an MA.


Table 2 Related parameters

Parameter Description

Number of RMEPs Indicates the number of RMEPs in an MA.

MEP List Indicates the list of local MEPs in an MA.

RMEP List Indicates the list of RMEPs in an MA.

5.7.1.6.1.14 CFMMD
TRANSPORT
+-CFMMD
+-CFMMA[0~32]

Description

A CFMMD MO consists of the parameters related to a Connectivity Fault Management (CFM)


maintenance domain (MD). An MD specifies the coverage of an Ethernet network where CFM is
performed. The boundaries of the network are defined by maintenance association end points
(MEPs) that are configured on ports. An MD is identified by the MD name.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Possible children:
CFMMA[0~32]

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD CFMMD Use this command to add a connectivity fault management (CFM) maintenance
domain (MD).

DSP CFMMD Use this command to query the status of one or all CFM MDs.

LST CFMMD Use this command to list the configuration of a CFM MD.

RMV CFMMD Use this command to remove a CFM MD.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

MD Name Indicates the name of the CFM MD.

MD Level Indicates the level of the CFM MD.

MA Number Indicates the number of MAs in a CFMMD.

MA List Indicates the list of all MAs in a CFMMD.

5.7.1.6.1.15 CFMMEP
TRANSPORT
+-CFMMD
+-CFMMA
+-CFMMEP

Description

The CFMMEP MO consists of the parameters related to the local maintenance association end
point (MEP). Local MEPs and remote MEPs (RMEPs) determine the scope and boundaries of a
maintenance domain (MD). The MD and MA to which MEPs belong determine the VLAN
attributes and level for messages sent from the MEPs.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
CFMMA

Relation with the CFMRMEP MO:


- Under a CFMMA MO, MEPID in the CFMMEP MO and RMEPID in the CFMRMEP
MO cannot be set to the same value.
- In a CFMMA MO, CFMMEP MO must be configured when a CFMRMEP MO has been
configured.
- RMEPID and MEPID in the CFMRMEP MO and CFMMEP MO must be unique in the
CFM MA.
Relation with the CFMMEP MO:
- Only one CFMMEP MO can be configured in a CFMMA MO.
- The cabinet number, subrack number, and slot number in a CFMMEP MO must be the same
as those in the associated CFMMA MO.
- If the parent CFMMA MO of a CFMMEP MO is bound to a VLAN, the LEVEL value in
the CFMMD MO to which the CFMMEP MO belongs must be greater than that of the
CFMMD MO containing any CFMMEP MO not bound to a VLAN.
- Before adding a CFMMEP MO to an ETHPORT MO in an ETHTRK MO, ensure that
LEVEL in the CFMMD MO to which the CFMMEP MO belongs is smaller than or equal to
that in the CFMMD MO to which the CFMMEP MO configured for the ETHTRK MO
belongs.
- When adding a CFMMEP MO to an ETHPORT MO that belongs to an ETHTRK MO,
CCMINTL in the CFMMD MO containing the CFMMEP MO in the ETHTRK MO must be
larger than CCMINTL in the CFMMD MO containing the CFMMEP MO in the
ETHTRKLNK MO.
Relation with the ETHTRK MO:
- Before configuring a CFMMEP MO on an ETHTRK MO, ensure that the ETHTRK MO
has been configured.
Relation with the ETHTRKLNK MO:
- Before an CFMMEP MO is configured on an ETHTRK MO or on an ETHPORT MO that
is not added to an ETHTRK MO, BNDVLAN in the parent CFMMA MO of the CFMMEP
MO must be set to YES.
- If an ETHPORT MO configured with a CFMMEP MO has joined an ETHTRK MO, the
CFMMA MO to which the CFMMEP MO belongs cannot be associated with any VLAN.
Relation with the PORTSECURITY MO:
- The ETHPORT MO that is associated with a CFMMEP MO must meet either of the
following conditions: (1) No PORTSECURITY MO is associated with the ETHPORT MO; (2)
A PORTSECURITY MO is associated with the ETHPORT MO, but SWITCH in the
PORTSECURITY MO is set to ENABLE.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ACT CFMCC Use this command to activate continuity check (CC) for the connectivity fault
management (CFM) maintenance association end point (MEP).

ACT ETHDM Use this command to activate the measurement of bidirectional delay and jitter
on the Ethernet.

ACT ETHLM Use this command to activate the packet loss detection function on the Ethernet.

ADD CFMMEP Use this command to add a local maintenance association end point (MEP).

CFMPING Use this command to start the CFM link loopback.

CFMTRACE Use this command to start the CFM link trace.

DEA CFMCC Use this command to deactivate continuity check (CC) for the local connectivity
fault management (CFM) maintenance association end point (MEP).

DEA ETHDM Use this command to deactivate the measurement of bidirectional delay and
jitter on the Ethernet.

DEA ETHLM Use this command to deactivate the packet loss detection function on the
Ethernet.

DSP CFMMEP Use this command to query the status of the local maintenance association end
point (MEP).

DSP ETHDM Use this command to query the bidirectional delay and jitter on the Ethernet.

DSP ETHLM Use this command to query the packet loss information on the Ethernet.
Table 1 Related MML commands

MML Command Function

LST CFMMEP Use this command to list the configuration of the local maintenance association
end point (MEP).

RMV CFMMEP Use this command to remove a local connectivity fault management (CFM)
maintenance association end point (MEP).

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

MD Name Indicates the name of the MD to which the MEP belongs.

MA Name Indicates the name of the MA to which the MEP belongs.

MEP ID Indicates the MEP ID.

Cabinet No. Indicates cabinet number of the board to which the MEP belongs.

Subrack No. Indicates subrack number of the board to which the MEP belongs.

Slot No. Indicates slot number of the board to which the MEP belongs.

Subboard Type Indicates the type of subboard on the board where the MEP is located.

Port Type Indicates the port type of MEP.

Port No. Indicates the port number of the MEP.

CC Switch Indicates whether to enable the continuity check (CC) of the CFM.

Binding VLAN Indicates the ID of a VLAN of the MA to which the MEP belongs.

VLAN ID Indicates the ID of a VLAN of the MA to which the MEP belongs.

VLAN Priority Indicates the priority of a VLAN of the MA to which the MEP belongs.

Number of TX CCM Indicates the number of transmitted Connectivity Check (CC) packets.
Table 2 Related parameters

Parameter Description

PDUs

Number of RX CCM Indicates the number of received Connectivity Check (CC) packets.
PDUs

Number of TX Indicates the number of transmitted loopback packets.


Loopback PDUs

Number of RX Indicates the number of received loopback packets.


Loopback PDUs

Number of TX Link Indicates the number of transmitted traced over packets.


Trace PDUs

Number of RX Link Indicates the number of received traced over packets.


Trace PDUs

Tx DMM Frames Indicates the number of sent DMM frames.

Rx DMR Frames Indicates the number of received DMR frames.

Jitter Std Deviation Indicates the jitter standard deviation. This parameter measures the standard
deviation of jitters sampled in the latest measurement period of 5s compared
with the average jitter.

RTT Sum Indicates the accumulated RTT delay in the latest measurement period of 5s.

Number of TX Success Indicates the number of transmitted packets CFM packets.


CFM PDUs

Number of RX Success Indicates the number of transmitted packets CFM packets.


CFM PDUs

Number of TX Dropped Indicates the number of transmitted packets CFM packets discarded.
CFM PDUs

Number of RX Dropped Indicates the number of received packets CFM packets discarded.
CFM PDUs

Local Tx Frames Indicates the number of frames sent by the local end in the activation
period.When the TX and RX frame counters flip or the counters are reset, the
measurement result of this parameter is lost by one time.

Remote Rx Frames Indicates the number of frames received by the peer end in the activation
period.When the TX and RX frame counters flip or the counters are reset, the
measurement result of this parameter is lost by one time.

Remote Tx Frames Indicates the number of frames sent by the peer end in the activation
period.When the TX and RX frame counters flip or the counters are reset, the
measurement result of this parameter is lost by one time.
Table 2 Related parameters

Parameter Description

Local Rx Frames Indicates the number of frames received by the local end in the activation
period.When the TX and RX frame counters flip or the counters are reset, the
measurement result of this parameter is lost by one time.

Down Lost Frames Indicates the absolute difference between the number of frames sent by the local
end and the number of frames received by the peer end in the activation
period.Generally, the number of frames sent is greater than or equal to the
number of frames received, and this parameter indicates the severity of packet
loss. In the case of transmission disorder, abnormal measurement result of the
local or peer end, or monitoring policy inconsistency, the number of frames sent
may be smaller than the number of frames received. In this case, this parameter
indicates the severity of abnormal measurement.

Upper Lost Frames Indicates the absolute difference between the number of frames sent by the local
end and the number of frames received by the peer end in the activation
period.Generally, the number of frames sent is greater than or equal to the
number of frames received, and this parameter indicates the severity of packet
loss. In the case of transmission disorder, abnormal measurement result of the
local or peer end, or monitoring policy inconsistency, the number of frames sent
may be smaller than the number of frames received. In this case, this parameter
indicates the severity of abnormal measurement.

Tx LMM Frames Indicates the number of sent LMM frames.

Rx LMR Frames Indicates the number of received LMR frames.

Measurement State Indicates the state of ITU-T Y.1731 performance measurement.

5.7.1.6.1.16 CFMRMEP
TRANSPORT
+-CFMMD
+-CFMMA
+-CFMRMEP
+-CFMBNDIP[0~4]

Description
A CFMRMEP MO consists of parameters related to a remote maintenance association end point
(RMEP). RMEPs and local maintenance association end point (MEPs) together determine the
scope and boundaries of a maintenance domain (MD). The MD and MA to which MEPs belong
determine the VLAN attributes and level for messages sent from the MEPs.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
CFMMA

Possible children:
CFMBNDIP[0~4]

Relation with the CFMRMEP MO:


- A maximum of 64 CFMRMEP MOs can be configured on a board.
Relation with the CFMMEP MO:
- Under a CFMMA MO, MEPID in the CFMMEP MO and RMEPID in the CFMRMEP
MO cannot be set to the same value.
- In a CFMMA MO, CFMMEP MO must be configured when a CFMRMEP MO has been
configured.
- RMEPID and MEPID in the CFMRMEP MO and CFMMEP MO must be unique in the
CFM MA.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD CFMRMEP Use this command to add a remote maintenance association end point (RMEP).

DSP CFMRMEP Use this command to query the status of the Remote maintenance association
end point (RMEP).

LST CFMRMEP Use this command to list the configuration of the remote maintenance
association end point (RMEP).
Table 1 Related MML commands

MML Command Function

RMV CFMRMEP Use this command to remove a remote maintenance association end point
(RMEP).

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

MD Name Indicates the name of the MD to which the RMEP belongs.

MA Name Indicates the name of the MA to which the RMEP belongs.

RMEP ID Indicates the RMEP ID.

MAC Address Indicates the MAC address of the RMEP. It must be a valid unicast address in
the format of XXXX-XXXX-XXXX. The MAC address of the RMEP can be
obtained from the MAC address field carried in the CCM message. If the MAC
address configured by the user is different from that carried in the CCM
message, the MAC address carried in the MAC message prevails.

Status Indicates the status of the RMEP.

Actual MAC Address Indicates the actual MAC address of the RMEP. The format is XXXX-XXXX-
XXXX.

Binding VLAN Indicates the priority of a VLAN of the MA to which the RMEP belongs.

VLAN ID Indicates the ID of a VLAN of the MA to which the RMEP belongs.

Number of RX CCM Indicates the number of received CCM packets from the RMEP.
PDUs

Number of Bound IPs Indicates the number of the IP addresses bound to the RMEP.

IP Address List Indicates the list of the IP addresses bound to the RMEP.
5.7.1.6.1.17 CPBEARER
TRANSPORT
+-CPBEARER

Description

A Control Port (CP) bearer MO consists of the parameters related to bearers for application-layer
control interfaces such as the NodeB Control Port (NCP), Communication Control Port (CCP),
S1, and X2 interfaces.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the SCTPLNK MO:


- If BEARTYPE in a CPBEARER MO is set to SCTP, an SCTPLNK MO whose SCTPNO
is the same as LINKNO in the CPBEARER MO must have been configured.
Relation with the CPBEARER MO:
- If two CPBEARER MOs work in active/standby mode, ensure that BEARTYPE in at least
one CPBEARER MO is not set to SCTP.
- If BEARTYPE in a CPBEARER MO is set to SCTP, the SCTP link specified by SCTPNO
in the associated SCTPLNK MO can carry only one CP bearer.
- If BEARTYPE in a CPBEARER MO is set to SCTP6, the link specified by SCTPNO in
the associated SCTPLNK6 MO can carry only one CP bearer.
- If two CPBEARER MOs work in active/standby mode, ensure that BEARTYPE in at least
one CPBEARER MO is not set to SCTP6.
- If two CPBEARER MOs work in active/standby mode, ensure that BEARTYPE in at least
one CPBEARER MO is not set to SCTP6 or SCTP.
- If BEARTYPE in a CPBEARER MO is set to SAAL, a SAALLNK MO whose SAALNO
is the same as LINKNO in the CPBEARER MO must have been configured.
Relation with the SCTPLNK6 MO:
- If BEARTYPE in a CPBEARER MO is set to SCTP6, the SCTPLNK6 MO whose
SCTPNO is the same as LINKNO in the CPBEARER MO must have been configured.
Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD CPBEARER Use this command to add Control Port Bearer.

DSP CPBEARER Use this command to query the status of Control Port Bearer.

LST CPBEARER Use this command to list the configuration of Control Port Bearer.

MOD CPBEARER Use this command to modify the configuration of a Control Port Bearer.

RMV CPBEARER Use this command to remove Control Port Bearer.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

CP Bear No. Indicates the number of a Control Port (CP) bearer.

Flag Indicates whether the transport channel carried on the CP bearer is a master or
slave channel.

Bear Type Indicates the type of CP bearer.The NodeB currently does not support SCTP6.
The eNodeB currently does not support SAAL.

Link No. Indicates the number of a link carried on the CP bearer.

Port Status Indicates the status of a CP bearer.

Used Status Indicates whether the CP bearer is in use.

Control Mode Indicates whether the object can be modified or deleted by the system. The value
MANUAL_MODE means that only the user can modify or delete the object.
The value AUTO_MODE means that both the system and the user can modify or
delete the object.
Table 2 Related parameters

Parameter Description

Auto Config Flag Indicates whether the object is created by the system. MANUAL_CREATED
means that the object is configured by the user manually. AUTO_CREATED
means that the object is created by the system.

5.7.1.6.1.18 CRL
TRANSPORT
+-CRL

Description

A CRL MO defines a certificate revocation list (CRL). The list records all certificates that are
revoked before their expiration due to key disclosure or other reasons.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD CRL Use this command to add a CRL.

DLD CERTFILE Use this command to download a certificate file from an FTP server to the
directory that the BS uses to store all certificate files downloaded from FTP
servers.
Table 1 Related MML commands

MML Command Function

DSP CRL Use this command to query the status of CRLs.

LST CERTFILE Use this command to list all certificate files in the BS. The certificate files in the
download directory, and those added to the configured device certificate, trust
certificate, cross-certificate, and CRL.downloaded from FTP servers.

LST CRL Use this command to list the configurations of CRLs.

RMV CERTFILE Use this command to remove a certificate file from the BS.downloaded from
FTP servers.

RMV CRL Use this command to remove a CRL and the corresponding CRL file.

ULD CERTFILE Use this command to upload a certificate file to the specified FTP server
directory by using FTP.The current version only supports the upload of
certificate request file.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

CRL File Name Indicates the file name of a CRL. The file name cannot include any of the
following characters: backslashes (\), slashes (/), colons (:), asterisks (*),
question marks (?), double quotation marks ("), left angle brackets (<), right
angle brackets (>), and bars (|).

Status Indicates the loading status of a CRL.

Issuer Indicates the issuer of a CRL.

Next Update Indicates the next update time of the CRL.

This Update Indicates the current update time of the CRL.

5.7.1.6.1.19 CRLPOLICY
TRANSPORT
+-CRLPOLICY

Description

The CRLPOLICY MO defines a policy to use CRLs. It determines which action to take when a
peer device certificate is revoked.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST CRLPOLICY Use this command to list the configuration of the policy to use CRLs.

SET CRLPOLICY Use this command to set the policy to use CRLs.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

CRL Using Policy Indicates the policy type. There are three policies to use CRLs. The value
NOVERIFY indicates that the BS does not perform CRL-based certificate
checks on the peer device. The value ALARM indicates that the BS performs
CRL-based certificate checks on the peer device and reports ALM-26832 Peer
Certificate Expiry if the peer certificate has been revoked. The value
Table 2 Related parameters

Parameter Description

DISCONNECT indicates that the BS performs CRL-based certificate checks on


the peer device. If the BS finds that the peer certificate has been revoked, the BS
stops the link negotiation with the peer device and reports ALM-26832 Peer
Certificate Expiry. If the BS finds that the CRL expires, the BS stops the link
negotiation with the peer device.

5.7.1.6.1.20 CRLTSK
TRANSPORT
+-CRLTSK

Description

A CRLTSK MO defines a CRL check task, in which a BS periodically obtains a CRL from the
File Transfer Protocol (FTP) server or Lightweight Directory Access Protocol (LDAP) server.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD CRLTSK Use this command to add a task of periodically updating a CRL.

LST CRLTSK Use this command to list the configurations of tasks of periodically updating
Table 1 Related MML commands

MML Command Function

CRLs.

RMV CRLTSK Use this command to remove a task of periodically updating a CRL.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

IP Address Indicates the IP address of an FTP server or LDAP server.

User Name Indicates the user name used to log in to an FTP server or LDAP server.

Password Indicates the password used to log in to an FTP server or LDAP server.

Port No. Indicates the port number of an LDAP server.

File Name Indicates the file name of a CRL. The file name cannot include any of the
following characters: backslashes (\), slashes (/), colons (:), asterisks (*),
question marks (?), double quotation marks ("), left angle brackets (<), right
angle brackets (>), and bars (|).

Using CRL's Next Indicates whether to update the CRL at the next update time specified in the
Update
CRL that is obtained during the latest update. If this parameter is set to
ENABLE, the BS automatically updates the CRL when the next update time
specified in the CRL arrives. If this parameter is set to DISABLE, the BS
automatically updates the CRL based on the configured updating period.

CRL Updating Period Indicates the interval at which the BS automatically obtains the CRL from the
FTP server or LDAP server.

Task ID Indicates the ID of the task for periodically obtaining the CRL.

Access Method Indicates the method using which the BS periodically obtains a CRL.

Distinguish Name Indicates the name of a node found in an LDAP server.

Source IP Indicates the source IP address for downloading CRLs. If this parameter is set to
Table 2 Related parameters

Parameter Description

0.0.0.0, the BS automatically uses the OM IP address of the main control board
as the source IP to access the CA and to update a certificate.

5.7.1.6.1.21 CROSSCERT
TRANSPORT
+-CROSSCERT

Description

A CROSSCERT MO defines a cross-certificate. The cross-certificate is used for cross-


certification between Certificate Authorities (CAs) so that a BS can authenticate a peer device
under a different CA.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD CROSSCERT Use this command to add a cross-certificate.

DSP CROSSCERT Use this command to query the status of cross-certificates.

LST CROSSCERT Use this command to list the configurations of all cross-certificates.
Table 1 Related MML commands

MML Command Function

RMV CROSSCERT Use this command to remove a cross-certificate and the corresponding
certificate file.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Certificate File Name Indicates the name of the cross-certificate. The file name cannot include any of
the following characters: backslashes (\), slashes (/), colons (:), asterisks (*),
question marks (?), double quotation marks ("), left angle brackets (<), right
angle brackets (>), and bars (|).

Serial Number Indicates the serial number of the cross-certificate.

Common Name Indicates the common name of the cross-certificate.

Issuer Name Indicates the issuer of the cross-certificate.

Expiring Date Indicates the expiration date of the cross-certificate.

Status Indicates the loading status of the cross-certificate.

Effective Date Indicates the date when the cross-certificate begins to take effect.

5.7.1.6.1.22 DEVIP
TRANSPORT
+-DEVIP

Description

A DEVIP MO consists of the parameters related to a device IP address of an IP port. An IP port


can be an Ethernet port, loopback port, or a port that carries a PPP link, MP group, or Ethernet
trunk. A device IP address of a loopback port is also called a loopback IP address or logical IP
address. Unlike other types of IP port, a loopback port is a virtual port. A loopback IP address
mainly serves as the destination IP address of an active/standby route or as the IP address at the
internal layer of an IPSec tunnel. The device IP addresses of IP ports of other types are called
interface IP addresses. The IP address takes effect immediately upon the completion of
configuration.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the IPCLKLNK MO:


- Before creating an IPCLKLNK MO, the corresponding DEVIP MO must have been
configured. The corresponding relationship of the two MOs is as follows: 1. CN, SRN, and SN
in the IPCLKLNK MO must be the same as CN, SRN, and SN respectively in the DEVIP MO.
2. CIP in the IPCLKLNK MO must be the same as IP in the DEVIP MO.
- Before creating an IPCLKLNK MO, the corresponding DEVIP MO must have been
configured. In addition, PT in the DEVIP MO must be set to LOOPINT, ETH, ETHTRK, or
- SUBIF.
Relation with the HAGRP MO:
- In one logical protection group, SN in an HAGRP MO must be the same as that in a DEVIP
MO.
Relation with the BFDSESSION MO:
- If a BFDSESSION MO and a DEVIP MO are in the same routing domain, DSTIP in the
BFDSESSION MO must be different from IP in the DEVIP MO.
Relation with the UDPSESSION MO:
- PEERIP in an UDPSESSION MO must be different from IP in a DEVIP MO.
Relation with the DEVIP MO:
- A maximum of eight DEVIP MOs can be configured on an Ethernet port, a sub-interface, or
a port carrying an Ethernet trunk.
- A maximum of seven DEVIP MOs can be configured on a port that carries a PPP link or MP
group.
- A maximum of two DEVIP MOs can be configured on a loopback port.
- Any two DEVIP MOs in the same routing domain must have different IP values.
- IP in any two DEVIP MOs of two boards that are in the same routing domain must be on
different network segments.
- For two DEVIP MOs that are in the same routing domain and are configured on different
ports of the same board, IP in the two MOs must be on different network segments if both of the
following conditions are met: (1) In one DEVIP MO, the port type is set to LOOPINT. (2) In the
other DEVIP MO, the port type is set to PPP or MPGRP.
- On a BS, the sum of DEVIP6 and DEVIP MOs must be smaller than or equal to 128.
- If the port types in two DEVIP MOs that are in the same routing domain and are configured
on different ports of the same board are not set to LOOPINT, IP in the two MOs must be on
different network segments.
- In a routing domain, two DEVIP MOs on different ports of the same board must not be in
the same network segment if the following conditions are met:
- The port type of one MO is LOOPINT, and the port type of the other MO is ETH, ETHTRK,
or SUBIF; the IP of one MO OR the MASK of the other MO is all one, or the IP of one MO
AND the negated MASK of the other MO is all zero.
- In a routing domain, two DEVIP MOs can be in the same network segment if the following
conditions are met:
- The port type of one MO is LOOPINT, and the port type of the other MO is ETH, ETHTRK,
or SUBIF; the loopback interface address is not the broadcast address or network address in the
interface address segment.
Relation with the LOCALIP MO:
- IP in a LOCALIP MO must be different from IP in a DEVIP MO in the same routing
domain.
- IP in a LOCALIP MO must be on a different network segment from IP in a DEVIP MO in
the same routing domain.
Relation with the IPRT MO:
- If an IPRT MO and a DEVIP MO whose PT is set to ETH, ETHTRK, or SUBIF are in the
same routing domain, NEXTHOP in the IPRT MO must be on the same network segment as IP
in the DEVIP MO. In addition, CN, SRN, SN, and SBT in the DEVIP MO must be the same as
CN, SRN, SN, and SBT in the IPRT MO, respectively.
- If an IPRT MO and a DEVIP MO are in the same routing domain, NEXTHOP in the IPRT
MO must be different from IP in the DEVIP MO.
- If RTTYPE and IFT in an IPRT MO are set to IF and TUNNEL, respectively, DSTIP in the
IPRT MO must be different from IP in a DEVIP MO in the same routing domain or from the
logical AND-operation result of IP and MASK.
- If RTTYPE and IFT in an IPRT MO are set to IF and TUNNEL, respectively, DSTIP in the
IPRT MO must be different from IP in a DEVIP MO in the same routing domain.
Relation with the SCTPLNK,PPPLNK,MPGRP MOs:
- Before adding an SCTPLNK MO, ensure that the MPGRP or PPPLNK MO that has the
same combination of cabinet number, subrack number, and slot number as the SCTPLNK MO
has been configured. Alternatively, ensure that the DEVIP, MPGRP, or PPPLNK MO that
meets both of the following conditions has been configured: (1) The DEVIP, MPGRP, or
PPPLNK MO is in the same routing domain as the SCTPLNK MO. (2) LOCIP or SECLOCIP
in the SCTPLNK MO is the same as IP in the DEVIP MO, LOCALIP in the MPGRP MO, or
LOCALIP in the PPPLNK MO.
Relation with the IPPATHRT MO:
- The value of SRCIP in an IPPATHRT MO must be the same as the IP address in a
configured DEVIP MO that meets both of the following conditions: (1) The DEVIP MO is in
the same routing domain as the IPPATHRT MO. (2) The port type in the DEVIP MO is set to
ETH, ETHTRK, LOOPINT, or SUBIF.
- The board whose IP address is used by SRCIP in an IPPATHRT MO must have a DEVIP
MO that meets both of the following conditions: (1) The IP address in the DEVIP MO and
NEXTHOPIP are different but on the same network segment. (2) The DEVIP and IPPATHRT
MOs are in the same routing domain.
- NEXTHOPIP in an IPPATHRT MO cannot be set to a broadcast IP address of the network
segment where the DEVIP MO on the egress port is located, and Network ID and Host ID
cannot be all 0 or all 1.
- If a DEVIP MO and an IPPATHRT MO are in the same routing domain, IP in the DEVIP
MO must be different from NEXTHOPIP in the IPPATHRT MO.
Relation with the IPPATH MO:
- If PT in an IPPATH MO is set to LOOPINT, the corresponding DEVIP MO must have been
configured, and VRFIDX, PT, and PN in the IPPATH MO must be the same as VRFIDX, PT,
and PN in the DEVIP MO, respectively.
- LOCALIP in an IPPATH MO must be the same as a DEVIP MO configured at a physical
port or loopback port of the same board. If LOCALIP in an IPPATH MO is the same as a
DEVIP MO configured at a physical port, PT and PN in the IPPATH MO must be the same as
PT and PN in the DEVIP MO, respectively. Alternatively, LOCALIP in the IPPATH MO must
be the same as LOCALIP in the associated PPPLNK MO or LOCALIP in the associated
MPGRP MO.
- If PT in an IPPATH MO is set to TUNNEL, the DEVIP MO whose PT is set to LOOPINT
and that is in the same routing domain as the IPPATH MO must have been configured.
Relation with the CFMBNDIP MO:
- BNDIP in a CFMBNDIP MO must be different from IP in a DEVIP MO in the same
routing domain.
Relation with the OMCH MO:
- PEERIP in an OMCH MO must be different from IP in a DEVIP MO in the same routing
domain.
Relation with the PPPLNK MO:
- If PT in a DEVIP MO is set to PPP, the associated PPPLNK MO must have been
configured.
- LOCALIP in a PPPLNK MO must be different from IP in a DEVIP MO in the same
routing domain.
- PEERIP in a PPPLNK MO must be different from IP in a DEVIP MO in the same routing
domain.
- LOCALIP in a PPPLNK MO must be on a different network segment from IP in a DEVIP
MO in the same routing domain on another interface.
Relation with the MPGRP MO:
- If PT in a DEVIP MO is set to MPGRP, the associated MPGRP MO must have been
configured.
- If a DEVIP MO and an MPGRP MO are in the same routing domain, IP in the DEVIP MO
must be different from LOCALIP in the MPGRP MO.
- If a DEVIP MO and an MPGRP MO are in the same routing domain, IP in the DEVIP MO
must be different from PEERIP in the MPGRP MO.
- LOCALIP in an MPGRP MO must be on a different network segment from IP in a DEVIP
MO in the same routing domain on another interface.
Relation with the ETHTRK MO:
- If PT in a DEVIP MO is set to ETHTRK, the associated ETHTRK MO must have been
configured.
Relation with the ETHTRKLNK MO:
- A DEVIP MO with PT set to ETH and PN set to the same value as that in an
ETHTRKLNK MO cannot be configured.
Relation with the UDPSESSION,PPPLNK,MPGRP MOs:
- UDPSESSION:LOCALIP in an UDPSESSION MO to be added must have been
configured. That is, for the UDPSESSION, DEVIP, PPPLNK, and MPGRP MOs configured
on the same board, LOCALIP in the UDPSESSION MO must be the same as any of the
following : IP in the DEVIP MO with the same routing domain, LOCALIP in the PPPLNK
MO, and LOCALIP in the MPGRP MO.
Relation with the IPPMSESSION MO:
- If BINDPATH and IPPMTYPE in an IPPMSESSION MO are set to NO and
THREE_TUPLE, respectively, in the same routing domain SBT in any DEVIP MO must be set
to BASE_BOARD or ETH_COVERBOARD.
- If BINDPATH in an IPPMSESSION MO is set to NO, IP in any DEVIP MO in the same
routing domain must be different from PEERIP in the IPPMSESSION MO.
Relation with the IPPMSESSION,PPPLNK,MPGRP MOs:
- If BINDPATH in an IPPMSESSION MO is set to NO, the IP address corresponding to
LOCALIP in the IPPMSESSION MO must have been configured. That is, for the
IPPMSESSION MO, DEVIP MO in the same routing domain, PPPLNK MO, and MPGRP
MO configured on the same board, LOCALIP in the IPPMSESSION MO must be the same as
any of the following: IP in the DEVIP MO; LOCALIP in the PPPLNK MO; or LOCALIP in
the MPGRP MO.
Relation with the IKEPEER MO:
- If LOCALIP in an IKEPEER MO is not set to 0.0.0.0, the DEVIP MO that has the same IP
address as LOCALIP and are in the same routing domain must have been configured.
- When LOCALIP in an IKEPEER MO is not set to 0.0.0.0, PT in a DEVIP MO cannot be
set to PPP or MPGRP if the DEVIP MO has the same IP address as LOCALIP and in the same
routing domain.
Relation with the BFDSESSION,MPGRP,PPPLNK MOs:
- SRCIP in a BFDSESSION MO to be added must have been configured. That is, for the
BFDSESSION, DEVIP, PPPLNK, and MPGRP MOs configured on the same board, SRCIP
in the BFDSESSION MO must be the same as any of the following : IP in the DEVIP MO in
the same routing domain, LOCALIP in the PPPLNK MO, and LOCALIP in the MPGRP MO.
Relation with the PORTSECURITY MO:
- If CN, SRN, SN, SBT, PT, and PN in a DEVIP MO are the same as CN, SRN, SN, SBT,
PT, and PN in a PORTSECURITY MO, respectively, and SWITCH in the PORTSECURITY
MO is set to DISABLE, the DEVIP MO cannot be configured.
Relation with the VLANMAP MO:
- If VLANID in two VLANMAP MOs is the same, NEXTHOPIP in the two MOs must be
on the same egress port.
Relation with the VRF MO:
- If PT in a DEVIP MO is not set to SUBIF or LOOPINT, the VRF instance in a VRF MO
must be set to 0.
- The VRF instance used by a DEVIP MO must have been configured.
Relation with the SUBIF MO:
- If PT in a DEVIP MO is set to SUBIF, the SUBIF MO that uses the same VRF instance as
the DEVIP MO must have been configured.
- If PT in a DEVIP MO is not set to SUBIF or LOOPINT, the SUBIF MO cannot be
configured.
Relation with the SCTPPEER,MPGRP,PPPLNK MOs:
- In a routing domain,SIGIP1V4 in an SCTPPEER MO must be different from
IP,LOCALIP or LOCALIP in a configured DEVIP MO,MPGRP and PPPLNK.
- In a routing domain,SIGIP2V4 in an SCTPPEER MO must be different from
IP,LOCALIP or LOCALIP in a configured DEVIP MO,MPGRP and PPPLNK.
Relation with the USERPLANEHOST,MPGRP,PPPLNK MOs:
- In a routing domain,LOCIPV4 in a USERPLANEHOST MO must be the same as
IP ,LOCALIP or LOCALIP in a configured DEVIP MO ,MPGRP or PPPLNK.
Relation with the USERPLANEPEER,MPGRP,PPPLNK MOs:
- PEERIPV4 in a USERPLANEPEER MO must be different from IP ,LOCALIP or
LOCALIP in a configured DEVIP MO ,MPGRP and PPPLNK.
Relation with the SECURITYPEER MO:
- PEERIKEIPV4 in a SECURITYPEER MO must be different from IP,LOCALIP or
LOCALIP in a configured DEVIP MO,MPGRP and PPPLNK.
Relation with the SECURITYHOST MO:
- LOCIKEIPV4 in a SECURITYHOST MO must be the same as IP in a configured DEVIP
MO.
Relation with the SCTPHOST MO:
- The DEVIP MOs referenced by SIGIP1V4 and SIGIP2V4 of the SCTPHOST MO must be
confiured on the same board.
- In a routing domain,SIGIP1V4 in an SCTPHOST MO must be the same as IP in a
configured DEVIP MO.
- In a routing domain,SIGIP2V4(SIGIP2V4 is not set to 0.0.0.0) in an SCTPHOST MO
must be the same as IP in a configured DEVIP MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD DEVIP Use this command to add a device IP address.

DSP DEVIP Use this command to query the device IP addresses that take effect.

LST DEVIP Use this command to list configured device IP addresses.

RMV DEVIP Use this command to remove a device IP address from a port.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the board where the port is located.

Subrack No. Indicates the subrack number of the board where the port is located.

Slot No. Indicates the slot number of the board where the port is located.

Subboard Type Indicates the type of sub-board on the board where a port is located.

Port Type Indicates the type of the physical port. The NodeB currently does not support
SUBIF.

Port No. Indicates the number of a port.

VRF Index Indicates the index of a VRF instance. The NodeB currently supports default
routes domain only (the VRF index is 0).

IP Address Indicates the IP address configured for the port.

Mask Indicates the subnet mask of the device IP address configured on the port.

5.7.1.6.1.23 DEVIP6
TRANSPORT
+-IPITF6
+-DEVIP6

Description

This MO indicates a device IPv6 address of an IPv6 interface. The device IPv6 address can be a
local IP address of a link or a global unicast address.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
IPITF6

Relation with the IPCLKLNK MO:


- When IPMODE in the IPCLKLNK MO is set to IPV6,the corresponding DEVIP6 MO
must have been configured.The corresponding relationship of the two MOs is as follows: 1. CN,
SRN, and SN in the IPCLKLNK MO must be the same as CN, SRN, and SN respectively in the
DEVIP6 MO. 2. CIPV6 in the IPCLKLNK MO must be the same as IPV6 in the IPITF6 MO.
which is corresponding to DEVIP6 MO.
Relation with the IKEPEER6 MO:
- Before adding an IKEPEER6 MO with LOCALIP set to a value other than 0, ensure that a
DEVIP MO with the same IP address as LOCALIP has been configured.
- REMOTEIP in an IKEPEER6 MO must be different from IPV6 in a DEVIP6 MO.
Relation with the DEVIP6 MO:
- No identical global unicast address can be added, for example, 2001::1/64 and 2001::1/65 are
identical global unicast addresses.
- When the DEVIP6 MO is configured as a global unicast address, the global unicast
addresses of any two IPITF6 MOs cannot have overlapped network segments.
- A maximum of one link-local address can be configured for an IPITF6 MO.
- A maximum of eight DEVIP6 MOs can be configured for an IPITF6 MO.
- On a BS, the sum of DEVIP6 and DEVIP MOs must be smaller than or equal to 128.
Relation with the IPRT6 MO:
- IPV6 in a DEVIP6 MO must be different from NEXTHOPIP in an IPRT6 MO.
- If NEXTHOPIP6TYPE in an IPRT6 MO is set to
IPADDR6_TYPE_GLOBAL_UNICAST, the DEVIP6 MO whose IPV6 has the same prefix as
the global unicast address must have been configured.
Relation with the IPPATH6 MO:
- LOCALIP6 in an IPPATH6 MO must be a locally configured DEVIP6 MO at the
corresponding physical port.
Relation with the OMCH6 MO:
- LOCALIP6 in the OMCH6 MO must be different from IPV6 in a DEVIP6 MO.
- LOCALIP6 in the OMCH6 MO must be on a different network segment from IPV6 in a
DEVIP6 MO.
- PEERIP6 in an OMCH6 MO must be different from IPV6 in a DEVIP6 MO.
Relation with the LOCALIP6 MO:
- IP6 in the LOCALIP6 MO must be different from IPV6 in a DEVIP6 MO.
- IP6 in the LOCALIP6 MO must be on a different network segment from IPV6 in a
DEVIP6 MO.
Relation with the SCTPLNK6 MO:
- LOCIP in an SCTPLNK6 MO must be the same as IPV6 in an existing DEVIP6 MO.
- SECLOCIP in an SCTPLNK6 MO must be the same as IPV6 in an existing DEVIP6 MO.
Relation with the SCTPPEER MO:
- SIGIP1V6 in an SCTPPEER MO must be different from IPV6 in a configured DEVIP6
MO.
- SIGIP2V6 in an SCTPPEER MO must be different from IPV6 in a configured DEVIP6
MO.
Relation with the USERPLANEPEER MO:
- PEERIPV6 in a USERPLANEPEER MO must be different from IPV6 in a configured
DEVIP6 MO.
Relation with the SECURITYPEER MO:
- PEERIKEIPV6 in a SECURITYPEER MO must be different from IPV6 in a configured
DEVIP6 MO.
Relation with the SCTPHOST MO:
- SIGIP1V6 in an SCTPHOST MO must be the same as IPV6 in a configured DEVIP6 MO.
- SIGIP2V6 (SIGIP2V6 is not set to 0:0:0:0:0:0:0:0) in an SCTPHOST MO must be the
same as IPV6 in a configured DEVIP6 MO.
- The DEVIP6 MOs referenced by SIGIP1V6 and SIGIP2V6 of the SCTPHOST MO must
be confiured on the same board.
Relation with the USERPLANEHOST MO:
- LOCIPV6 in a USERPLANEHOST MO must be the same as IPV6 in a configured
DEVIP6 MO.
Relation with the SECURITYHOST MO:
- LOCIKEIPV6 in a SECURITYHOST MO must be the same as IPV6 in a configured
DEVIP6 MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD DEVIP6 Use this command to add a device IPv6 address.

DSP DEVIP6 Use this command to query the device IPv6 addresses configured on IPv6
Table 1 Related MML commands

MML Command Function

interfaces.

LST DEVIP6 Use this command to list the configured device IPv6 addresses.

PING6 Use this command to test the quality of the IPv6 network cable and determine
whether faults exist in the network connections.

RMV DEVIP6 Use this command to remove a device IPv6 address.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Interface Index Indicates the interface index of the device IPv6 address.

IPv6 Address Indicates the device IPv6 address.

Prefix Length Indicates the length of the prefix of the device IPv6 address.

Address Status Indicates the status of the device IPv6 address.

Valid Lifetime Indicates the time interval during which the device IPv6 address is in the valid
state.

Preferred Lifetime Indicates the time interval during which the device IPv6 address is in the
preferred state. Valid states are categorized into the preferred state and the
deprecated state. In the preferred state, an address can be freely used; in the
deprecated state, the connections previously established on this address are still
usable, whereas any connection newly established on this address is not usable.

5.7.1.6.1.24 DHCPRELAYSWITCH
TRANSPORT
+-DHCPRELAYSWITCH

Description

The DHCPRELAYSWITCH MO consists of the parameter related to the Dynamic Host


Configuration Protocol (DHCP) relay function. DHCP messages, such as DHCPDISCOVER,
can be broadcast only within subnets. Therefore, in a tree topology comprised of BSs, an upper-
level BS must act as a DHCP relay for its lower-level BSs. The upper-level BS converts a DHCP
broadcast message from a lower-level BS into a unicast message and sends the message to a
DHCP server. After receiving unicast a response message from the server, the upper-level BS
sends the message to the lower-level BS through the previous port. In this way, cross-subnet
DHCP is implemented for the lower-level BSs.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the setting of the Dynamic Host Configuration
DHCPRELAYSWITCH
Protocol (DHCP) relay switch.

SET Use this command to turn on or turn off the Dynamic Host Configuration
DHCPRELAYSWITCH
Protocol (DHCP) relay switch for the BS. If the switch is turned on, lower-level
BSs can communicate with the DHCP server through this BS.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

DHCP Relay Switch Indicates whether to enable the DHCP relay switch.

5.7.1.6.1.25 DHCPSVRIP
TRANSPORT
+-DHCPSVRIP

Description

The DHCPSVRIP MO provides the IP address of the DHCP server. The DHCPSVRIP MO is
used to specify the DHCP server for the DHCP relay function. Thus, the lower level BS is able to
communicate with the DHCP server through this BS.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD DHCPSVRIP Use this command to add the IP address of a DHCP server.

LST DHCPSVRIP Use this command to list the setting of the DHCP server IP address.

RMV DHCPSVRIP Use this command to remove the IP address of a DHCP server.
Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

DHCP Server IP Indicates the IP address of the DHCP server.


Address

5.7.1.6.1.26 DHCPSW
TRANSPORT
+-DHCPSW

Description

The DHCPSW MO is the switch for the automatic establishment function of the remote
maintenance channel. The automatic establishment of the remote maintenance channel is
implemented by setting up connections with the Network Management System (NMS) by using
the Dynamic Host Configuration Protocol (DHCP) or Bootstrap Protocol (BootP) on all ports.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP DHCPDETECT Use this command to query the delay for automatic establishment of the remote
Table 1 Related MML commands

MML Command Function

maintenance channel.

LST DHCPSW Use this command to list the configuration of the automatic establishment
detection switch for the remote maintenance channel and the configuration of
the VLAN scanning switch in the detection state.

SET DHCPDETECT Use this command to set the delay for automatic detection of the remote
maintenance channel and let the BS exit the steady state. When the remote
maintenance channel stays disconnected for a period of time longer than the
delay specified through DELAYTIME and the service is unavailable, the BS
automatically begins to detect the remote maintenance channel. During the
detection, all the user-defined configurations are removed and the BS
automatically attempts to restore the remote maintenance channel.

SET DHCPSW Use this command to enable or disable detection of automatic establishment of
the remote maintenance channel and to enable or disable VLAN scanning in the
detection state.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

OMCH Auto- Indicates whether to enable detection of automatic establishment of the remote
Establishment Switch
maintenance channel.

Vlanscan Switch Indicates whether to enable VLAN scanning for the base station.

5.7.1.6.1.27 DIFPRI
TRANSPORT
+-DIFPRI

Description
The DIFPRI MO is the Quality of Service (QoS) priorities of different services.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST DIFPRI Use this command to list the settings of priorities for differentiated services.

SET DIFPRI Use this command to set the mapping from traffic types to priorities.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Priority Rule Indicates the rule for prioritizing traffic to meet service requirements. If this
parameter is set to IPPRECEDENCE, the protocol stack of the earlier version is
adopted, which firstly converts a Type of Service (TOS) to a DSCP and then
prioritizes traffic.

Signaling Priority Indicates the priority of signaling. The priority has a positive correlation with the
value of this parameter.

OM High Priority Indicates the priority of the high-level OM data. The priority has a positive
correlation with the value of this parameter.

OM Low Priority Indicates the priority of the low-level OM data, such as the data to be uploaded
or downloaded. The priority has a positive correlation with the value of this
Table 2 Related parameters

Parameter Description

parameter. The low-level OM data includes the packets related to File Transfer
Protocol (FTP).

IP Clock Priority Indicates the priority of the IP clock. If the IP clock that follows the Precision
Time Protocol (PTP) is used, set this parameter to the DSCP of the PTP packets.
If the IP clock that follows the Huawei proprietary protocol is used, set this
parameter to the DSCP of these packets that follow the Huawei proprietary
protocol.

5.7.1.6.1.28 DOT1X
TRANSPORT
+-DOT1X

Description

This MO describes the parameters required during the 802.1x authentication of the BS. When the
BS accesses the network, the 802.1x authentication is initiated according to the configuration of
802.1x if the network supports the 802.1X protocol.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the HAGRP MO:


- In one logical protection group, SN in an HAGRP MO must be the same as that in a
DOT1X MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ACT DOT1X Use this command to activate the 802.1X authentication.

DEA DOT1X Use this command to deactivate the 802.1X authentication.

DSP DOT1X Use this command to query the status of 802.1X.

LST DOT1X Use this command to list the configuration of 802.1X.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet that provides the port on which IEEE
802.1X authentication is configured.

Subrack No. Indicates the number of the subrack that provides the port on which IEEE
802.1X authentication is configured.

Slot No. Indicates the number of the slot that provides the port on which IEEE 802.1X
authentication is configured.

Subboard Type Indicates the type of sub-board that provides the port on which IEEE 802.1X
authentication is configured.

Port No. Indicates the number of the port on which IEEE 802.1X authentication is
configured.

Authentic Method Indicates the IEEE 802.1X authentication method. Currently, only Extensible
Authentication Protocol Transport Layer Security (EAP-TLS), a unidirectional
authentication method, is supported.

Abnormal Packet Indicates the number of abnormal packets received during the 802.1X
Number
authentication.

Fail Number Indicates the number of IEEE 802.1X authentication failures.

Fail Reason Indicates the cause of the latest IEEE 802.1X authentication failure or the latest
Table 2 Related parameters

Parameter Description

unauthentication where the BS does not initiate the authentication. The value of
this parameter is deleted after a successful IEEE 802.1X authentication.

Receive EAP Packet Indicates the number of received Extensible Authentication Protocol (EAP)
Number
messages.

Authentic State Indicates the status of IEEE 802.1X authentication. Possible states are as
follows: UNAUTHENTICATED(Unauthenticated),
AUTHENTICATING(Authenticating), AUTHENTIC_SUCCEED(Authenticate
Succeed), AUTHENTIC_FAIL(Authenticate Fail), and
DHCP_AUTHENTICATING(DHCP Activation Authenticating).

Send EAP Packet Indicates the number of transmitted Extensible Authentication Protocol (EAP)
Number
messages.

Authentic Succeed Indicates the number of successful IEEE 802.1X authentications.


Number

5.7.1.6.1.29 DSCPMAP
TRANSPORT
+-VRF
+-DSCPMAP

Description

An DSCPMAP MO defines the mapping between DSCPs and VLAN priorities. If the VLAN
priority is not specified when configuring a VLANMAP MO, VLAN priorities are specified for
user data based on DSCPMAP rules.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
VRF
Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP DSCPMAP Use this command to display the mapping between DSCPs and VLAN priorities.

LST DSCPMAP Use this command to list the mapping between DSCPs and VLAN priorities.

SET DSCPMAP Use this command to set the mapping between a DSCP and a VLAN priority.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

VRF Index Indicates the index of a VRF instance.

Differentiated Service Indicates the priority of a DSCP. A larger value of this parameter indicates a
Codepoint
higher priority.

VLAN Priority Indicates the priority of a VLAN. A larger value of this parameter indicates a
higher priority.

5.7.1.6.1.30 E1T1
TRANSPORT
+-E1T1

Description

This MO is used to set parameters for an E1/T1 port, including modifying the E1/T1 working
mode and setting the frame format, line code, and clock mode.

Effective Scenario
Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the HAGRP MO:


- In one logical protection group, SN in an HAGRP MO must be the same as that in an E1T1
MO.
Relation with the E1T1 MO:
- A maximum of eight E1T1 MOs with SBT set to BACK_BOARD can be configured on a
BS.
Relation with the PPPLNK MO:
- If SBT in a PPPLNK MO is not set to BACK_BOARD, the associated E1T1 MO must have
been configured.
Relation with the MPLNK MO:
- If SBT in an MPLNK MO is set to BACK_BOARD, the associated E1T1 MO must have
been configured.
Relation with the PORTSECURITY MO:
- When removing an E1T1 MO whose SBT is set to BASE_BOARD or E1_COVERBOARD,
the system automatically removes the PORTSECURITY that depends on the E1T1 MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD BACKE1T1 Use this command to add an E1/T1 port on the backplane.

ADD E1T1 Use this command to add an E1/T1 port.

CHK E1T1CRS Use this command to check an E1/T1 port for crossed pair connections.

DSP E1T1 Use this command to query the E1/T1 port status.

LST BACKE1T1 Use this command to list the configuration of an E1/T1 port configured on the
backplane.
Table 1 Related MML commands

MML Command Function

LST E1T1 Use this command to list the E1/T1 port configuration.

RMV BACKE1T1 Use this command to remove an E1/T1 port from the backplane.

RMV E1T1 Use this command to remove the current configuration of an E1/T1 port and
restore the default configuration of the port.

SET E1T1 Use this command to set an E1/T1 port.

SET E1T1LOP Use this command to set a loopback on an E1/T1 port.

STP E1T1OFFLTST Use this command to stop the E1/T1 offline performance test, summarize the
E1/T1 test data, and report the data to the maintenance terminal.

STP E1T1ONLTST Use this command to stop an E1/T1 online performance test and report the test
data to the LMT.

STR E1T1OFFLTST Use this command to start an E1/T1 offline BER test.

STR E1T1ONLTST Use this command to start an E1/T1 online performance test.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the board where an E1/T1 port is located.

Subrack No. Indicates the subrack number of the board where an E1/T1 port is located.

Slot No. Indicates the slot number of the board where an E1/T1 port is located.

Port No. Indicates the number of the E1/T1 port.

Port Selection Indicates the range of E1/T1 ports. Note that the E1T1 MO with this parameter
set to ALLPORT is actually not created on the BS.

Work Mode Indicates the working mode of the E1/T1 port. This parameter must be set to the
Table 2 Related parameters

Parameter Description

same value as that at the peer end.

Frame Format Indicates the frame format used by the E1/T1 port.

Line Code Indicates the line coding mode of an E1/T1 port.

Clock Mode Indicates the clock mode of the E1/T1 port.


1. If the BS extracts the line clock from the E1/T1 port, the clock mode of the
E1/T1 port must be set to SLAVE. If the BS provides the line clock for the
lower-level equipment through the E1/T1 port, the clock mode of the E1/T1 port
must be set to MASTER. Otherwise, the line clock may fail to work properly.
2. When the E1/T1 port provides an 8K clock reference for the transmission
interface board, the clock mode of the E1/T1 port must be set to SLAVE.
3. The clock modes of E1/T1 ports used by an inter-board MLPPP group cannot
be all set to SLAVE.

Destination Slot No. Indicates the number of the slot housing the destination board whose backplane
has an E1/T1 port.

Link Running Status Indicates the link running status. The link running status is classified into OK,
LOCAL_LOOP, REMOTE_LOOP, PAYLOAD_LOOP, SINGLE_CH_LOOP,
PHYSICAL_LOOP, LOS, AIS, RA, LFA, LMFA, SLIP, BACKUP, and
OTHERS.

Link Test Execution Indicates whether to perform the link test and the test type. The test types are
Status
classified into No Test, Offline Test, and Online Test.

Used Flag Indicates whether the E1/T1 port is used.

Loop Left Time Indicates the remaining loop time of the E1/T1 port.

Subboard Type Indicates the type of sub-board on the board where the E1/T1 port is located.

Actual Work Mode Indicates the actual work mode of the E1/T1 port.

Actual Frame Format Indicates the actual frame format of the E1/T1 port.

Actual Line Code Indicates the actual line coding mode of the E1/T1 port.

5.7.1.6.1.31 E1T1BER
TRANSPORT
+-E1T1BER

Description

The E1T1BER MO is the E1/T1 high BER threshold. It is used to determine whether to report
the E1/T1 high BER alarm.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST E1T1BER Use this command to list the configuration of the E1/T1 BER threshold.

SET E1T1BER Use this command to set the high BER threshold for an E1/T1 port. The E1/T1
BER alarm is determined based on the value of bit errors for the Frame
Alignment Signal (FAS) and Cyclic Redundancy Check (CRC) accumulated
within 15 minutes. If the value exceeds the threshold, the alarm is reported. If
the value falls to a level 20% lower than the threshold, the alarm is cleared.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

E1/T1 BER Threshold Indicates the BER threshold.


Level
5.7.1.6.1.32 EP2RSCGRP
TRANSPORT
+-EP2RSCGRP

Description

The EP2RSCGRP MO is used to configure the mapping between end points and transmission
resource groups. Based on the mapping, data flows are assigned to corresponding transmission
resource groups.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the RSCGRP MO:


- The RSCGRP MO on which an EP2RSCGRP MO depends must have been configured.
Relation with the EP2RSCGRP MO:
- The EPGROUP or USERPLANEPEER MO referenced by an EP2RSCGRP MO must not
be configured on different resource groups of the same physcial port.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD EP2RSCGRP Use this command to add the mapping between the node and the Resource
Group.

LST EP2RSCGRP Use this command to list the mapping between the node and the Resource
Group.
Table 1 Related MML commands

MML Command Function

RMV EP2RSCGRP Use this command to remove the mapping between the node and the Resource
Group.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Mapping Type Indicates two mapping methods between services and transmission resource
groups: end point group mapping and end point mapping. If the parameter is set
to ENDPOINT_GROUP, all end points of the user plane in the end point group
can be added to the specified transmission resource group. If the parameter is set
to ENDPOINT, the specified peer end points of the user plane can be added to
the specified transmission resource group.

End Point ID Indicates the end point group or user plane peer that needs to be added to the
specified transmission resource group.

Cabinet No. Indicates the number of the cabinet where the transmission resource group to
which a node maps is configured.

Subrack No. Indicates the number of the subrack where the transmission resource group to
which a node maps is configured.

Slot No. Indicates the number of the slot where the transmission resource group to which
a node maps is configured.

Subboard Type Indicates the subboard type of the board where the transmission resource group
to which a node maps is configured.

Bearing Port Type Indicates the type of the port where the transmission resource group to which a
node maps is configured.

Bearing Port No. Indicates the number of the port where the transmission resource group to which
a node maps is configured.

Transmission Resource Indicates the bearing type of the transmission resource group to which a node
Group Bear Type
maps.
Table 2 Related parameters

Parameter Description

Transmission Resource Indicates the ID of the transmission resource group to which a node maps.
Group ID

User Label Indicates the description of the end point mapping to resouce group.This
parameter takes effect only in LTE.

5.7.1.6.1.33 EPGROUP
TRANSPORT
+-EPGROUP

Description

The EPGROUP MO consists of transmission end points, which can be control plane end points,
user-plane end points, or both types of end points.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the PACKETFILTER MO:


- If PACKETFILTERSWITCH in an EPGROUP MO is set to ENABLE, a
PACKETFILTER MO whose FM is not set to L2_ACL must have been configured.
Relation with the SCTPHOST MO:
- SCTPHOSTID referenced by SCTPHOSTREFS in an EPGROUP MO must be the same
as SCTPHOSTID in a configured SCTPHOST MO.
- Only one SCTPHOST MO that meets both of the following conditions can be configured:
(1) The SCTPHOST MO has the same SCTP host ID as SCTPHOSTID referenced by
SCTPHOSTREFS in an EPGROUP MO. (2) IPVERSION in the SCTPHOST MO is set to
IPv4.
- Only one SCTPHOST MO that meets both of the following conditions can be configured:
(1) The SCTPHOST MO is referenced by SCTPHOSTID in SCTPHOSTREFS of an
EPGROUP MO. (2) IPVERSION in the SCTPHOST MO is set to IPv6.
Relation with the SCTPPEER MO:
- SCTPPEERID referenced by SCTPPEERREFS in an EPGROUP MO must be the same
as SCTPPEERID in a configured SCTPPEER MO.
Relation with the USERPLANEHOST MO:
- UPHOSTID referenced by USERPLANEHOSTREFS in an EPGROUP MO must be the
same as UPHOSTID in a configured USERPLANEHOST MO.
- If the USERPLANEHOST MOs referenced by the same EPGROUP MO have the same
IPVERSION set to IPv4, the SEGWSWITCH of SECURITYHOST referenced by these
USERPLANEHOST MOs must also be the same.
- In a routing domain,for the USERPLANEHOST MOs referenced by the same EPGROUP
MO with IPVERSION set to IPv4, if the LOCIPV4s of these USERPLANEHOSTs are
referenced by DEVIP MOs ,these IP addresses must be configured on the same board.
- In a routing domain,for the USERPLANEHOST MOs referenced by the same EPGROUP
MO with IPVERSION set to IPv4, the LOCIPV4 of these USERPLANEHOST must be
different.
- If the USERPLANEHOST MOs referenced by the same EPGROUP MO have the same
IPVERSION set to IPv6, the SEGWSWITCH of SECURITYHOST referenced by these
USERPLANEHOST MOs must also be the same.
- In a routing domain,for the USERPLANEHOST MOs referenced by the same EPGROUP
MO with IPVERSION set to IPv6, the LOCIPV6 of these USERPLANEHOST must be
configured on the same board.
- In a routing domain,for the USERPLANEHOST MOs referenced by the same EPGROUP
MO with IPVERSION set to IPv6, the LOCIPV6 of these USERPLANEHOST must be
different.
- In a routing domain,for the USERPLANEHOST MOs referenced by the same EPGROUP
MO with IPVERSION set to IPv4, if the LOCIPV4s of these USERPLANEHOSTs are
referenced by DEVIP MOs or MPGRPMOs,these IP addresses must be configured on the same
board.
- In a routing domain,for the USERPLANEHOST MOs referenced by the same EPGROUP
MO with IPVERSION being IPv4, if the LOCIPV4s of these USERPLANEHOSTs are
referenced by DEVIP MOs or PPPLNKMOs,these IP addresses must be configured on the same
board.
- In a routing domain,for the USERPLANEHOST MOs referenced by the same EPGROUP
MO with IPVERSION set to IPv4, if the LOCIPV4s of these USERPLANEHOSTs are
referenced by MPGRP MOs or PPPLNKMOs,these IP addresses must be configured on the
same board.
Relation with the USERPLANEPEER MO:
- UPPEERID referenced by USERPLANEPEERREFS in an EPGROUP MO must be the
same as UPPEERID in a configured USERPLANEPEER MO.
Relation with the VRF MO:
- The VRF instance used by a EPGROUP MO must have been configured.
Relation with the USERPLANEHOST,USERPLANEPEER,IPPATH MOs:
- When USERPLANEHOST MO and USERPLANEPEER MO are configured in one
EPGROUP MO simultaneously and their IP versions are set to IPv4,these MOs cannot coexist
with IPPATH with PATHTYPE set to FIXED.
Relation with the USERPLANEHOST,USERPLANEPEER,IPPATH6 MOs:
- When USERPLANEHOST MO and USERPLANEPEER MO are configured in one
EPGROUP MO simultaneously and their IP versions are set to IPv6,these MOs cannot coexist
with IPPATH6 with PATHTYPE set to FIXED.
Relation with the USERPLANEHOST,USERPLANEPEER MOs:
- In a routing domain IPv4 configuration,if there are USERPLANEHOST MOs with the same
local IP configured in different EPGROUP,the same USERPLANEPEER MO is only allowed
to be configured in one of these EPGROUP MO.
- In a routing domain IPv6 configuration,if there are USERPLANEHOST MOs with the same
local IPv6 configured in different EPGROUP,the same USERPLANEPEER MO is only
allowed to be configured in one of these EPGROUP MO.
Relation with the SCTPHOST,SCTPPEER MOs:
- In a routing domain IPv4 configuration,if there are SCTPHOST MOs configured in different
EPGROUP which PNs are the same, and one's SIGIP1V4 or SIGIP2V4 is the same with the
other's SIGIP1V4 or SIGIP2V4,the same SCTPPEER MO is only allowed to be configured in
one of these EPGROUP MO.
- In a routing domain IPv6 configuration,if there are SCTPHOST MOs configured in different
EPGROUP which PNs are the same, and one's SIGIP1V6 or SIGIP2V6 is the same with the
other's SIGIP1V6 or SIGIP2V6,the same SCTPPEER MO is only allowed to be configured in
one of these EPGROUP MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD EPGROUP User this command to add an end point group.


Table 1 Related MML commands

MML Command Function

ADD Use this command to add an SCTP host to an end point group.
SCTPHOST2EPGRP

ADD Use this command to add an SCTP peer to an end point group.
SCTPPEER2EPGRP

ADD UPHOST2EPGRP Use this command to add a user-plane host to an end point group.

ADD UPPEER2EPGRP Use this command to add a user-plane peer to an end point group.

LST EPGROUP User this command to list the configuration of an end point group.

LST Use this command to list the SCTP hosts in an end point group.
SCTPHOST2EPGRP

LST Use this command to list the SCTP peers in an end point group.
SCTPPEER2EPGRP

LST UPHOST2EPGRP Use this command to list the user-plane hosts in an end point group.

LST UPPEER2EPGRP Use this command to list the user-plane peers in an end point group.

MOD EPGROUP User this command to modify the configuration of an end point group.

RMV EPGROUP User this command to remove an end point group.

RMV Use this command to remove an SCTP host from an end point group.
SCTPHOST2EPGRP

RMV Use this command to remove an SCTP peer from an end point group.
SCTPPEER2EPGRP

RMV Use this command to remove a user-plane host from an end point group.
UPHOST2EPGRP

RMV UPPEER2EPGRP Use this command to remove a user-plane peer from an end point group.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

End Point Group ID Indicates the ID of the end point group to which an end point belongs.
Table 2 Related parameters

Parameter Description

VRF Index Indicates the index of the virtual route and forwarding(VRF) instance.

SCTP Host ID List Indicates the list of all SCTP hosts in the end point group. This parameter takes
effect only in LTE.

SCTP Host List Indicates the list of all SCTP hosts in the end point group. This parameter takes
effect only in LTE.

SCTP Peer ID List Indicates the list of all SCTP peers in the end point group. This parameter takes
effect only in LTE.

SCTP Peer List Indicates the list of all SCTP peers in the end point group. This parameter takes
effect only in LTE.

User Plane Host ID List Indicates the list of all user-plane hosts in the end point group.

User Plane Host List Indicates the list of all user plane hosts in the end point group.

User Plane Peer ID List Indicates the list of all user-plane peers in the end point group.

User Plane Peer List Indicates the list of all user plane peers in the end point group.

Packet Filter Switch Indicates whether to enable the ACL rule self-configuration function for packet
filtering. When this parameter is set to ENABLE, the system automatically
generates packet filtering rules for all links of the local end point. If this
parameter is set to DISABLE, the system does not generate packet filtering
rules.

User Label Indicates the description of an end point group.

5.7.1.6.1.34 ETHOAM3AH
TRANSPORT
+-ETHOAM3AH

Description
This MO helps to implement the functions such as link monitoring, fault detection, and remote
loopback described in the IEEE 802.3ah. This MO is used for Operation, Administration and
Maintenance (OAM) of the last kilometer on the Ethernet.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the HAGRP MO:


- In one logical protection group, SN in an HAGRP MO must be the same as that in an
ETHOAM3AH MO.
Relation with the PORTSECURITY MO:
- An ETHPORT MO on which an ETHOAM3AH MO depends must meet either of the
following conditions: (1) The corresponding PORTSECURITY MO is not configured. (2) If the
corresponding PORTSECURITY MO has been configured, SWITCH in the
PORTSECURITY MO is set to ENABLE.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ACT ETHOAM3AH Use this command to activate Ethernet OAM 3AH, where OAM stands for
Operation, Administration and Maintenance.

DEA ETHOAM3AH Use this command to deactivate the functions of the Ethernet OAM 3AH.

DSP ETHOAM3AH Use this command to query the status of the IEEE802.3ah Ethernet OAM.

LST ETHOAM3AH Use this command to list the configuration of the Ethernet OAM 3AH.

STP Use this command to stop the Ethernet OAM 3ah loopback test.
ETHOAMLOOPTST

STR Use this command to start an OAM loopback test on an Ethernet port.
ETHOAMLOOPTST

Related Parameters
Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the board where the Ethernet port is located.

Subrack No. Indicates the subrack number of the board where the Ethernet port is located.

Slot No. Indicates the slot number of the board where the Ethernet port is located.

Subboard Type Indicates the type of sub-board on the board where the Ethernet port is located.

Port Type Indicates the type of the Ethernet port.

Port No. Indicates the number of the Ethernet port.

Work Mode Indicates the work mode of the IEEE802.3ah Ethernet OAM.
If this parameter is set to ACTIVE, the local end initiates the IEEE802.3ah
Ethernet OAM negotiation.
If this parameter is set to PASSIVE, the local end does not initiate the
negotiation; instead, the local end waits for receiving negotiation packets from
the peer end.

Detection Period Indicates the internal at which a Protocol Data Unit (PDU) is transmitted for
fault detection. A shorter interval indicates that Ethernet link faults can be
detected more quickly.

PDU Size Indicates the size of the Protocol Data Unit (PDU).

Loopback Flag Indicates whether remote loopback can be enabled at the port where 3AH
detection is activated. If remote loopback is enabled, the OAM 3AH loopback is
allowed. For details, see the STR ETHOAMLOOPTST command. During the
loopback, only 3AH packets rather than other types of packet can be transmitted.
If remote loopback is disabled, the local end cannot initiate the loopback.

Fault Report Flag Indicates whether to enable indication of link faults.

Error Frame Event Indicates the duration of the erroneous frame event.
Duration

Error Frame Event Indicates the threshold for the erroneous frame event. If the number of erroneous
Threshold
frames within a second exceeds the threshold, an erroneous frame event occurs.
This event is checked every other second.

Error Frame Seconds Indicates the duration of the Error Frame Seconds Summary Event. An error
Summary Event
frame second refers to a second within which one or more error frames are
Table 2 Related parameters

Parameter Description

Duration detected.

Error Frame Seconds Indicates the threshold for the accumulated erroneous frame event. If the length
Summary Event
Threshold of time that erroneous frames occupy within a sampling period specified through
the ERRFRMSCDEVTPRD parameter exceeds the threshold, an accumulated
erroneous frame event occurs.

Current State Indicates the Finite State Machine (FSM) status of an Ethernet OAM 3AH.

Number of RX Dropped Indicates the number of discarded OAM PDUs on the RX channel.
OAMPDUs

Number of RX Event Indicates the number of received Event OAM PDUs.


OAMPDUs

Number of RX Fault Indicates the number of received Fault OAM PDUs.


OAMPDUs

Number of RX Indicates the number of Info OAM PDUs received on a port.


Information OAMPDUs

Number of RX Indicates the number of received Loopback Control OAM PDUs.


Loopback Control
OAMPDUs

Total Number of RX Indicates the total number of received OAM PDUs, including the information
OAMPDUs
OAM PDUs, event OAM PDUs, loopback OAM PDUs, and discarded OAM
PDUs.

Number of TX Dropped Indicates the number of discarded OAM PDUs on the TX channel.
OAMPDUs

Number of TX Event Indicates the number of transmitted Event OAM PDUs. The Event OAM PDUs
OAMPDUs
are used to notify the peer end of a link event.

Number of TX Fault Indicates the number of transmitted Fault OAM PDUs. The Fault OAM PDUs
OAMPDUs
are used to notify the peer end of a link failure.

Number of TX Indicates the number of transmitted Info OAM Protocol Data Units (PDUs). The
Information OAMPDUs
Info OAM PDUs are used to finish the search process.

Number of TX Indicates the number of transmitted loopback OAM PDUs. The loopback OAM
Loopback Control
OAMPDUs PDUs are used for remote loopback control.

Total Number of TX Indicates the total number of transmitted OAM PDUs, including the information
OAMPDUs
OAM PDUs, event OAM PDUs, loopback OAM PDUs, and discarded OAM
PDUs.
5.7.1.6.1.35 ETHPORT
TRANSPORT
+-ETHPORT

Description

This MO indicates an Ethernet port on a panel that is used to connect to other NEs. In this MO,
you can configure such parameters as rate, duplex mode, port attribute, ARP proxy, and
maximum transmission unit. You can also list information about the statistics of received and
transmitted packets and loopback status.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the HAGRP MO:


- If PA in an ETHPORT MO is set to AUTO, no HAGRP MO can be configured.
- In one logical protection group, SN in an HAGRP MO must be the same as that in an
ETHPORT MO.
Relation with the MPT MO:
- When TYPE in MPT is LMPT, If PA is AUTO in ETHPORT on the LMPT board, the
SPEED and DUPLEX of the ETHPORT must be AUTO.
Relation with the ETHPORT MO:
- The data rates of all ETHTRKLNK MOs in an ETHTRK MO must be the same.
Relation with the LR MO:
- When removing an ETHPORT MO, the system automatically removes the LR MO that
depends on the ETHPORT MO.
Relation with the PORTSECURITY MO:
- When removing an ETHPORT MO, the system automatically removes the
PORTSECURITY MO that depends on the ETHPORT MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD ETHPORT Use this command to add an Ethernet port and set its related parameters, such as
the Ethernet port speed, duplex mode, and port attribute.

DSP ARP Use this command to query the active Address Resolution Protocol (ARP) table
entries of the system. An ARP table entry records mapping from the IP address
of the peer port acquired by the BS to a MAC address.

DSP ETHPORT Use this command to query the status of an Ethernet port, including the
maximum transfer unit, speed, MAC address, duplex mode, physical layer
status, and traffic information.

LST ETHPORT Use this command to list the Ethernet port configuration, including the speed,
duplex mode, and port attribute.

RMV ETHPORT Use this command to restore the default configuration of an Ethernet port.

RST ETHPORT Use this command to reset an Ethernet port. After the Ethernet port is reset, the
port negotiation automatically restarts. The data to be negotiated consists of the
maximum transmission unit, port rate, and duplex mode.

SET ETHPORT Use this command to configure an Ethernet port. The configuration of an
Ethernet port includes (but not limited to) the port rate, duplex mode, and port
attribute.

SET MACLOOP Use this command to set a MAC loopback for an Ethernet port. If an Ethernet
port is faulty, you can set a MAC loopback to identify problems in the
transmission link or the port.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the board where the Ethernet port is located.

Subrack No. Indicates the subrack number of the board where the Ethernet port is located.

Slot No. Indicates the slot number of the board where the Ethernet port is located.
Table 2 Related parameters

Parameter Description

Subboard Type Indicates the type of sub-board on the board where the Ethernet port is located.

Port No. Indicates the number of the Ethernet port.

Port Attribute Indicates whether an Ethernet port is an electrical port or optical port. When the
system starts, the system binds an Ethernet port to an optical port preferentially
if the default value of the port attribute is AUTO. If the BS does not support
cascading, the port attribute is set to AUTO.

Maximum Transmission Indicates the maximum IP packet size (including the IP header) at the Ethernet
Unit
port. For the UMPT, LMPT, and UTRPc, the value of this parameter ranges
from 46 to 1800. For other boards, the value of this parameter ranges from 46 to
1500. If this parameter is set to a value greater than the maximum allowed value,
the maximum allowed value takes effect. A value greater than or equal to 776 is
recommended, because broadcast packets, such as DHCP packets, may
experience reception or transmission failures if the maximum transmission unit
is smaller than 776. If the Ethernet port is added to an Ethernet trunk, this
parameter becomes invalid. The actual maximum transmission unit depends on
the value set for the Ethernet trunk.

Speed Indicates the speed mode of the Ethernet port. This parameter must be set to the
same value as that of the peer port. GE electrical ports of base board support
1000 Mbit/s only when working in auto-negotiation mode. If SPEED of a GE
optical port is set to AUTO, the port works at 1000 Mbit/s in auto-negotiation
mode. If SPEED of a GE optical port is set to 1000M, the port works at 1000
Mbit/s in manual configuration mode.

Duplex Indicates the duplex mode of the Ethernet port.

ARP Proxy Indicates whether to enable the proxy ARP function. If this function is enabled,
the BS serves as an ARP proxy for the IP address of a loopback interface on the
BS or a port IP address of a lower-level BS. If this function is disabled, an
external device can access a loopback interface in the BS or a lower-level BS on
the same subnet only by using a route. After the Ethernet port is added to an
Ethernet trunk, this parameter stops taking effect and whether the proxy ARP
function is enabled for the Ethernet port depends on the setting of the same
parameter in the Ethernet trunk.

Flow Control Indicates whether to enable flow control on the Ethernet port. Flow control is
implemented to prevent congestion. When flow control is enabled, the RX end
repeatedly sends PAUSE frames to the TX end, instructing the TX end to lower
the TX rate if congestion occurs on the RX end. Upon receiving PAUSE frames,
the TX end stops sending data during a period of time to prevent congestion. For
details, see IEEE 802.3ah.
Table 2 Related parameters

Parameter Description

MAC Frame Error Rate Indicates the generation threshold for the MAC Excessive Frame Error Rate
Occur Threshold
alarm (ID: 25881). When the number of erroneous MAC frames exceeds this
threshold, the MAC Excessive Frame Error Rate alarm is reported.

MAC Frame Error Rate Indicates the clearance threshold for the MAC Excessive Frame Error Rate
Clear Threshold
alarm (ID: 25881). When the number of erroneous MAC frames falls below this
threshold, the MAC Excessive Frame Error Rate alarm is cleared.

MAC Address Indicates the MAC address (six bytes) configured for the Ethernet port. The
format is XXXX-XXXX-XXXX.

Port Status Indicates the status of the Ethernet port.

Loopback Status Indicates the loopback status of the Ethernet port.

In Loopback Mode or Indicates whether the Ethernet port is in the steady state of the OAM 3AH
Not
loopback response. For details, see IEEE 802.3ah.

Ethernet OAM 3AH Indicates whether the Ethernet OAM 3AH is enabled.
Flag

Number of RX Packets Indicates the number of packets received at the Ethernet port.

Number of RX Bytes Indicates the number of bytes received at the Ethernet port.

Number of RX CRC Indicates the number of CRC error packets received at the Ethernet port.
Error Packets

RX Traffic Indicates the traffic received at the Ethernet port.

Number of TX Packets Indicates the number of packets transmitted at the Ethernet port.

Number of TX Bytes Indicates the number of bytes transmitted at the Ethernet port.

TX Traffic Indicates the traffic transmitted at the Ethernet port.

Number of IPs Indicates the number of IP addresses configured for the Ethernet port.

IP Address List Indicates the IP address and mask list configured for the Ethernet port.

Local Configuration Indicates the negotiation mode configured on the Ethernet port.
Negotiation Mode

Local Actual Indicates the actual negotiation mode of the Ethernet port.
Negotiation Mode
Table 2 Related parameters

Parameter Description

Local Speed Indicates the speed mode of the Ethernet port. This parameter must be set to the
same value as that of the peer port.

Local Duplex Indicates the duplex mode of the Ethernet port. If an Ethernet electrical port is
used, this parameter is valid when SPEED is not set to AUTO. If an Ethernet
optical port is used, this parameter must be set to FULL.

Peer Actual Negotiation Indicates the negotiation mode of the NE connecting to the Ethernet port.
Mode

Peer Speed Indicates the speed mode of the NE connecting to the Ethernet port.

Peer Duplex Indicates the duplex mode of the NE connecting to the Ethernet port.

Rx Broadcast Pkts Indicates the generation threshold for the excessive RX broadcast packet alarm.
Alarm Occur Thd
If the average number of broadcast packets that are received on the Ethernet port
keeps above the threshold for 30 seconds, an excessive RX broadcast packet
alarm is reported.

Rx Broadcast Pkts Indicates the clear threshold for the excessive RX broadcast packet alarm. If the
Alarm Clear Thd
average number of broadcast packets that are received on the Ethernet port
keeps below the threshold for 30 seconds, the excessive RX broadcast packet
alarm is cleared.

Physical Layer Status Indicates the physical layer status of the Ethernet port.

User Label Indicates the user-defined information about an Ethernet port. PeerPortLocation
is contained in the UserLabel field.
The format of UserLabel is UserLabel="%PeerPortLocation::XXXX%ssssss",
where <i>XXXX</i> indicates the value of PeerPortLocation, and <i>ssssss</i>
indicates the value of UserLabel.

5.7.1.6.1.36 ETHTRK
TRANSPORT
+-ETHTRK
+-ETHTRKLNK[0~2]

Description
An ETHTRK MO consists of multiple parameters related to an Ethernet trunk, which contains
multiple Ethernet ports. This enables load sharing among the Ethernet ports and provides higher
reliability. The Ethernet port in an Ethernet trunk is called a member port. Member ports are
aggregated into an Ethernet trunk in either manual or static mode. In manual mode, a member
port takes effect immediately after being added to an Ethernet trunk without negotiating with the
Ethernet trunk at the peer end. In static mode, a member port does not take effect immediately
after being added to an Ethernet trunk. It takes effect only after the negotiation with the Ethernet
trunk at the peer end based on the Link Aggregation Control Protocol (LACP) is successful. For
details, see IEEE 802.3ad.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Possible children:
ETHTRKLNK[0~2]

Relation with the HAGRP MO:


- In one logical protection group, SN in an HAGRP MO must be the same as that in an
ETHTRK MO.
Relation with the ETHTRK MO:
- ETHTRK MOs must have a unique combination of CN, SRN, SN, and TN.
Relation with the IPPATH MO:
- If PT and JNRSCGRP in an IPPATH MO are set to ETHTRK and DISABLE, respectively,
the associated ETHTRK MO must have been configured.
Relation with the LR MO:
- If PT in an LR MO is set to ETHTRK, the associated ETHTRK MO must have been
configured.
- When removing an ETHTRK MO, the system automatically removes the LR MO that
depends on the ETHTRK MO.
Relation with the DEVIP MO:
- If PT in a DEVIP MO is set to ETHTRK, the associated ETHTRK MO must have been
configured.
Relation with the CFMMEP MO:
- Before configuring a CFMMEP MO on an ETHTRK MO, ensure that the ETHTRK MO
has been configured.
Relation with the RSCGRP MO:
- If PT in an RSCGRP MO is set to ETHTRK, the associated ETHTRK MO must have been
configured.
Relation with the IPSECBIND MO:
- Before binding an IPSECPOLICY to an ETHTRK MO, ensure that the ETHTRK MO is
configured.
Relation with the PACKETFILTER MO:
- If PT in a PACKETFILTER MO is set to ETHTRK, ensure that the associated ETHTRK
MO has been configured.
Relation with the IPITF6 MO:
- If PT in an IPITF6 MO is set to TRUNK, the associated ETHTRK MO must have been
configured.
Relation with the SUBIF MO:
- If PT in a SUBIF MO is set to ETHTRK, the corresponding ETHTRK MO must have been
configured.
Relation with the ETHTRKLNK MO:
- When removing an ETHTRK MO, the system automatically removes the ETHTRKLNK
MO that depends on the ETHTRK MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD ETHTRK Use this command to add an Ethernet trunk.

DSP ETHTRK Use this command to query the status of an Ethernet trunk.

LST ETHTRK Use this command to list the configuration of an Ethernet trunk.

MOD ETHTRK Use this command to modify the configuration of an Ethernet trunk.

RMV ETHTRK Use this command to remove an Ethernet trunk.

RST ETHTRK Use this command to reset an Ethernet trunk and restart automatic port
negotiation.
Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the board where the Ethernet trunk is
established.

Subrack No. Indicates the number of the subrack housing the board where the Ethernet trunk
is established.

Slot No. Indicates the number of the slot housing the board where the Ethernet trunk is
established.

Trunk No. Indicates the number of the Ethernet trunk.When the board is a UTRPc board,
the value of this parameter ranges from 0 to 2. When the board is a board other
than the UTRPc board, the value of this parameter ranges from 0 to 1.

Trunk Type Indicates the type of Ethernet trunk.


If this parameter is set to DISABLE, the trunk's status can not be notified to the
other end, member ports of the Ethernet trunk must be manually configured. In
this case, the configured member ports are considered as valid member ports of
the Ethernet trunk.
If this parameter is set to ENABLE, member ports of the Ethernet trunk must
also be manually configured. In this case, the valid member ports of the Ethernet
trunk are negotiated between the BS and the peer end according to LACP.

ARP Proxy Indicates whether to enable the ARP proxy function on the Ethernet trunk. If this
parameter is set to ENABLE, the BS performs the ARP proxy on the IP
addresses of its loopback interfaces (or of the lower-level BS). If this parameter
is set to DISABLE, the BS does not perform the ARP proxy on the IP addresses
of its loopback interfaces (or of the lower-level BS). The external device on the
same subnet needs to access the IP address through a configured route.

Subboard Type Indicates the type of subboard on the board where the Ethernet trunk is
established.

Max Transmission Unit Indicates the size of the maximum transmission unit for an Ethernet trunk. For
the UMPT, LMPT, and UTRPc, the value of this parameter ranges from 46 to
1800. For the WMPT, UQEC, and UEOC, the value of this parameter ranges
from 46 to 1500. If this parameter is set to a value greater than the maximum
allowed value, the maximum allowed value takes effect. A value greater than or
equal to 776 is recommended, because broadcast packets, such as DHCP
packets, may experience reception or transmission failures if the maximum
Table 2 Related parameters

Parameter Description

transmission unit is smaller than 776.

Ethernet Trunk Status Indicates the status of the Ethernet trunk. The state of the Ethernet trunk depends
on the state of the member ports. If the state of the member ports of the existing
Ethernet trunk is activated, the state of the Ethernet trunk is activated.

Local MAC Address Indicates the MAC address of the Ethernet trunk. The format is XXXX-XXXX-
XXXX. The MAC address of an Ethernet port is that of the first Ethernet port
added to the Ethernet trunk.

Peer System MAC Indicates the MAC address of the Ethernet trunk at the peer end. The format is
Address
XXXX-XXXX-XXXX. If the Ethernet trunk type is set to ENABLE, this
parameter specifies the MAC address of the peer end, which is negotiated
between the BS and the peer end by using the LACP protocol. For details, see
IEEE 802.3ad.

Number of Ethernet Indicates the number of member ports in the Ethernet trunk.
Trunk Ports

Ethernet Trunk Port No. Indicates the number of the member port of the Ethernet trunk.

Number of Active Trunk Indicates the number of active member ports of the Ethernet trunk.
Ports

Active Trunk Port No. Indicates the number of an active member port of the Ethernet trunk.

Number of RX Packets Indicates the number of packets (including the discarded packets) received by
the Ethernet trunk.

Number of RX Bytes Indicates the number of bytes (including the discarded bytes) received by the
Ethernet trunk.

Number of RX Dropped Indicates the number of discarded packets received by the Ethernet trunk.
Packets

Number of RX Dropped Indicates the number of discarded bytes received by the Ethernet trunk.
Bytes

Number of TX Packets Indicates the number of packets (including the discarded packets) transmitted by
the Ethernet trunk.

Number of TX Bytes Indicates the number of bytes (including the discarded bytes) transmitted by the
Ethernet trunk.

Number of TX Dropped Indicates the number of discarded packets transmitted by the Ethernet trunk.
Packets
Table 2 Related parameters

Parameter Description

Number of TX Dropped Indicates the number of discarded bytes transmitted by the Ethernet trunk.
Bytes

Number of IPs Indicates the number of IP addresses configured for the Ethernet trunk.

IP Address List Indicates the IP address list of the Ethernet trunk.

5.7.1.6.1.37 ETHTRKLNK
TRANSPORT
+-ETHTRK
+-ETHTRKLNK

Description

An ETHTRKLNK MO consists of multiple parameters related to a member port of an Ethernet


trunk, which contains multiple Ethernet ports. This enables load sharing among the Ethernet
ports and provides higher reliability. The Ethernet port in an Ethernet trunk is called a member
port. Member ports are aggregated into an Ethernet trunk in either manual or static mode. In
manual mode, a member port takes effect immediately after being added to an Ethernet trunk
without negotiating with the Ethernet trunk at the peer end. In static mode, a member port does
not take effect immediately after being added to an Ethernet trunk. To achieve this effect,
negotiation with the Ethernet trunk at the peer end based on the Link Aggregation Control
Protocol (LACP) is required. For details, see IEEE 802.3ad.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
ETHTRK

Relation with the IPSECBIND6 MO:


- Before binding an IPSECPOLICY6 MO to an ETHTRK MO, ensure that an
ETHTRKLNK MO has been configured under the ETHTRK MO.
Relation with the IPITF6 MO:
- The IPITF6 MO with PT set to ETH cannot be added to an ETHTRK MO.
Relation with the DEVIP MO:
- A DEVIP MO with PT set to ETH and PN set to the same value as that in an
ETHTRKLNK MO cannot be configured.
Relation with the LR MO:
- Before adding an ETHTRKLNK MO, ensure that an LR MO is not enabled for the
associated ETHPORT MO or LRSW in the LR MO is set to DISABLE.
Relation with the CFMMEP MO:
- Before an CFMMEP MO is configured on an ETHTRK MO or on an ETHPORT MO that
is not added to an ETHTRK MO, BNDVLAN in the parent CFMMA MO of the CFMMEP
MO must be set to YES.
- If an ETHPORT MO configured with a CFMMEP MO has joined an ETHTRK MO, the
CFMMA MO to which the CFMMEP MO belongs cannot be associated with any VLAN.
Relation with the ETHTRKLNK MO:
- A maximum of two ETHTRKLNK MOs can be configured in one ETHTRK MO.
- A maximum of one ETHTRKLNK MO with FLAG set to YES can be configured in one
ETHTRK MO.
- The data rates of all ETHTRKLNK MOs in an ETHTRK MO must be the same.
- For ETHTRKLNK MOs with the same combination of CN, SRN, and SN but with different
TN, their PN must be different.
- Before adding an ETHTRKLNK MO with FLAG set to NO, ensure that the associated
ETHTRKLNK MO with FLAG set to YES has been configured.
Relation with the IPSECBIND MO:
- Before configuring an IPSECBIND MO on an ETHPORT MO, ensure that the ETHPORT
MO has not been added to an ETHTRK MO.
- Before binding an IPSECPOLICY MO to an ETHTRK MO, ensure that an
ETHTRKLNK MO is configured in the ETHTRK MO.
Relation with the PACKETFILTER MO:
- If PT in a PACKETFILTER MO is set to ETH, and the ETHPORT MO is added to an
ETHTRK MO, the PACKETFILTER MO cannot be added.
Relation with the PORTSECURITY MO:
- An ETHPORT MO on which an ETHTRKLNK MO depends must meet either of the
following conditions: (1) The corresponding PORTSECURITY MO is not configured. (2) If the
corresponding PORTSECURITY MO has been configured, SWITCH in the
PORTSECURITY MO is set to ENABLE.
Relation with the RSCGRP MO:
- If an ETHPORT MO has been added to an ETHTRK MO, an RSCGRP MO that meets
both the following conditions must not be configured: (1) PT in the RSCGRP MO is set to ETH.
(2) CN, SRN, SN, SBT, and PN in the RSCGRP MO are the same as those in the associated
ETHTRKLNK MO, respectively.
Relation with the IPPATH MO:
- If PT in an IPPATH MO is set to ETH, ensure that the Ethernet port is not associated with
an ETHTRKLNK MO.
Relation with the SUBIF MO:
- If PT in a SUBIF MO is set to ETH, and the corresponding ETHPORT MO has joined an
ETHTRK MO, the SUBIF MO cannot be added.
Relation with the ETHTRK MO:
- When removing an ETHTRK MO, the system automatically removes the ETHTRKLNK
MO that depends on the ETHTRK MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD ETHTRKLNK Use this command to add an Ethernet trunk link in the Ethernet trunk.

DSP ETHTRKLNK Use this command to query the status of a member port of an Ethernet trunk.

LST ETHTRKLNK Use this command to list the configuration of member ports of Ethernet trunks.

RMV ETHTRKLNK Use this command to remove a member port from an Ethernet trunk.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet housing the board where the member port of
an Ethernet trunk is located.
Table 2 Related parameters

Parameter Description

Subrack No. Indicates the number of the subrack housing the board where the member port of
an Ethernet trunk is located.

Slot No. Indicates the number of the slot housing the board where the member port of an
Ethernet trunk is located.

Trunk No. Indicates the number of the parent Ethernet trunk of the port.

Port No. Indicates the number of the member port in an Ethernet trunk.

Port Priority Indicates the priority of the member port in an Ethernet trunk. A smaller
parameter value indicates a higher priority.

Master Flag Indicates whether the member port is the primary port of an Ethernet trunk. Each
Ethernet trunk has one and only one primary port. The primary port must be the
first port added to an Ethernet trunk and the last port removed from the Ethernet
trunk.

Subboard Type Indicates the type of sub-board on the board where the member port of an
Ethernet trunk is located.

Port Status Indicates the status of the member port in an Ethernet trunk.

MAC Address Indicates the MAC address of the member port when being added to an Ethernet
trunk. The format of the MAC address is XXXX-XXXX-XXXX.

Local Timeout Mode Indicates the period mode of transmitting the LACP Protocol Data Units (PDUs)
at the local end. In long period mode, the time interval for periodically
transmitting the LACP PDUs is large.

Peer Timeout Mode Indicates the period mode of transmitting the LACP PDUs at the peer end.

Number of RX LACP Indicates the number of received LACP PDUs on the member port of an
Packets
Ethernet trunk.

Number of TX LACP Indicates the number of transmitted LACP PDUs on the member port of an
Packets
Ethernet trunk.

5.7.1.6.1.38 FLOODDEFEND
TRANSPORT
+-FLOODDEFEND

Description

A FLOODDEFEND MO consists of the parameters related to the flood attack defense and
excessive flood packet alarm for a specific type of flood packet. If the local end receives
excessive flood packets from the peer end, the local end will spend a large amount of resources
processing these packets and therefore cannot provide user services normally.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD FLOODDEFEND Use this command to add a configuration of the flood attack defense and
excessive flood packet alarm for a specific type of flood packet.

DSP FLOODDEFEND Use this command to query information about flood packets.

LST FLOODDEFEND Use this command to list all configurations of flood attack defense and excessive
flood packet alarms.

MOD FLOODDEFEND Use this command to modify configurations of the flood attack defense and
excessive flood packet alarm for a specific type of flood packet.

RMV FLOODDEFEND Use this command to remove a configuration of the flood attack defense and
excessive flood packet alarm for a specific type of flood packet.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Flood Type Indicates the type of the flood packet to be measured.

Defend Switch Indicates whether to enable the protection against excessive flood packets.

Defend Threshold Indicates the threshold for starting the protection against excessive flood
packets. If the DFDSW parameter is set to ENABLE, the system discards the
extra packets when the RX rate of flood packets exceeds the threshold. It is
recommended that the difference between Defend Threshold and Alarm
Threshold is greater than 3% of Defend Threshold.

Alarm Switch Indicates whether to report an alarm when the local end receives excessive flood
packets from the peer end.

Alarm Threshold Indicates the threshold for the excessive flood packet alarm. If the ALMSW
parameter is set to ENABLE, the system measures the RX rate of flood packets
every 10 seconds. If the measured value exceeds the threshold, an excessive
flood packet alarm is reported. The alarm is cleared if the RX rate of flood
packets keeps below the threshold for five consecutive minutes. It is
recommended that the difference between Defend Threshold and Alarm
Threshold is greater than 3% of Defend Threshold.

Number of Flood Indicates the number of packets discarded because the total number of flood
Droped Packets
packets exceeds the specified threshold.

Receive Total packets Indicates the total number of received attack packets.

5.7.1.6.1.39 GTPU
TRANSPORT
+-GTPU

Description

A GTPU MO consists of the parameters related to GPRS Tunneling Protocol - User plane (GTP-
U) detection. These parameters specify the timer length and number of timeouts for detecting a
discontinuity or failure in the GTP-U.

Effective Scenario
Not involved

Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST GTPU Use this command to list the configurations of the GTP-U control message.

MOD GTPU Use this command to modify the parameters of the GTP-U control message.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

ECHO Frame Timeout Indicates the maximum wait time for an echo response. If no echo response is
received during the period specified by this parameter, the timer has expired.

ECHO Frame Timeout Indicates the maximum number of timeouts of the echo response waiting timer.
Count
If no echo response is received after the number specified by this parameter is
reached, the GTP-U path in use fails.

DSCP Indicates the Differentiated Services Code Point (DSCP) of a GTP-U control
packet.

Static Check Switch Indicates whether to enable static detection in compliance with GPRS Tunneling
Protocol for User Plane (GTP-U). If this parameter is set to ENABLE, the GTP-
U static check is enabled. In this case, the ALM-25886 IP Path Fault alarm is
reported if a link bearing an IP path is faulty. If this parameter is set to
DISABLE, the GTP-U static check is disabled.
5.7.1.6.1.40 GTRANSPARA
TRANSPORT
+-GTRANSPARA

Description

The GTRANSPARA MO consists of the global transport parameters within a BS. The settings of
the resource group scheduling weight switch and rate configuration type take effect on all
resource groups within the BS.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the CFMMA MO:


- if OAMTYPE of GTRANSPARA is set to ITU_T_Y1731,the length of MANAME in the
CFMMA cannot exceed 13 bytes.
- if OAMTYPE of GTRANSPARA is set to ITU_T_Y1731,MANAME in the CFMMA
must be different from each other.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ACT DHCPCFG Use this command to activate the configurations of the remote maintenance
channel after the remote maintenance channel is automatically established. The
configurations are obtained during automatic establishment of the channel ,IP
rout or manually changed by a user.

DSP Use this command to query the status of the IPSec Bypass function.
IPSECBYPASSCFG

DSP IPSTAT Use this command to list the statistical information about transmitted and
Table 1 Related MML commands

MML Command Function

received IP packets.

DSP PORTREDIRECT Use this command to query the information about port redirection.

DSP UDPLOOP Use this command to query the parameters of the User Datagram Protocol
(UDP) loopback.

LST ETHOAM Use this command to query Ethernet OAM configuration. The Ethernet OAM
complies with IEEE 802.1ag or ITU-T Y.1731.

LST GTRANSPARA Use this command to list the global transport-related parameters within a BS.

LST Use this command to list the IPSec Bypass status stored in the database.
IPSECBYPASSCFG

LST NETSTATE Use this command to list information about the working ports on a device.

LST Use this command to list the mode of the ping filter.
PINGFILTERMODE

PING Use this command to verify a connection or to check the quality of a connection.

SET ETHOAM Use this command to set the Ethernet OAM protocol IEEE 802.1ag or ITU-T
Y.1731.

SET GTRANSPARA Use this command to set the global transport parameters within a BS.

SET IPSECBYPASS Use this command to set the parameters related to IPSec bypass so that a base
station can switch between the IPSec network and the non-security network.

SET Use this command to set the IPSec bypass function. If the IPSec bypass switch
IPSECBYPASSCFG
is turned on, the base station can switch between the IPSec network and the non-
security network.

SET Use this command to set the ping filtering mode.


PINGFILTERMODE

SET UDPLOOP Use this command to set the UDP-type IP packet loopback. The UDP-type IP
packet loopback can be used to check the connectivity and quality of the
network based on the UDP packets sent by the peer end.

STP PORTREDIRECT Use this command to stop port redirection.

STR PORTREDIRECT Use this command to start port redirection.


Table 1 Related MML commands

MML Command Function

TRACERT Use this command to start route tracing. Route tracing obtains the information
about the gateways on the host-to-destination route by sending test packets on
the route. By running this command, you can check whether the route is
reachable and locate the position where a network connection failure occurs.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Resource Group Indicates the switch used to control whether to allocate bandwidths to
Scheduling Weight
Switch transmission resource groups on the physical port based on their scheduling
weights. When RATECFGTYPE (the rate configuration type) is set to
SINGLE_RATE and Physical Port Up Link OverBooking Switch or Physical
Port Down Link OverBooking Switch is set to OFF, different values of this
parameter lead to different bandwidth allocation methods as follows: (1) If this
parameter is set to DISABLE and the sum of TX bandwidths of the associated
resource groups exceeds the bandwidth of the physical port, each resource group
is allocated a bandwidth that is directly proportional to its configured TX
bandwidth; (2) If this parameter is set to ENABLE and the sum of TX
bandwidths of the associated resource groups exceeds the bandwidth of the
physical port, each resource group is allocated a bandwidth that is directly
proportional to its scheduling weight. When RATECFGTYPE (the rate
configuration type) is set to DUAL_RATE, different values of this parameter
lead to different CIR allocation methods as follows: (1) If the sum of CIRs of the
associated resource groups exceeds the bandwidth of the physical port, each
resource group is allocated a CIR that is directly proportional to its configured
CIR; (2) If the sum of CIRs of the associated resource groups is smaller than the
bandwidth of the physical port, each resource group is allocated a non-CIR that
is directly proportional to its scheduling weight. In this case, the PIR of a
resource group is the sum of the CIR and the non-CIR.

Rate Config Type Indicates the rate configuration mode of transmission resource groups in the BS,
which can be set to SINGLE_RATE or DUAL_RATE. The dual rate
configuration refers to the hybrid of the peak information rate (PIR) and
committed information rate (CIR). If this parameter is set to SINGLE_RATE,
the transmission resource group performs traffic shaping based on its transmit
bandwidth. If this parameter is set to DUAL_RATE, the transmission resource
group performs traffic shaping based on PIR and the transmission admission
Table 2 Related parameters

Parameter Description

algorithm ensures that the non-flow-controllable traffic does not exceed CIR.

Switch Back Time Indicates the period during which the active and standby routes are switched
over twice. This period indicates the interval between the time single-hop BFD
detects that an active route changes from DOWN to UP and the time the active
route becomes available. During the switchover, if the previous standby route
becomes faulty, the system waits for 10 seconds and then switches back to the
active route.

ARP Aging Time Indicates the aging time of a dynamic ARP item of the BS.This parameter does
not change the ARP aging time of the local maintenance Ethernet port.

Ping Filter Mode Indicates the mode of the ping filtering. When the whitelist is used, only the
network segments or hosts specified by the ping filter can ping the NE. When
the blacklist is used, the network segments or hosts specified by the ping filter
cannot ping the NE.

Number of Packets Indicates the number of packets discarded due to fragmentation failures on the
Discarded Due to
Fragmentation Failures transmitter.

Total Number of Indicates the number of received packets that have been encrypted.
Encrypted Packets
Received at the IP
Layer of the Receiver

Number of Packets Indicates the number of packets that have been successfully decrypted at the
Successfully Decrypted
at the IP Layer of the receiver.
Receiver

Total Number of Indicates the number of received packets that fail the ESP-based decryption.
Packets Failed in ESP
Decryption at the IP
Layer of the Receiver
Hardware

Total Number of Indicates the number of received packets that fail the AH-based authentication.
Packets Failed in AH
Authentication at the IP
Layer of the Receiver
Hardware

Total Number of Indicates the number of received packets that should not have been encrypted.
Packets Discarded at
the IP Layer of the
Receiver Due to Having
Been Encrypted

Total Number of Indicates the total number of packets received by the decryption module of the
Packets Received by
Table 2 Related parameters

Parameter Description

the Decryption Module receiver at the IP layer.


of the Receiver

Number of Failing Indicates the total number of packets that fail decryption at the IP layer of the
Decrypted Packets at
the Receiver receiver.

Total Number of IKE Indicates the number of received IKE packets.


Packets Received at
the IP Layer of the
Receiver

Total Number of Indicates the number of encrypted packets received by the IP layer of the
Packets Discarded at
the IP Layer of the receiver from invalid IP addresses.
Receiver Due to Invalid
Source IP Addresses

Total Number of Indicates the total number of packets discarded at the IP layer of the receiver due
Packets Discarded at
the IP Layer of the to replay attacks.
Receiver Due to Replay
Attacks

Total Number of Indicates the total number of packets discarded at the IP layer of the receiver due
Packets Discarded at
the IP Layer of the to a lack of inbound SA.
Receiver Due to No
Inbound SA

Total Number of Indicates the total number of packets discarded because the IP layer of the
Packets Discarded at
the IP Layer of the receiver does not support the AH algorithm.
Receiver Due to
Unsupported AH
Algorithm

Total Number of Indicates the total number of packets discarded because the IP layer of the
Packets Discarded at
the IP Layer of the receiver does not support the ESP algorithm.
Receiver Due to
Unsupported ESP
Algorithm

Total Number of Plain Indicates the total number of plain packets received at the IP layer of the
Packets Received at
the IP Layer of the receiver.
Receiver

Number of Packets Indicates the number of packets received at the IP layer that comply with ACL
Discarded at the IP
Layer of the Receiver rules and should have been encrypted.
Due to not Being
Encrypted

Number of Packets Indicates the number of transmitted packets that are successfully encrypted.
Table 2 Related parameters

Parameter Description

Successfully Encrypted
at the IP Layer of the
Transmitter

Total Number of Indicates the number of packets that fail to be encrypted at the transmitter.
Packets Failed to Be
Encrypted at the IP
Layer of the Transmitter

Total Number of Indicates the total number of received packets.


Packets Received by
the Encryption Module
of the Transmitter

Number of Packets Indicates the number of packets that need to be encrypted at the transmitter.
That Should be
Encrypted at the
Transmitter

Total Number of Indicates the number of packets discarded at the transmitter because the
Packets Discarded at
the IP Layer of the outbound SAs do not exist.
Transmitter due to No
Outbound SA

Total Number of Indicates the number of packets discarded because the transmitter does not
Packets Discarded at
the IP Layer of the support the AH algorithm.
Transmitter Due to
Unsupported AH
Algorithm

Total Number of Indicates the number of packets discarded because the transmitter does not
Packets Discarded at
the IP Layer of the support the ESP algorithm.
Transmitter Due to
Unsupported ESP
Algorithm

Total Number of Indicates the number of packets that fail the AH-based authentication at the
Packets Failed in AH
Authentication at the IP transmitter.
Layer of the Transmitter
Hardware

Total Number of Indicates the number of transmitted packets that fail ESP encryption.
Packets Failed in ESP
Encryption at the IP
Layer of the Transmitter

Total Number of Indicates the number of packets discarded due to transmitting sequence number
Packets Discarded at
the IP Layer of the overflow.
Transmitter Due to SN
Overflow
Table 2 Related parameters

Parameter Description

Total Number of Indicates the number of packets that do not need to be encrypted at the
Packets That Should
Not Have Been transmitter.
Encrypted at the IP
Layer of the Transmitter

Total Number of IKE Indicates the number of transmitted IKE packets.


Packets Sent at the IP
Layer of the Transmitter

Ethernet OAM Type Indicates the type of Ethernet OAM.The current Ethernet OAM type includes
IEEE 802.1ag or ITU-T Y.1731 ETHOAM.

Monitor Policy Indicates the ITU-T Y.1731 monitoring policy.The monitor policy includes the
following values: PORTID_VLANID (based on PortID and VLANID),
PORTID_VLANID_VLANPRI (based on PortID, VLANID, and VLAN PRI),
SA_DA_VLANID (based on PortID, source MAC address, destination MAC
address, and VLANID), SA_DA_VLANID_VLANPRI (based on PortID,
source MAC address, destination MAC address, VLANID, and VLAN PRI), and
SA_DA (based on PortID, source MAC address, and destination MAC address).

IPSec Bypass Switch Indicates whether to enable the switchover of IPSec Bypass. If this parameter is
set to DISABLE, the base station cannot switch between an IPSec network and a
non-IPSec network.

IPSec Bypass Code Indicates the password used for switching the base station between an IPSec
network and a non-IPSec network.

IPSec Status Indicates the state of IPSec Bypass.

Master SeGW IP Indicates the IP address of the active security gateway when the base station is
located in an IPSec network.

Slave SeGW IP Indicates the IP address of the standby security gateway when the base station is
located in an IPSec network.

OMCH Switch Back Indicates whether the remote maintenance channel supports switchover. This
parameter is valid only when the remote maintenance channel is bound to
UDPSESSION detection. Currently, only GSM supports the UDP session
detection. If the parameter is set to ENABLE, the OM channel switches over to
the active remote maintenance channel after the active/standby remote
maintenance channel is switched and the UDPSESSION detects that the active
channel is recovered. If the parameter is set to DISABLE, the OM channel does
not switch to the active remote maintenance channel after the active/standby
remote maintenance channel is switched and the UDPSESSION detects that the
active channel is recovered.
Table 2 Related parameters

Parameter Description

OMCH Switch Back Indicates the duration for the detection switching from the standby remote
Wait Time
maintenance channel to the active remote maintenance channel.

SCTP Fault Real-time Indicates whether to report ALM-25888 SCTP Link Fault in real time. When this
Reporting Switch
parameter is set to ENABLE, ALM-25888 SCTP Link Fault is reported
immediately after an SCTP link disconnection is detected. When this parameter
is set to DISABLE, a timer starts after an SCTP link disconnection is detected.
ALM-25888 SCTP Link Fault alarm is reported if the disconnection lasts for 18
consecutive seconds within 30s. Otherwise, this alarm is not reported.

5.7.1.6.1.41 HAGRP
TRANSPORT
+-HAGRP

Description

The HAGRP MO is used to configure two boards with active/standby transmission capability as
two boards working in active/standby mode. In this way, transmission reliability is increased.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the HAGRP MO:


- Only one HAGRP MO can be configured in a logical protection group. In a logical
protection group, CN and SRN of two boards are identical, respectively, SN values are adjacent,
but the value of slot numbers divided by two is the same.
Relation with the ETHPORT MO:
- In one logical protection group, SN in an HAGRP MO must be the same as that in an
ETHPORT MO.
- If PA in an ETHPORT MO is set to AUTO, no HAGRP MO can be configured.
Relation with the DEVIP MO:
- In one logical protection group, SN in an HAGRP MO must be the same as that in a DEVIP
MO.
Relation with the E1T1 MO:
- In one logical protection group, SN in an HAGRP MO must be the same as that in an E1T1
MO.
Relation with the RSCGRP MO:
- In one logical protection group, SN in an HAGRP MO must be the same as that in an
RSCGRP MO.
Relation with the PPPLNK MO:
- In one logical protection group, SN in an HAGRP MO must be the same as that in a
PPPLNK MO.
Relation with the MPGRP MO:
- In one logical protection group, SN in an HAGRP MO must be the same as that in an
MPGRP MO.
Relation with the IPSECBIND MO:
- In one logical protection group, SN in an HAGRP MO must be the same as that in an
IPSECBIND MO.
Relation with the ETHTRK MO:
- In one logical protection group, SN in an HAGRP MO must be the same as that in an
ETHTRK MO.
Relation with the LR MO:
- In one logical protection group, SN in an HAGRP MO must be the same as that in an LR
MO.
Relation with the ETHOAM3AH MO:
- In one logical protection group, SN in an HAGRP MO must be the same as that in an
ETHOAM3AH MO.
Relation with the PACKETFILTER MO:
- In one logical protection group, SN in an HAGRP MO must be the same as that in a
PACKETFILTER MO.
Relation with the CFMMA MO:
- In one logical protection group, SN in an HAGRP MO must be the same as that in a
CFMMA MO.
Relation with the PORTSECURITY MO:
- In one logical protection group, SN in an HAGRP MO must be the same as that in a
PORTSECURITY MO.
Relation with the IPITF6 MO:
- In one logical protection group, SN in an HAGRP MO must be the same as that in an
IPITF6 MO.
Relation with the CERTDEPLOY MO:
- In one logical protection group, SN in an HAGRP MO must be the same as that in a
CERTDEPLOY MO.
Relation with the DOT1X MO:
- In one logical protection group, SN in an HAGRP MO must be the same as that in a
DOT1X MO.
Relation with the TUNNEL MO:
- In the logical protection group where the SSN of the TUNNEL MO is located, the value of
SN in the HAGRP MO must be the same as the value of SSN in the TUNNEL.
- In the logical protection group where the DSN of the TUNNEL MO is located, the value of
SN in the HAGRP MO must be the same as the value of DSN in the TUNNEL.
Relation with the LLDPLOCAL MO:
- In one logical protection group, SN in an HAGRP MO must be the same as SN in a
LLDPLOCAL MO.
Relation with the SUBIF MO:
- In one logical protection group, SN in an HAGRP MO must be the same as SN in a SUBIF
MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST HAGRP Use this command to list the configuration of the transport HA group.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the boards that constitute the HA group. This
parameter can only be configured through CME.

Subrack No. Indicates the subrack number of the boards that constitute the HA group. This
parameter can only be configured through CME.

Logic Slot No. Indicates the logical slot number of the HA group. The logical slot number of an
HA group is the number of the physical slot housing one of the two boards
constituting the HA group. This parameter can only be configured through CME.

5.7.1.6.1.42 IKECFG
TRANSPORT
+-IKECFG

Description

The IKECFG MO is used to define basic IKE configuration such as the IKE local name and IKE
keepalive duration.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

DSP IKECFG Use this command to query the basic IKE configuration that takes effect. The
configuration includes the local IKE name and keepalive duration.

LST IKECFG Use this command to list the basic IKE configuration. The configuration
includes the local IKE name and keepalive timeout duration.

SET IKECFG Use this command to set the global parameters related to the basic IKE
configurations.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local Name Indicates the IKE local name.

Keepalive Interval Indicates the time interval for sending the keepalive packets. If the parameter is
set to 0, keepalive packets are not sent.

Keepalive Timeout Indicates the timeout duration for waiting for the keepalive packets. If this
parameter is set to 0, keepalive packets are not sent.

DSCP Indicates the DSCP for IKE negotiation packets.

Cabinet No. Indicates the cabinet number of the IKE local board.

Subrack No. Indicates the subrack number of the IKE local board.

Slot No. Indicates the slot number of the IKE local board.

5.7.1.6.1.43 IKEPEER
TRANSPORT
+-IKEPEER
Description

An IKEPEER MO consists of the parameters related to the peer end using Internet Key
Exchange (IKE). An IKE SA is established through negotiation based on information such as
verification information of the peer end and security proposals.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the IKEPEER6 MO:


- PEERNAME in an IKEPEER6 MO is case insensitive and must be different from
PEERNAME in an IKEPEER MO.
Relation with the DEVIP MO:
- If LOCALIP in an IKEPEER MO is not set to 0.0.0.0, the DEVIP MO that has the same IP
address as LOCALIP and are in the same routing domain must have been configured.
- When LOCALIP in an IKEPEER MO is not set to 0.0.0.0, PT in a DEVIP MO cannot be
set to PPP or MPGRP if the DEVIP MO has the same IP address as LOCALIP and in the same
routing domain.
Relation with the IKEPROPOSAL MO:
- Before configuring an IKEPEER MO, ensure that the IKEPROPOSAL MO that is
associated with PROPID in the IKEPEER MO is configured.
- If AUTHMETH in an IKEPROPOSAL MO is set to PRE_SHARED_KEY, PKEY in an
IKEPEER MO must have been configured.
Relation with the IPSECPOLICY MO:
- Before configuring an IPSECPOLICY MO, ensure that the associated IKEPEER MO is
configured.
Relation with the IKEPEER MO:
- REMOTEIP in each IKEPEER MO must be unique.
- On a BS, the total number of IKEPEER6 and IKEPEER MOs must be smaller than or
equal to 100.
- In the same routing domain, SRCIP in the BFDSESSION MOs for the primary and
secondary IPSec tunnels in an IPSECDTNL MO must be the same as LOCALIP in the
IKEPEER MOs for the primary and secondary IPSECPOLICY MOs used by the
IPSECDTNL MO, respectively. In addition, DSTIP in the BFDSESSION MOs for the primary
and secondary IPSec tunnels must be the same as REMOTEIP in the IKEPEER MOs for the
primary and secondary IPSECPOLICY MOs, respectively.
Relation with the SECURITYPEER,IKEPEER6 MOs:
- In a SECURITYPEER MO, if SEGWSWITCH is set to ENABLE, PEERNAME must be
the same as PEERNAME in a configured IKEPEER MO or PEERNAME in a configured
IKEPEER6 MO.
Relation with the SECURITYHOST MO:
- In a SECURITYHOST MO, if IPVERSION and SEGWCONFIGMODE are set to IPv4
and SEGW_CONFIG_ON_HOST, respectively, PEERNAME must be the same as
PEERNAME in a configured IKEPEER MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD IKEPEER Use this command to add an Internet Key Exchange (IKE) peer.

DSP IKEPEER Use this command to query the IKE peer configuration that takes effect.

LST IKEPEER Use this command to list the configuration of the IKE peer.

MOD IKEPEER Use this command to modify the configuration of the IKE peer.

RMV IKEPEER Use this command to remove an IKE peer.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

IKE Peer Name Indicates the name of the IKE peer.

IKE Proposal ID Indicates the ID of the IKE proposal in use.

Version Indicates the IKE protocol version.


Table 2 Related parameters

Parameter Description

Exchange Mode Indicates the IKE exchange mode. In main mode, keys are exchanged
independently from identity authentications. This protects identity information
and hence enhances security. The aggressive mode does not have identity
authentication protection.

Local ID Type Indicates the type of the identification payload that the local end transmits. The
authentication can be performed based on IP or fully qualified domain name
(FQDN).

Remote IP Address Indicates the IP address of the peer end.

Remote Name Indicates the name of the peer end.

Pre-shared Key Indicates the pre-shared key. The two negotiation ends must be configured with
the same authenticator. This parameter takes effect only when Authentication
Method in the corresponding IKEPROPOSAL is set to PRE_SHARED_KEY.

DPD Mode Indicates whether to enable the dead peer detection (DPD) function.

DPD Idle Time Indicates the DPD idle time. If the local end does not receive encrypted packets
for a time defined by this parameter, it sends a DPD packet to perform dead peer
detection. The interval for sending a DPD packet slightly varies in various
network environments.

DPD Retransmission Indicates the interval at which DPD detection frames are sent. The interval at
Interval
which DPD detection frames are sent may slightly vary in various network
environments such as network congestion, delay, and jitter.

DPD Retransmission Indicates the number of retransmission attempts after a DPD detection fails.
Count

Control Mode Indicates whether the object can be modified or deleted by the system. The value
MANUAL_MODE means that only the user can modify or delete the object.
The value AUTO_MODE means that both the system and the user can modify or
delete the object.

Local IP Address Indicates the IP address of the local end, which is used in IKE negotiation. This
IP address can be set to 0.0.0.0 or a configured interface IP address at the local
end. If this parameter is set to 0.0.0.0, the BS automatically uses the interface IP
address to negotiate with the peer. If multiple IP addresses are configured at the
port, it is recommended that you specify one IP address for the negotiation. If
the local BS uses the digital certificate and IP address for authentication in the
negotiation, ensure that the IP address in the certificate is the same as the local
IP address of the BS.
Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the IKE peer board.

Subrack No. Indicates the subrack number of the IKE peer board.

Slot No. Indicates the slot number of the IKE peer board.

Auto Config Flag Indicates whether the object is created by the system. MANUAL_CREATED
means that the object is configured by the user manually. AUTO_CREATED
means that the object is created by the system.

5.7.1.6.1.44 IKEPEER6
TRANSPORT
+-IKEPEER6

Description

An IKEPEER6 MO consists of the parameters related to the peer end using IPv6 Internet Key
Exchange (IKE). An IKEv6 SA is established through negotiation based on information such as
verification information of the peer end and security proposals.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the IPSECPOLICY6 MO:


- The IKEPEER6 MO corresponding to an IPSECPOLICY6 MO must have been
configured.
Relation with the IKEPEER6 MO:
- Each IKEPEER6 MO must have a unique REMOTEIP.
- On a BS, the total number of IKEPEER6 and IKEPEER MOs must be smaller than or
equal to 100.
Relation with the IKEPEER MO:
- PEERNAME in an IKEPEER6 MO is case insensitive and must be different from
PEERNAME in an IKEPEER MO.
Relation with the DEVIP6 MO:
- Before adding an IKEPEER6 MO with LOCALIP set to a value other than 0, ensure that a
DEVIP MO with the same IP address as LOCALIP has been configured.
- REMOTEIP in an IKEPEER6 MO must be different from IPV6 in a DEVIP6 MO.
Relation with the OMCH6 MO:
- REMOTEIP in an IKEPEER6 MO must be different from LOCALIP6 in an OMCH6
MO.
Relation with the SCTPLNK6 MO:
- REMOTEIP in an IKEPEER6 MO must be different from LOCIP and SECLOCIP in an
SCTPLNK6 MO.
Relation with the LOCALIP6 MO:
- REMOTEIP in an IKEPEER6 MO must be different from IP6 in a LOCALIP6 MO.
Relation with the IKEPROPOSAL MO:
- Before configuring an IKEPEER6 MO, ensure that the IKEPROPOSAL MO with the
associated PROPID value has been configured.
- If AUTHMETH in an IKEPROPOSAL MO is set to PRE_SHARED_KEY, PKEY in the
associated IKEPEER6 MO must have been configured.
- AUTHMETH in an IKEPROPOSAL MO used by an IKEPEER6 MO must be set to
PRE_SHARED_KEY.
Relation with the SECURITYPEER,IKEPEER MOs:
- In a SECURITYPEER MO, if SEGWSWITCH is set to ENABLE, PEERNAME must be
the same as PEERNAME in a configured IKEPEER MO or PEERNAME in a configured
IKEPEER6 MO.
Relation with the SECURITYHOST MO:
- In a SECURITYHOST MO, if IPVERSION and SEGWCONFIGMODE are set to IPv6
and SEGW_CONFIG_ON_HOST, respectively, PEERNAME must be the same as
PEERNAME in a configured IKEPEER6 MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD IKEPEER6 Use this command to add an IPv6 Internet Key Exchange (IKE) peer.

DSP IKEPEER6 Use this command to query the IKE peer configuration that takes effect.

LST IKEPEER6 Use this command to list the configurations of IPv6 IKE peers.

MOD IKEPEER6 Use this command to modify the configuration of an IPv6 IKE peer.

RMV IKEPEER6 Use this command to remove an IKE peer.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

IPv6 IKE Peer Name Indicates the name of the IPv6 IKE peer.

IKE Proposal ID Indicates the ID of the security proposal used by an IPv6 IKE negotiation.

Version Indicates the protocol version of the IPv6 IKE.

Exchange Mode Indicates the IPv6 IKE negotiation mode. In main mode, keys are exchanged
independently from identity authentications. This protects identity information
and hence enhances security. The aggressive mode does not have identity
authentication protection. This mode, however, meets the requirements in
specific network environments.

Local ID Type Indicates the type of the identification payload that the local end transmits in
IPv6 networks. The authentication can be performed based on IPv6 address or
fully qualified domain name (FQDN).

Remote IPv6 Address Indicates the IPv6 address of the peer end.

Remote Name Indicates the peer name used by an IPv6 IKE negotiation.

Pre-shared Key Indicates the authenticator of the pre-shared key in IPv6 networks. The two
negotiation ends must be configured with the same authenticator.
Table 2 Related parameters

Parameter Description

DPD Mode Indicates whether to enable the Dead Peer Detection (DPD) function in IPv6
networks.

DPD Idle Time Indicates the IPv6 DPD idle time. If the local end does not receive encrypted
packets for a period specified by this parameter, it sends a DPD packet to
perform dead peer detection. Time required to transmit DPD packets varies with
network conditions.

DPD Retransmission Indicates the interval for sending the IPv6 DPD detection frame. The interval at
Interval
which IPv6 DPD detection frames are sent may slightly vary in various network
environments such as network congestion, delay, and jitter.

DPD Retransmission Indicates the number of retransmission attempts after the IPv6 DPD detection
Count
fails.

Control Mode Indicates whether the object can be modified or deleted by the system. The value
MANUAL_MODE means that only the user can modify or delete the object.
The value AUTO_MODE means that both the system and the user can modify or
delete the object.

Local IPv6 Address Indicates the IPv6 address that is used by the local end in IPv6 IKE negotiation.
This IP address can be set to either 0:0:0:0:0:0:0:0 or a device IPv6 address
configured at the local end. If this parameter is set to 0:0:0:0:0:0:0:0, the BS
automatically uses a local interface IP address to negotiate with the peer end. If
multiple interface IPv6 addresses are configured for a port, it is recommended
that this parameter be set to one of the IP addresses.

Cabinet No. Indicates the cabinet number of the IPv6 IKE peer board.

Subrack No. Indicates the subrack number of the IPv6 IKE peer board.

Slot No. Indicates the slot number of the IPv6 IKE peer board.

Auto Config Flag Indicates whether the object is created by the system. MANUAL_CREATED
means that the object is configured by the user manually. AUTO_CREATED
means that the object is created by the system.

5.7.1.6.1.45 IKEPROPOSAL
TRANSPORT
+-IKEPROPOSAL

Description

This MO defines a combination of security-related parameters such as encryption algorithms and


authentication algorithms used by the Internet Key Exchange (IKE). The corresponding IKE
security proposal is referenced by the IKE peer based on the number of the security proposal.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the IKEPEER6 MO:


- Before configuring an IKEPEER6 MO, ensure that the IKEPROPOSAL MO with the
associated PROPID value has been configured.
- If AUTHMETH in an IKEPROPOSAL MO is set to PRE_SHARED_KEY, PKEY in the
associated IKEPEER6 MO must have been configured.
- AUTHMETH in an IKEPROPOSAL MO used by an IKEPEER6 MO must be set to
PRE_SHARED_KEY.
Relation with the IKEPEER MO:
- Before configuring an IKEPEER MO, ensure that the IKEPROPOSAL MO that is
associated with PROPID in the IKEPEER MO is configured.
- If AUTHMETH in an IKEPROPOSAL MO is set to PRE_SHARED_KEY, PKEY in an
IKEPEER MO must have been configured.
Relation with the SECURITYTEMPLATE MO:
- In a SECURITYTEMPLATE MO, if SEGWSWITCH is set to DISABLE, PROPID must
be the same as PROPID in a configured IKEPROPOSAL MO.
- If AUTHALG in an IKEPROPOSAL MO is set to AES_XCBC_96, IKEVERSION in a
SECURITYTEMPLATE MO cannot be set to IKE_V1.
- If AUTHMETH in the IKEPROPOSAL MO on which a SECURITYTEMPLATE MO
depends is set to PRE_SHARED_KEY, PKEY in the SECURITYTEMPLATE MO must be
specified.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD IKEPROPOSAL Use this command to add an IKE proposal.

DSP IKEPROPOSAL Use this command to query the IKE proposal configuration that takes effect.

LST IKEPROPOSAL Use this command to list the configuration of an IKE proposal.

MOD IKEPROPOSAL Use this command to modify an IKE proposal.

RMV IKEPROPOSAL Use this command to remove an IKE proposal.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Proposal ID Indicates the ID of the IKE proposal.

Encryption Algorithm Indicates the encryption algorithm used in the IKE proposal. The Data
Encryption Standard (DES) is an internationally used data encryption algorithm,
which uses a 56-bit key. The 3DES is also an internationally used encryption
algorithm, which uses a 168-bit key. The Advanced Encryption Standard (AES)
is an advanced encryption algorithm, which provides three types of key of
different lengths: 128, 192, and 256 bits. Thus, different protection levels are
available. For details, see RFC2401.

Authentication Indicates the authentication algorithm used in the IKE proposal. IKE uses
Algorithm
hashed message authentication code (HMAC) or cipher block chaining (CBC)
for identity authentication and data integrity check. For details about HMAC,
see RFC4306. HMAC currently supports two hash functions: message digest
algorithm 5 (MD5) and secure hash algorithm 1 (SHA1). For details about the
hash functions, see RFC2409. MD5 and SHA1 verify data by means of integrity
protection. SHA1 provides higher security level than MD5. CBC currently
supports AES-XCBC- 96, which is an enhancement to CBC and applies only to
IKEv2. For details about AES-XCBC-96, see RFC3566.

Authentication Method Indicates the authentication mode used in the IKE proposal. For details, see
RFC2409.
Table 2 Related parameters

Parameter Description

Diffie-Hellman Group Indicates the Diffie-Hellman (DH) group of the IKE proposal. The core
technology used in an IKE proposal is the Diffie-Hellman (DH) exchange
technology. The DH exchange technology is used to calculate private
information based on public information. It is mathematically proven that
decrypting the DH information is impractical due to calculation complexity.

ISAKMP SA Duration Indicates the life cycle of an ISAKMP SA. ISAKMP refers to Internet Security
Association and Key Management Protocol, and SA refers to security
association.
IKE negotiation requires a long time to calculate Diffie-Hellman (DH) keys. It is
recommended that this parameter be set to greater than 10 minutes so that the
update of the ISAKMP SA does not affect the secure communication.
Before the SA life cycle elapses, local and peer ends will negotiate with each
other to generate a new SA to replace the original one. The new SA is used upon
completion of the negotiation, and the original SA is automatically removed
once its life cycle elapses.

PRF Algorithm Indicates the Pseudo-random Function (PRF) algorithm used in IKEv2. The PRF
algorithm is used to generate the materials required for IKE authentication and
encryption. For details about how to generate materials, see RFC4306.

Cabinet No. Indicates the cabinet number of the board that adopts the IKE security proposal.

Subrack No. Indicates the subrack number of the board that adopts the IKE security proposal.

Slot No. Indicates the slot number of the board that adopts the IKE security proposal.

5.7.1.6.1.46 IP2RSCGRP
TRANSPORT
+-IP2RSCGRP

Description

The IP2RSCGRP MO indicates a mapping between the destination IP address of the passing-by
data or local OM data (over IP transmission)/signaling data and the transmission resource group.
This MO is used to guarantee the Quality of Service (QoS) of bound service streams in the target
network segment by binding these service streams to a transmission resource group.
Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the RSCGRP MO:


- The RSCGRP MO corresponding to an IP2RSCGRP MO must have been configured.
Relation with the IP2RSCGRP MO:
- in the same routing domain, only one destination network segment can be bound to resource
groups configured on the same physical port. That is, if two IP2RSCGRP MOs have the same
combination of CN, SRN, SN, BEAR, SBT, PT, and PN, DSTIP in the two MOs must be on
different network segments.
- A maximum of two resource groups can be bound to the same destination network segment
on one board and in one routing domain. That is, a maximum of two IP2RSCGRP MOs whose
DSTIP is on the same network segment can be configured if the two MOs have the same
combination of CN, SRN, SN, BEAR, and SBT.
- A maximum of 32 IP2RSCGRP MOs can be configured on a board.
Relation with the VRF MO:
- The VRF instance used by an IP2RSCGRP MO must have been configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD IP2RSCGRP Use this command to add mapping between an IP address and a transmission
resource group. The mapping between an IP address and a transmission resource
group is the mapping between the destination IP address of the passing-by data
or local OM data (over IP transmission)/signaling data and a transmission
resource group.

LST IP2RSCGRP Use this command to list the configuration of the mapping between the IP
address and the transmission resource group.

RMV IP2RSCGRP Use this command to remove a mapping between the IP address and the
transmission resource group.
Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Mapping Index Indicates the mapping between IP and Transport Resource Groups.

Cabinet No. Indicates the number of the cabinet housing the board where a transmission
resource group is established.

Subrack No. Indicates the number of the subrack that houses the board where a transmission
resource group is established.

Slot No. Indicates the number of the slot corresponding to the board where a transmission
resource group is established.

Transmission Resource Indicates the bearer type of transmission resource group.


Group Bear Type

Subboard Type Indicates the type of sub-board on the board where a transmission resource
group is established.

Bearing Port Type Indicates the type of port where a transmission resource group is carried.

Bearing Port No. Indicates the number of the port where the transmission resource group is
configured.

Transmission Resource Indicates the ID of a transmission resource group.


Group ID

VRF Index Indicates the index of a VRF instance. The NodeB currently supports default
routes domain only (the VRF index is 0).

Destination IP Indicates the destination IP address of the service flow that is bound to a
transmission resource group.

Mask Indicates the subnet mask of the destination IP address of the service traffic
bound to a transmission resource group.

5.7.1.6.1.47 IP2RSCGRP6
TRANSPORT
+-IP2RSCGRP6

Description

The IP2RSCGRP6 MO indicates a mapping between the destination IP address of the passing-by
data or local OM data (over IP transmission)/signaling data and the transmission resource group.
This MO is used to guarantee the Quality of Service (QoS) of bound service streams in the target
network segment by binding these service streams to a transmission resource group.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the RSCGRP MO:


- The RSCGRP MO corresponding to an IP2RSCGRP6 MO must have been configured.
Relation with the IP2RSCGRP6 MO:
- Only one destination network segment can be bound to resource groups configured on the
same physical port. That is, if two IP2RSCGRP6 MOs have the same combination of CN, SRN,
SN, BEAR, SBT, PT, and PN, DSTIPV6 in the two MOs must be on different network
segments.
- A maximum of two resource groups can be bound to the same destination network segment
on one board. That is, a maximum of two IP2RSCGRP6 MOs whose DSTIPV6 values are on
the same network segment can be configured if the two MOs have the same combination of CN,
SRN, SN, BEAR, and SBT.
- A maximum of 32 IP2RSCGRP6 MOs can be configured on one board.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD IP2RSCGRP6 Use this command to add mapping between an IPv6 address and a transmission
resource group.

LST IP2RSCGRP6 Use this command to list the configuration of the mapping between the IPv6
Table 1 Related MML commands

MML Command Function

address and the transmission resource group.

RMV IP2RSCGRP6 Use this command to remove a mapping between the IPv6 address and the
transmission resource group.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the board where the transmission resource group
is configured.

Subrack No. Indicates the subrack number of the board where the transmission resource
group is configured.

Slot No. Indicates the slot number of the board where the transmission resource group is
configured.

Subboard Type Indicates the subboard type of the board where the transmission resource group
is configured.

Bearing Port Type Indicates the type of the port where a transmission resource group is configured.

Bearing Port No. Indicates the number of the port where the transmission resource group is
configured.

Transmission Resource Indicates the bearing type of a transmission resource group.


Group Bear Type

Transmission Resource Indicates the ID of a transmission resource group.


Group ID

Destination IPv6 Indicates the destination IPv6 address.


Address

Prefix Length Indicates the prefix length of an IPv6 address.


5.7.1.6.1.48 IPGUARD
TRANSPORT
+-IPGUARD

Description

The IPGUARD MO consists of the parameters related to attack defense policies used at the
MAC and IP layers, attack alarm switches, and attack alarm thresholds.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP ARPSPOOFING Use this command to query the black list in an ARP table.

DSP INVALIDPKTINFO Use this command to query the source of invalid packets.

LST IPGUARD Use this command to list configuration information about ARP spoofing
detection, ARP learning strict, illegal packet detection, and IPSec replay alarm
detection.

SET IPGUARD Use this command to set the global parameters related to ARP spoofing
detection, ARP learning strict, illegal packet detection, and IPSec replay alarm
detection.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

ARP Spoofing Check Indicates whether to perform ARP spoofing checks. If this parameter is set to
Switch
ENABLE, an alarm is reported when ARP spoofing attacks occur. If this
parameter is set to DISABLE, no alarm is reported when ARP spoofing attacks
occur.

ARP Spoofing Alarm Indicates the ARP spoofing alarm threshold. When the ARP spoofing check
Threshold
switch is turned on, an ARP spoofing alarm is reported if the number of ARP
update attempts reaches this threshold within one minute. Note that the number
of ARP update attempts from trusted MAC addresses is not counted. This alarm
is cleared if no ARP update attempt is made in one minute after the ARP
spoofing alarm is reported.

ARP Learning Strict Indicates whether to enable APR learning strict. ARP learning strict is a function
Switch
that enables a BS to learn the acknowledgement packets in response to only ARP
request packets sent by itself. With ARP learning strict, the BS can reject most
ARP request and acknowledge packet attacks.

Invalid Packet Check Indicates whether to report an alarm when the number of invalid packets
Switch
received by a BS exceeds the specified threshold. If this parameter is set to
ENABLE, an alarm is reported when the number of invalid packets received by
a BS exceeds the specified threshold. If this parameter is set to DISABLE, no
alarm is reported when the number of invalid packets received by a BS exceeds
the specified threshold. Invalid packets are those filtered according to the packet
filter criteria.

Alarm Threshold Indicates the threshold for the excessive invalid packet alarm. When Invalid
Packet Check Switch is set to ENABLE, the system measures the RX rate of
invalid packets every 10 seconds. If the measured value exceeds this threshold,
an excessive invalid packet alarm is reported. The alarm is cleared if the RX rate
of invalid packets keeps below the threshold for 5 consecutive minutes.

IPSec Replay Alarm Indicates whether to report IPSec packet replay alarm.
Switch

IPSec Replay Alarm Indicates the IPSec anti-replay alarm threshold.


Threshold

Port Type Indicates the type of physical port.

Port No. Indicates the number of a port.

Source MAC Address of Indicates the source MAC address of an invalid packet.
Invalid Packet

Destination MAC Indicates the destination MAC address of an invalid packet.


Address of Invalid
Packet
Table 2 Related parameters

Parameter Description

VLAN ID of Invalid Indicates the VLAN ID of an invalid packet.


Packet

Protocol Type of MAC Indicates the type of MAC-layer protocol used by an invalid packet. A BS
Layer
interprets only the supported MAC-layer protocols and only displays the
protocol numbers of other MAC-layer protocols.

VRF Index Indicates the index of a VRF instance. The NodeB currently supports default
routes domain only (the VRF index is 0).

Source IP Address of Indicates the source IP address of an invalid packet.


Invalid Packet

Destination IP Address Indicates the destination IP address of an invalid packet.


of Invalid Packet

Protocol Type of IP Indicates the protocol used at the IP layer of an invalid packet. A BS interprets
Layer
only the supported IP-layer protocols and only displays the protocol numbers of
other IP-layer protocols.

Source Port of Invalid Indicates the source port number of an invalid packet.
Packet

Destination Port of Indicates the destination port number of an invalid packet.


Invalid Packet

Invalid Packet Data Indicates at most the first 64 bytes of an invalid packet.

5.7.1.6.1.49 IPITF6
TRANSPORT
+-IPITF6
+-IPPATH6[0~128]
+-DEVIP6[0~8]

Description

An IPITF6 MO, that is, an IPv6 interface, is abstracted from the network layer to identify
different ports on the links and manage the related attributes of the network layer.

Effective Scenario
Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Possible children:
IPPATH6[0~128];DEVIP6[0~8]

Relation with the HAGRP MO:


- In one logical protection group, SN in an HAGRP MO must be the same as that in an
IPITF6 MO.
Relation with the IPSECBIND6 MO:
- The IPITF6 MO corresponding to ITFIDX in an IPSECBIND6 MO must have been
configured.
- In an IPITF6 MO referenced by an IPSECBIND6 MO, ITFTYPE must be set to
NORMAL and PT must be set to ETH or TRUNK.
Relation with the ETHTRKLNK MO:
- The IPITF6 MO with PT set to ETH cannot be added to an ETHTRK MO.
Relation with the IPITF6 MO:
- In an ETHPORT MO, a maximum of one IPITF6 with ITFTYPE set to NORMAL or one
IPITF6 MO with ITFTYPE set to VLAN and with VLANID set to the same as the associated
VLAN ID can be configured.
- The IPITF6 MOs configured on different ports of the same board must have different
VLANID values.
- A maximum of 16 IPITF6 MOs can be configured on a board.
Relation with the ETHTRK MO:
- If PT in an IPITF6 MO is set to TRUNK, the associated ETHTRK MO must have been
configured.
Relation with the IPRT6 MO:
- If NEXTHOPIP6TYPE in an IPRT6 MO is set to IPADDR6_TYPE_LINK_LOCAL, the
IPITF6 MO corresponding to ITFIDX in the IPRT6 MO must have been configured.
- If NEXTHOPIP6TYPE in an IPRT6 MO is set to IPADDR6_TYPE_LINK_LOCAL, the
IPITF6 MO corresponding to ITFIDX in the IPRT6 MO cannot be a loopback port.
Relation with the IPPATH6 MO:
- PT in the IPITF6 MO corresponding to ITFIDX in an IPPATH6 MO cannot be set to
LOOPIF.
Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD IPITF6 Use this command to add an IP version 6 (IPv6) interface.

DSP IPITF6 Use this command to query the status of an IPv6 interface.

DSP ND Use this command to query the neighbor discovery (ND) table entry of the
system.

LST IPITF6 Use this command to list the configuration of the IPv6 interfaces.

RMV IPITF6 Use this command to remove an IPv6 interface.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Interface Index Indicates the index of the IPv6 interface.

Interface Type Indicates the type of the IPv6 interface, which can be set to NORMAL or
VLAN.

Cabinet No. Indicates the number of the cabinet housing the board where the IPv6 interface
is located.

Subrack No. Indicates the subrack number of the board where the IPv6 interface is located.

Slot No. Indicates the slot number of the board where the IPv6 interface is located.

Subboard Type Indicates the type of sub-board on the board where the IPv6 interface is located.

Port Type Indicates the port type of IPv6 interface.

Port No. Indicates the port number of the IPv6 interface.


Table 2 Related parameters

Parameter Description

VLAN ID Indicates the ID of the VLAN-type IPv6 interface.

Maximum Transmission Indicates the maximum transmission unit of the IPv6 interface.
Unit

Interface Status Indicates whether an IPv6 interface is already activated.

Link Local Address Indicates the valid link-local address of an IPv6 interface.

Global Unicast Address Indicates the number of valid global unicast addresses of an IPv6 interface.
Number

Global Unicast Indicates the list of valid global unicast addresses of an IPv6 interface.
Address(es)

Multicast Address Indicates the number of valid multicast addresses of an IPv6 interface.
Number

Multicast Address(es) Indicates the list of valid multicast addresses of an IPv6 interface.

ND DAD Indicates whether to enable the IPv6 interface to detect address conflicts during
neighbor discovery.

ND DAD Attempts Indicates the number of detection times during the neighbor discovery procedure
Number
of the IPv6 interface.

ND Reachable Time Indicates the time for the IPv6 interface to start a neighbor discovery procedure.

ND Retransmit Interval Indicates the interval between the time the IPv6 interface reinitiates neighbor
discovery and the time neighbor discovery fails or the ND table entry becomes
invalid.

Link Local Address Indicates whether to enable the IPv6 interface to automatically generate a link
Autoconfig
local address.

Stateless Autoconfig Indicates the stateless automatic configuration switch of the IPv6 interface.

5.7.1.6.1.50 IPPATH
TRANSPORT
+-IPPATH
Description

The IPPATH MO is used to differentiate service transmission through the service transmission
channel between the BS and other NEs by configuring the IP address and service quality on both
ends of the channel.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the IPPATH MO:


- Any two IPPATH MOs must have different DSCP values if all of the following conditions
are met: (1) The two MOs are in the same routing domain. (2) PATHTYPE is set to FIXED in
these two MOs. (3) The two MOs have the same combination of LOCALIP and PEERIP.
- If PATHTYPE is set to ANY in one or two IPPATH MOs in the same routing domain, the
two MOs must have different address pairs. That is, the two MOs must have different
combinations of LOCALIP and PEERIP.
- On a BS, the sum of IPPATH6 and IPPATH MOs must be smaller than or equal to 320.
Relation with the DEVIP MO:
- If PT in an IPPATH MO is set to LOOPINT, the corresponding DEVIP MO must have been
configured, and VRFIDX, PT, and PN in the IPPATH MO must be the same as VRFIDX, PT,
and PN in the DEVIP MO, respectively.
- LOCALIP in an IPPATH MO must be the same as a DEVIP MO configured at a physical
port or loopback port of the same board. If LOCALIP in an IPPATH MO is the same as a
DEVIP MO configured at a physical port, PT and PN in the IPPATH MO must be the same as
PT and PN in the DEVIP MO, respectively. Alternatively, LOCALIP in the IPPATH MO must
be the same as LOCALIP in the associated PPPLNK MO or LOCALIP in the associated
MPGRP MO.
- If PT in an IPPATH MO is set to TUNNEL, the DEVIP MO whose PT is set to LOOPINT
and that is in the same routing domain as the IPPATH MO must have been configured.
Relation with the PPPLNK MO:
- If PT and JNRSCGRP in an IPPATH MO are set to PPP and DISABLE, respectively, the
associated PPPLNK MO must have been configured.
- If LOCALIP in an IPPATH MO is set to 0.0.0.0, the IPPATH MO must have been
configured on a PPPLNK MO whose LOCALIP is set to 0.0.0.0.
Relation with the MPGRP MO:
- If PT and JNRSCGRP in an IPPATH MO are set to MPGRP and DISABLE, respectively,
the associated MPGRP MO must have been configured.
- If LOCALIP in an IPPATH MO is set to 0.0.0.0, the IPPATH MO must have been
configured on an MPGRP MO whose LOCALIP is set to 0.0.0.0.
Relation with the ETHTRK MO:
- If PT and JNRSCGRP in an IPPATH MO are set to ETHTRK and DISABLE, respectively,
the associated ETHTRK MO must have been configured.
Relation with the RSCGRP MO:
- If JNRSCGRP in an IPPATH MO is set to ENABLE, the associated RSCGRP MO must
have been configured.
Relation with the TUNNEL MO:
- If PT and JNRSCGRP in an IPPATH MO are set to TUNNEL and DISABLE, respectively,
the associated TUNNEL MO must have been configured.
Relation with the ETHTRKLNK MO:
- If PT in an IPPATH MO is set to ETH, ensure that the Ethernet port is not associated with
an ETHTRKLNK MO.
Relation with the IPPMSESSION MO:
- If BINDPATH in an IPPMSESSION MO is set to YES, the IPPATH MO specified by
PATHID in the IPPMSESSION MO must have been configured.
- If BINDPATH and IPPMTYPE in an IPPMSESSION MO are set to YES and
THREE_TUPLE, respectively, PATHTYPE in the IPPATH MO whose PATHID is the same as
PATHID in the IPPMSESSION MO must be set to ANY.
- If BINDPATH and IPPMTYPE in an IPPMSESSION MO are set to YES and
THREE_TUPLE, respectively, SBT in the IPPATH MO whose PATHID is the same as
PATHID in the IPPMSESSION MO must be set to BASE_BOARD or ETH_COVERBOARD.
Relation with the PORTSECURITY MO:
- The ETHPORT MO that is associated with an IPPATH MO must meet either of the
following conditions: (1) No PORTSECURITY MO is associated with the ETHPORT MO; (2)
A PORTSECURITY MO is associated with the ETHPORT MO, but SWITCH in the
PORTSECURITY MO is set to ENABLE.
Relation with the IPPATH6 MO:
- PATHID in an IPPATH6 MO must be different from PATHID in an IPPATH MO.
Relation with the USERPLANEHOST,USERPLANEPEER,EPGROUP MOs:
- When USERPLANEHOST MO and USERPLANEPEER MO are configured in one
EPGROUP MO simultaneously and their IP versions are set to IPv4,these MOs cannot coexist
with IPPATH with PATHTYPE set to FIXED.

Related MML Commands


Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD IPPATH Use this command to add an IP path.

DSP IPPATH Use this command to query the status of an IP path.

LST IPPATH Use this command to list the configuration of an IP path.

MOD IPPATH Use this command to modify the configuration of an IP path.

RMV IPPATH Use this command to remove an IP path.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Path ID Indicates the ID of an IP path.

Cabinet No. Indicates the cabinet number of the board where the IP path is located.

Subrack No. Indicates the subrack number of the board where the IP path is located.

Slot No. Indicates the slot number of the board where the IP path is located.

Port Type Indicates the physical port type of the IP path.

Port No. Indicates the number of the port where the IP path is configured.

Path Type Indicates the type of the IP path. FIXED indicates that this IP path is used to
carry the service with specified Quality of Service (QoS), that is, with a
specified DSCP. ANY indicates that this IP Path can be used to carry services of
any QoS and hence is used to carry the service without a specified DSCP.

DSCP Indicates the differentiated services code point (DSCP) of the services carried on
an IP path.

Local IP Indicates the local IP address of an IP path. The value 0.0.0.0 indicates that the
Table 2 Related parameters

Parameter Description

local IP address needs to be negotiated.

Peer IP Indicates the peer IP address of the IP path.

Transport Resource Indicates the type of transport resource for the IP path. The value HQ indicates
Type
high-quality transport resources, and the value LQ indicates low-quality
transport resources. This parameter must be set in the hybridtransmission
scenario. In other scenarios, the default value of this parameter is used.The
parameter takes effect only in LTE.

Path Check Indicates whether to use the PING detection to check an IP path.
Generally used to detect the connectivity of the IP path, the PING detection will
fail if the firewall disables the PING function.This parameter will be removed
from later versions. In this version, however, the setting of the parameter will be
synchronized to the M2000 from the BS or delivered to the BS from the M2000.
Note that this parameter is no longer used internally. Therefore, it is
recommended that this parameter not be used.

IPMUX Switch Flag Indicates whether the IPMUX function is enabled on IP paths. The eNodeB
currently does not support this function.

Max Timer Indicates the length of the IPMUX timer, which defines the maximum buffer
time for IPMUX packets. The eNodeB currently does not support the IPMUX
function.

Max Frame Length Indicates the maximum multiframe length of IPMUX. The eNodeB currently
does not support the IPMUX function.

Max Subframe Length Indicates the maximum subframe length of IPMUX. The eNodeB currently does
not support the IPMUX function.

Realtime TX Bandwidth Indicates the actual real-time traffic transmitted on the IP path.The parameter
takes effect only in LTE.

Realtime RX Bandwidth Indicates the actual real-time traffic received on the IP path.The parameter takes
effect only in LTE.

Non-Realtime TX Indicates the actual non-real-time traffic transmitted on the IP path.The


Bandwidth
parameter takes effect only in LTE.

Non-Realtime RX Indicates the actual non-real-time traffic received on the IP path.The parameter
Bandwidth
takes effect only in LTE.
Table 2 Related parameters

Parameter Description

Non-Realtime Reserved Indicates the actual TX bandwidth reserved for the non-real-time service
TX Bandwidth
transmitted on the IP path.The parameter takes effect only in LTE.

Non-Realtime Reserved Indicates the actual RX bandwidth reserved for the non-real-time service
RX Bandwidth
received on the IP path.The parameter takes effect only in LTE.

IP Path Check Result Indicates the check result for the GTP-U static detection of an IP path.The
parameter takes effect only in LTE.

Transmission Resource Indicates the ID of the transmission resource group established on an IP path.
Group ID

Description Indicates the description about the peer of the IP path.

Subboard Type Indicates the type of sub-board on the board where the IP path is established.

VRF Index Indicates the index of a VRF instance. The NodeB currently supports default
routes domain only (the VRF index is 0).

Join Transmission Indicates whether the IP path joins a transmission resource group. If this
Resource Group
parameter is set to DISABLE, the IP path is established on the default
transmission resource group on a specific physical port.

RX Bandwidth Indicates the actual total traffic received on the IP path.

TX Bandwidth Indicates the actual total traffic transmitted on the IP path.

5.7.1.6.1.51 IPPATH6
TRANSPORT
+-IPITF6
+-IPPATH6

Description

This MO defines an IPv6 service transmission channel between the BS and other NEs. The
channel is used to differentiate IPv6 transmission services through parameters such as IPv6
addresses of both ends of the channel and service quality.

Effective Scenario
Immediately

Relations Between MOs

Possible parents:
IPITF6

Relation with the RSCGRP MO:


- If JNRSCGRP in an IPPATH6 MO is set to ENABLE, the associated RSCGRP MO must
have been configured.
Relation with the IPPATH MO:
- PATHID in an IPPATH6 MO must be different from PATHID in an IPPATH MO.
Relation with the IPPATH6 MO:
- The values of LOCALIP6 and PEERIP6 in an IPPATH6 MO constitute an address pair.
Any two IPPATH6 MOs with PATHTYPE set to ANY cannot have the same address pair. Two
IPPATH6 MOs with PATHTYPE set to FIXED can have the same address pair. With the same
address pair, the two MOs must have different DSCP values.
- On a BS, the sum of IPPATH6 and IPPATH MOs must be smaller than or equal to 320.
- In an IPPATH6 MO, LOCALIP6 must be set to a global unicast address.
Relation with the DEVIP6 MO:
- LOCALIP6 in an IPPATH6 MO must be a locally configured DEVIP6 MO at the
corresponding physical port.
Relation with the IPITF6 MO:
- PT in the IPITF6 MO corresponding to ITFIDX in an IPPATH6 MO cannot be set to
LOOPIF.
Relation with the USERPLANEHOST,USERPLANEPEER,EPGROUP MOs:
- When USERPLANEHOST MO and USERPLANEPEER MO are configured in one
EPGROUP MO simultaneously and their IP versions are set to IPv6,these MOs cannot coexist
with IPPATH6 with PATHTYPE set to FIXED.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD IPPATH6 Use this command to add an IPv6 path.


Table 1 Related MML commands

MML Command Function

DSP IPPATH6 Use this command to query the status of an IPv6 path.

LST IPPATH6 Use this command to list the configuration of an IPv6 path.

MOD IPPATH6 Use this command to modify the configuration of an IPv6 path.

RMV IPPATH6 Use this command to remove an IPv6 path.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Path ID Indicates the ID of an IPv6 path, which identifies a unique IPv6 path.

Join Transmission Indicates whether the IPv6 path joins a transmission resource group.
Resource Group

Transmission Resource Indicates the ID of the transmission resource group to which an IPv6 path is
Group ID
added.

Interface Index Indicates the index of the IPv6 interface used by an IPv6 path.

Path Type Indicates the type of IPv6 path. The value FIXED indicates that the current IPv6
path only carries services of a fixed QoS. The value ANY indicates that the
current IPv6 path can carry services of any QoS.

DSCP Indicates the Differentiated Services Code Point (DSCP) of services allowed to
be carried on an IPv6 path.

Local IPv6 Address Indicates the local IPv6 address of an IPv6 path. This IPv6 address must be a
global unicast address.

Peer IPv6 Address Indicates the peer IPv6 address of an IPv6 path. This IPv6 address must be a
global unicast address.

Path Check Indicates whether to enable ping detection for an IPv6 path. Ping detection can
be used to check the connectivity of an IPv6 path.This parameter will be
removed in later versions.In this version, however, the setting of the parameter
Table 2 Related parameters

Parameter Description

will be synchronized to the M2000 from the BS or delivered to the BS from the
M2000. Note that this parameter is no longer used internally. Therefore, it is
recommended that this parameter not be used.

Realtime TX Bandwidth Indicates the actual real-time services transmitted on an IPv6 path.

Realtime RX Bandwidth Indicates the actual real-time services received on an IPv6 path.

Non-Realtime TX Indicates the actual non-real-time services transmitted on an IPv6 path.


Bandwidth

Non-Realtime RX Indicates the actual non-real-time services received on an IPv6 path.


Bandwidth

Non-Realtime Reserved Indicates the TX bandwidth reserved for non-real-time services on an IPv6 path.
TX Bandwidth

Non-Realtime Reserved Indicates the RX bandwidth reserved for non-real-time services on an IPv6 path.
RX Bandwidth

Description Info Indicates the description about the peer of the IPv6 path.

5.7.1.6.1.52 IPPATHRT
TRANSPORT
+-IPPATHRT

Description

The IPPATHRT MO enables data to be forwarded on different paths according to the source IP
address. This MO is used to carry services with various QoS requirements on the networks with
different QoS features. An IP path route and an IP path work together to implement the function
of hybrid transport.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the OMCH MO:


- In a routing domain,IP in an OMCH MO must be different from NEXTHOPIP in an
IPPATHRT MO.
Relation with the DEVIP MO:
- The value of SRCIP in an IPPATHRT MO must be the same as the IP address in a
configured DEVIP MO that meets both of the following conditions: (1) The DEVIP MO is in
the same routing domain as the IPPATHRT MO. (2) The port type in the DEVIP MO is set to
ETH, ETHTRK, LOOPINT, or SUBIF.
- The board whose IP address is used by SRCIP in an IPPATHRT MO must have a DEVIP
MO that meets both of the following conditions: (1) The IP address in the DEVIP MO and
NEXTHOPIP are different but on the same network segment. (2) The DEVIP and IPPATHRT
MOs are in the same routing domain.
- NEXTHOPIP in an IPPATHRT MO cannot be set to a broadcast IP address of the network
segment where the DEVIP MO on the egress port is located, and Network ID and Host ID
cannot be all 0 or all 1.
- If a DEVIP MO and an IPPATHRT MO are in the same routing domain, IP in the DEVIP
MO must be different from NEXTHOPIP in the IPPATHRT MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD IPPATHRT Use this command to add an IP path route.

DSP IPPATHRT Use this command to list the status of the IP path routes.

LST IPPATHRT Use this command to list the configuration of the IP path routes.

RMV IPPATHRT Use this command to remove an IP path route.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

VRF Index Indicates the index of a VRF instance.

Source IP Indicates the source IP address of an IP path route. The source IP address must
be the same as the configured device IP address.

Destination IP Indicates the destination IP address of an IP path route.

Transport Resource Indicates the type of transport resource carried on an IP path route. The value
Type
HQ indicates high-quality transport resources, and the value LQ indicates low-
quality transport resources.

Next Hop IP Indicates the next hop IP address of an IP path route. The next hop IP address
and the configured device IP address must be on the same network segment, but
cannot be the same.

5.7.1.6.1.53 IPPMSESSION
TRANSPORT
+-IPPMSESSION

Description

The IPPMSESSION MO is used to initiate IP Performance Monitoring (IP PM) to obtain the
status, such as the delay, jitter, and packet loss ratio, of the transmission line.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the DEVIP MO:


- If BINDPATH in an IPPMSESSION MO is set to NO, IP in any DEVIP MO in the same
routing domain must be different from PEERIP in the IPPMSESSION MO.
- If BINDPATH and IPPMTYPE in an IPPMSESSION MO are set to NO and
THREE_TUPLE, respectively, in the same routing domain SBT in any DEVIP MO must be set
to BASE_BOARD or ETH_COVERBOARD.
Relation with the MPGRP MO:
- If BINDPATH in an IPPMSESSION MO is set to NO, LOCALIP in the associated
MPGRP MO must be different from PEERIP in the IPPMSESSION MO.
Relation with the PPPLNK MO:
- If BINDPATH in an IPPMSESSION MO is set to NO, LOCALIP in the associated
PPPLNK MO must be different from PEERIP in the IPPMSESSION MO.
Relation with the IPPATH MO:
- If BINDPATH in an IPPMSESSION MO is set to YES, the IPPATH MO specified by
PATHID in the IPPMSESSION MO must have been configured.
- If BINDPATH and IPPMTYPE in an IPPMSESSION MO are set to YES and
THREE_TUPLE, respectively, PATHTYPE in the IPPATH MO whose PATHID is the same as
PATHID in the IPPMSESSION MO must be set to ANY.
- If BINDPATH and IPPMTYPE in an IPPMSESSION MO are set to YES and
THREE_TUPLE, respectively, SBT in the IPPATH MO whose PATHID is the same as
PATHID in the IPPMSESSION MO must be set to BASE_BOARD or ETH_COVERBOARD.
Relation with the IPPMSESSION MO:
- Any two IPPMSESSION MOs whose IPPMTYPE is set to FOUR_TUPLE must have
different combinations of LOCALIP, PEERIP, and IPPMDSCP.If IPPMTYPE is set to
THREE_TUPLE in only one IPPMSESSION MO or both IPPMSESSION MOs, the two MOs
must have different combinations of LOCALIP and PEERIP.
- A maximum of 128 IPPMSESSION MOs can be configured on a main control board.
- A maximum of 128 IPPMSESSION MOs can be configured on a transmission board.
Relation with the DEVIP,PPPLNK,MPGRP MOs:
- If BINDPATH in an IPPMSESSION MO is set to NO, the IP address corresponding to
LOCALIP in the IPPMSESSION MO must have been configured. That is, for the
IPPMSESSION MO, DEVIP MO in the same routing domain, PPPLNK MO, and MPGRP
MO configured on the same board, LOCALIP in the IPPMSESSION MO must be the same as
any of the following: IP in the DEVIP MO; LOCALIP in the PPPLNK MO; or LOCALIP in
the MPGRP MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD IPPMSESSION Use this command to add an IP Performance Monitoring (PM) session.

DSP IPPMSESSION Use this command to query the status of an IP PM session. The status
information includes parameters such as the transmission line delay, jitter, and
packet loss rate.

LST IPPMSESSION Use this command to list the configuration of the IP PM session.

RMV IPPMSESSION Use this command to remove an IP PM session.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Session ID Indicates the ID of an IP PM session of an NE.

Local IP Indicates the local IP address of an IP PM session. This IP address excluding


0.0.0.0 must be configured at the Ethernet port, Ethernet trunk, or loopback
interface.

Peer IP Indicates the peer IP address of the IP PM session. This IP address must be a
valid IP address of Class A, B, or C and different from any existing IP address of
the local end. In addition, it cannot be set to 0.x.x.x or 127.x.x.x.

DSCP Indicates the Differentiated Services Code Point (DSCP) of an IP PM session.

Activate Direction Indicates that the activation direction of the IP PM session. For this parameter to
be valid, the peer must also support the IP PM session. If this parameter is set to
UP, the IP PM session initiated by the BS is activated. If this parameter is set to
BIDIR, the IP PM sessions initiated by BS and the peer are activated. Before
configuring IP PM bidirectionally activated IP PM sessions, ensure that the peer
device supports IP PM bidirectionally activated IP PM sessions. The WMPT or
UTRP does not support BIDIR. The activation direction is specified by the DIR
parameter.

Round Trip Time Indicates the round-trip delay calculated by an IP PM session detection. The
round-trip delay is the time that is consumed to transmit IP PM detection packets
Table 2 Related parameters

Parameter Description

to and fro between the local and peer ends.

RX Jitter Indicates the DL jitter calculated by an IP PM session detection.

TX Jitter Indicates the UL jitter calculated by an IP PM session detection.

RX Loss Rate Indicates the DL packet loss rate calculated by an IP PM session detection.

TX Loss Rate Indicates the UL packet loss rate calculated by an IP PM session detection.

Activate State(Up) Indicates the UL activation status of an IP PM session.

Activate State(Down) Indicates the DL activation status of an IP PM session.

IP PM Type Indicates the type of IP PM session. A triplet consists of the local IP address,
peer IP address, and protocol type; a quadbit consists of the local IP address,
peer IP address, protocol type, and DSCP.

Bind IP Path Indicates whether to bind the IP PM session to an IP path. If the IP PM session is
bound to an IP path, the IP PM session uses the local and peer IP addresses of
the IP path in data transmission. In addition, if TXBWASW or RXBWASW is
set to ON and TCSW is set to ENABLE in the algorithm for the transmission
resource group associated with the IP path, the system dynamically adjusts the
TX or RX bandwidth of the transmission resource group based on the IP PM
detection result.

IP Path ID Indicates the ID of the IP path to which an IP PM session is bound.

DSCP Change Indicates whether the DSCP value of a DL IP PM session changes.


Flag(Down)

DSCP Initial Indicates the initial DSCP value of a DL IP PM session.


Value(Down)

DSCP Changed Indicates the modified DSCP value of a DL IP PM session.


Value(Down)

DSCP Changed Date Indicates the time when the DSCP value of a DL IP PM session changes.
And Time(Down)

DSCP Change Flag(Up) Indicates whether the DSCP value of an UL IP PM session changes.

DSCP Initial Value(Up) Indicates the initial DSCP value of an UL IP PM session.

DSCP Changed Indicates the modified DSCP value of an UL IP PM session.


Value(Up)
Table 2 Related parameters

Parameter Description

DSCP Changed Date Indicates the time when the DSCP value of an UL IP PM session changes.
And Time(Up)

IP PM Protocol Version Indicates the version of the negotiated data, when the status of IP PM is UP.

5.7.1.6.1.54 IPRT
TRANSPORT
+-IPRT

Description

The IPRT MO refers to the routing table, which is used for data forward. It can be manually
configured.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the IPRT MO:


- If an IPRT MO and a DEVIP MO are on the same network segment and are in the same
routing domain, NEXTHOP in the IPRT MO cannot be set to the broadcast IP address for the
DEVIP MO. That is, in the IP address consisting of NEXTHOP in the IPRT MO and MASK in
the DEVIP MO, the network ID cannot be all 0s and the host ID cannot be all 1s.
- In the same routing domain, a maximum of one IPRT MO whose DSTIP and DSTMASK
are both set to 0.0.0.0 can be configured on a BS.
- A maximum of 132 IPRT MOs can be configured on a board.
- In any two IPRT MOs in the same routing domain on a BS, if RTTYPE and IFT in one
IPRT MO are set to IF and TUNNEL, respectively, the two MOs must have different DSTIP
values.
- On a BS, the sum of IPRT6 and IPRT MOs must be smaller than or equal to 132.
- Each IPRT MO must have a unique combination of CN, SRN, SN, SBT, VRFIDX, DSTIP,
DSTMASK, RTTYPE, IFT, IFNO, and NEXTHOP.
Relation with the DEVIP MO:
- If an IPRT MO and a DEVIP MO are in the same routing domain, NEXTHOP in the IPRT
MO must be different from IP in the DEVIP MO.
- If an IPRT MO and a DEVIP MO whose PT is set to ETH, ETHTRK, or SUBIF are in the
same routing domain, NEXTHOP in the IPRT MO must be on the same network segment as IP
in the DEVIP MO. In addition, CN, SRN, SN, and SBT in the DEVIP MO must be the same as
CN, SRN, SN, and SBT in the IPRT MO, respectively.
- If RTTYPE and IFT in an IPRT MO are set to IF and TUNNEL, respectively, DSTIP in the
IPRT MO must be different from IP in a DEVIP MO in the same routing domain.
- If RTTYPE and IFT in an IPRT MO are set to IF and TUNNEL, respectively, DSTIP in the
IPRT MO must be different from IP in a DEVIP MO in the same routing domain or from the
logical AND-operation result of IP and MASK.
Relation with the OMCH MO:
- If an IPRT MO and an OMCH MO are in the same routing domain, NEXTHOP in the
IPRT MO must be different from IP in the OMCH MO.
- If BRT in an OMCH MO is set to YES, before configuring the RTIDX in this OMCH MO,
ensure that the IPRT MO with the same routing domain for the OMCH MO have been
configured. That is, in the same routing domain, the IPRT MOs whose RTIDX is the same as
RTIDX in the OMCH MO must have been configured.
- If BINDSECONDARYRT in an OMCH MO is set to YES, before configuring the
SECONDARYRTIDX in this OMCH MO, ensure that the IPRTwith the same routing domain
for the OMCH MO have been configured. That is, in the same routing domain, the IPRT MOs
whose RTIDX is the same as SECONDARYRTIDX in the OMCH MO must have been
configured.
- If RTTYPE and IFT in an IPRT MO are set to IF and TUNNEL, DSTIP in an IPRT MO
must be different from IP in an OMCH MO.
- If BEAR is set to IPv4 and BRT is set to YES in an OMCH MO, in the same routing
domain, the IPRT MOs whose RTIDX is the same as RTIDX in the OMCH MO must have
been configured. If the RTTYPE is set to IF, the IFT must not be set to IPOA.
- If BEAR is set to IPv4 and BINDSECONDARYRT is set to YES in an OMCH MO, in the
same routing domain, the IPRT MOs whose RTIDX is the same as SECONDARYRTIDX in
the OMCH MO must have been configured. If the RTTYPE is set to IF, the IFT must not be set
to IPOA.
Relation with the PPPLNK MO:
- If RTTYPE and IFT are set to IF and PPP, respectively in an IPRT MO, IFNO in the IPRT
MO must be the same as PPPLNKN in the associated PPPLNK MO.
- If RTTYPE and IFT in an IPRT MO are set to IF and TUNNEL, DSTIP in an IPRT MO
must be different from LOCALIP in an PPPLNK MO.
Relation with the MPGRP MO:
- If RTTYPE and IFT are set to IF and MPGRP, respectively in an IPRT MO, IFNO in the
IPRT MO must be the same as MPGRPN in the associated MPGRP MO.
- If RTTYPE and IFT in an IPRT MO are set to IF and TUNNEL, DSTIP in an IPRT MO
must be different from LOCALIP in an MPGRP MO.
Relation with the TUNNEL MO:
- If RTTYPE and IFT are set to IF and TUNNEL, respectively in an IPRT MO, IFNO in the
IPRT MO must be the same as TUNNELID in the associated TUNNEL MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD IPRT Use this command to add a static IP route.

DSP IPRT Use this command to query the information about all reachable IP routes.

LST IPRT Use this command to list the information about all the static IP routes.

MOD IPRT Use this command to modify the configuration of an IP route.

RMV IPRT Use this command to remove a static IP route.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Route Index Indicates the index of an IP route.

Cabinet No. Indicates the cabinet number of the board where the IP route is located.

Subrack No. Indicates the subrack number of the board where the IP route is located.

Slot No. Indicates the slot number of the board where the IP route is located.
Table 2 Related parameters

Parameter Description

Subboard Type Indicates the type of sub-board on the board where the IP route is established.

Port Type Indicates the type of port.

Port No. Indicates the port number.

Route Type Indicates the type of route. If this parameter is set to NEXTHOP, all the IP
packets that meet the route direction are first forwarded to the specified next hop
IP address. If this parameter is set to IF, all the IP packets that meet the route
direction are first forwarded to the specified egress port.

VRF Index Indicates the index of a VRF instance. The NodeB currently supports default
routes domain only (VRF index is 0).

Destination IP Indicates the destination IP address of the route.

Mask Indicates the subnet mask for the destination IP address of the route.

Next Hop IP Indicates the IP address of the next hop.

Preference Indicates the priority of the routing table entry. A smaller parameter value
indicates a higher priority.

Description Info Indicates the description about the destination of the route.

Protocol Indicates the type of the IP route. A static host route is a manually configured
route with the subnet mask set to 255.255.255.255. A static gateway route is a
manually configured route, in which the subnet mask is not set to
255.255.255.255. A dynamic host route is a dynamically generated route with
the subnet mask set to 255.255.255.255. A dynamic gateway route is a
dynamically generated route, in which the subnet mask is not set to
255.255.255.255.

Actual Port Type Indicates the type of the port.

Actual Port No. Indicates the port number.

5.7.1.6.1.55 IPRT6
TRANSPORT
+-IPRT6

Description

The IPRT6 is a static IPv6 route, which is used for data forwarding through route table.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the DEVIP6 MO:


- IPV6 in a DEVIP6 MO must be different from NEXTHOPIP in an IPRT6 MO.
- If NEXTHOPIP6TYPE in an IPRT6 MO is set to
IPADDR6_TYPE_GLOBAL_UNICAST, the DEVIP6 MO whose IPV6 has the same prefix as
the global unicast address must have been configured.
Relation with the IPITF6 MO:
- If NEXTHOPIP6TYPE in an IPRT6 MO is set to IPADDR6_TYPE_LINK_LOCAL, the
IPITF6 MO corresponding to ITFIDX in the IPRT6 MO must have been configured.
- If NEXTHOPIP6TYPE in an IPRT6 MO is set to IPADDR6_TYPE_LINK_LOCAL, the
IPITF6 MO corresponding to ITFIDX in the IPRT6 MO cannot be a loopback port.
Relation with the IPRT6 MO:
- A maximum of one IPRT6 MO with load sharing enabled can be configured on a BS.
- On a BS, the sum of IPRT6 and IPRT MOs must be smaller than or equal to 132.
- A maximum of 64 IPRT6 MOs can be configured on a board.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD IPRT6 Use this command to add a static IPv6 route.

DSP IPRT6 Use this command to query the IPv6 routing table.
Table 1 Related MML commands

MML Command Function

LST IPRT6 Use this command to list the static IPv6 route configuration.

MOD IPRT6 Use this command to modify the description of a static IPv6 route.

RMV IPRT6 Use this command to remove a static IPv6 route.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Destination IPv6 Indicates the destination IPv6 address of the static IPv6 route.
Address

Prefix Length Indicates the prefix length of the destination IPv6 address of the static IPv6
route.

Route Type Indicates the next hop type of static IPv6 route.
If this parameter is set to NEXTHOP, all the IP packets meeting the route
direction are first forwarded to the next hop IPv6 address, and then forwarded to
other addresses.

Next Hop IPv6 Type Indicates the type of next hop IPv6 address.

Next Hop IPv6 Address Indicates the next hop IPv6 address of the static IPv6 route.

Interface Index Indicates the index of the IPv6 interface to which a static IPv6 route belongs.

Preference Indicates the priority of a static IPv6 route. A smaller parameter value indicates a
higher priority.

Protocol Indicates the type of the static IPv6 route. A static host route is a manually
configured route with a 128-bit prefix. A static gateway route is a manually
configured route with a non-128-bit prefix, with the next hop IP address on a
different network segment from the egress port IP address. A dynamic host route
is a dynamically learned (not manually configured) route with a 128-bit prefix.
A dynamic gateway route is a dynamically learned (not manually configured)
route with a non-128-bit prefix, with the next hop IP address on a different
Table 2 Related parameters

Parameter Description

segment from the egress port IP address.

Description Info Indicates the description about the destination of a static IPv6 route.

5.7.1.6.1.56 IPSECBIND
TRANSPORT
+-IPSECBIND

Description

This MO indicates the binding relation between the IP Security (IPSec) policy group and the
port. An IPSec tunnel is negotiated to protect the data streams on a port only after an IPSec
policy group is bound to the port.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the HAGRP MO:


- In one logical protection group, SN in an HAGRP MO must be the same as that in an
IPSECBIND MO.
Relation with the ACLRULE,IPSECPOLICY MOs:
- The maximum of ACLRULE which are referenced by IPSECBIND on one board is 128.
Relation with the ETHTRK MO:
- Before binding an IPSECPOLICY to an ETHTRK MO, ensure that the ETHTRK MO is
configured.
Relation with the ETHTRKLNK MO:
- Before configuring an IPSECBIND MO on an ETHPORT MO, ensure that the ETHPORT
MO has not been added to an ETHTRK MO.
- Before binding an IPSECPOLICY MO to an ETHTRK MO, ensure that an
ETHTRKLNK MO is configured in the ETHTRK MO.
Relation with the IPSECPOLICY MO:
- The IPSECPOLICY MO associated with an IPSECBIND MO must have been configured.
- If the IPSECBIND MO with CTRLMODE set to MANUAL_MODE is configured, the
IPSECPOLICY MO with CTRLMODE set to MANUAL_MODE referenced by this
IPSECBIND MO must also have been configured.
Relation with the IPSECDTNL MO:
- In an IPSECDTNL MO, the active and standby IPSECPOLICY MOs must be bound to
ports; the active and standby IPSECPOLICY MOs must be bound to two different
IPSECBIND MOs, and the SPGN values in the two IPSECBIND MOs are the same as the
SPGN values in the active and standby IPSECPOLICY MOs, respectively.
Relation with the PORTSECURITY MO:
- Before adding an IPSECBIND MO, ensure that SWITCH in the PORTSECURITY MO
on the bound Ethernet port is set to ENABLE.
Relation with the IPSECBIND MO:
- One IPSECPOLICY MO can be bound to only one port.
- On a BS, the total number of IPSECBIND and IPSECBIND6 MOs must be smaller than or
equal to 4.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD IPSECBIND Use this command to bind an IPSec policy group to a port. IPSec tunnels are
negotiated to protect the data streams flowed through a port only after an IPSec
policy group is bound to the port.

DSP IKEMSGSTAT Use this command to query statistics on Internet Key Exchange (IKE) messages.

DSP IKESA Use this command to query the status of the IKE Security Association (SA).

DSP IKESTAT Use this command to query basic information about an Internet Key Exchange
(IKE) Security Association (SA).

DSP IKEV1EXCHSTAT Use this command to query status information about an Internet Key Exchange
version 1 (IKEv1) exchange.
Table 1 Related MML commands

MML Command Function

DSP IKEV2EXCHSTAT Use this command to query status information about an Internet Key Exchange
version 2 (IKEv2) exchange.

DSP IPSECSA Use this command to query the status of the IPSec SA.

DSP Use this command to query statistics on an IP Security (IPSec) SA.


IPSECSADELSTAT

LST IPSECBIND Use this command to list the binding relation between the IPSECBIND MO and
the port.

MOD IPSECBIND Use this command to modify the binding relationship between an IPSec policy
group and a port.

RMV IPSECBIND Use this command to remove the binding of an IPSec policy group to a port. The
execution of this command terminates the protection mechanism applied to the
data streams flowed through the port.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the port to which the IPSec policy group is
bound.

Subrack No. Indicates the subrack number of the port to which the IPSec policy group is
bound.

Slot No. Indicates the slot number of the port to which the IPSec policy group is bound.

Subboard Type Indicates the type of sub-board on the board with the port to which the IPSec
policy group is bound.

Port Type Indicates the type of port to which the IPSec policy group is bound.

Port No. Indicates the number of the port to which the IPSec policy group is bound.

Policy Group Name Indicates the name of the IPSec policy group.
Table 2 Related parameters

Parameter Description

Control Mode Indicates whether the object can be modified or deleted by the system. The value
MANUAL_MODE means that only the user can modify or delete the object.
The value AUTO_MODE means that both the system and the user can modify or
delete the object.

Auto Config Flag Indicates whether the object is created by the system. MANUAL_CREATED
means that the object is configured by the user manually. AUTO_CREATED
means that the object is created by the system.

5.7.1.6.1.57 IPSECBIND6
TRANSPORT
+-IPSECBIND6

Description

An IPSECBIND6 MO defines the binding relationship between an IPv6 security policy group
and an IPv6 interface. An IPSec tunnel is negotiated to protect the data flows transmitted on an
IPv6 port only after an IPv6 security policy group is bound to the port.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the IPSECPOLICY6 MO:


- The IPSECPOLICY6 MO corresponding to an IPSECBIND6 MO must have been
configured.
- If the IPSECBIND6 MO with CTRLMODE set to MANUAL_MODE is configured, the
IPSECPOLICY6 MO with CTRLMODE set to MANUAL_MODE referenced by this
IPSECBIND6 MO must also have been configured.
Relation with the IPSECBIND6 MO:
- On a BS, the total number of IPSECBIND and IPSECBIND6 MOs must be smaller than or
equal to 4.
- One IPSECPOLICY6 MO can be bound to only one port.
Relation with the ETHTRKLNK MO:
- Before binding an IPSECPOLICY6 MO to an ETHTRK MO, ensure that an
ETHTRKLNK MO has been configured under the ETHTRK MO.
Relation with the PORTSECURITY MO:
- Before adding an IPSECBIND6 MO, ensure that SWITCH in the PORTSECURITY MO
on the bound Ethernet port has been set to ENABLE.
Relation with the IPITF6 MO:
- The IPITF6 MO corresponding to ITFIDX in an IPSECBIND6 MO must have been
configured.
- In an IPITF6 MO referenced by an IPSECBIND6 MO, ITFTYPE must be set to
NORMAL and PT must be set to ETH or TRUNK.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD IPSECBIND6 Use this command to bind an IPv6 IPSec policy group to an interface. An IPv6
IPSec tunnel is negotiated to protect the data streams transmitted on an IPv6
interface only after an IPv6 IPSec policy group is bound to the interface.

DSP IKESA6 Use this command to query the status of an IPv6 IKE SA.

DSP IPSECSA6 Use this command to query the status of an IPv6 IPSec SA.

LST IPSECBIND6 Use this command to list the binding relationships between IPv6 IPSec policy
groups and IPv6 interfaces.

MOD IPSECBIND6 Use this command to modify the binding relationship between an IPv6 IPSec
policy group and an interface index.

RMV IPSECBIND6 Use this command to remove the binding relationship between an IPv6 IPSec
policy group and an IPv6 interface. Running this command will terminate the
protection of data streams on the IPv6 interface.
Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Interface Index Indicates the number of the port to which the IPv6 security policy group is
bound.

IPv6 IPSec Policy Indicates the name of the IPv6 security policy group.
Group Name

Control Mode Indicates whether the object can be modified or deleted by the system. The value
MANUAL_MODE means that only the user can modify or delete the object.
The value AUTO_MODE means that both the system and the user can modify or
delete the object.

Auto Config Flag Indicates whether the object is created by the system. MANUAL_CREATED
means that the object is configured by the user manually. AUTO_CREATED
means that the object is created by the system.

5.7.1.6.1.58 IPSECDTNL
TRANSPORT
+-IPSECDTNL

Description

An IPSECDTNL MO consists of the parameters related to an IPSec tunnel pair, such as the
IPSec policies and BFD sessions referenced by the IPSec tunnel pair. An IPSec tunnel pair, that
is, two IPSec tunnels between the BS and two security gateways (Se-GWs), enhances the
transmission security between the BS and the core network (CN) or between the BS and the
M2000. In implementation, if an IPSec tunnel becomes faulty and the other tunnel is detected to
be normal, the BS automatically switches over to the other tunnel and resumes secure
transmission with the CN or M2000.

Effective Scenario

Immediately

Relations Between MOs


Possible parents:
TRANSPORT

Relation with the IPSECPOLICY,BFDSESSION MOs:


- In an IPSECDTNL MO, SRCIP in the BFDSESSION MOs for the active and standby
tunnels must be the same as LOCALIP in the IKEPEER MOs of the active and standby
IPSECPOLICY MOs, respectively; DSTIP in the BFDSESSION MOs for the active and
standby tunnels must be the same as REMOTEIP in the IKEPEER MOs of the active and
standby IPSECPOLICY MOs, respectively.
Relation with the IPSECDTNL MO:
- The active and standby IPSECPOLICY MOs in an IPSECDTNL MO must be different.
That is, the combination of MSPGN and SSPGN MOs in the active IPSECPOLICY MO must
different from the combination of MSPSN and SSPSN MOs in the standby IPSECPOLICY
MO.
- ENCAPMODE in the IPSECPROPOSAL MO used by the IPSECPOLICY MO in an
IPSECDTNL MO must be set to TUNNEL.
- The active and standby IPSECPOLICY MOs in one IPSECDTNL MO must be different
from those in other IPSECDTNL MOs.
Relation with the IPSECPOLICY MO:
- The primary and secondary IPSECPOLICY MOs associated with an IPSECDTNL MO
must have been configured. SPGN and SPSN in the primary IPSECPOLICY MO are the same
as MSPGN and MSPSN in the IPSECDTNL MO, respectively; SPGN and SPSN in the
secondary IPSECPOLICY MO are the same as SSPGN and SSPSN in the IPSECDTNL MO,
respectively.
- The active and standby IPSECPOLICY MOs in an IPSECDTNL MO must have ACLID
of the same value.
- The active and standby IPSECPOLICY MOs in an IPSECDTNL MO must reference
different IKEPEER MOs.
- ACLID in the active and standby IPSECPOLICY MOs in an IPSECDTNL MO must be
different from that in other IPSECPOLICY MOs.
- The IPSECBIND MO in the active and standby IPSECPOLICY MOs of an IPSECDTNL
MO must be bound to the same board. That is, the combination of CN, SRN, and SN in the two
IPSECBIND MOs must be the same.
Relation with the IPSECBIND MO:
- In an IPSECDTNL MO, the active and standby IPSECPOLICY MOs must be bound to
ports; the active and standby IPSECPOLICY MOs must be bound to two different
IPSECBIND MOs, and the SPGN values in the two IPSECBIND MOs are the same as the
SPGN values in the active and standby IPSECPOLICY MOs, respectively.
Relation with the BFDSESSION MO:
- Before adding an IPSECDTNL MO, ensure that the BFDSESSION MOs for the active and
standby tunnels of the IPSECDTNL MO have been configured. That is, in the same routing
domain the BFDSESSION MOs whose BFDSN is the same as MBFDSN and SBFDSN in the
IPSECDTNL MO, respectively must have been configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD IPSECDTNL Use this command to add an IPSec tunnel pair. An IPSec tunnel pair, that is, two
IPSec tunnels between the BS and two security gateways (SeGWs), enhances
the transmission security between the BS and the core network (CN) or between
the BS and the M2000. Each IPSec tunnel pair references two BFD sessions:
one used to detect the status of the primary IPSec tunnel, and the other used to
detect that of the secondary IPSec tunnel. If the BFD detection result for the
IPSec tunnel in use shows that the Se-GW is unreachable or the associated IPSec
security associations (SAs) are abnormal, the other IPSec tunnel takes over
automatically and resumes secure transmission if it is detected to be normal and
the associated IPSec SAs are normal. IPSec SAs corresponding to all the ACL
rules in the ACL referenced by an IPSec tunnel are considered normal only
when these IPSec SAs are successfully negotiated.

DSP IPSECDTNL Use this command to query the information about an IPSec tunnel pair.

LST IPSECDTNL Use this command to list the information about an IPSec tunnel pair.

MOD IPSECDTNL Use this command to modify the configuration of an IPSec tunnel pair.

RMV IPSECDTNL Use this command to remove an IPSec tunnel pair.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

IPSec Dual Tunnel ID Indicates the ID of the IPSec tunnel pair. It uniquely identifies a pair of primary
and secondary IPSec tunnels.
Table 2 Related parameters

Parameter Description

Master Policy Group Indicates the name of the primary IPSec policy group. The primary IPSec tunnel
Name
uses an IPSec policy in the primary IPSec policy group.

Master IPSec Indicates the ID of the primary IPSec policy. The primary IPSec tunnel uses the
Sequence No.
primary IPSec policy, which is identified by this parameter and the MSPGN
parameter together.

Slave Policy Group Indicates the name of the secondary IPSec policy group. The secondary IPSec
Name
tunnel uses an IPSec policy in the secondary IPSec policy group.

Slave IPSec Sequence Indicates the ID of the secondary IPSec policy. The secondary IPSec tunnel uses
No.
the secondary IPSec policy, which is identified by this parameter and the
SSPGN parameter together.

Master Tunnel's BFD Indicates the ID of the BFD session referenced by the primary IPSec tunnel.
Session ID

Slave Tunnel's BFD Indicates the ID of the BFD session referenced by the secondary IPSec tunnel.
Session ID

Current Used IPSec Indicates the IPSec policy in use. If the primary IPSec tunnel is used, the IPSec
Policy
policy in use is the primary IPSec policy. If the slave IPSec tunnel is used, the
IPSec policy in use is the slave IPSec policy.

5.7.1.6.1.59 IPSECPOLICY
TRANSPORT
+-IPSECPOLICY

Description

The IPSECPOLICY MO defines the security measures for different data traffic. The data traffic
to be protected is specified through the reference of an ACL MO, and the security measure to be
used is specified through the reference of an IPSECPROPOSAL MO.

Effective Scenario

Immediately

Relations Between MOs


Possible parents:
TRANSPORT

Relation with the IPSECPOLICY6 MO:


- SPGN in an IPSECPOLICY6 MO is case insensitive and must be different from SPGN in
an IPSECPOLICY MO.
- ACLID in an IPSECPOLICY6 MO must be different from ACLID in an IPSECPOLICY
MO.
Relation with the IPSECBIND,ACLRULE MOs:
- The maximum of ACLRULE which are referenced by IPSECBIND on one board is 128.
Relation with the IPSECPOLICY MO:
- The ACL MO corresponding to an IPSECPOLICY MO must have been configured.
- On the BS, the total number of IPSECPOLICY and IPSECPOLICY6 MOs must be
smaller than or equal to 100.
- ENCAPMODE in the IPSECPROPOSAL MO used by the IPSECPOLICY MO in an
IPSECDTNL MO must be set to TUNNEL.
Relation with the ACLRULE MO:
- Before configuring an IPSECPOLICY MO, ensure that an ACLRULE MO is configured
for the ACL MO referenced by the IPSECPOLICY MO.
Relation with the IKEPEER MO:
- Before configuring an IPSECPOLICY MO, ensure that the associated IKEPEER MO is
configured.
Relation with the IPSECPROPOSAL MO:
- Before configuring an IPSECPOLICY MO, ensure that the associated IPSECPROPOSAL
MO is configured.
Relation with the IPSECBIND MO:
- The IPSECPOLICY MO associated with an IPSECBIND MO must have been configured.
- If the IPSECBIND MO with CTRLMODE set to MANUAL_MODE is configured, the
IPSECPOLICY MO with CTRLMODE set to MANUAL_MODE referenced by this
IPSECBIND MO must also have been configured.
Relation with the IPSECDTNL,BFDSESSION MOs:
- In an IPSECDTNL MO, SRCIP in the BFDSESSION MOs for the active and standby
tunnels must be the same as LOCALIP in the IKEPEER MOs of the active and standby
IPSECPOLICY MOs, respectively; DSTIP in the BFDSESSION MOs for the active and
standby tunnels must be the same as REMOTEIP in the IKEPEER MOs of the active and
standby IPSECPOLICY MOs, respectively.
Relation with the IPSECDTNL MO:
- The primary and secondary IPSECPOLICY MOs associated with an IPSECDTNL MO
must have been configured. SPGN and SPSN in the primary IPSECPOLICY MO are the same
as MSPGN and MSPSN in the IPSECDTNL MO, respectively; SPGN and SPSN in the
secondary IPSECPOLICY MO are the same as SSPGN and SSPSN in the IPSECDTNL MO,
respectively.
- The active and standby IPSECPOLICY MOs in an IPSECDTNL MO must have ACLID
of the same value.
- The active and standby IPSECPOLICY MOs in an IPSECDTNL MO must reference
different IKEPEER MOs.
- ACLID in the active and standby IPSECPOLICY MOs in an IPSECDTNL MO must be
different from that in other IPSECPOLICY MOs.
- The IPSECBIND MO in the active and standby IPSECPOLICY MOs of an IPSECDTNL
MO must be bound to the same board. That is, the combination of CN, SRN, and SN in the two
IPSECBIND MOs must be the same.
Relation with the ACL MO:
- VRFIDX in the ACL MO corresponding to an IPSECPOLICY MO must be set to 0.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD IPSECPOLICY Use this command to add an IP Security (IPSec) policy. An IPSec policy group
consists of IPSec policies with the same group name. An IPSec policy is
identified by the group name (specified by the SPGN parameter) and the policy
number (specified by the SPSN parameter).

DSP IPSECPOLICY Use this command to query the IPSec policy configuration that takes effect.

LST IPSECPOLICY Use this command to list the information about the IPSec policy.

MOD IPSECPOLICY Use this command to modify the configuration of an IPSec policy.

RMV IPSECPOLICY Use this command to remove an IPSec policy.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Policy Group Name Indicates the name of the IPSec policy group.

IPSec Sequence No. Indicates the sequence No. of the IPSec policy group. The smaller the number,
the higher the priority.

ACL ID Indicates the ID of the access control list.

IPSec Proposal Name Indicates the name of the IPSec proposal.

IKE Peer Name Indicates the name of the IKE peer that is referenced by the IPSec policy.

Perfect Forward Indicates the perfect forward secrecy (PFS) value. In the second phase of IPSec
Secrecy
negotiation, PFS enables the BS to use a key that is not derived from the first-
phase key, ensuring that the two keys are independent of each other. According
to PFS, a key protects a unique set of data. The elements used to generate keys
are not reusable. If a key is decrypted, other keys are still secure.
If the IPSec policy is used to initiate IPSec negotiation, a PFS exchange is
launched. If the PFS is assigned to the local end, then the PFS exchange is
required when the negotiation is launched at the peer end. The DH group
assigned to the local end and the peer end should be the same. Otherwise, the
negotiation fails. The security level of the 1024-bit Diffie-Hellman group (Dh-
group2) is higher than that of the 768-bit Diffie-Hellman group (Dh-group1).
However, a longer processing time is required by the Dh-group2.

SA Duration Mode Indicates the configuration mode of the IPSec SA life cycle. If this parameter is
set to GLOBAL, the default SA life cycle is used. In this case, LTS and LTKB
are set to the default values 3600 and 69120000, respectively. If this parameter is
set to LOCAL, the SA life cycle is configurable.

Lifetime Based On Time Indicates the life cycle of an IPSec SA. An IPSec SA becomes invalid once its
life cycle specified by this parameter elapses. Before the life cycle of an IPSec
SA elapses, the IPSec policy is used in an attempt to establish a new IPSec SA
through negotiation to ensure secure transmission; before the negotiation is
complete, the original IPSec SA is still used. After the negotiation is complete,
the new SA is immediately used. IPSec SA negotiation takes a period. To
prevent SA updating from affecting communication security, a life cycle longer
than 900 seconds is recommended.

Lifetime Based On Indicates the traffic volume threshold for the IPSec policy, above which
Traffic
negotiation for a new IPSec SA is started. The value 0 indicates that the
function, which initiates negotiation for a new IPSec SA based on the traffic
volume, is disabled. But when BS acts as initiator in IKEv1 and this value is set
to 0, if the responder insists or enforces the IPSec SA traffic lifetime to BS, BS
Table 2 Related parameters

Parameter Description

will enable this function to avoid service break down.

Control Mode Indicates whether the object can be modified or deleted by the system. The value
MANUAL_MODE means that only the user can modify or delete the object.
The value AUTO_MODE means that both the system and the user can modify or
delete the object.

Cabinet No. Indicates the cabinet number of the board that adopts the IPSec policy.

Subrack No. Indicates the subrack number of the board that adopts the IPSec policy.

Slot No. Indicates the slot number of the board that adopts the IPSec policy.

Anti-Replay Window Indicates the size of the IPSec packet anti-replay window. If the value of this
Size
parameter is set to 0, the IPSec packet anti-replay function is disabled. If the
value of this parameter is set to 32, 64, 128, 256, 512, 1024, 2048 or 4096, the
system checks whether the packets are duplicate in the window. A packet is
discarded if it has a duplicate packet or its sequence number is smaller than any
packet in the window. The window slides if the sequence number of the packet
is larger than any packet that is received in the window.

Auto Config Flag Indicates whether the object is created by the system. MANUAL_CREATED
means that the object is configured by the user manually. AUTO_CREATED
means that the object is created by the system.

5.7.1.6.1.60 IPSECPOLICY6
TRANSPORT
+-IPSECPOLICY6

Description

An IPSECPOLICY6 MO defines the security measures for different data traffic in IPv6
networks. The data traffic to be protected is specified by using an ACL MO. The used ACL may
be of IPv4 or IPv6. The security measure to be used is specified by using an IPSECPROPOSAL
MO.

Effective Scenario
Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the ACLRULE6 MO:


- The ACL6 MO corresponding to an IPSECPOLICY6 MO must have at least one
ACLRULE6 MO.
Relation with the IKEPEER6 MO:
- The IKEPEER6 MO corresponding to an IPSECPOLICY6 MO must have been
configured.
Relation with the IPSECPOLICY MO:
- SPGN in an IPSECPOLICY6 MO is case insensitive and must be different from SPGN in
an IPSECPOLICY MO.
- ACLID in an IPSECPOLICY6 MO must be different from ACLID in an IPSECPOLICY
MO.
Relation with the ACL6 MO:
- The ACL6 MO corresponding to an IPSECPOLICY6 MO must have been configured.
Relation with the IPSECBIND6 MO:
- The IPSECPOLICY6 MO corresponding to an IPSECBIND6 MO must have been
configured.
- If the IPSECBIND6 MO with CTRLMODE set to MANUAL_MODE is configured, the
IPSECPOLICY6 MO with CTRLMODE set to MANUAL_MODE referenced by this
IPSECBIND6 MO must also have been configured.
Relation with the IPSECPOLICY6 MO:
- On the BS, the total number of IPSECPOLICY and IPSECPOLICY6 MOs must be
smaller than or equal to 100.
Relation with the ACL MO:
- The ACL MO that uses the default VRF instance and corresponds to an IPSECPOLICY6
MO must have been configured.
Relation with the ACLRULE MO:
- The ACL MO corresponding to an IPSECPOLICY6 MO must have at least one
ACLRULE MO.
Relation with the IPSECPROPOSAL MO:
- The IPSECPROPOSAL MO corresponding to an IPSECPOLICY6 MO must have been
configured.
Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD IPSECPOLICY6 Use this command to add an IPv6 IPSec policy. The IPv6 IPSec policies that
have the same IPv6 IPSec policy group name form an IPv6 IPSec policy group.
An IPv6 IPSec policy is specified by the combination of IPv6 IPSec policy
group name and IPv6 IPSec policy sequence number.

DSP IPSECPOLICY6 Use this command to query the configurations of IPv6 IPSec policies that take
effect.

LST IPSECPOLICY6 Use this command to list the configurations of IPv6 IPSec policies.

MOD IPSECPOLICY6 Use this command to modify an IPv6 IPSec policy.

RMV IPSECPOLICY6 Use this command to remove an IPv6 IPSec policy.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

IPv6 Policy Group Indicates the name of the IPv6 IPSec policy group.
Name

IPv6 IPSec Sequence Indicates the sequence number of the IPv6 IPSec policy. A larger value of this
No.
parameter indicates a lower priority.

ACL Type Indicates the type of the ID of the access control list.

IPv4 ACL ID Indicates the ID of the IPv4 ACL.

IPv6 ACL ID Indicates the ID of the IPv6 ACL.

IPSec Proposal Name Indicates the name of the security proposal.

IPv6 IKE Peer Name Indicates the name of the IPv6 IKE peer that is referenced by the IPv6 IPSec
Table 2 Related parameters

Parameter Description

policy.

Perfect Forward Indicates the perfect forward secrecy (PFS) value. In the second phase of IPSec
Secrecy
negotiation, PFS enables the BS to use a key that is not derived from the first-
phase key, ensuring that the two keys are independent of each other. According
to PFS, a key protects a unique set of data. The elements used to generate keys
are not reusable. If a key is compromised, other keys are still secure.
If the IPSec policy is used to initiate IPSec negotiation, a PFS exchange is
launched. If the PFS is assigned to the local end, then the PFS exchange is
required when the negotiation is launched at the peer end. The DH group
assigned to the local end and the peer end should be the same. Otherwise, the
negotiation fails. The security level of the 1024-bit Diffie-Hellman group (Dh-
group2) is higher than that of the 768-bit Diffie-Hellman group (Dh-group1).
However, longer processing time is required by the Dh-group2.

IPv6 SA Duration Mode Indicates the configuration mode of the IPv6 IPSec SA life cycle. If this
parameter is set to GLOBAL, the default SA life cycle is used. In this case, LTS
and LTKB are set to the default values 3600 and 69120000, respectively. If this
parameter is set to LOCAL, the SA life cycle is configurable.

Lifetime Based On Time Indicates the life cycle of an IPv6 IPSec SA. When the lifetime reaches a
specified value, the IPv6 IPSec SA becomes invalid. Before the life cycle of an
IPv6 IPSec SA elapses, the IPSec policy is used in an attempt to establish a new
IPv6 IPSec SA through negotiation to ensure secure transmission; before the
negotiation is complete, the original IPv6 IPSec SA is still used. After the
negotiation is complete, the new SA is immediately used. IPv6 IPSec SA
negotiation takes a period. To prevent SA updating from affecting
communication security, a life cycle longer than 900 seconds is recommended.

Lifetime Based On Indicates the effective traffic of the IPv6 IPSec policy. The value 0 indicates that
Traffic
the function, which initiates negotiation for a new IPSec SA based on the traffic
volume, is disabled. But when BS acts as initiator in IKEv1 and this value is set
to 0, if the responder insists or enforces the IPSec SA traffic lifetime to BS, BS
will enable this function to avoid service break down.

Control Mode Indicates whether the object can be modified or deleted by the system. The value
MANUAL_MODE means that only the user can modify or delete the object.
The value AUTO_MODE means that both the system and the user can modify or
delete the object.

Cabinet No. Indicates the cabinet number of the board that adopts the IPv6 IPsec policy.

Subrack No. Indicates the subrack number of the board that adopts the IPv6 IPSec policy.
Table 2 Related parameters

Parameter Description

Slot No. Indicates the slot number of the board that adopts the IPv6 IPSec policy.

Auto Config Flag Indicates whether the object is created by the system. MANUAL_CREATED
means that the object is configured by the user manually. AUTO_CREATED
means that the object is created by the system.

5.7.1.6.1.61 IPSECPROPOSAL
TRANSPORT
+-IPSECPROPOSAL

Description

The IPSECPROPOSAL MO defines the combination of algorithm parameters related to data


encapsulation, encryption, and authentication of IP Security (IPSec). The parameters related to
security of the IPSECPOLICY MO refer to this proposal by name.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the IPSECPOLICY6 MO:


- The IPSECPROPOSAL MO corresponding to an IPSECPOLICY6 MO must have been
configured.
Relation with the IPSECPOLICY MO:
- Before configuring an IPSECPOLICY MO, ensure that the associated IPSECPROPOSAL
MO is configured.
Relation with the IPSECPROPOSAL MO:
- ENCAPMODE in the IPSECPROPOSAL MO used by the IPSECPOLICY MO in an
IPSECDTNL MO must be set to TUNNEL.
Relation with the SECURITYHOST MO:
- In a SECURITYHOST MO, if SEGWCONFIGMODE is set to
SEGW_CONFIG_ON_HOST, IPSECPROPNAME must be the same as PROPNAME in a
configured IPSECPROPOSAL MO.
Relation with the SECURITYPEER MO:
- In a SECURITYPEER MO, if SEGWSWITCH is set to ENABLE, IPSECPROPNAME
must be the same as PROPNAME in a configured IPSECPROPOSAL MO.
Relation with the SECURITYTEMPLATE MO:
- In a SECURITYTEMPLATE MO, if SEGWSWITCH is set to DISABLE,
IPSECPROPNAME must be the same as PROPNAME in a configured IPSECPROPOSAL
MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add an IP Security (IPSec) proposal.


IPSECPROPOSAL

DSP Use this command to query the IPSec proposal configuration that takes effect.
IPSECPROPOSAL

LST IPSECPROPOSAL Use this command to list the configuration of the IPSec proposal.

MOD Use this command to modify an IPSec proposal.


IPSECPROPOSAL

RMV Use this command to remove an IPSec proposal.


IPSECPROPOSAL

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

IPSec Proposal Name Indicates the name of the IPSec proposal.

Encapsulation Mode Indicates the encapsulation mode of an IPSec proposal, which can be set to
TUNNEL or TRANSPORT. In TRANSPORT mode, only data is encrypted. In
Table 2 Related parameters

Parameter Description

TUNNEL mode, the whole IP packet is protected, and a new IP header is added
to the original IP packet. The source IP address and the destination IP address of
the new IP header are the IP addresses of two ends of the security tunnel. Both
the TRANSPORT mode and the TUNNEL mode are used for end-to-end IPSec
protection. The TUNNEL mode, however, is also applied to the protection of a
certain segment.

Transform Indicates the security protocol used in an IPSec proposal. The value AH
indicates the Authentication Header (AH) protocol specified in RFC2402. The
value ESP indicates the Encapsulating Security Payload (ESP) protocol
specified in RFC2406. The value AH_ESP indicates that the ESP protocol is
preferentially used to protect packets, but not the AH protocol.

AH Authentication Indicates the AH authentication algorithm used by an IPSec proposal. IPSec can
Algorithm
use hashed message authentication code (HMAC) or cipher block chaining-
message authentication code (CBC-MAC) for identity authentication and data
integrity check. For details about HMAC, see RFC4306. HMAC currently
supports three hash functions: message digest algorithm 5 (MD5), secure hash
algorithm 1 (SHA1), and secure hash algorithm 256 (SHA256). The three hash
functions verify data by means of integrity protection. Among them, SHA256
provides the highest security level and MD5 provides the lowest security level.
For details about the hash functions, see RFC2409. CBC-MAC currently
supports AES-XCBC-MAC-96, which is an enhancement to CBC-MAC. For
details about AES-XCBC-MAC-96, see RFC3566.

ESP Authentication Indicates the ESP authentication algorithm used by an IPSec proposal. If this
Algorithm
parameter is set to NULL, the following algorithms are not used: MD5, SHA1,
SHA256, and AES-XCBC-MAC-96.

ESP Encryption Indicates the encryption algorithm used in ESP. The Data Encryption Standard
Algorithm
(DES) is an internationally used data encryption algorithm, which uses a 56-bit
key. The 3DES is also an internationally used encryption algorithm, which uses
a 168-bit key. The Advanced Encryption Standard (AES) is an advanced
encryption algorithm, which can use three types of keys of different lengths:
128, 192, and 256 bits. Therefore, different protection levels are available. For
details, see RFC2401.

Cabinet No. Indicates the cabinet number of the board that adopts the IPSec proposal.

Subrack No. Indicates the subrack number of the board that adopts the IPSec proposal.

Slot No. Indicates the slot number of the board that adopts the IPSec proposal.
5.7.1.6.1.62 LLDPGLOBAL
TRANSPORT
+-LLDPGLOBAL

Description

The Link Layer Discovery Protocol (LLDP) (IEEE 802.1ab-2005 and IEEE 802.1ab-2009)
provides a unified platform of topology discovery and interaction system configuration for
networking between different vendors' devices. The LLDP provides a standard link-layer
discovery method. It enables a local device to construct its capabilities, management address,
device ID, and interface ID into a sequence of type-length-value (TLV) structures, encapsulates
the TLV structure sequence in a Link Layer Discovery Protocol Data Unit (LLDPDU), and sends
the LLDPDU to adjacent neighbors,which is then used by the network management system to
query and determine link communication status.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP Use this command to query global LLDP configurations of a board.


LLDPGLOBALINFO

LST Use this command to list global LLDP configurations of a board.


LLDPGLOBALINFO

SET Use this command to set global LLDP parameters.


LLDPGLOBALINFO

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

LLDPDU Tx Interval Indicates the interval at which the local end sends LLDP packets to neighboring
nodes. If the status of the local LLDP does not change, the interface module of
the LLDP port sends LLDP packets to neighboring nodes at a regular interval
specified by this parameter. The network topology discovery frequency can be
adjusted by changing the setting of this parameter.

LLDP Hold Multiplier Indicates a multiple of the time period during which the local LLDP information
is stored in neighboring nodes. The time period (time to live, TTL for short)
during which the local LLDP information is stored in neighboring nodes is
calculated with the following formula:
TTL = Min (65535, (TXINTVAL x HOLDMULTI) + 1)
That is, TTL is the smaller one of 65535 and (TXINTVAL x HOLDMULTI) + 1.
The validity period (TTL) of storing the local LLDP information in neighboring
nodes can be adjusted by changing the value of this parameter. After a
neighboring node receives an LLDP packet, it updates the information aging
time of the transmit end based on this validity period. If the value of TTL is 0,
the receive end needs to remove the LLDP information about the transmit end
immediately.

Reinit Delay Indicates the delay in reinitializing the LLDP state machine when the interface
LLDP module state is changed from RxTx or Tx to Rx or Disabled. Interface
LLDP modules have four states: transmit and receive state (RxTx), transmit state
(Tx), receive state (Rx), and neither transmit nor receive state (Disabled). When
the interface LLDP module state changes, the interface LLDP module state
machine needs to be reinitialized. When the interface LLDP module state
changes from RxTx or Tx to Rx or Disabled, the system needs to wait for a
period specified by this parameter before reinitializing the internal state
machine. By default, the interface LLDP modules of the system are in the RxTx
state and the state cannot be changed.

Transmission Delay Indicates the delay in transmitting LLDP packets. This parameter specifies the
minimum delay for the interface LLDP module to send LLDP packets to a
neighboring node after the LLDP module discovers a new neighboring node.
Under normal conditions, interface LLDP modules periodically send LLDP
packets to neighboring nodes. When discovering a new neighboring node, the
local end enters the fast transmit mode. That is, the system needs to wait for at
least a period specified by this parameter before sending local LLDP
information to neighboring nodes. The state of the local interface LLDP module
becomes normal only after the local interface LLDP module has sent local
LLDP information to neighboring nodes for four consecutive times. If the
system discovers another new neighboring node in a fast transmit mode, LLDP
packets are still sent in the fast transmit mode.

LLDP Notify Switch Indicates whether to report LLDP change events to the network management
Table 2 Related parameters

Parameter Description

system. When this switch is turned on and the network management system has
subscribed to LLDP change events, the system reports LLDP change
information to the network management system if the local or neighboring
LLDP information changes. The purpose is to instruct the network management
system to update network topology information. When the system changes from
the state that the system does not need to report LLDP change events to the
network management system (that is, this switch is turned off or the network
management system has not subscribed to LLDP change events) to the state that
the system needs to report LLDP change events (that is, this switch is turned on
and the network management system has subscribed to LLDP change events),
the system immediately reports all the current local and neighboring LLDP
information to the network management system. The parameters set by running
this command take effect for the whole base station, that is, the parameter
settings control the capabilities of all LLDP ports to send LLDP change events.

Notify Interval Indicates the minimum delay in reporting a neighboring LLDP information
change notification to the network management system by the base station. This
delay takes effect only for such neighboring LLDP information change events as
adding, removing, and aging a neighboring node. If neighboring LLDP
information changes frequently, this parameter can be set to a large value to
reduce the frequency of sending neighboring LLDP information to the network
management system and minimize network topology flapping.

5.7.1.6.1.63 LLDPLOCAL
TRANSPORT
+-LLDPLOCAL

Description

The LLDPLOCAL MO defines an LLDP local entity, including the system information about the
local end and the statistics about the interaction between both ends.

Effective Scenario

Immediately

Relations Between MOs


Possible parents:
TRANSPORT

Relation with the HAGRP MO:


- In one logical protection group, SN in an HAGRP MO must be the same as SN in a
LLDPLOCAL MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD LLDPPORT Use this command to add a Link Layer Discovery Protocol (LLDP) port. When
this command is executed, the system automatically configures local LLDP
information using the default values. For details about the default settings, see
Note of this command.

DSP LLDPNEIGHBOR Use this command to query the configuration of a remote LLDP port.

DSP LLDPPORT Use this command to query the configuration of an LLDP port.

DSP LLDPSTAT Use this command to query statistics on an LLDP port.

LST LLDPPORT Use this command to list the configuration of an LLDP port.

RMV LLDPPORT Use this command to remove the configuration of an LLDP port.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Link Aggregation Indicates whether to enable link aggregation.


Enabled

Aggregation Port ID Indicates the trunk number of the Ethernet trunk link to which an LLDP port has
been added.

Link Aggregation Indicates whether an LLDP port has been added to an Ethernet trunk link.
Table 2 Related parameters

Parameter Description

Supported

Auto-negotiation Indicates whether to enable automatic negotiation.


Enabled

Auto-negotiation Indicates whether to support auto negotiation. In auto negotiation mode, a


Supported
connection can be set up even if different duplex modes or data rates are
configured at both ends.

Cabinet No. Indicates the cabinet number of the board where the LLDPLOCAL is located.

Chassis ID Indicates the chassis ID of a device. The port that receives LLDP information
can use Chassis ID and Port ID to identify a peer device.

Chassis ID Subtype Indicates the subtype of a chassis ID.

Expired Time Indicates the aging time of the information about the neighboring LLDP port.
When the aging time is 0 and the local end does not receive update information
about the neighboring LLDP port, the neighboring LLDP port information will
be aging out.

Management Address Indicates the management address that the network management system uses to
manage and identify a network device.

Management Address Indicates the type of a management address.


Type

MAU Indicates the medium attachment unit (MAU) of an Ethernet port. All MAUs are
named according to IEEE standards. Value AUI indicates the attachment unit
interface. Value Foirl indicates fiber optic inter repeater link. Value 10Broad36
indicates a 10 Mbit/s Ethernet that uses coaxial cables. All other MAUs are
named in the format of "digits+Base+type", where, digits indicate the maximum
transmit rate (for example, 10 indicates the maximum transmit rate of 10
Mbit/s), Base indicates that baseband transmission is used to transmit signals,
and types have the following meanings: T indicates unshielded twisted pair
(UTP) cables, 5 indicates thick coaxial cables, 2 indicates thin coaxial cables, X
indicates the 8B/10B encoding scheme with 8-bit data and 2-bit error correction
data, TX indicates category 5 twisted pair, FD indicates full duplex (for
example, 1000BaseXFD indicates full duplex of 1000BaseX), and HD indicates
half duplex. For details about other types, see RFC3636.

Maximum Frame Size Indicates the maximum frame length. When the value of the Maximum Frame
Size parameter is 0, the base station cannot detect any valid maximum frame
size.

Port Description Indicates the description of an LLDP port.


Table 2 Related parameters

Parameter Description

Port ID Indicates the ID of a port.

Port ID Subtype Indicates the subtype of a port ID.

Port No. Indicates the number of the Ethernet port where the LLDPLOCAL is located.

Port VLAN ID Indicates the ID of the VLAN to which the port of a Layer 2 switch (bridge)
belongs. A port can have at most one port VLAN ID. Value 0 indicates that the
port does not support VLANs or the port is not configured with a VLAN.

Port and Protocol VLAN Indicates whether to enable port and protocol VLAN.
Enabled

Port and Protocol VLAN Indicates the list of port and protocol VLAN ID. The system supports a
ID List
maximum of 16 port and protocol VLAN IDs.

Port and Protocol VLAN Indicates whether to support the port and protocol VLAN, which is an untagged
Supported
VLAN for a port. This untagged VLAN can map packets to packets with
specified VLANs according to specific rules. When a packet enters a port with
an untagged VLAN, the packet is tagged with a specific VLAN. When the
packet leaves the port with an untagged VLAN, the tagged VLAN is removed
from the packet. The port and protocol VLAN can be configured for LLDP
communication or not. However, the port and protocol VLAN helps users grasp
the system configuration.

The Number Of Rx Indicates the total number of discarded LLDP frames.


LLDP Frames
Discarded

The Number Of Rx Indicates the total number of discarded LLDP type-length-values (TLVs).
LLDP TLVs Discarded

The Number Of Rx Indicates the total number of received erroneous LLDP frames.
LLDP Error Frames

The Number Of LLDP Indicates the total number of received LLDP frames.
Frames Received

The Number Of LLDP Indicates the total number of aged LLDP neighbors.
Neighbor Information
Aged Out

The Number Of LLDP Indicates the total number of unrecognizable LLDP type-length-values (TLVs).
TLVs Unrecognized

Slot No. Indicates the slot number of the board where the LLDPLOCAL is located.
Table 2 Related parameters

Parameter Description

Subboard Type Indicates the type of sub-board on the board where the LLDPLOCAL is located.

Subrack No. Indicates the subrack number of the board where the LLDPLOCAL is located.

System Capabilities Indicates the enabled system capabilities.


Enabled

System Capabilities Indicates the capabilities supported by the system. The capabilities reflect the
Supported
main functions of the system. A single system can provide multiple functions,
such as routing, bridge, and relay.

System Description Indicates the system description, such as the vendor, device name, hardware
type, and version information about the software operating system. Such system
data is useful in collecting the network traffic.

System Name Indicates the system name.

The Number Of LLDP Indicates the total number of sent LLDP frames.
Frames Transmitted

VLAN Name List Indicates the list of VLAN names. A VLAN name list consists of three fields:
VLAN ID, bracket, and VLAN name. A VLAN name list supports a maximum
of 32 VLAN names.

Number of VLAN Name Indicates the number of VLAN names recorded in the VLAN name list.

Number of Port and Indicates the number of port and protocol VLAN IDs.
Protocol VLAN ID

Binding VLAN Indicates whether the local LLDP port is associated with the VLAN. If the local
LLDP port is bound to a VLAN, LLDP packets sent by the local end carry the
VLAN ID.

VLAN ID Indicates the VLAN ID of local LLDP port.

VLAN Priority Indicates the VLAN priority of local LLDP port.

5.7.1.6.1.64 LOCALETHPORT
TRANSPORT
+-LOCALETHPORT
Description

This MO is used to set a local maintenance Ethernet port.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP LOCALETHPORT Use this command to query the status of the local maintenance Ethernet port.

LST LOCALETHPORT Use this command to list the configuration of the local maintenance Ethernet
port.

SET LOCALETHPORT Use this command to enable or disable the local maintenance Ethernet port.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Enable Flag Indicates whether to enable the local maintenance Ethernet port. When the
parameter is set to DISABLE, the local maintenance Ethernet port is disabled if
the remote OM channel is working properly, but is enabled if the remote OM
channel is faulty. When the parameter is set to ENABLE, the local maintenance
Ethernet port is permanently enabled.

Actual Effect Status Indicates whether to enable the local maintenance Ethernet port.
Table 2 Related parameters

Parameter Description

Port Status Indicates the status of the local maintenance Ethernet port.If the parameter is
Down,this port cannot be maintained.

Number of RX Indicates the number of discarded packets that are received at the local
Discarded Packets
maintenance Ethernet port.

Number of RX Packets Indicates the number of packets received at the local maintenance Ethernet port.

Number of TX Indicates the number of discarded packets that are transmitted at the local
Discarded Packets
maintenance Ethernet port.

Number of TX Packets Indicates the number of packets transmitted at the local maintenance Ethernet
port.

5.7.1.6.1.65 LOCALIP
TRANSPORT
+-LOCALIP

Description

The LOCALIP MO refers to the IP address of the local maintenance channel. This IP address is
configured at the commissioning Ethernet port to connect the BS through this port for local
maintenance.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the UDPSESSION MO:


- PEERIP in an UDPSESSION MO must be different from IP in a LOCALIP MO with the
same routing domain.
Relation with the MPGRP MO:
- IP in a LOCALIP MO must be different from LOCALIP in an MPGRP MO.
- IP in a LOCALIP MO must be different from PEERIP in an MPGRP MO.
- IP in a LOCALIP MO and LOCALIP in an MPGRP MO must be on different network
segments.
Relation with the PPPLNK MO:
- IP in a LOCALIP MO must be different from LOCALIP in a PPPLNK MO.
- IP in a LOCALIP MO must be different from PEERIP in a PPPLNK MO.
- IP in a LOCALIP MO must be on a different network segment from LOCALIP in a
PPPLNK MO.
Relation with the OMCH MO:
- IP in a LOCALIP MO must be different from IP in an OMCH MO.
- IP in a LOCALIP MO and IP in an OMCH MO must be on different network segments.
- PEERIP in an OMCH MO must be different from IP in a LOCALIP MO.
Relation with the DEVIP MO:
- IP in a LOCALIP MO must be different from IP in a DEVIP MO in the same routing
domain.
- IP in a LOCALIP MO must be on a different network segment from IP in a DEVIP MO in
the same routing domain.
Relation with the BFDSESSION MO:
- If a BFDSESSION MO and a LOCALIP MO are in the same routing domain, DSTIP in the
BFDSESSION MO must be different from IP in the LOCALIP MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP LOCALIP Use this command to query the IP address of the local maintenance channel that
takes effect.

LST LOCALIP Use this command to list the IP address for local maintenance.

SET LOCALIP Use this command to set the IP address of the local maintenance channel. The IP
address of the local maintenance channel refers to the IP address of the local
commissioning Ethernet port on the board.
Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

IP Address Indicates the IP address for local maintenance. The value of this parameter must
meet the following conditions:
(1) It must be a valid IP address of Class A, B, or C, and cannot be set to 0.x.x.x
or 127.x.x.x.
(2) It must be different from the local IP address of any remote maintenance
channel and from any device IP address.
(3) It must be on different network segments from the IP address of any remote
maintenance channel and from any device IP address.
(4) It must be different from any IP address configured on other ports.
(5) It must be on different network segments from the destination IP address of
any IP route.

Mask Indicates the subnet mask for the IP address of a local maintenance channel.
This subnet mask must be a valid mask address and cannot be 0.0.0.0 or
255.255.255.255.

5.7.1.6.1.66 LOCALIP6
TRANSPORT
+-LOCALIP6

Description

The LOCALIP6 MO indicates the IPv6 address of the local maintenance channel. This IP
address is configured at the commissioning Ethernet port and used to connect to the BS through
this port for local maintenance.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the IKEPEER6 MO:


- REMOTEIP in an IKEPEER6 MO must be different from IP6 in a LOCALIP6 MO.
Relation with the DEVIP6 MO:
- IP6 in the LOCALIP6 MO must be different from IPV6 in a DEVIP6 MO.
- IP6 in the LOCALIP6 MO must be on a different network segment from IPV6 in a
DEVIP6 MO.
Relation with the OMCH6 MO:
- IP6 in the LOCALIP6 MO must be different from LOCALIP6 in an OMCH6 MO.
- IP6 in the LOCALIP6 MO must be on a different network segment from LOCALIP6 in an
OMCH6 MO.
- PEERIP6 in an OMCH6 MO must be different from IP6 in a LOCALIP6 MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP LOCALIP6 Use this command to list the IPv6 address of the local maintenance channel that
takes effect.

LST LOCALIP6 Use this command to list the configured IPv6 address of the local maintenance
channel.

SET LOCALIP6 Use this command to set the IPv6 address of a local maintenance channel.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

IPv6 Address Indicates the IPv6 address of the local maintenance channel. This IPv6 address
must be a global unicast address or a link-local address.
Table 2 Related parameters

Parameter Description

Prefix Length Indicates the prefix length of the IPv6 address of a local maintenance channel.

Address Status Indicates the status of the IPv6 address of the local maintenance channel.

Valid Lifetime Indicates the time period during which the IPv6 address of the local maintenance
channel is in valid state.

Preferred Lifetime Indicates the time period during which the IPv6 address of the local maintenance
channel is in preferred state. The valid state is categorized into the preferred
state and the deprecated state. In preferred state, the address can be freely used.
In deprecated state, the connections previously established through this address
are still usable, whereas any connection newly established through this address
is not usable.

5.7.1.6.1.67 LR
TRANSPORT
+-LR

Description

This MO is used to set the rate of uplink and downlink data transmitted over a physical port. By
setting the data rate, the transmission rate and reception rate on an Ethernet port, MLPPP group,
and Ethernet trunk are limited, data is transmitted to the external network at a specified rate, and
the QoS is guaranteed.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the HAGRP MO:


- In one logical protection group, SN in an HAGRP MO must be the same as that in an LR
MO.
Relation with the MPGRP MO:
- If PT in an LR MO is set to MPGRP, the associated MPGRP MO must have been
configured.
- When removing an MPGRP MO, the system automatically removes the LR MO that
depends on the MPGRP MO.
Relation with the ETHTRK MO:
- If PT in an LR MO is set to ETHTRK, the associated ETHTRK MO must have been
configured.
- When removing an ETHTRK MO, the system automatically removes the LR MO that
depends on the ETHTRK MO.
Relation with the ETHTRKLNK MO:
- Before adding an ETHTRKLNK MO, ensure that an LR MO is not enabled for the
associated ETHPORT MO or LRSW in the LR MO is set to DISABLE.
Relation with the TUNNEL MO:
- When removing a TUNNEL MO, the system automatically removes the LR MO that
depends on the TUNNEL MO.
- If PT in an LR MO is set to TUNNEL, the associated TUNNEL MO must have been
configured.
Relation with the RSCGRP MO:
- An RSCGRP MO and an LR MO can be configured on only one TUNNEL MO.
Relation with the LR MO:
- An LR MO can be configured on only one TUNNEL MO.
Relation with the ETHPORT MO:
- When removing an ETHPORT MO, the system automatically removes the LR MO that
depends on the ETHPORT MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST LR Use this command to list the configuration of all the line rates.

SET LR Use this command to set the data rate of a physical port. Rate limitation is
implemented between the data link layer and the physical layer. The length of a
Table 1 Related MML commands

MML Command Function

packets measures only the header of the data link layer, not the header of the
physical layer. If the port type is set to MPGRP, rate limitation is performed only
at the IP layer, but not at the MP header.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the board where the port is located.

Subrack No. Indicates the subrack number of the board where the port is located.

Slot No. Indicates the slot number of the board where the port is located.

Port Type Indicates the port type.

Port No. Indicates the port number.

LR Switch Indicates the switch for limiting the line rate at the port.

UL Committed Indicates the UL committed information rate after rate limitation is configured at
Information Rate
a port. The precision of the UL committed information rate supported by the
UMPTb is 64 Kbit/s, the precision supported by the other board is 32 Kbit/s. If
the configured UL committed information rate is not a multiple of the precision,
the UL committed information rate is rounded up.

Committed Burst Size Indicates the Committed Burst Size (CBS) after rate limitation is configured at a
port.The minimum rate supported by the UMPTb is 64 Kbit/s.

Excess Burst Size Indicates the Excess Burst Size (EBS) after rate limitation is configured at a
port.

Subboard Type Indicates the type of sub-board on the board where a port is located.

DL Committed Indicates the DL committed information rate after rate limitation is configured at
Information Rate
a port.This parameter computes the value of Physical Port Down Link
Admission.The minimum rate supported by the UMPTb is 64 Kbit/s.
5.7.1.6.1.68 MPGRP
TRANSPORT
+-MPGRP

Description

The MPGRP MO is used to bind multiple PPP links together, which are used for transmitting
fragmented packets to the same destination address based on the MLPPP protocol. In this way,
transmission bandwidth is increased.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the HAGRP MO:


- In one logical protection group, SN in an HAGRP MO must be the same as that in an
MPGRP MO.
Relation with the MPGRP MO:
- Each MPGRP MO must have a unique combination of LOCALIP and PEERIP.
- Each MPGRP MO configured on one board must have a unique MPGRPN. That is,
MPGRPN must be unique in the MPGRP MOs with an identical combination of CN, SRN, and
SN.
- Each MPGRP MO must have a unique LOCALIP.
- LOCALIP of two MPGRP MOs must be on different network segments.
Relation with the BFDSESSION MO:
- If a BFDSESSION MO and an MPGRP MO are in the same routing domain, DSTIP in the
BFDSESSION MO must be different from LOCALIP in the MPGRP MO.
Relation with the UDPSESSION MO:
- PEERIP in an UDPSESSION MO must be different from LOCALIP in a MPGRP MO.
Relation with the LOCALIP MO:
- IP in a LOCALIP MO must be different from LOCALIP in an MPGRP MO.
- IP in a LOCALIP MO must be different from PEERIP in an MPGRP MO.
- IP in a LOCALIP MO and LOCALIP in an MPGRP MO must be on different network
segments.
Relation with the PPPLNK MO:
- LOCALIP in a PPPLNK MO must be different from LOCALIP in an MPGRP MO.
- LOCALIP in a PPPLNK MO must be different from PEERIP in an MPGRP MO.
- PEERIP in a PPPLNK MO must be different from LOCALIP in an MPGRP MO.
- LOCALIP in a PPPLNK MO must be on a different network segment from LOCALIP in
an MPGRP MO.
Relation with the IPPMSESSION MO:
- If BINDPATH in an IPPMSESSION MO is set to NO, LOCALIP in the associated
MPGRP MO must be different from PEERIP in the IPPMSESSION MO.
Relation with the OMCH MO:
- IP in an OMCH MO must be different from PEERIP in an MPGRP MO.
- PEERIP in an OMCH MO must be different from LOCALIP in an MPGRP MO.
Relation with the SCTPLNK MO:
- In a routing domain,PEERIP in an MPGRP MO must be different from LOCIP and
SECLOCIP in an SCTPLNK MO.
Relation with the IPPATH MO:
- If PT and JNRSCGRP in an IPPATH MO are set to MPGRP and DISABLE, respectively,
the associated MPGRP MO must have been configured.
- If LOCALIP in an IPPATH MO is set to 0.0.0.0, the IPPATH MO must have been
configured on an MPGRP MO whose LOCALIP is set to 0.0.0.0.
Relation with the LR MO:
- If PT in an LR MO is set to MPGRP, the associated MPGRP MO must have been
configured.
- When removing an MPGRP MO, the system automatically removes the LR MO that
depends on the MPGRP MO.
Relation with the DEVIP MO:
- If PT in a DEVIP MO is set to MPGRP, the associated MPGRP MO must have been
configured.
- If a DEVIP MO and an MPGRP MO are in the same routing domain, IP in the DEVIP MO
must be different from LOCALIP in the MPGRP MO.
- If a DEVIP MO and an MPGRP MO are in the same routing domain, IP in the DEVIP MO
must be different from PEERIP in the MPGRP MO.
- LOCALIP in an MPGRP MO must be on a different network segment from IP in a DEVIP
MO in the same routing domain on another interface.
Relation with the IPRT MO:
- If RTTYPE and IFT are set to IF and MPGRP, respectively in an IPRT MO, IFNO in the
IPRT MO must be the same as MPGRPN in the associated MPGRP MO.
- If RTTYPE and IFT in an IPRT MO are set to IF and TUNNEL, DSTIP in an IPRT MO
must be different from LOCALIP in an MPGRP MO.
Relation with the RSCGRP MO:
- If PT in an RSCGRP MO is set to MPGRP, the associated MPGRP MO must have been
configured.
Relation with the UDPSESSION,DEVIP,PPPLNK MOs:
- UDPSESSION:LOCALIP in an UDPSESSION MO to be added must have been
configured. That is, for the UDPSESSION, DEVIP, PPPLNK, and MPGRP MOs configured
on the same board, LOCALIP in the UDPSESSION MO must be the same as any of the
following : IP in the DEVIP MO with the same routing domain, LOCALIP in the PPPLNK
MO, and LOCALIP in the MPGRP MO.
Relation with the IPPMSESSION,DEVIP,PPPLNK MOs:
- If BINDPATH in an IPPMSESSION MO is set to NO, the IP address corresponding to
LOCALIP in the IPPMSESSION MO must have been configured. That is, for the
IPPMSESSION MO, DEVIP MO in the same routing domain, PPPLNK MO, and MPGRP
MO configured on the same board, LOCALIP in the IPPMSESSION MO must be the same as
any of the following: IP in the DEVIP MO; LOCALIP in the PPPLNK MO; or LOCALIP in
the MPGRP MO.
Relation with the BFDSESSION,DEVIP,PPPLNK MOs:
- SRCIP in a BFDSESSION MO to be added must have been configured. That is, for the
BFDSESSION, DEVIP, PPPLNK, and MPGRP MOs configured on the same board, SRCIP
in the BFDSESSION MO must be the same as any of the following : IP in the DEVIP MO in
the same routing domain, LOCALIP in the PPPLNK MO, and LOCALIP in the MPGRP MO.
Relation with the MPLNK MO:
- Before adding an MPLNK MO, the associated MPGRP MO must have been configured. If
CN, SRN, SN, SBT, and MPGRPN in an MPGRP MO are the same as CN, SRN, SN, SBT,
and MPGRPN in an MPLNK MO, respectively, the two MOs are associated with each other.
- When removing an MPGRP MO, the system automatically removes the MPLNK MO that
depends on the MPGRP MO.
Relation with the SUBIF MO:
- An MPGRP MO and a SUBIF MO cannot both be configured.
Relation with the VRF MO:
- An MPGRP MO and a VRF MO whose VRFIDX is set to 1 to 7 cannot both be configured.
Relation with the SCTPLNK,PPPLNK,DEVIP MOs:
- Before adding an SCTPLNK MO, ensure that the MPGRP or PPPLNK MO that has the
same combination of cabinet number, subrack number, and slot number as the SCTPLNK MO
has been configured. Alternatively, ensure that the DEVIP, MPGRP, or PPPLNK MO that
meets both of the following conditions has been configured: (1) The DEVIP, MPGRP, or
PPPLNK MO is in the same routing domain as the SCTPLNK MO. (2) LOCIP or SECLOCIP
in the SCTPLNK MO is the same as IP in the DEVIP MO, LOCALIP in the MPGRP MO, or
LOCALIP in the PPPLNK MO.
Relation with the SCTPPEER,DEVIP,PPPLNK MOs:
- In a routing domain,SIGIP1V4 in an SCTPPEER MO must be different from
IP,LOCALIP or LOCALIP in a configured DEVIP MO,MPGRP and PPPLNK.
- In a routing domain,SIGIP2V4 in an SCTPPEER MO must be different from
IP,LOCALIP or LOCALIP in a configured DEVIP MO,MPGRP and PPPLNK.
Relation with the USERPLANEHOST,DEVIP,PPPLNK MOs:
- In a routing domain,LOCIPV4 in a USERPLANEHOST MO must be the same as
IP ,LOCALIP or LOCALIP in a configured DEVIP MO ,MPGRP or PPPLNK.
Relation with the USERPLANEPEER,DEVIP,PPPLNK MOs:
- PEERIPV4 in a USERPLANEPEER MO must be different from IP ,LOCALIP or
LOCALIP in a configured DEVIP MO ,MPGRP and PPPLNK.
Relation with the USERPLANEHOST MO:
- In a routing domain, if LOCIPV4 in the USERPLANEHOST MO is referenced by
LOCALIP in the MPGRP MO, the IPSECSWITCH in the USERPLANEHOST MO must
not be set to ENABLE.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD MPGRP Use this command to add a Multi-link PPP (MLPPP) group.

DSP MPGRP Use this command to query the status of an MLPPP group.

LST MPGRP Use this command to list the configuration of the MLPPP group.

MOD MPGRP Use this command to modify the configuration of the MLPPP group.

RMV MPGRP Use this command to remove a specified MLPPP group.


Table 1 Related MML commands

MML Command Function

RST MPGRP Use this command to reset a specified MLPPP group and restart negotiation.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet where the MLPPP group is located.

Subrack No. Indicates the number of the subrack where the MLPPP group is located.

Slot No. Indicates the number of the slot where the MLPPP group is located.

Group No. Indicates the number of the MLPPP group.

Multi-Class PPP Indicates whether an MLPPP group supports the multi-class feature.
If this parameter is set to ENABLE, the MLPPP group supports the Class of
Service (CoS) feature and four or eight service types of different priorities.

Authentication Type Indicates the authentication type of the MLPPP group.

User Name Indicates the authentication user name of an MLPPP group.

Password Indicates the authentication password.

Local IP Indicates the local IP address. If this parameter is set to 0.0.0.0, this IP address
needs to be negotiated. If this parameter is not set to 0.0.0.0, it must be set to a
valid IP address of class A, B, or C but must not be the reserved address 0.x.x.x
or 127.x.x.x.

Mask Indicates the subnet mask of the local IP address. If this parameter is set to
0.0.0.0, it needs to be negotiated.

Peer IP Indicates the peer IP address. When the BS is connected to a peer equipment, the
peer IP address can be either user-specified or set to 0.0.0.0. If this parameter is
set to 0.0.0.0, this IP address is obtained by means of negotiation.

MP/MC Header Option Indicates the MP/MC head option of the MLPPP.
Table 2 Related parameters

Parameter Description

PPPMUX Indicates whether to enable PPP multi-frame multiplexing.

MLPPP Fragment Size Indicates the fragment size of an MLPPP group.

PPP Mux Subframe Indicates the maximum length of the PPP MUX subframe.
Max Length

PPP Muxframe Max Indicates the maximum length of the PPP MUX frame.
Length

PPPMUX Combine Indicates the timeout duration of a PPP MUX combination. If the PPP MUX
Timeout
combination takes longer time than this parameter value, an alarm related to the
PPP MUX combination timeout is reported.

MCPPP Class Indicates the number of classes of service.

IP Header Compression Indicates whether to enable IP header compression.

MLPPP Packets Indicates the threshold above which the MLPPP packet loss alarm is generated.
Discard Alarm Appear
Threshold

MLPPP Packets Indicates the threshold below which the MLPPP packet loss alarm is cleared.
Discard Alarm
Disappear Threshold

IPHC SubOption Indicates whether to enable IPHC suboption negotiation.

MLPPP Group Status Indicates the status of an MLPPP group.

IPCP Status Indicates the status of the IPCP protocol.

PPPMUX Status Indicates the status of the PPP MUX.

Local IP Negotiation Indicates the negotiation result of the local IP address.


Result

Local IP Mask Indicates the negotiation result of the local IP mask.


Negotiation Result

Peer IP Negotiation Indicates the negotiation result of the peer IP address.


Result

Multi-Class PPP Indicates the negotiation result of the multi-class PPP.


Negotiation Result

Maximum Receive Unit Indicates the negotiation result of the maximum RX unit.
Negotiation Result
Table 2 Related parameters

Parameter Description

PPPMUX Negotiation Indicates the negotiation result of the PPP MUX.


Result

ACFC Negotiation Indicates the negotiation result of the address field and control field.
Result

PFC Negotiation Result Indicates the negotiation result of the protocol field compression.

IPHC Negotiation Indicates the negotiation result of the IPHC.


Result

Number of RX Packets Indicates the number of packets received.

Number of TX Packets Indicates the number of packets sent.

RX Flow Indicates the RX traffic.

TX Flow Indicates the TX traffic.

Number of IPs Indicates the number of IP addresses of an MLPPP group.

IP Address List Indicates the list of IP addresses of an MLPPP group.

Subboard Type Indicates the type of sub-board on the board where an MLPPP group is
established.

Number of RX Bytes Indicates the number of bytes received.

Number of RX Drop Indicates the number of discarded packets received.


Packets

Number of TX Bytes Indicates the number of bytes transmitted.

Number of TX Drop Indicates the number of discarded packets transmitted.


Packets

5.7.1.6.1.69 MPLNK
TRANSPORT
+-MPLNK

Description
The MPLNK MO consists of the parameters related to an PPP link in an MLPPP group. This MO
is used to set the parameters of an MLPPP link.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the MPLNK MO:


- Each MPLNK MO configured in the same slot must have a unique MLPPP link number.
That is, PPPLNKN must be unique in the MPLNK MOs with an identical combination of CN,
SRN, and SN.
- The E1/T1 timeslots used by any two MPLNK MOs must not have an intersection.
- E1T1SN in the cross-board MPLNK MOs under the same MPGRP MO must be the same.
Relation with the PPPLNK MO:
- On a board, PPPLNKN in a PPPLNK MO must be different from PPPLNKN in an
MPLNK MO.
- The E1/T1 timeslots occupied by an PPPLNK MO and those occupied by an MPLNK MO
must not have an intersection.
Relation with the PORTSECURITY MO:
- The E1T1 MO that is associated with an MPLNK MO must meet either of the following
conditions: (1) No PORTSECURITY MO is associated with the E1T1 MO; (2) A
PORTSECURITY MO is associated with the E1T1 MO, but SWITCH in the
PORTSECURITY MO is set to ENABLE.
Relation with the MPGRP MO:
- Before adding an MPLNK MO, the associated MPGRP MO must have been configured. If
CN, SRN, SN, SBT, and MPGRPN in an MPGRP MO are the same as CN, SRN, SN, SBT,
and MPGRPN in an MPLNK MO, respectively, the two MOs are associated with each other.
- When removing an MPGRP MO, the system automatically removes the MPLNK MO that
depends on the MPGRP MO.
Relation with the E1T1 MO:
- If SBT in an MPLNK MO is set to BACK_BOARD, the associated E1T1 MO must have
been configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD MPLNK Use this command to add an MLPPP link to an MLPPP group.

DSP MPLNK Use this command to query the status of one or all MLPPP links on a board.

LST MPLNK Use this command to list the configurations of the MLPPP links in an MLPPP
group.

RMV MPLNK Use this command to remove an MLPPP link from an MLPPP group.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet where the MLPPP link is located.

Subrack No. Indicates the number of the subrack where the MLPPP link is located.

Slot No. Indicates the number of the slot where the MLPPP link is located.

Link No. Indicates the number of the MLPPP link.

MLPPP Group No. Indicates the number of the MLPPP group.

E1/T1 Subrack No. Indicates the number of the subrack housing the board where the E1/T1 port
carrying the MLPPP link is located.

E1/T1 Slot No. Indicates the number of slot holding the board where the E1/T1 port carrying the
MLPPP link is located.

E1/T1 Port No. Indicates the number of the E1/T1 port carrying the MLPPP link.

Timeslot No. Indicates the number of the E1/T1 slot carrying the MLPPP link.

Maximum Receive Unit Indicates the Maximum Receive Unit (MRU). The received packet whose length
is greater than this parameter value is discarded.

Protocol Field Indicates whether to enable protocol field compression.


Table 2 Related parameters

Parameter Description

Compression

Address and Control Indicates whether to enable the compression of the address field and control
Field Compression
field.

Negotiation Time Indicates the timeout duration of the MLPPP link negotiation.

Subboard Type Indicates the type of sub-board where an MLPPP link is established.

MLPPP Group Indicates the type of sub-board where an MLPPP group is established.
Subboard Type

MLPPP Link Status Indicates the status of the MLPPP link.

LCP Status Indicates the status of the Link Control Protocol (LCP) protocol.

Maximum Receive Unit Indicates the negotiation result of the maximum RX unit.
Negotiation Result

PFC Negotiation Result Indicates the negotiation result of the protocol field compression.

ACFC Negotiation Indicates the negotiation result of the Address-And-Control-Field-Compression


Result
(ACFC).

E1/T1 Subboard Type Indicates the type of sub-board on the board where the E1/T1 port carrying the
MLPPP link is located.

Number of RX Packets Indicates the number of packets received.

Number of RX Bytes Indicates the number of bytes received.

Number of RX Drop Indicates the number of discarded packets received.


Packets

Number of TX Packets Indicates the number of packets transmitted.

Number of TX Bytes Indicates the number of bytes transmitted.

Number of TX Drop Indicates the number of discarded packets transmitted.


Packets

5.7.1.6.1.70 OMCH
TRANSPORT
+-OMCH

Description

An OMCH MO consists of the parameters related to a remote maintenance channel through


which the M2000 manages and maintains the BS. The OMCH MO has one active channel and
one standby channel. If the active channel is interrupted, the BS switches services to the other
channel according to instructions from the M2000.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the MPGRP MO:


- IP in an OMCH MO must be different from PEERIP in an MPGRP MO.
- PEERIP in an OMCH MO must be different from LOCALIP in an MPGRP MO.
Relation with the PPPLNK MO:
- IP in an OMCH MO must be different from PEERIP in a PPPLNK MO.
- PEERIP in an OMCH MO must be different from LOCALIP in a PPPLNK MO.
Relation with the IPRT MO:
- If an IPRT MO and an OMCH MO are in the same routing domain, NEXTHOP in the
IPRT MO must be different from IP in the OMCH MO.
- If BRT in an OMCH MO is set to YES, before configuring the RTIDX in this OMCH MO,
ensure that the IPRT MO with the same routing domain for the OMCH MO have been
configured. That is, in the same routing domain, the IPRT MOs whose RTIDX is the same as
RTIDX in the OMCH MO must have been configured.
- If BINDSECONDARYRT in an OMCH MO is set to YES, before configuring the
SECONDARYRTIDX in this OMCH MO, ensure that the IPRTwith the same routing domain
for the OMCH MO have been configured. That is, in the same routing domain, the IPRT MOs
whose RTIDX is the same as SECONDARYRTIDX in the OMCH MO must have been
configured.
- If BEAR is set to IPv4 and BRT is set to YES in an OMCH MO, in the same routing
domain, the IPRT MOs whose RTIDX is the same as RTIDX in the OMCH MO must have
been configured. If the RTTYPE is set to IF, the IFT must not be set to IPOA.
- If BEAR is set to IPv4 and BINDSECONDARYRT is set to YES in an OMCH MO, in the
same routing domain, the IPRT MOs whose RTIDX is the same as SECONDARYRTIDX in
the OMCH MO must have been configured. If the RTTYPE is set to IF, the IFT must not be set
to IPOA.
- If RTTYPE and IFT in an IPRT MO are set to IF and TUNNEL, DSTIP in an IPRT MO
must be different from IP in an OMCH MO.
Relation with the BFDSESSION MO:
- If a BFDSESSION MO and an OMCH MO are in the same routing domain, DSTIP in the
BFDSESSION MO must be different from IP in the OMCH MO.
Relation with the IPPATHRT MO:
- In a routing domain,IP in an OMCH MO must be different from NEXTHOPIP in an
IPPATHRT MO.
Relation with the LOCALIP MO:
- IP in a LOCALIP MO must be different from IP in an OMCH MO.
- IP in a LOCALIP MO and IP in an OMCH MO must be on different network segments.
- PEERIP in an OMCH MO must be different from IP in a LOCALIP MO.
Relation with the OMCH MO:
- Each OMCH MO must have a unique IP.
- IP in any two OMCH MOs must be on different network segments.
- PEERIP and IP in an OMCH MO must be different from PEERIP and IP in another
OMCH MO, respectively.
- If BRT in an OMCH MO is set to YES, the RTIDX in this OMCH MO must be different
from RTIDX in any other OMCH MOs whose BRT is set to YES.
- If BINDSECONDARYRT in an OMCH MO is set to YES, the SECONDARYRTIDX in
this OMCH MO must be different from SECONDARYRTIDX in any other OMCH MOs
whose BINDSECONDARYRT is set to YES.
- If BRT in an OMCH MO is set to YES, the RTIDX in this OMCH MO must be different
from SECONDARYRTIDX in OMCH MOs whose BINDSECONDARYRT is set to YES.
- If CHECKTYPE in an OMCH MO is set to UDPSESSION, the UDPSN in this OMCH
MO must be different from UDPSN in any other OMCH MOs whose :CHECKTYPE is set to
UDPSESSION.
- If BINDSECONDARYRT in an OMCH MO is set to YES, the SECONDARYRTIDX in
this OMCH MO must be different from RTIDX in any other OMCH MOs whose BRT is set to
YES.
- On a BS, the sum of OMCH6 and OMCH MOs must be smaller than or equal to 2.
Relation with the DEVIP MO:
- PEERIP in an OMCH MO must be different from IP in a DEVIP MO in the same routing
domain.
Relation with the SCTPLNK MO:
- PEERIP in an OMCH MO must be different from LOCIP and SECLOCIP in an
SCTPLNK MO in the same routing domain.
Relation with the UDPSESSION MO:
- If CHECKTYPE in an OMCH MO is set to UDPSESSION, before configuring the
UDPSN in this OMCH MO, ensure that the UDPSESSION for the OMCH MO have been
configured. That is, the UDPSESSION MOs whose UDPSN is the same as UDPSN in the
OMCH MO must have been configured.
- PEERIP in an UDPSESSION MO must be different from IP in an OMCH MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD OMCH Use this command to add a remote maintenance channel.

DSP DHCPRSLT Use this command to query the automatically obtained parameters after
automatic establishment of the remote maintenance channel.

DSP OMCH Use this command to query the status of a remote maintenance channel.

LST OMCH Use this command to list the configuration of both remote maintenance
channels.

MOD OMCH Use this command to modify the configuration of a remote maintenance
channel.

RMV OMCH Use this command to remove a remote maintenance channel.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Standby Status Indicates the master/slave flag of the remote maintenance channel.

Local IP Indicates the local IP address of a remote maintenance channel.


Table 2 Related parameters

Parameter Description

Local Mask Indicates the local subnet mask of a remote maintenance channel.

Peer IP Indicates the peer IP address of the remote maintenance channel, that is, the IP
address of the M2000.

Peer Mask Indicates the subnet mask of the peer IP address for the remote maintenance
channel.

Bearer Type Indicates the bearer type of a remote maintenance channel.

Binding Route Indicates whether a route is bound to the remote maintenance channel. If the
peer IP of the remote maintenance channel and device IP addresses are not in the
same network segment and the network segment of the device IP address cannot
cover that of the peer IP address, run the ADD IPRT command to add a route to
the remote maintenance channel.
If this parameter is set to YES, a route is bound to the remote maintenance
channel, and the route takes effect only when the remote maintenance takes
effect. If this parameter is set to NO, no route is bound to the remote
maintenance channel, and a remote maintenance channel switchover does not
trigger a route status switchover.

OM Channel Status Indicates the status of a remote maintenance channel.

Used State Indicates whether the remote maintenance channel is being used.

Route Index Indicates the index of the active route bound to the remote maintenance channel.

Binding Secondary Indicates whether a standby route needs to be bound to the remote maintenance
Route
channel. If the remote HA system is applied to the M2000 and no destination IP
address network segment for the route covers the M2000 destination IP address
network segment, run the ADD IPRT command to add a route to the M2000.
If this parameter is set to YES, a standby route is bound to the remote
maintenance channel, and the route takes effect only when the remote
maintenance takes effect. If this parameter is set to NO, no standby route is
bound to the remote maintenance channel, and a remote maintenance channel
switchover does not trigger a route status switchover.

Secondary Route Index Indicates the index of the standby route bound to the remote maintenance
channel.

Check Type Indicates the type of detection mechanism bound to the remote maintenance
channel. If this parameter is set to NONE, no detection mechanism is bound to
the remote maintenance channel and an active/standby remote maintenance
Table 2 Related parameters

Parameter Description

channel switchover is triggered by switchover message sent by the M2000. If


this parameter is set to UDPSESSION, the UDP ping detection is bound to the
remote maintenance channel and an active/standby remote maintenance channel
switchover depends on the UDP session detection,only GSM currently supports
this function.

UDP Session ID Indicates the session number of the UDP ping detection bound to the remote
maintenance channel.

5.7.1.6.1.71 OMCH6
TRANSPORT
+-OMCH6

Description

The OMCH6 MO consists of the parameters related to the remote maintenance IPv6 channel
between the BS and EMS. Users can perform management and maintenance of the BS remotely
through this channel.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the IKEPEER6 MO:


- REMOTEIP in an IKEPEER6 MO must be different from LOCALIP6 in an OMCH6
MO.
Relation with the OMCH6 MO:
- A maximum of one OMCH6 MO can be configured on a BS.
- On a BS, the sum of OMCH6 and OMCH MOs must be smaller than or equal to 2.
Relation with the DEVIP6 MO:
- LOCALIP6 in the OMCH6 MO must be different from IPV6 in a DEVIP6 MO.
- LOCALIP6 in the OMCH6 MO must be on a different network segment from IPV6 in a
DEVIP6 MO.
- PEERIP6 in an OMCH6 MO must be different from IPV6 in a DEVIP6 MO.
Relation with the LOCALIP6 MO:
- IP6 in the LOCALIP6 MO must be different from LOCALIP6 in an OMCH6 MO.
- IP6 in the LOCALIP6 MO must be on a different network segment from LOCALIP6 in an
OMCH6 MO.
- PEERIP6 in an OMCH6 MO must be different from IP6 in a LOCALIP6 MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD OMCH6 Use this command to add an IPv6 remote maintenance channel.

DSP OMCH6 Use this command to list the status of the IPv6 remote maintenance channel.

LST OMCH6 Use this command to list the configuration of the IPv6 remote maintenance
channels.

MOD OMCH6 Use this command to modify an IPv6 remote maintenance channel.

RMV OMCH6 Use this command to remove an IPv6 remote maintenance channel.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local IPv6 Address Indicates the local IPv6 address of a remote maintenance channel. This address
must be a global unicast address.

Peer IPv6 Address Indicates the peer IPv6 address of a remote maintenance channel. This address
Table 2 Related parameters

Parameter Description

must be a global unicast address.

OM Channel Status Indicates the status of an IPv6 remote maintenance channel.

5.7.1.6.1.72 PACKETFILTER
TRANSPORT
+-PACKETFILTER

Description

The PACKETFILTER MO indicates the filtering of IP packets. The system first obtains the
header information about the packets received or transmitted by NEs, compares the information
with the preset ACL rules, and then forwards or discards the packets according to the comparison
results. The header information involves the numbers of protocols carried at the IP layer, source
address and destination address of the packet, and source port and destination port of the packet.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the HAGRP MO:


- In one logical protection group, SN in an HAGRP MO must be the same as that in a
PACKETFILTER MO.
Relation with the ETHTRK MO:
- If PT in a PACKETFILTER MO is set to ETHTRK, ensure that the associated ETHTRK
MO has been configured.
Relation with the ETHTRKLNK MO:
- If PT in a PACKETFILTER MO is set to ETH, and the ETHPORT MO is added to an
ETHTRK MO, the PACKETFILTER MO cannot be added.
Relation with the PACKETFILTER MO:
- The ACL MO corresponding to ACLID in a PACKETFILTER MO must have been
configured.
- If PT in a PACKETFILTER MO is set to SUBIF, the corresponding SUBIF MO must use
the same VRF instance as the ACL MO corresponding to ACLID.
Relation with the ACLRULE MO:
- If FM in a PACKETFILTER MO is set to ADV_ACL or ADV_AND_L2, at least one
ACLRULE MO which is created manually is included in the ACL MO specified by ACLID.
- If FM in a PACKETFILTER MO is set to L2_ACL or ADV_AND_L2, at least one
ACLRULE MO is included in the ACL MO specified by ACLID2.
Relation with the PORTSECURITY MO:
- The ETHPORT MO that is associated with a PACKETFILTER MO must meet either of
the following conditions: (1) No PORTSECURITY MO is associated with the ETHPORT MO;
(2) A PORTSECURITY MO is associated with the ETHPORT MO, but SWITCH in the
PORTSECURITY MO is set to ENABLE.
Relation with the TUNNEL MO:
- If PT in a PACKETFILTER MO is set to TUNNEL, the TUNNEL MO corresponding to
PN in the PACKETFILTER MO must have been configured.
Relation with the MO:
- Only one PACKETFILTER MO with PT set to TUNNEL can be configured.
- Only one PACKETFILTER MO with PT set to TUNNEL can be configured.
Relation with the SUBIF MO:
- If PT in a PACKETFILTER MO is set to SUBIF, the corresponding SUBIF MO must have
been configured.
Relation with the ACL MO:
- If PT in a PACKETFILTER MO is set to ETH, ETHTRK, or TUNNEL, the ACL MO
corresponding to ACLID must use the default VRF instance.
Relation with the EPGROUP MO:
- If PACKETFILTERSWITCH in an EPGROUP MO is set to ENABLE, a
PACKETFILTER MO whose FM is not set to L2_ACL must have been configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD PACKETFILTER Use this command to add a packet filter. A packet filter binds an ACL to a
physical port so that IP packets that are received on the physical port can be
filtered by the ACL.

DSP PACKETFILTER Use this command to query the statistics of the packets that are matched with the
ACL rules after the packet filter is bound to the Ethernet port.

LST PACKETFILTER Use this command to list the configuration of all packet filters.

RMV PACKETFILTER Use this command to remove a PACKETFILTER MO.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the board where the packet filtering is used.

Subrack No. Indicates the subrack number of the board where the packet filtering is used.

Slot No. Indicates the slot number of the board where the packet filtering is used.

Port Type Indicates the port type. The NodeB currently does not support SUBIF.

Port No. Indicates the port number.

Advanced ACL ID Indicates the ID of an advanced ACL. The value of this parameter ranges from
3000 to 3999.

Match Behavior Indicates whether to permit or reject access of the data that does not match the
ACL rule. If this parameter is set to PERMIT, data that does not match the ACL
rule is allowed to pass. If this parameter is set to DENY, data that does not
match the ACL rule is discarded.

Subboard Type Indicates the type of sub-board on the board where packet filter is enabled.

Number of TX Packets Indicates the number of transmitted packets. This parameter is reserved for
further extension.
Table 2 Related parameters

Parameter Description

Number of RX Packets Indicates the number of received packets.

Number of TX Permit Indicates the number of permitted packets on the TX channel. This parameter is
Packets
reserved for further extension.

Number of RX Permit Indicates the number of permitted packets on the RX channel.


Packets

Number of TX Deny Indicates the number of rejected packets on the TX channel. This parameter is
Packets
reserved for further extension.

Number of RX Deny Indicates the number of rejected packets on the RX channel.


Packets

Bytes of TX Packets Indicates the number of bytes contained in transmitted packets. This parameter
is reserved for further extension.

Bytes of RX Packets Indicates the number of bytes contained in received packets.

Bytes of TX Permit Indicates the number of bytes contained in permitted packets on the TX channel.
Packets
This parameter is reserved for further extension.

Bytes of RX Permit Indicates the number of bytes contained in permitted packets on the RX channel.
Packets

Bytes of TX Deny Indicates the number of bytes contained in rejected packets on the TX channel.
Packets
This parameter is reserved for further extension.

Bytes of RX Deny Indicates the number of bytes contained in rejected packets on the RX channel.
Packets

Bytes of RX Packets Indicates the number of bytes contained in the packets that do not match the
Matched Default
Behavior ACL rules for packet filtering. If MB is set to PERMIT, this parameter measures
the number of bytes contained in the accessed packets. If MB is set to DENY,
this parameter measures the number of bytes contained in the discarded packets.
This parameter is valid only when CATALOG is set to PORT.

Number of RX Packets Indicates the number of the packets that do not match the ACL rules for packet
Matched Default
Behavior filtering. If MB is set to PERMIT, this parameter measures the number of
accessed packets. If MB is set to DENY, this parameter measures the number of
discarded packets. This parameter is valid only when CATALOG is set to PORT.

Layer 2 ACL ID Indicates the ID of an ACL at layer 2. The value of this parameter ranges from
4000 to 4999. The BS filters packets based on only VLAN IDs.

Filter Mode Indicates the packet filtering mode. The BS can filter packets based on the
Table 2 Related parameters

Parameter Description

advanced ACL, layer-2 ACL, or both at the same time.

5.7.1.6.1.73 PINGFILTER
TRANSPORT
+-PINGFILTER

Description

This MO is used to configure ping filter entries in whitelist mode (you can ping the IP addresses
included in the network segment of the BS or the Host IDs) or in blacklist mode (you cannot
ping the IP addresses in the network segment of the BS or Host IDs). By setting the ping filtering
mode, you can modify the whitelist or blacklist mode.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the PINGFILTER MO:


- If two PINGFILTER MOs are in the same routing domain and have the same MASK value,
IP in the two MOs must be on different network segments.
Relation with the VRF MO:
- The VRF instance used by a PINGFILTER MO must have been configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD PINGFILTER Use this command to add a ping filter. After a ping filter is added, operators can
ping only the host IP address or IP addresses of network segments that meet the
ping filtering conditions on the BS if the ping filtering mode is set to whitelist. If
the ping filtering mode is set to blacklist, operators cannot ping the host IP
address or IP addresses of network segments that meet the ping filtering
conditions on the BS.

LST PINGFILTER Use this command to list configurations of the ping filter on a BS.

RMV PINGFILTER Use this command to remove a ping filter entry.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

IP Address Indicates the IP address in a ping filter entry. This address must be a valid IP
address of class A, B, or C. It can also be a network segment address.

Mask Indicates the subnet mask corresponding to the IP address in a ping filter entry.
The subnet mask cannot be 0.0.0.0.

VRF Index Indicates the index of a VRF instance.

5.7.1.6.1.74 PLRTHRESHOLD
TRANSPORT
+-PLRTHRESHOLD

Description

This MO indicates the packet loss threshold for an IP path.

Effective Scenario
Not involved

Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST PLRTHRESHOLD Use this command to list the settings of the thresholds for generating and
clearing IP path packet loss alarms of the BS.

SET PLRTHRESHOLD Use this command to set the thresholds for generating and clearing IP path
packet loss alarms of the BS.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

PLR Appear Threshold Indicates the threshold above which the packet loss alarm is generated on an IP
path. When the packet loss rate of an IP path exceeds the threshold, the packet
loss alarm is generated on the IP path.

PLR Disappear Indicates the threshold below which the packet loss alarm is cleared on an IP
Threshold
path. When the packet loss rate of an IP path does not exceed the threshold, the
packet loss alarm is cleared on the IP path.

5.7.1.6.1.75 PMTUCFG
TRANSPORT
+-PMTUCFG
Description

The PMTUCFG MO is used to set the global parameters related to IPv6 basic path MTU
(PMTU) detection configurations, including the detection mode, UDP port number, detection
period, PTMU aging period, and DSCP.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP PMTU Use this command to query the status of IPv6 PMTU single-link detection.

LST PMTUCFG Use this command to list basic IPv6 PMTU detection configurations, such as
detection mode, UDP port number, detection period, and PTMU aging period.

SET PMTUCFG Use this command to set the global parameters related to basic IPv6 PMTU
detection configurations.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Detection Mode Indicates the PMTU detection mode: active or passive. When this parameter is
set to ACTIVE, PMTU detection is periodically performed. When this parameter
is set to PASSIVE, the PMTU is adjusted according to the ultra-large Internet
Control Message Protocol (ICMP) messages received.
Table 2 Related parameters

Parameter Description

UDP Port No. Indicates the destination port number of the UDP packets for PMTU detection.
Ports 65020, 65010, 65099, and 65100 are used for IP PM, FPMUX, and AACP,
and therefore these ports should not be used for PMTU detection.

Detection Period Indicates the timeout duration of a single PMTU detection.

Aging Period Indicates the aging period of the PMTU table.

DSCP Indicates the default DSCP. If no DSCP is specified for a link, the default DSCP
is used when a PMTU detection is performed on the link.

5.7.1.6.1.76 PORTSECURITY
TRANSPORT
+-PORTSECURITY

Description

The PORTSECURITY MO is used to prevent services from being performed on the disabled
service ports, thus ensuring security of service ports.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the HAGRP MO:


- In one logical protection group, SN in an HAGRP MO must be the same as that in a
PORTSECURITY MO.
Relation with the IPSECBIND6 MO:
- Before adding an IPSECBIND6 MO, ensure that SWITCH in the PORTSECURITY MO
on the bound Ethernet port has been set to ENABLE.
Relation with the ETHTRKLNK MO:
- An ETHPORT MO on which an ETHTRKLNK MO depends must meet either of the
following conditions: (1) The corresponding PORTSECURITY MO is not configured. (2) If the
corresponding PORTSECURITY MO has been configured, SWITCH in the
PORTSECURITY MO is set to ENABLE.
Relation with the PORTSECURITY MO:
- If the TYPE in the SYNCETH is set to IN, the PORTSECURITY MO corresponding to
CN, SRN, SN and PN in the SYNCETH MO has been configured and SWITCH in this
PORTSECURITY MO must be set to ENABLE.
- If the PORTSECURITY MO corresponding to CN, SRN, SN, and PN in the LINECLK
MO has been configured, SWITCH in this PORTSECURITY MO must be set to ENABLE.
Relation with the CFMMEP MO:
- The ETHPORT MO that is associated with a CFMMEP MO must meet either of the
following conditions: (1) No PORTSECURITY MO is associated with the ETHPORT MO; (2)
A PORTSECURITY MO is associated with the ETHPORT MO, but SWITCH in the
PORTSECURITY MO is set to ENABLE.
Relation with the DEVIP MO:
- If CN, SRN, SN, SBT, PT, and PN in a DEVIP MO are the same as CN, SRN, SN, SBT,
PT, and PN in a PORTSECURITY MO, respectively, and SWITCH in the PORTSECURITY
MO is set to DISABLE, the DEVIP MO cannot be configured.
Relation with the ETHOAM3AH MO:
- An ETHPORT MO on which an ETHOAM3AH MO depends must meet either of the
following conditions: (1) The corresponding PORTSECURITY MO is not configured. (2) If the
corresponding PORTSECURITY MO has been configured, SWITCH in the
PORTSECURITY MO is set to ENABLE.
Relation with the IPPATH MO:
- The ETHPORT MO that is associated with an IPPATH MO must meet either of the
following conditions: (1) No PORTSECURITY MO is associated with the ETHPORT MO; (2)
A PORTSECURITY MO is associated with the ETHPORT MO, but SWITCH in the
PORTSECURITY MO is set to ENABLE.
Relation with the IPSECBIND MO:
- Before adding an IPSECBIND MO, ensure that SWITCH in the PORTSECURITY MO
on the bound Ethernet port is set to ENABLE.
Relation with the MPLNK MO:
- The E1T1 MO that is associated with an MPLNK MO must meet either of the following
conditions: (1) No PORTSECURITY MO is associated with the E1T1 MO; (2) A
PORTSECURITY MO is associated with the E1T1 MO, but SWITCH in the
PORTSECURITY MO is set to ENABLE.
Relation with the PACKETFILTER MO:
- The ETHPORT MO that is associated with a PACKETFILTER MO must meet either of
the following conditions: (1) No PORTSECURITY MO is associated with the ETHPORT MO;
(2) A PORTSECURITY MO is associated with the ETHPORT MO, but SWITCH in the
PORTSECURITY MO is set to ENABLE.
Relation with the PPPLNK MO:
- The E1T1 MO that is associated with a PPPLNK MO must meet either of the following
conditions: (1) No PORTSECURITY MO is associated with the E1T1 MO; (2) A
PORTSECURITY MO is associated with the E1T1 MO, but SWITCH in the
PORTSECURITY MO is set to ENABLE.
Relation with the RSCGRP MO:
- The ETHPORT MO that is associated with an RSCGRP MO must meet either of the
following conditions: (1) No PORTSECURITY MO is associated with the ETHPORT MO; (2)
A PORTSECURITY MO is associated with the ETHPORT MO, but SWITCH in the
PORTSECURITY MO is set to ENABLE.
Relation with the SUBIF MO:
- An ETHPORT MO on which a SUBIF MO depends must meet either of the following
conditions: (1) The corresponding PORTSECURITY MO is not configured. (2) The
corresponding PORTSECURITY MO has been configured, and its SWITCH is set to
ENABLE.
Relation with the E1T1 MO:
- When removing an E1T1 MO whose SBT is set to BASE_BOARD or E1_COVERBOARD,
the system automatically removes the PORTSECURITY that depends on the E1T1 MO.
Relation with the ETHPORT MO:
- When removing an ETHPORT MO, the system automatically removes the
PORTSECURITY MO that depends on the ETHPORT MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP PORTSECURITY Use this command to query the status of a port security switch.

LST PORTSECURITY Use this command to list a port security configuration.

SET PORTSECURITY Use this command to set the port security switch of a port.
Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet that houses the board where port security is
enabled.

Subrack No. Indicates the number of the subrack that houses the board where port security is
enabled.

Slot No. Indicates the number of the slot corresponding to the board where port security
is enabled.

Subboard Type Indicates the type of sub-board on the board where port security is enabled.

Port Type Indicates the type of port on which port security is enabled.

Port No. Indicates the number of the port on which port security is configured.

Enable Flag Indicates whether to disable services on a specified port to implement port
security. If this parameter is set to DISABLE, running services on the port is
prohibited, thereby guaranteeing the security of the port.

5.7.1.6.1.77 PPPLNK
TRANSPORT
+-PPPLNK

Description

This MO is used to set the parameters of a PPP link.


The Point-to-Point Protocol (PPP) is a protocol at the data link layer that is used to carry network
layer packets on a PPP link. The PPP supports both synchronous communication and
asynchronous communication.

Effective Scenario

Immediately
Relations Between MOs

Possible parents:
TRANSPORT

Relation with the HAGRP MO:


- In one logical protection group, SN in an HAGRP MO must be the same as that in a
PPPLNK MO.
Relation with other PPPLNK Mos:
- Each PPPLNK MO configured on the same board has a unique PPP link number. That is,
PPPLNKN must be unique in the PPPLNK MOs with an identical combination of CN, SRN,
and SN.
Relation with the PPPLNK MO:
- Each PPPLNK MO must have a unique combination of LOCALIP and PEERIP.
- The E1/T1 timeslots used by any two PPPLNK MOs must not have an intersection.
- Each PPPLNK MO must have a unique LOCALIP.
- LOCALIP of two PPPLNK MOs must be on different network segments.
Relation with the BFDSESSION MO:
- If a BFDSESSION MO and a PPPLNK MO are in the same routing domain, DSTIP in the
BFDSESSION MO must be different from LOCALIP in the PPPLNK MO.
Relation with the UDPSESSION MO:
- PEERIP in an UDPSESSION MO must be different from LOCALIP in a PPPLNK MO.
Relation with the MPGRP MO:
- LOCALIP in a PPPLNK MO must be different from LOCALIP in an MPGRP MO.
- LOCALIP in a PPPLNK MO must be different from PEERIP in an MPGRP MO.
- PEERIP in a PPPLNK MO must be different from LOCALIP in an MPGRP MO.
- LOCALIP in a PPPLNK MO must be on a different network segment from LOCALIP in
an MPGRP MO.
Relation with the LOCALIP MO:
- IP in a LOCALIP MO must be different from LOCALIP in a PPPLNK MO.
- IP in a LOCALIP MO must be different from PEERIP in a PPPLNK MO.
- IP in a LOCALIP MO must be on a different network segment from LOCALIP in a
PPPLNK MO.
Relation with the IPPMSESSION MO:
- If BINDPATH in an IPPMSESSION MO is set to NO, LOCALIP in the associated
PPPLNK MO must be different from PEERIP in the IPPMSESSION MO.
Relation with the OMCH MO:
- IP in an OMCH MO must be different from PEERIP in a PPPLNK MO.
- PEERIP in an OMCH MO must be different from LOCALIP in a PPPLNK MO.
Relation with the SCTPLNK MO:
- In a routing domain,PEERIP in a PPPLNK MO must be different from LOCIP and
SECLOCIP in an SCTPLNK MO.
Relation with the IPPATH MO:
- If PT and JNRSCGRP in an IPPATH MO are set to PPP and DISABLE, respectively, the
associated PPPLNK MO must have been configured.
- If LOCALIP in an IPPATH MO is set to 0.0.0.0, the IPPATH MO must have been
configured on a PPPLNK MO whose LOCALIP is set to 0.0.0.0.
Relation with the MPLNK MO:
- On a board, PPPLNKN in a PPPLNK MO must be different from PPPLNKN in an
MPLNK MO.
- The E1/T1 timeslots occupied by an PPPLNK MO and those occupied by an MPLNK MO
must not have an intersection.
Relation with the E1T1 MO:
- If SBT in a PPPLNK MO is not set to BACK_BOARD, the associated E1T1 MO must have
been configured.
Relation with the DEVIP MO:
- If PT in a DEVIP MO is set to PPP, the associated PPPLNK MO must have been
configured.
- LOCALIP in a PPPLNK MO must be different from IP in a DEVIP MO in the same
routing domain.
- PEERIP in a PPPLNK MO must be different from IP in a DEVIP MO in the same routing
domain.
- LOCALIP in a PPPLNK MO must be on a different network segment from IP in a DEVIP
MO in the same routing domain on another interface.
Relation with the IPRT MO:
- If RTTYPE and IFT are set to IF and PPP, respectively in an IPRT MO, IFNO in the IPRT
MO must be the same as PPPLNKN in the associated PPPLNK MO.
- If RTTYPE and IFT in an IPRT MO are set to IF and TUNNEL, DSTIP in an IPRT MO
must be different from LOCALIP in an PPPLNK MO.
Relation with the RSCGRP MO:
- If PT in an RSCGRP MO is set to PPP, the associated PPPLNK MO must have been
configured.
Relation with the UDPSESSION,DEVIP,MPGRP MOs:
- UDPSESSION:LOCALIP in an UDPSESSION MO to be added must have been
configured. That is, for the UDPSESSION, DEVIP, PPPLNK, and MPGRP MOs configured
on the same board, LOCALIP in the UDPSESSION MO must be the same as any of the
following : IP in the DEVIP MO with the same routing domain, LOCALIP in the PPPLNK
MO, and LOCALIP in the MPGRP MO.
Relation with the IPPMSESSION,DEVIP,MPGRP MOs:
- If BINDPATH in an IPPMSESSION MO is set to NO, the IP address corresponding to
LOCALIP in the IPPMSESSION MO must have been configured. That is, for the
IPPMSESSION MO, DEVIP MO in the same routing domain, PPPLNK MO, and MPGRP
MO configured on the same board, LOCALIP in the IPPMSESSION MO must be the same as
any of the following: IP in the DEVIP MO; LOCALIP in the PPPLNK MO; or LOCALIP in
the MPGRP MO.
Relation with the BFDSESSION,DEVIP,MPGRP MOs:
- SRCIP in a BFDSESSION MO to be added must have been configured. That is, for the
BFDSESSION, DEVIP, PPPLNK, and MPGRP MOs configured on the same board, SRCIP
in the BFDSESSION MO must be the same as any of the following : IP in the DEVIP MO in
the same routing domain, LOCALIP in the PPPLNK MO, and LOCALIP in the MPGRP MO.
Relation with the PORTSECURITY MO:
- The E1T1 MO that is associated with a PPPLNK MO must meet either of the following
conditions: (1) No PORTSECURITY MO is associated with the E1T1 MO; (2) A
PORTSECURITY MO is associated with the E1T1 MO, but SWITCH in the
PORTSECURITY MO is set to ENABLE.
Relation with the SUBIF MO:
- A PPPLNK MO and a SUBIF MO cannot both be configured.
Relation with the VRF MO:
- A PPPLNK MO and a VRF MO whose VRFIDX is set to 1 to 7 cannot both be configured.
Relation with the SCTPLNK,MPGRP,DEVIP MOs:
- Before adding an SCTPLNK MO, ensure that the MPGRP or PPPLNK MO that has the
same combination of cabinet number, subrack number, and slot number as the SCTPLNK MO
has been configured. Alternatively, ensure that the DEVIP, MPGRP, or PPPLNK MO that
meets both of the following conditions has been configured: (1) The DEVIP, MPGRP, or
PPPLNK MO is in the same routing domain as the SCTPLNK MO. (2) LOCIP or SECLOCIP
in the SCTPLNK MO is the same as IP in the DEVIP MO, LOCALIP in the MPGRP MO, or
LOCALIP in the PPPLNK MO.
Relation with the SCTPPEER,DEVIP,MPGRP MOs:
- In a routing domain,SIGIP1V4 in an SCTPPEER MO must be different from
IP,LOCALIP or LOCALIP in a configured DEVIP MO,MPGRP and PPPLNK.
- In a routing domain,SIGIP2V4 in an SCTPPEER MO must be different from
IP,LOCALIP or LOCALIP in a configured DEVIP MO,MPGRP and PPPLNK.
Relation with the USERPLANEHOST,DEVIP,MPGRP MOs:
- In a routing domain,LOCIPV4 in a USERPLANEHOST MO must be the same as
IP ,LOCALIP or LOCALIP in a configured DEVIP MO ,MPGRP or PPPLNK.
Relation with the USERPLANEPEER,DEVIP,MPGRP MOs:
- PEERIPV4 in a USERPLANEPEER MO must be different from IP ,LOCALIP or
LOCALIP in a configured DEVIP MO ,MPGRP and PPPLNK.
Relation with the USERPLANEHOST MO:
- In a routing domain, if LOCIPV4 in the USERPLANEHOST MO is referenced by
LOCALIP in the PPPLNK MO, IPSECSWITCH in the USERPLANEHOST MO must not
be set to ENABLE.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD PPPLNK Use this command to add a PPP link.

DSP PPPLNK Use this command to query the status of a PPP link.

LST PPPLNK Use this command to list the parameters of the PPP links.

MOD PPPLNK Use this command to modify the parameters of the PPP links.

RMV PPPLNK Use this command to remove a PPP link.

RST PPPLNK Use this command to reset a PPP link and restart the negotiation.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the board where the PPP link is located.

Subrack No. Indicates the subrack number of the board where the PPP link is located.
Table 2 Related parameters

Parameter Description

Slot No. Indicates the slot number of the board where the PPP link is located.

Link No. Indicates the number of the PPP link.

Port No. Indicates the number of the E1/T1 port that carries the PPP link.

Authentication Type Indicates the mode in which the local end of a PPP link authenticates the peer
end. The authentication mode is classified into NONAUTH, PAP, and CHAP. In
PAP mode, user names and passwords are transmitted explicitly on the network.
If they are intercepted during transmission, a great threat to network security is
caused. Thus, the PAP is applied only to the network environment with low
security requirements. With three handshakes, the CHAP provides a more secure
authentication. In CHAP mode, only user accounts rather than passwords are
transmitted, enhancing security compared to the PAP.

User Name Indicates the authentication user name of the PPP link.

Password Indicates the password for authenticating a PPP link.

Time Slot No. Indicates the number of the ET/T1 timeslot that carries the PPP link.

Local IP Indicates the local IP address. If this parameter is set to 0.0.0.0, this parameter
needs to be negotiated.

Mask Indicates the subnet mask of the local IP address. If this parameter is set to
0.0.0.0, it needs to be negotiated.

Peer IP Indicates the peer IP address. If the BS is connected to an upper-level node, this
address is specified according to the upper-level node. If the BS is cascaded to a
lower-level node, this address must be specified. This parameter can be set to
0.0.0.0.

PPPMUX Indicates whether to enable the PPP multiframe multiplexing function. If this
parameter is set to ENABLE, multiple PPP frames are multiplexed on the PPP
link to reduce the bandwidth overhead.

Maximum Length of Indicates the maximum length of the PPP Multiplexing (MUX) subframe.
PPP Mux Subframe

Maximum Length of Indicates the maximum length of the PPP MUX frame.
PPP Muxframe

PPP Muxframe Indicates the timeout duration of the PPP MUX combination.
Table 2 Related parameters

Parameter Description

Combination Timeout

IP Header Compression Indicates whether to enable IP header compression.

IPHC SubOption Indicates whether to enable IPHC suboption negotiation.

Maximum Receive Unit Indicates the Maximum Receive Unit (MRU). If the size of a received packet is
greater than the MRU value, the packet is discarded.

Protocol Field Indicates whether to enable protocol field compression.


Compression

Address and Control Indicates whether to enable the compression of the address field and control
Field Compression
field.

Negotiation Time Indicates the timeout duration for the PPP link negotiation.

Link Status Indicates the status of the PPP link.

LCP Status Indicates the status of the Link Control Protocol (LCP) protocol.

IPCP Status Indicates the status of the IP Control Protocol (IPCP).

PPPMUX Status Indicates the status of the PPP MUX.

Local IP Negotiation Indicates the local IP address negotiated with the peer end.
Result

Local IP Mask Indicates the mask of the local IP address that is negotiated with the peer end.
Negotiation Result

Peer IP Negotiation Indicates the peer IP address negotiated with the peer end.
Result

IPHC Negotiation Indicates the negotiation result of the IP header compression.


Result

ACFC Negotiation Indicates the negotiation result of the compression switch of the address field
Result
and control field.

PFC Negotiation Result Indicates the negotiation result of the compression switch of the protocol field.

Maximum Receive Unit Indicates the negotiation result of the maximum RX unit.
Negotiation Result

PPPMUX Negotiation Indicates the negotiation result of the PPP MUX.


Result

Number of RX Packets Indicates the number of packets received on the PPP link.
Table 2 Related parameters

Parameter Description

Number of TX Packets Indicates the number of packets transmitted on the PPP link.

RX Flow Indicates the RX traffic of the PPP link.

TX Flow Indicates the TX traffic of the PPP link.

Number of IPs Indicates the number of IP addresses of the PPP link.

IP Address List Indicates the list of IP addresses of the PPP link.

PPP Fault Frame Indicates the PPP frame error rate threshold above which the related alarm is
Occurrence Threshold
generated.

PPP Fault Frame Clear Indicates the PPP frame error rate threshold below which the related alarm is
Threshold
cleared.

Subboard Type Indicates the type of sub-board on the board where a PPP link is located.

Number of RX Bytes Indicates the number of bytes received on the PPP link.

Number of RX Drop Indicates the number of discarded packets received on the PPP link.
Packets

Number of TX Bytes Indicates the number of bytes transmitted on the PPP link.

Number of TX Drop Indicates the number of discarded packets transmitted on the PPP link.
Packets

5.7.1.6.1.78 PRI2QUE
TRANSPORT
+-VRF
+-PRI2QUE

Description

This MO is used to set the mapping between transport bearer priorities (only DSCPs are
currently supported) and inner queues. The inner service scheduling function enables the data
packets with different priorities to be scheduled to the corresponding queues based on this
mapping. Currently, priorities can be configured only by DSCP.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
VRF

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST PRI2QUE Use this command to list the mapping from the transport bearer priority to the
inner queue.

SET PRI2QUE Use this command to set the mapping between the transport bearer priority (only
DSCP is supported) and the inner queue.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

VRF Index Indicates the index of a VRF instance.

PriOfQue0 Indicates the lowest priority of queue 0. If the Differentiated Services Code
Point (DSCP) value of a service packet is greater than or equal to this parameter
value, the service packet is assigned to queue 0.

PriOfQue1 Indicates the lowest priority of queue 1. If the DSCP value of a service packet is
smaller than the PRI0 value but greater than or equal to this parameter value, the
service packet is assigned to queue 1.
Table 2 Related parameters

Parameter Description

PriOfQue2 Indicates the lowest priority of queue 2. If the DSCP value of a service packet is
smaller than the PRI1 value but greater than or equal to this parameter value, the
service packet is assigned to queue 2.

PriOfQue3 Indicates the lowest priority of queue 3. If the DSCP value of a service packet is
smaller than the PRI2 value but greater than or equal to this parameter value, the
service packet is assigned to queue 3.

PriOfQue4 Indicates the lowest priority of queue 4. If the DSCP value of a service packet is
smaller than the PRI3 value but greater than or equal to this parameter value, the
service packet is assigned to queue 4.

PriOfQue5 Indicates the lowest priority of queue 5. If the DSCP value of a service packet is
smaller than the PRI4 value but greater than or equal to this parameter value, the
service packet is assigned to queue 5.

PriOfQue6 Indicates the lowest priority of queue 6. If the DSCP value of a service packet is
smaller than the PRI5 value but greater than or equal to this parameter value, the
service packet is assigned to queue 6.

5.7.1.6.1.79 RSCGRP
TRANSPORT
+-RSCGRP
+-RSCGRPALG[1~1]

Description

The RSCGRP MO indicates a collection of data streams. NEs perform bandwidth management
on transmission resource groups, including configuring the bandwidth of a transmission resource
group, traffic shaping, admission control, and flow control. Multiple transmission resource
groups can be configured on a physical bearer link, and each transmission resource group
occupies part of the bandwidth of the physical bearer link exclusively. Each transmission
resource group performs the functions such as admission control, congestion control. Each
transmission resource group has multiple transport bearers, which share the bandwidth
configured for the transmission resource group.

Effective Scenario
Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Possible children:
RSCGRPALG[1~1]

Relation with the RSCGRP MO:


- A maximum of eight RSCGRP MOs that meet the following condition can be configured on
a board: PT is set to PPP or MPGRP, and RSCGRPID is not set to DEFAULTPORT.
- A maximum of 16 RSCGRP MOs whose RSCGRPID is not set to DEFAULTPORT can be
configured on a board.
- An RSCGRP MO can be configured on only one TUNNEL MO.
- If PT in an RSCGRP MO is set to IMA, the associated IMAGRP MO must have been
configured.
- If PT in an RSCGRP MO is set to UNI, the associated UNILNK MO must have been
configured.
- If PT in an RSCGRP MO is set to FRAATM, the associated FRAATM MO must have been
configured.
Relation with the HAGRP MO:
- In one logical protection group, SN in an HAGRP MO must be the same as that in an
RSCGRP MO.
Relation with the RSCGRPALG MO:
- Before modifying an RSCGRPALG MO, ensure that the associated RSCGRP MO is
configured. An RSCGRP MO is associated with an RSCGRPALG MO when both the
following conditions are met: BEAR in the RSCGRP MO is set to IP; CN, SRN, SN, SBT, PT,
and PN in the RSCGRP MO are the same as those in the RSCGRPALG MO, respectively.
- When an RSCGRP MO is being added, the system automatically adds the associated
RSCGRPALG MO. Before an RSCGRP MO is removed, the system automatically removes the
RSCGRPALG MO associated with the RSCGRP MO.
Relation with the IPPATH MO:
- If JNRSCGRP in an IPPATH MO is set to ENABLE, the associated RSCGRP MO must
have been configured.
Relation with the IPPATH6 MO:
- If JNRSCGRP in an IPPATH6 MO is set to ENABLE, the associated RSCGRP MO must
have been configured.
Relation with the MPGRP MO:
- If PT in an RSCGRP MO is set to MPGRP, the associated MPGRP MO must have been
configured.
Relation with the PPPLNK MO:
- If PT in an RSCGRP MO is set to PPP, the associated PPPLNK MO must have been
configured.
Relation with the ETHTRK MO:
- If PT in an RSCGRP MO is set to ETHTRK, the associated ETHTRK MO must have been
configured.
Relation with the ETHTRKLNK MO:
- If an ETHPORT MO has been added to an ETHTRK MO, an RSCGRP MO that meets
both the following conditions must not be configured: (1) PT in the RSCGRP MO is set to ETH.
(2) CN, SRN, SN, SBT, and PN in the RSCGRP MO are the same as those in the associated
ETHTRKLNK MO, respectively.
Relation with the IP2RSCGRP MO:
- The RSCGRP MO corresponding to an IP2RSCGRP MO must have been configured.
Relation with the PORTSECURITY MO:
- The ETHPORT MO that is associated with an RSCGRP MO must meet either of the
following conditions: (1) No PORTSECURITY MO is associated with the ETHPORT MO; (2)
A PORTSECURITY MO is associated with the ETHPORT MO, but SWITCH in the
PORTSECURITY MO is set to ENABLE.
Relation with the TUNNEL MO:
- If PT in an RSCGRP MO is set to TUNNEL, the TUNNEL MO corresponding to PN in the
RSCGRP MO must have been configured.
Relation with the LR MO:
- An RSCGRP MO and an LR MO can be configured on only one TUNNEL MO.
Relation with the EP2RSCGRP MO:
- The RSCGRP MO on which an EP2RSCGRP MO depends must have been configured.
Relation with the IP2RSCGRP6 MO:
- The RSCGRP MO corresponding to an IP2RSCGRP6 MO must have been configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD RSCGRP Use this command to add a transmission resource group.

DSP RSCGRP Use this command to query the status of a transmission resource group.

LST RSCGRP Use this command to list the configurations of all transmission resource groups.

MOD RSCGRP Use this command to modify the configuration of a transmission resource group.

RMV RSCGRP Use this command to remove a transmission resource group.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet that houses the board where a transmission
resource group is established.

Subrack No. Indicates the number of the subrack that houses the board where a transmission
resource group is established.

Slot No. Indicates the number of the slot corresponding to the board where a transmission
resource group is established.

Transmission Resource Indicates the bearer type of the transmission group. The NodeB currently does
Group Bear Type
not support ATM.

Subboard Type Indicates the type of sub-board on the transmission group. The eNodeB
currently does not support UNCHANNELLED_COVERBOARD.

Bearing Port Type Indicates the type of port where a transmission resource group is carried. The
eNodeB currently does not support STM1, IMA, UNI, or FRAATM.

Bearing Port No. Indicates the number of the port where the transmission resource group is
configured.

Transmission Resource Indicates the ID of a transmission resource group. When you add a PPP link, an
Group ID
MP group, an Ethernet port, an Ethernet trunk, or a tunnel, the system
Table 2 Related parameters

Parameter Description

automatically creates a transmission resource group with Transmission Resource


Group ID set to DEFAULTPORT(Default Port). When you remove any of the
preceding objects, the system automatically removes the transmission resource
group.

Rate Unit Indicates the rate unit of the TX bandwidth, RX bandwidth, TX CIR, RX CIR,
TX PIR and RX PIR of the transmission resource group. The eNodeB currently
does not support CELL/S.

Tx Bandwidth Indicates the maximum uplink bandwidth of a transmission resource group at


the MAC layer when the transmission resource group is carried over IP. This
parameter value is used as the uplink transport admission bandwidth and TX
traffic shaping bandwidth.The LMPT can be configured with a maximum of 360
Mbit/s TX bandwidth.The UMPT can be configured with a maximum of 1
Gbit/s TX bandwidth.The value of TX bandwidth is set to the maximum value of
TX bandwidth supported by the board when it bigger than the maximum one.

Rx Bandwidth Indicates the RX bandwidth of a transmission resource group.This parameter


value is used as the downlink transport admission bandwidth.The minimum rate
supported by the UMPTb is 64 Kbit/s.The LMPT can be configured with a
maximum of 540 Mbit/s RX bandwidth.The UMPT can be configured with a
maximum of 1 Gbit/s RX bandwidth.The value of RX bandwidth is set to the
maximum value of RX bandwidth supported by the board when it bigger than
the maximum one.

TX Committed Burst Indicates the TX committed burst size of a transmission resource group.The
Size
LMPT can be configured with a maximum of 400 Mbit/s TX committed burst
size.The UMPT can be configured with a maximum of 1 Gbit/s TX committed
burst size.The value of TX committed burst size is set to the maximum value of
TX committed burst size supported by the board when it bigger than the
maximum one.

TX Excessive Burst Indicates the TX excessive burst size of a transmission resource group.The
Size
LMPT can be configured with a maximum of 450 Mbit/s TX excessive burst
size.The UMPT can be configured with a maximum of 1 Gbit/s TX excessive
burst size.The value of TX excessive burst size is set to the maximum value of
TX excessive burst size supported by the board when it bigger than the
maximum one.

Operator ID Indicates the index of the operator. This parameter is used to differentiate
between operators. This parameter is reserved for future extension and does not
take effect currently.

Scheduling Weight Indicates the scheduling weight of a transmission resource group. This
Table 2 Related parameters

Parameter Description

parameter is used in calculating the bandwidth scheduled to a resource group,


which helps achieve the user admission control.

TX Committed Indicates the transmit CIR of the transmission resource group.The LMPT can be
Information Rate
configured with a maximum of 360 Mbit/s TX committed information rate.The
UMPT can be configured with a maximum of 1 Gbit/s TX committed
information rate.The value of TX committed information rate is set to the
maximum value of TX committed information rate supported by the board when
it bigger than the maximum one.

RX Committed Indicates the receive CIR of the transmission resource group.This parameter
Information Rate
value is used as the downlink transport admission bandwidth for non-flow-
control services.The LMPT can be configured with a maximum of 540 Mbit/s
RX committed information rate.The UMPT can be configured with a maximum
of 1 Gbit/s RX committed information rate.The value of RX committed
information rate is set to the maximum value of RX committed information rate
supported by the board when it bigger than the maximum one.Only the LTE
supports this function currently.

TX Peak Information Indicates the transmit PIR of the transmission resource group.The LMPT can be
Rate
configured with a maximum of 360 Mbit/s TX peak information rate.The UMPT
can be configured with a maximum of 1 Gbit/s TX peak information rate.The
value of TX peak information rate is set to the maximum value of TX peak
information rate supported by the board when it bigger than the maximum one.

RX Peak Information Indicates the receive PIR of the transmission resource group.This parameter
Rate
value is used as the downlink transport admission bandwidth.The LMPT can be
configured with a maximum of 540 Mbit/s RX peak information rate.The UMPT
can be configured with a maximum of 1 Gbit/s RX peak information rate.The
value of RX peak information rate is set to the maximum value of RX peak
information rate supported by the board when it bigger than the maximum
one.Only the LTE supports this function currently.

TX Peak Burst Size Indicates the size of the peak burst transmitted from the transmission resource
group.The LMPT can be configured with a maximum of 540 Mbit/s TX peak
burst size.The UMPT can be configured with a maximum of 1 Gbit/s TX peak
burst size.The value of TX peak burst size is set to the maximum value of TX
peak burst size supported by the board when it bigger than the maximum one.

Realtime TX Bandwidth Indicates the local real-time traffic that is transmitted in a transmission resource
group. The local traffic includes only the local traffic stream exclusive of the
passing-by data flow and non-traffic stream.The parameter takes effect only in
LTE.
Table 2 Related parameters

Parameter Description

Realtime RX Bandwidth Indicates the local real-time traffic that is received in a transmission resource
group. The local traffic includes only the local traffic stream exclusive of the
passing-by data flow and non-traffic stream.The parameter takes effect only in
LTE.

Non-Realtime TX Indicates the local non-real-time traffic that is transmitted in a transmission


Bandwidth
resource group. The local traffic includes only the local traffic stream exclusive
of the passing-by data flow and non-traffic stream.The parameter takes effect
only in LTE.

Non-Realtime RX Indicates the local non-real-time traffic that is received in a transmission


Bandwidth
resource group. The local traffic includes only the local traffic stream exclusive
of the passing-by data flow and non-traffic stream.The parameter takes effect
only in LTE.

Non-Realtime Reserved Indicates the TX bandwidth reserved for non-real-time services in a transmission
TX Bandwidth
resource group.The parameter takes effect only in LTE.

Non-Realtime Reserved Indicates the RX bandwidth reserved for non-real-time services in a


RX Bandwidth
transmission resource group.The parameter takes effect only in LTE.

Tx Bandwidth Used Indicates the TX bandwidth that is already used by a transmission resource
group.

Rx Bandwidth Used Indicates the RX bandwidth that are already used by a transmission resource
group.

Tx Bandwidth Usable Indicates the RX bandwidth that are already used by a transmission resource
group.

Rx Bandwidth Usable Indicates the RX bandwidth that are already used by a transmission resource
group.

GBR Tx Bandwidth Indicates the GBR service traffic that is transmitted by the transmission resource
group.The parameter takes effect only in LTE.

GBR Rx Bandwidth Indicates the GBR service traffic received by the transmission resource
group.The parameter takes effect only in LTE.

Rate Configuration Indicates the rate configuration mode of the transmission resource group.
Type

UL Admission Indicates the uplink admission bandwidth of the transmission resource


Bandwidth
group.The parameter takes effect only in LTE.
Table 2 Related parameters

Parameter Description

DL Admission Indicates the downlink admission bandwidth of the transmission resource


Bandwidth
group.The parameter takes effect only in LTE.

UL CIR Admission Indicates the UL Committed Information Rate (CIR) admission bandwidth for
Bandwidth
the transmission resource group.The parameter takes effect only in LTE.

DL CIR Admission Indicates the CIR admission bandwidth of the transmission resource group in
Bandwidth
DL.The parameter takes effect only in LTE.

UL PIR Admission Indicates the UL PIR admission bandwidth of the transmission resource
Bandwidth
group.The parameter takes effect only in LTE.

DL PIR Admission Indicates the PIR admission bandwidth of the transmission resource group in
Bandwidth
DL.The parameter takes effect only in LTE.

Realtime Tx Traffic Indicates the realtime traffic sent on a transmission resource group.

5.7.1.6.1.80 RSCGRPALG
TRANSPORT
+-RSCGRP
+-RSCGRPALG

Description

This MO is used to set the parameters of the algorithm for a transmission resource group. Each
transmission resource group corresponds to a type of algorithm. According to the corresponding
algorithm, each transmission resource group performs operations such as traffic control.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
RSCGRP

Relation with the RSCGRP MO:


- Before modifying an RSCGRPALG MO, ensure that the associated RSCGRP MO is
configured. An RSCGRP MO is associated with an RSCGRPALG MO when both the
following conditions are met: BEAR in the RSCGRP MO is set to IP; CN, SRN, SN, SBT, PT,
and PN in the RSCGRP MO are the same as those in the RSCGRPALG MO, respectively.
- When an RSCGRP MO is being added, the system automatically adds the associated
RSCGRPALG MO. Before an RSCGRP MO is removed, the system automatically removes the
RSCGRPALG MO associated with the RSCGRP MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST RSCGRPALG Use this command to list the settings of all transmission resource group
algorithms.

SET RSCGRPALG Use this command to set the configuration of a transmission resource group.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet that houses the board where a transmission
resource group is established.

Subrack No. Indicates the number of the subrack that houses the board where a transmission
resource group is established.

Slot No. Indicates the number of the slot corresponding to the board where a transmission
resource group is occupied.

Subboard Type Indicates the type of sub-board on the transmission group. The eNodeB
currently does not support UNCHANNELLED_COVERBOARD.

Transmission Resource Indicates the bearer type of the transmission group. The eNodeB currently does
Group Bear Type
not support ATM.
Table 2 Related parameters

Parameter Description

Bearing Port Type Indicates the type of port where a transmission resource group is carried. The
eNodeB currently does not support STM1, IMA, UNI, or FRAATM.

Bearing Port No. Indicates the number of the port where the transmission resource group is
configured.

Transmission Resource Indicates the ID of a transmission resource group. When you add a PPP link, an
Group ID
MP group, an Ethernet port, an Ethernet trunk, or a tunnel, the system
automatically creates an algorithm for the transmission resource group with
Transmission Resource Group ID set to DEFAULTPORT(Default Port). When
you remove any of the preceding objects, the system automatically removes the
algorithm for the transmission resource group.

TX Traffic Shaping Indicates whether to enable traffic shaping for a transmission resource group. If
Switch
this parameter is set to ON, traffic shaping is performed according to the TX
bandwidth so that the transmit traffic would not exceed the capability of
downstream routers, thus avoiding unnecessary packet loss and congestion. If
this parameter is set to OFF, traffic shaping is not performed during data
transmission.

TX Bandwidth Indicates whether to enable the dynamic adjustment of the RX bandwidth of a


Adjustment Switch
transmission resource group,This parameter takes effect only for the resource
groups to which ENODEBPATH or GBTSPATH is added.
If this parameter is set to ON, the TX bandwidth is adjusted according to the
network performance and dynamic bandwidth adjustment parameters (down
speed PLR threshold and down speed delay threshold). The network
performance is monitored through IP PM sessions, which can be enabled at the
local end or at the peer end.
If this parameter is set to OFF, the TX bandwidth is not adjusted.
The NodeB currently does not support this function.

RX Bandwidth Indicates whether to enable the dynamic adjustment of the RX bandwidth of a


Adjustment Switch
transmission resource group.
If this parameter is set to ON, the RX bandwidth is adjusted according to the
network performance and dynamic bandwidth adjustment parameters (down
speed PLR threshold and down speed delay threshold). The network
performance is monitored through IP PM sessions, which can be enabled at the
local end or at the peer end.
If this parameter is set to OFF, the RX bandwidth is not adjusted.
The NodeB currently does not support this function.

Packet Loss Ratio Indicates the rate downsizing packet loss rate threshold for bandwidth
Down Threshold
adjustment. When RXBWASW or TXBWASW is set to ON, the estimated
Table 2 Related parameters

Parameter Description

available transport bandwidth is reduced if the packet loss rate detected through
IP Performance Monitoring (IP PM) is higher than this threshold. If the packet
loss rate detected through IP PM is lower than this threshold, the estimated
available transport bandwidth is increased.

Delay Variation Down Indicates the threshold for delay variation due to rate reduction. When
Threshold
RXBWASW or TXBWASW is set to ON, the estimated available transport
bandwidth is reduced if the delay variation detected by an IP PM session is
above this threshold.The NodeB currently does not support this function.

TX Bandwidth Adjust Indicates the minimum TX bandwidth that adjustments can achieve. If the
Minimum
RATECFGTYPE (global rate configuration type) and TXBWASW (TX
bandwidth adjustment switch) parameters are set to SINGLE_RATE and ON,
respectively, the TX bandwidth obtained after each adjustment is equal to or
larger than the value of this parameter.

RX Bandwidth Adjust Indicates the minimum RX bandwidth that adjustments can achieve. If the
Minimum
RATECFGTYPE (global rate configuration type) and RXBWASW (RX
bandwidth adjustment switch) parameters are set to SINGLE_RATE and ON,
respectively, the RX bandwidth obtained after each adjustment is equal to or
larger than the value of this parameter.

Traffic Control Switch Indicates whether to enable the backpressure algorithm of a transmission
resource group.
The BS monitors the data buffered in the queues of each transmission resource
group, determines whether the transmission resource group is congested, and
transmits the backpressure signals (number and congestion status of the
transmission resource group) to each flow control service.
If the number of data packets in the buffer of any backpressure queue exceeds
75% of the queue capacity, the BS regards this transmission resource group as
congested and transmits congestion signals.
If the buffered back-pressure packets are less than 50% of the total buffer
capacity, the BS decides that the transmission resource group is not congested.
In this situation, no congestion signal or congestion release signal is transmitted.

OM FTP Traffic Control Indicates whether backpressure is performed on the OM FTP queue in a
Switch
transmission resource group. If this parameter is set to ENABLE, the OM FTP
queue participates the decision of the congestion status of the transmission
resource group, and the OM low-level upload and download data preempts the
bandwidth of non-real-time services. If this parameter is set to DISABLE, the
OM FTP queue does not participate the decision of the congestion status of the
transmission resource group, and the OM low-level upload and download data
does not preempt the bandwidth of non-real-time services. The bandwidth of
OM low-level upload and download data is far smaller than that of any other
Table 2 Related parameters

Parameter Description

service.

PQ Number Indicates the number of Priority Queues (PQs) in a transmission resource group.
The queues in a transmission resource group are classified into PQs and non-
PQs. The scheduling priority of any PQ is higher than that of any non-PQ. There
is no Priority Queues when this parameter value is 0.The queues numbered from
0 to the result after this parameter value minus 1 are PQs. PQ scheduling is used
between PQs. A smaller PQ number indicates a higher scheduling priority. The
queues numbered from this parameter value to 6 are non-PQs. Weight Round
Robin (WPR) scheduling is used between non-PQs.

Congestion Time Indicates the congestion time threshold of a transmission resource group. When
Threshold
TCSW is set to ENABLE, if the buffer time of non-real-time service data in a
transmission resource group exceeds the threshold, it indicates that the
transmission resource group is congested and the backpressure signals are
transmitted.

Congestion Clear Time Indicates the congestion clear time threshold of a transmission resource group.
Threshold
When TCSW is set to ENABLE, if the buffer time of non-real-time service data
in a transmission resource group is below the threshold, it indicates that the
transmission resource group is not congested and therefore the congestion clear
signals are transmitted.

TX Reserved Indicates the TX bandwidth reserved for signaling or OM data. This parameter
Bandwidth
should be set to a value smaller than the TX bandwidth of a transmission
resource group. The recommended reserved TX bandwidth is lower than or
equal to 3% of the TX bandwidth of a transmission resource group.The NodeB
currently does not support this function.

RX Reserved Indicates the reserved RX bandwidth, which should be set to a value smaller
Bandwidth
than or equal to the RX bandwidth of a transmission resource group. The NodeB
currently does not support this function.

Drop Packet Number Indicates the number threshold of discarded packets. This parameter indicates
Threshold
the capability of the queue in a transmission resource group to buffer packets. A
greater parameter value indicates a stronger capability. If this parameter is set to
0, the queue in a transmission resource group cannot buffer packets, and thus all
the delayed packets on the TX channel are discarded. The number threshold of
discarded packets determines the maximum amount of data that can be buffered
in a transmission resource group. The congestion time threshold of a
transmission resource group determines the amount of data that is buffered when
the transmission resource group is congested. Ensure that the maximum amount
of data that can be buffered is not less than the amount of data that is buffered
during congestion.
5.7.1.6.1.81 SCTPHOST
TRANSPORT
+-SCTPHOST

Description

The SCTPHOST MO is used to configure an SCTP host. When the control plane is set up
automatically, an SCTP link is automatically set up between the configured SCTP host and SCTP
peer. When the security self establishment feature is enabled on the SCTP host, the SCTP host
needs to be configured with a security host, and the IP address of the SCTP host can quote only
one security host.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the DEVIP MO:


- In a routing domain,SIGIP1V4 in an SCTPHOST MO must be the same as IP in a
configured DEVIP MO.
- In a routing domain,SIGIP2V4(SIGIP2V4 is not set to 0.0.0.0) in an SCTPHOST MO
must be the same as IP in a configured DEVIP MO.
- The DEVIP MOs referenced by SIGIP1V4 and SIGIP2V4 of the SCTPHOST MO must be
confiured on the same board.
Relation with the DEVIP6 MO:
- SIGIP1V6 in an SCTPHOST MO must be the same as IPV6 in a configured DEVIP6 MO.
- SIGIP2V6 (SIGIP2V6 is not set to 0:0:0:0:0:0:0:0) in an SCTPHOST MO must be the
same as IPV6 in a configured DEVIP6 MO.
- The DEVIP6 MOs referenced by SIGIP1V6 and SIGIP2V6 of the SCTPHOST MO must
be confiured on the same board.
Relation with the SCTPTEMPLATE MO:
- SCTPTEMPLATEID in an SCTPHOST MO must be the same as SCTPTEMPLATEID
in a configured SCTPTEMPLATE MO.
Relation with the SECURITYHOST MO:
- In an SCTPHOST MO, if SIGIP1SECSWITCH is set to ENABLE, SIGIP1SECHOSTID
must be the same as SECURITYHOSTID in a configured SECURITYHOST MO.
- In an SCTPHOST MO, if SIGIP1SECSWITCH is set to ENABLE, IPVERSION must be
the same as IPVERSION in a referenced SECURITYHOST MO.
- In an SCTPHOST MO, if SIGIP2SECSWITCH is set to ENABLE, SIGIP2SECHOSTID
must be the same as SECURITYHOSTID in a configured SECURITYHOST MO.
- In an SCTPHOST MO, if SIGIP2SECSWITCH is set to ENABLE, IPVERSION must be
the same as IPVERSION in a referenced SECURITYHOST MO.
- If PT in a DEVIP MO referenced by SIGIP1V4 in an SCTPHOST MO is not set to
LOOPINT, SIGIP1V4 in the SCTPHOST MO must be configured on the same physical port as
LOCIKEIPV4 in a referenced SECURITYHOST MO.
- If PT in a DEVIP MO referenced by SIGIP2V4 in an SCTPHOST MO is not set to
LOOPINT, SIGIP2V4 in the SCTPHOST MO must be configured on the same physical port as
LOCIKEIPV4 in a referenced SECURITYHOST MO.
- If PT in an IPITF6 MO referenced by SIGIP1V6 in an SCTPHOST MO is not set to
LOOPINT, SIGIP1V6 in the SCTPHOST MO must be configured on the same physical port as
LOCIKEIPV6 in a referenced SECURITYHOST MO.
- If PT in an IPITF6 MO referenced by SIGIP2V6 in an SCTPHOST MO is not set to
LOOPINT, SIGIP2V6 in the SCTPHOST MO must be configured on the same physical port as
LOCIKEIPV6 in a referenced SECURITYHOST MO.
- In a SCTPHOST MO, if SIGIP1SECSWITCH is set to ENABLE, SIGIP1V4 and
LOCIKEIPV4 of SECURITYHOST referenced by this SCTPHOST MO must be on the same
board.
- In a SCTPHOST MO, if SIGIP2SECSWITCH is set to ENABLE, SIGIP2V4 and
LOCIKEIPV4 of SECURITYHOST referenced by this SCTPHOST MO must be on the same
board.
- In a SCTPHOST MO, if SIGIP1SECSWITCH is set to ENABLE, SIGIP1V6 and
LOCIKEIPV6 of SECURITYHOST referenced by this SCTPHOST MO must be on the same
board.
- In a SCTPHOST MO, if SIGIP2SECSWITCH is set to ENABLE, SIGIP2V6 and
LOCIKEIPV6 of SECURITYHOST referenced by this SCTPHOST MO must be on the same
board.
Relation with the SCTPHOST MO:
- If SIGIP2V4 and SIGIP1SECSWITCH in an SCTPHOST MO are set to 0.0.0.0 and
DISABLE, respectively, another SCTPHOST MO that has the same combination of VRFIDX,
SIGIP1V4, PN, and SCTPTEMPLATEID as this SCTPHOST MO cannot be configured.
- If SIGIP2V4 and SIGIP1SECSWITCH in an SCTPHOST MO are set to 0.0.0.0 and
ENABLE, respectively, another SCTPHOST MO that has the same combination of VRFIDX,
SIGIP1V4, PN, SCTPTEMPLATEID, and SIGIP1SECHOSTID as this SCTPHOST MO
cannot be configured.
- If SIGIP2V4 is valid and SIGIP1SECSWITCH and SIGIP2SECSWITCH are both set to
DISABLE in an SCTPHOST MO, another SCTPHOST MO that has the same combination of
VRFIDX, SIGIP1V4, PN, SCTPTEMPLATEID, and SIGIP2V4 as this SCTPHOST MO
cannot be configured.
- If SIGIP2V4 is valid and SIGIP1SECSWITCH and SIGIP2SECSWITCH are both set to
ENABLE in an SCTPHOST MO, another SCTPHOST MO that has the same combination of
VRFIDX, SIGIP1V4, SCTPTEMPLATEID, SIGIP2V4, PN, SIGIP1SECHOSTID, and
SIGIP2SECHOSTID as this SCTPHOST MO cannot be configured.
- If SIGIP2V4 is valid and SIGIP1SECSWITCH and SIGIP2SECSWITCH are set to
ENABLE and DISABLE, respectively in an SCTPHOST MO, another SCTPHOST MO that
has the same combination of VRFIDX, SIGIP1V4, SCTPTEMPLATEID, SIGIP2V4, PN, and
SIGIP1SECHOSTID as this SCTPHOST MO cannot be configured.
- If SIGIP2V4 is valid and SIGIP1SECSWITCH and SIGIP2SECSWITCH are set to
DISABLE and ENABLE, respectively in an SCTPHOST MO, another SCTPHOST MO that
has the same combination of VRFIDX, SIGIP1V4, SCTPTEMPLATEID, SIGIP2V4, PN, and
SIGIP2SECHOSTID as this SCTPHOST MO cannot be configured.
- If SIGIP2V6 and SIGIP1SECSWITCH in an SCTPHOST MO are set to 0:0:0:0:0:0:0:0
and DISABLE, respectively, another SCTPHOST MO that has the same combination of
SIGIP1V6, PN, and SCTPTEMPLATEID as this SCTPHOST MO cannot be configured.
- If SIGIP2V6 and SIGIP1SECSWITCH in an SCTPHOST MO are set to 0:0:0:0:0:0:0:0
and ENABLE, respectively, another SCTPHOST MO that has the same combination of
SIGIP1V6, PN, SCTPTEMPLATEID, and SIGIP1SECHOSTID as this SCTPHOST MO
cannot be configured.
- If SIGIP2V6 is valid and SIGIP1SECSWITCH and SIGIP2SECSWITCH are both set to
DISABLE in an SCTPHOST MO, another SCTPHOST MO that has the same combination of
SIGIP1V6, PN, SCTPTEMPLATEID, and SIGIP2V6 as this SCTPHOST MO cannot be
configured.
- If SIGIP2V6 is valid and SIGIP1SECSWITCH and SIGIP2SECSWITCH are both set to
ENABLE in an SCTPHOST MO, another SCTPHOST MO that has the same combination of
SIGIP1V6, SCTPTEMPLATEID, SIGIP2V6, PN,SIGIP1SECHOSTID, and
SIGIP2SECHOSTID as this SCTPHOST MO cannot be configured.
- If SIGIP2V6 is valid and SIGIP1SECSWITCH and SIGIP2SECSWITCH are set to
ENABLE and DISABLE, respectively in an SCTPHOST MO, another SCTPHOST MO that
has the same combination of SIGIP1V6, SCTPTEMPLATEID, SIGIP2V6, PN, and
SIGIP1SECHOSTID as this SCTPHOST MO cannot be configured.
- If SIGIP2V6 is valid and SIGIP1SECSWITCH and SIGIP2SECSWITCH are set to
DISABLE and ENABLE, respectively in an SCTPHOST MO, another SCTPHOST MO that
has the same combination of SIGIP1V6, SCTPTEMPLATEID, SIGIP2V6, PN, and
SIGIP2SECHOSTID as this SCTPHOST MO cannot be configured.
Relation with the EPGROUP MO:
- SCTPHOSTID referenced by SCTPHOSTREFS in an EPGROUP MO must be the same
as SCTPHOSTID in a configured SCTPHOST MO.
- Only one SCTPHOST MO that meets both of the following conditions can be configured:
(1) The SCTPHOST MO has the same SCTP host ID as SCTPHOSTID referenced by
SCTPHOSTREFS in an EPGROUP MO. (2) IPVERSION in the SCTPHOST MO is set to
IPv4.
- Only one SCTPHOST MO that meets both of the following conditions can be configured:
(1) The SCTPHOST MO is referenced by SCTPHOSTID in SCTPHOSTREFS of an
EPGROUP MO. (2) IPVERSION in the SCTPHOST MO is set to IPv6.
Relation with the VRF MO:
- The VRF instance used by a SCTPHOST MO must have been configured.
Relation with the EPGROUP,SCTPPEER MOs:
- In a routing domain IPv4 configuration,if there are SCTPHOST MOs configured in different
EPGROUP which PNs are the same, and one's SIGIP1V4 or SIGIP2V4 is the same with the
other's SIGIP1V4 or SIGIP2V4,the same SCTPPEER MO is only allowed to be configured in
one of these EPGROUP MO.
- In a routing domain IPv6 configuration,if there are SCTPHOST MOs configured in different
EPGROUP which PNs are the same, and one's SIGIP1V6 or SIGIP2V6 is the same with the
other's SIGIP1V6 or SIGIP2V6,the same SCTPPEER MO is only allowed to be configured in
one of these EPGROUP MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD SCTPHOST Use this command to add an SCTP host.

LST SCTPHOST Use this command to list the configuration of SCTP hosts.

MOD SCTPHOST Use this command to modify an SCTP host.

RMV SCTPHOST Use this command to remove an SCTP host.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

SCTP Host ID Indicates the ID of the SCTP host.

VRF Index Indicates the index of the virtual route and forwarding(VRF) instance.

IP Version Indicates the version of the local IP address of an SCTP link.

First Local IP Address Indicates the first IPv4 address of the sctp host, which is used in automatic setup
of a Stream Control Transmission Protocol (SCTP) link.

First Local IPv6 Indicates the first IPv6 address of the sctp host, which is used in automatic setup
Address
of a Stream Control Transmission Protocol (SCTP) link.

IPSec Switch for First Indicates whether to enable automatic setup of an IPSec tunnel between the local
Local IP
end and the peer end based on the SECURITYHOST and SECURITYPEER
MOs. The IPSec tunnel is used to encrypt the data to be transmitted on the
Stream Control Transmission Protocol (SCTP) link that is set up using the first
IP address of the sctp host or the data to be transmitted on the IPv6 SCTP link
that is set up using the first IPv6 address of the sctp host.

Security Host ID for Indicates the ID of the security host referenced by the first IP address of the
First Local IP
SCTP host.

Second Local IP Indicates the second IPv4 address of the sctp host, which is used in automatic
Address
setup of a Stream Control Transmission Protocol (SCTP) link.

Second Local IPv6 Indicates the second IPv6 address of the sctp host which is used in automatic
Address
setup of a Stream Control Transmission Protocol (SCTP) link.

IPSec Switch for Indicates whether to enable automatic setup of an IPSec tunnel between the local
Second Local IP
end and the peer end based on the SECURITYHOST and SECURITYPEER
MOs. The IPSec tunnel is used to encrypt the data to be transmitted on the
Stream Control Transmission Protocol (SCTP) link that is set up using the
second IP address of the sctp host or the data to be transmitted on the IPv6 SCTP
link that is set up using the second IPv6 address of the sctp host.

Security Host ID for Indicates the ID of the security host referenced by the second IP address of the
Second Local IP
SCTP host.

Local SCTP Port No. Indicates the number of the local SCTP port, which is used in automatic setup of
a Stream Control Transmission Protocol (SCTP) link.

SCTP Parameters Indicates the ID of the SCTP parameters template referenced by the SCTP link
Template ID
that is automatically set up.
Table 2 Related parameters

Parameter Description

User Label Indicates the description of the SCTP host.

5.7.1.6.1.82 SCTPLNK
TRANSPORT
+-SCTPLNK

Description

An SCTPLNK MO consists of the parameters related to a Stream Control Transmission Protocol


(SCTP) link. The SCTP link is used to carry signaling.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the MPGRP MO:


- In a routing domain,PEERIP in an MPGRP MO must be different from LOCIP and
SECLOCIP in an SCTPLNK MO.
Relation with the OMCH MO:
- PEERIP in an OMCH MO must be different from LOCIP and SECLOCIP in an
SCTPLNK MO in the same routing domain.
Relation with the PPPLNK MO:
- In a routing domain,PEERIP in a PPPLNK MO must be different from LOCIP and
SECLOCIP in an SCTPLNK MO.
Relation with the CPBEARER MO:
- If BEARTYPE in a CPBEARER MO is set to SCTP, an SCTPLNK MO whose SCTPNO
is the same as LINKNO in the CPBEARER MO must have been configured.
Relation with the SCTPLNK MO:
- In a routing domain, each SCTPLNK MO must have a unique combination of LOCIP or
SECLOCIP (SECLOCIP is not set to 0), PEERIP or SECPEERIP (SECPEERIP is not set to
0), LOCPORT, and PEERPORT.
- On a BS, the total number of SCTPLNK6 and SCTPLNK MOs must be smaller than or
equal to 112.
- In a routing domain,when SCTPHOST MO and SCTPPEER MO are configured in one
EPGROUP MO simultaneously and their IP version are IPv4, the SIGIP1V4 or
SIGIP2V4(SIGIP2V4 is not set to 0.0.0.0), PN of SCTPHOST and the SIGIP1V4 or
SIGIP2V4(SIGIP2V4 is not set to 0.0.0.0), PN of SCTPPEER must not conflict with the
SCTPLNK MO's 4-tuple parameters.
Relation with the PPPLNK,MPGRP,DEVIP MOs:
- Before adding an SCTPLNK MO, ensure that the MPGRP or PPPLNK MO that has the
same combination of cabinet number, subrack number, and slot number as the SCTPLNK MO
has been configured. Alternatively, ensure that the DEVIP, MPGRP, or PPPLNK MO that
meets both of the following conditions has been configured: (1) The DEVIP, MPGRP, or
PPPLNK MO is in the same routing domain as the SCTPLNK MO. (2) LOCIP or SECLOCIP
in the SCTPLNK MO is the same as IP in the DEVIP MO, LOCALIP in the MPGRP MO, or
LOCALIP in the PPPLNK MO.
Relation with the SCTPLNK6 MO:
- SCTPNO in an SCTPLNK MO must be different from SCTPNO in an SCTPLNK6 MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD SCTPLNK Use this command to add an SCTP link.

BLK SCTPLNK Use this command to block an SCTP link.

DSP SCTPLNK Use this command to query the status of an SCTP link.

LST SCTPLNK Use this command to list the configuration of SCTP links.

MOD SCTPLNK Use this command to modify the configuration of an SCTP link.

RMV SCTPLNK Use this command to remove an SCTP link.

RST SCTPLNK Use this command to reset an SCTP link.


Table 1 Related MML commands

MML Command Function

UBL SCTPLNK Use this command to unblock an SCTP link.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Link No. Indicates the number of the SCTP link.

Cabinet No. Indicates the cabinet number of the SCTP link.

Subrack No. Indicates the subrack number of the SCTP link.

Slot No. Indicates the slot number of the SCTP link.

Maximum Stream No. Indicates the maximum stream number of the SCTP link.

Control Mode Indicates whether the object can be modified or deleted by the system. The value
MANUAL_MODE means that only the user can modify or delete the object.
The value AUTO_MODE means that both the system and the user can modify or
delete the object.

First Local IP Address Indicates the first local IP address of the SCTP link.

Second Local IP Indicates the second local IP address of the SCTP link.
Address

Local SCTP Port No. Indicates the local port number of the SCTP link.

First Peer IP Address Indicates the first peer IP address of the SCTP link.

Second Peer IP Indicates the second peer IP address of the SCTP link.
Address

Peer SCTP Port No. Indicates the peer port number of the SCTP link.

RTO Min Value Indicates the minimum Retransmission Timeout (RTO) value for the SCTP link.
A smaller value of this parameter indicates a shorter time required to check link
connectivity. The time required to check link connectivity is twice the sum of
Table 2 Related parameters

Parameter Description

the new RTO and heartbeat interval. The new RTO ranges from the minimum
RTO value to maximum RTO value.

RTO Max Value Indicates the maximum RTO value of an SCTP link. A larger value indicates a
longer period required for checking link connectivity.

RTO Initial Value Indicates the initial RTO value of an SCTP link. A larger value indicates a longer
period required for checking link connectivity.

RTO Alpha Value Indicates the RTO alpha value of an SCTP link. This parameter computes the
value of the Smoothed Round-Trip Time (SRTT) for a specific destination
address; A larger value of this parameter indicates a higher importance to the last
RTT measurement. For definitions of the alpha value, see RFC4960.
RTO Calculation:
The rules governing the computation of SRTT, RTTVAR, and RTO are as
follows:
1) Until an RTT measurement has been made for a packet sent to the given
destination transport address, set RTO to the protocol parameter 'RTO.Initial'.
2) When the first RTT measurement R is made, set SRTT = R, RTTVAR = R/2,
and RTO = SRTT + 4 * RTTVAR.
3) When a new RTT measurement R' is made, set RTTVAR = (1 - RTO.Beta) *
RTTVAR + RTO.Beta * |SRTT - R'|, SRTT = (1 - RTO.Alpha) * SRTT +
RTO.Alpha * R'.
Note: The value of SRTT used in the update to RTTVAR is its value before
updating SRTT itself using the second assignment.
After the computation, update RTO = SRTT + 4 * RTTVAR.

RTO Beta Value Indicates the RTO beta value of an SCTP link. This parameter computes the
value of the Smoothed Round-Trip Time (SRTT) for a specific destination
address; A larger value of this parameter indicates a higher importance to the last
RTT measurement. For definitions of the beta value, see RFC4960.
RTO Calculation:
The rules governing the computation of SRTT, RTTVAR, and RTO are as
follows:
1) After an RTT measurement has been made for a packet sent to the given
destination transport address, set RTO to the protocol parameter 'RTO.Initial'.
2) When the first RTT measurement R is made, set SRTT = R, RTTVAR = R/2,
and RTO = SRTT + 4 * RTTVAR.
3) When a new RTT measurement R' is made, set RTTVAR = (1 - RTO.Beta) *
RTTVAR + RTO.Beta * |SRTT - R'|, SRTT = (1 - RTO.Alpha) * SRTT +
RTO.Alpha * R'.
Note: The value of SRTT used in the update to RTTVAR is its value before
Table 2 Related parameters

Parameter Description

updating SRTT itself using the second assignment.


After the computation, update RTO = SRTT + 4 * RTTVAR.

Heart-beat Interval Indicates the heartbeat interval for an SCTP link. The heartbeat check is
independently initiated by each end of an association and then confirmed by the
peer end through the HB ACK packet. When no services are carried, a link
disconnection is determined if the number of heartbeat check attempts reaches
the maximum retransmission attempts on an association but the HB ACK packet
is not received from the peer end.

Max Association Indicates the maximum number of retransmissions for the SCTP association.
Retransmission
When the number of retransmissions for the association exceeds the value of this
parameter, the SCTP link is broken and a link failure alarm is reported.

Max Path Indicates the maximum number of retransmissions over a path. When the
Retransmission
number of retransmissions over a path exceeds the value of this parameter, the
path is regarded as failed if no heartbeat acknowledgment is received. If multiple
paths are used, path switching is automatically performed.

Checksum Arithmetic Indicates the type of the checksum algorithm.The checksum algorithms at both
Type
ends of the SCTP links must be the same.

Switch Back Flag Indicates whether to switch back to the primary path when it is restored. The
SCTP link switches to the secondary path when the primary path cannot be
reached. If this parameter is set to ENABLE, the SCTP link switches to the
primary path when the primary path is restored. If this parameter is set to
DISABLE, the SCTP link does not switch to the primary path when the primary
path is restored.

Heart-beat Times When Indicates the number of heartbeats to be detected before the transmission
Switch Back
switches back to the primary path. After the primary path is restored, the
transmission switches back to the primary path when the number of heartbeats
detected reaches this value.

SCTP Link Status Indicates the status of the SCTP link.

Status Change Cause Indicates the cause of the latest change that the operational state of the SCTP
link transits from available to unavailable.

Status Change Time Indicates the time of the latest change that the operational state of the SCTP link
transits from available to unavailable.

Out Stream Number Indicates the number of outbound streams negotiated for the SCTP link.
Table 2 Related parameters

Parameter Description

In Stream Number Indicates the number of inbound streams negotiated for the SCTP link.

Work Address Flag Indicates the working address flag of the SCTP link.

Block Flag Indicates whether the SCTP link is blocked or not.

SACK Timeout Indicates the time interval that one end of an SCTP link has to wait before it can
send an SACK message in response to the reception of data. A larger value of
this parameter indicates a longer time interval between the reception of data and
the sending of the corresponding SACK message.

Description Info Indicates the peer description information of the SCTP link.

Auto Config Flag Indicates whether the object is created by the system. MANUAL_CREATED
means that the object is configured by the user manually. AUTO_CREATED
means that the object is created by the system.

VRF Index Indicates the index of a VRF instance. The NodeB currently supports default
routes domain only (the VRF index is 0).

5.7.1.6.1.83 SCTPLNK6
TRANSPORT
+-SCTPLNK6

Description

The SCTPLNK6 MO is used to set parameters of IPv6 packets based on the Stream Control
Transmission Protocol (SCTP). The SCTP link carries signaling, complying with the SCTP.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT
Relation with the IKEPEER6 MO:
- REMOTEIP in an IKEPEER6 MO must be different from LOCIP and SECLOCIP in an
SCTPLNK6 MO.
Relation with the CPBEARER MO:
- If BEARTYPE in a CPBEARER MO is set to SCTP6, the SCTPLNK6 MO whose
SCTPNO is the same as LINKNO in the CPBEARER MO must have been configured.
Relation with the SCTPLNK6 MO:
- Each SCTPLNK6 MO must have a unique combination of LOCIP or SECLOCIP,
PEERIP or SECPEERIP, LOCPORT, and PEERPORT. Neither SECLOCIP nor
SECPEERIP can be set to 0.
- In an SCTPLNK6 MO, LOCIP must be set to a global unicast address.
- In an SCTPLNK6 MO, SECLOCIP must be set to a global unicast address.
- On a BS, the total number of SCTPLNK6 and SCTPLNK MOs must be smaller than or
equal to 112.
- In a routing domain,when SCTPHOST MO and SCTPPEER MO are configured in one
EPGROUP MO simultaneously and their IP version are IPv6, the SIGIP1V6 or
SIGIP2V6(SIGIP2V6 is not set to 0:0:0:0:0:0:0:0), PN of SCTPHOST and the SIGIP1V6 or
SIGIP2V6(SIGIP2V6 is not set to 0:0:0:0:0:0:0:0), PN of SCTPPEER must not conflict with
the SCTPLNK6 MO's 4-tuple parameters.
Relation with the DEVIP6 MO:
- LOCIP in an SCTPLNK6 MO must be the same as IPV6 in an existing DEVIP6 MO.
- SECLOCIP in an SCTPLNK6 MO must be the same as IPV6 in an existing DEVIP6 MO.
Relation with the SCTPLNK MO:
- SCTPNO in an SCTPLNK MO must be different from SCTPNO in an SCTPLNK6 MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD SCTPLNK6 Use this command to add an IPv6 SCTP link.

BLK SCTPLNK6 Use this command to block an IPv6 SCTP link.

DSP SCTPLNK6 Use this command to query the status of an IPv6 SCTP link.
Table 1 Related MML commands

MML Command Function

LST SCTPLNK6 Use this command to list the configuration of an IPv6 SCTP link.

MOD SCTPLNK6 Use this command to modify the parameters of an IPv6 SCTP link.

RMV SCTPLNK6 Use this command to remove an IPv6 SCTP link.

RST SCTPLNK6 Use this command to reset an IPv6 SCTP link.

UBL SCTPLNK6 Use this command to unblock an IPv6 SCTP link.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Link No. Indicates the number of an IPv6 SCTP link.

Maximum Stream No. Indicates the number of streams supported simultaneously by an IPv6 SCTP
link.

Control Mode Indicates whether the object can be modified or deleted by the system. The value
MANUAL_MODE means that only the user can modify or delete the object.
The value AUTO_MODE means that both the system and the user can modify or
delete the object.

First Local IPv6 Indicates the first local IPv6 address of an IPv6 SCTP link.
Address

Second Local IPv6 Indicates the second local IPv6 address of an IPv6 SCTP link.
Address

Local IPv6 SCTP Port Indicates the local SCTP port number of the IPv6 SCTP link. This parameter
No.
must be set to the same value as that of the peer SCTP port number in the IPv6
SCTP link configured at the peer end.

First Peer IPv6 Address Indicates the first peer IPv6 address of an IPv6 SCTP link.

Second Peer IPv6 Indicates the second peer IPv6 address of an IPv6 SCTP link.
Address
Table 2 Related parameters

Parameter Description

Peer IPv6 SCTP Port Indicates the peer SCTP port number of the IPv6 SCTP link. This parameter
No.
must be set to the same value as that of the local SCTP port number in the IPv6
SCTP link configured at the peer end.

RTO Min Value Indicates the minimum Retransmission Timeout (RTO) value for the SCTP IPv6
link. A smaller value of this parameter indicates a shorter time required to check
link connectivity.

RTO Max Value Indicates the maximum RTO value of an IPv6 SCTP link. A larger value
indicates a longer period required for checking link connectivity.

RTO Initial Value Indicates the initial RTO value of an IPv6 SCTP link. A larger value indicates a
longer period required for checking link connectivity.

RTO Alpha Value Indicates the RTO alpha value of an IPv6 SCTP link. A larger value indicates
less sensitivity to the link delay. For details, see RFC4960.

RTO Beta Value Indicates the RTO beta value of an IPv6 SCTP link. A larger value indicates
more sensitivity to the link delay. For details, see RFC4960.

Heart-beat Interval Indicates the heartbeat interval for an IPv6 SCTP link. The heartbeat check is
independently initiated by each end of an association and then confirmed by the
peer end through the HB ACK packet indicating normal link connection.
If the number of heartbeat check attempts reaches the maximum retransmission
attempts on an association but the HB ACK packet is not received from the peer
end, a link disconnection is determined.

Max Association Indicates the maximum number of association retransmissions on the IPv6
Retransmission
SCTP link. If the number of retransmissions exceeds the value of this parameter,
the SCTP link is broken and a link failure alarm is reported.

Max Path Indicates the maximum number of retransmissions over a path of the IPv6 SCTP
Retransmission
link. If no heartbeat response is received when the number of retransmissions
over a path exceeds the value of this parameter, it indicates that the current path
cannot be reached. If multiple paths are used on the IPv6 SCTP link, path
switching is performed.

Checksum Algorithm Indicates the type of the checksum algorithm.The checksum algorithms at both
Type
ends of the IPv6 SCTP links must be the same.

Switch Back Flag Indicates whether to switch back to the primary path when the primary path is
restored. The IPv6 SCTP link switches to the secondary path when the primary
path cannot be reached. This parameter is used to set whether an IPv6 SCTP link
Table 2 Related parameters

Parameter Description

switches back to the primary path when the primary path is restored.

Heart-beat Times When Indicates the number of heartbeats that are detected before transmission
Switch Back
smoothly switches back from the associated secondary path to the primary path.
After the associated primary path is restored, transmission smoothly switches
back from the secondary path to the primary path when the number of detected
successive heartbeats reaches this parameter value.

IPv6 SCTP Link Status Indicates the status of the IPv6 SCTP link.

Status Change Cause Indicates the cause of the latest change of the operational state of an IPv6 SCTP
link from available to unavailable.

Status Change Time Indicates the last time when the operational state of an IPv6 SCTP link changes
from available to unavailable.

Out Stream Number Indicates the number of TX streams negotiated for an IPv6 SCTP link.

In Stream Number Indicates the number of RX streams negotiated for an IPv6 SCTP link.

Work Address Flag Indicates the working address flag of an IPv6 SCTP link.

Block Flag Indicates whether the IPv6 SCTP link is blocked.

Description Info Indicates the peer description information of an IPv6 SCTP link.

Auto Config Flag Indicates whether the object is created by the system. MANUAL_CREATED
means that the object is configured by the user manually. AUTO_CREATED
means that the object is created by the system.

Sack Timeout Indicates the time interval that one end of an SCPT link has to wait before it can
send an SACK message in response to the reception of certain data. A larger
value of this parameter indicates a longer time interval between the reception of
data and the sending of the corresponding SACK message.

5.7.1.6.1.84 SCTPPEER
TRANSPORT
+-SCTPPEER
Description

The SCTPPEER MO is used to configure an SCTP peer. It can be automatically created in the
X2 interface automatic setup scenarios, but needs to be manually configured in other scenarios.
In secure scenarios, if this MO is configured with an IPSec IP address, IPSec negotiation is
automatically performed between the source IP address and the configured IPSec IP address.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the DEVIP,MPGRP,PPPLNK MOs:


- In a routing domain,SIGIP1V4 in an SCTPPEER MO must be different from
IP,LOCALIP or LOCALIP in a configured DEVIP MO,MPGRP and PPPLNK.
- In a routing domain,SIGIP2V4 in an SCTPPEER MO must be different from
IP,LOCALIP or LOCALIP in a configured DEVIP MO,MPGRP and PPPLNK.
Relation with the DEVIP6 MO:
- SIGIP1V6 in an SCTPPEER MO must be different from IPV6 in a configured DEVIP6
MO.
- SIGIP2V6 in an SCTPPEER MO must be different from IPV6 in a configured DEVIP6
MO.
Relation with the SECURITYPEER MO:
- If SIGIP1SECSWITCH and IPVERSION in an SCTPPEER MO are set to ENABLE and
IPv6, respectively, the SECURITYPEER MO whose security peer ID is the same as
SIGIP1SECPEERID in the SCTPPEER MO must meet either of the following conditions: (1)
IPVERSION in the SECURITYPEER MO is set to IPv6. (2) PEERNAME in the
SECURITYPEER MO is the same as PEERNAME in a configured IKEPEER6 MO.
- If SIGIP2SECSWITCH and IPVERSION in an SCTPPEER MO are set to ENABLE and
IPv6, respectively, the SECURITYPEER MO whose security peer ID is the same as
SIGIP2SECPEERID in the SCTPPEER MO must meet either of the following conditions: (1)
IPVERSION in the SECURITYPEER MO is set to IPv6. (2) PEERNAME in the
SECURITYPEER MO is the same as PEERNAME in a configured IKEPEER6 MO.
- In an SCTPPEER MO, if SIGIP1SECSWITCH is set to ENABLE, SIGIP1SECPEERID
must be the same as SECURITYPEERID in a configured SECURITYPEER MO.
- If SIGIP1SECSWITCH and IPVERSION in an SCTPPEER MO are set to ENABLE and
IPv4, respectively, the SECURITYPEER MO whose security peer ID is the same as
SIGIP1SECPEERID in the SCTPPEER MO must meet either of the following conditions: (1)
IPVERSION in the SECURITYPEER MO is set to IPv4. (2) PEERNAME in the
SECURITYPEER MO is the same as PEERNAME in a configured IKEPEER MO.
- In an SCTPPEER MO, if SIGIP2SECSWITCH is set to ENABLE, SIGIP2SECPEERID
must be the same as SECURITYPEERID in a configured SECURITYPEER MO.
- If SIGIP2SECSWITCH and IPVERSION in an SCTPPEER MO are set to ENABLE and
IPv4, respectively, the SECURITYPEER MO whose security peer ID is the same as
SIGIP2SECPEERID in the SCTPPEER MO must meet either of the following conditions: (1)
IPVERSION in the SECURITYPEER MO is set to IPv4. (2) PEERNAME in the
SECURITYPEER MO is the same as PEERNAME in a configured IKEPEER MO.
Relation with the SCTPPEER MO:
- If SIGIP2V6 and SIGIP1SECSWITCH in an SCTPPEER MO are set to 0:0:0:0:0:0:0:0
and DISABLE, respectively, another SCTPPEER MO that has the same combination of
SIGIP1V6 and PN as this SCTPPEER MO cannot be configured.
- If SIGIP2V6 and SIGIP1SECSWITCH in an SCTPPEER MO are set to 0:0:0:0:0:0:0:0
and ENABLE, respectively, another SCTPPEER MO that has the same combination of
SIGIP1V6, PN, and SIGIP1SECPEERID as this SCTPPEER MO cannot be configured.
- If SIGIP2V6 is valid and SIGIP1SECSWITCH and SIGIP2SECSWITCH are both set to
DISABLE in an SCTPPEER MO, another SCTPPEER MO that has the same combination of
SIGIP1V6, PN, and SIGIP2V6 as this SCTPPEER MO cannot be configured.
- If SIGIP2V6 is valid and SIGIP1SECSWITCH and SIGIP2SECSWITCH are both set to
ENABLE in an SCTPPEER MO, another SCTPPEER MO that has the same combination of
SIGIP1V6, SIGIP2V6, PN, SIGIP1SECPEERID, and SIGIP2SECPEERID as this
SCTPPEER MO cannot be configured.
- If SIGIP2V6 is valid and SIGIP1SECSWITCH and SIGIP2SECSWITCH are set to
ENABLE and DISABLE, respectively in an SCTPPEER MO, another SCTPPEER MO that
has the same combination of SIGIP1V6, SIGIP2V6, PN, and SIGIP1SECPEERID as this
SCTPPEER MO cannot be configured.
- If SIGIP2V6 is valid and SIGIP1SECSWITCH and SIGIP2SECSWITCH are set to
DISABLE and ENABLE, respectively in an SCTPPEER MO, another SCTPPEER MO that
has the same combination of SIGIP1V6, SIGIP2V6, PN, and SIGIP2SECPEERID as this
SCTPPEER MO cannot be configured.
- In a routing domain, any two SCTPPEER MOs with IPVERSION set to IPv6 cannot
coexist, if the following condition is met: these two SCTPPEER MOs' PNs are the same, and
one's SIGIP1V6 or SIGIP2V6 is the same with the other's SIGIP1V6 or SIGIP2V6.
- If SIGIP2V4 and SIGIP1SECSWITCH in an SCTPPEER MO are set to 0.0.0.0 and
DISABLE, respectively, another SCTPPEER MO that has the same combination of
VRFIDX,SIGIP1V4 and PN as this SCTPPEER MO cannot be configured.
- If SIGIP2V4 and SIGIP1SECSWITCH in an SCTPPEER MO are set to 0.0.0.0 and
ENABLE, respectively, another SCTPPEER MO that has the same combination of
VRFIDX,SIGIP1V4, PN, and SIGIP1SECPEERID as this SCTPPEER MO cannot be
configured.
- If SIGIP2V4 is valid and SIGIP1SECSWITCH and SIGIP2SECSWITCH are both set to
DISABLE in an SCTPPEER MO, another SCTPPEER MO that has the same combination of
VRFIDX,SIGIP1V4, PN, and SIGIP2V4 as this SCTPPEER MO cannot be configured.
- If SIGIP2V4 is valid and SIGIP1SECSWITCH and SIGIP2SECSWITCH are both set to
ENABLE in an SCTPPEER MO, another SCTPPEER MO that has the same combination of
VRFIDX, SIGIP1V4, SIGIP2V4, PN, SIGIP1SECPEERID, and SIGIP2SECPEERID as this
SCTPPEER MO cannot be configured.
- If SIGIP2V4 is valid and SIGIP1SECSWITCH and SIGIP2SECSWITCH are set to
ENABLE and DISABLE, respectively in an SCTPPEER MO, another SCTPPEER MO that
has the same combination of VRFIDX, SIGIP1V4, SIGIP2V4, PN, and SIGIP1SECPEERID
as this SCTPPEER MO cannot be configured.
- If SIGIP2V4 is valid and SIGIP1SECSWITCH and SIGIP2SECSWITCH are set to
DISABLE and ENABLE, respectively in an SCTPPEER MO, another SCTPPEER MO that
has the same combination of VRFIDX, SIGIP1V4, SIGIP2V4, PN, and SIGIP2SECPEERID
as this SCTPPEER MO cannot be configured.
- In a routing domain, any two SCTPPEER MOs with IPVERSION set to IPv4 cannot
coexist, if the following condition is met: these two SCTPPEER MOs' PNs are the same, and
one's SIGIP1V4 or SIGIP2V4 is the same with the other's SIGIP1V4 or SIGIP2V4.
Relation with the EPGROUP MO:
- SCTPPEERID referenced by SCTPPEERREFS in an EPGROUP MO must be the same
as SCTPPEERID in a configured SCTPPEER MO.
Relation with the VRF MO:
- The VRF instance used by a SCTPPEER MO must have been configured.
Relation with the EPGROUP,SCTPHOST MOs:
- In a routing domain IPv6 configuration,if there are SCTPHOST MOs configured in different
EPGROUP which PNs are the same, and one's SIGIP1V6 or SIGIP2V6 is the same with the
other's SIGIP1V6 or SIGIP2V6,the same SCTPPEER MO is only allowed to be configured in
one of these EPGROUP MO.
- In a routing domain IPv4 configuration,if there are SCTPHOST MOs configured in different
EPGROUP which PNs are the same, and one's SIGIP1V4 or SIGIP2V4 is the same with the
other's SIGIP1V4 or SIGIP2V4,the same SCTPPEER MO is only allowed to be configured in
one of these EPGROUP MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD SCTPPEER Use this command to add an SCTP peer.

LST SCTPPEER Use this command to list the configuration of SCTP peers and whether the
object is created by the system. When the AUTOCFGFLAG is
MANUAL_CREATED, it means that the object is configured by the user
manually. AUTO_CREATED means that the object is created by the system.

MOD SCTPPEER Use this command to modify an SCTP peer.

RMV SCTPPEER Use this command to remove an SCTP peer.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

SCTP Peer ID Indicates the ID of the SCTP peer.

VRF Index Indicates the index of the virtual route and forwarding(VRF) instance.

IP Version Indicates the version of the peer IP address of an SCTP link.

First Peer IP Address Indicates the first IPv4 address of the peer end, which is used in automatic setup
of a Stream Control Transmission Protocol (SCTP) link.

First Peer IPv6 Address Indicates the first IPv6 address of the sctp peer, which is used for automatically
setting up a Stream Control Transmission Protocol (SCTP) link.

IPSec Switch for First Indicates whether to enable automatic setup of an IPSec tunnel between the local
Peer IP
end and the peer end based on the SECURITYHOST and SECURITYPEER
MOs. The IPSec tunnel is used to encrypt the data to be transmitted on the
Stream Control Transmission Protocol (SCTP) link that is set up using the first
IP address of the sctp peer or the data to be transmitted on the IPv6 SCTP link
that is set up using the first IPv6 address of the sctp peer.

Security Peer ID for Indicates the ID of the security peer referenced by the first IP address of the
First Peer IP
SCTP peer.
Table 2 Related parameters

Parameter Description

Second Peer IP Indicates the second IP address of the sctp peer, which is used for automatically
Address
setting up a Stream Control Transmission Protocol (SCTP) link.

Second Peer IPv6 Indicates the second IPv6 address of the sctp peer, which is used for
Address
automatically setting up a Stream Control Transmission Protocol (SCTP) link.

IPSec Switch for Indicates whether to enable automatic setup of an IPSec tunnel between the local
Second Peer IP
end and the peer end based on the SECURITYHOST and SECURITYPEER
MOs. The IPSec tunnel is used to encrypt the data to be transmitted on the
Stream Control Transmission Protocol (SCTP) link that is set up using the
second IP address of the sctp peer or the data to be transmitted on the IPv6
SCTP link that is set up using the second IPv6 address of the sctp peer.

Security Peer ID for Indicates the ID of the security peer referenced by the second IP address of the
Second Peer IP
SCTP peer.

Peer SCTP Port No. Indicates the number of the peer SCTP port, which is used in automatic setup of
a Stream Control Transmission Protocol (SCTP) link.

Remote ID This parameter indicates the remote ID and takes effect only in the SCTPPEER
MO that is automatically created during X2 self-setup. This parameter is
automatically configured during X2 self-setup and is used to identify the peer
eNodeB. The parameter value is displayed as follows: eNB:MCC_'The MCC of
the serving operator on the local eNodeB' MNC_'The MNC of the serving
operator on the local eNodeB' GlobaleNBId_'The global MCC of the peer
eNodeB'-'The global MNC of the peer eNodeB'-'The peer eNodeB ID'.

Control Mode Indicates whether the object can be modified or deleted by the system. The value
MANUAL_MODE means that only the user can modify or delete the object.
The value AUTO_MODE means that both the system and the user can modify or
delete the object.

Auto Config Flag Indicates whether the object is created by the system. MANUAL_CREATED
means that the object is configured by the user manually. AUTO_CREATED
means that the object is created by the system.

User Label Indicates the description of the SCTP peer.

5.7.1.6.1.85 SCTPTEMPLATE
TRANSPORT
+-SCTPTEMPLATE

Description

The SCTPTEMPLATE MO is used to configure the parameters for automatically setting up an


SCTP link. This MO can be quoted by multiple SCTP hosts.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the SCTPHOST MO:


- SCTPTEMPLATEID in an SCTPHOST MO must be the same as SCTPTEMPLATEID
in a configured SCTPTEMPLATE MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD SCTPTEMPLATE Use this command to add an SCTP parameter template.

LST SCTPTEMPLATE Use this command to list the configuration of an SCTP parameter template.

MOD SCTPTEMPLATE Use this command to modify an SCTP parameter template.

RMV SCTPTEMPLATE Use this command to remove an SCTP parameter template.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

SCTP Parameters Indicates the ID of the SCTP parameter template.


Template ID

RTO Min Value Indicates the minimum value of the retransmission timeout (RTO). According to
the SCTP protocol, if the calculated RTO is less than this parameter value, the
round trip delay is set to this parameter value to reduce the probability of
retransmission timeout.

RTO Max Value Indicates the maximum value of the retransmission timeout (RTO). According to
the SCTP protocol, it is the upper limit for the doubling operation of the
retransmission timeout timer.

RTO Initial Value Indicates the initial value of the Retransmission TimeOut (RTO). It is used as the
initial value when calculating the retransmission timeout in the SCTP protocol.

RTO Alpha Value Indicates the alpha value related to RTO of the SCTP link. The larger the
parameter value, the more insensitive services to the link delay. For details about
the RtoAlpha parameter, see RFC4960. The parameter value is used as smooth
factor for calculating the round-trip delay in the SCTP protocol. In a new
estimation, (RtoAlpha/100) is obtained based on a new measurement and 1-
(RtoAlpha/100) is obtained based on the last estimation.

RTO Beta Value Indicates the beta value related to RTO of the SCTP link. This parameter is used
to calculate the Round Trip Time Variation (RTTVAR). A larger value indicates
that the latest change is more important. For definitions of the beta value, see
RFC4960.

Heart-beat Interval Indicates the heartbeat interval, corresponding to the HBINTER parameter
specified in RFC4960. SCTP periodically transmits heartbeat messages to an
idle destination address to detect the reachability. According to RFC4960, the
actual interval at which heartbeat messages are transmitted equals the parameter
value (HBINTER) plus the retransmission timeout (RTO).

Max Association Indicates the maximum number of retransmissions on the SCTP link. If the
Retransmission
number of retransmissions on the SCTP link reaches this parameter value, this
SCTP link is considered broken and the eNodeB reports a link failure alarm.

Max Path Indicates the maximum number of retransmissions over a path. When the
Retransmission
number of retransmissions over a path exceeds the value of this parameter, the
path is regarded as failed if no heartbeat acknowledgment is received. If multiple
paths are used, path switching is automatically performed.

Switch Back Flag Indicates whether to switch back to the primary path upon restoration of the
primary path. If the primary path is unavailable, the SCTP link will be switched
to the secondary path. When this parameter is set to ENABLE and the primary
Table 2 Related parameters

Parameter Description

path is restored, the SCTP link will be switched to the primary path. When this
parameter is set to DISABLE and the primary path is restored, the SCTP link
will not be switched to the primary path.

Heart-beat Times When Indicates the number of consecutive heartbeat messages that must be transmitted
Switch Back
on the primary path before the system can switch back to the primary path when
SWITCHBACKFLAG is set to ENABLE.

SACK Timeout Indicates the time interval that one end of SCPT link has to wait before it can
send an SACK message in response to data reception. A larger value of this
parameter indicates a longer time interval between the reception of data and the
sending of the corresponding SACK message.

Checksum Arithmetic Indicates the type of the checksum algorithm. The checksum algorithms at both
Type
ends of SCTP links must be the same.

Maximum Stream No. Indicates the maximum stream number of an SCTP link.

5.7.1.6.1.86 SECURITYHOST
TRANSPORT
+-SECURITYHOST

Description

The SECURITYHOST MO is used to configure the parameters related to a security host. This
MO can be quoted by multiple SCTP hosts or user-plane hosts for configuration of their security
attributes.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the SECURITYTEMPLATE MO:


- SECURITYTEMPLATEID in a SECURITYHOST MO must be the same as
SECURITYTEMPLATEID in a configured SECURITYTEMPLATE MO.
- SEGWSWITCH in a SECURITYHOST MO must be the same as SEGWSWITCH in the
referenced SECURITYTEMPLATE MO.
Relation with the DEVIP MO:
- LOCIKEIPV4 in a SECURITYHOST MO must be the same as IP in a configured DEVIP
MO.
Relation with the DEVIP6 MO:
- LOCIKEIPV6 in a SECURITYHOST MO must be the same as IPV6 in a configured
DEVIP6 MO.
Relation with the SECURITYHOST MO:
- PT in an IPITF6 MO referenced by LOCIKEIPV6 in a SECURITYHOST MO must be
set to ETH or TRUNK.
- PT in a DEVIP MO referenced by LOCIKEIPV4 in a SECURITYHOST MO must be set
to ETH or ETHTRK.
Relation with the IKEPEER MO:
- In a SECURITYHOST MO, if IPVERSION and SEGWCONFIGMODE are set to IPv4
and SEGW_CONFIG_ON_HOST, respectively, PEERNAME must be the same as
PEERNAME in a configured IKEPEER MO.
Relation with the IKEPEER6 MO:
- In a SECURITYHOST MO, if IPVERSION and SEGWCONFIGMODE are set to IPv6
and SEGW_CONFIG_ON_HOST, respectively, PEERNAME must be the same as
PEERNAME in a configured IKEPEER6 MO.
Relation with the IPSECPROPOSAL MO:
- In a SECURITYHOST MO, if SEGWCONFIGMODE is set to
SEGW_CONFIG_ON_HOST, IPSECPROPNAME must be the same as PROPNAME in a
configured IPSECPROPOSAL MO.
Relation with the SCTPHOST MO:
- In an SCTPHOST MO, if SIGIP1SECSWITCH is set to ENABLE, SIGIP1SECHOSTID
must be the same as SECURITYHOSTID in a configured SECURITYHOST MO.
- In an SCTPHOST MO, if SIGIP1SECSWITCH is set to ENABLE, IPVERSION must be
the same as IPVERSION in a referenced SECURITYHOST MO.
- In an SCTPHOST MO, if SIGIP2SECSWITCH is set to ENABLE, SIGIP2SECHOSTID
must be the same as SECURITYHOSTID in a configured SECURITYHOST MO.
- In an SCTPHOST MO, if SIGIP2SECSWITCH is set to ENABLE, IPVERSION must be
the same as IPVERSION in a referenced SECURITYHOST MO.
- If PT in a DEVIP MO referenced by SIGIP1V4 in an SCTPHOST MO is not set to
LOOPINT, SIGIP1V4 in the SCTPHOST MO must be configured on the same physical port as
LOCIKEIPV4 in a referenced SECURITYHOST MO.
- If PT in a DEVIP MO referenced by SIGIP2V4 in an SCTPHOST MO is not set to
LOOPINT, SIGIP2V4 in the SCTPHOST MO must be configured on the same physical port as
LOCIKEIPV4 in a referenced SECURITYHOST MO.
- If PT in an IPITF6 MO referenced by SIGIP1V6 in an SCTPHOST MO is not set to
LOOPINT, SIGIP1V6 in the SCTPHOST MO must be configured on the same physical port as
LOCIKEIPV6 in a referenced SECURITYHOST MO.
- If PT in an IPITF6 MO referenced by SIGIP2V6 in an SCTPHOST MO is not set to
LOOPINT, SIGIP2V6 in the SCTPHOST MO must be configured on the same physical port as
LOCIKEIPV6 in a referenced SECURITYHOST MO.
- In a SCTPHOST MO, if SIGIP1SECSWITCH is set to ENABLE, SIGIP1V4 and
LOCIKEIPV4 of SECURITYHOST referenced by this SCTPHOST MO must be on the same
board.
- In a SCTPHOST MO, if SIGIP2SECSWITCH is set to ENABLE, SIGIP2V4 and
LOCIKEIPV4 of SECURITYHOST referenced by this SCTPHOST MO must be on the same
board.
- In a SCTPHOST MO, if SIGIP1SECSWITCH is set to ENABLE, SIGIP1V6 and
LOCIKEIPV6 of SECURITYHOST referenced by this SCTPHOST MO must be on the same
board.
- In a SCTPHOST MO, if SIGIP2SECSWITCH is set to ENABLE, SIGIP2V6 and
LOCIKEIPV6 of SECURITYHOST referenced by this SCTPHOST MO must be on the same
board.
Relation with the USERPLANEHOST MO:
- In a USERPLANEHOST MO, if IPSECSWITCH is set to ENABLE, SECHOSTID must
be the same as SECURITYHOSTID in a configured SECURITYHOST MO.
- In a USERPLANEHOST MO, if IPSECSWITCH is set to ENABLE, IPVERSION must
be the same as IPVERSION in a referenced SECURITYHOST MO.
- If PT in an IPITF6 MO referenced by LOCIPV6 in a USERPLANEHOST MO is not set
to LOOPINT, LOCIPV6 in the USERPLANEHOST MO must be configured on the same
physical port as LOCIKEIPV6 in a referenced SECURITYHOST MO.
- In an USERPLANEHOST MO, if IPSECSWITCH is set to ENABLE, LOCIPV6 and
LOCIKEIPV6 of SECURITYHOST referenced by this USERPLANEHOST MO must be on
the same board.
- If PT in a DEVIP MO referenced by LOCIPV4 in a USERPLANEHOST MO is not set to
LOOPINT, LOCIPV4 in the USERPLANEHOST MO must be configured on the same
physical port as LOCIKEIPV4 in a referenced SECURITYHOST MO.
- In a USERPLANEHOST MO, if IPSECSWITCH is set to ENABLE, LOCIPV4 and
LOCIKEIPV4 of SECURITYHOST referenced by this USERPLANEHOST MO must be on
the same board.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD SECURITYHOST Use this command to add the security hosts required by secure automatic
establishment.

LST SECURITYHOST Use this command to list the configuration of security hosts.

MOD SECURITYHOST Use this command to modify the configuration of security hosts.

RMV SECURITYHOST Use this command to remove a security host.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Security Host ID Indicates the security host ID.

SeGW Switch Indicates whether to enable the peer end to perform IPSec negotiation with the
local end through an SeGW. When this parameter is set to DISABLE, the peer
end performs IPSec negotiation with the local end directly. When this parameter
is set to ENABLE, the peer end establishes an IPSec tunnel to the peer end
through a SeGW.

SeGW Config Mode Indicates the configuration mode of the security gateway.

IP Version Indicates the version of the security host IP address.

Local IKE IP Address This parameter is used to designate the physical port of the IPSec Policy Group
Binding.
Table 2 Related parameters

Parameter Description

Local IKE IPv6 Address This parameter is used to designate the physical port of the IPv6 IPSec Policy
Group Binding. This parameter takes effect only in LTE.

IKE Peer Name Indicates the name of the IKE peer.

IPSec Proposal Name Indicates the name of the IPSec proposal used for IPSec negotiation between the
local end and the security gateway (SeGW).

Security Parameters Indicates the ID of the security parameter template referenced by the security
Template ID
host.

User Label Indicates the description of the security host.

5.7.1.6.1.87 SECURITYPEER
TRANSPORT
+-SECURITYPEER

Description

The SECURITYPEER MO is used to configure the parameters related to a security peer. This
MO can be quoted by multiple SCTP peers or user-plane peers for configuration of their security
attributes.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the USERPLANEPEER MO:


- If IPSECSWITCH and IPVERSION in a USERPLANEPEER MO are set to ENABLE
and IPv6, respectively, the SECURITYPEER MO whose security peer ID is the same as
SECPEERID in the USERPLANEPEER MO must meet either of the following conditions: (1)
IPVERSION in the USERPLANEPEER MO is set to IPv6. (2) PEERNAME in the
SECURITYPEER MO is the same as PEERNAME in an IKEPEER6 MO.
- In a USERPLANEPEER MO, if IPSECSWITCH is set to ENABLE, SECPEERID must
be the same as SECURITYPEERID in a configured SECURITYPEER MO.
- If IPSECSWITCH and IPVERSION in a USERPLANEPEER MO are set to ENABLE
and IPv4, respectively, the SECURITYPEER MO whose security peer ID is the same as
SECPEERID in the USERPLANEPEER MO must meet either of the following conditions: (1)
IPVERSION in the USERPLANEPEER MO is set to IPv4. (2) PEERNAME in the
SECURITYPEER MO is the same as PEERNAME in an IKEPEER MO.
Relation with the DEVIP MO:
- PEERIKEIPV4 in a SECURITYPEER MO must be different from IP,LOCALIP or
LOCALIP in a configured DEVIP MO,MPGRP and PPPLNK.
Relation with the DEVIP6 MO:
- PEERIKEIPV6 in a SECURITYPEER MO must be different from IPV6 in a configured
DEVIP6 MO.
Relation with the SECURITYPEER MO:
- Each SECURITYPEER MO must have a unique PEERIKEIPV6 value.
- Each SECURITYPEER MO must have a unique PEERIKEIPV4 value.
Relation with the IKEPEER,IKEPEER6 MOs:
- In a SECURITYPEER MO, if SEGWSWITCH is set to ENABLE, PEERNAME must be
the same as PEERNAME in a configured IKEPEER MO or PEERNAME in a configured
IKEPEER6 MO.
Relation with the IPSECPROPOSAL MO:
- In a SECURITYPEER MO, if SEGWSWITCH is set to ENABLE, IPSECPROPNAME
must be the same as PROPNAME in a configured IPSECPROPOSAL MO.
Relation with the SCTPPEER MO:
- In an SCTPPEER MO, if SIGIP1SECSWITCH is set to ENABLE, SIGIP1SECPEERID
must be the same as SECURITYPEERID in a configured SECURITYPEER MO.
- If SIGIP1SECSWITCH and IPVERSION in an SCTPPEER MO are set to ENABLE and
IPv4, respectively, the SECURITYPEER MO whose security peer ID is the same as
SIGIP1SECPEERID in the SCTPPEER MO must meet either of the following conditions: (1)
IPVERSION in the SECURITYPEER MO is set to IPv4. (2) PEERNAME in the
SECURITYPEER MO is the same as PEERNAME in a configured IKEPEER MO.
- In an SCTPPEER MO, if SIGIP2SECSWITCH is set to ENABLE, SIGIP2SECPEERID
must be the same as SECURITYPEERID in a configured SECURITYPEER MO.
- If SIGIP2SECSWITCH and IPVERSION in an SCTPPEER MO are set to ENABLE and
IPv4, respectively, the SECURITYPEER MO whose security peer ID is the same as
SIGIP2SECPEERID in the SCTPPEER MO must meet either of the following conditions: (1)
IPVERSION in the SECURITYPEER MO is set to IPv4. (2) PEERNAME in the
SECURITYPEER MO is the same as PEERNAME in a configured IKEPEER MO.
- If SIGIP1SECSWITCH and IPVERSION in an SCTPPEER MO are set to ENABLE and
IPv6, respectively, the SECURITYPEER MO whose security peer ID is the same as
SIGIP1SECPEERID in the SCTPPEER MO must meet either of the following conditions: (1)
IPVERSION in the SECURITYPEER MO is set to IPv6. (2) PEERNAME in the
SECURITYPEER MO is the same as PEERNAME in a configured IKEPEER6 MO.
- If SIGIP2SECSWITCH and IPVERSION in an SCTPPEER MO are set to ENABLE and
IPv6, respectively, the SECURITYPEER MO whose security peer ID is the same as
SIGIP2SECPEERID in the SCTPPEER MO must meet either of the following conditions: (1)
IPVERSION in the SECURITYPEER MO is set to IPv6. (2) PEERNAME in the
SECURITYPEER MO is the same as PEERNAME in a configured IKEPEER6 MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD SECURITYPEER Use this command to add the security peers required by secure automatic
establishment.

LST SECURITYPEER Use this command to list the configuration of security peers and whether the
object is created by the system. When the AUTOCFGFLAG is
MANUAL_CREATED, it means that the object is configured by the user
manually. AUTO_CREATED means that the object is created by the system.

MOD SECURITYPEER Use this command to modify a security peer.

RMV SECURITYPEER Use this command to remove a security peer.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Security Peer ID Indicates the ID of a security peer.


Table 2 Related parameters

Parameter Description

SeGW Switch Indicates whether to enable the peer end to perform IPSec negotiation with the
local end through an SeGW. When this parameter is set to DISABLE, the peer
end performs IPSec negotiation with the local end directly. When this parameter
is set to ENABLE, the peer end establishes an IPSec tunnel to the local end
through the SeGW.

IP Version Indicates the version of the security peer IP address.

Peer IKE IP Address Indicates the IPv4 address of the IKE peer.

Peer IKE IPv6 Address Indicates the IPv6 address of the IKE peer that corresponds to a service IP
address. This parameter takes effect only in LTE.

IKE Peer Name Indicates the name of the IKE peer. The IKE peer is the security gateway that
performs IKE negotiation with the local end.

IPSec Proposal Name Indicates the name of the IPSec proposal used for IPSec negotiation between the
local end and the security gateway (SeGW).

Control Mode Indicates whether the object can be modified or deleted by the system. The value
MANUAL_MODE means that only the user can modify or delete the object.
The value AUTO_MODE means that both the system and the user can modify or
delete the object.

User Label Indicates the description of a security peer.

Auto Config Flag Indicates whether the object is created by the system. MANUAL_CREATED
means that the object is configured by the user manually. AUTO_CREATED
means that the object is created by the system.

5.7.1.6.1.88 SECURITYTEMPLATE
TRANSPORT
+-SECURITYTEMPLATE

Description

The SECURITYTEMPLATE MO is used to configure the parameters for automatically setting


up security channels. This MO can be quoted by multiple SCTP hosts.
Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the IKEPROPOSAL MO:


- In a SECURITYTEMPLATE MO, if SEGWSWITCH is set to DISABLE, PROPID must
be the same as PROPID in a configured IKEPROPOSAL MO.
- If AUTHALG in an IKEPROPOSAL MO is set to AES_XCBC_96, IKEVERSION in a
SECURITYTEMPLATE MO cannot be set to IKE_V1.
- If AUTHMETH in the IKEPROPOSAL MO on which a SECURITYTEMPLATE MO
depends is set to PRE_SHARED_KEY, PKEY in the SECURITYTEMPLATE MO must be
specified.
Relation with the IPSECPROPOSAL MO:
- In a SECURITYTEMPLATE MO, if SEGWSWITCH is set to DISABLE,
IPSECPROPNAME must be the same as PROPNAME in a configured IPSECPROPOSAL
MO.
Relation with the SECURITYHOST MO:
- SECURITYTEMPLATEID in a SECURITYHOST MO must be the same as
SECURITYTEMPLATEID in a configured SECURITYTEMPLATE MO.
- SEGWSWITCH in a SECURITYHOST MO must be the same as SEGWSWITCH in the
referenced SECURITYTEMPLATE MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add a security parameter template.


SECURITYTEMPLATE

LST Use this command to list the configuration of a security parameter template.
SECURITYTEMPLATE

MOD Use this command to modify a security parameter template.


SECURITYTEMPLATE
Table 1 Related MML commands

MML Command Function

RMV Use this command to remove a security parameter template.


SECURITYTEMPLATE

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Security Parameters Indicates the ID of the security parameter template.


Template ID

SeGW Switch Indicates whether to enable the peer end to perform IPSec negotiation with the
local end through an SeGW. When this parameter is set to DISABLE, the peer
end performs IPSec negotiation with the local end directly. When this parameter
is set to ENABLE, the peer end establishes an IPSec tunnel to the local end
through the SeGW.

IKE Proposal ID Indicates the ID of the IKE proposal.

IPSec Proposal Name Indicates the name of the IPSec proposal.

IKE Version Indicates the IKE protocol version.

Exchange Mode Indicates the IKE V1 exchange mode. There are two exchange modes: main
mode and aggressive mode. In main mode, keys are exchanged separately from
identity information, which protects identity information and hence enhances
security. In aggressive mode, identity information is not protected, but
requirements of specific network environments can be met.

Pre-shared Key Indicates the preshared key. Both ends must use the same preshared key in
negotiation.

DPD Mode Indicates whether to enable the dead peer detection (DPD) function. When this
parameter is set to DISABLE, the local end does not perform DPD. When this
parameter is set to PERIODIC, the local end periodically sends DPD packets to
perform DPD if the total time during which the local end does not receive
encrypted packets reaches the value specified by the DPD Idle Time parameter.

DPD Idle Time Indicates the dead peer detection (DPD) idle time. If the local end does not
receive encrypted packets for a time defined by this parameter, it sends a DPD
Table 2 Related parameters

Parameter Description

message to perform dead peer detection. However, the exact time at which the
eNodeB sends DPD messages varies depending on network environment.

DPD Retransmission Indicates the interval at which the eNodeB sends DPD frames. However, the
Interval
exact interval at which the eNodeB sends DPD frames varies depending on
network environment.

DPD Retransmission Indicates the maximum allowed number of DPD frame retransmissions after a
Count
dead peer detection (DPD) failure.

Perfect Forward Indicates the perfect forward secrecy (PFS) value.


Security
In the second phase of IPSec negotiation, PFS enables the system to use a key
that is not derived from the first-phase key. Therefore, the two keys are
independent of each other. According to PFS, each key protects a unique set of
data. The elements used to generate a key cannot be reused, preventing the
disclosure of a key from affecting security of other keys.
If the parameter is set to PFS_GROUP1 or PFS_GROUP2 at the local end, the
peer end must launch a PFS exchange when initiating IPSec negotiation. In this
situation, both ends must use the same Diffie-Hellman (DH) group to calculate
the key; otherwise, negotiation fails. Compared with the 768-bit DH group (DH
group 1), the 1024-bit DH group (DH group 2) provides a higher security level
but requires longer calculation time.

SA Duration Mode Indicates the configuration mode of the IPSec SA's life cycle. This parameter
can be set to GLOBAL or LOCAL. The value GLOBAL means that this life
cycle applies to all IPSec SAs of the system, while the value LOCAL means that
this life cycle applies only to the IPSec SAs generated using the IPSec proposal
specified in the same MO.

Lifetime Based On Time Indicates the life cycle of an IPSec SA. An IPSec SA becomes invalid when its
life cycle elapses. Before an IPSec SA becomes invalid, IKE establishes a new
IPSec SA based on negotiation. Before a new IPSec SA is established, the old
IPSec SA is still used to ensure communication security. Once the negotiation is
complete, the new IPSec SA is immediately used. IPSec SA negotiation takes a
period of time. To prevent SA update from affecting communication security, a
life cycle longer than 900 seconds is recommended.

Lifetime Based On Indicates the traffic volume threshold for the IPSec policy, above which
Traffic
negotiation for a new IPSec SA is started. The value 0 indicates that the
function, which initiates negotiation for a new IPSec SA based on the traffic
volume, is disabled. But when BS acts as initiator in IKEv1 and this value is set
to 0, if the responder insists or enforces the IPSec SA traffic lifetime to BS, BS
will enable this function to avoid service break down.
Table 2 Related parameters

Parameter Description

Anti-Replay Window Indicates the size of the IPSec packet anti-replay window. If the value of this
Size
parameter is set to 0, the IPSec packet anti-replay function is disabled. If the
value of this parameter is set to 32, 64, 128, 256, 512, 1024, 2048 or 4096, the
system checks whether the packets are duplicate in the window. A packet is
discarded if it has a duplicate packet or its sequence number is smaller than any
packet in the window. The window slides if the sequence number of the packet
is larger than any packet that is received in the window.

5.7.1.6.1.89 SUBIF
TRANSPORT
+-SUBIF

Description

The SUBIF MO is the subinterface associating the virtual routing and forwarding (VRF) and
Ethernet Like interface. The Ethernet Like interface includes the Ethernet port and Ethernet
trunk.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the ETHTRK MO:


- If PT in a SUBIF MO is set to ETHTRK, the corresponding ETHTRK MO must have been
configured.
Relation with the VRF MO:
- The VRF instance used by a SUBIF MO must have been configured.
Relation with the PPPLNK MO:
- A PPPLNK MO and a SUBIF MO cannot both be configured.
Relation with the MPGRP MO:
- An MPGRP MO and a SUBIF MO cannot both be configured.
Relation with the TUNNEL MO:
- A TUNNEL MO and a SUBIF MO cannot both be configured.
Relation with the VLANCLASS MO:
- A VLANCLASS MO and a SUBIF MO cannot both be configured.
Relation with the VLANMAP MO:
- If an SUBIF MO has been configured, VLANMODE in the VLANMAP MO must not be
set to VLANGROUP.
Relation with the ETHTRKLNK MO:
- If PT in a SUBIF MO is set to ETH, and the corresponding ETHPORT MO has joined an
ETHTRK MO, the SUBIF MO cannot be added.
Relation with the PORTSECURITY MO:
- An ETHPORT MO on which a SUBIF MO depends must meet either of the following
conditions: (1) The corresponding PORTSECURITY MO is not configured. (2) The
corresponding PORTSECURITY MO has been configured, and its SWITCH is set to
ENABLE.
Relation with the HAGRP MO:
- In one logical protection group, SN in an HAGRP MO must be the same as SN in a SUBIF
MO.
Relation with the DEVIP MO:
- If PT in a DEVIP MO is set to SUBIF, the SUBIF MO that uses the same VRF instance as
the DEVIP MO must have been configured.
- If PT in a DEVIP MO is not set to SUBIF or LOOPINT, the SUBIF MO cannot be
configured.
Relation with the PACKETFILTER MO:
- If PT in a PACKETFILTER MO is set to SUBIF, the corresponding SUBIF MO must have
been configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD SUBIF User this command to add a sub-interface.


Table 1 Related MML commands

MML Command Function

LST SUBIF Use this command to list the configuration of a sub-interface.

RMV SUBIF User this command to remove a sub-interface.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the board where the sub-interface is located.

Subrack No. Indicates the subrack number of the board where the sub-interface is located.

Slot No. Indicates the slot number of the board where the sub-interface is located.

Subboard Type Indicates the subboard type of the board where the sub-interface is located.

Sub-interface No. Indicates the number of the sub-interface.

Port Type Indicates the port type.

Port No. Indicates the port number.

VRF Index Indicates the index of the virtual route and forwarding(VRF).

ARP Proxy Indicates whether to enable the proxy ARP function.

5.7.1.6.1.90 SUBNETVLAN
TRANSPORT
+-SUBNETVLAN

Description
A SUBNETVLAN MO defines the mapping between an IP address and a VLAN ID.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the SUBNETVLAN MO:


- A VLANMAP MO cannot be configured together with a SUBNETVLAN MO on a BS.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD SUBNETVLAN Use this command to add a subnet VLAN mapping relationship.

LST SUBNETVLAN Use this command to list the parameters of the subnet VLAN mapping
relationship.

MOD SUBNETVLAN Use this command to modify the parameters related to a subnet VLAN mapping.

RMV SUBNETVLAN Use this command to remove a subnet VLAN mapping relationship.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

IP Address Indicates the source IP address used for mapping the VLAN.

Mask Indicates the subnet mask of the source IP address used for mapping the VLAN.
Table 2 Related parameters

Parameter Description

VLAN ID Indicates the VLAN ID in the VLAN tag.

5.7.1.6.1.91 TACALG
TRANSPORT
+-TACALG

Description

The TACALG MO consists of the parameters related to the admission control algorithm. When a
service requests admission, the BS allocates a certain amount of resources to the service based on
the load on the resource group and the admission threshold for this type of service. By
implementing admission control, the bandwidth for admitted services is provisioned, and the
service quality of each admitted service and the admission success rate of high-priority users are
both guaranteed.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST TACALG Use this command to list the settings of the admission control algorithm.

SET TACALG Use this command to set the parameters of the admission control algorithm.
Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Resource Group Uplink Indicates the switch that is used to control whether to apply UL admission
Admission Control
Algorithm Switch control to a resource group.

Resource Group Indicates the switch that is used to control whether to apply DL admission
Downlink Admission
Control Algorithm control to a resource group.
Switch

Uplink Handover Indicates the UL admission threshold for handed-over services. A large value of
Service Admission
Threshold this parameter will result in a high UL admission success rate of handed-over
services.

Downlink Handover Indicates the DL admission threshold for handed-over services. A large value of
Service Admission
Threshold this parameter will result in a high DL admission success rate of handed-over
services.

Uplink Golden New Indicates the UL admission threshold for new Gold-level services. A large value
Service Admission
Threshold of this parameter will result in a high UL admission success rate of new Gold-
level services.

Downlink Golden New Indicates the DL admission threshold for new Gold-level services. A large value
Service Admission
Threshold of this parameter will result in a high DL admission success rate of new Gold-
level services.

Uplink Silver New Indicates the UL admission threshold for new Silver-level services. A large value
Service Admission
Threshold of this parameter will result in a high UL admission success rate of new Silver-
level services.

Downlink Silver New Indicates the DL admission threshold for new Silver-level services. A large value
Service Admission
Threshold of this parameter will result in a high DL admission success rate of new Silver-
level services.

Uplink Bronze New Indicates the UL admission threshold for new Copper-level services. A large
Service Admission
Threshold value of this parameter will results in a high UL admission success rate of new
Copper-level services.

Downlink Bronze New Indicates the DL admission threshold for new Copper-level services. A large
Service Admission
Threshold value of this parameter will result in a high DL admission success rate of new
Copper-level services.
Table 2 Related parameters

Parameter Description

Uplink GBR Service Indicates the uplink transport admission threshold for the Guaranteed the Bit
Admission Threshold
Rate (GBR) service. A large value of this parameter will result in a high UL
admission success rate of GBR services.

Downlink GBR Service Indicates the DL admission threshold for the guaranteed bit rate (GBR) service.
Admission Threshold
A large value of this parameter will result in a high DL admission success rate of
GBR services.

Uplink Pre-emption Indicates the switch that is used to control whether to enable the UL pre-emption
Algorithm Switch
algorithm. If this parameter is set to ON, the UL pre-emption algorithm is
enabled. In this case, the service with a higher priority that requests admission
may pre-empt the resources of admitted services with lower priorities when UL
transmission bandwidth is insufficient. If this parameter is set to OFF, the UL
pre-emption algorithm is disabled. In this case, services with higher priorities
that request admission cannot pre-empt the resources of admitted services with
lower priorities when UL transmission bandwidth is insufficient.

Downlink Pre-emption Indicates the switch that is used to control whether to enable the DL pre-emption
Algorithm Switch
algorithm. If this parameter is set to ON, the DL pre-emption algorithm is
enabled. In this case, the service with a higher priority that requests admission
can pre-empt the resources of admitted services with lower priorities when DL
transmission bandwidth is insufficient. If this parameter is set to OFF, the DL
pre-emption algorithm is disabled. In this case, services with higher priorities
that request admission cannot pre-empt the resources of admitted services with
lower priorities when DL transmission bandwidth is insufficient.

Physical Port Up Link Indicates the switch that is used to control whether to enable UL overbooking
OverBooking Switch
admission control. It is used to determine the admission bandwidth of the
resource group and facilitate admission control.

Physical Port Down Indicates the switch that is used to control whether to enable DL overbooking
Link OverBooking
Switch admission control. It is used to determine the admission bandwidth of the
resource group and facilitate admission control.

Physical Port Up Link Indicates the switch that is used to control whether to apply UL admission
Admission Switch
control to a physical port. If this parameter is set to ON, UL admission control is
applied to the physical port. If this parameter is set to OFF, UL admission
control is not applied to the physical port.

Physical Port Down Indicates the switch that is used to control whether to apply DL admission
Link Admission Switch
control to a physical port. If this parameter is set to ON, DL admission control is
applied to the physical port. If this parameter is set to OFF, DL admission
control is not applied to the physical port.
5.7.1.6.1.92 TLDRALG
TRANSPORT
+-TLDRALG

Description

This MO describes the parameters required of the traffic payload threshold of the eNodeB.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST TLDRALG Use this command to list the configuration of the traffic load threshold.

SET TLDRALG Use this command to set the parameters of the traffic load threshold.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Uplink High Load Indicates the threshold for triggering the UL high load. If the ratio of the UL
Trigger Threshold
transport load to the UL transport bandwidth of the BS keeps above this
threshold for a period of hysteresis, the UL transport load of the BS enters the
Table 2 Related parameters

Parameter Description

high-load state. In UL high-load state, the BS sends a UL S1 TNL Load


Indicator, which is set to HighLoad, to each neighboring BS through the X2
interface.

Downlink High Load Indicates the threshold for triggering the DL high load. If the ratio of the DL
Trigger Threshold
transport load to the DL transport bandwidth of the BS keeps above this
threshold for a period of hysteresis, the DL transport load of the BS enters the
high-load state. In DL high-load state, the BS sends a DL S1 TNL Load
Indicator, which is set to HighLoad, to each neighboring BS through the X2
interface.

Uplink High Load Clear Indicates the threshold for clearing the UL high load. If the ratio of the UL
Threshold
transport load to the UL transport bandwidth of the BS keeps below this
threshold for a period of hysteresis, the UL transport load of the BS enters the
medium-load state. In UL medium load state, the BS sends a UL S1 TNL Load
Indicator, which is set to MediumLoad, to each neighboring BS through the X2
interface.

Downlink High Load Indicates the threshold for clearing the DL high load. If the ratio of the transport
Clear Threshold
load to the transmission bandwidth in DL of the BS keeps below this threshold
for a period of time, the DL transport load of the BS enters the medium-load
state. In DL medium-load state, the BS sends a DL S1 TNL Load Indicator,
which is set to MediumLoad, to each neighboring BS through the X2 interface.

Uplink Medium Load Indicates the threshold for triggering the UL medium load. If the ratio of the UL
Trigger Threshold
transport load to the UL transport bandwidth of the BS is above this threshold,
the UL transport load of the BS enters the medium-load state. In UL medium-
load state, the BS sends a UL S1 TNL Load Indicator, which is set to
MediumLoad, to each neighboring BS through the X2 interface.

Downlink Medium Load Indicates the threshold for triggering the DL medium load. If the ratio of the DL
Trigger Threshold
transport load to the DL transport bandwidth of the BS is above this threshold,
the DL transport load of the BS enters the medium-load state. In DL medium-
load state, the BS sends a DL S1 TNL Load Indicator, which is set to
MediumLoad, to each neighboring BS through the X2 interface.

Uplink Medium Load Indicates the threshold for clearing the UL medium load. If the ratio of the UL
Clear Threshold
transport load to the UL transport bandwidth of the BS is below this threshold,
the UL transport load of the BS enters the low-load state. In UL low-load state,
the BS sends a UL S1 TNL Load Indicator, which is set to LowLoad, to each
neighboring BS through the X2 interface.

Downlink Medium Load Indicates the threshold for clearing the DL medium load. If the ratio of the DL
Clear Threshold
transport load to the DL transport bandwidth of the BS is below this threshold,
Table 2 Related parameters

Parameter Description

the DL transport load of the BS enters the low-load state. In DL low-load state,
the BS sends a DL S1 TNL Load Indicator, which is set to LowLoad, to each
neighboring BS through the X2 interface.

5.7.1.6.1.93 TLFRSWITCH
TRANSPORT
+-TLFRSWITCH

Description

The TLFRSWITCH MO indicates the switch for enabling the function of clearing the
transmission link fault.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST TLFRSWITCH Use this command to list the setting of the fault rectification switch for transport
links.

SET TLFRSWITCH Use this command to set the switch for clearing transmission link faults.
Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Transmission Link Fault Indicates whether to enable the function of clearing faults on a transmission link.
Recover Switch
If this parameter is set to ENABLE, a BS attempts to clear a fault by means of
automatic reset when the BS cannot be maintained (OMCH of the BS is
disconnected) and service interruption duration reaches 45 minutes. If the fault
fails to be cleared, the BS attempts to clear the fault again in the same way when
the service interruption duration reaches 480 minutes. If the fault fails to be
cleared after the two resets, the BS stops performing automatic reset. The
service interruption duration at which the BS automatically resets has fixed
values (45 minutes and 480 minutes) and is not configurable.

5.7.1.6.1.94 TOLCALG
TRANSPORT
+-TOLCALG

Description

The bandwidth of the services with low priority would be released to guarantee the QoS of the
services of high priority when the transmission bandwidth changes or during the overload caused
by real-time services.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

LST TOLCALG Use this command to list the parameters of the overload control algorithm.

SET TOLCALG Use this command to set the parameters of the overload control algorithm.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Uplink OLC Algorithm Indicates the UL Over Load Control (OLC) algorithm switch. In the case of
Switch
enabled switch, the bandwidth of the services with low priority would be
released to guarantee the QoS of the services of high priority when the TX
bandwidth changes or during the overload caused by real-time services.

Downlink OLC Indicates the switch for the DL OLC algorithm. If this parameter is set to ON,
Algorithm Switch
bandwidth of the services of a low priority is released to guarantee the QoS of
the services of a high priority when transport bandwidth changes or overload
occurs due to increased load of non-flow control services.

Uplink OLC Trigger Indicates the threshold for triggering the UL OLC. When the UL bandwidth
Threshold
occupancy reaches the threshold, low-priority services are removed to guarantee
the quality of high-priority services.

Uplink OLC Release Indicates the threshold for clearing the UL OLC. When the UL bandwidth
Threshold
occupancy is below this threshold, user services are no longer removed.

Number of Bearers Indicates the number of released services during an OLC action period.
Released During OLC

Downlink OLC Trigger Indicates the threshold for triggering the DL OLC. When the DL bandwidth
Threshold
occupancy reaches the threshold, low-priority services are removed to guarantee
the quality of high-priority services.

Downlink OLC Release Indicates the threshold for clearing the DL OLC. When the DL bandwidth
Threshold
occupancy is below this threshold, user services are no longer removed.

5.7.1.6.1.95 TRANSPORT
+-NE
+-NODE
+-TRANSPORT
+-GTPU[1~1]
+-CRLPOLICY[1~1]
+-TRUSTCERT[1~20]
+-CERTCHKTSK[1~1]
+-CRL[0~20]
+-CRLTSK[0~4]
+-CROSSCERT[0~20]
+-APPCERT[2~2]
+-CA[0~1]
+-CERTMK[1~20]
+-CERTREQ[1~1]
+-IPSECBIND[0~4]
+-TLFRSWITCH[1~1]
+-DOT1X[0~48]
+-DHCPSVRIP[0~2]
+-VLANCLASS[0~272]
+-DHCPRELAYSWITCH[1~1]
+-OMCH[0~2]
+-IKEPROPOSAL[0~99]
+-LR[0~80]
+-UDT[0~69]
+-IPSECBIND6[0~4]
+-IPRT[0~132]
+-MPGRP[0~32]
+-SCTPPEER[0~128]
+-CFMMD[0~8]
+-IPSECDTNL[0~50]
+-USERPLANEPEER[0~384]
+-IKEPEER[0~100]
+-TACALG[1~1]
+-VLANMAP[0~48]
+-PACKETFILTER[0~4]
+-DHCPSW[1~1]
+-SCTPHOST[0~24]
+-IPPATH[0~320]
+-PLRTHRESHOLD[1~1]
+-LOCALIP[1~1]
+-LLDPLOCAL[0~48]
+-CERTDEPLOY[1~1]
+-VRF[0~8]
+-ACL[0~64]
+-SECURITYPEER[0~128]
+-IKECFG[1~1]
+-E1T1BER[1~1]
+-IPPATHRT[0~64]
+-GTRANSPARA[1~1]
+-IP2RSCGRP[0~128]
+-SECURITYHOST[0~32]
+-BFDSESSION[0~96]
+-SUBNETVLAN[0~128]
+-IPITF6[0~128]
+-MPLNK[0~128]
+-HAGRP[0~4]
+-SUBIF[0~64]
+-IPRT6[0~128]
+-DIFPRI[1~1]
+-E1T1[0~32]
+-IPSECPOLICY[0~100]
+-TLDRALG[1~1]
+-SCTPLNK6[0~48]
+-PINGFILTER[0~8]
+-IP2RSCGRP6[0~128]
+-IPSECPOLICY6[0~64]
+-EP2RSCGRP[0~456]
+-TOLCALG[1~1]
+-IPGUARD[1~1]
+-UDPSESSION[0~2]
+-UDTPARAGRP[0~40]
+-ETHPORT[0~32]
+-IKEPEER6[0~64]
+-DEVIP[0~128]
+-SCTPTEMPLATE[0~12]
+-ETHTRK[0~16]
+-EPGROUP[0~74]
+-USERPLANEHOST[0~32]
+-IPPMSESSION[0~500]
+-ETHOAM3AH[0~32]
+-OMCH6[0~1]
+-LOCALETHPORT[1~1]
+-LOCALIP6[1~1]
+-PORTSECURITY[0~96]
+-FLOODDEFEND[0~5]
+-IPSECPROPOSAL[0~99]
+-LLDPGLOBAL[1~1]
+-PPPLNK[0~32]
+-SCTPLNK[0~48]
+-SECURITYTEMPLATE[0~32]
+-ACL6[0~64]
+-PMTUCFG[1~1]
+-TUNNEL[0~15]
+-CPBEARER[0~80]
+-RSCGRP[0~464]
+-SSL[1~1]
+-WEBLMT[1~1]

Description

The TRANSPORT MO is used to manage the commands of the transport layer.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
NODE

Possible children:
GTPU[1~1];CRLPOLICY[1~1];TRUSTCERT[1~20];CERTCHKTSK[1~1];CRL[0~20];CRLTSK[0~4];CROSS
CERT[0~20];APPCERT[2~2];CA[0~1];CERTMK[1~20];CERTREQ[1~1];IPSECBIND[0~4];TLFRSWITCH[
1~1];DOT1X[0~48];DHCPSVRIP[0~2];VLANCLASS[0~272];DHCPRELAYSWITCH[1~1];OMCH[0~2];IKEP
ROPOSAL[0~99];LR[0~80];UDT[0~69];IPSECBIND6[0~4];IPRT[0~132];MPGRP[0~32];SCTPPEER[0~1
28];CFMMD[0~8];IPSECDTNL[0~50];USERPLANEPEER[0~384];IKEPEER[0~100];TACALG[1~1];VLANM
AP[0~48];PACKETFILTER[0~4];DHCPSW[1~1];SCTPHOST[0~24];IPPATH[0~320];PLRTHRESHOLD[1~1
];LOCALIP[1~1];LLDPLOCAL[0~48];CERTDEPLOY[1~1];VRF[0~8];ACL[0~64];SECURITYPEER[0~128];
IKECFG[1~1];E1T1BER[1~1];IPPATHRT[0~64];GTRANSPARA[1~1];IP2RSCGRP[0~128];SECURITYHOST
[0~32];BFDSESSION[0~96];SUBNETVLAN[0~128];IPITF6[0~128];MPLNK[0~128];HAGRP[0~4];SUBIF[
0~64];IPRT6[0~128];DIFPRI[1~1];E1T1[0~32];IPSECPOLICY[0~100];TLDRALG[1~1];SCTPLNK6[0~48]
;PINGFILTER[0~8];IP2RSCGRP6[0~128];IPSECPOLICY6[0~64];EP2RSCGRP[0~456];TOLCALG[1~1];IP
GUARD[1~1];UDPSESSION[0~2];UDTPARAGRP[0~40];ETHPORT[0~32];IKEPEER6[0~64];DEVIP[0~12
8];SCTPTEMPLATE[0~12];ETHTRK[0~16];EPGROUP[0~74];USERPLANEHOST[0~32];IPPMSESSION[0~
500];ETHOAM3AH[0~32];OMCH6[0~1];LOCALETHPORT[1~1];LOCALIP6[1~1];PORTSECURITY[0~96];F
LOODDEFEND[0~5];IPSECPROPOSAL[0~99];LLDPGLOBAL[1~1];PPPLNK[0~32];SCTPLNK[0~48];SECU
RITYTEMPLATE[0~32];ACL6[0~64];PMTUCFG[1~1];TUNNEL[0~15];CPBEARER[0~80];RSCGRP[0~464
];SSL[1~1];WEBLMT[1~1]

5.7.1.6.1.96 TRUSTCERT
TRANSPORT
+-TRUSTCERT

Description

A TRUSTCERT MO defines a trusted certificate. The trusted certificate is used by a BS to verify


the device certificate of a peer device.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD TRUSTCERT Use this command to add a trusted certificate.

DSP TRUSTCERT Use this command to query the status of trusted certificates.

LST TRUSTCERT Use this command to list the configurations of all trusted certificates.

RMV TRUSTCERT Use this command to remove a trusted certificate and the corresponding
certificate file.

Related Parameters
Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Certificate File Name Indicates the file name of the trusted certificate. The file name cannot include
any of the following characters: backslashes (\), slashes (/), colons (:), asterisks
(*), question marks (?), double quotation marks ("), left angle brackets (<), right
angle brackets (>), and bars (|).

Serial Number Indicates the serial number of the trusted certificate.

Common Name Indicates the common name of the trusted certificate.

Issuer Name Indicates the issuer of the trusted certificate.

Expiring Date Indicates the expiration date of the trusted certificate.

Status Indicates the loading status of the trusted certificate.

Effective Date Indicates the date when the trusted certificate begins to take effect.

5.7.1.6.1.97 TUNNEL
TRANSPORT
+-TUNNEL

Description

A TUNNEL MO is used to set the parameters related to backplane communication when co-
transmission is implemented between radio access technologies.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the HAGRP MO:


- In the logical protection group where the SSN of the TUNNEL MO is located, the value of
SN in the HAGRP MO must be the same as the value of SSN in the TUNNEL.
- In the logical protection group where the DSN of the TUNNEL MO is located, the value of
SN in the HAGRP MO must be the same as the value of DSN in the TUNNEL.
Relation with the IPPATH MO:
- If PT and JNRSCGRP in an IPPATH MO are set to TUNNEL and DISABLE, respectively,
the associated TUNNEL MO must have been configured.
Relation with the LR MO:
- If PT in an LR MO is set to TUNNEL, the associated TUNNEL MO must have been
configured.
- When removing a TUNNEL MO, the system automatically removes the LR MO that
depends on the TUNNEL MO.
Relation with the RSCGRP MO:
- If PT in an RSCGRP MO is set to TUNNEL, the TUNNEL MO corresponding to PN in the
RSCGRP MO must have been configured.
Relation with the IPRT MO:
- If RTTYPE and IFT are set to IF and TUNNEL, respectively in an IPRT MO, IFNO in the
IPRT MO must be the same as TUNNELID in the associated TUNNEL MO.
Relation with the TUNNEL MO:
- All the TUNNEL MOs configured for a BS can only cross two subracks.
- Each TUNNEL MO must have a unique combination of SCN, DCN, SSRN, DSRN, SSN,
and DSN.
Relation with the PACKETFILTER MO:
- If PT in a PACKETFILTER MO is set to TUNNEL, the TUNNEL MO corresponding to
PN in the PACKETFILTER MO must have been configured.
Relation with the SUBIF MO:
- A TUNNEL MO and a SUBIF MO cannot both be configured.
Relation with the VRF MO:
- A TUNNEL MO and a VRF MO whose VRFIDX is set to 1 to 7 cannot both be configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function


Table 1 Related MML commands

MML Command Function

DSP TUNNEL Use this command to query the status of a tunnel.

LST TUNNEL Use this command to list the configurations of a tunnel.

MOD TUNNEL Use this command to modify the configurations of a tunnel.

RMV TUNNEL Use this command to remove a tunnel.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Source Cabinet No. Indicates the number of the source cabinet where the tunnel is configured.

Source Subrack No. Indicates the number of the source subrack where the tunnel is configured.

Source Slot No. Indicates the number of the source slot where the tunnel is configured.

Tunnel No. Indicates the index of the tunnel.

Destination Cabinet No. Indicates the number of the destination cabinet where the tunnel is located.

Destination Subrack Indicates the number of the destination subrack where the tunnel is located.
No.

Destination Slot No. Indicates the number of the destination slot where the tunnel is located.

Tunnel Type Indicates the type of the tunnel.

Number of RX Bytes Indicates the number of bytes received through the tunnel.

Number of RX Packets Indicates the actual number of packets received through a tunnel.

Number of TX Bytes Indicates the actual number of bytes sent through the tunnel.

Number of TX Packets Indicates the actual number of packets sent through the tunnel.
5.7.1.6.1.98 UDPSESSION
TRANSPORT
+-UDPSESSION

Description

The UDP session is used to detect the continuity of the channel.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the DEVIP,PPPLNK,MPGRP MOs:


- UDPSESSION:LOCALIP in an UDPSESSION MO to be added must have been
configured. That is, for the UDPSESSION, DEVIP, PPPLNK, and MPGRP MOs configured
on the same board, LOCALIP in the UDPSESSION MO must be the same as any of the
following : IP in the DEVIP MO with the same routing domain, LOCALIP in the PPPLNK
MO, and LOCALIP in the MPGRP MO.
Relation with the MO:
- The combination of LOCALIP and PEERIP in an UDPSESSION must be different from
the combination of LOCALIP and PEERIP in any other UDPSESSION MOs.
- The combination of LOCALIP and PEERIP in an UDPSESSION must be different from
the combination of LOCALIP and PEERIP in any other UDPSESSION MOs.
Relation with the LOCALIP MO:
- PEERIP in an UDPSESSION MO must be different from IP in a LOCALIP MO with the
same routing domain.
Relation with the OMCH MO:
- PEERIP in an UDPSESSION MO must be different from IP in an OMCH MO.
- If CHECKTYPE in an OMCH MO is set to UDPSESSION, before configuring the
UDPSN in this OMCH MO, ensure that the UDPSESSION for the OMCH MO have been
configured. That is, the UDPSESSION MOs whose UDPSN is the same as UDPSN in the
OMCH MO must have been configured.
Relation with the PPPLNK MO:
- PEERIP in an UDPSESSION MO must be different from LOCALIP in a PPPLNK MO.
Relation with the DEVIP MO:
- PEERIP in an UDPSESSION MO must be different from IP in a DEVIP MO.
Relation with the MPGRP MO:
- PEERIP in an UDPSESSION MO must be different from LOCALIP in a MPGRP MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD UDPSESSION Use this command to add a UDP session.

DSP UDPSESSION Use this command to query the UDP session status.

LST UDPSESSION Use this command to query the configuration of the UDP session.

MOD UDPSESSION Use this command to modify the configuration information of a UDP session.

RMV UDPSESSION Use this command to remove the configuration of a UDP session.

UDPECHO Use this command to test the network connectivity and transmission line quality
when the destination IP address supports UDP loopback. After this command is
executed for a destination IP address that supports UDP loopback, the source
host sends UDPECHO messages to the destination host, which loops back the
messages to the source host. According to the looped back messages, the source
host determines the network connectivity and transmission line quality.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

UDP Session ID Indicates the UDP session number.

Cabinet No. Indicates the cabinet number of the board where the UDP session is located.

Subrack No. Indicates the subrack number of the board where the UDP session is located.
Table 2 Related parameters

Parameter Description

Slot No. Indicates the slot number of the board where the UDP session is located.

Local IP Address Indicates the local IP address. The local IP address must be the configured IP
address on the board, such as the Ethernet port IP address, or logical IP address.
The address of the local maintenance Ethernet port cannot be used.

Peer IP Address Indicates the peer IP address. The IP address cannot be 0.0.0.0, broadcast IP
address, multicast IP address, loopback IP address, or any existing IP address in
the system.

DSCP Indicates the priority of a differentiated services code point (DSCP). The priority
has a positive correlation with the value of this parameter.

Response Messages Indicates the statistics of the UDPECHO response messages, including RTT
information.

Interval Indicates the interval at which UDP session detection packets are sent.

Check Count Indicates the number of UDP ping packet timeouts. If the number of UDP ping
timeouts is greater than the number of detection packets, the UDP session
detection is faulty.

Check Status Indicates the UDP session status. If the UDP session detects interruption, the
status is abnormal.

5.7.1.6.1.99 UDT
TRANSPORT
+-UDT

Description

UDT MO is used to support the differentiated gold, silver, and bronze user data types.The UDT
MO takes effect only in LTE.

Effective Scenario

Immediately
Relations Between MOs

Possible parents:
TRANSPORT

Relation with the UDT MO:


- UDTNO in an UDT MO is set to a value in the range of 1 to 9 by default. The default
settings cannot be removed.
Relation with the UDTPARAGRP MO:
- Before adding an UDT MO, ensure that the associated UDTPARAGRP is configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD UDT Use this command to add a user data type.

LST UDT Use this command to list the configuration of a user data type.

MOD UDT Use this command to modify a user data type.

RMV UDT Use this command to remove a user data type.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

User Data Type Indicates the number of the user data type.Numbers 1~9 are standard user data
Number
types, which are automatically configured by the BS. Numbers 10~254 are
extended user data types.

User Data Type Indicates the ID of the transport parameter group related to the services
Transfer Parameter
Group ID. corresponding to an QCI.User data type numbers 1~9 correspond to user data
type transfer parameter group IDs 40~48, which are automatically configured by
the BS.
5.7.1.6.1.100 UDTPARAGRP
TRANSPORT
+-UDTPARAGRP

Description

The UDTPARAGRP MO is used to support the parameter groups related to the differentiated
Gold-, Silver-, and Bronze-level user data types. Each parameter group is uniquely identified by
the group ID. Other parameters include data priority,priority rule, activity factor, primary
transport resource type, primary port load threshold, primary-to-secondary port load ratio
threshold and flow control type.The UDTPARAGRP MO takes effect only in LTE.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the UDT MO:


- Before adding an UDT MO, ensure that the associated UDTPARAGRP is configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD UDTPARAGRP Use this command to add a transport parameter group for a user data type.

LST UDTPARAGRP Use this command to list a transport parameter group for a user data type.

MOD UDTPARAGRP Use this command to modify a transport parameter group for a user data type.

RMV UDTPARAGRP Use this command to remove a transport parameter group for a user data types.
Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

User Data Type Indicates the ID of the transport parameter group related to the service that
Transfer Parameter
Group ID. corresponds to the QCI. It uniquely identifies a transport parameter group.User
data type numbers 1~9 correspond to user data type transfer parameter group
IDs 40~48, which are automatically configured by the BS.

Priority Rule Indicates the rule for prioritizing traffic to meet service requirements. If this
parameter is set to IPPRECEDENCE, the protocol stack of the earlier version is
adopted, which firstly converts a Type of Service (TOS) to a DSCP and then
prioritizes traffic.

Priority Indicates the priority of the service data, which is identified by a DSCP value.
The priority of the service data has a positive correlation with the DSCP value.

Act Factor Indicates the activity factor of the services corresponding to an QCI.

Primary Transport Indicates the type of primary transport resource used to transmit the user date
Resource Type
when hybrid transmission is adopted. HQ indicates that high-quality transport
resources are used, while LQ indicates that low-quality transport resources are
used. When a new service requests admission and admission control is
performed, one of the IP path routes with transport resources of the same quality
is used as the primary transport path.

Primary Port Load Indicates the primary port load threshold of the user data in the hybrid
Threshold
transmission scenario. A larger value indicates that services are more likely to be
admitted to the primary path.

Primary To Secondary Indicates the primary-to-secondary port load ratio threshold of user data in the
Port Load Ratio
Threshold hybrid transmission scenario. A smaller value indicates that services are more
likely to be admitted to the primary path.

5.7.1.6.1.101 USERPLANEHOST
TRANSPORT
+-USERPLANEHOST

Description
The USERPLANEHOST MO is used to configure a user-plane host. When the user plane is set
up automatically, the BS can automatically set up a user-plane link between the configured user-
plane host and user-plane peer. The user-plane link can also be manually configured.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the DEVIP,MPGRP,PPPLNK MOs:


- In a routing domain,LOCIPV4 in a USERPLANEHOST MO must be the same as
IP ,LOCALIP or LOCALIP in a configured DEVIP MO ,MPGRP or PPPLNK.
Relation with the DEVIP6 MO:
- LOCIPV6 in a USERPLANEHOST MO must be the same as IPV6 in a configured
DEVIP6 MO.
Relation with the SECURITYHOST MO:
- If PT in a DEVIP MO referenced by LOCIPV4 in a USERPLANEHOST MO is not set to
LOOPINT, LOCIPV4 in the USERPLANEHOST MO must be configured on the same
physical port as LOCIKEIPV4 in a referenced SECURITYHOST MO.
- In a USERPLANEHOST MO, if IPSECSWITCH is set to ENABLE, LOCIPV4 and
LOCIKEIPV4 of SECURITYHOST referenced by this USERPLANEHOST MO must be on
the same board.
- In a USERPLANEHOST MO, if IPSECSWITCH is set to ENABLE, SECHOSTID must
be the same as SECURITYHOSTID in a configured SECURITYHOST MO.
- In a USERPLANEHOST MO, if IPSECSWITCH is set to ENABLE, IPVERSION must
be the same as IPVERSION in a referenced SECURITYHOST MO.
- If PT in an IPITF6 MO referenced by LOCIPV6 in a USERPLANEHOST MO is not set
to LOOPINT, LOCIPV6 in the USERPLANEHOST MO must be configured on the same
physical port as LOCIKEIPV6 in a referenced SECURITYHOST MO.
- In an USERPLANEHOST MO, if IPSECSWITCH is set to ENABLE, LOCIPV6 and
LOCIKEIPV6 of SECURITYHOST referenced by this USERPLANEHOST MO must be on
the same board.
Relation with the USERPLANEHOST MO:
- If IPSECSWITCH in a USERPLANEHOST MO is set to DISABLE, another
USERPLANEHOST MO that has the same VRFIDX,LOCIPV4 value as this
USERPLANEHOST MO cannot be configured.
- If IPSECSWITCH in a USERPLANEHOST MO is set to ENABLE, another
USERPLANEHOST MO that has the same combination of LOCIPV4 and SECHOSTID as
this USERPLANEHOST MO cannot be configured.
- If IPSECSWITCH in a USERPLANEHOST MO is set to DISABLE, another
USERPLANEHOST MO that has the same LOCIPV6 value as this USERPLANEHOST MO
cannot be configured.
- If IPSECSWITCH in a USERPLANEHOST MO is set to ENABLE, another
USERPLANEHOST MO that has the same combination of LOCIPV6 and SECHOSTID as
this USERPLANEHOST MO cannot be configured.
Relation with the MPGRP MO:
- In a routing domain, if LOCIPV4 in the USERPLANEHOST MO is referenced by
LOCALIP in the MPGRP MO, the IPSECSWITCH in the USERPLANEHOST MO must
not be set to ENABLE.
Relation with the PPPLNK MO:
- In a routing domain, if LOCIPV4 in the USERPLANEHOST MO is referenced by
LOCALIP in the PPPLNK MO, IPSECSWITCH in the USERPLANEHOST MO must not
be set to ENABLE.
Relation with the VRF MO:
- The VRF instance used by a USERPLANEHOST MO must have been configured.
Relation with the USERPLANEPEER,EPGROUP,IPPATH MOs:
- When USERPLANEHOST MO and USERPLANEPEER MO are configured in one
EPGROUP MO simultaneously and their IP versions are set to IPv4,these MOs cannot coexist
with IPPATH with PATHTYPE set to FIXED.
Relation with the USERPLANEPEER,EPGROUP,IPPATH6 MOs:
- When USERPLANEHOST MO and USERPLANEPEER MO are configured in one
EPGROUP MO simultaneously and their IP versions are set to IPv6,these MOs cannot coexist
with IPPATH6 with PATHTYPE set to FIXED.
Relation with the EPGROUP MO:
- In a routing domain,for the USERPLANEHOST MOs referenced by the same EPGROUP
MO with IPVERSION set to IPv4, if the LOCIPV4s of these USERPLANEHOSTs are
referenced by DEVIP MOs or MPGRPMOs,these IP addresses must be configured on the same
board.
- In a routing domain,for the USERPLANEHOST MOs referenced by the same EPGROUP
MO with IPVERSION being IPv4, if the LOCIPV4s of these USERPLANEHOSTs are
referenced by DEVIP MOs or PPPLNKMOs,these IP addresses must be configured on the same
board.
- In a routing domain,for the USERPLANEHOST MOs referenced by the same EPGROUP
MO with IPVERSION set to IPv4, if the LOCIPV4s of these USERPLANEHOSTs are
referenced by MPGRP MOs or PPPLNKMOs,these IP addresses must be configured on the
same board.
- UPHOSTID referenced by USERPLANEHOSTREFS in an EPGROUP MO must be the
same as UPHOSTID in a configured USERPLANEHOST MO.
- If the USERPLANEHOST MOs referenced by the same EPGROUP MO have the same
IPVERSION set to IPv4, the SEGWSWITCH of SECURITYHOST referenced by these
USERPLANEHOST MOs must also be the same.
- In a routing domain,for the USERPLANEHOST MOs referenced by the same EPGROUP
MO with IPVERSION set to IPv4, if the LOCIPV4s of these USERPLANEHOSTs are
referenced by DEVIP MOs ,these IP addresses must be configured on the same board.
- In a routing domain,for the USERPLANEHOST MOs referenced by the same EPGROUP
MO with IPVERSION set to IPv4, the LOCIPV4 of these USERPLANEHOST must be
different.
- If the USERPLANEHOST MOs referenced by the same EPGROUP MO have the same
IPVERSION set to IPv6, the SEGWSWITCH of SECURITYHOST referenced by these
USERPLANEHOST MOs must also be the same.
- In a routing domain,for the USERPLANEHOST MOs referenced by the same EPGROUP
MO with IPVERSION set to IPv6, the LOCIPV6 of these USERPLANEHOST must be
configured on the same board.
- In a routing domain,for the USERPLANEHOST MOs referenced by the same EPGROUP
MO with IPVERSION set to IPv6, the LOCIPV6 of these USERPLANEHOST must be
different.
Relation with the EPGROUP,USERPLANEPEER MOs:
- In a routing domain IPv4 configuration,if there are USERPLANEHOST MOs with the same
local IP configured in different EPGROUP,the same USERPLANEPEER MO is only allowed
to be configured in one of these EPGROUP MO.
- In a routing domain IPv6 configuration,if there are USERPLANEHOST MOs with the same
local IPv6 configured in different EPGROUP,the same USERPLANEPEER MO is only
allowed to be configured in one of these EPGROUP MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add a user-plane host.


USERPLANEHOST

LST Use this command to list the configuration of user-plane hosts.


USERPLANEHOST

MOD Use this command to modify the configuration of a user-plane host.


Table 1 Related MML commands

MML Command Function

USERPLANEHOST

RMV Use this command to remove a user-plane host.


USERPLANEHOST

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

User Plane Host ID Indicates the ID of the user-plane host.

VRF Index Indicates the index of the virtual route and forwarding(VRF) instance.

IP Version Indicates the version of the user-plane host IP address.

Local IP Address Indicates the IP Address of the user plane host.

Local IPv6 Address Indicates the IPv6 Address of the user plane host. This parameter takes effect
only in LTE.

IPSec Switch Indicates whether to enable automatic setup of an IPSec tunnel between the local
end and the peer end based on the SECURITYHOST and SECURITYPEER
MOs. The IPSec tunnel is used to encrypt the data to be transmitted on the
internal user plane paths.

Security Host ID Indicates the security host ID used by the user-plane host.

User Label Indicates the description of the user-plane local device.

5.7.1.6.1.102 USERPLANEPEER
TRANSPORT
+-USERPLANEPEER
Description

The USERPLANEPEER MO is used to configure a user-plane peer. This MO can be


automatically or manually created.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the DEVIP,MPGRP,PPPLNK MOs:


- PEERIPV4 in a USERPLANEPEER MO must be different from IP ,LOCALIP or
LOCALIP in a configured DEVIP MO ,MPGRP and PPPLNK.
Relation with the DEVIP6 MO:
- PEERIPV6 in a USERPLANEPEER MO must be different from IPV6 in a configured
DEVIP6 MO.
Relation with the SECURITYPEER MO:
- In a USERPLANEPEER MO, if IPSECSWITCH is set to ENABLE, SECPEERID must
be the same as SECURITYPEERID in a configured SECURITYPEER MO.
- If IPSECSWITCH and IPVERSION in a USERPLANEPEER MO are set to ENABLE
and IPv4, respectively, the SECURITYPEER MO whose security peer ID is the same as
SECPEERID in the USERPLANEPEER MO must meet either of the following conditions: (1)
IPVERSION in the USERPLANEPEER MO is set to IPv4. (2) PEERNAME in the
SECURITYPEER MO is the same as PEERNAME in an IKEPEER MO.
- If IPSECSWITCH and IPVERSION in a USERPLANEPEER MO are set to ENABLE
and IPv6, respectively, the SECURITYPEER MO whose security peer ID is the same as
SECPEERID in the USERPLANEPEER MO must meet either of the following conditions: (1)
IPVERSION in the USERPLANEPEER MO is set to IPv6. (2) PEERNAME in the
SECURITYPEER MO is the same as PEERNAME in an IKEPEER6 MO.
Relation with the USERPLANEPEER MO:
- If IPSECSWITCH in a USERPLANEPEER MO is set to DISABLE, another
USERPLANEPEER MO that has the same VRFIDX,PEERIPV4 value as this
USERPLANEPEER MO cannot be configured.
- If IPSECSWITCH in a USERPLANEPEER MO is set to ENABLE, another
USERPLANEPEER MO that has the same combination of PEERIPV4 and SECPEERID as
this USERPLANEPEER MO cannot be configured.
- If IPSECSWITCH in a USERPLANEPEER MO is set to DISABLE, another
USERPLANEPEER MO that has the same PEERIPV6 value as this USERPLANEPEER MO
cannot be configured.
- If IPSECSWITCH in a USERPLANEPEER MO is set to ENABLE, another
USERPLANEPEER MO that has the same combination of PEERIPV6 and SECPEERID as
this USERPLANEPEER MO cannot be configured.
- In a routing domain,the PEERIPV6 of different USERPLANEPEER MOs with
IPVERSION set to IPv4 must not be the same.
- In a routing domain,the PEERIPV4 of different USERPLANEPEER MOs with
IPVERSION set to IPv4 must not be the same.
Relation with the EPGROUP MO:
- UPPEERID referenced by USERPLANEPEERREFS in an EPGROUP MO must be the
same as UPPEERID in a configured USERPLANEPEER MO.
Relation with the VRF MO:
- The VRF instance used by a USERPLANEPEER MO must have been configured.
Relation with the USERPLANEHOST,EPGROUP,IPPATH MOs:
- When USERPLANEHOST MO and USERPLANEPEER MO are configured in one
EPGROUP MO simultaneously and their IP versions are set to IPv4,these MOs cannot coexist
with IPPATH with PATHTYPE set to FIXED.
Relation with the USERPLANEHOST,EPGROUP,IPPATH6 MOs:
- When USERPLANEHOST MO and USERPLANEPEER MO are configured in one
EPGROUP MO simultaneously and their IP versions are set to IPv6,these MOs cannot coexist
with IPPATH6 with PATHTYPE set to FIXED.
Relation with the EPGROUP,USERPLANEHOST MOs:
- In a routing domain IPv4 configuration,if there are USERPLANEHOST MOs with the same
local IP configured in different EPGROUP,the same USERPLANEPEER MO is only allowed
to be configured in one of these EPGROUP MO.
- In a routing domain IPv6 configuration,if there are USERPLANEHOST MOs with the same
local IPv6 configured in different EPGROUP,the same USERPLANEPEER MO is only
allowed to be configured in one of these EPGROUP MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD Use this command to add a user-plane peer.


USERPLANEPEER

LST Use this command to list the configuration of user-plane peers and whether the
USERPLANEPEER
object is created by the system. When the AUTOCFGFLAG is
MANUAL_CREATED, it means that the object is configured by the user
manually. AUTO_CREATED means that the object is created by the system.

MOD Use this command to modify the configuration of a peer end on the user plane.
USERPLANEPEER

RMV Use this command to remove a user-plane peer.


USERPLANEPEER

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

User Plane Peer ID Indicates the ID of the user-plane peer.

VRF Index Indicates the index of the virtual route and forwarding(VRF) instance.

IP Version Indicates the version of the user-plane peer IP address.

Peer IP Address Indicates the IP Address of the user plane peer.

Peer IPv6 Address Indicates the IPv6 Address of the user plane peer. This parameter takes effect
only in LTE.

IPSec Switch Indicates whether to enable automatic setup of an IPSec tunnel between the local
end and the peer end based on the SECURITYHOST and SECURITYPEER
MOs. The IPSec tunnel is used to encrypt the data to be transmitted on the
internal user plane paths.

Security Peer ID Indicates the security peer ID used by the user-plane peer.

Remote ID This parameter indicates the remote ID and takes effect only in the
USERPLANEPEER MO that is automatically created during X2 self-setup. This
parameter is automatically configured during X2 self-setup and is used to
Table 2 Related parameters

Parameter Description

identify the peer eNodeB. The parameter value is displayed as follows:


eNB:MCC_'The MCC of the serving operator on the local eNodeB' MNC_'The
MNC of the serving operator on the local eNodeB' GlobaleNBId_'The global
MCC of the peer eNodeB'-'The global MNC of the peer eNodeB'-'The peer
eNodeB ID'.

Control Mode Indicates whether the object can be modified or deleted by the system. The value
MANUAL_MODE means that only the user can modify or delete the object.
The value AUTO_MODE means that both the system and the user can modify or
delete the object.

Auto Config Flag Indicates whether the object is created by the system. The value
MANUAL_CREATED means that the object is configured by the user. The
value AUTO_CREATED means that the object is created by the system.

User Label Indicates the information of the user-plane peer device.

5.7.1.6.1.103 VLANCLASS
TRANSPORT
+-VLANCLASS

Description

The VLANCLASS MO is used to map services with different VLAN tags according to the
service type. There are two mapping modes. If the service type is user data, VLAN tags are
mapped on the basis of the user data packet priorities (DSCPs). If the service type is not user
data, VLAN tags are mapped to user data/non user data on the basis of the service type.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the VLANCLASS MO:


- The total number of different VLAN IDs between VLANID in the VLANCLASS MO and
VLANID in the VLANMAP MO whose VLANMODE is set to SINGLEVLAN cannot exceed
48.
Relation with the SUBIF MO:
- A VLANCLASS MO and a SUBIF MO cannot both be configured.
Relation with the VRF MO:
- A VLANCLASS MO and a VRF MO whose VRFIDX is set to 1 to 7 cannot both be
configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD VLANCLASS Use this command to add a mapping from traffic types to VLANs.

LST VLANCLASS Use this command to list all the configured VLAN priority mapping
relationships.

MOD VLANCLASS Use this command to modify a mapping from traffic types to VLANs.

RMV VLANCLASS Use this command to remove a VLAN priority mapping from the VLAN group.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

VLAN Group No. Indicates the VLAN group that the added VLAN mapping belongs to. Multiple
VLAN groups are used in the scenario in which telecom operators share
transport resources and use different VLAN policies.

Traffic Type Indicates the traffic type. Traffic of different types is transmitted through
different VLANs. High-priority OM data includes the data of NTP/SNTP,
remote maintenance channel switchover, and TCP (excluding that related to
FTP). Low-priority OM data includes the data of the File Transfer Protocol
Table 2 Related parameters

Parameter Description

(FTP) service. Other data refers to the data except the user data, signaling, high-
priority OM data, and low-priority OM data.

User Data Service Indicates the DSCP priority of user data.


Priority

VLAN ID Indicates the VLAN ID that the service data belongs to.

VLAN Priority Indicates the VLAN priority. A greater parameter value denotes a higher priority.

5.7.1.6.1.104 VLANMAP
TRANSPORT
+-VLANMAP

Description

The VLANMAP MO is used to attach different VLAN tags to the data packets according to their
next hop IP addresses. The mapping modes are classified into single VLAN and VLAN group. In
single VLAN mode, next hop IP addresses are directly mapped to the VLAN tags. In VLAN
group mode, next hop IP addresses are mapped to the VLAN groups and then to the VLAN tags
in the VLAN groups according to the data packet priorities (DSCPs) and data type.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Relation with the VLANMAP MO:


- NEXTHOPIP and MASK must be different in any two VLANMAP MOs in a routing
domain. That is, NEXTHOPIP in two VLANMAP MOs must be on different network
segments.
- The total number of different VLAN IDs between VLANID in the VLANCLASS MO and
VLANID in the VLANMAP MO whose VLANMODE is set to SINGLEVLAN cannot exceed
48.
- All VLANMAP MOs that meet both of the following conditions must have the same
SETPRIO value: (1) VLANMODE in these MOs is set to SINGLEVLAN. (2) These MOs are
in the same routing domain.
- A VLANMAP MO cannot be configured together with a SUBNETVLAN MO on a BS.
- Any two VLANMAP MOs in different routing domains must have different VLANID
values.
Relation with the VRF MO:
- The VRF instance used by a VLANMAP MO must have been configured.
- A VLANCLASS MO whose VLANMODE is set to VLANGROUP and a VRF MO whose
VRFIDX is set to 1 to 7 cannot both be configured.
Relation with the SUBIF MO:
- If an SUBIF MO has been configured, VLANMODE in the VLANMAP MO must not be
set to VLANGROUP.
Relation with the DEVIP MO:
- If VLANID in two VLANMAP MOs is the same, NEXTHOPIP in the two MOs must be
on the same egress port.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD VLANMAP Use this command to add an entry of mapping from a next-hop IP address to a
single VLAN or VLAN group.

LST VLANMAP Use this command to list the parameters of the next hop VLAN mapping
relationship.

MOD VLANMAP Use this command to modify the parameters related to a next hop VLAN
mapping.

RMV VLANMAP Use this command to remove a next hop VLAN mapping relationship.

Related Parameters
Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

VRF Index Indicates the index of a VRF instance. The NodeB currently supports default
routes domain only (the VRF index is 0).

Next Hop IP Indicates the next hop IP address used for mapping the VLAN.

Mask Indicates the subnet mask of the next hop IP address used for mapping the
VLAN.

VLAN Mode Indicates the VLAN mode. When this parameter is set to SINGLEVLAN, the
configured VLAN ID and VLAN priority can be directly used to label the
VLAN tag.
If this parameter is set to VLANGROUP, the next hop IP addresses are mapped
to the VLAN groups, and then mapped to the VLAN tags in the VLAN groups
according to the DSCPs of the IP packets. In VLAN group mode, ensure that the
VLAN groups have been configured by running the ADD VLANCLASS command.
Otherwise, the configuration does not take effect.

VLAN ID Indicates the VLAN ID in the VLAN tag.

VLAN Priority Indicates the VLAN priority.

VLAN Group No. Indicates the VLAN group number.

Set VLAN Priority Indicates whether to set the priority of a single VLAN. When this parameter is
set to ENABLE, the VLAN priority is configured by running the ADD
VLANMAP command. When this parameter is set to DISABLE, the VLAN
priority is determined by the mapping between DSCP and VLAN priority. This
mapping can be configured by running the SET DSCPMAP command.
The default mapping between DSCP and VLAN priority is as follows:
If the DSCP is within the range from 0 to 7, the default priority is 0;
If the DSCP is within the range from 8 to 15, the default priority is 1;
If the DSCP is within the range from 16 to 23, the default priority is 2;
If the DSCP is within the range from 24 to 31, the default priority is 3;
If the DSCP is within the range from 32 to 39, the default priority is 4;
If the DSCP is within the range from 40 to 47, the default priority is 5;
If the DSCP is within the range from 48 to 55, the default priority is 6;
If the DSCP is within the range from 56 to 63, the default priority is 7.
5.7.1.6.1.105 VRF
TRANSPORT
+-VRF
+-PRI2QUE[1~1]
+-DSCPMAP[64~64]

Description

Virtual routing forwarding(VRF).The IP addresses and routes within one routing domain must be
unique, whereas those in different routing domains are independent of each other.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TRANSPORT

Possible children:
PRI2QUE[1~1];DSCPMAP[64~64]

Relation with the VRF MO:


- The default VRF instance must exist. That is, the VRF MO whose VRFIDX is set to 0 must
have been configured.
Relation with the PPPLNK MO:
- A PPPLNK MO and a VRF MO whose VRFIDX is set to 1 to 7 cannot both be configured.
Relation with the MPGRP MO:
- An MPGRP MO and a VRF MO whose VRFIDX is set to 1 to 7 cannot both be configured.
Relation with the TUNNEL MO:
- A TUNNEL MO and a VRF MO whose VRFIDX is set to 1 to 7 cannot both be configured.
Relation with the DEVIP MO:
- The VRF instance used by a DEVIP MO must have been configured.
- If PT in a DEVIP MO is not set to SUBIF or LOOPINT, the VRF instance in a VRF MO
must be set to 0.
Relation with the IP2RSCGRP MO:
- The VRF instance used by an IP2RSCGRP MO must have been configured.
Relation with the VLANMAP MO:
- The VRF instance used by a VLANMAP MO must have been configured.
- A VLANCLASS MO whose VLANMODE is set to VLANGROUP and a VRF MO whose
VRFIDX is set to 1 to 7 cannot both be configured.
Relation with the PINGFILTER MO:
- The VRF instance used by a PINGFILTER MO must have been configured.
Relation with the SUBIF MO:
- The VRF instance used by a SUBIF MO must have been configured.
Relation with the ACL MO:
- The VRF instance used by a ACL MO must have been configured.
Relation with the VLANCLASS MO:
- A VLANCLASS MO and a VRF MO whose VRFIDX is set to 1 to 7 cannot both be
configured.
Relation with the CFMBNDIP MO:
- The VRF instance used by a CFMBNDIP MO must have been configured.
Relation with the SCTPPEER MO:
- The VRF instance used by a SCTPPEER MO must have been configured.
Relation with the USERPLANEHOST MO:
- The VRF instance used by a USERPLANEHOST MO must have been configured.
Relation with the SCTPHOST MO:
- The VRF instance used by a SCTPHOST MO must have been configured.
Relation with the USERPLANEPEER MO:
- The VRF instance used by a USERPLANEPEER MO must have been configured.
Relation with the EPGROUP MO:
- The VRF instance used by a EPGROUP MO must have been configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD VRF Use this command to add a virtual routing forwarding (VRF). The IP addresses
Table 1 Related MML commands

MML Command Function

and routes within one routing domain must be unique, whereas those in different
routing domains are independent of each other.

LST VRF Use this command to list the configuration of a VRF.

MOD VRF Use this command to modify the configuration of a VRF.

RMV VRF User this command to remove a VRF.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

VRF Index Indicates the index of a VRF instance.

User Label Indicates the description of a VRF instance.

5.7.1.6.2 Equipments-tree
This chapter describes the MOs related to eNodeB equipment.

AAMU

AARU

AAS

ALD

ALMPORT

ANTENNAPORT

APPLICATION
BASEBANDEQM

BATCTPA

BATTERY

BBP

BBPLINK

BBUFAN

BCP

BITS

BRI

CABINET

CARRIERRESOURCE

CASCADEPORT

CCU

CDE

CFGBAK

CFGFILESTAT

CFGSTAT

CHK

CPRILBR

CPRIPORT

CTRLLNK

DIESELGEN

EMU

ENERGYCON

EQUIPMENT

FM
FMU

FTPCLT

FTPCLTPORT

GPS

GTMU

HTCDPA

IPCLKLNK

LINECLK

LOCATION

MAINSALARMBIND

MPT

NE

NODE

NTPCP

OMUCURTIME

OUTPORT

PEERCLK

PEU

PMU

PSU

PSUIS

RCVMODE

RE

RET

RETDEVICEDATA

RETPORT
RETSUBUNIT

RFU

RHUB

RRU

RRUCHAIN

RU

RXBRANCH

SECTOR

SECTOREQM

SES

SFP

SSL

SUBRACK

SYNCETH

TASM

TCU

TIMESRC

TMA

TMADEVICEDATA

TMASUBUNIT

TOD

TRP

TXBRANCH

TZ

UCIU

UEIU
USCU

VANTENNAPORT

VRET

VRETSUBUNIT

WEBLMT

Parent topic: MO

5.7.1.6.2.1 AAMU
EQUIPMENT
+-AAS
+-AAMU
+-CPRIPORT[2~2]
+-SFP[2~2]

Description

An AAMU MO defines an AAMU, which manages communication links between the AAS and
BBU and manages AARUs in the AAS.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
AAS

Possible children:
CPRIPORT[2~2];SFP[2~2]

Relation with the RET,RRU,RFU MOs:


- The RRU or RFU or AAMU MO corresponding to CTRLCN, CTRLSRN, and CTRLSN
in the RET MO must have been configured.
Relation with the AAMU MO:
- The RRUCHAIN MO where the AAMU MO is located must have been configured.
Relation with the RRUCHAIN,RRU,RFU MOs:
- The total number of RRU and RFU and AAMU MOs configured on the RRUCHAIN MO
must be smaller than or equal to 21.
Relation with the AAMU, RRU, and RFU MOs:
- If BM in the RRUCHAIN MO where the AAMU MO is located is set to HOT, the total
number of AAMU, RRU, and RFU MOs configured on the RRUCHAIN MO must be 0 or 1.
Relation with the RRU,RFU,RHUB MOs:
- Under a base station, the total number of RRU, RFU, AAMU, and RHUB MOs must be less
than or equal to 420.
Relation with the RHUB MO:
- The RRUCHAIN MO where the RHUB MO is located must not have RRU MO,RFU MO
and AAMU MO.
Relation with the AAMU, RRU, RFU, and RHUB MOs:
- When HCN, HSRN, and HSN in an RRUCHAIN MO are the same as CN, SRN, and SN in
an RHUB MO, respectively, the RT in the RRU MO that is configured on this RRUCHAIN
MO must be set to MPMU or MPRF.

Related Parameters

Table 1 describes the parameters related to this MO.

Table 1 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet where the AAMU is located.

Subrack No. Indicates the number of the subrack where the AAMU is located.

Slot No. Indicates the slot number of the AAMU.

RRU Topo Position Indicates the position where the AAS is installed in the topology.

RRU Chain No. Indicates the ID of an RRU chain or ring which the AAS is inserted in.

AAS Position Indicates where the AAS is inserted in an RRU chain or ring.It is calculated
from the start port one by one.

5.7.1.6.2.2 AARU
EQUIPMENT
+-AAS
+-AARU
+-VANTENNAPORT[32~32]
+-VRET[1~1]
+-TXBRANCH[0~8]
+-RXBRANCH[0~8]

Description

An AARU MO defines an AARU, which provides ports for sending and receiving baseband and
RF signals and processes the uplink and downlink baseband signals.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
AAS

Possible children:
VANTENNAPORT[32~32];VRET[1~1];TXBRANCH[0~8];RXBRANCH[0~8]

Relation with the VANTENNAPORT MO:


- The number of VANTENNAPORT MOs configured on one AARU MO must be 32.
Relation with the VRET MO:
- The AARU MO corresponding to DEVICENO, CONNCN, CONNSRN, and CONNSN in
the VRET MO must have been configured.
Relation with the AAS MO:
- The AAS MO corresponding to CN and SRN in the AARU MO must have been configured.
Relation with the TXBRANCH and RXBRANCH MOs:
- The number of TXBRANCH MOs related to the AARU MO must be equal to TXNUM in
the AARU MO, and the number of RXBRANCH MOs related to the AARU MO must be equal
to RXNUM in the AARU MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD AARU Use this command to add an active antenna radio unit (AARU).

DSP AARU Use this command to query the dynamic information about an active antenna
radio unit (AARU).

LST AARU Use this command to list the active antenna radio unit (AARU) configuration.

MOD AARU Use this command to modify the active antenna radio unit (AARU)
configuration.

RMV AARU Use this command to remove an active antenna radio unit (AARU).

STR ANTTEST Use this command to start an antenna quality test for an active antenna radio unit
(AARU).

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet where the AARU is located.

Subrack No. Indicates the number of the subrack where the AARU is located.

Slot No. Indicates the slot number of the AARU.

AARU Name Indicates the AARU name.

Administrative state Indicates the administrative state.

Frequency Min Indicates the minimum effective bandwidth of the carrier.


Bandwidth

Intermediate Frequency Indicates the intermediate frequency offset of the AARU. This parameter is set
Offset
by the user during the network planning to avoid the external signal interference
around the current received frequency, and accordingly improve the receiver
sensitivity of the system. This parameter, however, is not recommended to be
used.
Table 2 Related parameters

Parameter Description

Number of RX channels Indicates the number of RX channels of the AARU.

Number of TX channels Indicates the number of TX channels of the AARU.

Logical Switch of TX Indicates whether to enable TX channels on the AARU. On the AARU, all TX
Channel
channels must be simultaneously enabled or disabled.

AARU Work Standard Indicates the working standard of the AARU.

VRET No. Indicates the number of a virtual antenna corresponding to the AARU.

Max Beam Azimuth Indicates the maximum horizontal azimuth supported by the virtual antenna
subunit corresponding to the AARU.

Min Beam Azimuth Indicates the minimum horizontal azimuth supported by the virtual antenna
subunit corresponding to the AARU.

Max Beam Width Indicates the maximum horizontal beamwidth supported by the virtual antenna
subunit corresponding to the AARU.

Min Beam Width Indicates the minimum horizontal beamwidth supported by the virtual antenna
subunit corresponding to the AARU.

Max Tilt Indicates the maximum tilt supported by the virtual antenna subunit
corresponding to the AARU.

Min Tilt Indicates the minimum tilt supported by the virtual antenna subunit
corresponding to the AARU.

Max Tilt Difference Indicates the maximum tilt difference between carriers supported by the virtual
Between Carriers
antenna subunit corresponding to the AARU.

5.7.1.6.2.3 AAS
EQUIPMENT
+-AAS
+-AARU[0~3]
+-AAMU[0~1]
Description

An AAS MO defines an active antenna system, which consists of one Active Antenna
Management Unit (AAMU) and one to three Active Antenna Radio Units (AARUs).

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
EQUIPMENT

Possible children:
AARU[0~3];AAMU[0~1]

Relation with the AARU MO:


- The AAS MO corresponding to CN and SRN in the AARU MO must have been configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD AAS Use this command to add an active antenna system (AAS) to a specified chain or
ring.

DSP AAS Use this command to query the dynamic information about an active antenna
system (AAS).

LST AAS Use this command to list the active antenna system (AAS) configuration.

MOD AAS Use this command to modify the active antenna system (AAS) configuration.

RMV AAS Use this command to remove an active antenna system (AAS).

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet where the AAS is located.

Subrack No. Indicates the number of the subrack where the AAS is located.

AAS Name Indicates the AAS name.

Access Direction Indicates the access direction of the service plane.

5.7.1.6.2.4 ALD
Description

An ALD MO consists of the common attributes and common operations of the Antenna Line
Device (ALD). An ALD is the Remote Electrical Tilt Unit (RET), or Tower Mounted Amplifier
(TMA).

Effective Scenario

Immediately

Relations Between MOs

Inherit children:
RET;TMA

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DLD ALDSW Use this command to load software for the antenna line device (ALD). The ALD
software is provided by the ALD manufacturer.

DSP ALDVER Use this command to query the version information about one or all antenna line
Table 1 Related MML commands

MML Command Function

devices (ALDs). The version information contains the device type, device
model, serial number of the device, software version, hardware version, and
protocol version.

RST ALD Use this command to reset an antenna line device (ALD) or all ALDs connected
to the same port on the RF module.

RST ALDPWRSW Use this command to turn on the antenna line device (ALD) power switch that
has been powered off automatically due to an exception. This command is used
to terminate the self-protection state of the ALD.

SCN ALD Use this command to scan the antenna line devices (ALDs) connected to the
RRU or RFU. This command can also be used to check the serial number of the
device. The scanning result contains the information about all ALDs that are
physically connected to the BS, regardless of whether the ALDs are configured.

STP ALDSCAN Use this command to terminate ongoing scanning of antenna line devices
(ALDs). If no ALD is being scanned, an operation success message is displayed.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Device No. Indicates the device number of the ALD. The device number of the ALD must
be unique.

Actual Vendor Code Indicates the vendor code of the device in the scanning result.

Actual Device Serial Indicates the serial number of the device in the scanning result.
No.

Device Name Indicates the device name of the ALD, which identifies the ALD. It is
recommended that you set the device name in the following format:
sector_device type_network type. The meanings of the parts are as follows:
Sector: indicates the number of the sector. Device type: indicates the type of
currently connected device. It can be SINGLE_RET (Single-antenna Remote
Electrical Tilt Unit), MULTI_RET (Multi-antenna Remote Electrical Tilt Unit),
TMA (Tower-mounted Amplifier). Network type: indicates whether the current
Table 2 Related parameters

Parameter Description

ALD is used for a 2G network or 3G/LTE network. The device name is optional,
but the device name configured for each ALD must be unique.

Control Port Cabinet Indicates the cabinet number of the RRU or RFU that controls the ALD.
No.

Control Port Subrack Indicates the subrack number of the RRU or RFU that controls the ALD.
No.

Control Port Slot No. Indicates the slot number of the RRU or RFU that controls the ALD.

Protocol Version Indicates the actual protocol version of the ALD. NULL means that the protocol
version information fails to be obtained.

Actual Subunit Number Indicates the total number of ALD subunits.

Vendor Code Indicates the vendor code.

Serial No. Indicates the serial number of the ALD. The vendor code and the serial number
uniquely identify an ALD.

Hardware Version Indicates the version information about the ALD hardware.

Software Version Indicates the version information about the ALD software.

Device Model Indicates the device model of the ALD.

Device Type Indicates the device type of the ALD.

Control Port No. Indicates the port number of the RRU or RFU that controls the ALD. It will be
NULL if the RRU or RFU does not support to report this parameter.

5.7.1.6.2.5 ALMPORT
EQUIPMENT
+-CABINET
+-SUBRACK
EQUIPMENT
+-CABINET
+-SUBRACK
+-CCU
+-ALMPORT
EQUIPMENT
+-CABINET
+-SUBRACK
+-TCU
+-ALMPORT
EQUIPMENT
+-CABINET
+-SUBRACK
+-FMU
+-ALMPORT
EQUIPMENT
+-CABINET
+-SUBRACK
+-PEU
+-ALMPORT
EQUIPMENT
+-CABINET
+-SUBRACK
+-UEIU
+-ALMPORT
EQUIPMENT
+-CABINET
+-SUBRACK
+-EMU
+-ALMPORT
EQUIPMENT
+-CABINET
+-SUBRACK
+-PMU
+-ALMPORT
EQUIPMENT
+-CABINET
+-SUBRACK
+-RFU
+-ALMPORT
EQUIPMENT
EQUIPMENT
+-RHUB
+-ALMPORT
EQUIPMENT
+-RRU
+-ALMPORT

Description

An AlmPort MO is used to monitor the environment through external sensors. The alarm ports
are: analog alarm port and digital alarm port. An analog alarm port is used to monitor the
external environment factor in which the change is continuous, and it is supported only by an
EMU. The analog port monitors the current environment factor and compares it with the
configured measurement upper and lower limits and output signal upper and lower limits. A
digital alarm port is used to monitor the external environment factor in which the change is
indicated in Boolean or discrete values. It is contained in the EMU, PMU, TCU, FMU, RRU, and
power boards. The SC48200 PMU and the EPS4815 PMU do not support digital ports.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
CCU;TCU;FMU;PEU;UEIU;EMU;PMU;RFU;RHUB;RRU

Relation with the RRU MO:


- The relationships between the RRU MO and ALMPORT MO are as follows: When RT in
the RRU MO is not set to MPMU or MPRF, the number of ALMPORT MOs must range from 2
to 4.
- The relationships between the RRU MO and ALMPORT MO are as follows: When RT in
the RRU MO is set to MPMU or MPRF, the number of ALMPORT MOs must be 0.
Relation with the CCU MO:
- The number of ALMPORT MOs configured on one CCU MO must be 2.
Relation with the EMU MO:
- The number of ALMPORT MOs configured on one EMU MO must be 36.
Relation with the FMU MO:
- The number of ALMPORT MOs configured on one FMU MO must be greater than or equal
to 0 and smaller than or equal to 4.
Relation with the PEU MO:
- The number of ALMPORT MOs configured on one PEU MO must be 8.
Relation with the PMU MO:
- The number of ALMPORT MOs configured on one PMU MO must be greater than or equal
to 0 and smaller than or equal to 5.
Relation with the RFU MO:
- The number of ALMPORT MOs configured on one RFU MO must be 0.
Relation with the TCU MO:
- The number of ALMPORT MOs configured on one TCU MO must be greater than or equal
to 0 and smaller than or equal to 32.
Relation with the UEIU MO:
- The number of ALMPORT MOs configured on one UEIU MO must be 8.
Relation with the devices:
- The board corresponding to CN, SRN, and SN in the ALMPORT MO must have been
configured and must be one of following ones: PMU, EMU, TCU, FMU, RRU, PEU, UEIU,
and CCU MOs.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST ALMPORT Use this command to list the configuration of an environment signal input port.

SET ALMPORT Use this command to set an environment signal input port.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the board where the port is located.

Subrack No. Indicates the subrack number of the board where the port is located.

Slot No. Indicates the slot number of the board where the port is located.

Port No. Indicates the port number.

Switch Indicates the enabled/disabled state of the port. Alarms can be detected and
reported through the port only when the state of the port is ON.
Table 2 Related parameters

Parameter Description

Alarm ID Indicates the alarm ID bound to the alarm port. This parameter is reported as the
ID of the alarm detected at the port.

Port Type Indicates the alarm port types: analog alarm port and digital alarm port. An
analog alarm port is used to monitor the external environment that changes
continuously. The port is supported only by the EMU. A digital alarm port is
used to monitor the external environment of which the change is indicated in
Boolean or discrete values. It is contained in the EMU, PMU, TCU, FMU, RRU,
CCU, and power boards. The SC48200 PMU and the EPS4815 PMU do not
support digital ports.

Alarm Voltage Indicates the alarm level. This parameter specifies whether alarms generated by
the sensor over the port are in high or low voltage. The alarm level is set
according to the type of external sensor.

Alarm Upper Limit Indicates the alarm upper limit. If the environment measurement value is greater
than the alarm upper limit configured for the sensor, the alarm is reported.
Environment measurement value = Measurement lower limit + (Measurement
upper limit - Measurement lower limit) x (Observed electric current or voltage -
Output lower limit)/(Output upper limit - Output lower limit).Temperature is
measured in the unit of degree Celsius, voltage is measured in the unit of volt,
and current is measured in the unit of milliampere.

Alarm Lower Limit Indicates the alarm lower limit. If the environment measurement value is smaller
than the alarm lower limit configured for the sensor, the alarm is reported.
Environment measurement value = Measurement lower limit + (Measurement
upper limit - Measurement lower limit) x (Observed electric current or voltage -
Output lower limit)/(Output upper limit - Output lower limit).Temperature is
measured in the unit of degree Celsius, voltage is measured in the unit of volt,
and current is measured in the unit of milliampere.

Sensor Type Indicates the sensor type. The user can set the sensor type to current type or
voltage type according to the actual external sensor.

Sensor Measurement Indicates the measurement upper limit of the analog port. The range is set based
Upper Limit
on the actual situations such as the temperature and humidity.Temperature is
measured in the unit of degree Celsius, voltage is measured in the unit of volt,
and current is measured in the unit of milliampere.

Sensor Measurement Indicates the measurement lower limit of the analog port. The range is set based
Lower Limit
on the actual situations such as the temperature and humidity.Temperature is
measured in the unit of degree Celsius, voltage is measured in the unit of volt,
and current is measured in the unit of milliampere.
Table 2 Related parameters

Parameter Description

Sensor Output Upper Indicates the upper limit of the output signals from the analog port. For sensors
Limit
of either the current type or voltage type, the upper limit should be set according
to the specifications of the sensor.

Sensor Output Lower Indicates the lower limit of the output signals from the analog port. For sensors
Limit
of either the current type or voltage type, the lower limit should be set according
to the specifications of the sensor.

5.7.1.6.2.6 ANTENNAPORT
EQUIPMENT
+-CABINET
+-SUBRACK
EQUIPMENT
+-CABINET
+-SUBRACK
+-RFU
+-ANTENNAPORT
EQUIPMENT
+-RRU
+-ANTENNAPORT

Description

An AntennaPort MO is an antenna port that is located on an RRU or RFU and connected to a


feeder. The antenna port labeled R0A also serves as an antenna control port.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
RFU;RRU

Relation with the RRU MO:


- When RT in an RRU MO is set to MPMU, the number of ANTENNAPORT MOs must be
0.
- When RT in an RRU MO is set to MPRF, the number of ANTENNAPORT MOs must be 2.
- When RT in an RRU MO is not set to MPMU, the number of ANTENNAPORT MOs must
range from 1 to 8.
Relation with the RFU MO:
- The number of ANTENNAPORT MOs configured on one RFU MO must be greater than or
equal to 1 and smaller than or equal to 8.
Relation with the RRU and RFU MOs:
- The RRU or RFU MO corresponding to CN, SRN, and SN in the ANTENNAPORT MO
must have been configured.
Relation with the RETSUBUNIT MO:
- One of the following ANTENNAPORT MOs must have been configured: 1. An
ANTENNAPORT MO corresponding to CONNCN1, CONNSRN1, CONNSN1, and
CONNPN1 in the RETSUBUNIT MO. 2. An ANTENNAPORT MO corresponding to
CONNCN2, CONNSRN2, CONNSN2, and CONNPN2 in the RETSUBUNIT MO.
Relation with the TMASUBUNIT MO:
- The ANTENNAPORT MO corresponding to CONNCN, CONNSRN, CONNSN, and
CONNPN in the TMASUBUNIT MO must have been configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP ANTENNAPORT Use this command to query the dynamic information about an antenna port
(ANTENNAPORT).

LST ANTENNAPORT Use this command to list the configuration of the antenna port
(ANTENNAPORT).

MOD ANTENNAPORT Use this command to modify the configuration of an antenna port
(ANTENNAPORT).

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the RRU or RFU where the antenna port is
located.

Subrack No. Indicates the subrack number of the RRU or RFU where the antenna port is
located.

Slot No. Indicates the slot number of the RRU or RFU where the antenna port is located.

Antenna Port No. Indicates the number of the antenna port on the RRU or RFU.For the RRU that
works in TDD mode and has eight channels to be connected to the antenna, the
service channels are ANT1 to ANT8 and the corresponding ports on the antenna
are R0A to R0H.
For the RRU that works in TDD mode and does not have eight channels or the
RRU that works in FDD mode, the service channels are named from ANT0 and
the corresponding port on the antenna is R0A.

Feeder Length Indicates the length of the feeder at the antenna port.

DL Time Delay Indicates the downlink delay of the antenna, that is, the propagation delay from
the output port of an RF unit to the antenna port. If no TMA is configured, this
parameter is set to the propagation delay of the feeder. If the TMA is configured,
the parameter also includes the delay of the TMA. This parameter does not need
to be specified when non-bidirectional channels are used.

UL Time Delay Indicates the uplink delay of the antenna, that is, the propagation delay from the
antenna port to the input port of an RF unit. If no TMA is configured, this
parameter is set to the propagation delay of the feeder. If the TMA is configured,
the parameter also includes the delay of the TMA.

ALD Power Switch Indicates the state of the ALD power supply switch. The ALD power supply
switches for the SINGLE_RET (Single-antenna Remote Electrical Tilt),
MULTI_RET (Multi-antenna Remote Electrical Tilt), STMA (Smart Tower-
mounted Amplifier)must be set to ON. In actual running, the RRU/RFU
automatically sets this switch to OFF for an Antenna port when the ALM-26530
RF Module ALD Current Abnormal alarm is reported due to overcurrent,
overcurrent protection, or undercurrent protection (the RRU/RFU supports
undercurrent protection and Low Current Protect Switch is set to ON for the
RRU/RFU) on the Antenna port. For details, see ALM-26530 RF Module ALD
Current Abnormal.

Current Alarm Indicates the type of the ALD current alarm threshold. The current alarm
Threshold Type
thresholds for ALDs (excluding user-defined ALDs) must be selected according
to the ALD type and connection mode. For 12 dB non-AISG TMAs only: the
Undercurrent Alarm Occur Threshold is 30 mA, the Undercurrent Alarm Clear
Table 2 Related parameters

Parameter Description

Threshold is 40 mA, the Overcurrent Occur Alarm Threshold is 170 mA, and the
Overcurrent Alarm Clear Threshold is 150 mA. For 24 dB non-AISG TMAs
only: the Undercurrent Alarm Occur Threshold is 40 mA, the Undercurrent
Alarm Clear Threshold is 60 mA, the Overcurrent Occur Alarm Threshold is 310
mA, and the Overcurrent Alarm Clear Threshold is 280 mA. For RET (coaxial)
only: the Undercurrent Alarm Occur Threshold is 25 mA, the Undercurrent
Alarm Clear Threshold is 33 mA, the Overcurrent Occur Alarm Threshold is 150
mA, and the Overcurrent Alarm Clear Threshold is 120 mA. For 12 dB TMA
and RET or 12 dB TMA (AISG) only: the Undercurrent Alarm Occur Threshold
is 30 mA, the Undercurrent Alarm Clear Threshold is 40 mA, the Overcurrent
Occur Alarm Threshold is 450 mA, and the Overcurrent Alarm Clear Threshold
is 400 mA. For 24 dB TMA and RET or 24 dB TMA (AISG) only: the
Undercurrent Alarm Occur Threshold is 40 mA, the Undercurrent Alarm Clear
Threshold is 60 mA, the Overcurrent Occur Alarm Threshold is 850 mA, and the
Overcurrent Alarm Clear Threshold is 750 mA. This parameter can be set to
UER_SELF_DEFINE, TMA12DB_ONLY_NON_AISG,
TMA24DB_ONLY_NON_AISG, RET_ONLY_COAXIAL, TMA12DB_AISG,
or TMA24DB_AISG.

Undercurrent Alarm Indicates the undercurrent alarm occur threshold. When the ALD current value
Occur Threshold
is smaller than this threshold, an ALM-26530 RF Module ALD Current
Abnormal alarm is reported. The specific problem is undercurrent.

Undercurrent Alarm Indicates the undercurrent alarm clear threshold. When the ALD current value is
Clear Threshold
greater than this threshold, the ALM-26530 RF Module ALD Current Abnormal
alarm is cleared.

Overcurrent Alarm Indicates the overcurrent alarm occur threshold. When the ALD current value is
Occur Threshold
greater than this threshold, an ALM-26530 RF Module ALD Current Abnormal
alarm is reported. The specific problem is overcurrent. When the overcurrent
alarm occur threshold is lower than the maximum current supported by the
hardware, the overcurrent alarm occur threshold prevails. When the overcurrent
alarm occur threshold is higher than the maximum current supported by the
hardware, the maximum current supported by the hardware serves as the
overcurrent alarm occur threshold.

Overcurrent Alarm Indicates the overcurrent alarm clear threshold. When the overcurrent alarm
Clear Threshold
clear threshold is lower than the maximum current supported by the hardware,
the overcurrent alarm clear threshold prevails. When the ALD current value is
lower than this threshold, ALM-26530 RF Module ALD Current Abnormal is
cleared.When the overcurrent alarm clear threshold is higher than the maximum
current supported by the hardware, the maximum current supported by the
hardware serves as the overcurrent alarm clear threshold. When the ALD current
value is lower than the maximum current supported by the hardware, ALM-
Table 2 Related parameters

Parameter Description

26530 RF Module ALD Current Abnormal is cleared.

ALD Current Value Indicates the present value of the current of the ALD.

ALD Actual Power Indicates the actual status of the ALD power supply switch.
Switch

5.7.1.6.2.7 APPLICATION
+-NE
+-NODE
+-APPLICATION

Description

An application provides the operating environment for the functions of a BTS, NodeB, or
eNodeB. If an MBTS needs to provide functions of a certain standard, operators need to add an
application for the standard. For example, if LTE is added to an MBTS after evolution, operators
need to add an application for the eNodeB.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
NODE

Relation with the APPLICATION MO:


- It is not allowed to add or rmv app when PRODUCTTYPE is
DBS3900,BTS3900,BTS3900A,BTS3900L or BTS3900AL and WM is NON-CONCURRENT

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

DSP APP Use this command to query information about applications running on the BS.

RST APP Use this command to restart an application based on a specified application ID.
An application provides the operating environment for the functions of a base
station of a certain standard. When an application cannot work properly, the base
station can reset the application to restore the functions provided by the
application.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Application ID Indicates the application ID.

Application Type Indicates the application type.

Application Name Indicates the application name.

Application State Indicates the application status.

Software Version Indicates the application software version.

5.7.1.6.2.8 BASEBANDEQM
+-NE
+-NODE
+-CARRIERRESOURCE
+-BASEBANDEQM

Description

Baseband equipment is a set of baseband processing units, which are classified into three types:
uplink, downlink, and uplink and downlink combined.
Effective Scenario

Immediately

Relations Between MOs

Possible parents:
CARRIERRESOURCE

Relation with the BASEBANDEQM MO:


- When BASEBANDEQMTYPE in a BASEBANDEQM MO is set to UL or ULDL, the MO
cannot be configured across subracks.
- When BASEBANDEQMTYPE in a BASEBANDEQM MO is set to DL, the MO supports
a maximum of 12 baseband processing units.
- A baseband processing unit can be added to a maximum of two pieces of baseband
equipment (either uplink baseband equipment or uplink and downlink combined baseband
equipment) that have uplink processing capabilities.
- A baseband processing unit can be added to only one set of baseband equipment (either
downlink baseband equipment or uplink and downlink combined baseband equipment) that has
downlink processing capabilities.
- The baseband equipment number of a BASEBANDEQM MO whose
BASEBANDEQMTYPE is set to ULDL must differ from the baseband equipment number of a
BASEBANDEQM MO whose BASEBANDEQMTYPE is set to UL or DL.
- A BASEBANDEQM MO must be configured with at least one baseband processing unit.
- A maximum of 24 sets of baseband equipment that is capable of processing uplink services
can be configured.
- A maximum of 12 sets of baseband equipment that is capable of processing downlink
services can be configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD BASEBANDEQM Use this command to add a set of uplink, downlink, or uplink and downlink
baseband equipment. Baseband processing units are added with the baseband
equipment.

LST BASEBANDEQM Use this command to list the configuration of baseband equipment.
Table 1 Related MML commands

MML Command Function

MOD BASEBANDEQM Use this command to modify a set of specified baseband equipment, including
adding or removing a baseband processing unit.

RMV BASEBANDEQM Use this command to remove baseband equipment.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Baseband Equipment Indicates the number of the baseband equipment.


ID

Baseband Equipment Indicates the type of baseband equipment.


Type

UMTS UL Indicates the demodulation mode of an uplink baseband signaling processing


Demodulation Mode
equipment for UMTS. For a newly added uplink baseband signaling processing
board, the demodulation mode must be specified. Different sets of uplink
baseband signaling processing board can have different demodulation modes.
This parameter cannot be set to NULL(Null) in UMTS mode. In other modes,
this parameter is invalid and should be set to NULL(Null).

Baseband Equipment Indicates the information about the baseband equipment board.
Board

5.7.1.6.2.9 BATCTPA
EQUIPMENT
+-CABINET
+-SUBRACK
+-PMU
+-BATTERY
+-BATCTPA

Description
A BatCTPa MO consists of parameters related to the battery capacity test. When a Battery MO is
created, its corresponding BatCTPa MO is created automatically. Whereas, the corresponding
BatCTPa MO is not created automatically when a Battery MO for the SC48200 PMU is created.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
BATTERY

Relation with the BATTERY MO:


- In a PMU MO, if PTYPE is set to a value other than SC48200, and the BATTERY MO
managed by the PMU MO is configured, a BATCTPA MO must also be configured. CN, SRN,
and SN in this BATTERY MO must be the same as CN, SRN, and SN respectively in the
BATCTPA MO.
- The number of BATCTPA MOs configured on one BATTERY MO must be greater than or
equal to 0 and smaller than or equal to 1.
Relation with the PMU MO:
- If PTYPE in a PMU MO is set to SC48200, a BATCTPA MO corresponding to CN, SRN,
and SN in the PMU MO cannot be configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP BATTR Use this command to query the test result of a specified battery.

LST BATCTPA Use this command to list the configuration of parameters used for a battery
capacity test.

MOD BATCTPA Use this command to modify the battery capacity test parameters.

STP BATTST Use this command to stop the ongoing battery test, which can be a test launched
by users, a scheduled test launched by the power monitoring unit (PMU), or an
automatic power-off test.

STR BATTST Use this command to start the battery test immediately. The main purpose of the
Table 1 Related MML commands

MML Command Function

battery test is to test the capacity of the battery and to judge the quality of the
battery based on the capacity.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet where the PMU managing the battery is
located.

Subrack No. Indicates the number of the subrack where the PMU managing the battery is
located.

Slot No. Indicates the number of the slot where the PMU managing the battery is located.

0.05C10 Discharge Indicates the duration of discharging the battery with the current of 0.05C10 to
Time
the moment when the discharging voltage is terminated. C10 indicates the
nominal capacity of the battery, and 0.05C10 indicates that the battery is
discharged with the current of 0.05 x norminal capacity of the battery. For
example, if the battery capacity is 100 AH, 0.05C10 indicates that the battery is
discharged with the current of 5 AH.

0.1C10 Discharge Time Indicates the duration of discharging the battery with the current of 0.1C10 to
the moment when the discharging voltage is terminated. C10 indicates the
nominal capacity of the battery, and 0.1C10 indicates that the battery is
discharged with the current of 0.1 x norminal capacity of the battery. For
example, if the battery capacity is 100 AH, 0.1C10 indicates that the battery is
discharged with the current of 10 AH.

0.2C10 Discharge Time Indicates the duration of discharging the battery with the current of 0.2C10 to
the moment when the discharging voltage is terminated. C10 indicates the
nominal capacity of the battery, and 0.2C10 indicates that the battery is
discharged with the current of 0.2 x norminal capacity of the battery. For
example, if the battery capacity is 100 AH, 0.2C10 indicates that the battery is
discharged with the current of 20 AH.

0.3C10 Discharge Time Indicates the duration of discharging the battery with the current of 0.3C10 to
Table 2 Related parameters

Parameter Description

the moment when the discharging voltage is terminated. C10 indicates the
nominal capacity of the battery, and 0.3C10 indicates that the battery is
discharged with the current of 0.3 x nominal capacity of the battery. For
example, if the battery capacity is 100 AH, 0.3C10 indicates that the battery is
discharged with the current of 30 AH.

0.4C10 Discharge Time Indicates the duration of discharging the battery with the current of 0.4C10 to
the moment when the discharging voltage is terminated. C10 indicates the
nominal capacity of the battery, and 0.4C10 indicates that the battery is
discharged with the current of 0.4 x nominal capacity of the battery. For
example, if the battery capacity is 100 AH, 0.4C10 indicates that the battery is
discharged with the current of 40 AH.

0.5C10 Discharge Time Indicates the duration of discharging the battery with the current x 0.5C10 to the
moment when the discharging voltage is terminated. C10 indicates the nominal
capacity of the battery, and 0.5C10 indicates that the battery is discharged with
the current of 0.5 x nominal capacity of the battery. For example, if the battery
capacity is 100 AH, 0.5C10 indicates that the battery is discharged with the
current of 50 AH.

0.6C10 Discharge Time Indicates the duration of discharging the battery with the current of 0.6C10 to
the moment when the discharging voltage is terminated. C10 indicates the
nominal capacity of the battery, and 0.6C10 indicates that the battery is
discharged with the current of 0.6 x nominal capacity of the battery. For
example, if the battery capacity is 100 AH, 0.6C10 indicates that the battery is
discharged with the current of 60 AH.

0.7C10 Discharge Time Indicates the duration of discharging the battery with the current of 0.7C10 to
the moment when the discharging voltage is terminated. C10 indicates the
nominal capacity of the battery, and 0.7C10 indicates that the battery is
discharged with the current of 0.7 x nominal capacity of the battery. For
example, if the battery capacity is 100 AH, 0.7C10 indicates that the battery is
discharged with the current of 70 AH.

0.8C10 Discharge Time Indicates the duration of discharging the battery with the current of 0.8C10 to
the moment when the discharging voltage is terminated. C10 indicates the
nominal capacity of the battery, and 0.8C10 indicates that the battery is
discharged with the current of 0.8 x nominal capacity of the battery. For
example, if the battery capacity is 100 AH, 0.8C10 indicates that the battery is
discharged with the current of 80 AH.

0.9C10 Discharge Time Indicates the duration of discharging the battery with the current of 0.9C10 to
the moment when the discharging voltage is terminated. C10 indicates the
nominal capacity of the battery, and 0.9C10 indicates that the battery is
Table 2 Related parameters

Parameter Description

discharged with the current of 0.9 x nominal capacity of the battery. For
example, if the battery capacity is 100 AH, 0.9C10 indicates that the battery is
discharged with the current of 90 AH.

Battery Charge Indicates the charging efficiency of batteries. The battery efficiency is a
Efficiency
percentage of battery performance to the normal battery capacity. For example, a
normal battery can supply power for 10 hours. If a battery can supply power for
only eight hours, its battery efficiency is 80%.

Discharge Test End Indicates the end voltage of the discharging test.
Voltage

Battery Number Indicates the quantity of battery in the battery group.

Discharge Test Time Indicates the time limit of the discharging test.
Limit

Simple Discharge Test Indicates the time limit for the simplified discharging test. There are two types
Time Limit
of discharging tests for a battery: a standard test and a simplified test. A standard
test calculates the battery efficiency, and a simplified test judges only the quality
of the battery.

Simple Discharge Test Indicates the end voltage of the simple discharging test.
End Voltage

Automatic Test Mode Indicates the test mode. It specifies whether to use the automatic test and which
automatic test mode is used. There are four types of test modes: NOAUTOTEST
(No Auto Test), PERIOD (Period Auto Test), POWERCUT (Power Off Auto
Test), and PERIODPOWERCUT (Period and Power Off Auto Test). No Auto
Test: indicates that the battery test is launched and controlled by the user. Period
Auto Test: indicates that the battery test is launched automatically by the system
as scheduled. Power Off Auto Test: indicates that the battery test is launched
automatically by the system after the AC power supply is cut off.

Timing Discharge Test Indicates the time limit of the scheduled discharging test.
Time

Delayed Discharge Test Indicates the time limit for the discharging test delay when the power is off or
Time
the discharging test is launched automatically. The interval between two battery
tests must be greater than this time limit. Otherwise, the execution of the STR
BATTST command fails.

Battery Efficency Indicates the battery efficiency. The battery is normal when the result is between
80% and 100%.

Discharge Last Time Indicates the continued discharge duration of the battery.
Table 2 Related parameters

Parameter Description

Discharge End Voltage Indicates the voltage of the battery when the discharge is ended.

Discharge Average Indicates the average current in the process of the battery discharge.
Current

Discharge AH Indicates the accumulated discharged power (Ah) from the beginning of
discharge.

Battery Temperature Indicates the current temperature of the battery.

5.7.1.6.2.10 BATTERY
EQUIPMENT
+-CABINET
+-SUBRACK
+-PMU
+-BATTERY
+-BATCTPA[0~1]

Description

A Battery MO provides backup power for the BS when the mains is cut off.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
PMU

Possible children:
BATCTPA[0~1]

Relation with the PMU MO:


- The upper-level PMU MO of the BATTERY MO must have been configured.
- The number of BATTERY MOs configured on one PMU MO must be greater than or equal
to 0 and smaller than or equal to 1.
Relation with the BATTERY MO:
- When PTYPE in the PMU MO is set to SC48200, the BATTERY MO corresponding to the
PMU MO must have been configured.
Relation with the BATCTPA MO:
- If PTYPE in the upper-level PMU MO of the BATTERY MO is set to a value other than
SC48200, both the BATTERY and BATCTPA MOs must be configured.
- The number of BATCTPA MOs configured on one BATTERY MO must be greater than or
equal to 0 and smaller than or equal to 1.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD BATTERY Use this command to add a battery. When an SC48200 power monitoring unit
(PMU) is added, batteries are configured automatically by default. Manual
configuration of batteries is not allowed. Batteries are optional. When non-
SC48200 types of PMU are added, batteries are not configured by default.

DSP BATINDT Use this command to query the installation date of a battery.

DSP BATTERY Use this command to query the dynamic information about a battery.

LST BATTERY Use this command to list the configuration of a battery.

MOD BATINDT Use this command to modify the installation date of the battery.

MOD BATTERY Use this command to modify the configuration of a battery.

RMV BATTERY Use this command to remove a battery.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet where the PMU managing the battery is
located.

Subrack No. Indicates the number of the subrack where the PMU managing the battery is
located.

Slot No. Indicates the number of the slot where the PMU managing the battery is located.

Installation Type Indicates the installation type of battery. This parameter can be set to INNER or
OUTER. The value INNER indicates that batteries are installed in a power
cabinet. The value OUTER indicates that batteries are installed in a standalone
battery cabinet. For lithium batteries, this parameter is set to INNER. For lead-
acid batteries, this parameter can be set to either INNER or OUTER, depending
on the type of power cabinet. If the power cabinet is APM30 of version 301
(silkscreen: APM30) or 302 (silkscreen: APM30H), this parameter is set as
required. If the power cabinet is not APM30 of version 301 or 302, this
parameter is set to INNER. The reasons are as follows: In an APM30 of version
301 or 302, the battery temperature sensor is connected to different ports on the
APMI board by the battery temperature sensor cable, depending on the
installation type of lead-acid battery. When the installation type is INNER, the
battery temperature sensor is connected to the BAT_TEM1 port. When the
installation type is OUTER, the battery temperature sensor is connected to the
BAT_TEM2 port. The configuration data on the maintenance console must be
set based on the actual installation, enabling the PMU to select the correct port
for battery temperature management. In power cabinets other than APM30s of
versions 301 and 302, the battery temperature is reported to the PMU through
the RS485 bus. Under this circumstance, the PMU can always select the correct
battery temperature for temperature management. This parameter is set to
INNER to avoid a configuration conflict between different modes of a multi-
mode base station.

Boost-Charging Indicates the scheduled boost charging interval. Batteries are boost-charged at
Duration
this interval (in the unit of day), which keeps the batteries fully charged. This
parameter is configured according to the instructions provided by manufacturers.

Boost-Charging Voltage Indicates the boost charging voltage. Boost charge is used to quickly recover the
capacity of batteries. During the boost charge, the charging voltage is relatively
high. After the batteries are discharged, the system automatically starts boost
charge on the batteries. This parameter is configured according to the
instructions provided by manufacturers.

Battery 1 Capacity Indicates the capacity of battery 1. This parameter should be set according to the
actual situation. Incorrect configuration may reduce the life span of the battery.
Table 2 Related parameters

Parameter Description

Battery Current Limiting Indicates the battery charging current limiting coefficient. Charging coefficient x
Coefficient
Storage capacity = Maximum charging current. When the charging current is not
smaller than the maximum charging current plus 5 A, an ALM-25625 Battery
Current Abnormal alarm is reported. This parameter is configured according to
the instructions provided by manufacturers.

Float-Charging Voltage Indicates the floating charging voltage. Floating charge is used to compensate
for the power loss of the batteries due to self-discharge. The floating charging
voltage is lower than the boost charging voltage. This parameter is configured
according to the instructions provided by manufacturers.

High Temperature Indicates whether to enable battery disconnection against high temperature.
Shutdown Flag

Shutdown Temperature Indicates the temperature above which the battery is powered off automatically
under the condition that HtempShutdownFlg is enabled.

Low Voltage Shutdown Indicates whether to enable battery power-off against low voltage.
Flag

Shutdown Voltage Indicates the voltage below which the battery is powered off automatically under
the condition that LvolShutdownFlg is enabled.

Temperature Indicates the increased or reduced charging voltage of every battery when the
Compensation
Coefficient ambient temperature is 1 degree Celsius (2 degree Fahrenheit) higher or lower
than the standard temperature specified by manufacturers. This parameter should
be set according to the instructions provided by manufacturers.

Temperature Alarm Indicates the lower limit of temperature. When the battery temperature is below
Lower Threshold
the lower limit, an ALM-25650 Environmental Temperature Abnormal alarm is
reported.

Temperature Alarm Indicates the upper limit of temperature. When the battery temperature exceeds
Upper Threshold
the upper limit, an ALM-25650 Environmental Temperature Abnormal alarm is
reported.

Battery Number Indicates the number of battery groups.

Battery Type Indicates the type of the battery.

Power Cut Times Indicates the number of times that the battery is powered off.

Charge Times In Half Indicates the number of times that the battery is charged in half an hour.
an Hour

Charge Times In 1 Hour Indicates the number of times that the battery is charged when the battery is
Table 2 Related parameters

Parameter Description

charged for more than half an hour and less than one hour or for one hour.

Charge Times In 2 Indicates the number of times that the battery is charged when the battery is
Hours
charged for more than one hour and less than two hours or for two hours.

Charge Times In 3 Indicates the number of times that the battery is charged when the battery is
Hours
charged for more than two hours and less than three hours or for three hours.

Charge Times In 4 Indicates the number of times that the battery is charged when the battery is
Hours
charged for more than three hours and less than four hours or for four hours.

Charge Times In 5 Indicates the number of times that the battery is charged when the battery is
Hours
charged for more than four hours and less than five hours or for five hours.

Charge Times In 6 Indicates the number of times that the battery is charged when the battery is
Hours
charged for more than five hours and less than six hours or for six hours.

Charge Times In 7 Indicates the number of times that the battery is charged when the battery is
Hours
charged for more than six hours and less than seven hours or for seven hours.

Charge Times In 8 Indicates the number of times that the battery is charged when the battery is
Hours
charged for more than seven hours and less than eight hours or for eight hours.

Charge Times In More Indicates the number of times that the battery is charged in more than eight
than 8 Hours
hours.

Discharge Times In Half Indicates the number of times that the battery is discharged in half an hour.
an Hour

Discharge Times In 1 Indicates the number of times that the battery is discharged when the battery is
Hour
discharged for more than half an hour and less than one hour or for one hour.

Discharge Times In 2 Indicates the number of times that the battery is discharged when the battery is
Hours
discharged for more than one hour and less than two hours or for two hours.

Discharge Times In 3 Indicates the number of times that the battery is discharged when the battery is
Hours
discharged for more than two hours and less than three hours or for three hours.

Discharge Times In 4 Indicates the number of times that the battery is discharged when the battery is
Hours
discharged for more than three hours and less than four hours or for four hours.

Discharge Times In 5 Indicates the number of times that the battery is discharged when the battery is
Hours
discharged for more than four hours and less than five hours or for five hours.
Table 2 Related parameters

Parameter Description

Discharge Times In 6 Indicates the number of times that the battery is discharged when the battery is
Hours
discharged for more than five hours and less than six hours or for six hours.

Discharge Times In 7 Indicates the number of times that the battery is discharged when the battery is
Hours
discharged for more than six hours and less than seven hours or for seven hours.

Discharge Times In 8 Indicates the number of times that the battery is discharged when the battery is
Hours
discharged for more than seven hours and less than eight hours or for eight
hours.

Discharge Times In Indicates the number of times that the battery is discharged in more than eight
More than 8 Hours
hours.

Installation Date Indicates the date when the battery is installed. The scheduled tests for the
battery are dependent on the installation date.

Battery 2 Capacity Indicates the capacity of battery 2. This parameter should be set according to the
actual situation. Incorrect configuration may reduce the life span of the battery.

5.7.1.6.2.11 BBP
EQUIPMENT
+-CABINET
+-SUBRACK
+-BBP
+-CPRIPORT[6~6]
+-SFP[6~6]
+-CASCADEPORT[1~1]

Description

The BBP MO is the baseband processing board that processes signals over the ports of the
baseband module and the RF module and also processes the UL and DL baseband signals.

Effective Scenario

Immediately
Relations Between MOs

Base class:
RU

Possible parents:
SUBRACK

Possible children:
CPRIPORT[6~6];SFP[6~6];CASCADEPORT[1~1]

Relation with the BBPLINK MO:


- HCN, HSRN, HSN, HPN and TCN, TSRN, TSN, TPN in the BBPLINK corresponding to
BBP must exit.
Relation with the BRI,GTMU,RHUB,RRUCHAIN MOs:
- When the RRUCHAIN MO whose AT is set to a value other than PEERPORT, one of the
following BBP, BRI , GTMU or RHUB MOs must have been configured:
- 1. A BBP, BRI, GTMU or RHUB MO corresponding to HCN, HSRN, and HSN.
- 2. A BBP, BRI, GTMU or RHUB MO corresponding to TCN, TSRN, and TSN in the
RRUCHAIN MO when TT in the RRUCHAIN MO is set to a value other than CHAIN.
Relation with other boards in the BBU subrack:
- A unique combination is necessary for the following parameters: 1. CN, SRN, and SN in the
BBP MO; 2. CN, SRN, and SN in the TRP MO;3. CN, SRN, and SN in the UCIU MO; 4. CN,
SRN, and SN in the USCU MO; 5. CN, SRN, and SN in the BRI.
Relation with the SUBRACK MO:
- The number of BBP MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 6.
Relation with the CASCADEPORT MO:
- When the combination of CN, SRN and SN in the CASCADEPORT MO is same as the
combination of CN, SRN and SN in the BBP MO, the PT of CASCADEPORT must be set to
ExpandedCascadePort.
Relation with the RRUCHAIN,BRI,GTMU MOs:
- In the RRUCHAIN MO, when TT is set to RING and the combination of HCN, HSRN, and
HSN is not the same as the combination of TCN, TSRN, and TSN, this RRUCHAIN cannot be
configured on the BRI, GTMU, or BBP with TYPE set to GBBP.
- When the TT in the RRUCHAIN MO is set to LOADBALANCE, the total number of BBP
MO with the TYPE set to GBBP, BRI MO, and GTMU MO where the RRUCHAIN MO is
configured must be 0 or 1.
Relation with the RRUCHAIN MO:
- In the RRUCHAIN MO, when TT is set to RING and the combination
- of HCN, HSRN, and HSN is not the same as the combination
- of TCN, TSRN, and TSN,
- the TYPE of BBP MO where the RRUCHAIN MO is configured is the same or the TYPE
of one BBP MO is UBBP.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP BBPTC Use this command to query the traffic that can be carried by a baseband board.

LST BBP Use this command to list the configurations of baseband processing boards.

MOD BBP Use this command to modify the configuration of a baseband processing board
(BBP).

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the baseband processing board.

Subrack No. Indicates the subrack number of the baseband processing board.

Slot No. Indicates the slot number of the baseband processing board.

Board Type Indicates the type of the board.

Work Mode Indicates the working mode of the baseband processing board. There are seven
working modes: FDD, TDD, HYBRID, TDD_ENHANCE, TDD_8T8R,
TDD_TL and FDD_ATG. The Frequency Division Duplex (FDD) mode carries
the traditional voice and data services. TDD is short for Time Division Duplex.
The HYBRID mode is a combination of FDD and IMB modes. In Integrated
Mobile Broadcasting (IMB) mode, the baseband processing board carries the
mobile TV services. The value TDD_ENHANCE indicates the TDD mode
integrated with the BeamForming (BF) function. The BF function provides the
Table 2 Related parameters

Parameter Description

data transmission service in transmission modes 7 and 8 defined in protocols.


For details, see 3GPP TS 36.213. In TDD_8T8R mode, the baseband processing
board supports TD-LTE single-mode 8T8R. In addition, the baseband processing
board supports the BF function and CPRI specifications are applied between the
BBU and RRU. In TDD_TL mode, the baseband processing board supports the
TD-LTE&TDS-CDMA dual mode and the TD-LTE single mode. In addition, the
baseband processing board supports 8T8R BF and 2T2R Multiple-Input
Multiple-Output (MIMO) and CMCC TD-LTE IR specifications are applied
between the BBU and RRU. In FDD_ATG mode, the baseband processing board
supports communication between Air and Ground. The FDD_ATG mode applies
only to communication between air and ground.

Administrative state Indicates the administrative state of the board. The administrative state of the
board can be locked, unlocked, or shutting down. For details, see ITU-T X.731.

Duration of the shutting Indicates the scheduled duration before a board is blocked.
down state

Block Type Indicates the block type of the board. IMMEDIATE (Immediate) means that the
board is blocked and services carried on the board are interrupted immediately
after the command is executed. SHUTDOWN (Shutdown) means that the board
is blocked when no service is carried on the board. DELAY (Delay) means that
the board is blocked and services carried by the board are interrupted after a
scheduled duration.

Hardware Capacity Indicates the hardware capabilities of a baseband processing board. This
Enhance
parameter is controlled by a license control item and is customized for a specific
operator. For other operators, this parameter is invalid and the hardware
capabilities of a baseband processing board are consistent with the hardware
specifications of this board.

CPRI Extension Indicates the CPRI extension switch of a BBP. The transmission capability of a
fiber optic cable is improved when this parameter is set to ON. Only LBBPd
supports this parameter.The BBP is reset after the parameter is modified.

Base Band Work Indicates the modes for which the UBBP provides baseband processing
Standard
resources. This parameter is valid only for a UBBP. For a non-UBBP board, this
parameter is set to NULL by default.

BBP Capacity Indicates the BBP capability. If NULL is displayed, the BBP capability fails to
be queried.

Alarm Status(from RU) Indicates the alarm status of the board. The alarm state of the board can be
normal, warning, minor or critical. For details about the definition of Alarm
Table 2 Related parameters

Parameter Description

Status, see ITU-T X.731.

Operational State(from Indicates the operational state of the board, which can be set to Enabled or
RU)
Disabled. Enabled indicates that services can be carried on the board. Disabled
indicates that no service can be carried on the board.

Availability Status(from Indicates the physical operation status of the board, which can be Uninstalled,
RU)
Starting up, Normal, Inconsistent, Unconfigured, Power off, Fault,
Communication lost, In test, or the combination of various states. For example,
if a board is not configured and fails to communicate with the main control and
transmission board, the physical operation status of the board is Unconfigured,
Communication lost.

Electronic Label(from Indicates the E-label, a text file with a maximum of 2 KB. It is used to record the
RU)
manufacturing information about equipment such as the board, sub-board, or
optical module. Among board properties displayed in the text file, "BoardType"
indicates the type of the board, "BarCode" indicates the bar code of the board
and is the same as the code labeled on the board, and "Item" indicates the BOM
code.

Type(from RU) Indicates the type of the board.

Serial Number(from Indicates the bar code of the board or the cabinet.
RU)

Description(from RU) Indicates the description about the services and functions provided by the board
or the cabinet.

Date of Indicates the manufacturing date of the board or the cabinet.


Manufacture(from RU)

Vendor(from RU) Indicates the manufacturer of the board or the cabinet.

Issue Number(from RU) Indicates the issue number of the board.

Config Type(from RU) Indicates the type of a board.

Board Indicates the temperature of a board.


Temperature(from RU)

HPA Temperature(from Indicates the temperature of the power amplifier.


RU)

DEVTYPE(from RU) Indicates the type of the device.

Software Version(from Indicates the software version of the board.


RU)
Table 2 Related parameters

Parameter Description

Hardware Version(from Indicates the hardware version of the board.


RU)

BootRom Version(from Indicates the BootROM version of the board.


RU)

5.7.1.6.2.12 BBPLINK
EQUIPMENT
+-BBPLINK

Description

The BBPLINK MO manages the interconnection links between the interconnected baseband
processing boards of BBUs.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
EQUIPMENT

Relation with the BBP MO:


- HCN, HSRN, HSN, HPN and TCN, TSRN, TSN, TPN in the BBPLINK corresponding to
BBP must exit.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD BBPLNK Use this command to add a baseband processing link. The baseband processing
Table 1 Related MML commands

MML Command Function

link is a logical concept. The physical entity of the interconnection link is the
topology between the interconnected baseband processing boards of BBUs.

DSP BBPLNK Use this command to query the actual information of a baseband processing
link.

LST BBPLNK Use this command to list the configuration of a baseband processing link.

MOD BBPLNK Use this command to modify the configuration of a baseband processing link.

RMV BBPLNK Use this command to delete a baseband processing link.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Link No. Indicates the number of the interconnection link.

Head Cabinet No. Indicates the cabinet number of the head node at one end of the interconnection
link.

Head Subrack No. Indicates the subrack number of the head node at one end of the interconnection
link.

Head Slot No. Indicates the slot number of the head node at one end of the interconnection link.

Head Port No. Indicates the port number of the head node at the other end of the
interconnection link. This port indicates the port HEI on the board panel.

Tail Cabinet No. Indicates the cabinet number of the tail node at one end of the interconnection
link.

Tail Subrack No. Indicates the subrack number of the tail node at one end of the interconnection
link.

Tail Slot No. Indicates the slot number of the tail node at one end of the interconnection link.
Table 2 Related parameters

Parameter Description

Tail Port No. Indicates the port number of the tail node at one end of the interconnection link.
This port indicates the port HEI on the board panel.

CPRI Line Bit Rate Indicates the transmission rate of the Common Public Radio Interface (CPRI).
The parameter value NULL indicates that no CPRI rate is queried.

Cabinet No. Indicates the cabinet number of the local node at one end of the interconnection
link.

Subrack No. Indicates the subrack number of the local node at one end of the interconnection
link.

Slot No. Indicates the slot number of the local node at one end of the interconnection
link.

Port No. Indicates the port number of the local node at one end of the interconnection
link. This port indicates the port HEI on the board panel.

Peer Cabinet No. Indicates the cabinet number of the peer node at one end of the interconnection
link. This parameter is set to NULL when there is no physical connection.

Peer Subrack No. Indicates the subrack number of the peer node at one end of the interconnection
link. This parameter is set to NULL when there is no physical connection.

Peer Slot No. Indicates the slot number of the peer node at one end of the interconnection link.
This parameter is set to NULL when there is no physical connection.

Peer Port No. Indicates the port number of the peer node at one end of the interconnection link.
This port indicates the port HEI on the board panel.

SRIO Line Bit Rate Indicates the transmission rate of the Serial Rapid Input and Output (SRIO). The
parameter value NULL indicates that no SRIO rate is queried.

5.7.1.6.2.13 BBUFAN
EQUIPMENT
+-CABINET
+-SUBRACK
+-BBUFAN
Description

The BbuFan MO provides the heat dissipation function for the BBU.

Effective Scenario

Immediately

Relations Between MOs

Base class:
RU

Possible parents:
SUBRACK

Relation with the SUBRACK MO:


- The number of BBUFAN MOs configured on one SUBRACK MO must be greater than or
equal to 0 and smaller than or equal to 1.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP FAN Use this command to query the status of the FAN unit in the BBU, including the
temperature and rotation speed ratio.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet where the BBU FAN unit is located.

Subrack No. Indicates the number of the subrack where the BBU FAN unit is located.
Table 2 Related parameters

Parameter Description

Slot No. Indicates the number of the slot where the BBU FAN unit is located.

Temperature Indicates the current temperature of the BBU FAN unit.

Fan Speed Rate Indicates the rotation speed of a fan in the BBU, which is the ratio of the current
rotation speed of the fan to its maximum rotation speed.

Alarm Status(from RU) Indicates the alarm status of the board. The alarm state of the board can be
normal, warning, minor or critical. For details about the definition of Alarm
Status, see ITU-T X.731.

Operational State(from Indicates the operational state of the board, which can be set to Enabled or
RU)
Disabled. Enabled indicates that services can be carried on the board. Disabled
indicates that no service can be carried on the board.

Availability Status(from Indicates the physical operation status of the board, which can be Uninstalled,
RU)
Starting up, Normal, Inconsistent, Unconfigured, Power off, Fault,
Communication lost, In test, or the combination of various states. For example,
if a board is not configured and fails to communicate with the main control and
transmission board, the physical operation status of the board is Unconfigured,
Communication lost.

Electronic Label(from Indicates the E-label, a text file with a maximum of 2 KB. It is used to record the
RU)
manufacturing information about equipment such as the board, sub-board, or
optical module. Among board properties displayed in the text file, "BoardType"
indicates the type of the board, "BarCode" indicates the bar code of the board
and is the same as the code labeled on the board, and "Item" indicates the BOM
code.

Type(from RU) Indicates the type of the board.

Serial Number(from Indicates the bar code of the board or the cabinet.
RU)

Description(from RU) Indicates the description about the services and functions provided by the board
or the cabinet.

Date of Indicates the manufacturing date of the board or the cabinet.


Manufacture(from RU)

Vendor(from RU) Indicates the manufacturer of the board or the cabinet.

Issue Number(from RU) Indicates the issue number of the board.

Config Type(from RU) Indicates the type of a board.


Table 2 Related parameters

Parameter Description

Board Indicates the temperature of a board.


Temperature(from RU)

HPA Temperature(from Indicates the temperature of the power amplifier.


RU)

DEVTYPE(from RU) Indicates the type of the device.

Software Version(from Indicates the software version of the board.


RU)

Hardware Version(from Indicates the hardware version of the board.


RU)

BootRom Version(from Indicates the BootROM version of the board.


RU)

5.7.1.6.2.14 BCP
Description

This MO has no actual objects. It is defined for providing command parameters for related
commands of batch configuration.

Effective Scenario

Immediately

Relations Between MOs

None

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ACT BATCHFILE Use this command to activate the batch configuration session.
Table 1 Related MML commands

MML Command Function

CNL BATCHFILESN Use this command to stop the current operations of the batch configuration
session.

DLD BATCHFILE Use this command to download a batch configuration file from the FTP server to
an NE.

END BATCHFILESN Use this command to end a batch configuration session.

FOE BATCHFILESN Use this command to forcibly end the batch configuration session. The function
is similar to that of END BATCHFILESN. The difference lies in that: END
BATCHFILESN is used to end the batch configuration sessions started by the same
type of terminals. FOE BATCHFILESN is used to end batch configuration sessions
started by different types of terminals.

LST BATCHFILESN Use this command to list the information about one or all batch configuration
sessions.

PRA BATCHFILE Use this command to pre-activate a batch configuration session. Pre-activation
means that commands are executed but the configurations do not take effect.
This command is used to check the format validity of .xml files.

RBK BATCHFILE Use this command to roll back a batch configuration session.

STR BATCHFILESN Use this command to start a batch configuration session.


Only users that have configuration management (CM) rights are allowed to
configure data for NEs. When running this command, the user can only choose
the lock type to lock CM rights.

ULD BATCHFILERST Use this command to upload a batch configuration result file.

Parent topic: Equipments-tree

5.7.1.6.2.15 BITS
EQUIPMENT
+-BITS

Description
A building integrated timing supply system (BITS) MO is a type of reference clock source. The
BITS clock can be configured only on the USCU.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
EQUIPMENT

Relation with the TASM MO:


- If MODE and CLKSRC in the TASM MO are set to MANUAL and BITS, respectively, the
corresponding BITS MO must have been configured.
Relation with the GPS MO:
- A unique combination is necessary for the following parameters: 1. CN, SRN, and SN in the
BITS MO. 2. CN, SRN, and SN in the GPS MO.
Relation with the TOD MO:
- A unique combination is necessary for the following parameters: 1. CN, SRN, and SN in the
BITS MO. 2. CN, SRN, and SN in the TOD MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD BITS Use this command to add a BITS clock link. If the BS can properly obtain
synchronization signals from the BITS clock, this link becomes available.

DSP BITS Use this command to query the running status of a specified BITS clock link.

LST BITS Use this command to list the configuration of all BITS clock links.

MOD BITS Use this command to modify the priority of the BITS clock link.

RMV BITS Use this command to remove a specified BITS clock link.

Related Parameters
Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

BITS Clock No. Indicates the number of the BITS clock link.

Cabinet No. Indicates the number of the cabinet where the BITS clock link is configured.

Subrack No. Indicates the number of the subrack where the BITS clock link is configured.

Slot No. Indicates the number of the slot where the BITS clock link is configured.

Link Active State Indicates the activation status of the BITS clock link. If the link is active, the
BITS clock link is the current clock source of the system.

Link Available State Indicates the availability of a BITS clock link. Only an available clock link can
serve as the current clock source. Otherwise, the clock link cannot be locked
even if it is activated.

Priority Indicates the priority of the clock source. The value 1 indicates that the current
clock source has the highest priority, and the value 4 indicates that the current
clock source has the lowest priority.

5.7.1.6.2.16 BRI
EQUIPMENT
+-CABINET
+-SUBRACK
+-BRI
+-CPRIPORT[6~6]
+-SFP[6~6]

Description

The BRI MO defines a baseband radio interface board, which provides ports for receiving and
sending RF signals.

Effective Scenario

Immediately
Relations Between MOs

Base class:
RU

Possible parents:
SUBRACK

Possible children:
CPRIPORT[6~6];SFP[6~6]

Relation with the BBP,GTMU,RHUB,RRUCHAIN MOs:


- When the RRUCHAIN MO whose AT is set to a value other than PEERPORT, one of the
following BBP, BRI , GTMU or RHUB MOs must have been configured:
- 1. A BBP, BRI, GTMU or RHUB MO corresponding to HCN, HSRN, and HSN.
- 2. A BBP, BRI, GTMU or RHUB MO corresponding to TCN, TSRN, and TSN in the
RRUCHAIN MO when TT in the RRUCHAIN MO is set to a value other than CHAIN.
Relation with other boards in the BBU subrack:
- A unique combination is necessary for the following parameters: 1. CN, SRN, and SN in the
BBP MO; 2. CN, SRN, and SN in the TRP MO;3. CN, SRN, and SN in the UCIU MO; 4. CN,
SRN, and SN in the USCU MO; 5. CN, SRN, and SN in the BRI MO.
Relation with the SUBRACK MO:
- The number of BRI MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 4.
Relation with the RRUCHAIN,BBP,GTMU MOs:
- In the RRUCHAIN MO, when TT is set to RING and the combination of HCN, HSRN, and
HSN is not the same as the combination of TCN, TSRN, and TSN, this RRUCHAIN cannot be
configured on the BRI, GTMU, or BBP with TYPE set to GBBP.
- When the TT in the RRUCHAIN MO is set to LOADBALANCE, the total number of BBP
MO with the TYPE set to GBBP, BRI MO, and GTMU MO where the RRUCHAIN MO is
configured must be 0 or 1.

Related Parameters

Table 1 describes the parameters related to this MO.

Table 1 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the baseband radio interface board.
Table 1 Related parameters

Parameter Description

Subrack No. Indicates the subrack number of the baseband radio interface board.

Slot No. Indicates the slot number of the baseband radio interface board.

Board Type Indicates the type of the board.

Administrative state Indicates the administrative state of the board. The administrative state of the
board can be locked, unlocked, or shutting down. For details, see ITU-T X.731.

Duration of the shutting Indicates the scheduled duration before a board is blocked.
down state

Block Type Indicates the block type of the board. IMMEDIATE (Immediate) means that the
board is blocked and services carried on the board are interrupted immediately
after the command is executed. SHUTDOWN (Shutdown) means that the board
is blocked when no service is carried on the board. DELAY (Delay) means that
the board is blocked and services carried by the board are interrupted after a
scheduled duration.

Alarm Status(from RU) Indicates the alarm status of the board. The alarm state of the board can be
normal, warning, minor or critical. For details about the definition of Alarm
Status, see ITU-T X.731.

Operational State(from Indicates the operational state of the board, which can be set to Enabled or
RU)
Disabled. Enabled indicates that services can be carried on the board. Disabled
indicates that no service can be carried on the board.

Availability Status(from Indicates the physical operation status of the board, which can be Uninstalled,
RU)
Starting up, Normal, Inconsistent, Unconfigured, Power off, Fault,
Communication lost, In test, or the combination of various states. For example,
if a board is not configured and fails to communicate with the main control and
transmission board, the physical operation status of the board is Unconfigured,
Communication lost.

Electronic Label(from Indicates the E-label, a text file with a maximum of 2 KB. It is used to record the
RU)
manufacturing information about equipment such as the board, sub-board, or
optical module. Among board properties displayed in the text file, "BoardType"
indicates the type of the board, "BarCode" indicates the bar code of the board
and is the same as the code labeled on the board, and "Item" indicates the BOM
code.

Type(from RU) Indicates the type of the board.

Serial Number(from Indicates the bar code of the board or the cabinet.
RU)
Table 1 Related parameters

Parameter Description

Description(from RU) Indicates the description about the services and functions provided by the board
or the cabinet.

Date of Indicates the manufacturing date of the board or the cabinet.


Manufacture(from RU)

Vendor(from RU) Indicates the manufacturer of the board or the cabinet.

Issue Number(from RU) Indicates the issue number of the board.

Config Type(from RU) Indicates the type of a board.

Board Indicates the temperature of a board.


Temperature(from RU)

HPA Temperature(from Indicates the temperature of the power amplifier.


RU)

DEVTYPE(from RU) Indicates the type of the device.

Software Version(from Indicates the software version of the board.


RU)

Hardware Version(from Indicates the hardware version of the board.


RU)

BootRom Version(from Indicates the BootROM version of the board.


RU)

5.7.1.6.2.17 CABINET
EQUIPMENT
+-CABINET
+-SUBRACK[1~60]

Description

A Cabinet MO is an actual or virtual cabinet. An actual cabinet provides various functions


according to its type, for example, power distribution, environment monitoring, and surge
protection. A virtual cabinet is only a container of Subrack MOs.

Effective Scenario
Immediately

Relations Between MOs

Possible parents:
EQUIPMENT

Possible children:
SUBRACK[1~60]

Relation with the CABINET MO:


- When TYPE in the CABINET MO is set to one of the following values, the number of
SUBRACK MOs with TYPE set to RFU in this CABINET MO must be 0 or 1: RFC,
BTS3900, BTS3012_SRAN, BTS3012AE_SRAN and BTS3900AL.
Relation with the CCU MO:
- The TYPE in the CABINET MO which is corresponding to CCU must be set to
BTS3900AL, TP48600A, BBC.
Relation with the FMU MO:
- A FMU MO with SRN set to 12 cannot be configured in/for a CABINET MO when TYPE
in the CABINET MO is set to one of the following values: RFC, BTS3900, BTS3900AL.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD CABINET Use this command to add a cabinet.

DSP CABMFRINFO Use this command to query the manufacturing information about a cabinet.

LST CABINET Use this command to list the configuration of a cabinet. If the cabinet number is
not specified, the system would list the configuration of all cabinets.

MOD CABINET Use this command to modify attributes, including the cabinet description of a
cabinet.

RMV CABINET Use this command to remove a cabinet.

Related Parameters
Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number.

Cabinet Type Type of a cabinet. This parameter is set to VIRTUAL when the type of a cabinet
is not within the value range of this parameter.

Cabinet Description Indicates a brief description of the cabinet, which can be the function, location,
and some other information of the cabinet.

Model Indicates the cabinet type.

5.7.1.6.2.18 CARRIERRESOURCE
+-NE
+-NODE
+-CARRIERRESOURCE
+-SECTOR[0~102]
+-SECTOREQM[0~102]
+-BASEBANDEQM[0~36]

Description

The CarrierResource MO is the carrier management root object, which manages the MOs
associated with carrier resources.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
NODE

Possible children:
SECTOR[0~102];SECTOREQM[0~102];BASEBANDEQM[0~36]
5.7.1.6.2.19 CASCADEPORT
EQUIPMENT
+-CABINET
+-SUBRACK
EQUIPMENT
+-CABINET
+-SUBRACK
+-UCIU
+-CASCADEPORT
EQUIPMENT
+-CABINET
+-SUBRACK
+-BBP
+-CASCADEPORT
EQUIPMENT
+-CABINET
+-SUBRACK
+-MPT
+-CASCADEPORT

Description

The CascadePort MO, which can be either a basic interconnection port or an extended
interconnection ports, is used to interconnect the BBU. The basic interconnection port transmits
control-panel data and clock signals. The extended interconnection port transmits user-plane
data.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
UCIU;BBP;MPT

Relation with the BBP MO:


- When the combination of CN, SRN and SN in the CASCADEPORT MO is same as the
combination of CN, SRN and SN in the BBP MO, the PT of CASCADEPORT must be set to
ExpandedCascadePort.
Relation with the MPT MO:
- When the combination of CN, SRN and SN in the CASCADEPORT MO is same as the
combination of CN, SRN and SN in the MPT MO, the PT of CASCADEPORT must be set to
BasicCascadePort.
Relation with the UCIU MO:
- When the combination of CN, SRN and SN in the CASCADEPORT MO is same as the
combination of CN, SRN and SN in the UCIU MO, the PT of CASCADEPORT must be set to
BasicCascadePort.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP BBPLNKSTAT Use this command to query the statistics of the data link between subracks. The
transmission quality of the data link is measured by performing sampling on the
extended interconnection port every second and accumulating the sampled
values obtained in a certain period of time.

LST CASCADEPORT Use this command to list the configuration of one or all cascade ports.

SET CASCADEPORT Use this command to set the alarm detection state of a specified cascading port.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the board where the interconnection port is
located.

Subrack No. Indicates the subrack number of the board where the interconnection port is
located.

Slot No. Indicates slot number of the board where the interconnection port is located.

Port No. Indicates the number of the port that carries the interconnection link.
Table 2 Related parameters

Parameter Description

Port Type Indicates the type of the cascading port.

Switch Indicates the enabled/disabled state of the port. Alarms can be detected and
reported through the port only when the state of the port is ON.

5.7.1.6.2.20 CCU
EQUIPMENT
+-CABINET
+-SUBRACK
+-CCU
+-ALMPORT[2~2]

Description

A CCU MO defines a cabinet control unit (CCU). The CCU monitors the electromechanical
devices such as the power monitoring unit (PMU), fan monitoring unit (FMU), temperature
control unit (TCU), and environment monitoring unit (EMU) in a cabinet.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
SUBRACK

Possible children:
ALMPORT[2~2]

Relation with the SUBRACK,CTRLLNK MOs:


- If the MO corresponding to MCN and MSRN in the CCU MO is a SUBRACK MO with
SRN of 0 or 1, the SUBRACK MO cannot be a secondary subrack.
Relation with the ALMPORT MO:
- The number of ALMPORT MOs configured on one CCU MO must be 2.
Relation with the EMU,SUBRACK,RRU MOs:
- The MO corresponding to MCN and MSRN in the EMU MO must have been configured
and be one of the following types: 1. A SUBRACK MO with SRN set to 0 or 1; 2. A RRU MO;
3. A CCU MO.
Relation with the FMU,SUBRACK,RRU MOs:
- The MO corresponding to MCN and MSRN in the FMU MO must have been configured
and be one of the following types: 1. A SUBRACK MO with SRN set to 0 or 1; 2. A RRU MO;
3. A CCU MO.
Relation with the PMU,SUBRACK,RRU MOs:
- The MO corresponding to MCN and MSRN in the PMU MO must have been configured
and be one of the following types: 1. A SUBRACK MO with SRN set to 0 or 1; 2. A RRU MO;
3. A CCU MO.
Relation with the TCU,SUBRACK,RRU MOs:
- The MO corresponding to MCN and MSRN in the TCU MO must have been configured and
be one of the following types: 1. A SUBRACK MO with SRN set to 0 or 1; 2. A RRU MO; 3. A
CCU MO.
Relation with the TCU, PMU, EMU, andFMUMOs:
- It is not allowed in the following cases: 1. The combination of MCN, MSRN, and MPN in
the PMU MO is same as the combination of those in the configured CCU MO, and ADDR in
the PMU MO is equal to 21; 2. The combination of MCN, MSRN, and MPN in the FMU MO is
same as the combination of those in the configured CCU MO, and ADDR in the FMU MO is
equal to 21; 3. The combination of MCN, MSRN, and MPN in the TCU MO is same as the
combination of those in the configured CCU MO, and ADDR in the TCU MO is equal to 21; 4.
The combination of MCN, MSRN, and MPN in the EMU MO is same as the combination of
those in the configured CCU MO, and ADDR in the EMU MO is equal to 21.
Relation with the CABINET MO:
- The TYPE in the CABINET MO which is corresponding to CCU must be set to
BTS3900AL, TP48600A, BBC.
Relation with the CCU MO:
- If the manager unit BBU has lower-level CCU MOs, DCF of at least one CCU MO must be
set to YES.
Relation with the SUBRACK MO:
- The MO corresponding to MCN and MSRN in the CCU MO must have been configured
and must be a SUBRACK MO with SRN set to 0 or 1.
- The number of CCU MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 1.

Related MML Commands


Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD CCU Use this command to add a cabinet control unit (CCU). The CCU and its
subrack are added at the same time. Add the CCU that is directly connected to
the manager unit before adding other CCUs that are cascaded to the directly-
connected CCU.

CLR CCUALM Use this command to clear a cabinet control unit (CCU) smoke alarm.

DSP CCU Use this command to query the dynamic information about one or all cabinet
control units (CCUs).

LST CCU Use this command to list the configuration of one or all cabinet control units
(CCUs).

MOD CCU Use this command to modify the configuration of a cabinet control unit (CCU).

RMV CCU Use this command to remove a cabinet control unit (CCU). The CCU and its
subrack are removed at the same time.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the CCU.

Subrack No. Indicates the subrack number of the CCU.

Slot No. Indicates the slot number of the CCU.

Manager Cabinet No. Indicates the cabinet number of the manager unit of the CCU.

Manager Subrack No. Indicates the subrack number of the manager unit of the CCU.

Manager Port No. Indicates the number of the serial port where the CCU is connected. The serial
port is the port through which the CCU is connected to the BBU.
Table 2 Related parameters

Parameter Description

DirectConnectFlag Indicates whether the CCU is directly connected to its manager unit, which is a
BBU.

Cascade No. Indicates the position of the CCU on a CCU chain.

Connected RAT Indicates the working standard of the BBU to which the CCU is connected.

Special Boolean Alarm Indicates whether to allow the report of a dedicated Boolean alarm. If the shield
Flag
flag for a Boolean alarm is enabled, the Boolean alarm cannot be reported.

Left Port Status Indicates the connecting status of the port on the left of the CCU.

Right Port Status Indicates the connecting status of the port on the right of the CCU.

Software Version Indicates the software version of the CCU.

PCB Version Indicates the PCB version of the CCU.

EPLD Version Indicates the erasable programmable logic device (EPLD) version of the CCU.

5.7.1.6.2.21 CDE
Description

The CDE MO is the configuration data synchronization model. No actual object is related to this
MO. It provides definitions of the commands such as exporting, querying, and uploading the
exported file.

Effective Scenario

Immediately

Relations Between MOs

None

Parent topic: Equipments-tree


5.7.1.6.2.22 CFGBAK
Description

The CFGBAK MO is the configuration backup model. No actual object is related to this MO. It
provides the definitions of the parameters related to this MO.

Effective Scenario

Immediately

Relations Between MOs

None

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

BKP CFGFILE Use this command to back up the current configuration of the BS. The system
can be restored to the backed up configuration file.

DLD CFGFILE Use this command to download a configuration file from the FTP server to an
NE. The downloaded configuration file will replace the configuration file
backed up in or downloaded to the NE.

LST CFGFILE Use this command to query the backed up or downloaded configuration file of a
specified type.

RMV CFGFILE Use this command to remove a backed up or downloaded configuration file.

ULD CFGFILE Use this command to upload a backup configuration file to an FTP server.

Parent topic: Equipments-tree

5.7.1.6.2.23 CFGFILESTAT
Description

The CFGFILESTAT MO is used to query the activation status of configuration files.

Effective Scenario

Immediately

Relations Between MOs

None

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP Use this command to query the activation status of a configuration file after the
CFGFILEACTSTAT
configuration activation command is executed.

Parent topic: Equipments-tree

5.7.1.6.2.24 CFGSTAT
Description

This MO is used to query the configuration restore mode and other information about the
configuration restore performance.

Effective Scenario

Immediately

Relations Between MOs

None

Related MML Commands


Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP CFGSTAT Use this command to query performance statistics on restoration of the
configuration database.

Parent topic: Equipments-tree

5.7.1.6.2.25 CHK
Description

The CHK MO is used to store only the periodical checking enabling flag in the database. Other
parameters are used for checking other commands and are not stored in the database.

Effective Scenario

Not involved

Relations Between MOs

None

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST CFGCHK Use this command to list the setting of the flag that indicates whether a
periodical configuration check is enabled. If the flag is set to Enable, the system
automatically performs the periodical configuration check. The default period is
one day.

LST Use this command to list the result file of a configuration check. The file
CFGCHKRSLTFILE
Table 1 Related MML commands

MML Command Function

contains results of a configuration check that is initiated manually or


automatically. This command can be executed to check the name of the result
file to be uploaded.

SET CFGCHK Use this command to set the periodical configuration check flag. If the
periodical configuration check is required, this flag must be set to Enable by the
execution of this command.

STR CFGCHK Use this command to start the consistency check between effective data of
application modules and data in the database and to record inconsistencies in the
check result file.
After the system runs for a period, effective data of application modules may be
inconsistent with data in the database. This command can be used to record
inconsistencies in a file, based on which data synchronization can be performed
by running the STR CFGCHKSYNC command.

STR CFGCHKSYNC Use this command to start the synchronization of configuration data checking.

ULD Use this command to upload the result file generated during the configuration
CFGCHKRSLTFILE
data check. Thus, consistency between the actual data on the application module
and the data in the database can be detected.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Enable Flag Indicates whether to enable a periodical configuration check. If this parameter is
set to Enable, the NE automatically performs the periodical configuration check.

5.7.1.6.2.26 CPRILBR
Description
A CPRILBR MO consists of two operations related to the Common Public Radio Interface
(CPRI) line rate: querying the current line rate of a specified chain or ring, the maximum line
rate of the remote equipment controller (REC), and the maximum line rate of all remote
equipment (RE), and starting the line rate negotiation of a specified chain or ring.

Effective Scenario

Immediately

Relations Between MOs

None

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP CPRILBR Use this command to query the current line rate of the specified chain/ring and
the maximum line rates of the remote equipment controller (REC) and each
remote equipment (RE).

STR CPRILBRNEG Use this command to start negotiation on the common public radio interface
(CPRI) line rate of a specified chain or ring. If the link cannot recover for 5
minutes or a longer time after the topology changes, try to recover the link by
running this command.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

RRU Chain No. Indicates the ID of the RRU chain/ring.

5.7.1.6.2.27 CPRIPORT
EQUIPMENT
+-CABINET
+-SUBRACK
+-BRI
+-CPRIPORT
EQUIPMENT
+-CABINET
+-SUBRACK
+-RFU
+-CPRIPORT
EQUIPMENT
+-RHUB
+-CPRIPORT
EQUIPMENT
+-RRU
+-CPRIPORT
EQUIPMENT
+-CABINET
+-SUBRACK
+-UCIU
+-CPRIPORT
EQUIPMENT
+-AAS
+-AAMU
+-CPRIPORT
EQUIPMENT
EQUIPMENT
+-CABINET
+-SUBRACK
+-GTMU
+-CPRIPORT
EQUIPMENT
+-CABINET
+-SUBRACK
+-BBP
+-CPRIPORT

Description

A CpriPort MO is a port that supports the Common Public Radio Interface (CPRI) protocol. The
link between the CPRI ports of the BBU and the RRU allows transfer of control signals and user
data between the BBU and the RRU.
Effective Scenario

Immediately

Relations Between MOs

Possible parents:
BRI;RFU;RHUB;RRU;UCIU;AAMU;GTMU;BBP

Relation with the CPRIPORT MO:


- When the RRUCHAIN MO whose AT is set to a value other than PEERPORT, one of the
following CPRIPORT MOs must have been configured:
- 1. A CPRIPORT MO corresponding to HCN, HSRN, HSN, and HPN.
- 2. A CPRIPORT MO corresponding to TCN, TSRN, TSN, and TPN in the RRUCHAIN
MO when TT in the RRUCHAIN MO is set to a value other than CHAIN.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP CPRIPORT Use this command to query the dynamic information about a CPRI port on an
RF or a BBU.

DSP Use this command to query the topology and hardware information about the
RRUCHAINPHYTOPO
RRU chain or ring connected to a CPRI port.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the board where the CPRI port is located. This
parameter is configured automatically when the CPRI port is created. A CPRI
port is created automatically when a BBP is added by running the ADD BRD
command. The CPRI port is used for the configuration check when an RRU
Table 2 Related parameters

Parameter Description

chain/ring is added.

Subrack No. Indicates the subrack number of the board where the CPRI port is located. This
parameter is configured automatically when the CPRI port is created. A CPRI
port is created automatically when a BBP is added by running the ADD BRD
command. The CPRI port is used for the configuration check when an RRU
chain/ring is added.

Slot No. Indicates the slot number of the board where the CPRI port is located. This
parameter is configured automatically when the CPRI port is created. A CPRI
port is created automatically when a BBP is added by running the ADD BRD
command. The CPRI port is used for the configuration check when an RRU
chain/ring is added.

Port No. Indicates the port number of the board where the CPRI port is located. This
parameter is configured automatically when the CPRI port is created. A CPRI
port is created automatically when a BBP is added by running the ADD BRD
command. The CPRI port is used for the configuration check when an RRU
chain/ring is added.

CPRI Bit Rate Indicates the rate at the CPRI port.

Block Status Indicates the administrative state of the CPRI port. When the CPRI port is
locked, it indicates that a breakpoint is configured on the RRU chain/ring. At
this moment, although the optical cables are connected, the CPRI link is
disconnected. The breakpoint is configured to prevent temporary alarms from
being reported during network operations. When the CPRI port is unlocked, it
indicates that there is no breakpoint on the RRU chain/ring. If the base station
uses CPRI MUX, the queried value of this parameter is NULL on the converged
party side.

Install Status Indicates the in-position state of the CPRI port. If the base station uses CPRI
MUX, the queried value of this parameter is NULL on the converged party side.

CPRI Port Mode Indicates the mode of the CPRI port. There are two modes: Maser and Slave. All
CPRI ports on a baseband processing board work in master mode. On the first-
level RRU in an RRU chain, the CPRI port connected to a baseband processing
board works in slave mode and the other CPRI port connected to the second-
level RRU works in master mode. When an RRU and the baseband processing
boards are in dual-star topology, the two CPRI ports on the RRU work in slave
mode.

Port Type Indicates the type of the CPRI port. If the base station uses CPRI MUX, the
queried value of this parameter is UNKNOWN on the converged party side.
Table 2 Related parameters

Parameter Description

CPRI Port Mux Status Indicates the Mux Status of the CPRI port.

5.7.1.6.2.28 CTRLLNK
EQUIPMENT
+-CTRLLNK

Description

The CTRLLNK MO defines the control link between baseband units (BBUs).

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
EQUIPMENT

Relation with the CCU,SUBRACK MOs:


- If the MO corresponding to MCN and MSRN in the CCU MO is a SUBRACK MO with
SRN of 0 or 1, the SUBRACK MO cannot be a secondary subrack.
Relation with the EMU,SUBRACK MOs:
- If the MO corresponding to MCN and MSRN in the EMU MO is a SUBRACK MO with
SRN of 0 or 1, the SUBRACK MO cannot be a secondary subrack.
Relation with the FMU,SUBRACK MOs:
- If the MO corresponding to MCN and MSRN in the FMU MO is a SUBRACK MO with
SRN of 0 or 1, the SUBRACK MO cannot be a secondary subrack.
Relation with the PMU,SUBRACK MOs:
- If the MO corresponding to MCN and MSRN in the PMU MO is a SUBRACK MO with
SRN of 0 or 1, the SUBRACK MO cannot be a secondary subrack.
Relation with the TCU,SUBRACK MOs:
- If the MO corresponding to MCN and MSRN in the TCU MO is a SUBRACK MO with
SRN of 0 or 1, the SUBRACK MO cannot be a secondary subrack.
Relation with the TRP,SUBRACK MOs:
- If SUBTYPE in the TRP MO is set to UTRPc,the TRP MO must be configured in master
BBU subrack.
Relation with the CTRLLNK MO:
- A unique combination is necessary for the following parameters: CN and SRN SN in the
CTRLLNK MO; UPCN and UPSRN in the CTRLLNK MO.
- In the CTRLLNK MO, the setting of the combination of CN, SRN, and SN must be unique.
- In the CTRLLNK MO, the setting of the combination of UPCN, UPSRN, UPSN, and
UPPT must be unique.
Relation with the SUBRACK MO:
- The SUBRACK MO corresponding to the combination of CN and SRN or the combination
of UPCN and UPSRN in the CTRLLNK MO has been configured.
- When two SUBRACK MOs with SRN set to 0 or 1 are configured, the current SUBRACK
MO must meet one of the following conditions: 1. CN and SRN in the SUBRACK MO are the
same as CN and SRN in a CTRLLNK that is already configured. 2. CN and SRN in the
SUBRACK MO are the same as UPCN and UPSRN in a CTRLLNK respectively that is
already configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD CTRLLNK Use this command to add a control link. The control link is a logical concept.
The physical entity of the control link is the topology between the
interconnected BBUs.

DSP CTRLLNKSTAT Use this command to query the bit error rate of a control link. The statistical
information mainly includes the number of received packets, number of
erroneous packets, total packet receiving time, and total erroneous packet
receiving time and reflects the transmission quality of the link.For the UCIU,
this command can be used to display the bit error rates (BERs) of ports 0 to 4
and port 8. For the UMPT, this command can only be used to display the BER of
port 8.

LST CTRLLNK Use this command to list the configuration of a control link.
Table 1 Related MML commands

MML Command Function

MOD CTRLLNK Use this command to modify the configuration of a control link.

RMV CTRLLNK Use this command to remove a control link.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local Link No. Indicates the number of the control link at the local end.

Local Cabinet No. Indicates the cabinet number of the local node at one end of the control link.

Local Subrack No. Indicates the subrack number of the local node at one end of the control link.

Local Slot No. Indicates the slot number of the local node at one end of the control link.

Upper Cabinet No. Indicates the cabinet number of the upper-level node at the other end of the
control link.

Upper Subrack No. Indicates the subrack number of the upper-level node at the other end of the
control link.

Upper Slot No. Indicates the slot number of the upper-level node at the other end of the control
link.

Upper Port No. Indicates the port number of the upper-level node at the other end of the control
link.Values 0 to 4 indicate the ports M0 to M4 on the board panel.

5.7.1.6.2.29 DIESELGEN
EQUIPMENT
+-CABINET
+-SUBRACK
+-PMU
+-DIESELGEN

Description

The DieselGen MO is a diesel generator, which provides power supply to the solar power system
when the combined solar power supply mode of light and oil is used.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
PMU

Relation with the PMU MO:


- The PMU MO corresponding to CN, SRN, and SN in the DIESELGEN MO must have
been configured and PTYPE in the PMU MO must be SC48200.
- Only a PMU MO with PTYPE set to SC48200 can be configured with a lower-level
DIESELGEN MO.
- The number of DIESELGEN MOs configured on one PMU MO must be greater than or
equal to 0 and smaller than or equal to 1.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD DIESELGEN Use this command to add a diesel generator. The diesel generator is compatible
only with the SC48200 power monitoring unit (PMU).

DSP DIESELGEN Use this command to query the dynamic information about a diesel generator.

LST DIESELGEN Use this command to list the configuration of a diesel generator.

MOD DIESELGEN Use this command to modify the configuration of a diesel generator.

RMV DIESELGEN Use this command to remove a diesel generator.


Table 1 Related MML commands

MML Command Function

STP DIESELGENTST Use this command to stop the ongoing diesel generator test. This command is
applicable only to a diesel generator test that is performed on the SC48200
power monitoring unit (PMU).

STR DIESELGENTST Use this command to start the diesel generator test immediately. If this command
fails, an alarm indicating the diesel generator startup failure is reported. This
command is applicable only to a diesel generator test that is performed on the
SC48200 power monitoring unit (PMU).

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet where the PMU managing the diesel
generator is located.

Subrack No. Indicates the number of the subrack where the PMU managing the diesel
generator is located.

Slot No. Indicates the number of the slot where the PMU managing the diesel generator is
located.

Intelligent Control Flag Indicates whether intelligent control of the diesel generator is enabled. When
intelligent control is enabled, the PMU automatically controls the diesel
generator according to the preset parameters, thus reducing the operation cost of
the diesel generator.

Rated Power Indicates the maximum rated output power of the diesel generator. It should be
configured according to the rated output power printed on the name plate of the
diesel generator.

Oil Level Indicates the oil level of the diesel generator.

Diesel Generator Indicates the current of the diesel generator.


Current

Total Running Time Indicates the total running time of the diesel generator.
5.7.1.6.2.30 EMU
EQUIPMENT
+-CABINET
+-SUBRACK
+-EMU
+-OUTPORT[6~6]
+-ALMPORT[36~36]

Description

The environment monitoring unit (EMU) MO is used for an indoor BS. It monitors the status
about the environment (humidity, temperature, water, and smoke), burglarproofing (infrared and
door status), and power distribution.

Effective Scenario

Immediately

Relations Between MOs

Base class:
RU

Possible parents:
SUBRACK

Possible children:
OUTPORT[6~6];ALMPORT[36~36]

Relation with the SUBRACK,CTRLLNK MOs:


- If the MO corresponding to MCN and MSRN in the EMU MO is a SUBRACK MO with
SRN of 0 or 1, the SUBRACK MO cannot be a secondary subrack.
Relation with the ALMPORT MO:
- The number of ALMPORT MOs configured on one EMU MO must be 36.
Relation with the OUTPORT MO:
- The number of OUTPORT MOs configured on one EMU MO must be 6.
Relation with the SUBRACK MO:
- The number of EMU MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 1.
Relation with the TCU, PMU, EMU,andFMU Mos:
- It is not allowed in the following cases: 1. The combination of MCN, MSRN, MPN, and
ADDR in the EMU MO is same as the combination of those in other EMU MOs; 2. The
combination of MCN, MSRN, MPN, and ADDR in the EMU MO is same as the combination
of those in the PMU MOs; 3. The combination of MCN, MSRN, MPN, and ADDR in the EMU
MO is same as the combination of those in the TCU MOs; 4. The combination of MCN, MSRN,
MPN, and ADDR in the EMU MO is same as the combination of those in the FMU MOs; 5.
The combination of MCN, MSRN, and MPN in the EMU MO is same as the combination of
those in the CCU MOs, and ADDR in the EMU MO is equal to 21.
Relation with the CABINET MO:
- TYPE in the CABINET MO where the EMU MO is configured cannot be set to any of the
following values: BBC, RFC, and TP48300A.
Relation with the SUBRACK,RRU,CCU MOs:
- The MO corresponding to MCN and MSRN in the EMU MO must have been configured
and be one of the following types: 1. A SUBRACK MO with SRN set to 0 or 1; 2. A RRU MO;
3. A CCU MO.
Relation with the subrack that houses the EMU MO:
- A subrack must be configured together with an EMU MO to house the EMU MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD EMU Use this command to add an environment monitoring unit (EMU). When the
EMU is added, an EMU subrack and an EMU board are added at the same time.

CLR EMUALM Use this command to clear an environment monitoring unit (EMU) smoke or
burglar alarm. When an EMU smoke or burglar alarm is reported, you must clear
the fault that triggers the alarm, and then run this command to clear
alarm.Burglar alarm includes gate alarm and infrared alarm.

DSP EMU Use this command to query the dynamic information about an environment
monitoring unit (EMU).

LST EMU Use this command to list the configuration of an environment monitoring unit
(EMU).

MOD EMU Use this command to modify the configuration of an environment monitoring
unit (EMU).
Table 1 Related MML commands

MML Command Function

RMV EMU Use this command to remove an environment monitoring unit (EMU). When the
EMU is removed, an EMU subrack and an EMU board are removed at the same
time.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet where the EMU is located.

Subrack No. Indicates the number of the subrack where the EMU is located.

Slot No. Indicates the number of the slot where the EMU is located.

Manager Cabinet No. Indicates the cabinet number of the manager that manages the EMU. The
manager of the EMU is usually a BBU, RRU or CCU.

Manager Subrack No. Indicates the subrack number of the manager. The manager of the EMU is
usually a BBU, RRU or CCU.

Manager Port No. Indicates the number of the serial port where the EMU is connected. The serial
port is the port through which the EMU is connected to the manager unit.

Address Indicates the communication address of the EMU, which is determined by the
settings of the 4-bit dual in-line package (DIP) switch on the EMU. The
communication address is used by the EMU to communicate with the main
control and transmission board. The value of this parameter must be consistent
with the actual settings of the DIP switch. The 4-bit DIP switch can be treated as
a 4-bit binary number. The settings of ON and OFF are represented by 1 and 0
respectively. Convert the 4-bit number from binary to decimal, and then the
decimal number is used as the value of this parameter.

Temperature Alarm Indicates the lower limit of temperature. When the temperature is below the
Lower Threshold
lower limit, an ALM-25650 Temperature Abnormal alarm is reported.

Temperature Alarm Indicates the upper limit of temperature. When the temperature exceeds the
Upper Threshold
upper limit, an ALM-25650 Temperature Abnormal alarm is reported.
Table 2 Related parameters

Parameter Description

Humidity Alarm Lower Indicates the lower limit of humidity. When the humidity is below the lower
Threshold
limit, an ALM-25651 Humidity Abnormal alarm is reported.

Humidity Alarm Upper Indicates the upper limit of humidity. When the humidity exceeds the upper
Threshold
limit, an ALM-25651 Humidity Abnormal alarm is reported.

Special Analog Alarm Indicates whether to allow the report of a dedicated analog alarm. If the shield
Flag
flag for an analog alarm is enabled, the analog alarm cannot be reported. The
48V_DISABLE check box under this parameter must be set to off. Otherwise,
ALM-26271 Inter-System Monitoring Device Parameter Settings Conflict will
be reported mistakenly in a separate-MPT multimode base station that involves
the GBTS.

Special Boolean Alarm Indicates whether to allow the report of a dedicated Boolean alarm. If the shield
Flag
flag for a Boolean alarm is enabled, the Boolean alarm cannot be reported.

Ambient Temperature Indicates the current temperature of the environment.

Ambient Humidity Indicates the ambient humidity.

-48V Input Voltage Indicates the -48 V input voltage from the power supply cabinet.

Analog Port 1 Indicates the current value measured by the external sensor that is connected to
Measurement Value
analog port 1.

Analog Port 2 Indicates the current value measured by the external sensor that is connected to
Measurement Value
analog port 2.

Analog Port 3 Indicates the current value measured by the external sensor that is connected to
Measurement Value
analog port 3.

Analog Port 4 Indicates the current value measured by the external sensor that is connected to
Measurement Value
analog port 4.

Alarm Status(from RU) Indicates the alarm status of the board. The alarm state of the board can be
normal, warning, minor or critical. For details about the definition of Alarm
Status, see ITU-T X.731.

Operational State(from Indicates the operational state of the board, which can be set to Enabled or
RU)
Disabled. Enabled indicates that services can be carried on the board. Disabled
indicates that no service can be carried on the board.

Availability Status(from Indicates the physical operation status of the board, which can be Uninstalled,
RU)
Table 2 Related parameters

Parameter Description

Starting up, Normal, Inconsistent, Unconfigured, Power off, Fault,


Communication lost, In test, or the combination of various states. For example,
if a board is not configured and fails to communicate with the main control and
transmission board, the physical operation status of the board is Unconfigured,
Communication lost.

Electronic Label(from Indicates the E-label, a text file with a maximum of 2 KB. It is used to record the
RU)
manufacturing information about equipment such as the board, sub-board, or
optical module. Among board properties displayed in the text file, "BoardType"
indicates the type of the board, "BarCode" indicates the bar code of the board
and is the same as the code labeled on the board, and "Item" indicates the BOM
code.

Type(from RU) Indicates the type of the board.

Serial Number(from Indicates the bar code of the board or the cabinet.
RU)

Description(from RU) Indicates the description about the services and functions provided by the board
or the cabinet.

Date of Indicates the manufacturing date of the board or the cabinet.


Manufacture(from RU)

Vendor(from RU) Indicates the manufacturer of the board or the cabinet.

Issue Number(from RU) Indicates the issue number of the board.

Config Type(from RU) Indicates the type of a board.

Board Indicates the temperature of a board.


Temperature(from RU)

HPA Temperature(from Indicates the temperature of the power amplifier.


RU)

DEVTYPE(from RU) Indicates the type of the device.

Software Version(from Indicates the software version of the board.


RU)

Hardware Version(from Indicates the hardware version of the board.


RU)

BootRom Version(from Indicates the BootROM version of the board.


RU)
5.7.1.6.2.31 ENERGYCON
EQUIPMENT
+-ENERGYCON

Description

The ENERGYCON MO manages the configuration of the power consumption measurement


point in a BS. A PMU measures DC and AC power consumption. The DC power consumption
refers to the power consumption of major devices in the BS. The AC power consumption
consists of the power consumption of PSUs, battery charging, and major devices in the BS.
Because the precision of DC power consumption is higher than that of AC power consumption,
the DC power consumption is reported by default. When some energy-saving functions are
performed by PSUs, the AC power consumption also needs to be reported. In this case, you need
to modify the configuration.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
EQUIPMENT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST ECMP Use this command to list the power consumption measurement point of a BS.

SET ECMP Use this command to set the power consumption measurement point of a BS.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Energy Consumption Indicates the power consumption measurement point of the BS.
Measurement Point

5.7.1.6.2.32 EQUIPMENT
+-NE
+-NODE
+-EQUIPMENT
+-RET[0~35]
+-TMA[0~35]
+-CTRLLNK[0~2]
+-SYNCETH[0~1]
+-BITS[0~1]
+-TASM[1~1]
+-GPS[0~2]
+-TOD[0~2]
+-PEERCLK[0~1]
+-IPCLKLNK[0~2]
+-LINECLK[0~1]
+-BBPLINK[0~1]
+-MAINSALARMBIND[1~1]
+-ENERGYCON[1~1]
+-RHUB[0~195]
+-CABINET[1~32]
+-RRU[0~18]
+-AAS[0~24]
+-PSUIS[1~1]
+-RRUCHAIN[0~36]
+-LOCATION[0~256]
+-FTPCLT[1~1]
+-FTPCLTPORT[0~20]
+-NTPCP[0~4]
+-TIMESRC[1~1]
+-TZ[1~1]

Description
The Equipment MO is the equipment root object, which manages the MOs of equipment class.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
NODE

Possible children:
RET[0~35];TMA[0~35];CTRLLNK[0~2];SYNCETH[0~1];BITS[0~1];TASM[1~1];GPS[0~2];TOD[0~2];PE
ERCLK[0~1];IPCLKLNK[0~2];LINECLK[0~1];BBPLINK[0~1];MAINSALARMBIND[1~1];ENERGYCON[1~1];
RHUB[0~195];CABINET[1~32];RRU[0~18];AAS[0~24];PSUIS[1~1];RRUCHAIN[0~36];LOCATION[0~25
6];FTPCLT[1~1];FTPCLTPORT[0~20];NTPCP[0~4];TIMESRC[1~1];TZ[1~1]

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP BSSTATUS Use this command to query the NE status.

DSP CANSTATE Use this command to query the status of the controller area network BUS
(CANbus).

DSP INTERCONTOPO Use this command to query the box interconnection topology.

DSP MNTMODE Use this command to query the current maintenance status of an NE.

DSP TCMODE Use this command to query supported mode of temperature control of an NE.

EXP DEVFILE Use this command to export a device file. You can export the device file
containing one table or all tables.

LST DVAS Use this command to list the alarm switch status of the DC.

LST EQUIPMENT Use this command to list NE equipment configuration,include intelligent


management swtich status, power lose redundancy alarm enabled flag, open DU
interface (ODI) ID of NE equipment, power supplying unit (PSU) fault
shutdown TRx enabled flag, protocol type and Smart TRx enabled flag.
Table 1 Related MML commands

MML Command Function

LST MNTMODE Use this command to list the maintenance status of the NE.

RST BTSNODE Use this command to reset the configured in-position boards (excluding the
UPEU and passive boards such as the USCU) in a BS.

SCN RS485 Use this command to scan an RS485 bus to check the types and status of
monitoring devices connected on the bus. This command can also help the OM
engineers to locate and rectify connection or configuration faults on the RS485
bus.

SET DVAS Use this command to set the special alarm switch and threshold of the volts DC.

SET EQUIPMENT Use this command to set battery intelligent management switch,set power lose
redundancy alarm enabled flag,set open DU interface (ODI) ID of NE
equipment, set power supplying unit (PSU) fault shutdown TRx enabled flag,
protocol type and Smart TRx enabled flag.

SET MNTMODE Use this command to set the maintenance status of the NE. When the NE is in
the maintenance status, the way of alarm reporting is changed and the
performance measurement is unbelievable.

ULD DEVFILE Use this command to upload a device file.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Battery Intelligent Indicates the battery intelligent management switch status. Intelligent battery
Management Switch
power management prolongs the lifespan of a battery using the floating charge
mode.

Power Lose Whether to allow the generation of the Power Lose Redundancy alarm. The
Redundancy Alarm
Enabled PSUs need to be configured in N+1 backup mode. When this parameter is set to
"OPEN", the BTS reports the Power Lose Redundancy alarm if the PSUs are not
configured in N+1 mode.

Maintenance Mode Indicates the maintenance status of the NE. The status is set to TESTING by
Table 2 Related parameters

Parameter Description

default by the manufacturers. ExpandStatus1 to ExpandStatus10 can be self-


defined.

Start Time of Status Indicates the start time of maintenance status of the NE. If this parameter is not
Setting
specified, the start time of the maintenance status is 2000-01-01 00:00:00.

End Time of Status Indicates the end time of maintenance status of the NE. If this parameter is not
Setting
specified, the maintenance status ends at 2037-12-31 23:59:59.

Maintenance Mode Indicates the remarks of maintenance status of the NE.


Setting Remark

Current Maintenance Indicates the current maintenance mode of the network element (NE).
Mode

Direct Voltage Alarm Indicates the direct voltage alarm switch. The switch controls whether to report
Switch
the ALM-26113 Base Station DC Power Supply Abnormal in the case of low
DC input voltage.

Direct Voltage Alarm Indicates the DC voltage alarm occured threshold. When the load voltage is
Occured Threshold
lower than the DC voltage alarm occured threshold and the direct voltage alarm
switch is set to ENABLE, an ALM-26113 Base Station DC Power Supply
Abnormal is reported.

Direct Voltage Alarm Indicates the DC voltage alarm restored threshold. When the load voltage is
Restored Threshold
higher than the DC voltage alarm restored threshold and the direct voltage alarm
switch is set to ENABLE, an ALM-26113 Base Station DC Power Supply
Abnormal is cleared.

Open DU Interface ID Indicates the ID of the open DU interface (ODI) and can be used only in
LTE_TDD. If this parameter is set to 0, no ID is configured for the ODI and this
base station cannot communicate with other base stations.

Equipment Type Indicates the physic state of the NE.

PSU Fault Shutdown Indicates whether the BS enters the energy saving mode when some PSUs
TRX Enabled
become faulty. If this parameter is set to ON, the BS enters the energy saving
mode to reduce power consumption when some PSUs become faulty and the
remaining PSUs cannot meet the BS's power requirements. In energy saving
mode, the BS shuts down TRXs or reduces their transmit power.

Protocol Type Indicates the communication protocol type used between the BBU and radio
frequency (RF) units. The value CPRI indicates the Huawei proprietary
protocol, and the value TDL_IR indicates the IR communication protocol
defined by China Mobile Communication Corporation (CMCC).
Table 2 Related parameters

Parameter Description

Smart TRX Switch Indicates whether the Smart TRX function is enabled or disabled. The Smart
TRX function is supported only when the XMU is installed. If the Smart TRX
function is disabled, the Smart TRX function of the XMU cannot be processed
by the BTS.

5.7.1.6.2.33 FM
Description

The FM MO is used for file transmission management. It manages the uploading and
downloading task of the file.

Effective Scenario

Immediately

Relations Between MOs

None

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

CLR FILE Use this command to clear trash files from a board based on their deletion levels
when the board has insufficient flash memory. The deletion levels can be high,
medium, or low.

DLD GENFILE Use this command to download the generic file from the FTP server to the NE.

ULD FILE Use this command to upload the file with specified file type.

Parent topic: Equipments-tree


5.7.1.6.2.34 FMU
EQUIPMENT
+-CABINET
+-SUBRACK
+-FMU
+-ALMPORT[0~4]

Description

The fan monitoring unit (FMU) MO is used to dissipate heat from a cabinet. Currently, there are
two types of FMU: indoor FMU and outdoor FMU.

Effective Scenario

Immediately

Relations Between MOs

Base class:
RU

Possible parents:
SUBRACK

Possible children:
ALMPORT[0~4]

Relation with the SUBRACK,CTRLLNK MOs:


- If the MO corresponding to MCN and MSRN in the FMU MO is a SUBRACK MO with
SRN of 0 or 1, the SUBRACK MO cannot be a secondary subrack.
Relation with the ALMPORT MO:
- The number of ALMPORT MOs configured on one FMU MO must be greater than or equal
to 0 and smaller than or equal to 4.
Relation with the SUBRACK MO:
- The number of FMU MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 1.
Relation with the TCU, PMU, EMU,andFMUMOs:
- It is not allowed in the following cases: 1. The combination of MCN, MSRN, MPN, and
ADDR in the FMU MO is same as the combination of those in other FMU MOs; 2. The
combination of MCN, MSRN, MPN, and ADDR in the FMU MO is same as the combination
of those in the PMU MOs; 3. The combination of MCN, MSRN, MPN, and ADDR in the FMU
MO is same as the combination of those in the TCU MOs; 4. The combination of MCN, MSRN,
MPN, and ADDR in the FMU MO is same as the combination of those in the EMU MOs; 5.The
combination of MCN, MSRN, and MPN in the FMU MO is same as the combination of those
in the CCU MOs, and ADDR in the FMU MO is equal to 21.
Relation with the CABINET MO:
- A FMU MO with SRN set to 12 cannot be configured in/for a CABINET MO when TYPE
in the CABINET MO is set to one of the following values: RFC, BTS3900, BTS3900AL.
Relation with the SUBRACK,RRU,CCU MOs:
- The MO corresponding to MCN and MSRN in the FMU MO must have been configured
and be one of the following types: 1. A SUBRACK MO with SRN set to 0 or 1; 2. A RRU MO;
3. A CCU MO.
Relation with the subrack that houses the FMU MO:
- A subrack must be configured together with a FMU MO to house the FMU MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD FMU Use this command to add a fan monitoring unit (FMU). When the FMU is
added, a FMU subrack and a FMU board are added at the same time.

CLR FMUALM Use this command to clear a fan monitoring unit (FMU) smoke alarm. When a
FMU smoke alarm is reported, you must clear the fault that triggers the alarm,
and then run this command to clear the alarm.

DSP FMU Use this command to query the dynamic information about a fan monitoring unit
(FMU).

LST FMU Use this command to list the configuration of a fan monitoring unit (FMU).

MOD FMU Use this command to modify the configuration of a fan monitoring unit (FMU).

RMV FMU Use this command to remove a fan monitoring unit (FMU). When the FMU is
removed, a FMU subrack and a FMU board are removed at the same time.

Related Parameters
Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet where the FMU is located.

Subrack No. Indicates the number of the subrack where the FMU is located.

Slot No. Indicates the number of the slot where the FMU is located.

Manager Cabinet No. Indicates the cabinet number of the manager. The manager of the FMU is
usually a BBU, RRU or CCU.

Manager Subrack No. Indicates the subrack number of the manager. The manager of the FMU is
usually a BBU, RRU or CCU.

Manager Port No. Indicates the number of the serial port where the FMU is connected. The serial
port is the port through which the FMU is connected to the manager unit.

Address Indicates the communication address of the FMU. The FMU communicates with
the main control and transmission board by using this communication address.

Special Boolean Alarm Indicates whether to allow the report of a dedicated Boolean alarm. If the shield
Flag
flag for a Boolean alarm is enabled, the Boolean alarm cannot be reported.

Fan Speed Rate Indicates the ratio of the current rotation speed of the fan to its maximum
rotation speed.

Temperature at Fan Air Indicates the temperature at the air outlet of the FMU.
Outlet

Temperature at Fan Air Indicates the temperature at the air inlet of the FMU.
Inlet

Fan Average Speed Indicates the average rotation speed of the fan per minute.

Smart Temperature Indicates the switch of smart temperature control. When the smart temperature
Control
control is enabled, the rotation speed of the fan is adjusted by the FMU
according to the temperature control parameters delivered by the BBU. When
the smart temperature control is disabled, the rotation speed of the fan is
adjusted by the FMU automatically according to the temperature.

Temperature Control Indicates the mode that the fan speed adjustment adopts. Mode 0 is the default
Mode
mode, which achieves balance in system power consumption, noise, and
temperature control. It applies to most scenarios. Mode 9 is the synchronization
mode, which brings low noise but poor temperature control. Inappropriate
configuration of this parameter may lead to serious results such as high noise or
Table 2 Related parameters

Parameter Description

service interruption on the RF modules due to overtemperature. You need to


contact Huawei technical support before configuring this parameter. You can run
the DSP TCMODE command to list the number and description of the
temperature control modes supported by the base station. After configuring this
parameter, you can run the DSP FMU command to query whether the
temperature control mode in the command output is consistent with the
configuration. If yes, the configuration is successful. If no, the configuration
fails and the system adopts the default mode (mode 0). The reasons for the
configuration failure and countermeasures are as follows:
1. The FMU version does not support the temperature control mode
configuration.
2. The curve corresponding to the configured temperature control mode is
incorrect and the configuration cannot take effect on the FMU. You need to
contact the Huawei technical support.

Alarm Status(from RU) Indicates the alarm status of the board. The alarm state of the board can be
normal, warning, minor or critical. For details about the definition of Alarm
Status, see ITU-T X.731.

Operational State(from Indicates the operational state of the board, which can be set to Enabled or
RU)
Disabled. Enabled indicates that services can be carried on the board. Disabled
indicates that no service can be carried on the board.

Availability Status(from Indicates the physical operation status of the board, which can be Uninstalled,
RU)
Starting up, Normal, Inconsistent, Unconfigured, Power off, Fault,
Communication lost, In test, or the combination of various states. For example,
if a board is not configured and fails to communicate with the main control and
transmission board, the physical operation status of the board is Unconfigured,
Communication lost.

Electronic Label(from Indicates the E-label, a text file with a maximum of 2 KB. It is used to record the
RU)
manufacturing information about equipment such as the board, sub-board, or
optical module. Among board properties displayed in the text file, "BoardType"
indicates the type of the board, "BarCode" indicates the bar code of the board
and is the same as the code labeled on the board, and "Item" indicates the BOM
code.

Type(from RU) Indicates the type of the board.

Serial Number(from Indicates the bar code of the board or the cabinet.
RU)

Description(from RU) Indicates the description about the services and functions provided by the board
or the cabinet.
Table 2 Related parameters

Parameter Description

Date of Indicates the manufacturing date of the board or the cabinet.


Manufacture(from RU)

Vendor(from RU) Indicates the manufacturer of the board or the cabinet.

Issue Number(from RU) Indicates the issue number of the board.

Config Type(from RU) Indicates the type of a board.

Board Indicates the temperature of a board.


Temperature(from RU)

HPA Temperature(from Indicates the temperature of the power amplifier.


RU)

DEVTYPE(from RU) Indicates the type of the device.

Software Version(from Indicates the software version of the board.


RU)

Hardware Version(from Indicates the hardware version of the board.


RU)

BootRom Version(from Indicates the BootROM version of the board.


RU)

5.7.1.6.2.35 FTPCLT
EQUIPMENT
+-FTPCLT

Description

The FTPCLT MO contains the parameters related to the FTP client, such as the encryption mode
and the state firewall flag.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
EQUIPMENT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST FTPSCLT Use this command to list the configurations of the FTP client.

SET FTPSCLT Use this command to set the configurations of the FTP client.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Transport Encrypted Indicates the transmission encryption mode of the FTP client. If this parameter is
Mode
set to Auto, the FTP client first attempts to transmit data in ciphertext. If the
attempt fails, the FTP client automatically switches the encryption mode to
retransmit data in plaintext. However, if there are faults in transmission
equipment, the FTP client does not attempt to retransmit data in plaintext even if
the FTP server supports encrypted transmission. In this case, the FTP connection
setup fails.

Support State Firewall Indicates whether FTP connections in encrypted mode can be established when
there is a state firewall. In plaintext mode, this parameter is invalid. In encrypted
mode, if this parameter is set to Yes, the FTP client sends a command to switch
the transmission mode of the control connection channel to plaintext. In this
way, the state firewall can identify and dynamically open the port required for
FTP transmission; if this parameter is set to No, the FTP connection may fail to
be set up due to port restrictions imposed by the state firewall. If security
requirements are met, it is recommended that this parameter be set to Yes.

Support SSL Certificate Indicates whether the certificate authentication mode is supported when
Authentication
encrypted data is being transmitted.

5.7.1.6.2.36 FTPCLTPORT
EQUIPMENT
+-FTPCLTPORT

Description

The FTPCLTPORT MO contains the parameters related to a destination port on the FTP server
that the FTP client accesses.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
EQUIPMENT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD FTPSCLTDPORT Use this command to add a destination port that the FTP client accesses (that is,
a listening port on the FTP server). The ports have a one-to-one relationship with
destination IP addresses.

LST FTPSCLTDPORT Use this command to view the server port and IP address list that is set for the
FTP client.

MOD FTPSCLTDPORT Use this command to change a destination port that the FTP client accesses (that
is, a listening port on the FTP server). The ports have a one-to-one relationship
with destination IP addresses.

RMV FTPSCLTDPORT Use this command to remove a destination port that the FTP client accesses (that
is, a listening port on the FTP server). The port corresponds to a destination IP
address. Therefore, to remove the port is to remove the corresponding IP
address.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

FTP Server IP Address Indicates the IP address of the FTP server.

Destination Port Indicates the port of the FTP server.If no port is added to an IP address using the
ADD FTPSCLTDPORT command, port 21 is used for the IP address by default. If a
port is added to an IP address using the ADD FTPSCLTDPORT command, the
default port 21 is no longer valid for the IP address.

5.7.1.6.2.37 GPS
EQUIPMENT
+-GPS

Description

The GPS MO is a type of reference clock source. The term GPS is a collective name for all
satellite synchronization systems, including GPS, GLONASS, and COMPASS. A satellite card is
attached to the MPT or USCU. The cabinet number, subrack number, and slot number are
parameters about the MPT or USCU where the satellite card is attached.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
EQUIPMENT

Relation with the GPS MO:


- A board can be configured with one GPS MO only.
- GPS MOs must be configured on the SUBRACK MO with SRN set to 0 or 1 or configured
on the RRU MO with SRN greater than or equal to 60 and smaller than or equal to 254.
Relation with the SYNCETH,TASM MOs:
- If MODE and CLKSRC in the TASM MO are set to MANUAL and GPS+SYNCETH,
respectively, the corresponding GPS and SYNCETH MOs must have been configured.
Relation with the TASM MO:
- If MODE and CLKSRC in the TASM MO are set to MANUAL and GPS, respectively, the
corresponding GPS MO must have been configured.
Relation with the BITS MO:
- A unique combination is necessary for the following parameters: 1. CN, SRN, and SN in the
BITS MO. 2. CN, SRN, and SN in the GPS MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD GPS Use this command to add a GPS clock link. After the GPS clock link is added, if
the physical status of the satellite card is normal, this link becomes available.

DSP GPS Use this command to query the dynamic attributes of a specified GPS clock link.
The information to be queried is as follows: the physical status, type, and
working mode of the satellite receiver; the hold status of the satellite card; the
number of traced GPS satellites, that of traced GLONASS satellites, and that of
traced COMPASS satellites; the longitude, latitude, altitude, and angle of the
GPS antenna; the activation status of the GPS clock link; the latency of the GPS
feed line; the version of the satellite receiver.

DSP GPSSNR Use this command to query the signal-to-noise ratio (SNR) of satellite signals.
The SNR indicates the strength of signals received from satellites.

LST GPS Use this command to list the configuration of all GPS clock links.

LST GPSPOS Use this command to list the location information of the GPS.

MOD GPS Use this command to modify the configuration of a specified GPS clock link.

MOD GPSPOS Use this command to modify the location information of a GPS antenna.

RMV GPS Use this command to remove a specified GPS clock link.

RST SATCARD Use this command to reset a satellite card. If a satellite card is not functional,
you can run this command to restore it.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

GPS Clock No. Indicates the number of the GPS clock link.

Cabinet No. Indicates the cabinet number of the board where the satellite card is attached.

Subrack No. Indicates the subrack number of the board where the satellite card is attached.

Slot No. Indicates the slot number of the board where the satellite card is attached.

Way to Get Position Indicates the mode to obtain the position of the GPS satellite.

Antenna Longitude Indicates the longitude of the GPS antenna. A negative value indicates the west
longitude, and a positive value indicates the east longitude.

Antenna Latitude Indicates the latitude of the GPS antenna. A negative value indicates the south
latitude, and a positive value indicates the north latitude.

Antenna Altitude Indicates the altitude of the GPS antenna. A negative value indicates that the
GPS antenna is below the sea level, and a positive value indicates that the GPS
antenna is above the sea level.

Antenna Angle Indicates the antenna angle, which is the angle with the horizontal line.Value
NULL indicates that this parameter is not supported by the hardware or the
hardware is faulty.

Feeder Delay Indicates the feeder delay of the GPS clock link.

Duration Indicates the duration for tracing the position of the GPS satellite.

Precision Indicates the precision requirement for tracing the position of the GPS satellite.

Cable Type Indicates the type of the GPS feeder, which can be the twisted-pair cable or
coaxial cable. The board-mounted GPS antenna uses the coaxial cable. The
RGPS antenna uses the twisted-pair cable.

Cable Length Indicates the length of the GPS feeder. The actual feeder length is the one
between the GPS antenna and the board connected to the GPS antenna. Based on
the feeder length, the feeder delay is calculated to ensure the clock accuracy. The
clock accuracy is affected if the error between the value of this parameter and
the actual feeder length is greater than 20 m(66 ft).

GPS Version Indicates the software version of the satellite receiver. If the software version of
the satellite receiver is not supported by the satellite card, this parameter is set to
NULL.
Table 2 Related parameters

Parameter Description

GPS Position Fixed Indicates whether the position of the GPS satellite is locked by the GPS
reference receiver.

Almanac Validity Indicates whether the calendar information of the GPS reference receiver is
valid.

Position Solution Indicates whether the GPS satellite positioned by the GPS reference receiver is
valid.

Fixed Position Indicates whether the position of the GPS satellite is set on the GPS reference
receiver.

Clock Steering Indicates the clock adjusting state of the GPS reference receiver.

Clock Model Validity Indicates whether the clock mode of the GPS reference receiver is valid.

GLONASS Satellites Indicates the number of locked GLONASS satellites.


Traced

GPS Card State Indicates the physical status of the satellite card, which can be NOTEXIST
(Inexistent), ANTENNASHORTED (Antenna Shorted), ANTENNAOPENED
(Antenna Opened), SELF_CHECK_FAILURE (Self-check Failure),
COMEXCEPTION (Star Card Communication Fault), NORMAL (Normal),
UNKNOWN (Unknown Exception), USCUINVALID (USCU Invalid), or
UNKNOWN_STAR_CARD (Unknown Star Card).

GPS Card Type Indicates the physical type of the satellite card, which can be M12M, UT, RT,
K161, GG16, JNS100, RGPS, CWAIN, RTSMT, UBLOX5, BD7702, NAVIOR,
PPSTOD, M1000, TRGPS, BD7702CMS, OEM4, or N24MS.

GPS Satellites Traced Indicates the number of locked GPS satellites.

GPS Work Mode Indicates the working mode of the satellite card, which can be GPS, GLONASS,
COMPASS, GPS/GLONASS, COMPASS/GPS with COMPASS prioritized, and
GPS/COMPASS with GPS prioritized. Satellite cards are classified into dual-
mode satellite cards and single-mode satellite cards. A dual-mode satellite card
supports two satellite searching modes. For example, the working mode of a
COMPASS/GPS satellite card can be COMPASS prioritized or GPS prioritized.
In COMPASS prioritized mode, the satellite card processes signals from
COMPASS satellites only. In GPS prioritized mode, the satellite card processes
signals from GPS satellites only. A single-mode satellite card supports only one
satellite searching mode. For example, a satellite card working in GPS mode.

COMPASS Satellites Indicates the number of locked COMPASS satellites.


Traced
Table 2 Related parameters

Parameter Description

Link Active State Indicates the activation status of the GPS clock link. If the link is active, the
GPS clock link is the current clock source of the system.

Priority Indicates the priority of the clock source. The value 1 indicates the current clock
source has the highest priority, and the value 4 indicates the current clock source
has the lowest priority.

Hold Status Indicates the hold status of a satellite card.

5.7.1.6.2.38 GTMU
EQUIPMENT
+-CABINET
+-SUBRACK
+-GTMU
+-CPRIPORT[6~6]
+-SFP[6~6]

Description

None

Effective Scenario

Immediately

Relations Between MOs

Base class:
RU

Possible parents:
SUBRACK

Possible children:
CPRIPORT[6~6];SFP[6~6]

Relation with the BBP,BRI,RHUB,RRUCHAIN MOs:


- When the RRUCHAIN MO whose AT is set to a value other than PEERPORT, one of the
following BBP, BRI , GTMU or RHUB MOs must have been configured:
- 1. A BBP, BRI, GTMU or RHUB MO corresponding to HCN, HSRN, and HSN.
- 2. A BBP, BRI, GTMU or RHUB MO corresponding to TCN, TSRN, and TSN in the
RRUCHAIN MO when TT in the RRUCHAIN MO is set to a value other than CHAIN.
Relation with other boards in the BBU subrack:
- A unique combination is necessary for the following parameters: 1. CN, SRN, and SN in the
GTMU MO; 2. CN, SRN, and SN in the TRP MO; 3. CN, SRN, and SN in the UCIU MO; 4.
CN, SRN, and SN in the MPT MO.
Relation with the RRUCHAIN,BBP,BRI MOs:
- In the RRUCHAIN MO, when TT is set to RING and the combination of HCN, HSRN, and
HSN is not the same as the combination of TCN, TSRN, and TSN, this RRUCHAIN cannot be
configured on the BRI, GTMU, or BBP with TYPE set to GBBP.
- When the TT in the RRUCHAIN MO is set to LOADBALANCE, the total number of BBP
MO with the TYPE set to GBBP, BRI MO, and GTMU MO where the RRUCHAIN MO is
configured must be 0 or 1.

Related Parameters

Table 1 describes the parameters related to this MO.

Table 1 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the baseband radio interface board.

Subrack No. Indicates the subrack number of the baseband radio interface board.

Slot No. Indicates the slot number of the baseband radio interface board.

Board Type Indicates the type of the board.

Administrative state Indicates the administrative state of the board. The administrative state of the
board can be locked, unlocked, or shutting down. For details, see ITU-T X.731.

Duration of the shutting Indicates the scheduled duration before a board is blocked.
down state

Block Type Indicates the block type of the board. IMMEDIATE (Immediate) means that the
board is blocked and services carried on the board are interrupted immediately
after the command is executed. SHUTDOWN (Shutdown) means that the board
is blocked when no service is carried on the board. DELAY (Delay) means that
the board is blocked and services carried by the board are interrupted after a
Table 1 Related parameters

Parameter Description

scheduled duration.

Alarm Status(from RU) Indicates the alarm status of the board. The alarm state of the board can be
normal, warning, minor or critical. For details about the definition of Alarm
Status, see ITU-T X.731.

Operational State(from Indicates the operational state of the board, which can be set to Enabled or
RU)
Disabled. Enabled indicates that services can be carried on the board. Disabled
indicates that no service can be carried on the board.

Availability Status(from Indicates the physical operation status of the board, which can be Uninstalled,
RU)
Starting up, Normal, Inconsistent, Unconfigured, Power off, Fault,
Communication lost, In test, or the combination of various states. For example,
if a board is not configured and fails to communicate with the main control and
transmission board, the physical operation status of the board is Unconfigured,
Communication lost.

Electronic Label(from Indicates the E-label, a text file with a maximum of 2 KB. It is used to record the
RU)
manufacturing information about equipment such as the board, sub-board, or
optical module. Among board properties displayed in the text file, "BoardType"
indicates the type of the board, "BarCode" indicates the bar code of the board
and is the same as the code labeled on the board, and "Item" indicates the BOM
code.

Type(from RU) Indicates the type of the board.

Serial Number(from Indicates the bar code of the board or the cabinet.
RU)

Description(from RU) Indicates the description about the services and functions provided by the board
or the cabinet.

Date of Indicates the manufacturing date of the board or the cabinet.


Manufacture(from RU)

Vendor(from RU) Indicates the manufacturer of the board or the cabinet.

Issue Number(from RU) Indicates the issue number of the board.

Config Type(from RU) Indicates the type of a board.

Board Indicates the temperature of a board.


Temperature(from RU)

HPA Temperature(from Indicates the temperature of the power amplifier.


RU)
Table 1 Related parameters

Parameter Description

DEVTYPE(from RU) Indicates the type of the device.

Software Version(from Indicates the software version of the board.


RU)

Hardware Version(from Indicates the hardware version of the board.


RU)

BootRom Version(from Indicates the BootROM version of the board.


RU)

5.7.1.6.2.39 HTCDPA
EQUIPMENT
+-CABINET
+-SUBRACK
+-TCU
+-HTCDPA

Description

The HtCDPa MO consists of the heat control delta parameters related to the TCU with a
breathable film.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TCU

Relation with the TCU MO:


- The TCU MO corresponding to CN, SRN, and SN in the HTCDPA MO must have been
configured.
- The number of HTCDPA MOs configured on one TCU MO must be 1.

Related MML Commands


Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST HTCDPA Use this command to list the configuration of the temperature control unit
(TCU) heat control delta parameters. This command is applicable only to a TCU
of the direct-ventilation type or a TCU with a breathable film.

MOD HTCDPA Use this command to modify the temperature control unit (TCU) heat control
delta parameters. This command is applicable only to the TCU of the direct-
ventilation type and that with a breathable film.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet where the TCU is located.

Subrack No. Indicates the number of the subrack where the TCU is located.

Slot No. Indicates the number of the slot where the TCU is located.

Low Temperature Indicates the threshold of the low temperature state.


Critical Point

High Temperature Indicates the threshold of the high temperature state.


Critical Point

Temperature Limit at Air Indicates the expected lowest temperature at the air outlet.
Outlet

Dead Band Indicates the tolerable error value of temperature control.

Normal Temperature Indicates the difference between the temperature at the air inlet and that of the
Delta Tin
environment at the normal temperature.

Normal Temperature Indicates the difference between the temperature at the air outlet and that of the
Delta Tout
air inlet at the normal temperature.

High Temperature Delta Indicates the difference between the temperature at the air outlet and that of the
Tout
environment at the high temperature.
5.7.1.6.2.40 IPCLKLNK
EQUIPMENT
+-IPCLKLNK

Description

An IpClkLink MO indicates an IP clock link. The IP clock complies either with the IEEE1588
V2 standard or Huawei proprietary IP clock protocol.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
EQUIPMENT

Relation with the SYNCETH,TASM MOs:


- If MODE and CLKSRC in the TASM MO are set to MANUAL and SYNCETH+IPCLK,
respectively, the corresponding SYNCETH and IPCLKLNK MOs must have been configured.
Relation with the TASM MO:
- If MODE and CLKSRC in the TASM MO are set to MANUAL and IPCLK, respectively,
the corresponding IPCLKLNK MO must have been configured.
Relation with the DEVIP MO:
- Before creating an IPCLKLNK MO, the corresponding DEVIP MO must have been
configured. The corresponding relationship of the two MOs is as follows: 1. CN, SRN, and SN
in the IPCLKLNK MO must be the same as CN, SRN, and SN respectively in the DEVIP MO.
2. CIP in the IPCLKLNK MO must be the same as IP in the DEVIP MO.
- Before creating an IPCLKLNK MO, the corresponding DEVIP MO must have been
configured. In addition, PT in the DEVIP MO must be set to LOOPINT, ETH, ETHTRK, or
- SUBIF.
Relation with the DEVIP6 MO:
- When IPMODE in the IPCLKLNK MO is set to IPV6,the corresponding DEVIP6 MO
must have been configured.The corresponding relationship of the two MOs is as follows: 1. CN,
SRN, and SN in the IPCLKLNK MO must be the same as CN, SRN, and SN respectively in the
DEVIP6 MO. 2. CIPV6 in the IPCLKLNK MO must be the same as IPV6 in the IPITF6 MO.
which is corresponding to DEVIP6 MO.
Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD IPCLKLINK Use this command to add an IP clock link. If the BS can obtain synchronization
signals properly from the IP clock server, this link becomes available.

DSP IPCLKLINK Use this command to query the status of an IP clock link. If the link number is
not specified, the status of all IP clock links is displayed.

DSP PRICLASS Use this command to query priority clock classes.

LST IPCLKLINK Use this command to list the configuration of all the IP clock links.

LST PRICLASS Use this command to list the settings of clock classes.

RMV IPCLKLINK Use this command to remove a specified IP clock link.

SET CLASSIDENTIFY Use this command to set the flag for the priority clock class of a specified IP
clock link. If the IP clock link complies with the Precision Time Protocol (PTP)
but the peer clock server does not support standardized priority clock classes,
you can run this command to set the identifier for the priority clock class to
OFF.

SET PRICLASS Use this command to set priorities for the four clock classes of a specified IP
clock link. This command is applicable only when the IEEE1588 v2 standard is
supported.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Link No. Indicates the number of the IP clock link.

Protocol Type Indicates the type of the IP clock protocol, which can be PTP or Huawei
proprietary protocol. PTP includes IEEE1588 V2 and G.8265.1. IEEE1588 V2,
defined by the IEEE, supports both time synchronization and frequency
Table 2 Related parameters

Parameter Description

synchronization. G.8265.1 supports frequency synchronization only. Huawei


proprietary protocol, which is the Huawei-defined IP clock protocol, applies to
the interconnection between Huawei equipment and supports frequency
synchronization only.

Cabinet No. Indicates the number of the cabinet where the IP clock link is configured.

Subrack No. Indicates the number of the subrack where the IP clock link is configured.

Slot No. Indicates the number of the slot where the IP clock link is configured.

Client IPv4 Indicates the client IPv4 address of the IP clock link.

Server IPv4 Indicates the server IPv4 address of the IP clock link.

Domain Indicates the domain to which the IP clock link belongs. The setting of this
parameter must be the same as the setting of the clock server.

Delay Type Indicates the compensation mechanism for the transmission delay between the
clock server and the base station. The E2E mode uses the Delay-Request-
Response mechanism to measure the average delay between the primary and
secondary devices. The P2P mode uses the Peer-Delay mechanism to measure
the average delay between two devices.

Priority Clock Class Indicates whether the BMC (Best Master Clock) algorithm is enabled or not. ON
Identify Flag
indicates that the BMC algorithm is enabled, and OFF indicates that the BMC
algorithm is disabled.

Priority Clock Class0 Indicates the priority configured by the user for the BMC (Best Master Clock)
algorithm. The information about the priority can be collected from the upper-
level clock equipment. This parameter specifies the clock quality that is
anticipated by the user. The upper-level clock equipment with the matching
clock quality is selected as the target server. Class0 has the highest priority, and
Class0 to Class3 indicate priorities in descending order.

Priority Clock Class1 Indicates the priority configured by the user for the BMC (Best Master Clock)
algorithm. The information about the priority can be collected from the upper-
level clock equipment. This parameter specifies the clock quality that is
anticipated by the user. The upper-level clock equipment with the matching
clock quality is selected as the target server. Class0 has the highest priority, and
Class0 to Class3 indicate priorities in descending order.

Priority Clock Class2 Indicates the priority configured by the user for the BMC (Best Master Clock)
algorithm. The information about the priority can be collected from the upper-
Table 2 Related parameters

Parameter Description

level clock equipment. This parameter specifies the clock quality that is
anticipated by the user. The upper-level clock equipment with the matching
clock quality is selected as the target server. Class0 has the highest priority, and
Class0 to Class3 indicate priorities in descending order.

Priority Clock Class3 Indicates the priority configured by the user for the BMC (Best Master Clock)
algorithm. The information about the priority can be collected from the upper-
level clock equipment. This parameter specifies the clock quality that is
anticipated by the user. The upper-level clock equipment with the matching
clock quality is selected as the target server. Class0 has the highest priority, and
Class0 to Class3 indicate priorities in descending order.

Current Priority Clock Indicates the current priority class of the IP clock link.
Class

Clock Source Specified Indicates whether the clock source is specified.


or Not

Clock Source MAC Indicates the MAC address of the clock source for the IP clock server. The MAC
Address
address must be in the format of XXXX-XXXX-XXXX.

Link Active State Indicates the activation status of the IP clock link. If the IP clock link is active, it
is the current clock source of the system.

Link Available State Indicates the availability of the IP clock link. Only an available clock link can
serve as the current clock source. Otherwise, the clock link cannot be locked
even if it is activated.

Clock Net Mode Indicates the networking type for the IP clock. The LTE currently does not
support L3 Multicast function.

Compensation Indicates the compensation for asymmetry of IP clock links.

Number of Disorder Indicates the number of out-of-order packets over the IP clock link. The LTE
Packets
currently does not support this function.

Number of Dropped Indicates the number of packets lost over the IP clock link. The LTE currently
Packets
does not support this function.

Number of Received Indicates the number of synchronization packets received over the IP clock link.
Packets
The LTE currently does not support this function.

Step Mode Indicates the step mode, which can be One Step or Two Step.

VLAN ID Indicates the self-acquired VLAN ID of the IP clock server.


Table 2 Related parameters

Parameter Description

Priority Indicates the priority of the clock source. The value 1 indicates that the current
clock source has the highest priority, and the value 4 indicates that the current
clock source has the lowest priority.

Announce Freq Indicates the frequency at which the clock source sends announcement packets
based on its negotiation with the BS.

Sync Freq Indicates the frequency at which the clock source sends synchronization packets
based on its negotiation with the BS.

Master Priority Indicates the priority of the IP clock server. The value 0 indicate the highest
priority, and the value 255 indicates the lowest priority.If two IP clock servers
are required, the value of this parameter is used to identify the active and
standby IP clock servers. The IP clock server with a higher priority serves as the
active server and the IP clock server with a lower priority serves as the standby
server.

Profile Type Indicates the type of protocol supported by the IEEE 1588 V2-compliant IP
clock link, which can be ITU-T G.8265.1 or IEEE 1588 V2. ITU-T G.8265.1 is
defined by the International Telecommunication Union (ITU) for frequency
synchronization of an IEEE 1588 V2-compliant IP clock link with the
networking type of UNICAST. An IP clock link in compliant with ITU-T
G.8265.1 supports interconnection with servers from other vendors. An IP clock
link in compliant with IEEE 1588 V2 does not support interconnection with
servers from other vendors.

Negotiate Duration Indicates the interval at which negotiations are performed between the BS and
IP clock server. After the interval elapses, the BS initiates another negotiation
with the IP clock server.

IP mode Indicates the mode of the IP address.

Client IPv6 Indicates the client IPv6 address of the IP clock link. The UMTS currently does
not support this function.

Server IPv6 Indicates the server IPv6 address of the IP clock link. The UMTS currently does
not support this function.

Pre-Hop IPv4 Indicates the pre-hop IPv4 address of an IP clock.

PDelay Request Freq Indicates the frequency at which PDelay Request packets are sent on an IP clock
link.
5.7.1.6.2.41 LINECLK
EQUIPMENT
+-LINECLK

Description

A LineClk MO is the E1/T1 line clock, which is a type of reference clock source. The E1/T1 line
clock is usually configured on the main control board or a transmission board. The cabinet
number, subrack number, slot number, and port number are parameters of the board where the
E1/T1 line clock is configured.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
EQUIPMENT

Relation with the TASM MO:


- If MODE and CLKSRC in the TASM MO are set to MANUAL and LINECLK,
respectively, the corresponding LINECLK MO must have been configured.
Relation with the PORTSECURITY MO:
- If the PORTSECURITY MO corresponding to CN, SRN, SN, and PN in the LINECLK
MO has been configured, SWITCH in this PORTSECURITY MO must be set to ENABLE.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD LINECLK Use this command to add an E1/T1 line clock link. If the BS can properly obtain
synchronization signals from the E1/T1 line clock, this link becomes available.

DSP LINECLK Use this command to query the running status of a specified E1/T1 line clock
link.
Table 1 Related MML commands

MML Command Function

LST LINECLK Use this command to list the configuration of all E1/T1 line clock links.

MOD LINECLK Use this command to modify the priority of an E1/T1 line clock link.

RMV LINECLK Use this command to remove a specified E1/T1 line clock link.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Line Clock No. Indicates the number of the E1/T1 line clock link.

Cabinet No. Indicates the number of the cabinet where the E1/T1 line clock link is
configured.

Subrack No. Indicates the number of the subrack where the E1/T1 line clock link is
configured.

Slot No. Indicates the number of the slot where the E1/T1 line clock link is configured.

Port Type Indicates the type of the port where the line clock link is located. The LTE
currently does not support STM1 function.

Port No. Indicates the number of the port where the E1/T1 line clock link is configured.

Link Active State Indicates the activation status of the E1/T1 line clock link. If the link is active,
the E1/T1 line clock link is the current clock source of the system.

Link Available State Indicates the availability of the E1/T1 line clock link. Only an available clock
link can serve as the current clock source. Otherwise, the clock link cannot be
locked even if it is activated.

Priority Indicates the priority of the clock source. The value 1 indicates that the current
clock source has the highest priority, and the value 4 indicates that the current
clock source has the lowest priority.
5.7.1.6.2.42 LOCATION
EQUIPMENT
+-LOCATION

Description

None

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
EQUIPMENT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD LOCATION Use this command to add a record of the Location.

LST LOCATION Use this command to query the parameters of the Location.

MOD LOCATION Use this command to modify the data record of the Location.

RMV LOCATION Use this command to delete a record of the Location.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

address Indicates the address of the base station.

Altitude Indicates the altitude of the base station.

City Indicates the city where the base station is located.

Contact Indicates the addresses related to this base station or telephone numbers of the
personnel related to this base station.

Geo-coordinate Data Indicates the format of geographical coordinates.


Format

Latitude With Degree Indicates the latitude of the base station. A negative value indicates the south.
Format

Latitude With Second Indicates the latitude of the base station in the WGS-84 coordinate system.
Format

Location Id Indicates the location ID of the base station.

Location Name Indicates the location name of the base station.

Longitude With Degree Indicates the longitude of the base station. A negative value indicates the west.
Format

Longitude With Second Indicates the longitude of the base station in the WGS-84 coordinate system.
Format

Office Indicates the site that the base station belongs to.

Range Indicates the range of the location.

Region Indicates the block where the base station is located.

Telephone Indicates the telephone number of the maintenance personnel of the base station.

User Label Indicates the user-defined information of the location.

Precise Indicates the positioning accuracy of the the base station's geographical location.
This parameter defines the radius of a sphere with the named longitude, latitude
and altitude as its centre.
The actual location is in this sphere.

5.7.1.6.2.43 MAINSALARMBIND
EQUIPMENT
+-MAINSALARMBIND

Description

None

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
EQUIPMENT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST NMSABIND Use this command to list the bind relation of the Mains Input Out of Range
alarm.

MOD NMSABIND Use this command to modify the bind relation of the Mains Input Out of Range
alarm.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Base Station Almport Indicates the Base Station Almport Switch.


Switch

Almport Cabinet No. Indicates the Almport Cabinet No.


Table 2 Related parameters

Parameter Description

Almport Subrack No. Indicates the Almport Subrack No.

Almport Slot No. Indicates the Almport Slot No.

Almport Port No. Indicates the Almport Port No.

5.7.1.6.2.44 MPT
EQUIPMENT
+-CABINET
+-SUBRACK
+-MPT
+-SFP[3~3]
+-CASCADEPORT[1~1]

Description

The MPT MO performs main controlling, switching, and transmission, and provides clock
sources.
Main control: involves O&M functions such as configuration management, device management,
performance monitoring, signaling processing, and active/standby switchover, and controls each
board in the system.
Switching: forwards low-speed UP data and control/maintenance signals from all boards in the
BBU to destination ports through a low-speed bus.
Clock: integrates the OCXO and phase-lock module to provide unified clock for all traffic
boards. You can enable the MPT to support the integration of a single satellite card or not.
Through the integrated single satellite card, the MPT can provide absolute time information and
1PPS reference clock source. The extraction of the IP clock source is supported.
Transmission: implemented using the transmission port.

Effective Scenario

Immediately

Relations Between MOs


Base class:
RU

Possible parents:
SUBRACK

Possible children:
SFP[3~3];CASCADEPORT[1~1]

Relation with other boards in the BBU subrack:


- A unique combination is necessary for the following parameters: 1. CN, SRN, and SN in the
TRP MO; 2. CN, SRN, and SN in the UCIU MO; 3. CN, SRN, and SN in the MPT MO;4. CN,
SRN, and SN in the GTMU MO.
Relation with the SUBRACK MO:
- The number of MPT MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 2.
Relation with the CASCADEPORT MO:
- When the combination of CN, SRN and SN in the CASCADEPORT MO is same as the
combination of CN, SRN and SN in the MPT MO, the PT of CASCADEPORT must be set to
BasicCascadePort.
Relation with the MPT MO:
- The number of MPT MOs configured on slave BBU subrack must be smaller than or equal
to 1.
Relation with the ETHPORT MO:
- When TYPE in MPT is LMPT, If PA is AUTO in ETHPORT on the LMPT board, the
SPEED and DUPLEX of the ETHPORT must be AUTO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP LOCALUSBPORT Use this command to query the USB Port status.

LST LOCALUSBPORT Use this command to list the configuration of the USB Port.

SET LOCALUSBPORT Use this command to modify the configuration of the USB Port. This command
applies only to the main control boards.
Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the main control and transmission board.

Subrack No. Indicates the subrack number of the main control and transmission board.

Slot No. Indicates the slot number of the main control and transmission board.

Board Type Indicates the type of the board.

Enable Flag Indicates whether to enable the USB port. When this parameter is set to
DISABLE, the USB port is disabled. When this parameter is set to ENABLE,
the USB port is enabled.

Standby Status Indicates the active, standby or slave status of the main control and transmission
board. The active or standby status is available only to the main control and
transmission board. This parameter for other types of board is set to NULL.
When a board is in an abnormal state, Unknown is displayed.

Alarm Status(from RU) Indicates the alarm status of the board. The alarm state of the board can be
normal, warning, minor or critical. For details about the definition of Alarm
Status, see ITU-T X.731.

Operational State(from Indicates the operational state of the board, which can be set to Enabled or
RU)
Disabled. Enabled indicates that services can be carried on the board. Disabled
indicates that no service can be carried on the board.

Availability Status(from Indicates the physical operation status of the board, which can be Uninstalled,
RU)
Starting up, Normal, Inconsistent, Unconfigured, Power off, Fault,
Communication lost, In test, or the combination of various states. For example,
if a board is not configured and fails to communicate with the main control and
transmission board, the physical operation status of the board is Unconfigured,
Communication lost.

Electronic Label(from Indicates the E-label, a text file with a maximum of 2 KB. It is used to record the
RU)
manufacturing information about equipment such as the board, sub-board, or
optical module. Among board properties displayed in the text file, "BoardType"
indicates the type of the board, "BarCode" indicates the bar code of the board
and is the same as the code labeled on the board, and "Item" indicates the BOM
code.
Table 2 Related parameters

Parameter Description

Type(from RU) Indicates the type of the board.

Serial Number(from Indicates the bar code of the board or the cabinet.
RU)

Description(from RU) Indicates the description about the services and functions provided by the board
or the cabinet.

Date of Indicates the manufacturing date of the board or the cabinet.


Manufacture(from RU)

Vendor(from RU) Indicates the manufacturer of the board or the cabinet.

Issue Number(from RU) Indicates the issue number of the board.

Config Type(from RU) Indicates the type of a board.

Board Indicates the temperature of a board.


Temperature(from RU)

HPA Temperature(from Indicates the temperature of the power amplifier.


RU)

DEVTYPE(from RU) Indicates the type of the device.

Software Version(from Indicates the software version of the board.


RU)

Hardware Version(from Indicates the hardware version of the board.


RU)

BootRom Version(from Indicates the BootROM version of the board.


RU)

5.7.1.6.2.45 NE
NE
+-NODE[1~1]

Description

The root of NE model.

Effective Scenario
Not involved

Relations Between MOs

Possible children:
NODE[1~1]

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST NE Use this command to list Network Element configuration.

SET NE Use this command to set Network Element Name,Site Location,Deployment


Identifier,Site Name and User Label.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Site Location Indicates the location of the base station.

Software Version Indicates the software version of the NE.

User Label Indicates the user-defined information of the NE.

NeRM Version Indicates the module version of NE resources, including the MOC, attributes,
and configuration rules.

Product InterfaceID Indicates the ID of the product interface.

Product Version Indicates the product software version of the base station.

LMT Version Indicates the LMT version.

Deployment Identifier Indicates the deployment identifier that specifies the site of the NE. When
Table 2 Related parameters

Parameter Description

multiple NEs are deployed at the same site, these NEs have the same
deployment identifier.

Site Name Indicates the site name. When multiple NEs are at the same site, these NEs are
configured with the same site name.

Network Element Name Indicates the NE name.

5.7.1.6.2.46 NODE
+-NE
+-NODE
+-EQUIPMENT[1~1]
+-TRANSPORT[1~1]
+-CARRIERRESOURCE[1~1]
+-APPLICATION[1~1]

Description

The root of the common resource model other than RAT specific resource models.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
NE

Possible children:
EQUIPMENT[1~1];TRANSPORT[1~1];CARRIERRESOURCE[1~1];APPLICATION[1~1]

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

LST NODE Use this command to list Node configuration.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Product Type Indicates the type of an NE.

User Label Indicates the user-defined information of a node.

NeRM Version Indicates the resouce model version of the node.

Node Identifier Indicates the unique identifier of a node within a base station.

Node Name Indicates the node name.

Working Mode Indicates the working mode of a base station. The value of this parameter can
only be Non-ConCurrent when the product type of the NE is not DBS3900,
BTS3900, BTS3900A, BTS3900L, or BTS3900AL.

5.7.1.6.2.47 NTPCP
EQUIPMENT
+-NTPCP

Description

The NtpCp MO is used to manage the parameters that are set in the NTP client, such as the IP
address of the time server, port number, synchronization period, and synchronization switch.
The Network Time Protocol (NTP) is a protocol designed for time synchronization of computers.
By NTP, the time of the computers is synchronized with the time server or time source (such as
GPS and a quartz clock) with high accuracy of time calibration. For example, the time difference
from the standard reference is tens of milliseconds in a WAN or less than one millisecond in a
LAN. In addition, encryption is used to protect NTP against attacks from other protocols. The
NTP client in the NE is synchronized with the external NTP server by NTP.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
EQUIPMENT

Relation with the NTPCP MO:


- There can be only one master NTPCP at most.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD NTPC Use this command to add a Network Time Protocol (NTP) client to an NE.

DSP NTPC Use this command to display the running state of a Network Time Protocol
client (NTPC).

LST NTPC Use this command to list Network Time Protocol (NTP) client parameters for an
NE.

MOD NTPC Use this command to modify configurations for the Network Time
Protocol(NTP) client of an NE with the IP Address of NTP Server parameter set
to the used value.

RMV NTPC Use this command to remove the NTP client of the NE.

SET MASTERNTPS Use this command to set a Network Time Protocol (NTP) server as a master
NTP server. The server must have been added by running the ADD NTPC
command.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

IPv4 Address of NTP Indicates the IPv4 address of the NTP server.
Server

Synchronization Period Indicates the period based on which NTP time synchronization is performed
periodically. The switch for periodic NTP time synchronization is turned on
automatically.The time of a base station may have differences with the standard
time, and a large difference affects the accuracy of KPIs. Therefore, a period
must be configured for the base station to perform time synchronization with the
NTP server periodically to ensure the accurate time.
The period for periodic NTP time synchronization must be configured based on
the NTP server performance, transport network quality, and base station
quantity.
A smaller period for periodic NTP time synchronization leads to higher loads for
the NTP server and transport network. A larger period leads to lower loads.

Port Number Indicates the port number of the NTP server. An NTP client performs time
calibration with the NTP server through the port specified by this parameter.

IP Mode Indicates the mode of the IP address of the NTP server.

IPv6 Address of NTP Indicates the IPv6 address of the NTP server.
Server

Authentication Mode Indicates the encryption mode. If this parameter is set to PLAIN, data is
transmitted in plaintext.

Authentication Key Indicates the key used for NTP authentication.


The key used in the DES_S algorithm is a hexadecimal number whose length is
64 bits in binary format. The seven least significant bits of each byte are used to
construct 56-bit key data, and the eighth bit is the odd parity bit for each byte.
Any empty bit is filled with 0 to ensure that the key data is composed of 16
hexadecimal digits and has an odd number for parity check. The key used in the
DES_N algorithm is similar to the key used in the DES_S algorithm. The only
difference is that in the key used in the DES_N algorithm, the most significant
bit is used for parity check of each byte. The key used in the DES_A algorithm
is an ASCII string of one to eight characters. The seven least significant digits of
the ASCII value corresponding to each character are used to construct 56-bit key
data. For any ASCII string of less than eight characters, 0s are appended to the
string to ensure that the key data is composed of 56 bits. The key used in the
MD5 algorithm is an encrypted ASCII string of one to eight characters.

Authentication Key Indicates the server-side index of the NTP authentication key. The index must be
Index
the same as the setting on the server.

Master Flag Indicates an NTP server is an active or standby server.


Table 2 Related parameters

Parameter Description

Users can run the SET MASTERNTPS command to set an NTP server as a master
NTP server.

5.7.1.6.2.48 OMUCURTIME
Description

The OmuCurTime MO is used to manage the current date and time information of the NE.

Effective Scenario

Immediately

Relations Between MOs

None

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP TIME Use this command to query the current time of the NE.

SET TIME Use this command to set the current date and time of the NE. The date and time
are modified separately.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Date Indicates the date to be set for the NE.


The format is as follows: YYYY-MM-DD. For example, 2006-09-08 indicates
September 8th of 2006.

Time Indicates the time to be set for the NE.


The format is as follows: HH:MM:SS. For example, 10:20:05.

Time Indicates the current date and time of the NE. The query result is the local time
of the NE, including the year, month, day, hour, minute, second, and time zone.
If the DST of the NE is effective, the query result contains a DST flag (the flag
used to indicate whether the DST is applied). The format is as follows: YYYY-
MM-DD HH:MM:SS.

5.7.1.6.2.49 OUTPORT
EQUIPMENT
+-CABINET
+-SUBRACK
+-EMU
+-OUTPORT

Description

An OutPort MO is supported only by an EMU. It connects to environment equipment. The


output port controls environment equipment to perform functions such as refrigerating,
humidifying, dehumidifying, fire extinguishing, heating, and burglarproofing.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
EMU

Relation with the EMU MO:


- The number of OUTPORT MOs configured on one EMU MO must be 6.
Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST OUTPORT Use this command to list the configuration of an output port (relay).

SET OUTPORT Use this command to modify the configuration of an output port (relay).

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the board where the output port is located.

Subrack No. Indicates the subrack number of the board where the output port is located.

Slot No. Indicates the slot number of the board where the output port is located.

Port No. Indicates the number of the output port.

Port Name Indicates the name of the output port.

Port Switch Indicates the enabled/disabled state of the output port.

5.7.1.6.2.50 PEERCLK
EQUIPMENT
+-PEERCLK

Description

A PeerClk MO is the peer reference clock, which is a reference clock source. In a multi-mode
BS, the peer reference clock is shared by multiple modes. Currently, only one peer reference
clock can be shared by multiple modes. The cabinet number, subrack number, and slot number
do not need to be specified for configuration of the peer reference clock link. In a single-mode
BS, the peer reference clock link is not applicable. In a multi-mode BS, the peer reference clock
link cannot be configured as reference clock for all modes.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
EQUIPMENT

Relation with the TASM MO:


- If MODE and CLKSRC in the TASM MO are set to MANUAL and PEERCLK,
respectively, the corresponding PEERCLK MO must have been configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD PEERCLK Use this command to add a peer reference clock link. If the BS can properly
obtain synchronization signals from the peer reference clock, this link becomes
available.

DSP PEERCLK Use this command to query the running status of a specified peer reference clock
link.

LST PEERCLK Use this command to list the configuration of the peer reference clock link.

RMV PEERCLK Use this command to remove a specified peer reference clock link.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Peer Clock No. Indicates the number of the peer reference clock link.

Peer Standard Indicates the standard of the peer reference clock. The standard of the peer
reference clock is another standard in the same BBU subrack by default.

Link Active State Indicates the activation status of the peer reference clock link. If the link is
active, the peer reference clock link is the current clock source of the system.

Link Available State Indicates the availability of the peer reference clock link. Only an available
clock link can serve as the current clock source. Otherwise, the clock link cannot
be locked even if it is activated.

5.7.1.6.2.51 PEU
EQUIPMENT
+-CABINET
+-SUBRACK
+-PEU
+-ALMPORT[8~8]

Description

The PEU MO is the power and environment unit (PEU) that is used to convert -48 V DC or +24
V DC power to +12 V DC power for the boards in the BBU subrack. A BBU subrack can be
configured with a maximum of two PEUs. Each PEU supports eight dry contact alarms for
environment monitoring.

Effective Scenario

Immediately

Relations Between MOs

Base class:
RU

Possible parents:
SUBRACK
Possible children:
ALMPORT[8~8]

Relation with the ALMPORT MO:


- The number of ALMPORT MOs configured on one PEU MO must be 8.
Relation with the SUBRACK MO:
- The number of PEU MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 2.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP UPEU Use this command to query the UPEU status, including the spare power of the
UPEU and the BBU.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet where the PEU is located.

Subrack No. Indicates the number of the subrack where the PEU is located.

Slot No. Indicates the number of the slot where the PEU is located.

UPEU Spare Power Indicates the spare power of the UPEU.

BBU Spare Power Indicates the spare power of the BBU.

Alarm Status(from RU) Indicates the alarm status of the board. The alarm state of the board can be
normal, warning, minor or critical. For details about the definition of Alarm
Status, see ITU-T X.731.

Operational State(from Indicates the operational state of the board, which can be set to Enabled or
Table 2 Related parameters

Parameter Description

RU) Disabled. Enabled indicates that services can be carried on the board. Disabled
indicates that no service can be carried on the board.

Availability Status(from Indicates the physical operation status of the board, which can be Uninstalled,
RU)
Starting up, Normal, Inconsistent, Unconfigured, Power off, Fault,
Communication lost, In test, or the combination of various states. For example,
if a board is not configured and fails to communicate with the main control and
transmission board, the physical operation status of the board is Unconfigured,
Communication lost.

Electronic Label(from Indicates the E-label, a text file with a maximum of 2 KB. It is used to record the
RU)
manufacturing information about equipment such as the board, sub-board, or
optical module. Among board properties displayed in the text file, "BoardType"
indicates the type of the board, "BarCode" indicates the bar code of the board
and is the same as the code labeled on the board, and "Item" indicates the BOM
code.

Type(from RU) Indicates the type of the board.

Serial Number(from Indicates the bar code of the board or the cabinet.
RU)

Description(from RU) Indicates the description about the services and functions provided by the board
or the cabinet.

Date of Indicates the manufacturing date of the board or the cabinet.


Manufacture(from RU)

Vendor(from RU) Indicates the manufacturer of the board or the cabinet.

Issue Number(from RU) Indicates the issue number of the board.

Config Type(from RU) Indicates the type of a board.

Board Indicates the temperature of a board.


Temperature(from RU)

HPA Temperature(from Indicates the temperature of the power amplifier.


RU)

DEVTYPE(from RU) Indicates the type of the device.

Software Version(from Indicates the software version of the board.


RU)

Hardware Version(from Indicates the hardware version of the board.


RU)
Table 2 Related parameters

Parameter Description

BootRom Version(from Indicates the BootROM version of the board.


RU)

5.7.1.6.2.52 PMU
EQUIPMENT
+-CABINET
+-SUBRACK
+-PMU
+-BATTERY[0~1]
+-ALMPORT[0~5]
+-DIESELGEN[0~1]

Description

The PMU MO monitors and manages the voltage, current, load, power source temperature,
battery, and diesel generator of the power system.

Effective Scenario

Immediately

Relations Between MOs

Base class:
RU

Possible parents:
SUBRACK

Possible children:
BATTERY[0~1];ALMPORT[0~5];DIESELGEN[0~1]

Relation with the SUBRACK,CTRLLNK MOs:


- If the MO corresponding to MCN and MSRN in the PMU MO is a SUBRACK MO with
SRN of 0 or 1, the SUBRACK MO cannot be a secondary subrack.
Relation with the ALMPORT MO:
- The number of ALMPORT MOs configured on one PMU MO must be greater than or equal
to 0 and smaller than or equal to 5.
Relation with the SUBRACK MO:
- The number of PMU MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 1.
Relation with the TCU, PMU, EMU,and FMUMOs:
- It is not allowed in the following cases: 1. The combination of MCN, MSRN, MPN, and
ADDR in the PMU MO is same as the combination of those in other PMU MOs; 2. The
combination of MCN, MSRN, MPN, and ADDR in the PMU MO is same as the combination
of those in the EMU MOs; 3. The combination of MCN, MSRN, MPN, and ADDR in the PMU
MO is same as the combination of those in the TCU MOs; 4. The combination of MCN, MSRN,
MPN, and ADDR in the PMU MO is same as the combination of those in the FMU MOs; 5.
The combination of MCN, MSRN, and MPN in the PMU MO is same as the combination of
those in the CCU MOs, and ADDR in the PMU MO is equal to 21.
Relation with the DIESELGEN MO:
- Only a PMU MO with PTYPE set to SC48200 can be configured with a lower-level
DIESELGEN MO.
- The number of DIESELGEN MOs configured on one PMU MO must be greater than or
equal to 0 and smaller than or equal to 1.
Relation with the SUBRACK,RRU,CCU MOs:
- The MO corresponding to MCN and MSRN in the PMU MO must have been configured
and be one of the following types: 1. A SUBRACK MO with SRN set to 0 or 1; 2. A RRU MO;
3. A CCU MO.
Relation with the PSU MO:
- The PMU MO corresponding to a PSU MO must have been configured.
- The upper-level PMU MO of the PSU MO must have been configured.
- If PTYPE in the PMU MO is set to SC48200, there must be no lower-level PSU MO for the
PMU MO.
Relation with the BATTERY MO:
- When a PMU MO with PTYPE set to SC48200 is configured, a BATTERY MO must be
configured.
- The upper-level PMU MO of the BATTERY MO must have been configured.
- The number of BATTERY MOs configured on one PMU MO must be greater than or equal
to 0 and smaller than or equal to 1.
Relation with the subrack that houses the PMU MO:
- A subrack must be configured together with a PMU MO to house the PMU MO.

Related MML Commands


Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD PMU Use this command to add a power monitoring unit (PMU). When the PMU is
added, a PMU subrack and a PMU board are added at the same time.

CLR PMUALM Use this command to clear a power monitoring unit (PMU) smoke alarm. When
a PMU smoke alarm is reported, you must clear the fault that triggers the alarm,
and then run this command to clear the alarm.

DSP PMU Use this command to query the dynamic information about a power monitoring
unit (PMU), which include the information about the PMU, PSU, and batteries.

LST PMU Use this command to list the configuration of a power monitoring unit (PMU).

MOD PMU Use this command to modify the configuration of a power monitoring unit
(PMU).

RMV PMU Use this command to remove a power monitoring unit (PMU). When the PMU
is removed, a PMU subrack and a PMU board are removed at the same time.

RST PMUPWR Use this command to shut down the DC output of the power system and then
resume the DC output after a specified period of time.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet where the PMU is located.

Subrack No. Indicates the number of the subrack where the PMU is located.

Slot No. Indicates the number of the slot where the PMU is located.

Manager Cabinet No. Indicates the cabinet number of the manager. The manager of the PMU is
usually a BBU, RRU or CCU.

Manager Subrack No. Indicates the subrack number of the manager. The manager of the PMU is
Table 2 Related parameters

Parameter Description

usually a BBU, RRU or CCU.

Manager Port No. Indicates the number of the serial port where the PMU is connected. The serial
port is the port through which the PMU is connected to the manager unit.

Address Indicates the communication address of the PMU, which is determined by the
settings of the 4-bit dual in-line package (DIP) switch on the PMU. The
communication address is used by the PMU to communicate with the main
control and transmission board. The value of this parameter must be consistent
with the actual settings of the DIP switch. The 4-bit DIP switch can be treated as
a 4-bit binary number. The settings of ON and OFF are represented by 1 and 0
respectively. Convert the 4-bit number from binary to decimal, and then the
decimal number is used as the value of this parameter.

Power System Type Indicates the type of the power system for the PMU.

AC Voltage Alarm Indicates the lower threshold of AC input voltage. When the AC input voltage is
Lower Threshold
lower than the value, an ALM-25622 Mains Input Abnormal alarm is reported.

AC Voltage Alarm Indicates the higher threshold of AC input voltage. When the AC input voltage is
Upper Threshold
higher than the value, an ALM-25622 Mains Input Abnormal alarm is reported.

DC Voltage Alarm Indicates the lower threshold of the DC voltage. When the output voltage of the
Lower Threshold
busbar is lower than the value, an ALM-25621 DC Output Abnormal alarm is
reported.

DC Voltage Alarm Indicates the upper threshold of the DC voltage. When the output voltage of the
Upper Threshold
busbar is higher than the value, an ALM-25621 DC Output Abnormal alarm is
reported.

Load Shutdown Flag Indicates the flag for power-off against low voltage, which determines whether
the load is powered off in the case of low voltage.

Load Shutdown Voltage Indicates the load voltage below which the load is powered off automatically
when load power-off against low voltage is enabled.

Cabinet Temperature Indicates the lower threshold of the cabinet temperature. If the cabinet
Alarm Lower Threshold
temperature is lower than the value, an ALM-25652 Cabinet Temperature
Abnormal alarm is reported.

Cabinet Temperature Indicates the upper threshold of the cabinet temperature. If the cabinet
Alarm Upper Threshold
temperature is higher than the value, an ALM-25652 Cabinet Temperature
Abnormal alarm is reported.
Table 2 Related parameters

Parameter Description

Cabinet Humidity Alarm Indicates the lower threshold of the cabinet humidity. If the cabinet humidity is
Lower Threshold
lower than the value, an ALM-25653 Cabinet Humidity Abnormal alarm is
reported.

Cabinet Humidity Alarm Indicates the upper threshold of the cabinet humidity. If the cabinet humidity is
Upper Threshold
higher than the value, an ALM-25653 Cabinet Humidity Abnormal alarm is
reported.

Special Analog Alarm Indicates whether to allow the report of a dedicated analog alarm. If the shield
Flag
flag for an analog alarm is enabled, the analog alarm cannot be reported.

Special Boolean Alarm Indicates whether to allow the report of a dedicated Boolean alarm. If the shield
Flag
flag for a Boolean alarm is enabled, the Boolean alarm cannot be reported.

AC Voltage Indicates the current AC voltage, that is, the input mains voltage to the rectifier.

Busbar Voltage Indicates the DC output voltage of the busbar.

Load Total Current Indicates the total load current. The total load current is the sum of current
supplied by all the DC output terminals on the power subrack.

Temperature Indicates the current cabinet temperature of the cabinet.Value NULL indicates
that this parameter is not supported by the antenna or the antenna is faulty.

Cabinet Humidity Indicates the ambient humidity of the cabinet.Value NULL indicates that this
parameter is not supported by the hardware or the hardware is faulty.

Secondary Load Power Indicates the power-on status of the secondary load. The secondary load can be
State
set to automatically powered off in the following modes:
HighTemperaturePowerOff(High temperature power off),
LowTemperaturePowerOff(Low temperature power off), and
LowVoltagePowerOff(Low voltage power off).

Charging/Discharging Indicates the charging or discharging status of batteries. Boost charge is used to
State
quickly recover the capacity of the battery. During the boost charge, the charging
voltage is relatively high. After the battery is discharged, generally, the system
automatically starts boost-charge on the battery. Floating charge is used to
compensate for the power loss of the battery due to self-discharge and to keep
the capacity of the battery. It can also recover the battery capacity. During the
floating charge, the charging voltage is relatively low. Force boost charge is an
enhanced mode of the boost charge. The charging current and boost charging
voltage of the force boost charge are higher than those of the boost charge, while
the charging time is shorter than that of the boost charge. It can be used in the
scenario where the electricity network is unsatisfactory and the battery is
Table 2 Related parameters

Parameter Description

discharged frequently.Sleeping indicates that a battery is neither in the charging


state nor in the discharging state.

Battery Current Indicates the charging or discharging current of batteries.

Current Limiting State Indicates whether the batteries that are being charged are in the current limiting
status.Value NULL indicates that this parameter is not supported by the
hardware or the hardware is faulty.

Battery Power State Indicates the power-on/power-off status of the battery. The battery can be
disconnected manually or disconnected automatically for protection purpose
based on different situations.

Remaining Capacity Indicates the remaining capacity of the battery by displaying the percentage of
the current capacity to the total capacity.

Battery Temperature Indicates the current temperature of the battery.

Battery Test Phase Indicates the phase of the battery test.

Photovoltaic Array Total Indicates the total current of the photovoltaic array of the PMU.
Current

Diesel Generator Indicates the current of the diesel generator which is managed by the PMU.
Current

Auxiliary Battery Indicates the temperature of auxiliary battery cabinet which is connected to the
Cabinet Temperature
PMU.Value NULL indicates that this parameter is not supported by the hardware
or the hardware is faulty.

Software Version Indicates the software version of the PMU.

PCB Version Indicates the PCB version of the PMU.

EPLD Version Indicates the erasable programmable logic device version of the PMU.

Software Build Time Indicate the software compiling time of the PMU.

Version Description Indicates the version description of the PMU.

Produce Date Indicates the manufacturing date of the PMU.

Manufacturer Indicates the manufacturer of the PMU.

PSU Intelligent Indicates the PSU intelligent shutdown capability of the PMU.
Table 2 Related parameters

Parameter Description

Shutdown Capability

PSU Intelligent Indicates the status of the PSU intelligent shutdown switch of the PMU.
Shutdown Switch

Remaining Time Indicates the remaining discharging time of a battery.

Battery Accumulated Indicates the accumulated charging time of a battery, including floating charging
Charge Time
time and equalized charging time.

Battery Accumulated Indicates the accumulated sleeping time of a battery. Battery sleeping effectively
Sleeping Time
prolongs the battery lifespan.

Battery Intelligent Indicates the battery intelligent management capability of the PMU.
Management Capability

Battery Intelligent Indicates the battery intelligent management mode of the PMU.Value NULL
Management Mode
indicates that this parameter is not supported by the hardware or the hardware is
faulty.

Alarm Status(from RU) Indicates the alarm status of the board. The alarm state of the board can be
normal, warning, minor or critical. For details about the definition of Alarm
Status, see ITU-T X.731.

Operational State(from Indicates the operational state of the board, which can be set to Enabled or
RU)
Disabled. Enabled indicates that services can be carried on the board. Disabled
indicates that no service can be carried on the board.

Availability Status(from Indicates the physical operation status of the board, which can be Uninstalled,
RU)
Starting up, Normal, Inconsistent, Unconfigured, Power off, Fault,
Communication lost, In test, or the combination of various states. For example,
if a board is not configured and fails to communicate with the main control and
transmission board, the physical operation status of the board is Unconfigured,
Communication lost.

Electronic Label(from Indicates the E-label, a text file with a maximum of 2 KB. It is used to record the
RU)
manufacturing information about equipment such as the board, sub-board, or
optical module. Among board properties displayed in the text file, "BoardType"
indicates the type of the board, "BarCode" indicates the bar code of the board
and is the same as the code labeled on the board, and "Item" indicates the BOM
code.

Type(from RU) Indicates the type of the board.

Serial Number(from Indicates the bar code of the board or the cabinet.
Table 2 Related parameters

Parameter Description

RU)

Description(from RU) Indicates the description about the services and functions provided by the board
or the cabinet.

Date of Indicates the manufacturing date of the board or the cabinet.


Manufacture(from RU)

Vendor(from RU) Indicates the manufacturer of the board or the cabinet.

Issue Number(from RU) Indicates the issue number of the board.

Config Type(from RU) Indicates the type of a board.

Board Indicates the temperature of a board.


Temperature(from RU)

HPA Temperature(from Indicates the temperature of the power amplifier.


RU)

DEVTYPE(from RU) Indicates the type of the device.

Software Version(from Indicates the software version of the board.


RU)

Hardware Version(from Indicates the hardware version of the board.


RU)

BootRom Version(from Indicates the BootROM version of the board.


RU)

5.7.1.6.2.53 PSU
EQUIPMENT
+-CABINET
+-SUBRACK
+-PSU

Description

A PSU MO converts +220 V AC or +110 V AC power to -48 V DC power. The number of PSUs
to be configured depends on the load capacity.

Effective Scenario
Immediately

Relations Between MOs

Base class:
RU

Possible parents:
SUBRACK

Relation with the SUBRACK MO:


- The number of PSU MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 7.
Relation with the PMU MO:
- The upper-level PMU MO of the PSU MO must have been configured.
- If PTYPE in the PMU MO is set to SC48200, there must be no lower-level PSU MO for the
PMU MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD PSU Use this command to add a power supplying unit (PSU).

DSP PSU Use this command to query the dynamic information about a power supplying
unit (PSU).

LST PSU Use this command to list the configuration of a power supplying unit (PSU).

RMV PSU Use this command to remove a power supplying unit (PSU).

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet where the PSU is located.

Subrack No. Indicates the number of the subrack where the PSU is located.

Slot No. Indicates the number of the slot where the PSU is located.

Running Status Indicates the running status of the PSU.

Produce Date Indicates the manufacturing date of the PSU.

Manufacturer Indicates the manufacturer of the PSU.

PCB Version Indicates the PCB version of the PSU.

EPLD Version Indicates the erasable programmable logic device (EPLD) version of the PSU.

Software Build Time Indicates the compiling time of the software program in the PSU.

Alarm Status(from RU) Indicates the alarm status of the board. The alarm state of the board can be
normal, warning, minor or critical. For details about the definition of Alarm
Status, see ITU-T X.731.

Operational State(from Indicates the operational state of the board, which can be set to Enabled or
RU)
Disabled. Enabled indicates that services can be carried on the board. Disabled
indicates that no service can be carried on the board.

Availability Status(from Indicates the physical operation status of the board, which can be Uninstalled,
RU)
Starting up, Normal, Inconsistent, Unconfigured, Power off, Fault,
Communication lost, In test, or the combination of various states. For example,
if a board is not configured and fails to communicate with the main control and
transmission board, the physical operation status of the board is Unconfigured,
Communication lost.

Electronic Label(from Indicates the E-label, a text file with a maximum of 2 KB. It is used to record the
RU)
manufacturing information about equipment such as the board, sub-board, or
optical module. Among board properties displayed in the text file, "BoardType"
indicates the type of the board, "BarCode" indicates the bar code of the board
and is the same as the code labeled on the board, and "Item" indicates the BOM
code.

Type(from RU) Indicates the type of the board.

Serial Number(from Indicates the bar code of the board or the cabinet.
RU)
Table 2 Related parameters

Parameter Description

Description(from RU) Indicates the description about the services and functions provided by the board
or the cabinet.

Date of Indicates the manufacturing date of the board or the cabinet.


Manufacture(from RU)

Vendor(from RU) Indicates the manufacturer of the board or the cabinet.

Issue Number(from RU) Indicates the issue number of the board.

Config Type(from RU) Indicates the type of a board.

Board Indicates the temperature of a board.


Temperature(from RU)

HPA Temperature(from Indicates the temperature of the power amplifier.


RU)

DEVTYPE(from RU) Indicates the type of the device.

Software Version(from Indicates the software version of the board.


RU)

Hardware Version(from Indicates the hardware version of the board.


RU)

BootRom Version(from Indicates the BootROM version of the board.


RU)

5.7.1.6.2.54 PSUIS
EQUIPMENT
+-PSUIS

Description

The PSUIS MO is used to manage the configuration of the intelligent shutdown switch for PSUs
that supply power to the entire BS. The PSU intelligent shutdown switch is used to shut down
redundant PSUs to improve the power conversion efficiency.

Effective Scenario

Not involved
Relations Between MOs

Possible parents:
EQUIPMENT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST PSUISS Use this command to query the status of the power supplying unit (PSU)
intelligent shutdown switch in a BS.

SET PSUISS Use this command to set the power supplying unit (PSU) intelligent shutdown
switch in a BS. If PSU intelligent shutdown is enabled, redundant PSUs are shut
down to ensure that the operating PSUs provide only the maximum power
required by the BS. In this way, power conversion efficiency can be improved.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

PSU Intelligent Indicates whether the PSU intelligent shutdown switch in a BS is enabled or
Shutdown Switch
disabled.

5.7.1.6.2.55 RCVMODE
Description

This MO does not have actual objects. It is used to configure commands related to restoration
and to provide definitions for the parameters of the commands.

Effective Scenario
Immediately

Relations Between MOs

None

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ACT CFGFILE Use this command to activate a configuration file so that the system
configuration is restored to the data in a specified configuration file. The
configuration file to be activated can be the minimum configuration file that is
issued with the NE software or the configuration file that matches with the NE
version software backed up in the system or downloaded from the M2000. This
command is usually issued by the M2000 to an NE to activate configuration
data.

Parent topic: Equipments-tree

5.7.1.6.2.56 RE
Description

The RE MO is the virtual base class of the RF processing unit, which enables the RRU and RFU
to inherit the common RF attributes.

Effective Scenario

Immediately

Relations Between MOs

Base class:
RU

Inherit children:
RRU;RFU
Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD RFCONNGRP Use this command to add an RRU/RFU RF interconnection.

ADD RRU Use this command to add an RRU or RFU on a specified chain/ring.

DSP Use this command to query the online CPRI bit error rate (BER) threshold.
CPRITHRESHOLD

DSP RRU Use this command to query the dynamic information about an RRU or RFU.
The information to be queried is as follows: the number of RX and TX channels,
the number of carriers on each RX channel and TX channel, Maximum output
power on the TX channel, the uplink channel gain, and other information about
the RRU or RFU.

LST FREQBWH Use this command to start a BER test on the CPRI link between the baseband
processing board and the specified RRU or RFU.

LST RFCONNGRP Use this command to list the configured RF interconnection.

LST RRU Use this command to query the configuration of the RRU or RFU.

MOD RRU Use this command to modify the configuration of an RRU or RFU.

RMV RFCONNGRP Use this command to remove an RRU/RFU RF interconnection.

RMV RRU Use this command to remove an RRU/RFU.

SET Use this command to set the online CPRI bit error rate (BER) threshold.
CPRITHRESHOLD

SET FREQBWH Use this command to set the minimum frequency spacing in the UO and GU
scenarios. If the bandwidth resources of the operator is limited, smaller
frequency spacing (than normal bandwidth) can be set in the UO and GU
scenarios during the network planning. In addition, the RRU or RFU can work
with small frequency spacing after the effective frequency bandwidth of the
RRU or RFU is set, thus achieving the optimal performance in the case of small
frequency spacing.

STP RRULNKTST Use this command to stop a BER test on the CPRI link between the baseband
processing board and the specified RRU or RFU.

STR RRUCHK Use this command to start a healthy check on the RRU or RFU.
Table 1 Related MML commands

MML Command Function

STR RRULNKTST Use this command to start a BER test on the CPRI link between the baseband
processing board and the specified RRU or RFU.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Administrative state Indicates the administrative state.

VSWR alarm post- The VSWR alarm post-processing switch. If the switch is set to ON when the
processing switch
VSWR is greater than the VSWR alarm post-processing threshold, the TX
channel is performed to shut down. If the switch is set to OFF, the RRU
degrades power.
When this switch is set to OFF, an RF module decreases the total TX power of
the TX channel by 3 dB to minimize the impacts of high VSWR. Different
scenarios are described as follows:
1. An RF module degrades its power by decreasing the TX power of carriers
sharing TX channels by 3 dB.
2. In the scenario where two TX channels are configured with transmit diversity
and MIMO, the TX power of one channel is decreased by 3 dB if a major
VSWR alarm is generated in this channel. Meanwhile, the TX power of the
other channel also needs to be decreased by 3 dB for the power balance of TX
channels.
3. In the scenario where multi modes share TX channels and a major VSWR
alarm is generated in one channel, this TX channel is shut down if the switch is
set to ON in any mode. The power of this channel is degraded if this switch is
set to OFF in all the modes.

VSWR alarm post- Indicates the VSWR alarm post-processing threshold. If the VSWR alarm post-
processing threshold
processing switch is set to ON and the VSWR is greater than the threshold, post-
processing is performed to shut down the TX channel. In this case, the TX
channel cannot be open automatically after the VSWR is normal. If this
parameter is set to different values in different modes of a multimode base
station, the smallest value takes effect in all the modes.
Table 2 Related parameters

Parameter Description

VSWR alarm threshold Indicates the VSWR alarm threshold. When the current VSWR is greater than
the threshold, a VSWR Abnormal alarm is reported.
It is recommended that the VSWR alarm threshold be set according to the
VSWR required by the engineering quality to reduce the probability that the
VSWR alarm is reported falsely.
To stabilize the false alarm probability to 1%, 0.1%, and 0.01%, you need to set
the VSWR alarm threshold to the following recommended values:
When the VSWR required by the engineering quality is smaller than or equal to
1.4, the recommended thresholds are 1.8, 2.0, and 2.4, respectively.
When the VSWR required by the engineering quality is smaller than or equal to
1.5, the recommended thresholds are 2.0, 2.2, and 2.6, respectively.
If this parameter is set to different values in different modes of a multimode base
station, the smallest value takes effect in all the modes.

RRU Position Indicates the position of the RRU, RFU on the chain or ring. It is calculated
from the start port one by one.

RRU Chain No. Indicates the ID of the RRU or RFU chain/ring.

RRU Topo Position Indicates the position where the RRU or RFU is installed in the topology. There
are two types of positions for the RRU or RFU: TRUNK and BRANCH.
BRANCH indicates that the RRU is connected to the RHUB. TRUNK indicates
that the RRU or RFU is located on the main chain/ring. The main chain/ring is
connected to the optical port on the baseband processing board.

RF Unit Working Mode Indicates the working mode of the RRU or RFU. MRFU, MRRU, and PRRU
support both single-mode and multi-mode base stations. LRFU supports only
LTE_FDD and LRRU supports LTE_TDD and LTE_FDD.

Number of RX channels Indicates the number of RX channels of the RRU or RFU. The RX channels are
numbered starting from 0 and must be numbered in the sequence of 0, 1, 2, 3,
4. 0 corresponds to R0A, 1 corresponds to R0B, and the rest can be deduced
by analogy. Ensure that sufficient RX channels are configured before using an
RX channel No. For example, if R0D is used, at least four RX channels must be
configured.

Number of TX channels Indicates the number of TX channels of the RRU or RFU. The TX channels are
numbered starting from 0 and must be numbered in the sequence of 0, 1, 2, 3,
4. 0 corresponds to R0A, 1 corresponds to R0B, and the rest can be deduced
by analogy. Ensure that sufficient TX channels are configured before using an
TX channel No. For example, if R0D is used, at least four TX channels must be
configured.
Table 2 Related parameters

Parameter Description

Number of carriers on Indicates the number of carriers on each RX channel.


the RX channel

Number of carriers on Indicates the number of carriers on each TX channel.


the TX channel

Maximum output power Indicates the total output power of RRU/RFU TX channels.
on the TX channel

UL channel gain Indicates the UL channel gain.

Trunk Level Indicates the RRU/RFU level on the trunk of the chain/ring.

Physical RRU device Indicates the serial number of the RRU or RFU. NULL means that the serial
serial No.
number fail to be obtained.

RRU standard Indicates the standards that are supported by the RRU or RFU. Invalid means
capability
that the standards fail to be obtained.

Access Direction Indicates the access direction of the service plane.

IfOffset Indicates the intermediate frequency offset of the RRU or RFU. This parameter
is set by the user during the network planning to avoid the external signal
interference around the current received frequency, and accordingly improve the
receiver sensitivity of the system. This parameter, however, is not recommended
to be used.

RF Desensitivity Indicates the RF desensitization intensity of the RRU or RFU. When the air
interface is under strong blocking or interference, the anti-interference capability
of RF modules can be improved by decreasing the gain on RX channels and
lowering the receiver sensitivity. Currently, this parameter can only be set to 0
dB or 10 dB. When the parameter is set to 10 dB, the uplink receiver sensitivity
is lowered by 10 dB. Therefore, the anti-interference capability is improved.

UL Support Feature Indicates whether the RRU or RFU supports the UL features.

Frequency Min Indicates the minimum effective bandwidth of the carrier.


Bandwidth

Low Current Protect Indicates the undercurrent protection switch. If an undercurrent alarm is
Switch
generated, the ALD power switch for this RRU or RFU is automatically turned
off only when this parameter is set to ENABLE. NULL means that this RRU or
RFU does not support the undercurrent protection function. Only UMTS
currently support this function.

ALD Reuse Flag Indicates whether the ALD is reused. Value 0 indicates that the ALD is not
Table 2 Related parameters

Parameter Description

reused. Value 1 indicates that the ALD is reused in Greece.

Antenna ID Indicates the serial number of the RU in the AAU. The serial numbers of
antennas on other RF modules are invalid.

Antenna Location Indicates the slot number of the RU in the AAU. The value of this parameter is
NULL for other RF modules. The slots of RUs are numbered from 0 in
ascending order from bottom to top.

RU Specification Indicates the type of an RF module, which must be the same as the hardware
type of the RF module. After this parameter is specified, the CME checks the
configurations of power, carrier, and receive and transmit capabilities based on
the value of this parameter. This ensures that these configurations are correct
before they take effect. Only GSM currently support this function.

Cabinet No. of RRU2 Indicates the cabinet number of RRU2/RFU2 for RF interconnection.For RF
interconnection in outer interconnection mode, value NULL is displayed
because the cabinet No., subrack No., and slot No. of the peer RRU remain
unknown.

Slot No. of RRU2 Indicates the slot number of RRU2/RFU2 for RF interconnection.For RF
interconnection in outer interconnection mode, value NULL is displayed
because the cabinet No., subrack No., and slot No. of the peer RRU remain
unknown.

Subrack No. of RRU2 Indicates the subrack number of RRU2/RFU2 for RF interconnection.For RF
interconnection in outer interconnection mode, value NULL is displayed
because the cabinet No., subrack No., and slot No. of the peer RRU remain
unknown.

RF Connect Type Indicates the RF interconnection type. Intra interconnection means the
interconnection between two RRUs or RFUs managed by the same main control
board. Outer connection means the interconnection between two RRUs or RFUs
managed by different main control boards.

PA Efficiency Indicates the power amplifier efficiency improvement switch for an RF module.
Improvement Switch
When this parameter is set to ON, the power amplifier efficiency of an RF
module is improved. When this parameter is set to OFF, the power amplifier
efficiency of an RF module is not improved. You can run the DSP RRU
command to query whether an RF module supports the power amplifier
efficiency improvement.

PA Efficiency Indicates whether an RF module supports the power amplifier efficiency


Improvement Capability
improvement.
Table 2 Related parameters

Parameter Description

Alarm Status(from RU) Indicates the alarm status of the board. The alarm state of the board can be
normal, warning, minor or critical. For details about the definition of Alarm
Status, see ITU-T X.731.

Operational State(from Indicates the operational state of the board, which can be set to Enabled or
RU)
Disabled. Enabled indicates that services can be carried on the board. Disabled
indicates that no service can be carried on the board.

Availability Status(from Indicates the physical operation status of the board, which can be Uninstalled,
RU)
Starting up, Normal, Inconsistent, Unconfigured, Power off, Fault,
Communication lost, In test, or the combination of various states. For example,
if a board is not configured and fails to communicate with the main control and
transmission board, the physical operation status of the board is Unconfigured,
Communication lost.

Electronic Label(from Indicates the E-label, a text file with a maximum of 2 KB. It is used to record the
RU)
manufacturing information about equipment such as the board, sub-board, or
optical module. Among board properties displayed in the text file, "BoardType"
indicates the type of the board, "BarCode" indicates the bar code of the board
and is the same as the code labeled on the board, and "Item" indicates the BOM
code.

Type(from RU) Indicates the type of the board.

Serial Number(from Indicates the bar code of the board or the cabinet.
RU)

Description(from RU) Indicates the description about the services and functions provided by the board
or the cabinet.

Date of Indicates the manufacturing date of the board or the cabinet.


Manufacture(from RU)

Vendor(from RU) Indicates the manufacturer of the board or the cabinet.

Issue Number(from RU) Indicates the issue number of the board.

Config Type(from RU) Indicates the type of a board.

Board Indicates the temperature of a board.


Temperature(from RU)

HPA Temperature(from Indicates the temperature of the power amplifier.


RU)

DEVTYPE(from RU) Indicates the type of the device.


Table 2 Related parameters

Parameter Description

Software Version(from Indicates the software version of the board.


RU)

Hardware Version(from Indicates the hardware version of the board.


RU)

BootRom Version(from Indicates the BootROM version of the board.


RU)

5.7.1.6.2.57 RET
EQUIPMENT
+-RET
+-RETSUBUNIT[1~8]

Description

The remote electrical tilting unit (RET) MO is used to adjust the antenna tilt.

Effective Scenario

Immediately

Relations Between MOs

Base class:
ALD

Possible parents:
EQUIPMENT

Possible children:
RETSUBUNIT[1~8]

Relation with the RETSUBUNIT MO:


- The number of RETSUBUNIT MOs configured on one RET MO must be greater than or
equal to 1 and smaller than or equal to 8.
Relation with the RRU,RFU,AAMU MOs:
- The RRU or RFU or AAMU MO corresponding to CTRLCN, CTRLSRN, and CTRLSN
in the RET MO must have been configured.
Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD RET Use this command to add a remote electrical tilting (RET) antenna. The subunits
and device data are added at the same time.

DSP RET Use this command to query the dynamic information about one or all remote
electrical tilting (RET) antennas.

LST RET Use this command to list the configuration of one or all remote electrical tilting
(RET) antennas.

MOD RET Use this command to modify the configuration of a remote electrical tilting
(RET).

RMV RET Use this command to remove a remote electrical tilting (RET) antenna. The
subunits and device data are removed at the same time.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

RET Type Indicates the antenna type. This parameter can be set to SINGLE_RET or
MULTI_RET.

Polar Type Indicates the polarization type of the antenna. This parameter can be set to
SINGLE or DUAL.

Antenna Scenario Indicates the connection scenario of the antenna. This parameter must be set
based on the hardware installation. The vendor code and serial number of the
device must be correctly configured in a non-regular scenario. This parameter
can be set to REGULAR, DAISY_CHAIN, SECTOR_SPLITTING, or
2G_EXTENSION.

RET Subunit Number Indicates the number of configured RET subunits.


Table 2 Related parameters

Parameter Description

Device No.(from ALD) Indicates the device number of the ALD. The device number of the ALD must
be unique.

Actual Vendor Indicates the vendor code of the device in the scanning result.
Code(from ALD)

Actual Device Serial Indicates the serial number of the device in the scanning result.
No.(from ALD)

Device Name(from Indicates the device name of the ALD, which identifies the ALD. It is
ALD)
recommended that you set the device name in the following format:
sector_device type_network type. The meanings of the parts are as follows:
Sector: indicates the number of the sector. Device type: indicates the type of
currently connected device. It can be SINGLE_RET (Single-antenna Remote
Electrical Tilt Unit), MULTI_RET (Multi-antenna Remote Electrical Tilt Unit),
TMA (Tower-mounted Amplifier). Network type: indicates whether the current
ALD is used for a 2G network or 3G/LTE network. The device name is optional,
but the device name configured for each ALD must be unique.

Control Port Cabinet Indicates the cabinet number of the RRU or RFU that controls the ALD.
No.(from ALD)

Control Port Subrack Indicates the subrack number of the RRU or RFU that controls the ALD.
No.(from ALD)

Control Port Slot No. Indicates the slot number of the RRU or RFU that controls the ALD.
(from ALD)

Protocol Version(from Indicates the actual protocol version of the ALD. NULL means that the protocol
ALD)
version information fails to be obtained.

Actual Subunit Indicates the total number of ALD subunits.


Number(from ALD)

Vendor Code(from ALD) Indicates the vendor code.

Serial No.(from ALD) Indicates the serial number of the ALD. The vendor code and the serial number
uniquely identify an ALD.

Hardware Version(from Indicates the version information about the ALD hardware.
ALD)

Software Version(from Indicates the version information about the ALD software.
ALD)

Device Model(from Indicates the device model of the ALD.


ALD)

Device Type(from ALD) Indicates the device type of the ALD.


Table 2 Related parameters

Parameter Description

Control Port No.(from Indicates the port number of the RRU or RFU that controls the ALD. It will be
ALD)
NULL if the RRU or RFU does not support to report this parameter.

5.7.1.6.2.58 RETDEVICEDATA
EQUIPMENT
+-RET
+-RETSUBUNIT
+-RETDEVICEDATA

Description

The RetDeviceData MO refers to the configuration of the antenna and the capability supported
by the antenna. For details, see 3GPP TS25.466 and AISG2.0.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
RETSUBUNIT

Relation with the RETSUBUNIT MO:


- The number of RETDEVICEDATA MOs configured on one RETSUBUNIT MO must be
1.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

DSP RETDEVICEDATA Use this command to query the dynamic information in the remote electrical
tilting (RET) device data.

LST RETDEVICEDATA Use this command to list the configuration in the remote electrical tilting (RET)
device data.

MOD Use this command to modify the configuration in the remote electrical tilting
RETDEVICEDATA
(RET) device data.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Device No. Indicates the device number of the RET.

Subunit No. Indicates the number of the RET subunit, which starts from 1.

Antenna Bearing Indicates the antenna azimuth.

Antenna Model Number Indicates the model of the RET antenna module.

Base Station ID Indicates the base station ID. AISG1.1-based RET antennas support a maximum
length of 12 characters for the base station ID. If the input base station ID has
more than 12 characters, only the first 12 characters are saved on the RET
antenna.

Beamwidth1 Indicates the beamwidth of band 1. Beamwidth is used to describe the capability
of the antenna to transmit RF signals. It is also used to measure the antenna
pattern.

Beamwidth2 Indicates the beamwidth of band 2. Beamwidth is used to describe the capability
of the antenna to transmit RF signals. It is also used to measure the antenna
pattern.

Beamwidth3 Indicates the beamwidth of band 3. Beamwidth is used to describe the capability
of the antenna to transmit RF signals. It is also used to measure the antenna
pattern.
Table 2 Related parameters

Parameter Description

Beamwidth4 Indicates the beamwidth of band 4. Beamwidth is used to describe the capability
of the antenna to transmit RF signals. It is also used to measure the antenna
pattern.

Gain1 Indicates the gain of band 1.

Gain2 Indicates the gain of band 2.

Gain3 Indicates the gain of band 3.

Gain4 Indicates the gain of band 4.

Installation Date Indicates the date when the antenna is installed.

Installed Mechanical Tilt Indicates the mechanical tilt of the installation.

Installer's ID Indicates the ID of the installation technician who installed the antenna.

Band1 Indicates band 1 supported by the antenna.

Band2 Indicates band 2 supported by the antenna.

Band3 Indicates band 3 supported by the antenna.

Band4 Indicates band 4 supported by the antenna.

Sector ID Indicates the sector ID. AISG1.1-based RET antennas support a maximum
sector ID length of 4 characters. If the input sector ID has more than 4
characters, only the first 4 characters are saved on the RET antenna.

Antenna Serial No. Indicates the serial number of the RET antenna module.

Max Tilt Indicates the maximum tilt supported by the RET subunit.

Min Tilt Indicates the minimum tilt supported by the RET subunit.

Band1 Indicates band 1 supported by the antenna.

Band2 Indicates band 2 supported by the antenna.

Band3 Indicates band 3 supported by the antenna.

Band4 Indicates band 4 supported by the antenna.


Table 2 Related parameters

Parameter Description

Beamwidth1 Indicates the beamwidth of band 1. Beamwidth describes the capability of an


antenna to transmit RF signals. It also defines the width of the antenna pattern.

Beamwidth2 Indicates the beamwidth of band 2. Beamwidth describes the capability of an


antenna to transmit RF signals. It also defines the width of the antenna pattern.

Beamwidth3 Indicates the beamwidth of band 3. Beamwidth describes the capability of an


antenna to transmit RF signals. It also defines the width of the antenna pattern.

Beamwidth4 Indicates the beamwidth of band 4. Beamwidth describes the capability of an


antenna to transmit RF signals. It also defines the width of the antenna pattern.

Gain1 Indicates the gain of band 1.

Gain2 Indicates the gain of band 2.

Gain3 Indicates the gain of band 3.

Gain4 Indicates the gain of band 4.

5.7.1.6.2.59 RETPORT
EQUIPMENT
+-RRU
+-RETPORT

Description

The RetPort MO is a port on the RRU to which the multi-wire cable can be connected. The MO
is used by the BS to communicate with and control the ALD using S485 signals.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
RRU

Relation with the RRU MO:


- The number of RETPORT MOs configured on one RRU MO must be greater than or equal
to 0 and smaller than or equal to 1.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP RETPORT Use this command to query the dynamic information about a remote electrical
tilting (RET) port.

LST RETPORT Use this command to list the configuration of a remote electrical tilting (RET)
port.

MOD RETPORT Use this command to modify the configuration of a remote electrical tilting
(RET) port.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the RRU where the RET port is located.

Subrack No. Indicates the subrack number of the RRU where the RET port is located.

Slot No. Indicates the slot number of the RRU where the RET port is located.

Port No. Indicates the number of the RET port on an RRU. This parameter is set to
RET_PORT.

ALD Power Switch Indicates the state of the ALD power supply switch. If SINGLE_RET(Single-
antenna Remote Electrical Tilt) or MULTI_RET(Multi-antenna Remote
Electrical Tilt) is used, the ALD power supply switch must be set to ON. In
actual running, the RRU automatically sets this switch to OFF for an RET port
when the ALM-26530 RF Module ALD Current Abnormal alarm is reported due
Table 2 Related parameters

Parameter Description

to overcurrent, overcurrent protection, or undercurrent protection (the RRU


supports undercurrent protection and Low Current Protect Switch is set to ON
for the RRU) on the RET port. For details, see ALM-26530 RF Module ALD
Current Abnormal.

Current Alarm Indicates the type of the ALD current alarm threshold. The current alarm
Threshold Type
threshold for the ALDs (excluding user-defined ALDs), that is, for RET
antennas only (multi-wire cable), must be selected according to the ALD type.
The Undercurrent Alarm Occur Threshold is 10 mA, the Undercurrent Alarm
Clear Threshold is 15 mA, the Overcurrent Alarm Occur Threshold is 150 mA,
and the Overcurrent Alarm Clear Threshold is 120 mA. This parameter can be
set to UER_SELF_DEFINE or RET_ONLY_MULTICORE.

Undercurrent Alarm Indicates the undercurrent alarm occur threshold. When the ALD current value
Occur Threshold
is smaller than this threshold, an ALM-26530 RF Module ALD Current
Abnormal alarm is reported. The specific problem is undercurrent.

Undercurrent Alarm Indicates the undercurrent alarm clear threshold. When the ALD current value is
Clear Threshold
greater than this threshold, the ALM-26530 RF Module ALD Current Abnormal
alarm is cleared.

Overcurrent Alarm Indicates the overcurrent alarm occur threshold. When the overcurrent alarm
Occur Threshold
occur threshold is lower than the maximum current supported by the hardware,
the overcurrent alarm occur threshold prevails. When the ALD current value is
greater than this threshold, ALM-26530 RF Module ALD Current Abnormal is
reported and the specific problem is overcurrent.When the overcurrent alarm
occur threshold is higher than the maximum current supported by the hardware,
the maximum current supported by the hardware serves as the overcurrent alarm
threshold. When the ALD current value is the same as or greater than the
maximum current supported by the hardware, ALM-26530 RF Module ALD
Current Abnormal is reported and the specific problem is overcurrent protection.

Overcurrent Alarm Indicates the overcurrent alarm clear threshold. When the overcurrent alarm
Clear Threshold
clear threshold is lower than the maximum current supported by the hardware,
the overcurrent alarm clear threshold prevails. When the ALD current value is
lower than this threshold, ALM-26530 RF Module ALD Current Abnormal is
cleared.When the overcurrent alarm clear threshold is higher than the maximum
current supported by the hardware, the maximum current supported by the
hardware serves as the overcurrent alarm clear threshold. When the ALD current
value is lower than the maximum current supported by the hardware, ALM-
26530 RF Module ALD Current Abnormal is cleared.

ALD Current Value Indicates the present value of the current of the ALD.
Table 2 Related parameters

Parameter Description

ALD Actual Power Indicates the actual status of the ALD power supply switch.
Switch

5.7.1.6.2.60 RETSUBUNIT
EQUIPMENT
+-RET
+-RETSUBUNIT
+-RETDEVICEDATA[1~1]

Description

The RETSubunit MO is the managed object of a RET subunit, which receives and transmits RF
signals.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
RET

Possible children:
RETDEVICEDATA[1~1]

Relation with the RET MO:


- The number of RETSUBUNIT MOs configured on one RET MO must be greater than or
equal to 1 and smaller than or equal to 8.
Relation with the RETDEVICEDATA MO:
- The number of RETDEVICEDATA MOs configured on one RETSUBUNIT MO must be
1.
Relation with the RETSUBUNIT MO:
- One of the following ANTENNAPORT MOs must have been configured: 1. An
ANTENNAPORT MO corresponding to CONNCN1, CONNSRN1, CONNSN1, and
CONNPN1 in the RETSUBUNIT MO. 2. An ANTENNAPORT MO corresponding to
CONNCN2, CONNSRN2, CONNSN2, and CONNPN2 in the RETSUBUNIT MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

CLB RET Use this command to calibrate a remote electrical tilting (RET) antenna. The
calibration is to ensure that all the antenna tilts are configured correctly and
consistent with the actual configuration.

DLD RETCFGDATA Use this command to load the remote electrical tilting (RET) configuration data.
The RET configuration file is provided by the manufacturer.

DSP RETSUBUNIT Use this command to query the dynamic information about a remote electrical
tilting (RET) subunit.

LST RETSUBUNIT Use this command to list the configuration of a remote electrical tilting (RET)
subunit.

MOD RETSUBUNIT Use this command to modify a remote electrical tilting (RET) subunit.

MOD RETTILT Use this command to modify the remote electrical tilting(RET) tilt.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Device No. Indicates the device number of the RET.

Subunit No. Indicates the number of the RET subunit, which starts from 1.

Online Status Indicates the online status of the subunit.

Actual Tilt Indicates the actual tilt of the RET subunit.


Table 2 Related parameters

Parameter Description

Sector Id Indicates the sector ID of the RET subunit.

Connect Port 1 Cabinet Indicates the cabinet number of the RRU or RFU that is connected to antenna
No.
port 1.

Connect Port 1 Subrack Indicates the subrack number of the RRU or RFU that is connected to antenna
No.
port 1.

Connect Port 1 Slot No. Indicates the slot number of the RRU or RFU that is connected to antenna port
1.

Connect Port 1 Port No. Indicates the port number of the RRU or RFU that is connected to antenna port
1.

Connect Port 2 Cabinet Indicates the cabinet number of the RRU or RFU that is connected to antenna
No.
port 2. This parameter is valid when a dual-polarized antenna is used.

Connect Port 2 Subrack Indicates the subrack number of the RRU or RFU that is connected to antenna
No.
port 2. This parameter is valid when a dual-polarized antenna is used.

Connect Port 2 Slot No. Indicates the slot number of the RRU or RFU that is connected to antenna port
2. This parameter is valid when a dual-polarized antenna is used.

Connect Port 2 Port No. Indicates the port number of RRU or RFU that is connected to antenna port 2.
This parameter is valid when a dual-polarized antenna is used.

Tilt Indicates the antenna tilt of the RET subunit. If this parameter is set to 32767, it
is invalid and the actual tilt is not changed.

Tilt Alarm Error Range Indicates the allowed maximum tilt inconsistency. When the difference between
the actual tilt of an RET subunit and configured tilt is larger than the value of
this parameter, ALM-26757 RET Antenna Running Data and Configuration
Mismatch is reported.

Subunit Name Indicates the name of the RET subunit.The name of the RET subunit is optional,
but the name configured for each RET subunit must be unique.

5.7.1.6.2.61 RFU
EQUIPMENT
+-CABINET
+-SUBRACK
+-RFU
+-ANTENNAPORT[1~8]
+-CPRIPORT[2~2]
+-SFP[2~2]
+-ALMPORT[0~0]
+-TXBRANCH[0~8]
+-RXBRANCH[0~8]

Description

The RFU MO is the RF processing unit of a macro BS, which provides ports for sending and
receiving baseband and RF signals and processes the UL and DL baseband signals.

Effective Scenario

Immediately

Relations Between MOs

Base class:
RE

Possible parents:
SUBRACK

Possible children:
ANTENNAPORT[1~8];CPRIPORT[2~2];SFP[2~2];ALMPORT[0~0];TXBRANCH[0~8];RXBRANCH[0~8]

Relation with the ALMPORT MO:


- The number of ALMPORT MOs configured on one RFU MO must be 0.
Relation with the ANTENNAPORT MO:
- The number of ANTENNAPORT MOs configured on one RFU MO must be greater than or
equal to 1 and smaller than or equal to 8.
Relation with the RXBRANCH MO:
- The number of RXBRANCH MOs configured on one RFU MO must be greater than or
equal to 0 and smaller than or equal to 8.
Relation with the SUBRACK MO:
- The number of RFU MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 9.
Relation with the TXBRANCH MO:
- The number of TXBRANCH MOs configured on one RFU MO must be greater than or
equal to 0 and smaller than or equal to 8.
Relation with the RET,RRU,AAMU MOs:
- The RRU or RFU or AAMU MO corresponding to CTRLCN, CTRLSRN, and CTRLSN
in the RET MO must have been configured.
Relation with the TMA,RRU MOs:
- The RRU or RFU MO corresponding to CTRLCN, CTRLSRN, and CTRLSN in the TMA
MO must have been configured.
Relation with the RFU MO:
- The RRUCHAIN MO where the RFU MO is located must have been configured.
- In the RRUCHAIN MO where the RFU MO is located, when TT is set to
LOADBALANCE, RS is not set to UO or GO.
Relation with the RRUCHAIN,RRU,AAMU MOs:
- The total number of RRU and RFU and AAMU MOs configured on the RRUCHAIN MO
must be smaller than or equal to 21.
Relation with the AAMU, RRU, and RFU MOs:
- If BM in the RRUCHAIN MO where the RFU MO is located is set to HOT, the total
number of AAMU, RRU, and RFU MOs configured on the RRUCHAIN MO must be 0 or 1.
Relation with the RRU,AAMU,RHUB MOs:
- Under a base station, the total number of RRU, RFU, AAMU, and RHUB MOs must be less
than or equal to 420.
Relation with the RRU MO:
- When TT in the RRUCHAIN MO is set to LOADBALANCE, the number of RFU MOs
specified by RCN and RRU MOs specified by RCN and with RT not set to MPRF must be 0 or
1.
Relation with the RHUB MO:
- The RRUCHAIN MO where the RHUB MO is located must not have RRU MO,RFU MO
and AAMU MO.
Relation with the AAMU, RRU, RFU, and RHUB MOs:
- When HCN, HSRN, and HSN in an RRUCHAIN MO are the same as CN, SRN, and SN in
an RHUB MO, respectively, the RT in the RRU MO that is configured on this RRUCHAIN
MO must be set to MPMU or MPRF.
Relation with the TXBRANCH and RXBRANCH MOs:
- The number of TXBRANCH MOs related to a RFU MO must be equal to TXNUM in the
RFU MO, and the number of RXBRANCH MOs related to the RFU MO must be equal to
RXNUM in the RFU MO.
Related Parameters

Table 1 describes the parameters related to this MO.

Table 1 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet where the RFU is located.

Subrack No. Indicates the number of the subrack where the RFU is located.

Slot No. Indicates the slot number of the RFU.

RRU type Indicates the type of the RFU.

Administrative Indicates the administrative state.


state(from RE)

Alarm Status(from RU) Indicates the alarm status of the board. The alarm state of the board can be
normal, warning, minor or critical. For details about the definition of Alarm
Status, see ITU-T X.731.

Operational State(from Indicates the operational state of the board, which can be set to Enabled or
RU)
Disabled. Enabled indicates that services can be carried on the board. Disabled
indicates that no service can be carried on the board.

Availability Status(from Indicates the physical operation status of the board, which can be Uninstalled,
RU)
Starting up, Normal, Inconsistent, Unconfigured, Power off, Fault,
Communication lost, In test, or the combination of various states. For example,
if a board is not configured and fails to communicate with the main control and
transmission board, the physical operation status of the board is Unconfigured,
Communication lost.

Electronic Label(from Indicates the E-label, a text file with a maximum of 2 KB. It is used to record the
RU)
manufacturing information about equipment such as the board, sub-board, or
optical module. Among board properties displayed in the text file, "BoardType"
indicates the type of the board, "BarCode" indicates the bar code of the board
and is the same as the code labeled on the board, and "Item" indicates the BOM
code.

Type(from RU) Indicates the type of the board.

Serial Number(from Indicates the bar code of the board or the cabinet.
RU)

Description(from RU) Indicates the description about the services and functions provided by the board
or the cabinet.
Table 1 Related parameters

Parameter Description

Date of Indicates the manufacturing date of the board or the cabinet.


Manufacture(from RU)

Vendor(from RU) Indicates the manufacturer of the board or the cabinet.

Issue Number(from RU) Indicates the issue number of the board.

Config Type(from RU) Indicates the type of a board.

Board Indicates the temperature of a board.


Temperature(from RU)

HPA Temperature(from Indicates the temperature of the power amplifier.


RU)

DEVTYPE(from RU) Indicates the type of the device.

VSWR alarm post- The VSWR alarm post-processing switch. If the switch is set to ON when the
processing switch(from
RE) VSWR is greater than the VSWR alarm post-processing threshold, the TX
channel is performed to shut down. If the switch is set to OFF, the RRU
degrades power.
When this switch is set to OFF, an RF module decreases the total TX power of
the TX channel by 3 dB to minimize the impacts of high VSWR. Different
scenarios are described as follows:
1. An RF module degrades its power by decreasing the TX power of carriers
sharing TX channels by 3 dB.
2. In the scenario where two TX channels are configured with transmit diversity
and MIMO, the TX power of one channel is decreased by 3 dB if a major
VSWR alarm is generated in this channel. Meanwhile, the TX power of the
other channel also needs to be decreased by 3 dB for the power balance of TX
channels.
3. In the scenario where multi modes share TX channels and a major VSWR
alarm is generated in one channel, this TX channel is shut down if the switch is
set to ON in any mode. The power of this channel is degraded if this switch is
set to OFF in all the modes.

VSWR alarm post- Indicates the VSWR alarm post-processing threshold. If the VSWR alarm post-
processing
threshold(from RE) processing switch is set to ON and the VSWR is greater than the threshold, post-
processing is performed to shut down the TX channel. In this case, the TX
channel cannot be open automatically after the VSWR is normal. If this
parameter is set to different values in different modes of a multimode base
station, the smallest value takes effect in all the modes.

VSWR alarm Indicates the VSWR alarm threshold. When the current VSWR is greater than
threshold(from RE)
the threshold, a VSWR Abnormal alarm is reported.
Table 1 Related parameters

Parameter Description

It is recommended that the VSWR alarm threshold be set according to the


VSWR required by the engineering quality to reduce the probability that the
VSWR alarm is reported falsely.
To stabilize the false alarm probability to 1%, 0.1%, and 0.01%, you need to set
the VSWR alarm threshold to the following recommended values:
When the VSWR required by the engineering quality is smaller than or equal to
1.4, the recommended thresholds are 1.8, 2.0, and 2.4, respectively.
When the VSWR required by the engineering quality is smaller than or equal to
1.5, the recommended thresholds are 2.0, 2.2, and 2.6, respectively.
If this parameter is set to different values in different modes of a multimode base
station, the smallest value takes effect in all the modes.

RRU Position(from RE) Indicates the position of the RRU, RFU on the chain or ring. It is calculated
from the start port one by one.

RRU Chain No.(from Indicates the ID of the RRU or RFU chain/ring.


RE)

RRU Topo Indicates the position where the RRU or RFU is installed in the topology. There
Position(from RE)
are two types of positions for the RRU or RFU: TRUNK and BRANCH.
BRANCH indicates that the RRU is connected to the RHUB. TRUNK indicates
that the RRU or RFU is located on the main chain/ring. The main chain/ring is
connected to the optical port on the baseband processing board.

RF Unit Working Indicates the working mode of the RRU or RFU. MRFU, MRRU, and PRRU
Mode(from RE)
support both single-mode and multi-mode base stations. LRFU supports only
LTE_FDD and LRRU supports LTE_TDD and LTE_FDD.

Number of RX Indicates the number of RX channels of the RRU or RFU. The RX channels are
channels(from RE)
numbered starting from 0 and must be numbered in the sequence of 0, 1, 2, 3,
4. 0 corresponds to R0A, 1 corresponds to R0B, and the rest can be deduced
by analogy. Ensure that sufficient RX channels are configured before using an
RX channel No. For example, if R0D is used, at least four RX channels must be
configured.

Number of TX Indicates the number of TX channels of the RRU or RFU. The TX channels are
channels(from RE)
numbered starting from 0 and must be numbered in the sequence of 0, 1, 2, 3,
4. 0 corresponds to R0A, 1 corresponds to R0B, and the rest can be deduced
by analogy. Ensure that sufficient TX channels are configured before using an
TX channel No. For example, if R0D is used, at least four TX channels must be
configured.

Number of carriers on Indicates the number of carriers on each RX channel.


the RX channel(from
RE)
Table 1 Related parameters

Parameter Description

Number of carriers on Indicates the number of carriers on each TX channel.


the TX channel(from
RE)

Maximum output power Indicates the total output power of RRU/RFU TX channels.
on the TX channel(from
RE)

UL channel gain(from Indicates the UL channel gain.


RE)

Trunk Level(from RE) Indicates the RRU/RFU level on the trunk of the chain/ring.

Physical RRU device Indicates the serial number of the RRU or RFU. NULL means that the serial
serial No.(from RE)
number fail to be obtained.

RRU standard Indicates the standards that are supported by the RRU or RFU. Invalid means
capability(from RE)
that the standards fail to be obtained.

Access Direction(from Indicates the access direction of the service plane.


RE)

IfOffset(from RE) Indicates the intermediate frequency offset of the RRU or RFU. This parameter
is set by the user during the network planning to avoid the external signal
interference around the current received frequency, and accordingly improve the
receiver sensitivity of the system. This parameter, however, is not recommended
to be used.

RF Desensitivity(from Indicates the RF desensitization intensity of the RRU or RFU. When the air
RE)
interface is under strong blocking or interference, the anti-interference capability
of RF modules can be improved by decreasing the gain on RX channels and
lowering the receiver sensitivity. Currently, this parameter can only be set to 0
dB or 10 dB. When the parameter is set to 10 dB, the uplink receiver sensitivity
is lowered by 10 dB. Therefore, the anti-interference capability is improved.

UL Support Indicates whether the RRU or RFU supports the UL features.


Feature(from RE)

Frequency Min Indicates the minimum effective bandwidth of the carrier.


Bandwidth(from RE)

Low Current Protect Indicates the undercurrent protection switch. If an undercurrent alarm is
Switch(from RE)
generated, the ALD power switch for this RRU or RFU is automatically turned
off only when this parameter is set to ENABLE. NULL means that this RRU or
RFU does not support the undercurrent protection function. Only UMTS
currently support this function.

ALD Reuse Flag(from Indicates whether the ALD is reused. Value 0 indicates that the ALD is not
RE)
Table 1 Related parameters

Parameter Description

reused. Value 1 indicates that the ALD is reused in Greece.

Antenna ID(from RE) Indicates the serial number of the RU in the AAU. The serial numbers of
antennas on other RF modules are invalid.

Antenna Location(from Indicates the slot number of the RU in the AAU. The value of this parameter is
RE)
NULL for other RF modules. The slots of RUs are numbered from 0 in
ascending order from bottom to top.

RU Specification(from Indicates the type of an RF module, which must be the same as the hardware
RE)
type of the RF module. After this parameter is specified, the CME checks the
configurations of power, carrier, and receive and transmit capabilities based on
the value of this parameter. This ensures that these configurations are correct
before they take effect. Only GSM currently support this function.

Cabinet No. of Indicates the cabinet number of RRU2/RFU2 for RF interconnection.For RF


RRU2(from RE)
interconnection in outer interconnection mode, value NULL is displayed
because the cabinet No., subrack No., and slot No. of the peer RRU remain
unknown.

Slot No. of RRU2(from Indicates the slot number of RRU2/RFU2 for RF interconnection.For RF
RE)
interconnection in outer interconnection mode, value NULL is displayed
because the cabinet No., subrack No., and slot No. of the peer RRU remain
unknown.

Subrack No. of Indicates the subrack number of RRU2/RFU2 for RF interconnection.For RF


RRU2(from RE)
interconnection in outer interconnection mode, value NULL is displayed
because the cabinet No., subrack No., and slot No. of the peer RRU remain
unknown.

RF Connect Type(from Indicates the RF interconnection type. Intra interconnection means the
RE)
interconnection between two RRUs or RFUs managed by the same main control
board. Outer connection means the interconnection between two RRUs or RFUs
managed by different main control boards.

Software Version(from Indicates the software version of the board.


RU)

Hardware Version(from Indicates the hardware version of the board.


RU)

BootRom Version(from Indicates the BootROM version of the board.


RU)

PA Efficiency Indicates the power amplifier efficiency improvement switch for an RF module.
Improvement
Switch(from RE) When this parameter is set to ON, the power amplifier efficiency of an RF
Table 1 Related parameters

Parameter Description

module is improved. When this parameter is set to OFF, the power amplifier
efficiency of an RF module is not improved. You can run the DSP RRU
command to query whether an RF module supports the power amplifier
efficiency improvement.

PA Efficiency Indicates whether an RF module supports the power amplifier efficiency


Improvement
Capability(from RE) improvement.

5.7.1.6.2.62 RHUB
EQUIPMENT
+-RHUB
+-CPRIPORT[10~10]
+-SFP[2~2]
+-ALMPORT[4~4]

Description

The RHUB MO consists of the configuration of an RF unit hub. The configuration contains the
cabinet number, subrack number, and slot number of the RHUB, the chain/ring number where
the RHUB is located, the name of the RHUB, and other information.

Effective Scenario

Immediately

Relations Between MOs

Base class:
RU

Possible parents:
EQUIPMENT

Possible children:
CPRIPORT[10~10];SFP[2~2];ALMPORT[4~4]

Relation with the BBP,BRI,GTMU,RRUCHAIN MOs:


- When the RRUCHAIN MO whose AT is set to a value other than PEERPORT, one of the
following BBP, BRI , GTMU or RHUB MOs must have been configured:
- 1. A BBP, BRI, GTMU or RHUB MO corresponding to HCN, HSRN, and HSN.
- 2. A BBP, BRI, GTMU or RHUB MO corresponding to TCN, TSRN, and TSN in the
RRUCHAIN MO when TT in the RRUCHAIN MO is set to a value other than CHAIN.
Relation with the RHUB MO:
- The RRUCHAIN MO where the RHUB MO is located must have been configured.
- When TP in the RRU MO is set to BRANCH, the RHUB MO corresponding to RCN must
have been configured.
- The RRUCHAIN MO where the RHUB MO is located must not have RRU MO,RFU MO
and AAMU MO.
- Under a base station, The total number of RHUB MOs must be smaller than or equal to 24.
- The total number of RHUB MOs configured on the RRUCHAIN MO must be smaller than
or equal to 4.
- When an RRUCHAIN MO is configured on an RHUB MO, TT in the RRUCHAIN MO
cannot be set to RING.
Relation with the RRU,RFU,AAMU MOs:
- Under a base station, the total number of RRU, RFU, AAMU, and RHUB MOs must be less
than or equal to 420.
Relation with the AAMU, RRU, RFU, and RHUB MOs:
- When HCN, HSRN, and HSN in an RRUCHAIN MO are the same as CN, SRN, and SN in
an RHUB MO, respectively, the RT in the RRU MO that is configured on this RRUCHAIN
MO must be set to MPMU or MPRF.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD RHUB Use this command to add an RHUB before adding a branch chain/ring.

DSP FARPWRINFO Use this command to query the remote power state of an RHUB.

DSP RHUB Use this command to query the information about an RHUB.

LST RHUB Use this command to query the configuration of an RHUB.


Table 1 Related MML commands

MML Command Function

MOD RHUB Use this command to modify the configuration of an RHUB.

RMV RHUB Use this command to remove an RHUB.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet where the RHUB is located.

Subrack No. Indicates the number of the subrack where the RHUB is located.

Slot No. Indicates the slot number of the RHUB.

RRU Chain No. Indicates the ID of the RHUB chain. It uniquely identifies a chain within a base
station.

RHUB Position Indicates the position of the RHUB on the RRU chain/ring. It is calculated from
the start port one by one.

RHUB Name Indicates the name of the RHUB.

Alarm Status(from RU) Indicates the alarm status of the board. The alarm state of the board can be
normal, warning, minor or critical. For details about the definition of Alarm
Status, see ITU-T X.731.

Operational State(from Indicates the operational state of the board, which can be set to Enabled or
RU)
Disabled. Enabled indicates that services can be carried on the board. Disabled
indicates that no service can be carried on the board.

Availability Status(from Indicates the physical operation status of the board, which can be Uninstalled,
RU)
Starting up, Normal, Inconsistent, Unconfigured, Power off, Fault,
Communication lost, In test, or the combination of various states. For example,
if a board is not configured and fails to communicate with the main control and
transmission board, the physical operation status of the board is Unconfigured,
Communication lost.
Table 2 Related parameters

Parameter Description

Electronic Label(from Indicates the E-label, a text file with a maximum of 2 KB. It is used to record the
RU)
manufacturing information about equipment such as the board, sub-board, or
optical module. Among board properties displayed in the text file, "BoardType"
indicates the type of the board, "BarCode" indicates the bar code of the board
and is the same as the code labeled on the board, and "Item" indicates the BOM
code.

Type(from RU) Indicates the type of the board.

Serial Number(from Indicates the bar code of the board or the cabinet.
RU)

Description(from RU) Indicates the description about the services and functions provided by the board
or the cabinet.

Date of Indicates the manufacturing date of the board or the cabinet.


Manufacture(from RU)

Vendor(from RU) Indicates the manufacturer of the board or the cabinet.

Issue Number(from RU) Indicates the issue number of the board.

Config Type(from RU) Indicates the type of a board.

Board Indicates the temperature of a board.


Temperature(from RU)

HPA Temperature(from Indicates the temperature of the power amplifier.


RU)

DEVTYPE(from RU) Indicates the type of the device.

Software Version(from Indicates the software version of the board.


RU)

Hardware Version(from Indicates the hardware version of the board.


RU)

BootRom Version(from Indicates the BootROM version of the board.


RU)

5.7.1.6.2.63 RRU
EQUIPMENT
+-RRU
+-RETPORT[0~1]
+-ANTENNAPORT[0~8]
+-CPRIPORT[2~2]
+-SFP[2~2]
+-ALMPORT[0~4]
+-TXBRANCH[0~8]
+-RXBRANCH[0~8]

Description

The remote radio unit (RRU) provides ports for sending and receiving baseband and RF signals
and processes the UL and DL baseband signals.

Effective Scenario

Immediately

Relations Between MOs

Base class:
RE

Possible parents:
EQUIPMENT

Possible children:
RETPORT[0~1];ANTENNAPORT[0~8];CPRIPORT[2~2];SFP[2~2];ALMPORT[0~4];TXBRANCH[0~8];RXB
RANCH[0~8]

Relation with the ANTENNAPORT MO:


- When RT in an RRU MO is set to MPMU, the number of ANTENNAPORT MOs must be
0.
- When RT in an RRU MO is set to MPRF, the number of ANTENNAPORT MOs must be 2.
- When RT in an RRU MO is not set to MPMU, the number of ANTENNAPORT MOs must
range from 1 to 8.
Relation with the ALMPORT MO:
- The relationships between the RRU MO and ALMPORT MO are as follows: When RT in
the RRU MO is not set to MPMU or MPRF, the number of ALMPORT MOs must range from 2
to 4.
- The relationships between the RRU MO and ALMPORT MO are as follows: When RT in
the RRU MO is set to MPMU or MPRF, the number of ALMPORT MOs must be 0.
Relation with the RETPORT MO:
- The number of RETPORT MOs configured on one RRU MO must be greater than or equal
to 0 and smaller than or equal to 1.
Relation with the RXBRANCH MO:
- The number of RXBRANCH MOs configured on one RRU MO must be greater than or
equal to 0 and smaller than or equal to 8.
Relation with the TXBRANCH MO:
- The number of TXBRANCH MOs configured on one RRU MO must be greater than or
equal to 0 and smaller than or equal to 8.
Relation with the EMU,SUBRACK,CCU MOs:
- The MO corresponding to MCN and MSRN in the EMU MO must have been configured
and be one of the following types: 1. A SUBRACK MO with SRN set to 0 or 1; 2. A RRU MO;
3. A CCU MO.
Relation with the FMU,SUBRACK,CCU MOs:
- The MO corresponding to MCN and MSRN in the FMU MO must have been configured
and be one of the following types: 1. A SUBRACK MO with SRN set to 0 or 1; 2. A RRU MO;
3. A CCU MO.
Relation with the PMU,SUBRACK,CCU MOs:
- The MO corresponding to MCN and MSRN in the PMU MO must have been configured
and be one of the following types: 1. A SUBRACK MO with SRN set to 0 or 1; 2. A RRU MO;
3. A CCU MO.
Relation with the TCU,SUBRACK,CCU MOs:
- The MO corresponding to MCN and MSRN in the TCU MO must have been configured and
be one of the following types: 1. A SUBRACK MO with SRN set to 0 or 1; 2. A RRU MO; 3. A
CCU MO.
Relation with the RET,RFU,AAMU MOs:
- The RRU or RFU or AAMU MO corresponding to CTRLCN, CTRLSRN, and CTRLSN
in the RET MO must have been configured.
Relation with the TMA,RFU MOs:
- The RRU or RFU MO corresponding to CTRLCN, CTRLSRN, and CTRLSN in the TMA
MO must have been configured.
Relation with the RRUCHAIN,RFU,AAMU MOs:
- The total number of RRU and RFU and AAMU MOs configured on the RRUCHAIN MO
must be smaller than or equal to 21.
Relation with the AAMU, RRU, and RFU MOs:
- If BM in the RRUCHAIN MO where the RRU MO is located is set to HOT, the total
number of AAMU, RRU, and RFU MOs configured on the RRUCHAIN MO must be 0 or 1.
Relation with the RFU,AAMU,RHUB MOs:
- Under a base station, the total number of RRU, RFU, AAMU, and RHUB MOs must be less
than or equal to 420.
Relation with the RRU MO:
- When TT in the RRUCHAIN MO is set to LOADBALANCE, the number of RFU MOs
specified by RCN and RRU MOs specified by RCN and with RT not set to MPRF must be 0 or
1.
- The RRUCHAIN MO where the RRU MO is located must have been configured.
- The number of RRU whose RT is MPMU configured on the branch chain or ring must be
smaller than or equal to 1.
- A base station can be configured with a maximum of 96 RRU MOs whose RT is set to
MPMU.
- Under a base station, A maximum of 36 RRU MOs with RT set to MRRU or AIRU and RS
set to TDS_TDL can be configured.
- In the RRUCHAIN MO where the RRU MO is located, when TT is set to
LOADBALANCE and HSRN be less than 60, RS is not set to UO or GO.
- When RT in an RRU MO is set to MPRF, another RRU MO with RT set to MPMU must be
configured on the same RRU chain/ring and in the same subrack as the RRU MO with RT set
toMPRF.
Relation with the RHUB MO:
- The RRUCHAIN MO where the RHUB MO is located must not have RRU MO,RFU MO
and AAMU MO.
- When TP in the RRU MO is set to BRANCH, the RHUB MO corresponding to RCN must
have been configured.
Relation with the AAMU, RRU, RFU, and RHUB MOs:
- When HCN, HSRN, and HSN in an RRUCHAIN MO are the same as CN, SRN, and SN in
an RHUB MO, respectively, the RT in the RRU MO that is configured on this RRUCHAIN
MO must be set to MPMU or MPRF.
Relation with the SECTOREQM MO:
- When the antenna of pair of RRU/RFUs for RF intra interconnection is configered in sector
equipment, the sector equipment can contain two antennas at most.
Relation with the number of ALMPORT MOs:
- The relationships between the RRU MO and ALMPORT MO are as follows: 1. If RT in a
RRU MO is set to MRRU, the number of ALMPORT MOs must be 4; 2. If RT in a RRU MO
is set to LRRU, the number of ALMPORT MOs must be 2.
- The relationships between the RRU MO and ALMPORT MO are as follows: 1. If RT in a
RRU MO is set to MRRU or MRXU or AIRU, the number of ALMPORT MOs must be 4; 2. If
RT in a RRU MO is set to PRRU, the number of ALMPORT MOs must be 2.
Relation with the TXBRANCH and RXBRANCH MOs:
- The number of TXBRANCH MOs related to a RRU MO must be equal to TXNUM in the
RRU MO, and the number of RXBRANCH MOs related to the RRU MO must be equal to
RXNUM in the RRU MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP RRUCLKSRC Use this command to query the information about the RRU clock source,
including the number of the slot where the locked baseband board is installed,
number of the port on the locked baseband board, and number of the RRU port
through which clock signals are obtained.

SET RRUCLKSRC Use this command to specify the number of the RRU port through which clock
signals are obtained. The clock signals used by dual-mode RRUs can be
obtained through either of the two (CPRI) ports.

TST LOPRRU Use this command to perform an RRU loopback test to check whether the
physical link between an RRU and its next lower-level RRU is normal. The
execution of this command does not affect the running of the RRUs.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet where the RRU is located.

Subrack No. Indicates the number of the subrack where the RRU is located.

Slot No. Indicates the number of the slot where the RRU is located.

RRU Name Indicates the RRU name.

RRU type Indicates the type of the RRU.

Slot Number of the Indicates the number of the slot where the baseband board providing clock
Locked Baseband
Table 2 Related parameters

Parameter Description

Board signals to the RRU is installed.

Port Number of the Indicates the number of the port on the baseband board providing the clock
Locked Baseband
Board source to the RRU.

Port Number of the Indicates the number of the RRU port through which clock signals are obtained.
Locked RRU

Administrative Indicates the administrative state.


state(from RE)

Alarm Status(from RU) Indicates the alarm status of the board. The alarm state of the board can be
normal, warning, minor or critical. For details about the definition of Alarm
Status, see ITU-T X.731.

Operational State(from Indicates the operational state of the board, which can be set to Enabled or
RU)
Disabled. Enabled indicates that services can be carried on the board. Disabled
indicates that no service can be carried on the board.

Availability Status(from Indicates the physical operation status of the board, which can be Uninstalled,
RU)
Starting up, Normal, Inconsistent, Unconfigured, Power off, Fault,
Communication lost, In test, or the combination of various states. For example,
if a board is not configured and fails to communicate with the main control and
transmission board, the physical operation status of the board is Unconfigured,
Communication lost.

Electronic Label(from Indicates the E-label, a text file with a maximum of 2 KB. It is used to record the
RU)
manufacturing information about equipment such as the board, sub-board, or
optical module. Among board properties displayed in the text file, "BoardType"
indicates the type of the board, "BarCode" indicates the bar code of the board
and is the same as the code labeled on the board, and "Item" indicates the BOM
code.

Type(from RU) Indicates the type of the board.

Serial Number(from Indicates the bar code of the board or the cabinet.
RU)

Description(from RU) Indicates the description about the services and functions provided by the board
or the cabinet.

Date of Indicates the manufacturing date of the board or the cabinet.


Manufacture(from RU)

Vendor(from RU) Indicates the manufacturer of the board or the cabinet.


Table 2 Related parameters

Parameter Description

Issue Number(from RU) Indicates the issue number of the board.

Config Type(from RU) Indicates the type of a board.

Board Indicates the temperature of a board.


Temperature(from RU)

HPA Temperature(from Indicates the temperature of the power amplifier.


RU)

DEVTYPE(from RU) Indicates the type of the device.

VSWR alarm post- The VSWR alarm post-processing switch. If the switch is set to ON when the
processing switch(from
RE) VSWR is greater than the VSWR alarm post-processing threshold, the TX
channel is performed to shut down. If the switch is set to OFF, the RRU
degrades power.
When this switch is set to OFF, an RF module decreases the total TX power of
the TX channel by 3 dB to minimize the impacts of high VSWR. Different
scenarios are described as follows:
1. An RF module degrades its power by decreasing the TX power of carriers
sharing TX channels by 3 dB.
2. In the scenario where two TX channels are configured with transmit diversity
and MIMO, the TX power of one channel is decreased by 3 dB if a major
VSWR alarm is generated in this channel. Meanwhile, the TX power of the
other channel also needs to be decreased by 3 dB for the power balance of TX
channels.
3. In the scenario where multi modes share TX channels and a major VSWR
alarm is generated in one channel, this TX channel is shut down if the switch is
set to ON in any mode. The power of this channel is degraded if this switch is
set to OFF in all the modes.

VSWR alarm post- Indicates the VSWR alarm post-processing threshold. If the VSWR alarm post-
processing
threshold(from RE) processing switch is set to ON and the VSWR is greater than the threshold, post-
processing is performed to shut down the TX channel. In this case, the TX
channel cannot be open automatically after the VSWR is normal. If this
parameter is set to different values in different modes of a multimode base
station, the smallest value takes effect in all the modes.

VSWR alarm Indicates the VSWR alarm threshold. When the current VSWR is greater than
threshold(from RE)
the threshold, a VSWR Abnormal alarm is reported.
It is recommended that the VSWR alarm threshold be set according to the
VSWR required by the engineering quality to reduce the probability that the
VSWR alarm is reported falsely.
To stabilize the false alarm probability to 1%, 0.1%, and 0.01%, you need to set
Table 2 Related parameters

Parameter Description

the VSWR alarm threshold to the following recommended values:


When the VSWR required by the engineering quality is smaller than or equal to
1.4, the recommended thresholds are 1.8, 2.0, and 2.4, respectively.
When the VSWR required by the engineering quality is smaller than or equal to
1.5, the recommended thresholds are 2.0, 2.2, and 2.6, respectively.
If this parameter is set to different values in different modes of a multimode base
station, the smallest value takes effect in all the modes.

RRU Position(from RE) Indicates the position of the RRU, RFU on the chain or ring. It is calculated
from the start port one by one.

RRU Chain No.(from Indicates the ID of the RRU or RFU chain/ring.


RE)

RRU Topo Indicates the position where the RRU or RFU is installed in the topology. There
Position(from RE)
are two types of positions for the RRU or RFU: TRUNK and BRANCH.
BRANCH indicates that the RRU is connected to the RHUB. TRUNK indicates
that the RRU or RFU is located on the main chain/ring. The main chain/ring is
connected to the optical port on the baseband processing board.

RF Unit Working Indicates the working mode of the RRU or RFU. MRFU, MRRU, and PRRU
Mode(from RE)
support both single-mode and multi-mode base stations. LRFU supports only
LTE_FDD and LRRU supports LTE_TDD and LTE_FDD.

Number of RX Indicates the number of RX channels of the RRU or RFU. The RX channels are
channels(from RE)
numbered starting from 0 and must be numbered in the sequence of 0, 1, 2, 3,
4. 0 corresponds to R0A, 1 corresponds to R0B, and the rest can be deduced
by analogy. Ensure that sufficient RX channels are configured before using an
RX channel No. For example, if R0D is used, at least four RX channels must be
configured.

Number of TX Indicates the number of TX channels of the RRU or RFU. The TX channels are
channels(from RE)
numbered starting from 0 and must be numbered in the sequence of 0, 1, 2, 3,
4. 0 corresponds to R0A, 1 corresponds to R0B, and the rest can be deduced
by analogy. Ensure that sufficient TX channels are configured before using an
TX channel No. For example, if R0D is used, at least four TX channels must be
configured.

Number of carriers on Indicates the number of carriers on each RX channel.


the RX channel(from
RE)

Number of carriers on Indicates the number of carriers on each TX channel.


the TX channel(from
RE)
Table 2 Related parameters

Parameter Description

Maximum output power Indicates the total output power of RRU/RFU TX channels.
on the TX channel(from
RE)

UL channel gain(from Indicates the UL channel gain.


RE)

Trunk Level(from RE) Indicates the RRU/RFU level on the trunk of the chain/ring.

Physical RRU device Indicates the serial number of the RRU or RFU. NULL means that the serial
serial No.(from RE)
number fail to be obtained.

RRU standard Indicates the standards that are supported by the RRU or RFU. Invalid means
capability(from RE)
that the standards fail to be obtained.

Access Direction(from Indicates the access direction of the service plane.


RE)

IfOffset(from RE) Indicates the intermediate frequency offset of the RRU or RFU. This parameter
is set by the user during the network planning to avoid the external signal
interference around the current received frequency, and accordingly improve the
receiver sensitivity of the system. This parameter, however, is not recommended
to be used.

RF Desensitivity(from Indicates the RF desensitization intensity of the RRU or RFU. When the air
RE)
interface is under strong blocking or interference, the anti-interference capability
of RF modules can be improved by decreasing the gain on RX channels and
lowering the receiver sensitivity. Currently, this parameter can only be set to 0
dB or 10 dB. When the parameter is set to 10 dB, the uplink receiver sensitivity
is lowered by 10 dB. Therefore, the anti-interference capability is improved.

UL Support Indicates whether the RRU or RFU supports the UL features.


Feature(from RE)

Frequency Min Indicates the minimum effective bandwidth of the carrier.


Bandwidth(from RE)

Low Current Protect Indicates the undercurrent protection switch. If an undercurrent alarm is
Switch(from RE)
generated, the ALD power switch for this RRU or RFU is automatically turned
off only when this parameter is set to ENABLE. NULL means that this RRU or
RFU does not support the undercurrent protection function. Only UMTS
currently support this function.

ALD Reuse Flag(from Indicates whether the ALD is reused. Value 0 indicates that the ALD is not
RE)
reused. Value 1 indicates that the ALD is reused in Greece.

Antenna ID(from RE) Indicates the serial number of the RU in the AAU. The serial numbers of
Table 2 Related parameters

Parameter Description

antennas on other RF modules are invalid.

Antenna Location(from Indicates the slot number of the RU in the AAU. The value of this parameter is
RE)
NULL for other RF modules. The slots of RUs are numbered from 0 in
ascending order from bottom to top.

RU Specification(from Indicates the type of an RF module, which must be the same as the hardware
RE)
type of the RF module. After this parameter is specified, the CME checks the
configurations of power, carrier, and receive and transmit capabilities based on
the value of this parameter. This ensures that these configurations are correct
before they take effect. Only GSM currently support this function.

Cabinet No. of Indicates the cabinet number of RRU2/RFU2 for RF interconnection.For RF


RRU2(from RE)
interconnection in outer interconnection mode, value NULL is displayed
because the cabinet No., subrack No., and slot No. of the peer RRU remain
unknown.

Slot No. of RRU2(from Indicates the slot number of RRU2/RFU2 for RF interconnection.For RF
RE)
interconnection in outer interconnection mode, value NULL is displayed
because the cabinet No., subrack No., and slot No. of the peer RRU remain
unknown.

Subrack No. of Indicates the subrack number of RRU2/RFU2 for RF interconnection.For RF


RRU2(from RE)
interconnection in outer interconnection mode, value NULL is displayed
because the cabinet No., subrack No., and slot No. of the peer RRU remain
unknown.

RF Connect Type(from Indicates the RF interconnection type. Intra interconnection means the
RE)
interconnection between two RRUs or RFUs managed by the same main control
board. Outer connection means the interconnection between two RRUs or RFUs
managed by different main control boards.

Software Version(from Indicates the software version of the board.


RU)

Hardware Version(from Indicates the hardware version of the board.


RU)

BootRom Version(from Indicates the BootROM version of the board.


RU)

PA Efficiency Indicates the power amplifier efficiency improvement switch for an RF module.
Improvement
Switch(from RE) When this parameter is set to ON, the power amplifier efficiency of an RF
module is improved. When this parameter is set to OFF, the power amplifier
efficiency of an RF module is not improved. You can run the DSP RRU
command to query whether an RF module supports the power amplifier
Table 2 Related parameters

Parameter Description

efficiency improvement.

PA Efficiency Indicates whether an RF module supports the power amplifier efficiency


Improvement
Capability(from RE) improvement.

5.7.1.6.2.64 RRUCHAIN
EQUIPMENT
+-RRUCHAIN

Description

The RRUCHAIN MO manages the RRU topology in aspects of the RRU chain/ring number,
networking modes, backup modes, the cabinet number, subrack number, and slot number of the
head and tail of the chain/ring, the position of the breakpoints, the number of RRU levels on the
chain/ring, and the number of RRUs.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
EQUIPMENT

Relation with the RHUB MO:


- The RRUCHAIN MO where the RHUB MO is located must have been configured.
- When TP in the RRU MO is set to BRANCH, the RHUB MO corresponding to RCN must
have been configured.
- The total number of RHUB MOs configured on the RRUCHAIN MO must be smaller than
or equal to 4.
- When an RRUCHAIN MO is configured on an RHUB MO, TT in the RRUCHAIN MO
cannot be set to RING.
Relation with the RFU MO:
- The RRUCHAIN MO where the RFU MO is located must have been configured.
- In the RRUCHAIN MO where the RFU MO is located, when TT is set to
LOADBALANCE, RS is not set to UO or GO.
Relation with the AAMU MO:
- The RRUCHAIN MO where the AAMU MO is located must have been configured.
Relation with the CPRIPORT MO:
- When the RRUCHAIN MO whose AT is set to a value other than PEERPORT, one of the
following CPRIPORT MOs must have been configured:
- 1. A CPRIPORT MO corresponding to HCN, HSRN, HSN, and HPN.
- 2. A CPRIPORT MO corresponding to TCN, TSRN, TSN, and TPN in the RRUCHAIN
MO when TT in the RRUCHAIN MO is set to a value other than CHAIN.
Relation with the RRU,RFU,AAMU MOs:
- The total number of RRU and RFU and AAMU MOs configured on the RRUCHAIN MO
must be smaller than or equal to 21.
Relation with the AAMU, RRU, and RFU MOs:
- If BM in the RRUCHAIN MO where the RFU MO is located is set to HOT, the total
number of AAMU, RRU, and RFU MOs configured on the RRUCHAIN MO must be 0 or 1.
- If BM in the RRUCHAIN MO where the RRU MO is located is set to HOT, the total
number of AAMU, RRU, and RFU MOs configured on the RRUCHAIN MO must be 0 or 1.
- If BM in the RRUCHAIN MO where the AAMU MO is located is set to HOT, the total
number of AAMU, RRU, and RFU MOs configured on the RRUCHAIN MO must be 0 or 1.
Relation with the RRU MO:
- When TT in the RRUCHAIN MO is set to LOADBALANCE, the number of RFU MOs
specified by RCN and RRU MOs specified by RCN and with RT not set to MPRF must be 0 or
1.
- The RRUCHAIN MO where the RRU MO is located must have been configured.
- The number of RRU whose RT is MPMU configured on the branch chain or ring must be
smaller than or equal to 1.
- In the RRUCHAIN MO where the RRU MO is located, when TT is set to
LOADBALANCE and HSRN be less than 60, RS is not set to UO or GO.
Relation with the BBP,BRI,GTMU MOs:
- In the RRUCHAIN MO, when TT is set to RING and the combination of HCN, HSRN, and
HSN is not the same as the combination of TCN, TSRN, and TSN, this RRUCHAIN cannot be
configured on the BRI, GTMU, or BBP with TYPE set to GBBP.
- When the TT in the RRUCHAIN MO is set to LOADBALANCE, the total number of BBP
MO with the TYPE set to GBBP, BRI MO, and GTMU MO where the RRUCHAIN MO is
configured must be 0 or 1.
Relation with the BBP,BRI,GTMU,RHUB MOs:
- When the RRUCHAIN MO whose AT is set to a value other than PEERPORT, one of the
following BBP, BRI , GTMU or RHUB MOs must have been configured:
- 1. A BBP, BRI, GTMU or RHUB MO corresponding to HCN, HSRN, and HSN.
- 2. A BBP, BRI, GTMU or RHUB MO corresponding to TCN, TSRN, and TSN in the
RRUCHAIN MO when TT in the RRUCHAIN MO is set to a value other than CHAIN.
Relation with the AAMU, RRU, RFU, and RHUB MOs:
- When HCN, HSRN, and HSN in an RRUCHAIN MO are the same as CN, SRN, and SN in
an RHUB MO, respectively, the RT in the RRU MO that is configured on this RRUCHAIN
MO must be set to MPMU or MPRF.
Relation with the BBP MO:
- In the RRUCHAIN MO, when TT is set to RING and the combination
- of HCN, HSRN, and HSN is not the same as the combination
- of TCN, TSRN, and TSN,
- the TYPE of BBP MO where the RRUCHAIN MO is configured is the same or the TYPE
of one BBP MO is UBBP.
Relation with the RRUCHAIN MO:
- A maximum of 96 RRUCHAIN MOs where the value of HSRN ranges from 60 to 254 can
be configured on a base station.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD RRUCHAIN Use this command to add an RRU chain/ring before adding an RRU to the
chain/ring. There are two types of RRU chains/rings: TRUNK and BRANCH.
TRUNK indicates that the RRU or RFU is located on the main chain/ring
connected to the optical port on the baseband processing board. BRANCH
indicates that the RRU or RFU is connected to the RHUB.

CMB RRUCHAIN Use this command to combine two RRU chains into a cold backup RRU ring.
The cold backup mode is described in the backup mode description of the MOD
RRUCHAIN command.
To improve the reliability of the RRU topology, use an optical fiber to connect
two RRUs on the tails of two chains. Then, run this command to combine them
into a ring.
Table 1 Related MML commands

MML Command Function

When the original two RRU chains are combined successfully, the number of the
first chain is used as the number of the newly created ring by default.
If the original two RRU chains have no breakpoints, the new ring has no
breakpoint.
If only one RRU chain has breakpoints, breakpoints 1 and 2 of the new ring
coincide.
If both the original RRU chains have breakpoints, the new ring has two
breakpoints. The position of breakpoint 1 is that of the breakpoint on the first
RRU chain. The position of breakpoint 2 is the level of the new ring minus the
position of the breakpoint on the second RRU chain.

DSP RRUCHAIN Use this command to query the physical information of the RRU chain.

LST RRUCHAIN Use this command to query the configuration of the RRU chain.

MOD RRUCHAIN Use this command to modify the attributes of an RRU chain/ring, including the
positions of the optical ports at the RRU chain head, ring head, and ring tail,
networking mode of the RRU chain/ring, and positions of the breakpoints on the
RRU chain/ring.
To modify the configuration of an RRU chain or ring, perform the following
steps:
1. Run this command to set breakpoints at the optical port on the chain/ring to be
modified.
Only one breakpoint (breakpoint 0) needs to be set for a chain.
Two breakpoints need to be set for a ring. The position of the first breakpoint is
0, and the position of the second breakpoint is the level of the RRU.
2. Reconnect the cables, and modify the configurations. Ensure that the physical
connection is consistent with the configuration.
3. Run this command to remove the breakpoints by setting the positions of
breakpoints 1 and 2 to 255.

RMV RRUCHAIN Use this command to remove an RRU chain or ring.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Chain No. Indicates the ID of the RRU chain. It uniquely identifies a chain within a base
station.

Topo Type Indicates the type of the topology.In a ring topology, the service data is
transmitted on the fiber optic cable that carries the HDLC link. In a load sharing
topology, the service data is transmitted on two fiber optic cables
simultaneously, which enhances the transmission capability. The physical
connection in the ring topology is similar to that in the load sharing topology.

Backup Mode Indicates the backup mode of the RRU chain/ring. There are two modes: cold
backup and hot backup. Cold backup indicates that when the link on one end of
the chain/ring fails, the service is disrupted for a short period of time, and then
re-established on the other end of the chain/ring. Hot backup indicates that when
the link on one end of the chain/ring fails, the service is taken over by the other
end of the chain/ring immediately. There is only one RRU on the chain/ring in
hot backup mode.In the RRUCHAIN MO, if TT is set to RING and BM is set to
HOT, the head CPRI port and the tail CPRI port of the RRU ring must be on
different baseband boards.

Head Cabinet No. Indicates the cabinet number of the board where the head CPRI port is located.

Head Subrack No. Indicates the subrack number of the board where the head CPRI port is located.

Head Slot No. Indicates the slot number of the board where the head CPRI port is located.

Head Port No. Indicates the number of the head CPRI port.

Tail Cabinet No. Indicates the cabinet number of the board where the tail CPRI port is
located.Value NULL is displayed for the RRU chain which does not have a tail
CPRI port.

Tail Subrack No. Indicates the subrack number of the board where the tail CPRI port is
located.Value NULL is displayed for the RRU chain which does not have a tail
CPRI port.

Tail Slot No. Indicates the slot number of the board where the tail CPRI port is located.Value
NULL is displayed for the RRU chain which does not have a tail CPRI port.

Tail Port No. Indicates the number of the tail CPRI port. Value NULL is displayed for the
RRU chain which does not have a tail CPRI port.

BreakPoint Position1 Indicates the breakpoint position 1 on the chain/ring. When this parameter is set
to 255, the breakpoint is disabled.
Table 2 Related parameters

Parameter Description

BreakPoint Position2 Indicates the breakpoint position 2 on the chain/ring. When this parameter is set
to 255, the breakpoint is disabled.

Access Type Indicates the access type of the RRU. When AccessType is set to the local port,
the BBP is connected to the RRU/RFU through the CPRI port. When
AccessType is set to the peer port, the peer BBP is directly connected to the
RRU/RFU, and the local BBP is connected to the peer BBP through the IDX2
port on the backplane.

CPRI Line Rate Indicates the user-defined rate. The value AUTO indicates the the auto
negotiation mode is adopted. The value 1.25 indicates that the CPRI rate is 1.25
Gbit/s. The value 2.5 indicates that the CPRI rate is 2.5 Gbit/s. The value 4.9
indicates that the CPRI rate is 4.9 Gbit/s. The value 6.1 indicates that the CPRI
rate is 6.1 Gbit/s. The value 9.8 indicates that the CPRI rate is 9.8 Gbit/s.

Chain Level Indicates the level of the RRU chain.

RRU Number Indicates the number of RRUs carried on the RRU chain/ring.

5.7.1.6.2.65 RU
Description

The RU(replaceable unit) MO is a virtual base class of a board, which provides keywords and
status information of the cabinet, subrack, and slot.

Effective Scenario

Immediately

Relations Between MOs

Inherit children:
TRP;BRI;UEIU;MPT;USCU;RE;FMU;UCIU;PEU;PMU;EMU;GTMU;BBP;TCU;RHUB;BBUFAN;PSU

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD BRD Use this command to add a board. Only the boards in the BBU can be added by
running this command.

BLK BRD Use this command to block a specified board.

DSP BKPSTATUS Use this command to query information about the backup status, including
software packages, configuration data, and logs.

DSP BRD Use this command to query the status of a board.

DSP BRDMFRINFO Use this command to query the manufacturing information about a board. Only
one board can be queried at a time. Because there is only one backplane in the
BBU subrack, the manufacturing information about the subrack can be obtained
by the query of the manufacturing information about the backplane.

DSP BRDTEMP Use this command to query the temperature of a board. The temperature of the
board includes the board temperature and power amplifier temperature.

DSP CPUUSAGE Use this command to query the CPU/DSP usage of a board. After the execution
of this command, the usage of the master CPU, slave CPU, and DSP (if any) is
displayed.

DSP ELABEL Use this command to query the electronic label of cabinet, subrack, board (can
be a monitoring board,RRU or RFU), sub-board, Small Form-factor Pluggable
(SFP) or GPS. The command output includes the manufacturing information.

DSP HWTSTRESULT Use this command to query the result of the latest hardware test on a board.

DSP MEMUSAGE Use this command to query the memory usage.

DSP SWAPLOG Use this command to query the recent swap records.

MOD PEERMODE Use this command to modify the working mode of the main control board at the
peer end. If the local subrack is selected, the working mode of the peer main
control board in the local subrack will be modified. Otherwise, the working
mode of the peer main control board in the peer subrack will be modified.

OPR BRDPWR Use this command to perform power-on and power-off of a board. If a board in
the BBU subrack is not carrying services, you can power off the board to save
power. To use the board, you can power on it again. In a dual-mode BS, this
command can be run to power on or off a board of the other mode. The service
carried on the board is interrupted after the power-off.
Table 1 Related MML commands

MML Command Function

RMV BRD Use this command to remove a board.

RST BRD Use this command to reset a specified board, except passive boards such as the
UPEU and USCU.

RST BRDPWROFF Use this command to power off a board. Then, the board is powered on
automatically and is reset, which helps to clear some hardware faults of the
board. Currently, only the boards (excluding the FAN unit, UPEU, UEIU) in the
BBU, and the RRU/RFU/PRRU support power-off reset. Some RRUs do not
support power-off reset.

RST CANBUS Use this command to reset the controller area network BUS (CANBUS) of a
specified board.

STR HWTST Use this command to start a hardware test on a board, which aims to locate or
rectify the hardware faults on the board.

SWP BRD Use this command to manually start the swap of the active and standby boards
(main control boards). When this command is executed successfully, the
previous standby board becomes active and functions as the active board, while
the previous active one becomes standby.

UBL BRD Use this command to unblock a specified board.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Alarm Status Indicates the alarm status of the board. The alarm state of the board can be
normal, warning, minor or critical. For details about the definition of Alarm
Status, see ITU-T X.731.

Operational State Indicates the operational state of the board, which can be set to Enabled or
Disabled. Enabled indicates that services can be carried on the board. Disabled
indicates that no service can be carried on the board.

Availability Status Indicates the physical operation status of the board, which can be Uninstalled,
Table 2 Related parameters

Parameter Description

Starting up, Normal, Inconsistent, Unconfigured, Power off, Fault,


Communication lost, In test, or the combination of various states. For example,
if a board is not configured and fails to communicate with the main control and
transmission board, the physical operation status of the board is Unconfigured,
Communication lost.

Electronic Label Indicates the E-label, a text file with a maximum of 2 KB. It is used to record the
manufacturing information about equipment such as the board, sub-board, or
optical module. Among board properties displayed in the text file, "BoardType"
indicates the type of the board, "BarCode" indicates the bar code of the board
and is the same as the code labeled on the board, and "Item" indicates the BOM
code.

Type Indicates the type of the board.

Serial Number Indicates the bar code of the board or the cabinet.

Description Indicates the description about the services and functions provided by the board
or the cabinet.

Date of Manufacture Indicates the manufacturing date of the board or the cabinet.

Vendor Indicates the manufacturer of the board or the cabinet.

Issue Number Indicates the issue number of the board.

Config Type Indicates the type of a board.

Board Temperature Indicates the temperature of a board.

HPA Temperature Indicates the temperature of the power amplifier.

DEVTYPE Indicates the type of the device.

Software Version Indicates the software version of the board.

Hardware Version Indicates the hardware version of the board.

BootRom Version Indicates the BootROM version of the board.

5.7.1.6.2.66 RXBRANCH
EQUIPMENT
+-CABINET
+-SUBRACK
EQUIPMENT
+-RRU
+-RXBRANCH
EQUIPMENT
+-AAS
+-AARU
+-RXBRANCH
EQUIPMENT
+-CABINET
+-SUBRACK
+-RFU
+-RXBRANCH
EQUIPMENT

Description

The RxBranch MO is responsible for the number of RX channel, the logical switch, attenuation,
physical status of the RX channel, and the initial correction value of the RTWP.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
RRU;AARU;RFU;

Relation with the RFU MO:


- The number of RXBRANCH MOs configured on one RFU MO must be greater than or
equal to 0 and smaller than or equal to 8.
Relation with the RRU MO:
- The number of RXBRANCH MOs configured on one RRU MO must be greater than or
equal to 0 and smaller than or equal to 8.
Relation with the ANTENNAPORT MO:
- One ANTENNAPORT MO maps to TXBRANCH MO and one RXBRANCH MO.

Related MML Commands


Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP RXBRANCH Use this command to query the dynamic attributes of the RX channel of the
RRU or RFU.

LST RXBRANCH Use this command to list the RX channel configuration of an RRU or RFU.

MOD RXBRANCH Use this command to modify the RX channel of an RRU or RFU. If the main
antenna is responsible only for transmitting signals, you can run this command
to set the switch of the RX channel of the main antenna to OFF.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the RRU or RFU where the RX channel of the
RRU or RFU is located.

Subrack No. Indicates the subrack number of the RRU or RFU where the RX channel of the
RRU or RFU is located.

Slot No. Indicates the slot number of the RRU or RFU where the RX channel of the RRU
or RFU is located.

RX Channel No. Indicates the number of the RX channel of the RRU or RFU.0 corresponds to
R0A, 1 corresponds to R0B, and the rest can be deduced by analogy.

Logical Switch of RX Indicates the logical switch of the RX channel of the RRU or RFU, which is set
Channel
to ON by default. The switch can be set by running the MOD RXBRANCH
command.

Attenuation Indicates the attenuation of the RX channel of the RRU or RFU.

Physical Switch of RX Indicates the actual physical status of the RX channel of the RRU or RFU, the
Channel
switch of which is set to ON by default. When the logical switch of the RX
channel is OFF, the physical switch of the RX channel must be OFF. When the
logical switch of the RX channel is ON and the RRU is running properly, the
Table 2 Related parameters

Parameter Description

physical switch of the RX channel of the RRU can be ON.

RTWP Initial0 Indicates the initial correction value of the Received Total Wideband Power
(RTWP) for carrier 0. The big offset between the RTWP in empty load and the
theoretical background noise can be adjusted through the setting of initial
correction value of the RTWP.

RTWP Initial1 Indicates the initial correction value of the RTWP for carrier 1.

RTWP Initial2 Indicates the initial correction value of the RTWP for carrier 2.

RTWP Initial3 Indicates the initial correction value of the RTWP for carrier 3.

RTWP Initial4 Indicates the initial correction value of the RTWP for carrier 4.

RTWP Initial5 Indicates the initial correction value of the RTWP for carrier 5.

RTWP Initial6 Indicates the initial correction value of the RTWP for carrier 6.

RTWP Initial7 Indicates the initial correction value of the RTWP for carrier 7.

Band 1 Minimum Indicates the minimum uplink frequency supported by the RRU or RFU band 1.
frequency
For example, if this parameter is set to 9250, the minimum uplink frequency of
the RRU is 9250 x 0.1 MHz, which equals to 925 MHz.

Band 1 Maximum Indicates the maximum uplink frequency supported by the RRU or RFU band 1.
frequency
For example, if this parameter is set to 9450, the maximum uplink frequency of
the RRU is 9450 x 0.1 MHz, which equals to 945 MHz.

Band 1 UL Bandwidth Indicates the bandwidth supported by each TX channel band 1 in the downlink.
This bandwidth is an instantaneous bandwidth.

Band 2 Minimum Indicates the minimum uplink frequency supported by the RRU or RFU band
frequency
2.This parameter is NULL,when the RRU does not supported many bands. For
example, if this parameter is set to 9250, the minimum uplink frequency of the
RRU is 9250 x 0.1 MHz, which equals to 925 MHz.

Band 2 Maximum Indicates the maximum downlink frequency supported by the RRU or RFU band
frequency
2.This parameter is NULL,when the RRU does not supported many bands. For
example, if this parameter is set to 9850, the maximum downlink frequency of
the RRU is 9850 x 0.1 MHz, which equals to 985 MHz.

Band 2 UL Bandwidth Indicates the bandwidth supported by each TX channel band 2 in the uplink.
Table 2 Related parameters

Parameter Description

This bandwidth is an instantaneous bandwidth. This parameter is NULL, when


the RRU does not supported multi-bands.

5.7.1.6.2.67 SECTOR
+-NE
+-NODE
+-CARRIERRESOURCE
+-SECTOR

Description

A sector is a radio area covered by a set of RF antennas with the same coverage.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
CARRIERRESOURCE

Relation with the SECTOR MO:


- An antenna can be configured only in one SECTOR MO.
- A SECTOR MO must be configured with at least one sector antenna.
Relation with the SECTOREQM MO:
- The SECTOR MO corresponding to the SECTOREQM MO must have been configured.
- An antenna in the sector equipment must exist in the sector that is quoted by the sector
equipment.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD QUICKSECTOR Use this command to quickly create sectors and sector equipment.

ADD SECTOR Use this command to add a sector and antennas in the sector.

DSP SECTOR Use this command to display state of a sector.

LST SECTOR Use this command to list configuration of a sector.

MOD SECTOR Use this command to modify the name and location name of a sector. You can
also use this command to add an antenna to or remove an antenna from this
sector.

RMV SECTOR Use this command to remove a sector.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Sector ID Indicates the number of the sector.

Sector Name Indicates the name of the sector.

Location Name Indicates the location name of the base station.

User Label Indicates the user-defined information of a sector. The value of this parameter
consists of xx::yy and common character strings, which are separated by
percentage signs (%), for example, %tel::88888888%owner::huawei
%20130101. xx::yy indicates that the value of xx is yy.

Sector Antenna Indicates the information about the sector antenna.

RX Frequency Range Indicates the range of RX channel frequencies supported by the sector. The
minimum and maximum frequencies used by an RX channel are obtained based
on the RRU to which the channel is connected. If the sector is served by
multiple RRUs, the frequency range supported by the sector is the intersection
of all frequencies used by these RRUs. If the sector is served by only one RRU,
the frequency range supported by the sector is the same as that of the RRU.
Table 2 Related parameters

Parameter Description

TX Frequency Range Indicates the range of TX channel frequencies supported by the sector. The
minimum and maximum frequencies used by a TX channel are obtained based
on the RRU to which the channel is connected. If the sector is served by
multiple RRUs, the frequency range supported by the sector is the intersection
of all frequencies used by these RRUs. If the sector is served by only one RRU,
the frequency range supported by the sector is the same as that of the RRU.

Sector License Indicates the license to be requested for a sector.

License State Indicates the license status of a sector.

5.7.1.6.2.68 SECTOREQM
+-NE
+-NODE
+-CARRIERRESOURCE
+-SECTOREQM

Description

Sector equipment is a set of RF antennas that can transmit or receive signals. This set of antennas
must belong to a sector.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
CARRIERRESOURCE

Relation with the SECTOREQM MO:


- A SECTOREQM MO must be configured with at least one sector equipment antenna.
- When the sector equipment is configured with a slave antenna, it must be configured with
only one master antenna and one slave antenna.
- The cabinet number, subrack number, slot number, and channel number of any two antennas
in a set of sector equipment cannot be the same at the same time.
Relation with the SECTOR MO:
- The SECTOR MO corresponding to the SECTOREQM MO must have been configured.
- An antenna in the sector equipment must exist in the sector that is quoted by the sector
equipment.
Relation with the RRU MO:
- When the antenna of pair of RRU/RFUs for RF intra interconnection is configered in sector
equipment, the sector equipment can contain two antennas at most.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD SECTOREQM Use this command to add sector equipment and sector equipment antennas.

LST SECTOREQM Use this command to list the configuration of sector equipment.

MOD SECTOREQM Use this command to add or remove a sector equipment antenna in sector
equipment.

RMV SECTOREQM Use this command to remove sector equipment.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Sector Equipment ID Indicates the number of the sector equipment.

Sector ID Indicates the number of the sector in which the sector equipment is located.

Sector Equipment Indicates the information about the sector equipment antenna.
Antenna
5.7.1.6.2.69 SES
Description

The SES MO is used to report the progress and to magage the FTP connection.

Effective Scenario

Immediately

Relations Between MOs

None

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST SESSIONID Use this command to list the IDs and descriptions of all ongoing file transfer
sessions on the NE.

STP FTP Use this command to stop one or all ongoing FTP transfer sessions.

Parent topic: Equipments-tree

5.7.1.6.2.70 SFP
EQUIPMENT
+-CABINET
+-SUBRACK
+-BRI
+-SFP
EQUIPMENT
+-CABINET
+-SUBRACK
EQUIPMENT
+-CABINET
+-SUBRACK
+-GTMU
+-SFP
EQUIPMENT
+-CABINET
+-SUBRACK
EQUIPMENT
+-RRU
+-SFP
EQUIPMENT
+-CABINET
+-SUBRACK
+-RFU
+-SFP
EQUIPMENT
+-CABINET
+-SUBRACK
+-BBP
+-SFP
EQUIPMENT
+-RHUB
+-SFP
EQUIPMENT
+-AAS
+-AAMU
+-SFP
EQUIPMENT
+-CABINET
+-SUBRACK
+-UCIU
+-SFP
EQUIPMENT
+-CABINET
+-SUBRACK
+-MPT
+-SFP
EQUIPMENT

Description
The SFP MO consists of optical modules and electrical modules. The optical and electrical
modules are used to transmit signals through optical fibers or cables between the BBU and other
equipment. The information about the optical or electrical module is not configurable. This
information can only be queried.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
BRI;GTMU;RRU;RFU;BBP;RHUB;AAMU;UCIU;MPT;

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP SFP Use this command to query the dynamic information of an optical or electrical
module.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the optical or electrical module.

Subrack No. Indicates the subrack number of the optical or electrical module.

Slot No. Indicates the slot number of the optical or electrical module.

Port No. Indicates the number of the optical or electrical module. If a UCIU is queried,
values 0 to 4 indicate the ports M0 to M4 on the board panel, and value 8
indicates the port S0 on the board panel. If a UMPT is queried, value 8 indicates
the port CI on the board panel. If a LBBPd board is queried, value 6 indicates
Table 2 Related parameters

Parameter Description

the port HEI on the board panel.

Installed status Indicates whether the optical or electrical module is in position.

SFP Module Type Indicates the type of an optical or electrical module, which can be SFP, enhanced
SFP, SFP electrical port, QSFP, QSFP electrical port, or CPRI_E. These six
types are different in the supported rate sets, transmission distance, and number
of channels. The transmission distance of the electrical port is short, so it is used
to connect the BBU or RFU. The Small Form-factor Pluggable (SFP) is a small
hot-swappable module, which can be connected to an optical or electrical
module. The enhanced SFP and SFP are different in their supported rate sets.
QSFP has four bi-directional channels and SFP has one bi-directional channel.
CPRI_E, used in an RJ45 connector, is used to connect the RHUB and MPMU.
In addition, CPRI_E transmits data using Ethernet cables.

Manufacturer name Indicates the manufacturer of the optical or electrical module.

Transmission Mode Indicates the transmission mode of the optical module, that is, single-mode or
multi-mode.

Wavelength Indicates the wavelength of the optical module.

Transmission code rate Indicates the transmission code rate of the optical or electrical module.

Transmission distance Indicates the maximum distance that signals from the optical module can travel
of single-mode fiber (9-
micrometer core along a single-mode optical fiber with a 9-micrometer core diameter. The value
diameter) 0 indicates that the optical module does not support this type of optical fiber.

Transmission distance Indicates the maximum distance that signals from the optical module can travel
of single-mode fiber (9-
micrometer core along a single-mode optical fiber with a 9-micrometer core diameter. The value
diameter) 0 indicates that the optical module does not support this type of optical fiber.

Transmission distance Indicates the maximum distance that signals from the optical module can travel
of multi-mode fiber (50-
micrometer core along a multi-mode optical fiber with a 50-micrometer core diameter. The value
diameter) 0 indicates that the optical module does not support this type of optical fiber.

Transmission distance Indicates the maximum distance that signals from the optical module can travel
of multi-mode fiber
(62.5-micrometer core along a multi-mode optical fiber with a 62.5-micrometer core diameter. The
diameter) value 0 indicates that the optical module does not support this type of optical
fiber.

Temperature Indicates the observed temperature of the optical module. This parameter is
valid only when the optical module type is ESFP.
Table 2 Related parameters

Parameter Description

Voltage Indicates the observed voltage of the optical module. This parameter is valid
only when the optical module type is ESFP.

Current Indicates the observed current of the optical module. This parameter is valid
only when the optical module type is ESFP.

TX optical power Indicates the TX optical power of the optical module. This parameter is valid
only when the optical module type is ESFP.

RX optical power Indicates the RX optical power of the optical module. This parameter is valid
only when the optical module type is ESFP.

Receive Power Upper Indicates the upper threshold for the receive power of an optical module.
Threshold

Receive Power Lower Indicates the lower threshold for the receive power of an optical module.
Threshold

Transmit Power Upper Indicates the upper threshold for the transmit power of an optical module.
Threshold

Transmit Power Lower Indicates the lower threshold for the transmit power of an optical module.
Threshold

5.7.1.6.2.71 SSL
TRANSPORT
+-SSL

Description

The SSL MO defines the configuration information about the Security Socket Layer (SSL),
which includes the configuration of the SSL connection and the query of SSL version supported
by an NE.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP SSLCPB Use this command to query the Secure Sockets Layer (SSL) versions supported
by an NE. The SSL version information indicates the NE SSL connection
capability.

DSP SSLERRINFO Use this command to query the latest error information about the Secure Socket
Layer (SSL) connection.

LST AUTHPOLICY Use this command to query the authentication method for login.

LST OMCONNPOLICY Use this command to list the security policy of OM connections.

LST SSLCONF Use this command to list the configuration parameter attributes of SSL.

SET AUTHPOLICY Use this command to set the authentication method for login.

SET CONNTYPE Use this command to set the type of connection between an NE and a client.

SET OMCONNPOLICY Use this command to set the security policy of OM connections.

SET SSLAUTHMODE Use this command to set the authentication mode for the NE to be used during
the Secure Sockets Layer (SSL) handshake.

SET SSLCONF Use this command to set configurations of the SSL.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Connection Type Indicates the connection type supported by the NE.Compatible connection mode
indicates that the NE supports both the common connection mode and the SSL
connection mode.
Table 2 Related parameters

Parameter Description

Authentication Mode Indicates the authentication mode of the SSL connection.If the authentication
mode is set to NONE, the NE does not verify the certificate of the M2000 or
LMT during setup of an SSL connection. In this case, both parties must support
the same algorithm for anonymous authentication.If authentication using the
peer certificate is used, the NE must verify the certificate of the M2000 or LMT
during setup of an SSL connection. If the certificate verification fails, the SSL
connection cannot be set up.

Login Authentication Indicates the login type of the authentication.


Type

TLS/SSL Version Indicates the TLS or SSL version supported by the NE.TLS(Transport Layer
Security).The TLS1.2 version is enabled eternally in the system, and therefore it
cannot be disabled currently.

5.7.1.6.2.72 SUBRACK
EQUIPMENT
+-CABINET
+-SUBRACK
+-TRP[0~7]
+-BRI[0~1]
+-USCU[0~1]
+-BBP[0~6]
+-PSU[0~7]
+-EMU[0~1]
+-RFU[0~9]
+-FMU[0~1]
+-MPT[0~2]
+-PEU[0~2]
+-BBUFAN[0~1]
+-UEIU[0~2]
+-TCU[0~4]
+-GTMU[0~1]
+-CCU[0~1]
+-UCIU[0~8]
+-PMU[0~1]
Description

A Subrack MO is a container of boards. It can be an actual subrack, for example, a BBU subrack
or an RF surback. It can also be a virtual subrack, for example, a PMU subrack, a TCU surback,
or an RRU surback.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
CABINET

Possible children:
TRP[0~7];BRI[0~1];USCU[0~1];BBP[0~6];PSU[0~7];EMU[0~1];RFU[0~9];FMU[0~1];MPT[0~2];PEU[
0~2];BBUFAN[0~1];UEIU[0~2];TCU[0~4];GTMU[0~1];CCU[0~1];UCIU[0~8];PMU[0~1]
Relation with the CTRLLNK MO:
- When two SUBRACK MOs with SRN set to 0 or 1 are configured, the current SUBRACK
MO must meet one of the following conditions: 1. CN and SRN in the SUBRACK MO are the
same as CN and SRN in a CTRLLNK that is already configured. 2. CN and SRN in the
SUBRACK MO are the same as UPCN and UPSRN in a CTRLLNK respectively that is
already configured.
Relation with the CABINET MO:
- A maximum of two SUBRACK MOs can have the same value for TYPE, which can be
BBU3900 or BBU3900-1U.
- When TYPE in the CABINET MO is set to one of the following values, the number of
SUBRACK MOs with TYPE set to RFU in this CABINET MO must be 0 or 1: RFC,
BTS3900, BTS3012_SRAN, BTS3012AE_SRAN and BTS3900AL.
Relation with the CCU,CTRLLNK MOs:
- If the MO corresponding to MCN and MSRN in the CCU MO is a SUBRACK MO with
SRN of 0 or 1, the SUBRACK MO cannot be a secondary subrack.
Relation with the EMU,CTRLLNK MOs:
- If the MO corresponding to MCN and MSRN in the EMU MO is a SUBRACK MO with
SRN of 0 or 1, the SUBRACK MO cannot be a secondary subrack.
Relation with the FMU,CTRLLNK MOs:
- If the MO corresponding to MCN and MSRN in the FMU MO is a SUBRACK MO with
SRN of 0 or 1, the SUBRACK MO cannot be a secondary subrack.
Relation with the PMU,CTRLLNK MOs:
- If the MO corresponding to MCN and MSRN in the PMU MO is a SUBRACK MO with
SRN of 0 or 1, the SUBRACK MO cannot be a secondary subrack.
Relation with the TCU,CTRLLNK MOs:
- If the MO corresponding to MCN and MSRN in the TCU MO is a SUBRACK MO with
SRN of 0 or 1, the SUBRACK MO cannot be a secondary subrack.
Relation with the TRP,CTRLLNK MOs:
- If SUBTYPE in the TRP MO is set to UTRPc,the TRP MO must be configured in master
BBU subrack.
Relation with the CCU MO:
- The number of CCU MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 1.
- The MO corresponding to MCN and MSRN in the CCU MO must have been configured
and must be a SUBRACK MO with SRN set to 0 or 1.
Relation with the BBP MO:
- The number of BBP MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 6.
Relation with the BBUFAN MO:
- The number of BBUFAN MOs configured on one SUBRACK MO must be greater than or
equal to 0 and smaller than or equal to 1.
Relation with the BRI MO:
- The number of BRI MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 4.
Relation with the EMU MO:
- The number of EMU MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 1.
Relation with the FMU MO:
- The number of FMU MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 1.
Relation with the MPT MO:
- The number of MPT MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 2.
Relation with the PEU MO:
- The number of PEU MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 2.
Relation with the PMU MO:
- The number of PMU MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 1.
Relation with the PSU MO:
- The number of PSU MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 7.
Relation with the RFU MO:
- The number of RFU MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 9.
Relation with the TCU MO:
- The number of TCU MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 4.
Relation with the TRP MO:
- The number of TRP MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 7.
Relation with the UCIU MO:
- The number of UCIU MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 8.
Relation with the UEIU MO:
- The number of UEIU MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 2.
Relation with the USCU MO:
- The number of USCU MOs configured on one SUBRACK MO must be greater than or
equal to 0 and smaller than or equal to 1.
Relation with the EMU,RRU,CCU MOs:
- The MO corresponding to MCN and MSRN in the EMU MO must have been configured
and be one of the following types: 1. A SUBRACK MO with SRN set to 0 or 1; 2. A RRU MO;
3. A CCU MO.
Relation with the FMU,RRU,CCU MOs:
- The MO corresponding to MCN and MSRN in the FMU MO must have been configured
and be one of the following types: 1. A SUBRACK MO with SRN set to 0 or 1; 2. A RRU MO;
3. A CCU MO.
Relation with the PMU,RRU,CCU MOs:
- The MO corresponding to MCN and MSRN in the PMU MO must have been configured
and be one of the following types: 1. A SUBRACK MO with SRN set to 0 or 1; 2. A RRU MO;
3. A CCU MO.
Relation with the TCU,RRU,CCU MOs:
- The MO corresponding to MCN and MSRN in the TCU MO must have been configured and
be one of the following types: 1. A SUBRACK MO with SRN set to 0 or 1; 2. A RRU MO; 3. A
CCU MO.
Relation with the SUBRACK MO:
- The SUBRACK MO corresponding to the combination of CN and SRN or the combination
of UPCN and UPSRN in the CTRLLNK MO has been configured.
Relation with the monitoring boards:
- A SUBRACK MO can be configured with the following MOs: 0 or 1 TCU MO, 0 or 1 PMU
MO, 0 or 1 EMU MO, 0 to 7 PSU MOs, and 0 to 2 FMU MOs.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD SUBRACK Use this command to add a BBU subrack or an RFU subrack. This command is
not applicable to other types of subracks. Those subracks are added
automatically while the devices are added.

DSP PWRTYPE Use this command to query the type of power supply to an RRU or a BBU
subrack. The BBU supports the -48 V DC or +24 V DC power supply, and the
RRU supports the 220 V AC or -48 V DC power supply.

LST SUBRACK Use this command to list the configuration of a subrack. If the user does not
specify the subrack number, the system would return the configuration of all
subracks within the specified cabinet. If the user does not specify the cabinet
number and subrack number, the system would return the configuration of all
subracks (including the electromagnetic subrack) in the system.

MOD SUBRACK Use this command to modify the configuration of a subrack. The description of
the subrack can be modified.

RMV SUBRACK Use this command to remove a subrack.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the subrack.

Subrack No. Indicates the number of the subrack.

Subrack Type Indicates the type of the subrack.

Subrack Description Indicates a brief description of the subrack, which can be the function, location,
and some other information of the subrack.

Power Type Indicates the type of power supply to the subrack.

5.7.1.6.2.73 SYNCETH
EQUIPMENT
+-SYNCETH

Description

The SyncEth MO is the synchronous Ethernet, which is a type of reference clock source. The
Synchronous-Ethernet clock inherits the basic principles of clock synchronization in
Synchronous Digital Hierarchy (SDH) and Plesiochronous Digital Hierarchy (PDH) networks.
That is, downstream nodes extract and trace upstream clocks by recovering the clocks from the
parallel bit streams at the physical layer. Therefore, the clocks are irrelevant to upper-layer
services.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
EQUIPMENT

Relation with the GPS,TASM MOs:


- If MODE and CLKSRC in the TASM MO are set to MANUAL and GPS+SYNCETH,
respectively, the corresponding GPS and SYNCETH MOs must have been configured.
Relation with the IPCLKLNK,TASM MOs:
- If MODE and CLKSRC in the TASM MO are set to MANUAL and SYNCETH+IPCLK,
respectively, the corresponding SYNCETH and IPCLKLNK MOs must have been configured.
Relation with the TASM MO:
- If MODE and CLKSRC in the TASM MO are set to MANUAL and SYNCETH,
respectively, the corresponding SYNCETH MO must have been configured.
Relation with the PORTSECURITY MO:
- If the TYPE in the SYNCETH is set to IN, the PORTSECURITY MO corresponding to
CN, SRN, SN and PN in the SYNCETH MO has been configured and SWITCH in this
PORTSECURITY MO must be set to ENABLE.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD SYNCETH Use this command to add a synchronous-Ethernet clock link.

DSP SYNCETH Use this command to query the running status of a specified synchronous-
Ethernet clock link.

LST SYNCETH Use this command to list the configuration of all synchronous-Ethernet clock
links.

MOD SYNCETH Use this command to modify the configuration of a specified synchronous-
Ethernet clock link.

RMV SYNCETH Use this command to remove a specified synchronous-Ethernet clock link.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

SyncEth Clock No. Indicates the number of the synchronous-Ethernet clock link. A maximum of
two links can be configured currently.
Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet where the synchronous-Ethernet clock link
is configured.

Subrack No. Indicates the number of the subrack where the synchronous-Ethernet clock link
is configured.

Slot No. Indicates the number of the slot where the synchronous-Ethernet clock link is
configured.

Port No. Indicates the number of the port where the synchronous-Ethernet clock link is
configured.

SSM Selection Indicates whether handling of SSM frames is supported.The setting of this
parameter is consistent with the setting on the Ethernet clock server.
The synchronization status message (SSM) carries clock quality information,
which is specified in ITU-T.
This parameter is valid only when the synchronous-Ethernet clock link is of the
input type.

Link Active State Indicates the activation status of a synchronous-Ethernet clock link. If the link is
active, the synchronous-Ethernet clock link is the current clock source of the
system.This parameter is valid only when the synchronous-Ethernet clock link is
of the input type.

Link Available State Indicates the availability of a synchronous-Ethernet clock link. Only an
available clock link can serve as the current clock source. Otherwise, the clock
link cannot be locked even if it is activated.This parameter is valid only when
the synchronous-Ethernet clock link is of the input type.

Priority Indicates the priority of the clock source. The value 1 indicates that the current
clock source has the highest priority, and the value 4 indicates that the current
clock source has the lowest priority.

SyncEth Type Indicates the type of a synchronous-Ethernet clock link. It indicates whether the
corresponding synchronous-Ethernet port is an input or output port. An input
port is used to import clock signals to the BS, and an output port is used to
export clock signals to other BSs. Only the synchronous-Ethernet clock of input
type can serve as a clock source.

5.7.1.6.2.74 TASM
EQUIPMENT
+-TASM

Description

The Tasm MO is the system clock. It is created by the system automatically and can be changed
to another reference clock source according to the priority and availability.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
EQUIPMENT

Relation with the BITS MO:


- If MODE and CLKSRC in the TASM MO are set to MANUAL and BITS, respectively, the
corresponding BITS MO must have been configured.
Relation with the GPS MO:
- If MODE and CLKSRC in the TASM MO are set to MANUAL and GPS, respectively, the
corresponding GPS MO must have been configured.
Relation with the GPS,SYNCETH MOs:
- If MODE and CLKSRC in the TASM MO are set to MANUAL and GPS+SYNCETH,
respectively, the corresponding GPS and SYNCETH MOs must have been configured.
Relation with the IPCLKLNK MO:
- If MODE and CLKSRC in the TASM MO are set to MANUAL and IPCLK, respectively,
the corresponding IPCLKLNK MO must have been configured.
Relation with the LINECLK MO:
- If MODE and CLKSRC in the TASM MO are set to MANUAL and LINECLK,
respectively, the corresponding LINECLK MO must have been configured.
Relation with the PEERCLK MO:
- If MODE and CLKSRC in the TASM MO are set to MANUAL and PEERCLK,
respectively, the corresponding PEERCLK MO must have been configured.
Relation with the SYNCETH MO:
- If MODE and CLKSRC in the TASM MO are set to MANUAL and SYNCETH,
respectively, the corresponding SYNCETH MO must have been configured.
Relation with the SYNCETH,IPCLKLNK MOs:
- If MODE and CLKSRC in the TASM MO are set to MANUAL and SYNCETH+IPCLK,
respectively, the corresponding SYNCETH and IPCLKLNK MOs must have been configured.
Relation with the TOD MO:
- If MODE and CLKSRC in the TASM MO are set to MANUAL and TOD, respectively, the
corresponding TOD MO must have been configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP AISSSTAT Use this command to query the status of soft synchronization over the Um
interface.

DSP CLKDA Use this command to query the initial DA value, center DA value, and current
DA value of a clock.

DSP Use this command to query the major standard for clock mutual lock on an
CLKMUTUALLOCK
MBTS. The clock on the side of the major standard is used as the criterion clock.

DSP CLKRECORD Use this command to display the records of clock status. The main control board
stores the latest 100 records. The board records the clock status when users
change the clock source, current DA value, clock working mode, or center DA
value or when the system automatically calibrates the clock that operates for a
long time.

DSP CLKSRC Use this command to query the status of all configured clock sources. The status
of each clock source depends on the availability of its associated clock link.

DSP CLKSTAT Use this command to query the status of the system clock.

DSP CLKTHD Use this command to query the clock tracing mode of a specified main control
board.

DSP CLKTST Use this command to display the clock quality test monitoring result. The result
shows the frequency or phase offset of the current clock source. The offset
indicates the quality of the clock.

DSP DARECORD Use this command to display the records of center DA values. The main control
board stores the latest 100 records. The board records the center DA value each
time the value is changed by users or the system. The system changes the center
DA to the current DA when the external reference clock source is in the locked
state for 96 hours.
Table 1 Related MML commands

MML Command Function

DSP FREQDIFFRSLT Use this command to query the result of a reference clock excessive frequency
deviation check.

DSP PHASEDIFF Use this command to query the phase offset between the IEEE 1588 V2 and
GPS reference clocks when both IEEE 1588 V2 and GPS clock links are
configured in the BS.

DSP TSTCLKOUT Using this command to display clock output type.

LST AISS Use this command to list the Um Interface Soft Synchronization Parameters.

LST Use this command to list the configuration of an IP clock.


CLKDATARECORD

LST CLKMODE Use this command to list the clock source in use and the working mode of the
clock.

LST CLKSYNCMODE Use this command to query the clock synchronization mode of a BS.

LST IPCLKALGO Use this command to query the clock algorithm mode for the IP clock link.

LST LOCALCLKQL Use this command to query the clock quality level of a BS.

MOD CENTERDA Use this command to change the center DA value of a BS.

MOD CURRDA Use this command to change the current DA value of the base station. When the
clock of the base station works in free-running mode, the current DA value
changes with the center DA value. When an external reference clock is
available, the current DA value changes with the frequency of the reference
clock, that is, the current DA value is adjusted on the basis of the frequency
deviation during software phase-locking. If the reference clock is locked for 96
hours, it is an indication that the reference is stable. In this case, the average of
current DA values in this period is used as the center DA value. Each time the
base station or the main control board is reset, the current DA value is
automatically overwritten by the center DA value.

SET AISS Use this command to set parameters related to Um interface soft
synchronization.

SET CLKMODE Use this command to set the working mode of the reference clock source.

SET Use this command to set the major standard for clock mutual lock on an MBTS.
CLKMUTUALLOCK
The clock on the side of the major standard is used as the criterion clock.
Table 1 Related MML commands

MML Command Function

SET CLKSYNCMODE Use this command to set the clock synchronization mode of a BS.

SET CLKTHD Use this command to set the clock tracing mode of a specified main control
board.

SET IPCLKALGO Using this command to set the clock algorithm mode for the IP clock link.

SET LOCALCLKQL Use this command to set the clock quality level of a BS.

SET TSTCLKOUT Using this command to set clock output type.

STP CLKTST Use this command to stop the clock quality test monitoring.

STR CLKTST Use this command to start a clock quality test monitoring. The test time,
frequency offset, and phase offset are saved as test records. A maximum of 100
test records can be saved. If there are more than 100 test records, the historical
records will be overwritten.

STR FREQDIFFCHK Use this command to check the cause of an excessive frequency deviation when
ALM-26262 External Clock Reference Problem is reported and the alarm cause
is Excessive Frequency Difference Between Clock Reference and Local Crystal
Oscillator.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Clock Source No. Indicates the clock link number of the reference clock source. When the Selected
Clock Source parameter is set to GPS+SYNCETH, this parameter indicates the
number of the GPS clock link. When the Selected Clock Source parameter is set
to SYNCETH+IPCLK, this parameter indicates the number of the IP clock link.
When this parameter is set to AUTO, the system selects an available clock link
from those of the specified reference clock source. If there is more than one
clock link and the selected clock link fails, another available clock link will be
used.

Selected Clock Source Indicates the type of the user-selected clock source. The UMTS currently does
Table 2 Related parameters

Parameter Description

not support "SyncEth Clock+IP Clock" and "GPS Clock+SyncEth Clock"


function.

Clock Working Mode Indicates the working mode of the system clock. Manual indicates that a clock
source must be specified by the user. Auto indicates that the system
automatically selects a clock source based on the priority and availability of the
clock source. Free indicates that the system clock works in free-running mode,
that is, the system clock does not trace any reference clock source.

Algorithm Indicates the clock algorithm mode for the IP clock link. In DEFAULT mode
that is also called the adaptive mode, and the system adjusts the filtering period
and sampling period based on the network quality in this mode. In CLASSA
mode, the Free Count, Search Count, Hold Count, Lock Count, and Sample
Time parameters are set to 4, 4, 4, 10, and 2400, respectively. In CLASSB mode,
the Free Count, Search Count, Hold Count, Lock Count, and Sample Time
parameters are set to 4, 4, 4, 10, and 4800, respectively. In CUSTOM mode, the
filtering period and sampling period are set by the customer. The LTE currently
does not support this function.

Free Count Indicates the filtering period of the IP clock link when the IP clock works in
free-running mode. The LTE currently does not support this function.

Search Count Indicates the filtering period of the IP clock link when the IP clock works in fast-
tracking mode. The LTE currently does not support this function.

Hold Count Indicates the filtering period of the IP clock link when the IP clock works in hold
mode. The LTE currently does not support this function.

Lock Count Indicates the filtering period of the IP clock link when the IP clock works in
locked mode. The LTE currently does not support this function.

Sample Time Indicates the sampling period of the IP clock link. The LTE currently does not
support this function.

IP Clock Time Indicates the mode of scheduled synchronization for the IP clock link. In
Synchronization Mode
ABSOLUTE mode, the system clock obtains synchronization signals from the
clock server at a fixed time every few days until the system clock is stable. In
RELATIVE mode, the system clock obtains synchronization signals from the
clock server at regular intervals until the system clock is stable. In OFF mode,
the system clock obtains only messages from the clock server in real time. The
LTE currently does not support this function.

Synchronization Period Indicates the synchronization period of the IP clock link. The LTE currently does
not support this function.
Table 2 Related parameters

Parameter Description

Synchronization Time Indicates the start time of scheduled synchronization for the IP clock link. The
LTE currently does not support this function.

Clock Synchronization Indicates the clock synchronization mode of a BS, which can be frequency
Mode
synchronization or time synchronization.

Current Clock Source Indicates the status of the current clock source, which can be Normal, Lost,
State
Unavailable, Jitter, Unknown, Frequency Deviation, Phaseoutscope, or
Inconsistent Clock References.

PLL Status Indicates the working mode of the clock. It also indicates whether the system
clock is stable. The working mode of the clock can be Fast tracking, Locked,
Holdover, or Free running.

Current Clock Source Indicates the clock source in use.

Cabinet No. Indicates the number of the cabinet where the system clock is located.

Subrack No. Indicates the number of the subrack where the system clock is located.

Slot No. Indicates the number of the slot where the system clock is located.

Quality Level Indicates the clock quality level of the BS. The values for this parameter are
listed in quality descending order. QL-PRC indicates the highest quality level
and QL-DNU indicates the lowest quality level.

Um Interface Soft Indicates the status of soft synchronization over the Um interface, including
Synchronization Status
Phase Lock Not Started, Phase Lock Succeeded, Phase Lock Tracking, and
Phase Lock Failed. Only GSM currently support this function.

Um Soft Syn Phase Indicates the adjustment period of the frame clock phase when the Um interface
Adjustment Period
soft synchronization function is enabled on the base station. Only GSM
currently support this function.

Soft-synchronized Indicates the adaptive mode of the soft synchronous transport network. The
Network Adaptive Mode
value of this parameter depends on the synchronous status of the transport
network. Only GSM currently support this function.

Um Interface Soft Indicates whether the Um interface Soft synchronization function is enabled on
Synchronization Switch
the base station. Only GSM currently support this function.

Day Indicates the number of timing synchronization days of the IP clock. The LTE
currently does not support this function.
Table 2 Related parameters

Parameter Description

GSM Frame Bit Offset Indicates GSM frame bit offset. This parameter applies to GSM only and is valid
in time synchronization mode only.

5.7.1.6.2.75 TCU
EQUIPMENT
+-CABINET
+-SUBRACK
+-TCU
+-ALMPORT[0~32]
+-HTCDPA[1~1]

Description

The TCU MO is the temperature control unit, which is used to monitor and adjust the
temperature in the cabinet.

Effective Scenario

Immediately

Relations Between MOs

Base class:
RU

Possible parents:
SUBRACK

Possible children:
ALMPORT[0~32];HTCDPA[1~1]

Relation with the SUBRACK,CTRLLNK MOs:


- If the MO corresponding to MCN and MSRN in the TCU MO is a SUBRACK MO with
SRN of 0 or 1, the SUBRACK MO cannot be a secondary subrack.
Relation with the SUBRACK MO:
- The number of TCU MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 4.
Relation with the TCU, PMU, EMU,and FMUMOs:
- It is not allowed in the following cases: 1. The combination of MCN, MSRN, MPN, and
ADDR in the TCU MO is same as the combination of those in other TCU MOs; 2. The
combination of MCN, MSRN, MPN, and ADDR in the TCU MO is same as the combination of
those in the PMU MOs; 3. The combination of MCN, MSRN, MPN, and ADDR in the TCU
MO is same as the combination of those in the EMU MOs; 4. The combination of MCN,
MSRN, MPN, and ADDR in the TCU MO is same as the combination of those in the FMU
MOs; 5. The combination of MCN, MSRN, and MPN in the TCU MO is same as the
combination of those in the CCU MOs, and ADDR in the TCU MO is equal to 21.
Relation with the SUBRACK,RRU,CCU MOs:
- The MO corresponding to MCN and MSRN in the TCU MO must have been configured and
be one of the following types: 1. A SUBRACK MO with SRN set to 0 or 1; 2. A RRU MO; 3. A
CCU MO.
Relation with the ALMPORT MO:
- When TYPE in the CABINET MO that houses the TCU MO is set to OMB, the TCU MO
will not be configured with an ALMPORT MO.
- The number of ALMPORT MOs configured on one TCU MO must be greater than or equal
to 0 and smaller than or equal to 32.
Relation with the HTCDPA MO:
- When a TCU MO is configured, a HTCDPA MO must also be configured. CN, SRN, and
SN in the TCU MO must be the same as CN, SRN, and SN respectively in the HTCDPA MO.
- The number of HTCDPA MOs configured on one TCU MO must be 1.
Relation with the subrack that houses the TCU MO:
- A TCU MO and its housing subrack must be configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD TCU Use this command to add a temperature control unit (TCU). When the TCU is
added, a TCU subrack, a TCU board, and the HtCDPa are added at the same
time.

CLR TCUALM Use this command to clear a temperature control unit (TCU) smoke alarm.
Table 1 Related MML commands

MML Command Function

When a TCU smoke alarm is reported, you must clear the fault that triggers the
alarm, and then run this command to clear the alarm.

DSP TCU Use this command to query the dynamic information about a temperature
control unit (TCU).

LST TCU Use this command to list the configuration of a temperature control unit (TCU).

MOD TCU Use this command to modify the configuration of a temperature control unit
(TCU).

RMV TCU Use this command to remove a temperature control unit (TCU). When the TCU
is removed, a TCU subrack and a TCU board are removed at the same time.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet where the TCU is located.

Subrack No. Indicates the number of the subrack where the TCU is located.

Slot No. Indicates the number of the slot where the TCU is located.

Manager Cabinet No. Indicates the cabinet number of the manager. The manager of the TCU is usually
a BBU, RRU or CCU.

Manager Subrack No. Indicates the subrack number of the manager. The manager of the TCU is
usually a BBU, RRU or CCU.

Manager Port No. Indicates the number of the serial port where the TCU is connected. The serial
port is the port through which the TCU is connected to the manager unit.

Address Indicates the communication address of the TCU. The TCU communicates with
the main control and transmission board by using this communication address.

Temperature Alarm Indicates the lower threshold of the temperature. If the cabinet air outlet
Table 2 Related parameters

Parameter Description

Lower Threshold temperature is lower than the value, the ALM-25655 Cabinet Air Outlet
Temperature Unacceptable is reported.

Temperature Alarm Indicates the upper threshold of the temperature. If the cabinet air outlet
Upper Threshold
temperature is higher than the value, the ALM-25655 Cabinet Air Outlet
Temperature Unacceptable is reported.

Special Boolean Alarm Indicates whether to allow the report of a dedicated Boolean alarm. If the shield
Flag
flag for a Boolean alarm is enabled, the Boolean alarm cannot be reported.

Device Type Indicates the device type of the TCU.

Temperature In Indicates the temperature at the air inlet of the TCU.Value NULL indicates that
this parameter is not supported by the hardware or the hardware is faulty.

Temperature Out Indicates the temperature at the air outlet of the TCU.

Temperature Inner Indicates the temperature inside the TCU.Value NULL indicates that this
parameter is not supported by the hardware or the hardware is faulty.

Inner Cycle Fan Indicates the average rotation speed of the inner circulation fan per minute.
Average Speed

Outer Cycle Fan Indicates the average rotation speed of the outer circulation fan per minute.
Average Speed

Power Indicates the current heating power of the TCU. If this parameter is displayed as
0, the TCU is not heating the cabinet. If this parameter is not displayed as 0, the
TCU is heating the cabinet. If this parameter is displayed as NULL, the TCU
used for heating does not exist or is not supported.

Software Version Indicates the software version of the TCU.

PCB Version Indicates the PCB version of the TCU.

EPLD Version Indicates the erasable programmable logic device (EPLD) version of the TCU.

Software Build Time Indicates the compiling time of the software program in the TCU.

Version Description Indicates the version description of the TCU.

Manufacturer Indicates the manufacturer of the TCU.

Temperature Control Indicates the mode that the fan speed adjustment adopts. Mode 0 is the default
Mode
mode, which achieves balance in system power consumption, noise, and
Table 2 Related parameters

Parameter Description

temperature control. It applies to most scenarios. Inappropriate configuration of


this parameter may lead to serious results such as high noise or service
interruption on the RF modules due to overtemperature. You need to contact
Huawei technical support before configuring this parameter. You can run the
DSP TCMODE command to list the number and description of the temperature
control modes supported by the base station. After configuring this parameter,
you can run the DSP TCU command to query whether the temperature control
mode in the command output is consistent with the configuration. If yes, the
configuration is successful. If no, the configuration fails and the system adopts
the default mode (mode 0). The reasons for the configuration failure and
countermeasures are as follows:
1. The TCU version does not support the temperature control mode
configuration.
2. The curve corresponding to the configured temperature control mode is
incorrect and the configuration cannot take effect on the TCU. You need to
contact the Huawei technical support.

Alarm Status(from RU) Indicates the alarm status of the board. The alarm state of the board can be
normal, warning, minor or critical. For details about the definition of Alarm
Status, see ITU-T X.731.

Operational State(from Indicates the operational state of the board, which can be set to Enabled or
RU)
Disabled. Enabled indicates that services can be carried on the board. Disabled
indicates that no service can be carried on the board.

Availability Status(from Indicates the physical operation status of the board, which can be Uninstalled,
RU)
Starting up, Normal, Inconsistent, Unconfigured, Power off, Fault,
Communication lost, In test, or the combination of various states. For example,
if a board is not configured and fails to communicate with the main control and
transmission board, the physical operation status of the board is Unconfigured,
Communication lost.

Electronic Label(from Indicates the E-label, a text file with a maximum of 2 KB. It is used to record the
RU)
manufacturing information about equipment such as the board, sub-board, or
optical module. Among board properties displayed in the text file, "BoardType"
indicates the type of the board, "BarCode" indicates the bar code of the board
and is the same as the code labeled on the board, and "Item" indicates the BOM
code.

Type(from RU) Indicates the type of the board.

Serial Number(from Indicates the bar code of the board or the cabinet.
RU)
Table 2 Related parameters

Parameter Description

Description(from RU) Indicates the description about the services and functions provided by the board
or the cabinet.

Date of Indicates the manufacturing date of the board or the cabinet.


Manufacture(from RU)

Vendor(from RU) Indicates the manufacturer of the board or the cabinet.

Issue Number(from RU) Indicates the issue number of the board.

Config Type(from RU) Indicates the type of a board.

Board Indicates the temperature of a board.


Temperature(from RU)

HPA Temperature(from Indicates the temperature of the power amplifier.


RU)

DEVTYPE(from RU) Indicates the type of the device.

Software Version(from Indicates the software version of the board.


RU)

Hardware Version(from Indicates the hardware version of the board.


RU)

BootRom Version(from Indicates the BootROM version of the board.


RU)

5.7.1.6.2.76 TIMESRC
EQUIPMENT
+-TIMESRC

Description

The TimeSrc MO is used to manage the external clock sources for the time synchronization of
the NE.

Effective Scenario

Not involved
Relations Between MOs

Possible parents:
EQUIPMENT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP TIMESRC Use this command to query the type of available time source.

LST Use this command to query the last update time from an external reference time
LATESTSUCCDATE
source.

LST TIMESRC Use this command to list the type of the configured time sources.

SET TIMESRC Use this command to set the time source.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Time Source Indicates the external reference time source of the NE.

Latest Successful Indicates the date and time of the last successfully-synchronized time of the NE.
Synchronization Time
The format is as follows: YYYY-MM-DD HH:MM:SS.

5.7.1.6.2.77 TMA
EQUIPMENT
+-TMA
+-TMASUBUNIT[1~2]
Description

A TMA MO is a managed object of a tower mounted amplifier (TMA), which is a low noise
amplifier installed close to the antenna. It can improve the Signal-to-Noise Ratio and system
sensitivity.

Effective Scenario

Immediately

Relations Between MOs

Base class:
ALD

Possible parents:
EQUIPMENT

Possible children:
TMASUBUNIT[1~2]

Relation with the TMASUBUNIT MO:


- The number of TMASUBUNIT MOs configured on one TMA MO must be greater than or
equal to 1 and smaller than or equal to 2.
Relation with the RRU,RFU MOs:
- The RRU or RFU MO corresponding to CTRLCN, CTRLSRN, and CTRLSN in the TMA
MO must have been configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD TMA Use this command to add a tower mounted amplifier (TMA). The subunits and
device data are added at the same time.

DSP TMA Use this command to query the dynamic information about one or all tower
mounted amplifiers (TMAs).

LST TMA Use this command to list the configuration of one or all tower mounted
amplifiers (TMAs).
Table 1 Related MML commands

MML Command Function

MOD TMA Use this command to modify the configuration of a tower mounted amplifier
(TMA).

RMV TMA Use this command to remove a tower mounted amplifier (TMA). The contained
subunits and device data are removed at the same time.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

TMA Subunit Number Indicates the number of configured TMA subunits.

Device No.(from ALD) Indicates the device number of the ALD. The device number of the ALD must
be unique.

Actual Vendor Indicates the vendor code of the device in the scanning result.
Code(from ALD)

Actual Device Serial Indicates the serial number of the device in the scanning result.
No.(from ALD)

Device Name(from Indicates the device name of the ALD, which identifies the ALD. It is
ALD)
recommended that you set the device name in the following format:
sector_device type_network type. The meanings of the parts are as follows:
Sector: indicates the number of the sector. Device type: indicates the type of
currently connected device. It can be SINGLE_RET (Single-antenna Remote
Electrical Tilt Unit), MULTI_RET (Multi-antenna Remote Electrical Tilt Unit),
TMA (Tower-mounted Amplifier). Network type: indicates whether the current
ALD is used for a 2G network or 3G/LTE network. The device name is optional,
but the device name configured for each ALD must be unique.

Control Port Cabinet Indicates the cabinet number of the RRU or RFU that controls the ALD.
No.(from ALD)

Control Port Subrack Indicates the subrack number of the RRU or RFU that controls the ALD.
No.(from ALD)

Control Port Slot No. Indicates the slot number of the RRU or RFU that controls the ALD.
(from ALD)

Protocol Version(from Indicates the actual protocol version of the ALD. NULL means that the protocol
Table 2 Related parameters

Parameter Description

ALD) version information fails to be obtained.

Actual Subunit Indicates the total number of ALD subunits.


Number(from ALD)

Vendor Code(from ALD) Indicates the vendor code.

Serial No.(from ALD) Indicates the serial number of the ALD. The vendor code and the serial number
uniquely identify an ALD.

Hardware Version(from Indicates the version information about the ALD hardware.
ALD)

Software Version(from Indicates the version information about the ALD software.
ALD)

Device Model(from Indicates the device model of the ALD.


ALD)

Device Type(from ALD) Indicates the device type of the ALD.

Control Port No.(from Indicates the port number of the RRU or RFU that controls the ALD. It will be
ALD)
NULL if the RRU or RFU does not support to report this parameter.

5.7.1.6.2.78 TMADEVICEDATA
EQUIPMENT
+-TMA
+-TMASUBUNIT
+-TMADEVICEDATA

Description

The TMADeviceData MO refers to the configuration data of the TMA and the capability
supported by the TMA. For details, see 3GPP TS25.466 and AISG2.0.

Effective Scenario

Immediately

Relations Between MOs


Possible parents:
TMASUBUNIT

Relation with the TMASUBUNIT MO:


- The number of TMADEVICEDATA MOs configured on one TMASUBUNIT MO must be
1.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP TMADEVICEDATA Use this command to query the dynamic information in the tower mounted
amplifier (TMA) device data.

LST TMADEVICEDATA Use this command to list the configuration in the tower mounted amplifier
(TMA) device data.

MOD Use this command to modify the tower mounted amplifier (TMA) device data.
TMADEVICEDATA

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Device No. Indicates the device number of the TMA.

Subunit No. Indicates the number of the TMA subunit, which starts from 1.

Antenna Bearing Indicates the antenna azimuth.

Base Station ID Indicates the base station ID. AISG1.1-based TMA support a maximum base
station ID length of 12 characters. If the input base station ID has more than 12
characters, only the first 12 characters are saved on the TMA.

Beamwidth1 Indicates the beamwidth of band 1. Beamwidth is used to describe the capability
of the antenna to transmit RF signals. It is also used to measure the antenna
pattern.
Table 2 Related parameters

Parameter Description

Beamwidth2 Indicates the beamwidth of band 2. Beamwidth is used to describe the capability
of the antenna to transmit RF signals. It is also used to measure the antenna
pattern.

Beamwidth3 Indicates the beamwidth of band 3. Beamwidth is used to describe the capability
of the antenna to transmit RF signals. It is also used to measure the antenna
pattern.

Beamwidth4 Indicates the beamwidth of band 4. Beamwidth is used to describe the capability
of the antenna to transmit RF signals. It is also used to measure the antenna
pattern.

Gain1 Indicates the gain of band 1.

Gain2 Indicates the gain of band 2.

Gain3 Indicates the gain of band 3.

Gain4 Indicates the gain of band 4.

Installation Date Indicates the date when the antenna is installed.

Installed Mechanical Tilt Indicates the mechanical tilt of the installation.

Installer's ID Indicates the ID of the installation technician who installed the antenna.

Band1 Indicates band 1 supported by the antenna.

Band2 Indicates band 2 supported by the antenna.

Band3 Indicates band 3 supported by the antenna.

Band4 Indicates band 4 supported by the antenna.

Sector ID Indicates the sector ID. AISG1.1-based TMA support a maximum sector ID
length of 4 characters. If the input sector ID has more than 4 characters, only the
first 4 characters are saved on the TMA.

Serial No. Indicates the serial number of the ALD.

Connect Antenna Model Indicates the model of the RET antenna connected to the TMA.
Number

Max Supported Gain Indicates the maximum gain supported by the TMA.
Table 2 Related parameters

Parameter Description

Min Supported Gain Indicates the minimum gain supported by the TMA.

Real Subunit Type Indicates the type of TMA subunit. It indicates whether the voltage standing
wave ratio (VSWR) measurement and the bypass mode are supported.

Real Gain Resolution Indicates the step for the TMA gain change.

Band1 Indicates band 1 supported by the antenna.

Band2 Indicates band 2 supported by the antenna.

Band3 Indicates band 3 supported by the antenna.

Band4 Indicates band 4 supported by the antenna.

Beamwidth1 Indicates the beamwidth of band 1. Beamwidth describes the capability of an


antenna to transmit RF signals. It also defines the width of the antenna pattern.

Beamwidth2 Indicates the beamwidth of band 2. Beamwidth describes the capability of an


antenna to transmit RF signals. It also defines the width of the antenna pattern.

Beamwidth3 Indicates the beamwidth of band 3. Beamwidth describes the capability of an


antenna to transmit RF signals. It also defines the width of the antenna pattern.

Beamwidth4 Indicates the beamwidth of band 4. Beamwidth describes the capability of an


antenna to transmit RF signals. It also defines the width of the antenna pattern.

Gain1 Indicates the gain of band 1.

Gain2 Indicates the gain of band 2.

Gain3 Indicates the gain of band 3.

Gain4 Indicates the gain of band 4.

Real Received Min Indicates the minimum RX frequency band supported by the TMA.
Frequency Band

Real Transmit Max Indicates the maximum TX frequency band supported by the TMA.
Frequency Band

Real Transmit Min Indicates the minimum TX frequency band supported by the TMA.
Frequency Band

Real Received Max Indicates the maximum RX frequency band supported by the TMA.
Frequency Band
5.7.1.6.2.79 TMASUBUNIT
EQUIPMENT
+-TMA
+-TMASUBUNIT
+-TMADEVICEDATA[1~1]

Description

The TMASubunit MO is the managed object of a TMA subunit, which amplifies one-channel UL
RF signals.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
TMA

Possible children:
TMADEVICEDATA[1~1]

Relation with the TMA MO:


- The number of TMASUBUNIT MOs configured on one TMA MO must be greater than or
equal to 1 and smaller than or equal to 2.
Relation with the TMADEVICEDATA MO:
- The number of TMADEVICEDATA MOs configured on one TMASUBUNIT MO must be
1.
Relation with the TMASUBUNIT MO:
- The ANTENNAPORT MO corresponding to CONNCN, CONNSRN, CONNSN, and
CONNPN in the TMASUBUNIT MO must have been configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

DSP TMASUBUNIT Use this command to query the dynamic information about one or all tower
mounted amplifier (TMA) subunits.

LST TMASUBUNIT Use this command to list the configuration of one or all tower mounted amplifier
(TMA) subunits.

MOD TMASUBUNIT Use this command to modify a tower mounted amplifier (TMA) subunit.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Device No. Indicates the device number of the TMA.

Subunit No. Indicates the number of the TMA subunit, which starts from 1.

Actual Sector ID Indicates the sector ID of the TMA subunit.

Actual Gain Indicates the actual gain of the TMA subunit.

Actual Work Mode Indicates the actual working mode of the TMA subunit.

Online Status Indicates the online status of the TMA subunit.

Connect Port No. Indicates the number of the antenna port to which the TMA subunit is
connected.

Connect Port Cabinet Indicates the cabinet number of the RRU or RFU that provides the antenna port
No.
to which the TMA subunit is connected.

Connect Port Slot No. Indicates the slot number of the RRU or RFU that provides the antenna port to
which the TMA subunit is connected.

Connect Port Subrack Indicates the subrack number of the RRU or RFU that provides the antenna port
No.
to which the TMA subunit is connected.

Gain Indicates the gain of the TMA subunit. If this parameter is set to 255, it is invalid
Table 2 Related parameters

Parameter Description

and the actual gain is not changed.

Work Mode Indicates the working mode of the TMA subunit. If the TMA subunit works in
BYPASS mode, it does not amplify the uplink signals. If this parameter is set to
DEVICE_DEFAULT_VALUE, it is invalid and the actual mode is not changed.

5.7.1.6.2.80 TOD
EQUIPMENT
+-TOD

Description

Time of day (TOD) is a type of reference clock. The TOD clock can be configured only on the
USCUb. The clock can be set to the input or output mode.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
EQUIPMENT

Relation with the TASM MO:


- If MODE and CLKSRC in the TASM MO are set to MANUAL and TOD, respectively, the
corresponding TOD MO must have been configured.
Relation with the BITS MO:
- A unique combination is necessary for the following parameters: 1. CN, SRN, and SN in the
BITS MO. 2. CN, SRN, and SN in the TOD MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD TOD Use this command to add a Time of Date (TOD) clock link. If the BS can
properly obtain the TOD synchronization signals, this link becomes available.

DSP TOD Use this command to query the running status of a specified Time of Date
(TOD) clock link.

LST TOD Use this command to list the configuration of all Time of Date (TOD) clock
links.

MOD TOD Use this command to modify the feeder type, feeder length, and priority of a
specified Time of Date (TOD) clock link.

RMV TOD Use this command to remove a specified Time of Date (TOD) clock link.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

TOD Clock No. Indicates the number of a TOD clock link. The number of the TOD clock link
must correspond to the number of the TOD port on the USCUb. For example,
clock link No.0 corresponds to port No.0, clock link No.1 corresponds to port
No.1.

TOD Type Indicates the type of a TOD clock link. It indicates whether the corresponding
TOD port is an input or output port. An input port is used to input clock signals
to the BS, and an output port is used to provide clock signals for other BSs. Only
the TOD clock of input type can serve as a clock source.

Cabinet No. Indicates the number of the cabinet where the TOD clock link is configured.

Subrack No. Indicates the number of the subrack where the TOD clock link is configured.

Slot No. Indicates the number of the slot where the TOD clock link is configured.

Cable Type Indicates the type of TOD feeder, which can only be the twisted-pair cable
currently.
Table 2 Related parameters

Parameter Description

Cable Length Indicates the length of the TOD feeder. The feeder delay is calculated on the
basis of the TOD feeder length to ensure the clock accuracy. The clock accuracy
is affected if there is an excessively large difference [about 20 m (66 ft)]
between the value of this parameter and the actual feeder length.

Link Active State Indicates the activation status of a TOD clock link. If the link is active, the TOD
clock link is the current clock source of the system.

Link Available State Indicates the availability of an TOD clock link. Only an available clock link can
serve as the current clock source. Otherwise, the clock link cannot be locked
even if it is activated.

Delay Indicates the feeder delay of the TOD clock link.

Priority Indicates the priority of the clock source. The value 1 indicates that the current
clock source has the highest priority, and the value 4 indicates that the current
clock source has the lowest priority.

5.7.1.6.2.81 TRP
EQUIPMENT
+-CABINET
+-SUBRACK
+-TRP

Description

The TRP MO provides more transmission ports and wider bandwidth for the system, enables
cascading between BSs, and supports the application of transport gateways.

Effective Scenario

Immediately

Relations Between MOs

Base class:
RU
Possible parents:
SUBRACK

Relation with other boards in the BBU subrack:


- A unique combination is necessary for the following parameters: 1. CN, SRN, and SN in the
BBP MO; 2. CN, SRN, and SN in the TRP MO;3. CN, SRN, and SN in the UCIU MO; 4. CN,
SRN, and SN in the USCU MO; 5. CN, SRN, and SN in the MPT MO; 6. CN, SRN, and SN in
the BRI MO;7. CN, SRN, and SN in the GTMU MO.
Relation with the SUBRACK,CTRLLNK MOs:
- If SUBTYPE in the TRP MO is set to UTRPc,the TRP MO must be configured in master
BBU subrack.
Relation with the TRP MO:
- Only one TRP MO with SUBTYPE set to UTRPc can be configured under a BBU subrack.
Relation with the SUBRACK MO:
- The number of TRP MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 7.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP BRDRAT Use this command to query the mode negotiation flag of the extension
transmission board.

LST UTRP Use this command to list the configuration of the universal transmission
processing unit (UTRP).

MOD UTRP Use this command to modify the subboard type of a universal transmission
processing unit (UTRP).

SET BRDRAT Use this command to set the mode negotiation of the extension transmission
board.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the extension transmission board.

Subrack No. Indicates the subrack number of the extension transmission board.

Slot No. Indicates the slot number of the extension transmission board.

SubBoard Type Indicates the type of the sub-board.

Alarm Status(from RU) Indicates the alarm status of the board. The alarm state of the board can be
normal, warning, minor or critical. For details about the definition of Alarm
Status, see ITU-T X.731.

Operational State(from Indicates the operational state of the board, which can be set to Enabled or
RU)
Disabled. Enabled indicates that services can be carried on the board. Disabled
indicates that no service can be carried on the board.

Availability Status(from Indicates the physical operation status of the board, which can be Uninstalled,
RU)
Starting up, Normal, Inconsistent, Unconfigured, Power off, Fault,
Communication lost, In test, or the combination of various states. For example,
if a board is not configured and fails to communicate with the main control and
transmission board, the physical operation status of the board is Unconfigured,
Communication lost.

Electronic Label(from Indicates the E-label, a text file with a maximum of 2 KB. It is used to record the
RU)
manufacturing information about equipment such as the board, sub-board, or
optical module. Among board properties displayed in the text file, "BoardType"
indicates the type of the board, "BarCode" indicates the bar code of the board
and is the same as the code labeled on the board, and "Item" indicates the BOM
code.

Type(from RU) Indicates the type of the board.

Serial Number(from Indicates the bar code of the board or the cabinet.
RU)

Description(from RU) Indicates the description about the services and functions provided by the board
or the cabinet.

Date of Indicates the manufacturing date of the board or the cabinet.


Manufacture(from RU)

Vendor(from RU) Indicates the manufacturer of the board or the cabinet.

Issue Number(from RU) Indicates the issue number of the board.


Table 2 Related parameters

Parameter Description

Config Type(from RU) Indicates the type of a board.

Board Indicates the temperature of a board.


Temperature(from RU)

HPA Temperature(from Indicates the temperature of the power amplifier.


RU)

DEVTYPE(from RU) Indicates the type of the device.

Software Version(from Indicates the software version of the board.


RU)

Hardware Version(from Indicates the hardware version of the board.


RU)

BootRom Version(from Indicates the BootROM version of the board.


RU)

5.7.1.6.2.82 TXBRANCH
EQUIPMENT
+-CABINET
+-SUBRACK
EQUIPMENT
+-RRU
+-TXBRANCH
EQUIPMENT
EQUIPMENT
+-CABINET
+-SUBRACK
+-RFU
+-TXBRANCH
EQUIPMENT
+-AAS
+-AARU
+-TXBRANCH

Description
The TxBranch MO manages the number, the logical switch of the TX channel, the VSWR, the
physical status, and the adjusted output power of the TX channel.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
RRU;RFU;AARU

Relation with the RFU MO:


- The number of TXBRANCH MOs configured on one RFU MO must be greater than or
equal to 0 and smaller than or equal to 8.
Relation with the RRU MO:
- The number of TXBRANCH MOs configured on one RRU MO must be greater than or
equal to 0 and smaller than or equal to 8.
Relation with the ANTENNAPORT MO:
- One ANTENNAPORT MO maps to one TXBRANCH MO and one RXBRANCH MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP TXBRANCH Use this command to query the dynamic attributes of the TX channel of the
RRU or RFU.

DSP VSWR Use this command to display the results of an automatic voltage standing wave
ratio (VSWR) test for the RRU or RFU transmit channel.

DSP VSWRTEST Use this command to query an ongoing VSWR test.

LOC RRUTC Use this command to set and lock the maximum TX power of a TX channel on
an RRU or RFU.

LST TXBRANCH Use this command to list the configuration of the TX channel.

MOD TXBRANCH Use this command to set a TxBranch MO of the RRU or RFU.
Table 1 Related MML commands

MML Command Function

STP VSWRTEST Use this command to stop a high-precision VSWR test.

STR CROSFEEDTST Use this command to detect a crossed feeder connection. Crossed feeder
connection is a wiring error in twisted pair cabling where both the main and
diversity in a sector are incorrectly connected to different antennas at both sides.

STR VSWRTEST Use this command to start the VSWR test on the TX channel to check whether
the antenna system is properly installed. If the numbers of the cabinet, subrack,
slot, and antenna port are not specified, the VSWR information of all the RRUs
or RFUs are queried in batch.

VER TXPOWER Use this command to tune the TX power of the RRU or RFU.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the RRU or RFU where the TX channel of the
RRU or RFU is located.

Subrack No. Indicates the subrack number of the RRU or RFU where the TX channel of the
RRU or RFU is located.

Slot No. Indicates the slot number of the RRU or RFU where the TX channel of the RRU
or RFU is located.

TX Channel No. Indicates the number of the TX channel of the RRU or RFU.0 corresponds to
R0A, 1 corresponds to R0B, and the rest can be deduced by analogy.

Logical Switch of TX Indicates the logical switch of the TX channel of the RRU or RFU. This switch
Channel
is used to open or close the TX channel. The logical switch of the TX channel
and the ARFCNs(absolute radio frequency channel numbers) on the TX channel
determine the state of the physical switch of the TX channel: When this switch is
ON and the TX channel is configured with ARFCNs(absolute radio frequency
channel numbers), the physical switch is ON. In other cases, the physical switch
is OFF.
Table 2 Related parameters

Parameter Description

VSWR Indicates the current VSWR of the TX channel. When the TX power is relatively
low , the S/N of the reflected signal passing through the detector channel is
relatively low, which leads to the inaccuracy of the VSWR calculation, the value
of this field will be displayed as NULL.

Physical Switch of TX Indicates the actual physical status of the TX channel of the RRU or RFU. The
Channel
logical switch of the TX channel and the ARFCN on the TX channel determine
the state of the physical switch of the TX channel: If the logical switch of a TX
channel is ON and the ARFCN is configured for the TX channel, the physical
switch of the TX channel is ON. In other cases, the physical switch is OFF.

Maximum Output Indicates the maximum output power supported by the TX channel hardware
Power of the TX
Channel after the maximum output power locking is enabled for this TX channel. When
the maximum output power locking is disabled for this TX channel, the value of
this parameter is the same as that of the Hardware Maximum Output Power of
the TX Channel parameter. This parameter value can be 0.5 dB higher or lower
than the actual maximum output power.

Maximum Output Indicates the maximum output power of the RRU or RFU TX unit (single
Power of TX Unit
(Single Carrier) carrier).

Maximum Output Indicates the maximum output power of the RRU or RFU TX unit (multiple
Power of TX Unit
(Multiple Carriers) carriers).

Hardware Maximum Indicates the maximum output power supported by the TX channel hardware.
Output Power of the TX
Channel This parameter value can have a 0.5 dB difference from the actual maximum
output power.

Band 1 Minimum Indicates the minimum downlink frequency supported by the RRU or RFU band
frequency
1. For example, this parameter is set to 9650, the minimum downlink frequency
of the RRU or RFU is 9650 x 0.1 MHz, which equals to 965 MHz.

Band 1 Maximum Indicates the maximum downlink frequency supported by the RRU or RFU band
frequency
1. For example, if this parameter is set to 9850, the maximum downlink
frequency of the RRU is 9850 x 0.1 MHz, which equals to 985 MHz.

Band 1 DL Bandwidth Indicates the bandwidth supported by each TX channel band 1 in the downlink.
This bandwidth is an instantaneous bandwidth.

Band 2 Minimum Indicates the minimum downlink frequency supported by the RRU or RFU band
frequency
2. This parameter is NULL,when the RRU or RFU does not supported many
bands.For example, this parameter is set to 9650, the minimum downlink
frequency of the RRU is 9650 x 0.1 MHz, which equals to 965 MHz.
Table 2 Related parameters

Parameter Description

Band 2 Maximum Indicates the maximum downlink frequency supported by the RRU or RFU band
frequency
2. This parameter is NULL,when the RRU or RFU does not supported many
bands.For example, if this parameter is set to 9850, the maximum downlink
frequency of the RRU is 9850 x 0.1 MHz, which equals to 985 MHz.

Band 2 DL Bandwidth Indicates the bandwidth supported by each TX channel band 2 in the downlink.
This bandwidth is an instantaneous bandwidth. This parameter is NULL, when
the RRU or RFU does not supported multi-bands.

5.7.1.6.2.83 TZ
EQUIPMENT
+-TZ

Description

The TZ MO indicates the time zone and daylight saving time of an NE. The time zone of the NE
may vary with different countries and districts. The time zone is divided into the east time zone
and the west time zone. The start time and the end time of the daylight saving time are also
different in different countries and districts. The daylight saving time has an offset with the
standard time to satisfy the living habit of people.

Effective Scenario

Not involved

Relations Between MOs

Possible parents:
EQUIPMENT

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

LST TZ Use this command to list the time zone and the daylight saving time (DST)
information about the NE.

SET TZ Use this command to set the time zone and the daylight saving time (DST)
information about the NE.
This command can also be used to set the time zone and DST information about
the southern hemisphere. That is, the start time can be later than the end time.
The start time and the end time can be specified in different formats while
setting DST information.
The command can be used to self-define a time zone precise to the minute.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Time Zone Indicates the time zone of the NE.

DST Tag Information Indicates whether DST is enabled.

DST Start Mode Indicates the mode in which the DST start date is specified. There are three
formats:
date format, for example, April 1st;
week format, for example, the first Sunday in April;
date and week format, for example, April 1st and Sunday. If it is Sunday on
April 1st, April 1st is the date. Otherwise, the first Sunday after April 1st is the
date.

DST Start Month Indicates the month in which the NE DST starts.

DST Start Day Indicates the day on which the NE DST starts.

DST Start Week Indicates in which week the NE DST starts.


Sequence

DST Start Weekday Indicates the week in which the NE DST starts.

DST Start Time Indicates the time when the NE DST starts. The value of this parameter observes
Table 2 Related parameters

Parameter Description

the standard time.

DST End Mode Indicates the end date mode of the NE DST. There are three formats:
date format, for example, April 1st;
week format, for example, the first Sunday in April;
date and week format, for example, April 1st and Sunday. If it is Sunday on
April 1st, April 1st is the date. Otherwise, the first Sunday after April 1st is the
date.

DST End Month Indicates the month in which the NE DST ends.

DST End Day Indicates the day on which the NE DST ends.

DST End Week Indicates the week in which DST ends.


Sequence

DST End Weekday Indicates the week in which the NE DST ends.

DST End Time Indicates the time when the DST of the NE ends. The value of this parameter
observes DST.

DST Offset Indicates the DST time offset of the NE. This parameter can be set to a negative
value. A negative value indicates that the NE time is earlier than the DST time,
and a positive value indicates that the NE time is later than the DST time.

Time Difference Indicates the offset of time zone. This parameter can be set to a negative value.

5.7.1.6.2.84 UCIU
EQUIPMENT
+-CABINET
+-SUBRACK
+-UCIU
+-CPRIPORT[0~6]
+-SFP[6~6]
+-CASCADEPORT[6~6]

Description
The UCIU MO is a universal cascading interface unit, which connects two BBUs. It provides
channels for communication.

Effective Scenario

Immediately

Relations Between MOs

Base class:
RU

Possible parents:
SUBRACK

Possible children:
CPRIPORT[0~6];SFP[6~6];CASCADEPORT[6~6]

Relation with other boards in the BBU subrack:


- A unique combination is necessary for the following parameters: 1. CN, SRN, and SN in the
BBP MO; 2. CN, SRN, and SN in the TRP MO;3. CN, SRN, and SN in the UCIU MO; 4. CN,
SRN, and SN in the USCU MO; 5. CN, SRN, and SN in the MPT MO; 6. CN, SRN, and SN in
the BRI MO;7. CN, SRN, and SN in the GTMU MO.
Relation with the SUBRACK MO:
- The number of UCIU MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 8.
Relation with the CASCADEPORT MO:
- When the combination of CN, SRN and SN in the CASCADEPORT MO is same as the
combination of CN, SRN and SN in the UCIU MO, the PT of CASCADEPORT must be set to
BasicCascadePort.

Related Parameters

Table 1 describes the parameters related to this MO.

Table 1 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the UCIU.

Subrack No. Indicates the subrack number of the UCIU.

Slot No. Indicates the slot number of the UCIU.


Table 1 Related parameters

Parameter Description

Alarm Status(from RU) Indicates the alarm status of the board. The alarm state of the board can be
normal, warning, minor or critical. For details about the definition of Alarm
Status, see ITU-T X.731.

Operational State(from Indicates the operational state of the board, which can be set to Enabled or
RU)
Disabled. Enabled indicates that services can be carried on the board. Disabled
indicates that no service can be carried on the board.

Availability Status(from Indicates the physical operation status of the board, which can be Uninstalled,
RU)
Starting up, Normal, Inconsistent, Unconfigured, Power off, Fault,
Communication lost, In test, or the combination of various states. For example,
if a board is not configured and fails to communicate with the main control and
transmission board, the physical operation status of the board is Unconfigured,
Communication lost.

Electronic Label(from Indicates the E-label, a text file with a maximum of 2 KB. It is used to record the
RU)
manufacturing information about equipment such as the board, sub-board, or
optical module. Among board properties displayed in the text file, "BoardType"
indicates the type of the board, "BarCode" indicates the bar code of the board
and is the same as the code labeled on the board, and "Item" indicates the BOM
code.

Type(from RU) Indicates the type of the board.

Serial Number(from Indicates the bar code of the board or the cabinet.
RU)

Description(from RU) Indicates the description about the services and functions provided by the board
or the cabinet.

Date of Indicates the manufacturing date of the board or the cabinet.


Manufacture(from RU)

Vendor(from RU) Indicates the manufacturer of the board or the cabinet.

Issue Number(from RU) Indicates the issue number of the board.

Config Type(from RU) Indicates the type of a board.

Board Indicates the temperature of a board.


Temperature(from RU)

HPA Temperature(from Indicates the temperature of the power amplifier.


RU)
Table 1 Related parameters

Parameter Description

DEVTYPE(from RU) Indicates the type of the device.

Software Version(from Indicates the software version of the board.


RU)

Hardware Version(from Indicates the hardware version of the board.


RU)

BootRom Version(from Indicates the BootROM version of the board.


RU)

5.7.1.6.2.85 UEIU
EQUIPMENT
+-CABINET
+-SUBRACK
+-UEIU
+-ALMPORT[8~8]

Description

The UEIU MO is used to expand the environment monitoring capacity of the BBU. The MO
supports eight dry contacts.

Effective Scenario

Immediately

Relations Between MOs

Base class:
RU

Possible parents:
SUBRACK

Possible children:
ALMPORT[8~8]

Relation with the ALMPORT MO:


- The number of ALMPORT MOs configured on one UEIU MO must be 8.
Relation with the SUBRACK MO:
- The number of UEIU MOs configured on one SUBRACK MO must be greater than or equal
to 0 and smaller than or equal to 2.

Related Parameters

Table 1 describes the parameters related to this MO.

Table 1 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet where the UEIU is located.

Subrack No. Indicates the number of the subrack where the UEIU is located.

Slot No. Indicates the number of the slot where the UEIU is located.

Alarm Status(from RU) Indicates the alarm status of the board. The alarm state of the board can be
normal, warning, minor or critical. For details about the definition of Alarm
Status, see ITU-T X.731.

Operational State(from Indicates the operational state of the board, which can be set to Enabled or
RU)
Disabled. Enabled indicates that services can be carried on the board. Disabled
indicates that no service can be carried on the board.

Availability Status(from Indicates the physical operation status of the board, which can be Uninstalled,
RU)
Starting up, Normal, Inconsistent, Unconfigured, Power off, Fault,
Communication lost, In test, or the combination of various states. For example,
if a board is not configured and fails to communicate with the main control and
transmission board, the physical operation status of the board is Unconfigured,
Communication lost.

Electronic Label(from Indicates the E-label, a text file with a maximum of 2 KB. It is used to record the
RU)
manufacturing information about equipment such as the board, sub-board, or
optical module. Among board properties displayed in the text file, "BoardType"
indicates the type of the board, "BarCode" indicates the bar code of the board
and is the same as the code labeled on the board, and "Item" indicates the BOM
code.

Type(from RU) Indicates the type of the board.

Serial Number(from Indicates the bar code of the board or the cabinet.
RU)

Description(from RU) Indicates the description about the services and functions provided by the board
Table 1 Related parameters

Parameter Description

or the cabinet.

Date of Indicates the manufacturing date of the board or the cabinet.


Manufacture(from RU)

Vendor(from RU) Indicates the manufacturer of the board or the cabinet.

Issue Number(from RU) Indicates the issue number of the board.

Config Type(from RU) Indicates the type of a board.

Board Indicates the temperature of a board.


Temperature(from RU)

HPA Temperature(from Indicates the temperature of the power amplifier.


RU)

DEVTYPE(from RU) Indicates the type of the device.

Software Version(from Indicates the software version of the board.


RU)

Hardware Version(from Indicates the hardware version of the board.


RU)

BootRom Version(from Indicates the BootROM version of the board.


RU)

5.7.1.6.2.86 USCU
EQUIPMENT
+-CABINET
+-SUBRACK
+-USCU

Description

The USCU MO provides reference clock for the main control and transmission board and
supports the GPS, RGPS, TOD, and BITS clocks.

Effective Scenario

Immediately
Relations Between MOs

Base class:
RU

Possible parents:
SUBRACK

Relation with other boards in the BBU subrack:


- A unique combination is necessary for the following parameters: 1. CN, SRN, and SN in the
BBP MO; 2. CN, SRN, and SN in the TRP MO;3. CN, SRN, and SN in the UCIU MO; 4. CN,
SRN, and SN in the USCU MO; 5. CN, SRN, and SN in the BRI MO.
Relation with the SUBRACK MO:
- The number of USCU MOs configured on one SUBRACK MO must be greater than or
equal to 0 and smaller than or equal to 1.

Related Parameters

Table 1 describes the parameters related to this MO.

Table 1 Related parameters

Parameter Description

Cabinet No. Indicates the number of the cabinet where the USCU is located.

Subrack No. Indicates the number of the subrack where the USCU is located.

Slot No. Indicates the number of the slot where the USCU is located.

Alarm Status(from RU) Indicates the alarm status of the board. The alarm state of the board can be
normal, warning, minor or critical. For details about the definition of Alarm
Status, see ITU-T X.731.

Operational State(from Indicates the operational state of the board, which can be set to Enabled or
RU)
Disabled. Enabled indicates that services can be carried on the board. Disabled
indicates that no service can be carried on the board.

Availability Status(from Indicates the physical operation status of the board, which can be Uninstalled,
RU)
Starting up, Normal, Inconsistent, Unconfigured, Power off, Fault,
Communication lost, In test, or the combination of various states. For example,
if a board is not configured and fails to communicate with the main control and
transmission board, the physical operation status of the board is Unconfigured,
Communication lost.

Electronic Label(from Indicates the E-label, a text file with a maximum of 2 KB. It is used to record the
Table 1 Related parameters

Parameter Description

RU) manufacturing information about equipment such as the board, sub-board, or


optical module. Among board properties displayed in the text file, "BoardType"
indicates the type of the board, "BarCode" indicates the bar code of the board
and is the same as the code labeled on the board, and "Item" indicates the BOM
code.

Type(from RU) Indicates the type of the board.

Serial Number(from Indicates the bar code of the board or the cabinet.
RU)

Description(from RU) Indicates the description about the services and functions provided by the board
or the cabinet.

Date of Indicates the manufacturing date of the board or the cabinet.


Manufacture(from RU)

Vendor(from RU) Indicates the manufacturer of the board or the cabinet.

Issue Number(from RU) Indicates the issue number of the board.

Config Type(from RU) Indicates the type of a board.

Board Indicates the temperature of a board.


Temperature(from RU)

HPA Temperature(from Indicates the temperature of the power amplifier.


RU)

DEVTYPE(from RU) Indicates the type of the device.

Software Version(from Indicates the software version of the board.


RU)

Hardware Version(from Indicates the hardware version of the board.


RU)

BootRom Version(from Indicates the BootROM version of the board.


RU)

5.7.1.6.2.87 VANTENNAPORT
EQUIPMENT
+-AAS
+-AARU
+-VANTENNAPORT

Description

A VAntennaPort MO defines a virtual antenna port between the RF processing module and
virtual remote electrical tilt (VRET) antenna in an active antenna radio unit (AARU). This port
must be specified when a sector or cell is to be created.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
AARU

Relation with the AARU MO:


- The AARU MO corresponding to CONNCN, CONNSRN, and CONNSN in the
VANTENNAPORT MO must have been configured.
- The number of VANTENNAPORT MOs configured on one AARU MO must be 32.
Relation with the VANTENNAPORT MO:
- One of the following VANTENNAPORT MOs must have been configured: 1. A
VANTENNAPORT MO corresponding to CONNCN, CONNSRN, CONNSN, and CONNPN1
in the VRETSUBUNIT MO whose CONNPN1 is set to a value other than 255. 2. A
VANTENNAPORT MO corresponding to CONNCN, CONNSRN, CONNSN, and CONNPN2
in the VRETSUBUNIT MO when CONNPN2 in the VRETSUBUNIT MO is set to a value
other than 255. 3. A VANTENNAPORT MO corresponding to CONNCN, CONNSRN,
CONNSN, and CONNPN3 in the VRETSUBUNIT MO when CONNPN3 in the
VRETSUBUNIT MO is set to a value other than 255. 4. A VANTENNAPORT MO
corresponding to CONNCN, CONNSRN, CONNSN, and CONNPN4 in the VRETSUBUNIT
MO when CONNPN4 in the VRETSUBUNIT MO is set to a value other than 255.

Related Parameters

Table 1 describes the parameters related to this MO.

Table 1 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the AARU where the virtual antenna port is
located.
Table 1 Related parameters

Parameter Description

Subrack No. Indicates the subrack number of the AARU where the virtual antenna port is
located.

Slot No. Indicates the slot number of the AARU where the virtual antenna port is located.

Port No. Indicates the number of the virtual antenna port.

5.7.1.6.2.88 VRET
EQUIPMENT
+-AAS
+-AARU
+-VRET
+-VRETSUBUNIT[8~8]

Description

A VRET MO defines a virtual remote electrical tilting (VRET) antenna in an active antenna
radio unit (AARU). The tilt of the antenna can be adjusted through remote control.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
AARU

Possible children:
VRETSUBUNIT[8~8]

Relation with the VRETSUBUNIT MO:


- The number of VRETSUBUNIT MOs configured on one VRET MO must be 8.
- The VRET MO corresponding to DEVICENO, CONNCN, CONNSRN, and CONNSN in
the VRETSUBUNIT MO must have been configured.
Relation with the AARU MO:
- The AARU MO corresponding to DEVICENO, CONNCN, CONNSRN, and CONNSN in
the VRET MO must have been configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST VRET Use this command to list the configuration of one or all virtual remote electrical
tilting (VRET) antennas.

MOD VRET Use this command to modify the configuration of a virtual remote electrical
tilting (VRET) antenna. The VRET antenna is added automatically when an
active antenna radio unit (AARU) is added. The configuration information about
the VRET antenna can be queried by running the LST VRET command.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Device No. Indicates the device number of the VRET antenna.The device number of the
VRET antenna must be unique.

Cabinet No. Indicates the cabinet number of the AARU where the VRET antenna is located.

Subrack No. Indicates the subrack number of the AARU where the VRET antenna is located.

Slot No. Indicates the slot number of the AARU where the VRET antenna is located.

Device Name Indicates the device name of the VRET antenna.The device name is optional, but
the device name configured for each ALD must be unique.

Subunit Quantity Indicates the number of subunits contained in the VRET antenna.

5.7.1.6.2.89 VRETSUBUNIT
EQUIPMENT
+-AAS
+-AARU
+-VRET
+-VRETSUBUNIT

Description

A VRETSubunit MO defines a virtual remote electrical tilting (VRET) subunit in an active


antenna radio unit (AARU), which receives and transmits RF signals.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
VRET

Relation with the VRET MO:


- The number of VRETSUBUNIT MOs configured on one VRET MO must be 8.
- The VRET MO corresponding to DEVICENO, CONNCN, CONNSRN, and CONNSN in
the VRETSUBUNIT MO must have been configured.
Relation with the VANTENNAPORT MO:
- One of the following VANTENNAPORT MOs must have been configured: 1. A
VANTENNAPORT MO corresponding to CONNCN, CONNSRN, CONNSN, and CONNPN1
in the VRETSUBUNIT MO whose CONNPN1 is set to a value other than 255. 2. A
VANTENNAPORT MO corresponding to CONNCN, CONNSRN, CONNSN, and CONNPN2
in the VRETSUBUNIT MO when CONNPN2 in the VRETSUBUNIT MO is set to a value
other than 255. 3. A VANTENNAPORT MO corresponding to CONNCN, CONNSRN,
CONNSN, and CONNPN3 in the VRETSUBUNIT MO when CONNPN3 in the
VRETSUBUNIT MO is set to a value other than 255. 4. A VANTENNAPORT MO
corresponding to CONNCN, CONNSRN, CONNSN, and CONNPN4 in the VRETSUBUNIT
MO when CONNPN4 in the VRETSUBUNIT MO is set to a value other than 255.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

DSP VRETSUBUNIT Use this command to query the dynamic information about one or all virtual
remote electrical tilting (VRET) subunits.

LST VRETSUBUNIT Use this command to list the configuration of one or all virtual remote electrical
tilting (VRET) subunits.

MOD VRETSUBUNIT Use this command to modify the configuration of a virtual remote electrical
tilting (VRET) subunit.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Cabinet No. Indicates the cabinet number of the AARU where the VRET subunit is located.

Connected Port 1 Indicates the number of the first virtual antenna port to which the VRET subunit
is connected.

Connected Port 2 Indicates the number of the second virtual antenna port to which the VRET
subunit is connected.

Subunit Name Indicates the name of the VRET subunit.The name of the VRET subunit is
optional, but the name configured for each VRET subunit must be unique.

Device No. Indicates the device number of the VRET antenna where the VRET subunit is
contained.The device number of the VRET antenna must be unique.

Polar Type1 Indicates the polarization type of the virtual antenna port 1 to which the VRET
subunit is connected.

Slot No. Indicates the slot number of the AARU where the VRET subunit is located.

Subrack No. Indicates the subrack number of the AARU where the VRET subunit is located.

Subunit No. Indicates the number of the VRET subunit, which starts from 1.

Connected Port 3 Indicates the number of the third virtual antenna port to which the VRET subunit
Table 2 Related parameters

Parameter Description

is connected.

Polar Type2 Indicates the polarization type of the virtual antenna port 2 to which the VRET
subunit is connected.

Downlink Tilt Indicates the downlink tilt of the VRET subunit. If this parameter is set to
32767, it is invalid and the actual tilt is not changed.

Uplink Tilt Indicates the uplink tilt of the VRET subunit. If this parameter is set to 32767, it
is invalid and the actual tilt is not changed.

Connected Port 4 Indicates the number of the fourth virtual antenna port to which the VRET
subunit is connected.

Polar Type3 Indicates the polarization type of the virtual antenna port 3 to which the VRET
subunit is connected.

Polar Type4 Indicates the polarization type of the virtual antenna port 4 to which the VRET
subunit is connected.

PORTNUM Indicates the number of ports that can be added to a VRET subunit.

BeamAzimuth Indicates the horizontal azimuth of the virtual antenna subunit.

BeamWidth Indicates the horizontal beamwidth of the virtual antenna subunit.

5.7.1.6.2.90 WEBLMT
TRANSPORT
+-WEBLMT

Description

The WEBLMT MO defines the policy for logging in to the Web LMT.

Effective Scenario

Not involved
Relations Between MOs

Possible parents:
TRANSPORT

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the configuration of the policy for logging in to the
WEBLOGINPOLICY
Web LMT.

RST WEBLMT Use this command to reset the Web LMT.

SET Use this command to modify the configuration of a Web LMT login policy.
WEBLOGINPOLICY

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

WebLMT Login Policy Indicates the policy for logging in to the Web LMT.
The value COMPATIBLE indicates that if http is entered in the address bar of an
IE browser, the HTTP is used for and after the login. If https is entered in the
address bar of an IE browser, the HTTPS is used for and after the login.
The value HTTPS_ONLY indicates that the HTTPS is used for and after the
login no matter whether http or https is entered in the address bar of an IE
browser.
The value LOGIN_HTTPS_ONLY indicates that the HTTPS is used for login
and the HTTP is used after the login no matter whether http or https is entered in
the address bar of an IE browser.

5.7.1.6.3 Radio-tree
This chapter describes the MOs related to eNodeB radio.

AlgoDefaultPara

ANR

BcchCfg

BfAnt

BfMimoAdaptiveParaCfg

CaGroup

CaGroupCell

CaMgtCfg

Cdma20001XrttExtCell

Cdma20001XrttNCell

Cdma20001XrttPreReg

Cdma2000BandClass

Cdma2000BcSCellOp

Cdma2000HrpdExtCell

Cdma2000HrpdNCell

Cdma2000HrpdPreReg

Cdma2000HrpdRefCell

Cdma2000Nfreq

Cell

CellAcBar

CellAccess

CellAlgoSwitch

CellBf

CellChPwrCfg

CellDlCompAlgo
CellDlIcic

CellDLIcicMcPara

CellDlpcPdcch

CellDlpcPdsch

CellDlpcPdschPa

CellDlpcPhich

CellDlschAlgo

CellDrxPara

CellEicic

CellExtendedQci

CellHoParaCfg

CellIdPrdUpt

CellLowPower

CellMLB

CellMro

CellNoAccessAlmPara

CellOp

CellPdcchAlgo

CellPucchAlgo

CellRacThd

CellResel

CellReselCdma2000

CellReselGeran

CellReselUtran

CellRfShutdown

CellRicAlgo
CellSel

CellServiceDiffCfg

CellShutdown

CellSiMap

CellSimuLoad

CellStandardQci

CellUlCompAlgo

CellUlIcic

CellULIcicMcPara

CellUlpcComm

CellUlpcDedic

CellUlschAlgo

CnOperator

CnOperatorExtendedQci

CnOperatorHoCfg

CnOperatorIpPath

CnOperatorSpidCfg

CnOperatorStandardQci

CnOperatorTa

CounterCheckPara

CqiAdaptiveCfg

CSFallBackBlindHoCfg

CSFallBackHo

CSFallBackPolicyCfg

DistBasedHO

Drx
DrxParaGroup

Emc

eNBCellOpRsvdPara

eNBCellQciRsvdPara

eNBCellRsvdPara

eNBCnOpQciRsvdPara

eNBCnOpRsvdPara

eNBLicenseAlmThd

eNBQciRsvdPara

eNBRsvdPara

ENodeBAlgoSwitch

eNodeBAutoPowerOff

eNodeBChrOutputCtrl

ENodeBCipherCap

ENodeBConnStateTimer

eNodeBFlowCtrlPara

eNodeBFunction

ENodeBIntegrityCap

eNodeBPath

ENodeBSharingMode

eUCellSectorEqm

EuSectorEqmGroup

EutranExternalCell

EutranExternalCellPlmn

EutranInterFreqNCell

EutranInterNFreq
EutranIntraFreqNCell

EutranNFreqRanShare

EutranNFreqSCellOp

ExtendedQci

GeranExternalCell

GeranExternalCellPlmn

GeranInterfArfcn

GeranInterfCfg

GeranNcell

GeranNFGroupSCellOp

GeranNfreqGroup

GeranNfreqGroupArfcn

GeranRanShare

GlobalProcSwitch

HoMeasComm

IbdlInfo

InterFreqBlkCell

InterFreqHoGroup

InterPlmnHoList

InterRatCellShutdown

InterRatHoCdma1xRttGroup

InterRatHoCdmaHrpdGroup

InterRatHoComm

InterRatHoCommGroup

InterRatHoGeranGroup

InterRatHoUtranGroup
InterRatPolicyCfgGroup

IntraFreqBlkCell

IntraFreqHoGroup

IntraRatHoComm

LicenseSharingPolicy

LicRatio

LicRatioSharePolicy

MimoAdaptiveParaCfg

MmeFeatureCfg

MRO

PCCHCfg

PdcpRohcPara

PDSCHCfg

PHICHCfg

PUCCHCfg

PUSCHCfg

PuschParam

RACHCfg

RatFreqPriorityGroup

RlcPdcpParaGroup

RlfTimerConstGroup

RrcConnStateTimer

S1

S1Interface

S1ReestTimer

ServiceIfHoCfgGroup
ServiceIrHoCfgGroup

SfnAuxResBind

SfnCellBind

SimuLoad

SpidCfg

SrsAdaptiveCfg

SRSCfg

StandardQci

TceIpMapping

TcpAckCtrlAlgo

TcpMssCtrl

TddFrameOffset

TddResModeSwitch

TimeAlignmentTimer

TpeAlgo

TypDrbBsr

UeTimerConst

UtranExternalCell

UtranExternalCellPlmn

UtranNCell

UtranNFreq

UtranNFreqSCellOp

UtranRanShare

VQMAlgo

X2

X2AutoSetupOperator
X2BlackWhiteList

X2Interface

Parent topic: MO

5.7.1.6.3.1 AlgoDefaultPara
+-NE
+-eNodeBFunction
+-AlgoDefaultPara

Description

The AlgoDefaultPara MO consists of the default parameter related to an algorithm.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the setting of the default parameter applied when
ALGODEFAULTPARA
measurement switches are turned off.

MOD Use this command to modify the default parameter applied when measurement
ALGODEFAULTPARA
switches are turned off.

Related Parameters
Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Default doppler level Indicates the default Doppler shift level. This is the default parameter used when
Doppler shift measurement is not required. This parameter is unavailable in this
version.

5.7.1.6.3.2 ANR
+-NE
+-eNodeBFunction
+-ANR

Description

The ANR MO consists of the parameters related to the Automatic Neighbor Relation (ANR)
algorithm, which is used to solve the problems of neighboring cell missing, unusual handover
between neighboring cells, and physical cell ID conflict. The ANR feature reduces the
probability of the preceding problems and therefore increases the handover success rate.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

LST ANR Use this command to list the ANR configuration.

MOD ANR Use this command to modify the ANR configuration.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

ANR add cell threshold Indicates the threshold above which a neighboring cell is added to a serving cell
by ANR. The threshold is the percentage of the number of successful handovers
to the total number of handovers from the serving cell to the neighboring cell. In
this version, this parameter is no longer used internally although it supports
setting synchronization between the M2000 and the eNodeB. Avoid using this
parameter as it will be removed from later versions.

ANR delete cell Indicates the threshold for removing a neighbor relationship with a cell by ANR
threshold
based on the handover success rate. The threshold is the percentage of the
number of successful handovers to the total number of handovers from the local
cell to the neighboring cell. For example, an external cell is configured as a
neighboring cell for all cells under an eNodeB, this neighboring cell permits
automatic removal of the neighboring relationship by ANR and its CtrlMode is
AutoMode. If the success rate of handovers from each cell under the eNodeB to
this neighboring cell is lower than or equal to this threshold after a measurement
period, the corresponding external cell and the neighbor relationship with this
cell are automatically removed.

Least Handover Num Indicates the threshold for the total number of handovers to an intra-RAT
for Statistic
neighboring cell, above which ANR begins to evaluate the removal of the
neighboring relation in the case of a low handover success rate.

Statistic cycle Indicates the period during which the total number of handovers to an intra-RAT
neighboring cell is measured by ANR to evaluate the removal of the neighboring
relation in the case of a low handover success rate.

Fast ANR PCI report Indicates the number of periodic measurement reports sent for fast ANR.
amount

Fast ANR PCI report Indicates the interval at which periodic measurement reports are sent for fast
interval
Table 2 Related parameters

Parameter Description

ANR.

Fast ANR checking Indicates the fast ANR checking timer. When the timer is expired, the eNodeB
period
automatically checks whether to disable fast ANR.

Fast ANR measurement Indicates the reference signal received power (RSRP) threshold for intra-RAT
RSRP threshold
fast ANR. If the signal quality in a neighboring E-UTRAN cell reported by the
UE is lower than the threshold, the cell is not automatically added as an external
cell of the eNodeB.

IntraRat Fast ANR Indicates the maximum allowed number of UEs that perform intra-RAT
measurement UE
number measurements for fast ANR. After the number of UEs performing intra-RAT
measurements for fast ANR reaches the maximum number, intra-RAT
measurements for fast ANR will not be performed on other UEs.

InterRat Fast ANR Indicates the maximum allowed number of UEs that perform inter-RAT
measurement UE
number measurements for fast ANR. After the number of UEs performing inter-RAT
measurements for fast ANR reaches the maximum number, inter-RAT
measurements for fast ANR will not be performed on other UEs.

IntraRat Fast ANR valid Indicates the threshold above which the eNodeB enters the monitoring state for
measurement min UE
number intra-RAT fast ANR. The threshold is expressed as the number of UEs that have
performed measurements for intra-RAT fast ANR.

InterRat Fast ANR valid Indicates the threshold above which the eNodeB enters the monitoring state for
measurement min UE
number inter-RAT fast ANR. The threshold is expressed as the number of UEs that have
performed measurements for inter-RAT fast ANR.

Optimization Mode Indicates the mode for optimizing neighboring relations. If this parameter is set
to FREE, neighboring relations are optimized automatically by ANR. If this
parameter is set to CONTROLLED, neighboring relations to be added or
removed are reported to the M2000 and then subject to manual processing for
optimization.

Statistic Cycle For Indicates the period during which the number of handovers are measured for
Delete NRT
neighbor relationship removal from a neighbor relation table (NRT) when the
number of neighbor relationships in the NRT has reached the maximum
specification and a new neighbor relationship is to be added to the NRT by
ANR. This parameter is also used to determine external cell removal from a
neighboring cell list (NCL). Within four consecutive measurement periods, if an
external cell is not added to the NRT as a neighboring cell, and the local eNodeB
is not configured with an X2 interface with the peer eNodeB providing this
external cell, this external cell is removed from the NCL.
Table 2 Related parameters

Parameter Description

Statistic Number For Indicates the number of handovers above which a neighbor relationship is to be
Delete NRT
removed from a neighbor relation table (NRT) when the number of neighbor
relationships in the NRT has reached the maximum specification and a new
neighbor relationship is to be added to the NRT by ANR. In the latest
measurement period for neighbor relationship removal, if the total number of
handovers from the local cell exceeds the value of this parameter, a neighboring
cell that is not detected by UEs is removed from the NRT.

ANR Active PCI Conflict Indicates the switch used to enable or disable proactive PCI conflict detection.
Detection Switch
Within a specified duration after this switch is turned on, the eNodeB delivers
measurement configurations for proactive PCI conflict detection to UEs that
meet specific requirements. Then, the eNodeB starts the detection based on the
measurement reports from the UEs.

Start time Indicates the start time of the active PCI conflict detection. If the stop time is
earlier than or the same as the start time, the stop time is assumed to be the time
of the next day.

Stop time Indicates the stop time of the active PCI conflict detection. If the stop time is
earlier than or the same as the start time, the stop time is assumed to be the time
of the next day.

UTRAN Fast ANR Indicates the received signal code power (RSCP) threshold for fast ANR with
RSCP threshold
UTRAN. If the signal quality in a neighboring UTRAN cell reported by the UE
is lower than the threshold, the cell is not automatically added as an external cell
of the eNodeB.

GERAN Fast ANR Indicates the received signal strength indicator (RSSI) threshold for fast ANR
RSSI threshold
with GERAN. If the signal quality in a neighboring GERAN cell reported by the
UE is lower than the threshold, the cell is not automatically added as an external
cell of the eNodeB.

CDMA2000 1XRTT Indicates the pilot strength threshold for fast ANR with CDMA2000 1xRTT. If
Fast ANR Pilot
threshold the signal quality in a neighboring CDMA2000 1xRTT cell reported by the UE
is lower than the threshold, the cell is not automatically added as an external cell
of the eNodeB.

CDMA2000 HRPD Fast Indicates the pilot strength threshold for fast ANR with CDMA2000 HRPD. If
ANR Pilot threshold
the signal quality in a neighboring CDMA2000 HRPD cell reported by the UE is
lower than the threshold, the cell is not automatically added as an external cell
of the eNodeB.

Fast ANR Mode Indicates the policy to add neighboring cells based on fast ANR. When this
parameter is set to NCL_MODE, neighboring cells measured by fast ANR are
Table 2 Related parameters

Parameter Description

added to only the neighboring cell list (NCL). When this parameter is set to
NCL_NRT_MODE, neighboring cells measured by the ANR are added to the
NCL, and neighboring cells with the strongest signals are added to the
neighboring relation table (NRT) simultaneously.Currently, only the inter-
frequency neighboring cell, neighboring UTRAN cell, and neighboring GERAN
cell with the strongest signals can be added to the NRT by fast ANR, and the
intra-frequency neighboring cell and neighboring CDMA2000 cell with the
strongest signals cannot be added to the NRT by fast ANR.The intra-frequency
neighboring cells and neighboring CDMA2000 cells can only be added to the
NCL regardless of the parameter setting.

5.7.1.6.3.3 BcchCfg
+-NE
+-eNodeBFunction
+-Cell
+-BcchCfg

Description

The BcchCfg MO consists of the parameters related to the Broadcast Control Channel (BCCH),
which is common radio resources in a cell.
The BCCH is a downlink logical channel that is used to broadcast the control information in the
system.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the PCCHCfg MO:


- The product of DefaultPagingCycle in the PCCHCfg MO and ModifyPeriodCoeff in the
BcchCfg MO cannot exceed 1024 radio frames, that is 10,240 milliseconds.
Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST BCCHCFG Use this command to list the BCCH configuration.

MOD BCCHCFG Use this command to modify the BCCH configuration.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Modification period Indicates the modification period coefficient for the BCCH. BCCH modification
coefficient
period is equal to Modification period coefficient multiplies Default paging
cycle, where the BCCH modification period and default paging cycle are
measured in unit of radio frames, and the modification period coefficient is
specified by this parameter.

5.7.1.6.3.4 BfAnt
+-NE
+-eNodeBFunction
+-BfAnt

Description

A BFANT MO defines a beamforming (BF) antenna. By adjusting the amplitude and phase of
output signals at each port of a BF antenna, the eNodeB can transmit a beam of a specific width
to achieve increased gains.
Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ACT BFANTDB Use this command to activate a weight database file for a beamforming antenna.

ADD BFANT Use this command to add a beamforming antenna.

DLD BFANTDB Use this command to download a weight database file for a beamforming
antenna.

DSP BFANT Use this command to query the dynamic information about one or all
beamforming antennas.

DSP BFANTDB Use this command to query a weight database file for a beamforming antenna.

LST BFANT Use this command to list the configuration of one or all beamforming antennas.

MOD BFANT Use this command to modify the configuration of a beamforming antenna.

RMV BFANT Use this command to remove a beamforming antenna.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Device No. Indicates the device number of the BF antenna, it uniquely identifies a RET
Table 2 Related parameters

Parameter Description

within an eNodeB.

Manufactory Indicates the manufacturer of the BF antenna.

Connect RRU cabinet Indicates the cabinet number of the RRU connecting to the BF antenna.
No.

Connect RRU subrack Indicates the subrack number of the RRU connecting to the BF antenna.
No.

Connect RRU slot No. Indicates the slot number of the RRU connecting to the BF antenna.

Antenna model number Indicates the model of the BF antenna.

Tilt Indicates the configured tilt of the BF antenna.

Beamwidth Indicates the beamwidth formed after beamforming.

Band Indicates the frequency band in which the BF antenna operates.

Antenna Type Indicates the type of the BF antenna.

Polar Mode Indicates the polarization mode of the BF antenna.

Element Beamform Indicates the beamwidth of the antenna element.


Width

Number of Port Indicates the number of physical antenna ports to which the BF antenna is
connected.

Amplitude Offset of Indicates the amplitude offset at physical antenna port 1 when the BF antenna is
Physical Port 1 for
CRS2 used and cell-specific reference signals are transmitted from two ports. Each
port may consist of multiple physical antenna ports.

Phase of Physical Port Indicates the phase offset at physical antenna port 1 when the BF antenna is used
1 for CRS2
and cell-specific reference signals are transmitted from two ports. Each port may
consist of multiple physical antenna ports.

Amplitude Offset of Indicates the amplitude offset at physical antenna port 2 when the BF antenna is
Physical Port 2 for
CRS2 used and cell-specific reference signals are transmitted from two ports. Each
port may consist of multiple physical antenna ports.

Phase of Physical Port Indicates the phase offset at physical antenna port 2 when the BF antenna is used
2 for CRS2
and cell-specific reference signals are transmitted from two ports. Each port may
consist of multiple physical antenna ports.
Table 2 Related parameters

Parameter Description

Amplitude Offset of Indicates the amplitude offset at physical antenna port 3 when the BF antenna is
Physical Port 3 for
CRS2 used and cell-specific reference signals are transmitted from two ports. Each
port may consist of multiple physical antenna ports.

Phase of Physical Port Indicates the phase offset at physical antenna port 3 when the BF antenna is used
3 for CRS2
and cell-specific reference signals are transmitted from two ports. Each port may
consist of multiple physical antenna ports.

Amplitude Offset of Indicates the amplitude offset at physical antenna port 4 when the BF antenna is
Physical Port 4 for
CRS2 used and cell-specific reference signals are transmitted from two ports. Each
port may consist of multiple physical antenna ports.

Phase of Physical Port Indicates the phase offset at physical antenna port 4 when the BF antenna is used
4 for CRS2
and cell-specific reference signals are transmitted from two ports. Each port may
consist of multiple physical antenna ports.

Amplitude Offset of Indicates the amplitude offset at physical antenna port 1 when the BF antenna is
Physical Port 1 for
CRS4 used and cell-specific reference signals are transmitted from four ports. Each
port may consist of multiple physical antenna ports.

Phase of Physical Port Indicates the phase offset at physical antenna port 1 when the BF antenna is used
1 for CRS4
and cell-specific reference signals are transmitted from four ports. Each port
may consist of multiple physical antenna ports.

Amplitude Offset of Indicates the amplitude offset at physical antenna port 2 when the BF antenna is
Physical Port 2 for
CRS4 used and cell-specific reference signals are transmitted from four ports. Each
port may consist of multiple physical antenna ports.

Phase of Physical Port Indicates the phase offset at physical antenna port 2 when the BF antenna is used
2 for CRS4
and cell-specific reference signals are transmitted from four ports. Each port
may consist of multiple physical antenna ports.

Session ID Indicates the ID of the file transfer session.

5.7.1.6.3.5 BfMimoAdaptiveParaCfg
+-NE
+-eNodeBFunction
+-BfMimoAdaptiveParaCfg
Description

The BfMimoAdaptiveParaCfg MO consists of the parameters related to adaptive beamforming


and MIMO (BFMIMO). If adaptive BFMIMO is enabled, the eNodeB sets a MIMO or
beamforming transmission mode based on channel conditions. If adaptive BFMIMO is disabled,
the eNodeB uses a fixed MIMO or beamforming transmission mode. Currently, only open-loop
beamforming and open-loop MIMO transmission modes are supported.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the parameters related to adaptive beamforming and
BFMIMOADAPTIVEPA
RACFG MIMO (BFMIMO).

MOD Use this command to modify the parameters related to adaptive beamforming
BFMIMOADAPTIVEPA
RACFG and MIMO (BFMIMO).

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

BfMIMO adaptive Indicates the type of adaptive beamforming and MIMO (BFMIMO) for a multi-
switch
antenna eNodeB. The values are described as follows: NO_ADAPTIVE: A fixed
BFMIMO transmission mode is used. That is, transition between BFMIMO
transmission modes is not supported. TxD_BF_ADAPTIVE: The transmission
Table 2 Related parameters

Parameter Description

mode changes adaptively between TM2 and TM7 or between TM2 and TM8,
depending on the protocol release with which UEs comply.
MIMO_BF_ADAPTIVE: The transmission mode changes adaptively between
TM2, TM3, and TM7 or between TM2, TM3, and TM8, depending on the
protocol release with which UEs comply.

Fixed BfMIMO mode Indicates the fixed beamforming and MIMO (BFMIMO) transmission mode
configured by a multi-antenna eNodeB for UEs. This parameter is valid only
when BfMimoAdaptiveSwitch is set to NO_ADAPTIVE. There are five values.
TM2: Transmission mode 2 is always used for UEs. TM3: Transmission mode 3
is always used for UEs. TM7: Transmission mode 7 is always used for UEs.
TM8: Transmission mode 8 is always used for UEs. TM4: Transmission mode 4
is always used for UEs.

5.7.1.6.3.6 CaGroup
+-NE
+-eNodeBFunction
+-CaGroup
+-CaGroupCell[0~2]

Description

The CaGroup MO defines a carrier aggregation (CA) group.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Possible children:
CaGroupCell[0~2]

Relation with the CaGroupCell MO:


- A maximum of two CaGroupCell MOs can be configured under each CaGroup MO.
Relation with the CaGroupCell,Cell MOs:
- If CaGroupType in a CaGroup MO is set to FDD, the Cell MOs associated with the
CaGroupCell MO under this CaGroup MO must also work in CELL_FDD mode.
- If CaGroupType in a CaGroup MO is set to TDD_SAME_SA, FddTddInd in Cell MO
associated with a CaGroupCell MO under this CaGroup MO must be CELL_TDD,and
SubframeAssignment must be SA1 or SA2 at the same time.
- If CaGroupType in a CaGroup MO is set to TDD_SAME_SA, FddTddInd in Cell MO
associated with a CaGroupCell MO under this CaGroup MO must be CELL_TDD,and
SubframeAssignment of one cell must be SA1, SubframeAssignment of the other cell must be
SA2.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD CAGROUP Use this command to add a CA group.

LST CAGROUP Use this command to list the configuration of a CA group.

MOD CAGROUP Use this command to modify a CA group.

RMV CAGROUP Use this command to remove a CA group.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

CA Group Identity Indicates the identity of the CA group. It uniquely identifies a CA group within
an eNodeB.

CA Group Type Indicates the type of the carrier aggregation (CA) group. If this parameter is set
to FDD, only FDD cells can be configured into the CA group. If this parameter
is set to TDD_SAME_SA, only TDD cells can be configured into the CA group
Table 2 Related parameters

Parameter Description

and they must have the same uplink-downlink subframe configuration (specified
by the SubframeAssignment parameter) of SA1 or SA2. If this parameter is set
to TDD_DIFF_SA, only TDD cells can be configured into the CA group and
they must have different uplink-downlink subframe configurations with one
using SA1 and the other using SA2.

5.7.1.6.3.7 CaGroupCell
+-NE
+-eNodeBFunction
+-CaGroup
+-CaGroupCell

Description

The CaGroupCell MO defines a cell in a carrier aggregation (CA) group.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
CaGroup

Relation with the CaGroup MO:


- A maximum of two CaGroupCell MOs can be configured under each CaGroup MO.
Relation with the Cell MO:
- LocalCellId in a CaGroupCell MO must have been set in the associated Cell MO.
- One Cell MO can be configured only as one CaGroupCell MO.
- DlBandWidth in the Cell MOs associated with a CaGroupCell MO must be set to
CELL_BW_N25, CELL_BW_N50, CELL_BW_N75, or CELL_BW_N100.
- CustomizedBandWidthCfgInd in the Cell MOs associated with a CaGroupCell MO must
be set to NOT_CFG.
- HighSpeedFlag in the Cell MOs associated with a CaGroupCell MO can be set only to
LOW_SPEED.
- UlCyclicPrefix or DlCyclicPrefix in the Cell MOs associated with a CaGroupCell MO
under the same CaGroup MO must be set to the same value.
- For two Cell MOs associated with a CaGroupCell MO under the same CaGroup MO, if the
spacing between their downlink center frequencies is less than their average downlink
bandwidth, the spacing must be the nominal channel spacing between contiguously aggregated
component carriers.
- For two Cell MOs associated with a CaGroupCell MO under the same CaGroup MO, if the
spacing between their uplink center frequencies is less than their average uplink bandwidth, the
spacing must be the nominal channel spacing between contiguously aggregated component
carriers.
- For two Cell MOs associated with a CaGroupCell MO under the same CaGroup MO, if
FddTddInd of one cell is set to CELL_TDD and SpecialSubframePatterns is set to SSP4,
FddTddInd of the other cell must be set to CELL_TDD and SpecialSubframePatterns must
not be set to SSP5, SSP6, SSP7, SSP8.
- If a FDD Cell MO is associated with the CaGroupCell MO, the MultiRruCellMode of this
cell cannot be set to SFN.
Relation with the CaGroup,Cell MOs:
- If CaGroupType in a CaGroup MO is set to FDD, the Cell MOs associated with the
CaGroupCell MO under this CaGroup MO must also work in CELL_FDD mode.
- If CaGroupType in a CaGroup MO is set to TDD_SAME_SA, FddTddInd in Cell MO
associated with a CaGroupCell MO under this CaGroup MO must be CELL_TDD,and
SubframeAssignment must be SA1 or SA2 at the same time.
- If CaGroupType in a CaGroup MO is set to TDD_SAME_SA, FddTddInd in Cell MO
associated with a CaGroupCell MO under this CaGroup MO must be CELL_TDD,and
SubframeAssignment of one cell must be SA1, SubframeAssignment of the other cell must be
SA2.
Relation with the CellOp MO:
- Assume that set A consists of all TrackingAreaId values under one Cell MO associated with
a CaGroupCell MO, and set B consists of all TrackingAreaId values under the other Cell MO
associated with a CaGroupCell MO under the same CaGroup MO with A. Then, sets A and B
must have at least one overlapping TrackingAreaId value.
Relation with the Cell,EutranInterFreqNCell MOs:
- The two Cell MOs associated with a CaGroupCell MO under the same CaGroup MO must
have inter-frequency neighbor relationships with each other.
Relation with the Cell,eUCellSectorEqm,SECTOREQM,RRU,RRUCHAIN MOs:
- If CellActiveState in both Cell MOs corresponding to a CaGroupCell MO under the same
CaGroup MO are set to CELL_ACTIVE, the RRUCHAIN MOs where the RRU MOs
associated with SECTOREQM MOs corresponding to eUCellSectorEqm MOs under both Cell
MOs are configured must be in the same subrack.
Relation with the Cell,eUCellSectorEqm,SECTOREQM,RFU,RRUCHAIN MOs:
- If CellActiveState in both Cell MOs corresponding to a CaGroupCell MO under the same
CaGroup MO are set to CELL_ACTIVE, the RRUCHAIN MOs where the RFU MOs
associated with SECTOREQM MOs corresponding to eUCellSectorEqm MOs under both Cell
MOs are configured must be in the same subrack.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD CAGROUPCELL Use this command to add a cell to a CA group.

LST CAGROUPCELL Use this command to list the cells in a CA group.

RMV CAGROUPCELL Use this command to remove a cell from a CA group.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

CA Group Identity Indicates the identity of the CA group. It uniquely identifies a CA group within
an eNodeB.

Local Cell ID Indicates the local cell identity. It uniquely identifies a cell within an eNodeB.

5.7.1.6.3.8 CaMgtCfg
+-NE
+-eNodeBFunction
+-Cell
+-CaMgtCfg

Description

A CaMgtCfg MO consists of parameters related to carrier aggregation management


configuration. It is used to measure the channel quality of a serving cell. If the measurement
results meet the corresponding conditions, the UE sends a measurement report.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the Cell MO:


- LocalCellId in an CaMgtCfg MO must have been set in the associated Cell MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST CAMGTCFG Use this command to list the settings of parameters related to carrier aggregation
management.

MOD CAMGTCFG Use this command to modify the settings of parameters related to carrier
aggregation management.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local identity of the cell. It uniquely identifies a cell within an
eNodeB.

Carrier Aggregation A2 Indicates the Reference Signal Received Power (RSRP) threshold for reporting
RSRP threshold
event A2 in a secondary cell. When the RSRP of a UE is lower than this
threshold, event A2 is reported.

Carrier Aggregation A4 Indicates the Reference Signal Received Power (RSRP) threshold for a UE to
RSRP threshold
report event A4 of a secondary cell. When the RSRP of the UE is greater than
the threshold, event A4 is reported.

Carrier Management Indicates the carrier management switch. If this switch is turned on, a secondary
Switch
component carrier (SCC) is activated and deactivated based on the traffic
volume, which reduces the UE power consumption when a carrier aggregation
(CA) UE performs no service or a few services. If this switch is turned off, the
SCC is always active after being configured, a CA UE can use the SCC
immediately when the traffic volume is large.

CA Active Buffer Length Indicates the threshold for a CA UE to activate an SCell. A CA UE can active an
Threshold
SCell only when its buffered data on the eNodeB exceeds this threshold.

CA Deactive Buffer Indicates the threshold for a CA UE to deactivate an SCell. A CA UE can


Length Threshold
deactivate an SCell only when its buffered data on the eNodeB is smaller than
this threshold.

CA Active Buffer Delay Indicates the threshold for a CA UE to activate an SCell. A CA UE can activate
Threshold
an SCell only when its buffer delay on the eNodeB exceeds this threshold.

CA Deactive Indicates the threshold for a CA UE to deactivate an SCell. A CA UE can


Throughput Threshold
deactivate an SCell only when its throughput is smaller than the value of this
parameter.

5.7.1.6.3.9 Cdma20001XrttExtCell
+-NE
+-eNodeBFunction
+-Cdma20001XrttExtCell

Description
A Cdma20001XrttExtCell MO consists of the parameters related to an external CDMA2000
1xRTT cell. It provides the common information about neighboring CDMA2000 1xRTT cells.
For details, see 3GPP TS 36.331.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Relation with the Cdma20001XrttNCell MO:


- Before adding a Cdma20001XrttNCell MO, ensure that the associated
Cdma20001XrttExtCell MO has been configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add an external CDMA2000 1xRTT cell.


CDMA20001XRTTEXT
CELL

LST Use this command to list the parameters related to the external CDMA2000
CDMA20001XRTTEXT
CELL 1xRTT cell.

MOD Use this command to modify an external CDMA2000 1xRTT cell.


CDMA20001XRTTEXT
CELL

RMV Use this command to remove an external CDMA2000 1xRTT cell.


CDMA20001XRTTEXT
CELL

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

CDMA20001XRTT cell Indicates the cell ID of the external CDMA2000 1xRTT cell. The cell ID and
ID
sector ID together uniquely identify a CDMA2000 cell in the mobile switching
center (MSC). In the CDMA2000 1xRTT network, a cell ID uniquely identifies
a cell within the mobile switching center (MSC). A cell ID consists of 12 bits.

CDMA20001XRTT Indicates the sector ID of the external CDMA2000 1xRTT cell. The cell ID and
sector ID
sector ID together uniquely identify a CDMA2000 cell in the mobile switching
center (MSC). A sector ID is unique in a CDMA2000 cell and consists of four
bits.

Band class Indicates the band class on which the external CDMA2000 1x radio
transmission technology (1xRTT) cell operates. For details about this parameter,
see 3GPP TS 36.331.

Frequency Indicates the frequency on which the external CDMA2000 1xRTT cell operates.
For details about this parameter, see 3GPP TS 36.331.

System ID Indicates the system ID of the external CDMA2000 1xRTT cell. A system ID is
assigned to each local mobile network and is used to determine whether a UE is
in the roaming state. For details about this parameter, see 3GPP TS 36.331.

Network ID Indicates the ID of the network to which the external CDMA2000 1xRTT cell
belongs. A base station is a cellular system and a member of the network. A
network is a subset of a system that is identified by a system ID. A network in a
system is identified by a network ID. A system ID and a network ID together
uniquely identify a network. System ID 0 and network ID 0 indicate all base
stations outside a specified network and are reserved values. Network ID 65535
is also reserved; this ID indicates that the roaming status of UEs is non-roaming
in the whole system no matter what the network ID is. For details, see the
description of NID in 3GPP2 C.S0005.

Mobile country code Indicates the mobile country code (MCC) of the external CDMA2000 1xRTT
cell.
A public land mobile network (PLMN) ID is comprised of an MCC and a
mobile network code (MNC).
The MCC consists of three digits.
The MNC consists of two or three digits.
For example, if the MCC is 123 and the MNC is 45, the PLMN ID is 12345.

Mobile network code Indicates the mobile network code (MNC) of the external CDMA2000 1xRTT
cell.
A public land mobile network (PLMN) ID is comprised of a mobile country
code (MCC) and an MNC.
Table 2 Related parameters

Parameter Description

The MCC consists of three digits.


The MNC consists of two or three digits.
For example, if the MCC is 123 and the MNC is 45, the PLMN ID is 12345.

MSC ID Indicates the ID of the MSC to which the reference CDMA2000 1xRTT cell
belongs. The value begins with 0x followed by a maximum of 6 hexadecimal
characters (0 to 9, and A to F), for example, 0x123A. The hexadecimal character
string cannot begin with 0, for example, the value cannot be 0x0123A. An MSC
ID uniquely identifies an MSC and is determined by the operator.
MSCID is defined in TIA/EIA-41.5-D and consists of MarketID (2 bytes) and
SwitchNo (1 byte). MarketID is described in TIA/EIA TSB29 and can be
defined by the operator. It can be the SID or another ID that can differentiate
operators. SwitchNo consists of a group of cell addresses and circuit resource
IDs under MarketID.

Physical cell ID Indicates the pseudo noise (PN) sequence number of the external CDMA2000
1xRTT cell. This number is used as the physical cell ID of the cell. For details,
see the description of PILOT_PN in 3GPP2 C.S0005.

Cell name Indicates the name of the external CDMA2000 1xRTT cell.

Control Mode Indicates the control policy on ANR-related MOs, which can be defined by the
user or be based on the automatic neighbor relation (ANR) algorithm. When this
parameter is set to MANUAL_MODE, the ANR-related MOs can be modified
or removed by only the user. A failure message is displayed when the user adds
an existing MO. When this parameter is set to AUTO_MODE, the ANR-related
MOs can be modified or removed by the user or based on the ANR algorithm.
The MO removal is successful even if the MO does not exist. An MO can be
added both by the user and based on the ANR algorithm. If an existing MO is to
be added, the MO is modified when the user performs the addition, but it cannot
be added based on the ANR algorithm. When the ANR-related MOs are
automatically added based on the ANR algorithm, this parameter is set to
AUTO_MODE by default. When the ANR-related MOs are added by the user,
this parameter can be set to AUTO_MODE or MANUAL_MODE.

5.7.1.6.3.10 Cdma20001XrttNCell
+-NE
+-eNodeBFunction
+-Cell
+-Cdma20001XrttNCell

Description

A Cdma20001XrttNCell MO consists of parameters related to a neighboring CDMA2000 1xRTT


cell. The parameters are used for handover or reselection from an E-UTRAN cell to a
CDMA2000 1xRTT cell.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the Cdma2000Nfreq MO:


- Before adding a Cdma20001XrttNCell MO, ensure that the associated Cdma2000Nfreq
MO with the same LocalCellId, BandClass, and Frequency has been configured.
Relation with the Cell MO:
- A maximum of 32 Cdma20001XrttNCell MOs can be configured for each cell.
Relation with the Cdma20001XrttExtCell MO:
- Before adding a Cdma20001XrttNCell MO, ensure that the associated
Cdma20001XrttExtCell MO has been configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add the neighboring relation with a CDMA2000 1xRTT
CDMA20001XRTTNCE
LL cell.

LST Use this command to list the parameters of the neighboring relation with the
CDMA20001XRTTNCE
LL CDMA2000 1xRTT cell.

MOD Use this command to modify the configuration of the neighboring relation with a
CDMA20001XRTTNCE
LL CDMA2000 1xRTT cell.
Table 1 Related MML commands

MML Command Function

RMV Use this command to remove the neighboring relation with a CDMA2000
CDMA20001XRTTNCE
LL 1xRTT cell.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the ID of the Local cell. It uniquely identifies a cell within an eNodeB.

CDMA20001XRTT cell Indicates the cell ID of the neighboring CDMA2000 1xRTT cell. The cell ID
ID
and sector ID together uniquely identify a CDMA2000 cell in the entire
network. In the CDMA2000 1xRTT network, a cell ID uniquely identifies a cell
within the mobile switching center (MSC). A cell ID consists of 12 bits.

CDMA20001XRTT Indicates the sector ID of the neighboring CDMA2000 1xRTT cell. The cell ID
sector ID
and sector ID together uniquely identify a CDMA2000 cell within the MSC. A
sector ID is unique in a CDMA2000 cell and consists of 4 bits.

Band class Indicates the band class on which the neighboring CDMA2000 1xRTT cell
operates. For details about this parameter, see 3GPP TS 36.331.

Frequency Indicates the frequency on which the neighboring CDMA2000 1xRTT cell
operates. For details about this parameter, see 3GPP TS 36.331.

System ID Indicates the system ID of the neighboring CDMA2000 1xRTT cell. A system
ID is assigned to each local mobile network and is used to determine whether a
UE is in the roaming state. For details about this parameter, see 3GPP TS
36.331.

Network ID Indicates the network ID of the neighboring CDMA2000 1xRTT cell. For details
about this parameter, see 3GPP TS 36.331.

No handover indicator Indicates whether to permit or prohibit handovers from the local cell to the
neighboring cell.

No remove indicator Indicates whether to permit or prohibit removal of the neighboring relationship
by ANR.
Table 2 Related parameters

Parameter Description

ANR flag Indicates whether ANR with CDMA2000 1xRTT cells is enabled.

Local cell name Indicates the name of the local cell.

Neighbour cell name Indicates the name of the neighboring CDMA2000 1xRTT cell.

Control Mode Indicates the control policy on ANR-related MOs, which can be defined by the
user or be based on the automatic neighbor relation (ANR) algorithm. When this
parameter is set to MANUAL_MODE, the ANR-related MOs can be modified
or removed by only the user. A failure message is displayed when the user adds
an existing MO. When this parameter is set to AUTO_MODE, the ANR-related
MOs can be modified or removed by the user or based on the ANR algorithm.
The MO removal is successful even if the MO does not exist. An MO can be
added both by the user and based on the ANR algorithm. If an existing MO is to
be added, the MO is modified when the user performs the addition, but it cannot
be added based on the ANR algorithm. When the ANR-related MOs are
automatically added based on the ANR algorithm, this parameter is set to
AUTO_MODE by default. When the ANR-related MOs are added by the user,
this parameter can be set to AUTO_MODE or MANUAL_MODE.

5.7.1.6.3.11 Cdma20001XrttPreReg
+-NE
+-eNodeBFunction
+-Cell
+-Cdma20001XrttPreReg

Description

A Cdma20001Xrtt MO consists of CDMA2000 1xRTT CSFB pre-registration parameters. The


parameters are delivered in SIB8. After a UE receives CSFB pre-registration parameters in SIB8,
the UE initiates CDMA2000 1xRTT CSFB pre-registration.

Effective Scenario

Immediately

Relations Between MOs


Possible parents:
Cell

Relation with the Cell MO:


- A maximum of 1 Cdma20001XrttPreReg MOs can be configured for each cell.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add the pre-registration information about a CDMA2000
CDMA20001XRTTPRE
REG 1xRTT cell.

LST Use this command to list the configuration of pre-registration information about
CDMA20001XRTTPRE
REG the CDMA2000HRPD cell.

MOD Use this command to modify the configuration of pre-registration information


CDMA20001XRTTPRE
REG about a CDMA2000 HRPD cell.

RMV Use this command to remove the pre-registration information about a


CDMA20001XRTTPRE
REG CDMA2000 1xRTT cell.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the ID of the local cell. It uniquely identifies a cell within an eNodeB.

Mobile country code Indicates the mobile country code (MCC) of the CDMA2000 1xRTT cell.
A public land mobile network (PLMN) ID is comprised of an MCC and a
mobile network code (MNC).
The MCC consists of three digits.
The MNC consists of two or three digits.
For example, if the MCC is 123 and the MNC is 45, the PLMN ID is 12345.
Table 2 Related parameters

Parameter Description

Mobile network code Indicates the mobile network code (MNC) of the CDMA2000 1xRTT cell.
A public land mobile network (PLMN) ID is comprised of a mobile country
code (MCC) and an MNC.
The MCC consists of three digits.
The MNC consists of two or three digits.
For example, if the MCC is 123 and the MNC is 45, the PLMN ID is 12345.

CDMA20001XRTT cell Indicates the cell ID of the reference CDMA2000 1xRTT cell. The cell ID and
ID
sector ID together uniquely identify a CDMA2000 cell in the mobile switching
center (MSC). In the CDMA2000 1xRTT network, a cell ID uniquely identifies
a cell within the mobile switching center (MSC). A cell ID consists of 12 bits.

CDMA20001XRTT Indicates the sector ID of the reference CDMA2000 1xRTT cell. The cell ID and
sector ID
sector ID together uniquely identify a CDMA2000 cell in the mobile switching
center (MSC). A sector ID is unique in a CDMA2000 cell and consists of four
bits.

System ID Indicates the system ID of the reference CDMA2000 1xRTT cell. A system ID is
allocated to each local CDMA mobile network and is used to determine whether
a UE is in the roaming state. For details about this parameter, see 3GPP2
C.S0005.

Network ID Indicates the network ID of the reference CDMA2000 1xRTT cell. A base
station is a cellular system and a member of the network. A network is a subset
of a system that is identified by a system ID. A network in a system is identified
by a network ID. A system ID and a network ID together uniquely identify a
network. System ID 0 and network ID 0 indicate all base stations outside a
specified network and are reserved values. Network ID 65535 is also reserved;
this ID indicates that the roaming status of UEs is non-roaming in the whole
system no matter what the network ID is. For details, see the description of NID
in 3GPP2 C.S0005.

MSC ID Indicates the ID of the MSC to which the reference CDMA2000 1xRTT cell
belongs. The value begins with 0x followed by a maximum of 6 hexadecimal
characters (0 to 9, and A to F), for example, 0x123A. The hexadecimal character
string cannot begin with 0, for example, the value cannot be 0x0123A. An MSC
ID uniquely identifies an MSC and is determined by the operator.
MSCID is defined in TIA/EIA-41.5-D and consists of MarketID (2 bytes) and
SwitchNo (1 byte). MarketID is described in TIA/EIA TSB29 and can be
defined by the operator. It can be the SID or another ID that can differentiate
operators. SwitchNo consists of a group of cell addresses and circuit resource
IDs under MarketID.
Table 2 Related parameters

Parameter Description

Band class include Indicates whether to configure a band class for a UE. If this parameter is set to
indicator
CFG, the UE sends a location update request to the CDMA2000 1xRTT system
when the UE finds that the current band class is different from the band class
pre-registered the last time. For details, see the description of
BAND_CLASSIncluded in 3GPP2 C.S0097.

Band class Indicates the band class that a UE can pre-register at. If this parameter is set to
CFG, the UE sends a location update request to the CDMA2000 1xRTT system
when the UE finds that the current band class is different from the band class
pre-registered the last time. For details, see the description of BAND_CLASS in
3GPP2 C.S0097.

CSFB-registration Indicates whether the CDMA2000 1xRTT CSFB registration parameters need to
parameters configure
indicator be set. If this parameter is set to CFG, the CDMA2000 1xRTT circuit-switched
fallback (CSFB) registration parameters need to be set. If this parameter is set to
NOT_CFG, the CDMA2000 1xRTT CSFB registration parameters do not need
to be set and the parameters are not broadcast in SIB8.

Multiple system ID Indicates whether multiple system IDs (SIDs) can be stored. That is, whether
storage indicator
UEs are allowed to store SID_NID_LIST that contains different SIDs. For
details about this parameter, see 3GPP TS 36.331.

Multiple network ID Indicates whether multiple network IDs (NIDs) can be stored. That is, whether
storage indicator
UEs are allowed to store SID_NID_LIST that contains the same SID but
different NIDs. For details about this parameter, see 3GPP TS 36.331.

Home rgistration Indicates whether a non-roaming UE is allowed to register at the current system.
indicator
If this parameter is set to BOOLEAN_TRUE and MOB_TERM_HOME in the
UE is set to BOOLEAN_TRUE, the UE can automatically register at the current
system. MOB_TERM_HOME indicates whether a UE can be called in the home
PLMN. Automatic registration can be power-on registration, power-off
registration, periodic registration, zone-based registration, or distance-based
registration. For details, see the description of homeReg in 3GPP TS 36.331.

System ID roamer Indicates whether a UE roaming from another system is allowed to register at
registration indicator
the current system. If this parameter is set to BOOLEAN_TRUE and
MOB_TERM_FOR_SID in the UE is set to 1, the UE can automatically register
at the current system. For details, see the description of foreignSIDReg in 3GPP
TS 36.331.

Network ID roamer Indicates whether a UE roaming from another network is allowed to register at
registration indicator
the current network. If this parameter is set to BOOLEAN_TRUE, the UE can
automatically register at the current network. For details, see the description of
foreignNIDReg in 3GPP TS 36.331.
Table 2 Related parameters

Parameter Description

Parameter change Indicates whether a UE can initiate automatic registration when some of its
registration indicator
parameters are changed or when it enters a new system. If this parameter is set
to BOOLEAN_TRUE, automatic registration is allowed. If this parameter is set
to BOOLEAN_FALSE, automatic registration is not allowed. For details, see the
description of parameterReg in 3GPP TS 36.331.

Power up registration Indicates whether power-on registration is allowed, that is, whether a UE can
indicator
initiate automatic registration immediately after being powered on and receiving
a system message. If this parameter is set to BOOLEAN_TRUE, the UE can
initiate automatic registration. If this parameter is set to BOOLEAN_FALSE,
the UEs cannot initiate automatic registration. To prevent frequent registration
due to immediate power-off after power-on, the UE can initiate registration 20
seconds after it enters the idle mode. For details, see the description of
powerUpReg in 3GPP TS 36.331.

Registration period Indicates the CDMA2000 1xRTT registration period. If this parameter is set to
0, the UE does not perform time-based registration. If this parameter is set to a
value in the range from 29 to 85, the period can be calculated using the
following formula: [2^(Registration period/4)] 0.08s. For details, see the
description of registrationPeriod in 3GPP TS 36.331.

Registration zone Indicates the CDMA2000 1xRTT registration zone. This parameter, the system
ID, and the network ID together uniquely identify a CDMA2000 registration
zone. This parameter is used for registration-zone-based registration.
Registration zones are planned based on actual network conditions. For details,
see the description of registrationZone in 3GPP TS 36.331.

Number of registration Indicates the total number of CDMA2000 1xRTT registration zones to be
zones to be retained
retained. If this parameter is set to 0, registration-zone-based registration is
disabled. If this parameter is set to a value greater than 1, UEs do not frequently
switch between registration zones. However, this results in delayed location
updates. For details, see the description of totalZone in 3GPP TS 36.331.

Zone timer length Indicates the length of the CDMA 1xRTT registration zone timer. The UE saves
the registration zone code contained in an SPM message to a registration zone
list. If the UE does not receive any message from a registration zone within the
timer length, the UE deletes this registration zone code. This timer takes effect
only if the number of retained registration zones is not 0. This parameter is used
for registration-zone-based registration. The parameter values 0 to 7 indicate 1,
2, 5, 10, 20, 30, 45, and 60 minutes, respectively. To reduce the impact on
paging when the number of retained registration zones is greater than 1, you are
advised to set this timer to a small value, for example, 1. If the number of
retained registration zones is 1, this timer does not take much effect. For details,
see the description of zoneTimer in 3GPP TS 36.331.
Table 2 Related parameters

Parameter Description

Power-down Indicates whether a CDMA2000 1xRTT UE needs to initiate registration during


registration include
indicator power-off. For details, see the description of powerDownReg-r9 in 3GPP TS
36.331.

AC barring information Indicates whether access class barring for CDMA2000 1xRTT is configured.
configure indicator

Persistence value for Indicates the persistence value for common call access overload classes 0 to 9
access overload
classes 0 to 9 and determines the threshold P for performing continuity checks by UEs. A UE
must pass the continuity check to access the network. For details, see IS95A-C6.
In each timeslot after the RS, the UE performs a pseudorandom continuity check
based on parameter P. During each timeslot, a random value RP ranging from 0
to 1 is generated. If RP is less than P, the UE passes the check. Then, the UE
sends the first probe of the access sequence in the timeslot. If the check fails, the
UE needs to perform the check in the next timeslot. For details, see the
description of ac-Barring0to9-r9 in 3GPP TS 36.331.

Persistence value for Indicates the persistence value for access overload class 10. The persistence
access overload class
10 values for emergency call access overload classes 10 to 15 determine the
threshold P for performing continuity checks by UEs. For details, see the
description of ac-Barring10-r9 in 3GPP TS 36.331.

Persistence value for Indicates the persistence value for access overload class 11. The persistence
access overload class
11 values for emergency call access overload classes 10 to 15 determine the
threshold P for performing continuity checks by UEs. For details, see the
description of ac-Barring11-r9 in 3GPP TS 36.331.

Persistence value for Indicates the persistence value for access overload class 12. The persistence
access overload class
12 values for emergency call access overload classes 10 to 15 determine the
threshold P for performing continuity checks by UEs. For details, see the
description of ac-Barring12-r9 in 3GPP TS 36.331.

Persistence value for Indicates the persistence value for access overload class 13. The persistence
access overload class
13 values for emergency call access overload classes 10 to 15 determine the
threshold P for performing continuity checks by UEs. For details, see the
description of ac-Barring13-r9 in 3GPP TS 36.331.

Persistence value for Indicates the persistence value for access overload class 14. The persistence
access overload class
14 values for emergency call access overload classes 10 to 15 determine the
threshold P for performing continuity checks by UEs. For details, see the
description of ac-Barring14-r9 in 3GPP TS 36.331.

Persistence value for Indicates the persistence value for access overload class 15. The persistence
access overload class
15 values for emergency call access overload classes 10 to 15 determine the
threshold P for performing continuity checks by UEs. For details, see the
Table 2 Related parameters

Parameter Description

description of ac-Barring15-r9 in 3GPP TS 36.331.

Persistence Modifier Indicates the persistence amendment value sent in access attempt messages. In
For Access barring
factor for message the access attempt indicated by the message, the value of (P x 2 - MSG_PSIST)
transmissions and RP will be compared. For details, see ac-BarringMsg-r9 in 3GPP TS 36.331.

Persistence modifier Indicates the autonomously registered persistence amendment value for the
For Access barring
factor for registrations access barring factor. For details, see ac-BarringReg-r9 in 3GPP TS 36.331.

Persistence modifier Indicates the persistence value for emergency calls by UEs belonging to access
For Access barring
factor for emergency overload classes 0 to 9. If PSISTEMGINCL is set to 0, AcBarEmg is invalid. If
service PSISTEMGINCL is set to 1, set AcBarEmg based on whether UEs belonging to
access overload classes 0 to 9 are allowed to send emergency call requests on
the access channel. If allowed, set AcBarEmg to 0. If not allowed, set
AcBarEmg to 7. For details, see ac-BarringEmg-r9 in 3GPP TS 36.331.

Protocol revision level Indicates whether to configure the latest CDMA2000 1xRTT protocol revision
include indicator
supported by the eNodeB. For details about this parameter, see 3GPP2 C.S0097.

Protocol revision level Indicates the latest CDMA2000 1xRTT protocol revision supported by the
eNodeB. If the latest protocol revision is required by some features, change the
protocol revision as required. For details about this parameter, see 3GPP2
C.S0097.

Min protocol revision Indicates whether to configure the CDMA2000 1xRTT minimum protocol
level include indicator
revision level. For details about this parameter, see 3GPP2 C.S0097.

Min protocol revision Indicates the minimum protocol revision that UEs need to support to access the
level
system. For details about this parameter, see 3GPP2 C.S0097.

Authentication include Indicates whether to include authentication. For details about this parameter, see
indicator
3GPP2 C.S0097.

Authentication indicator Indicates whether to perform authentication. For details about this parameter, see
3GPP2 C.S0097.

Max number of Indicates whether to configure the maximum number of alternative service
alternative service
options include options. For details about this parameter, see 3GPP2 C.S0097.
indicator

Max number of Indicates the maximum number of alternative service options that can be
alternative srvice
options included in the Origination Message (ORM) and Page Response Message
(PRM). This parameter is valid for UEs with MOB_P_REV greater than or
Table 2 Related parameters

Parameter Description

equal to 6. For details about this parameter, see 3GPP2 C.S0097.

Preferred ACH MS ID Indicates whether to configure the preferred access channel MS ID type. For
type include indicator
details about this parameter, see 3GPP2 C.S0097.

Preferred ACH MS ID Indicates the preferred access channel MS ID type. For details about this
type
parameter, see 3GPP2 C.S0097.

Mobile country code Indicates whether the mobile country code (MCC) is delivered. If this parameter
include indicator
is set to CFG, the MCC is delivered at CDMA2000 1xRTT parameter
registration. For details about this parameter, see 3GPP2 C.S0097.

Mobile network code Indicates whether the mobile network code (MNC) is delivered. If this
send indicator
parameter is set to CFG, the MNC is delivered at CDMA2000 1xRTT parameter
registration. For details about this parameter, see 3GPP2 C.S0097.

IMSI_T supported Indicates whether IMSI_Ts are supported. For details about this parameter, see
include indicator
3GPP2 C.S0097.

IMSI_T support Indicates whether 15-digit IMSI_T are supported. If IMSI_T_SUPPORTED in


indicator
ESPM is set to 1 and the IMSI_T is correctly set in the UE, the UE reports
IMSI_T. If IMSI_T_SUPPORTED is set to 1 but the IMSI_T is not set in the
UE, the UE may report an incorrect IMSI. When you modify this parameter,
ensure that the true IMSI is correctly set for the UE. For details about this
parameter, see 3GPP2 C.S0097.

Forword power control Indicates whether power control parameters are carried by UEs from the LTE
parameter of FCH
include indicator network to the CDMA2000 1xRTT network. For details about this parameter,
see 3GPP2 C.S0097.

RC3 initial setpoint of Indicates the initial setpoint for RC3 used for UE-performed forward FCH outer-
forword power control
parameter loop power control. For details about this parameter, see 3GPP2 C.S0097.

RC4 initial setpoint of Indicates the initial setpoint for RC4 used for UE-performed forward FCH outer-
forword power control
parameter loop power control. For details about this parameter, see 3GPP2 C.S0097.

RC5 initial setpoint of Indicates the initial setpoint for RC5 used for UE-performed forward FCH outer-
forword power control
parameter loop power control. For details about this parameter, see 3GPP2 C.S0097.

RC11 initial setpoint of Indicates the initial setpoint for RC11 used for UE-performed forward channel
forword power control
parameter outer-loop power control. For details about this parameter, see 3GPP2 C.S0097.

RC12 initial setpoint of Indicates the initial setpoint for RC12 used for UE-performed forward FCH
forword power control
Table 2 Related parameters

Parameter Description

parameter outer-loop power control. For details about this parameter, see 3GPP2 C.S0097.

Pilot PN sequence Indicates whether to configure the pilot PN sequence offset index increment. For
offset index increment
include indicator details about this parameter, see 3GPP2 C.S0097.

Pilot PN sequence Indicates the pilot pseudo noise (PN) sequence offset index increment. The value
offset index increment
of this parameter is a greatest common divisor for pilot PN sequence offsets of
all adjacent base stations. For a given pilot PN sequence offset index increment,
the number of PNs available in the system is 512 divided by the value of this
parameter. For details about this parameter, see 3GPP2 C.S0097.

Leap seconds include Indicates whether the leap second is included in a pre-registration message.
indicator
When this parameter is set to CFG, the eNodeB automatically calculates the leap
second value based on the system time.

Time zone include Indicates whether to configure the time zone. If this parameter is set to CFG, the
indicator
eNodeB uses the DST information configured by running the SET TZ command.
For details, see the description of LTM_OFF_Included in 3GPP2 C.S0097.

Daylight flag include Indicates whether to configure the daylight saving time (DST) information. If
indicator
this parameter is set to CFG, the eNodeB uses the DST information configured
by running the SET TZ command. For details, see the description of
DAYLT_Included in 3GPP2 C.S0097.

GCSNA layer2 Indicates whether to configure the GCSNA L2 acknowledge timer. If a timer
acknowledge timer
include indicator length needs to be specified, set this parameter to CFG. For details about this
parameter, see 3GPP2 C.S0097.

GCSNA layer2 Indicates the length of the GCSNA L2 timer for responding to the
acknowledge timer
GCSNA1xCircuitService message. It is recommended that this parameter be set
to a value smaller than the value of GcsnaSeqContextTimer. For details, see the
description of GCSNAL2AckTimer in 3GPP2 C.S0097.

GCSNA sequence Indicates whether to configure the GCSNA sequence context timer. If a timer
context timer include
indicator length needs to be specified, set this parameter to CFG. For details about this
parameter, see 3GPP2 C.S0097.

GCSNA sequence Indicates the length of the timer for retransmitting the GCSNA1xCircuitService
context timer
message. After the timer expires, the message will not be retransmitted. It is
recommended that this parameter be set to a value greater than the value of
GcsnaL2AckTimer. For details, see the description of
GCSNASequenceContextTimer in 3GPP2 C.S0097.
5.7.1.6.3.12 Cdma2000BandClass
+-NE
+-eNodeBFunction
+-Cell
+-Cdma2000BandClass
+-Cdma2000BcSCellOp[0~6]
+-Cdma2000Nfreq[0~16]

Description

A Cdma2000BandClass MO consists of the parameters related to a CDMA2000 band class. It is


contained in system information block type 8 (SIB8) and used in measurement control for
handover and reselection to a CDMA2000 neighboring cell.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Possible children:
Cdma2000BcSCellOp[0~6];Cdma2000Nfreq[0~16]

Relation with the Cell MO:


- A maximum of 16 Cdma2000BandClass MOs can be configured for each cell.
Relation with the Cdma2000Nfreq MO:
- Before adding a Cdma2000Nfreq MO, ensure that the associated Cdma2000BandClass
MO has been configured.
Relation with the EutranInterNFreq MO:
- If CellReselPriorityCfgInd in EutranInterNFreq MO is set to CFG, and if
Cdma20001XrttCellReselInd in Cdma2000BandClass MO is set to CFG,
Cdma20001XrttCellReselPri in Cdma2000BandClass MO cannot be set same as
CellReselPriority in EutranInterNFreq MO for each cell, and if
Cdma2000HrpdCellReselInd in Cdma2000BandClass MO is set to CFG,
Cdma2000HrpdCellReselPri in Cdma2000BandClass MO cannot be set same as
CellReselPriority in EutranInterNFreq MO for each cell.
Relation with the CellResel MO:
- If Cdma20001XrttCellReselInd in Cdma2000BandClass MO is set to CFG,
Cdma20001XrttCellReselPri in Cdma2000BandClass MO cannot be set same as
CellReselPriority in CellResel MO for each cell,and if Cdma2000HrpdCellReselInd in
Cdma2000BandClass MO is set to CFG, Cdma2000HrpdCellReselPri in
Cdma2000BandClass MO cannot be set same as CellReselPriority in CellResel MO for each
cell.
Relation with the UtranNFreq MO:
- If CellReselPriorityCfgInd in UtranNFreq MO is set to CFG, and if
Cdma20001XrttCellReselInd in Cdma2000BandClass MO is set to CFG,
Cdma20001XrttCellReselPri in Cdma2000BandClass MO cannot be set same as
CellReselPriority in UtranNFreq MO for each cell, and if Cdma2000HrpdCellReselInd in
Cdma2000BandClass MO is set to CFG, Cdma2000HrpdCellReselPri in
Cdma2000BandClass MO cannot be set same as CellReselPriority in UtranNFreq MO for
each cell.
Relation with the GeranNfreqGroup MO:
- If CellReselPriorityCfgInd in GeranNfreqGroup MO is set to CFG, and if
Cdma20001XrttCellReselInd in Cdma2000BandClass MO is set to CFG,
Cdma20001XrttCellReselPri in Cdma2000BandClass MO cannot be set same as
CellReselPriority in GeranNfreqGroup MO for each cell, and if
Cdma2000HrpdCellReselInd in Cdma2000BandClass MO is set to CFG,
Cdma2000HrpdCellReselPri in Cdma2000BandClass MO cannot be set same as
CellReselPriority in GeranNfreqGroup MO for each cell.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add the information about a CDMA2000 band class.
CDMA2000BANDCLAS
S

LST Use this command to list the parameters related to the CDMA2000 band class.
CDMA2000BANDCLAS
S

MOD Use this command to modify the configuration of a CDMA2000 band class.
CDMA2000BANDCLAS
S

RMV Use this command to remove the configuration of a CDMA2000 band class.
CDMA2000BANDCLAS
S
Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the cell ID of the local cell. It uniquely identifies a cell within an
eNodeB.

Band class Indicates the neighboring CDMA2000 band class. Signals on a frequency within
the band class can be obtained by UEs. For details, see the
BandclassCDMA2000 IE defined in 3GPP 36.331.

CDMA20001XRTT cell Indicates whether to configure cell reselection priorities for CDMA2000 1xRTT
reselection indicator
band class. If this parameter is set to NOT_CFG, the cell reselection priorities
are not delivered in the system information.

CDMA20001XRTT cell Indicates the absolute priority of the CDMA2000 1xRTT band class to be used
reselection priority
during cell reselection. The value 0 indicates the lowest priority. Frequencies
used for different RATs must be assigned different cell reselection priorities. The
information is contained in SIB8. For details, see 3GPP TS 36.331.

CDMA20001XRTT high Indicates the RX signal level required for a cell on a frequency in the higher-
priority threshold
priority CDMA2000 1xRTT band class to become a candidate for cell
reselection. After measurements are started for cells on a frequency in the band
class, a cell on the frequency can become a candidate for reselection only if the
RX signal level of the cell is higher than the value specified by this parameter
for a time-to-trigger. For details, see 3GPP TS 36.304 5.2.4.5.

CDMA20001XRTT Indicates the RX signal level required for a cell on a frequency in the lower-
lower priority threshold
priority CDMA2000 1xRTT band class to become a candidate for cell
reselection.
After measurements are started for cells on a frequency in the band class, a cell
on the frequency can become a candidate for reselection only if the RX signal
level of the cell is better than the value specified by this parameter for a time-to-
trigger. For details, see 3GPP TS 36.304 5.2.4.5.

CDMA2000HRPD cell Indicates whether to configure cell reselection priorities for CDMA2000 HRPD
reselection indicator
band class. If this parameter is set to NOT_CFG, the cell reselection priorities
are not delivered in the system information.

CDMA2000HRPD cell Indicates the absolute priority of the CDMA2000 HRPD band class to be used
reselection priority
during cell reselection. The value 0 indicates the lowest priority. Frequencies
used for different RATs must be assigned different cell reselection priorities. The
information is contained in SIB8. For details, see 3GPP TS 36.331.
Table 2 Related parameters

Parameter Description

CDMA2000HRPD high Indicates the RX signal level required for a cell on a frequency in the higher-
priority threshold
priority CDMA2000 HRPD band class to become a candidate for cell
reselection. After measurements are started for cells on a frequency in the band
class, a cell on the frequency can become a candidate for reselection only if the
RX signal level of the cell is higher than the value specified by this parameter
for a time-to-trigger. For details, see 3GPP TS 36.304 5.2.4.5.

CDMA2000HRPD lower Indicates the RX signal level required for a cell on a frequency in the lower-
priority threshold
priority CDMA2000 HRPD band class to become a candidate for cell
reselection.
After measurements are started for cells on a frequency in the band class, a cell
on the frequency can become a candidate for reselection only if the RX signal
level of the cell is lower than the value specified by this parameter for a time-to-
trigger. For details, see 3GPP TS 36.304 5.2.4.5.

5.7.1.6.3.13 Cdma2000BcSCellOp
+-NE
+-eNodeBFunction
+-Cell
+-Cdma2000BandClass
+-Cdma2000BcSCellOp

Description

The Cdma2000BcSCellOp MO defines cell reselection dedicated priorities based on the PLMN
of the local cell for the CDMA2000 1xRTT and CDMA2000 HRPD band class.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cdma2000BandClass

Relation with the CnOperator MO:


- CnOperatorID in a Cdma2000BcSCellOp MO must have been set in the associated
CnOperator MO.
Relation with the
EutranNFreqSCellOp,UtranNFreqSCellOp,GeranNFGroupSCellOp,EutranNFreqRanSha
re,UtranRanShare,GeranRanShare MOs:
- Cell reselection priorities based on operators of the local cell (which are specified in the
EutranNFreqSCellOp, UtranNFreqSCellOp, GeranNFGroupSCellOp, and
Cdma2000BcSCellOp MOs) cannot coexist with cell reselection priorities based on operators of
neighboring frequencies (which are specified in the EutranNFreqRanShare, UtranRanShare,
and GeranRanShare MOs).
Relation with the EutranNFreqSCellOp MO:
- Cell reselection priorities specified in the EutranNFreqSCellOp and
Cdma2000BcSCellOp MOs for the same operator cannot be the same.
Relation with the GeranNFGroupSCellOp MO:
- Cell reselection priorities specified in the GeranNFGroupSCellOp and
Cdma2000BcSCellOp MOs for the same operator cannot be the same.
Relation with the UtranNFreqSCellOp MO:
- Cell reselection priorities specified in the UtranNFreqSCellOp and Cdma2000BcSCellOp
MOs for the same operator cannot be the same.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add an operator-specific configuration for the CDMA2000
CDMA2000BCSCELLO
P band class.

LST Use this command to list operator-specific configurations for the CDMA2000
CDMA2000BCSCELLO
P band class.

MOD Use this command to modify operator-specific configurations for the


CDMA2000BCSCELLO
P CDMA2000 band class.

RMV Use this command to remove an operator-specific configuration for the


CDMA2000BCSCELLO
P CDMA2000 band class.

Related Parameters
Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the cell ID of the local cell. It uniquely identifies a cell within an
eNodeB.

Band class Indicates the neighboring CDMA2000 band class. For details, see the
BandclassCDMA2000 IE defined in 3GPP 36.331.

Cn operator ID Indicates the ID of the operator.

CDMA2000 1xRTT Indicates whether to configure a dedicated cell-reselection priority based on the
dedicated priority
configure indicator PLMN ID of the local cell for the CDMA2000 1xRTT band class.

CDMA2000 1xRTT Cell Indicates the dedicated cell reselection priority for a CDMA2000 1xRTT band
Reselection Dedicated
Priority class based on the PLMN ID of the local cell. The value 0 indicates the lowest
priority. If the related SPID configuration is specified, set this priority to the one
specified in the SPID configuration. If no related SPID configuration is specified
but this parameter is set, the eNodeB delivers the cell reselection priorities of all
PLMNs supported by a UE by using the IE idleModeMobilityControlInfo in an
RRC Connection Release message to the UE. If no related SPID configuration is
specified and this parameter is not set, a UE uses the cell reselection priority of
the CDMA2000 band class, which is broadcast in the system information.

CDMA2000 HRPD Indicates whether to configure dedicated a cell-reselection priority based on the
dedicated priority
configure indicator PLMN ID of the local cell for the CDMA2000 HRPD band class.

CDMA2000 HRPD Cell Indicates the dedicated cell reselection priority for a CDMA2000 HRPD band
Reselection Dedicated
Priority class based on the PLMN ID of the local cell. The value 0 indicates the lowest
priority. If the related SPID configuration is specified, set this priority to the one
specified in the SPID configuration. If no related SPID configuration is specified
but this parameter is set, the eNodeB delivers the cell reselection priorities of all
PLMNs supported by a UE by using the IE idleModeMobilityControlInfo in an
RRC Connection Release message to the UE. If no related SPID configuration is
specified and this parameter is not set, a UE uses the cell reselection priority of
the CDMA2000 band class, which is broadcast in the system information.

5.7.1.6.3.14 Cdma2000HrpdExtCell
+-NE
+-eNodeBFunction
+-Cdma2000HrpdExtCell

Description

A Cdma2000HrpdExtCell MO consists of the parameters related to an external CDMA2000


HRPD cell. It provides the common information about neighboring CDMA2000 HRPD cells.
For details, see 3GPP TS 36.331.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Relation with the Cdma2000HrpdNCell MO:


- Before adding a Cdma2000HrpdNCell MO, ensure that the associated
Cdma2000HrpdExtCell MO has been configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add an external CDMA2000 HRPD cell.


CDMA2000HRPDEXTC
ELL

LST Use this command to list the parameters related to the external CDMA2000
CDMA2000HRPDEXTC
ELL HRPD cell.

MOD Use this command to modify an external CDMA2000 HRPD cell.


CDMA2000HRPDEXTC
ELL

RMV Use this command to remove an external CDMA2000 HRPD cell.


CDMA2000HRPDEXTC
ELL

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

SectorID104 Indicates the value for SectorID104 of the external CDMA2000 high rate packet
data (HRPD) cell. The value begins with 0x followed by a maximum of 26
hexadecimal characters (0 to 9, and A to F), for example, 0x123A. The
hexadecimal character string cannot begin with 0, for example, the value cannot
be 0x0123A. SECTORID128 uniquely identifies an EV-DO sector in the global
scope and is comprised of SECTORID104 and SECTORID24. SECTORID104
uniquely identifies a subnetwork in the global scope and SECTORID24
uniquely identifies an EV-DO sector in the subnetwork.

SectorID24 Indicates the value for SectorID24 of the external CDMA2000 high rate packet
data (HRPD) cell. The value begins with 0x followed by a maximum of six
hexadecimal characters (0 to 9, and A to F), for example, 0x123A. The
hexadecimal character string cannot begin with 0, for example, the value cannot
be 0x0123A. SECTORID128 uniquely identifies an EV-DO sector in the global
scope and is comprised of SECTORID104 and SECTORID24. SECTORID104
uniquely identifies a subnetwork in the global scope and SECTORID24
uniquely identifies an EV-DO sector in the subnetwork.

Band class Indicates the band class on which the external CDMA2000 high rate packet data
(HRPD) cell operates. For details about this parameter, see 3GPP TS 36.331.

Frequency Indicates the frequency on which the external CDMA2000 high rate packet data
(HRPD) cell operates. For details about this parameter, see 3GPP TS 36.331.

Mobile country code Indicates the mobile country code (MCC) of the external CDMA2000 high rate
packet data (HRPD) cell.
A public land mobile network (PLMN) ID is comprised of an MCC and a
mobile network code (MNC).
The MCC consists of three digits.
The MNC consists of two or three digits.
For example, if the MCC is 123 and the MNC is 45, the PLMN ID is 12345.

Mobile network code Indicates the mobile network code (MNC) of the external CDMA2000 high rate
packet data (HRPD) cell.
A public land mobile network (PLMN) ID is comprised of a mobile country
code (MCC) and an MNC.
The MCC consists of three digits.
The MNC consists of two or three digits.
For example, if the MCC is 123 and the MNC is 45, the PLMN ID is 12345.

Physical cell ID Indicates the pseudo noise (PN) sequence number of the external CDMA2000
high rate packet data (HRPD) cell. This number is used as the physical cell ID of
Table 2 Related parameters

Parameter Description

the cell. For details, see C.S0005 PILOT_PN.

Cell name Indicates the name of the external CDMA2000 HRPD cell.

Control Mode Indicates the control policy on ANR-related MOs, which can be defined by the
user or be based on the automatic neighbor relation (ANR) algorithm. When this
parameter is set to MANUAL_MODE, the ANR-related MOs can be modified
or removed by only the user. A failure message is displayed when the user adds
an existing MO. When this parameter is set to AUTO_MODE, the ANR-related
MOs can be modified or removed by the user or based on the ANR algorithm.
The MO removal is successful even if the MO does not exist. An MO can be
added both by the user and based on the ANR algorithm. If an existing MO is to
be added, the MO is modified when the user performs the addition, but it cannot
be added based on the ANR algorithm. When the ANR-related MOs are
automatically added based on the ANR algorithm, this parameter is set to
AUTO_MODE by default. When the ANR-related MOs are added by the user,
this parameter can be set to AUTO_MODE or MANUAL_MODE.

5.7.1.6.3.15 Cdma2000HrpdNCell
+-NE
+-eNodeBFunction
+-Cell
+-Cdma2000HrpdNCell

Description

A Cdma2000HrpdNCell MO consists of parameters related to a neighboring CDMA2000 HRPD


cell. The parameters are used for handover or reselection from an E-UTRAN cell to a
CDMA2000 HRPD cell.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the Cdma2000Nfreq MO:


- Before adding a Cdma2000HrpdNCell MO, ensure that the associated Cdma2000Nfreq
MO with the same LocalCellId, BandClass, and Frequency has been configured.
Relation with the Cell MO:
- A maximum of 32 Cdma2000HrpdNCell MOs can be configured for each cell.
Relation with the Cdma2000HrpdExtCell MO:
- Before adding a Cdma2000HrpdNCell MO, ensure that the associated
Cdma2000HrpdExtCell MO has been configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add the neighboring relation with a CDMA2000 HRPD
CDMA2000HRPDNCEL
L cell.

LST Use this command to list the parameters of the neighboring relation with the
CDMA2000HRPDNCEL
L CDMA2000 HRPD cell.

MOD Use this command to modify the configuration of the neighboring relation with a
CDMA2000HRPDNCEL
L CDMA2000 HRPD cell.

RMV Use this command to remove the neighboring relation with a CDMA2000
CDMA2000HRPDNCEL
L HRPD cell.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the ID of the local cell. It uniquely identifies a cell within an eNodeB.

SectorID104 Indicates the value for SectorID104 of the neighboring CDMA2000 high rate
Table 2 Related parameters

Parameter Description

packet data (HRPD) cell. The value begins with 0x followed by a maximum of
26 hexadecimal characters (0 to 9, and A to F), for example, 0x123A. The
hexadecimal character string cannot begin with 0, for example, the value cannot
be 0x0123A. SECTORID128 uniquely identifies an EV-DO sector in the global
scope and is comprised of SECTORID104 and SECTORID24. SECTORID104
uniquely identifies a subnetwork in the global scope and SECTORID24
uniquely identifies an EV-DO sector in the subnetwork.

SectorID24 Indicates the value for SectorID24 of the neighboring CDMA2000 high rate
packet data (HRPD) cell. The value begins with 0x followed by a maximum of
six hexadecimal characters (0 to 9, and A to F), for example, 0x123A. The
hexadecimal character string cannot begin with 0, for example, the value cannot
be 0x0123A. SECTORID128 uniquely identifies an EV-DO sector in the global
scope and is comprised of SECTORID104 and SECTORID24. SECTORID104
uniquely identifies a subnetwork in the global scope and SECTORID24
uniquely identifies an EV-DO sector in the subnetwork.

Band class Indicates the band class on which the neighboring CDMA2000 high rate packet
data (HRPD) cell operates. For details about this parameter, see 3GPP TS
36.331.

Frequency Indicates the frequency on which the neighboring CDMA2000 high rate packet
data (HRPD) cell operates. For details about this parameter, see 3GPP TS
36.331.

No handover indicator Indicates whether to permit or prohibit handovers from the local cell to the
neighboring cell.

No remove indicator Indicates whether to permit or prohibit removal of the neighboring relationship
by ANR.

ANR flag Indicates whether ANR with neighboring CDMA2000 high rate packet data
(HRPD) cells is enabled.

Local cell name Indicates the name of the local cell.

Neighbour cell name Indicates the name of the neighboring CDMA2000 HRPD cell.

Control Mode Indicates the control policy on ANR-related MOs, which can be defined by the
user or be based on the automatic neighbor relation (ANR) algorithm. When this
parameter is set to MANUAL_MODE, the ANR-related MOs can be modified
or removed by only the user. A failure message is displayed when the user adds
an existing MO. When this parameter is set to AUTO_MODE, the ANR-related
MOs can be modified or removed by the user or based on the ANR algorithm.
Table 2 Related parameters

Parameter Description

The MO removal is successful even if the MO does not exist. An MO can be


added both by the user and based on the ANR algorithm. If an existing MO is to
be added, the MO is modified when the user performs the addition, but it cannot
be added based on the ANR algorithm. When the ANR-related MOs are
automatically added based on the ANR algorithm, this parameter is set to
AUTO_MODE by default. When the ANR-related MOs are added by the user,
this parameter can be set to AUTO_MODE or MANUAL_MODE.

5.7.1.6.3.16 Cdma2000HrpdPreReg
+-NE
+-eNodeBFunction
+-Cell
+-Cdma2000HrpdPreReg

Description

A Cdma2000HrpdPreReg MO consists of the parameters related to CDMA2000 HRPD pre-


registration. The parameters are delivered in SIB8. After an HRPD-capable UE receives
information about eHRPD pre-registration in SIB8, the UE can initiate eHRPD pre-registration.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the Cell MO:


- A maximum of 1 Cdma2000HrpdPreReg MOs can be configured for each cell.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD Use this command to add the neighboring relation with a CDMA2000 HRPD
CDMA2000HRPDPRE
REG cell.

LST Use this command to list the configuration of the neighboring relation with the
CDMA2000HRPDPRE
REG CDMA2000 HRPD cell.

MOD Use this command to modify the configuration of the neighboring relation with a
CDMA2000HRPDPRE
REG CDMA2000 HRPD cell.

RMV Use this command to remove the neighboring relation with a CDMA2000
CDMA2000HRPDPRE
REG HRPD cell.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the ID of the local cell. It uniquely identifies a cell within an eNodeB.

Mobile country code Indicates the mobile country code (MCC) of the CDMA2000 high rate packet
data (HRPD) pre-registration parameter.
A public land mobile network (PLMN) ID is comprised of an MCC and a
mobile network code (MNC).
The MCC consists of three digits.
The MNC consists of two or three digits.
For example, if the MCC is 123 and the MNC is 45, the PLMN ID is 12345.

Mobile network code Indicates the mobile network code (MNC) of the CDMA2000 high rate packet
data (HRPD) pre-registration parameter.
A public land mobile network (PLMN) ID is comprised of a mobile country
code (MCC) and an MNC.
The MCC consists of three digits.
The MNC consists of two or three digits.
For example, if the MCC is 123 and the MNC is 45, the PLMN ID is 12345.

SIB8 Pre-registration Indicates whether a UE without valid pre-registration is allowed to initiate high
allowed indicator
Table 2 Related parameters

Parameter Description

rate packet data (HRPD) pre-registration. If this parameter is set to


BOOLEAN_TRUE, the UE is allowed to initiate the pre-registration. If this
parameter is set to BOOLEAN_FALSE, the UE is not allowed to initiate the pre-
registration. For details about this parameter, see 3GPP TS 36.331.

PreRegistrationInfoHRP Indicates whether the measurement configuration pre-registration parameter is


D configure indicator in
MeasConfig configured.

Pre-registration allowed Indicates whether measurement configuration pre-registration is allowed.


indicator in MeasConfig

Pre-registration zone ID Indicates the ID of the pre-registration CDMA2000 HRPD zone. This parameter
is used to control the re-registration of the UE and is valid only when pre-
registration is allowed. For details about this parameter, see 3GPP TS 36.331.

Secondary pre- Indicates whether the secondary pre-registration zone ID 0 is configured. If this
registration zone ID 0
configure indicator parameter is set to CFG, the secondary pre-registration zone ID 0 exists. If this
parameter is set to NOT_CFG, the secondary pre-registration zone ID 0 does not
exist. For details about this parameter, see 3GPP TS 36.331.

Secondary pre- Indicates the secondary pre-registration zone ID 0. This parameter is used to
registration zone ID 0
control the re-registration of the UE. For details about this parameter, see 3GPP
TS 36.331.

Secondary pre- Indicates whether the secondary pre-registration zone ID 1 is configured. If this
registration zone ID 1
configure indicator parameter is set to CFG, the secondary pre-registration zone ID 1 exists. If this
parameter is set to NOT_CFG, the secondary pre-registration zone ID 1 does not
exist. For details about this parameter, see 3GPP TS 36.331.

Secondary pre- Indicates the secondary pre-registration zone ID 1. This parameter is used to
registration zone ID 1
control the re-registration of the UE. For details about this parameter, see 3GPP
TS 36.331.

5.7.1.6.3.17 Cdma2000HrpdRefCell
+-NE
+-eNodeBFunction
+-Cell
+-Cdma2000HrpdRefCell
Description

A Cdma2000HrpdRefCell MO consists of parameters related to a CDMA2000 HRPD reference


cell.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the Cell MO:


- A maximum of 6 Cdma2000HrpdRefCell MOs can be configured for each cell.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add the neighboring relation with a CDMA2000 HRPD
CDMA2000HRPDREF
CELL cell.

LST Use this command to list the parameters of the neighboring relation with the
CDMA2000HRPDREF
CELL CDMA2000 HRPD cell.

MOD Use this command to modify the configuration of the neighboring relation with a
CDMA2000HRPDREF
CELL CDMA2000 HRPD cell.

RMV Use this command to remove the neighboring relation with a CDMA2000
CDMA2000HRPDREF
CELL HRPD cell.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Local cell ID Indicates the ID of the local cell. It uniquely identifies a cell within an eNodeB.

Mobile country code Indicates the mobile country code (MCC) of the reference CDMA2000 high rate
packet data (HRPD) cell.
A public land mobile network (PLMN) ID is comprised of an MCC and a
mobile network code (MNC).
The MCC consists of three digits.
The MNC consists of two or three digits.
For example, if the MCC is 123 and the MNC is 45, the PLMN ID is 12345.

Mobile network code Indicates the mobile network code (MNC) of the reference CDMA2000 high
rate packet data (HRPD) cell.
A public land mobile network (PLMN) ID is comprised of a mobile country
code (MCC) and an MNC.
The MCC consists of three digits.
The MNC consists of two or three digits.
For example, if the MCC is 123 and the MNC is 45, the PLMN ID is 12345.

SectorID104 Indicates the value for SectorID104 of the reference CDMA2000 high rate
packet data (HRPD) cell. The value begins with 0x followed by a maximum of
26 hexadecimal characters (0 to 9, and A to F), for example, 0x123A. The
hexadecimal character string cannot begin with 0, for example, the value cannot
be 0x0123A. SECTORID128 uniquely identifies an EV-DO sector in the global
scope and is comprised of SECTORID104 and SECTORID24. SECTORID104
uniquely identifies a subnetwork in the global scope and SECTORID24
uniquely identifies an EV-DO sector in the subnetwork. For details, see
C.S0024.

SectorID24 Indicates the value for SectorID24 of the reference CDMA2000 high rate packet
data (HRPD) cell. The value begins with 0x followed by a maximum of six
hexadecimal characters (0 to 9, and A to F), for example, 0x123A. The
hexadecimal character string cannot begin with 0, for example, the value cannot
be 0x0123A. SECTORID128 uniquely identifies an EV-DO sector in the global
scope and is comprised of SECTORID104 and SECTORID24. SECTORID104
uniquely identifies a subnetwork in the global scope and SECTORID24
uniquely identifies an EV-DO sector in the subnetwork. For details, see
C.S0024.

Selected ratio Indicates the selection ratio of the reference CDMA2000 high rate packet data
(HRPD) cell that a UE in the E-UTRAN cell can pre-register at. An E-UTRAN
cell may overlap multiple CDMA2000 HRPD cells, for example, when three E-
UTRAN sectors and six CDMA2000 HRPD sectors cover the same area.
Therefore, multiple CDMA2000 HRPD sector IDs can be specified for an E-
Table 2 Related parameters

Parameter Description

UTRAN cell, with each CDMA2000 HRPD sector ID configured with a


selection ratio. During UE pre-registration, CDMA2000 HRPD sector IDs are
selected based on historical selection ratios. Considering the cellular network
structure, a maximum of six CDMA2000 HRPD sector IDs can be configured
for a UE in the E-UTRAN cell.

5.7.1.6.3.18 Cdma2000Nfreq
+-NE
+-eNodeBFunction
+-Cell
+-Cdma2000BandClass
+-Cdma2000Nfreq

Description

A Cdma2000Nfreq MO consists of the parameters about a CDMA2000 frequency. The


parameters are mainly used for handover and reselection. For details, see 3GPP TS 36.331.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cdma2000BandClass

Relation with the Cell MO:


- A maximum of 32 Cdma2000Nfreq MOs can be configured for each cell.
Relation with the Cdma2000Nfreq MO:
- A maximum of 16 Cdma2000Nfreq MOs can be configured for each
Cdma2000BandClass.
Relation with the Cdma2000HrpdNCell MO:
- Before adding a Cdma2000HrpdNCell MO, ensure that the associated Cdma2000Nfreq
MO with the same LocalCellId, BandClass, and Frequency has been configured.
Relation with the Cdma20001XrttNCell MO:
- Before adding a Cdma20001XrttNCell MO, ensure that the associated Cdma2000Nfreq
MO with the same LocalCellId, BandClass, and Frequency has been configured.
Relation with the Cdma2000BandClass MO:
- Before adding a Cdma2000Nfreq MO, ensure that the associated Cdma2000BandClass
MO has been configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add a neighboring CDMA2000 frequency.


CDMA2000NFREQ

LST Use this command to list the parameters related to the neighboring CDMA2000
CDMA2000NFREQ
frequency.

MOD Use this command to modify the configuration of a neighboring CDMA2000


CDMA2000NFREQ
frequency.

RMV Use this command to remove a neighboring CDMA2000 frequency.


CDMA2000NFREQ

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the cell ID of the local cell. It uniquely identifies a cell within an
eNodeB.

Band class Indicates the neighboring CDMA2000 band class. Signals on a frequency within
the band class can be obtained by UEs. For details, see the
BandclassCDMA2000 IE defined in 3GPP 36.331 6.3.4.

Frequency Indicates the neighboring CDMA2000 frequency of the serving cell. For details,
see the IE CDMA2000-CarrierInfo in the 3GPP 36.331 6.3.4 protocol.
Table 2 Related parameters

Parameter Description

Frequency offset Indicates the frequency-specific offset of the local cell to the neighboring
CDMA2000 cell on the frequency. A larger value of this parameter leads to a
higher probability of triggering measurement reports. For details, see the Q-
OffsetRangeInterRAT IE defined in section 6.3.4 in 3GPP TS 36.331.

Search window size Indicates whether to set the size of the CDMA2000 search window. If this
configure indicator
parameter is set to NOT_CFG, the default size (8) is used.

Search window size Indicates the search window size to be used by the UE for searching for the
pilots of the neighboring CDMA2000 cells. For details, see the
MeasObjectCDMA2000 IE defined in 3GPP TS 36.331.

Frequency priority Indicates the priority or scaling factor of the CDMA2000 frequency.If the
eNodeB selects target frequencies based on frequency priorities in handovers to
CDMA2000, this parameter indicates the priority of the CDMA2000 frequency,
whose value has a positive correlation with the probability of the neighboring
CDMA2000 frequency being selected as the target frequency.If the eNodeB
selects target frequencies based on scaling factors in handovers to CDMA2000,
this parameter indicates the scaling factor of the CDMA2000 frequency, whose
value has a positive correlation with the probability of the neighboring
CDMA2000 frequency being selected as the target frequency.

5.7.1.6.3.19 Cell
+-NE
+-eNodeBFunction
+-Cell
+-CellDrxPara[1~1]
+-IntraFreqHoGroup[1~10]
+-InterRatHoCommGroup[1~10]
+-InterRatHoGeranGroup[1~10]
+-CellStandardQci[9~9]
+-InterFreqHoGroup[1~10]
+-CellDlpcPdschPa[1~1]
+-InterRatHoUtranGroup[1~10]
+-CellExtendedQci[0~60]
+-CellHoParaCfg[1~1]
+-CellUlCompAlgo[1~1]
+-CaMgtCfg[1~1]
+-CellDlCompAlgo[1~1]
+-GeranInterfArfcn[0~20]
+-eNBCellQciRsvdPara[9~9]
+-DistBasedHO[1~1]
+-CellUlpcDedic[1~1]
+-DrxParaGroup[4~10]
+-InterRatHoCdmaHrpdGroup[1~10]
+-InterRatHoCdma1xRttGroup[1~10]
+-RlfTimerConstGroup[0~10]
+-CSFallBackHo[1~1]
+-SfnCellBind[0~6]
+-CellReselCdma2000[0~1]
+-CellAcBar[1~1]
+-CellAccess[1~1]
+-CellReselUtran[0~1]
+-CellOp[0~6]
+-CellSiMap[1~1]
+-UeTimerConst[1~1]
+-CellSel[1~1]
+-CellResel[1~1]
+-CellReselGeran[0~1]
+-eUCellSectorEqm[0~8]
+-EuSectorEqmGroup[0~8]
+-CellUlpcComm[1~1]
+-TimeAlignmentTimer[1~1]
+-InterRatCellShutdown[1~1]
+-CellUlIcic[1~1]
+-Cdma20001XrttNCell[0~32]
+-CellMLB[1~1]
+-GeranInterfCfg[1~1]
+-EutranInterNFreq[0~8]
+-Cdma20001XrttPreReg[0~1]
+-EutranInterFreqNCell[0~64]
+-Cdma2000BandClass[0~16]
+-CellULIcicMcPara[1~1]
+-CellDlschAlgo[1~1]
+-CellBf[1~1]
+-CellChPwrCfg[1~1]
+-PDSCHCfg[1~1]
+-eNBCellRsvdPara[1~1]
+-CellUlschAlgo[1~1]
+-Cdma2000HrpdRefCell[0~6]
+-PHICHCfg[1~1]
+-CellAlgoSwitch[1~1]
+-UtranNFreq[0~16]
+-CellPdcchAlgo[1~1]
+-CellDlpcPhich[1~1]
+-CellLowPower[1~1]
+-IntraFreqBlkCell[0~32]
+-CellDlpcPdcch[1~1]
+-CellMro[1~1]
+-CellServiceDiffCfg[1~1]
+-Cdma2000HrpdPreReg[0~1]
+-CellNoAccessAlmPara[1~1]
+-CellRicAlgo[1~1]
+-RACHCfg[1~1]
+-CellRfShutdown[1~1]
+-UtranNCell[0~128]
+-CellRacThd[1~1]
+-EutranIntraFreqNCell[0~64]
+-GeranNcell[0~64]
+-CellPucchAlgo[1~1]
+-CellShutdown[1~1]
+-SRSCfg[1~1]
+-CellEicic[1~1]
+-CellSimuLoad[0~1]
+-CellDLIcicMcPara[1~1]
+-PUCCHCfg[1~1]
+-GeranNfreqGroup[0~16]
+-PCCHCfg[1~1]
+-CellDlIcic[1~1]
+-CellDlpcPdsch[1~1]
+-BcchCfg[1~1]
+-PUSCHCfg[1~1]
+-Cdma2000HrpdNCell[0~32]
+-InterFreqBlkCell[0~32]

Description

A Cell MO includes the cell ID and related radio frequency (RF) information. It is configured by
network planning engineers based on site requirements.

Effective Scenario
Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Possible children:
CellDrxPara[1~1];IntraFreqHoGroup[1~10];InterRatHoCommGroup[1~10];InterRatHoGeranGroup[1~10];Cell
StandardQci[9~9];InterFreqHoGroup[1~10];CellDlpcPdschPa[1~1];InterRatHoUtranGroup[1~10];CellExtended
Qci[0~60];CellHoParaCfg[1~1];CellUlCompAlgo[1~1];CaMgtCfg[1~1];CellDlCompAlgo[1~1];GeranInterfArfcn
[0~20];eNBCellQciRsvdPara[9~9];DistBasedHO[1~1];CellUlpcDedic[1~1];DrxParaGroup[4~10];InterRatHoC
dmaHrpdGroup[1~10];InterRatHoCdma1xRttGroup[1~10];RlfTimerConstGroup[0~10];CSFallBackHo[1~1];Sfn
CellBind[0~6];CellReselCdma2000[0~1];CellAcBar[1~1];CellAccess[1~1];CellReselUtran[0~1];CellOp[0~6];
CellSiMap[1~1];UeTimerConst[1~1];CellSel[1~1];CellResel[1~1];CellReselGeran[0~1];eUCellSectorEqm[0~
8];EuSectorEqmGroup[0~8];CellUlpcComm[1~1];TimeAlignmentTimer[1~1];InterRatCellShutdown[1~1];CellUl
Icic[1~1];Cdma20001XrttNCell[0~32];CellMLB[1~1];GeranInterfCfg[1~1];EutranInterNFreq[0~8];Cdma20001
XrttPreReg[0~1];EutranInterFreqNCell[0~64];Cdma2000BandClass[0~16];CellULIcicMcPara[1~1];CellDlschAl
go[1~1];CellBf[1~1];CellChPwrCfg[1~1];PDSCHCfg[1~1];eNBCellRsvdPara[1~1];CellUlschAlgo[1~1];Cdma
2000HrpdRefCell[0~6];PHICHCfg[1~1];CellAlgoSwitch[1~1];UtranNFreq[0~16];CellPdcchAlgo[1~1];CellDlpc
Phich[1~1];CellLowPower[1~1];IntraFreqBlkCell[0~32];CellDlpcPdcch[1~1];CellMro[1~1];CellServiceDiffCfg[
1~1];Cdma2000HrpdPreReg[0~1];CellNoAccessAlmPara[1~1];CellRicAlgo[1~1];RACHCfg[1~1];CellRfShutd
own[1~1];UtranNCell[0~128];CellRacThd[1~1];EutranIntraFreqNCell[0~64];GeranNcell[0~64];CellPucchAlg
o[1~1];CellShutdown[1~1];SRSCfg[1~1];CellEicic[1~1];CellSimuLoad[0~1];CellDLIcicMcPara[1~1];PUCCH
Cfg[1~1];GeranNfreqGroup[0~16];PCCHCfg[1~1];CellDlIcic[1~1];CellDlpcPdsch[1~1];BcchCfg[1~1];PUSC
HCfg[1~1];Cdma2000HrpdNCell[0~32];InterFreqBlkCell[0~32]

Relation with the DistBasedHO MO:


- If a Cell MO is configured, the DistBasedHO MO that references LocalCellId in the Cell
MO must exist.
Relation with the CellDlpcPdschPa MO:
- If a Cell MO is configured, the CellDlpcPdschPa MO that references LocalCellId in the
Cell MO must exist.
Relation with the CellDrxPara MO:
- If a Cell MO is configured, the CellDrxPara MO that references LocalCellId in the Cell
MO must exist.
Relation with the CellUlpcDedic MO:
- If a Cell MO is configured, the CellUlpcDedic MO that references LocalCellId in the Cell
MO must exist.
Relation with the CellStandardQci MO:
- If a Cell MO is configured, the number of CellStandardQci MOs that reference
LocalCellId in the Cell MO must be 9.
Relation with the eNBCellQciRsvdPara MO:
- If a Cell MO is configured, the number of eNBCellQciRsvdPara MOs that reference
LocalCellId in the Cell MO be 9.
Relation with the CellRicAlgo MO:
- If CellActiveState in a Cell MO is set to CELL_ACTIVE, FddTddInd is CELL_TDD
Model and DlBandWidth is CELL_BW_N25, RicAlgoSwitch in the CellRicAlgo must be set
OFF.
Relation with the CellRfShutdown MO:
- If CellActiveState in a Cell MO is set to CELL_ACTIVE, FddTddInd is CELL_TDD
Model and DlBandWidth is CELL_BW_N25, RfShutdownSwitch in the CellRfShutdown
must be set OFF.
Relation with the PUSCHCfg MO:
- The number of RB resources corresponding to the value of UlBandWidth in a Cell MO
must be greater than or equal to the value of HoppingOffset in the PUSCHCfg MO.
- If UlBandWidth is set to CELL_BW_N6(1.4M), the number of RB resources is 6.
- If UlBandWidth is set to CELL_BW_N15(3M), the number of RB resources is 15.
- If UlBandWidth is set to CELL_BW_N25(5M), the number of RB resources is 25.
- If UlBandWidth is set to CELL_BW_N50(10M), the number of RB resources is 50.
- If UlBandWidth is set to CELL_BW_N75(15M), the number of RB resources is 75.
- If UlBandWidth is set to CELL_BW_N100(20M), the number of RB resources is 100.
Relation with the CellPdcchAlgo,PHICHCfg MOs:
- If PhichDuration in the PHICHCfg MO is set to NORMAL, and PdcchSymNumSwitch in
the CellPdcchAlgo MO is set to OFF, InitPdcchSymNum in the CellPdcchAlgo MO cannot be
set to 1 if the cell bandwidth is 1.4 MHz.
- If PhichDuration in the PHICHCfg MO is set to NORMAL, InitPdcchSymNum in the
CellPdcchAlgo MO can not be set to 4 if the cell bandwidth is not 1.4 MHz.
- If PhichDuration in the PHICHCfg MO is set to EXTENDED, InitPdcchSymNum in the
CellPdcchAlgo MO can be set to 3 or 4 if the cell bandwidth is 1.4 MHz.
- If PhichDuration in the PHICHCfg MO is set to EXTENDED, InitPdcchSymNum in the
CellPdcchAlgo MO must be set to 3 when the cell bandwidth is not 1.4 MHz.
Relation with the CaGroupCell MO:
- LocalCellId in a CaGroupCell MO must have been set in the associated Cell MO.
- One Cell MO can be configured only as one CaGroupCell MO.
- DlBandWidth in the Cell MOs associated with a CaGroupCell MO must be set to
CELL_BW_N25, CELL_BW_N50, CELL_BW_N75, or CELL_BW_N100.
- CustomizedBandWidthCfgInd in the Cell MOs associated with a CaGroupCell MO must
be set to NOT_CFG.
- HighSpeedFlag in the Cell MOs associated with a CaGroupCell MO can be set only to
LOW_SPEED.
- UlCyclicPrefix or DlCyclicPrefix in the Cell MOs associated with a CaGroupCell MO
under the same CaGroup MO must be set to the same value.
- For two Cell MOs associated with a CaGroupCell MO under the same CaGroup MO, if the
spacing between their downlink center frequencies is less than their average downlink
bandwidth, the spacing must be the nominal channel spacing between contiguously aggregated
component carriers.
- For two Cell MOs associated with a CaGroupCell MO under the same CaGroup MO, if the
spacing between their uplink center frequencies is less than their average uplink bandwidth, the
spacing must be the nominal channel spacing between contiguously aggregated component
carriers.
- For two Cell MOs associated with a CaGroupCell MO under the same CaGroup MO, if
FddTddInd of one cell is set to CELL_TDD and SpecialSubframePatterns is set to SSP4,
FddTddInd of the other cell must be set to CELL_TDD and SpecialSubframePatterns must
not be set to SSP5, SSP6, SSP7, SSP8.
- If a FDD Cell MO is associated with the CaGroupCell MO, the MultiRruCellMode of this
cell cannot be set to SFN.
Relation with the CaGroup,CaGroupCell MOs:
- If CaGroupType in a CaGroup MO is set to FDD, the Cell MOs associated with the
CaGroupCell MO under this CaGroup MO must also work in CELL_FDD mode.
- If CaGroupType in a CaGroup MO is set to TDD_SAME_SA, FddTddInd in Cell MO
associated with a CaGroupCell MO under this CaGroup MO must be CELL_TDD,and
SubframeAssignment must be SA1 or SA2 at the same time.
- If CaGroupType in a CaGroup MO is set to TDD_SAME_SA, FddTddInd in Cell MO
associated with a CaGroupCell MO under this CaGroup MO must be CELL_TDD,and
SubframeAssignment of one cell must be SA1, SubframeAssignment of the other cell must be
SA2.
Relation with the CaGroupCell,EutranInterFreqNCell MOs:
- The two Cell MOs associated with a CaGroupCell MO under the same CaGroup MO must
have inter-frequency neighbor relationships with each other.
Relation with the SectorEqm,eUCellSectorEqm MOs:
- In a Cell MO, if FddTddInd is set to CELL_TDD and CellActiveState is set to
CELL_ACTIVE and MultiRruCellMode is not set to CELL_COMBINATION,
MPRU_AGGREGATION, the CrsPortNum value must be smaller than or equal to the number
of antennas specified by SECTOREQMANTENNA in the associated SECTOREQM MOs
corresponding to SectorEqmId.
Relation with the MimoAdaptiveParaCfg MO:
- If AirCellFlag in Cell MO is set to BOOLEAN_TRUE, MimoAdaptiveSwitch in
MimoAdaptiveParaCfg MO must be set to NO_ADAPTIVE.
Relation with the MimoAdaptiveParaCfg,CellAlgoSwitch MOs:
- If CellActiveState in a Cell MO is set to CELL_ACTIVE, EicicSwitch in CellAlgoSwitch
MO cannot be set to ON and MimoAdaptiveSwitch in MimoAdaptiveParaCfg MO cannot be
set to OC_ADAPTIVE at the same time.
Relation with the eUCellSectorEqm,EuSectorEqmGroup MOs:
- In a Cell MO, if FddTddInd is set to CELL_TDD and MultiRruCellFlag is set to
BOOLEAN_TRUE and MultiRruCellMode is set to MPRU_AGGREGATION, the number of
EuSectorEqmGroup plus the number of different values of SectorEqmRef between
eUCellSectorEqm and EuSectorEqmGroup must be less than 8.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE and MultiRruCellMode is set to
MPRU_AGGREGATION, the eUCellSectorEqm MO or EuSectorEqmGroup MO under this
Cell MO must have been configured.
- In a Cell MO, if FddTddInd is set to CELL_FDD and MultiRruCellFlag is set to
BOOLEAN_TRUE and MultiRruCellMode is set to MPRU_AGGREGATION, the number of
EuSectorEqmGroup plus the number of different values of SectorEqmRef between
eUCellSectorEqm and EuSectorEqmGroup must be less than 7.
- In a Cell MO, if FddTddInd is set to CELL_TDD and MultiRruCellFlag is set to
BOOLEAN_TRUE and MultiRruCellMode is set to MPRU_AGGREGATION, and
UlBandWidth is set to CELL_BW_N50, the total number of eUCellSectorEqm and
EuSectorEqmGroup cannot exceed one.
Relation with the EuSectorEqmGroup,SECTOREQM MOs:
- In a Cell MO, if FddTddInd is set to CELL_TDD, MultiRruCellFlag is set to
BOOLEAN_TRUE, MultiRruCellMode is set to MPRU_AGGREGATION and
CellActiveState is set to CELL_ACTIVE, the SECTOREQM MO corresponding to each
EuSectorEqmGroup MO under this Cell MO must be associated with two TX antennas and
two RX antennas.
- If CellActiveState and MultiRruCellMode in a Cell MO are set to CELL_ACTIVE and
MPRU_AGGREGATION, respectively, EuSectorEqmGroup MOs cannot be configured under
this Cell MO after the cell is activated. If an EuSectorEqmGroup MO has been configured
under this Cell MO before the cell is activated, the SECTOREQM MO associated with this
EuSectorEqmGroup MO must already exist. If only one SECTOREQM MO is associated with
the EuSectorEqmGroup MO, the association between the SECTOREQM MO and the
EuSectorEqmGroup MO cannot be removed after the cell is activated.
- In a Cell MO, if FddTddInd is set to CELL_FDD, MultiRruCellFlag is set to
BOOLEAN_TRUE, MultiRruCellMode is set to MPRU_AGGREGATION and
CellActiveState is set to CELL_ACTIVE, the SECTOREQM MO corresponding to each
EuSectorEqmGroup MO under this Cell MO must be associated with one TX antenna or two
TX antennas,one RX antenna or two RX antennas.
- In a Cell MO, ifMultiRruCellFlag is set to BOOLEAN_TRUE, MultiRruCellMode is set
to MPRU_AGGREGATION and CellActiveState is set to CELL_ACTIVE, the SECTOREQM
MO corresponding to each EuSectorEqmGroup MO under this Cell MO can only have antenna
of channel A or B.
Relation with the SECTOREQM,EuSectorEqmGroup MOs:
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, SectorEqmRef in each
EuSectorEqmGroup MO under this Cell MO must be unique.
Relation with the eUCellSectorEqm,SECTOREQM,RRU,RFU MOs:
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE and MultiRruCellFlag is set to
BOOLEAN_FALSE, a maximum of two RRU MOs or RFU MOs can be associated with an
SECTOREQM MO corresponding to an eUCellSectorEqm MO under this Cell MO.
Relation with the eUCellSectorEqm,SECTOREQM,RFU,RRUCHAIN MOs:
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, and the TT in RRUCHAIN
MOs where the RFU MOs associated with a SECTOREQM MO corresponding to an
eUCellSectorEqm MO under this Cell MO is not LOADBALANCE, these RRUCHAIN MOs
must be in the same subrack.
Relation with the eUCellSectorEqm,BASEBANDEQM,SECTOREQM,RRU,RRUCHAIN
MOs:
- If CellActiveState in a Cell MO is set to CELL_ACTIVE and BaseBandEqmId in an
eUCellSectorEqm MO under this Cell MO is not 255, the BBP MOs associated with the
BASEBANDEQM MOs corresponding to BaseBandEqmId and the RRUCHAIN MOs where
the RRU MOs associated with a SECTOREQM MO corresponding to an eUCellSectorEqm
MO under this Cell MO are configured must be in the same subrack.
Relation with the eUCellSectorEqm,BASEBANDEQM,SECTOREQM,RFU,RRUCHAIN
MOs:
- If CellActiveState in a Cell MO is set to CELL_ACTIVE and BaseBandEqmId in an
eUCellSectorEqm MO under this Cell MO is not 255, the BBP MOs associated with the
BASEBANDEQM MOs corresponding to BaseBandEqmId and the RRUCHAIN MOs where
the RFU MOs associated with a SECTOREQM MO corresponding to an eUCellSectorEqm
MO under this Cell MO are configured must be in the same subrack.
Relation with the CaGroupCell,eUCellSectorEqm,SECTOREQM,RRU,RRUCHAIN MOs:
- If CellActiveState in both Cell MOs corresponding to a CaGroupCell MO under the same
CaGroup MO are set to CELL_ACTIVE, the RRUCHAIN MOs where the RRU MOs
associated with SECTOREQM MOs corresponding to eUCellSectorEqm MOs under both Cell
MOs are configured must be in the same subrack.
Relation with the CaGroupCell,eUCellSectorEqm,SECTOREQM,RFU,RRUCHAIN MOs:
- If CellActiveState in both Cell MOs corresponding to a CaGroupCell MO under the same
CaGroup MO are set to CELL_ACTIVE, the RRUCHAIN MOs where the RFU MOs
associated with SECTOREQM MOs corresponding to eUCellSectorEqm MOs under both Cell
MOs are configured must be in the same subrack.
Relation with the eUCellSectorEqm,SECTOR,SECTOREQM MOs:
- If CellActiveState in a Cell MO is set to CELL_ACTIVE, each SECTOR MO
corresponding to an eUCellSectorEqm MO under this Cell MO must be configured and unique.
- If CellActiveState in a Cell MO is set to CELL_ACTIVE and multiple SECTOREQM
MOs are associated with a SECTOR MO corresponding to this Cell MO, only one of these
SECTOREQM MOs can be referenced by Cell MO.
Relation with the eUCellSectorEqm,CellAlgoSwitch,SECTOREQM MOs:
- Among all cells which use a same SECTOREQM,the number of cells which
CellActiveState in a Cell MO is set to CELL_ACTIVE and GLPwrShare in the
CellAlgoSwitch is set to ON must be less than 2.
Relation with the EuSectorEqmGroup,BASEBANDEQM MOs:
- If CellActiveState in a Cell MO is set to CELL_ACTIVE and BaseBandEqmId in an
EuSectorEqmGroup MO under this Cell MO is not 255, the BASEBANDEQM MO
corresponding to BaseBandEqmId must have been configured.
Relation with the EuSectorEqmGroup,BASEBANDEQM,BBP MOs:
- When CellActiveState in a Cell MO is set to CELL_ACTIVE: if FddTddInd is set to
CELL_FDD, TYPE and WM in all BBP MOs corresponding to an EuSectorEqmGroup MO
under this Cell MO must be set to LBBP and FDD; if FddTddInd is set to CELL_TDD, TYPE
in all BBP MOs specified by BaseBandEqmId in an EuSectorEqmGroup MO under this Cell
MO must be set to LBBP, and WM can not be set to FDD.
Relation with the EuSectorEqmGroup MO:
- In a Cell, the EuSectorEqmGroup can be configured only when MultiRruCellFlag is set
to BOOLEAN_TRUE and MultiRruCellMode is set to MPRU_AGGREGATION.
Relation with the EuSectorEqmGroup,SECTOREQM,RRU MOs:
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE and MultiRruCellMode is set to
MPRU_AGGREGATION, the RRUs specified in the SECTOREQM MO under the
EuSectorEqmGroup MO must be on the same RRU chain, and their positions on the chain
must be the same.
Relation with the eUCellSectorEqm,SECTOREQM,RRU,RRUCHAIN,BBP,RHUB MOs:
- When the LBBPs connected to a RRU specified in the SECTOREQM MO that corresponds
to the eUCellSectorEqm MO is set to ON, CPRICompression specified in the Cell must be set
to NORMAL_COMPRESSION.
Relation with the EuSectorEqmGroup,SECTOREQM,RRU,RRUCHAIN,BBP,RHUB
MOs:
- When the LBBPs connected to a RRU specified in the SECTOREQM MO that corresponds
to the EuSectorEqmGroup MO is set to ON, CPRICompression specified in the Cell must be
set to NORMAL_COMPRESSION.
Relation with the CellMLB MO:
- If FddTddInd is CELL_FDD Model, HotSpotUeMode in the CellMLB must be set OFF.
Relation with the eUCellSectorEqm,PDSCHCfg MOs:
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, MultiRruCellFlag is set to
BOOLEAN_TRUE and MultiRruCellMode is set to MPRU_AGGREGATION, the number of
valid values of ReferenceSignalPwr in eUCellSectorEqm must be not more than that of
ReferenceSignalPwr in PDSCHCfg.
Relation with the eUCellSectorEqm MO:
- In a Cell MO, if MultiRruCellFlag is set to BOOLEAN_TRUE, MultiRruCellMode is set
to SFN, and CellActiveState is set to CELL_ACTIVE, the number of associated
eUCellSectorEqm MOs with the same LocalCellId value must be smaller than or equal to the
value of SectorEqmNum in this Cell.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE and MultiRruCellFlag is set to
BOOLEAN_FALSE, an eUCellSectorEqm MO must be configured under this Cell MO and
only one eUCellSectorEqm MO can be configured.
- When CellActiveState and FddTddInd in a Cell MO are set to CELL_ACTIVE and
CELL_TDD, respectively, a minimum of one and a maximum of seven eUCellSectorEqm MOs
must be configured under the Cell MO if MultiRruCellFlag and MultiRruCellMode in the
Cell MO are set to BOOLEAN_TRUE and SFN, respectively.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, MultiRruCellFlag is set to
BOOLEAN_TRUE, and MultiRruCellMode is set to CELL_COMBINATION, the number of
eUCellSectorEqm MOs configured under this Cell MO ranges from 1 to 6.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, MultiRruCellFlag is set to
BOOLEAN_TRUE, and MultiRruCellMode is set to TWO_RRU_COMBINATION, two
eUCellSectorEqm MOs must be configured under this Cell MO.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, MultiRruCellFlag is set to
BOOLEAN_TRUE, and MultiRruCellMode is set to DIGITAL_COMBINATION, the number
of eUCellSectorEqm MOs configured under this Cell MO ranges from 2 to 8.
- A maximum of eight eUCellSectorEqm can be configured for each Cell in which
MultiRruCellMode is not set to MPRU_AGGREGATION.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, MultiRruCellFlag is set to
BOOLEAN_TRUE, and MultiRruCellMode is set to CELL_COMBINATION, associated
eUCellSectorEqm MOs under this Cell MO must have the same BaseBandEqmId value.
- When CellActiveState and FddTddInd in a Cell MO are set to CELL_ACTIVE and
CELL_FDD, respectively, a minimum of one and a maximum of six eUCellSectorEqm MOs
must be configured under the Cell MO if MultiRruCellFlag and MultiRruCellMode in the
Cell MO are set to BOOLEAN_TRUE and SFN, respectively.
- In a Cell MO, If CellActiveState is set to CELL_ACTIVE and FddTddInd is set to
CELL_FDD, all Cell MOs associated with the SECTOREQM MO corresponding to any
eUCellSectorEqm MO under this Cell MO must have the same TxRxMode value.
- In a Cell MO, If CellActiveState is set to CELL_ACTIVE and FddTddInd is set to
CELL_FDD, all Cell MOs associated with the SECTOREQM MO corresponding to any
eUCellSectorEqm MO under this Cell MO must have the same MultiRruCellFlag value and
the same MultiRruCellMode value.
Relation with the SfnCellBind MO:
- If MultiRruCellMode is not set to SFN, SfnCellBind with the same LocalCellId can not be
exist.
Relation with the IntraFreqBlkCell MO:
- PhyCellId of the local Cell MO cannot be within the intra-frequency blacklist cell range
specified by PhyCellId and PhyCellIdRange in an IntraFreqBlkCell MO.
Relation with the EutranInterNFreq MO:
- DlEarfcn in a Cell MO must be different from that in each associated EutranInterNFreq
MO.
Relation with the EutranIntraFreqNCell MO:
- Before adding an intra-eNodeB intra-frequency neighboring cell for a serving cell, ensure
that a Cell MO corresponding to this intra-eNodeB intra-frequency cell has been configured.
- DlEarfcn in the Cell MO corresponding to an intra-eNodeB intra-frequency neighboring cell
must be the same as DlEarfcn in the local Cell MO.
- PhyCellId in the Cell MO corresponding to an intra-eNodeB intra-frequency neighboring
cell must be different from that in the local Cell MO.
Relation with the EutranIntraFreqNCell,EutranExternalCell MOs:
- DlEarfcn in the EutranExternalCell MO corresponding to an inter-eNodeB intra-frequency
neighboring cell must be the same as DlEarfcn in the local Cell MO.
- PhyCellId in the EutranExternalCell MO that is associated with an inter-eNodeB intra-
frequency neighboring cell must be different from PhyCellId in the local Cell MO.
Relation with the EutranInterFreqNCell,EutranInterNFreq MOs:
- DlEarfcn in the Cell MO corresponding to an intra-eNodeB inter-frequency neighboring cell
must be the same as DlEarfcn in an EutranInterNFreq MO.
Relation with the eUCellSectorEqm,SECTOREQM MOs:
- In a Cell MO, if MultiRruCellMode is not set to MPRU_AGGREGATION and
CellActiveState is set to CELL_ACTIVE, the eUCellSectorEqm MO corresponding to the Cell
MO must be configured, and the SECTOREQM MO corresponding to an eUCellSectorEqm
MO under this Cell MO must be configured.
- If CellActiveState in a Cell MO is set to CELL_ACTIVE, each antenna associated with the
SECTOREQM MO corresponding to an eUCellSectorEqm MO under this Cell MO must be
unique.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, TxRxMode is set to 1T1R,
2T2R, 4T4R, or 8T8R and MultiRruCellMode is not set to CELL_COMBINATION, the total
number of TX antennas and that of RX antennas associated with the SECTOREQM MO
corresponding to an eUCellSectorEqm MO under this Cell MO must be equal to the number of
TX antennas and that of RX antennas specified by the value of TxRxMode, respectively.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE and TxRxMode is set to 2T4R,
the SECTOREQM MO corresponding to an eUCellSectorEqm MO under this Cell MO must
be associated with two or four TX antennas and four RX antennas.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE and MultiRruCellFlag is set to
BOOLEAN_TRUE and MultiRruCellMode is not set to CELL_COMBINATION, the
SECTOREQM MO corresponding to each eUCellSectorEqm MO under this Cell MO must be
associated with an MO defining a unique RF module.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, MultiRruCellFlag is set to
BOOLEAN_TRUE, and MultiRruCellMode is set to SFN, the SECTOREQM MO
corresponding to an eUCellSectorEqm MO under this Cell MO must be associated with an
RRU MO.
- In a Cell MO, CellActiveState is set to CELL_ACTIVE, MultiRruCellFlag is set to
BOOLEAN_FALSE, and two RRU MOs or RFU MOs are associated with an SECTOREQM
MO corresponding to an eUCellSectorEqm MO under this Cell MO. If FddTddInd is set to
CELL_FDD, TxRxMode must be set to 2T2R, 2T4R, or 4T4R. If FddTddInd is set to
CELL_TDD, TxRxMode must be set to 2T2R.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE and MultiRruCellMode is set to
MPRU_AGGREGATION, the SECTOREQM MO corresponding to each eUCellSectorEqm
MO under this Cell MO must have been configured.
- In a Cell MO, if FddTddInd is set to CELL_TDD, MultiRruCellFlag is set to
BOOLEAN_TRUE, MultiRruCellMode is set to MPRU_AGGREGATION and
CellActiveState is set to CELL_ACTIVE, the SECTOREQM MO corresponding to each
eUCellSectorEqm MO under this Cell MO must be associated with two TX antennas and two
RX antennas.
- In a Cell MO, if FddTddInd is set to CELL_FDD, MultiRruCellFlag is set to
BOOLEAN_TRUE, MultiRruCellMode is set to MPRU_AGGREGATION and
CellActiveState is set to CELL_ACTIVE, the SECTOREQM MO corresponding to each
eUCellSectorEqm MO under this Cell MO must be associated with one TX antenna or two TX
antennas,one RX antenna or two RX antennas.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE and TxRxMode is set to 1T2R,
the SECTOREQM MO corresponding to an eUCellSectorEqm MO under this Cell MO must
be associated with one or two TX antennas and two RX antennas.
- In a Cell MO, If CellActiveState, FddTddInd are set to CELL_ACTIVE, CELL_FDD,
respectively, and a SECTOREQM MO is shared by the eUCellSectorEqm MO under this Cell
MO and under the other Cell MOs, all SECTOREQM MOs must be shared.
Relation with the eUCellSectorEqm,SECTOREQM,RRU MOs:
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE and FddTddInd is set to
CELL_FDD, the SECTOREQM MO corresponding to an eUCellSectorEqm MO under this
Cell MO must be associated with an RRU MO supporting LTE_FDD.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE and FddTddInd is set to
CELL_TDD, the SECTOREQM MO corresponding to an eUCellSectorEqm MO under this
Cell MO must be associated with an RRU MO supporting LTE_TDD.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, MultiRruCellFlag is set to
BOOLEAN_TRUE, and MultiRruCellMode is set to DIGITAL_COMBINATION, the
SECTOREQM MO corresponding to an eUCellSectorEqm MO under this Cell MO must be
associated with an RRU MO with RT set to PRRU.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, FddTddInd is set to
CELL_FDD, MultiRruCellMode is not set to MPRU_AGGREGATION, and
CPRICompression is set to NORMAL_COMPRESSION, the SECTOREQM MO
corresponding to an eUCellSectorEqm MO under this Cell MO must be associated with an
RRU MO with RT set to PRRU.
- In a Cell MO, if FddTddInd is set to CELL_TDD, CellActiveState is set to
CELL_ACTIVE, MultiRruCellFlag is set to BOOLEAN_TRUE, and MultiRruCellMode is
set to SFN, the SECTOREQM MO corresponding to an eUCellSectorEqm MO under this Cell
MO must be associated with an RRU MO with RS set to TDL.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, MultiRruCellFlag is set to
BOOLEAN_TRUE, and MultiRruCellMode is set to SFN, the SECTOREQMMO
corresponding to an eUCellSectorEqm MO under this Cell MO must be associated with an
RRU MO with PS less than 2.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, MultiRruCellFlag is set to
BOOLEAN_TRUE, and at least one SECTOREQM MO corresponding to an
eUCellSectorEqm MO under this Cell MO is associated with an RRU MO with RT set to
PRRU, other such SECTOREQM MOs must also be associated with RRU MOs with RT set to
PRRU.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, MultiRruCellFlag is set to
BOOLEAN_TRUE, and the SECTOREQM MO corresponding to an eUCellSectorEqm MO
under this Cell MO is associated with an RRU MO with RT set to PRRU, TxRxMode must be
set to 1T1R or 2T2R.
Relation with the eUCellSectorEqm,SECTOREQM,RFU MOs:
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE and FddTddInd is set to
CELL_FDD, the SECTOREQM MO corresponding to an eUCellSectorEqm MO under this
Cell MO must be associated with an RFU MO supporting LTE_FDD.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE and FddTddInd is set to
CELL_TDD, the SECTOREQM MO corresponding to an eUCellSectorEqm MO under this
Cell MO must be associated with an RFU MO supporting LTE_TDD.
Relation with the eUCellSectorEqm,BASEBANDEQM,BBP MOs:
- When CellActiveState in a Cell MO is set to CELL_ACTIVE: if FddTddInd is set to
CELL_FDD, TYPE and WM in all BBP MOs corresponding to an eUCellSectorEqm MO
under this Cell MO must be set to LBBP and FDD; if FddTddInd is set to CELL_TDD, TYPE
in all BBP MOs specified by BaseBandEqmId in an eUCellSectorEqm MO under this Cell
MO must be set to LBBP, and WM cannot be set to FDD.
Relation with the eUCellSectorEqm,BASEBANDEQM MOs:
- If CellActiveState in a Cell MO is set to CELL_ACTIVE, BASEBANDEQMTYPE in all
BASEBANDEQM MOs corresponding to an eUCellSectorEqm MO under this Cell MO must
be set to ULDL.
- If CellActiveState in a Cell MO is set to CELL_ACTIVE and BaseBandEqmId in an
eUCellSectorEqm MO under this Cell MO is not 255, the BASEBANDEQM MO
corresponding to BaseBandEqmId must have been configured.
Relation with the eUCellSectorEqm,SECTOREQM,RRU,RRUCHAIN MOs:
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, MultiRruCellFlag is set to
BOOLEAN_TRUE, and the SECTOREQM MO corresponding to an eUCellSectorEqm MO
under this Cell MO is associated with an RRU MO with RT set to PRRU, all RRU MOs must
be configured on the same RRU chain.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, and the TT in RRUCHAIN
MOs where the RRU MOs associated with a SECTOREQM MO corresponding to an
eUCellSectorEqm MO under this Cell MO is not LOADBALANCE, these RRUCHAIN MOs
must be in the same subrack.
Relation with the eUCellSectorEqm,BBP MOs:
- In a Cell MO, If CellActiveState is set to CELL_ACTIVE, FddTddInd is set to
CELL_FDD, and BaseBandEqmId in an eUCellSectorEqm MO under this Cell MO is set to
255, at least one LBBP working in FDD mode is available. If CellActiveState is set to
CELL_ACTIVE, FddTddInd is set to CELL_TDD, and BaseBandEqmId in an
eUCellSectorEqm MO under this Cell MO is set to 255, at least one LBBP working in non-
FDD mode is available.
Relation with the EutranInterFreqNCell MO:
- DlEarfcn in the Cell MO corresponding to an intra-eNodeB inter-frequency neighboring cell
must be different from DlEarfcn in the local Cell MO.
- Before adding an intra-eNodeB inter-frequency neighboring cell for a serving cell, ensure
that a Cell MO corresponding to this intra-eNodeB inter-frequency cell has been configured.
Relation with the CellUlschAlgo,PUSCHCfg MOs:
- Let A be the number of RB resources corresponding to the value of UlBandWidth in a Cell
MO, B the even number that HoppingOffset in the PUSCHCfg MO is rounded up to, and C the
difference between A and B. If UlHoppingType in the CellUlschAlgo MO is set to
HOPPING_TYPE1, C must be greater than A modulo 2. If UlHoppingType in the
CellUlschAlgo MO is set to HOPPING_TYPE2 or HOPPING_TYPE2_RANDOM, and Nsb in
the PUSCHCfg MO is greater than 1, the integer value of C divide Nsb in the PUSCHCfg MO
must be greater than 0.
- If UlBandWidth is set to CELL_BW_N6(1.4M), the number of RB resources is 6.
- If UlBandWidth is set to CELL_BW_N15(3M), the number of RB resources is 15.
- If UlBandWidth is set to CELL_BW_N25(5M), the number of RB resources is 25.
- If UlBandWidth is set to CELL_BW_N50(10M), the number of RB resources is 50.
- If UlBandWidth is set to CELL_BW_N75(15M), the number of RB resources is 75.
- If UlBandWidth is set to CELL_BW_N100(20M), the number of RB resources is 100.
Relation with the SRSCfg MO:
- If FddTddInd in a Cell MO is set to CELL_TDD, SrsSubframeCfg in the associated
SRSCfg MO must be smaller than SC14.
Relation with the CellOp,ENodeBSharingMode MOs:
- If the ENodeBSharingMode parameter in the ENodeBSharingMode MO is set to
INDEPENDENT, a maximum of one CellOp MO with the same LocalCellId as that in a Cell
MO can be configured.
- If the ENodeBSharingMode parameter in the ENodeBSharingMode MO is set to
SEPARATED_FREQ, a maximum of one CellOp MO with the same LocalCellId as that in a
Cell MO can be configured.
Relation with the CellOp MO:
- If CellActiveState in a Cell MO is set to CELL_ACTIVE, one or more CellOp MOs must
have been configured for the Cell MO.
- If ENodeBSharingMode in ENodeBSharingMode is set to SHARED_FREQ, a maximum
of six CellOp MO with the same LocalCellId as that in a Cell MO can be configured.
- If ENodeBSharingMode in the ENodeBSharingMode MO is set to SHARED_FREQ and
CellActiveState in a Cell MO is set to CELL_ACTIVE, one of the CellOp MOs which have the
same LocalCellId as that in a Cell MO must represent the primary operator.
Relation with the PHICHCfg MO:
- If CustomizedBandWidthCfgInd is set to CFG and CustomizedDLBandWidth is set to a
value in the range of 183 to 192 in a Cell MO, PhichResource in the associated PHICHCfg MO
cannot be set to TWO.
Relation with the CellAlgoSwitch MO:
- If CellActiveState in a Cell MO is set to CELL_ACTIVE and MultiRruCellFlag in a Cell
MO is set to BOOLEAN_TRUE and MultiRruCellMode in a Cell MO is set to
CELL_COMBINATION, MuBfAlgoSwitch in a CellAlgoSwitch MO must be Off.
- If CellActiveState in a Cell MO is set to CELL_ACTIVE and MultiRruCellFlag in a Cell
MO is set to BOOLEAN_TRUE and MultiRruCellMode in a Cell MO is set to
CELL_COMBINATION, BfAlgoSwitch in a CellAlgoSwitch MO must be Off.
- If MultiRruCellFlag, MultiRruCellMode, and CellActiveState in a Cell MO are set to
BOOLEAN_TRUE, CELL_COMBINATION, and CELL_ACTIVE, respectively,
UlVmimoSwitch under UlSchSwitch in the associated CellAlgoSwitch MO must be Off.
- If CellActiveState in a Cell MO is set to CELL_ACTIVE, FddTddInd is CELL_TDD
Model and DlBandWidth is CELL_BW_N25, BfAlgoSwitch in the CellAlgoSwitch must be
set OFF.
- If CellActiveState in a Cell MO is set to CELL_ACTIVE, FddTddInd is CELL_TDD
Model and DlBandWidth is CELL_BW_N25, UlCompSwitch in the CellAlgoSwitch must be
set DISABLE.
- If CellActiveState in a Cell MO is set to CELL_ACTIVE and MultiRruCellFlag in a Cell
MO is set to BOOLEAN_TRUE and MultiRruCellMode in a Cell MO is set to
DIGITAL_COMBINATION, UlCompSwitch in the CellAlgoSwitch MO must be set
DISABLE.
- DlCompSwitch in the CellAlgoSwitch MO is set to On only if HighSpeedFlag in a Cell
MO is set to LOW_SPEED.
- In a Cell MO, if FddTddInd is set to CELL_FDD, and MultiRruCellFlag is set to
BOOLEAN_TRUE, and MultiRruCellMode is set to SFN, UlCompSwitch in a
CellAlgoSwitch MO must be DISABLE.
- If CellActiveState in a Cell MO is set to CELL_ACTIVE, FddTddInd is CELL_TDD
Model and DlBandWidth is CELL_BW_N25, DlCompSwitch in the CellAlgoSwitch must be
set OFF.
- PsicSwitch in the CellAlgoSwitch MO is set to On only if TxRxMode in a Cell MO is set
to 1T2R or 2T2R.
- In a Cell MO, if FddTddInd is set to CELL_FDD, MultiRruCellFlag is set to
BOOLEAN_TRUE, and MultiRruCellMode is set to SFN or MPRU_AGGREGATION,
UlVmimoSwitch under UlSchSwitch in the CellAlgoSwitch MO under the Cell MO must be
turned off.
- If FddTddInd, MultiRruCellFlag, and MultiRruCellMode in a Cell MO are set to
CELL_FDD, BOOLEAN_TRUE, and MPRU_AGGREGATION, respectively, UlCompSwitch
in the CellAlgoSwitch MO under the Cell MO must be set to DISABLE.
- If CellActiveState in a Cell MO is set to CELL_ACTIVE, FddTddInd is CELL_TDD
Model and DlBandWidth is CELL_BW_N25, RanShareModeSwitch in the CellAlgoSwitch
must be set OFF.
- The InterFreqBlindMlbSwitch under the MlbAlgoSwitch cannot be turned on when the Cell
is Tdd.
Relation with the CellOp,CnOperatorTa MOs:
- If ENodeBSharingMode in the ENodeBSharingMode MO is set to SHARED_FREQ and
CellActiveState in a Cell MO is set to CELL_ACTIVE, CnOperatorId in the CnOperatorTa
MO corresponding to TrackingAreaId in each CellOp MO must be unique.
- If ENodeBSharingMode in the ENodeBSharingMode MO is set to SHARED_FREQ and
CellActiveState in a Cell MO is set to CELL_ACTIVE, Tac in the CnOperatorTa MO
corresponding to TrackingAreaId in each CellOp MO must have the same value.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ACT CELL Use this command to activate a cell.

ADD CELL Use this command to add a cell.

ADD CELLBAND Use this command to add a cell slave band.

BLK CELL Use this command to block a cell.

DEA CELL Use this command to deactivate a cell. When a cell is deactivated, all the user-
related services are disrupted.

DSP CELL Use this command to list the dynamic information about a cell.

DSP Use this command to query the uplink (UL) coordinated multi-point
CELLULCOMPCLUST
ER transmission/reception technology (CoMP) list of a cell.
.

DSP PRIBBPADJUST Use this command to query whether the eNodeB has sufficient resources and
how to configure a cell on the primary LBBP by adjusting the configuration of
other cells after the cell allocation to the primary LBBP failed.

LST CELL Use this command to list the static information about a cell.

LST CELLBAND Use this command to list a cell slave band.

MOD CELL Use this command to modify a cell.

RMV CELL Use this command to remove a cell. The execution of this command deactivates
the cell, interrupts the services provided by the cell, and removes all
configurations related to the cell from the data base.

RMV CELLBAND Use this command to remove a cell slave band.

STR Use this command to start an RF loopback test for a cell.


CELLRFLOOPBACK

STR CELLSELFTEST Use this command to start a self-test for virtual services.Currently, this
command applies only to cells established on an LBBPd.

UBL CELL Use this command to unblock a cell.

Related Parameters
Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local Cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Cell Name Indicates the name of the cell.

Csg indicator Indicates whether the cell is a closed subscriber group (CSG) cell. A CSG cell
has restrictions on UE access. It broadcasts a specific CSG ID in the SIB and
only those UEs of the group can access the CSG cell. BOOLEAN_FALSE
indicates that the cell is not a CSG cell, and BOOLEAN_TRUE indicates that
the cell is a CSG cell. Currently, Huawei eNodeBs do not support CSG cells.

Uplink cyclic prefix Indicates the UL cyclic prefix length of a cell. A cyclic prefix can be a common
length
or extended cyclic prefix. An extended cyclic prefix is generally used in a
complex environment with a strong multi-path effect and long delay. In a cell,
the UL cyclic prefix length can be different from the DL one. In addition, the UL
or DL cyclic prefix length of a cell must be the same as that of the cell using the
same LBBP. For details, see 3GPP TS 36.211.

Downlink cyclic prefix Indicates the length of the DL cyclic prefix of a cell. A DL cyclic prefix can be a
length
common or extended cyclic prefix. An extended cyclic prefix is generally used
in a complex environment with a strong multi-path effect and long delay. In a
cell, the UL cyclic prefix length can be different from the DL one. In addition,
the UL or DL cyclic prefix length of a cell must be the same as that of the cell
using the same LBBP. For details, see 3GPP TS 36.211.

Frequency band Indicates the frequency band in which the cell operates. For details about this
parameter, see 3GPP TS 36.104.

Uplink EARFCN Indicates whether to configure the UL EARFCN of the cell. For an FDD cell, if
indication
no UL EARFCN is configured, the UL EARFCN equals the sum of the DL
EARFCN and 18000 by default. For a TDD cell, the UL EARFCN equals the
DL EARFCN.

Uplink EARFCN Indicates the UL EARFCN of the cell. It is optional, depending on the setting of
the UL EARFCN configuration indicator (UlEarfcnCfgInd). If the value of this
parameter is not specified, the default UL EARFCN is used, which is calculated
based on the DL EARFCN. For details, see 3GPP TS 36.104.

Downlink EARFCN Indicates the DL EARFCN of the cell. For details, see the 3GPP TS 36.104.

Uplink bandwidth Indicates the UL bandwidth of the cell, which is based on the number of
resource blocks (RBs). The value CELL_BW_N25 indicates a cell bandwidth of
25 RBs. The value CELL_BW_N50 indicates a cell bandwidth of 50 RBs. The
Table 2 Related parameters

Parameter Description

mapping between the parameter value and the actual cell bandwidth (that is, the
number of RBs) can be deduced similarly. For details, see 3GPP TS 36.104.

Downlink bandwidth Indicates the DL bandwidth of the cell, which is based on the number of
resource blocks (RBs). The value CELL_BW_N25 indicates a cell bandwidth of
25 RBs. The value CELL_BW_N50 indicates a cell bandwidth of 50 RBs. The
mapping between the parameter value and the actual cell bandwidth (that is, the
number of RBs) can be deduced similarly. For details, see 3GPP TS 36.104.

Cell ID Indicates the ID of the E-UTRAN cell. The combination of this parameter and
the eNodeB ID forms the E-UTRAN cell identity. The combination of the E-
UTRAN cell identity and the PLMN identity forms the ECGI. For details, see
3GPP TS 36.413.

Physical cell ID Indicates the physical cell ID. For details, see 3GPP TS 36.331.

Additional spectrum Indicates the additional spectrum emission, which restricts the emission power
emission
of the UEs in the cell. For details, see the 3GPP TS 36.101.

Cell active state Indicates the active state of the cell. It consists of the activated and deactivated
states.

Cell admin state Indicates the administrative state, which can be Unblock, High block, Middle
block, or Low block.If the CellAdminState parameter is set to
CELL_HIGH_BLOCK, the cell is deactivated immediately. If the
CellAdminState parameter is set to CELL_MIDDLE_BLOCK, the cell is
deactivated when it has no user to serve during the time period specified by the
CellMidBlkTimer parameter, and is deactivated when the timer expires
irrespective of whether it has users to serve. If the CellAdminState parameter is
set to CELL_LOW_BLOCK, the cell is deactivated only when the cell does not
have any users to serve.

Cell middle block timer Indicates the length of the timer used to determine whether to block a middle-
blocking-priority cell. If CellAdminState is set to CELL_MIDDLE_BLOCK,
the cell is deactivated when no user accesses the cell during the period of time
specified by this parameter. The cell is also deactivated if the timer expires.

Cell FDD TDD Indicates the duplex mode of the cell. CELL_FDD indicates the FDD mode, and
indication
CELL_TDD indicates the TDD mode.

Subframe assignment Indicates the ratio of UL subframes to DL subframes in a TDD cell. For details,
see 3GPP TS 36.211.

Special subframe Indicates the ratio of special UL subframes to special DL subframes in a TDD
Table 2 Related parameters

Parameter Description

patterns cell. For details, see 3GPP TS 36.211.

Cell specific offset Indicates the cell specific offset for the serving cell. It affects the probability of
triggering handovers from the serving cell to its neighboring cells. A smaller
value of this parameter leads to a higher probability. For details, see 3GPP TS
36.331.

Frequency offset Indicates the specific frequency offset of the serving cell. This parameter is
contained in the measurement control information and is related to the handover
difficulty between the serving cell and the neighboring cell. For details, see
3GPP TS 36.331.

Root sequence index Indicates the first logical root sequence, which is used to generate the preamble
sequence. Each logical root sequence corresponds to a physical root sequence.
For the mapping between logical root sequences and physical root sequences,
see 3GPP TS 36.211.

High speed flag Indicates the speed flag of the cell. Set this parameter to
ULTRA_HIGH_SPEED if the cell is used to provide coverage for an ultra-high-
speed railway. Set this parameter to HIGH_SPEED if the cell is used to provide
coverage for a high way. Set this parameter to LOW_SPEED in other scenarios.

Preamble format Indicates the preamble format used in the cell. For details, see 3GPP TS 36.211.

Cell radius Indicates the radius of the cell.

Customized bandwidth Indicates whether to configure bandwidth customization for the cell. Bandwidth
configure indicator
customization is available only when the bandwidth is 5 MHz, 10 MHz, 15
MHz, or 20 MHz.

Customized uplink Indicates the customized UL cell bandwidth. Bandwidth customization is


bandwidth
available only when the bandwidth is 5 MHz, 10 MHz, 15 MHz, or 20 MHz.

Customized downlink Indicates the customized DL cell bandwidth. Bandwidth customization is


bandwidth
available only when the bandwidth is 5 MHz, 10 MHz, 15 MHz, or 20 MHz.

Emergency Area Id Indicates whether to set an emergency area ID.


indicator

Emergency Area ID Indicates the ID of the notification area within which a warning notification is
broadcast. The area consists of one or more cells and can be customized by
operators. For details about this parameter, see 3GPP TS 36.413.

Ue max power allowed Indicates whether to configure the maximum TX power of the UE in the cell. If
configure indicator
Table 2 Related parameters

Parameter Description

the value of this parameter is not specified, the maximum power is subject to the
UE capability.

Max transmit power Indicates the maximum transmit power that a UE can apply to uplink
allowed
transmission in the cell. It is used in cell selection criterion S to calculate the
compensated power. If the value of this parameter is not specified, the maximum
power is subject to the UE capability. For details, see 3GPP TS 36.304.

Flag of Multi-RRU Cell Indicates whether to enable or disable the multi-RRU cell feature.

Mode of Multi-RRU Cell Indicates the type of the multi-RRU cell.

CPRI Compression Indicates the CPRI compression type of the cell. CPRI compression is used in
RRU cascading scenarios to improve the cascading specifications without
changing the CPRI data rate. This parameter can be set to NO_COMPRESSION
or NORMAL_COMPRESSION. The value NO_COMPRESSION indicates that
CPRI compression is not used, and the value NORMAL_COMPRESSION
indicates that CPRI compression is used. In addition, the CPRI compression
type must be the same for cells using the same RRU chain.

Sector equipment Indicates the number of sector devices that serve an SFN cell.
number of SFN cell

Air Cell Flag Indicates whether the cell is an air cell.

CRS Port Number Indicates the number of ports for transmitting reference signals in a cell. This
parameter is dedicated to LTE TDD cells. As specified in protocols, the CRS
Port Number parameter can be set to 1, 2, or 4. (CRS is short for Cell Reference
Signal.) The value 1 indicates that one CRS port (port 0) is configured. The
value 2 indicates that two CRS ports (port 0 and port 1) are configured. The
value 4 indicates that four CRS ports (port 0, port 1, port 2, and port 3) are
configured.

Cell transmission and Indicates the transmission and reception mode of the cell.
reception mode

User label Indicates the user label of the cell.

Work mode Indicates the work mode of the cell. The DL_ONLY mode applies only to the
carrier aggregation scenario.

Cell Standby Mode Indicates the active or standby mode of the cell. A cell is in active mode by
default. The standby mode applies to LTE TDD. If this parameter is set to
STANDBY, an inter-BBU SFN auxiliary cell can roll back to the standby mode
to provide services if inter-BBU faults occur. Only common or SFN cells
Table 2 Related parameters

Parameter Description

support the standby mode.

Cell instance state Indicates the state of the cell instance.

Reason for latest state Indicates the reason that causes the latest state change of the cell, which can be a
change
cell activation success or a cell setup failure.

Cell latest setup time Indicates the latest setup time of the cell.

Cell latest setup Indicates the latest setup type of the cell.
operate type

Cell latest remove time Indicates the latest remove time of the cell.

Cell latest remove Indicates the latest remove type of the cell.
operate type

Cell power save state Indicates the energy conservation and emission reduction mode of the cell. The
energy conservation and emission reduction mode of the cell can be set to: RF
channel intelligent shutdown mode, intelligent power-off of carriers mode, low
power consumption mode, RF module regular time sleep mode, intelligent
power-off of carriers in the same coverage of UMTS network mode, or dynamic
voltage adjustment mode.

Primary LBBP Indicates the cabinet number, subrack number and slot number of the primary
information
LBBP that serves the cell.

Cell topology type Indicates the topology of the cell.

RF module cabinet Indicates the cabinet number of the RF module that serves the cell.
number

RF module subrack Indicates the subrack number of the RF module that serves the cell.
number

RF module slot number Indicates the slot number of the RF module that serves the cell.

Symbol shutdown state Indicates whether the cell is in the symbol power saving state.

Maximum transmit Indicates the maximum transmit power of the cell in theory. The value 65535
power
indicates that this parameter is invalid, which can be changed by modifying the
physical downlink shared channel (PDSCH) configuration or the PA parameter
related to power control for the PDSCH.

eNodeB ID Indicates the ID of the eNodeB.


Table 2 Related parameters

Parameter Description

LBBP Cabinet No. Indicates the cabinet number of the LBBP that serves the cell.

LBBP Subrack No. Indicates the subrack number of the LBBP that serves the cell.

LBBP Slot No. Indicates the slot number of the LBBP that serves the cell.

Work Status Indicates the work status of the RF module and LBBP that serves the cell.

Coordinating local cell Indicates the local cell identity of the uplink coordinating cell.
ID

Cell Slave Band Indicates slave frequency bands of a cell. If the working frequency of a cell
belongs to multiple frequency bands, the downlink frequency in the frequency
band of the highest priority is configured based on FreqBand, and the downlink
frequencies in other frequency bands are configured based on this parameter. If
there are multiple frequency bands of different priorities, downlink frequencies
in the frequency bands are configured based on the priorities in descending
order. The frequency band priorities of a cell are determined based on the
network planning of an operator. It is recommended that the frequency band
values are arranged in ascending order. The frequency band with the minimum
value is of the highest priority, and the frequency band with the maximum value
is of the lowest priority.

5.7.1.6.3.20 CellAcBar
+-NE
+-eNodeBFunction
+-Cell
+-CellAcBar

Description

The CellAcBar MO consists of the access barring information in the System Information Block 2
(SIB2) of the cell. This information contains the access barring information related to emergency
call access, originating call access, and signaling access.
By setting related parameters to control the access to the cell, operators can effectively avoid
channel overload.
The SIM or USIM of each UE in the network is allocated with one access class within the range
of access class 0 to 9. In addition, the SIM/USIM of a UE belonging to certain specific category
may be allocated with and store one or more special access classes (access class 11 to 15). The
mapping between the special access class and the specific category is shown as follows:
1. Access class 15 for Home PLMN staff;
2. Access class 14 for emergency services;
3. Access class 13 for public utilities;
4. Access class 12 for security services;
5. Access class 11 for PLMN management.
Different from access class 0 to 9 and 11 to 15, the control information about access class 10 is
sent to UEs through air interface signaling, and is used to indicate whether the UE belonging to
access class 0 to 9 or without an IMSI can access to the cell in case of emergency calls. A UE of
access class 11 to 15 cannot initiate emergency calls when access class 10 and access class 11 to
15 are all barred for the UE. Otherwise, the UE can initiate emergency calls.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST CELLACBAR Use this command to list the parameters about cell access barring.

MOD CELLACBAR Use this command to modify the configuration of cell access barring.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

AC barring information Indicates whether to configure the access barring information.


configure indicator

Emergency call barring Indicates the emergency call barring status of access class 10, indicating whether
state
UEs of access class 10 can initiate emergency calls.
If this parameter is set to BOOLEAN_TRUE, UEs of access classes 0 to 9 or
those without IMSIs cannot initiate emergency calls. If this parameter is set to
BOOLEAN_FALSE, UEs of access classes 0 to 9 and those without IMSIs can
initiate emergency calls.
A UE in access classes 11 to 15 cannot initiate emergency calls only when its
access class and access class 10 are both barred. If its access class or access
class 10 is not barred, emergency calls initiated by the UE are granted access.

AC barring for mobile Indicates whether to configure the access barring information for mobile-
data configure indicator
originated calls.

Access probability Indicates the access probability factor for mobile-originated calls. A mobile-
factor for originating call
originated call is granted access if the random number generated by the UE is
smaller than this access probability factor; otherwise, the access request is
rejected. If this parameter is set to P00, all mobile-originated calls initiated by
UEs of access class 11 to access class 15 are granted access.

Mean access barring Indicates the average access barring duration for mobile-originated calls.
time for originating call

AC11 barring state for Indicates the mobile-originated call barring status of access class 11, indicating
originating call
whether UEs of access class 11 can initiate mobile-originated calls.
If this parameter is set to BOOLEAN_TRUE, UEs of access class 11 cannot
initiate mobile-originated calls. If this parameter is set to BOOLEAN_FALSE,
UEs of access class 11 can initiate mobile-originated calls.

AC12 barring state for Indicates the mobile-originated call barring status of access class 12, indicating
originating call
whether UEs of access class 12 can initiate mobile-originated calls.
If this parameter is set to BOOLEAN_TRUE, UEs of access class 12 cannot
initiate mobile-originated calls. If this parameter is set to BOOLEAN_FALSE,
UEs of access class 12 can initiate mobile-originated calls.

AC13 barring state for Indicates the mobile-originated call barring status of access class 13, indicating
originating call
whether UEs of access class 13 can initiate mobile-originated calls.
If this parameter is set to BOOLEAN_TRUE, UEs of access class 13 cannot
initiate mobile-originated calls. If this parameter is set to BOOLEAN_FALSE,
UEs of access class 13 can initiate mobile-originated calls.
Table 2 Related parameters

Parameter Description

AC14 barring state for Indicates the mobile-originated call barring status of access class 14, indicating
originating call
whether UEs of access class 14 can initiate mobile-originated calls.
If this parameter is set to BOOLEAN_TRUE, UEs of access class 14 cannot
initiate mobile-originated calls. If this parameter is set to BOOLEAN_FALSE,
UEs of access class 14 can initiate mobile-originated calls.

AC15 barring state for Indicates the mobile-originated call barring status of access class 15, indicating
originating call
whether UEs of access class 15 can initiate mobile-originated calls.
If this parameter is set to BOOLEAN_TRUE, UEs of access class 15 cannot
initiate mobile-originated calls. If this parameter is set to BOOLEAN_FALSE,
UEs of access class 15 can initiate mobile-originated calls.

AC barring for mobile Indicates whether to configure the access barring information for signaling.
signal configure
indicator

Access probability Indicates the access probability factor for signaling. Signaling from a UE is
factor for signaling
granted access if the random number generated by the UE is smaller than this
access probability factor; otherwise, the access request is rejected. If this
parameter is set to P00, signaling from UEs of access class 11 to access class 15
is granted access.

Mean access barring Indicates the average access barring duration for signaling.
time for signaling

AC11 barring state for Indicates the signaling barring status of access class 11, indicating whether UEs
signaling
of access class 11 can initiate signaling access.
If this parameter is set to BOOLEAN_TRUE, UEs of access class 11 cannot
initiate signaling access. If this parameter is set to BOOLEAN_FALSE, UEs of
access class 11 can initiate signaling access.

AC12 barring state for Indicates the signaling barring status of access class 12, indicating whether UEs
signaling
of access class 12 can initiate signaling access.
If this parameter is set to BOOLEAN_TRUE, UEs of access class 12 cannot
initiate signaling access. If this parameter is set to BOOLEAN_FALSE, UEs of
access class 12 can initiate signaling access.

AC13 barring state for Indicates the signaling barring status of access class 13, indicating whether UEs
signalling
of access class 13 can initiate signaling access.
If this parameter is set to BOOLEAN_TRUE, UEs of access class 13 cannot
initiate signaling access. If this parameter is set to BOOLEAN_FALSE, UEs of
access class 13 can initiate signaling access.

AC14 barring state for Indicates the signaling barring status of access class 14, indicating whether UEs
signalling
Table 2 Related parameters

Parameter Description

of access class 14 can initiate signaling access.


If this parameter is set to BOOLEAN_TRUE, UEs of access class 14 cannot
initiate signaling access. If this parameter is set to BOOLEAN_FALSE, UEs of
access class 14 can initiate signaling access.

AC15 barring state for Indicates the signaling barring status of access class 15, indicating whether UEs
signaling
of access class 15 can initiate signaling access.
If this parameter is set to BOOLEAN_TRUE, UEs of access class 15 cannot
initiate signaling access. If this parameter is set to BOOLEAN_FALSE, UEs of
access class 15 can initiate signaling access.

AC barring for MMTEL Indicates whether to configure the access barring information for multimedia
voice configure
indicator telephony (MMTEL) voice services.

Access probability Indicates the access probability factor for multimedia telephony (MMTEL)
factor for MMTEL voice
voice services. An MMTEL voice service is granted access if the random
number generated by the UE is less than this access probability factor;
otherwise, the access request is barred.

Mean access barring Indicates the average access barring time of multimedia telephony (MMTEL)
time for MMTEL voice
voice services.

AC 11-15 barring state Indicates whether multimedia telephony (MMTEL) voice services initiated by
for MMTEL voice
UEs of AC 11 to AC 15 are granted access.
AC11BARSTATE: If this option is selected, the MMTEL voice services initiated
by UEs of AC 11 in idle mode are barred.
AC12BARSTATE: If this option is selected, the MMTEL voice services initiated
by UEs of AC 12 in idle mode are barred.
AC13BARSTATE: If this option is selected, the MMTEL voice services initiated
by UEs of AC 13 in idle mode are barred.
AC14BARSTATE: If this option is selected, the MMTEL voice services initiated
by UEs of AC 14 in idle mode are barred.
AC15BARSTATE: If this option is selected, the MMTEL voice services initiated
by UEs of AC 15 in idle mode are barred.

AC barring for MMTEL Indicates whether to configure the access barring information for multimedia
video configure
indicator telephony (MMTEL) video services.

Access probability Indicates the access probability factor for multimedia telephony (MMTEL)
factor for MMTEL video
video services. An MMTEL video service is granted access if the random
number generated by the UE is less than this access probability factor;
otherwise, the access request is barred.
Table 2 Related parameters

Parameter Description

Mean access barring Indicates the average access barring time of multimedia telephony (MMTEL)
time for MMTEL video
video services.

AC 11-15 barring state Indicates whether multimedia telephony (MMTEL) video services initiated by
for MMTEL video
UEs of AC 11 to AC 15 are granted access.
AC11BARSTATE: If this option is selected, the MMTEL video services
initiated by UEs of AC 11 in idle mode are barred.
AC12BARSTATE: If this option is selected, the MMTEL video services
initiated by UEs of AC 12 in idle mode are barred.
AC13BARSTATE: If this option is selected, the MMTEL video services
initiated by UEs of AC 13 in idle mode are barred.
AC14BARSTATE: If this option is selected, the MMTEL video services
initiated by UEs of AC 14 in idle mode are barred.
AC15BARSTATE: If this option is selected, the MMTEL video services
initiated by UEs of AC 15 in idle mode are barred.

5.7.1.6.3.21 CellAccess
+-NE
+-eNodeBFunction
+-Cell
+-CellAccess

Description

The CellAccess MO consists of the parameters related to access information in System


Information Block 1 (SIB1).For details on the access control procedure, see the 3GPP TS 36.304.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell
Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST CELLACCESS Use this command to list the parameters about cell access.

MOD CELLACCESS Use this command to modify the configuration of cell access.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Cell barring state Indicates whether the cell is barred. If the cell is barred, the UE cannot camp on
the serving cell. During cell reselection, the serving cell is not selected as a
candidate cell.

Cell reserved for Indicates whether the cell is reserved for future extension. If the cell is reserved,
extension
whether a UE can access the cell depends on the access class of the UE and its
serving PLMN. Details are described as follows: (1) A UE of access class 11 or
15 treats the cell as a candidate if the UE is served by its home PLMN
(HPLMN) or equivalent home PLMN (EHPLMN); (2) A UE of access class 11
or 15 treats the cell as a barred cell if it is not served by its HPLMN or
EHPLMN; (3) A UE of an access class within the two ranges of 0-9 and 12-14
treats the cell as a barred cell. In this version, the parameter still supports setting
synchronization between the M2000 and the eNodeB, but is no longer used
internally. Avoid using this parameter as it will be removed from the later
versions.

Intra-frequency Indicates whether the cell can initiate the intra-frequency cell reselection when
reselection indication
the cell is barred.
NOT_ALLOWED means that the UE cannot initiate the intra-frequency cell
reselection, and ALLOWED means that the UE can initiate the intra-frequency
cell reselection.

Plmn Broadcast Mode Indicates the PLMN broadcast mode of the cell. If certain cells on the live
Table 2 Related parameters

Parameter Description

network are in RAN sharing with common carriers mode and at least one of
these cells uses the round robin mode, NBSLTEPLMNRoundSwitch under the
ANR Under RAN Sharing Algorithm Switch parameter must be turned on for
eNodeBs whose cells are configured as neighboring cells for the local cell.
Otherwise, the local eNodeB may experience failures in handing over UEs from
the local cell to an ANR-established neighboring cell that is in round robin
mode.If this parameter is set to NORMAL_MODE, the cell broadcasts PLMN-
specific information in normal mode. If this parameter is set to RR_MODE, the
cell broadcasts PLMN-specific information in round robin mode.

Plmn Round Broadcast Indicates the changing period of cell PLMN.


Period

Plmn Round Action Indicates the start time for broadcasting PLMN-specific information in round
Time
robin mode.

5.7.1.6.3.22 CellAlgoSwitch
+-NE
+-eNodeBFunction
+-Cell
+-CellAlgoSwitch

Description

The CellAlgoSwitch MO consists of the following cell-level switches: random access channel
(RACH) algorithm switch, sounding reference signal (SRS) algorithm switch, physical uplink
control channel (PUCCH) algorithm switch, active queue management (AQM) algorithm switch,
channel quality indicator (CQI) adjustment algorithm switch, radio link failure (RLF) detection
algorithm switch, dynamic voltage adjustment algorithm switch, radio access control (RAC)
algorithm switch, load balancing algorithm switch, downlink (DL) power control algorithm
switch, uplink (UL) power control algorithm switch, beamforming algorithm switch, DL
scheduling switch, UL scheduling switch, RAN sharing mode switch, frequency-priority-based
handover switch, multi-user beamforming algorithm switch, distance-based handover switch,
access barring algorithm switch, enhanced inter-cell interference coordination (eICIC) algorithm
switch, UL coordinated multi-point (CoMP) algorithm switch, and maximum ratio combining
(MRC)/interference rejection combining (IRC) adaptation switch.

Effective Scenario
Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the CellSimuLoad MO:


- If BfAlgoSwitch in the CellAlgoSwitch MO is set to Off, SimuLoadTransMode in the
CellSimuLoad MO cannot be set to TM7 or TM8.
Relation with the Cell,MimoAdaptiveParaCfg MOs:
- If CellActiveState in a Cell MO is set to CELL_ACTIVE, EicicSwitch in CellAlgoSwitch
MO cannot be set to ON and MimoAdaptiveSwitch in MimoAdaptiveParaCfg MO cannot be
set to OC_ADAPTIVE at the same time.
Relation with the Cell,eUCellSectorEqm,SECTOREQM MOs:
- Among all cells which use a same SECTOREQM,the number of cells which
CellActiveState in a Cell MO is set to CELL_ACTIVE and GLPwrShare in the
CellAlgoSwitch is set to ON must be less than 2.
Relation with the Cell MO:
- If CellActiveState in a Cell MO is set to CELL_ACTIVE and MultiRruCellFlag in a Cell
MO is set to BOOLEAN_TRUE and MultiRruCellMode in a Cell MO is set to
CELL_COMBINATION, MuBfAlgoSwitch in a CellAlgoSwitch MO must be Off.
- If CellActiveState in a Cell MO is set to CELL_ACTIVE and MultiRruCellFlag in a Cell
MO is set to BOOLEAN_TRUE and MultiRruCellMode in a Cell MO is set to
CELL_COMBINATION, BfAlgoSwitch in a CellAlgoSwitch MO must be Off.
- If MultiRruCellFlag, MultiRruCellMode, and CellActiveState in a Cell MO are set to
BOOLEAN_TRUE, CELL_COMBINATION, and CELL_ACTIVE, respectively,
UlVmimoSwitch under UlSchSwitch in the associated CellAlgoSwitch MO must be Off.
- If CellActiveState in a Cell MO is set to CELL_ACTIVE, FddTddInd is CELL_TDD
Model and DlBandWidth is CELL_BW_N25, BfAlgoSwitch in the CellAlgoSwitch must be
set OFF.
- If CellActiveState in a Cell MO is set to CELL_ACTIVE, FddTddInd is CELL_TDD
Model and DlBandWidth is CELL_BW_N25, UlCompSwitch in the CellAlgoSwitch must be
set DISABLE.
- If CellActiveState in a Cell MO is set to CELL_ACTIVE and MultiRruCellFlag in a Cell
MO is set to BOOLEAN_TRUE and MultiRruCellMode in a Cell MO is set to
DIGITAL_COMBINATION, UlCompSwitch in the CellAlgoSwitch MO must be set
DISABLE.
- DlCompSwitch in the CellAlgoSwitch MO is set to On only if HighSpeedFlag in a Cell
MO is set to LOW_SPEED.
- In a Cell MO, if FddTddInd is set to CELL_FDD, and MultiRruCellFlag is set to
BOOLEAN_TRUE, and MultiRruCellMode is set to SFN, UlCompSwitch in a
CellAlgoSwitch MO must be DISABLE.
- If CellActiveState in a Cell MO is set to CELL_ACTIVE, FddTddInd is CELL_TDD
Model and DlBandWidth is CELL_BW_N25, DlCompSwitch in the CellAlgoSwitch must be
set OFF.
- PsicSwitch in the CellAlgoSwitch MO is set to On only if TxRxMode in a Cell MO is set
to 1T2R or 2T2R.
- In a Cell MO, if FddTddInd is set to CELL_FDD, MultiRruCellFlag is set to
BOOLEAN_TRUE, and MultiRruCellMode is set to SFN or MPRU_AGGREGATION,
UlVmimoSwitch under UlSchSwitch in the CellAlgoSwitch MO under the Cell MO must be
turned off.
- If FddTddInd, MultiRruCellFlag, and MultiRruCellMode in a Cell MO are set to
CELL_FDD, BOOLEAN_TRUE, and MPRU_AGGREGATION, respectively, UlCompSwitch
in the CellAlgoSwitch MO under the Cell MO must be set to DISABLE.
- If CellActiveState in a Cell MO is set to CELL_ACTIVE, FddTddInd is CELL_TDD
Model and DlBandWidth is CELL_BW_N25, RanShareModeSwitch in the CellAlgoSwitch
must be set OFF.
- The InterFreqBlindMlbSwitch under the MlbAlgoSwitch cannot be turned on when the Cell
is Tdd.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the settings of cell-level algorithm switches.
CELLALGOSWITCH

MOD Use this command to modify the settings of cell-level algorithm switches.
CELLALGOSWITCH

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

RACH algorithm switch RachAdjSwitch: Indicates the switch used to enable or disable random access
channel (RACH) resource adjustment, which adaptively adjusts the RACH
resources in the cell based on the access type and the number of accesses. If the
switch is turned off, RACH resource adjustment is disabled.
HoRaSwitch: Indicates the switch used to control the random access mode
applied during handovers.
If the switch is turned on, the eNodeB instructs UEs to use the non-contention-
based random access mode during handovers.
If the switch is turned off, the eNodeB instructs UEs to use the contention-based
random access mode during handovers.
UnsyncRaSwitch: Indicates the switch used to control the random access mode
applied when UEs are out of synchronization in the uplink.
If the switch is turned on, the eNodeB instructs UEs to use the non-contention-
based random access mode upon DL data arrivals in the case of out-of-
synchronization.
If the switch is turned off, the eNodeB instructs UEs to use the contention-based
random access mode upon DL data arrivals in the case of out-of-
synchronization.
MaksIdxSwitch: Indicates the switch used to control reuse of dedicated
preambles between UEs.
If the switch is turned on, the eNodeB enables reuse of dedicated preambles
among UEs based on the MaskIndex parameter.
If the switch is turned off, the eNodeB allocates a dedicated preamble to only
one UE at a time.
BackOffSwitch: Indicates the switch for backoff control.
If the switch is turned on, backoff control is enabled.
If the switch is turned off, backoff control is disabled.

SoundingRS algorithm Indicates the switch used to enable or disable change in the cell-specific SRS
switch
subframe configuration (that is, the adjustment on the setting of the
SrsSubframeCfg parameter).
If the switch is turned on, the algorithm dynamically adjusts the SRS subframe
configuration based on the usage of cell resources.
If the switch is turned off, the algorithm uses the initial configuration and does
not perform dynamic switching.

PUCCH algorithm PucchSwitch: Indicates the switch used to enable or disable the PUCCH
switch
resource adjustment algorithm.
If this switch is turned on, PUCCH resource adjustment is initiated when the
Table 2 Related parameters

Parameter Description

PUCCH resources are insufficient or excessive.


If this switch is turned off, PUCCH resource adjustment is disabled.
PucchFlexCfgSwitch: Indicates whether to enable the PUCCH flexible
configuration function. The switch setting does not take effect if the LBBPc is
configured or the cell bandwidth is 1.4 MHz or 3 MHz. When PUCCH flexible
configuration is enabled, UL ICIC and UL frequency hopping scheduling cannot
be used.
If this switch is turned on, an equal number of RBs (specified by the
PucchExtendedRBNum parameter) are separately added to both ends of the
uplink band allocated for the PUCCH. The total number of extension PUCCH
RBs equals to the PucchExtendedRBNum parameter value multiplied by two. If
this switch is turned off, this function is disabled. This parameter is valid only in
FDD mode.

AQM algorithm switch Indicates the switch that is used to enable and disable the Active Queue
Management (AQM) algorithm. If this switch is set to ON, the AQM function is
enabled to prevent or control congestion. The length of the PDCP packet queue
is maintained at a relatively small value to help achieve an appropriate trade-off
between throughput and time latency. If this switch is set to OFF, the AQM
function is disabled.

CQI adjust algorithm CqiAdjAlgoSwitch: Indicates the switch used to control whether to allow the
switch
eNodeB to adjust the UE-reported CQI based on the initial block error rate
(IBLER). If this switch is turned on, the CQI adjustment algorithm is enabled. In
this case, the eNodeB adjusts the UE-reported CQI based on the IBLER. If this
switch is turned off, the CQI adjustment algorithm is disabled. In this case, the
eNodeB does not adjust the UE-reported CQI based on the IBLER.
StepVarySwitch: Indicates the switch used to enable or disable the variable-step-
based adjustment algorithm. If this switch is turned on, the variable-step-based
adjustment algorithm is enabled to accelerate the convergence of IBLER. In this
case, rapid adjustment at large steps is applied if there is a relatively large
difference between the measured IBLER and target IBLER; fine-tuning at small
steps is applied if the measured IBLER approaches the target IBLER. If this
switch is turned off, the adjustment is performed at a fixed step.
DlVarIBLERtargetSwitch: Indicates whether to enable the downlink target initial
block error rate (IBLER) adaption. If this switch is turned on, the downlink
target IBLER is adjusted based on the size of transport blocks (TBs) to improve
the spectrum efficiency. If this switch is turned off, the downlink target IBLER
is a fixed value.
TddBundlingCqiAdjOptSwitch: Indicates the switch used to control whether to
enable optimized CQI adjustment algorithm in ACK bundling mode.If this
switch is turned on, the optimized CQI adjustment algorithm is enabled. If this
switch is turned off, the optimized CQI adjustment algorithm cannot be enabled.
Table 2 Related parameters

Parameter Description

TddMultiplexingCqiAdjOptSwitch: Indicates the switch used to control whether


to enable the optimized CQI adjustment algorithm in ACK multiplexing mode.
If this switch is turned on, the optimized CQI adjustment algorithm is enabled. If
this switch is turned off, the optimized CQI adjustment algorithm cannot be
enabled.

RLF detection algorithm Indicates the switch used to enable or disable radio link failure (RLF) detection
switch
for UL links. This parameter will be removed in later versions. In this version,
the setting of this parameter is still synchronized between the M2000 and the
eNodeB, but it is no longer used internally. Therefore, avoid using this
parameter.

Dynamic adjust voltage Indicates the switch used to enable or disable dynamic voltage adjustment. If the
algorithm switch
switch is turned on, the PA working voltage is adjusted according to the load of
the eNodeB. The purpose is to reduce power consumption of the PA and
improve energy efficiency of the eNodeB. Only FDD Cell with a bandwidth no
smaller than 5M supports dynamic voltage adjustment.

RAC algorithm switch Indicates the switches used to enable or disable the admission and load control
algorithms.
DlSwitch: Indicates the switch used to enable or disable the algorithm of
downlink admission control based on the satisfaction rate. If this switch is
turned on, the algorithm is enabled. If this switch is turned off, the algorithm is
disabled. During the calculation of the QoS satisfaction rate of services with
different QCIs, the satisfaction estimation method used dedicatedly for VoIP
services is implemented on services with the QCI of 1. If a service with the QCI
of 1 is not a VoIP service, the satisfaction rate calculated using this method is
lower than the actual value, which affects the admission of GBR services.
Therefore, if not all the services with the QCI of 1 are VoIP services, it is
recommended that this switch be turned off.
UlSwitch: Indicates the switch used to enable or disable the algorithm of uplink
admission control based on the satisfaction rate. If this switch is turned on, the
algorithm is enabled. If this switch is turned off, the algorithm is disabled.
During the calculation of the QoS satisfaction rate of services with different
QCIs, the satisfaction estimation method used dedicatedly for VoIP services is
implemented on services with the QCI of 1. If a service with the QCI of 1 is not
a VoIP service, the satisfaction rate calculated using this method is lower than
the actual value, which affects the admission of GBR services. Therefore, if not
all the services with the QCI of 1 are VoIP services, it is recommended that this
switch be turned off.
DlPredictSwitch: Indicates the switch used to enable or disable the algorithm of
downlink admission control based on prediction. If this switch is turned on, the
algorithm is enabled. If this switch is turned off, the algorithm is disabled. This
parameter will be removed in later versions. In this version, the setting of this
Table 2 Related parameters

Parameter Description

parameter is still synchronized between the M2000 and the eNodeB, but it is no
longer used internally. Therefore, avoid using this parameter.
UlPredictSwitch: Indicates the switch used to enable or disable the algorithm of
uplink admission control based on prediction. If this switch is turned on, the
algorithm is enabled. If this switch is turned off, the algorithm is disabled. This
parameter will be removed in later versions. In this version, the setting of this
parameter is still synchronized between the M2000 and the eNodeB, but it is no
longer used internally. Therefore, avoid using this parameter.
GbrUsageSwitch: Indicates the switch used to enable or disable the check on the
number of PRBs used by GBR services. If this switch is turned on, the number
of PRBs used by existing GBR services is checked before a new GBR service
can be admitted. If this switch is turned off, the number of PRBs used by
existing GBR services is not checked during admission evaluation of the GBR
services. This parameter will be removed in later versions. In this version, the
setting of this parameter is still synchronized between the M2000 and the
eNodeB, but it is no longer used internally. Therefore, avoid using this
parameter.
DlLdcSwitch: Indicates the switch used to control whether to implement load
control in the downlink of a cell. If this switch is turned on, the system checks
for congestion in the downlink of the cell. If the downlink is congested, load
control is performed. If this switch is turned off, the system does not check for
congestion in the downlink of the cell and the congestion cannot be relieved.
During the calculation of the QoS satisfaction rate of services with different
QCIs, the satisfaction estimation method used dedicatedly for VoIP services is
implemented on services with the QCI of 1. If a service with the QCI of 1 is not
a VoIP service, the satisfaction rate calculated using this method is lower than
the actual value, which affects the cell load control. Therefore, if not all the
services with the QCI of 1 are VoIP services, it is recommended that this switch
be turned off.
UlLdcSwitch: Indicates the switch used to control whether to implement load
control in the uplink of a cell. If this switch is turned on, the system checks for
congestion in the uplink of the cell. If the uplink is congested, load control is
performed. If this switch is turned off, the system does not check for congestion
in the uplink of the cell and the congestion cannot be relieved. During the
calculation of the QoS satisfaction rate of services with different QCIs, the
satisfaction estimation method used dedicatedly for VoIP services is
implemented on services with the QCI of 1. If a service with the QCI of 1 is not
a VoIP service, the satisfaction rate calculated using this method is lower than
the actual value, which affects the cell load control. Therefore, if not all the
services with the QCI of 1 are VoIP services, it is recommended that this switch
be turned off.
RelDrbSwitch: Indicates the switch used to control whether low-priority
services can be released in the case of congestion. If this switch is turned on,
low-priority services can be released. If this switch is turned off, low-priority
Table 2 Related parameters

Parameter Description

services cannot be released. This parameter will be removed in later versions. In


this version, the setting of this parameter is still synchronized between the
M2000 and the eNodeB, but it is no longer used internally. Therefore, avoid
using this parameter.
PreemptionSwitch: Indicates the switch used to enable or disable the preemption
control algorithm. If this switch is turned on, preemption can be used when the
admission of high-priority services fails. If this switch is turned off, only
emergency calls can be admitted to the system when resources are insufficient.

Load balancing Indicates the switches used to enable or disable load balancing algorithms,
algorithm switch
including the switches which are used to control the intra-frequency, intra-
frequency idle, and inter-frequency load balancing algorithms, blind inter-
frequency load balancing algorithms, and UTRAN, UTRAN idle, GERAN,
CDMA2000 and LoadInfo load sharing algorithms. If one switch is turned on,
the corresponding algorithm is enabled to balance or share the loads between
neighboring cells of the specified category.
If IntraFreqMlbSwitch is set to On, intra-frequency load balancing is enabled
and therefore IntraFreqIdleMlbSwitch becomes valid. If IntraFreqMlbSwitch is
set to Off, intra-frequency load balancing is disabled and therefore
IntraFreqIdleMlbSwitch does not take effect. This parameter will be removed in
later versions. In this version, the setting of this parameter is still synchronized
between the M2000 and the eNodeB, but it is no longer used internally.
Therefore, avoid using this parameter.
If InterFreqMlbSwitch is set to On, inter-frequency load balancing is enabled. If
InterFreqMlbSwitch is set to Off, inter-frequency load balancing is disabled.
If UtranMlbSwitch is set to On, load sharing with UTRAN is enabled. If
UtranMlbSwitch is set to Off, load sharing with UTRAN is disabled.
If GeranMlbSwitch is set to On, load sharing with GERAN is enabled. If
GeranMlbSwitch is set to Off, load sharing with GERAN is disabled.
If CdmaMlbSwitch is set to On, load sharing with CDMA2000 is enabled. If
CdmaMlbSwitch is set to Off, load sharing with CDMA2000 is disabled. This
parameter will be removed in later versions. In this version, the setting of this
parameter is still synchronized between the M2000 and the eNodeB, but it is no
longer used internally. Therefore, avoid using this parameter.
If both IntraFreqIdleMlbSwitch and IntraFreqMlbSwitch are set to On, intra-
frequency load balancing for UEs in idle mode is enabled. Otherwise, intra-
frequency idle load balancing for UEs in idle mode is disabled. This parameter
will be removed in later versions. In this version, the setting of this parameter is
still synchronized between the M2000 and the eNodeB, but it is no longer used
internally. Therefore, avoid using this parameter.
If UtranIdleMlbSwitch is set to On, load sharing with UTRAN for UEs in idle
mode is enabled. If UtranIdleMlbSwitch is set to Off, load sharing with UTRAN
for UEs in idle mode is disabled.
Table 2 Related parameters

Parameter Description

If MlbLoadInfoSwitch is set to On, whether the load sharing between an E-


UTRAN cell and an inter-RAT cell is performed based on load of the inter-RAT
cell. If MlbLoadInfoSwitch is set to Off, load of an inter-RAT cell is not
considered when the load sharing between an E-UTRAN cell and the inter-RAT
cell is performed. In load sharing between an E-UTRAN cell and an inter-RAT
cell based on load of the inter-RAT cell, the inter-RAT cell must be a UTRAN
cell. If MlbLoadInfoSwitch and UtranMlbSwitch are both set to On, the
UTRAN cells with the UMTS cell load status parameter set to Normal among all
the UTRAN cells whose load status is obtained are considered as target cells in
load sharing between an E-UTRAN cell and a UTRAN cell.
When InterFreqBlindMlbSwitch is set to On, the blind inter-frequency MLB is
enabled. When InterFreqBlindMlbSwitch is set to Off, the blind inter-frequency
MLB is disabled.InterFreqBlindMlbSwitch and InterFreqMlbSwitch cannot be
set to On simultaneously.

Downlink power control Indicates the switches used to enable or disable power control for PDSCH,
algorithm switch
PDCCH, and PHICH.
PdschSpsPcSwitch: Indicates the switch for power control during semi-
persistent scheduling on the PDSCH. If the switch is turned off, power is
allocated evenly during semi-persistent scheduling on the PDSCH. If the switch
is turned on, power control is applied during semi-persistent scheduling on the
PDSCH, ensuring communication quality (indicated by IBLER) of VoIP services
in the QPSK modulation scheme.
PhichInnerLoopPcSwitch: Indicates the switch for PHICH inner-loop power
control. If the switch is turned off, only the initial transmit power for the PHICH
is set. If the switch is turned on, the eNodeB controls the physical channel
transmit power to enable the receive SINR to converge to the target SINR.
PdcchPcSwitch: Indicates the switch for PDCCH power control. If the switch is
turned off, power is allocated evenly to PDCCH. If the switch is turned on,
power allocated to PDCCH is adjusted dynamically.
EDlMaxTXPwrSwitch: Indicates the switch for enhanced maximum TX power
of the cell. If this switch is turned off, the maximum TX power of the cell is
determined by the reference signal (RS) power and the scaling factor indexes Pa
and Pb. If this switch is turned on, the maximum TX power of the cell can be
increased to improve the RB usage in the cell. This switch has no impact on the
TDD 20M or 10M cell.

Uplink power control Indicates the switches used to enable or disable power control for PUSCH and
algorithm switch
PUCCH. CloseLoopSpsSwitch: If this switch is turned off, closed-loop power
control is not performed for PUSCH in semi-persistent scheduling mode. If this
switch is turned on, TPC commands are adjusted based on correctness of the
initially received data packet to decrease the IBLER. InnerLoopPuschSwitch: If
this switch is turned off, inner-loop power control is not performed for PUSCH
Table 2 Related parameters

Parameter Description

in dynamic scheduling mode. If this switch is turned on, inner-loop power


control is performed for PUSCH in dynamic scheduling mode.
PhSinrTarUpdateSwitch is the switch used to enable or disable PH-based SINR
target updates in dynamic scheduling mode. This switch will be removed in later
versions. In this version, the setting of this switch is still synchronized between
the M2000 and the eNodeB, but it is no longer used internally. Therefore, avoid
using this switch. This function is incorporated into inner-loop power control for
PUSCH in dynamic scheduling mode. Therefore, to enable this function, set
InnerLoopPuschSwitch to On. InnerLoopPucchSwitch: If this switch is turned
off, inner-loop power control is not performed for PUCCH. If this switch is
turned on, inner-loop power control is performed for PUCCH.
OiSinrTarUpdateSwitch: This switch will be removed in later versions. In this
version, the setting of this switch is still synchronized between the M2000 and
the eNodeB, but it is no longer used internally. Therefore, avoid using this
switch. This function is incorporated into inner-loop power control for PUSCH
in dynamic scheduling mode. Therefore, to enable this function, set
InnerLoopPuschSwitch to On. PowerSavingSwitch: This switch will be removed
in later versions. In this version, the setting of this switch is still synchronized
between the M2000 and the eNodeB, but it is no longer used internally.
Therefore, avoid using this switch.
CloseLoopOptPUSCHSwitch: If this switch is turned off, closed-loop power
control is not optimized for PUSCH in dynamic scheduling mode.If this switch
is turned on, closed-loop power control is optimized for PUSCH in dynamic
scheduling mode.

BF algorithm switch Indicates the switch that is used to enable or disable the beamforming algorithm.
If the switch is turned on, UEs in the cell can be served by the beamforming
algorithm. If the switch is turned off, UEs in the cell cannot be served by the
beamforming algorithm. The beamforming algorithm is disabled by default. It
must be enabled manually if required.

DL schedule switch Indicates the switches related to DL scheduling in the cell.


FreqSelSwitch: Indicates whether to enable frequency selective scheduling.
When this switch is turned on, data is transmitted on the frequency band in good
signal quality.
ServiceDiffSwitch: Indicates the switch used to enable or disable service
differentiation. If the switch is turned on, service differentiation is applied. If the
switch is turned off, service differentiation is not applied. This parameter will be
removed in later versions. In this version, the setting of this parameter is still
synchronized between the M2000 and the eNodeB, but it is no longer used
internally. Therefore, avoid using this parameter.
SpsSchSwitch: Indicates whether to enable semi-persistent scheduling during
talk spurts of VoIP services. If the switch is turned on, semi-persistent
scheduling is enabled during talk spurts of VoIP services. If the switch is turned
Table 2 Related parameters

Parameter Description

off, semi-persistent scheduling is disabled during talk spurts of VoIP services.


MBSFNShutDownSwitch: Indicates the switch used to enable or disable
Multimedia Broadcast Single Frequency Network (MBSFN) subframe
shutdown. If the switch is turned on, MBSFN subframe shutdown is applied. If
the switch is turned off, MBSFN subframe shutdown is not applied. This switch
is valid only when symbol-based power amplifier (PA) shutdown is enabled. If
MBSFNShutDownSwitch is turned on, the switch for the mapping from SIBs to
SI messages becomes invalid. The latter can be specified by the SiMapSwitch
parameter in the CellSiMap MO. If MBSFNShutDownSwitch is turned off, the
switch for the mapping from SIBs to SI messages becomes valid. MBSFN
subframe shutdown applies only to single-mode eNodeBs.
NonGbrBundlingSwitch: Indicates the switch used to enable or disable DL non-
GBR packet bundling. If this switch is turned on, delay of non-GBR services
can be controlled in non-congestion scenarios. If this switch is turned off, delay
of non-GBR services cannot be controlled.
EnAperiodicCqiRptSwitch: Indicates whether to enable enhanced aperiodic
channel quality indicator (CQI) reporting. If this switch is turned on, the
eNodeB triggers aperiodic CQI reporting for a UE based on downlink services
of the UE and the interval at which the UE sends periodic CQI reports. If this
switch is turned off, UEs under non-frequency selective scheduling do not
trigger aperiodic CQI reporting based on downlink services and triggers an
aperiodic CQI reporting if no valid periodic CQI reports are sent in eight
consecutive periodic CQI reporting periods.

Uplink schedule switch Indicates the switches related to uplink (UL) scheduling in the cell. The switches
are used to enable or disable specific UL scheduling functions.
SpsSchSwitch: Indicates whether to enable or disable semi-persistent scheduling
during talk spurts of VoIP services. If this switch is turned on, semi-persistent
scheduling is applied. If this switch is turned off, dynamic scheduling is applied.
SinrAdjustSwitch: Indicates whether to adjust the measured SINR based on
ACK/NACK messages in a UL HARQ process.
PreAllocationSwitch: Indicates whether to enable preallocation in the uplink.
When this switch is on: (1) if SmartPreAllocationSwitch is off and a UE is in the
discontinuous reception (DRX) state, preallocation is disabled for the UE in the
uplink; (2) if SmartPreAllocationSwitch is off and the UE is not in the DRX
state, preallocation is enabled for the UE in the uplink; (3) if
SmartPreAllocationSwitch is on and the SmartPreAllocationDuration parameter
value is greater than 0, smart preallocation is enabled for the UE in the uplink;
(4) if SmartPreAllocationSwitch is on and the SmartPreAllocationDuration
parameter value is 0, preallocation is disabled for the UE in the uplink. If this
switch is off, preallocation is disabled for the UE in the uplink.
UlVmimoSwitch: Indicates whether to enable or disable UL MU-MIMO. If UL
MU-MIMO is enabled, the eNodeB selects UEs for pairing according to pairing
Table 2 Related parameters

Parameter Description

rules. Then, the pair of UEs transmits data using the same frequency-time
resources, increasing system throughput and spectral efficiency.
TtiBundlingSwitch: Indicates whether to enable or disable TTI bundling. If TTI
bundling is enabled, more transmission opportunities are available to UEs within
the delay budget for VoIP services on the air interface, thereby improving uplink
coverage.
ImIcSwitch: Indicates whether to enable or disable intermodulation (IM)
component elimination for UEs. When data is transmitted in both UL and DL,
two IM components are generated symmetrically beside the Direct Current (DC)
subcarrier on the DL receive channel due to interference from UL radio signals.
If this switch is turned on, IM component elimination is performed on UEs. If
this switch is turned off, IM component elimination is not performed on UEs.
This switch applies only to FDD cells working in band 20.
SmartPreAllocationSwitch: Indicates whether to enable uplink smart
preallocation when preallocation is enabled (by turning on
PreAllocationSwitch). If both PreAllocationSwitch and
SmartPreAllocationSwitch are set to On, and SmartPreAllocationDuration is set
to a value greater than 0, uplink smart preallocation is enabled. Otherwise,
uplink smart preallocation is disabled.
PuschDtxSwitch: Indicates whether the eNodeB uses the physical uplink shared
channel (PUSCH) discontinuous transmission (DTX) detection result during
uplink (UL) scheduling. If this switch is turned on, based on the PUSCH DTX
detection result, the eNodeB determines whether to perform adaptive
retransmission during UL scheduling and also adjusts the control channel
element (CCE) aggregation level of the physical downlink control channel
(PDCCH) carrying downlink control information (DCI) format 0. This switch
takes effect only on FDD cells. If an FDD cell is established on an LBBPc, this
switch takes effect only when the cell uses less than four RX antennas and
normal cyclic prefix (CP) in the uplink, and the SrsCfgInd parameter in the
SRSCfg MO is set to BOOLEAN_TRUE. Note that the LBBPc does not support
PUSCH DTX detection for UEs with multi-user MIMO (MU-MIMO) applied.
UlIblerAdjustSwitch: Indicates whether to enable uplink IBLER adjustment
algorithm. When this switch is turned on, it Changes the IBLER restraining goal
for upgrading the turnover rate of cell edge.
UlEnhancedFssSwitch:Indicates whether to enable the uplink load-based
frequency selection enhancement.This switch is valid only in FDD mode.
UlEnhancedSrSchSwitch:Indicates whether uplink re-scheduling is performed
only when the On Duration timer for the DRX long cycle starts. Uplink re-
scheduling is required if the number of hybrid automatic repeat request (HARQ)
retransmissions for a scheduling request (SR) reaches the maximum value but
the scheduling still fails. If this switch is turned on, uplink re-scheduling is
performed only when the On Duration timer for the DRX long cycle starts. If
this switch is turned off, uplink re-scheduling is performed immediately after the
Table 2 Related parameters

Parameter Description

number of HARQ retransmissions for SR reaches the maximum value but the
scheduling still fails. It is recommended that the switch be turned on in live
networks.
SchedulerCtrlPowerSwitch:Indicates whether the uplink scheduler performs
scheduling without considering power control restrictions. If this switch is
turned on, the uplink scheduler performs scheduling without considering power
control restrictions, which ensures full utilization of the transmit power for all
UEs. If this switch is turned off, the uplink scheduler considers power control
restrictions while performing scheduling, which prevents full utilization of the
transmit power for UEs at far or medium distances from cell center.

RAN Sharing Mode Indicates whether to enable or disable RAN sharing for admission and
Switch
scheduling. If this switch is turned on, operators share data channel resources
according to the specified percentages.

Based on Frequency Indicates the switch related to the frequency-priority-based inter-frequency


Priority HO Switch
handover. FreqPriorIFHOSwitch: Indicates the frequency-priority-based inter-
frequency handover switch.Frequency-priority-based inter-frequency handover
is applicable when the eNodeB provides dual coverage and one frequency is
preferred for carrying services. If this switch is set to On, the frequency-priority-
based inter-frequency handover will be triggered even when the serving cell
provides a good signal quality. If this switch is set to Off, the frequency-priority-
based inter-frequency handover is disabled. The inter-frequency handover can
only be triggered when other conditions for triggering inter-frequency handovers
are met.FreqPriorIFBlindHOSwitch: Indicates the frequency-priority-based
inter-frequency blind handover switch. If this switch is set to On, the frequency-
priority-based inter-frequency blind handover is enabled. If this switch is set to
Off, the eNodeB decides whether to perform the frequency-priority-based inter-
frequency handover based on measurements. This switch is valid only when
FreqPriorIFHOSwitch is set to On.

MUBF algorithm switch Indicates the switch used to enable or disable the multi-user beamforming
algorithm.
If this switch and the switch for the beamforming algorithm are both turned on,
the multi-user beamforming algorithm is enabled.
If this switch is turned off, the multi-user beamforming algorithm is disabled.

Distance-based Indicates the switch used to enable or disable distance-based handovers. If this
Handover Switch
switch is turned on, distance-based handovers are allowed. If this switch is
turned off, distance-based handovers are prohibited.

AcBar algorithms switch Indicates the switch for the access barring algorithm. If this parameter is set to
ACBAR_SWITCH_DYNAMIC, dynamic access barring is enabled. In this
situation, the access probability factor and the average access barring duration
Table 2 Related parameters

Parameter Description

for mobile-originated calls are dynamically adjusted based on the current cell
load. If this parameter is set to ACBAR_SWITCH_STATIC, static access
barring is also enabled. In this situation, the access probability factor and the
average access barring duration for mobile-originated calls are configured in the
access barring information. If this parameter is set to
ACBAR_SWITCH_DISABLE, access barring is disabled.

UlCoMP algorithms Indicates the switch used to enable or disable the UL CoMP algorithm.
switch

MRC/IRC adaptation Indicates the switch used to enable or disable MRC/IRC adaptation on PUSCH.
switch

SFN UL Scheduling Indicates the switch for SFN UL scheduling. It is used to set SFN UL scheduling
Switch
to joint scheduling mode, or auto-selection mode between joint scheduling and
independent scheduling.

SFN DL Scheduling Indicates the switch for SFN DL scheduling. It is used to set SFN DL scheduling
Switch
to joint scheduling mode, or auto-selection mode between joint scheduling and
independent scheduling.

IRC Switch Indicates the switch used to enable or disable MRC/IRC adaptation on PUCCH
or PRACH. LBBPc boards do not support this function.

Dynamic DRX switch Indicates whether to enable the dynamic discontinuous reception (DRX) feature.
If this switch is turned on, the dynamic DRX feature is applied to newly
admitted UE to reduce the signaling overhead and decrease UE power
consumption. If this switch is turned off, the dynamic DRX feature is not
applied to newly admitted UEs. The dynamic DRX feature applies to carrier
aggregation (CA) UEs only when this switch is turned on in both the PCell and
SCell. If the DynDrxSwitch(DynDrxSwitch) option is selected, the
DrxAlgSwitch parameter cannot control DRX for UEs in the synchronized state.

High Mobility Triggered Indicates whether to enable the high-mobility-triggered-idle switch. When this
Idle Mode Switch
parameter is set to ENABLE, UEs in high mobility are released and enter the
idle mode, and therefore the signaling impact on the network caused by frequent
handovers are reduced. When this parameter is set to DISABLED, UEs in high
mobility are not released.

Interference avoidance Indicates whether to enable the function of avoiding interference from adjacent
switch
GERAN cells. If AvoidGeranInterfSwitch is set to On, GL bufferzone
optimization is enabled.
Before turning on this switch, pay attention to the following:
(1) The cell bandwidth must be changed to its next higher standard bandwidth
level. For example, the bandwidth of a 15-MHz cell must be changed to 20
Table 2 Related parameters

Parameter Description

MHz.
(2) It is recommended that this switch be turned off if the bandwidth of a cell is
1.4, 3, 5, or 10 MHz.
(3) To avoid interference to the PUCCH from adjacent GERAN cells, the
PUCCH flexible configuration switch must also be turned on, which can be
specified by PucchFlexCfgSwitch under the PucchAlgoSwitch parameter.

GL power share switch Indicates the switch used to enable or disable the GL dynamic power sharing
algorithm. This algorithm can be used when the GSM and LTE carriers share the
same power amplifier. This improves power usage and service quality of LTE
UEs adopting quadrature phase shift keying (QPSK) as their modulation scheme
in case that the GSM and LTE busy hours appear at different time points or that
the traffic is unbalanced. This parameter indicates the switch for the GL dynamic
power sharing feature at the LTE side.

eIcic switch Indicates the switch used to enable or disable the TDM-based eICIC function. If
this switch is turned on, the TDM-based eICIC function is enabled. If this switch
is turned off, the TDM-based eICIC function is disabled. In a heterogeneous
network (HetNet), this function is used together with the range expansion
function of the micro to expand the coverage of micro cells, and increase the
number of users absorbed by the micro cell. To support TDM-based eICIC, this
function must be enabled for both the macro and micro cells.

PUCCH resource Indicates the switch used to control whether PUCCH resources are allocated
switch based on UL
peak rate based on the UL peak rate. If this switch is turned on, resources are flexibly
allocated to PUCCH. When there is only a few UEs, the PUCCH is allocated
with less RBs. This maximizes the number of PUSCH RBs available to each
UE.

Downlink CoMP Indicates the switch used to enable or disable the DL CoMP algorithm.
algorithms switch

PSIC algorithm switch Indicates the switch used to enable or disable the parallel soft interference
cancellation (PSIC) algorithm in a cell.

Load Balancing Indicates whether to enable or disable handovers triggered by the load balancing
Handover Policy
algorithm, based on which the eNodeB determines handover policies.
When a load-based handover to an inter-frequency neighboring cell in E-
UTRAN is to be performed, the inter-frequency blind handover is preferentially
performed if InterFreqMlbBlindHo is set to ON, and the inter-frequency blind
handover is not performed if InterFreqMlbBlindHo is set to OFF.
When a load-based handover from an E-UTRAN cell to a UTRAN or GERAN
cell is to be performed, the inter-RAT blind handover is preferentially performed
if InterRatMlbBlindHo is set to ON, and the inter-RAT blind handover is not
Table 2 Related parameters

Parameter Description

performed if InterRatMlbBlindHo is set to OFF.

SFN Load-based Indicates whether to enable load-based adaptive adjustment in the adaptive
Adaptive Switch
SFN/SDMA feature.If this switch is turned on, load-based adaptive adjustment
is enabled, which increases the proportion of joint-scheduling UEs and improves
user experience when the network load is light, and increases the proportion of
dependent-scheduling UEs and ensures the spectral efficiency when the network
load is heavy.If this switch is turned off, load-based adaptive adjustment in the
adaptive SFN/SDMA feature cannot be enabled.

5.7.1.6.3.23 CellBf
+-NE
+-eNodeBFunction
+-Cell
+-CellBf

Description

The CellBf MO consists of the parameters related to beamforming in the cell.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

DSP Use this command to query the cell channel calibration result.
CELLCALIBRATION

LST CELLBF Use this command to list the information used to control the single-stream or
dual-stream beamforming.

MOD CELLBF Use this command to modify the information used to control the single-stream
or dual-stream beamforming.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the cell ID of the local cell. It uniquely identifies a cell within an
eNodeB.

Beamforming maximum Indicates the maximum number of beamforming layers, that is, the rank of
number of layers
beamforming. The value SINGLE_LAYER_BF indicates single-stream
beamforming (that is, beamforming with the rank of 1), and the value
DUAL_LAYER_BF indicates dual-stream beamforming (that is, beamforming
with the rank of 2).

Latest operation Indicates the result after the last cell channel rectification.

Second latest operation Indicates the result after the second from the last cell channel rectification.

Third latest operation Indicates the result after the third from the last cell channel rectification.

Fourth latest operation Indicates the result after the fourth from the last cell channel rectification.

Fifth latest operation Indicates the result after the fifth from the last cell channel rectification.

Sixth latest operation Indicates the result after the sixth from the last cell channel rectification.

Seventh latest Indicates the result after the seventh from the last cell channel rectification.
operation

Eighth latest operation Indicates the result after the eighth from the last cell channel rectification.
Table 2 Related parameters

Parameter Description

Ninth latest operation Indicates the result after the ninth from the last cell channel rectification.

Tenth latest operation Indicates the result after the tenth from the last cell channel rectification.

Latest operation time Indicates the time after the last cell channel rectification.

Second latest operation Indicates the time after the second from the last cell channel rectification.
time

Third latest operation Indicates the time after the third from the last cell channel rectification.
time

Fourth latest operation Indicates the time after the fourth from the last cell channel rectification.
time

Fifth latest operation Indicates the time after the fifth from the last cell channel rectification.
time

Sixth latest operation Indicates the time after the sixth from the last cell channel rectification.
time

Seventh latest Indicates the time after the seventh from the last cell channel rectification.
operation time

Eighth latest operation Indicates the time after the eighth from the last cell channel rectification.
time

Ninth latest operation Indicates the time after the ninth from the last cell channel rectification.
time

Tenth latest operation Indicates the time after the tenth from the last cell channel rectification.
time

Latest operation type Indicates the type after the last cell channel rectification.

Second latest operation Indicates the type after the second from the last cell channel rectification.
type

Third latest operation Indicates the type after the third from the last cell channel rectification.
type

Fourth latest operation Indicates the type after the fourth from the last cell channel rectification.
type

Fifth latest operation Indicates the type after the fifth from the last cell channel rectification.
type

Sixth latest operation Indicates the type after the sixth from the last cell channel rectification.
type

Seventh latest Indicates the type after the seventh from the last cell channel rectification.
operation type

Eighth latest operation Indicates the type after the eighth from the last cell channel rectification.
type
Table 2 Related parameters

Parameter Description

Ninth latest operation Indicates the type after the ninth from the last cell channel rectification.
type

Tenth latest operation Indicates the type after the tenth from the last cell channel rectification.
type

5.7.1.6.3.24 CellChPwrCfg
+-NE
+-eNodeBFunction
+-Cell
+-CellChPwrCfg

Description

The CellChPwrCfg MO consists of the parameters related to the power for all types of channels
in the cell. It is also used in DL power control.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST CELLCHPWRCFG Use this command to list the parameters of the cell channel power configuraion.
Table 1 Related MML commands

MML Command Function

MOD Use this command to modify the configuration of cell channel power.
CELLCHPWRCFG

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

PCFICH power Indicates the offset of the PCFICH transmit power relative to the reference
signal power.

PBCH power Indicates the offset of the PBCH transmit power relative to the reference signal
power.

SCH power Indicates the offset of the transmit power for the cell synchronization signals
relative to the reference signal power.

DBCH power Indicates the offset of the transmit power for broadcast information on the
PDSCH channel relative to the reference signal power.

PCH power Indicates the offset of the transmit power for the paging information on the
PDSCH channel relative to the reference signal power.

Rach response power Indicates the offset of the transmit power for the random access responses on the
PDSCH channel relative to the reference signal power.

Prs power Indicates the offset of the pilot power relative to the reference signal power.

5.7.1.6.3.25 CellDlCompAlgo
+-NE
+-eNodeBFunction
+-Cell
+-CellDlCompAlgo

Description

The CellDlCompAlgo MO defines the offset for DL CoMP event A3. This offset is delivered
with the RRC Connection Reconfiguration message. For details, see 3GPP TS 36.331.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the Cell MO:


- LocalCellId in an CellDlCompAlgo MO must have been set in the associated Cell MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the downlink coordinated multi-point (CoMP)
CELLDLCOMPALGO
algorithm.

MOD Use this command to modify the downlink coordinated multi-point (CoMP)
CELLDLCOMPALGO
algorithm.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

LocalCellId Indicates the local identity of the cell. It uniquely identifies a cell within an
eNodeB.
Table 2 Related parameters

Parameter Description

DlCompA3Offset Indicates the offset for reporting the downlink CoMP measurement event. This
offset is the difference between the signal quality of a neighboring cell and that
of the serving cell. A larger value indicates that a neighboring cell must have
better quality for reporting the event. For details, see 3GPP TS 36.331.

5.7.1.6.3.26 CellDlIcic
+-NE
+-eNodeBFunction
+-Cell
+-CellDlIcic

Description

The CellDlIcic MO consists of the parameters related to DL ICIC in the cell. It is used to set the
band division scheme adopted by DL ICIC in the cell.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST CELLDLICIC Use this command to list the configuration of cell DL ICIC algorithm.
Table 1 Related MML commands

MML Command Function

MOD CELLDLICIC Use this command to modify the configuration of cell DL ICIC algorithm.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Downlink band division Indicates the band division scheme used in downlink ICIC. The band division in
scheme
the cell is adjusted according to the setting of this parameter so that the edge
bands for neighboring cells do not overlap. If this parameter is set to INVALID,
the cell does not distinguish center and edge bands.

User Attribution Gfactor Indicates the G factor threshold for user attribute determination in downlink
Threshold
adaptive Inter-Cell Interference Coordination (ICIC). If downlink adaptive ICIC
is enabled, the eNodeB selects cell edge users (CEUs) from the users whose G
factors are less than this threshold. Determine the parameter value based on the
distribution of UEs' modulation and coding scheme (MCS) indexes within an
area so that about one third users are determined to be CEUs. For example, if an
area is covered by 155 cells and the percentages of users whose MCS indexes
are less than 6 and 7 are about 30% and 40%, respectively, you can set this
parameter to 1. (The G factors corresponding to MCS indexes 6 and 7 are 0.5 dB
and 1.45 dB, respectively.) The G factors corresponding to MCS indexes 0 to 28
are -5.65, -4.5, -3.55, -2.35, -1.5, -0.5, 0.5, 1.45, 2.45, 3.4, 3.7, 4.4, 5.4, 6.3,
7.25, 8.3, 8.95, 9.6, 10.15, 11.15, 12.1, 13.15, 14.05, 15.1, 16, 17, 18.1, 19, 20.1,
and respectively.

Noise User RSRP Indicates the reference signal received power (RSRP) threshold for determining
Threshold
noise-afflicted UEs (that is, UEs that are mainly affected by noise) within a
network. If all RSRP values of neighboring cells included in A3 reports sent by a
UE are less than or equal to this threshold, the event A3 is not considered in
interference calculation.In general scenarios, the recommended value of this
parameter is -102. In tests for small-scale networks, this parameter can set to
other values.
5.7.1.6.3.27 CellDLIcicMcPara
+-NE
+-eNodeBFunction
+-Cell
+-CellDLIcicMcPara

Description

The CellDLIcicMcPara MO consists of the parameters related to intra-RAT measurement for


inter-cell interference coordination (ICIC) in DL of the cell. As a UE moves, the signal qualities
of both the serving cell and the neighboring cell changes. This will trigger a DL ICIC
measurement event or stop the event, based on which the UE location can be updated timely.
These parameters are contained in the RRCConnectionReconfiguration message. For details, see
3GPP TS 36.331.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the measurement control parameters related to DL
CELLDLICICMCPARA
ICIC.

MOD Use this command to modify the measurement control parameters related to DL
CELLDLICICMCPARA
ICIC.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Downlink ICIC Indicates the interval between periodic measurement reports that are sent after a
measurement report
interval DL ICIC measurement event is triggered. For details, see 3GPP TS 36.331.

Downlink ICIC Indicates the maximum number of cells to be included in each measurement
measurement max
report cell number report after a DL ICIC measurement event is triggered. For details, see 3GPP TS
36.331.

DownLink ICIC Indicates the number of periodic measurement reports after a DL ICIC
measurement report
amount measurement event is triggered. For details, see 3GPP TS 36.331.

DownLink ICIC Indicates the quantity to be included in the measurement report after a DL ICIC
measurement report
quantity measurement event is triggered, which can be set to SAME_AS_TRIG_QUAN
or BOTH.
The value SAME_AS_TRIG_QUAN indicates that the quantity to be included is
the same as that specified by the TriggerQuantity parameter. The value BOTH
indicates that both RSRP and RSRQ values are included.
The measured RSRP values are stable, varying little with the load, and therefore
there is little signal fluctuation. The measured RSRQ values vary with the load
and are likely to reflect the signal quality of the cell in real time. For details, see
3GPP TS 36.331.

DownLink ICIC Indicates the quantity used in the evaluation of a DL ICIC measurement event.
measurement trigger
quantity The quantity can be RSRP or RSRQ. The measured RSRP values are stable,
varying little with the load, and therefore there is little signal fluctuation. The
measured RSRQ values vary with the load but are likely to reflect the signal
quality of the cell in real time.

DownLink ICIC Indicates the hysteresis for the DL ICIC measurement event. This parameter is
measurement
hysteresis used to decrease frequent triggering of event evaluations due to radio signal
fluctuations. For details, see 3GPP TS 36.331.

DownLink ICIC Indicates the time-to-trigger for the DL ICIC measurement event. When
measurement time to
trigger detecting that the signal quality in the serving cell and that in at least one
neighboring cell meet the entering condition, the UE does not send a
measurement report to the eNodeB immediately. Instead, the UE sends a report
only when the signal quality continuously meets the entering condition during
the time-to-trigger.

Downlink ICIC A3 offset Indicates the offset for DL ICIC event A3. This offset is the difference between
the quality of a neighboring cell and that of the serving cell. A larger value
indicates that a neighboring cell must have better quality for the reporting of the
Table 2 Related parameters

Parameter Description

event.

Downlink ICIC A6 offset Indicates the offset for DL ICIC event A6. This offset is the difference between
the quality of a neighboring cell and that of the serving cell. A larger value
indicates that a neighboring cell must have better quality for the reporting of the
event.

5.7.1.6.3.28 CellDlpcPdcch
+-NE
+-eNodeBFunction
+-Cell
+-CellDlpcPdcch

Description

The CellDlpcPdcch MO consists of the parameters related to Physical Downlink Control


Channel (PDCCH) power control.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

LST Use this command to list the configuration of power control on the PDCCH in a
CELLDLPCPDCCH
cell.

MOD Use this command to modify the configuration of power control on the PDCCH
CELLDLPCPDCCH
in a cell.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

DCI power offset for Indicates the offset of the DCI power relative to the reference signal power when
dedicated control
the PDCCH channel carries dedicated control information.

5.7.1.6.3.29 CellDlpcPdsch
+-NE
+-eNodeBFunction
+-Cell
+-CellDlpcPdsch

Description

The CellDlpcPdsch MO consists of the parameters related to PDSCH power control. It is used
for the PDSCH power control.

Effective Scenario

Immediately

Relations Between MOs


Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the configuration of cell PDSCH downlink power
CELLDLPCPDSCH
control.

MOD Use this command to modify the configuration of cell PDSCH downlink power
CELLDLPCPDSCH
control.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Center UE PA Indicates the PA value of cell center UEs when DL ICIC is enabled.

Edge UE PA Indicates the PA value of cell edge UEs when DL ICIC is enabled.

5.7.1.6.3.30 CellDlpcPdschPa
+-NE
+-eNodeBFunction
+-Cell
+-CellDlpcPdschPa

Description
The CellDlPcPdschPa MO contains the PA parameters related to power control for the Physical
Downlink Shared Channel (PDSCH).

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the PA parameters related to power control for the
CELLDLPCPDSCHPA
PDSCH.

MOD Use this command to modify the PA parameters related to power control for the
CELLDLPCPDSCHPA
PDSCH.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

PA adjusting switch Indicates the switch for adjusting the PA through power control on the PDSCH.
If this parameter is set to ON, the PA is adjusted dynamically when the channel
quality is extremely good or bad.

PA for even power Indicates the PA to be used when PA adjustment for PDSCH power control is
distribution
disabled, DL ICIC is disabled, and the even power distribution is used for the
PDSCH.
5.7.1.6.3.31 CellDlpcPhich
+-NE
+-eNodeBFunction
+-Cell
+-CellDlpcPhich

Description

The CellDlpcPhich MO consists of the parameters related to PHICH power control. It is used for
the PHICH power control.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST CELLDLPCPHICH Use this command to list the configuration of cell PHICH downlink power
control.

MOD Use this command to modify the configuration of cell PHICH downlink power
CELLDLPCPHICH
control.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Phich Pc Off Power Indicates the power offset between the PHICH TX power and the RS power.
Offset
This offset is used when PHICH power control is disabled.

5.7.1.6.3.32 CellDlschAlgo
+-NE
+-eNodeBFunction
+-Cell
+-CellDlschAlgo

Description

The CellDlschAlgo MO consists of the parameters related to cell DL scheduling parameters. The
DL scheduling parameters determine the policy and other configurations of DL scheduling.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the configuration of the cell DL scheduling algorithm.
CELLDLSCHALGO
Table 1 Related MML commands

MML Command Function

MOD Use this command to modify the configuration of the cell DL scheduling
CELLDLSCHALGO
algorithm.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Downlink scheduling Indicates the switch of the DL scheduling policy. According to the Max C/I
Strategy
scheduling policy, the UE with good-quality channels are scheduled and hence
the spectral efficiency is very high. The QoS and fairness among users, however,
cannot be ensured. The Max C/I scheduling policy can be used to verify the
maximum capacity of the system. The RR scheduling policy is the fairest
scheduling policy. When RR is adopted, the system capacity is the smallest.
Therefore, RR is used only to verify the upper bound of the scheduling fairness
in the system. In terms of the scheduling effect, the PF scheduling policy is
between the previous two policies. Therefore, PF can be used to verify the
capacity, coverage, and fairness of the system. The EPF scheduling policy
supports the features such as user QoS, system capacity, and channel frequency
selection. The basic scheduling policy is mainly used for the performance test
purpose. During common operation, the EPF scheduling policy is recommended.

Free Users Downlink Indicates the percentage of free shared RBs on the PDSCH in scheduling based
RB Ratio
on pay-free users and pay users. The other RBs on the PDSCH are allocated to
pay users. When sufficient capacity is available, the percentage of RBs occupied
by pay-free users and that occupied by pay users will reach the preset values.
Changes in this parameter affect the percentage of RBs for pay-free users and
that for pay users. Modifying the value of this parameter for an active cell will
lead to the re-setup of the cell.

P2P Service Weight Indicates the weight of the point-to-point (P2P) service, which is used in
enhanced proportional fair (EPF) scheduling. The value of this parameter is used
in calculating the priority of a UE during scheduling and therefore determines
the amount of physical resources to be allocated to the UE that requests the P2P
service. The P2P service priority has a positive correlation with the value of this
parameter. This parameter is valid only when the service differentiation function
is enabled. This parameter will be removed in later versions. In this version, the
Table 2 Related parameters

Parameter Description

setting of this parameter is still synchronized between the M2000 and the
eNodeB, but it is no longer used internally. Therefore, avoid using this
parameter.

Other Service Weight Indicates the weight of the non-P2P service used in enhanced proportional fair
(EPF) scheduling. The value of this parameter is used in calculating the priority
of a UE during scheduling and therefore determines the amount of physical
resources to be allocated to the UE that requests the non-P2P service. The
priority of the non-P2P service has a positive correlation with the value of this
parameter. This parameter is valid only when the service differentiation function
is enabled. This parameter will be removed in later versions. In this version, the
setting of this parameter is still synchronized between the M2000 and the
eNodeB, but it is no longer used internally. Therefore, avoid using this
parameter.

maximum number of Indicates the maximum number of layers (the rank) in the implementation of
MIMO layers
multiple-input multiple-output (MIMO) in DL scheduling.

Downlink CA Schedule Indicates the scheduling policy used when CA is applied, which can be basic
Strategy
scheduling or differentiated scheduling. If the CA basic scheduling policy is
adopted, the eNodeB calculates the proportional fair (PF) scheduling priority of
each component carrier (CC) for a CA UE using the total data rates on both CCs
of this CA UE. In this way, CA UEs and non-CA UEs can be allocated similar
number of RBs. If the CA differentiated scheduling policy is adopted, the
eNodeB calculates the PF scheduling priority of each CC for a CA UE using the
data rate only on the primary component carrier (PCC) or secondary component
carrier (SCC) of this CA UE. In this way, CA UEs can achieve better
performance than non-CA UEs.

Reserved resource ratio Indicates the proportion of resources reserved for non-GBR services. A
for non-GBR services
proportion of resources is reserved periodically to prevent non-GBR services
from failing to be allocated resources. During the periods when resources are
reserved, resources are scheduled preferentially for non-GBR services. If this
parameter is set to 0, resources are not reserved for non-GBR services.

Downlink EPF capacity Indicates the capacity factor for downlink enhanced proportional fair (EPF)
factor
scheduling. This factor affects the scheduling priorities of UEs running services
with the QCI of 6, 7, 8, or 9, and accordingly can be used to adjust the cell
capacity and fairness among users.

RB Priority MCS Select Indicates the selection ratio threshold for the function of lowering the
Ratio Threshold
modulation and coding scheme (MCS) index to increase the number of resource
blocks (RBs) with priority for UEs running services with small packets. The
value 0 indicates that the function of lowering the MCS index is disabled. The
Table 2 Related parameters

Parameter Description

value 100 indicates that the function is always enabled.

Cell Edge User RB Indicates resource block (RB) allocation modes for cell edge users (CEUs) when
Allocation Mode
downlink ICIC is enabled. If this parameter is set to ALL_EDGE_USER, RBs
are allocated to all CEUs in the current transmission time interval (TTI) after
RBs are allocated to cell center users (CCUs). If this parameter is set to
PART_EDGE_USER, RBs are allocated to CEUs that have not been allocated
RBs after RBs are allocated to CCUs.

Downlink ICIC Indicates the scheduling policy used when downlink ICIC is enabled. If this
Schedule Mode
parameter is set to EDGE_USER_NO_PRIO, both cell center users (CCUs) and
cell edge users (CEUs) can preempt edge bands, thereby improving CCUs'
performance. If this parameter is set to EDGE_USER_PRIO, CCUs are
scheduled at both the center band and the edge band only after CEUs have been
scheduled at the edge band, and therefore CEUs' performance increases.

RBG Resource Indicates the resource block group (RBG) allocation strategy, which is used to
Allocation Strategy
adjust spectral efficiency and throughput of the cell. Consider the situation
where the number of required RBGs is greater than N but less than N+1 (where
N > 1). If this parameter is set to ROUND_DOWN(Round Down), RBs of N
RBGs are allocated to UEs in the current transmission time interval (TTI) and
the remaining RBs are allocated to UEs in the next TTI. If this parameter is set
to ROUND_UP(Round Up), RBs of N+1 RBGs are allocated to UEs in the
current TTI.

5.7.1.6.3.33 CellDrxPara
+-NE
+-eNodeBFunction
+-Cell
+-CellDrxPara

Description

A CellDrxPara MO consists of cell-level Discontinuous Reception (DRX) parameters. This MO


is used to configure traffic volume thresholds for UEs to enter and exit the DRX mode and the
length of the UE traffic measurement period. Whether to enable DRX depends on the
measurement result within a UE traffic measurement period.
Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST CELLDRXPARA Use this command to list DRX parameters of a cell.

MOD CELLDRXPARA Use this command to modify DRX parameters of a cell.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

FDD enter DRX Indicates the threshold for UEs to enter the discontinuous reception (DRX)
threshold
mode in a cell that operates in FDD mode. This threshold is used in the DRX
algorithm. It is expressed as a proportion of the transmission time intervals
(TTIs) with data transmission to the total TTIs. If the measurement result of UE
traffic is equal to or lower than this threshold, the eNodeB determines that the
UE should remain in DRX mode or the UE should be triggered to enter DRX
mode. If both the values of the FddExitDrxThd and FddEnterDrxThd parameters
are small and close to each other, the UE frequently enters and exits the DRX
mode. When both the FddEnterDrxThd parameter and the FddExitDrxThd
parameter are set to 1000 and DRX is enabled, the eNodeB directly determines
that the UE should enter or exit the DRX mode, but not according to the
measurement result of UE traffic.
Table 2 Related parameters

Parameter Description

FDD exit DRX threshold Indicates the threshold for UEs to exit the discontinuous reception (DRX) mode
in a cell that operates in FDD mode. This threshold is used in the DRX
algorithm. It is expressed as a proportion of the transmission time intervals
(TTIs) with data transmission to the total TTIs. If the measurement result of UE
traffic is higher than this threshold, the eNodeB determines that the UE should
remain in the non-DRX mode or the UE should be triggered to exit the DRX
mode. If the value of the FddExitDrxThd parameter is set to 1000 and the value
of the FddEnterDrxThd parameter is set to a value smaller than 1000, the UE
will not exit the DRX mode once entering the DRX mode. If both the values of
the FddExitDrxThd and FddEnterDrxThd parameters are small and close to each
other, the UE frequently enters and exits the DRX mode. When both the
FddEnterDrxThd parameter and the FddExitDrxThd parameter are set to 1000
and DRX is enabled, the eNodeB directly determines that the UE should enter or
exit the DRX mode, but not according to the measurement result of UE traffic.

TDD enter DRX Indicates the uplink traffic volume threshold for UEs to enter DRX in the cell
threshold Uplink
that operates in TDD mode. This threshold is used in the DRX algorithm. It is
expressed as a proportion of the transmission time intervals (TTIs) with uplink
data transmission to the total TTIs. If the traffic volume at a UE is equal to or
lower than this threshold, the eNodeB decides that the UE should retain its DRX
state or enter DRX.

TDD exit DRX threshold Indicates the uplink traffic volume threshold for UEs to exit DRX in the cell that
Uplink
operates in TDD mode. This threshold is used in the DRX algorithm. It is
expressed as a proportion of the transmission time intervals (TTIs) with uplink
data transmission to the total TTIs. If the traffic volume at a UE is equal to or
higher than this threshold, the eNodeB decides that the UE should retain its non-
DRX state or exit DRX.

TDD enter DRX Indicates the downlink traffic volume threshold for UEs to enter DRX in the cell
threshold Downlink
that operates in TDD mode. This threshold is used in the DRX algorithm. It is
expressed as a proportion of the transmission time intervals (TTIs) with
downlink data transmission to the total TTIs. If the traffic volume at a UE is
equal to or lower than this threshold, the eNodeB decides that the UE should
retain its DRX state or enter DRX.

TDD exit DRX threshold Indicates the downlink traffic volume threshold for UEs to exit DRX in the cell
Downlink
that operates in TDD mode. This threshold is used in the DRX algorithm. It is
expressed as a proportion of the transmission time intervals (TTIs) with
downlink data transmission to the total TTIs. If the traffic volume at a UE is
equal to or higher than this threshold, the eNodeB decides that the UE should
retain its non-DRX state or exit DRX.

Data amount Statistic Indicates the length of the UE traffic measurement period. The traffic volume of
timer
Table 2 Related parameters

Parameter Description

a UE during this period is measured. Based on the measurement result, the DRX
algorithm decides whether the UE should enter or exit DRX.

DRX Power Saving Indicates whether DRX active-time measurement is supported in the cell that
Measurement Switch
operates in TDD mode. If this parameter is set to ON, DRX active-time
measurement is supported in the cell that operates in TDD mode. If this
parameter is set to OFF, DRX active-time measurement is not supported in the
cell that operates in TDD mode.

DRX Power Saving Indicates the length of the UE DRX power saving measurement period for cells
Measurement Period
that operate in TDD mode. The power saving volume of a UE during this period
is measured. Based on the measurement result, the DRX algorithm decides
whether the UE should enter or exit DRX.

DRX Power Saving Indicates the active-time measurement threshold for UEs to enter DRX in the
Measurement Enter
DRX Threshold cell that operates in TDD mode. This threshold is used in the DRX algorithm. If
the measurement result of a UE is lower than this threshold, the eNodeB decides
that the UE should retain its DRX state or enter DRX.

DRX Power Saving Indicates the active-time measurement threshold for UEs to exit DRX in the cell
Measurement Exit DRX
Threshold that operates in TDD mode. This threshold is used in the DRX algorithm. If the
measurement result of a UE is higher than this threshold, the eNodeB decides
that the UE should retain its non-DRX state or exit DRX.

UnSync Long DRX Indicates the length of the long DRX cycle for a UE in the unsynchronized state.
Cycle
Set this parameter to a value greater than the value of LongDrxCycle; otherwise,
the power saving gain of the DRX for unsynchronized UEs decreases.

Cqi-Mask Config Switch Indicates whether the cqi-Mask IE can be set. The cqi-Mask IE is an optional IE
introduced in 3GPP Release 9. If the cqi-Mask IE is set to Setup, the UE can
send CQI/PMI/RI/PTI reports on PUCCH only in the onDuration period of
discontinuous reception (DRX). If the cqi-Mask IE is not set, the UE can send
CQI/PMI/RI/PTI reports on PUCCH in the active period of DRX.

Onduration Timer Indicates the DRX onduration timer for UEs when the eNodeB does not
Unsync
maintain synchronization for UEs.

DRX Inactivity Timer Indicates the DRX inactivity timer for UEs when the eNodeB does not maintain
Unsync
synchronization for UEs.

5.7.1.6.3.34 CellEicic
+-NE
+-eNodeBFunction
+-Cell
+-CellEicic

Description

The CELLEICIC MO Consists of parameters related to the switch of TDM eICIC function.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST CELLEICIC Use this command to list the configuration of an ABS pattern.

MOD CELLEICIC Use this command to modify the configuration of an ABS pattern.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local cell identity. It uniquely identifies a cell within an eNodeB.

Abs pattern Indicates the ABS pattern after the TDM eICIC is enabled. This parameter is
valid only when the eICIC is enabled. Different ABS pattern settings indicate
Table 2 Related parameters

Parameter Description

configurations with different ABS numbers in the same period. For example, the
value SUBFRAME_ONE_PER_FIVE indicates that One ABS per 5 ms. The
ABS pattern is a bitmap with a bit string of 40 bits. For details, see the definition
of ABS Pattern Info in 3GPP TS 36.423. This parameter is valid only when all
the ABS patterns for all cells are the same.

5.7.1.6.3.35 CellExtendedQci
+-NE
+-eNodeBFunction
+-Cell
+-CellExtendedQci

Description

A CellExtendedQci MO consists of the settings of an extended QoS Class Identifier (QCI) for a
cell. This MO associates a cell-specific extended QCI with DRX and handover parameters.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the InterFreqHoGroup MO:


- InterFreqHoGroupId in a CellExtendedQci MO must have been set in the associated
InterFreqHoGroup MO.
Relation with the InterRatHoCdma1xRttGroup MO:
- InterRatHoCdma1xRttGroupId in a CellExtendedQci MO must have been set in the
associated InterRatHoCdma1xRttGroup MO.
Relation with the InterRatHoCdmaHrpdGroup MO:
- InterRatHoCdmaHrpdGroupId in a CellExtendedQci MO must have been set in the
associated InterRatHoCdmaHrpdGroup MO.
Relation with the InterRatHoCommGroup MO:
- InterRatHoCommGroupId in a CellExtendedQci MO must have been set in the
associated InterRatHoCommGroup MO.
Relation with the InterRatHoGeranGroup MO:
- InterRatHoGeranGroupId in a CellExtendedQci MO must have been set in the associated
InterRatHoGeranGroup MO.
Relation with the InterRatHoUtranGroup MO:
- InterRatHoUtranGroupId in a CellExtendedQci MO must have been set in the associated
InterRatHoUtranGroup MO.
Relation with the IntraFreqHoGroup MO:
- IntraFreqHoGroupId in a CellExtendedQci MO must have been set in the associated
IntraFreqHoGroup MO.
Relation with the DrxParaGroup MO:
- DrxParaGroupId in a CellExtendedQci MO must have been set in the associated
DrxParaGroup MO.
Relation with the Cell MO:
- A maximum of 60 CellExtendedQci MOs can be configured for each Cell MO.
Relation with the RlfTimerConstGroup MO:
- When RlfTimerConstCfgInd is set to CFG, RlfTimerConstGroupId in a
CellExtendedQci MO must have been set in the associated RlfTimerConstGroup MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add a cell-level extended QCI.


CELLEXTENDEDQCI

LST Use this command to list cell-level extended QCI settings.


CELLEXTENDEDQCI

MOD Use this command to modify a cell-level extended QCI.


CELLEXTENDEDQCI

RMV Use this command to remove a cell-level extended QCI.


CELLEXTENDEDQCI

Related Parameters
Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Extended QCI Indicates the extended QoS Class Identifier (QCI), which is required by the
operator for service differentiation.

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Interfreq handover Indicates the ID of a parameter group related to inter-frequency handover.


group ID

InterRAT handover to Indicates the ID of a parameter group related to inter-RAT handover to


CDMA20001xRTT
group ID CDMA2000 1xRTT.

InterRAT handover to Indicates the ID of a parameter group related to inter-RAT handover to


CDMA2000HRPD
group ID CDMA2000 HRPD.

InterRAT handover Indicates the ID of a group of common parameters related to inter-RAT


common group ID
handover.

InterRAT handover to Indicates the ID of a parameter group related to inter-RAT handover to GERAN.
GERAN group ID

InterRAT handover to Indicates the ID of a parameter group related to inter-RAT handover to UTRAN.
UTRAN Group ID

Intrafreq handover Indicates the ID of a parameter group related to intra-frequency handover.


group ID

DRX parameter group Indicates the ID of a DRX parameter group.


ID

RLF timer and Indicates the RLF timer and constants indication.
constants indication

RLF timer and Indicates the RLF timer and constants group ID.
constants group ID

Traffic Release Delay Indicates the waiting duration for the eNodeB to release services with a specific
QCI after the eNodeB detects that the radio link is abnormal. When the eNodeB
detects that the radio link is abnormal, the eNodeB waits for the UE to initiate an
RRC connection reestablishment procedure to restore services. If the waiting
duration times out, the eNodeB releases the services.

5.7.1.6.3.36 CellHoParaCfg
+-NE
+-eNodeBFunction
+-Cell
+-CellHoParaCfg

Description

The CellHoParaCfg MO consists of cell-specific handover parameters.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the Cell MO:


- LocalCellId in an CellHoParaCfg MO must have been set in the associated Cell MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list cell-specific handover configurations.


CELLHOPARACFG

MOD Use this command to modify cell-specific handover configurations.


CELLHOPARACFG

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local identity of the cell. It uniquely identifies a cell within an
Table 2 Related parameters

Parameter Description

eNodeB.

BlindHO A1A2 RSRP Indicates the RSRP threshold for events A1 and A2 that are used for inter-
trigger threshold
frequency and inter-RAT blind handovers based on coverage. If the RSRP
measurement result of the serving cell is higher than the threshold, an event A1
is reported. If the RSRP measurement result of the serving cell is lower than the
threshold, an event A2 is reported.

BlindHO A1A2 RSRQ Indicates the RSRQ threshold for events A1 and A2 that are used for inter-
trigger threshold
frequency and inter-RAT blind handovers based on coverage. If the RSRQ
measurement result of the serving cell is higher than the threshold, an event A1
is reported. If the RSRQ measurement result of the serving cell is lower than the
threshold, an event A2 is reported.

5.7.1.6.3.37 CellIdPrdUpt
+-NE
+-eNodeBFunction
+-CellIdPrdUpt

Description

The CellIdPrdUpt MO consists of the parameters related to the algorithm for periodically
updating cell IDs. If the switch for the algorithm is turned on, cell IDs are periodically updated,
inserted into system information, and broadcast to the associated UEs once the time at which the
algorithm begins to take effect is reached. The time that the algorithm begins to take effect must
be specified according to the Greenwich Mean Time (GMT).

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands


Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST CELLIDPRDUPT Use this command to list the configuration of the cell ID periodic updating
algorithm.

MOD CELLIDPRDUPT Use this command to modify the configuration of the cell ID periodic updating
algorithm.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Period update switch Indicates the switch for the algorithm for periodically updating cell IDs. If this
parameter is set to BOOLEAN_TRUE, cell IDs are periodically updated,
inserted into the system information, and broadcast to the associated UEs once
the time at which the algorithm begins to take effect is reached.

Action time Indicates the time at which the algorithm for periodically updating cell IDs
begins to take effect. If the switch for the algorithm is turned on, cell IDs are
periodically updated, inserted into the system information, and broadcast to the
associated UEs once the time specified by this parameter is reached.

Period Indicates the period of updating cell IDs.

5.7.1.6.3.38 CellLowPower
+-NE
+-eNodeBFunction
+-Cell
+-CellLowPower

Description
The CellLowPower MO consists of the parameters related to the low power consumption mode
of a cell. The eNodeB enters the low power consumption mode after it receives a command from
a user or after a mains input out of range(Specific Problem: AC Failure) alarm is reported. The
service time of an eNodeB can be prolonged by taking the following measures in low power
consumption mode: (1) reducing the transmit power for services in a cell; (2) reducing the
transmit power for reference signals in a cell; (3) shutting down half of the transmit diversity
channels in a cell; (4) shutting down all transmit diversity channels in a cell. A cell enters the low
power consumption mode when both of the following conditions are met: (1) the switch for the
low power consumption mode is turned on; (2) the switch for forcibly entering the low power
consumption mode is turned on; alternatively, it is within the duration when the low power
consumption mode is active, and a mains input out of range(Specific Problem: AC Failure) alarm
is reported.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST CELLLOWPOWER Use this command to list the configuration of the low power consumption mode
in a cell.

MOD Use this command to modify the configuration of the low power consumption
CELLLOWPOWER
mode in a cell. The eNodeB enters the low power consumption mode after it
receives a command from a user or after a mains input out of range(Specific
Problem: AC Failure) alarm is reported.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Low power Indicates the switch for the functionality of the low power consumption mode.
consumption mode
switch The cell can enter the low power consumption mode only when this parameter is
set to ON and specific conditions are met.

Low power Indicates the switch for forcibly entering the low power consumption mode.
consumption mode
order When both this switch and the functionality switch are set to ON, the cell enters
the low power consumption mode as soon as the wait time for entering the mode
elapses, regardless of whether it is within the low power consumption period.
When the functionality switch is set to ON but this switch is set to OFF, the cell
enters the low power consumption mode as soon as the wait time for entering
the mode elapses, if a mains input out of range(Specific Problem: AC Failure)
alarm is reported within the low power consumption period.

Start time Indicates the start time of the low power consumption mode.

Stop time Indicates the stop time of the low power consumption mode. If the stop time is
earlier than or the same as the start time, the stop time is assumed to be a time of
the next day.

Cell used power reduce Indicates the duration in which the transmit power for services is reduced in the
time length
cell in low power consumption mode.

Reference signal power Indicates the duration in which the reference signal transmit power is reduced in
reduce time length
the cell in low power consumption mode.

RF shutdown time Indicates the duration in which RF channels are shut down in the cell in low
length
power consumption mode.

Cell used power ratio Indicates the percentage of the transmit power for services to the total transmit
power for services when the low power consumption mode is implemented by
means of reducing the transmit power for services.

Reference signal power Indicates the amount by which the reference signal transmit power is reduced in
adjust offset
the cell in low power consumption mode.

Time length for entering Indicates the duration when the cell stays in normal mode before entering the
the low power
consumption mode low power consumption mode. In low power consumption mode, a cell
automatically takes the following actions in sequence: 1. lowers the transmit
power for services; 2. lowers the transmit power for reference signals; 3. shuts
down some RF channels in the cell; 4. shuts down the cell. This duration
smooths the transition from the normal mode to the low power consumption
mode for the cell. If the conditions for the cell to enter the low power
Table 2 Related parameters

Parameter Description

consumption mode are no longer met during this period of time, the cell will not
enter the low power consumption mode; otherwise, it enters the low power
consumption mode and takes the preceding actions in sequence.

Back power save policy Indicates the backup power saving policy of the eNodeB when the mains supply
is cut off and the eNodeB is powered by storage batteries. The degradation
duration in each policy is automatically configured as follows: If this parameter
is set to POLICY3, the duration of service power degradation and that of
reference signal power degradation are both 120 minutes, and the maximum
duration of RF channel intelligent shutdown is 1440 minutes. If this parameter is
set to POLICY2, the duration of service power degradation, reference signal
power degradation, and RF channel intelligent shutdown is all 120 minutes. If
this parameter is set to POLICY1, the duration of service power degradation,
that of reference signal power degradation, and that of RF channel intelligent
shutdown are all 0 minutes. If this parameter is set to POLICY1, POLICY2 or
POLICY3, the ratio of available service power to total service power is 50%, the
adjustment offset for reference signal power is -1 dB, and the wait time for
entering the low power consumption mode is 5 minutes. If this parameter is set
to CUSTOMIZED, you can customize the duration of power degradation, the
ratio of available service power to total service power, the adjustment offset for
reference signal power, and the wait time for entering the low power
consumption mode.

5.7.1.6.3.39 CellMLB
+-NE
+-eNodeBFunction
+-Cell
+-CellMLB

Description

The CellMLB MO consists of the parameters related to Mobility Load Balancing (MLB) in a
cell. When a UE is moving, because of the randomness of the UE location and the diversity of
UE services, a cell may be heavily loaded, whereas its neighboring cells may carry relatively low
loads. MLB can be used to mitigate the imbalance. Through negotiation with its neighboring
cells, the cell with a heavy load transfers a proportion of its UEs to a neighboring cell to balance
the cell loads and maximize the utilization of network resources. By means of MLB, both the
throughput and performance of the network are improved.
Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the Cell MO:


- If FddTddInd is CELL_FDD Model, HotSpotUeMode in the CellMLB must be set OFF.
Relation with the CellShutdown MO:
- The sum of InterFreqMlbThd and LoadOffset in the CellMLB MO must be greater than
that of DlPrbThd and DlPrbOffset in the CellShutdown MO. In addition, the sum of
InterFreqMlbThd and LoadOffset in the CellMLB MO must be greater than that of
UlPrbThd and UlPrbOffset in the CellShutdown MO.
- InterFreqMlbThd in the CellMLB MO must be greater than DlPrbThd in the
CellShutdown MO. In addition, InterFreqMlbThd in the CellMLB MO must be greater than
UlPrbThd in the CellShutdown MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST CELLMLB Use this command to list the configuration of the cell MLB algorithm.

MOD CELLMLB Use this command to modify the configuration of the cell MLB algorithm.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.
Table 2 Related parameters

Parameter Description

Intra-Frequency Indicates the threshold for triggering intra-frequency load balancing. Intra-
Mobility Load Balancing
Threshold frequency load balancing is started if the cell load exceeds the sum of the
threshold and the offset, and is stopped if the cell load falls below the threshold.
This parameter will be removed in later versions. In this version, the setting of
this parameter is still synchronized between the M2000 and the eNodeB, but it is
no longer used internally. Therefore, avoid using this parameter.

Inter-Frequency Indicates the threshold for triggering inter-frequency load balancing. Load
Mobility Load Balancing
Threshold balancing between the cell and its inter-frequency neighboring cell is triggered if
the cell load exceeds the sum of this threshold and the offset, and is stopped if
the cell load falls below this threshold.

Inter-RAT Mobility Load Indicates the threshold for triggering inter-RAT load balancing. Load balancing
Balancing Threshold
between the cell and its inter-RAT neighboring cell is triggered if the cell load
exceeds the sum of this threshold and the offset, and is stopped if the cell load
falls below this threshold.

Load Information Indicates the period of the inter-cell load exchange. This parameter is contained
Exchange Period
in the load exchange request message. If the source cell sends a load exchange
request message containing a period, the target cell reports its load to the source
cell at intervals based on the period. If the source cell sends such a message
without a period, the target cell reports its load to the source cell at a default
interval of 5s. In this version, the parameter still supports setting
synchronization between the M2000 and the eNodeB, but is no longer used
internally. Avoid using this parameter as it will be removed from later versions.

Load Offset Indicates the offset used in the evaluation of whether to trigger load balancing.
To prevent load fluctuations from frequently triggering or stopping load
balancing, an offset needs to be set. That is, a specific load balancing action is
taken only if the cell load exceeds the sum of the corresponding load balancing
threshold and this offset.

Load Difference Indicates the threshold of load difference between two cells for load balancing.
Threshold
If the load difference between two cells exceeds this threshold, the eNodeB
determines that load imbalance occurs and therefore initiates load balancing
between the cells. If the load difference between cells falls below this threshold,
the eNodeB determines that load imbalance is resolved and therefore stops load
balancing between the cells.

Inter-RAT Mobility Load Indicates the threshold of the number of uplink-synchronized UEs for triggering
Balancing UE Number
Threshold inter-RAT load sharing. Load balancing between the cell and its neighboring
inter-RAT cell is triggered if the number of uplink-synchronized UEs in the cell
exceeds this threshold, and is stopped if the number of uplink synchronized UEs
falls below this threshold. The threshold for the number of uplink-synchronized
Table 2 Related parameters

Parameter Description

UEs equals the GUI value multiplied by 1000 and 1%. For example, a GUI
value of 1 means that the threshold for the number of uplink-synchronized UEs
is 10 (that is, 1000 x 1%), a GUI value of 2 means that the threshold for the
number of uplink-synchronized UEs is 20, and a GUI value of 10 means that the
number of uplink-synchronized UEs is 100. However, if the GUI values are 100
and 99, the thresholds for the numbers of uplink-synchronized UEs are 1 and 2,
respectively.

UTRAN Idle Mode Indicates the standard valid duration for load sharing with universal terrestrial
Mobility Load Balancing
Initial Valid Period radio access network (UTRAN) for UEs in idle mode. The actual duration
increases on the basis of a standard valid duration with the increase of the
number of uplink-synchronized UEs.

Load Transfer Factor Indicates the control factor for the amount of a single load transfer. The value of
this parameter has an impact on the efficiency of MLB algorithm and the
algorithm to prevent ping-pong load transfer.

Mobility Load Balancing Indicates the mode to trigger MLB. PRB_ONLY: Indicates that the inter-
Trigger Mode
frequency MLB is triggered by PRB usage. UE_NUMBER_ONLY: Indicates
that the inter-frequency MLB is triggered by the number of UEs in the serving
cell. PRB_OR_UE_NUMBER: Indicates that blind inter-frequency MLB is
triggered by either the PRB usage or the number of UEs in the serving cell. The
MlbTriggerMode parameter only applies to blind inter-frequency MLB in this
version.

Inter-frequency Mobility Indicates the threshold of maximum number of UL-synchronized users when the
Load Balancing UE
Number Threshold MLB is triggered by the number of UEs in the serving cell. When the number of
UL-synchronized users in the serving cell exceeds the sum of the
InterFreqMlbUeNumThd parameter value and the MlbUeNumOffset parameter
value, inter-frequency MLB is triggered.When the number of UL-synchronized
users in the serving cell is less than the InterFreqMlbUeNumThd parameter
value, the inter-frequency MLB stops. The InterFreqMlbUeNumThd parameter
only applies to blind inter-frequency MLB in this version.

Mobility Load Balancing Indicates the offset of the number of UL-synchronized users for triggering the
UE Number Offset
inter-frequency MLB. The inter-frequency MLB is triggered when the number
of UL-synchronized users exceeds the sum of the InterFreqMlbUeNumThd
parameter value and the MlbUeNumOffset parameter value. The
MlbUeNumOffset parameter only applies to blind inter-frequency MLB in this
version.

Mobility Load Balancing Indicates the maximum number of UEs that can be handed over to the inter-
Max UE Number
frequency cell in the inter-frequency MLB. This parameter aims to avoid too
many UEs being handed over to the inter-frequency cell at a time, and therefore
Table 2 Related parameters

Parameter Description

the impact on the inter-frequency cell is reduced. The MlbMaxUeNum


parameter only applies to blind inter-frequency MLB in this version.

Mobility Load Balancing Indicates the PRB usage threshold of a UE in the inter-frequency MLB. When
UE Selection PRB
Usage Threshold the MlbTriggerMode parameter is set to PRB_ONLY, the UE whose the PRB
usage with the load balancing in downlink or uplink is larger than the
MlbUeSelectPrbThd parameter value and the PRB usage with the load balancing
in the reserve direction (uplink or downlink) is less than the
MlbUeSelectPrbThd parameter value is selected. When the MlbTriggerMode
parameter is set to UE_NUMBER_ONLY, the UE whose PRB usage is less than
the MlbUeSelectPrbThd parameter value is selected. When MlbTriggerMode
parameter is set to PRB_OR_UE_NUMBER, a related UE is selected based on
the scenario where the inter-frequency MLB is triggered the number of UEs in
the serving cell. The parameter only applies to blind inter-frequency MLB in this
version.

Hot Spot UE Mode Indicates the switch used to control whether inter-RAT load balancing can be
performed only on UEs in hotspots. This parameter is dedicated to LTE TDD
cells.

5.7.1.6.3.40 CellMro
+-NE
+-eNodeBFunction
+-Cell
+-CellMro

Description

The CellMro MO consists of the parameters related to inter-cell Mobility Robustness


Optimization (MRO), such as the upper and lower limits of the cell individual offset (CIO)
adjustment range for a cell.

Effective Scenario

Immediately

Relations Between MOs


Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST CELLMRO Use this command to list the configuration of inter-cell Mobility Robustness
Optimization (MRO).

MOD CELLMRO Use this command to modify the configuration of inter-cell Mobility Robustness
Optimization (MRO).

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within an eNodeB.

CIO adjustment range Indicates whether to set the upper and lower limits of the CIO adjustment range
configuration indicator
for the cell. If this parameter is set to CFG(Configure), the CIO for the cell can
be changed by an amount within the range specified by the upper and lower
limits. If this parameter is set to NOT_CFG(Not configure), the upper and lower
limits of the CIO adjustment range for the cell in intra-frequency MRO are
calculated by using the following formulas: Lower limit = Off + Ofs + Ocs - Ofn
+ Hys - 5, Upper limit = Off + Ofs + Ocs - Ofn + Hys - 2, where Off is the offset
for intra-frequency handover, Ofs and Ofn are the frequency-specific offsets for
the serving frequency and neighboring frequency respectively, Ocs is the cell-
specific offset for the serving cell, and Hys is the hysteresis for intra-frequency
handover. If this parameter is set to NOT_CFG(Not configure), the upper and
lower limits of the CIO adjustment range for the cell in inter-frequency MRO
are calculated by using the following formulas: Lower limit = -24, Upper limit =
thresh + 110 - Ofn + Hys, where thresh is the RSRP threshold for triggering a
coverage-based inter-frequency handover and Hys is the hysteresis for inter-
frequency handover.

CIO adjustment upper Indicates the upper limit of cell individual offset (CIO) adjustment range for the
Table 2 Related parameters

Parameter Description

limit cell in mobility robustness optimization (MRO). This parameter needs to be set
only when the CioAdjLimitCfgInd parameter is set to CFG.

CIO adjustment lower Indicates the lower limit of cell individual offset (CIO) adjustment range for the
limit
cell in mobility robustness optimization (MRO). This parameter needs to be set
only when the CioAdjLimitCfgInd parameter is set to CFG.

5.7.1.6.3.41 CellNoAccessAlmPara
+-NE
+-eNodeBFunction
+-Cell
+-CellNoAccessAlmPara

Description

The CellNoAccessAlmPara MO consists of the parameters related to cell no-traffic detection in a


cell. The parameters specify the detection period and the duration threshold for alarm reporting.
After a cell is set up, the eNodeB automatically resets the cell and reports the cell no-traffic
alarm if there is no traffic in the cell within a duration in a period.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

LST Use this command to list the parameters related to no-traffic detection in a cell.
CELLNOACCESSALM
PARA

MOD Use this command to modify the parameters related to no-traffic detection in a
CELLNOACCESSALM
PARA cell.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

No access detect start Indicates the time when the cell no-traffic detection starts. If the stop time is
time
earlier than or the same as the start time, the end time is assumed to be a time of
the next day. If the timer for reporting the no-traffic alarm is not set to 0, the
eNodeB performs the cell no-traffic detection from the start time to the stop
time.

No access detect stop Indicates the time when the cell no-traffic detection stops. If the stop time is
time
earlier than or the same as the start time, the stop time is assumed to be a time of
the next day. If the timer for reporting the no-traffic alarm is not set to 0, the
eNodeB performs the cell no-traffic detection from the start time to the stop
time.

No access detect timer Indicates the length of the timer for the cell no-traffic detection. If there is no
traffic in the cell within the duration specified by this parameter, the eNodeB
reports the no-access alarm and resets the cell. If this parameter is set to 0, the
cell no-traffic detection is not performed. If the timer for reporting the no-traffic
alarm is set to a non-zero value, the eNodeB performs the cell no-traffic
detection from the start time to the stop time.

5.7.1.6.3.42 CellOp
+-NE
+-eNodeBFunction
+-Cell
+-CellOp
+-eNBCellOpRsvdPara[1~1]

Description

A CellOp MO consists of the parameters used to identify an operator of a cell. The maximum
number of CellOp MOs that can be configured varies with the specific RAN sharing mode. In
independent mode, one and only one CellOp MO can be configured for each cell and this MO
must correspond to the primary operator. In RAN sharing with dedicated carrier mode, one and
only one CellOp MO can be configured for each cell. In RAN sharing with common carrier
mode, a maximum of six CellOp MOs can be configured for each cell.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Possible children:
eNBCellOpRsvdPara[1~1]

Relation with the CnOperatorTa MO:


- TrackingAreaId in a CellOp MO must have been set in the associated CnOperatorTa MO.
Relation with the ENodeBSharingMode,CnOperatorTa MOs:
- If ENodeBSharingMode in the ENodeBSharingMode MO is set to SHARED_FREQ,
CnOperator MOs configured with Cell MO must have one CnOperator MO which is primary
operator.
Relation with the CaGroupCell MO:
- Assume that set A consists of all TrackingAreaId values under one Cell MO associated with
a CaGroupCell MO, and set B consists of all TrackingAreaId values under the other Cell MO
associated with a CaGroupCell MO under the same CaGroup MO with A. Then, sets A and B
must have at least one overlapping TrackingAreaId value.
Relation with the EutranIntraFreqNCell,CnOperator,CnOperatorTa MOs:
- A CellOp MO must be configured for each EutranIntraFreqNCell MO that corresponds to
an intra-eNodeB intra-frequency neighboring cell. If the ENodeBSharingMode parameter in the
ENodeBSharingMode MO is set to SHARED_FREQ, Mcc and Mnc in such an
EutranIntraFreqNCell MO must be the same as the Mcc and Mnc specified in the
CnOperator MO representing the primary operator. If ENodeBSharingMode is set to
INDEPENDENT or SEPARATED_FREQ, Mcc and Mnc in such an EutranIntraFreqNCell
MO must be set to the same values as Mcc and Mnc specified in the CnOperator MO
corresponding to the CellOp MO associated with this EutranIntraFreqNCell MO.
Relation with the EutranInterFreqNCell,CnOperator,CnOperatorTa MOs:
- A CellOp MO must be configured for each EutranInterFreqNCell MO that corresponds to
an intra-eNodeB inter-frequency neighboring cell. If the ENodeBSharingMode parameter in the
ENodeBSharingMode MO is set to SHARED_FREQ, Mcc and Mnc in such an
EutranInterFreqNCell MO must be the same as the Mcc and Mnc specified in the
CnOperator MO representing the primary operator. If ENodeBSharingMode is set to
INDEPENDENT or SEPARATED_FREQ, Mcc and Mnc in such an EutranInterFreqNCell
MO must be set to the same values as Mcc and Mnc specified in the CnOperator MO
corresponding to the CellOp MO associated with this EutranInterFreqNCell MO.
Relation with the Cell,ENodeBSharingMode MOs:
- If the ENodeBSharingMode parameter in the ENodeBSharingMode MO is set to
INDEPENDENT, a maximum of one CellOp MO with the same LocalCellId as that in a Cell
MO can be configured.
- If the ENodeBSharingMode parameter in the ENodeBSharingMode MO is set to
SEPARATED_FREQ, a maximum of one CellOp MO with the same LocalCellId as that in a
Cell MO can be configured.
Relation with the Cell MO:
- If CellActiveState in a Cell MO is set to CELL_ACTIVE, one or more CellOp MOs must
have been configured for the Cell MO.
- If ENodeBSharingMode in ENodeBSharingMode is set to SHARED_FREQ, a maximum
of six CellOp MO with the same LocalCellId as that in a Cell MO can be configured.
- If ENodeBSharingMode in the ENodeBSharingMode MO is set to SHARED_FREQ and
CellActiveState in a Cell MO is set to CELL_ACTIVE, one of the CellOp MOs which have the
same LocalCellId as that in a Cell MO must represent the primary operator.
Relation with the Cell,CnOperatorTa MOs:
- If ENodeBSharingMode in the ENodeBSharingMode MO is set to SHARED_FREQ and
CellActiveState in a Cell MO is set to CELL_ACTIVE, CnOperatorId in the CnOperatorTa
MO corresponding to TrackingAreaId in each CellOp MO must be unique.
- If ENodeBSharingMode in the ENodeBSharingMode MO is set to SHARED_FREQ and
CellActiveState in a Cell MO is set to CELL_ACTIVE, Tac in the CnOperatorTa MO
corresponding to TrackingAreaId in each CellOp MO must have the same value.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD CELLOP Use this command to add a cell operator.

DSP Use this command to query the broadcasting sequence of operators in the cell
CELLBROADCASTCN
OPERATOR system information.

LST CELLOP Use this command to list the parameters about a cell operator.

MOD CELLOP Use this command to modify the parameters about a cell operator.

RMV CELLOP Use this command to remove a cell operator.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a base
station.

Local tracking area ID Indicates the local tracking area identity of the cell, which uniquely identifies an
operator's record of tracking area information within a cell. This parameter is
used only in the eNodeB and is different from the tracking area identity
configured in the tracking area list on the MME.

Cell reserved for Indicates whether the cell is reserved for operator use.
operator
If this parameter is set to CELL_RESERVED_FOR_OP, the cell is reserved for
operator use. UEs of AC11 or AC15 in their HPLMN or EHPLMN can consider
this cell as a candidate cell for cell selection or reselection. UEs of AC11 or
AC15 outside their HPLMN/EHPLMN and UEs of AC0-9/AC12-14 consider
this cell as a barred cell during cell selection or reselection.
If this parameter is set to CELL_NOT_RESERVED_FOR_OP, the cell is not
reserved for operator use. All UEs can consider this cell as a candidate cell for
cell selection or reselection.

Operator uplink RB Indicates the percentage of RBs occupied by the operator on the physical uplink
used ratio
shared channel (PUSCH) when RAN sharing is enabled at the eNodeB and the
RAN sharing mode switch of the cell-level switch is turned on. When the data
volume is sufficiently large, the percentage of RBs actually occupied by each
Table 2 Related parameters

Parameter Description

operator will reach the preset value. Modifications on this parameter affect
operators' percentages of RBs.This parameter takes effect only in RAN sharing
with common carriers mode.

Operator downlink RB Indicates the percentage of RBs occupied by the operator on the physical
used ratio
downlink shared channel (PDSCH) when RAN sharing is enabled at the eNodeB
and the RAN sharing mode switch of the cell-level switch is turned on. When
the data volume is sufficiently large, the percentage of RBs actually occupied by
each operator will reach the preset value. Modifications on this parameter affect
operators' percentages of RBs.This parameter takes effect only in RAN sharing
with common carriers mode.

MME configure number Indicates the number of MMEs configured for a cell. This parameter specifies
whether to support the TDD/FDD cell configured with dedicated MME scenario.
When this parameter is set to 0, the TDD/FDD cell configured with dedicated
MME scenario is not supported, and no MME can be configured for a cell.
When this parameter is set to a value between 1 and 4, the TDD/FDD cell
configured with dedicated MME scenario is supported, and the number of
MMEs for a cell can be configured according to the parameter value. An MME
is uniquely specified by the MME group identifier (MMEGI) and MME code
(MMEC).

First MME group Indicates the MMEGI of the first MME configured for a cell. This parameter can
identity
be configured only when the MMECfgNum parameter is greater than or equal to
1.
When setting this parameter, ensure that the globally unique MME identifier
(GUMMEI), consisting of the PLMN, MMEGI, and MMEC, must be unique.
The S1 link between an MME configured for a cell and the eNodeB supporting
the cell must be available, and the GUMMEI of the MME must be specified in
the ServedGummeis parameter of the S1Interface MO. Otherwise, the cell
cannot broadcast the PLMN in system information.
If all MMEs configured for a cell cannot establish S1 links to the eNodeB
supporting the cell, the cell cannot be established.

First MME code Indicates the MMEC of the first MME configured for a cell. This parameter can
be configured only when the MMECfgNum parameter is greater than or equal to
1.
When setting this parameter, ensure that the globally unique MME identifier
(GUMMEI), consisting of the PLMN, MMEGI, and MMEC, must be unique.
The S1 link between an MME configured for a cell and the eNodeB supporting
the cell must be available, and the GUMMEI of the MME must be specified in
the ServedGummeis parameter of the S1Interface MO. Otherwise, the cell
cannot broadcast the PLMN in system information.
Table 2 Related parameters

Parameter Description

If all MMEs configured for a cell cannot establish S1 links to the eNodeB
supporting the cell, the cell cannot be established.

Second MME group Indicates the MMEGI of the second MME configured for a cell. This parameter
identity
can be configured only when the MMECfgNum parameter is greater than or
equal to 2.
When setting this parameter, ensure that the globally unique MME identifier
(GUMMEI), consisting of the PLMN, MMEGI, and MMEC, must be unique.
The S1 link between an MME configured for a cell and the eNodeB supporting
the cell must be available, and the GUMMEI of the MME must be specified in
the ServedGummeis parameter of the S1Interface MO. Otherwise, the cell
cannot broadcast the PLMN in system information.
If all MMEs configured for a cell cannot establish S1 links to the eNodeB
supporting the cell, the cell cannot be established.

Second MME code Indicates the MMEC of the second MME configured for a cell. This parameter
can be configured only when the MMECfgNum parameter is greater than or
equal to 2.
When setting this parameter, ensure that the globally unique MME identifier
(GUMMEI), consisting of the PLMN, MMEGI, and MMEC, must be unique.
The S1 link between an MME configured for a cell and the eNodeB supporting
the cell must be available, and the GUMMEI of the MME must be specified in
the ServedGummeis parameter of the S1Interface MO. Otherwise, the cell
cannot broadcast the PLMN in system information.
If all MMEs configured for a cell cannot establish S1 links to the eNodeB
supporting the cell, the cell cannot be established.

Third MME group Indicates the MMEGI of the third MME configured for a cell. This parameter
identity
can be configured only when the MMECfgNum parameter is greater than or
equal to 3.
When setting this parameter, ensure that the globally unique MME identifier
(GUMMEI), consisting of the PLMN, MMEGI, and MMEC, must be unique.
The S1 link between an MME configured for a cell and the eNodeB supporting
the cell must be available, and the GUMMEI of the MME must be specified in
the ServedGummeis parameter of the S1Interface MO. Otherwise, the cell
cannot broadcast the PLMN in system information.
If all MMEs configured for a cell cannot establish S1 links to the eNodeB
supporting the cell, the cell cannot be established.

Third MME code Indicates the MMEC of the third MME configured for a cell. This parameter can
be configured only when the MMECfgNum parameter is greater than or equal to
3.
Table 2 Related parameters

Parameter Description

When setting this parameter, ensure that the globally unique MME identifier
(GUMMEI), consisting of the PLMN, MMEGI, and MMEC, must be unique.
The S1 link between an MME configured for a cell and the eNodeB supporting
the cell must be available, and the GUMMEI of the MME must be specified in
the ServedGummeis parameter of the S1Interface MO. Otherwise, the cell
cannot broadcast the PLMN in system information.
If all MMEs configured for a cell cannot establish S1 links to the eNodeB
supporting the cell, the cell cannot be established.

Fourth MME group Indicates the MMEGI of the fourth MME configured for a cell. This parameter
identity
can be configured only when the MMECfgNum parameter is equal to 4.
When setting this parameter, ensure that the globally unique MME identifier
(GUMMEI), consisting of the PLMN, MMEGI, and MMEC, must be unique.
The S1 link between an MME configured for a cell and the eNodeB supporting
the cell must be available, and the GUMMEI of the MME must be specified in
the ServedGummeis parameter of the S1Interface MO. Otherwise, the cell
cannot broadcast the PLMN in system information.
If all MMEs configured for a cell cannot establish S1 links to the eNodeB
supporting the cell, the cell cannot be established.

Fourth MME code Indicates the MMEC of the fourth MME configured for a cell. This parameter
can be configured only when the MMECfgNum parameter is equal to 4.
When setting this parameter, ensure that the globally unique MME identifier
(GUMMEI), consisting of the PLMN, MMEGI, and MMEC, must be unique.
The S1 link between an MME configured for a cell and the eNodeB supporting
the cell must be available, and the GUMMEI of the MME must be specified in
the ServedGummeis parameter of the S1Interface MO. Otherwise, the cell
cannot broadcast the PLMN in system information.
If all MMEs configured for a cell cannot establish S1 links to the eNodeB
supporting the cell, the cell cannot be established.

Broadcast CN operator Indicates the operator index that is broadcast in the cell system information.
ID

5.7.1.6.3.43 CellPdcchAlgo
+-NE
+-eNodeBFunction
+-Cell
+-CellPdcchAlgo

Description

The CellPdcchAlgo MO consists of the parameters related to the PDCCH resource allocation
algorithm in a cell. These parameters are used to specify control signaling resource configuration
in DL and hence must be set properly to minimize the DL control overhead and guarantee the
user plane throughput.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the PHICHCfg,Cell MOs:


- If PhichDuration in the PHICHCfg MO is set to NORMAL, and PdcchSymNumSwitch in
the CellPdcchAlgo MO is set to OFF, InitPdcchSymNum in the CellPdcchAlgo MO cannot be
set to 1 if the cell bandwidth is 1.4 MHz.
- If PhichDuration in the PHICHCfg MO is set to NORMAL, InitPdcchSymNum in the
CellPdcchAlgo MO can not be set to 4 if the cell bandwidth is not 1.4 MHz.
- If PhichDuration in the PHICHCfg MO is set to EXTENDED, InitPdcchSymNum in the
CellPdcchAlgo MO can be set to 3 or 4 if the cell bandwidth is 1.4 MHz.
- If PhichDuration in the PHICHCfg MO is set to EXTENDED, InitPdcchSymNum in the
CellPdcchAlgo MO must be set to 3 when the cell bandwidth is not 1.4 MHz.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the configuration of the PDCCH resource allocation
CELLPDCCHALGO
algorithm.

MOD Use this command to modify the configuration of the PDCCH resource
CELLPDCCHALGO
allocation algorithm.
Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the Local ID of the cell. It uniquely identifies a cell within a BS.

SignalCongregateLevel Indicates the CCE aggregation level for common signaling.

Cce Ratio Adjust Switch Indicates the CCE ratio adjustment switch for the PDCCH. If this switch is
turned on, the resource allocation algorithm of the PDCCH dynamically adjusts
the UL and DL CCE ratios within each transmission time interval (TTI) based
on CCE usages in UL and DL. If this switch is turned off, the UL and DL CCE
ratios are not dynamically adjusted.

PDCCH Initial Symbol Indicates the number of OFDM symbols initially occupied by the PDCCH. If the
Number
switch for dynamic adjustment of the number of OFDM symbols occupied by
the PDCCH is turned off, this parameter indicates the number of OFDM
symbols that are always occupied by the PDCCH. If the switch is turned on and
the bandwidth is 1.4 MHz or 3 MHz, the PDCCH occupies 4 or 3 OFDM
symbols, in this scenario, this parameter cannot be manually set.. If the switch is
turned on and the bandwidth is 5 MHz, 10 MHz, 15 MHz, or 20 MHz, the
eNodeB adjusts the number of OFDM symbols in the range of 1, 2, and 3 when
this parameter is set to the default value 1, or in the range of 2 and 3 when this
parameter is set to 2 or 3.

PDCCH Virtual Loading Indicates the percentage of the number of virtually loaded PDCCH CCEs when
Proportion
the PDCCH power control switch is turned off, or indicates the percentage of the
power of virtually loaded PDCCH CCEs when the PDCCH power control
switch is turned on. This parameter is used to analyze the impact of the
parameter values on PDCCH demodulation performance and provide reference
to intra-frequency networking in LTE.

PDCCH Symbol Indicates whether to enable dynamic adjustment on the number of orthogonal
Number Adjust Switch
frequency division multiplexing (OFDM) symbols occupied by the physical
downlink control channel (PDCCH). If this parameter is set to OFF, the number
of OFDM symbols occupied by the PDCCH is fixed and cannot be dynamically
adjusted. If this parameter is set to ON, the number of OFDM symbols occupied
by the PDCCH is dynamically adjusted based on the required number of
PDCCH control channel elements (CCEs). If this parameter is set to
ECFIADAPTIONON, the number of OFDM symbols occupied by the PDCCH
is dynamically adjusted based on the cell downlink throughput, and the
adjustment performance is the best among the three methods.

CCE use ratio Indicates the upper limit for the CCE usage within each transmission time
Table 2 Related parameters

Parameter Description

interval (TTI). When the switch for dynamically adjusting the number of OFDM
symbols on the PDCCH is turned on, the parameter setting is invalid, that is, the
CCE usage within each TTI cannot be limited. This parameter is valid only in
TDD mode.

PDCCH Aggregation Indicates the switch used to enable or disable closed-loop adjustment to the
Level CL Switch
PDCCH aggregation level. If this switch is turned on, PDCCH aggregation level
is adjusted based on the block error rate (BLER) of the PDCCH. If this switch is
turned off, PDCCH aggregation level is not adjusted based on the BLER of the
PDCCH.

DPD Virtual Load Indicates whether to enable virtual loading for Digital PreDistortion (DPD). This
Switch
parameter is valid only for LTE TDD cells.

DPD Virtual Load Type Indicates the virtual load type for Digital PreDistortion (DPD). This parameter is
valid only for LTE TDD cells.

5.7.1.6.3.44 CellPucchAlgo
+-NE
+-eNodeBFunction
+-Cell
+-CellPucchAlgo

Description

The CellPucchAlgo MO consists of the parameters related to the PUCCH resource allocation
algorithm in a cell. This algorithm is used to configure all types of control signaling resources,
which minimizes the control overhead in UL and guarantees the user plane throughput.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell
Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the configuration related to the PUCCH resources
CELLPUCCHALGO
allocation algorithm.

MOD Use this command to modify the configuration related to the PUCCH resources
CELLPUCCHALGO
allocation algorithm.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

SRI Low Load Indicates the threshold for the low load state of the SRI resources. The SRI
Threshold
resources enter the low load state if the PUCCH resource allocation algorithm
detects that the number of admitted UEs is smaller than the value of this
parameter.

5.7.1.6.3.45 CellRacThd
+-NE
+-eNodeBFunction
+-Cell
+-CellRacThd

Description

The CellRacThd MO consists of the parameters related to admission and load control algorithms
for different types of services in a cell. Admission control algorithm is mainly used for the
eNodeB to determine whether to accept the radio bearer (RB) setup request initiated by a UE.
The load control algorithm is used for the eNodeB to determine whether a cell is congested,
based on which corresponding actions are performed.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST CELLRACTHD Use this command to list the configuration of the thresholds for admission and
load control.

MOD CELLRACTHD Use this command to modify the configuration of the thresholds for admission
and load control.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local cell ID. It uniquely identifies a cell within a BS.

Gold service arp Indicates the Allocation and Retention Priority (ARP) threshold for the Golden-
threshold
level services. A service is defined as a Golden-level service if its ARP value is
smaller than or equal to this threshold. The service priority has a negative
correlation with the ARP value.

Silver service arp Indicates the Allocation and Retention Priority (ARP) threshold for the Silver-
threshold
level services. A service is defined as a Silver-level service if its ARP value is
Table 2 Related parameters

Parameter Description

smaller than or equal to the value of this parameter and is larger than the value
of GoldServiceArpThd. A service is defined as a Bronze-level service if its ARP
value is larger than the value of this parameter. The service priority has a
negative correlation with the ARP value.

QCI1 handover Indicates the admission threshold for the handed-over service with QCI of 1.
admission threshold
This threshold applies to both UL and DL.
If the satisfaction rate of services with QCI of 1 is above or equal to this
threshold, the handed-over service with QCI of 1 can be admitted.
If the satisfaction rate of services with QCI of 1 is below this threshold, the
handed-over service with QCI of 1 cannot be admitted.

QCI2 handover Indicates the admission threshold for the handed-over service with QCI of 2.
admission threshold
This threshold applies to both UL and DL.
If the satisfaction rate of services with QCI of 2 is above or equal to this
threshold, the handed-over service with QCI of 2 can be admitted.
If the satisfaction rate of services with QCI of 2 is below this threshold, the
handed-over service with QCI of 2 cannot be admitted.

QCI3 handover Indicates the admission threshold for the handed-over service with QCI of 3.
admission threshold
This threshold applies to both UL and DL.
If the satisfaction rate of services with QCI of 3 is above or equal to this
threshold, the handed-over service with QCI of 3 can be admitted.
If the satisfaction rate of services with QCI of 3 is below this threshold, the
handed-over service with QCI of 3 cannot be admitted.

QCI4 handover Indicates the admission threshold for the handed-over service with QCI of 4.
admission threshold
This threshold applies to both UL and DL.
If the satisfaction rate of services with QCI of 4 is above or equal to this
threshold, the handed-over service with QCI of 4 can be admitted.
If the satisfaction rate of services with QCI of 4 is below this threshold, the
handed-over service with QCI of 4 cannot be admitted.

Gold new service Indicates the offset for admission of new gold-level services. This parameter
admission threshold
offset applies to both downlink and uplink. New gold-level services and handed-over
services with QCI N are admitted if both the following conditions are met: (1)
The satisfaction rate of services with QCI N is higher than or equal to the sum of
this offset and the admission threshold for the handed-over services with QCI N.
(2) The satisfaction rate of services with any other QCI is higher than or equal to
the corresponding admission threshold for the handed-over services with that
QCI.

Silver new service Indicates the offset for admission of new silver-level services. This parameter
Table 2 Related parameters

Parameter Description

admission threshold applies to both downlink and uplink. New silver-level services and handed-over
offset
services with QCI N are admitted if both the following conditions are met: (1)
The satisfaction rate of services with QCI N is higher than or equal to the sum of
this offset and the admission threshold for the handed-over services with QCI N.
(2) The satisfaction rate of services with any other QCI is higher than or equal to
the corresponding admission threshold for the handed-over services with that
QCI.

Bronze new service Indicates the offset for admission of new bronze-level services. This parameter
admission threshold
offset applies to both downlink and uplink. New bronze-level services and handed-
over services with QCI N are admitted if both the following conditions are met:
(1) The satisfaction rate of services with QCI N is higher than or equal to the
sum of this offset and the admission threshold for the handed-over services with
QCI N. (2) The satisfaction rate of services with any other QCI is higher than or
equal to the corresponding admission threshold for the handed-over services
with that QCI.

QCI1 congest threshold Indicates the congestion threshold for services with QCI of 1. This threshold
applies to both UL and DL.
If the satisfaction rate of services with QCI of 1 in the cell becomes lower than
this threshold, the services with QCI of 1 enter the congested state.
If the satisfaction rate of services with QCI of 1 in the cell becomes higher than
the sum of this threshold and the congestion relief offset, the services with QCI
of 1 leave the congested state.

QCI2 congest threshold Indicates the congestion threshold for services with QCI of 2. This threshold
applies to both UL and DL.
If the satisfaction rate of services with QCI of 2 in the cell becomes lower than
this threshold, the services with QCI of 2 enter the congested state.
If the satisfaction rate of services with QCI of 2 in the cell becomes higher than
the sum of this threshold and the congestion relief offset, the services with QCI
of 2 leave the congested state.

QCI3 congest threshold Indicates the congestion threshold for services with QCI of 3. This threshold
applies to both UL and DL.
If the satisfaction rate of the services with QCI of 3 in the cell becomes lower
than this threshold, the services with QCI of 3 enter the congested state.
If the satisfaction rate of services with QCI of 3 in the cell becomes higher than
the sum of this threshold and the congestion relief offset, the services with QCI
of 3 leave the congested state.

QCI4 congest threshold Indicates the congestion threshold for services with QCI of 4. This threshold
applies to both UL and DL.
Table 2 Related parameters

Parameter Description

If the satisfaction rate of services with QCI of 4 in the cell becomes lower than
this threshold, the services with QCI of 4 enter the congested state.
If the satisfaction rate of services with QCI of 4 in the cell becomes higher than
the sum of this threshold and the congestion relief offset, the services with QCI
of 4 leave the congested state.

Gold-level GBR service Indicates the rate reduction proportion for Gold-level GBR services. When
congest scheduler
proportion congestion occurs, the rate that the scheduling algorithm provides for Gold-level
GBR services (except VoIP services) is the product of GBR and this proportion.
This parameter will be removed in later versions. In this version, the setting of
this parameter is still synchronized between the M2000 and the eNodeB, but it is
no longer used internally. Therefore, avoid using this parameter.

Silver-level GBR Indicates the rate reduction proportion for Silver-level GBR services. When
service congest
scheduler proportion congestion occurs, the rate that the scheduling algorithm provides for Silver-
level GBR services (except VoIP services) is the product of the GBR and this
proportion. This parameter will be removed in later versions. In this version, the
setting of this parameter is still synchronized between the M2000 and the
eNodeB, but it is no longer used internally. Therefore, avoid using this
parameter.

Bronze-level GBR Indicates the rate reduction proportion for Bronze-level GBR services. When
service congest
scheduler proportion congestion occurs, the rate that the scheduling algorithm provides for Bronze-
level GBR services (except VoIP services) is the product of GBR and this
proportion. This parameter will be removed in later versions. In this version, the
setting of this parameter is still synchronized between the M2000 and the
eNodeB, but it is no longer used internally. Therefore, avoid using this
parameter.

GBR used resource Indicates the threshold for high resource usage by guaranteed bit rate (GBR)
high proportion
threshold services. This parameter is expressed in percentage and applies to both uplink
and downlink. If the MAC layer detects that the resource usage by GBR services
exceeds the threshold, the usage is high. In this situation, new GBR services are
not admitted if GbrUsageSwitch under the RacAlgoSwitch parameter is turned
on. This parameter will be removed in later versions. In this version, the setting
of this parameter is still synchronized between the M2000 and the eNodeB, but
it is no longer used internally. Therefore, avoid using this parameter.

GBR used resource low Indicates the threshold for low resource usage by guaranteed bit rate (GBR)
proportion threshold
services. This parameter is expressed in percentage and applies to both uplink
and downlink. If the MAC layer detects that the resource usage by GBR services
falls below the threshold, the usage is low. This parameter will be removed in
later versions. In this version, the setting of this parameter is still synchronized
between the M2000 and the eNodeB, but it is no longer used internally.
Table 2 Related parameters

Parameter Description

Therefore, avoid using this parameter.

ARP threshold Indicates the Allocation and Retention Priority (ARP) threshold for low Energy
Efficiency Ratio (EER) services. If the ARP value of a service is less than the
value of this parameter, the service will not be released for congestion control.
This parameter will be removed in later versions. In this version, the setting of
this parameter is still synchronized between the M2000 and the eNodeB, but it is
no longer used internally. Therefore, avoid using this parameter.

Offset for service Indicates the congestion release offset. The service of a specific QCI exits the
congest relieving
congestion state if the satisfaction rate of the service exceeds the sum of this
congestion release offset and the congestion threshold for the QCI. The service
retains the congestion state if the satisfaction rate is below or equal to the sum of
this congestion release offset and the congestion threshold for the QCI.

Preemption ARP Indicates the Allocation and Retention Priority (ARP) threshold for preemption.
threshold
The services that have ARP values larger than or equal to the value of this
parameter are preemptible. This parameter will be removed in later versions. In
this version, the setting of this parameter is still synchronized between the
M2000 and the eNodeB, but it is no longer used internally. Therefore, avoid
using this parameter.

Uplink RB used ratio Indicates the threshold for deciding on whether the UL RB usage is high. This
high threshold
threshold applies to UL admission decision. If the UL RB usage reported by the
MAC layer is above this threshold, the UL RB usage is assumed to be high.

Downlink RB used ratio Indicates the threshold for high downlink RB usage. This parameter is used for
high threshold
downlink admission decision. If the downlink RB usage reported by the MAC
layer is greater than the value of this parameter, the downlink RB usage is high.
This parameter will be removed in later versions. In this version, the setting of
this parameter is still synchronized between the M2000 and the eNodeB, but it is
no longer used internally. Therefore, avoid using this parameter.

Uplink RB used ratio Indicates the threshold for deciding on whether the UL RB usage is low. It
low threshold
applies to UL admission decision. If the UL RB usage reported by the MAC
layer is below this threshold, the UL RB usage is assumed to be low.

Downlink RB used ratio Indicates the threshold for low downlink RB usage. This parameter is used for
low threshold
downlink admission decision. If the downlink RB usage reported by the MAC
layer is less than the value of this parameter, the downlink RB usage is low. This
parameter will be removed in later versions. In this version, the setting of this
parameter is still synchronized between the M2000 and the eNodeB, but it is no
longer used internally. Therefore, avoid using this parameter.
Table 2 Related parameters

Parameter Description

Non-GBR max bearer Indicates the maximum number of non-GBR bearers (excluding bearers of IP
number
Multimedia Subsystem [IMS] services) that can be provided by a cell. This
parameter applies to both uplink and downlink. This parameter will be removed
in later versions. In this version, the setting of this parameter is still
synchronized between the M2000 and the eNodeB, but it is no longer used
internally. Therefore, avoid using this parameter.

5.7.1.6.3.46 CellResel
+-NE
+-eNodeBFunction
+-Cell
+-CellResel

Description

The CellResel MO consists of the parameters related to reselection in the cell System
Information Block 3 (SIB3). For details of the cell reselection, see 3GPP TS 36.304.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the UtranNFreq MO:


- If CellReselPriorityCfgInd in UtranNFreq MO is set to CFG, CellReselPriority in
CellResel MO cannot be set same as CellReselPriority in UtranNFreq MO for each cell.
Relation with the GeranNfreqGroup MO:
- If CellReselPriorityCfgInd in GeranNfreqGroup MO is set to CFG, CellReselPriority in
CellResel MO cannot be set same as CellReselPriority in GeranNfreqGroup MO for each cell.
Relation with the Cdma2000BandClass MO:
- If Cdma20001XrttCellReselInd in Cdma2000BandClass MO is set to CFG,
Cdma20001XrttCellReselPri in Cdma2000BandClass MO cannot be set same as
CellReselPriority in CellResel MO for each cell,and if Cdma2000HrpdCellReselInd in
Cdma2000BandClass MO is set to CFG, Cdma2000HrpdCellReselPri in
Cdma2000BandClass MO cannot be set same as CellReselPriority in CellResel MO for each
cell.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST CELLRESEL Use this command to list the parameters about cell reselection.

MOD CELLRESEL Use this command to modify the parameters about cell reselection.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Hysteresis value for Indicates the hysteresis for cell reselection when RSRP values are used in the
ranking criteria
evaluation. This parameter must be set based on the slow fading characteristic of
the area covered by the cell. The greater the slow fading variance is, the larger
the value of this parameter must be set to. A larger value of the hysteresis results
in a larger boundary of the serving cell and a higher probability of cell
reselection to neighboring cells.

Speed-dependent Indicates whether to set the parameters related to speed-dependent cell


reselection parameter
configure indicator reselection.

The duration for Indicates the duration in which the mobility status of the UE is evaluated. This
evaluating criteria to
enter mobility states parameter is one of the key parameters in deciding on the UE mobility. A smaller
value of this parameter may lead to more frequent switching among mobility
status and lower decision accuracy. A larger value of this parameter leads to the
opposite effect.
Table 2 Related parameters

Parameter Description

Additional time Indicates the extra duration required in the evaluation before the UE can enter
hysteresis for normal
speed the normal-mobility state. This parameter can prevent UEs from frequently
switching from the high- or medium-mobility state to the normal-mobility state,
and is one of the key parameters in deciding on the UE mobility. A larger value
of this parameter leads to a lower probability of transition from the high- or
medium-mobility state to the normal-mobility state but higher decision accuracy.
A smaller value of this parameter leads to the opposite effect.

The number of cell Indicates the threshold of the number of cell reselections, which is used for a UE
changes to enter
medium mobility state to enter the medium mobility state. This parameter is one of the key parameters
in determining the mobility state of the UE. During a UE mobility evaluation
period, if the number of cell reselections is greater than this parameter value and
is less than or equal to the NCellChangeHigh parameter value, the UE enters the
medium mobility state.

The number of cell Indicates the threshold for a UE to enter the high mobility state. Based on the
changes to enter high
mobility state number of cell reselections, this parameter is one of the key parameters in
determining the mobility state of the UE. During the UE mobility evaluation, if
the number of cell reselections is greater than this parameter value, the UE
enters the high mobility state.

Additional hysteresis for Indicates the scaling factor (or known as additional hysteresis) applied to Qhyst
medium speed
for medium-mobility UEs. For details, see 3GPP TS 36.304 and 3GPP TS
36.331.

Additional hysteresis for Indicates the scaling factor (or known as additional hysteresis) applied to Qhyst
high speed
for high-mobility UEs. For details, see 3GPP TS 36.304 and 3GPP TS 36.331.

Threshold for non-intra Indicates whether to set the measurement triggering threshold for reselection to
freq measurements
configure indicator inter-frequency or inter-RAT cells. If this parameter is set to NOT_CFG(Not
configure), a UE always measures inter-frequency and inter-RAT cells
regardless of the serving cell's signal quality.

Threshold for non-intra Indicates the measurement triggering threshold for cell reselection to inter-
frequency
measurements frequency or inter-RAT cells. If the cell reselection priority of a frequency or
RAT is higher than that of the serving frequency, the UE always starts inter-
frequency or inter-RAT measurement. If the cell reselection priority of a
frequency is less than or equal to that of the serving frequency or the cell
reselection priority of a RAT is less than that of the serving frequency, the UE
starts inter-frequency or inter-RAT measurements only when the value of Cell
selection RX level value (dB) is lower than or equal to the value of this
parameter.

Serving frequency Indicates the threshold used in the evaluation of reselection to a cell on a lower
lower priority threshold
Table 2 Related parameters

Parameter Description

priority E-UTRAN frequency or on an inter-RAT frequency. Cell reselection to a


cell on a lower priority E-UTRAN frequency or on an inter-RAT frequency is
performed if no cell on the serving frequency or on a higher priority E-UTRAN
frequency fulfills criteria 1 for inter-frequency and inter-RAT reselections. For
details, see 3GPP TS 36.304.

Cell reselection priority Indicates the cell reselection priority of the serving frequency. 0 indicates the
lowest priority. The value of this parameter must be determined together with
the priorities of other frequencies during the network planning. Frequencies used
for different RATs must be assigned different cell reselection priorities.

Minimum required RX Indicates the minimum required RX level used in intra-frequency E-UTRAN
level
cell reselection, which corresponds to the IE q-RxLevMin in SIB3. This value is
used in the evaluation of cell reselection. For details, see 3GPP TS 36.304.

Ue max power allowed Indicates whether to configure the maximum TX power of the UE in the intra-
configure indicator
frequency neighboring cell. If the value of this parameter is not specified, the
maximum power is subject to the UE capability.

Max transmit power Indicates the maximum power that the UE can apply to transmission in the intra-
allowed
frequency neighboring cell. It is used in cell reselection criteria to calculate the
compensated power. If the value of this parameter is not specified, the maximum
power is subject to the UE capability. For details, see 3GPP TS 36.304.

Threshold for intra freq Indicates whether to set the measurement triggering threshold for reselection to
measurements
configure indicator intra-frequency cells.

Threshold for intra Indicates the measurement triggering threshold for reselection to intra-frequency
frequency
measurements cells.
The UEs start intra-frequency measurements only if the value of Cell selection
RX level value (dB) is lower than or equal to the value of this parameter.

Measurement Indicates whether to set the measurement bandwidth.


bandwidth configure
indicator

Measurement Indicates the measurement bandwidth on the serving frequency on which the UE
bandwidth
camps. It is used in intra-frequency measurements for cell reselection and those
by UEs in RRC_CONNECTED mode. This parameter is optional; if it is not set,
the downlink bandwidth of the serving cell is used by default.

Cell reselection timer Indicates the cell reselection duration of the E-UTRAN. When the signal quality
value for EUTRAN
of the new cell is better than the serving cell all the time and the UE stays in the
current serving cell for more than 1s, the UE is initiating cell reselection request
Table 2 Related parameters

Parameter Description

to the new cell.

Speed state scale Indicates whether to set the scaling parameters for speed-dependent cell
factor configure
indicator reselection within E-UTRAN.

Scaling factor of Indicates the scaling factor applied to TReselEutra for medium-mobility UEs.
TReselEutra in medium
mobility state The actual duration of cell reselection for medium-mobility UEs to E-UTRAN is
equal to the product of TReselEutra and TReselEutranSfMedium.

Scaling factor of Indicates the scaling factor applied to TReselEutran for high-mobility UEs. The
TReselEutra in high
mobility state actual duration of cell reselection of high-mobility UEs to E-UTRAN is equal to
TReselEutran multiplied by TReselEutranSfHigh.

Neighbor cell config Indicates the information related to MBSFN and TDD UL/DL configurations of
intra-frequency neighboring cells of the serving cell.
BitString00: Indicates that some neighboring cells have the same MBSFN
subframe configuration as the serving cell.
BitString01: Indicates that none of the neighboring cells is configured with
MBSFN subframes.
BitString10: Indicates that the MBSFN subframe configurations of all
neighboring cells are the same as or subsets of that of the serving cell.
BitString11: Indicates that some neighboring cells have different UL-DL
configurations from the serving TDD cell.
For details, see 3GPP TS 36.331.

Presence antenna port1 Indicates whether the intra-frequency neighboring cells are configured with at
least two antenna ports.
Set this parameter to TRUE when all the intra-frequency neighboring cells are
configured with at least two antenna ports.
Set this parameter to FALSE when one of the intra-frequency neighboring cells
is configured with only one antenna port.

RSRQ Threshold for Indicates the RSRQ threshold for starting intra-frequency measurements. It
intra frequency
measurements determines the probability of triggering cell reselection to an intra-frequency
neighboring cell. For details, see 3GPP TS 36.304.

RSRQ Threshold for Indicates the RSRQ threshold for starting inter-frequency or inter-RAT
non-intra frequency
measurements measurements. It determines the probability of triggering cell reselection to an
inter-frequency or inter-RAT neighboring cell. For details, see 3GPP TS 36.304.

Serving frequency Indicates whether to set the RSRQ threshold for reselection to cells on lower-
lower priority RSRQ
threshold configure priority frequencies.
Table 2 Related parameters

Parameter Description

indicator

Serving frequency Indicates the RSRQ threshold for cell reselection to cells on lower-priority
lower priority RSRQ
threshold frequencies. It determines the probability of triggering cell reselection to inter-
frequency or inter-RAT neighboring cells on lower-priority frequencies. For
details, see 3GPP TS 36.304.

Minimum required Indicates whether to set cell reselection parameters in compliance with 3GPP
quality level configure
indicator Release 9 in SIB3.

Minimum required Indicates the minimum required RX signal quality used in intra-frequency E-
quality level
UTRAN cell reselection, which corresponds to the IE q-QualMin in SIB3. This
value is included in criteria R and used in the evaluation of cell reselection. For
details, see 3GPP TS 36.304.

5.7.1.6.3.47 CellReselCdma2000
+-NE
+-eNodeBFunction
+-Cell
+-CellReselCdma2000

Description

The CellReselCdma2000 MO consists of the parameters related to cell reselection to


CDMA2000. This MO contains the SIB8 information and is optional.
If this MO is not configured, cell reselection to CDMA2000 is not allowed.
For details on cell reselection to CDMA2000, see 3GPP TS 36.304.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell
Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add the configuration related to cell reselection to
CELLRESELCDMA200
0 CDMA2000.

LST Use this command to list the parameters about cell reselection to CDMA2000.
CELLRESELCDMA200
0

MOD Use this command to modify the configuration of cell reselection to


CELLRESELCDMA200
0 CDMA2000.

RMV Use this command to remove the configuration of cell reselection to


CELLRESELCDMA200
0 CDMA2000.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

System time Indicates whether to configure the CDMA2000 system time information. For
information configure
indicator details, see 3GPP TS 36.331.

CDMA and EUTRA Indicates the network synchronization status. If this parameter is set to
network synchronised
indicator BOOLEAN_TRUE, the E-UTRAN and the CDMA2000 RAN are synchronized
without drifts. If this parameter is set to BOOLEAN_FALSE, the E-UTRAN and
the CDMA2000 RAN are not synchronized. For details, see 3GPP TS 36.331.

CDMA search window Indicates whether to set the search window size. For details, see 3GPP TS
size configure indicator
36.331.

Search window size Indicates the size of the CDMA2000 search window, and can be used to assist in
searching for the neighboring pilots. For details, see 3GPP TS 36.331.
Table 2 Related parameters

Parameter Description

HRPD parameters Indicates whether the eNodeB contains the information about CDMA2000
configure indicator
HRPD in SIB8. If this parameter is set to CFG, the eNodeB contains the
parametersHRPD field in SIB8. If this parameter is set to NOT_CFG, the
eNodeB does not contain the parametersHRPD field in SIB8. For details, see
3GPP TS 36.331.

HRPD cell reselection Indicates whether to set the parameters related to cell reselection to CDMA2000
configure indicator
HRPD.

Cell reselection timer Indicates the duration used in cell reselection to CDMA2000 HRPD. If the
for HRPD
signal quality in a CDMA2000 HRPD cell is better than that in the serving cell
for the period specified by this parameter and a UE has been camped on the
serving cell for more than 1s, the UE attempts to reselect the CDMA2000 HRPD
cell to camp on. For details, see 3GPP TS 36.331.

Speed state scale Indicates whether to set the speed-dependent scaling parameters related to cell
factor configure
indicator reselection to CDMA2000 HRPD. For details, see 3GPP TS 36.331.

Scaling factor of Indicates the scaling factor applied to TReselCdmaHrpd for high-mobility UEs.
TReselCdmaHrpd in
high mobility state The actual duration of cell reselection of high-mobility UEs to CDMA2000
HRPD is equal to TReselCdmaHrpd multiplied by TReselCdmaHrpdSfHigh.
For details, see 3GPP TS 36.331.

Scaling factor of Indicates the scaling factor applied to TReselCdmaHrpd for medium-mobility
TReselCdmaHrpd in
medium mobility state UEs. The actual duration of cell reselection of medium-mobility UEs to
CDMA2000 HRPD is equal to TReselCdmaHrpd multiplied by
TReselCdmaHrpdSfMedium. For details, see 3GPP TS 36.331.

1XRTT parameters Indicates whether the eNodeB contains the information about CDMA2000
configure indicator
1xRTT in SIB8. If this parameter is set to CFG, the eNodeB contains the
parameters1xRTT field in SIB8. If this parameter is set to NOT_CFG, the
eNodeB does not contain the parameters1xRTT field in SIB8. For details, see
3GPP TS 36.331.

1XRTT state of long Indicates whether the information element (IE) longCodeState1XRTT is
code generation
registers configure contained in system information message 8 (SIB8). When this parameter is set to
indicator CFG(Configure), the IE longCodeState1XRTT is contained in SIB 8. When this
parameter is set to NOT_CFG(Not configure), the IE longCodeState1XRTT is
not contained in SIB 8. The CDMA2000 1xRTT-specific long code state is
automatically generated based on system time. For details, see 3GPP TS 36.331.

1XRTT cell reselection Indicates whether the parameters applicable only for cell reselection to
configure indicator
CDMA2000 1xRTT need to be set.
Table 2 Related parameters

Parameter Description

Cell reselection timer Indicates the duration used in cell reselection to CDMA2000 1xRTT. If the
for 1XRTT
signal quality in a CDMA2000 1xRTT cell is better than that in the serving cell
for the period specified by this parameter and a UE has been camped on the
serving cell for more than 1s, the UE attempts to reselect the CDMA2000
1xRTT cell to camp on. For details, see 3GPP TS 36.331.

1XRTT speed state Indicates whether speed-dependent scaling parameters need to be set for cell
scale factors configure
indicator reselection to CDMA2000 1xRTT.

1XRTT medium speed Indicates the scaling factor applicable to cell reselection of medium-mobility
scale factor
UEs to CDMA2000 1xRTT. For details, see 3GPP TS 36.331.

1XRTT high speed Indicates the scaling factor applicable to cell reselection of high-mobility UEs to
scale factor
CDMA2000 1xRTT. For details, see 3GPP TS 36.331.

5.7.1.6.3.48 CellReselGeran
+-NE
+-eNodeBFunction
+-Cell
+-CellReselGeran

Description

The CellReselGeran MO consists of the parameters related to cell reselection to GERAN. This
MO contains the SIB7 information and is optional. If this MO is not configured, cell reselection
to GERAN is not allowed. For details on cell reselection to GERAN, see 3GPP TS 36.304.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands


Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add the configuration related to cell reselection to
CELLRESELGERAN
GERAN.

LST Use this command to list the parameters about cell reselection to GERAN.
CELLRESELGERAN

MOD Use this command to modify the parameters about cell reselection to GERAN.
CELLRESELGERAN

RMV Use this command to remove the configuration of cell reselection to GERAN.
CELLRESELGERAN

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Cell reselection timer Indicates the evaluation period for a UE to determine whether to reselect a
value for GERAN
GERAN cell to camp on. If the signal quality in a GERAN cell is better than
that in the serving cell for the period specified by this parameter and a UE has
been camped on the serving cell for more than 1s, the UE attempts to reselect
the GERAN cell to camp on.

Speed state scale Indicates whether to set the speed-dependent scaling parameters related to cell
factor configure
indicator reselection to GERAN.

Scaling factor of Indicates the scaling factor applied to TReselGeran for medium-mobility UEs.
TReselGeran in
medium mobility state The actual duration of cell reselection of medium-mobility UEs to GERAN is
equal to TReselGeran multiplied by TReselGeranSfMedium.

Scaling factor of Indicates the scaling factor applied to TReselGeran for high-mobility UEs. The
TReselGeran in high
mobility state actual duration of cell reselection of high-mobility UEs to GERAN is equal to
TReselGeran multiplied by TReselGeranSfHigh.
5.7.1.6.3.49 CellReselUtran
+-NE
+-eNodeBFunction
+-Cell
+-CellReselUtran

Description

The CellReselUtran MO consists of the parameters related to cell reselection to UTRAN. This
MO contains the SIB6 information and is optional. If this MO is not configured, cell reselection
to UTRAN is not allowed. For details on cell reselection to UTRAN, see 3GPP TS 36.304.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add the configuration related to cell reselection to
CELLRESELUTRAN
UTRAN.

LST Use this command to list the parameters about cell reselection to UTRAN.
CELLRESELUTRAN

MOD Use this command to modify the parameters about cell reselection to UTRAN.
CELLRESELUTRAN

RMV Use this command to remove the configuration of cell reselection to UTRAN.
CELLRESELUTRAN

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Cell reselection timer Indicates the evaluation period for a UE to determine whether to reselect a
value for UTRAN
UTRAN cell to camp on. If the signal quality in a UTRAN cell is better than
that in the serving cell for the period specified by this parameter and a UE has
been camped on the serving cell for more than 1s, the UE attempts to reselect
the UTRAN cell to camp on.

Speed state scale Indicates whether to set the speed-dependent scaling parameters related to cell
factor configure
indicator reselection to UTRAN.

Scaling factor of Indicates the scaling factor applied to TReselUtran for medium-mobility UEs.
TReselUtran in medium
mobility state The actual duration of cell reselection of medium-mobility UEs to UTRAN is
equal to TReselUtran multiplied by TReselUtranSfMedium.
The value T_RESEL_SF_0DOT25 means a scaling factor of 0.25,
T_RESEL_SF_0DOT5 means 0.5, and so on.

Scaling factor of Indicates the scaling factor applied to TReselUtran for high-mobility UEs. The
TReselUtran in high
mobility state actual duration of cell reselection of high-mobility UEs to UTRAN is equal to
TReselUtran multiplied by TReselUtranSfHigh.
The value T_RESEL_SF_0DOT25 means a scaling factor of 0.25,
T_RESEL_SF_0DOT5 means 0.5, and so on.

5.7.1.6.3.50 CellRfShutdown
+-NE
+-eNodeBFunction
+-Cell
+-CellRfShutdown

Description

The CellRfShutdown MO consists of the parameters related to RF channel intelligent shutdown


mode for a cell. In a specified time span, if RF channel intelligent shutdown is enabled, the
conditions for triggering intelligent shutdown in specific scenarios are as follows: For FDD cells,
the cell status is normal and no UE accesses the cell. For TDD cells with different number of
antennas and interfaces, such as 2T2P or 4T4P scenario, the cell status is normal and no UE
accesses the cell. For TDD cells with different number of antennas and interfaces, such as 4T2P,
8T2P, or 8T4P scenario, the cell status is normal and the UL and DL loads are lower than the UL
and DL PRB usage thresholds. If the condition is met, the eNodeB automatically shuts down half
of the PAs for TX channels. If the condition is not met, the eNodeB automatically starts the PAs
that have been shut down. In this way, energy conservation and emission reduction are
achieved.A cell enters the RF channel intelligent shutdown state when all the following
conditions are met: (1) transmit diversity is used in the cell, and the switch for RF intelligent
shutdown is turned on; (2) it is within the duration when RF channel intelligent shutdown is
active; (3) For FDD cells, the cell status is normal and no UE accesses the cell. For TDD cells
with different number of antennas and interfaces, such as 2T2P or 4T4P scenario, the cell status
is normal and no UE accesses the cell. For TDD cells with different number of antennas and
interfaces, such as 4T2P, 8T2P, or 8T4P scenario, the cell status is normal and the UL and DL
loads are lower than the UL and DL PRB usage thresholds.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the Cell MO:


- If CellActiveState in a Cell MO is set to CELL_ACTIVE, FddTddInd is CELL_TDD
Model and DlBandWidth is CELL_BW_N25, RfShutdownSwitch in the CellRfShutdown
must be set OFF.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP Use this command to query the dynamic information about RF channel
CELLRFSHUTDOWN
intelligent shutdown for a cell.

LST Use this command to list the configuration of RF channel intelligent shutdown
CELLRFSHUTDOWN
for a cell.

MOD Use this command to modify the configuration of RF channel intelligent


CELLRFSHUTDOWN
shutdown in a cell.

Related Parameters
Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

RF intelligent shutdown Indicates whether to enable or disable RF channel intelligent shutdown for the
switch
cell. RF channel intelligent shutdown can be performed in the cell only when
this parameter is set to ON and certain conditions are met.

Start time Indicates the start time of the cell RF channel intelligent shutdown.

Stop time Indicates the stop time of RF channel intelligent shutdown for the cell. If the
stop time is earlier than or the same as the start time, the stop time is assumed to
be a time of the next day.

Reference signal power Indicates the value by which the reference signal power is increased during the
adjust offset
RF channel intelligent shutdown period. The reference signal power increases by
the value specified by this parameter to ensure coverage of the cell. If this
parameter is set to a value greater than 3, the value 3 applies in effect.
Otherwize,the configuration value applies in effect.

Downlink PRB Indicates the downlink PRB usage threshold for RF channel intelligent
threshold
shutdown. If the current cell load is smaller than both the uplink PRB usage
threshold and downlink PRB usage threshold, the cell enters the RF channel
intelligent shutdown mode. If the current cell load is greater than or equal to the
total value of the uplink PRB usage threshold and the uplink PRB offset or the
total value of the downlink PRB usage threshold and the downlink PRB offset,
the cell exits the RF channel intelligent shutdown mode.
If this parameter is set to a smaller value, the cell is harder to enter the RF
channel intelligent shutdown mode, which does not facilitate eNodeB power
saving. If this parameter is set to a larger value, the cell is easier to enter the RF
channel intelligent shutdown mode, which affects user services.

Uplink PRB threshold Indicates the uplink PRB usage threshold for RF channel intelligent shutdown. If
the current cell load is smaller than both the uplink PRB usage threshold and
downlink PRB usage threshold, the cell enters the RF channel intelligent
shutdown mode. If the current cell load is greater than or equal to the total value
of the uplink PRB usage threshold and the uplink PRB offset or the total value
of the downlink PRB usage threshold and the downlink PRB offset, the cell exits
the RF channel intelligent shutdown mode.
If this parameter is set to a smaller value, the cell is harder to enter the RF
channel intelligent shutdown mode, which does not facilitate eNodeB power
saving. If this parameter is set to a larger value, the cell is easier to enter the RF
channel intelligent shutdown mode, which affects user services.
Table 2 Related parameters

Parameter Description

Downlink PRB offset Indicates the downlink PRB offset for RF channel intelligent shutdown.
If the current cell load is greater than or equal to the total value of the uplink
PRB usage threshold and the uplink PRB offset or the total value of the
downlink PRB usage threshold and the downlink PRB offset, the cell exits the
RF channel intelligent shutdown mode.
If this parameter is set to a smaller value, the cell is easier to exit the RF channel
intelligent shutdown mode and the risk of ping-pong RF channel shutdown
increases. If this parameter is set to a larger value, the cell is harder to exit the
RF channel intelligent shutdown mode, which affects user services.

Uplink PRB offset Indicates the uplink PRB offset for RF channel intelligent shutdown.
If the current cell load is greater than or equal to the total value of the uplink
PRB usage threshold and the uplink PRB offset or the total value of the
downlink PRB usage threshold and the downlink PRB offset, the cell exits the
RF channel intelligent shutdown mode.
If this parameter is set to a smaller value, the cell is easier to exit the RF channel
intelligent shutdown mode and the risk of ping-pong RF channel shutdown
increases. If this parameter is set to a larger value, the cell is harder to exit the
RF channel intelligent shutdown mode, which affects user services.

Current status about RF Indicates the current status about RF channel intelligent shutdown for a cell.
intelligent shutdown

Latest exiting cause Indicates the latest exiting cause about RF channel intelligent shutdown for a
about RF intelligent
shutdown cell.

5.7.1.6.3.51 CellRicAlgo
+-NE
+-eNodeBFunction
+-Cell
+-CellRicAlgo

Description

The CellRicAlgo MO consists of the parameters related to remote interference cancellation. This
function detects downlink interference between TDD eNodeBs that are distant from each other
and also prevents or eliminates the interference. Remote interference cancellation applies to an
LTE TDD network consisting of more than 200 eNodeBs or consisting of multiple subnetworks
with inter-subnetwork spacing greater than 21.4 km. The time that related commands begin to
take effect must be specified according to the Greenwich Mean Time (GMT).

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the Cell MO:


- If CellActiveState in a Cell MO is set to CELL_ACTIVE, FddTddInd is CELL_TDD
Model and DlBandWidth is CELL_BW_N25, RicAlgoSwitch in the CellRicAlgo must be set
OFF.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

GET CELLRICDATA Use this command to collect data about remote interference to the local TDD
cell. Based on the collected dedicated signals (DSs) or cell reference signals
(CRSs), PCIs can be obtained to help identify the cells that cause remote
interference.

LST CELLRICALGO Use this command to list the configuration of the remote interference
cancellation algorithm in one or all cells.

MOD CELLRICALGO Use this command to modify the configuration of the remote interference
cancellation algorithm in a cell.

SND CELLRICPCISEQ Use this command to send data about TDD cell remote interference. Dedicated
signals (DSs) are generated based on the equivalent PCI of a cell. The equivalent
PCI equals the sum of the cell PCI and the PCI offset set in this command. DSs
are used to distinguish cells with the same PCI and help identify the cells that
cause remote interference.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local identity of the cell. It uniquely identifies a cell within an
eNodeB.

RIC algorithm switch Indicates the switch for the remote interference cancellation algorithm. If this
switch is turned on, the eNodeB performs remote interference detection and
records in call history record (CHR) logs if any interference is detected. If this
switch is turned off, the eNodeB does not perform remote interference detection.

Mute UpPTS Symbol Indicates the number of empty symbols in an uplink pilot timeslot (UpPTS). If
Number
this parameter is set to a non-zero value N, then no data is transmitted within the
N symbols starting from the first symbol in the UpPTS. Note that, for any given
special subframe configuration, the value of this parameter cannot be greater
than the total number of symbols contained in the UpPTS.

Whether to mute UL Indicates whether to empty the last symbol in each uplink subframe. If this
symbol
parameter is set to ON(On), the last symbol in each uplink subframe is emptied.
If this parameter is set to OFF(Off), the last symbol in each uplink subframe is
not emptied.

5.7.1.6.3.52 CellSel
+-NE
+-eNodeBFunction
+-Cell
+-CellSel

Description

The CellSel MO consists of the parameters related to cell selection in the cell System
Information Block 1 (SIB1). For detail of the cell selection, see 3GPP TS 36.304.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST CELLSEL Use this command to list the parameters about cell selection.

MOD CELLSEL Use this command to modify the parameters about cell selection.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Minimum required RX Indicates the minimum required RX level for the cell to become a candidate for
level
cell selection. This value is included in criteria S and used in the evaluation of
cell selection. For details, see 3GPP TS 36.304.

Minimum required RX Indicates the offset to the minimum required RX level. This value is included in
level offset
criteria S and used in the evaluation of cell selection. This parameter is valid
only when the cell selection is triggered by periodic searches for higher-priority
PLMNs and the UE is served by a Visited Public Land Mobile Network
(VPLMN). For details, see 3GPP TS 36.304.

Minimum required RX Indicates the minimum required RX signal quality for the cell to become a
quality level
candidate for cell selection, which corresponds to the IE q-QualMin in SIB1.
This value is included in criteria S and used in the evaluation of cell selection.
For details, see 3GPP TS 36.304.

Minimum required RX Indicates whether to set the offset to the minimum required RX level for the cell.
quality level offset
configure indicator

Minimum required RX Indicates the offset to the minimum required RX level for the cell. It is included
quality level offset
in criteria S and used in the evaluation of cell selection. This parameter is
required only when the cell selection is triggered by periodic searches for
Table 2 Related parameters

Parameter Description

higher-priority PLMNs and the UE is served by a Visited Public Land Mobile


Network (VPLMN). For details, see 3GPP TS 36.304.

5.7.1.6.3.53 CellServiceDiffCfg
+-NE
+-eNodeBFunction
+-Cell
+-CellServiceDiffCfg

Description

The CellServiceDiffCfg MO consists of parameters related to service differentiation in a cell.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the configuration of cell service differentiation.
CELLSERVICEDIFFCF
G

MOD Use this command to modify the configuration of cell service differentiation.
CELLSERVICEDIFFCF
G
Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local cell identity. It uniquely identifies a cell within an eNodeB.

Service differentiation Indicates the switches related to service differentiation in a cell.


switch
CellConStaReportSwitch: Indicates the switch used to control whether the cell
congestion information is reported using the extended GTP-U headers to the
EPC. The guideline can be found in documents related to the EPC feature, which
is Wireless Optimization Based on Flow Priority.
FPIGTPUSwitch: Indicates whether to enable the service differentiation feature
using the extended GTP-U header containing the FPI value. The guideline can
be found in documents related to the EPC feature, which is Wireless
Optimization Based on Flow Priority.
DSCPRemarkSwitch: Indicates whether to enable the DSCP Remark-based
service differentiation feature. If DSCPRemarkSwitch is set to On, the eNodeB
guarantees differentiated quality of service (QoS) based on the service type
specified by the DSCP field in the IP packet sent by the PDN gateway to the
eNodeB.

Weight of queue 0 Indicates the weight of the queue, which is used in service differentiation
scheduling. The value of this parameter is used in calculating the priority of a
UE during scheduling and therefore determines the scheduling probability of
this UE. The scheduling probability and priority of services in a queue has a
positive correlation with the value of this parameter. This parameter is valid only
if FPIGTPUSwitch(FPIGTPUSwitch) or
DSCPRemarkSwitch(DSCPRemarkSwitch) is turned on. When
DSCPRemarkSwitch is turned on, this parameter indicates the weight of nonP2P
service queue.

Weight of queue 1 Indicates the weight of the queue, which is used in service differentiation
scheduling. The value of this parameter is used in calculating the priority of a
UE during scheduling and therefore determines the scheduling probability of
this UE. The scheduling probability and priority of services in a queue has a
positive correlation with the value of this parameter. This parameter is valid only
if FPIGTPUSwitch(FPIGTPUSwitch) or
DSCPRemarkSwitch(DSCPRemarkSwitch) is turned on. When
DSCPRemarkSwitch is turned on, this parameter indicates the weight of P2P
service queue.

Weight of queue 2 Indicates the weight of the queue, which is used in service differentiation
scheduling. The value of this parameter is used in calculating the priority of a
Table 2 Related parameters

Parameter Description

UE during scheduling and therefore determines the scheduling probability of


this UE. The scheduling probability and priority of services in a queue has a
positive correlation with the value of this parameter. This parameter is valid only
if FPIGTPUSwitch(FPIGTPUSwitch) is turned on.

Weight of queue 3 Indicates the weight of the queue, which is used in service differentiation
scheduling. The value of this parameter is used in calculating the priority of a
UE during scheduling and therefore determines the scheduling probability of
this UE. The scheduling probability and priority of services in a queue has a
positive correlation with the value of this parameter. This parameter is valid only
if FPIGTPUSwitch(FPIGTPUSwitch) is turned on.

Weight of queue 4 Indicates the weight of the queue, which is used in service differentiation
scheduling. The value of this parameter is used in calculating the priority of a
UE during scheduling and therefore determines the scheduling probability of
this UE. The scheduling probability and priority of services in a queue has a
positive correlation with the value of this parameter. This parameter is valid only
if FPIGTPUSwitch(FPIGTPUSwitch) is turned on.

Weight of queue 5 Indicates the weight of the queue, which is used in service differentiation
scheduling. The value of this parameter is used in calculating the priority of a
UE during scheduling and therefore determines the scheduling probability of
this UE. The scheduling probability and priority of services in a queue has a
positive correlation with the value of this parameter. This parameter is valid only
if FPIGTPUSwitch(FPIGTPUSwitch) is turned on.

Weight of queue 6 Indicates the weight of the queue, which is used in service differentiation
scheduling. The value of this parameter is used in calculating the priority of a
UE during scheduling and therefore determines the scheduling probability of
this UE. The scheduling probability and priority of services in a queue has a
positive correlation with the value of this parameter. This parameter is valid only
if FPIGTPUSwitch(FPIGTPUSwitch) is turned on.

5.7.1.6.3.54 CellShutdown
+-NE
+-eNodeBFunction
+-Cell
+-CellShutdown
Description

The CellShutDown MO consists of the parameters related to intelligent power-off of carriers in


the same coverage. This feature applies to scenarios where the local cell has inter-frequency
neighboring cells under the same eNodeB. If the local cell and its intra-eNodeB inter-frequency
neighboring cells are all lightly loaded and the PRB usage of the local cell meets the conditions
for intelligent power-off of carriers in the same coverage, the local cell enters intelligent power-
off of carriers in the same coverage mode after all UEs are diverted to these inter-frequency
neighboring cells. Then, if the intra-eNodeB inter-frequency neighboring cells become heavily
loaded, the local cell automatically exits intelligent power-off of carriers in the same coverage
mode. With this feature, the power consumption is reduced. A cell enters intelligent power-off of
carriers in the same coverage mode when all the following conditions are met: (1) the local cell
has at least an intra-eNodeB inter-frequency neighboring cell whose intelligent power-off of
carriers switch is enabled and the UL or DL PRB usage threshold is set to 0, which is also called
a basic cell; (2) the basic cell works properly and serves the same PLMNs as the local cell; (3)
intelligent power-off of carriers switch is enabled in the local cell and the time is within the
duration when intelligent power-off of carriers in the same coverage is active in both cells; (4)
both cells are lightly loaded and the PRB usage of the local cell meets the conditions to start
intelligent power-off of carriers in the same coverage; (5) (this condition is required when there
are ongoing services in the local cell) inter-frequency handover is enabled.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the CellMLB MO:


- The sum of InterFreqMlbThd and LoadOffset in the CellMLB MO must be greater than
that of DlPrbThd and DlPrbOffset in the CellShutdown MO. In addition, the sum of
InterFreqMlbThd and LoadOffset in the CellMLB MO must be greater than that of
UlPrbThd and UlPrbOffset in the CellShutdown MO.
- InterFreqMlbThd in the CellMLB MO must be greater than DlPrbThd in the
CellShutdown MO. In addition, InterFreqMlbThd in the CellMLB MO must be greater than
UlPrbThd in the CellShutdown MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

LST CELLSHUTDOWN Use this command to list the configuration of intelligent power-off of carriers in
the same coverage.

MOD Use this command to modify the configuration of intelligent power-off of


CELLSHUTDOWN
carriers in the same coverage. This feature applies to scenarios where the local
cell has inter-frequency neighboring cells under the same eNodeB. If the local
cell and its intra-eNodeB inter-frequency neighboring cells are all lightly loaded
and the PRB usage of the local cell meets the conditions for intelligent power-
off of carriers in the same coverage, the local cell enters intelligent power-off of
carriers in the same coverage mode after all UEs are diverted to these inter-
frequency neighboring cells. Then, if the intra-eNodeB inter-frequency
neighboring cells become heavily loaded, the local cell automatically exits
intelligent power-off of carriers in the same coverage mode. With this feature,
the power consumption is reduced.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Intelligent power-off of Indicates whether to enable or disable intelligent power-off of carriers in the
carriers switch
same coverage. Intelligent power-off of carriers in the same coverage can be
performed only when this parameter is set to ON and specific conditions are
met. For intelligent power-off of carriers in the same coverage, each basic cell
must have its intelligent power-off of carriers switch enabled and the UL or DL
PRB usage threshold set to 0.

Start time Indicates the start time of intelligent power-off of carriers in the same coverage.

Stop time Indicates the stop time of intelligent power-off of carriers in the same coverage.
If the stop time is earlier than or the same as the start time, the stop time is
assumed to be a time of the next day.

Downlink PRB Indicates the downlink PRB threshold for starting intelligent power-off of
threshold
carriers in the same coverage for the cell.
Table 2 Related parameters

Parameter Description

Downlink PRB offset Indicates the downlink PRB offset for stopping intelligent power-off of carriers
in the same coverage for the cell. The downlink PRB threshold for stopping
intelligent power-off of carriers in the same coverage for the cell is equal to the
sum of the downlink PRB threshold for starting intelligent power-off of carriers
in the same coverage and the value of this parameter.

Uplink PRB threshold Indicates the uplink PRB threshold for starting intelligent power-off of carriers
in the same coverage for the cell.

Uplink PRB offset Indicates the uplink PRB offset for stopping intelligent power-off of carriers in
the same coverage for the cell. The uplink PRB threshold for stopping intelligent
power-off of carriers in the same coverage for the cell is equal to the sum of the
uplink PRB threshold for starting intelligent power-off of carriers in the same
coverage and the value of this parameter.

5.7.1.6.3.55 CellSiMap
+-NE
+-eNodeBFunction
+-Cell
+-CellSiMap

Description

The CellSiMap MO consists of the parameters related to the mapping between the system
message (SIB) and SI algorithm. It ensures the coverage of system broadcast and provides
configurable interfaces of system broadcast parameters.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands


Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST CELLSIMAP Use this command to list the parameters about SIB-to-SI mapping.

MOD CELLSIMAP Use this command to modify the SIB-to-SI mapping.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

SIB mapping SI Indicates whether the mapping from SIBs to SI messages is enabled. If it is
algorithm switch
disabled, a fixed configuration is used for the mapping from SIBs to SI
messages and the SI window size. If it is enabled, the mapping from SIBs to SI
messages and the SI window size are determined based on the transmission
period, quantity, and data traffic of SIBs.

SIB2 period Indicates the transmission period for system information block type 2 (SIB2).
For details, see 3GPP TS 36.331.

SIB3 period Indicates the transmission period for system information block type 3 (SIB3).
For details, see 3GPP TS 36.331.

SIB4 period Indicates the transmission period for system information block type 4 (SIB4).
For details, see 3GPP TS 36.331.

SIB5 period Indicates the transmission period for system information block type 5 (SIB5).
For details, see 3GPP TS 36.331.

SIB6 period Indicates the transmission period for system information block type 6 (SIB6).
For details, see 3GPP TS 36.331.

SIB7 period Indicates the transmission period for system information block type 7 (SIB7).
For details, see 3GPP TS 36.331.

SIB8 period Indicates the transmission period for system information block type 8 (SIB8).
Table 2 Related parameters

Parameter Description

For details, see 3GPP TS 36.331.

SIB10 period Indicates the transmission period for system information block type 10 (SIB10).
For details, see 3GPP TS 36.331.

SIB11 period Indicates the transmission period for system information block type 11 (SIB11).
For details, see 3GPP TS 36.331.

ETWS PN message Indicates the duration of the primary notification (PN) broadcast for the
duration time
Earthquake and Tsunami Warning System (ETWS).

ETWS SN message Indicates the policy of processing repeated secondary notification (SN)
overlap policy
broadcast for the Earthquake and Tsunami Warning System (ETWS). A repeated
SN is a second SN that has the same IEs Message Identifier and Serial Number
as those in the first SN. The value MERGE indicates that the cell stops
broadcasting the first SN and then broadcasts the second SN. The value
DISCARD indicates that the cell ignores the second SN and continues
broadcasting the first SN.

ETWS PN message Indicates the policy of processing repeated primary notification (PN) broadcast
overlap policy
for the Earthquake and Tsunami Warning System (ETWS). A repeated PN is a
second PN that has the same Message Identifier and Serial Number IEs as those
in the first PN. If this parameter is set to MERGE, the eNodeB stops
broadcasting the first PN and starts broadcasting the second PN. If this
parameter is set to DISCARD, the eNodeB discards the second PN and
continues broadcasting the first PN.

SIB12 period Indicates the transmission period for system information block type 12 (SIB12).
For details, see 3GPP TS 36.331.

Effective code rate for Indicates the code rate of system information transmission. For details about this
SI transmission
parameter, see 3GPP TS 36.331.

5.7.1.6.3.56 CellSimuLoad
+-NE
+-eNodeBFunction
+-Cell
+-CellSimuLoad
Description

The CellSimuLoad MO consists of the parameters related to simulated load configuration of a


cell. When there are few UEs accessing the cell or the number of UEs that can access the cell is
limited, the load simulation is started to test the DL scheduling. During the test, parameters such
as the RB usage and power utilization are monitored to evaluation the effect of DL scheduling.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the CellAlgoSwitch MO:


- If BfAlgoSwitch in the CellAlgoSwitch MO is set to Off, SimuLoadTransMode in the
CellSimuLoad MO cannot be set to TM7 or TM8.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD CELLSIMULOAD Use this command to start a cell simulated load control configuration.

DSP CELLSIMULOAD Use this command to query a cell load simulation configuration.

LST CELLSIMULOAD Use this command to list the parameters about simulated load control for a cell.

MOD CELLSIMULOAD Use this command to modify a cell simulated load control configuration.

RMV CELLSIMULOAD Use this command to remove the cell simulated load configuration.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Configure Index Indicates the index of a simulated load configuration. One eNodeB can store a
maximum of 10 simulated load configurations identified by the indexes ranging
from 0 to 9, which corresponds to the RB usage thresholds (specified by the
SimuLoadRbThd parameter) 10% to 100%, respectively. That is, the RB usage
threshold of the simulated load configuration identified by the index 1 is 20%,
and that of the simulated load configuration identified by the index 4 is 50%,
and so on. The RB usage threshold for a simulated load configuration can be
manually specified by setting the SimuLoadRbThd parameter.

SimuLoad transmission Indicates the transmission mode adopted by the simulated load configuration for
mode
beamforming in TDD cells, including:
TM1: indicates transmission mode 1 for the simulated load configuration.
TM2: indicates transmission mode 2 for the simulated load configuration.
TM7: indicates transmission mode 7 for the simulated load configuration.
TM8: indicates transmission mode 8 for the simulated load configuration.

SimuLoad allocated RB Indicates the number of RBs allocated to a simulated load configuration in
Number
downlink scheduling.

Commercial service RB Indicates the number of RBs allocated for commercial services in downlink
number
scheduling.

SimuLoad allocated Indicates the power allocated to a simulated load configuration in downlink
power
scheduling.

Commercial service Indicates the power allocated for commercial services in downlink scheduling.
power

SimuLoad allocated Indicates the number of UEs allocated by a simulated load configuration in
user Number
downlink scheduling.

Commercial service Indicates the number of users to be scheduled in each transmission time interval
user number
(TTI) in downlink scheduling.

5.7.1.6.3.57 CellStandardQci
+-NE
+-eNodeBFunction
+-Cell
+-CellStandardQci

Description

A CellStandardQci MO consists of parameters related to a standardized QoS Class Identifier


(QCI) for a cell. This MO associates the cell-specific standardized QCI with DRX, SRI and
handover parameters.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the InterFreqHoGroup MO:


- InterFreqHoGroupId in a CellStandardQci MO must have been set in the associated
InterFreqHoGroup MO.
Relation with the InterRatHoCdma1xRttGroup MO:
- InterRatHoCdma1xRttGroupId in a CellStandardQci MO must have been set in the
associated InterRatHoCdma1xRttGroup MO.
Relation with the InterRatHoCdmaHrpdGroup MO:
- InterRatHoCdmaHrpdGroupId in a CellStandardQci MO must have been set in the
associated InterRatHoCdmaHrpdGroup MO.
Relation with the InterRatHoUtranGroup MO:
- InterRatHoUtranGroupId in a CellStandardQci MO must have been set in the associated
InterRatHoUtranGroup MO.
Relation with the DrxParaGroup MO:
- DrxParaGroupId in a CellStandardQci MO must have been set in the associated
DrxParaGroup MO.
Relation with the InterRatHoCommGroup MO:
- InterRatHoCommGroupId in a CellStandardQci MO must have been set in the associated
InterRatHoCommGroup MO.
Relation with the InterRatHoGeranGroup MO:
- InterRatHoGeranGroupId in a CellStandardQci MO must have been set in the associated
InterRatHoGeranGroup MO.
Relation with the IntraFreqHoGroup MO:
- IntraFreqHoGroupId in a CellStandardQci MO must have been set in the associated
IntraFreqHoGroup MO.
Relation with the RlfTimerConstGroup MO:
- When RlfTimerConstCfgInd is set to CFG, RlfTimerConstGroupId in a
CellStandardQci MO must have been set in the associated RlfTimerConstGroup MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the settings of a standardized QCI for a cell.
CELLSTANDARDQCI

MOD Use this command to modify the settings of a standardized QCI for a cell.
CELLSTANDARDQCI

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

QoS Class Indication Indicates the QoS class identifier (QCI) of an evolved packet system (EPS)
bearer. Different QCIs indicate different QoS requirements, such as the packet
delay budget, packet error loss rate, and resource type. For details, see Table
6.1.7 in 3GPP TS 23.203.

Interfreq handover Indicates the ID of a parameter group related to inter-frequency handovers.


group ID

InterRAT handover to Indicates the ID of a parameter group related to inter-RAT handover to


CDMA20001xRTT
group ID CDMA2000 1xRTT.

InterRAT handover to Indicates the ID of a parameter group related to inter-RAT handover to


CDMA2000HRPD
group ID CDMA2000 HRPD.

InterRAT handover Indicates the ID of a common parameter group related to inter-RAT handover.
common group ID
Table 2 Related parameters

Parameter Description

InterRAT handover to Indicates the ID of a parameter group related to inter-RAT handover to GERAN.
GERAN group ID

InterRAT handover to Indicates the ID of a parameter group related to inter-RAT handover to UTRAN.
UTRAN Group ID

Intrafreq handover Indicates the ID of a parameter group related to intra-frequency handover.


group ID

DRX parameter group Indicates the ID of a DRX parameter group.


ID

SRI Period Indicates the interval at which scheduling request indicators are sent.

RLF timer and Indicates the RLF timer and constants indication.
constants indication

RLF timer and Indicates the RLF timer and constants group ID.
constants group ID

Traffic Release Delay Indicates the waiting duration for the eNodeB to release services with a specific
QCI after the eNodeB detects that the radio link is abnormal. When the eNodeB
detects that the radio link is abnormal, the eNodeB waits for the UE to initiate an
RRC connection reestablishment procedure to restore services. If the waiting
duration times out, the eNodeB releases the services.

5.7.1.6.3.58 CellUlCompAlgo
+-NE
+-eNodeBFunction
+-Cell
+-CellUlCompAlgo

Description

The CellUlCompAlgo MO defines the offset for UL CoMP event A3. This parameter is delivered
with the RRC Connection Reconfiguration message. For details, see 3GPP TS 36.331.

Effective Scenario

Immediately

Relations Between MOs


Possible parents:
Cell

Relation with the Cell MO:


- LocalCellId in an CellUlCompAlgo MO must have been set in the associated Cell MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the uplink coordinated multi-point (CoMP) algorithm.
CELLULCOMPALGO

MOD Use this command to modify the uplink coordinated multi-point (CoMP)
CELLULCOMPALGO
algorithm.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

LocalCellId Indicates the local identity of the cell. It uniquely identifies a cell within an
eNodeB.

UlCompA3Offset Indicates the offset for UL CoMP event A3. This offset is the difference between
the quality of a neighboring cell and that of the serving cell. A larger value
indicates that a neighboring cell must have better quality for the reporting of the
event. For details, see 3GPP TS 36.331.

5.7.1.6.3.59 CellUlIcic
+-NE
+-eNodeBFunction
+-Cell
+-CellUlIcic

Description

The CellUlIcic MO consists of the parameters related to UL ICIC. It is used to set the band
division scheme adopted by UL ICIC in the cell.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST CELLULICIC Use this command to list the configuration of the cell UL ICIC algorithm.

MOD CELLULICIC Use this command to modify the configuration of the cell UL ICIC algorithm.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Uplink band division Indicates the band division scheme used in uplink ICIC. The band division in the
scheme
cell is changed according to the setting of this parameter so that the edge bands
do not overlap between neighboring cells. If this parameter is set to INVALID,
the cell does not distinguish center and edge bands.
5.7.1.6.3.60 CellULIcicMcPara
+-NE
+-eNodeBFunction
+-Cell
+-CellULIcicMcPara

Description

The CellULIcicMcPara MO consists of the parameters related to intra-RAT measurement for


inter-cell interference coordination (ICIC) in UL of the cell. As a UE moves, the signal qualities
of both the serving cell and the neighboring cell changes. This will trigger a UL ICIC
measurement event or stop the event, based on which the UE location can be updated timely.
These parameters are contained in the RRCConnectionReconfiguration message. For details, see
3GPP TS 36.331.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the measurement control parameters for UL ICIC.
CELLULICICMCPARA

MOD Use this command to modify the measurement control parameters related to UL
CELLULICICMCPARA
ICIC.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Uplink ICIC Indicates the interval between periodic measurement reports that are sent after a
measurement report
interval UL ICIC measurement event is triggered. For details, see 3GPP TS 36.331.
In this version, this parameter still supports setting synchronization between the
M2000 and the eNodeB, but is no longer used internally. Avoid using this
parameter as it will be removed from later versions.

Uplink ICIC Indicates the maximum number of cells to be included in each measurement
measurement max
report cell number report after a UL ICIC measurement event is triggered. For details, see 3GPP TS
36.331.
In this version, this parameter still supports setting synchronization between the
M2000 and the eNodeB, but is no longer used internally. Avoid using this
parameter as it will be removed from later versions.

Uplink ICIC Indicates the number of periodic measurement reports after a UL ICIC
measurement report
amount measurement event is triggered. For details, see 3GPP TS 36.331.
In this version, this parameter still supports setting synchronization between the
M2000 and the eNodeB, but is no longer used internally. Avoid using this
parameter as it will be removed from later versions.

Uplink ICIC Indicates the quantity to be included in the measurement report after a UL ICIC
measurement report
quantity measurement event is triggered, which can be set to SAME_AS_TRIG_QUAN
or BOTH.
The value SAME_AS_TRIG_QUAN indicates that the quantity to be included is
the same as that specified by the TriggerQuantity parameter. The value BOTH
indicates that both RSRP and RSRQ values are included.
The measured RSRP values are stable, varying little with the load, and therefore
there is little signal fluctuation. The measured RSRQ values vary with the load
and are likely to reflect the signal quality of the cell in real time. For details, see
3GPP TS 36.331.
In this version, this parameter still supports setting synchronization between the
M2000 and the eNodeB, but is no longer used internally. Avoid using this
parameter as it will be removed from later versions.

Uplink ICIC Indicates the quantity used in the evaluation of a UL ICIC measurement event.
measurement trigger
quantity The quantity can be RSRP or RSRQ. The measured RSRP values are stable,
varying little with the load, and therefore there is little signal fluctuation. The
measured RSRQ values vary with the load and are likely to reflect the signal
quality of the cell in real time.
In this version, this parameter still supports setting synchronization between the
M2000 and the eNodeB, but is no longer used internally. Avoid using this
parameter as it will be removed from later versions.
Table 2 Related parameters

Parameter Description

Uplink ICIC Indicates the hysteresis for the UL ICIC measurement event. This parameter is
measurement
hysteresis used to decrease frequent triggering of event evaluations due to radio signal
fluctuations. For details, see 3GPP TS 36.331.
In this version, this parameter still supports setting synchronization between the
M2000 and the eNodeB, but is no longer used internally. Avoid using this
parameter as it will be removed from later versions.

Uplink ICIC Indicates the time-to-trigger for the UL ICIC measurement event. When
measurement time to
trigger detecting that the signal quality in the serving cell and that in at least one
neighboring cell meet the entering condition, the UE does not send a
measurement report to the eNodeB immediately. Instead, the UE sends a report
only when the signal quality continuously meets the entering condition during
the time-to-trigger.
In this version, this parameter still supports setting synchronization between the
M2000 and the eNodeB, but is no longer used internally. Avoid using this
parameter as it will be removed from later versions.

Uplink ICIC A3 offset Indicates the offset for the UL ICIC measurement event. If this parameter is set
to a large value, the signal quality of the neighboring cell must be significantly
better than that of the serving cell before a UL ICIC measurement event is
triggered. For details, see 3GPP TS 36.331.

5.7.1.6.3.61 CellUlpcComm
+-NE
+-eNodeBFunction
+-Cell
+-CellUlpcComm

Description

The CellUlpcComm MO consists of the parameters related to UL power control over common
radio resources in the cell, such as the target UE transmit power for the PUCCH expected by the
eNodeB on condition that normal demodulation can be performed.
For details about UL power control, see 3GPP TS 36.213.

Effective Scenario
Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST CELLULPCCOMM Use this command to list the parameters about uplink power control for a cell.

MOD Use this command to modify the configuration of uplink power control for a
CELLULPCCOMM
cell.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Path loss coefficient Indicates the compensation factor for path loss. It is used in UL power control.
For details, see 3GPP TS 36.213.

P0 nominal PUCCH Indicates the target UE transmit power for the PUCCH expected by the eNodeB
on condition that normal demodulation can be performed. For details, see 3GPP
TS 36.213.

P0 nominal PUSCH Indicates the nominal P0 value of the PUSCH. It is used in UL power control.
For details, see 3GPP TS 36.213.

DeltaF for PUCCH Indicates the Delta value corresponding to PUCCH format 1. For details, see
format 1
3GPP TS 36.213.

DeltaF for PUCCH Indicates the Delta value corresponding to PUCCH format 1b. For details, see
format 1b
Table 2 Related parameters

Parameter Description

3GPP TS 36.213.

DeltaF for PUCCH Indicates the Delta value corresponding to PUCCH format 2. For details, see
format 2
3GPP TS 36.213.

DeltaF for PUCCH Indicates the Delta value corresponding to PUCCH format 2a. For details, see
format 2a
3GPP TS 36.213.

DeltaF for PUCCH Indicates the Delta value corresponding to PUCCH format 2b. For details, see
format 2b
3GPP TS 36.213.

Delta preamble value Indicates the power offset (delta value) of message 3 relative to the preamble.
for msg3
This power offset has a step size of 2. For details, see 3GPP TS 36.213.

5.7.1.6.3.62 CellUlpcDedic
+-NE
+-eNodeBFunction
+-Cell
+-CellUlpcDedic

Description

The CELLULPCDEDIC MO contains the parameters related to power control for the Physical
Uplink Shared Channel (PUSCH). This MO has the following functions:
1. Contains the setting of DeltaMcsEnabled, which determines whether TF is equal to 0 or is
calculated on the condition that Ks is equal to 1.25.
2. Specifies whether accumulation is applied to power control for the PUSCH.
3. Contains the power offset of the sounding reference signal to the PUSCH and the filtering
coefficient for RSRP.

Effective Scenario

Immediately

Relations Between MOs


Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST CELLULPCDEDIC Use this command to list the dedicated RRC parameters related to power control
for the PUSCH.

MOD Use this command to modify the dedicated RRC parameters related to power
CELLULPCDEDIC
control for the PUSCH.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Delta-MCS enable or Indicates whether a UE needs to adjust the transmit power based on the MCS.
disable indication
The indication is sent to the UE through an RRC message. The indication is
denoted by a bit. Bit 0 indicates that both Ks and TF are equal to 0. Bit 1
indicates that Ks is equal to 1.25 and TF is calculated. For details, see 3GPP
TS 36.213.

Power Offset of SRS Indicates the power offset of the sounding reference signal to the PUSCH when
When
DeltaMcsEnabled Off DeltaMcsEnabled is set to UU_DISABLE.

Power Offset of SRS Indicates the power offset of the sounding reference signal to the PUSCH when
When
DeltaMcsEnabled On DeltaMcsEnabled is set to UU_ENABLE.

RSRP filtering Indicates the alpha filtering coefficient used by the UE during RSRP
coefficient
measurement for path loss estimation.
5.7.1.6.3.63 CellUlschAlgo
+-NE
+-eNodeBFunction
+-Cell
+-CellUlschAlgo

Description

The CellUlschAlgo MO consists of the parameters related to the UL scheduling algorithm for the
cell. The parameters specify the scheduling policy and functions used in UL scheduling.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the PUSCHCfg,Cell MOs:


- Let A be the number of RB resources corresponding to the value of UlBandWidth in a Cell
MO, B the even number that HoppingOffset in the PUSCHCfg MO is rounded up to, and C the
difference between A and B. If UlHoppingType in the CellUlschAlgo MO is set to
HOPPING_TYPE1, C must be greater than A modulo 2. If UlHoppingType in the
CellUlschAlgo MO is set to HOPPING_TYPE2 or HOPPING_TYPE2_RANDOM, and Nsb in
the PUSCHCfg MO is greater than 1, the integer value of C divide Nsb in the PUSCHCfg MO
must be greater than 0.
- If UlBandWidth is set to CELL_BW_N6(1.4M), the number of RB resources is 6.
- If UlBandWidth is set to CELL_BW_N15(3M), the number of RB resources is 15.
- If UlBandWidth is set to CELL_BW_N25(5M), the number of RB resources is 25.
- If UlBandWidth is set to CELL_BW_N50(10M), the number of RB resources is 50.
- If UlBandWidth is set to CELL_BW_N75(15M), the number of RB resources is 75.
- If UlBandWidth is set to CELL_BW_N100(20M), the number of RB resources is 100.
Relation with the PUSCHCfg MO:
- If HoppingMode in the PUSCHCfg MO is set to INTRA_AND_INTER_SUB_FRAME
and UlHoppingType in the CellUlschAlgo MO is set to HOPPING_TYPE2, Nsb in the
PUSCHCfg MO must be set to 1.
- If HoppingMode in the PUSCHCfg MO is set to INTER_SUB_FRAME and
UlHoppingType in the CellUlschAlgo MO is set to HOPPING_TYPE2_RANDOM, Nsb in the
PUSCHCfg MO cannot be set to 1.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the configuration of the cell UL scheduling algorithm.
CELLULSCHALGO

MOD Use this command to modify the configuration of the cell UL scheduling
CELLULSCHALGO
algorithm.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Uplink Scheduling Indicates the UL scheduling policy, which determines the scheduling priority
Strategy
order in which UEs are arranged in UL. There are four UL scheduling strategies:
MAX C/I, proportional fair (PF), round Robin (RR), and enhanced proportional
fair (EPF). The MAX C/I policy schedules UEs in descending order of average
signal to interference plus noise ratio (SINR). The PF policy schedules UEs in
ascending order of ratio of the data rate to the SINR. The RR policy schedules
each UE in sequence, and therefore each UE has an equal opportunity to be
scheduled. The EPF policy schedules UEs in ascending order of priority. In EPF,
the priority of an UE is calculated based on the following factors: the data rate,
average SINR, QoS-satisfying data rate for each service, and service
differentiation requirements of the UE. The MAX C/I, PF, and RR policies are
basic UL scheduling policies and supported by the eNodeB by default, whereas
the EPF policy is intended for commercial use.

adaptive HARQ switch Indicates the switch that is used to control whether to enable or disable UL
adaptive HARQ. If this switch is set to ADAPTIVE_HARQ_SW_OFF, UL data
is retransmitted by non-adaptive synchronous HARQ. If this switch is set to
ADAPTIVE_HARQ_SW_ON, UL data is retransmitted by adaptive
Table 2 Related parameters

Parameter Description

synchronous HARQ. If this switch is set to ADAPTIVE_HARQ_SW_SEMION,


adaptive HARQ is triggered when a UL grant is delivered to an HARQ process
that is previously suspended due to reasons such as resource collision, activation
of a measurement gap, and PDCCH congestion. Setting this parameter to
ADAPTIVE_HARQ_SW_ON helps reduce resource consumption due to
retransmission, increase the cell throughput, and prevent retransmission
conflicts. This, on the other hand, will increase signaling overhead and therefore
consume more PDCCH resources.

SINR target IBLER Indicates the target IBLER of the SINR adjustment algorithm. A greater
adjustment
parameter value indicates a greater SINR adjustment value, and thus a higher-
level MCS is used.

System Bandwidth Indicates the ratio of the maximum bandwidth resources that the uplink
Ratio Used By Pre-
schedule user per TTI scheduler can allocate to preallocation UEs to the total system bandwidth.

minimal period of pre- Indicates the minimum interval between two pre-allocations. That is, the actual
allocation
interval between two pre-allocations of one UE must be longer than or equal to
the value of this parameter.

data size of pre- Indicates the data amount pre-allocated to each user.
allocation

Uplink hopping type Indicates whether frequency hopping (FH) is enabled or disabled and which FH
type is used.
Hopping_OFF: indicates that FH is disabled.
Hopping_Type1: indicates that adaptive FH is enabled and FH type 1 is used. In
this scenario, UEs in the cell can determine whether to use FH based on the
actual situation.
Hopping_Type2: indicates that adaptive FH is enabled and FH type 2 is used. In
this scenario, UEs in the cell can determine whether to use FH based on the
actual situation.
Hopping_Type2_RANDOM: indicates that random FH is enabled and FH type 2
is used. In this scenario, all UEs in the cell use FH.

Free Users Uplink RB Indicates the percentage of free shared RBs on the PUSCH in scheduling based
Ratio
on free users and subscribers. The other RBs on the PUSCH are allocated to
subscribers. When sufficient capacity is available, the percentage of RBs
occupied by free users and that occupied by subscribers will reach the preset
values. Changes in this parameter affect the percentage of RBs for free users and
that for subscribers. The value of this parameter cannot be changed when the
cell is active.

UL scheduling request Indicates the data length that the UL scheduler assigns to UEs that have sent
Table 2 Related parameters

Parameter Description

user data length scheduling requests. Within the data length, the UEs reports their buffer status
and transmit certain data.

Semi-persistent Indicates the threshold for the number of consecutive zero-payload packets
resource implicit
release threshold received by the eNodeB. After receiving consecutive zero-payload packets of a
number that is equal to the value of this parameter, the eNodeB performs
implicit release of semi-persistent resources.

Smart pre-allocation Indicates the duration of uplink smart preallocation triggered by downlink
duration
scheduling. If SmartPreAllocationSwitch is set to On and this parameter is set to
0, neither smart preallocation nor preallocation takes effect. If
SmartPreAllocationSwitch is set to Off, this parameter is invalid.

Uplink EPF capacity Indicates the capacity factor for uplink enhanced proportional fair (EPF)
factor
scheduling. When the eNodeB schedules UEs with unsatisfied GBR, this factor
affects the scheduling priorities of UEs running services with the QCI of 1, 2, 3,
or 4. When the eNodeB schedules UEs running Non-GBR services, this factor
affects the scheduling priorities of UEs running services with the QCI of 6, 7, 8,
or 9. In this way, this factor can be used to adjust the cell capacity and fairness
among UEs.

Uplink Resource Block Indicates the strategy for allocating resource blocks (RBs) in the uplink of the
Allocation Strategy
cell. If this parameter is set to FS_NONFS_ADAPTIVE, this strategy adaptively
switches between frequency selective scheduling and non-frequency selective
scheduling. If this parameter is set to FS_INRANDOM_ADAPTIVE, this
strategy adaptively switches between frequency selective scheduling and
interference-randomization-based scheduling.

5.7.1.6.3.64 CnOperator
+-NE
+-eNodeBFunction
+-CnOperator
+-ServiceIrHoCfgGroup[1~10]
+-CnOperatorHoCfg[1~1]
+-CSFallBackBlindHoCfg[1~1]
+-CnOperatorSpidCfg[0~256]
+-CnOperatorExtendedQci[0~60]
+-ServiceIfHoCfgGroup[1~10]
+-InterPlmnHoList[0~8]
+-CnOperatorStandardQci[9~9]
+-eNBCnOpQciRsvdPara[9~9]
+-LicenseSharingPolicy[0~1]
+-eNBCnOpRsvdPara[1~1]
+-LicRatioSharePolicy[1~1]
+-Emc[1~1]

Description

A CnOperator MO consists of the ID, name, type, mobile country code (MCC), and mobile
network code (MNC) of an operator. The MCC and MNC constitute a public land mobile
network (PLMN) ID, which uniquely identifies the operator.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Possible children:
ServiceIrHoCfgGroup[1~10];CnOperatorHoCfg[1~1];CSFallBackBlindHoCfg[1~1];CnOperatorSpidCfg[0~256];
CnOperatorExtendedQci[0~60];ServiceIfHoCfgGroup[1~10];InterPlmnHoList[0~8];CnOperatorStandardQci[9~
9];eNBCnOpQciRsvdPara[9~9];LicenseSharingPolicy[0~1];eNBCnOpRsvdPara[1~1];LicRatioSharePolicy[1~1
];Emc[1~1]
Relation with the InterPlmnHoList MO:
- CnOperatorId in an InterPlmnHoList MO must have been set in the associated
CnOperator MO.
- If TarMcc in an InterPlmnHoList MO is the same as Mcc in the CnOperator MO
corresponding to CnOperatorId in the InterPlmnHoList MO, TarMnc in the
InterPlmnHoList MO must be different from Mnc in the CnOperator MO.
Relation with the CnOperatorTa MO:
- CnOperatorId in a CnOperatorTa MO must have been set in the associated CnOperator
MO.
Relation with the S1Interface MO:
- CnOperatorId in an S1Interface MO must have been set in the associated CnOperator
MO.
Relation with the X2Interface MO:
- CnOperatorId in an X2Interface MO must have been set in the associated CnOperator
MO.
Relation with the ENodeBSharingMode MO:
- If ENodeBSharingMode in the ENodeBSharingMode MO is set to SEPARATED_FREQ
and eNodeBId in an EutranExternalCell MO is the same as ENODEBID in the eNodeB MO,
the combination of Mcc and Mnc in the EutranExternalCell MO must be different from the
combination of Mcc and Mnc in any CnOperator MO.
- If ENodeBSharingMode in the ENodeBSharingMode MO is set to INDEPENDENT, a
maximum of one CnOperator MO can be configured.
Relation with the CnOperatorStandardQci MO:
- If a CnOperator MO is configured, the number of CnOperatorStandardQci MOs that
reference CnOperatorId in the CnOperator MO must be 9.
Relation with the CSFallBackBlindHoCfg MO:
- If a CnOperator MO is configured, the CSFallBackBlindHoCfg MO that references
CnOperatorId in the CnOperator MO must exist.
Relation with the Emc MO:
- If a CnOperator MO is configured, the Emc MO that references CnOperatorId in the
CnOperator MO must exist.
Relation with the eNBCnOpRsvdPara MO:
- If a CnOperator MO is configured, the eNBCnOpRsvdPara MO that references
CnOperatorId in the CnOperator MO must exist.
Relation with the eNBCnOpQciRsvdPara MO:
- If a CnOperator MO is configured, the number of eNBCnOpQciRsvdPara MOs that
reference CnOperatorId in the CnOperator MO must be 9.
Relation with the CnOperatorHoCfg MO:
- CnOperatorId in an CnOperatorHoCfg MO must have been set in the associated
CnOperator MO.
Relation with the CnOperatorSpidCfg MO:
- CnOperatorId in an CnOperatorSpidCfg MO must have been set in the associated
CnOperator MO.
Relation with the EutranNFreqSCellOp MO:
- CnOperatorID in a EutranNFreqSCellOp MO must have been set in the associated
CnOperator MO.
Relation with the UtranNFreqSCellOp MO:
- CnOperatorID in a UtranNFreqSCellOp MO must have been set in the associated
CnOperator MO.
Relation with the GeranNFGroupSCellOp MO:
- CnOperatorID in a GeranNFGroupSCellOp MO must have been set in the associated
CnOperator MO.
Relation with the Cdma2000BcSCellOp MO:
- CnOperatorID in a Cdma2000BcSCellOp MO must have been set in the associated
CnOperator MO.
Relation with the EutranExternalCell,eNodeBFunction,ENodeBSharingMode MOs:
- If eNodeBId in an EutranExternalCell MO is the same as that in the eNodeBFunction MO
and the ENodeBSharingMode parameter in the ENodeBSharingMode MO is set to
SEPARATED_FREQ, the combination of Mcc and Mnc in an EutranExternalCell MO must be
different from that in any CnOperator MO. If the ENodeBSharingMode parameter in the
ENodeBSharingMode MO is set to INDEPENDENT or SHARED_FREQ, the combination of
Mcc and Mnc in the EutranExternalCell MO must be different from that in the CnOperator
MO that represents the primary operator.
Relation with the CnOperator MO:
- A CnOperator MO cannot modify Mcc or Mnc when cell cononfig as each intra-eNodeB
intra-frequency neighboring cell.
- A CnOperator MO cannot modify mcc or mnc when cell cononfig as each intra-eNodeB
intra-frequency neighboring cell.
- Among CnOperator MOs, a primary operator must be configured before a secondary
operator can be configured.
- If ENodeBSharingMode in the ENodeBSharingMode MO is set to SHARED_FREQ,
CnOperator MO configured with Cell can not be all CNOPERATOR_SECONDARY.
- CnOperatorId in an CnOperatorIpPath MO must have been set in the associated
CnOperator MO.
- CnOperatorId in an S1 MO must have been configured in the associated CnOperator MO.
- CnOperatorId in an X2 MO must have been configured in the associated CnOperator MO.
Relation with the EutranInterFreqNCell,CellOp,CnOperatorTa MOs:
- A CellOp MO must be configured for each EutranInterFreqNCell MO that corresponds to
an intra-eNodeB inter-frequency neighboring cell. If the ENodeBSharingMode parameter in the
ENodeBSharingMode MO is set to SHARED_FREQ, Mcc and Mnc in such an
EutranInterFreqNCell MO must be the same as the Mcc and Mnc specified in the
CnOperator MO representing the primary operator. If ENodeBSharingMode is set to
INDEPENDENT or SEPARATED_FREQ, Mcc and Mnc in such an EutranInterFreqNCell
MO must be set to the same values as Mcc and Mnc specified in the CnOperator MO
corresponding to the CellOp MO associated with this EutranInterFreqNCell MO.
Relation with the EutranInterFreqNCell,EutranExternalCell,eNodeBFunction MOs:
- Before adding an inter-eNodeB inter-frequency neighboring cell, ensure that the associated
EutranExternalCell MO has been configured.
Relation with the EutranIntraFreqNCell,CellOp,CnOperatorTa MOs:
- A CellOp MO must be configured for each EutranIntraFreqNCell MO that corresponds to
an intra-eNodeB intra-frequency neighboring cell. If the ENodeBSharingMode parameter in the
ENodeBSharingMode MO is set to SHARED_FREQ, Mcc and Mnc in such an
EutranIntraFreqNCell MO must be the same as the Mcc and Mnc specified in the
CnOperator MO representing the primary operator. If ENodeBSharingMode is set to
INDEPENDENT or SEPARATED_FREQ, Mcc and Mnc in such an EutranIntraFreqNCell
MO must be set to the same values as Mcc and Mnc specified in the CnOperator MO
corresponding to the CellOp MO associated with this EutranIntraFreqNCell MO.
Relation with the EutranIntraFreqNCell,EutranExternalCell,eNodeBFunction MOs:
- Before adding an inter-eNodeB intra-frequency neighboring cell, ensure that the associated
EutranExternalCell MO has been configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD CNOPERATOR Use this command to add an operator. After this command is executed, a license
sharing policy and the ratio of traffic that each operator can use to the total
licensed traffic of the eNodeB must be specified except in the following cases:
1)The ENodeBSharingMode parameter is set to INDEPENDENT(Independent
Operator Mode).
2)No license sharing policy or traffic ratio is configured for any operator.
A maximum of six operators can be added for an eNodeB. When the eNodeB is
configured to work in RAN sharing with common carriers mode or RAN sharing
with dedicated carriers mode but does not have the required RAN sharing
license, the configuration of a secondary operator does not take effect. If the
license control item RAN Sharing by More Operators is disabled, the
configurations of a maximum of four operators take effect. The other two
operators whose configurations do not take effect cannot provide services.
The order in which the configurations take effect is as follows: The
configuration of the primary operator takes effect first. The configurations of
secondary operators take effect in the same order as the secondary operators are
added. If the eNodeB is restarted, the configuration of the primary operator takes
effect first and the configurations of secondary operators take effect based on the
operator IDs. The configuration of a secondary operator with a smaller ID takes
effect before that of a secondary operator with a larger ID takes effect. As a
result, the following situation is possible:
Before the eNodeB is restarted, the configurations of secondary operators with
larger IDs 4 and 5 take effect while the configurations of secondary operators
with smaller IDs 0 and 1 do not take effect. However, after the eNodeB is
restarted, the configurations of secondary operators with the smaller IDs 0 and 1
Table 1 Related MML commands

MML Command Function

take effect while the configurations of secondary operators with the larger IDs 4
and 5 do not take effect.
In any case, two operators cannot provide services normally. To solve the
problem, the operators need to purchase the license control item RAN Sharing
by More Operators.

LST CNOPERATOR Use this command to list operator information.

MOD CNOPERATOR Use this command to modify an operator. The combination of the mobile
country code (MCC) and mobile network code (MNC) uniquely identifies an
operator. If the MCC or MNC is changed, the operator ID is changed. After
modification, if the eNodeB is configured to work in RAN sharing with
common carriers mode or RAN sharing with dedicated carriers mode but does
not have the required RAN sharing license, the configuration of a secondary
operator does not take effect. A maximum of six operators can be added for an
eNodeB. If the license control item RAN Sharing by More Operators is disabled,
the configurations of a maximum of four operators take effect. The other two
operators whose configurations do not take effect cannot provide services.
The order in which the configurations take effect is as follows: The
configuration of the primary operator takes effect first. The configurations of
secondary operators take effect in the same order as the secondary operators are
added. If the eNodeB is restarted, the configuration of the primary operator takes
effect first and the configurations of secondary operators take effect based on the
operator IDs. The configuration of a secondary operator with a smaller ID takes
effect before that of a secondary operator with a larger ID takes effect. As a
result, the following situation is possible:
Before the eNodeB is restarted, the configurations of secondary operators with
larger IDs 4 and 5 take effect while the configurations of secondary operators
with smaller IDs 0 and 1 do not take effect. However, after the eNodeB is
restarted, the configurations of secondary operators with the smaller IDs 0 and 1
take effect while the configurations of secondary operators with the larger IDs 4
and 5 do not take effect.
In any case, two operators cannot provide services normally. To solve the
problem, the operators need to purchase the license control item RAN Sharing
by More Operators.

RMV CNOPERATOR Use this command to remove an operator.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

CN Operator ID Indicates the index of the operator.

CN Operator name Indicates the name of the operator. The name is a string of a maximum of 32
characters. The string cannot be all null characters or contain any of the
following characters: double quotation marks ("), commas (,), semicolons (;),
equal signs (=), single quotation marks ('), three consecutive plus signs (+++),
two or more consecutive spaces, and two or more consecutive percent signs (%).

CN Operator type Indicates the type of the operator. The operator can be the primary operator or a
secondary operator. For each eNodeB, only one primary operator but more than
one secondary operator can be configured.

Mobile country code Indicates the mobile country code (MCC) of the operator.

Mobile network code Indicates the mobile network code (MNC) of the operator. The value of this
parameter is a string of two or three characters, each of which must be a digit in
the range from 0 to 9.

5.7.1.6.3.65 CnOperatorExtendedQci
+-NE
+-eNodeBFunction
+-CnOperator
+-CnOperatorExtendedQci

Description

A CnOperatorExtendedQci MO contains an operator-specific extended QoS Class Identifier


(QCI) and a service-based inter-RAT handover policy group.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
CnOperator
Relation with the ServiceIrHoCfgGroup MO:
- ServiceIrHoCfgGroupId in a CnOperatorExtendedQci MO must have been set in the
associated ServiceIrHoCfgGroup MO.
Relation with the ServiceIfHoCfgGroup MO:
- ServiceIfHoCfgGroupId in a CnOperatorExtendedQci MO must have been set in the
associated ServiceIfHoCfgGroup MO.
Relation with the CnOperator MO:
- A maximum of 60 CnOperatorExtendedQci MOs can be configured for each CnOperator
MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add an extended QCI for an operator.


CNOPERATOREXTEN
DEDQCI

LST Use this command to list operator-specific extended QCI settings.


CNOPERATOREXTEN
DEDQCI

MOD Use this command to modify an extended QCI of an operator.


CNOPERATOREXTEN
DEDQCI

RMV Use this command to remove an extended QCI of an operator.


CNOPERATOREXTEN
DEDQCI

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

CN Operator ID Indicates the index of the operator.

CN Operator extended Indicates the extended QoS Class Identifier (QCI), which is required by the
QCI
Table 2 Related parameters

Parameter Description

operator for user differentiation.

Service-based inter- Indicates the ID of the service-based inter-RAT handover policy group.
RAT handover policy
group ID

Service-based inter- Indicates the ID of the service-based inter-frequency handover policy group.
Freq handover policy
group ID

5.7.1.6.3.66 CnOperatorHoCfg
+-NE
+-eNodeBFunction
+-CnOperator
+-CnOperatorHoCfg

Description

The CnOperatorHoCfg MO consists of operator-specific handover parameters, including the


priorities of different RATs and the threshold offsets for different types of event A2.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
CnOperator

Relation with the CnOperator MO:


- CnOperatorId in an CnOperatorHoCfg MO must have been set in the associated
CnOperator MO.
Relation with the InterFreqHoGroup MO:
- The sum of the value of InterFreqHoA2ThdRsrp in the InterFreqHoGroup MO and the
value of TddIfHoA2ThdRsrpOffset in the CnOperatorHoCfg MO cannot be greater than the
value of InterFreqHoA1ThdRsrp in the InterFreqHoGroup MO.
- The sum of the value of InterFreqHoA2ThdRsrp in the InterFreqHoGroup MO and the
value of FddIfHoA2ThdRsrpOffset in the CnOperatorHoCfg MO cannot be greater than the
value of InterFreqHoA1ThdRsrp in the InterFreqHoGroup MO.
- The sum of the value of A3InterFreqHoA2ThdRsrp in the InterFreqHoGroup MO and
the value of TddIfHoA2ThdRsrpOffset in the CnOperatorHoCfg MO cannot be greater than
the value of A3InterFreqHoA1ThdRsrp in the InterFreqHoGroup MO.
- The sum of the value of A3InterFreqHoA2ThdRsrp in the InterFreqHoGroup MO and
the value of FddIfHoA2ThdRsrpOffset in the CnOperatorHoCfg MO cannot be greater than
the value of A3InterFreqHoA1ThdRsrp in the InterFreqHoGroup MO.
Relation with the InterRatHoCommGroup MO:
- The sum of the value of InterRatHoA2ThdRsrp in the InterRatHoCommGroup MO and
the value of UtranA2ThdRsrpOffset in the CnOperatorHoCfg MO cannot be greater than the
value of InterRatHoA1ThdRsrp in the InterRatHoCommGroup MO.
- The sum of the value of InterRatHoA2ThdRsrp in the InterRatHoCommGroup MO and
the value of GeranA2ThdRsrpOffset in the CnOperatorHoCfg MO cannot be greater than the
value of InterRatHoA1ThdRsrp in the InterRatHoCommGroup MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list operator-specific handover configurations.


CNOPERATORHOCFG

MOD Use this command to modify operator-specific handover configurations.


CNOPERATORHOCFG

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

CN Operator ID Indicates the ID of the operator.

First RAT Priority Indicates the priorities of E-UTRAN TDD and E-UTRAN FDD. To prioritize E-
UTRAN TDD and E-UTRAN FDD, set this parameter to EUTRAN_TDD or
Table 2 Related parameters

Parameter Description

EUTRAN_FDD. To treat E-UTRAN TDD and E-UTRAN FDD equally, set this
parameter to EUTRAN.

Second RAT Priority Indicates the priorities of E-UTRAN TDD and E-UTRAN FDD. To prioritize E-
UTRAN TDD and E-UTRAN FDD, set this parameter to EUTRAN_TDD or
EUTRAN_FDD. If FirstRatPri is set to EUTRAN, set SecondRatPri to NULL,
indicating that E-UTRAN TDD and E-UTRAN FDD are not prioritized.

LTE TDD inter-freq A2 Indicates the offset of the RSRP threshold for LTE TDD inter-frequency
Threshold RSRP Offset
measurement event A2 relative to the RSRP threshold for inter-frequency
measurement event A2 (which is specified by InterFreqHoA2ThdRsrp). If
TddIfHoA2ThdRsrpOffset and FddIfHoA2ThdRsrpOffset are set to the same
value (excluding the value -100), LTE TDD measurement and LTE FDD
measurement are not prioritized, and the RSRP threshold delivered by the
eNodeB is the sum of the value of TddIfHoA2ThdRsrpOffset or
FddIfHoA2ThdRsrpOffset and the RSRP threshold for inter-frequency
measurement event A2. If both TddIfHoA2ThdRsrpOffset and
FddIfHoA2ThdRsrpOffset are set to -100, LTE TDD measurement and LTE
FDD measurement are not prioritized, and the RSRP threshold delivered by the
eNodeB is the RSRP threshold for inter-frequency measurement event A2.
If only TddIfHoA2ThdRsrpOffset is set to -100, LTE TDD measurement is not
performed and the RSRP threshold delivered by the eNodeB is the sum of the
value of FddIfHoA2ThdRsrpOffset and the RSRP threshold for inter-frequency
measurement event A2.

LTE FDD inter-freq A2 Indicates the offset of the RSRP threshold for LTE FDD inter-frequency
Threshold RSRP Offset
measurement event A2 relative to the RSRP threshold for inter-frequency
measurement event A2 (which is specified by InterFreqHoA2ThdRsrp). If
TddIfHoA2ThdRsrpOffset and FddIfHoA2ThdRsrpOffset are set to the same
value (excluding the value -100), LTE TDD measurement and LTE FDD
measurement are not prioritized, and the RSRP threshold delivered by the
eNodeB is the sum of the value of TddIfHoA2ThdRsrpOffset or
FddIfHoA2ThdRsrpOffset and the RSRP threshold for inter-frequency
measurement event A2. If both TddIfHoA2ThdRsrpOffset and
FddIfHoA2ThdRsrpOffset are set to -100, LTE TDD measurement and LTE
FDD measurement are not prioritized, and the RSRP threshold delivered by the
eNodeB is the RSRP threshold for inter-frequency measurement event A2.
If only FddIfHoA2ThdRsrpOffset is set to -100, LTE FDD measurement is not
performed and the RSRP threshold delivered by the eNodeB is the sum of the
value of TddIfHoA2ThdRsrpOffset and the RSRP threshold for inter-frequency
measurement event A2.

UTRAN A2 Threshold Indicates the offset of the RSRP threshold for UTRAN inter-RAT handover
RSRP Offset
event A2 relative to the RSRP threshold for inter-RAT handover event A2
Table 2 Related parameters

Parameter Description

(which is specified by InterRatHoA2ThdRsrp). If the value of


UtranA2ThdRsrpOffset and that of GeranA2ThdRsrpOffset are identical
(excluding the value -100), UTRAN measurement and GERAN measurement
are not prioritized, and the RSRP threshold delivered by the eNodeB is the sum
of the value of this parameter and the RSRP threshold for inter-RAT
measurement event A2. If both UtranA2ThdRsrpOffset and
GeranA2ThdRsrpOffset are set to -100, UTRAN measurement and GERAN
measurement are not prioritized, and the RSRP threshold delivered by the
eNodeB is the RSRP threshold for inter-RAT measurement event A2. If only
UtranA2ThdRsrpOffset is set to -100, UTRAN measurement is not performed
and the RSRP threshold delivered by the eNodeB is the sum of the value of
GeranA2ThdRsrpOffset and the RSRP threshold for inter-RAT measurement
event A2.

GERAN A2 Threshold Indicates the offset of the RSRP threshold for GERAN inter-RAT handover
RSRP Offset
event A2 relative to the RSRP threshold for inter-RAT handover event A2
(which is specified by InterRatHoA2ThdRsrp). If the value of
UtranA2ThdRsrpOffset and that of GeranA2ThdRsrpOffset are identical
(excluding the value -100), UTRAN measurement and GERAN measurement
are not prioritized, and the RSRP threshold delivered by the eNodeB is the sum
of the value of this parameter and the RSRP threshold for inter-RAT
measurement event A2. If both UtranA2ThdRsrpOffset and
GeranA2ThdRsrpOffset are set to -100, UTRAN measurement and GERAN
measurement are not prioritized, and the RSRP threshold delivered by the
eNodeB is the RSRP threshold for inter-RAT measurement event A2. If only
GeranA2ThdRsrpOffset is set to -100, GERAN measurement is not performed
and the RSRP threshold delivered by the eNodeB is the sum of the value of
UtranA2ThdRsrpOffset and the RSRP threshold for inter-RAT measurement
event A2.

5.7.1.6.3.67 CnOperatorIpPath
+-NE
+-eNodeBFunction
+-CnOperatorIpPath

Description

The CnOperatorIpPath MO consists of the parameters used to associate an IP path with an


operator of the eNodeB.
Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Relation with the IPPATH, IPPATH6 MOs:


- IpPathId in an CnOperatorIpPath MO must have been set in the associated IPPATH MO
or in the associated IPPATH6 MO.
Relation with the CnOperator MO:
- CnOperatorId in an CnOperatorIpPath MO must have been set in the associated
CnOperator MO.
Relation with the IPPATH MO:
- IPMUXSWITCH in the IPPATH that is associated with IpPathId in the
CnOperatorIpPath cannot be set to ENABLE.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add the operator that owns the IP path.
CNOPERATORIPPATH

LST Use this command to list the operator that owns the IP path.
CNOPERATORIPPATH

MOD Use this command to allocate the IP path to another operator.


CNOPERATORIPPATH

RMV Use this command to remove the operator that owns the IP path.
CNOPERATORIPPATH

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

IP path ID Indicates the ID of the IP path.

CN Operator ID Indicates the ID of the operator.

5.7.1.6.3.68 CnOperatorSpidCfg
+-NE
+-eNodeBFunction
+-CnOperator
+-CnOperatorSpidCfg

Description

A CnOperatorSpidCfg MO consists of parameters related to a subscriber profile ID of the


operator.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
CnOperator

Relation with the RatFreqPriorityGroup MO:


- RatFreqPriorityGroupId in an CnOperatorSpidCfg MO must have been set in the
associated RatFreqPriorityGroup MO.
Relation with the CnOperator MO:
- CnOperatorId in an CnOperatorSpidCfg MO must have been set in the associated
CnOperator MO.
- A maximum of 256 CnOperatorSpidCfg MOs can be configured for each CnOperator
MO.

Related MML Commands


Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add a dedicated subscriber profile ID (SPID) configuration
CNOPERATORSPIDCF
G for an operator.

LST Use this command to list the dedicated subscriber profile ID (SPID)
CNOPERATORSPIDCF
G configuration for one or all operators.

MOD Use this command to modify the dedicated subscriber profile ID (SPID)
CNOPERATORSPIDCF
G configuration for an operator.

RMV Use this command to remove the dedicated subscriber profile ID (SPID)
CNOPERATORSPIDCF
G configuration for an operator.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

CN Operator ID Indicates the ID of the operator.

Spid Indicates the dedicated SPID for an operator.Operators can define the
RatFreqPriorityGroupId MO corresponding to the dedicated SPID. Each
operator can be configured with a maximum of 256 dedicated SPIDs.

RAT frequency priority Indicates whether to set a RAT or frequency priority. If this parameter is set to
indication
CFG(CFG), UEs preferentially camp on the RAT or frequency. If this parameter
is set to NOT_CFG(NOT_CFG), UEs do not preferentially camp on the RAT or
frequency.

RAT frequency priority Indicates the ID of a RAT/frequency priority group.


group ID

5.7.1.6.3.69 CnOperatorStandardQci
+-NE
+-eNodeBFunction
+-CnOperator
+-CnOperatorStandardQci

Description

A CnOperatorStandardQci MO contains an operator-specific standardized QoS Class Identifier


(QCI) and a service-based inter-RAT handover policy group.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
CnOperator

Relation with the ServiceIrHoCfgGroup MO:


- ServiceIrHoCfgGroupId in a CnOperatorStandardQci MO must have been set in the
associated ServiceIrHoCfgGroup MO.
Relation with the ServiceIfHoCfgGroup MO:
- ServiceIfHoCfgGroupId in a CnOperatorStandardQci MO must have been set in the
associated ServiceIfHoCfgGroup MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list operator-specific standardized QCI settings.


CNOPERATORSTAND
ARDQCI

MOD Use this command to modify the settings of a standardized QCI for an operator.
CNOPERATORSTAND
ARDQCI

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

CN Operator ID Indicates the index of the operator.

QoS Class Indication Indicates the QoS Class Identifier (QCI) of an EPS bearer. Different QCIs
represent different QoS specifications such as the packet delay budget, packet
error loss rate, and resource type (whether the service is a GBR service or not).
For details, see Table 6.1.7 in 3GPP TS 23.203.

Service-based inter- Indicates the ID of the service-based inter-RAT handover policy group.
RAT handover policy
group ID

Service-based inter- Indicates the ID of the service-based inter-frequency handover policy group.
Freq handover policy
group ID

5.7.1.6.3.70 CnOperatorTa
+-NE
+-eNodeBFunction
+-CnOperatorTa

Description

A CnOperatorTa MO consists of parameters related to a tracking area, which is identified by a


tracking area code (TAC), for an operator. The TAC is used by the evolved packet core (EPC) to
determine the area within which paging messages are sent. One tracking area is comprised of one
or more cells. An eNodeB can be configured with a maximum of 108 CnOperatorTa MOs.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Relation with the ENodeBSharingMode MO:


- If ENodeBSharingMode in the ENodeBSharingMode MO is set to SHARED_FREQ,
CnOperator MO configured with Cell can not be all CNOPERATOR_SECONDARY.
Relation with the CnOperator MO:
- A maximum of 18 CnOperatorTa MOs can be configured for each CnOperator MO.
- CnOperatorId in a CnOperatorTa MO must have been set in the associated CnOperator
MO.
Relation with the ENodeBSharingMode,CellOp MOs:
- If ENodeBSharingMode in the ENodeBSharingMode MO is set to SHARED_FREQ,
CnOperator MOs configured with Cell MO must have one CnOperator MO which is primary
operator.
Relation with the CellOp MO:
- TrackingAreaId in a CellOp MO must have been set in the associated CnOperatorTa MO.
Relation with the EutranInterFreqNCell,CellOp,CnOperator MOs:
- A CellOp MO must be configured for each EutranInterFreqNCell MO that corresponds to
an intra-eNodeB inter-frequency neighboring cell. If the ENodeBSharingMode parameter in the
ENodeBSharingMode MO is set to SHARED_FREQ, Mcc and Mnc in such an
EutranInterFreqNCell MO must be the same as the Mcc and Mnc specified in the
CnOperator MO representing the primary operator. If ENodeBSharingMode is set to
INDEPENDENT or SEPARATED_FREQ, Mcc and Mnc in such an EutranInterFreqNCell
MO must be set to the same values as Mcc and Mnc specified in the CnOperator MO
corresponding to the CellOp MO associated with this EutranInterFreqNCell MO.
Relation with the EutranIntraFreqNCell,CellOp,CnOperator MOs:
- A CellOp MO must be configured for each EutranIntraFreqNCell MO that corresponds to
an intra-eNodeB intra-frequency neighboring cell. If the ENodeBSharingMode parameter in the
ENodeBSharingMode MO is set to SHARED_FREQ, Mcc and Mnc in such an
EutranIntraFreqNCell MO must be the same as the Mcc and Mnc specified in the
CnOperator MO representing the primary operator. If ENodeBSharingMode is set to
INDEPENDENT or SEPARATED_FREQ, Mcc and Mnc in such an EutranIntraFreqNCell
MO must be set to the same values as Mcc and Mnc specified in the CnOperator MO
corresponding to the CellOp MO associated with this EutranIntraFreqNCell MO.
Relation with the CellOp,Cell MOs:
- If ENodeBSharingMode in the ENodeBSharingMode MO is set to SHARED_FREQ and
CellActiveState in a Cell MO is set to CELL_ACTIVE, CnOperatorId in the CnOperatorTa
MO corresponding to TrackingAreaId in each CellOp MO must be unique.
- If ENodeBSharingMode in the ENodeBSharingMode MO is set to SHARED_FREQ and
CellActiveState in a Cell MO is set to CELL_ACTIVE, Tac in the CnOperatorTa MO
corresponding to TrackingAreaId in each CellOp MO must have the same value.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD CNOPERATORTA Use this command to add a tracking area for the eNodeB.

LST CNOPERATORTA Use this command to list tracking area settings of the eNodeB.

MOD Use this command to modify the tracking area parameters of the eNodeB.
CNOPERATORTA

RMV CNOPERATORTA Use this command to remove a tracking area for the eNodeB.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local tracking area ID Indicates the tracking area ID, which uniquely identifies an entry of tracking
area information. This parameter is used only within the eNodeB and is not used
during the information exchange with the EPC. This is different from the TAI
configured in the EPC TAL.

CN Operator ID Indicates the index of the operator.

Tracking area code Indicates the tracking area code (TAC), which is used by the EPC to determine
the area within which paging messages are sent. One tracking area is comprised
of one or more cells. Two TAC values 0x0000(0) and 0xFFFE(65534) are
reserved according to the protocol and will not be used in future versions.
Therefore, do not use 0 or 65534 as a TAC value in TAC planning or
configuration.

5.7.1.6.3.71 CounterCheckPara
+-NE
+-eNodeBFunction
+-CounterCheckPara

Description
The CounterCheckPara MO consists of the parameters related to counter checks. The parameters
include the counter check timer, COUNT value, and data radio bearer (DRB) release switch. The
counter check procedure is initiated by the eNodeB. This procedure is used to request the UE to
verify the amount of data sent and received on each DRB.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the parameters related to counter checks.
COUNTERCHECKPAR
A

MOD Use this command to modify the parameters related to counter checks.
COUNTERCHECKPAR
A

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Counter check timer Indicates the length of the counter check timer. When the timer expires, a
counter check procedure is initiated. After the procedure is complete, the timer is
restarted. A length of 0 indicates that the timer is invalid. In this case, the
eNodeB cannot initiate periodic counter check procedures.

Counter check count Indicates the COUNT value for initiating counter check procedures. When the
number
COUNT value (used at the PDCP layer) of any DRB for a UE is a multiple of
Table 2 Related parameters

Parameter Description

the value of this parameter, the eNodeB initiates a counter check procedure. The
value 0 indicates that the eNodeB does not initiate a counter check procedure
based on the COUNT value.

Counter check user Indicates whether to release a DRB when the counter check detects an
Release switch
unexpected result in the DRB.

5.7.1.6.3.72 CqiAdaptiveCfg
+-NE
+-eNodeBFunction
+-CqiAdaptiveCfg

Description

The CqiAdaptiveCfg MO consists of the parameters related to UE-specific channel quality


indicator (CQI) adaptation. If CQI adaptation is enabled, the eNodeB sets the CQI period based
on channel conditions. If CQI adaptation is disabled, the eNodeB sets a fixed CQI period.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

LST Use this command to list the parameters related to CQI adaptation.
CQIADAPTIVECFG

MOD Use this command to modify the parameters related to CQI adaptation.
CQIADAPTIVECFG

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

CQI period adaptive Indicates whether to enable or disable CQI reporting period adaptation. If this
switch
parameter is set to ON, the CQI period adaptively changes based on the air
interface load of the cell. If this parameter is set to OFF, the CQI period is the
specified by the UserCqiPeriodCfg parameter. This parameter is valid only for
FDD cells.

User CQI period config Indicates the fixed CQI period. A fixed CQI period is used when CQI period
adaptation is disabled. If the UserCqiPeriodCfg parameter is set to 32 ms, the
eNodeB automatically changes the value to 20 ms. If the UserCqiPeriodCfg
parameter is set to 64 ms, the eNodeB automatically changes the value to 40 ms.
If the UserCqiPeriodCfg parameter is set to 128 ms, the eNodeB automatically
changes the value to 80 ms. This parameter is valid only for FDD cells.

SimultaneousAckNackA Indicates whether CQI and Ack or Nack can be concurrently sent over the
ndCQI config switch
PUCCH. For details, see the contents related to PUCCH format in 3GPP
TS36.213. When this parameter is set to OFF, the value of
simultaneousAckNackAndCQI becomes False, that is, CQI and Ack or Nack
cannot be sent simultaneously over the PUCCH. When this parameter is set to
ON, the value of simultaneousAckNackAndCQI becomes True, that is, CQI and
Ack or Nack can be sent simultaneously over the PUCCH.

5.7.1.6.3.73 CSFallBackBlindHoCfg
+-NE
+-eNodeBFunction
+-CnOperator
+-CSFallBackBlindHoCfg

Description

The CSFallBackBlindHoCfg MO consists of the parameters that specify the operator-specific


priorities of inter-RAT systems to be considered in handovers. The eNodeB supports a maximum
of six sets of priorities, with each set defined for one operator. By default, UTRAN, GERAN and
CDMA2000 are assigned priorities in descending order. The operator ID must be obtained before
this MO is configured. By default, the eNodeB considers that inter-RAT systems do not support
location service (LCS). If a system supports LCS, the associated parameters must be set in this
MO. During evaluation of LCS-triggered CSFB, an LCS-supporting system takes precedence
over a non-LCS-supporting system. If more than one system supports LCS, the user-defined
priorities apply. The inter-RAT system priorities also apply to redirection, for example, based on
coverage.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
CnOperator

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the configuration related to inter-RAT handover.
CSFALLBACKBLINDH
OCFG

MOD Use this command to modify the configuration related to inter-RAT handover.
CSFALLBACKBLINDH
OCFG

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

CN Operator ID Indicates the index of the operator.

Highest priority InterRat Indicates the highest-priority RAT for handovers. It is UTRAN by default. If this
parameter is set to UTRAN, GERAN, or CDMA2000, the highest-priority RAT
is UTRAN, GERAN, or CDMA2000, respectively.

Second priority InterRat Indicates the medium-priority RAT for handovers. It is GERAN by default. If
this parameter is set to UTRAN, GERAN, or CDMA2000, the medium-priority
RAT is UTRAN, GERAN, or CDMA2000, respectively. If this parameter is set
to NULL, no medium-priority RAT is specified and only the highest-priority
RAT can be selected for handovers.

Lowest priority InterRat Indicates the lowest-priority RAT for handovers. It is CDMA2000 by default. If
this parameter is set to UTRAN, GERAN, or CDMA2000, the lowest-priority
RAT is UTRAN, GERAN, or CDMA2000, respectively. If this parameter is set
to NULL, no lowest-priority RAT is specified and only the highest- or medium-
priority RAT can be selected for handovers.

UTRAN LCS capability Indicates the LCS capability of the UTRAN. If this parameter is set to ON, the
UTRAN supports LCS. If this parameter is set to OFF, the UTRAN does not
support LCS.

GERAN LCS capability Indicates the LCS capability of the GERAN. If this parameter is set to ON, the
GERAN supports LCS. If this parameter is set to OFF, the GERAN does not
support LCS.

CDMA2000 LCS Indicates the LCS capability of the CDMA2000. If this parameter is set to ON,
capability
the CDMA2000 supports LCS. If this parameter is set to OFF, the CDMA2000
does not support LCS.

CSFB Highest priority Indicates the highest-priority RAT for CSFB initiated by a UE in idle mode. It is
InterRat for Idle UE
UTRAN by default. If this parameter is set to UTRAN, GERAN, or
CDMA2000, the highest-priority RAT is UTRAN, GERAN, or CDMA2000,
respectively.

CSFB Second priority Indicates the medium-priority RAT for CSFB initiated by a UE in idle mode. It
InterRat for Idle UE
is GERAN by default. If this parameter is set to UTRAN, GERAN, or
CDMA2000, the medium-priority RAT is UTRAN, GERAN, or CDMA2000,
respectively. If this parameter is set to NULL, no medium-priority RAT is
specified and only the highest-priority RAT can be selected for CSFB initiated
by a UE in idle mode.

CSFB Lowest priority Indicates the lowest-priority RAT for CSFB initiated by a UE in idle mode. It is
InterRat for Idle UE
CDMA2000 by default. If this parameter is set to UTRAN, GERAN, or
Table 2 Related parameters

Parameter Description

CDMA2000, the lowest-priority RAT is UTRAN, GERAN, or CDMA2000,


respectively. If this parameter is set to NULL, no lowest-priority RAT is
specified and only the highest- or medium-priority RAT can be selected for
CSFB initiated by a UE in idle mode.

5.7.1.6.3.74 CSFallBackHo
+-NE
+-eNodeBFunction
+-Cell
+-CSFallBackHo

Description

The CSFallBackHo MO consists of the parameters related to handovers for CS fallback. CS


fallback is a policy of interoperability between LTE and 2G/3G RATs, for the purpose of reusing
the CS domain of the 2G/3G system to provide voice services. For example, when IMS is not
deployed for voice services in the LTE system, CS fallback is applicable in the areas covered by
both the E-UTRAN and the 2G/3G network; that is, voice services can be diverted to the 2G/3G
network.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the Cell MO:


- LocalCellId in an CSFallBackHo MO must have been set in the associated Cell MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

LST CSFALLBACKHO Use this command to list the CS fallback configuration.

MOD CSFALLBACKHO Use this command to modify the CS fallback configuration.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

CSFB Utran EventB1 Indicates the time-to-trigger for event B1 that is used in CS fallback to UTRAN.
Time To Trig
When CS fallback to UTRAN is applicable, this parameter is set for UEs and
used in the evaluation of whether to trigger event B1. When detecting that the
signal quality in at least one UTRAN cell meets the entering condition, the UE
does not send a measurement report to the eNodeB immediately. Instead, the UE
sends a report only when the signal quality continuously meets the entering
condition during the time-to-trigger. This parameter helps decrease the number
of occasionally triggered event reports, the average number of handovers, and
the number of wrong handovers, and thus helps to prevent unnecessary
handovers. For details, see 3GPP TS 36.331.

CSFB Geran EventB1 Indicates the time-to-trigger for event B1 that is used in CS fallback to GERAN.
Time To Trig
When CS fallback to GERAN is applicable, this parameter is set for UEs and
used in the evaluation of whether to trigger event B1. When detecting that the
signal quality in at least one GERAN cell meets the entering condition, the UE
does not send a measurement report to the eNodeB immediately. Instead, the UE
sends a report only when the signal quality continuously meets the entering
condition during the time-to-trigger. This parameter helps decrease the number
of occasionally triggered event reports, the average number of handovers, and
the number of wrong handovers, and thus helps to prevent unnecessary
handovers. For details, see 3GPP TS 36.331.

CSFB CDMA EventB1 Indicates the time-to-trigger for event B1, which is used in CS fallback to
Time To Trig
CDMA2000. When CS fallback to CDMA2000 is applicable, this parameter is
set for UEs and used in the evaluation of whether to trigger event B1. When
detecting that the signal quality in at least one CDMA2000 cell meets the
entering condition, the UE does not send a measurement report to the eNodeB
Table 2 Related parameters

Parameter Description

immediately. Instead, the UE sends a report only when the signal quality
continuously meets the entering condition during the time-to-trigger. This
parameter helps reduce the number of occasionally triggered event reports, the
average number of handovers, and the number of wrong handovers, and hence
helps prevent unnecessary handovers. For details, see 3GPP TS 36.331.

CSFB UTRAN EventB1 Indicates the RSCP threshold for event B1, which is used in CS fallback to
RSCP Trigger
Threshold UTRAN. When CS fallback to UTRAN is applicable, this parameter is set for
UEs and used in the evaluation about whether to trigger event B1. This
parameter indicates the RSCP requirement for the UTRAN cells to be included
in the measurement report. A UE sends a measurement report related to event B1
to the eNodeB when the RSCP in at least one UTRAN cell exceeds this
threshold and other triggering conditions are met. For details, see 3GPP TS
36.331.

CSFB UTRAN EventB1 Indicates the Ec/N0 threshold for event B1, which is used in CS fallback to
ECN0 Trigger
Threshold UTRAN. When CS fallback to UTRAN is required, this parameter is set for UEs
and used in the evaluation about whether to trigger event B1. This parameter
indicates the Ec/N0 requirement for the UTRAN cells to be included in the
measurement report. A UE sends a measurement report related to event B1 to the
eNodeB when the Ec/N0 in at least one UTRAN cell exceeds this threshold and
other triggering conditions are met. For a cell with large signal fading variance,
set this parameter to a large value to prevent unnecessary handovers. For a cell
with small signal fading variance, set this parameter to a small value to ensure
timely handovers. For details, see 3GPP TS 36.331.

CSFB GERAN EventB1 Indicates the RSSI threshold for event B1 that is used in CS fallback to GERAN.
Trigger Threshold
A UE sends a measurement report related to event B1 to the eNodeB when the
RSSI in at least one GERAN cell exceeds this threshold and other triggering
conditions are met. For details, see 3GPP TS 36.331.

CSFB CDMA2000 Indicates the pilot strength threshold related to event B1, which is used in CS
EventB1 Trigger
Threshold fallback to CDMA2000. A UE sends a measurement report related to event B1
to the eNodeB when the pilot strength in at least one CDMA2000 cell exceeds
this threshold and other triggering conditions are met. For details, see 3GPP TS
36.331.

CSFB Adaptive Blind Indicates the RSRP threshold for event A1 associated with CSFB-triggered
Ho A1 RSRP Trigger
Threshold adaptive blind handovers. This parameter is set for a UE as a triggering
condition of event A1 measurement related to a CSFB-triggered adaptive blind
handover. This parameter specifies the RSRP threshold of the local cell above
which a CSFB-triggered adaptive blind handover is triggered. If the RSRP value
measured by the UE exceeds this threshold, this UE submits a measurement
report related to event A1.
Table 2 Related parameters

Parameter Description

CSFB Protection Timer Indicates the timer governing the period in which only CSFB can be performed .
After the timer expires, the eNodeB performs a blind redirection for the UE.

5.7.1.6.3.75 CSFallBackPolicyCfg
+-NE
+-eNodeBFunction
+-CSFallBackPolicyCfg

Description

The CSFallBackPolicyCfg MO defines circuit switched fallback (CSFB) policies. Depending on


whether UEs are in connected or idle mode, eNodeBs can use different CSFB policies when
handing over UEs from the E-UTRAN to another inter-RAT network.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the CSFB policy configuration.


CSFALLBACKPOLICY
CFG

MOD Use this command to modify the CSFB policy configuration.


Table 1 Related MML commands

MML Command Function

CSFALLBACKPOLICY
CFG

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

CSFB handover policy Indicates the CSFB policy for a UE in connected mode. If the CSFB steering
Configuration
function is disabled, this parameter also applies to UEs in idle mode. The policy
can be PS handover, CCO, or redirection.

CSFB handover policy Indicates the CSFB policy for a UE in idle mode. The policy can be PS
Configuration for idle ue
handover, CCO, or redirection.

5.7.1.6.3.76 DistBasedHO
+-NE
+-eNodeBFunction
+-Cell
+-DistBasedHO

Description

The DistBasedHo MO consists of parameters related to handovers based on the distance between
the eNodeB and the UE.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST DISTBASEDHO Use this command to list the settings of distance-based handovers.

MOD DISTBASEDHO Use this command to modify the settings of distance-based handovers.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local identity of the cell. It uniquely identifies a cell within an
eNodeB.

Distance-based Indicates the measurement object type for distance-based handovers. The
Measurement Object
Type measurement object type can be E-UTRAN, UTRAN, or GERAN.

Distance-based Indicates the threshold for distance-based handovers. If the distance between a
Handover Threshold
UE and the cell center is greater than this threshold, a distance-based handover
is triggered for this UE.

5.7.1.6.3.77 Drx
+-NE
+-eNodeBFunction
+-Drx

Description
The DRX MO consists of the parameters related to discontinuous reception (DRX). If DRX is
enabled, a UE receives data only during necessary periods of time.
DRX is introduced for the following purposes:
1. To reduce the UE power consumption and stretch the service time.
2. To increase system resource efficiency.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST DRX Use this command to list the DRX configuration.

MOD DRX Use this command to modify the DRX configuration.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

DRX switch Indicates the DRX switch. The setting of this parameter has no effect on
dynamic DRX.

Short-cycle DRX switch Indicates whether to enable or disable short DRX cycles. Short DRX cycles
reduce the traffic delay.

Special long DRX cycle Indicates the length of a long DRX cycle that is applied only to non-power-
Table 2 Related parameters

Parameter Description

saving UEs whose subscriber profile ID for RAT/frequency priority (RFSP)


indexes are contained in the RFSP index set. Because of the impact of the SRS
bandwidth and TA period specified by the TimeAlignmentTimer parameter, the
actual value of this parameter assigned to a UE may be less than the configured
value. In addition, the configured value will be rounded down to an integral
multiple of 10. Therefore, you are advised to configure this parameter to a value
that is an integral multiple of 10. If users hope that the value actually assigned to
a UE is equal to or greater than 80 ms, set the TimeAlignmentTimer parameter
to a value equal to or greater than 10240 ms. If the TimingAdvCmdOptSwitch
parameter is set to ON, it is recommended that the LongDrxCycleSpecial
parameter be set to a value smaller than or equal to 320 ms. Otherwise, the
uplink time alignment performance of UEs is affected. If the
TimingAdvCmdOptSwitch parameter is set to ON, it is recommended that the
TimeAlignmentTimer parameter be set to sf10240. A smaller value of the
TimeAlignmentTimer parameter, such as sf5120, increases the probability that
UEs in DRX mode become uplink asynchronized.

Special On Duration Indicates the length of the On Duration Timer that applies only to non-power-
timer
saving UEs whose RFSP indexes are contained in the RFSP index set. For
details about this timer, see 3GPP TS 36.321. Because of the impact of CQI
reporting intervals and SRS transmission intervals, the actual value of this
parameter assigned to a UE may be greater than the configured value.

Special DRX inactivity Indicates the length of the DRX Inactivity Timer that applies only to non-power-
timer
saving UEs whose RFSP indexes are contained in the RFSP index set. For
details about this timer, see 3GPP TS 36.321.

Special short-cycle Indicates whether to enable or disable short DRX cycles for non-power-saving
DRX supported
indication UEs whose RFSP indexes are contained in the RFSP index set.

Special short DRX Indicates the length of a short DRX cycle that is applied only to non-power-
cycle
saving UEs whose subscriber profile ID for RAT/frequency priority (RFSP)
indexes are contained in the RFSP index set. According to 3GPP specifications,
the length of a long DRX cycle must be an integer multiple of that of a short
DRX cycle. In addition, the actual value of LongDrxCycleSpecial assigned to a
UE may be less than the configured value because of the impact of the SRS
bandwidth and TA period specified by the TimeAlignmentTimer parameter.
Therefore, the actual value of ShortDrxCycleSpecial assigned to a UE may be
less than the configured value.

Special DRX short Indicates the length of the DRX Short Cycle Timer that applies only to non-
cycle timer
power-saving UEs whose RFSP indexes are contained in the RFSP index set.
The length of this timer is expressed in the number of short DRX cycles. If this
parameter is set to 1, the length of this timer is one short DRX cycle. If this
Table 2 Related parameters

Parameter Description

parameter is set to 2, the length of this timer is two short DRX cycles. For
details, see 3GPP TS 36.321 5.7.

Long DRX Cycle for Indicates the long DRX cycle for intra-RAT ANR. If intra-RAT ANR is enabled,
ANR
this parameter is valid regardless of whether DRX is enabled. If a long DRX
cycle is configured for ANR measurement, it is recommended that this
parameter be set to a value equal to or greater than 256 ms to ensure that the UE
can successfully obtain the CGI of a cell. However, if this parameter is set to a
large value, the delay of obtaining the CGI is large, and therefore the system
delay increases.

Long DRX Cycle for Indicates the long DRX cycle for inter-RAT ANR. If inter-RAT ANR is enabled,
Inter-RAT ANR
this parameter is valid regardless of whether DRX is enabled. If there are
multiple inter-RAT systems, and all of them require inter-RAT ANR
measurements, it is recommended that this parameter be set to the maximum
value of the long DRX cycle configured for inter-RAT ANR measurements.
Otherwise, the success rate for inter-RAT ANR measurements may be affected.

5.7.1.6.3.78 DrxParaGroup
+-NE
+-eNodeBFunction
+-Cell
+-DrxParaGroup

Description

A DrxParaGroup MO is a group of Discontinuous Reception (DRX) parameters to be mapped to


a QoS Class Identifier (QCI). DRX parameter groups are mapped to different QCIs to meet
different service requirements.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the CellStandardQci MO:


- DrxParaGroupId in a CellStandardQci MO must have been set in the associated
DrxParaGroup MO.
Relation with the CellExtendedQci MO:
- DrxParaGroupId in a CellExtendedQci MO must have been set in the associated
DrxParaGroup MO.
Relation with the Cell:
- If a Cell MO is configured, the number of DrxParaGroup MOs that reference LocalCellId
in the Cell MO must be from 1 to 10.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add a DRX parameter group.


DRXPARAGROUP

LST DRXPARAGROUP Use this command to list one or all DRX parameter groups.

MOD Use this command to modify a DRX parameter group.


DRXPARAGROUP

RMV Use this command to remove a DRX parameter group.


DRXPARAGROUP

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

DRX parameter group Indicates the ID of the DRX parameter group.


ID

Enter DRX Switch Indicates whether bearers to which the parameter group applies support DRX.
Table 2 Related parameters

Parameter Description

The value ON indicates that the bearers support DRX. The value OFF indicates
that the bearers do not support DRX.

On Duration Timer Indicates the length of the On Duration Timer. Because of the impact of CQI
reporting intervals and SRS transmission intervals, the actual value of this
parameter assigned to a UE may be greater than the configured value.

DRX Inactivity Timer Indicates the length of the DRX Inactivity Timer.

DRX Retransmission Indicates the length of the DRX Retransmission Timer.


Timer

Long DRX Cycle Indicates the length of the long DRX cycle. Because of the impact of the SRS
bandwidth and TA period specified by the TimeAlignmentTimer parameter, the
actual value of this parameter assigned to a UE may be less than the configured
value. In addition, the configured value will be rounded down to an integral
multiple of 10. Therefore, you are advised to configure this parameter to a value
that is an integral multiple of 10. If users hope that the value actually assigned to
a UE is equal to or greater than 80 ms, set the TimeAlignmentTimer parameter
to a value equal to or greater than 10240 ms. If the TimingAdvCmdOptSwitch
parameter is set to ON, it is recommended that the LongDrxCycle parameter be
set to a value smaller than or equal to 320 ms. Otherwise, the uplink time
alignment performance of UEs is affected. If the TimingAdvCmdOptSwitch
parameter is set to ON, it is recommended that the TimeAlignmentTimer
parameter be set to sf10240. A smaller value of the TimeAlignmentTimer
parameter, such as sf5120, increases the probability that UEs in DRX mode
become uplink asynchronized. The length of the long DRX cycle must be
smaller than the length of the PDCP packet discarding timer for the
corresponding QCI. Otherwise, packet loss occurs during a ping operation or
low-traffic service.

Short-cycle DRX Indicates whether short DRX cycles are enabled.


supported indication

Short DRX Cycle Indicates the length of the short DRX cycle. According to 3GPP specifications,
the length of a long DRX cycle must be an integer multiple of that of a short
DRX cycle. In addition, the actual value of LongDrxCycle assigned to a UE
may be less than the configured value because of the impact of the SRS
bandwidth and TA period specified by the TimeAlignmentTimer parameter.
Therefore, the actual value of ShortDrxCycle assigned to a UE may be less than
the configured value.

DRX Short Cycle Timer Indicates the length of the DRX Short Cycle Timer. If this parameter is set to 1,
the length of this timer is one short DRX cycle. If this parameter is set to 2, the
length of this timer is two short DRX cycles. If this parameter is set to a large
Table 2 Related parameters

Parameter Description

value, a UE for which short DRX cycles are enabled stays in short-cycle DRX
for a long time. For details, see 3GPP TS 36.321 5.7.

5.7.1.6.3.79 Emc
+-NE
+-eNodeBFunction
+-CnOperator
+-Emc

Description

An Emc MO consists of parameters related to emergency calls. The parameters include the
switches that control whether an operator supports emergency calls and provide the
allocation/retention priority (ARP) values of bearers for emergency calls.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
CnOperator

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST EMC Use this command to list the emergency call configuration.

MOD EMC Use this command to modify the emergency call configuration.
Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

CN Operator ID Indicates the index of the operator.

Emergency call enabled Indicates whether to enable or disable emergency calls. It is recommended that
switch
this parameter be set to a value in accordance with the actual emergency call
capability of the operator.

Emergency call enabled Indicates whether the operator supports emergency calls initiated by UEs in
switch in limited mode
limited mode.

The ARP of EMC Indicates the Allocation and Retention Priority (ARP) value of the dedicated
dedicated bearer
emergency call bearer.

The ARP of EMC Indicates the Allocation and Retention Priority (ARP) value of the default
default bearer
emergency call bearer.

5.7.1.6.3.80 eNBCellOpRsvdPara
+-NE
+-eNodeBFunction
+-Cell
+-CellOp
+-eNBCellOpRsvdPara

Description

An eNBCellOpRsvdPara MO consists of the cell- operator-level parameters that are reserved for
future requirements.

Effective Scenario

Immediately

Relations Between MOs


Possible parents:
CellOp

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list reserved cell-operator-level parameters.


ENBCELLOPRSVDPA
RA

MOD Use this command to modify reserved cell-operator-level parameters.


ENBCELLOPRSVDPA
RA

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Local tracking area ID Indicates the local tracking area identity of the cell, which uniquely identifies an
operator's record of tracking area information within a cell. This parameter is
used only in the eNodeB and is different from the TAI configured in the TAL on
the MME.

Reserved Switch Indicates reserved 32-bit switch parameter 0 that is reserved for future
Parameter 0
requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Switch Indicates reserved 32-bit switch parameter 1 that is reserved for future
Parameter 1
requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
Table 2 Related parameters

Parameter Description

parameter.

Reserved Switch Indicates reserved 32-bit switch parameter 2 that is reserved for future
Parameter 2
requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 2 Indicates reserved parameter 2 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 3 Indicates reserved parameter 3 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 4 Indicates reserved parameter 4 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 5 Indicates reserved parameter 5 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 6 Indicates reserved parameter 6 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 7 Indicates reserved parameter 7 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
Table 2 Related parameters

Parameter Description

parameter.

Reserved Parameter 8 Indicates reserved parameter 8 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 9 Indicates reserved parameter 9 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 10 Indicates reserved parameter 10 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 11 Indicates reserved parameter 11 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 12 Indicates reserved parameter 12 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 13 Indicates reserved parameter 13 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 14 Indicates reserved parameter 14 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
Table 2 Related parameters

Parameter Description

parameter.

Reserved Parameter 15 Indicates reserved parameter 15 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 16 Indicates reserved parameter 16 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 17 Indicates reserved parameter 17 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 18 Indicates reserved parameter 18 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 19 Indicates reserved parameter 19 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 20 Indicates reserved parameter 20 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 21 Indicates reserved parameter 21 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
Table 2 Related parameters

Parameter Description

parameter.

5.7.1.6.3.81 eNBCellQciRsvdPara
+-NE
+-eNodeBFunction
+-Cell
+-eNBCellQciRsvdPara

Description

An eNBCellQciRsvdPara MO consists of the cell-level QCI parameters that are reserved for
future requirements.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list reserved cell-level QCI parameters.


ENBCELLQCIRSVDPA
RA

MOD Use this command to modify reserved cell-level QCI parameters.


ENBCELLQCIRSVDPA
RA
Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local identity of the cell. It uniquely identifies a cell within an
eNodeB.

QoS Class Indication Indicates the QoS class identifier (QCI) of an evolved packet system (EPS)
bearer. Different QCIs indicate different QoS requirements, such as the packet
delay budget, packet error loss rate, and resource type. For details, see Table
6.1.7 in 3GPP TS 23.203.

Reserved Switch Indicates reserved 32-bit switch parameter 0 that is reserved for future
Parameter 0
requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Switch Indicates reserved 32-bit switch parameter 1 that is reserved for future
Parameter 1
requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Switch Indicates reserved 32-bit switch parameter 2 that is reserved for future
Parameter 2
requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 2 Indicates reserved parameter 2 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 3 Indicates reserved parameter 3 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
Table 2 Related parameters

Parameter Description

parameter.

Reserved Parameter 4 Indicates reserved parameter 4 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 5 Indicates reserved parameter 5 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 6 Indicates reserved parameter 6 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 7 Indicates reserved parameter 7 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 8 Indicates reserved parameter 8 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 9 Indicates reserved parameter 9 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 10 Indicates reserved parameter 10 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
Table 2 Related parameters

Parameter Description

parameter.

Reserved Parameter 11 Indicates reserved parameter 11 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 12 Indicates reserved parameter 12 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 13 Indicates reserved parameter 13 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 14 Indicates reserved parameter 14 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 15 Indicates reserved parameter 15 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 16 Indicates reserved parameter 16 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 17 Indicates reserved parameter 17 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
Table 2 Related parameters

Parameter Description

parameter.

Reserved Parameter 18 Indicates reserved parameter 18 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 19 Indicates reserved parameter 19 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 20 Indicates reserved parameter 20 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 21 Indicates reserved parameter 21 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

5.7.1.6.3.82 eNBCellRsvdPara
+-NE
+-eNodeBFunction
+-Cell
+-eNBCellRsvdPara

Description

An eNBCellRsvdPara MO consists of the cell-level parameters that are reserved for future
requirements.
Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list reserved cell-level parameter.


ENBCELLRSVDPARA

MOD Use this command to modify reserved cell-level parameter.


ENBCELLRSVDPARA

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Reserved Switch Indicates reserved 32-bit switch parameter 0 that is reserved for future
Parameter 0
requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Switch Indicates reserved 32-bit switch parameter 1 that is reserved for future
Parameter 1
requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
Table 2 Related parameters

Parameter Description

parameter.

Reserved Switch Indicates reserved 32-bit switch parameter 2 that is reserved for future
Parameter 2
requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 2 Indicates reserved parameter 2 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 3 Indicates reserved parameter 3 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 4 Indicates reserved parameter 4 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 5 Indicates reserved parameter 5 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 6 Indicates reserved parameter 6 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 7 Indicates reserved parameter 7 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
Table 2 Related parameters

Parameter Description

parameter.

Reserved Parameter 8 Indicates reserved parameter 8 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 9 Indicates reserved parameter 9 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 10 Indicates reserved parameter 10 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 11 Indicates reserved parameter 11 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 12 Indicates reserved parameter 12 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 13 Indicates reserved parameter 13 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 14 Indicates reserved parameter 14 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
Table 2 Related parameters

Parameter Description

parameter.

Reserved Parameter 15 Indicates reserved parameter 15 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 16 Indicates reserved parameter 16 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 17 Indicates reserved parameter 17 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 18 Indicates reserved parameter 18 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 19 Indicates reserved parameter 19 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 20 Indicates reserved parameter 20 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 21 Indicates reserved parameter 21 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
Table 2 Related parameters

Parameter Description

parameter.

5.7.1.6.3.83 eNBCnOpQciRsvdPara
+-NE
+-eNodeBFunction
+-CnOperator
+-eNBCnOpQciRsvdPara

Description

An eNBCnOpQciRsvdPara MO consists of the operator-level QCI parameters that are reserved


for future requirements.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
CnOperator

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list reserved operator-level QCI parameters.


ENBCNOPQCIRSVDP
ARA

MOD Use this command to modify reserved operator-level QCI parameters.


ENBCNOPQCIRSVDP
ARA
Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

CN Operator ID Indicates the ID of the operator.

QoS Class Indication Indicates the QoS class identifier (QCI) of an evolved packet system (EPS)
bearer. Different QCIs indicate different QoS requirements, such as the packet
delay budget, packet error loss rate, and resource type. For details, see Table
6.1.7 in 3GPP TS 23.203.

Reserved Switch Indicates reserved 32-bit switch parameter 0 that is reserved for future
Parameter 0
requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Switch Indicates reserved 32-bit switch parameter 1 that is reserved for future
Parameter 1
requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Switch Indicates reserved 32-bit switch parameter 2 that is reserved for future
Parameter 2
requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 2 Indicates reserved parameter 2 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 3 Indicates reserved parameter 3 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.
Table 2 Related parameters

Parameter Description

Reserved Parameter 4 Indicates reserved parameter 4 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 5 Indicates reserved parameter 5 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 6 Indicates reserved parameter 6 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 7 Indicates reserved parameter 7 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 8 Indicates reserved parameter 8 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 9 Indicates reserved parameter 9 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 10 Indicates reserved parameter 10 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 11 Indicates reserved parameter 11 that is reserved for future requirements.
Table 2 Related parameters

Parameter Description

Note on parameter replacement: Reserved parameters are temporarily used in


patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 12 Indicates reserved parameter 12 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 13 Indicates reserved parameter 13 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 14 Indicates reserved parameter 14 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 15 Indicates reserved parameter 15 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 16 Indicates reserved parameter 16 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 17 Indicates reserved parameter 17 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 18 Indicates reserved parameter 18 that is reserved for future requirements.
Table 2 Related parameters

Parameter Description

Note on parameter replacement: Reserved parameters are temporarily used in


patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 19 Indicates reserved parameter 19 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 20 Indicates reserved parameter 20 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 21 Indicates reserved parameter 21 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

5.7.1.6.3.84 eNBCnOpRsvdPara
+-NE
+-eNodeBFunction
+-CnOperator
+-eNBCnOpRsvdPara

Description

An eNBCnOpRsvdPara MO consists of the operator-level parameters that are reserved for future
requirements.

Effective Scenario
Immediately

Relations Between MOs

Possible parents:
CnOperator

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list reserved operator-level parameters.


ENBCNOPRSVDPARA

MOD Use this command to modify reserved operator-level parameters.


ENBCNOPRSVDPARA

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

CN Operator ID Indicates the ID of the operator.

Reserved Switch Indicates reserved 32-bit switch parameter 0 that is reserved for future
Parameter 0
requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Switch Indicates reserved 32-bit switch parameter 1 that is reserved for future
Parameter 1
requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.
Table 2 Related parameters

Parameter Description

Reserved Switch Indicates reserved 32-bit switch parameter 2 that is reserved for future
Parameter 2
requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 2 Indicates reserved parameter 2 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 3 Indicates reserved parameter 3 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 4 Indicates reserved parameter 4 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 5 Indicates reserved parameter 5 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 6 Indicates reserved parameter 6 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 7 Indicates reserved parameter 7 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.
Table 2 Related parameters

Parameter Description

Reserved Parameter 8 Indicates reserved parameter 8 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 9 Indicates reserved parameter 9 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 10 Indicates reserved parameter 10 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 11 Indicates reserved parameter 11 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 12 Indicates reserved parameter 12 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 13 Indicates reserved parameter 13 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 14 Indicates reserved parameter 14 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 15 Indicates reserved parameter 15 that is reserved for future requirements.
Table 2 Related parameters

Parameter Description

Note on parameter replacement: Reserved parameters are temporarily used in


patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 16 Indicates reserved parameter 16 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 17 Indicates reserved parameter 17 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 18 Indicates reserved parameter 18 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 19 Indicates reserved parameter 19 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 20 Indicates reserved parameter 20 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 21 Indicates reserved parameter 21 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.
5.7.1.6.3.85 eNBLicenseAlmThd
+-NE
+-eNodeBFunction
+-eNBLicenseAlmThd

Description

The eNBLicenseAlmThd MO consists of parameters related to license alarms of an eNodeB. The


parameters include intervals for detecting and clearing license alarms, and thresholds for
generating and clearing license alarms. Currently, this MO applies only to license control items
the Throughput Capacity and the number of RRC Connected User.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the thresholds and intervals related to license alarms.
ENBLICENSEALMTHD
Currently, this command applies only to license control items the Throughput
Capacity and the RRC Connected User.

SET Use this command to set the thresholds and intervals related to license alarms.
ENBLICENSEALMTHD
Currently, this command applies only to license control items the Throughput
Capacity and the RRC Connected User.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

OPRD Indicates the interval for detecting license-related alarms. The eNodeB detects
license control items every other interval and reports a license-related alarm if
the corresponding reporting condition is met.

OTHD Indicates the threshold for generating license alarms. A license alarm is
generated if the proportion of the actually used value to the allocated value of
the license control item exceeds this threshold.

RPRD Indicates the interval for clearing license alarms. During this interval, the
eNodeB detects license control items and clears license alarms if the condition
for clearing license alarms is met.

RTHD Indicates the threshold for clearing license alarms. A license alarm is cleared if
the proportion of the actually used value to the allocated value of the license
control item is below this threshold.

5.7.1.6.3.86 eNBQciRsvdPara
+-NE
+-eNodeBFunction
+-eNBQciRsvdPara

Description

An eNBQciRsvdPara MO consists of the QCI parameters that are reserved for future
requirements.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Relation with the eNodeBFunction MO:


- The number of eNBQciRsvdPara MOs must be 9.
Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list reserved QCI parameters.


ENBQCIRSVDPARA

MOD Use this command to modify reserved QCI parameters.


ENBQCIRSVDPARA

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

QoS Class Indication Indicates the QoS class identifier (QCI) of an evolved packet system (EPS)
bearer. Different QCIs indicate different QoS requirements, such as the packet
delay budget, packet error loss rate, and resource type. For details, see Table
6.1.7 in 3GPP TS 23.203.

Reserved Switch Indicates reserved 32-bit switch parameter 0 that is reserved for future
Parameter 0
requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Switch Indicates reserved 32-bit switch parameter 1 that is reserved for future
Parameter 1
requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Switch Indicates reserved 32-bit switch parameter 2 that is reserved for future
Parameter 2
requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
Table 2 Related parameters

Parameter Description

parameter.

Reserved Parameter 2 Indicates reserved parameter 2 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 3 Indicates reserved parameter 3 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 4 Indicates reserved parameter 4 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 5 Indicates reserved parameter 5 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 6 Indicates reserved parameter 6 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 7 Indicates reserved parameter 7 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 8 Indicates reserved parameter 8 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
Table 2 Related parameters

Parameter Description

parameter.

Reserved Parameter 9 Indicates reserved parameter 9 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 10 Indicates reserved parameter 10 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 11 Indicates reserved parameter 11 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 12 Indicates reserved parameter 12 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 13 Indicates reserved parameter 13 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 14 Indicates reserved parameter 14 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 15 Indicates reserved parameter 15 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
Table 2 Related parameters

Parameter Description

parameter.

Reserved Parameter 16 Indicates reserved parameter 16 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 17 Indicates reserved parameter 17 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 18 Indicates reserved parameter 18 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 19 Indicates reserved parameter 19 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 20 Indicates reserved parameter 20 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 21 Indicates reserved parameter 21 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

5.7.1.6.3.87 eNBRsvdPara
+-NE
+-eNodeBFunction
+-eNBRsvdPara

Description

An eNBRsvdPara MO consists of the eNodeB-level parameters that are reserved for future
requirements.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST ENBRSVDPARA Use this command to list reserved eNodeB-level parameters.

MOD ENBRSVDPARA Use this command to modify reserved eNodeB-level parameters.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Reserved Switch Indicates reserved 32-bit switch parameter 0 that is reserved for future
Parameter 0
requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
Table 2 Related parameters

Parameter Description

a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Switch Indicates reserved 32-bit switch parameter 1 that is reserved for future
Parameter 1
requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Switch Indicates reserved 32-bit switch parameter 2 that is reserved for future
Parameter 2
requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 2 Indicates reserved parameter 2 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 3 Indicates reserved parameter 3 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 4 Indicates reserved parameter 4 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 5 Indicates reserved parameter 5 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 6 Indicates reserved parameter 6 that is reserved for future requirements.
Table 2 Related parameters

Parameter Description

Note on parameter replacement: Reserved parameters are temporarily used in


patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 7 Indicates reserved parameter 7 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 8 Indicates reserved parameter 8 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 9 Indicates reserved parameter 9 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 10 Indicates reserved parameter 10 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 11 Indicates reserved parameter 11 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 12 Indicates reserved parameter 12 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 13 Indicates reserved parameter 13 that is reserved for future requirements.
Table 2 Related parameters

Parameter Description

Note on parameter replacement: Reserved parameters are temporarily used in


patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 14 Indicates reserved parameter 14 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 15 Indicates reserved parameter 15 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 16 Indicates reserved parameter 16 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 17 Indicates reserved parameter 17 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 18 Indicates reserved parameter 18 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 19 Indicates reserved parameter 19 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 20 Indicates reserved parameter 20 that is reserved for future requirements.
Table 2 Related parameters

Parameter Description

Note on parameter replacement: Reserved parameters are temporarily used in


patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

Reserved Parameter 21 Indicates reserved parameter 21 that is reserved for future requirements.
Note on parameter replacement: Reserved parameters are temporarily used in
patch versions and will be replaced with new parameters. For example, the ID of
a new parameter can signify the parameter function. Therefore, avoid using this
parameter.

5.7.1.6.3.88 ENodeBAlgoSwitch
+-NE
+-eNodeBFunction
+-ENodeBAlgoSwitch

Description

The ENodeBAlgoSwitch MO consists of the switches related to eNodeB-level algorithms,which


are applicable to all the cells and admitted UEs of the eNodeB.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

LST Use this command to list the settings of eNodeB-level algorithm switches.
ENODEBALGOSWITC
H

MOD Use this command to modify the configuration of eNodeB-level algorithm


ENODEBALGOSWITC
H switches.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Handover Algo switch Indicates the collective switch used to enable or disable.
IntraFreqCoverHoSwitch: If this switch is turned on, coverage-based intra-
frequency handovers are enabled to ensure service continuity. If this switch is
turned off, coverage-based intra-frequency handovers are disabled.
InterFreqCoverHoSwitch: If this switch is turned on, coverage-based inter-
frequency handovers are enabled to ensure service continuity. If this switch is
turned off, coverage-based inter-frequency handovers are disabled.
UtranCsfbSwitch: If this switch is turned on, CSFB to UTRAN is enabled and
UEs can fall back to UTRAN. If this switch is turned off, CSFB to UTRAN is
disabled.
GeranCsfbSwitch: If this switch is turned on, CSFB to GERAN is enabled and
UEs can fall back to GERAN . If this switch is turned off, CSFB to GERAN is
disabled.
Cdma1xRttCsfbSwitch: If this switch is turned on, CSFB to CDMA2000 1xRTT
is enabled and UEs can fall back to CDMA2000 1xRTT. If this switch is turned
off, CSFB to CDMA2000 1xRTT is disabled.
UtranServiceHoSwitch: If this switch is turned on, service-based handovers to
UTRAN are enabled and UEs with a specific type of services can be handed
over to UTRAN. If this switch is turned off, service-based handovers to UTRAN
are disabled.
GeranServiceHoSwitch: If this switch is turned on, service-based handovers to
GERAN are enabled and UEs with a specific type of services can be handed
over to GERAN . If this switch is turned off, service-based handovers to
GERAN are disabled.
CdmaHrpdServiceHoSwitch: If this switch is turned on, service-based
handovers to CDMA2000 HRPD are enabled and UEs with a specific type of
Table 2 Related parameters

Parameter Description

services can be handed over to CDMA2000 HRPD. If this switch is turned off,
service-based handovers to CDMA2000 HRPD are disabled.
Cdma1xRttServiceHoSwitch: If this switch is turned on, service-based
handovers to CDMA2000 1xRTT are enabled and UEs with a specific type of
services can be handed over to CDMA2000 1xRTT. If this switch is turned off,
service-based handovers to CDMA2000 1xRTT are disabled.
UlQualityInterRATHoSwitch: If this switch is turned on, UL-quality-based
inter-RAT handovers are enabled and UEs can be handed over to inter-RAT cells
to ensure service continuity when the UL signal quality is poor. If this switch is
turned off, UL-quality-based inter-RAT handovers are disabled.
InterPlmnHoSwitch: If this switch is turned on, inter-PLMN handovers are
enabled and UEs can be handed over to cells in other PLMNs. If this switch is
turned off, inter-PLMN handovers are disabled.
UtranFlashCsfbSwitch: This switch takes effect only when UtranCsfbSwitch is
turned on. If UtranFlashCsfbSwitch is turned on, flash CSFB to UTRAN is
enabled and the eNodeB sends system information of candidate target UTRAN
cells to UEs during redirection. If UtranFlashCsfbSwitch is turned off, flash
CSFB to UTRAN is disabled.
GeranFlashCsfbSwitch: This switch takes effect only when GeranCsfbSwitch is
turned on. If GeranFlashCsfbSwitch is turned on, flash CSFB to GERAN is
enabled and the eNodeB sends system information of candidate target GERAN
cells to UEs during redirection. If GeranFlashCsfbSwitch is turned off, flash
CSFB to GERAN is disabled.
ServiceBasedInterFreqHoSwitch: If this switch is turned on, service-based inter-
frequency handovers are enabled and UEs with a specific type of services can be
handed over to inter-frequency cells. If this switch is turned off, service-based
inter-frequency handovers are disabled.
UlQualityInterFreqHoSwitch: If this switch is turned on, UL-quality-based inter-
frequency handovers are enabled and UEs can be handed over to inter-frequency
cells to ensure service continuity when the UL signal quality is poor. If this
switch is turned off, UL-quality-based inter-frequency handovers are disabled.
CsfbAdaptiveBlindHoSwitch: This switch takes effect only when
BlindHoSwitch is enabled. If CsfbAdaptiveBlindHoSwitch is turned on,
adaptive blind handovers for CSFB are enabled and appropriate handover
mechanisms are selected for UEs based on their locations. If
CsfbAdaptiveBlindHoSwitch is turned off, adaptive blind handovers for CSFB
are disabled.
UtranCsfbSteeringSwitch: If this switch is turned on, CSFB steering to UTRAN
is enabled and CSFB policies for idle UEs can be configured. If this switch is
turned off, CSFB steering to UTRAN is disabled.
GeranCsfbSteeringSwitch: If this switch is turned on, CSFB steering to GERAN
is enabled and CSFB policies for idle UEs can be configured. If this switch is
turned off, CSFB steering to GERAN is disabled.
Table 2 Related parameters

Parameter Description

CSFBLoadInfoSwitch: If this switch is turned on, load-based CSFB is enabled


and a target cell for CSFB is selected based on loads of candidate target cells. If
this switch is turned off, load-based CSFB is disabled.
Cdma1XrttEcsfbSwitch: If this switch is turned on, eCSFB to CDMA2000
1xRTT is enabled and UEs can fall back to CDMA2000 1xRTT through
handovers. If this switch is turned off, eCSFB to CDMA2000 1xRTT is
disabled.
EmcBlindHoA1Switch: If this switch is turned on, blind handover event A1
measurements are enabled. If a blind handover event measurement conflicts with
a handover procedure, an emergency blind handover can be triggered after the
handover procedure is complete. If this switch is turned off, blind handover
event A1 measurements are disabled. If a blind handover event measurement
conflicts with a handover procedure, an emergency blind handover cannot be
triggered.
EmcInterFreqBlindHoSwitch: If this switch is turned on, the eNodeB
preferentially performs an inter-frequency blind handover when an emergency
blind handover is triggered. If this switch is turned off, the eNodeB only
performs an inter-RAT blind handover when an emergency blind handover is
triggered.

Handover Mode switch Indicates the switches corresponding to the inputs based on which the eNodeB
determines handover policies.
EutranVoipCapSwitch: This switch will be removed in later versions. In this
version, the setting of this switch is still synchronized between the M2000 and
the eNodeB, but it is no longer used internally. Therefore, avoid using this
switch.
UtranVoipCapSwitch: If this switch is turned on, UTRAN supports VoIP. If this
switch is turned off, UTRAN does not support VoIP.
GeranVoipCapSwitch: If this switch is turned on, GERAN supports VoIP. If this
switch is turned off, GERAN does not support VoIP.
Cdma1xRttVoipCapSwitch: If this switch is turned on, CDMA2000 1xRTT
supports VoIP. If this switch is turned off, CDMA2000 1xRTT does not support
VoIP.
UtranPsHoSwitch: If this switch is turned on, UTRAN supports PS handovers.
If this switch is turned off, UTRAN does not support PS handovers.
GeranPsHoSwitch: If this switch is turned on, GERAN supports PS handovers.
If this switch is turned off, GERAN does not support PS handovers.
CdmaHrpdNonOtpimisedHoSwitch: If this switch is turned on, non-optimized
handovers to CDMA2000 HRPD are enabled. If this switch is turned off, non-
optimized handovers to CDMA2000 HRPD are disabled.
CdmaHrpdOptimisedHoSwitch: If this switch is turned on, optimized handovers
to CDMA2000 HRPD are enabled. If this switch is turned off, optimized
Table 2 Related parameters

Parameter Description

handovers to CDMA2000 HRPD are disabled.


GeranNaccSwitch: This switch does not take effect if GeranCcoSwitch is
disabled. If this switch is turned on, GERAN supports network assisted cell
change (NACC). If this switch is turned off, GERAN does not support NACC.
GeranCcoSwitch: If this switch is turned on, GERAN supports cell change order
(CCO). If this switch is turned off, GERAN does not support CCO.
UtranSrvccSwitch: If this switch is turned on, UTRAN supports single radio
voice call continuity (SRVCC). If this switch is turned off, UTRAN does not
support SRVCC.
GeranSrvccSwitch: If this switch is turned on, GERAN supports SRVCC. If this
switch is turned off, GERAN does not support SRVCC.
Cdma1xRttSrvccSwitch: If this switch is turned on, CDMA2000 1xRTT
supports SRVCC. If this switch is turned off, CDMA2000 1xRTT does not
support SRVCC.
UtranRedirectSwitch: If this switch is turned on, redirection to UTRAN is
enabled. If this switch is turned off, redirection to UTRAN is disabled.
GeranRedirectSwitch: If this switch is turned on, redirection to GERAN is
enabled. If this switch is turned off, redirection to GERAN is disabled.
CdmaHrpdRedirectSwitch: If this switch is turned on, redirection to
CDMA2000 HRPD is enabled. If this switch is turned off, redirection to
CDMA2000 HRPD is disabled.
Cdma1xRttRedirectSwitch: If this switch is turned on, redirection to
CDMA2000 1xRTT is enabled. If this switch is turned off, redirection to
CDMA2000 1xRTT is disabled.
BlindHoSwitch: If this switch is turned on, blind handovers for CSFB are
enabled. If this switch is turned off, blind handovers for CSFB are disabled.
LcsSrvccSwitch: If this switch is turned on, an SRVCC procedure is triggered
when a UE receives a CSFB instruction during a VoIP service. If this switch is
turned off, an SRVCC procedure is not triggered when a UE receives a CSFB
instruction during a VoIP service.
AutoGapSwitch: If this switch is turned on and UEs support automatic
measurement gap configurations on the target frequency, the eNodeB does not
deliver gap configurations to UEs. If this switch is turned off, the eNodeB
delivers gap configurations to UEs during all inter-frequency and inter-RAT
measurements.

DlIcic algorithm switch Indicates the DL ICIC algorithm switch. There are four states.
DlIcicSwitch_OFF_ENUM:Indicates that DL ICIC is disabled.
DlIcicDynamicSwitch_ON_ENUM:Indicates that dynamic DL ICIC is enabled.
DlIcicStaticSwitch_ON_ENUM:Indicates that static DL ICIC is enabled.
DlIcicReuse3Switch_ON_ENUM: This state will be removed in later versions.
Table 2 Related parameters

Parameter Description

In this version, the setting of this state is still synchronized between the M2000
and the eNodeB, but it is no longer used internally. Therefore, avoid using this
state.

ANR algorithm switch Indicates the automatic neighbor relation (ANR) algorithm switch. Switches
related to ANR are described as follows:
IntraRatEventAnrSwitch: If this switch is turned on, intra-RAT event-triggered
ANR is enabled to construct and optimize intra-RAT neighboring relations by
triggering intra-RAT coverage-based handover events and inter-frequency MLB.
Inter-frequency MLB-based event-triggered ANR can be performed only when
the MlbBasedEventAnrSwitch is turned on.
IntraRatFastAnrSwitch: If this switch is turned on, intra-RAT fast ANR is
enabled to construct and optimize intra-RAT neighboring relations by
performing periodic intra-RAT measurements.
IntraRatAnrAutoDelSwitch: If this switch is turned on, IntraRatEventAnrSwitch
is turned on, No remove indicator of an intra-RAT neighboring cell is set to
PERMIT_RMV_ENUM, and Control Mode is set to AUTO_MODE, automatic
removal of the neighboring relation with intra-RAT cells is allowed. If
IntraRatAnrAutoDelSwitch is turned off, automatic removal of the neighboring
relation with intra-RAT cells is not allowed.
UtranEventAnrSwitch: If this switch is turned on, event-triggered ANR with
UTRAN is enabled to construct and optimize inter-RAT neighboring relations
with UTRAN cells by triggering events for inter-RAT coverage-based handovers
to UTRAN and inter-RAT MLB to UTRAN. Event-triggered ANR based on
inter-RAT MLB to UTRAN can be performed only when the
MlbBasedEventAnrSwitch is turned on.
GeranEventAnrSwitch: If this switch is turned on, event-triggered ANR with
GERAN is enabled to construct and optimize inter-RAT neighboring relations
with GERAN cells by triggering events for inter-RAT coverage-based handovers
to GERAN and inter-RAT MLB to GERAN.Event-triggered ANR based on
inter-RAT MLB to GERAN can be performed only when the
MlbBasedEventAnrSwitch is turned on.
UtranFastAnrSwitch: If this switch is turned on, fast ANR with UTRAN is
enabled to construct and optimize inter-RAT neighboring relations with UTRAN
cells based on periodic UE measurements on UTRAN. The eNodeB does not
deliver information about external UTRAN cells in the measurement
configuration to UEs and the UEs measure only neighboring cells contained in
the measurement configuration. Therefore, if you want external UTRAN cells
added by fast ANR with UTRAN to be measured in handovers, you are advised
to turn on UtranEventAnrSwitch as well.
GeranFastAnrSwitch: If this switch is turned on, fast ANR with GERAN is
enabled to construct and optimize inter-RAT neighboring relations with GERAN
cells by performing periodic inter-RAT measurements on GERAN.
Table 2 Related parameters

Parameter Description

CdmaFastAnrSwitch: If this switch is turned on, fast ANR with CDMA2000 is


enabled to construct and optimize inter-RAT neighboring relations with
CDMA2000 cells by performing periodic inter-RAT measurements on
CDMA2000 networks.
UtranAutoNrtDeleteSwitch: If this switch is turned on, UtranEventAnrSwitch is
turned on, No remove indicator of a neighboring UTRAN cell is set to
PERMIT_RMV_ENUM, and Control Mode is set to AUTO_MODE, automatic
removal of the inter-RAT neighboring relation with UTRAN cells is allowed. If
UtranAutoNrtDeleteSwitch is turned off, automatic removal of the inter-RAT
neighboring relation with UTRAN cells is not allowed.
GeranAutoNrtDeleteSwitch: If this switch is turned on, GeranEventAnrSwitch
is turned on, No remove indicator of a neighboring GERAN cell is set to
PERMIT_RMV_ENUM, and Control Mode is set to AUTO_MODE, automatic
removal of the inter-RAT neighboring relation with GERAN cells is allowed. If
GeranAutoNrtDeleteSwitch is turned off, automatic removal of the inter-RAT
neighboring relation with GERAN cells is not allowed.
CdmaAutoNrtDeleteSwitch: If this switch is turned on, CdmaEventAnrSwitch is
turned on, No remove indicator of a neighboring CDMA2000 cell is set to
PERMIT_RMV_ENUM, and Control Mode is set to AUTO_MODE, automatic
removal of the inter-RAT neighboring relation with CDMA2000 cells is
allowed. If CdmaAutoNrtDeleteSwitch is turned off, automatic removal of the
inter-RAT neighboring relation with CDMA2000 cells is not allowed.
ExtendIntraRatAnrSwitch: This switch is used to control whether cells with
unknown physical cell identifiers (PCIs) can be configured as external cells of
the eNodeB by using the eCoordinator. If this switch is turned on, cells with
unknown PCIs can be configured as external cells of the eNodeB by using the
eCoordinator in any of the following scenarios: (1) When unknown PCIs are
detected by triggering handover events, IntraRatEventAnrSwitch is turned off or
the UE is incapable of measuring cell global identifications (CGIs). (2) When
unknown PCIs are detected by performing periodic intra-RAT measurements,
the UE is incapable of measuring CGIs. This parameter will be removed in later
versions. In this version, the setting of this parameter is still synchronized
between the M2000 and the eNodeB, but it is no longer used internally.
Therefore, avoid using this parameter.
CdmaEventAnrSwitch: If this switch is turned on, event-triggered ANR with
CDMA2000 is enabled to construct and optimize inter-RAT neighbor relations
with CDMA2000 cells by triggering events for inter-RAT handovers to
CDMA2000.
MlbBasedEventAnr:Indicates whether to enable the MLB-based event-triggered
ANR. When this switch is turned on and the intra-RAT event-triggered ANR is
enabled, inter-frequency MLB can be triggered to construct and optimize inter-
frequency neighboring relations with intra-RAT cells.When this switch is turned
on and event-triggered ANR with UTRAN is enabled, MLB to UTRAN can be
Table 2 Related parameters

Parameter Description

triggered to construct and optimize inter-RAT neighboring relations with


UTRAN cells.When this switch is turned on and event-triggered ANR with
GERAN is enabled, MLB to GERAN can be triggered to construct and optimize
inter-RAT neighboring relations with GERAN cells.When this switch is turned
off, the neighboring relation construction and optimization based on MLB is not
enabled.

Redirection switch Indicates the switch used to enable or disable the redirection algorithm. This
switch does not control redirection or fast redirection for CSFB.
GeranFlashRedirectSwitch: If this switch and GeranRedirectSwitch are turned
on, fast redirection to GERAN can be performed.
UranFlashRedirectSwitch: If this switch and UtranRedirectSwitch are turned on,
fast redirection to UTRAN can be performed.
LoadBasedSwitch: If this switch is turned on, load based redirection can be
performed.

MRO algorithm switch Indicates the switches for Mobility Robustness Optimization (MRO) algorithms.
IntraFreqMroSwitch: If this switch is turned on, the eNodeB can dynamically
adjust the intra-frequency handover parameters to decrease the number of
abnormal handovers (including premature handovers, delayed handovers, ping-
pong handovers, and handovers to wrong cells), thereby increasing the intra-
frequency handover success rate. If this switch is turned off, the adjustment is
not performed.
InterFreqMroSwitch: If this switch is turned on, the eNodeB can dynamically
adjust the inter-frequency handover parameters to decrease the number of
abnormal handovers (including premature handovers, delayed handovers, ping-
pong handovers, and handovers to wrong cells), thereby increasing the inter-
frequency handover success rate. If this switch is turned off, the adjustment is
not performed.
UtranMroSwitch: If this switch is turned on, the eNodeB can dynamically adjust
the UTRAN handover parameters to decrease the number of abnormal
handovers (including premature handovers and delayed handovers), thereby
increasing the success rate of handovers to UTRAN. If this switch is turned off,
the adjustment is not performed.
GeranMroSwitch: If this switch is turned on, the eNodeB can dynamically adjust
the GERAN handover parameters to decrease the number of abnormal
handovers (including premature handovers and delayed handovers), thereby
increasing the success rate of handovers to GERAN. If this switch is turned off,
the adjustment is not performed.
UEMroSwitch: If this switch is turned on, the eNodeB can dynamically adjust
the UE handover parameters to decrease the number of ping-pong handovers,
thereby increasing the UEs' handover success rate. If this switch is turned off,
the adjustment is not performed.
Table 2 Related parameters

Parameter Description

TPE switch Indicates the switch for the TCP Proxy Enhancer (TPE) algorithm. The TPE
algorithm increases the rates of TCP services by measures such as ACK
splitting. If this switch is turned on, the TPE algorithm is enabled. In this
situation, the algorithm is valid only for UEs that newly access or reaccess the
network. If this switch is turned off, the TPE algorithm is disabled.

UlIcic time switch This parameter will be removed in later versions. In this version, the setting of
this parameter is still synchronized between the M2000 and the eNodeB, but it is
no longer used internally. Therefore, avoid using this parameter.

UlIcic freq switch Indicates the switch used to enable or disable UL ICIC in the frequency domain.
If this switch is set to OFF, UL ICIC in the frequency domain is disabled in the
eNodeB cells. If this switch is set to STATIC, static UL ICIC in the frequency
domain is enabled in the eNodeB cells. If this switch is set to DYNAMIC,
dynamic UL ICIC in the frequency domain is enabled in the eNodeB
cells,Dynamic ICIC and static ICIC will not take effect when the UL adaptive
ICIC switch of the cell is turned on.

LCS switch Indicates the location services (LCS) switch. OtdoaSwitch: If the switch is
turned on, observed time difference of arrival-based (OTDOA-based)
positioning is enabled. If the switch is turned off, OTDOA-based positioning is
disabled.

TRM switch Indicates the switch for uplink flow control over the air interface. If this switch
is turned on, the scheduling algorithm is notified to limit the uplink data rate of
UEs in the case of uplink congestion. This method prevents uplink congestion in
the eNodeB, but may affect fairness and differentiation for combined services. If
this switch is turned off, the scheduling algorithm is not notified and therefore
no rate restriction is applied to uplink data from UEs in the case of uplink
congestion. In this case, uplink congestion may occur in the eNodeB, but
fairness and differentiation for combined services are ensured.
A UE is considered to have combined services if the UE has two or more flow-
controllable non-GBR bearers. Fairness and differentiation for combined
services of a UE are ensured if the uplink scheduling algorithm allocates
bandwidths to these flow-controllable non-GBR bearers based on weighting
factors for uplink scheduling priorities (UlschPriorityFactor). If this switch is
turned on, the scheduling algorithm is notified to limit the number of resource
blocks (RBs) allocated to the UE in the case of uplink congestion. According to
the related specifications, however, the scheduling algorithm cannot decide how
many RBs to be allocated to each bearer. The number of RBs that each non-
GBR bearer can use is determined based on the prioritized bit rates (PBRs) and
priorities of the associated logical channels rather than based on
UlschPriorityFactor. As a result, if this switch is turned on, fairness and
differentiation for combined services of a UE may be affected.
Table 2 Related parameters

Parameter Description

PCI conflict alarm Indicates the switch for reporting the PCI conflict alarm. If this switch is turned
switch
on, an alarm is reported in case of PCI collision or PCI confusion to notify users.
If this switch is turned off, alarms related to PCI conflict are not reported.

Power save switch Indicates the switch used to enable or disable the eNodeB-level energy
conservation function. This function is achieved through the symbol-based
power amplifier (PA) shutdown. Symbol-based PA shutdown is applicable in
single-mode eNodeBs. If this function is enabled, the eNodeB shuts down power
amplifiers (PAs) on the corresponding RF unit when it detects no signal
transmitted on OFDM symbols in DL subframes. This reduces static power
consumption and hence conserves energy for the eNodeB.

RIM switch Indicates the collective switch for the RAN information management (RIM)
function. UTRAN_RIM_SWITCH: Indicates the switch used to enable or
disable the RIM procedure that requests event-driven multiple reports from
UTRAN cells. If this switch is turned on, the eNodeB can send RAN-
INFORMATION-REQUEST protocol data units (PDUs) to UTRAN cells to
request multiple event-driven reports. If this switch is turned off, the eNodeB
cannot send RAN-INFORMATION-REQUEST PDUs to UTRAN cells to
request multiple event-driven reports. GERAN_RIM_SWITCH: Indicates the
switch used to enable or disable the RIM procedure that requests event-driven
multiple reports from GERAN cells. If this switch is turned on, the eNodeB can
send RAN-INFORMATION-REQUEST PDUs to CERAN cells to request
multiple event-driven reports. If this switch is turned off, the eNodeB cannot
send RAN-INFORMATION-REQUEST PDUs to GERAN cells to request
multiple event-driven reports.

ANR Under RAN Indicates the ANR algorithm switch in RAN sharing mode. Related switches are
Sharing Algorithm
Switch described as follows:
NBSLTEPLMNRoundSwitch: If this switch is turned on, some neighboring
eNodeBs provide cells that work in RAN sharing mode and broadcast their
PLMN lists in a round robin (RR) manner. In this situation, if
IntraRatEventAnrSwitch or IntraRatFastAnrSwitch is turned on for the local
eNodeB, the local eNodeB will ask the M2000 for the actual cell global
identifier (CGI) and PLMN list for a cell broadcasting PLMNs in an RR manner
after the UE reports the CGI of the cell during ANR measurements. If both
NBSLTEPLMNRoundSwitch and NBSLTERANSharingSwitch are turned on,
NBSLTEPLMNRoundSwitch overrides NBSLTERANSharingSwitch.
NBSLTERANSharingSwitch: If this switch is turned on, some neighboring
eNodeBs provide cells that work in RAN sharing mode. In this situation, if
IntraRatEventAnrSwitch or IntraRatFastAnrSwitch is turned on for the local
eNodeB, the local eNodeB will ask the M2000 for the PLMN list for a cell after
the UE reports the CGI of the cell during ANR measurements. If the UE has
reported the PLMNlist, the local eNodeB will not ask the M2000 for the PLMN
Table 2 Related parameters

Parameter Description

list.
NBSUTRANRANSharingSwitch: If this switch is turned on, some neighboring
NodeBs provide cells that work in UTRAN sharing mode. In this situation, if
UtranEventAnrSwitch or UtranFastAnrSwitch is turned on for the local eNodeB,
the local eNodeB will ask the M2000 for the PLMN list for a cell after the UE
reports the CGI of the cell during ANR measurements. If the UE has reported
the PLMNlist, the local eNodeB will not ask the M2000 for the PLMN list.
NBSGERANRANSharingSwitch: If this switch is turned on, some neighboring
BTSs provide cells that work in GERAN sharing mode. In this situation, if
GeranEventAnrSwitch or GeranFastAnrSwitch is turned on for the local
eNodeB, the local eNodeB will ask the M2000 for the PLMN list for a cell after
the UE reports the CGI of the cell during ANR measurements.

Frequency Layer This parameter includes the following three switches:


Switch
UtranFreqLayerMeasSwitch, UtranFreqLayerBlindSwitch, and
UtranSrvccSwitch. UtranSrvccSwitch takes effect only when
UtranFreqLayerMeasSwitch is turned on. If UtranFreqLayerMeasSwitch is
turned on, the UTRAN hierarchy-based measurement algorithm takes effect for
measurements related to coverage-based and CSFB-triggered handovers from
EUTRAN to UTRAN. If UtranFreqLayerBlindSwitch is turned on, the UTRAN
hierarchy-based blind-handover algorithm takes effect for coverage-based and
CSFB-triggered blind handovers from EUTRAN to UTRAN. If
UtranSrvccSwitch is turned on, the UTRAN SRVCC hierarchy-based
measurement algorithm takes effect for SRVCC-triggered handovers from
EUTRAN to UTRAN.

Cmas Switch Indicates the switch controls whether to enable the eNodeB to broadcast alerting
messages based on the eNodeB-level commercial mobile alert system (CMAS).

Voice quality monitoring Indicates the switch controls whether to enable the eNodeB to periodically select
algo switch
UEs performing voice services and evaluate voice quality based on the voice
quality monitoring (VQM) algorithm. It is recommended that this parameter be
set to VQM_ALGO_SWITCH_ON when voice services are encoded based on
adaptive multirate (AMR).

UE number preemption Indicates the switch used to enable or disable the preemption based on the
switch
number of users. IntraOpUeNumPreemptSwitch: This parameter indicates the
switch used to enable or disable the intra-operator preemption based on the
number of users. If this switch is turned on, when a user cannot access the
network because of the user number restriction, the user can preempt resources
of other lower-priority users served by the same operator. If this switch is turned
off, preemption is not allowed. InterOpUeNumPreemptSwitch: This parameter
indicates the switch used to enable or disable the inter-operator preemption
based on the number of users. If this switch is turned on, the inter-operator
Table 2 Related parameters

Parameter Description

preemption based on the number of users is allowed. If this switch is turned off,
the inter-operator preemption based on the number of users is not allowed.

5.7.1.6.3.89 eNodeBAutoPowerOff
+-NE
+-eNodeBFunction
+-eNodeBAutoPowerOff

Description

The eNodeBAutoPowerOff MO consists of the parameters related to RF module regular time


sleep in energy conservation and emission reduction.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP Use this command to query the RF module regular time sleep information about
ENODEBAUTOPOWE
ROFF the eNodeB.

LST Use this command to list the RF module regular time sleep configurations about
ENODEBAUTOPOWE
ROFF the eNodeB.
Table 1 Related MML commands

MML Command Function

MOD Use this command to modify the RF module regular time sleep configurations
ENODEBAUTOPOWE
ROFF about the eNodeB.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

RF module sleep switch Indicates the switch for RF module regular time sleep. Cells are unavailable
after the eNodeB enters RF module regular time sleep. After the eNodeB exit RF
module regular time sleep, it is in the normal state.

RF module sleep start Indicates the time for enter RF module regular time sleep.
time

RF module sleep stop Indicates the time for exit RF module regular time sleep.
time

RF module sleep status Indicates whether the eNodeB is RF module regular time sleep. If this parameter
is RF module regular time sleep mode, all cells are unavailable. If this parameter
is normal, the eNodeB runs normally.

5.7.1.6.3.90 eNodeBChrOutputCtrl
+-NE
+-eNodeBFunction
+-eNodeBChrOutputCtrl

Description

The eNodeBChrOutputCtrl MO is used to configure mode of outputting internal call history


records (CHRs).

Effective Scenario
Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the eNodeB call history record (CHR) output control
ENODEBCHROUTPUT
CTRL settings.

MOD Use this command to modify the eNodeB call history record (CHR) output
ENODEBCHROUTPUT
CTRL control settings.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

CHR Output Mode Indicates the mode of outputting call history records (CHRs).ALL_OUTPUT
means both normal and abnormal calls are output. When there is no storage
space for new CHRs, a new record will cover the beginning
one.ABNORMAL_NORMAL_SAMPLE means calls are output based on the
storage space and the proportion of normalcalls to abnormal calls. Ensure that
CHR recording time meets the
requirement.ABNORMAL_ALL_NORMAL_SAMPLE means all abnormal
calls are output and the normal calls are output based on the proportion of
normal calls to abnormal calls.

Sample Rate of Indicates the percentage of CHRs for abnormal calls in the CHR output. For
Abnomal Call
example, if this parameter is set to 90, the percentage of CHRs for abnormal
calls in the CHR output is 90% and that of CHRs for normal calls is 10%. This
parameter is invalid when CHR Output Mode is set to ALL_OUTPUT. This
parameter takes effect immediately after being set or modified, and the CHR
Table 2 Related parameters

Parameter Description

output will be refreshed.

Max Store Call Indicateds the maximum number of internal call history records (CHR) be
stored. For example, if this parameter is set to 4000, 4000 CHRs can be stored.
(The size of a CHR for one call is about 6 KB, and the storage space is 24 MB.)
This parameter is invalid when CHR Output Mode is set to ALL_OUTPUT or
ABNORMAL_ALL_NORMAL_SAMPLE. When CHR Output Mode is set to
ABNORMAL_NORMAL_SAMPLE, the value of this parameter indicates the
expected number of CHRs that can be stored, and you are advised to estimate
the value of this parameter based on the actual storage space and the size of a
CHR.

5.7.1.6.3.91 ENodeBCipherCap
+-NE
+-eNodeBFunction
+-ENodeBCipherCap

Description

The ENodeBCipherCap MO consists of the parameters related to the priorities of eNodeB


ciphering algorithms. After being ciphered on the radio interface, data is converted from
plaintext into ciphertext to provide confidentiality. If the integrity protection algorithm is set to
NULL, the ciphering algorithm is also NULL.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

LST Use this command to list the priorities of the eNodeB ciphering algorithms.
ENODEBCIPHERCAP

MOD Use this command to modify the priorities of the eNodeB ciphering algorithms.
ENODEBCIPHERCAP

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Primary cipher Indicates the highest-priority ciphering algorithm supported by the eNodeB. The
algorithm
value NULL indicates that ciphering is not applied.

Second cipher Indicates the second-priority ciphering algorithm supported by the eNodeB. The
algorithm
value NULL indicates that ciphering is not applied.

Third cipher algorithm Indicates the third-priority ciphering algorithm supported by the eNodeB. The
value NULL indicates that ciphering is not applied.

Fourth cipher algorithm Indicates the fourth-priority ciphering algorithm supported by the eNodeB. The
value NULL indicates that ciphering is not applied.

5.7.1.6.3.92 ENodeBConnStateTimer
+-NE
+-eNodeBFunction
+-ENodeBConnStateTimer

Description

The ENodeBConnStateTimer MO consists of parameters related to the timers indicating eNodeB


connection states.

Effective Scenario
Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the eNodeB connection state timers.
ENODEBCONNSTATE
TIMER

MOD Use this command to modify the eNodeB connection state timers.
ENODEBCONNSTATE
TIMER

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

S1 Message Waiting Indicates the timer governing the period the eNodeB will wait for a response
Timer
message from the MME.

X2 Message Waiting Indicates the timer governing the period the eNodeB will wait for a response
Timer
message from the neighboring eNodeB.

UU Message Waiting Indicates the timer governing the period the eNodeB will wait for a response
Timer
message from a UE.

CDMA2000 1xRTT HO Indicates the timer for the eNodeB to wait for a handover preparation
Uu Prepare Timer
completion message when a UE is handed over to a CDMA2000 1xRTT cell.
The eNodeB starts the timer after sending a Handover From EUTRA Preparation
Request message to the UE and stops the timer after receiving a UL Handover
Preparation Transfer message from the UE.
Table 2 Related parameters

Parameter Description

CDMA2000 1xRTT HO Indicates the timer for the eNodeB to wait for a Downlink S1 CDMA2000
S1 Waiting Timer
Tunneling message when a UE is handed over to a CDMA2000 1xRTT cell. The
eNodeB starts the timer after sending an UPLINK S1 CDMA2000
TUNNELING message to the MME and stops the timer after receiving a
Downlink S1 CDMA2000 Tunneling message containing CDMA2000 HO
Status.

CDMA2000 1xRTT HO Indicates the timer for the eNodeB to release resources for a UE after the UE is
Complete Timer
handed over to a CDMA2000 1xRTT cell. The eNodeB starts the timer after
sending a MobilityFromEUTRACommand message.

CDMA2000 HRPD HO Indicates the timer for the eNodeB to release resources for a UE after the UE is
Complete Timer
handed over to a CDMA2000 HRPD cell. The eNodeB starts the timer after
sending a MobilityFromEUTRACommand message.

CDMA2000 HRPD HO Indicates the timer for the eNodeB to wait for a Downlink S1 CDMA2000
S1 Waiting Timer
Tunneling message when a UE is handed over to a CDMA2000 HRPD cell. The
eNodeB starts the timer after sending an UPLINK S1 CDMA2000
TUNNELING message to the MME and stops the timer after receiving a
Downlink S1 CDMA2000 Tunneling message containing CDMA2000 HO
Status.

CDMA2000 HRPD HO Indicates the timer for the eNodeB to wait for a handover preparation
Uu Prepare Timer
completion message when a UE is handed over to a CDMA2000 HRPD cell.
The eNodeB starts the timer after sending a Handover From EUTRA Preparation
Request message to the UE and stops the timer after receiving a UL Handover
Preparation Transfer message from the UE.

RRCConnSetupCmp Indicates the timer for the eNodeB to wait for a RRC Connection Setup
Waiting Timer
Complete.

SecurityModeComplete Indicates the timer for the eNodeB to wait for a Security Mode Complete
Waiting Timer
message.

Unprotected UeCapInfo Indicates the timer for the eNodeB to wait for an unprotected UE Capability
Waiting Timer
Information message.

First Forward Packet Indicates the timer for the eNodeB to wait for the first forwarded packet.
Timer

End Marker Timer Indicates the timer for the eNodeB to wait for the endmarker packet.
5.7.1.6.3.93 eNodeBFlowCtrlPara
+-NE
+-eNodeBFunction
+-eNodeBFlowCtrlPara

Description

An eNodeBFlowCtrlPara MO consists of parameters AdaptUnsyncUserNumThd and


AdaptUnsyncTimerLen.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the eNodeB Flow Control Parameter.
ENODEBFLOWCTRLP
ARA

MOD Use this command to modify the eNodeB Flow Control Parameter.
ENODEBFLOWCTRLP
ARA

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Adaptive Indicates whether an adaptive asynchronization UE is selected when the


Unsynchronized Timer
Length adaptive asynchronization function is enabled. If a UE does not transmit packets
or receive packets for a period of time that is longer than the
AdaptUnsyncTimerLen parameter value, the UE is a candidate adaptive
asynchronization UE. When this parameter value is larger than or equal to the
UlSynTimer parameter value, the adaptive asynchronization function does not
take effect.

Adaptive Indicates the threshold for the number of UEs that can keep uplink
Unsynchronized User
Num Threshold synchronization in a cell or a baseband processing unit. When the number of
UEs that keep uplink synchronization in a cell or a baseband processing unit
exceeds the threshold, the eNodeB adaptively enables some UEs that do not
transmit or receive data for a period of time that is longer than the
AdaptUnsyncTimerLen parameter value to enter the uplink asynchronization
mod. In this case, uplink control channel resources can be released for other
UEs.

5.7.1.6.3.94 eNodeBFunction
+-NE
+-eNodeBFunction
+-RatFreqPriorityGroup[0~2048]
+-SpidCfg[0~256]
+-CSFallBackPolicyCfg[1~1]
+-ENodeBCipherCap[1~1]
+-SrsAdaptiveCfg[1~1]
+-eNodeBFlowCtrlPara[1~1]
+-TypDrbBsr[9~9]
+-UtranExternalCell[0~2304]
+-IntraRatHoComm[1~1]
+-MRO[1~1]
+-PdcpRohcPara[1~1]
+-HoMeasComm[1~1]
+-S1[0~32]
+-MimoAdaptiveParaCfg[1~1]
+-LicRatio[1~1]
+-Cdma20001XrttExtCell[0~576]
+-X2BlackWhiteList[0~64]
+-BfMimoAdaptiveParaCfg[1~1]
+-TpeAlgo[1~1]
+-TcpMssCtrl[1~1]
+-CnOperatorTa[0~108]
+-eNodeBPath[0~320]
+-eNBLicenseAlmThd[1~1]
+-ExtendedQci[0~60]
+-Drx[1~1]
+-eNBRsvdPara[1~1]
+-SfnAuxResBind[0~144]
+-ANR[1~1]
+-eNodeBChrOutputCtrl[1~1]
+-GlobalProcSwitch[1~1]
+-BfAnt[0~18]
+-AlgoDefaultPara[1~1]
+-StandardQci[9~9]
+-X2Interface[0~96]
+-TddResModeSwitch[1~1]
+-eNBQciRsvdPara[9~9]
+-EutranExternalCell[0~2304]
+-ENodeBAlgoSwitch[1~1]
+-ENodeBConnStateTimer[1~1]
+-GeranExternalCell[0~1152]
+-Cdma2000HrpdExtCell[0~576]
+-TcpAckCtrlAlgo[1~1]
+-S1Interface[0~32]
+-CaGroup[0~18]
+-VQMAlgo[1~1]
+-RlcPdcpParaGroup[6~9]
+-CnOperator[0~6]
+-InterRatHoComm[1~1]
+-SimuLoad[10~10]
+-InterRatPolicyCfgGroup[4~40]
+-eNodeBAutoPowerOff[1~1]
+-S1ReestTimer[1~1]
+-RrcConnStateTimer[1~1]
+-CqiAdaptiveCfg[1~1]
+-PuschParam[1~1]
+-X2[0~12]
+-CellIdPrdUpt[1~1]
+-Cell[0~18]
+-TceIpMapping[0~256]
+-ENodeBIntegrityCap[1~1]
+-CounterCheckPara[1~1]
+-CnOperatorIpPath[0~320]
+-ENodeBSharingMode[1~1]
+-TddFrameOffset[1~1]
+-X2AutoSetupOperator[0~10]

Description

Root node of the eNodeB function domain. The eNodeB function is used for radio access in the
LTE system. It mainly performs radio resource management (RRM) functions such as air
interface management, access control, mobility control, and UE resource allocation.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
NE

Possible children:
RatFreqPriorityGroup[0~2048];SpidCfg[0~256];CSFallBackPolicyCfg[1~1];ENodeBCipherCap[1~1];SrsAdapti
veCfg[1~1];eNodeBFlowCtrlPara[1~1];TypDrbBsr[9~9];UtranExternalCell[0~2304];IntraRatHoComm[1~1];M
RO[1~1];PdcpRohcPara[1~1];HoMeasComm[1~1];S1[0~32];MimoAdaptiveParaCfg[1~1];LicRatio[1~1];Cd
ma20001XrttExtCell[0~576];X2BlackWhiteList[0~64];BfMimoAdaptiveParaCfg[1~1];TpeAlgo[1~1];TcpMssCtrl[
1~1];CnOperatorTa[0~108];eNodeBPath[0~320];eNBLicenseAlmThd[1~1];ExtendedQci[0~60];Drx[1~1];e
NBRsvdPara[1~1];SfnAuxResBind[0~144];ANR[1~1];eNodeBChrOutputCtrl[1~1];GlobalProcSwitch[1~1];Bf
Ant[0~18];AlgoDefaultPara[1~1];StandardQci[9~9];X2Interface[0~96];TddResModeSwitch[1~1];eNBQciRsv
dPara[9~9];EutranExternalCell[0~2304];ENodeBAlgoSwitch[1~1];ENodeBConnStateTimer[1~1];GeranExtern
alCell[0~1152];Cdma2000HrpdExtCell[0~576];TcpAckCtrlAlgo[1~1];S1Interface[0~32];CaGroup[0~18];VQ
MAlgo[1~1];RlcPdcpParaGroup[6~9];CnOperator[0~6];InterRatHoComm[1~1];SimuLoad[10~10];InterRatPol
icyCfgGroup[4~40];eNodeBAutoPowerOff[1~1];S1ReestTimer[1~1];RrcConnStateTimer[1~1];CqiAdaptiveCfg[
1~1];PuschParam[1~1];X2[0~12];CellIdPrdUpt[1~1];Cell[0~18];TceIpMapping[0~256];ENodeBIntegrityCap
[1~1];CounterCheckPara[1~1];CnOperatorIpPath[0~320];ENodeBSharingMode[1~1];TddFrameOffset[1~1];
X2AutoSetupOperator[0~10];

Relation with the APPLICATION MO:


- ApplicationRef in eNodeBFunction MO must have been set in the associated
APPLICATION MO with eNodeB AT.
Relation with the SfnCellBind MO:
- eNodeBId in the SfnCellBind MO must be different from eNodeBId in the
eNodeBFunction MO.
Relation with the SfnAuxResBind MO:
- eNodeBId in the SfnAuxResBind MO must be different from eNodeBId in the
eNodeBFunction MO.
Relation with the eNodeBFunction MO:
- If two cells under the eNodeB have intra-frequency neighboring relationships with each
other (that is, either cell is configured as an EutranIntraFreqNCell MO for the other cell),
eNodeBId in the eNodeBFunction MO cannot be changed.
- If two cells under the eNodeB have inter-frequency neighboring relationships with each other
(that is, either cell is configured as an EutranInterFreqNCell MO for the other cell), eNodeBId
in the eNodeBFunction MO cannot be changed.
Relation with the EutranInterFreqNCell,EutranExternalCell,CnOperator MOs:
- Before adding an inter-eNodeB inter-frequency neighboring cell, ensure that the associated
EutranExternalCell MO has been configured.
Relation with the EutranIntraFreqNCell,EutranExternalCell,CnOperator MOs:
- Before adding an inter-eNodeB intra-frequency neighboring cell, ensure that the associated
EutranExternalCell MO has been configured.
Relation with the EutranExternalCell,ENodeBSharingMode,CnOperator MOs:
- If eNodeBId in an EutranExternalCell MO is the same as that in the eNodeBFunction MO
and the ENodeBSharingMode parameter in the ENodeBSharingMode MO is set to
SEPARATED_FREQ, the combination of Mcc and Mnc in an EutranExternalCell MO must be
different from that in any CnOperator MO. If the ENodeBSharingMode parameter in the
ENodeBSharingMode MO is set to INDEPENDENT or SHARED_FREQ, the combination of
Mcc and Mnc in the EutranExternalCell MO must be different from that in the CnOperator
MO that represents the primary operator.
Relation with the SimuLoad MO:
- A eNodeBFunction MO must contain 10 SimuLoad MOs.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add an eNodeB function.


ENODEBFUNCTION

LST Use this command to list eNodeB function configuration information.


ENODEBFUNCTION
Table 1 Related MML commands

MML Command Function

MOD Use this command to modify an eNodeB function.


ENODEBFUNCTION

RMV Use this command to remove an eNodeB function.


ENODEBFUNCTION

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

eNodeB Function Name Indicates the name of an eNodeB function, which uniquely identifies the
eNodeB function.

Application Reference Indicates the ID of the application referenced by an eNodeB function. The
application provides an operating environment for the eNodeB function.

eNodeB ID Indicates the eNodeB ID defined in the service protocol interface, which
uniquely identifies an eNodeB within a PLMN. For details, see 3GPP TS
36.300.

User Label Indicates user-defined remarks.

NeRM Version Indicates model definition version of eNodeB resources, including the
management object (MO) definition, attribute definition, and configuration
rules.

5.7.1.6.3.95 ENodeBIntegrityCap
+-NE
+-eNodeBFunction
+-ENodeBIntegrityCap

Description
The ENodeBIntegrityCap MO consists of the parameters related to the priorities of the eNodeB
integrity protection algorithms. The integrity protection function, which consists of integrity
protection and integrity check, can be used to protect data from modification by unauthorized
users. This function is applicable only to RRC signaling. Four algorithms are available for
integrity protection: SNOW 3G, AES, ZUC, and NULL.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the priorities of the eNodeB integrity protection
ENODEBINTEGRITYC
AP algorithms.

MOD Use this command to modify the priorities of the eNodeB integrity protection
ENODEBINTEGRITYC
AP algorithms.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Primary integrity Indicates the highest-priority integrity protection algorithm supported by the
algorithm
eNodeB.

Second integrity Indicates the second-priority integrity protection algorithm supported by the
algorithm
eNodeB.
Table 2 Related parameters

Parameter Description

Third integrity algorithm Indicates the third-priority integrity protection algorithm supported by the
eNodeB.

NULL Algorithm config Indicates whether the eNodeB can use the null algorithm for integrity protection.
switch
If this switch is turned off, the null algorithm cannot be used for integrity
protection. When this switch is turned off, the eNodeB selects an integrity
protection algorithm based on the algorithm priorities specified by
PrimaryIntegrityAlgo, SecondIntegrityAlgo, and ThirdIntegrityAlgo, but skips
the null algorithm.

5.7.1.6.3.96 eNodeBPath
+-NE
+-eNodeBFunction
+-eNodeBPath

Description

An eNodeBPath MO consists of parameters related to the application type of an IP path.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Relation with the IPPATH, IPPATH6 Mos:


- IpPathId in an eNodeBPath MO must have been set in the associated IPPATH MO or in
the associated IPPATH6 MO.
Relation with the IPPATH MO:
- IPMUXSWITCH in the IPPATH that is associated with IpPathId in the eNodeBPath
cannot be set to ENABLE.

Related MML Commands


Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD ENODEBPATH Use this command to add the application type of the IP path.

LST ENODEBPATH Use this command to list the application type of an IP path.

MOD ENODEBPATH Use this command to modify the application type of an IP path.

RMV ENODEBPATH Use this command to remove the application type of an IP path.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

IP Path ID Indicates the ID of the IP path.

Application Type Indicates the application type of the IP path.

S1 Interface ID Indicates the S1 interface ID of the IP path. This parameter is unavailable in this
version, it is recommended to be set as 0.

X2 Interface ID Indicates the X2 interface ID of the IP path.

5.7.1.6.3.97 ENodeBSharingMode
+-NE
+-eNodeBFunction
+-ENodeBSharingMode

Description

The ENodeBSharingMode MO consists of the parameter that indicates the sharing mode of the
eNodeB. The eNodeB supports the following modes: INDEPENDENT(Independent Operator
Mode), SHARED_FREQ(Shared Frequency Sharing Mode), SEPARATED_FREQ(Separate
Frequency Sharing Mode).

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Relation with the CellOp MO:


- If ENodeBSharingMode in the ENodeBSharingMode MO is set to SEPARATED_FREQ,
a maximum of one CellOp MO with the same LocalCellId as that in a Cell MO can be
configured.
- If ENodeBSharingMode in the ENodeBSharingMode MO is set to INDEPENDENT, only
one CellOp MO with the same LocalCellId as that in a Cell MO can be configured.
Relation with the LicenseSharingPolicy MO:
- If ENodeBSharingMode in the ENodeBSharingMode MO is set to INDEPENDENT, no
LicenseSharingPolicy MO can be configured.
Relation with the CnOperator MO:
- If ENodeBSharingMode in the ENodeBSharingMode MO is set to SEPARATED_FREQ
and eNodeBId in an EutranExternalCell MO is the same as ENODEBID in the eNodeB MO,
the combination of Mcc and Mnc in the EutranExternalCell MO must be different from the
combination of Mcc and Mnc in any CnOperator MO.
- If ENodeBSharingMode in the ENodeBSharingMode MO is set to INDEPENDENT, a
maximum of one CnOperator MO can be configured.
Relation with the CnOperatorTa MO:
- If ENodeBSharingMode in the ENodeBSharingMode MO is set to SHARED_FREQ,
CnOperator MO configured with Cell can not be all CNOPERATOR_SECONDARY.
Relation with the EPGROUP MO:
- In RAN sharing with dedicated carriers mode, the X2 MOs with different CnOperatorId
values cannot reference the EPGROUP MOs that contain theSCTPHOST MOs with the same
PN and IPv4 address.
- In RAN sharing with dedicated carriers mode, the X2 MOs with different CnOperatorId
values cannot reference the EPGROUP MOs that contain theSCTPHOST MOs with the same
PN and IPv6 address.
- In RAN sharing with dedicated carriers mode, the X2 MOs with different CnOperatorId
values cannot reference the EPGROUP MOs that contain theUSERPLANEHOST MOs with
the same PN and IPv4 address.
- In RAN sharing with dedicated carriers mode, the X2 MOs with different CnOperatorId
values cannot reference the EPGROUP MOs that contain theUSERPLANEHOST MOs with
the same PN and IPv6 address.
Relation with the CnOperatorTa,CellOp MOs:
- If ENodeBSharingMode in the ENodeBSharingMode MO is set to SHARED_FREQ,
CnOperator MOs configured with Cell MO must have one CnOperator MO which is primary
operator.
Relation with the EutranExternalCell,eNodeBFunction,CnOperator MOs:
- If eNodeBId in an EutranExternalCell MO is the same as that in the eNodeBFunction MO
and the ENodeBSharingMode parameter in the ENodeBSharingMode MO is set to
SEPARATED_FREQ, the combination of Mcc and Mnc in an EutranExternalCell MO must be
different from that in any CnOperator MO. If the ENodeBSharingMode parameter in the
ENodeBSharingMode MO is set to INDEPENDENT or SHARED_FREQ, the combination of
Mcc and Mnc in the EutranExternalCell MO must be different from that in the CnOperator
MO that represents the primary operator.
Relation with the CellOp,Cell MOs:
- If the ENodeBSharingMode parameter in the ENodeBSharingMode MO is set to
SEPARATED_FREQ, a maximum of one CellOp MO with the same LocalCellId as that in a
Cell MO can be configured.
- If the ENodeBSharingMode parameter in the ENodeBSharingMode MO is set to
INDEPENDENT, a maximum of one CellOp MO with the same LocalCellId as that in a Cell
MO can be configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the eNodeB sharing mode.


ENODEBSHARINGMO
DE

MOD Use this command to change the eNodeB sharing mode.


ENODEBSHARINGMO
DE

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

eNodeB sharing mode Indicates the eNodeB sharing mode, which can be independent operator mode,
shared frequency sharing mode, or separate frequency sharing mode.

5.7.1.6.3.98 eUCellSectorEqm
+-NE
+-eNodeBFunction
+-Cell
+-eUCellSectorEqm

Description

An eUCellSectorEqm MO consists of parameters related to the sector device and baseband


device that serve the cell.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the Cell,SectorEqm MOs:


- In a Cell MO, if FddTddInd is set to CELL_TDD and CellActiveState is set to
CELL_ACTIVE and MultiRruCellMode is not set to CELL_COMBINATION,
MPRU_AGGREGATION, the CrsPortNum value must be smaller than or equal to the number
of antennas specified by SECTOREQMANTENNA in the associated SECTOREQM MOs
corresponding to SectorEqmId.
Relation with the Cell,EuSectorEqmGroup MOs:
- In a Cell MO, if FddTddInd is set to CELL_TDD and MultiRruCellFlag is set to
BOOLEAN_TRUE and MultiRruCellMode is set to MPRU_AGGREGATION, the number of
EuSectorEqmGroup plus the number of different values of SectorEqmRef between
eUCellSectorEqm and EuSectorEqmGroup must be less than 8.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE and MultiRruCellMode is set to
MPRU_AGGREGATION, the eUCellSectorEqm MO or EuSectorEqmGroup MO under this
Cell MO must have been configured.
- In a Cell MO, if FddTddInd is set to CELL_FDD and MultiRruCellFlag is set to
BOOLEAN_TRUE and MultiRruCellMode is set to MPRU_AGGREGATION, the number of
EuSectorEqmGroup plus the number of different values of SectorEqmRef between
eUCellSectorEqm and EuSectorEqmGroup must be less than 7.
- In a Cell MO, if FddTddInd is set to CELL_TDD and MultiRruCellFlag is set to
BOOLEAN_TRUE and MultiRruCellMode is set to MPRU_AGGREGATION, and
UlBandWidth is set to CELL_BW_N50, the total number of eUCellSectorEqm and
EuSectorEqmGroup cannot exceed one.
Relation with the Cell,SECTOREQM,RRU,RFU MOs:
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE and MultiRruCellFlag is set to
BOOLEAN_FALSE, a maximum of two RRU MOs or RFU MOs can be associated with an
SECTOREQM MO corresponding to an eUCellSectorEqm MO under this Cell MO.
Relation with the Cell,SECTOREQM,RFU,RRUCHAIN MOs:
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, and the TT in RRUCHAIN
MOs where the RFU MOs associated with a SECTOREQM MO corresponding to an
eUCellSectorEqm MO under this Cell MO is not LOADBALANCE, these RRUCHAIN MOs
must be in the same subrack.
Relation with the Cell,BASEBANDEQM,SECTOREQM,RRU,RRUCHAIN MOs:
- If CellActiveState in a Cell MO is set to CELL_ACTIVE and BaseBandEqmId in an
eUCellSectorEqm MO under this Cell MO is not 255, the BBP MOs associated with the
BASEBANDEQM MOs corresponding to BaseBandEqmId and the RRUCHAIN MOs where
the RRU MOs associated with a SECTOREQM MO corresponding to an eUCellSectorEqm
MO under this Cell MO are configured must be in the same subrack.
Relation with the Cell,BASEBANDEQM,SECTOREQM,RFU,RRUCHAIN MOs:
- If CellActiveState in a Cell MO is set to CELL_ACTIVE and BaseBandEqmId in an
eUCellSectorEqm MO under this Cell MO is not 255, the BBP MOs associated with the
BASEBANDEQM MOs corresponding to BaseBandEqmId and the RRUCHAIN MOs where
the RFU MOs associated with a SECTOREQM MO corresponding to an eUCellSectorEqm
MO under this Cell MO are configured must be in the same subrack.
Relation with the CaGroupCell,Cell,SECTOREQM,RRU,RRUCHAIN MOs:
- If CellActiveState in both Cell MOs corresponding to a CaGroupCell MO under the same
CaGroup MO are set to CELL_ACTIVE, the RRUCHAIN MOs where the RRU MOs
associated with SECTOREQM MOs corresponding to eUCellSectorEqm MOs under both Cell
MOs are configured must be in the same subrack.
Relation with the CaGroupCell,Cell,SECTOREQM,RFU,RRUCHAIN MOs:
- If CellActiveState in both Cell MOs corresponding to a CaGroupCell MO under the same
CaGroup MO are set to CELL_ACTIVE, the RRUCHAIN MOs where the RFU MOs
associated with SECTOREQM MOs corresponding to eUCellSectorEqm MOs under both Cell
MOs are configured must be in the same subrack.
Relation with the Cell,SECTOR,SECTOREQM MOs:
- If CellActiveState in a Cell MO is set to CELL_ACTIVE, each SECTOR MO
corresponding to an eUCellSectorEqm MO under this Cell MO must be configured and unique.
- If CellActiveState in a Cell MO is set to CELL_ACTIVE and multiple SECTOREQM
MOs are associated with a SECTOR MO corresponding to this Cell MO, only one of these
SECTOREQM MOs can be referenced by Cell MO.
Relation with the Cell,CellAlgoSwitch,SECTOREQM MOs:
- Among all cells which use a same SECTOREQM,the number of cells which
CellActiveState in a Cell MO is set to CELL_ACTIVE and GLPwrShare in the
CellAlgoSwitch is set to ON must be less than 2.
Relation with the Cell,SECTOREQM,RRU,RRUCHAIN,BBP,RHUB MOs:
- When the LBBPs connected to a RRU specified in the SECTOREQM MO that corresponds
to the eUCellSectorEqm MO is set to ON, CPRICompression specified in the Cell must be set
to NORMAL_COMPRESSION.
Relation with the Cell,PDSCHCfg MOs:
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, MultiRruCellFlag is set to
BOOLEAN_TRUE and MultiRruCellMode is set to MPRU_AGGREGATION, the number of
valid values of ReferenceSignalPwr in eUCellSectorEqm must be not more than that of
ReferenceSignalPwr in PDSCHCfg.
Relation with the Cell MO:
- In a Cell MO, if MultiRruCellFlag is set to BOOLEAN_TRUE, MultiRruCellMode is set
to SFN, and CellActiveState is set to CELL_ACTIVE, the number of associated
eUCellSectorEqm MOs with the same LocalCellId value must be smaller than or equal to the
value of SectorEqmNum in this Cell.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE and MultiRruCellFlag is set to
BOOLEAN_FALSE, an eUCellSectorEqm MO must be configured under this Cell MO and
only one eUCellSectorEqm MO can be configured.
- When CellActiveState and FddTddInd in a Cell MO are set to CELL_ACTIVE and
CELL_TDD, respectively, a minimum of one and a maximum of seven eUCellSectorEqm MOs
must be configured under the Cell MO if MultiRruCellFlag and MultiRruCellMode in the
Cell MO are set to BOOLEAN_TRUE and SFN, respectively.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, MultiRruCellFlag is set to
BOOLEAN_TRUE, and MultiRruCellMode is set to CELL_COMBINATION, the number of
eUCellSectorEqm MOs configured under this Cell MO ranges from 1 to 6.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, MultiRruCellFlag is set to
BOOLEAN_TRUE, and MultiRruCellMode is set to TWO_RRU_COMBINATION, two
eUCellSectorEqm MOs must be configured under this Cell MO.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, MultiRruCellFlag is set to
BOOLEAN_TRUE, and MultiRruCellMode is set to DIGITAL_COMBINATION, the number
of eUCellSectorEqm MOs configured under this Cell MO ranges from 2 to 8.
- A maximum of eight eUCellSectorEqm can be configured for each Cell in which
MultiRruCellMode is not set to MPRU_AGGREGATION.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, MultiRruCellFlag is set to
BOOLEAN_TRUE, and MultiRruCellMode is set to CELL_COMBINATION, associated
eUCellSectorEqm MOs under this Cell MO must have the same BaseBandEqmId value.
- When CellActiveState and FddTddInd in a Cell MO are set to CELL_ACTIVE and
CELL_FDD, respectively, a minimum of one and a maximum of six eUCellSectorEqm MOs
must be configured under the Cell MO if MultiRruCellFlag and MultiRruCellMode in the
Cell MO are set to BOOLEAN_TRUE and SFN, respectively.
- In a Cell MO, If CellActiveState is set to CELL_ACTIVE and FddTddInd is set to
CELL_FDD, all Cell MOs associated with the SECTOREQM MO corresponding to any
eUCellSectorEqm MO under this Cell MO must have the same TxRxMode value.
- In a Cell MO, If CellActiveState is set to CELL_ACTIVE and FddTddInd is set to
CELL_FDD, all Cell MOs associated with the SECTOREQM MO corresponding to any
eUCellSectorEqm MO under this Cell MO must have the same MultiRruCellFlag value and
the same MultiRruCellMode value.
Relation with the Cell,SECTOREQM MOs:
- In a Cell MO, if MultiRruCellMode is not set to MPRU_AGGREGATION and
CellActiveState is set to CELL_ACTIVE, the eUCellSectorEqm MO corresponding to the Cell
MO must be configured, and the SECTOREQM MO corresponding to an eUCellSectorEqm
MO under this Cell MO must be configured.
- If CellActiveState in a Cell MO is set to CELL_ACTIVE, each antenna associated with the
SECTOREQM MO corresponding to an eUCellSectorEqm MO under this Cell MO must be
unique.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, TxRxMode is set to 1T1R,
2T2R, 4T4R, or 8T8R and MultiRruCellMode is not set to CELL_COMBINATION, the total
number of TX antennas and that of RX antennas associated with the SECTOREQM MO
corresponding to an eUCellSectorEqm MO under this Cell MO must be equal to the number of
TX antennas and that of RX antennas specified by the value of TxRxMode, respectively.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE and TxRxMode is set to 2T4R,
the SECTOREQM MO corresponding to an eUCellSectorEqm MO under this Cell MO must
be associated with two or four TX antennas and four RX antennas.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE and MultiRruCellFlag is set to
BOOLEAN_TRUE and MultiRruCellMode is not set to CELL_COMBINATION, the
SECTOREQM MO corresponding to each eUCellSectorEqm MO under this Cell MO must be
associated with an MO defining a unique RF module.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, MultiRruCellFlag is set to
BOOLEAN_TRUE, and MultiRruCellMode is set to SFN, the SECTOREQM MO
corresponding to an eUCellSectorEqm MO under this Cell MO must be associated with an
RRU MO.
- In a Cell MO, CellActiveState is set to CELL_ACTIVE, MultiRruCellFlag is set to
BOOLEAN_FALSE, and two RRU MOs or RFU MOs are associated with an SECTOREQM
MO corresponding to an eUCellSectorEqm MO under this Cell MO. If FddTddInd is set to
CELL_FDD, TxRxMode must be set to 2T2R, 2T4R, or 4T4R. If FddTddInd is set to
CELL_TDD, TxRxMode must be set to 2T2R.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE and MultiRruCellMode is set to
MPRU_AGGREGATION, the SECTOREQM MO corresponding to each eUCellSectorEqm
MO under this Cell MO must have been configured.
- In a Cell MO, if FddTddInd is set to CELL_TDD, MultiRruCellFlag is set to
BOOLEAN_TRUE, MultiRruCellMode is set to MPRU_AGGREGATION and
CellActiveState is set to CELL_ACTIVE, the SECTOREQM MO corresponding to each
eUCellSectorEqm MO under this Cell MO must be associated with two TX antennas and two
RX antennas.
- In a Cell MO, if FddTddInd is set to CELL_FDD, MultiRruCellFlag is set to
BOOLEAN_TRUE, MultiRruCellMode is set to MPRU_AGGREGATION and
CellActiveState is set to CELL_ACTIVE, the SECTOREQM MO corresponding to each
eUCellSectorEqm MO under this Cell MO must be associated with one TX antenna or two TX
antennas,one RX antenna or two RX antennas.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE and TxRxMode is set to 1T2R,
the SECTOREQM MO corresponding to an eUCellSectorEqm MO under this Cell MO must
be associated with one or two TX antennas and two RX antennas.
- In a Cell MO, If CellActiveState, FddTddInd are set to CELL_ACTIVE, CELL_FDD,
respectively, and a SECTOREQM MO is shared by the eUCellSectorEqm MO under this Cell
MO and under the other Cell MOs, all SECTOREQM MOs must be shared.
Relation with the Cell,SECTOREQM,RRU MOs:
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE and FddTddInd is set to
CELL_FDD, the SECTOREQM MO corresponding to an eUCellSectorEqm MO under this
Cell MO must be associated with an RRU MO supporting LTE_FDD.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE and FddTddInd is set to
CELL_TDD, the SECTOREQM MO corresponding to an eUCellSectorEqm MO under this
Cell MO must be associated with an RRU MO supporting LTE_TDD.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, MultiRruCellFlag is set to
BOOLEAN_TRUE, and MultiRruCellMode is set to DIGITAL_COMBINATION, the
SECTOREQM MO corresponding to an eUCellSectorEqm MO under this Cell MO must be
associated with an RRU MO with RT set to PRRU.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, FddTddInd is set to
CELL_FDD, MultiRruCellMode is not set to MPRU_AGGREGATION, and
CPRICompression is set to NORMAL_COMPRESSION, the SECTOREQM MO
corresponding to an eUCellSectorEqm MO under this Cell MO must be associated with an
RRU MO with RT set to PRRU.
- In a Cell MO, if FddTddInd is set to CELL_TDD, CellActiveState is set to
CELL_ACTIVE, MultiRruCellFlag is set to BOOLEAN_TRUE, and MultiRruCellMode is
set to SFN, the SECTOREQM MO corresponding to an eUCellSectorEqm MO under this Cell
MO must be associated with an RRU MO with RS set to TDL.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, MultiRruCellFlag is set to
BOOLEAN_TRUE, and MultiRruCellMode is set to SFN, the SECTOREQMMO
corresponding to an eUCellSectorEqm MO under this Cell MO must be associated with an
RRU MO with PS less than 2.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, MultiRruCellFlag is set to
BOOLEAN_TRUE, and at least one SECTOREQM MO corresponding to an
eUCellSectorEqm MO under this Cell MO is associated with an RRU MO with RT set to
PRRU, other such SECTOREQM MOs must also be associated with RRU MOs with RT set to
PRRU.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, MultiRruCellFlag is set to
BOOLEAN_TRUE, and the SECTOREQM MO corresponding to an eUCellSectorEqm MO
under this Cell MO is associated with an RRU MO with RT set to PRRU, TxRxMode must be
set to 1T1R or 2T2R.
Relation with the Cell,SECTOREQM,RFU MOs:
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE and FddTddInd is set to
CELL_FDD, the SECTOREQM MO corresponding to an eUCellSectorEqm MO under this
Cell MO must be associated with an RFU MO supporting LTE_FDD.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE and FddTddInd is set to
CELL_TDD, the SECTOREQM MO corresponding to an eUCellSectorEqm MO under this
Cell MO must be associated with an RFU MO supporting LTE_TDD.
Relation with the Cell,BASEBANDEQM,BBP MOs:
- When CellActiveState in a Cell MO is set to CELL_ACTIVE: if FddTddInd is set to
CELL_FDD, TYPE and WM in all BBP MOs corresponding to an eUCellSectorEqm MO
under this Cell MO must be set to LBBP and FDD; if FddTddInd is set to CELL_TDD, TYPE
in all BBP MOs specified by BaseBandEqmId in an eUCellSectorEqm MO under this Cell
MO must be set to LBBP, and WM cannot be set to FDD.
Relation with the Cell,BASEBANDEQM MOs:
- If CellActiveState in a Cell MO is set to CELL_ACTIVE, BASEBANDEQMTYPE in all
BASEBANDEQM MOs corresponding to an eUCellSectorEqm MO under this Cell MO must
be set to ULDL.
- If CellActiveState in a Cell MO is set to CELL_ACTIVE and BaseBandEqmId in an
eUCellSectorEqm MO under this Cell MO is not 255, the BASEBANDEQM MO
corresponding to BaseBandEqmId must have been configured.
Relation with the Cell,SECTOREQM,RRU,RRUCHAIN MOs:
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, MultiRruCellFlag is set to
BOOLEAN_TRUE, and the SECTOREQM MO corresponding to an eUCellSectorEqm MO
under this Cell MO is associated with an RRU MO with RT set to PRRU, all RRU MOs must
be configured on the same RRU chain.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, and the TT in RRUCHAIN
MOs where the RRU MOs associated with a SECTOREQM MO corresponding to an
eUCellSectorEqm MO under this Cell MO is not LOADBALANCE, these RRUCHAIN MOs
must be in the same subrack.
Relation with the Cell,BBP MOs:
- In a Cell MO, If CellActiveState is set to CELL_ACTIVE, FddTddInd is set to
CELL_FDD, and BaseBandEqmId in an eUCellSectorEqm MO under this Cell MO is set to
255, at least one LBBP working in FDD mode is available. If CellActiveState is set to
CELL_ACTIVE, FddTddInd is set to CELL_TDD, and BaseBandEqmId in an
eUCellSectorEqm MO under this Cell MO is set to 255, at least one LBBP working in non-
FDD mode is available.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add sector equipment for a cell.


EUCELLSECTOREQM

DSP EURTWP Use this command to query the total power of the receive channels of the RRU
and provide the brief analysis on whether the RRU works normally.

LST Use this command to list the configuration of sector equipment for a cell.
EUCELLSECTOREQM

MOD Use this command to modify the configuration of sector equipment for a cell.
EUCELLSECTOREQM

RMV Use this command to remove sector equipment for a cell.


EUCELLSECTOREQM

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local cell identity. It uniquely identifies a cell within an eNodeB.

Sector equipment ID Indicates the ID of the sector device that serves the cell, it uniquely identifies a
sector device within an eNodeB.

Reference signal power Indicates the reference signal power of the cell sector device. The value 32767
indicates that this reference signal power parameter is invalid. In this case, the
reference signal power of the cell equals the value of the PDSCHCfg parameter.
For details, see 3GPP TS 36.213.This parameter is valid only when a multi-RRU
cell works in SFN,MPRU_AGGREGATION or cell combination mode.

Baseband equipment Indicates the ID of the baseband equipment serving a cell.


ID
When this parameter is set to 255, the baseband equipment serving a cell is not
specified. In this scenario, the LTE baseband processing units (LBBPs) serving a
cell are selected among all LBBPs in the eNodeB, and the LBBPs to which the
cell's serving RRU is connected are preferentially selected.
When this parameter is set to a value other than 255, the cell is served by LBBPs
in the specified baseband equipment, and the LBBPs to which the cell's serving
RRU is connected are preferentially selected.

RRU Cabinet No. Indicates the cabinet number of the RRU.

RRU Subrack No. Indicates the subrack number of the RRU.

RRU Slot No. Indicates the slot number of the RRU.

Received total Indicates the received total wideband power (RTWP) for the carrier. The normal
wideband power
value range is from -110 dBm to -40 dBm. The RRU cannot work properly if the
value is out of range.

RX Channels No. Indicates the RX channel number of the RRU. An RRU is configured with
multiple RX channels.

Reference signal power Indicates the cell reference signal power headroom of each physical antenna.
margin

5.7.1.6.3.99 EuSectorEqmGroup
+-NE
+-eNodeBFunction
+-Cell
+-EuSectorEqmGroup

Description

An EuSectorEqmGroup MO consists of parameters related to the sector device group and


baseband device that serve the cell.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the Cell,eUCellSectorEqm MOs:


- In a Cell MO, if FddTddInd is set to CELL_TDD and MultiRruCellFlag is set to
BOOLEAN_TRUE and MultiRruCellMode is set to MPRU_AGGREGATION, the number of
EuSectorEqmGroup plus the number of different values of SectorEqmRef between
eUCellSectorEqm and EuSectorEqmGroup must be less than 8.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE and MultiRruCellMode is set to
MPRU_AGGREGATION, the eUCellSectorEqm MO or EuSectorEqmGroup MO under this
Cell MO must have been configured.
- In a Cell MO, if FddTddInd is set to CELL_FDD and MultiRruCellFlag is set to
BOOLEAN_TRUE and MultiRruCellMode is set to MPRU_AGGREGATION, the number of
EuSectorEqmGroup plus the number of different values of SectorEqmRef between
eUCellSectorEqm and EuSectorEqmGroup must be less than 7.
- In a Cell MO, if FddTddInd is set to CELL_TDD and MultiRruCellFlag is set to
BOOLEAN_TRUE and MultiRruCellMode is set to MPRU_AGGREGATION, and
UlBandWidth is set to CELL_BW_N50, the total number of eUCellSectorEqm and
EuSectorEqmGroup cannot exceed one.
Relation with the Cell,SECTOREQM MOs:
- In a Cell MO, if FddTddInd is set to CELL_TDD, MultiRruCellFlag is set to
BOOLEAN_TRUE, MultiRruCellMode is set to MPRU_AGGREGATION and
CellActiveState is set to CELL_ACTIVE, the SECTOREQM MO corresponding to each
EuSectorEqmGroup MO under this Cell MO must be associated with two TX antennas and
two RX antennas.
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, SectorEqmRef in each
EuSectorEqmGroup MO under this Cell MO must be unique.
- If CellActiveState and MultiRruCellMode in a Cell MO are set to CELL_ACTIVE and
MPRU_AGGREGATION, respectively, EuSectorEqmGroup MOs cannot be configured under
this Cell MO after the cell is activated. If an EuSectorEqmGroup MO has been configured
under this Cell MO before the cell is activated, the SECTOREQM MO associated with this
EuSectorEqmGroup MO must already exist. If only one SECTOREQM MO is associated with
the EuSectorEqmGroup MO, the association between the SECTOREQM MO and the
EuSectorEqmGroup MO cannot be removed after the cell is activated.
- In a Cell MO, if FddTddInd is set to CELL_FDD, MultiRruCellFlag is set to
BOOLEAN_TRUE, MultiRruCellMode is set to MPRU_AGGREGATION and
CellActiveState is set to CELL_ACTIVE, the SECTOREQM MO corresponding to each
EuSectorEqmGroup MO under this Cell MO must be associated with one TX antenna or two
TX antennas,one RX antenna or two RX antennas.
- In a Cell MO, ifMultiRruCellFlag is set to BOOLEAN_TRUE, MultiRruCellMode is set
to MPRU_AGGREGATION and CellActiveState is set to CELL_ACTIVE, the SECTOREQM
MO corresponding to each EuSectorEqmGroup MO under this Cell MO can only have antenna
of channel A or B.
Relation with the Cell,BASEBANDEQM MOs:
- If CellActiveState in a Cell MO is set to CELL_ACTIVE and BaseBandEqmId in an
EuSectorEqmGroup MO under this Cell MO is not 255, the BASEBANDEQM MO
corresponding to BaseBandEqmId must have been configured.
Relation with the Cell,BASEBANDEQM,BBP MOs:
- When CellActiveState in a Cell MO is set to CELL_ACTIVE: if FddTddInd is set to
CELL_FDD, TYPE and WM in all BBP MOs corresponding to an EuSectorEqmGroup MO
under this Cell MO must be set to LBBP and FDD; if FddTddInd is set to CELL_TDD, TYPE
in all BBP MOs specified by BaseBandEqmId in an EuSectorEqmGroup MO under this Cell
MO must be set to LBBP, and WM can not be set to FDD.
Relation with the Cell MO:
- In a Cell, the EuSectorEqmGroup can be configured only when MultiRruCellFlag is set
to BOOLEAN_TRUE and MultiRruCellMode is set to MPRU_AGGREGATION.
Relation with the Cell,SECTOREQM,RRU MOs:
- In a Cell MO, if CellActiveState is set to CELL_ACTIVE and MultiRruCellMode is set to
MPRU_AGGREGATION, the RRUs specified in the SECTOREQM MO under the
EuSectorEqmGroup MO must be on the same RRU chain, and their positions on the chain
must be the same.
Relation with the Cell,SECTOREQM,RRU,RRUCHAIN,BBP,RHUB MOs:
- When the LBBPs connected to a RRU specified in the SECTOREQM MO that corresponds
to the EuSectorEqmGroup MO is set to ON, CPRICompression specified in the Cell must be
set to NORMAL_COMPRESSION.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD Use this command to add a sector device group.


EUSECTOREQMGRO
UP

ADD Use this command to add a sector equipment ID to a sector equipment group.
EUSECTOREQMID2G
ROUP

LST Use this command to list the configuration of a sector equipment group.
EUSECTOREQMGRO
UP

LST Use this command to list sector equipment ID from a sector equipment group.
EUSECTOREQMID2G
ROUP

MOD Use this command to modify the configuration a sector equipment group.
EUSECTOREQMGRO
UP

RMV Use this command to remove a sector device group.


EUSECTOREQMGRO
UP

RMV Use this command to remove a sector equipment from a sector equipment group.
EUSECTOREQMID2G
ROUP

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local cell identity. It uniquely identifies a cell within an eNodeB.

Sector Equipment Indicates the group ID of the sector devices that serve the cell, it uniquely
Group ID
identifies a group of sector devices within a Cell.

Sector Equipment Indicates the list of the sector devices that serve the cell.
Reference

Baseband equipment Indicates the ID of the baseband equipment serving a cell.


ID
When this parameter is set to 255, the baseband equipment serving a cell is not
specified. In this scenario, the LTE baseband processing units (LBBPs) serving a
cell are selected among all LBBPs in the eNodeB, and the LBBPs to which the
Table 2 Related parameters

Parameter Description

cell's serving RRU is connected are preferentially selected.


When this parameter is set to a value other than 255, the cell is served by LBBPs
in the specified baseband equipment, and the LBBPs to which the cell's serving
RRU is connected are preferentially selected.

5.7.1.6.3.100 EutranExternalCell
+-NE
+-eNodeBFunction
+-EutranExternalCell
+-EutranExternalCellPlmn[0~5]

Description

An EutranExternalCell MO consists of the parameters related to an external E-UTRAN cell,


which can be configured as an intra- or inter-frequency of one or more cells under the local
eNodeB. The neighboring cell list (NCL) of an eNodeB contains the common information about
its external E-UTRAN cells, which are under other eNodeBs. In RAN sharing mode, additional
PLMN IDs must be added for each external E-UTRAN cell. If a connection setup request or
update message transmitted over an X2 interface contains information about cells under the peer
eNodeB, the local eNodeB automatically configures the cells as external E-UTRAN cells. If an
external E-UTRAN cell works in RAN sharing with common carrier mode, additional PLMN
IDs are automatically configured for the external E-UTRAN cell.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Possible children:
EutranExternalCellPlmn[0~5]

Relation with the EutranIntraFreqNCell,Cell MOs:


- DlEarfcn in the EutranExternalCell MO corresponding to an inter-eNodeB intra-frequency
neighboring cell must be the same as DlEarfcn in the local Cell MO.
- PhyCellId in the EutranExternalCell MO that is associated with an inter-eNodeB intra-
frequency neighboring cell must be different from PhyCellId in the local Cell MO.
Relation with the eNodeBFunction,ENodeBSharingMode,CnOperator MOs:
- If eNodeBId in an EutranExternalCell MO is the same as that in the eNodeBFunction MO
and the ENodeBSharingMode parameter in the ENodeBSharingMode MO is set to
SEPARATED_FREQ, the combination of Mcc and Mnc in an EutranExternalCell MO must be
different from that in any CnOperator MO. If the ENodeBSharingMode parameter in the
ENodeBSharingMode MO is set to INDEPENDENT or SHARED_FREQ, the combination of
Mcc and Mnc in the EutranExternalCell MO must be different from that in the CnOperator
MO that represents the primary operator.
Relation with the EutranIntraFreqNCell,CnOperator,eNodeBFunction MOs:
- Before adding an inter-eNodeB intra-frequency neighboring cell, ensure that the associated
EutranExternalCell MO has been configured.
Relation with the EutranInterFreqNCell,CnOperator,eNodeBFunction MOs:
- Before adding an inter-eNodeB inter-frequency neighboring cell, ensure that the associated
EutranExternalCell MO has been configured.
Relation with the EutranInterFreqNCell MO:
- DlEarfcn in the EutranExternalCell MO corresponding to an inter-eNodeB inter-frequency
neighboring cell must be different from DlEarfcn in the current Cell MO.
Relation with the EutranInterFreqNCell,EutranInterNFreq MOs:
- DlEarfcn in the EutranExternalCell MO corresponding to an inter-eNodeB inter-frequency
neighboring cell must be the same as DlEarfcn in an EutranInterNFreq MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add an external E-UTRAN cell.


EUTRANEXTERNALC
ELL

ADD Use this command to add the parameters related to the external E-UTRAN cell
EUTRANEXTERNALC
ELLBAND slave band.

LST Use this command to list the parameters related to the external E-UTRAN cell.
EUTRANEXTERNALC
Table 1 Related MML commands

MML Command Function

ELL

LST Use this command to list the parameters related to the external E-UTRAN cell
EUTRANEXTERNALC
ELLBAND slave band.

MOD Use this command to modify the configuration of an external E-UTRAN cell.
EUTRANEXTERNALC
ELL

RMV Use this command to remove an external E-UTRAN cell.


EUTRANEXTERNALC
ELL

RMV Use this command to remove the parameters related to the external E-UTRAN
EUTRANEXTERNALC
ELLBAND cell slave band.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Mobile country code Indicates the mobile country code of the external E-UTRAN cell.
The PLMN consists of the MCC and the MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, MCC = 123, MNC = 45, PLMN = 12345.

Mobile network code Indicates the mobile network code of the external E-UTRAN cell.
The PLMN consists of the MCC and the MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, MCC = 123, MNC = 45, PLMN = 12345.

eNodeB ID Indicates the eNodeB identity of the external E-UTRAN cell. It uniquely
identifies an eNodeB within a PLMN. The 28-bit E-UTRAN cell identity is
comprised of the cell identity and the eNodeB identity (represented by the most
significant 20 bits). The cell global identity (CGI) of an E-UTRAN cell is
comprised of the E-UTRAN cell identity and the PLMN ID. For details, see
3GPP TS 36.413.
Table 2 Related parameters

Parameter Description

Cell ID Indicates the cell identity of the external E-UTRAN cell. It uniquely identifies a
cell within an eNodeB. The 28-bit E-UTRAN cell identity is comprised of the
cell identity (represented by the least significant eight bits) and the eNodeB
identity. The cell global identity (CGI) of an E-UTRAN cell is comprised of the
E-UTRAN cell identity and the PLMN ID. For details, see 3GPP TS 36.413.

Downlink EARFCN Indicates the DL EARFCN of the external E-UTRAN cell. For details, see 3GPP
TS 36.104.

Uplink EARFCN Indicates whether to set the UL EARFCN for the external E-UTRAN cell. If this
indicator
parameter is set to NOT_CFG, the UL EARFCN is the DL EARFCN plus 18000
in FDD mode and is the same as the DL EARFCN in TDD mode.

Uplink EARFCN Indicates the UL EARFCN of the external E-UTRAN cell. For an FDD cell, if
no UL EARFCN is configured, the UL EARFCN equals the sum of the DL
EARFCN and 18000. For a TDD cell, the UL EARFCN equals the DL
EARFCN. For details, see 3GPP TS 36.104.

Physical cell ID Indicates the physical cell ID of the external E-UTRAN cell. For details, see
3GPP TS 36.331.

Tracking area code Indicates the tracking area code (TAC) of the external E-UTRAN cell. Two TAC
values 0x0000(0) and 0xFFFE(65534) are reserved according to the protocol
and will not be used in future versions. Therefore, do not use 0 or 65534 as a
TAC value in TAC planning or configuration.

Cell name Indicates the name of the external E-UTRAN cell.

External E-UTRAN Cell Indicates slave frequency bands of an external E-UTRAN cell. If the working
Slave Band
frequency of an external E-UTRAN cell belongs to multiple frequency bands,
the downlink frequency in the frequency band of the highest priority is
configured based on DlEarfcn, and the downlink frequencies in other frequency
bands are configured based on this parameter. If there are multiple frequency
bands of different priorities, downlink frequencies in the frequency bands are
configured based on the priorities in descending order. The frequency band
priorities of an external E-UTRAN cell are determined based on the network
planning of an operator. It is recommended that the frequency band values are
arranged in ascending order. The frequency band with the minimum value is of
the highest priority, and the frequency band with the maximum value is of the
lowest priority.

Control Mode Indicates the control policy on ANR-related MOs, which can be defined by the
user or be based on the automatic neighbor relation (ANR) algorithm. When this
parameter is set to MANUAL_MODE, the ANR-related MOs can be modified
Table 2 Related parameters

Parameter Description

or removed by only the user. A failure message is displayed when the user adds
an existing MO. When this parameter is set to AUTO_MODE, the ANR-related
MOs can be modified or removed by the user or based on the ANR algorithm.
The MO removal is successful even if the MO does not exist. An MO can be
added both by the user and based on the ANR algorithm. If an existing MO is to
be added, the MO is modified when the user performs the addition, but it cannot
be added based on the ANR algorithm. The preceding control policy also applies
to the EutranExternalCellPlmn MO, which is a child MO of the
EutranExternalCell MO. When the ANR-related MOs are automatically added
based on the ANR algorithm, this parameter is set to AUTO_MODE by default.
When the ANR-related MOs are added by the user, this parameter can be set to
AUTO_MODE or MANUAL_MODE.

5.7.1.6.3.101 EutranExternalCellPlmn
+-NE
+-eNodeBFunction
+-EutranExternalCell
+-EutranExternalCellPlmn

Description

An EutranExternalCellPlmn MO consists of the parameters related to an additional PLMN ID for


an external E-UTRAN cell. If the external E-UTRAN cell works in RAN sharing with common
carrier mode, a PLMN ID list must be configured before services can run properly among the
operators. A maximum of five additional PLMN IDs can be configured for each external E-
UTRAN cell. If there is an X2 interface between two eNodeBs, external E-UTRAN cells and
PLMN lists for the external E-UTRAN cells are configured automatically.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
EutranExternalCell

Relation with the EutranExternalCell MO:


- Before adding an EutranExternalCellPlmn MO, ensure that the associated
EutranExternalCell MO has been configured.
- A maximum of five EutranExternalCellPlmn MOs can be configured for each
EutranExternalCell MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add an additional PLMN ID for an external E-UTRAN
EUTRANEXTERNALC
ELLPLMN cell.

LST Use this command to list an additional PLMN ID for an external E-UTRAN cell.
EUTRANEXTERNALC
ELLPLMN

RMV Use this command to remove an additional PLMN ID for an external E-UTRAN
EUTRANEXTERNALC
ELLPLMN cell.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Mobile country code Indicates the mobile country code of the external cell.
A PLMN ID is comprised of an MCC and an MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, if the MCC is 123 and the MNC is 45, then the PLMN ID is
12345.

Mobile network code Indicates the mobile network code of the external cell.
A PLMN ID is comprised of an MCC and an MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, if the MCC is 123 and the MNC is 45, then the PLMN ID is
Table 2 Related parameters

Parameter Description

12345.

eNodeB ID Indicates the eNodeB identity of the external E-UTRAN cell. It uniquely
identifies an eNodeB within a PLMN. The 28-bit E-UTRAN cell identity is
comprised of the cell identity and the eNodeB identity (represented by the most
significant 20 bits). The cell global identity (CGI) of an E-UTRAN cell is
comprised of the E-UTRAN cell identity and the PLMN ID. For details, see
3GPP TS 36.413.

Cell ID Indicates the cell identity of the external E-UTRAN cell. It uniquely identifies a
cell within an eNodeB. The 28-bit E-UTRAN cell identity is comprised of the
cell identity (represented by the least significant eight bits) and the eNodeB
identity. The cell global identity (CGI) of an E-UTRAN cell is comprised of the
E-UTRAN cell identity and the PLMN ID. For details, see 3GPP TS 36.413.

Share mobile country Indicates the mobile country code of the external E-UTRAN cell that is shared
code
among multiple operators.
A PLMN ID is comprised of an MCC and an MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, if the MCC is 123 and the MNC is 45, then the PLMN ID is
12345.

Share mobile network Indicates the mobile network code of the external E-UTRAN cell that is shared
code
among multiple operators.
A PLMN ID is comprised of an MCC and an MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, if the MCC is 123 and the MNC is 45, then the PLMN ID is
12345.

5.7.1.6.3.102 EutranInterFreqNCell
+-NE
+-eNodeBFunction
+-Cell
+-EutranInterFreqNCell
Description

An EutranInterFreqNCell MO consists of the parameters related to the neighbor relationship with


an inter-frequency E-UTRAN cell. These parameters include those used in measurement control
for inter-frequency handovers and those in system information block type 5 (SIB5) for inter-
frequency cell reselections. Inter-frequency neighboring relations can be maintained by
automatic neighbor relation (ANR). Inter-frequency neighboring relationships are used in
algorithms such as mobility load balancing (MLB), mobility robustness optimization (MRO).

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the CaGroupCell,Cell MOs:


- The two Cell MOs associated with a CaGroupCell MO under the same CaGroup MO must
have inter-frequency neighbor relationships with each other.
Relation with the Cell MO:
- A maximum of 64 EutranInterFreqNCell MOs can be configured for each cell.
- The CGI of the local cell must be different from that of any intra-eNodeB inter-frequency
neighboring cell. A CGI is comprised of Mcc, Mnc, eNodeBId and CellId. Two CGIs are
considered to be the same if they have an identical combination of the four parameters. The CGI
of an inter-frequency neighboring cell is comprised of Mcc, Mnc, eNodeBId, and CellId in the
EutranInterFreqNCell MO. The CGI of the local cell is comprised of Mcc and Mnc in one
associated CnOperator MO, eNodeBId in the associated eNodeBFunction MO, and CellId in
the Cell MO.
- Before adding an intra-eNodeB inter-frequency neighboring cell for a serving cell, ensure
that a Cell MO corresponding to this intra-eNodeB inter-frequency cell has been configured.
- DlEarfcn in the Cell MO corresponding to an intra-eNodeB inter-frequency neighboring cell
must be different from DlEarfcn in the local Cell MO.
Relation with the EutranExternalCell,CnOperator,eNodeBFunction MOs:
- Before adding an inter-eNodeB inter-frequency neighboring cell, ensure that the associated
EutranExternalCell MO has been configured.
Relation with the Cell,EutranInterNFreq MOs:
- DlEarfcn in the Cell MO corresponding to an intra-eNodeB inter-frequency neighboring cell
must be the same as DlEarfcn in an EutranInterNFreq MO.
Relation with the EutranExternalCell,EutranInterNFreq MOs:
- DlEarfcn in the EutranExternalCell MO corresponding to an inter-eNodeB inter-frequency
neighboring cell must be the same as DlEarfcn in an EutranInterNFreq MO.
Relation with the CellOp,CnOperator,CnOperatorTa MOs:
- A CellOp MO must be configured for each EutranInterFreqNCell MO that corresponds to
an intra-eNodeB inter-frequency neighboring cell. If the ENodeBSharingMode parameter in the
ENodeBSharingMode MO is set to SHARED_FREQ, Mcc and Mnc in such an
EutranInterFreqNCell MO must be the same as the Mcc and Mnc specified in the
CnOperator MO representing the primary operator. If ENodeBSharingMode is set to
INDEPENDENT or SEPARATED_FREQ, Mcc and Mnc in such an EutranInterFreqNCell
MO must be set to the same values as Mcc and Mnc specified in the CnOperator MO
corresponding to the CellOp MO associated with this EutranInterFreqNCell MO.
Relation with the EutranExternalCell MO:
- DlEarfcn in the EutranExternalCell MO corresponding to an inter-eNodeB inter-frequency
neighboring cell must be different from DlEarfcn in the current Cell MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add the neighboring relation with an inter-frequency E-
EUTRANINTERFREQN
CELL UTRAN cell.

LST Use this command to list the parameters of the neighboring relations with inter-
EUTRANINTERFREQN
CELL frequency E-UTRAN cell.

MOD Use this command to modify the neighboring relation with an inter-frequency E-
EUTRANINTERFREQN
CELL UTRAN cell.

RMV Use this command to remove the neighboring relation with an inter-frequency E-
EUTRANINTERFREQN
CELL UTRAN cell.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Local cell ID Indicates the cell ID of the local cell. It uniquely identifies a cell within an
eNodeB.

Mobile country code Indicates the mobile country code of the E-UTRAN neighboring cell.
The PLMN consists of the MCC and the MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, MCC = 123, MNC = 45, PLMN = 12345.

Mobile network code Indicates the mobile network code of the E-UTRAN neighboring cell.
The PLMN consists of the MCC and the MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, MCC = 123, MNC = 45, PLMN = 12345.

eNodeB ID Indicates the eNodeB identity of the inter-frequency neighboring cell. It


uniquely identifies an eNodeB within a PLMN. The 28-bit E-UTRAN cell
identity is comprised of the cell identity and the eNodeB identity (represented by
the most significant 20 bits). The cell global identity (CGI) of an E-UTRAN cell
is comprised of the E-UTRAN cell identity and the PLMN ID. For details, see
3GPP TS 36.413.

Cell ID Indicates the local identity of the inter-frequency neighboring cell. It uniquely
identifies a cell within an eNodeB. The 28-bit E-UTRAN cell identity is
comprised of the cell identity (represented by the least significant eight bits) and
the eNodeB identity. The cell global identity (CGI) of an E-UTRAN cell is
comprised of the E-UTRAN cell identity and the PLMN ID. For details, see
3GPP TS 36.413.

Cell individual offset Indicates the cell individual offset for the inter-frequency neighboring cell,
which is used in evaluation for handovers. It affects the probability of triggering
inter-frequency measurement reports. A larger value of this parameter indicates a
higher probability. For details, see 3GPP TS 36.331.

Cell offset Indicates the offset for the inter-frequency neighboring cell, which is used in
evaluation for cell reselections. A larger value of this parameter results in a
lower probability of cell reselections. If this parameter is not set to dB0, it is
delivered in SIB5. For details, see 3GPP TS 36.331. If this parameter is set to
dB0, it is not delivered in SIB5. In this situation, UEs use 0 dB as the offset for
cell reselections. For details, see 3GPP TS 36.304.

No handover indicator Indicates whether handovers of UEs to the neighboring cell are prohibited.
Table 2 Related parameters

Parameter Description

No remove indicator Indicates whether to permit or prohibit removal of the neighboring relationship
by ANR.

Blind handover Priority Indicates the priority of the neighboring cell during handovers. The parameter
values are divided into three segments, indicating the blind-handover priority,
frequency-based-handover priority, and 0. Within the same segment, a larger
parameter value indicates a higher priority. Blind handover is a process in which
the eNodeB instructs a UE to hand over to a specified neighboring cell without
measurements. If this parameter value is set to 0, blind handovers and
frequency-based handovers cannot be performed. The parameter values 1 to 16
indicate the blind-handover priorities. The parameter values 17 to 32 indicate the
frequency-based-handover priorities for frequency-based blind handovers and
measurement-based handovers.

ANR flag Indicates whether this neighboring cell is automatically discovered by the ANR
algorithm.

Local cell name Indicates the name of the local cell.

Neighbour cell name Indicates the name of the inter-frequency neighboring cell.

Cell Measure Priority Indicates the priority of measurement on the inter-frequency neighboring cell.
The eNodeB preferentially contains the information about a neighboring cell
with this priority set to HIGH_PRIORITY while delivering a measurement
configuration.

Control Mode Indicates the control policy on ANR-related MOs, which can be defined by the
user or be based on the automatic neighbor relation (ANR) algorithm. When this
parameter is set to MANUAL_MODE, the ANR-related MOs can be modified
or removed by only the user. A failure message is displayed when the user adds
an existing MO. When this parameter is set to AUTO_MODE, the ANR-related
MOs can be modified or removed by the user or based on the ANR algorithm.
The MO removal is successful even if the MO does not exist. An MO can be
added both by the user and based on the ANR algorithm. If an existing MO is to
be added, the MO is modified when the user performs the addition, but it cannot
be added based on the ANR algorithm. When the ANR-related MOs are
automatically added based on the ANR algorithm, this parameter is set to
AUTO_MODE by default. When the ANR-related MOs are added by the user,
this parameter can be set to AUTO_MODE or MANUAL_MODE.

5.7.1.6.3.103 EutranInterNFreq
+-NE
+-eNodeBFunction
+-Cell
+-EutranInterNFreq
+-EutranNFreqSCellOp[0~6]
+-EutranNFreqRanShare[0~6]

Description

An EutranInterNFreq MO consists of the common parameters related to a neighboring E-


UTRAN frequency. The parameters include the frequency priority for cell reselection and the
measurement bandwidth. They are used in measurement control for reselection to inter-
frequency neighboring cells. For details, see 3GPP TS 36.331.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Possible children:
EutranNFreqSCellOp[0~6];EutranNFreqRanShare[0~6]

Relation with the ServiceIfHoCfgGroup MO:


- if InterFreqHoState in a ServiceIfHoCfgGroup is set to PERMIT_HO,DlEarfcn in the
ServiceIfHoCfgGroup MO must have been set in the associated EutranInterNFreq MO.
Relation with the EutranExternalCell,EutranInterFreqNCell MOs:
- DlEarfcn in the EutranExternalCell MO corresponding to an inter-eNodeB inter-frequency
neighboring cell must be the same as DlEarfcn in an EutranInterNFreq MO.
Relation with the EutranInterFreqNCell,Cell MOs:
- DlEarfcn in the Cell MO corresponding to an intra-eNodeB inter-frequency neighboring cell
must be the same as DlEarfcn in an EutranInterNFreq MO.
Relation with the InterFreqBlkCell MO:
- DlEarfcn in an InterFreqBlkCell MO must be the same as DlEarfcn in an
EutranInterNFreq MO for each cell.
Relation with the Cell MO:
- DlEarfcn in a Cell MO must be different from that in each associated EutranInterNFreq
MO.
- A maximum of eight EutranInterNFreq MOs can be configured for each cell.
Relation with the UtranNFreq MO:
- If CellReselPriorityCfgInd in EutranInterNFreq MO and UtranNFreq MO is both set to
CFG, CellReselPriority cannot be set to a same value for each cell.
Relation with the GeranNfreqGroup MO:
- If CellReselPriorityCfgInd in EutranInterNFreq MO and GeranNfreqGroup MO is both
set to CFG, CellReselPriority cannot be set to a same value for each cell.
Relation with the Cdma2000BandClass MO:
- If CellReselPriorityCfgInd in EutranInterNFreq MO is set to CFG, and if
Cdma20001XrttCellReselInd in Cdma2000BandClass MO is set to CFG,
Cdma20001XrttCellReselPri in Cdma2000BandClass MO cannot be set same as
CellReselPriority in EutranInterNFreq MO for each cell, and if
Cdma2000HrpdCellReselInd in Cdma2000BandClass MO is set to CFG,
Cdma2000HrpdCellReselPri in Cdma2000BandClass MO cannot be set same as
CellReselPriority in EutranInterNFreq MO for each cell.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add a neighboring E-UTRAN frequency.


EUTRANINTERNFREQ

LST Use this command to list the configuration of the neighboring E-UTRAN
EUTRANINTERNFREQ
frequency.

MOD Use this command to modify the configuration of a neighboring E-UTRAN


EUTRANINTERNFREQ
frequency.

RMV Use this command to remove a neighboring E-UTRAN frequency.


EUTRANINTERNFREQ

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description
Table 2 Related parameters

Parameter Description

Downlink EARFCN Indicates the DL EARFCN of the neighboring cell on the neighboring E-
UTRAN frequency. For details, see the 3GPP TS 36.104.

Uplink EARFCN Indicates whether to set the UL EARFCN. If this parameter is set to NOT_CFG,
configure indicator
the UL EARFCN is the DL EARFCN plus 18000 in FDD mode and is the same
as the DL EARFCN in TDD mode.

Uplink EARFCN Indicates the UL EARFCN of the neighboring cell on the neighboring E-
UTRAN frequency. For an FDD cell, if no UL EARFCN is configured, the UL
EARFCN equals the sum of the DL EARFCN and 18000. For a TDD cell, the
UL EARFCN equals the DL EARFCN. For details, see the 3GPP TS 36.104.

Inter frequency cell Indicates whether to set the reselection priority of the neighboring E-UTRAN
resel priority configure
indicator frequency. If the value of this parameter is not specified, the UE does not
reselect to neighboring cells on the frequency.

Inter frequency cell Indicates the cell reselection priority of the neighboring E-UTRAN frequency.
resel priority
The value 0 indicates the lowest priority. It is contained in system information
block type 5 (SIB5). The UE decides whether to reselect a neighboring cell on
the frequency based on the value of this parameter and the absolute priority of
the serving cell. If the value of this parameter is larger than the absolute priority
of the serving cell, the UE starts measurements on neighboring cells on the
frequency; then if the signal quality of some neighboring cells meets the related
conditions, the UE starts cell reselection. If the value of this parameter is less
than or equal to the absolute priority of the serving cell, the UE starts the
measurements only when the signal quality of the serving cell is poor; then if the
signal quality of some neighboring cells meets the related conditions, the UE
starts cell reselection. Frequencies used for different RATs must be assigned
different cell reselection priorities. For details, see 3GPP TS 36.331.

EUTRAN reselection Indicates the evaluation duration for a UE to determine whether to select an
time
inter-frequency neighboring cell to camp on. If the signal quality in an inter-
frequency neighboring cell is better than that in the serving cell for the period
specified by this parameter and a UE has been camped on the serving cell for
more than 1s, the UE attempts to reselect the inter-frequency neighboring cell to
camp on. This parameter is contained in SIB5. For details, see 3GPP TS 36.331.

Speed dependent resel Indicates whether to set the speed-dependent scaling parameters related to cell
parameter configuring
indicator reselection.
If this parameter is set to NOT_CFG, speed-dependent cell reselections are not
supported by default.

Scaling factor of Indicates the scaling factor applied to the cell reselection duration for medium-
treseleutran in medium
mobility UEs. This parameter is delivered in SIB5. For details, see 3GPP TS
Table 2 Related parameters

Parameter Description

mobility state 36.331.

Scaling factor of Indicates the scaling factor applied to the cell reselection duration for high-
treseleutra in high
mobility state mobility UEs. This parameter is delivered in SIB5. For details, see 3GPP TS
36.331.

Measurement Indicates the measurement bandwidth of the inter-frequency neighboring cell on


bandwidth
the frequency. The setting of this parameter depends on the bandwidth
configuration of the cell. In E-UTRAN, a cell bandwidth is also expressed in
units of resource blocks (RBs). Cell bandwidths 1.4 MHz, 3 MHz, 5 MHz, 10
MHz, 15 MHz, and 20 MHz correspond to 6 RBs, 15 RBs, 25 RBs, 50 RBs, 75
RBs, and 100 RBs, respectively.

Frequency offset Indicates the frequency-specific offset for the neighboring E-UTRAN frequency
that applies to UEs in idle mode. It is contained in system information block
type 5 (SIB5) and delivered to UEs in idle mode for cell reselection. For details,
see 3GPP TS 36.331.

Inter frequency high Indicates the RX level required for a neighboring cell on the frequency to
priority threshold
become a candidate for reselection if the priority of the frequency is higher than
that of the serving frequency. After measurements are started for neighboring
cells on the frequency, the UE reselects to a neighboring cell on the frequency
only if the RX level of the cell is better than the value specified by this
parameter for a time-to-trigger. For details, see 3GPP TS 36.331.

Inter frequency lower Indicates the minimum RX level required for a neighboring cell on the
priority threshold
frequency to become a candidate for reselection if the priority of the frequency
is lower than that of the serving frequency. After measurements are started for
neighboring cells on the frequency, the UE reselects to a neighboring cell on the
frequency only if the RX level of the serving cell is lower than a specified
threshold and that of the cell is higher than the value specified by this parameter
for a time-to-trigger. For details, see 3GPP TS 36.331.

Minimum required RX Indicates the RX level required for a neighboring cell on the frequency to
level
become a suitable cell for selection. It is included in criteria S and used in the
evaluation for cell selection. During the evaluation for cell reselection, the UE
performs the following calculation: Srxlev = Measured RSRP value of a
neighboring cell on the frequency - Value of this parameter - Compensated
power. If Srxlev for a cell is better than a threshold for a time-to-trigger,
reselection to the cell is started. For details, see 3GPP TS 36.304.

PMAX configure Indicates whether to set the maximum power that the UE can apply to
indicator
transmission on the neighboring E-UTRAN frequency. If the value of this
parameter is not specified, the maximum power is subject to the UE capability.
Table 2 Related parameters

Parameter Description

PMAX Indicates the maximum power that the UE can apply to transmission on the
neighboring E-UTRAN frequency. It is used in cell reselection criteria to
calculate the compensated power. If the value of this parameter is not specified,
the maximum power is subject to the UE capability. For details, see 3GPP TS
36.304.

Neighbor cell config Indicates the information related to MBSFN and TDD UL/DL configurations of
inter-frequency neighboring cell of the serving cell.
BitString00: Indicates that some neighboring cells have the same MBSFN
subframe configuration as the serving cell.
BitString01: Indicates that none of the neighboring cells is configured with
MBSFN subframes.
BitString10: Indicates that the MBSFN subframe configurations of all
neighboring cells are the same as or subsets of that of the serving cell.
BitString11: Indicates that the serving TDD cells have neighboring cells of
different UL-DL configurations.
For details, see 3GPP TS 36.331.

Presence antenna port1 Indicates whether all inter-frequency neighboring cells on this frequency are
configured with at least two antenna ports.
Set this parameter to TRUE if all inter-frequency neighboring cells on this
frequency are configured with at least two antenna ports.
Set this parameter to FALSE if one inter-frequency neighboring cell on this
frequency is configured with only one antenna port.

Inter-Freq HO trigger Indicates the event to trigger coverage-based inter-frequency handovers. This
Event Type
parameter can be set to EventA3, EventA4, or EventA5. If the neighboring E-
UTRAN frequency and the serving frequency are in the same frequency band,
event A3 is recommended as it provides better handover performance in this
situation. If the neighboring E-UTRAN frequency and the serving frequency are
in different frequency bands, event A4 or A5 is used.

Inter frequency high Indicates the RSRQ-based minimum RX level required for a neighboring cell on
priority RSRQ threshold
the frequency to become a candidate for reselection if the RSRQ-based priority
of the frequency is higher than that of the serving frequency.
After measurements are started for neighboring cells on the neighboring E-
UTRAN frequency, the UE reselects to a neighboring cell on the frequency only
if the RSRQ-based RX level of the cell is higher than the value specified by this
parameter for a time-to-trigger. For details, see 3GPP TS 36.331.

Inter frequency low Indicates the RSRQ-based minimum RX level required for a neighboring cell on
priority RSRQ threshold
the frequency to become a candidate for reselection if the RSRQ-based priority
Table 2 Related parameters

Parameter Description

of the frequency is lower than that of the serving frequency.


After measurements are started for neighboring cells on a frequency in the
GERAN carrier frequency group, the UE reselects to a neighboring cell on the
frequency only if the RSRQ-based RX level of the serving cell is lower than a
specified threshold and that of the cell is higher than the value specified by this
parameter for a time-to-trigger. For details, see 3GPP TS 36.331.

Minimum RX signal Indicates whether to set the minimum required RX level.


quality configuration
indicator

Minimum RX signal Indicates the minimum RX level of an inter-frequency neighboring cell, which is
quality
required for it to become a candidate for cell reselection. It determines the
probability of triggering cell reselection to inter-frequency neighboring cells on
the frequency. The value of this parameter is contained in SIB5. For details, see
3GPP TS 36.331.

Connect frequency Indicates the frequency priority based on which the eNodeB selects a target
priority
frequency for blind redirection or contains a frequency in a measurement
configuration. If a blind redirection is triggered and the target neighboring cell is
not specified, the eNodeB selects a target frequency based on this priority. If a
measurement configuration is to be delivered, the eNodeB preferentially delivers
a frequency with the highest priority. If this priority is set to 0 for a frequency,
this frequency is not selected as the target frequency for a blind redirection. A
larger value indicates a higher priority.

Mobility Load Balancing Indicates whether an inter-frequency is allowed to function as the target
Target Indicator
frequency in the inter-frequency MLB. When this parameter is set to
ALLOWED, an inter-frequency can function as the target frequency in the inter-
frequency MLB. When this parameter is set to NOT_ALLOWED, an inter-
frequency cannot function as the target frequency in the inter-frequency MLB.
This parameter applies only to inter-frequency blind MLB in the current version.

Frequency Offset for Indicates the frequency-specific offset for the neighboring E-UTRAN frequency
Connected Mode
that applies to UEs in connected mode. It is contained in the event A3/A4/A5
measurement configuration and delivered to UEs in connected mode. The offset
controls the probability of reporting events A3, A4, and A5. For details, see
3GPP TS 36.331.

Control Mode Indicates the control policy on ANR-related MOs, which can be defined by the
user or be based on the automatic neighbor relation (ANR) algorithm. When this
parameter is set to MANUAL_MODE, the ANR-related MOs can be modified
or removed by only the user. A failure message is displayed when the user adds
an existing MO. When this parameter is set to AUTO_MODE, the ANR-related
MOs can be modified or removed by the user or based on the ANR algorithm.
Table 2 Related parameters

Parameter Description

The MO removal is successful even if the MO does not exist. An MO can be


added both by the user and based on the ANR algorithm. If an existing MO is to
be added, the MO is modified when the user performs the addition, but it cannot
be added based on the ANR algorithm. When the ANR-related MOs are
automatically added based on the ANR algorithm, this parameter is set to
AUTO_MODE by default. When the ANR-related MOs are added by the user,
this parameter can be set to AUTO_MODE or MANUAL_MODE.

5.7.1.6.3.104 EutranIntraFreqNCell
+-NE
+-eNodeBFunction
+-Cell
+-EutranIntraFreqNCell

Description

An EutranIntraFreqNCell MO consists of the parameters related to the neighbor relationship with


an intra-frequency E-UTRAN cell. These parameters include those used in measurement control
for intra-frequency handovers and those in system information block type 4 (SIB4) for intra-
frequency cell reselections. Intra-frequency neighboring relations can be maintained by
automatic neighbor relation (ANR). Intra-frequency neighboring relations are used in mobility
load balancing (MLB), mobility robustness optimization (MRO), and inter-cell interference
coordination (ICIC).

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the EutranExternalCell,Cell MOs:


- DlEarfcn in the EutranExternalCell MO corresponding to an inter-eNodeB intra-frequency
neighboring cell must be the same as DlEarfcn in the local Cell MO.
- PhyCellId in the EutranExternalCell MO that is associated with an inter-eNodeB intra-
frequency neighboring cell must be different from PhyCellId in the local Cell MO.
Relation with the Cell MO:
- The CGI of the local cell must be different from that of any intra-eNodeB intra-frequency
neighboring cell. A CGI is comprised of Mcc, Mnc, eNodeBId and CellId. Two CGIs are
considered to be the same if they have an identical combination of the four parameters. The CGI
of an intra-frequency neighboring cell is comprised of Mcc, Mnc, eNodeBId, and CellId in the
EutranIntraFreqNCell MO. The CGI of the local cell is comprised of Mcc and Mnc in one
associated CnOperator MO, eNodeBId in the associated eNodeBFunction MO, and CellId in
the Cell MO.
- Before adding an intra-eNodeB intra-frequency neighboring cell for a serving cell, ensure
that a Cell MO corresponding to this intra-eNodeB intra-frequency cell has been configured.
- DlEarfcn in the Cell MO corresponding to an intra-eNodeB intra-frequency neighboring cell
must be the same as DlEarfcn in the local Cell MO.
- PhyCellId in the Cell MO corresponding to an intra-eNodeB intra-frequency neighboring
cell must be different from that in the local Cell MO.
- A maximum of 64 EutranIntraFreqNCell MOs can be configured for each cell.
Relation with the EutranExternalCell,CnOperator,eNodeBFunction MOs:
- Before adding an inter-eNodeB intra-frequency neighboring cell, ensure that the associated
EutranExternalCell MO has been configured.
Relation with the CellOp,CnOperator,CnOperatorTa MOs:
- A CellOp MO must be configured for each EutranIntraFreqNCell MO that corresponds to
an intra-eNodeB intra-frequency neighboring cell. If the ENodeBSharingMode parameter in the
ENodeBSharingMode MO is set to SHARED_FREQ, Mcc and Mnc in such an
EutranIntraFreqNCell MO must be the same as the Mcc and Mnc specified in the
CnOperator MO representing the primary operator. If ENodeBSharingMode is set to
INDEPENDENT or SEPARATED_FREQ, Mcc and Mnc in such an EutranIntraFreqNCell
MO must be set to the same values as Mcc and Mnc specified in the CnOperator MO
corresponding to the CellOp MO associated with this EutranIntraFreqNCell MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add the neighboring relation with an intra-frequency E-
EUTRANINTRAFREQN
CELL UTRAN cell.
Table 1 Related MML commands

MML Command Function

LST Use this command to list the parameters of the neighboring relations with intra-
EUTRANINTRAFREQN
CELL frequency E-UTRAN cell.

MOD Use this command to modify the neighboring relation with an intra-frequency E-
EUTRANINTRAFREQN
CELL UTRAN cell.

RMV Use this command to remove the neighboring relation with an intra-frequency E-
EUTRANINTRAFREQN
CELL UTRAN cell.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the cell ID of the local cell. It uniquely identifies a cell within an
eNodeB.

Mobile country code Indicates the mobile country code of the E-UTRAN neighboring cell.
The PLMN consists of the MCC and the MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, MCC = 123, MNC = 45, PLMN = 12345.

Mobile network code Indicates the mobile network code of the E-UTRAN neighboring cell.
The PLMN consists of the MCC and the MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, MCC = 123, MNC = 45, PLMN = 12345.

eNodeB ID Indicates the eNodeB identity of the intra-frequency neighboring cell. It


uniquely identifies an eNodeB within a PLMN. The 28-bit E-UTRAN cell
identity is comprised of the cell identity and the eNodeB identity (represented by
the most significant 20 bits). The cell global identity (CGI) of an E-UTRAN cell
is comprised of the E-UTRAN cell identity and the PLMN ID. For details, see
3GPP TS 36.413.

Cell ID Indicates the local identity of the intra-frequency neighboring cell. It uniquely
Table 2 Related parameters

Parameter Description

identifies a cell within an eNodeB. The 28-bit E-UTRAN cell identity is


comprised of the cell identity (represented by the least significant eight bits) and
the eNodeB identity. The cell global identity (CGI) of an E-UTRAN cell is
comprised of the E-UTRAN cell identity and the PLMN ID. For details, see
3GPP TS 36.413.

Cell individual offset Indicates the cell individual offset for the intra-frequency neighboring cell,
which is used in evaluation for handovers. It affects the probability of triggering
intra-frequency measurement reports. A larger value of this parameter indicates a
higher probability. For details, see 3GPP TS 36.331.

Cell offset Indicates the offset for the intra-frequency neighboring cell, which is used in
evaluation for cell reselections. A larger value of this parameter results in a
lower probability of cell reselections. If this parameter is not set to dB0, it is
delivered in SIB4. For details, see 3GPP TS 36.331. If this parameter is set to
dB0, it is not delivered in SIB4. In this situation, UEs use 0 dB as the offset for
cell reselections. For details, see 3GPP TS 36.304.

No handover indicator Indicates whether handovers of UEs to the neighboring cell are prohibited.

No remove indicator Indicates whether to permit or prohibit removal of the neighboring relationship
by ANR.

ANR flag Indicates whether this neighboring cell is automatically discovered by the ANR
algorithm.

Local cell name Indicates the name of the local cell.

Neighbour cell name Indicates the name of the intra-frequency neighboring E-UTRAN cell.

Cell Measure Priority Indicates the priority of measurement on the intra-frequency neighboring cell.
The eNodeB preferentially contains the information about a neighboring cell
with this priority set to HIGH_PRIORITY while delivering a measurement
configuration.

Cell Range Expansion Indicates cell coverage offset. This parameter is used to support the cell
coverage expansion in micro. This parameter is valid only when EicicSwitch is
set to ON and is valid only in UEs supporting the eICIC feature. The eNodeB
generates a new CellIndividualOffset value by exempting the original
CellIndividualOffset value from the CellRangeExpansion value, and delivers the
new CellIndividualOffset value to a UE, based on which the UE can be handed
over from the eNodeB to a micro earlier. The eNodeB generates a new
CellIndividualOffset value by adding up original CellIndividualOffset value and
the CellRangeExpansion value, and delivers the new CellIndividualOffset value
Table 2 Related parameters

Parameter Description

to a UE, based on which the UE can be handed over from a micro to the eNodeB
later. Therefore, the cell coverage of micro is expanded.

Control Mode Indicates the control policy on ANR-related MOs, which can be defined by the
user or be based on the automatic neighbor relation (ANR) algorithm. When this
parameter is set to MANUAL_MODE, the ANR-related MOs can be modified
or removed by only the user. A failure message is displayed when the user adds
an existing MO. When this parameter is set to AUTO_MODE, the ANR-related
MOs can be modified or removed by the user or based on the ANR algorithm.
The MO removal is successful even if the MO does not exist. An MO can be
added both by the user and based on the ANR algorithm. If an existing MO is to
be added, the MO is modified when the user performs the addition, but it cannot
be added based on the ANR algorithm. When the ANR-related MOs are
automatically added based on the ANR algorithm, this parameter is set to
AUTO_MODE by default. When the ANR-related MOs are added by the user,
this parameter can be set to AUTO_MODE or MANUAL_MODE.

5.7.1.6.3.105 EutranNFreqRanShare
+-NE
+-eNodeBFunction
+-Cell
+-EutranInterNFreq
+-EutranNFreqRanShare

Description

An EutranNFreqRanShare MO consists of the parameters related to information about an


operator that shares a neighboring E-UTRAN frequency with other operators. In RAN sharing
scenarios, operator-specific neighboring E-UTRAN frequencies can be configured as required.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
EutranInterNFreq

Relation with the


EutranNFreqSCellOp,UtranNFreqSCellOp,GeranNFGroupSCellOp,Cdma2000BcSCellOp
,UtranRanShare,GeranRanShare MOs:
- Cell reselection priorities based on operators of the local cell (which are specified in the
EutranNFreqSCellOp, UtranNFreqSCellOp, GeranNFGroupSCellOp, and
Cdma2000BcSCellOp MOs) cannot coexist with cell reselection priorities based on operators of
neighboring frequencies (which are specified in the EutranNFreqRanShare, UtranRanShare,
and GeranRanShare MOs).
Relation with the EutranInterNFreq MO:
- A maximum of Six EutranNFreqRanShare MOs can be configured for each
EutranInterNFreq MO.
Relation with the GeranRanShare MO:
- If CellReselPriorityCfgInd in GeranRanShare MO and EutranNFreqRanShare MO is
both set to CFG, Mcc, Mnc and CellReselPriority can not set to a same value for each cell.
Relation with the UtranRanShare MO:
- If CellReselPriorityCfgInd in UtranRanShare MO and EutranNFreqRanShare MO is
both set to CFG, Mcc, Mnc and CellReselPriority can not set to a same value for each cell.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add information about an operator that shares a
EUTRANNFREQRANS
HARE neighboring E-UTRAN frequency.

LST Use this command to list information about operators that share a neighboring
EUTRANNFREQRANS
HARE E-UTRAN frequency.

MOD Use this command to modify information about an operator that shares a
EUTRANNFREQRANS
HARE neighboring E-UTRAN frequency.

RMV Use this command to remove information about an operator that shares a
EUTRANNFREQRANS
HARE neighboring EUTRAN frequency.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Local cell ID Indicates the ID of the local cell. It uniquely identifies a cell within an eNodeB.

Downlink EARFCN Indicates the DL EARFCN of the operator that shares the neighboring E-
UTRAN frequency. For details, see the 3GPP TS 36.104.

Mobile country code Indicates the mobile country code (MCC) of the operator that shares the
neighboring E-UTRAN frequency.
A public land mobile network (PLMN) ID is comprised of an MCC and a
mobile network code (MNC).
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, if the MCC is 123 and the MNC is 45, the PLMN ID is 12345.

Mobile network code Indicates the mobile network code (MNC) of the operator that shares the
neighboring E-UTRAN frequency.
A public land mobile network (PLMN) ID is comprised of a mobile network
code (MCC) and an MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, if the MCC is 123 and the MNC is 45, the PLMN ID is 12345.

Cell reselection priority Indicates whether to configure the cell reselection priority.
configure indicator

Cell reselection priority Indicates the cell reselection priority of the operator that shares the neighboring
E-UTRAN frequency. The value 0 indicates the lowest priority. If the related
SPID configuration is specified, the cell reselection priority specified in the
SPID configuration is used. If no related SPID configuration is specified but this
parameter is set, the eNodeB delivers the cell reselection priorities of all PLMNs
supported by a UE by using the IE idleModeMobilityControlInfo in an RRC
Connection Release message to the UE. If no related SPID configuration is
specified and this parameter is not set, a UE uses the cell reselection priority of
the neighboring E-UTRAN frequency, which is broadcast in the system
information.

5.7.1.6.3.106 EutranNFreqSCellOp
+-NE
+-eNodeBFunction
+-Cell
+-EutranInterNFreq
+-EutranNFreqSCellOp

Description

The EutranNFreqSCellOp MO defines cell reselection dedicated priorities based on the PLMN
of the local cell for the E-UTRAN frequency.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
EutranInterNFreq

Relation with the CnOperator MO:


- CnOperatorID in a EutranNFreqSCellOp MO must have been set in the associated
CnOperator MO.
Relation with the
UtranNFreqSCellOp,GeranNFGroupSCellOp,Cdma2000BcSCellOp,EutranNFreqRanSha
re,UtranRanShare,GeranRanShare MOs:
- Cell reselection priorities based on operators of the local cell (which are specified in the
EutranNFreqSCellOp, UtranNFreqSCellOp, GeranNFGroupSCellOp, and
Cdma2000BcSCellOp MOs) cannot coexist with cell reselection priorities based on operators of
neighboring frequencies (which are specified in the EutranNFreqRanShare, UtranRanShare,
and GeranRanShare MOs).
Relation with the UtranNFreqSCellOp MO:
- Cell reselection priorities specified in the EutranNFreqSCellOp and UtranNFreqSCellOp
MOs for the same operator cannot be the same.
Relation with the GeranNFGroupSCellOp MO:
- Cell reselection priorities specified in the EutranNFreqSCellOp and
GeranNFGroupSCellOp MOs for the same operator cannot be the same.
Relation with the Cdma2000BcSCellOp MO:
- Cell reselection priorities specified in the EutranNFreqSCellOp and
Cdma2000BcSCellOp MOs for the same operator cannot be the same.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD Use this command to add an operator-specific configuration for the E-UTRAN
EUTRANNFREQSCEL
LOP frequency.

LST Use this command to list operator-specific configurations for the E-UTRAN
EUTRANNFREQSCEL
LOP frequency.

MOD Use this command to modify operator-specific configurations for the EUTRAN
EUTRANNFREQSCEL
LOP frequency.

RMV Use this command to remove an operator-specific configuration for the


EUTRANNFREQSCEL
LOP EUTRAN frequency.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the ID of the local cell. It uniquely identifies a cell within an eNodeB.

Downlink EARFCN Indicates the DL EARFCN of the Operator Configuration for Serving Cell in
EUTRAN Frequency. For details, see the 3GPP TS 36.104.

Cn operator ID Indicates the ID of the operator.

Cell reselection Indicates whether to configure a dedicated cell-reselection priority based on the
dedicated priority
configure indicator PLMN ID of the local cell for the neighboring E-UTRAN frequency.

Cell reselection Indicates the cell reselection dedicated priority for an E-UTRAN frequency
dedicated priority
based on the PLMN ID of the local cell. The value 0 indicates the lowest
priority. If the related SPID configuration is specified, the cell reselection
priority specified in the SPID configuration is used. If no related SPID
configuration is specified but this parameter is set, the eNodeB delivers the cell
reselection priorities of all PLMNs supported by a UE by using the IE
idleModeMobilityControlInfo in an RRC Connection Release message to the
UE. If no related SPID configuration is specified and this parameter is not set, a
UE uses the cell reselection priority of the neighboring E-UTRAN frequency,
which is broadcast in the system information.
5.7.1.6.3.107 ExtendedQci
+-NE
+-eNodeBFunction
+-ExtendedQci

Description

An ExtendedQci MO consists of the service type and other parameters related to an extended
QoS Class Identifier (QCI).

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Relation with the InterRatPolicyCfgGroup MO:


- InterRatPolicyCfgGroupId in an ExtendedQci MO must have been set in the associated
InterRatPolicyCfgGroup MO.
Relation with the RlcPdcpParaGroup MO:
- RlcPdcpParaGroupId in an ExtendedQci MO must have been set in the associated
RlcPdcpParaGroup MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD EXTENDEDQCI Use this command to add an extended QCI configuration.

LST EXTENDEDQCI Use this command to list eNodeB-level extended QCI settings.

MOD EXTENDEDQCI Use this command to modify an eNodeB-level extended QCI.

RMV EXTENDEDQCI Use this command to remove an eNodeB-level extended QCI.


Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Extended QoS Class Indicates the extended QoS Class Identifier (QCI), which is required by the
Identifier
operator for user differentiation.

Service type Indicates the service type corresponding to the extended QCI.

Uplink scheduling Indicates the weight factor used in the calculation of connection priorities during
priority factor
uplink scheduling.

Downlink scheduling Indicates the weight factor used in the calculation of connection priorities during
priority factor
downlink scheduling.

Uplink MinGBR Indicates the uplink minimum guaranteed bit rate of the non-GBR service.

Downlink MinGBR Indicates the downlink minimum guaranteed bit rate of the non-GBR service.

Pre-allocation weight Indicates the pre-allocation weight. The pre-allocation weight of a UE is the pre-
allocation weight of services carried by the highest-priority logical channel. If
services carried by highest-priority logical channels have different pre-allocation
weights, the UE takes the highest pre-allocation weight. When resources are
insufficient, pre-allocation weights affect the pre-allocation probabilities of
users. The pre-allocation probability has a positive correlation with the pre-
allocation weight. This parameter is QCI-specific.

InterRAT policy config Indicates the group ID of the parameters related to the inter-RAT handover with
group ID
the extended QCI.

Prioritised bit rate Indicates the prioritized bit rate of the logical channel. The UE scheduler
guarantees prioritized bit rates of logical channels in descending order of logical
channel priority. For details, see 3GPP TS 36.321.

Logical channel priority Indicates the priority of the logical channel. The UE scheduler guarantees
prioritized bit rates of logical channels in descending order of logical channel
priority. Resources are allocated in descending order of logical channel priority
after the prioritized bit rates of all services are guaranteed. For details, see 3GPP
TS 36.321.

RLC PDCP parameter Indicates the ID of an RLC/PDCP parameter group.


group ID

Free user flag Indicates whether the extended QCI is specific to free users or paid users.
Table 2 Related parameters

Parameter Description

Flow Control Type Indicates whether to enable flow control for the QCI.

5.7.1.6.3.108 GeranExternalCell
+-NE
+-eNodeBFunction
+-GeranExternalCell
+-GeranExternalCellPlmn[0~3]

Description

A GeranExternalCell MO consists of the parameters related to an external GERAN cell. The


inter-RAT neighboring cell list (NCL) for the eNodeB contains the common information about
the neighboring relations with GERAN cells and is used in the setup of the neighboring relations.
Additional PLMN IDs must be added for each external GERAN cell in RAN sharing mode.
GERAN RAN Information Management (RIM) requires the routing area code (RAC) of each
external GERAN cell. For details, see 3GPP TS 36.331 and 3GPP TS 36.413.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Possible children:
GeranExternalCellPlmn[0~3]

Relation with the GeranNcell,GeranNfreqGroup,GeranNfreqGroupArfcn MOs:


- GeranArfcn and BandIndicator in a GeranExternalCell MO corresponding to a
GeranNcell MO must be the same as GeranArfcn in a GeranNfreqGroupArfcn MO and
BandIndicator in the GeranNfreqGroup MO associated with the GeranNfreqGroupArfcn
MO, respectively. Alternatively, GeranArfcn and BandIndicator in a GeranExternalCell MO
corresponding to a GeranNcell MO must be the same as StartingArfcn and BandIndicator in a
GeranNfreqGroup MO, respectively.
Relation with the GeranNcell MO:
- Before adding a GeranNcell MO, ensure that the associated GeranExternalCell MO has
been configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add an external GERAN cell.


GERANEXTERNALCE
LL

LST Use this command to list the parameters related to the external GERAN cell.
GERANEXTERNALCE
LL

MOD Use this command to modify the configuration of an external GERAN cell.
GERANEXTERNALCE
LL

RMV Use this command to remove an external GERAN cell.


GERANEXTERNALCE
LL

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Mobile country code Indicates the mobile country code of the external cell.
The PLMN consists of the MCC and the MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, MCC = 123, MNC = 45, PLMN = 12345.

Mobile network code Indicates the mobile network code of the external cell.
The PLMN consists of the MCC and the MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
Table 2 Related parameters

Parameter Description

For example, MCC = 123, MNC = 45, PLMN = 12345.

GERAN cell ID Indicates the cell ID of the external GERAN cell. It uniquely identifies a
GERAN cell within the area specified by the location area identity (LAI). An
LAI consists of the MCC, MNC, and LAC.

Location area code Indicates the LAC of the external GERAN cell. It uniquely identifies a location
within a PLMN.

Routing area code Indicates whether to set the routing area code (RAC) of the external GERAN
configure indicator
cell. This parameter is required if the external GERAN cell supports packet
switched (PS) services.

Routing area code Indicates the routing area code.

Band indicator Indicates the GERAN band indicator. If the GERAN ARFCN is a value in the
range of 512 to 810, the value of this parameter is used to indicate whether the
GERAN ARFCN is in the 1800 MHz band or the 1900 MHz band. If the
GERAN ARFCN is not in either band, this parameter does not take effect and
can be set to either value. For details, see 3GPP TS 36.331.

GERAN ARFCN Indicates the GERAN BCCH ARFCN. For details, see 3GPP TS 45.005.

Network color code Indicates the network color code (NCC) of GERAN. It is operator-specific and
identifies a network within the whole country.The base transceiver station
identity code (BSIC) consists of the NCC and the base station color code (BCC).
For details, see 3GPP TS 23.003.

Base station color code Indicates the base station color code (BCC) of an external GERAN cell. This
parameter is used to discriminate external GERAN cells working at the same
frequency.The base transceiver station identity code (BSIC) consists of the BCC
and the network color code (NCC). For details, see 3GPP TS 23.003.

DTM indication Indicates whether the cell supports the dual transmission mode. If the cell
supports the dual transmission mode, both CS and PS services can be handed
over to the cell at the same time. Otherwise, only the CS service or the PS
service can be handed over to the cell.

Cell name Indicates the name of the external GERAN cell.

CS and PS handover Indicates whether the external GERAN cell supports single radio voice call
indication
continuity (SRVCC) for both CS and PS services. If this parameter is set to
BOOLEAN_FALSE(False), the external GERAN cell does not support SRVCC
Table 2 Related parameters

Parameter Description

for both CS and PS services.

Control Mode Indicates the control policy on ANR-related MOs, which can be defined by the
user or be based on the automatic neighbor relation (ANR) algorithm. When this
parameter is set to MANUAL_MODE, the ANR-related MOs can be modified
or removed by only the user. A failure message is displayed when the user adds
an existing MO. When this parameter is set to AUTO_MODE, the ANR-related
MOs can be modified or removed by the user or based on the ANR algorithm.
The MO removal is successful even if the MO does not exist. An MO can be
added both by the user and based on the ANR algorithm. If an existing MO is to
be added, the MO is modified when the user performs the addition, but it cannot
be added based on the ANR algorithm. The preceding control policy also applies
to the GeranExternalCellPlmn MO, which is a child MO of the
GeranExternalCell MO. When the ANR-related MOs are automatically added
based on the ANR algorithm, this parameter is set to AUTO_MODE by default.
When the ANR-related MOs are added by the user, this parameter can be set to
AUTO_MODE or MANUAL_MODE.

5.7.1.6.3.109 GeranExternalCellPlmn
+-NE
+-eNodeBFunction
+-GeranExternalCell
+-GeranExternalCellPlmn

Description

A GeranExternalCellPlmn MO consists of the parameters related to an additional PLMN ID for


an external GERAN cell. A maximum of three additional PLMN IDs can be configured for each
external GERAN cell.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
GeranExternalCell

Relation with the GeranExternalCell MO:


- Before adding a GeranExternalCellPlmn MO, ensure that the associated
GeranExternalCell MO has been configured.
- A maximum of three GeranExternalCellPlmn MOs can be configured for each
GeranExternalCell MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add an additional PLMN ID for an external GERAN cell.
GERANEXTERNALCE
LLPLMN

LST Use this command to list an additional PLMN ID for an external GERAN cell.
GERANEXTERNALCE
LLPLMN

RMV Use this command to remove an additional PLMN ID for an external GERAN
GERANEXTERNALCE
LLPLMN cell.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

GERAN cell ID Indicates the identity of the external GERAN cell. It uniquely identifies a
GERAN cell within a PLMN.

Location area code Indicates the LAC of the external GERAN cell.

Mobile country code Indicates the mobile country code of the external cell.
A PLMN ID is comprised of an MCC and an MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, if the MCC is 123 and the MNC is 45, then the PLMN ID is
Table 2 Related parameters

Parameter Description

12345.

Mobile network code Indicates the mobile network code of the external cell.
A PLMN ID is comprised of an MCC and an MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, if the MCC is 123 and the MNC is 45, then the PLMN ID is
12345.

Share mobile country Indicates the mobile country code of the external GERAN cell that is shared
code
among multiple operators.
A PLMN ID is comprised of an MCC and an MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, if the MCC is 123 and the MNC is 45, then the PLMN ID is
12345.

Share mobile network Indicates the mobile network code of the external GERAN cell that is shared
code
among multiple operators.
A PLMN ID is comprised of an MCC and an MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, if the MCC is 123 and the MNC is 45, then the PLMN ID is
12345.

5.7.1.6.3.110 GeranInterfArfcn
+-NE
+-eNodeBFunction
+-Cell
+-GeranInterfArfcn

Description

A GeranInterfArfcn MO defines a GERAN frequency that causes interference to LTE. This


frequency can be obtained based on signal strength measurement.
Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the Cell MO:


- LocalCellId in an GeranInterfArfcn MO must have been set in the associated Cell MO.
- A maximum of 20 GeranInterfArfcn MOs can be configured for each Cell MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add a GERAN frequency that causes interference to LTE.
GERANINTERFARFCN

LST Use this command to list GERAN frequencies that cause interference to LTE.
GERANINTERFARFCN

MOD Use this command to modify the frequency band indicator corresponding to a
GERANINTERFARFCN
GERAN frequency that causes interference to LTE network.

RMV Use this command to remove a GERAN frequency that causes interference to
GERANINTERFARFCN
LTE.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local identity of the cell. It uniquely identifies a cell within an
eNodeB.

Interference GERAN Indicates the received signal strength indicator (RSSI) of the GERAN BCCH
Table 2 Related parameters

Parameter Description

BCCH ARFCN ARFCN that a UE needs to measure to determine whether it is tolerant of the
interference from the cells working on this frequency.

Interference GERAN Indicates the GERAN band to which the absolute radio frequency channel
Frequency Band
Indicator number (ARFCN) that the UE needs to measure belongs. If the GERAN
ARFCN is in the range of 512 to 810, the value of this parameter is used to
indicate whether the GERAN ARFCN is in the DCS 1800 MHz band or the PCS
1900 MHz band. If the GERAN ARFCN is in neither band, this parameter does
not take effect and can be set to either value. For details, see 3GPP TS 36.331.

5.7.1.6.3.111 GeranInterfCfg
+-NE
+-eNodeBFunction
+-Cell
+-GeranInterfCfg

Description

A GeranInterfCfg MO consists of the parameters related to GL Bufferzone optimization. It is set


to avoid interference from adjacent GERAN cells.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

LST Use this command to list the configuration of the GL Bufferzone optimization.
GERANINTERFCFG

MOD Use this command to modify the GL Bufferzone optimization configuration.


GERANINTERFCFG

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local identity of the cell. It uniquely identifies a cell within an
eNodeB.

Number of DL RBs Indicates the number of RBs that are interfered by GERAN at each end of the
interfered by GERAN
LTE DL frequency band. If the numbers of such RBs are different at both ends,
the larger number is used as the value of this parameter.
If this parameter is set to 3, three RBs are interfered by GERAN at each end of
the LTE DL frequency band and altogether six RBs are interfered.

SINR threshold for Indicates the SINR threshold for determining whether DL RB resources of an E-
available DL RBs
UTRAN cell using the LTE frequency spectrum that overlaps the GSM
frequency spectrum are available. If the result of the local cell RSRP plus 11.2
and minus the RSSI of the GERAN cell that brings the severest interference is
greater than the value of this parameter, UEs can use these RB resources.
Otherwise, UEs cannot use these RB resources. UEs measure the local cell
RSRP and the RSSI of the GERAN cell that brings the severest interference and
report the measurement results to the eNodeB.

5.7.1.6.3.112 GeranNcell
+-NE
+-eNodeBFunction
+-Cell
+-GeranNcell
Description

A GERANNCELL MO consists of the parameters related to a GERAN neighboring cell of the


local cell, which can be the target cell of an inter-RAT handover.
For details, see 3GPP TS 36.331.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the GeranExternalCell,GeranNfreqGroup,GeranNfreqGroupArfcn MOs:


- GeranArfcn and BandIndicator in a GeranExternalCell MO corresponding to a
GeranNcell MO must be the same as GeranArfcn in a GeranNfreqGroupArfcn MO and
BandIndicator in the GeranNfreqGroup MO associated with the GeranNfreqGroupArfcn
MO, respectively. Alternatively, GeranArfcn and BandIndicator in a GeranExternalCell MO
corresponding to a GeranNcell MO must be the same as StartingArfcn and BandIndicator in a
GeranNfreqGroup MO, respectively.
Relation with the Cell MO:
- A maximum of 64 GeranNcell MOs can be configured for each cell.
Relation with the GeranExternalCell MO:
- Before adding a GeranNcell MO, ensure that the associated GeranExternalCell MO has
been configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD GERANNCELL Use this command to add the neighboring relation with a GERAN cell.

DSP GERANRIMINFO Use this command to query the status of the RAN Information Management
(RIM) function for neighboring GERAN cells.

LST GERANNCELL Use this command to list the parameters of the neighboring relation with the
GERAN cell.
Table 1 Related MML commands

MML Command Function

MOD GERANNCELL Use this command to modify the neighboring relation with a GERAN cell.

RMV GERANNCELL Use this command to remove the neighboring relation with a GERAN cell.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the cell ID of the Local cell. It uniquely identifies a cell within an
eNodeB.

Mobile country code Indicates the mobile country code of the neighboring GERAN cell.
The PLMN consists of the MCC and the MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, MCC = 123, MNC = 45, PLMN = 12345.

Mobile network code Indicates the mobile network code of the neighboring GERAN cell.
The PLMN consists of the MCC and the MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, MCC = 123, MNC = 45, PLMN = 12345.

Location area code Indicates the LAC of the GERAN neighboring cell. It uniquely identifies a
location within a PLMN.

GERAN cell ID Indicates the cell ID of the GERAN neighboring cell. It uniquely identifies a
GERAN cell within the area specified by the location area identity (LAI). An
LAI consists of the MCC, MNC, and LAC.

No remove indicator Indicates whether to permit or prohibit removal of the neighboring relationship
by ANR.

No handover indicator Indicates whether handovers of UEs to the neighboring cell are prohibited.

Blind handover priority Indicates the priority of the neighboring cell during blind handovers. Blind
Table 2 Related parameters

Parameter Description

handover is a process in which the eNodeB instructs a UE to hand over to a


specified neighboring cell. There are 32 priorities altogether. The priority has a
positive correlation with the value of this parameter. Note that the value 0
indicates that blind handovers to the neighboring cell are not allowed.

ANR flag Indicates whether this neighboring cell is automatically discovered by the ANR
algorithm.

Local cell name Indicates the name of the local cell.

Neighbour cell name Indicates the name of the GERAN neighboring cell.

Control Mode Indicates the control policy on ANR-related MOs, which can be defined by the
user or be based on the automatic neighbor relation (ANR) algorithm. When this
parameter is set to MANUAL_MODE, the ANR-related MOs can be modified
or removed by only the user. A failure message is displayed when the user adds
an existing MO. When this parameter is set to AUTO_MODE, the ANR-related
MOs can be modified or removed by the user or based on the ANR algorithm.
The MO removal is successful even if the MO does not exist. An MO can be
added both by the user and based on the ANR algorithm. If an existing MO is to
be added, the MO is modified when the user performs the addition, but it cannot
be added based on the ANR algorithm. When the ANR-related MOs are
automatically added based on the ANR algorithm, this parameter is set to
AUTO_MODE by default. When the ANR-related MOs are added by the user,
this parameter can be set to AUTO_MODE or MANUAL_MODE.

eNodeB ID Indicates the eNodeB ID defined in the service protocol interface, which
uniquely identifies an eNodeB within a PLMN. For details, see 3GPP TS
36.300.

Rim latest start time Indicates the start time of the latest RIM procedure towards the neighboring
GERAN cell.

Rim latest update time Indicates the time of the latest RIM request received by the neighboring
GERAN cell.

5.7.1.6.3.113 GeranNFGroupSCellOp
+-NE
+-eNodeBFunction
+-Cell
+-GeranNfreqGroup
+-GeranNFGroupSCellOp

Description

The GeranNFGroupSCellOp MO defines cell reselection dedicated priorities based on the


PLMN of the local cell for the GERAN carrier frequency group.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
GeranNfreqGroup

Relation with the CnOperator MO:


- CnOperatorID in a GeranNFGroupSCellOp MO must have been set in the associated
CnOperator MO.
Relation with the
EutranNFreqSCellOp,UtranNFreqSCellOp,Cdma2000BcSCellOp,EutranNFreqRanShare,
UtranRanShare,GeranRanShare MOs:
- Cell reselection priorities based on operators of the local cell (which are specified in the
EutranNFreqSCellOp, UtranNFreqSCellOp, GeranNFGroupSCellOp, and
Cdma2000BcSCellOp MOs) cannot coexist with cell reselection priorities based on operators of
neighboring frequencies (which are specified in the EutranNFreqRanShare, UtranRanShare,
and GeranRanShare MOs).
Relation with the EutranNFreqSCellOp MO:
- Cell reselection priorities specified in the EutranNFreqSCellOp and
GeranNFGroupSCellOp MOs for the same operator cannot be the same.
Relation with the UtranNFreqSCellOp MO:
- Cell reselection priorities specified in the GeranNFGroupSCellOp and
UtranNFreqSCellOp MOs for the same operator cannot be the same.
Relation with the Cdma2000BcSCellOp MO:
- Cell reselection priorities specified in the GeranNFGroupSCellOp and
Cdma2000BcSCellOp MOs for the same operator cannot be the same.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD Use this command to add the operator-specific configuration for neighboring
GERANNFGROUPSCE
LLOP GERAN frequency group of the serving cell.

LST Use this command to list operator-specific configuration for the neighboring
GERANNFGROUPSCE
LLOP GERAN frequency group of the serving cell.

MOD Use this command to modify the operator-specific configuration for neighboring
GERANNFGROUPSCE
LLOP GERAN frequency group of the serving cell.

RMV Use this command to remove an operator-specific configuration for serving cell
GERANNFGROUPSCE
LLOP in GERAN frequency group.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the ID of the local cell. It uniquely identifies a cell within an eNodeB.

BCCH group ID Indicates the index of the GERAN carrier frequency group. It uniquely identifies
a GERAN carrier frequency group.

Cn operator ID Indicates the ID of the operator.

Cell reselection Indicates whether to configure a dedicated cell-reselection priority based on the
dedicated priority
configure indicator PLMN ID of the local cell for the GERAN carrier frequency group.

Cell reselection Indicates the cell reselection dedicated priority for a GERAN frequency based
dedicated priority
on the PLMN ID of the local cell. The value 0 indicates the lowest priority. If
the related SPID configuration is specified, set this priority to the one specified
in the SPID configuration. If no related SPID configuration is specified but this
parameter is set, the eNodeB delivers the cell reselection priorities of all PLMNs
supported by a UE by using the IE idleModeMobilityControlInfo in an RRC
Connection Release message to the UE. If no related SPID configuration is
specified and this parameter is not set, a UE uses the cell reselection priority of
the neighboring GERAN carrier frequency group, which is broadcast in the
system information.
5.7.1.6.3.114 GeranNfreqGroup
+-NE
+-eNodeBFunction
+-Cell
+-GeranNfreqGroup
+-GeranNfreqGroupArfcn[0~31]
+-GeranNFGroupSCellOp[0~6]
+-GeranRanShare[0~4]

Description

A GeranNfreqGroup MO consists of the parameters related to a neighboring GERAN carrier


frequency group. The configuration of this MO is shared by all frequencies in the group, and is
used in measurement control for inter-RAT handovers and also used for inter-RAT cell
reselections to GERAN. If no operator is configured to share a neighboring GERAN carrier
frequency group, this group can be used by all operators of the current cell. If operators are
configured to share a neighboring GERAN carrier frequency group, this group can be used only
by the configured operators. For details, see 3GPP TS 36.331.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Possible children:
GeranNfreqGroupArfcn[0~31];GeranNFGroupSCellOp[0~6];GeranRanShare[0~4]

Relation with the GeranNcell,GeranExternalCell,GeranNfreqGroupArfcn MOs:


- GeranArfcn and BandIndicator in a GeranExternalCell MO corresponding to a
GeranNcell MO must be the same as GeranArfcn in a GeranNfreqGroupArfcn MO and
BandIndicator in the GeranNfreqGroup MO associated with the GeranNfreqGroupArfcn
MO, respectively. Alternatively, GeranArfcn and BandIndicator in a GeranExternalCell MO
corresponding to a GeranNcell MO must be the same as StartingArfcn and BandIndicator in a
GeranNfreqGroup MO, respectively.
Relation with the GeranNfreqGroup MO:
- Each GeranNfreqGroup MO must have a unique value of StartingArfcn and
BandIndicator for each cell.
Relation with the Cell MO:
- A maximum of 64 neighboring GERAN frequencies can be configured for each cell.
Neighboring GERAN frequencies consist of those specified by StartingArfcn in the
GeranNfreqGroup MOs and those specified by GeranArfcn in the GeranNfreqGroupArfcn
MOs.
- A maximum of 16 GeranNfreqGroup MOs can be configured for each cell.
Relation with the GeranNfreqGroupArfcn MO:
- In GeranNfreqGroup MOs of a cell, if BandIndicator values are the same, the value of
StartingArfcn in a GeranNfreqGroup must be different from the value of GeranArfcn in a
GeranNfreqGroupArfcn MO associated to BcchGroupId.
- In GeranNfreqGroup MOs of a cell, if BandIndicator values are the same, the
GeranArfcn values in GeranNfreqGroupArfcn MOs under GeranNfreqGroup MOs cannot
be the same.
- A maximum of 31 GeranNfreqGroupArfcn can be configured for each GeranNfreqGroup.
- Before adding a GeranNfreqGroupArfcn MO, ensure that the associated
GeranNfreqGroup MO has been configured.
Relation with the EutranInterNFreq MO:
- If CellReselPriorityCfgInd in EutranInterNFreq MO and GeranNfreqGroup MO is both
set to CFG, CellReselPriority cannot be set to a same value for each cell.
Relation with the CellResel MO:
- If CellReselPriorityCfgInd in GeranNfreqGroup MO is set to CFG, CellReselPriority in
CellResel MO cannot be set same as CellReselPriority in GeranNfreqGroup MO for each cell.
Relation with the UtranNFreq MO:
- If CellReselPriorityCfgInd in UtranNFreq MO and GeranNfreqGroup MO is both set to
CFG, CellReselPriority cannot be set to a same value for each cell.
Relation with the Cdma2000BandClass MO:
- If CellReselPriorityCfgInd in GeranNfreqGroup MO is set to CFG, and if
Cdma20001XrttCellReselInd in Cdma2000BandClass MO is set to CFG,
Cdma20001XrttCellReselPri in Cdma2000BandClass MO cannot be set same as
CellReselPriority in GeranNfreqGroup MO for each cell, and if
Cdma2000HrpdCellReselInd in Cdma2000BandClass MO is set to CFG,
Cdma2000HrpdCellReselPri in Cdma2000BandClass MO cannot be set same as
CellReselPriority in GeranNfreqGroup MO for each cell.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD Use this command to add a neighboring GERAN carrier frequency group.
GERANNFREQGROU
P

LST Use this command to list the parameters of the neighboring GERAN carrier
GERANNFREQGROU
P frequency group.

MOD Use this command to modify the configuration of a neighboring GERAN carrier
GERANNFREQGROU
P frequency group.

RMV Use this command to remove a neighboring GERAN carrier frequency group.
GERANNFREQGROU
P

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the cell ID of the local cell. It uniquely identifies a cell within an
eNodeB.

BCCH group ID Indicates a GERAN carrier frequency group. In the cell reselection procedure,
the GERAN carrier frequencies are organized in groups and the cell reselection
parameters are provided per group of GERAN carrier frequencies.

GERAN version Indicates the standard that is supported by the current carrier frequency group.

Starting ARFCN Indicates the first ARFCN in the GERAN carrier frequency group. If the
GERAN ARFCN is not between 512 and 810, one ARFCN can only in one
frequency band. For details, see 3GPP TS 45.005.

Band indicator Indicates the GERAN band indicator. If the GERAN ARFCN is between 512
and 810, this parameter indicates whether the GERAN ARFCN is in the 1800
MHz band or the 1900 MHz band. If the GERAN ARFCN is not in either band,
this parameter does not take effect and can be set to either value and one
ARFCN can only in one frequency band. For details, see 3GPP TS 45.005.

Cell reselection priority Indicates whether to set the reselection priority of the frequencies in the GERAN
configure indicator
carrier frequency group. If the value of this parameter is not configured, the UE
Table 2 Related parameters

Parameter Description

does not reselect to neighboring cells on the frequencies in the GERAN carrier
frequency group.

Cell reselection priority Indicates the cell reselection priority of the GERAN carrier frequency group.
The value 0 indicates the lowest priority. It is contained in system information
block type 7 (SIB7). The UE decides whether to reselect a neighboring cell on a
frequency in the GERAN carrier frequency group based on the value of this
parameter and the absolute priority of the serving cell. If the value of this
parameter is larger than the absolute priority of the serving cell, the UE starts
measurements on neighboring cells on the frequencies in the GERAN carrier
frequency group; then if the signal quality of some neighboring cells meets the
related conditions, the UE starts cell reselection. If the value of this parameter is
smaller than the absolute priority of the serving cell, the UE starts the
measurements only when the signal quality of the serving cell is poor; then if the
signal quality of some neighboring cells meets the related conditions, the UE
starts cell reselection. Frequencies used for different RATs must be assigned
different cell reselection priorities. For details, see 3GPP TS 36.331.

PMAX configure Indicates whether to set the maximum power that the UE can apply to
indicator
transmission on a frequency in the GERAN carrier frequency group. If the value
of this parameter is not specified, the maximum power is subject to the UE
capability.

PMAX Indicates the maximum power that the UE can apply to transmission on a
frequency in the GERAN carrier frequency group. It is used in cell reselection
criteria to calculate the compensated power. If the value of this parameter is not
specified, the maximum power is subject to the UE capability. For details, see
3GPP TS 36.304.

Minimum required RX Indicates the minimum RX level required for a neighboring cell on a frequency
level
in the GERAN carrier frequency group to become a candidate for selection. It is
included in criteria S and used in the evaluation for cell selection. During the
evaluation for cell reselection, the UE performs the following calculation:
Srxlev = Measured RSSI value of a neighboring cell on a frequency in the
GERAN carrier frequency group - Value of this parameter - Compensated
power. If Srxlev for a neighboring cell is better than a threshold for a time-to-
trigger, reselection to the cell is started. For details, see 3GPP TS 36.104.

High priority threshold Indicates the RX level required for a neighboring cell on a frequency in the
GERAN carrier frequency group to become a candidate for reselection if the
priority of the frequency is higher than that of the serving frequency.
After measurements are started for neighboring cells on a frequency in the
GERAN carrier frequency group, the UE reselects to a cell on the frequency
only if the RX level of the cell is better than the value specified by this
Table 2 Related parameters

Parameter Description

parameter for a time-to-trigger. For details, see 3GPP TS 36.104.

Lower priority threshold Indicates the RX level required for a neighboring cell on a frequency in the
GERAN carrier frequency group to become a candidate for reselection if the
priority of the frequency is lower than that of the serving frequency.
After measurements are started for neighboring cells on a frequency in the
GERAN carrier frequency group, the UE reselects to a cell on the frequency
only if the RX level of the serving cell is lower than a specified threshold and
that of the cell is better than the value specified by this parameter for a time-to-
trigger. For details, see 3GPP TS 36.104.

Frequency offset Indicates the frequency offset of the group of neighboring GERAN carrier
frequencies. This parameter is used in the decision of the UE to send
measurement reports for inter-RAT handovers. For details, see 3GPP TS 36.331.

NCC monitoring Indicates whether a BCCH carrier with the specific NCC is permitted for
permitted
monitoring. For details, see 3GPP TS 36.331.

Connect frequency Indicates the frequency group priority based on which the eNodeB selects a
priority
target frequency group for blind redirection or delivers a frequency group in
measurement configuration messages. If a blind redirection is triggered and the
target neighboring cell is not specified, the eNodeB selects a target frequency
group based on the setting of this parameter. If a measurement configuration is
to be delivered, the eNodeB preferentially delivers the frequency group with the
highest priority. If this parameter is set to 0 for a frequency group, this frequency
group is not selected as the target frequency group for a blind redirection. A
larger value indicates a higher priority.

5.7.1.6.3.115 GeranNfreqGroupArfcn
+-NE
+-eNodeBFunction
+-Cell
+-GeranNfreqGroup
+-GeranNfreqGroupArfcn

Description
A GeranNfreqGroupArfcn MO consists of the parameters related to an ARFCN in a neighboring
GERAN carrier frequency group. It is used in measurement control for both inter-RAT handover
to and cell reselection to GERAN. For details, see 3GPP TS 36.331.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
GeranNfreqGroup

Relation with the GeranNcell,GeranExternalCell,GeranNfreqGroup MOs:


- GeranArfcn and BandIndicator in a GeranExternalCell MO corresponding to a
GeranNcell MO must be the same as GeranArfcn in a GeranNfreqGroupArfcn MO and
BandIndicator in the GeranNfreqGroup MO associated with the GeranNfreqGroupArfcn
MO, respectively. Alternatively, GeranArfcn and BandIndicator in a GeranExternalCell MO
corresponding to a GeranNcell MO must be the same as StartingArfcn and BandIndicator in a
GeranNfreqGroup MO, respectively.
Relation with the Cell MO:
- A maximum of 64 neighboring GERAN frequencies can be configured for each cell.
Neighboring GERAN frequencies consist of those specified by StartingArfcn in the
GeranNfreqGroup MOs and those specified by GeranArfcn in the GeranNfreqGroupArfcn
MOs.
Relation with the GeranNfreqGroup MO:
- A maximum of 31 GeranNfreqGroupArfcn MOs can be configured for each
GeranNfreqGroup MO.
- In GeranNfreqGroup MOs of a cell, if BandIndicator values are the same, the value of
StartingArfcn in a GeranNfreqGroup must be different from the value of GeranArfcn in a
GeranNfreqGroupArfcn MO associated to BcchGroupId.
- In GeranNfreqGroup MOs of a cell, if BandIndicator values are the same, the
GeranArfcn values in GeranNfreqGroupArfcn MOs under GeranNfreqGroup MOs cannot
be the same.
- Before adding a GeranNfreqGroupArfcn MO, ensure that the associated
GeranNfreqGroup MO has been configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD Use this command to add a GERAN ARFCN to a neighboring GERAN carrier
GERANNFREQGROUP
ARFCN frequency group.

LST Use this command to list the parameters related to the neighboring GERAN
GERANNFREQGROUP
ARFCN ARFCN.

RMV Use this command to remove a neighboring GERAN ARFCN.


GERANNFREQGROUP
ARFCN

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the cell ID of the local cell. It uniquely identifies a cell within an
eNodeB.

BCCH group ID Indicates the index of the BCCH carrier frequency group. It identifies a BCCH
carrier frequency group.

GERAN ARFCN Specifies the ARFCN of the GERAN BCCH. If the GERAN ARFCN value is
not between 512 and 810, one ARFCN can only in one frequency band. For
details about this parameter, see 3GPP TS 45.005.

5.7.1.6.3.116 GeranRanShare
+-NE
+-eNodeBFunction
+-Cell
+-GeranNfreqGroup
+-GeranRanShare

Description
A GeranRanShare MO consists of the parameters related to information about an operator that
shares a neighboring GERAN carrier frequency group. In RAN sharing scenarios, operator-
specific neighboring GERAN carrier frequency groups can be configured as required.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
GeranNfreqGroup

Relation with the


EutranNFreqSCellOp,UtranNFreqSCellOp,GeranNFGroupSCellOp,Cdma2000BcSCellOp
,EutranNFreqRanShare,UtranRanShare MOs:
- Cell reselection priorities based on operators of the local cell (which are specified in the
EutranNFreqSCellOp, UtranNFreqSCellOp, GeranNFGroupSCellOp, and
Cdma2000BcSCellOp MOs) cannot coexist with cell reselection priorities based on operators of
neighboring frequencies (which are specified in the EutranNFreqRanShare, UtranRanShare,
and GeranRanShare MOs).
Relation with the GeranNfreqGroup MO:
- A maximum of four GeranRanShare MOs can be configured for each GeranNfreqGroup
MO.
Relation with the UtranRanShare MO:
- If CellReselPriorityCfgInd in UtranRanShare MO and GeranRanShare MO is both set
to CFG, Mcc, Mnc and CellReselPriority can not set to a same value for each cell.
Relation with the EutranNFreqRanShare MO:
- If CellReselPriorityCfgInd in GeranRanShare MO and EutranNFreqRanShare MO is
both set to CFG, Mcc, Mnc and CellReselPriority can not set to a same value for each cell.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add information about an operator that shares a
GERANRANSHARE
neighboring GERAN carrier frequency group.
Table 1 Related MML commands

MML Command Function

LST Use this command to list information about operators that share a neighboring
GERANRANSHARE
GERAN carrier frequency group.

MOD Use this command to modify information about an operator that shares a
GERANRANSHARE
neighboring GERAN carrier frequency group.

RMV Use this command to remove information about an operator that shares a
GERANRANSHARE
neighboring GERAN carrier frequency group.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the cell identity of the local cell. It uniquely identifies a cell within an
eNodeB.

BCCH group ID Indicates the index of the GERAN carrier frequency group. It uniquely identifies
a GERAN carrier frequency group.

Mobile country code Indicates the mobile country code (MCC) of the operator that shares the
neighboring GERAN carrier frequency group.
A public land mobile network (PLMN) ID is comprised of an MCC and a
mobile network code (MNC).
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, if the MCC is 123 and the MNC is 45, then the PLMN ID is
12345.

Mobile network code Indicates the mobile network code (MNC) of the operator that shares the
neighboring GERAN carrier frequency group.
A public land mobile network (PLMN) ID is comprised of a mobile country
code (MCC) and an MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, if the MCC is 123 and the MNC is 45, then the PLMN ID is
12345.
Table 2 Related parameters

Parameter Description

Cell reselection priority Indicates whether to configure the cell reselection priority of the operator that
configure indicator
shares the neighboring GERAN carrier frequency group.

Cell reselection priority Indicates the cell reselection priority of the operator that shares the neighboring
GERAN carrier frequency group. The value 0 indicates the lowest priority. If the
related SPID configuration is specified, set this priority to the one specified in
the SPID configuration. If no related SPID configuration is specified but this
parameter is set, the eNodeB delivers the cell reselection priorities of all PLMNs
supported by a UE by using the IE idleModeMobilityControlInfo in an RRC
Connection Release message to the UE. If no related SPID configuration is
specified and this parameter is not set, a UE uses the cell reselection priority of
the neighboring GERAN carrier frequency group, which is broadcast in the
system information.

5.7.1.6.3.117 GlobalProcSwitch
+-NE
+-eNodeBFunction
+-GlobalProcSwitch

Description

The GlobalProcSwitch MO consists of the switch of automatic X2 setup, the method of


automatic X2 setup, the scheduling request indication (SRI) adaptation switch, and logical
channel group profile.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

LST Use this command to list the settings of parameters related to some global
GLOBALPROCSWITC
H functions in the eNodeB.

MOD Use this command to modify the settings of parameters related to some global
GLOBALPROCSWITC
H functions in the eNodeB.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

The Switch of X2 setup Indicates whether to enable or disable X2 setup by SON.


by SON

The method of X2 setup Indicates the method of X2 setup by SON, that is, the method of automatically
by SON
setting up X2 interfaces. The value X2_OVER_M2000 can be set only for
Huawei eNodeBs, and the value X2_OVER_S1 can be set for any eNodeB.

SRI adaptive switch Indicates whether to enable scheduling request indication (SRI) adaptation. If
this switch is turned on, the SRI period adaptively changes based on the SRI
algorithm. If this switch is turned off, the SRI period is the value of the
SriPeriod parameter in the CellStandardQci MO.

LCG Profile Indicates whether to set a logical channel group profile.


Currently, two logical channel group profiles are available: LCG_PROFILE_0
and LCG_PROFILE_1. If LCG_PROFILE_0 is used, only one logical channel
group is assigned to non-GBR services. If LCG_PROFILE_1 is used, two
logical channel groups are assigned to non-GBR services: one to high-priority
non-GBR services and the other to low-priority non-GBR services.

RNC POOL HO RIM Indicates whether to enable or disable RAN information management (RIM) for
Switch
handovers within an RNC pool. An RNC pool can be used for load balancing
between RNCs. An RNC can take over a cell that was controlled by another
RNC in the pool.

UU Message Indicates whether the eNodeB simultaneously sends Uu messages during


Simultaneous Sending
Switch security mode activation and reconfiguration. If this switch is turned on, the
eNodeB simultaneously sends Uu messages. If this switch is turned off, the
Table 2 Related parameters

Parameter Description

eNodeB sends Uu messages one by one.

Update eNB Indicates whether the eNodeB automatically updates the configuration of
Configuration Via X2
Switch neighboring cells based on the messages received over the X2 interface. The
messages include X2 SETUP REQUEST, X2 SETUP RESPONSE, and ENB
CONFIGURATION UPDATE.
Turn off the switch if the eNodeB configuration data on a network is to be
modified by using the interlocking modification function on the CME and
modifications to the parameters of a neighboring eNodeB will be updated on the
local eNodeB through messages over the X2 interface. These parameters include
eNodeBId, CellId, LocalCellId, CnOperator, CnOperatorTa, CellOp, PhyCellId,
and DlEarfcn. This prevents the configuration data from being lost or abnormal
during the automatic update.
This switch must be turned on if the interlocking modification function on the
CME is not used and the eNodeB configuration data on a network is to be
modified by using the automatic eNodeB configuration update over the X2
interface.

X2 Auto Setup Switch Indicates whether to enable the X2 interface self-setup function for the target
Via Target Operator
operator.

X2 Son TNL Select Indicates whether to select transport network layer (TNL) parameters based on
Mode
the primary PLMN ID or selected PLMN ID that contained in the SON
configuration message. This parameter is used for X2 self-setup in RAN sharing
scenarios. Selecting TNL parameters based on the primary PLMN ID applies to
X2 self-setup between eNodeBs provided by different suppliers. For X2 self-
setup between Huawei eNodeBs, selecting TNL parameters based on the
selected PLMN ID is used in preference.

Choose UMTS Cell Indicates the UMTS load transmission channel. The eNodeB sends RAN-
Load Info Trans
Channel INFORMATION-REQUEST PDUs to UTRAN cells to request multiple reports
on the load status of UTRAN cells only when the parameter is set to
BASED_ON_RIM.The function specified by the parameter value
BASED_ON_ECO is temporarily unavailable.

S1 handover in data Indicates the switch controlling the data forwarding mechanism in S1-based
forwarding switch
incoming handovers.
If the switch is turned off, uplink data forwarding and downlink data forwarding
are separately determined.
If this switch is turned on, uplink data forwarding and downlink data forwarding
are determined together. The target eNodeB sends the destination address to the
source eNodeB only if both uplink data and downlink data need to be forwarded.
If either the uplink data or downlink data does not need to be forwarded, the
Table 2 Related parameters

Parameter Description

target eNodeB does not send the destination address to the source eNodeB.

RRC Reest Protect Indicates the RRC connection reestablishment protection threshold. UE
Threshold
manufacturers may have different understanding of protocols, and therefore UE
compliance with protocols varies and may be different from eNodeB compliance
with the same protocols. After a UE initiates an RRC connection reestablishment
procedure due to reconfigurationFailure and the reestablishment is complete, the
subsequent RRC connection reconfiguration may fail again. As a result, the UE
initiates an RRC connection reestablishment procedure again. If this repeatedly
happens, the UE repeatedly initiates RRC connection reestablishment. If this
parameter is set to 0, the function of RRC connection reestablishment protection
is not used. If this parameter is set to a value other than 0, the eNodeB rejects
the RRC connection reestablishment request due to reconfigurationFailure from
a UE when the number of RRC connection reestablishment requests initiated by
the UE served by the eNodeB due to reconfigurationFailure has exceeded the
parameter value within 1 minute.

The Timer of X2 delete Indicates the time during which the X2 interface configuration is retained for a
by SON
local eNodeB and a peer eNodeB when the two eNodeBs do not have a neighbor
relationship with each other. If the X2 interface configuration is retained for a
local eNodeB and a peer eNodeB and the local eNodeB determines that a
neighbor relationship is not configured for the local and peer eNodeBs, the local
eNodeB starts the timer and removes the X2 interface configuration when the
timer expires. If this parameter is set to 0, the function of automatic X2 interface
configuration removal is disabled.

RIM Coding Policy Indicates the eNodeB coding scheme for Global eNodeB ID IE and Reporting
Cell ID IE in the RIM message. If the EPC devices that exchange RIM messages
with eNodeBs are provided by Huawei and the peer devices adopt the private
coding scheme, set this parameter to Private Coding. In other cases, set this
parameter to Standard Coding.

L2GU Handover Indicates whether the handover request message for a handover from E-UTRAN
Required With LTE Cap
Switch to UTRAN or GERAN contains the UE-EUTRA-Capability information
element (IE).

Different Operator With Indicates whether MMEs of operators that share the eNodeB can be configured
Same MMEC Switch
with the same mobility management entity code (MMEC). If this parameter is
set to OFF(Off), MMEs of operators that share the eNodeB cannot be configured
with the same MMEC. If this parameter is set to ON(On), MMEs of operators
that share the eNodeB can be configured with the same MMEC.
5.7.1.6.3.118 HoMeasComm
+-NE
+-eNodeBFunction
+-HoMeasComm

Description

The HoMeasComm MO consists of the common parameters that are related to handover
measurements. These parameters include the gap pattern and the L3 filtering coefficients for
different systems.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST HOMEASCOMM Use this command to list the common measurement parameters for handover.

MOD HOMEASCOMM Use this command to modify the common measurement parameters for
handover.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

GAP measurement Indicates the measurement gap pattern.


pattern
The eNodeB defines measurement gaps for UEs in connected mode. During the
measurement gaps, a UE measures the signal quality of the cells on a specific
frequency.
There are two gap patterns: pattern 1 and pattern 2. In pattern 1, the gap width is
6 ms and the repetition period is 40 ms. In pattern 2, the gap width is 6 ms and
the repetition period is 80 ms. For details, see 3GPP TS 36.331. Pattern 1 and
pattern 2 correspond to Gap Pattern Id 0 and Gap Pattern Id 1 in 3GPP TS
36.331, respectively.

EUTRAN RSRP filter Indicates the upper-layer filtering coefficient for RSRP measurements on E-
coefficient
UTRAN.
A larger value of this parameter indicates a stronger smoothing effect and higher
resistance to fast fading, but it may weaken the tracing capability towards
varying signals. For details, see 3GPP TS 36.331.

EUTRAN RSRQ filter Indicates the upper-layer filtering coefficient for RSRQ measurements on E-
coefficient
UTRAN.
A larger value of this parameter indicates a stronger smoothing effect and higher
resistance to fast fading, but it may weaken the tracing capability towards
varying signals. For details, see 3GPP TS 36.331.

GERAN filter coefficient Indicates the L3 filtering coefficient used for the measurement quantity in inter-
RAT measurements of GERAN.
A great value of this parameter indicates a strong smoothing effect and a high
anti-fast-fading capability, but a low signal change tracing capability. For details,
see 3GPP TS 36.331.

SMeasureInd Indicates whether the measurement threshold needs to be set.

SMeasure Indicates the threshold below which measurements on neighboring cells are
started. If the signal quality of the serving cell exceeds this threshold, the UE is
not required to perform intra-frequency, inter-frequency, or inter-RAT
measurements, leading to reduced power consumption. The value -141 does not
take effect, and is reserved for forward compatibility. If this parameter is set to
-141, the value -140 is used as the threshold in implementation.

SpeedDependInd Indicates whether mobility-based cell handover measurement parameters need to


be set.

TCRmax in connected Indicates the cycle during which evaluations of the UE medium and high
mode
mobility states in RRC_CONNECTED mode are performed. It is one of the key
parameters in deciding on a UE's mobility state. If this parameter is set to a
Table 2 Related parameters

Parameter Description

small value, switchings among mobility states may be frequent and the decision
precision may be relatively low. If this parameter is set to a large value,
switchings among mobility states are less frequent and the decision precision is
relatively high.

TCRmaxHyst in Indicates the cycle during which evaluations of the UE normal mobility state in
connected mode
RRC_CONNECTED mode are performed. It is one of the key parameters in
deciding on a UE's mobility state. If this parameter is set to a small value,
switchings among mobility states may be frequent and the decision precision
may be relatively low. If this parameter is set to a large value, switchings among
mobility states are less frequent and the decision precision is relatively high.

NCR Medium in Indicates the handover number threshold used in the UE medium mobility state
connected mode
evaluation. If the number of handovers performed during a period of time
specified by the TcrMaxConnMode parameter exceeds the value of this
parameter, the UE is considered to be in medium mobility state and its
handover-related parameters are adjusted.

NCR High in connected Indicates the handover number threshold used in the UE high mobility state
mode
evaluation. If the number of handovers performed during a period of time
specified by the TcrMaxConnMode parameter exceeds the value of this
parameter, the UE is considered to be in high mobility state and its handover-
related parameters are adjusted.

TTT Scaling factor for Indicates the scaling factor for the time-to-trigger defined for medium-mobility
Medium mobility state
in connected mode UEs. For a UE in medium mobility, the time-to-trigger used in event evaluation
is multiplied by this scaling factor, to facilitate triggering of the handover.

TTT Scaling factor for Indicates the scaling factor for the time-to-trigger defined for high-mobility
High mobility state in
connected mode UEs. For a UE in high mobility, the time-to-trigger used in event evaluation is
multiplied by this scaling factor, to facilitate triggering of the handover.

UTRAN RSCP filter Indicates the filtering coefficient for RSCP measurements on UTRAN.
coefficient
A larger value of this parameter indicates a stronger smoothing effect and higher
resistance to fast fading, but it may weaken the tracing capability towards
varying signals. For details, see 3GPP TS 36.331.

UTRAN ECN0 filter Indicates the upper-layer filtering coefficient for Ec/No measurements on
coefficient
UTRAN.
A larger value of this parameter indicates a stronger smoothing effect and higher
resistance to fast fading, but it may weaken the tracing capability towards
varying signals. For details, see 3GPP TS 36.331.
5.7.1.6.3.119 IbdlInfo
Description

This MO consists of the parameters used to identify Internal Baseband Data Link Information.

Effective Scenario

Immediately

Relations Between MOs

None

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP IBDLINFO Use this command to query information about the LBBP data link.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local cell identity of the cell. It uniquely identifies a cell within an
eNodeB.

Connect eNodeB ID Indicates the ID of the eNodeB to which the RRU/RFU connected.

RRU/RFU Cabinet No. Indicates the cabinet number of the RRU/RFU.

RRU/RFU Subrack No. Indicates the subrack number of the RRU/RFU.

RRU/RFU Slot No. Indicates the slot number of the RRU/RFU.


Table 2 Related parameters

Parameter Description

Number of LBBP Data Indicates the number of LBBP data links.


Links

LBBP Data Link ID Indicates the LBBP data link ID.

LBBP Data Link Status Indicates the status of the LBBP data link.

ODI ID Indicates the open DU interface (ODI) ID.

LBBP Data Link Input Indicates the input port number of the LBBP data link.
Port No.

LBBP Data Link Output Indicates the output port number of the LBBP data link.
Port No.

LBBP Data Link Indicates the loopback delay on the LBBP data link.
Loopback Delay (us)

LBBP Data Link Indicates the number of loopback timeouts on the LBBP data link.
Loopback Timeout
Counter

Board Cabinet No. Indicates the cabinet number of the board involved in data link transmission.

Board Subrack No. Indicates the subrack number of the board involved in data link transmission.

Board Slot No. Indicates the slot number of the board involved in data link transmission.

Parent topic: Radio-tree

5.7.1.6.3.120 InterFreqBlkCell
+-NE
+-eNodeBFunction
+-Cell
+-InterFreqBlkCell

Description

An InterFreqBlkCell MO consists of the parameters related to a blacklisted inter-frequency cell.


The blacklist is contained in SIB5 and measurement object information that are delivered to UEs.
Handover and reselection to blacklisted cells are prohibited for UEs in connected mode and those
in idle mode, respectively. For details, see 3GPP TS 36.331.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the Cell MO:


- A maximum of 32 InterFreqBlkCell MOs can be configured for each cell.
Relation with the EutranInterNFreq MO:
- DlEarfcn in an InterFreqBlkCell MO must be the same as DlEarfcn in an
EutranInterNFreq MO for each cell.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add an inter-frequency E-UTRAN cell to the blacklist.
INTERFREQBLKCELL

LST Use this command to list the parameters of the blacklisted inter-frequency E-
INTERFREQBLKCELL
UTRAN cell.

MOD Use this command to modify an E-UTRAN blacklist of inter-frequency cells.


INTERFREQBLKCELL

RMV Use this command to remove an inter-frequency E-UTRAN cell from the
INTERFREQBLKCELL
blacklist.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Local cell ID Indicates the cell ID of the local cell. It uniquely identifies a cell within an
eNodeB.

Downlink EARFCN Indicates the DL EARFCN of the inter-frequency blacklisted cell. For details,
see 3GPP TS 36.104.

Start physical cell ID Indicates the starting physical cell ID of the inter-frequency blacklisted cell. For
details, see 3GPP TS 36.331.

Cell name Indicates the name of the inter-frequency blacklisted cell.

Physical cell ID range Indicates the physical cell ID range of the inter-frequency blacklisted cell. For
details, see 3GPP TS 36.331.

5.7.1.6.3.121 InterFreqHoGroup
+-NE
+-eNodeBFunction
+-Cell
+-InterFreqHoGroup

Description

An InterFreqHoGroup MO is a group of parameters related to inter-frequency handover.


Different MOs of this class will be associated with different QCIs to meet various requirements
of services for the target cell. For details, see 3GPP TS 36.331.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the CellStandardQci MO:


- InterFreqHoGroupId in a CellStandardQci MO must have been set in the associated
InterFreqHoGroup MO.
Relation with the CellExtendedQci MO:
- InterFreqHoGroupId in a CellExtendedQci MO must have been set in the associated
InterFreqHoGroup MO.
Relation with the CnOperatorHoCfg MO:
- The sum of the value of InterFreqHoA2ThdRsrp in the InterFreqHoGroup MO and the
value of TddIfHoA2ThdRsrpOffset in the CnOperatorHoCfg MO cannot be greater than the
value of InterFreqHoA1ThdRsrp in the InterFreqHoGroup MO.
- The sum of the value of InterFreqHoA2ThdRsrp in the InterFreqHoGroup MO and the
value of FddIfHoA2ThdRsrpOffset in the CnOperatorHoCfg MO cannot be greater than the
value of InterFreqHoA1ThdRsrp in the InterFreqHoGroup MO.
- The sum of the value of A3InterFreqHoA2ThdRsrp in the InterFreqHoGroup MO and
the value of TddIfHoA2ThdRsrpOffset in the CnOperatorHoCfg MO cannot be greater than
the value of A3InterFreqHoA1ThdRsrp in the InterFreqHoGroup MO.
- The sum of the value of A3InterFreqHoA2ThdRsrp in the InterFreqHoGroup MO and
the value of FddIfHoA2ThdRsrpOffset in the CnOperatorHoCfg MO cannot be greater than
the value of A3InterFreqHoA1ThdRsrp in the InterFreqHoGroup MO.
Relation with the Cell MO:
- LocalCellId in an InterFreqHoGroup MO must have been set in the associated Cell MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add a parameter group related to inter-frequency handover.
INTERFREQHOGROU
P

LST Use this command to list one or all parameter groups related to inter-frequency
INTERFREQHOGROU
P handover.

MOD Use this command to modify a parameter group related to inter-frequency


INTERFREQHOGROU
P handover.

RMV Use this command to remove a parameter group related to inter-frequency


INTERFREQHOGROU
P handover.
Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Interfreq handover Indicates the ID of the parameter group related to inter-frequency handover.
group ID

Interfreq A1A2 Indicates the hysteresis for inter-frequency measurement events A1 and A2. This
hysteresis
parameter is used to prevent frequent triggering of event evaluation caused by
radio signal fluctuation. In this way, the probability of ping-pong handovers or
handover decision errors is reduced. A larger value of this parameter results in a
lower probability.

Interfreq A1A2 time to Indicates the time-to-trigger for inter-frequency measurement event A1 or A2.
trigger
When detecting that the signal quality in the serving cell meets the triggering
condition, the UE does not send a measurement report to the eNodeB
immediately. Instead, the UE sends a report only when the signal quality
continuously meets the entering condition during the time-to-trigger. This
parameter helps decrease the number of occasionally triggered event reports, the
average number of handovers, and the number of wrong handovers. In summary,
it helps prevent unnecessary handovers.

Interfreq A1 RSRP Indicates the RSRP threshold for inter-frequency measurement event A1.
threshold
When the measured RSRP value exceeds this threshold, a measurement report
will be sent. The value -141 does not take effect and is reserved for forward
compatibility. If this parameter is set to -141, the value -140 is used as the
threshold in implementation.

Interfreq A1 RSRQ Indicates the RSRQ threshold for inter-frequency measurement event A1.
threshold
When the measured RSRQ value exceeds this threshold, a measurement report
will be sent.

Interfreq A2 RSRP Indicates the RSRP threshold for inter-frequency measurement event A2.
threshold
When the measured RSRP value is below the threshold, a measurement report
will be sent. The value -141 does not take effect and is reserved for forward
compatibility. If this parameter is set to -141, the value -140 is used as the
threshold in implementation.

Interfreq A2 RSRQ Indicates the RSRQ threshold for inter-frequency measurement event A2.
threshold
When the measured RSRQ value is below this threshold, a measurement report
will be sent.
Table 2 Related parameters

Parameter Description

Interfreq handover Indicates the hysteresis for event A4. This parameter is used to prevent frequent
hysteresis
triggering of event evaluation caused by radio signal fluctuation. In this way, the
probability of ping-pong handovers or handover decision errors is reduced. A
larger value of this parameter results in a lower probability.

CoverageBased Indicates the RSRP threshold for event A4 related to coverage-based inter-
Interfreq RSRP
threshold frequency handover. When the measured RSRP value exceeds this threshold, an
inter-frequency measurement report will be sent. The value -141 does not take
effect and is reserved for forward compatibility. If this parameter is set to -141,
the value -140 is used as the threshold in implementation.The value of this
parameter is also used as the RSRP threshold for event A4 related to distance-
based, UL-power-based, or SPID-based inter-frequency handover back to the
HPLMN.

CoverageBased Indicates the RSRQ threshold for event A4 related to coverage-based inter-
Interfreq RSRQ
threshold frequency handover. When the measured RSRQ value exceeds this threshold, an
inter-frequency measurement report will be sent.The value of this parameter is
also used as the RSRQ threshold for event A4 related to distance-based, UL-
power-based, or SPID-based inter-frequency handover back to the HPLMN.

Interfreq HandOver Indicates the time-to-trigger for event A4 for the inter-frequency handover.
Time to Trigger
When detecting that the signal quality in at least one neighboring cell meets the
entering condition, the UE does not send a measurement report to the eNodeB
immediately. Instead, the UE sends a report only when the signal quality
continuously meets the entering condition during the time-to-trigger.
This parameter helps decrease the number of occasionally triggered event
reports, the average number of handovers, and the number of wrong handovers.
In summary, it helps prevent unnecessary handovers.

Load Based Interfreq Indicates the RSRP threshold for event A4 related to load-based inter-frequency
RSRP threshold
handover. When the measured RSRP value exceeds this threshold, an inter-
frequency measurement report will be sent. The value -141 does not take effect
and is reserved for forward compatibility. If this parameter is set to -141, the
value -140 is used as the threshold in implementation.The value of this
parameter is also used as the RSRP threshold for event A4 related to frequency-
priority-based or service-based inter-frequency handover.

Load Based Interfreq Indicates the RSRQ threshold for event A4 related to load-based inter-frequency
RSRQ threshold
handover. When the measured RSRQ value exceeds this threshold, an inter-
frequency measurement report will be sent.The value of this parameter is also
used as the RSRQ threshold for event A4 related to frequency-priority-based or
service-based inter-frequency handover.

Freq Priority Based Indicates the RSRP threshold for frequency-priority-based inter-frequency
Table 2 Related parameters

Parameter Description

Interfreq A1 RSRP measurement event A1. When the measured RSRP value exceeds this threshold,
threshold
an event A1 report will be sent. The value -141 does not take effect, and is
reserved for forward compatibility. If this parameter is set to -141, the value
-140 is used as the threshold in implementation.

Freq Priority Based Indicates the RSRQ threshold for frequency-priority-based inter-frequency
Interfreq A1 RSRQ
threshold measurement event A1.
When the measured RSRQ value exceeds this threshold, an event A1 report will
be sent.

Interfreq A3 offset Indicates the offset for event A3 associated with inter-frequency handover. This
parameter determines the border between the serving cell and the neighboring
cell. If the parameter is set to a large value, an inter-frequency handover is
performed only when the signal quality of the neighboring cell is significantly
better than that of the serving cell and other triggering conditions are met. For
details, see 3GPP TS 36.331.

A3 based interfreq A1 Indicates the RSRP threshold for event A1 associated with event-A3-triggered
RSRP threshold
inter-frequency handover. When the measured RSRP value exceeds this
threshold, a measurement report will be sent. The value -141 does not take effect
and is reserved for forward compatibility. If this parameter is set to -141, the
value -140 is used as the threshold in implementation.

A3 based Interfreq A2 Indicates the RSRP threshold for event A2 associated with event-A3-triggered
RSRP threshold
inter-frequency handover. When the measured RSRP value is below the
threshold, a measurement report will be sent. The value -141 does not take effect
and is reserved for forward compatibility. If this parameter is set to -141, the
value -140 is used as the threshold in implementation.

Freq Priority Based Indicates the RSRP threshold for frequency-priority-based inter-frequency
Interfreq A2 RSRP
threshold measurement event A2.
If the measured RSRP value is less than this threshold, an event A2 report will
be sent.

Freq Priority Based Indicates the RSRQ threshold for inter-frequency measurement event A2.
Interfreq A2 RSRQ
threshold When the measured RSRQ value is below this threshold, a measurement report
will be sent.

5.7.1.6.3.122 InterPlmnHoList
+-NE
+-eNodeBFunction
+-CnOperator
+-InterPlmnHoList

Description

An InterPlmnHoList MO consists of the parameters about a pair of source and target public land
mobile networks (PLMNs) for inter-PLMN handovers. If inter-PLMN handovers are allowed,
specify each PLMN pair between which UEs can be handed over. If inter-PLMN handovers are
not allowed, the settings of PLMN pairs do not take effect. If inter-PLMN handovers are not
required, do not configure this MO.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
CnOperator

Relation with the CnOperator MO:


- A maximum of eight InterPlmnHoList MOs can be configured for each CnOperator MO.
- CnOperatorId in an InterPlmnHoList MO must have been set in the associated
CnOperator MO.
- If TarMcc in an InterPlmnHoList MO is the same as Mcc in the CnOperator MO
corresponding to CnOperatorId in the InterPlmnHoList MO, TarMnc in the
InterPlmnHoList MO must be different from Mnc in the CnOperator MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add InterPlmnHo information.


INTERPLMNHOLIST

LST Use this command to list InterPlmnHo information.


INTERPLMNHOLIST

RMV Use this command to remove InterPlmnHo information.


INTERPLMNHOLIST
Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

CN Operator ID Indicates the index of the operator.

Target Mobile country Indicates the mobile country code of the target PLMN.
code

Target Mobile network Indicates the mobile network code of the target PLMN.
code

5.7.1.6.3.123 InterRatCellShutdown
+-NE
+-eNodeBFunction
+-Cell
+-InterRatCellShutdown

Description

The InterRatCellShutdown MO consists of the parameters related to inter-RAT cell shutdown. if


inter-RAT cell shutdown is enabled, UEs in a lightly loaded E-UTRAN cell are handed over or
redirected to neighboring UTRAN cells. Then, the E-UTRAN cell does not serve any UEs. In
this situation, the carrier of this cell can be shut down to achieve energy conservation and
emission reduction. For this version only support intelligent power-off of carriers in the same
coverage of UMTS network.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands


Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the configuration of inter-RAT cell shutdown.
INTERRATCELLSHUT
DOWN

MOD Use this command to modify the configuration of inter-RAT cell shutdown. A
INTERRATCELLSHUT
DOWN cell requiring inter-RAT cell shutdown must be configured with neighboring
UTRAN cells. Meanwhile, this cell cannot be configured as a basic cell for
intelligent power-off of carriers in the same coverage. For this version only
support intelligent power-off of carriers in the same coverage of UMTS network.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local identity of the cell. It uniquely identifies a cell within an
eNodeB.

Inter-RAT cell shutdown Indicates the switch used to enable or disable inter-RAT joint shutdown.
switch

Start time Indicates the start time of inter-RAT cell shutdown. If the switch for inter-RAT
cell shutdown is turned on, inter-RAT cell shutdown can be performed during
the period specified by the start time and stop time of inter-RAT cell shutdown.

Stop time Indicates the stop time of inter-RAT cell shutdown. If the stop time is earlier
than or the same as the start time, the stop time is assumed to be the time of the
next day. If the switch for inter-RAT cell shutdown is turned on, inter-RAT cell
shutdown can be performed during the period specified by the start time and
stop time of inter-RAT cell shutdown.

UE number threshold Indicates the threshold number of UEs served by the cell. Inter-RAT cell
shutdown is performed if shutdown conditions are met and the number of UEs
served by the cell is less than or equal to this threshold. The shutdown
conditions include the inter-RAT cell shutdown switch, specified duration, and
UL/DL physical resource block (PRB) thresholds. In this situation, the eNodeB
automatically hands over or redirects the UEs in the E-UTRAN cell to UTRAN
cells, and then shuts down the carrier of the E-UTRAN cell.
Table 2 Related parameters

Parameter Description

Downlink PRB Indicates the threshold of DL RB usage in the cell. Inter-RAT cell shutdown is
threshold
performed if shutdown conditions are met and the real-time UL RB usage and
DL RB usage in the cell are less than or equal to the thresholds specified by
UlPrbThd and DlPrbThd, respectively. The shutdown conditions include the
setting of the inter-RAT cell shutdown switch, specified duration, and threshold
of the number of UEs served by the cell. In this situation, the eNodeB
automatically hands over or redirects the UEs in the E-UTRAN cell to UTRAN
cells, and then shuts down the carrier of the E-UTRAN cell.

Uplink PRB threshold Indicates the threshold of UL RB usage in the cell. Inter-RAT cell shutdown is
performed if shutdown conditions are met and the real-time UL RB usage and
DL RB usage in the cell are less than or equal to the thresholds specified by
UlPrbThd and DlPrbThd, respectively. The shutdown conditions include the
setting of the inter-RAT cell shutdown switch, specified duration, and threshold
of the number of UEs served by the cell. In this situation, the eNodeB
automatically hands over or redirects the UEs in the E-UTRAN cell to UTRAN
cells, and then shuts down the carrier of the E-UTRAN cell.

5.7.1.6.3.124 InterRatHoCdma1xRttGroup
+-NE
+-eNodeBFunction
+-Cell
+-InterRatHoCdma1xRttGroup

Description

An InterRatHoCdma1xRttGroup MO is a group of parameters related to inter-RAT handover to


CDMA2000 1xRTT. Different MOs of this class will be associated with different QCIs to meet
various requirements of services for the target cell. For details, see 3GPP TS 36.331.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the CellStandardQci MO:


- InterRatHoCdma1xRttGroupId in a CellStandardQci MO must have been set in the
associated InterRatHoCdma1xRttGroup MO.
Relation with the CellExtendedQci MO:
- InterRatHoCdma1xRttGroupId in a CellExtendedQci MO must have been set in the
associated InterRatHoCdma1xRttGroup MO.
Relation with the Cell MO:
- LocalCellId in an InterRatHoCdma1xRttGroup MO must have been set in the associated
Cell MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add a parameter group related to inter-RAT handover to
INTERRATHOCDMA1X
RTTGROUP CDMA2000 1xRTT.

LST Use this command to list one or all parameter groups related to inter-RAT
INTERRATHOCDMA1X
RTTGROUP handover to CDMA2000 1xRTT.

MOD Use this command to modify a parameter group related to inter-RAT handover to
INTERRATHOCDMA1X
RTTGROUP CDMA2000 1xRTT.

RMV Use this command to remove a parameter group related to inter-RAT handover
INTERRATHOCDMA1X
RTTGROUP to CDMA2000 1xRTT.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.
Table 2 Related parameters

Parameter Description

InterRAT handover to Indicates the ID of the parameter group related to inter-RAT handover to
CDMA20001xRTT
group ID CDMA2000 1xRTT.

CDMA20001XRTT Indicates the hysteresis for event B1 for inter-RAT handover to CDMA2000
handover hysteresis
1xRTT. This parameter is used to prevent frequent triggering of event evaluation
caused by radio signal fluctuation. In this way, the probability of ping-pong
handovers or handover decision errors is reduced. A larger value of this
parameter results in a lower probability of ping-pong handovers or handover
decision errors.

CoverageBased Indicates the pilot strength threshold for event B1 related to coverage-based
CDMA20001XRTT
trigger threshold inter-RAT handover to CDMA2000 1xRTT. When the measurement value
exceeds this threshold, a measurement report will be sent.

CDMA20001XRTT time Indicates the time-to-trigger for event B1 related to inter-RAT handover to
to trigger
CDMA2000 1xRTT.
When detecting that the signal quality in at least one neighboring cell meets the
entering condition, the UE does not send a measurement report to the eNodeB
immediately. Instead, the UE sends a report only when the signal quality
continuously meets the entering condition during the time-to-trigger.
This parameter helps decrease the number of occasionally triggered event
reports, the average number of handovers and the number of wrong handovers,
preventing unnecessary handovers.

Load Service Based Indicates the pilot strength threshold for event B1 related to load- or service-
CDMA20001XRTT
trigger threshold based inter-RAT handover to CDMA2000 1xRTT.
When the measurement value exceeds this threshold, a measurement report will
be sent.

5.7.1.6.3.125 InterRatHoCdmaHrpdGroup
+-NE
+-eNodeBFunction
+-Cell
+-InterRatHoCdmaHrpdGroup

Description
An InterRatHoCdmaHrpdGroup MO is a group of parameters related to inter-RAT handover to
CDMA2000 HRPD. Different MOs of this class will be associated with different QCIs to meet
various requirements of services for the target cell. For details, see 3GPP TS 36.331.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the CellStandardQci MO:


- InterRatHoCdmaHrpdGroupId in a CellStandardQci MO must have been set in the
associated InterRatHoCdmaHrpdGroup MO.
Relation with the CellExtendedQci MO:
- InterRatHoCdmaHrpdGroupId in a CellExtendedQci MO must have been set in the
associated InterRatHoCdmaHrpdGroup MO.
Relation with the Cell MO:
- LocalCellId in an InterRatHoCdmaHrpdGroup MO must have been set in the associated
Cell MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add a parameter group related to inter-RAT handover to
INTERRATHOCDMAH
RPDGROUP CDMA2000 HRPD.

LST Use this command to list one or all parameter groups related to inter-RAT
INTERRATHOCDMAH
RPDGROUP handover to CDMA2000 HRPD.

MOD Use this command to modify a parameter group related to inter-RAT handover to
INTERRATHOCDMAH
RPDGROUP CDMA2000 HRPD.

RMV Use this command to remove a parameter group related to inter-RAT handover
INTERRATHOCDMAH
RPDGROUP to CDMA2000 HRPD.
Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

InterRAT handover to Indicates the ID of the parameter group related to inter-RAT handover to
CDMA2000HRPD
group ID CDMA2000 HRPD.

CDMA2000HRPD Indicates the hysteresis for event B1 related to inter-RAT handover to


handover hysteresis
CDMA2000 HRPD. This parameter is used to prevent frequent triggering of
event evaluation caused by radio signal fluctuation. In this way, the probability
of ping-pong handovers or handover decision errors is reduced. A larger value of
this parameter results in a lower probability of ping-pong handovers or handover
decision errors.

CoverageBased Indicates the pilot strength threshold for event B1 related to load- or service-
CDMA2000HRPD
trigger threshold based inter-RAT handover to CDMA2000 HRPD.
When the measurement value exceeds this threshold, a measurement report will
be sent.

CDMA2000HRPD time Indicates the time-to-trigger for event B1 related to inter-RAT handover to
to trigger
CDMA2000 HRPD.
When detecting that the signal quality in at least one neighboring cell meets the
entering condition, the UE does not send a measurement report to the eNodeB
immediately. Instead, the UE sends a report only when the signal quality
continuously meets the entering condition during the time-to-trigger.
This parameter helps decrease the number of occasionally triggered event
reports, the average number of handovers and the number of wrong handovers,
preventing unnecessary handovers.

Load Service Based Indicates the pilot strength threshold for event B1 related to load- or service-
CDMA2000HRPD
trigger threshold based inter-RAT handover to CDMA2000 HRPD.
When the measurement value exceeds this threshold, a measurement report will
be sent.

Cdma2000 HRPD Indicates the B2 RSRP threshold 1 used during optimized handovers from E-
Optimized handover B2
RSRP thld1 UTRAN to CDMA2000 eHRPD.

Cdma2000 HRPD Indicates the B2 RSRQ threshold 1 used during optimized handovers from E-
Optimized handover B2
RSRQ thld1 UTRAN to CDMA2000 eHRPD.
5.7.1.6.3.126 InterRatHoComm
+-NE
+-eNodeBFunction
+-InterRatHoComm

Description

The InterRatHoComm MO consists of the common eNodeB-level parameters that are related to
inter-RAT handovers. The configuration of this MO is delivered with the
RRCConnectionReconfiguration message. For details, see 3GPP TS 36.331.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the common parameters about inter-RAT handovers.
INTERRATHOCOMM

MOD Use this command to modify the common parameters about inter-RAT
INTERRATHOCOMM
handovers.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description
Table 2 Related parameters

Parameter Description

Measurement report Indicates the number of periodical measurement reports to be sent after an inter-
amount
RAT handover event is triggered. It is used to prevent the impact of
measurement report loss and internal processing failure on the handover. For
details, see 3GPP TS 36.331.

Geran measurement Indicates the interval at which periodic measurement reports are sent to the
report interval
eNodeB after the event for inter-RAT handover to GERAN is triggered.
For details, see 3GPP TS 36.331.

Utran measurement Indicates the quantity to be included in the measurements for handovers to
trigger quantity
UTRAN. This parameter is dedicated to UTRAN FDD.
The RSCP values are relatively stable, while the Ec/No values may vary with the
network load. The value BOTH applies only to UEs complying with 3GPP
Release 10. For UEs complying with 3GPP Release 8 or 9, the value BOTH
takes the same effect as the value RSCP. For details, see 3GPP TS 23.003.

UTRAN FDD Indicates the interval at which periodical measurement reports are sent after the
measurement report
interval event for the handover to UTRAN is triggered.
For details, see 3GPP TS 36.331.

CDMA20001XRTT Indicates the measurement quantity required for the inter-RAT handover to
measurement trigger
quantity CDMA2000 1xRTT. For details, see 3GPP TS 36.331.

CDMA20001XRTT Indicates the interval at which periodic measurement reports are sent to the
measurement report
interval eNodeB after the event for inter-RAT handover to CDMA2000 1xRTT is
triggered.
For details, see 3GPP TS 36.331.

CDMA2000HRPD Indicates the measurement quantity required for the inter-RAT handover to
measurement trigger
quantity CDMA2000 HRPD. For details, see 3GPP TS 36.331.

CDMA2000HRPD Indicates the interval at which periodic measurement reports are sent to the
measurement report
interval eNodeB after the event for inter-RAT handover to CDMA2000 HRPD is
triggered.
For details, see 3GPP TS 36.331.

InterRat A1A2 Indicates the triggering quantity for the inter-RAT measurement event A1 or A2
measurement trigger
quantity report. The quantity can be RSRP, RSRQ, or both RSRP and RSRQ. The
measured RSRP values are stable, varying little with the load, and therefore
there is little signal fluctuation. The measured RSRQ values vary with the load
and are likely to reflect the signal quality of the cell in real time. For details, see
3GPP TS 36.331.
Table 2 Related parameters

Parameter Description

Inter RAT HO Trigger Indicates the type of the inter-RAT handover event. The event type can be B1 or
Event Type
B2. This parameter applies only to coverage-based handovers. For details, see
3GPP TS 36.331.

CDMA2000 1xRTT Indicates the timer for measurements on CDMA2000 1xRTT cells.
Measure Timer

CDMA2000 1xRTT Indicates the number of CDMA2000 1xRTT cells whose reference signal
Judge PN Number
strength is used to calculate the target reference signal strength.

CDMA2000 HRPD Indicates the mode of selecting a CDMA2000 HRPD frequency.


Frequency Select Mode

CDMA2000 1xRTT Indicates the mode of selecting a CDMA2000 1xRTT frequency.


Frequency Select Mode

eCSFB PS Concurrent Indicates whether eCSFB is based on redirection.


Mode

eCSFB Measurement Indicates the measurement mode for eCSFB.


Mode

eCSFB SectorID Select Indicates the mode of selecting a sector ID during eCSFB.
Mode

Max Utran cell num in Indicates the maximum number of UTRAN cell system information messages
redirection
that can be transmitted during a flash redirection procedure.

Max Geran cell num in Indicates the maximum number of GERAN cell system information messages
redirection
that can be transmitted during a flash redirection procedure.

Max Geran cell num in Indicates the maximum number of GERAN cell system information messages
CSFB EMC redirection
that can be transmitted during a CSFB emergency redirection procedure.

Max Utran cell num in Indicates the maximum number of UTRAN cell system information messages
CSFB EMC redirection
that can be transmitted during a CSFB emergency redirection procedure.

5.7.1.6.3.127 InterRatHoCommGroup
+-NE
+-eNodeBFunction
+-Cell
+-InterRatHoCommGroup
Description

An InterRatHoCommGroup MO is a group of common parameters related to inter-RAT


handover. Different MOs of this class will be associated with different QCIs to meet various
requirements of services for the target cell. For details, see 3GPP TS 36.331.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the CellStandardQci MO:


- InterRatHoCommGroupId in a CellStandardQci MO must have been set in the associated
InterRatHoCommGroup MO.
Relation with the CellExtendedQci MO:
- InterRatHoCommGroupId in a CellExtendedQci MO must have been set in the
associated InterRatHoCommGroup MO.
Relation with the CnOperatorHoCfg MO:
- The sum of the value of InterRatHoA2ThdRsrp in the InterRatHoCommGroup MO and
the value of UtranA2ThdRsrpOffset in the CnOperatorHoCfg MO cannot be greater than the
value of InterRatHoA1ThdRsrp in the InterRatHoCommGroup MO.
- The sum of the value of InterRatHoA2ThdRsrp in the InterRatHoCommGroup MO and
the value of GeranA2ThdRsrpOffset in the CnOperatorHoCfg MO cannot be greater than the
value of InterRatHoA1ThdRsrp in the InterRatHoCommGroup MO.
Relation with the Cell MO:
- LocalCellId in an InterRatHoCommGroup MO must have been set in the associated Cell
MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add a group of common parameters related to inter-RAT
INTERRATHOCOMMG
Table 1 Related MML commands

MML Command Function

ROUP handover.

LST Use this command to list one or all groups of common parameters related to
INTERRATHOCOMMG
ROUP inter-RAT handover.

MOD Use this command to modify a group of common parameters related to inter-
INTERRATHOCOMMG
ROUP RAT handover.

RMV Use this command to remove a group of common parameters related to inter-
INTERRATHOCOMMG
ROUP RAT handover.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

InterRAT handover Indicates the ID of the common parameter group related to inter-RAT handover.
common group ID

InterRAT A1A2 Indicates the hysteresis for inter-RAT measurement events A1 and A2. This
hysteresis
parameter is used to prevent frequent triggering of event evaluation caused by
radio signal fluctuation. In this way, the probability of ping-pong handovers or
handover decision errors is reduced. A larger value of this parameter results in a
lower probability.

InterRAT A1A2 time to Indicates the time-to-trigger for inter-RAT measurement event A1 or A2.
trigger
When detecting that the signal quality in the serving cell meets the entering
condition, the UE does not send a measurement report to the eNodeB
immediately. Instead, the UE sends a report only when the signal quality
continuously meets the entering condition during the time-to-trigger.
This parameter helps decrease the number of occasionally triggered event
reports, the average number of handovers, and the number of wrong handovers.
In summary, it helps prevent unnecessary handovers.

InterRAT A1 RSRP Indicates the RSRP threshold for inter-RAT measurement event A1. When the
trigger threshold
measured RSRP value of the serving cell exceeds this threshold, an event A1
Table 2 Related parameters

Parameter Description

report will be sent. The value -141 does not take effect and is reserved for
forward compatibility. If this parameter is set to -141, the value -140 is used as
the threshold in implementation.

InterRAT A1 RSRQ Indicates the RSRQ threshold for inter-RAT measurement event A1.
trigger threshold
When the measured RSRQ value of the serving cell exceeds this threshold, an
event A1 report will be sent.

InterRAT A2 RSRP Indicates the RSRP threshold for inter-RAT measurement event A2.
trigger threshold
When the measured RSRP value of the serving cell is below this threshold, an
event A2 report will be sent. The value -141 does not take effect and is reserved
for forward compatibility. If this parameter is set to -141, the value -140 is used
as the threshold in implementation.

InterRAT A2 RSRQ Indicates the RSRQ threshold for inter-RAT measurement event A2.
trigger threshold
When the measured RSRQ value of the serving cell is below this threshold, an
event A2 report will be sent.

Blind HO A2 Threshold Indicates the offset of the event A2 threshold for inter-RAT blind redirections
Offset
relative to the event A2 threshold for handovers. This parameter is reserved for
forward compatibility. It does not take effect currently.

5.7.1.6.3.128 InterRatHoGeranGroup
+-NE
+-eNodeBFunction
+-Cell
+-InterRatHoGeranGroup

Description

An InterRatHoGeranGroup MO is a group of parameters related to inter-RAT handover to


GERAN. Different MOs of this class will be associated with different QCIs to meet various
requirements of services for the target cell. For details, see 3GPP TS 36.331.

Effective Scenario

Immediately
Relations Between MOs

Possible parents:
Cell

Relation with the CellStandardQci MO:


- InterRatHoGeranGroupId in a CellStandardQci MO must have been set in the associated
InterRatHoGeranGroup MO.
Relation with the CellExtendedQci MO:
- InterRatHoGeranGroupId in a CellExtendedQci MO must have been set in the associated
InterRatHoGeranGroup MO.
Relation with the Cell MO:
- LocalCellId in an InterRatHoGeranGroup MO must have been set in the associated Cell
MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add a parameter group related to inter-RAT handover to
INTERRATHOGERAN
GROUP GERAN.

LST Use this command to list one or all parameter groups related to inter-RAT
INTERRATHOGERAN
GROUP handover to GERAN.

MOD Use this command to modify a parameter group related to inter-RAT handover to
INTERRATHOGERAN
GROUP GERAN.

RMV Use this command to remove a parameter group related to inter-RAT handover
INTERRATHOGERAN
GROUP to GERAN.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description
Table 2 Related parameters

Parameter Description

InterRAT handover to Indicates the ID of the parameter group related to inter-RAT handover to
GERAN group ID
GERAN.

GERAN handover Indicates the hysteresis for event B1 related to inter-RAT handover to GERAN.
hysteresis
This parameter is used to prevent frequent triggering of event evaluation caused
by radio signal fluctuation. In this way, the probability of ping-pong handovers
or handover decision errors is reduced. A larger value of this parameter results in
a lower probability of ping-pong handovers or handover decision errors.

CoverageBased Indicates the RSSI threshold for event B1 related to coverage-based inter-RAT
GERAN trigger
threshold handover to GERAN.
A UE sends a measurement report related to event B1 to the eNodeB when the
RSSI in at least one GERAN cell exceeds this threshold and other triggering
conditions are met. For details, see 3GPP TS 36.331.

GERAN time to trigger Indicates the time-to-trigger for event B1 related to inter-RAT handover to
GERAN. When detecting that the signal quality in at least one neighboring cell
meets the entering condition, the UE does not send a measurement report to the
eNodeB immediately. Instead, the UE sends a report only when the signal
quality continuously meets the entering condition during the time-to-trigger.
This parameter helps decrease the number of occasionally triggered event
reports, the average number of handovers and the number of wrong handovers,
preventing unnecessary handovers.

Load Service Based Indicates the RSSI threshold for event B1 related to load- or service-based inter-
Geran EventB1 trigger
threshold RAT handover to GERAN.
When the measured RSSI value exceeds this threshold, a measurement report
will be sent.

5.7.1.6.3.129 InterRatHoUtranGroup
+-NE
+-eNodeBFunction
+-Cell
+-InterRatHoUtranGroup

Description
An InterRatHoUtranGroup MO is a group of parameters related to inter-RAT handover to
UTRAN. Different MOs of this class will be associated with different QCIs to meet various
requirements of services for the target cell. For details, see 3GPP TS 36.331.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the CellStandardQci MO:


- InterRatHoUtranGroupId in a CellStandardQci MO must have been set in the associated
InterRatHoUtranGroup MO.
Relation with the CellExtendedQci MO:
- InterRatHoUtranGroupId in a CellExtendedQci MO must have been set in the associated
InterRatHoUtranGroup MO.
Relation with the Cell MO:
- LocalCellId in an InterRatHoUtranGroup MO must have been set in the associated Cell
MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add a parameter group related to inter-RAT handover to
INTERRATHOUTRANG
ROUP UTRAN.

LST Use this command to list one or all parameter groups related to inter-RAT
INTERRATHOUTRANG
ROUP handover to UTRAN.

MOD Use this command to modify a parameter group related to inter-RAT handover to
INTERRATHOUTRANG
ROUP UTRAN.

RMV Use this command to remove a parameter group related to inter-RAT handover
INTERRATHOUTRANG
ROUP to UTRAN.
Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

InterRAT handover to Indicates the ID of the parameter group related to inter-RAT handover to
UTRAN Group ID
UTRAN.

CoverageBased Indicates the Ec/N0 threshold for event B1 related to coverage-based inter-RAT
UTRAN ECN0 trigger
threshold handover to UTRAN. This parameter specifies the requirement for Ec/N0 of the
target UTRAN cell. For a cell with large signal fading variance, set this
parameter to a large value to prevent unnecessary handovers. For a cell with
small signal fading variance, set this parameter to a small value to ensure timely
handovers. A large value of this parameter results in a low probability of
handover to the UTRAN cell, and a small value leads to a high probability.
When the measurement value exceeds this threshold, a measurement report will
be sent.

CoverageBased Indicates the RSCP threshold for event B1 related to coverage-based inter-RAT
UTRAN RSCP trigger
threshold handover to UTRAN.
This parameter specifies the requirement for RSCP of the target UTRAN cell.
When the measurement value exceeds this threshold, a measurement report will
be sent.

UTRAN handover Indicates the hysteresis for event B1 related to inter-RAT handover to UTRAN.
hysteresis
This parameter is used to prevent frequent triggering of event evaluation caused
by radio signal fluctuation. In this way, the probability of ping-pong handovers
or handover decision errors is reduced. A larger value of this parameter results in
a lower probability of ping-pong handovers or handover decision errors.

UTRAN time to trigger Indicates the time-to-trigger for event B1 related to inter-RAT handover to
UTRAN. When detecting that the signal quality in at least one neighboring cell
meets the entering condition, the UE does not send a measurement report to the
eNodeB immediately. Instead, the UE sends a report only when the signal
quality continuously meets the entering condition during the time-to-trigger.
This parameter helps decrease the number of occasionally triggered event
reports, the average number of handovers and the number of wrong handovers,
preventing unnecessary handovers.

Load Service Based Indicates the Ec/N0 threshold for event B1 related to load- or service-based
UTRANB1 ECN0
threshold inter-RAT handover to UTRAN.
This parameter specifies the requirement for Ec/N0 of the target UTRAN cell.
Table 2 Related parameters

Parameter Description

When the measurement value exceeds this threshold, a measurement report may
be sent. For a cell with large signal fading variance, set this parameter to a large
value to prevent unnecessary handovers. For a cell with small signal fading
variance, set this parameter to a small value to ensure timely handovers.

Load Service Based Indicates the RSCP threshold for event B1 related to load- or service-based
UTRAN EventB1 RSCP
trigger threshold inter-RAT handover to UTRAN.
This parameter specifies the requirement for RSCP of the target UTRAN cell.
When the measurement value exceeds this threshold, a measurement report will
be sent.

5.7.1.6.3.130 InterRatPolicyCfgGroup
+-NE
+-eNodeBFunction
+-InterRatPolicyCfgGroup

Description

An InterRatPolicyCfgGroup MO contains a group of policies for inter-RAT handover. Different


MOs of this class will be associated with different QCIs to meet various requirements of services
for the target cell.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Relation with the ExtendedQci MO:


- InterRatPolicyCfgGroupId in an ExtendedQci MO must have been set in the associated
InterRatPolicyCfgGroup MO.
Relation with the StandardQci MO:
- InterRatPolicyCfgGroupId in a StandardQci MO must have been set in the associated
InterRatPolicyCfgGroup MO.
Relation with the eNodeBFunction:
- The number of InterRatPolicyCfgGroup MOs must be from 1 to 40.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add an inter-RAT handover policy group.


INTERRATPOLICYCFG
GROUP

LST Use this command to list one or all inter-RAT handover policy groups.
INTERRATPOLICYCFG
GROUP

MOD Use this command to modify the parameters related to inter-RAT handover
INTERRATPOLICYCFG
GROUP policies.

RMV Use this command to remove an inter-RAT handover policy group.


INTERRATPOLICYCFG
GROUP

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

InterRAT policy config Indicates the group ID of the parameters related to the inter-RAT handover with
group ID
a specific QCI.

UTRAN handover Indicates the policy of handovers to UTRAN.


policy Configuration
PS_HO: indicates whether to allow PS handovers to UTRAN.
SRVCC: indicates whether to allow transfers to UTRAN in SRVCC mode.
REDIRECTION: indicates whether to allow redirection to UTRAN.

GERAN GSM handover Indicates the switch used to enable or disable the single radio voice call
policy Configuration
continuity (SRVCC) handover to GERAN GSM.
Table 2 Related parameters

Parameter Description

If this switch is set to On, the UE can perform the SRVCC handover to the
GERAN GSM cell.
If this switch is set to Off, the UE cannot perform the SRVCC handover to the
GERAN GSM cell.

GERAN GPRS EDGE Indicates the policy of handovers to GPRS/EDGE. PS_HO: Indicates whether
handover policy
Configuration PS handovers to neighboring GPRS/EDGE cells are allowed. NACC_HO:
Indicates whether NACC handovers to neighboring GPRS/EDGE cells are
allowed. This switch will be removed in the later versions. In this version, the
setting of this switch is still synchronized between the M2000 and the eNodeB,
but it is no longer used internally. Therefore, avoid using this parameter.
CCO_HO: Indicates whether CCO handovers to neighboring GPRS/EDGE cells
are allowed. SRVCC: Indicates whether SRVCC handovers to neighboring
GPRS/EDGE cells are allowed. REDIRECTION: Indicates whether redirections
to neighboring GPRS/EDGE cells are allowed.

CDMA2000 1XRTT Indicates the switch used to enable or disable QCI-specific SRVCC to
handover policy
Configuration CDMA2000 1xRTT.
If this switch is turned on, UEs can perform SRVCC to CDMA2000 1xRTT
cells.
If this switch is turned off, UEs cannot perform SRVCC to CDMA2000 1xRTT
cells.

CDMA2000 HRPD Indicates the policy of handovers to CDMA2000 HRPD networks.


handover policy
Configuration NON_OPT_HO:
Indicates whether to allow non-optimized handovers to neighboring CDMA2000
HRPD cells.
OPT_HO:
Indicates whether to allow optimized handovers to neighboring CDMA2000
HRPD cells.

No handover flag Indicates whether to permit or forbid the inter-RAT handover under the QCI.

No fast ANR flag Indicates whether to allow the fast ANR under the QCI. The function specified
by this parameter is an extended function and is reserved. The current version
does not support this function.

5.7.1.6.3.131 IntraFreqBlkCell
+-NE
+-eNodeBFunction
+-Cell
+-IntraFreqBlkCell

Description

An IntraFreqBlkCell MO consists of the parameters related to a blacklisted intra-frequency cell.


The blacklist is contained in system information block type 4 (SIB4). Handover and reselection
to blacklisted cells are prohibited for UEs in connected mode and those in idle mode,
respectively. For details, see 3GPP TS 36.331.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the Cell MO:


- A maximum of 32 IntraFreqBlkCell MOs can be configured for each cell.
- PhyCellId of the local Cell MO cannot be within the intra-frequency blacklist cell range
specified by PhyCellId and PhyCellIdRange in an IntraFreqBlkCell MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add intra-frequency E-UTRAN cells to the blacklist.
INTRAFREQBLKCELL

LST Use this command to list the parameters of the blacklisted intra-frequency E-
INTRAFREQBLKCELL
UTRAN cell.

MOD Use this command to modify a E-UTRAN blacklist of intra-frequency cells.


INTRAFREQBLKCELL

RMV Use this command to remove an intra-frequency E-UTRAN cell from the
INTRAFREQBLKCELL
blacklist.
Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the cell ID of the local cell. It uniquely identifies a cell within an
eNodeB.

Start physical cell ID Indicates the starting physical cell ID of the intra-frequency blacklisted cell. For
details, see 3GPP TS 36.331.

Cell name Indicates the name of the intra-frequency blacklisted cell.

Physical cell ID range Indicates the physical cell ID range of the intra-frequency blacklisted cell. For
details, see 3GPP TS 36.331.

5.7.1.6.3.132 IntraFreqHoGroup
+-NE
+-eNodeBFunction
+-Cell
+-IntraFreqHoGroup

Description

An IntraFreqHoGroup MO is a group of parameters related to intra-frequency handover.


Different MOs of this class will be associated with different QCIs to meet various requirements
of services for the target cell. For details, see 3GPP TS 36.331.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the CellStandardQci MO:


- IntraFreqHoGroupId in a CellStandardQci MO must have been set in the associated
IntraFreqHoGroup MO.
Relation with the Cell MO:
- LocalCellId in an IntraFreqHoGroup MO must have been set in the associated Cell MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add a parameter group related to intra-frequency handover.
INTRAFREQHOGROU
P

LST Use this command to list one or all parameter groups related to intra-frequency
INTRAFREQHOGROU
P handover.

MOD Use this command to modify a parameter group related to intra-frequency


INTRAFREQHOGROU
P handover.

RMV Use this command to remove a parameter group related to intra-frequency


INTRAFREQHOGROU
P handover.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Intrafreq handover Indicates the ID of the parameter group related to intra-frequency handover.
group ID

Intrafreq handover Indicates the hysteresis for intra-frequency handover event A3. This parameter
hysteresis
decreases frequent event triggering due to radio signal fluctuations and reduces
the probability of handover decision errors and ping-pong handovers. A larger
value of this parameter results in a lower probability. The hysteresis for inter-
frequency handover event A3 is the same as the value of this parameter. For
details, see 3GPP TS 36.331.
Table 2 Related parameters

Parameter Description

Intrafreq handover Indicates the offset for event A3. If the parameter is set to a large value, an intra-
offset
frequency handover is performed only when the signal quality of the
neighboring cell is significantly better than that of the serving cell and other
triggering conditions are met. For details, see 3GPP TS 36.331.

Intrafreq handover time Indicates the time-to-trigger for intra-frequency handover event A3.
to trigger
When the UE detects that the signal quality in the serving cell and that in at least
one neighboring cell meet the entering condition, it does not immediately send a
measurement report to the eNodeB. Instead, the UE sends a report only when the
signal quality meets the entering condition throughout the time-to-trigger.
This parameter helps decrease the number of occasionally triggered event
reports, the average number of handovers, and the number of incorrect
handovers, preventing unnecessary handovers. The time-to-trigger for inter-
frequency handover event A3 is the same as the value of this parameter.

5.7.1.6.3.133 IntraRatHoComm
+-NE
+-eNodeBFunction
+-IntraRatHoComm

Description

The IntraRatHoComm MO consists of the eNodeB-level parameters that are related to intra-RAT
handovers. The configuration of this MO is delivered with the RRCConnectionReconfiguration
message. For details, see 3GPP TS 36.331.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands


Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the eNodeB-level parameters that are related to intra-
INTRARATHOCOMM
RAT handovers.

MOD Use this command to modify the common parameters for intra-RAT handover.
INTRARATHOCOMM

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Max report cell number Indicates the maximum number of cells to be included in the measurement
report after an intra-RAT inter-frequency or intra-RAT intra-frequency
measurement event for handover purposes or a periodic intra-RAT measurement
for ANR purposes is triggered. For details, see 3GPP TS 36.331.

Measurement report Indicates the number of periodical measurement reports to be sent after an event
amount
for the intra- or inter-frequency handover within the E-UTRAN is triggered.
It is used to prevent the impact of measurement report loss and internal
processing failure on the handover. For details, see 3GPP TS 36.331.

A3 measurement Indicates the quantity used to evaluate the triggering condition for the intra-
trigger quantity
frequency handover event. The quantity can be RSRP or RSRQ.
The measured RSRP values are stable, varying little with the load, and therefore
there is little signal fluctuation. The measured RSRQ values vary with the load
and are likely to reflect the signal quality of the cell in real time.
For details, see 3GPP TS 36.331.

A3 measurement report Indicates the quantity to be included in the measurement report for the intra-
quantity
frequency handover event. The quantity can be RSRP, RSRQ, or both.
The measured RSRP values are stable, varying little with the load, and therefore
there is little signal fluctuation. The measured RSRQ values vary with the load
and are likely to reflect the signal quality of the cell in real time. Even when this
parameter is set to BOTH, the eNodeB triggers a handover based on the setting
of the IntraFreqHoA3TrigQuan parameter.The value of this parameter is also
used as the quantity to be included in the measurement report between A3-
Table 2 Related parameters

Parameter Description

related inter-frequency measurement reports.


For details, see 3GPP TS 36.331.

A3 measurement report Indicates the interval between periodic measurement reports that are sent after
interval
an intra-frequency handover is triggered. The value of this parameter is also
used as the interval between A3-related inter-frequency measurement reports.
For details, see 3GPP TS 36.331.

Measurement A4 report Indicates the quantity to be included in the measurement report for the inter-
quantity
frequency handover event. The quantity can be RSRP, RSRQ, or both. The
measured RSRP values are stable, varying little with the load, and therefore
there is little signal fluctuation. The measured RSRQ values vary with the load
and are likely to reflect the signal quality of the cell in real time. For details, see
3GPP TS 36.331.

Interfreq measurement Indicates the interval at which periodical measurement reports are sent after an
report interval
inter-frequency handover event is triggered.
For details, see 3GPP TS 36.331.

InterFreq A1A2 Indicates the quantity used in the evaluation for inter-frequency measurement
Measurement trigger
quantity event A1 or A2. The quantity can be RSRP, RSRQ, or both. The measured RSRP
values are stable, varying little with the load, and therefore there is little signal
fluctuation. The measured RSRQ values vary with the load and are likely to
reflect the signal quality of the cell in real time. For details, see 3GPP TS
36.331.

A1A2 Measurement Indicates the triggering quantity for frequency-priority-based inter-frequency


trigger quantity of Freq
Priority measurement events A1 and A2. The quantity can be either RSRP or RSRQ, or
both. The measured RSRP values are stable, varying little with the load, and
therefore there is little signal fluctuation. The measured RSRQ values vary with
the load and are likely to reflect the signal quality of the cell in real time. For
details, see 3GPP TS 36.331.

FreqPrior loadBased A4 Indicates the triggering quantity for frequency-priority- and load-based inter-
Measurement trigger
quantity frequency handover event A4.

5.7.1.6.3.134 LicenseSharingPolicy
+-NE
+-eNodeBFunction
+-CnOperator
+-LicenseSharingPolicy

Description

A LicenseSharingPolicy MO consists of the parameters about a license sharing policy among


operators. The parameters are set to determine the proportion of the maximum number of RRC
connected users for each operator. If a LicenseSharingPolicy MO is not configured for an
operator, the proportion of the maximum number of RRC connected users for this operator is 0
by default. Users of this operator cannot access the shared eNodeB.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
CnOperator

Relation with the ENodeBSharingMode MO:


- If ENodeBSharingMode in the ENodeBSharingMode MO is set to INDEPENDENT, no
LicenseSharingPolicy MO can be configured.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add a license sharing policy.


LICENSESHARINGPO
LICY

LST Use this command to list the parameters related to license sharing policy.
LICENSESHARINGPO
LICY

MOD Use this command to modify the parameters related to license sharing policy.
LICENSESHARINGPO
LICY

RMV Use this command to remove a license sharing policy.


LICENSESHARINGPO
LICY

Related Parameters
Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

CN Operator ID Indicates the index of the operator.

The proportion of the Indicates the proportion of the maximum number of RRC connected users for
maximum number of
users the operator at the shared eNodeB. This parameter must be set according to the
contract signed by the operators.

The proportion of the Indicates the proportion of users that the operator can share to other operators
sharing number of
users when the eNodeB is shared among operators. This parameter must be set based
on the contract signed by operators.

5.7.1.6.3.135 LicRatio
+-NE
+-eNodeBFunction
+-LicRatio

Description

The LicRatio MO includes the parameter indicating the proportion of the UL licensed traffic to
the total licensed traffic of the eNodeB.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

LST LICRATIO Use this command to list the configuration of licensed traffic ratios.

MOD LICRATIO Use this command to modify the configuration of licensed traffic ratios.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Uplink Traffic License Indicates the proportion of the UL licensed traffic to the total licensed traffic of
Ratio
the eNodeB. The total licensed traffic is the sum of UL and DL licensed traffic.
If this parameter is set to 100%, there is no DL licensed traffic, affecting service
admission.

Traffic Sharing Type Indicates the mode of traffic sharing between the operators in RAN sharing
scenarios. If this parameter is set to SHARING, all the operators share the total
traffic of the eNodeB without proportional limits. If this parameter is set to
DEDICATE and the ENodeBSharingMode parameter is not set to
INDEPENDENT, all the operators share the total traffic of the eNodeB based on
specific proportions. However, the vacant traffic of an operator can be used by
other operators.

5.7.1.6.3.136 LicRatioSharePolicy
+-NE
+-eNodeBFunction
+-CnOperator
+-LicRatioSharePolicy

Description

The LicRatioSharePolicy MO specifies the proportion of the traffic and traffic sharing ratio that
each operator can use or share to the total licensed traffic.
Effective Scenario

Immediately

Relations Between MOs

Possible parents:
CnOperator

Relation with the LicRatioSharePolicy MO:


- CnOperatorId in a LicRatioSharePolicy MO must have been set in the associated
CnOperator MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add a license ratio share policy.


LICRATIOSHAREPOLI
CY

LST Use this command to list a license ratio share policy.


LICRATIOSHAREPOLI
CY

MOD Use this command to modify a license ratio share policy.


LICRATIOSHAREPOLI
CY

RMV Use this command to remove a license ratio share policy.


LICRATIOSHAREPOLI
CY

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

CN Operator ID Indicates the ID of the operator.


Table 2 Related parameters

Parameter Description

TrfRatio Indicates the proportion of traffic used by the operator when the eNodeB is
shared among operators. This parameter must be set based on the contract signed
by operators. If this parameter is set to 0, services except emergency calls of this
operator are not admitted.

TrfSharingRatio Indicates the proportion of traffic that the operator can share with other
operators when the eNodeB is shared among operators.

5.7.1.6.3.137 MimoAdaptiveParaCfg
+-NE
+-eNodeBFunction
+-MimoAdaptiveParaCfg

Description

The MimoAdaptiveParaCfg MO consists of the parameters related to the initial Multiple Input
Multiple Output (MIMO) transmission mode configuration and adaptive MIMO. If adaptive
MIMO is enabled, the eNodeB sets the corresponding MIMO transmission mode based on
channel conditions. If adaptive MIMO is disabled, the eNodeB uses the fixed MIMO
transmission mode.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Relation with the Cell MO:


- If AirCellFlag in Cell MO is set to BOOLEAN_TRUE, MimoAdaptiveSwitch in
MimoAdaptiveParaCfg MO must be set to NO_ADAPTIVE.
Relation with the Cell,CellAlgoSwitch MOs:
- If CellActiveState in a Cell MO is set to CELL_ACTIVE, EicicSwitch in CellAlgoSwitch
MO cannot be set to ON and MimoAdaptiveSwitch in MimoAdaptiveParaCfg MO cannot be
set to OC_ADAPTIVE at the same time.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the configuration of adaptive MIMO.


MIMOADAPTIVEPARA
CFG

MOD Use this command to modify the parameters related to adaptive MIMO.
MIMOADAPTIVEPARA
CFG

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

MIMO adaptive switch Indicates the type of adaptive MIMO for a multi-antenna eNodeB. The values
are described as follows:
NO_ADAPTIVE: A fixed MIMO transmission mode is used. That is, transition
between MIMO transmission modes is not supported.
OL_ADAPTIVE: open-loop adaptive MIMO transmission mode. UEs report
RANK and CQI values but do not report PMI values to the eNodeB.
CL_ADAPTIVE: closed-loop adaptive MIMO transmission mode. UEs report
RANK, CQI, and PMI values to the eNodeB.
OC_ADAPTIVE: UEs switch between the open-loop and closed-loop adaptive
MIMO transmission modes automatically.

Fixed MIMO mode Indicates the fixed MIMO mode for a multi-antenna eNodeB. This parameter is
valid only when MimoAdaptiveSwitch is set to NO_ADAPTIVE. There are four
values.
TM2: Transmission mode 2 is applied to UEs.
TM3: Transmission mode 3 is applied to UEs.
TM4: Transmission mode 4 is applied to UEs.
Table 2 Related parameters

Parameter Description

TM6: Transmission mode 6 is applied to UEs.

Initial Mimo Type Indicates the MIMO type used during initial network access.
If this parameter is set to TM2(TM2), the MIMO type used during initial
network access is TM2.
If this parameter is set to ADAPTIVE(ADAPTIVE), the MIMO type used
during initial network access is determined by the MimoAdaptiveSwitch and
FixedMimoMode settings. If MimoAdaptiveSwitch is set to NO_ADAPTIVE,
the initial MIMO type is determined by the FixedMimoMode parameter setting.
If MimoAdaptiveSwitch is set to OL_ADAPTIVE, the initial MIMO type is
TM3. If MimoAdaptiveSwitch is set to CL_ADAPTIVE, the initial MIMO type
is TM4.

5.7.1.6.3.138 MmeFeatureCfg
+-NE
+-eNodeBFunction
+-S1Interface
+-MmeFeatureCfg

Description

An MmeFeatureCfg MO consists of parameters related to the minimization of drive test (MDT)


feature configuration.
With MDTs, operators replace some of traditional drive tests with measurement reporting by
commercial UEs of subscribers or test users. In this way, UE measurement results are
automatically collected to detect problems and faults in radio networks for network optimization.
Among UEs complying with 3GPP Release 9 and Release 10, some UEs support the Observed
Time Difference Of Arrival (OTDOA) and Network-Assisted GPS (A-GPS) positioning
methods. According to the current specifications, a positioning procedure is as follows: An MME
initiates the procedure, an evolved serving mobile location center (E-SMLC) obtains assistance
data from the UE and eNodeB by LTE Positioning Protocol (LPP) and LTE Positioning Protocol
A (LPPa), and finally the E-SMLC derives the location information about the UE by calculation.
The MDT feature includes Huawei-proprietary positioning procedures between eNodeBs and
Huawei MMEs. In such a procedure, an eNodeB sends a private message to an MME to initiate
A-GPS positioning, and the MME obtains location information from an E-SMLC and then sends
the eNodeB a private message containing the location information.
Before the eNodeB sends the location request to the MME, the eNodeB must check whether the
MME supports Huawei-proprietary positioning procedures.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
S1Interface

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to query the configuration of the MME features.
MMEFEATURECFG

MOD Use this command to modify the configuration of the MME features.
MMEFEATURECFG

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

S1Interface ID Indicates the ID of an S1 interface.

MME supporting MDT Indicates whether the MME at the other end of the S1 interface supports
or not
Huawei-proprietary positioning procedures, which are included in minimization
of drive tests (MDT). The value DISABLE(disable) indicates that the MME
does not support the procedures and therefore the eNodeB cannot obtain UE
location information from the MME through the procedures. The value
ENABLE(enable) indicates the opposite.
5.7.1.6.3.139 MRO
+-NE
+-eNodeBFunction
+-MRO

Description

The MRO MO consists of the parameters related to mobility robustness optimization (MRO).
With the purpose of increasing handover success rates, MRO identifies undesirable handovers or
service drops, measures the number of such handovers or service drops within a measurement
period, and optimizes the settings of handover-related parameters. Undesirable handovers
include premature handovers, delayed handovers, and ping-pong handovers. Undesirable
handovers and service drops may occur in areas with weak coverage or no coverage.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST MRO Use this command to list the MRO configuration.

MOD MRO Use this command to modify the MRO configuration.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

MRO optimization Indicates the period of MRO measurements. During the period, the number of
period
handovers is measured and abnormal scenarios (including premature handovers,
delayed handovers, ping-pong handovers, and handovers to wrong cells) are
identified. After the period elapses, the eNodeB makes a decision on parameter
adjustment.

Ncell optimization Indicates the threshold for enabling MRO based on the handover success rate.
threshold
MRO is applied and parameter adjustment is started only if the success rate of
handovers from the local cell to a neighboring cell is below this threshold.

MRO statistics number Indicates the threshold of the number of handovers required for enabling MRO.
threshold
MRO is applied and parameter adjustment is started only if the number of
handovers from the local cell to a neighboring cell reaches this threshold.

Pingpong handover Indicates the time threshold for ping-pong handover. If a UE is handed over
threshold
back to the source cell after staying in the target cell for a period shorter than
this threshold, the eNodeB decides that a ping-pong handover occurs based on
the history information about this UE.

Pingpong ratio Indicates the threshold for the percentage of intra-RAT ping-pong handovers. If
threshold
the percentage of intra-RAT ping-pong handovers exceeds the threshold,
parameter adjustment is performed. If the percentage is lower than the threshold,
parameter adjustment is not performed.

Abnormal coverage Indicates the threshold for the percentage of coverage-induced abnormal
threshold
handovers to all abnormal handovers from the serving cell to a neighboring cell.
If the percentage exceeds this threshold when an MRO period approaches its
end, the eNodeB does not adjust MRO-related parameters of the neighboring
cell within this period.

Serving cell RSRP Indicates the reference signal received power (RSRP) threshold for the serving
threshold
cell, which is used to identify coverage-induced abnormal handovers from the
serving cell to the neighboring cell. When a UE successfully reestablishes an
RRC connection after a radio link failure (RLF) in the serving cell, the UE sends
the eNodeB an RLF report, which includes the RSRP values of the serving and
neighboring cells. If the RSRP value of the serving cell is less than this
parameter value and the RSRP value of the neighboring cell is less than the
NeighborRsrpThd parameter value, this RLF is induced by abnormal coverage
rather than inappropriate MRO configurations.

Neighbour cell RSRP Indicates the reference signal received power (RSRP) threshold for a
threshold
neighboring cell, which is used to identify coverage-induced abnormal
handovers from the serving cell to the neighboring cell. When a UE successfully
reestablishes an RRC connection after a radio link failure (RLF) in the serving
Table 2 Related parameters

Parameter Description

cell, the UE sends the eNodeB an RLF report, which includes the RSRP values
of the serving and neighboring cells. If the RSRP value of the serving cell is less
than the ServingRsrpThd parameter value and the RSRP value of the
neighboring cell is less than this parameter value, this RLF is induced by
abnormal coverage rather than inappropriate MRO configurations.

UE PingPong Number Indicates the threshold for the number of pingpong handovers. If the number of
Threshold
consecutive ping-pong handovers reaches the threshold, the UE is a ping-pong
UE.

5.7.1.6.3.140 PCCHCfg
+-NE
+-eNodeBFunction
+-Cell
+-PCCHCfg

Description

The PCCHCfg MO consists of the parameters related to the Paging Control Channel (PCCH),
which is common radio resources in a cell.
The PCCH is a downlink logical channel that transmits paging messages and system information
modification indicators.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the BcchCfg MO:


- The product of DefaultPagingCycle in the PCCHCfg MO and ModifyPeriodCoeff in the
BcchCfg MO cannot exceed 1024 radio frames, that is 10,240 milliseconds.
Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST PCCHCFG Use this command to list the PCCH configuration.

MOD PCCHCFG Use this command to modify the PCCH configuration.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Default paging cycle Indicates the default paging period for the cell. It is also called the discontinuous
reception (DRX) period. If the EPC specifies a DRX period for a UE, the UE
compares this period with the value of this parameter and uses the smaller one as
its DRX period. If the EPC does not specify a DRX period, the UE uses the
value of this parameter, which is delivered in the system information, as its DRX
period. For details, see 3GPP TS 36.304.

NB Indicates the number of paging occasions (a type of subframe) within a paging


period. This parameter value also indicates the number of paging groups within
a paging period. For details, see 3GPP TS 36.304.

Paging Sent Number Indicates the number of paging messages transmitted to UEs over the air
interface.

5.7.1.6.3.141 PdcpRohcPara
+-NE
+-eNodeBFunction
+-PdcpRohcPara
Description

The PdcpRohcPara MO consists of the parameters related to Robust Header Compression


(ROHC). ROHC provides a header compression mechanism for data packets. It is specially
designed for radio links with a high bit error rate and long round trip time.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST PDCPROHCPARA Use this command to list the parameters related to ROHC. The parameters are
used by the ROHC entities at the PDCP layer on the radio interface, for header
compression and decompression of data packets on the user plane.

MOD Use this command to modify the parameters related to ROHC. The parameters
PDCPROHCPARA
are used by the ROHC entities at the PDCP layer on the radio interface, for
header compression and decompression of data packets on the user plane.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

ROHC switch Indicates whether to enable ROHC.


Set this parameter to ON if the eNodeB is expected to support VoIP or video
services.
Table 2 Related parameters

Parameter Description

ROHC Highest mode Indicates the operating mode of ROHC. In Unidirectional Mode (U-Mode),
packets are sent only from the compressor to the decompressor, and a feedback
channel is not mandatory. Therefore, U-Mode is less reliable than Bidirectional
Optimistic Mode (O-Mode) and Bidirectional Reliable Mode (R-Mode), but its
feedback-induced overhead is minimum compared with the overhead in O-Mode
and R-Mode. In O-Mode, the decompressor can send feedback messages to the
compressor to indicate decompression failures or successful context updates. O-
Mode is more reliable than U-Mode and requires a smaller amount of feedback
than R-Mode. In R-Mode, the reliability of context synchronization between the
compressor and the decompressor is higher than that in any other mode.
However, because of frequent feedback, R-Mode causes the largest amount of
link overhead.

Compression profiles Indicates the compression profile supported by the eNodeB.


Under the ROHC framework, header compression algorithms vary with
protocols. Profiles define the header compression protocols (such as
RTP/UDP/IP or TCP/IP), which are under the same ROHC framework, for
specific types of packet streams. Each profile has a unique identifier.
As defined by LTE specifications, the eNodeB supports the following profiles:
profile 0x0001 (usage: RTP/UDP/IP; reference: RFC 3095 and RFC 4815),
profile 0x0002 (usage: UDP/IP; reference: RFC 3095 and RFC 4815), profile
0x0003 (usage: ESP/IP; reference: RFC 3095 and RFC 4815), and profile
0x0004 (usage: IP; reference: RFC 3843 and RFC 4815).

5.7.1.6.3.142 PDSCHCfg
+-NE
+-eNodeBFunction
+-Cell
+-PDSCHCfg

Description

The PDSCHCfg MO consists of the parameters related to the physical downlink shared channel
(PDSCH). All services in the cell share the PDSCH. The PDSCH carries the following channels:
downlink shared channel (DL-SCH) and paging channel (PCH).

Effective Scenario
Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the Cell,eUCellSectorEqm MOs:


- In a Cell MO, if CellActiveState is set to CELL_ACTIVE, MultiRruCellFlag is set to
BOOLEAN_TRUE and MultiRruCellMode is set to MPRU_AGGREGATION, the number of
valid values of ReferenceSignalPwr in eUCellSectorEqm must be not more than that of
ReferenceSignalPwr in PDSCHCfg.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST PDSCHCFG Use this command to list the PDSCH configuration.

MOD PDSCHCFG Use this command to modify the PDSCH configuration.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Reference signal power Indicates the cell reference signal power of each physical antenna. However, the
cell reference signal power delivered in SIB2 is that of each logical antenna.

PB Indicates the scaling factor index of the Energy Per Resource Element (EPRE)
on the PDSCH. This scaling factor is determined by the value of this parameter
and the antenna port. For details, see 3GPP TS 36.213.

Reference signal power Indicates the cell reference signal power headroom of each physical antenna.
margin
5.7.1.6.3.143 PHICHCfg
+-NE
+-eNodeBFunction
+-Cell
+-PHICHCfg

Description

The PHICHCfg MO consists of the parameters related to the physical hybrid ARQ indicator
channel (PHICH). Services in a cell share the PHICH. The PHICH carries HARQ ACK/NACK
messages for the UL data.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the CellPdcchAlgo,Cell MOs:


- If PhichDuration in the PHICHCfg MO is set to NORMAL, and PdcchSymNumSwitch in
the CellPdcchAlgo MO is set to OFF, InitPdcchSymNum in the CellPdcchAlgo MO cannot be
set to 1 if the cell bandwidth is 1.4 MHz.
- If PhichDuration in the PHICHCfg MO is set to NORMAL, InitPdcchSymNum in the
CellPdcchAlgo MO can not be set to 4 if the cell bandwidth is not 1.4 MHz.
- If PhichDuration in the PHICHCfg MO is set to EXTENDED, InitPdcchSymNum in the
CellPdcchAlgo MO can be set to 3 or 4 if the cell bandwidth is 1.4 MHz.
- If PhichDuration in the PHICHCfg MO is set to EXTENDED, InitPdcchSymNum in the
CellPdcchAlgo MO must be set to 3 when the cell bandwidth is not 1.4 MHz.
Relation with the Cell MO:
- If CustomizedBandWidthCfgInd is set to CFG and CustomizedDLBandWidth is set to a
value in the range of 183 to 192 in a Cell MO, PhichResource in the associated PHICHCfg MO
cannot be set to TWO.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

LST PHICHCFG Use this command to list the PHICH configuration.

MOD PHICHCFG Use this command to modify the PHICH configuration.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

PHICH duration Indicates the PHICH duration type. If this parameter is set to NORMAL, the
number of OFDM symbols occupied by the PDCCH is automatically adjusted. If
this parameter is set to EXTENDED, the number of OFDM symbols occupied
by the PDCCH is fixed. Specifically, this number is fixed to 3 or 4 for 1.4 MHz
cells and 3 for cells with other bandwidths. For the mapping between the type
and the duration, see 3GPP TS 36.211.

PHICH resource Indicates a coefficient that is used to calculate the resources used by the PHICH
for the cell. It corresponds to the Ng parameter in the protocol.
For details on the usage of the Ng parameter, see 3GPP TS 36.211.

5.7.1.6.3.144 PUCCHCfg
+-NE
+-eNodeBFunction
+-Cell
+-PUCCHCfg

Description

The PUCCHCfg MO consists of the parameters related to the Physical Uplink Control Channel
(PUCCH), which is common radio resources in a cell.
The PUCCH has the following features:
1. Carries HARQ ACKs/NACKs of downlink data.
2. Carries scheduling requests.
3. Carries CQI reports.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Modification limitation:
- The modifications on the PUCCH configuration of an in-service cell would result in
automatic reset of the cell.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST PUCCHCFG Use this command to list the PUCCH configuration.

MOD PUCCHCFG Use this command to modify the PUCCH configuration.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Delta shift Indicates the interval between cyclic shifts used for the PUCCH. The interval
between cyclic shifts used for the PUCCH can be acquired based on the average
Table 2 Related parameters

Parameter Description

delay spread in the cell, where the average delay spread is acquired based on the
networking environment. The parameter value DS1_DELTA_SHIFT is not
supported by the LBBPc. If a cell is established on an LBBPc but this parameter
is set to DS1_DELTA_SHIFT, the value of this parameter is automatically
changed to DS2_DELTA_SHIFT when this parameter takes effect. For details,
see 3GPP TS 36.211.

ACK/SRI Channel Indicates the number of resource indexes allocated to SRI and semi-persistent
Number
ACK at the RRC layer for the FDD cell. If this parameter is set to 0, UEs may
fail to access the cell.

CQI RB number Indicates the number of RBs allocated to the CQI at the RRC layer of FDD cell.

PUCCH Extended RB Indicates the total number of RBs at the two ends of the system band that are
Number
reserved for the PUSCH. This parameter is valid only when the PUCCH flexible
configuration switch (PucchFlexCfgSwitch) is turned on. The parameter setting
must consider the number of RBs used by the PRACH, SRS, and PUCCH as
well as the number of RBs compressed. If the parameter setting exceeds the
system bandwidth capability and accordingly affects the preceding RB resource
allocation, the cell cannot be established successfully.

5.7.1.6.3.145 PUSCHCfg
+-NE
+-eNodeBFunction
+-Cell
+-PUSCHCfg

Description

The PUSCHCfg MO consists of the parameters related to the physical uplink shared channel
(PUSCH). Services in a cell share the PUSCH.
The PUSCH carries the UL shared channel (UL-SCH).

Effective Scenario

Immediately
Relations Between MOs

Possible parents:
Cell

Relation with the Cell MO:


- The number of RB resources corresponding to the value of UlBandWidth in a Cell MO
must be greater than or equal to the value of HoppingOffset in the PUSCHCfg MO.
- If UlBandWidth is set to CELL_BW_N6(1.4M), the number of RB resources is 6.
- If UlBandWidth is set to CELL_BW_N15(3M), the number of RB resources is 15.
- If UlBandWidth is set to CELL_BW_N25(5M), the number of RB resources is 25.
- If UlBandWidth is set to CELL_BW_N50(10M), the number of RB resources is 50.
- If UlBandWidth is set to CELL_BW_N75(15M), the number of RB resources is 75.
- If UlBandWidth is set to CELL_BW_N100(20M), the number of RB resources is 100.
Relation with the CellUlschAlgo,Cell MOs:
- Let A be the number of RB resources corresponding to the value of UlBandWidth in a Cell
MO, B the even number that HoppingOffset in the PUSCHCfg MO is rounded up to, and C the
difference between A and B. If UlHoppingType in the CellUlschAlgo MO is set to
HOPPING_TYPE1, C must be greater than A modulo 2. If UlHoppingType in the
CellUlschAlgo MO is set to HOPPING_TYPE2 or HOPPING_TYPE2_RANDOM, and Nsb in
the PUSCHCfg MO is greater than 1, the integer value of C divide Nsb in the PUSCHCfg MO
must be greater than 0.
- If UlBandWidth is set to CELL_BW_N6(1.4M), the number of RB resources is 6.
- If UlBandWidth is set to CELL_BW_N15(3M), the number of RB resources is 15.
- If UlBandWidth is set to CELL_BW_N25(5M), the number of RB resources is 25.
- If UlBandWidth is set to CELL_BW_N50(10M), the number of RB resources is 50.
- If UlBandWidth is set to CELL_BW_N75(15M), the number of RB resources is 75.
- If UlBandWidth is set to CELL_BW_N100(20M), the number of RB resources is 100.
Relation with the CellUlschAlgo MO:
- If HoppingMode in the PUSCHCfg MO is set to INTRA_AND_INTER_SUB_FRAME
and UlHoppingType in the CellUlschAlgo MO is set to HOPPING_TYPE2, Nsb in the
PUSCHCfg MO must be set to 1.
- If HoppingMode in the PUSCHCfg MO is set to INTER_SUB_FRAME and
UlHoppingType in the CellUlschAlgo MO is set to HOPPING_TYPE2_RANDOM, Nsb in the
PUSCHCfg MO cannot be set to 1.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

LST PUSCHCFG Use this command to list the PUSCH configuration.

MOD PUSCHCFG Use this command to modify the PUSCH configuration.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Subband number Indicates the number of PUSCH sub-bands.


For details, see 3GPP TS 36.211.

Hopping mode Indicates the hopping mode of the PUSCH.


For details, see 3GPP TS 36.211.

Hopping offset Indicates the hopping offset of the PUSCH.


For details, see 3GPP TS 36.211.

Group hopping enabled Indicates whether group hopping of the PUSCH is enabled.
For details, see 3GPP TS 36.211.

Group assignment Indicates the group assignment of the PUSCH.


PUSCH
For details, see 3GPP TS 36.211.

Sequence hopping Indicates whether sequence hopping of the PUSCH is enabled.


enabled
For details, see 3GPP TS 36.211.

Cyclic shift Indicates the cyclic shift of the PUSCH.


For details, see 3GPP TS 36.211.

Qam64 enabled Indicates whether 64QAM of the PUSCH is enabled.


For details, see 3GPP TS 36.211.
5.7.1.6.3.146 PuschParam
+-NE
+-eNodeBFunction
+-PuschParam

Description

The PuschParam MO consists of the parameters related to the physical uplink shared channel
(PUSCH), including the resource block (RB) offset values for channel quality indicators (CQIs),
rank indications (RIs), and acknowledgments (ACKs) transmitted with data on PUSCH.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST PUSCHPARAM Use this command to list the modulation and coding scheme (MCS) offset
values for control information transmitted with data on PUSCH.

MOD PUSCHPARAM Use this command to modify the modulation and coding scheme (MCS) offset
values for control information transmitted with data on PUSCH.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Delta Offset CQI Index Indicates the index mapped to the MCS offset for channel quality indicators
(CQIs) transmitted with data on PUSCH. For details, see 3GPP TS 36.213.
Some values are reserved, for example, values 0 and 1 are reserved in 3GPP TS
36.213 Release 9. When this parameter is set to a reserved value, a UE initiates
an RRC connection reestablishment or fails to access the network.

Delta Offset RI Index Indicates the index mapped to the MCS offset for rank indications (RIs)
transmitted with data on PUSCH. For details, see 3GPP TS 36.213. Some values
are reserved, for example, values 13, 14, and 15 are reserved in 3GPP TS 36.213
Release 9. When this parameter is set to a reserved value, a UE initiates an RRC
connection reestablishment or fails to access the network.

Delta Offset Indicates the index mapped to the MCS offset for acknowledgments (ACKs)
Acknowledge Index
transmitted with data on PUSCH. For details, see 3GPP TS 36.213. Some values
are reserved, for example, value 15 is reserved in 3GPP TS 36.213 Release 9.
When this parameter is set to a reserved value, a UE initiates an RRC connection
reestablishment or fails to access the network.

5.7.1.6.3.147 RACHCfg
+-NE
+-eNodeBFunction
+-Cell
+-RACHCfg

Description

The RACHCfg MO consists of the parameters related to the Random Access Channel (RACH),
which is common radio resources in a cell.
For details about the random access procedure, see 3GPP TS 36.321.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST RACHCFG Use this command to list the configuration information of the Random Access
Channel (RACH).

MOD RACHCFG Use this command to modify the RACH configuration.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Power ramping step Indicates the step by which the TX power for random access preambles is
increased each time after a RACH access failure. If multiple attempts to access
the PRACH fail, the UE increases the TX power for random access preambles
by a step specified by this parameter each time after an access failure to ensure
successful access.
For details, see 3GPP TS 36.321.

Preamble initial Indicates the target UE transmit power for the PRACH expected by the eNodeB
received target power
when PRACH preamble format 0 is applied on condition that requirements for
preamble detection performance are met.
For details, see 3GPP TS 36.321.

Message size of select Indicates the threshold for determining the size of Msg3 when a UE selects a
group A
preamble from random access preamble group A during a random access
procedure.
For details, see 3GPP TS 36.321.

PRACH Frequency Indicates the offset to the starting position of each PRACH in the frequency
Offset
domain of the FDD cell.
Table 2 Related parameters

Parameter Description

Indication of PRACH Indicates whether to configure the PRACH configuration index of the cell.
Configuration Index

PRACH Configuration Indicates the PRACH configuration index of the cell. If cells are established on
Index
an LBBPc in a 4T4R scenario, the PRACH configuration indexes of different
cells must be separated in the time domain.

Maximum number of Indicates the maximum number of preamble transmission times. For details
preamble transmission
about this parameter, see 3GPP TS 36.321.

Timer for contention Indicates the period that a UE waits for message 4 (Msg4) during a random
resolution
access (RA) procedure. This timer starts when a UE initially sends or resends
message 3 (Msg3). If the UE receives Msg4 or the NACK to Msg3 before the
timer expires, the timer stops. If the UE does not receive either message until the
timer expires, the RA fails, and the UE must reinitiate an RA procedure. For
details about this parameter, see 3GPP TS 36.321.

Maximum number of Indicates the maximum number of HARQ retransmissions of the message 3. For
Msg3 HARQ
transmissions details about this parameter, see 3GPP TS 36.321.

5.7.1.6.3.148 RatFreqPriorityGroup
+-NE
+-eNodeBFunction
+-RatFreqPriorityGroup

Description

A RatFreqPriorityGroup MO consists of the parameters related to a RAT/frequency priority


group.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction
Relation with the SpidCfg MO:
- RatFreqPriorityGroupId in an SpidCfg MO must have been set in the associated
RatFreqPriorityGroup MO.
Relation with the RatFreqPriorityGroup MO:
- A maximum of twenty RatFreqPriorityGroup MOs can configure the same
RatFreqPriorityGroupId.
Relation with the CnOperatorSpidCfg MO:
- RatFreqPriorityGroupId in an CnOperatorSpidCfg MO must have been set in the
associated RatFreqPriorityGroup MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add a RAT/frequency priority group configuration.


RATFREQPRIORITYG
ROUP

LST Use this command to list the configuration of one or all RAT/frequency priority
RATFREQPRIORITYG
ROUP groups.

MOD Use this command to modify the RAT/frequency priority group configuration.
RATFREQPRIORITYG
ROUP

RMV Use this command to remove the RAT/frequency priority group configuration.
RATFREQPRIORITYG
ROUP

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

RAT frequency priority Indicates the ID of the RAT/frequency priority group.


group ID

RAT Type Indicates the Radio Access Technology (RAT).


Table 2 Related parameters

Parameter Description

DL Earfcn or Bandclass Indicates the downlink frequency. In CDMA2000, this parameter indicates the
bandclass. Before configuring a priority for a frequency specified by this
parameter, ensure that an external or local cell operating on this frequency has
been configured.

Priority Indicates the priority of the intra-RAT frequency band or frequency. The value 0
indicates the lowest priority.

GERAN Frequency Indicates the GERAN frequency band.


Indicator

5.7.1.6.3.149 RlcPdcpParaGroup
+-NE
+-eNodeBFunction
+-RlcPdcpParaGroup

Description

An RlcPdcpParaGroup MO is a group of parameters related to Radio Link Control (RLC) and


Packet Data Convergence Protocol (PDCP).
RLC provides data transmission service for the upper layer.
PDCP provides encryption and integrity protection.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Relation with the ExtendedQci MO:


- RlcPdcpParaGroupId in an ExtendedQci MO must have been set in the associated
RlcPdcpParaGroup MO.
Relation with the StandardQci MO:
- RlcPdcpParaGroupId in a StandardQci MO must have been set in the associated
RlcPdcpParaGroup MO.
Relation with the eNodeBFunction:
- The number of RlcPdcpParaGroup MOs must be from 1 to 40.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add an RLC/PDCP parameter group.


RLCPDCPPARAGROU
P

LST Use this command to list one or all RLC/PDCP parameter groups.
RLCPDCPPARAGROU
P

MOD Use this command to modify an RLC/PDCP parameter group.


RLCPDCPPARAGROU
P

RMV Use this command to remove an RLC/PDCP parameter group.


RLCPDCPPARAGROU
P

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

RLC PDCP parameter Indicates the ID of the RLC/PDCP parameter group.


group ID

Discard timer Indicates the length of the PDCP discard timer.

RLC-UM or RLC-AM Indicates the RLC transmission mode. Only the AM and UM modes are
mode
available.

MaxretxThreshold for Indicates the UE-specific maximum number of RLC ARQ retransmissions,
UE
namely the maximum number of AM PDU retransmissions. When the number of
retransmissions reaches the value of this parameter, RRC connection re-
Table 2 Related parameters

Parameter Description

establishment is initiated.

MaxRetxThreshold for Indicates the eNodeB-specific maximum number of RLC ARQ retransmissions,
eNodeB
namely the maximum number of AM PDU retransmissions. When the number of
retransmissions reaches the value of this parameter, RRC connection re-
establishment is initiated.

PollByte for UE Indicates the UE-specific data volume threshold of PDUs to trigger polling.
When the transmitted data volume reaches the value of this parameter, the Poll
flag is set in the PDU header.

PollByte for eNodeB Indicates the eNodeB-specific data volume threshold of PDUs to trigger polling.
When the transmitted data volume reaches the value of this parameter, the Poll
flag is set in the PDU header.

PollPdu for UE Indicates the UE-specific number of PDUs to trigger polling. When the
transmitted number of PDUs reaches the value of this parameter, the Poll flag is
set in the PDU header.

PollPdu for eNodeB Indicates the eNodeB-specific number of PDUs to trigger polling. When the
transmitted number of PDUs reaches the value of this parameter, the Poll flag is
set in the PDU header.

Poll retransmit timer for Indicates the length of the Polling PDU retransmission timer for the UE.
UE

Poll retransmit timer for Indicates the length of the Polling PDU retransmission timer for the eNodeB.
eNodeB

Status prohibit timer for Indicates the length of the UE-specific timer for prohibiting status reporting
UE
from the receiver in AM.

Status prohibit timer for Indicates the length of the eNodeB-specific timer for prohibiting status reporting
eNodeB
from the receiver in AM.

AM reordering timer for Indicates the length of the UE-specific timer for reordering at the receiver in
UE
AM.

AM reordering timer for Indicates the length of the eNodeB-specific timer for reordering at the receiver
eNodeB
in AM.

UM PDCP-SN size Indicates the length of a PDCP sequence number of a UL DRB in RLC UM.

Uplink RLC-Sn size Indicates the length of a UL RLC sequence number in UM. The length is
permanently 10 bits in AM.
Table 2 Related parameters

Parameter Description

Downlink RLC-SN size Indicates the length of a DL RLC sequence number in UM. The length is
permanently 10 bits in AM.

UM reordering timer for Indicates the length of the UE-specific timer for reordering at the receiver in
UE
UM.

UM reordering timer for Indicates the length of the eNodeB-specific timer for reordering at the receiver
eNodeB
in UM.

AM PDCP status report Indicates whether a PDCP status report is required upon handover in AM.
required indication

5.7.1.6.3.150 RlfTimerConstGroup
+-NE
+-eNodeBFunction
+-Cell
+-RlfTimerConstGroup

Description

The RlfTimerConstGroup MO defines the RLF timer and constants for services with a specific
QCI. For details, see 3GPP TS 36.331.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the CellExtendedQci MO:


- When RlfTimerConstCfgInd is set to CFG, RlfTimerConstGroupId in a
CellExtendedQci MO must have been set in the associated RlfTimerConstGroup MO.
Relation with the CellStandardQci MO:
- When RlfTimerConstCfgInd is set to CFG, RlfTimerConstGroupId in a
CellStandardQci MO must have been set in the associated RlfTimerConstGroup MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add a parameter group related to RLF timer and constants.
RLFTIMERCONSTGR
OUP

LST Use this command to list one or all parameter groups related to RLF timer and
RLFTIMERCONSTGR
OUP constants.

MOD Use this command to modify a parameter group related to RLF timer and
RLFTIMERCONSTGR
OUP constants.

RMV Use this command to remove a parameter group related to RLF timer and
RLFTIMERCONSTGR
OUP constants.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local cell identity. It uniquely identifies a cell within an eNodeB.

RLF timer and Indicates the RLF timer and constants group ID.
constants group ID

Timer 301 Indicates the length of the timer T301. For details, see 3GPP TS 36.331.

Timer 310 Indicates the length of the timer T310. For details, see 3GPP TS 36.331.

Timer 311 Indicates the length of the timer T311. For details, see 3GPP TS 36.331.

Constant N310 Indicates the maximum number of successive "out of sync" indications received
from L1. For details, see 3GPP TS 36.331.
Table 2 Related parameters

Parameter Description

Constant N311 Indicates the maximum number of successive "in sync" indications received
from L1. For details, see 3GPP TS 36.331.

5.7.1.6.3.151 RrcConnStateTimer
+-NE
+-eNodeBFunction
+-RrcConnStateTimer

Description

The RrcConnStateTimer MO contains the timers related to RRC connection control. These
timers are defined in 3GPP TS 36.331.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the parameters related to the timers of RRC connection
RRCCONNSTATETIME
R control.

MOD Use this command to modify the parameters related to the timers of RRC
RRCCONNSTATETIME
R connection control.
Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Timer302 Indicates the length of the timer T302.


T302 specifies the wait duration for retransmitting an RRCConnectionRequest
message after the previous request is rejected.
This timer is started when the UE receives an RRCConnectionReject message
and stopped when the UE enters the RRC_CONNECTED mode or performs cell
reselection.

Timer320 for load Indicates the length of timer T320 for load balancing. T320 specifies the time
balance
period during which the dedicated priorities (used for cell reselection) retain
valid. The time period is contained in the RRCConnectionRelease message that
is received by the UE. After T320 expires, the dedicated priorities become
invalid.
This timer is started when the UE receives an RRCConnectionRelease message
containing the t320 IE.
This timer is stopped when the UE enters the RRC_CONNECTED mode.

Timer304 for EUTRAN Indicates the length of timer T304 for intra-RAT handover. If the UE does not
complete the handover before this timer expires, the UE reverts back to the
associated configuration and initiates an RRC connection reestablishment
procedure.

Timer304 for GERAN Indicates the length of timer T304 for inter-RAT handover to GERAN. If the UE
does not complete the handover before this timer expires, the UE reverts back to
the associated configuration and initiates an RRC connection re-establishment
procedure.

Timer320 for other Indicates the length of timer T320 to be contained in RRCConnectionRelease
messages sent for reasons other than load balancing. T320 specifies the time
period during which the dedicated priorities (used for cell reselection) are valid.
After T320 expires, the dedicated priorities become invalid. This parameter is
invalid for UEs to be redirected based on the subscriber profile ID (SPID).
This timer is started when the UE receives an RRCConnectionRelease message
containing the t320 IE. It is stopped when the UE enters the
RRC_CONNECTED mode.

Ue inactive timer Indicates the length of the UE inactivity timer. If the eNodeB detects that a UE
has neither received nor sent data for a duration exceeding the value of this
parameter, the eNodeB releases the RRC connection for the UE. If this
parameter is set to 0, the UE inactivity timer is not used. If this parameter is
Table 2 Related parameters

Parameter Description

modified, the modified value applies only to UEs that access the network later.

Uplink Sync Timer Indicates the timer used to govern the period in which the eNodeB maintains
uplink synchronization for a UE. After this timer expires, the eNodeB does not
send Timing Advance Command to the UE. This parameter does not take effect
if it is set to 0. That is, the eNodeB will constantly send Timing Advance
Command to the UE to maintain uplink synchronization for the UE.

Filter Repeated Indicates the length of the timer for the eNodeB to filter repeated RRC
RRCConnReq Timer
Connection Request messages. The actually used timer length is the sum of
T300 length and the value of this parameter.

UE Inactivity Timer Indicates the length of the UE inactivity timer for DRX UEs when dynamic
Dynamic DRX
DRX is enabled. If the eNodeB detects that a UE has neither received nor sent
data for a duration exceeding the value of this parameter, the eNodeB releases
the RRC connection for the UE. A large value of this parameter reduces the
amount of signaling but increase UE power consumption.You are advised to set
this parameter to a value greater than the value of UlSynTimerDynDrx.In power
saving mode, you are advised to set this parameter significantly different to the
value of the UlSynTimerDynDrx parameter, for example a gap of 10 seconds, to
avoid power consumption increase due to the increase of signaling.

Uplink Sync Timer Indicates the timer used to govern the period in which the eNodeB maintains
Dynamic DRX
uplink synchronization for a DRX UE when dynamic DRX is enabled. After this
timer expires, the eNodeB does not send Timing Advance Command to the UE.
You are advised to set this parameter to a value smaller than the value of
UeInactivityTimerDynDrx.In power saving mode, you are advised to set this
parameter significantly different to the value of the UeInactivityTimerDynDrx
parameter, for example a gap of 10 seconds, to avoid power consumption
increase due to the increase of signaling.

5.7.1.6.3.152 S1
+-NE
+-eNodeBFunction
+-S1

Description
An S1 MO is used to configure transport resources for S1 interfaces. The configuration items
include the control-plane end point group ID, user-plane end point group ID, and the CN
operator that owns the S1 object.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Relation with the CnOperator MO:


- CnOperatorId in an S1 MO must have been configured in the associated CnOperator MO.
Relation with the EPGROUP MO:
- EPGROUP MO referenced by CpEpGroupId in an S1 MO must have been configured.
- EPGROUP MO referenced by CpEpGroupId in an S1 MO must have been configured.
And the SCTPHOST MO referenced by the EPGROUP MO must have been configured.
- EPGROUP MO referenced by CpEpGroupId in an S1 MO must have been configured.
And only one SCTPHOST MO referenced by the EPGROUP MO can be configured with an
IPv4 address.
- EPGROUP MO referenced by UpEpGroupId in an S1 MO must have been configured.
- EPGROUP MO referenced by UpEpGroupId in an S1 MO must have been configured.
And the USERPLANEHOST MO referenced by the EPGROUP MO must have been
configured.
- EPGROUP MO referenced by UpEpGroupId in an S1 MO must have been configured. At
most six USERPLANEHOST MOs referenced by the EPGROUP MO can be configured with
IPv4 addresses.
- EPGROUP MO referenced by CpEpGroupId in an S1 MO must have been configured.
And only one SCTPHOST MO referenced by the EPGROUP MO can be configured with an
IPv6 address.
- EPGROUP MO referenced by UpEpGroupId in an S1 MO must have been configured. At
most six USERPLANEHOST MOs referenced by the EPGROUP MO can be configured with
IPv6 addresses.
- The USERPLANEHOST MO in the EPGROUP MO referenced by the S1 MO cannot be
configured with an IPv4 address other than the DEVIP.
- The S1 MOs with the same CnOperatorId value cannot reference the EPGROUP MOs that
contain the SCTPHOST MOs in which the values of the SCTPHOSTID parameters are
different.
- The S1 MOs with the same CnOperatorId value cannot reference the EPGROUP MOs that
contain the USERPLANEHOST MOs in which the values of the UPHOSTID parameters are
different.
Relation with the X2 MO:
- CpEpGroupId in an S1 MO must be different from CpEpGroupId in any X2 MO.
- UpEpGroupId in an S1 MO must be different from UpEpGroupId in any X2 MO.
- CpEpGroupId in an S1 MO must be different from UpEpGroupId in any X2 MO.
- UpEpGroupId in an S1 MO must be different from CpEpGroupId in any X2 MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD S1 Use this command to add an S1 object.

DSP S1 Use this command to query the control-plane information about the S1 interface
under an S1 object.

LST S1 Use this command to list the S1 object information such as the S1 object ID, CN
operator ID, end point group config flag, control-plane end point group ID, user-
plane end point group ID, peer MME release, and user label.

MOD S1 Use this command to modify parameters of an S1 object.

RMV S1 Use this command to remove an S1 object.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

S1 ID Indicates the S1 object ID.

CN Operator ID Indicates the ID of the operator that owns the S1 object.


Table 2 Related parameters

Parameter Description

Control Plane End Point Indicates the ID of the control-plane end point group used by the S1 object.
Group ID

User Plane End Point Indicates the ID of the user-plane end point group used by the S1 object.
Group ID

MME Release Indicates the compliance protocol release of the MMEs to which the eNodeB is
connected through the S1 interfaces under this S1 object.

User Label Indicates the description of the S1 object.

End Point Group Config Indicates whether to configure the control-plane or user-plane end point group.
Flag

MME Selection Priority Indicates the priority of an MME to which the eNodeB is connected through the
S1 interface. A large parameter value indicates a high priority. After this
parameter is set for MMEs, the eNodeB can select a high-priority MME for UEs
attempting to access the network.

S1 Interface ID Indicates the S1 interface ID.

S1 Interface State Indicates the status of the S1 interface.

S1 Interface Is Block Indicates whether the S1 interface is blocked. An S1 interface is blocked after
the execution of BLK S1INTERFACE and is unblocked after the execution of
UBL S1INTERFACE.

S1 Interface CP Bearer Indicates the ID of the control port bearer for the S1 interface.
ID

S1 Interface CP Bearer Indicates the status of the control port (CP) bearer for the S1 interface.
State

5.7.1.6.3.153 S1Interface
+-NE
+-eNodeBFunction
+-S1Interface
+-MmeFeatureCfg[1~1]

Description
An S1Interface MO consists of user-configured parameters related to an S1 interface between an
eNodeB and a mobility management entity (MME). The parameters specify information about
the S1 interface and the MME, including the control port bearer used for the S1 interface, the
operator to which the S1 interface belongs, and the global unique MME identifier (GUMMEI)
and public land mobile network (PLMN) ID of the MME.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Possible children:
MmeFeatureCfg[1~1]

Relation with the X2Interface MO:


- S1CpBearerId in an S1Interface MO must be different from X2CpBearerId in any
X2Interface MO.
Relation with the CnOperator MO:
- CnOperatorId in an S1Interface MO must have been set in the associated CnOperator
MO.
Relation with the MmeFeatureCfg MO:
- If a S1Interface MO is configured, the MmeFeatureCfg MO that references S1InterfaceId
in the S1Interface MO must exist.
Relation with the CPBEARER MO:
- S1CpBearerId in an S1Interface MO must have been set in the associated CPBEARER
MO, and must not have been set in the SAAL type.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD S1INTERFACE Use this command to add an S1 interface.

BLK S1INTERFACE Use this command to block an S1 interface.


Table 1 Related MML commands

MML Command Function

DSP S1INTERFACE Use this command to query the information about an S1 interface, such as the
information about the CP, S1 interface status, and peer MME status. If the status
of an S1 interface is abnormal, the command output displays the information
about the peer MME that is connected to the eNodeB for the last time before the
interface is abnormal.

MOD S1INTERFACE Use this command to modify parameters of an S1 interface.

RMV S1INTERFACE Use this command to remove an S1 interface.

RST S1INTERFACE Use this command to reset an S1 interface.

UBL S1INTERFACE Use this command to unblock an S1 interface. The unblocked S1 interface
allows admission of new users.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

S1 Interface ID Indicates the ID of the S1 interface.

S1 Interface CP Bearer Indicates the ID of the control port bearer for the S1 interface.
ID

CN Operator ID Indicates the ID of the operator that owns the S1 interface.

MME Release Indicates the compliance protocol release of the MME to which the eNodeB is
connected through the S1 interface. The eNodeB sends S1 messages complying
with the protocol release specified by this parameter. The value of this parameter
must be the same as the MME-complied protocol release. If the parameter value
is different from the MME-complied protocol release, the way in which the
MME handles these message is subject to the MME implementation.

S1 Interface Is Blocked Indicates whether the S1 interface is blocked. An S1 interface is blocked after
the execution of BLK S1INTERFACE and is unblocked after the execution of
UBL S1INTERFACE.

Control Mode Indicates the control mode of the S1 interface, which determines the control
Table 2 Related parameters

Parameter Description

policies of users and the SON function on the S1 interface. When it is set to
MANUAL_MODE, only users can control the S1 interface. When it is set to
AUTO_MODE, both users and the SON function can control the S1 interface.
The control policies set in this parameter also apply to the MmeFeatureCfg MO.
When the SON function automatically sets up an S1 interface, this parameter is
set to AUTO_MODE by default. When users add or modify an S1 interface,
users can set this parameter to AUTO_MODE or MANUAL_MODE.

Auto Config Flag Indicates whether the S1 interface is created automatically or manually. This
parameter is set by the system. Users cannot modify the parameter setting. The
system sets this parameter to AUTO_CREATE when the S1 interface is created
automatically using the SON function and to MANUAL_CREATE when the S1
interface is created manually by using the CME or running an MML command.

MME Selection Priority Indicates the priority of an MME to which the eNodeB is connected through the
S1 interface. A large parameter value indicates a high priority. After this
parameter is set for MMEs, the eNodeB can select a high-priority MME for UEs
attempting to access the network.

S1 Interface State Indicates the status of the S1 interface.

S1 CP Bearer State Indicates the status of the control port bearer for the S1 interface.

MME Is Overloaded Indicates whether the MME connected to the eNodeB over the S1 interface is
overloaded. This parameter is valid after the S1 interface is established. Before
the S1 interface is established, the MME load status is NULL. For details about
the MME load status after the S1 interface is established, see 3GPP TS 36.413.

S1 Interface User Indicates the number of users that have accessed the S1 interface.
Number

MME Name Indicates the name of the MME to which the eNodeB is connected through the
S1 interface. This parameter is valid after the S1 interface is established and the
MME name is contained in the S1 interface establishing response message or the
MME configuration update message. In other conditions, the parameter value is
NULL. For details, see 3GPP TS 36.413.

Served PLMNs Indicates the IDs of all served PLMNs of the MME to which the eNodeB is
connected. The ID of a served PLMN consists of the MCC and MNC. PLMN
IDs are separated by commas (,).

Served GUMMEIs Indicates the Global Unique MME Identifiers (GUMMEIs) of all MME to
which the eNodeB is connected. A GUMMEI of a serving MME consists of the
MCC, MNC, MME group ID, and MME code. GUMMEIs are separated by
Table 2 Related parameters

Parameter Description

commas (,).

MME Relative Capacity Indicates the capacity of the connected MME relative to that of other MMEs. A
larger value of this parameter indicates a larger capacity allowing UE access.

S1 Interface Fault Indicates the reason of the fault on the S1 link.


Reason

5.7.1.6.3.154 S1ReestTimer
+-NE
+-eNodeBFunction
+-S1ReestTimer

Description

The S1ReestTimer MO consists of parameters related to the S1 reestablishment timer. This timer
is used to prevent MME breakdown or exceptions caused by signaling storms that occur when
multiple eNodeBs initiate S1 interface setup requests to one mobility management entity (MME)
at the same time. If the S1 establishment requested by an eNodeB fails, the eNodeB initiates S1
reestablishment after a period. The length of the period is a random value within the range from
the minimum length of the timer to the maximum length of the timer.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

LST S1REESTTIMER Use this command to list the parameters related to the S1 re-establishment timer.

MOD S1REESTTIMER Use this command to modify the parameters related to the S1 re-establishment
timer.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

S1 reestablish min Indicates the minimum length of the S1 re-establishment timer.


timer length

S1 reestablish max Indicates the maximum length of the S1 re-establishment timer.


timer length

5.7.1.6.3.155 ServiceIfHoCfgGroup
+-NE
+-eNodeBFunction
+-CnOperator
+-ServiceIfHoCfgGroup

Description

A ServiceIfHoCfgGroup MO is an operator-specific group of policies for service-based inter-


frequency handovers. Each MO of this class will be associated with a QCI. The default policy is
to prohibit handovers. Operators may query the operator IDs supported by the eNodeB before
configuring this MO.

Effective Scenario

Immediately
Relations Between MOs

Possible parents:
CnOperator

Relation with the CnOperatorExtendedQci MO:


- ServiceIfHoCfgGroupId in a CnOperatorExtendedQci MO must have been set in the
associated ServiceIfHoCfgGroup MO.
Relation with the CnOperatorStandardQci MO:
- ServiceIfHoCfgGroupId in a CnOperatorStandardQci MO must have been set in the
associated ServiceIfHoCfgGroup MO.
Relation with the EutranInterNFreq MO:
- if InterFreqHoState in a ServiceIfHoCfgGroup is set to PERMIT_HO,DlEarfcn in the
ServiceIfHoCfgGroup MO must have been set in the associated EutranInterNFreq MO.
Relation with the CnOperator MO:
- CnOperatorId in an ServiceIfHoCfgGroup MO must have been set in the associated
CnOperator MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add a service-based inter-frequency handover policy


SERVICEIFHOCFGGR
OUP group.

LST Use this command to list one or all service-based inter-frequency handover
SERVICEIFHOCFGGR
OUP policy groups.

MOD Use this command to modify a service-based inter-frequency handover policy


SERVICEIFHOCFGGR
OUP group.

RMV Use this command to remove a service-based inter-frequency handover policy


SERVICEIFHOCFGGR
OUP group.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

CN Operator ID Indicates the ID of the operator.

Service-based inter- Indicates the ID of the service-based inter-frequency handover policy group.
Freq handover policy
group ID

Inter-Freq handover Indicates whether UEs of an operator in this policy group can be handed over to
state
a specified frequency during service-based inter-frequency handovers.

Downlink EARFCN Indicates the frequency to which a service with a specified QCI is preferentially
handed over.

5.7.1.6.3.156 ServiceIrHoCfgGroup
+-NE
+-eNodeBFunction
+-CnOperator
+-ServiceIrHoCfgGroup

Description

A ServiceIrHoCfgGroup MO is an operator-specific group of policies for service-based inter-


RAT handovers. Each MO of this class will be associated with a QCI. The default policy is to
prohibit handover. You may query the operator indexes supported by the eNodeB before
configuring this MO.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
CnOperator

Relation with the CnOperatorExtendedQci MO:


- ServiceIrHoCfgGroupId in a CnOperatorExtendedQci MO must have been set in the
associated ServiceIrHoCfgGroup MO.
Relation with the CnOperatorStandardQci MO:
- ServiceIrHoCfgGroupId in a CnOperatorStandardQci MO must have been set in the
associated ServiceIrHoCfgGroup MO.
Relation with the CnOperator:
- If a CnOperator MO is configured, the number of ServiceIrHoCfgGroup MOs that
reference CnOperatorId in the CnOperator MO must be from 1 to 10.
Relation with the CnOperator MO:
- CnOperatorId in an ServiceIrHoCfgGroup MO must have been set in the associated
CnOperator MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add a service-based inter-RAT handover policy group.
SERVICEIRHOCFGGR
OUP

LST Use this command to list one or all service-based inter-RAT handover policy
SERVICEIRHOCFGGR
OUP groups.

MOD Use this command to modify a service-based inter-RAT handover policy group.
SERVICEIRHOCFGGR
OUP

RMV Use this command to remove a service-based inter-RAT handover policy group.
SERVICEIRHOCFGGR
OUP

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

CN Operator ID Indicates the index of the operator.

Service-based inter- Indicates the ID of the service-based inter-RAT handover policy group.
RAT handover policy
Table 2 Related parameters

Parameter Description

group ID

Inter-RAT handover Indicates whether service-based inter-RAT handovers are required, allowed, or
state
not allowed for a QCI.

5.7.1.6.3.157 SfnAuxResBind
+-NE
+-eNodeBFunction
+-SfnAuxResBind

Description

None

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Relation with the Cell MO:


- A maximum of 7 SfnCellBind MOs can be configured for each cell with same slave site
eNodeB ID.
Relation with the SfnAuxResBind MO:
- The eNodeBId in the SfnAuxResBind MO has a maximum of nine values.
Relation with the eNodeBFunction MO:
- eNodeBId in the SfnAuxResBind MO must be different from eNodeBId in the
eNodeBFunction MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD Use this command to add single frequency network(SFN) auxiliary eNodeB
SFNAUXRESBIND
resource binding relationship.

LST SFNAUXRESBIND Use this command to list single frequency network(SFN) auxiliary eNodeB
resource binding relationship.

MOD Use this command to modify a single frequency network (SFN) cell binding
SFNAUXRESBIND
relationship with an auxiliary eNodeB.

RMV Use this command to remove single frequency network(SFN) auxiliary eNodeB
SFNAUXRESBIND
resource binding relationship.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Sector equipment ID Indicates the ID of the sector device, it uniquely identifies a sector device within
an eNodeB.

Main eNodeB ID Indicates the ID of the main eNodeB.

Main eNodeB Local cell Indicates the local cell identity of a cell of the main eNodeB, it uniquely
ID
identifies a cell within the main eNodeB.

Baseband equipment Indicates the ID of the baseband equipment serving a cell.


ID
When this parameter is set to 255, the baseband equipment serving a cell is not
specified. In this scenario, the LTE baseband processing units (LBBPs) serving a
cell are selected among all LBBPs in the eNodeB, and the LBBPs to which the
cell's serving RRU is connected are preferentially selected.
When this parameter is set to a value other than 255, the cell is served by LBBPs
in the specified baseband equipment, and the LBBPs to which the cell's serving
RRU is connected are preferentially selected.

Reference signal power Indicates the reference signal power of the single frequency network (SFN)
auxiliary eNodeB resource. The value 32767 indicates that this reference signal
power parameter is invalid. In this case, the reference signal power of the cell
refers to the value of the PDSCHCfg parameter. For details, see 3GPP TS
Table 2 Related parameters

Parameter Description

36.213.

Reference signal power Indicates the cell reference signal power headroom of each physical antenna.
margin

5.7.1.6.3.158 SfnCellBind
+-NE
+-eNodeBFunction
+-Cell
+-SfnCellBind

Description

None

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the Cell MO:


- A maximum of 6 SfnCellBind MOs can be configured for each cell.
- If MultiRruCellMode is not set to SFN, SfnCellBind with the same LocalCellId can not be
exist.
Relation with the eNodeBFunction MO:
- eNodeBId in the SfnCellBind MO must be different from eNodeBId in the
eNodeBFunction MO.
Relation with the SfnCellBind MO:
- The eNodeBId in the SfnCellBind MO has a maximum of nine values.

Related MML Commands


Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD SFNCELLBIND Use this command to add single frequency network(SFN) cell binding
relationship to an auxiliary eNodeB.

LST SFNCELLBIND Use this command to list a single frequency network (SFN) cell binding
relationship to an auxiliary eNodeB.

RMV SFNCELLBIND Use this command to remove a single frequency network (SFN) cell binding
relationship to an auxiliary eNodeB.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Slave site eNodeB ID Indicates the ID of the auxiliary eNodeB.

5.7.1.6.3.159 SimuLoad
+-NE
+-eNodeBFunction
+-SimuLoad

Description

A SimuLoad MO consists of a set of parameters that constitute one simulated load configuration
in the eNodeB. One eNodeB stores 10 simulated load configurations, each of which is identified
by an index. When load simulation is started in a cell, the set of parameters (that is, the
referenced simulated load configuration) are used by the cell.
Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Relation with the eNodeBFunction MO:


- A eNodeBFunction MO must contain 10 SimuLoad MOs.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST SIMULOAD Use this command to list the simulated load configuration.

MOD SIMULOAD Use this command to modify the simulated load configuration.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

configuration index Indicates the index of a simulated load configuration. One BS can store 10
simulated load configurations, which are identified by the indexes.

RB usage threshold Indicates the RB usage threshold of a simulated load configuration. If the RB
usage of a cell is below this threshold, the simulated load scheduling is
performed.

Power usage threshold Indicates the power usage threshold of a simulated load configuration. If the
power usage of a cell is below this threshold, the simulated load scheduling is
performed.

Report period Indicates the reporting period for simulated load. The value 0 indicates that
Table 2 Related parameters

Parameter Description

simulated load is not reported.

Statistic period Indicates the measurement period for simulated load. The value 0 indicates that
simulated load is not measured.

Frequency selective Indicates the switch that is used to control whether to enable and disable the
switch
frequency-selective scheduling in simulated load configuration. If the switch is
set to ON, the frequency-selective scheduling is enabled. If the switch is set to
OFF, the frequency-diversity scheduling is used.

5.7.1.6.3.160 SpidCfg
+-NE
+-eNodeBFunction
+-SpidCfg

Description

An SpidCfg MO consists of parameters related to a subscriber profile ID. Parameters in an


SpidCfg MO include the priority of camping of a UE in idle mode, inter-frequency or inter-RAT
handover priority of a UE in connected mode, support of special DRX, support of pre-allocation,
SPID-based inter-frequency or inter-RAT load balancing switch, and SPID-based handover back
to HPLMN switch. Special DRX is used for UEs that do not require power saving.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Relation with the RatFreqPriorityGroup MO:


- RatFreqPriorityGroupId in an SpidCfg MO must have been set in the associated
RatFreqPriorityGroup MO.

Related MML Commands


Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD SPIDCFG Use this command to add a subscriber profile ID (SPID) configuration.

LST SPIDCFG Use this command to list the configuration of one or all subscriber profile IDs
(SPIDs).

MOD SPIDCFG Use this command to modify the subscriber profile ID (SPID) configuration.

RMV SPIDCFG Use this command to remove the subscriber profile ID (SPID) configuration.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Spid Indicates the subscriber profile ID (SPID).

Drx status Indicates whether to use normal or special DRX. If this parameter is set to
TRUE, ordinary DRX parameters are applied to UEs with the SPID. If this
parameter is set to FALSE, special DRX parameters are applied to UEs with the
SPID.

RAT frequency priority Indicates whether to set the priority for the intra-RAT frequency group. If this
indication
parameter is set to CFG(CFG), UEs select the target frequency based on the
priority setting. If this parameter is set to NOT_CFG(NOT_CFG), UEs do not
select the target frequency based on the priority setting.

RAT frequency priority Indicates the ID of the intra-RAT frequency priority group.
group ID

PreallocationStatus Indicates whether to support preallocation. If this parameter is set to TRUE and
PreAllocationSwitch under the UlSchSwitch parameter in the CellAlgoSwitch
MO is set to On, resources can be preallocated to UEs. Otherwise, resources are
not preallocated to UEs.

InterFreq Mlb Switch Indicates whether to enable or disable inter-frequency load balancing for the
SPID. The values TRUE or FALSE indicate that inter-frequency load balancing
is allowed or prohibited for UEs with the SPID, respectively.
Table 2 Related parameters

Parameter Description

InterRat Mlb Switch Indicates whether to enable or disable inter-RAT load sharing for the SPID. The
values TRUE or FALSE indicate that inter-RAT load sharing is allowed or
prohibited for UEs with the SPID, respectively.

SPID-based Handover Indicates whether to allow SPID-based handovers back to the home public land
Back To HPLMN Switch
mobile network (HPLMN). If this parameter is set to TRUE(TRUE), a roaming
UE can be handed over to the HPLMN network when it moves back to the
coverage of the HPLMN network based on the SPID. If this parameter is set to
FALSE(FALSE), this UE cannot be handed over to the HPLMN network based
on the SPID.

5.7.1.6.3.161 SrsAdaptiveCfg
+-NE
+-eNodeBFunction
+-SrsAdaptiveCfg

Description

The SrsAdaptiveCfg MO consists of the parameters related to UE-specific sounding reference


signal (SRS) adaptation. If SRS adaptation is enabled, the eNodeB sets the SRS period based on
channel conditions. If SRS adaptation is disabled, the eNodeB sets a fixed SRS period.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

LST Use this command to list the parameters related to SRS adaptation.
SRSADAPTIVECFG

MOD Use this command to modify the parameters related to SRS adaptation.
SRSADAPTIVECFG

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

SRS period adaptive Indicates whether to enable or disable SRS period adaptation. If this parameter
switch
is set to ON, the SRS period adaptively changes based on the SRS algorithm. If
this parameter is set to OFF, the SRS period is the specified by the
UserSrsPeriodCfg parameter.If the parameter TddSrsCfgMode is set to
ACCESS_FIRST or EXPERIENCE_ENHANCED,this parameter setting is
invalid.

User SRS period config Indicates the fixed SRS period. A fixed SRS period is used when SRS period
adaptation is disabled.

5.7.1.6.3.162 SRSCfg
+-NE
+-eNodeBFunction
+-Cell
+-SRSCfg

Description

The SRSCfg MO consists of the parameters related to the configuration of sounding reference
signals (SRSs). For details about the SRSs, see 3GPP TS 36.211.

Effective Scenario
Immediately

Relations Between MOs

Possible parents:
Cell

Relation with the Cell MO:


- If FddTddInd in a Cell MO is set to CELL_TDD, SrsSubframeCfg in the associated
SRSCfg MO must be smaller than SC14.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

DSP SRSCFG Use this command to query the cell-specific SRS bandwidth.

LST SRSCFG Use this command to list the parameters of the SRS configuration.

MOD SRSCFG Use this command to modify the SRS configuration.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

SRS subframe Indicates the index of the SRS subframe configuration for the cell.
configuration
The value SCn, where n is variable, represents configuration n. For example, the
value SC0 indicates subframe configuration 0, and the value SC1 indicates
subframe configuration 1. If the cell operates in FDD mode, the value SC15 is
reserved. If the cell operates in TDD mode, the values SC14 and SC15 are
reserved. The reserved values cannot be used. For the relationship between the
subframe configuration index and the cell-specific subframe cycle/offset, see
3GPP TS 36.211. In FDD mode, this parameter is permanently valid. In TDD
mode, this parameter is valid only if TddSrsCfgMode is set to
Table 2 Related parameters

Parameter Description

EXPERIENCE_FIRST.

SRS ACK/NACK Indicates whether the sounding reference signal (SRS) of a UE and the
simultaneous
transmission ACK/NACK or scheduling request (SR) on the PUCCH are allowed to use the
same time resources for simultaneous transmission.
If this parameter is set to BOOLEAN_FALSE, simultaneous transmission is not
allowed. In this situation, the UE discards the SRS and only transmits the
ACK/NACK or SR on the PUCCH.
If this parameter is set to BOOLEAN_TRUE, simultaneous transmission is
allowed. In this situation, the UE transmits truncated ACK/NACK or SR. For
details, see 3GPP TS 36.211.

SRS Configuration Indicates whether to configure sounding reference signal (SRS) resources for
Indicator
UEs in a cell. The value BOOLEAN_TRUE indicates that SRS resources are
available in the cell and can be configured for UEs in the cell. The value
BOOLEAN_FALSE indicates that no SRS resource is available in the cell, and
therefore no UE in the cell is configured with SRS resources. This parameter
does not take effect on: (1) an FDD cell that is established on an LBBPc and
uses four or more RX antennas; (2) an FDD cell that is established on an LBBPc
and uses extended cyclic prefix (CP) in the uplink; (3) a TDD cell established on
an LBBPc. If this parameter does not take effect on a cell but SRS resources are
available in the cell, SRS resources can be configured for UEs in the cell.

TDD SRS Configuration Indicates the TDD SRS configuration to be used. If this parameter is set to
Mode
ACCESS_FIRST, the TDD SRS configuration that is designed to preferentially
guarantee the specifications (for example, accessed UEs and CAPS) is used. If
this parameter is set to EXPERIENCE_FIRST, the TDD SRS configuration that
is designed to preferentially guarantee user experience (for example,
beamforming performance) is used. CAPS is short for call attempt per second. If
this parameter is set to EXPERIENCE_ENHANCED, users can get better DL
user experience than that in EXPERIENCE_FIRST mode. This parameter
cannot be set to EXPERIENCE_ENHANCED if the LBBPc is used. If a cell is
established on an LBBPc but this parameter is set to
EXPERIENCE_ENHANCED, EXPERIENCE_ENHANCED is automatically
changed to EXPERIENCE_FIRST when this parameter takes effect. This
parameter is valid only in TDD mode.

Cell srs bandwidth Indicates the cell-specific SRS bandwidth. It corresponds to the srs-
configuration
BandwidthConfig parameter in the protocol. For details, see 3GPP TS 36.211.

5.7.1.6.3.163 StandardQci
+-NE
+-eNodeBFunction
+-StandardQci

Description

The StandardQci MO consists of the parameters related to each standardized QoS Class
Identifier (QCI).

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Relation with the InterRatPolicyCfgGroup MO:


- InterRatPolicyCfgGroupId in a StandardQci MO must have been set in the associated
InterRatPolicyCfgGroup MO.
Relation with the RlcPdcpParaGroup MO:
- RlcPdcpParaGroupId in a StandardQci MO must have been set in the associated
RlcPdcpParaGroup MO.
Relation with the eNodeBFunction MO:
- The number of StandardQci MOs must be 9.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST STANDARDQCI Use this command to list standardized QCI settings.

MOD STANDARDQCI Use this command to modify the settings of a standardized QCI.

Related Parameters
Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

QoS Class Indication Indicates the QoS Class Identifier (QCI) of an EPS bearer. Different QCIs
represent different QoS specifications such as the packet delay budget, packet
error loss rate, and resource type (whether the service is a GBR service or not).
For details, see Table 6.1.7 in 3GPP TS 23.203.

Ulsch priority factor Indicates the weight factor used in the calculation of connection priorities during
uplink scheduling.

Dlsch priority factor Indicates the weight factor used in the calculation of connection priorities during
downlink scheduling.

Uplink MinGBR Indicates the uplink minimum guaranteed bit rate of the non-GBR service.

Downlink MinGBR Indicates the downlink minimum guaranteed bit rate of the non-GBR service.

Pre-allocation weight Indicates the pre-allocation weight. The pre-allocation weight of a UE is the pre-
allocation weight of services carried by the highest-priority logical channel. If
services carried by highest-priority logical channels have different pre-allocation
weights, the UE takes the highest pre-allocation weight. When resources are
insufficient, pre-allocation weights affect the pre-allocation probabilities of
users. The pre-allocation probability has a positive correlation with the pre-
allocation weight. This parameter is QCI-specific.

InterRAT policy config Indicates the ID of a parameter group related to inter-RAT handover.
group ID

RLC PDCP parameter Indicates the ID of an RLC/PDCP parameter group.


group ID

Prioritised bit rate Indicates the prioritized bit rate of the logical channel. The UE scheduler
guarantees prioritized bit rates of logical channels in descending order of logical
channel priority. For details, see 3GPP TS 36.321.

Logical channel priority Indicates the priority of the logical channel. The UE scheduler guarantees
prioritized bit rates of logical channels in descending order of logical channel
priority. Resources are allocated in descending order of logical channel priority
after the prioritized bit rates of all services are guaranteed. For details, see 3GPP
TS 36.321.

Flow control type Indicates whether to enable flow control for the QCI.
5.7.1.6.3.164 TceIpMapping
+-NE
+-eNodeBFunction
+-TceIpMapping

Description

A TceIPMapping MO consists of the parameters related to the mapping between the ID and IP
address of a trace collection entity (TCE) for minimization of drive tests (MDT).
For an area-specific MDT procedure, the NMS or EMS specifies at logged MDT subscription the
TCE to which the collected data will be reported. At the delivery of subscribed information, the
application sends the TCE IP address to the eNodeB.
In a single-user-based MDT procedure, the MME sends the TCE IP address to the eNodeB. To
ensure security, 3GPP TS 37.320 specifies that the TCE ID instead of the TCE IP address be
transmitted over the radio interface.
To ensure that TCE IDs and TCE IP addresses are converted in the same way in both procedures,
the EMS needs to be configured with a table of mapping between TCE IDs and TCE IP
addresses. This table must be unique in the entire network. Based on the mapping table, the
eNodeB converts a TCE IP address into a TCE ID and sends this ID to the UE.
TCE IP addresses and TCE IDs must have a one-to-one mapping.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD TCEIPMAPPING Use this


Table 1 Related MML commands

MML Command Function

command to add a mapping between the Trace Collection Entity (TCE) ID and
IP address.

LST TCEIPMAPPING Use this


command to list the mapping between TCE IDs and TCE IP addresses.

MOD TCEIPMAPPING Use this command to modify the mapping between TCE IDs and IP addresses.

RMV TCEIPMAPPING Use this command to remove the mapping between a TCE ID and a TCE IP
address.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

TCE ID Indicates the ID of the TCE for MDT.

IP Mode Indicates the IP address version. IPv4~0 indicates that the IP version is IPv4.
IPv6~1 indicates that the IP version is IPv6.

TCE IPv4 Address Indicates the IPv4 address of the TCE.

TCE IPv6 Address Indicates the IPv6 address of the TCE.

5.7.1.6.3.165 TcpAckCtrlAlgo
+-NE
+-eNodeBFunction
+-TcpAckCtrlAlgo

Description
The TcpAckCtrlAlgo MO defines the TCP ACK control algorithm between the Packet Data
Convergence Protocol (PDCP) and GPRS Tunneling Protocol-User plane (G-TPU) modules on
the eNodeB. By controlling traffic of the ACKs to uplink Transmission Control Protocol (TCP)
packets, this algorithm prevents traffic bursts caused by error or lost packets over the air
interface, thereby reducing the packet loss rate and improving the TCP throughput in the
downlink.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the configuration of the TCP ACK control algorithm.
TCPACKCTRLALGO

MOD Use this command to modify the configuration of the TCP ACK control
TCPACKCTRLALGO
algorithm.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

TCP ACK Control Indicates whether to enable or disable the TCP ACK control algorithm.
Switch

DL Max Throughput Indicates the maximum downlink throughput in the TCP ACK control algorithm.
If this parameter is set to 0, the downlink throughput in the TCP ACK control
algorithm is not under control.
Table 2 Related parameters

Parameter Description

Control Timer Length Indicates the timer length for the TCP ACK control algorithm. This timer can be
used to control traffic of the ACKs to uplink TCP packets, therefore preventing
traffic bursts in the downlink.

5.7.1.6.3.166 TcpMssCtrl
+-NE
+-eNodeBFunction
+-TcpMssCtrl

Description

The TcpMssCtrl MO defines the TCP maximum segment size (MSS) control function on the
eNodeB side. If the eNodeB detects a packet that is not used for setting up a TCP connection, the
eNodeB transparently transmits the packet. If the eNodeB detects a packet that is used for setting
up a TCP connection, the eNodeB checks the MSS field in the packet. If the MSS is greater than
the value specified by this MO, the eNodeB changes the MSS to the specified value, calculates
the TCP checksum again, writes the checksum in the packet, and then sends the packet.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

LST TCPMSSCTRL Use this command to list the configuration of the TCP MSS control algorithm.

MOD TCPMSSCTRL Use this command to modify the TCP MSS control algorithm.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

TCP MSS Control Indicates the switch used to enable or disable the TCP MSS function. If this
Switch
switch is turned off, TCP packets are transparently transmitted without being
processed. If this switch is turned on, the value of the MSS field in each packet
for TCP link setups can be modified.

TCP MSS Threshold Indicates the threshold for the value of the MSS field in packets for TCP link
setups. If the TCP MSS function is enabled, the eNodeB first checks the MSS
field in each packet for TCP link setups. If the value of the MSS field is greater
than the predefined threshold, the eNodeB changes the value of the MSS field to
the predefined threshold. Then, the eNodeB recalculates the TCP checksum and
retransmits the packet with modified fields. For other packets, the eNodeB
transparently transmits them.

5.7.1.6.3.167 TddFrameOffset
+-NE
+-eNodeBFunction
+-TddFrameOffset

Description

The TddFrameOffset MO contains the parameter that indicates the time delay of the frame start
time for all TDD E-UTRAN cells under the eNodeB to standard time.

Effective Scenario
Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to list the time delay of the frame start time for all TDD E-
TDDFRAMEOFFSET
UTRAN cells under the eNodeB to standard time.

MOD Use this command to modify the time delay of the frame start time for all TDD
TDDFRAMEOFFSET
E-UTRAN cells under the eNodeB to standard time.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

TDD time offset Indicates the time delay of the frame start time for all TDD E-UTRAN cells
under the eNodeB to the time of the reference clock.

5.7.1.6.3.168 TddResModeSwitch
+-NE
+-eNodeBFunction
+-TddResModeSwitch

Description
The TddResModeSwitch MO specifies the switch for controlling the TDD cell resource mode. If
the switch is turned on, the TDD cell can be forcibly activated in specific resource mode.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST Use this command to query whether the activation of a TDD cell depends on the
TDDRESMODESW
availability of clock resources.

MOD Use this command to specify whether the activation of a TDD cell depends on
TDDRESMODESW
the availability of clock resources. Only TDD cells support this parameter.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Clock-Unavailable Cell Indicates the switch for forcibly activating a TDD cell. If this parameter is set to
Activation Switch
ON, a TDD cell can be activated when no clock resource is available. If this
parameter is set to OFF, a TDD cell cannot be activated when no clock resource
is available.

5.7.1.6.3.169 TimeAlignmentTimer
+-NE
+-eNodeBFunction
+-Cell
+-TimeAlignmentTimer

Description

The TimeAlignmentTimer MO defines parameters related to uplink time alignment for UEs in a
cell.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST TATIMER Use this command to list the parameters of the uplink time alignment timer for
UEs in a cell.

MOD TATIMER Use this command to modify the parameters of the uplink time alignment timer
for UEs in a cell.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local identity of the cell. It uniquely identifies a cell within an
Table 2 Related parameters

Parameter Description

eNodeB.

Uplink time alignment Indicates the length of the uplink time alignment timer for UEs in the cell. A UE
timer
is considered not time-aligned in the uplink if the timer expires.

Uplink timing advance Indicates whether optimization of the mechanism for delivering the uplink time
command optimization
switch alignment command takes effect. If the optimization takes effect, the number of
unnecessary uplink time alignment commands delivered to motionless or low-
mobility UEs can be reduced to save air interface resources and reduce power
consumption of UEs in DRX mode. This ensures the uplink time alignment
performance if the length of the uplink time alignment timer is set to a large
value.
If this parameter is set to ON, it is recommended that the TimeAlignmentTimer
parameter be set to SF10240. A smaller value of the TimeAlignmentTimer
parameter, such as SF5120, leads to a higher probability of becoming out-of-
synchronization in the uplink for UEs in DRX mode.
If this parameter is set to ON, it is recommended that the LongDrxCycle
parameter be smaller than or equal to SF320. Otherwise, the uplink time
alignment performance of UEs in DRX mode is affected.

5.7.1.6.3.170 TpeAlgo
+-NE
+-eNodeBFunction
+-TpeAlgo

Description

The TpeAlgo MO consists of the parameters related to TCP performance enhancer (TPE), which
includes the number of ports to which TPE is to be applied and specific port numbers.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST TPEALGO Use this command to list the configuration of the TPE algorithm. The ports with
enabled TPE are listed starting from TPE Port 1 in the command output, with the
number of ports equal the value of TPE Port Num.

MOD TPEALGO Use this command to modify the configuration of the TPE algorithm.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

TCP Port Number Indicates the number of ports that enable TCP acceleration.

TCP Port 1 Indicates port 1 to which TPE is to be applied.

TCP Port 2 Indicates port 2 to which TPE is to be applied.

TCP Port 3 Indicates port 3 to which TPE is to be applied.

TCP Port 4 Indicates port 4 to which TPE is to be applied.

TCP Port 5 Indicates port 5 to which TPE is to be applied.

TCP Port 6 Indicates port 6 to which TPE is to be applied.

TCP Port 7 Indicates port 7 to which TPE is to be applied.

TCP Port 8 Indicates port 8 to which TPE is to be applied.

TCP Port 9 Indicates port 9 to which TPE is to be applied.

TCP Port 10 Indicates port 10 to which TPE is to be applied.


Table 2 Related parameters

Parameter Description

TCP Port 11 Indicates port 11 to which TPE is to be applied.

TCP Port 12 Indicates port 12 to which TPE is to be applied.

TCP Port 13 Indicates port 13 to which TPE is to be applied.

TCP Port 14 Indicates port 14 to which TPE is to be applied.

TCP Port 15 Indicates port 15 to which TPE is to be applied.

TCP Port 16 Indicates port 16 to which TPE is to be applied.

TCP Port 17 Indicates port 17 to which TPE is to be applied.

TCP Port 18 Indicates port 18 to which TPE is to be applied.

TCP Port 19 Indicates port 19 to which TPE is to be applied.

TCP Port 20 Indicates port 20 to which TPE is to be applied.

5.7.1.6.3.171 TypDrbBsr
+-NE
+-eNodeBFunction
+-TypDrbBsr

Description

A BSR indicates the total amount of data in the uplink buffer in a UE. For details, see 3GPP TS
36.321.

Effective Scenario

Immediately

Relations Between MOs


Possible parents:
eNodeBFunction

Relation with the eNodeBFunction MO:


- The number of TypDrbBsr MOs must be 9.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST TYPDRBBSR Use this command to list timer settings related to buffer status reports (BSRs)
for a QoS class identifier (QCI).

MOD TYPDRBBSR Use this command to modify timer settings related to buffer status reports
(BSRs) for a QoS class identifier (QCI).

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

QoS Class Identifier Indicates the QoS class identifier (QCI).


QCI 1 indicates voice services.
QCI 2 indicates video (live streaming) services.
QCI 3 indicates real-time gaming services.
QCI 4 indicates video (buffered streaming) services.
QCI 5 indicates IMS signaling.
QCI 7 indicates voice, video, and interactive gaming services.
QCIs 6, 8, and 9 indicate video services and TCP-based services.

Periodic BSR Timer Indicates the length of the timer for periodic transmission of buffer status reports
(BSRs).
BSRs are sent periodically or as triggered by events.
Periodic transmission of BSRs uses the timer specified by this parameter.
When the timer expires, a BSR is sent.
Table 2 Related parameters

Parameter Description

After the BSR is sent, the timer is restarted.

BSR Retransmission Indicates the length of the BSR (Buffer Status Report) retransmission timer. This
Timer
timer is started after a BSR is sent.

5.7.1.6.3.172 UeTimerConst
+-NE
+-eNodeBFunction
+-Cell
+-UeTimerConst

Description

The UeTimerConst MO consists of the parameters related to UE timers, which are constant
information in system information block 2 (SIB2). For details on these timers, see 3GPP TS
36.331.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

LST UETIMERCONST Use this command to list the settings of UE timers and constants.
Table 1 Related MML commands

MML Command Function

MOD UETIMERCONST Use this command to modify the settings of UE timers and constants.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

Timer 300 Indicates the timer value of Timer 300. For details, see 3GPP TS 36.331.
This timer is started when the UE sends RRCConnectionRequest.
Before the timer expires, it is stopped if the UE receives RRCConnectionSetup
or RRCConnectionReject.
After the timer expires, the UE enters the RRC_IDLE state.

Timer 301 Indicates the length of timer 301. For details, see 3GPP TS 36.331.
This timer is started when the UE sends an RRC Connection Reestablishment
Request message.
The timer is stopped if, before it expires, the UE receives an RRC Connection
Reestablishment or RRC Connection Reestablishment Reject message. The
timer is also stopped if the selected cell becomes an unsuitable cell. For the
definition of a suitable cell, see 3GPP TS 36.331.
After the timer expires, the UE enters the RRC_IDLE mode.

Timer 310 Indicates the length of timer 310. For details, see 3GPP TS 36.331.
This timer is started when the UE detects any fault at the physical layer.
The timer is stopped if the UE detects one of the following before the timer
expires: (1) The physical-layer fault is rectified; (2) A handover is triggered; (3)
The UE initiates an RRC connection reestablishment procedure.
After the timer expires, the UE enters the RRC_IDLE mode if the security mode
is not activated. If the security mode is activated, the UE initiates an RRC
connection reestablishment procedure.

Timer 311 Indicates the length of timer 311. For details, see 3GPP TS 36.331.
This timer is started when the UE starts the RRC connection reestablishment
procedure.
Table 2 Related parameters

Parameter Description

The timer is stopped if, before the timer expires, the UE selects an E-UTRAN or
inter-RAT cell to camp on.
After the timer expires, the UE enters the RRC_IDLE mode.

Constant N311 Indicates the maximum number of successive "in sync" indications received
from L1. For details, see 3GPP TS 36.331.

Constant N310 Indicates the maximum number of successive "out of sync" indications received
from L1. For details, see 3GPP TS 36.331.

5.7.1.6.3.173 UtranExternalCell
+-NE
+-eNodeBFunction
+-UtranExternalCell
+-UtranExternalCellPlmn[0~3]

Description

A UtranExternalCell MO consists of the parameters related to an external UTRAN cell, which


can be configured as a neighboring cell of one or more cell under the local eNodeB. The
neighboring cell list (NCL) of an eNodeB contains the common information about its external
UTRAN cells. In RAN sharing mode, additional PLMN IDs must be added for each external
UTRAN cell.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Possible children:
UtranExternalCellPlmn[0~3]

Relation with the UtranNCell,UtranNFreq MOs:


- UtranDlArfcn and UtranFddTddType in the UtranExternalCell MO associated with a
UtranNCell MO must have been configured in a UtranNFreq MO.
Relation with the UtranNCell MO:
- Before adding a UtranNCell MO, ensure that the associated UtranExternalCell MO has
been configured.
- In all UtranNCell MOs of a local Cell MO, the combination of UtranDlArfcn and
PScrambCode in the UtranExternalCell MO corresponding to each UtranNCell MO must be
unique.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add an external UTRAN cell.


UTRANEXTERNALCEL
L

ADD Use this command to add the external UTRAN cell slave band.
UTRANEXTERNALCEL
LBAND

LST Use this command to list the external UTRAN cell.


UTRANEXTERNALCEL
L

LST Use this command to list the external UTRAN cell slave band.
UTRANEXTERNALCEL
LBAND

MOD Use this command to modify the parameters of an external UTRAN cell.
UTRANEXTERNALCEL
L

RMV Use this command to remove an external UTRAN cell.


UTRANEXTERNALCEL
L

RMV Use this command to remove the external UTRAN cell slave band.
UTRANEXTERNALCEL
LBAND

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Mobile country code Indicates the mobile country code of the external UTRAN cell.
The PLMN consists of the MCC and the MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, MCC = 123, MNC = 45, PLMN = 12345.

Mobile network code Indicates the mobile network code of the external UTRAN cell.
The PLMN consists of the MCC and the MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, MCC = 123, MNC = 45, PLMN = 12345.

RNC ID Indicates the RNC ID of the external UTRAN cell. The 28-bit UTRAN cell ID is
comprised of the RNC cell ID and the RNC ID that are represented by the least
significant 16 bits and the most significant 12 bits, respectively. The formula for
calculating the UTRAN cell ID is as follows: UTRAN cell ID = RNC ID x
65536 + RNC cell ID. For details, see 3GPP TS 25.401.

RNC cell ID Indicates the RNC cell ID of an external UTRAN cell. It uniquely identifies a
cell within an RNC. The 28-bit UTRAN cell ID is comprised of the RNC cell ID
and the RNC ID that are represented by the least significant 16 bits and the most
significant 12 bits, respectively. The formula for calculating the UTRAN cell ID
is as follows: UTRAN cell ID = RNC ID x 65536 + RNC cell ID. For details,
see 3GPP TS 25.401.

Downlink UARFCN Indicates the DL UARFCN of the external UTRAN cell. The UARFCN range in
each FDD frequency band is shown as follows:
Band 1:
Normal UARFCNs: [10562-10838]
Special UARFCNs: none
Band 2:
Normal UARFCNs: [9662-9938]
Special UARFCNs: (412,437,462,487,512,537,562,587,612,637,662,687)
Band 3:
Normal UARFCNs: [1162-1513]
Special UARFCNs: none
Band 4:
Normal UARFCNs: [1537-1738]
Special UARFCNs: (1887, 1912, 1937, 1962, 1987, 2012, 2037, 2062, 2087)
Band 5:
Table 2 Related parameters

Parameter Description

Normal UARFCNs: [4357-4458]


Special UARFCNs: (1007, 1012, 1032, 1037, 1062, 1087)
Band 6:
Normal UARFCNs: [4387-4413]
Special UARFCNs: (1037, 1062)
Band 7:
Normal UARFCNs: [2237-2563]
Special UARFCNs: (2587, 2612, 2637, 2662, 2687, 2712, 2737, 2762, 2787,
2812, 2837, 2862, 2887, 2912)
Band 8:
Normal UARFCNs: [2937-3088]
Special UARFCNs: none
Band 9:
Normal UARFCNs: [9237-9387]
Special UARFCNs: none
The UARFCN range in each TDD frequency band is shown as follows:
Band 1:
Normal UARFCNs: [9500-9600] and [10050-10125]
Special UARFCNs: none
Band 2:
Normal UARFCNs: [9250-9550] and [9650-9950]
Special UARFCNs: none
Band 3:
Normal UARFCNs: [9550-9650]
Special UARFCNs: none
Band 4:
Normal UARFCNs: [12850-13100]
Special UARFCNs: (2112, 2137, 2162, 2187, 2212, 2237, 2262, 2287, 2312,
2337)
Band 5:
Normal UARFCNs: [11500-12000]
Special UARFCNs: none
Band 6:
Normal UARFCNs: [9400-9600]
Special UARFCNs: none
For details, see 3GPP TS 25.104 and 3GPP TS 25.105.

Uplink UARFCN Indicates whether to set the UL UARFCN for the external UTRAN cell. If the
configure indicator
Table 2 Related parameters

Parameter Description

value of this parameter is not specified, the default DL UARFCN is used. For an
UTRAN FDD cell, the way to calculate the default UL UARFCN varies
depending on whether the DL frequency is a normal or special one.
The default UL UARFCN is calculated as follows if the DL frequency is a
normal one:
Band 1: UL UARFCN = DL UARFCN - 950;
Band 2: UL UARFCN = DL UARFCN - 400;
Band 3: UL UARFCN = DL UARFCN - 475;
Band 4: UL UARFCN = DL UARFCN - 2000;
Band 5: UL UARFCN = DL UARFCN - 225;
Band 6: UL UARFCN = DL UARFCN - 225;
Band 7: UL UARFCN = DL UARFCN - 600;
Band 8: UL UARFCN = DL UARFCN - 225;
Band 9: UL UARFCN = DL UARFCN - 475;
The default UL UARFCN is calculated as follows if the DL frequency is a
special one:
Band 2: UL UARFCN = DL UARFCN - 400;
Band 4: UL UARFCN = DL UARFCN - 300;
Band 5: UL UARFCN = DL UARFCN - 225;
Band 6: UL UARFCN = DL UARFCN - 225;
Band 7: UL UARFCN = DL UARFCN - 225;
For a TDD UTRAN cell, the UL UARFCN is the same as the DL UARFCN. For
details, see 3GPP TS 25.104 and 3GPP TS 25.105.

Uplink UARFCN Indicates the UL UARFCN of the external UTRAN cell. The UARFCN range in
each FDD frequency band is shown as follows:
Band 1:
Normal UARFCNs: [9612-9888]
Special UARFCNs: none
Band 2:
Normal UARFCNs: [9262-9538]
Special UARFCNs: (12, 37, 62, 87, 112, 137, 162, 187, 212, 237, 262, 287)
Band 3:
Normal UARFCNs: [937-1288]
Special UARFCNs: none
Band 4:
Normal UARFCNs: [1312-1513]
Special UARFCNs: (1662, 1687, 1712, 1737, 1762, 1787, 1812, 1837, 1862)
Band 5:
Table 2 Related parameters

Parameter Description

Normal UARFCNs: [4132-4233]


Special UARFCNs: (782, 787, 807, 812, 837, 862)
Band 6:
Normal UARFCNs: [4162-4188]
Special UARFCNs: (812, 837)
Band 7:
Normal UARFCNs: [2012-2338]
Special UARFCNs: (2362, 2387, 2412, 2437, 2462, 2487, 2512, 2537, 2562,
2587, 2612, 2637, 2662, 2687)
Band 8:
Normal UARFCNs: [2712-2863]
Special UARFCNs: none
Band 9:
Normal UARFCNs: [8762-8912]
Special UARFCNs: none
The UARFCN range in each TDD frequency band is shown as follows:
Band 1:
Normal UARFCNs: [9500-9600] and [10050-10125]
Special UARFCNs: none
Band 2:
Normal UARFCNs: [9250-9550] and [9650-9950]
Special UARFCNs: none
Band 3:
Normal UARFCNs: [9550-9650]
Special UARFCNs: none
Band 4:
Normal UARFCNs: [12850-13100]
Special UARFCNs: (2112, 2137, 2162, 2187, 2212, 2237, 2262, 2287, 2312,
2337)
Band 5:
Normal UARFCNs: [11500-12000]
Special UARFCNs: none
Band 6:
Normal UARFCNs: [9400-9600]
Special UARFCNs: none
For details, see 3GPP TS 25.104 and 3GPP TS 25.105.

UTRAN cell type Indicates the duplex mode of the UTRAN cell.
indicator
Table 2 Related parameters

Parameter Description

Routing area code Indicates whether to set the routing area code (RAC) of the external UTRAN
configure indicator
cell. This parameter must be set to CFG(Configure) if the external UTRAN cell
supports packet switched (PS) services.

Routing area code Indicates the routing area code.

Primary scrambling Indicates the primary DL scrambles of the external UTRAN cell. For details, see
code
3GPP TS 25.331.

Location area code Indicates the LAC of the external UTRAN cell.

Cell name Indicates the name of the external UTRAN cell.

CS and PS handover Indicates whether the external UTRAN cell supports single radio voice call
indicator
continuity (SRVCC) for both CS and PS services. If this parameter is set to
BOOLEAN_FALSE(False), the external UTRAN cell does not support SRVCC
for both CS and PS services.

External UTRAN Cell Indicates slave frequency bands of an external UTRAN cell. If the working
Slave Band
frequency of an external UTRAN cell belongs to multiple frequency bands, the
downlink frequency in the frequency band of the highest priority is configured
based on UtranDlArfcn, and the downlink frequencies in other frequency bands
are configured based on this parameter. If there are multiple frequency bands of
different priorities, downlink frequencies in the frequency bands are configured
based on the priorities in descending order. The frequency band priorities of an
external UTRAN cell are determined based on the network planning of an
operator. It is recommended that the frequency band values are arranged in
ascending order. The frequency band with the minimum value is of the highest
priority, and the frequency band with the maximum value is of the lowest
priority.

Control Mode Indicates the control policy on ANR-related MOs, which can be defined by the
user or be based on the automatic neighbor relation (ANR) algorithm. When this
parameter is set to MANUAL_MODE, the ANR-related MOs can be modified
or removed by only the user. A failure message is displayed when the user adds
an existing MO. When this parameter is set to AUTO_MODE, the ANR-related
MOs can be modified or removed by the user or based on the ANR algorithm.
The MO removal is successful even if the MO does not exist. An MO can be
added both by the user and based on the ANR algorithm. If an existing MO is to
be added, the MO is modified when the user performs the addition, but it cannot
be added based on the ANR algorithm. The preceding control policy also applies
to the UtranExternalCellPlmn MO, which is a child MO of the
UtranExternalCell MO. When the ANR-related MOs are automatically added
based on the ANR algorithm, this parameter is set to AUTO_MODE by default.
Table 2 Related parameters

Parameter Description

When the ANR-related MOs are added by the user, this parameter can be set to
AUTO_MODE or MANUAL_MODE.

5.7.1.6.3.174 UtranExternalCellPlmn
+-NE
+-eNodeBFunction
+-UtranExternalCell
+-UtranExternalCellPlmn

Description

A UtranExternalCellPlmn MO consists of the parameters related to an additional PLMN ID for


an external UTRAN cell.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
UtranExternalCell

Relation with the UtranExternalCell MO:


- Before adding a UtranExternalCellPlmn MO, ensure that the associated
UtranExternalCell MO has been configured.
- A maximum of three UtranExternalCellPlmn MOs can be configured for each
UtranExternalCell MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

ADD Use this command to add an additional PLMN ID for an external UTRAN cell.
UTRANEXTERNALCEL
LPLMN

LST Use this command to list an additional PLMN ID for an external UTRAN cell.
UTRANEXTERNALCEL
LPLMN

RMV Use this command to remove an additional PLMN ID for an external UTRAN
UTRANEXTERNALCEL
LPLMN cell.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Mobile country code Indicates the mobile country code of the external UTRAN cell.
A PLMN ID is comprised of an MCC and an MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, if the MCC is 123 and the MNC is 45, then the PLMN ID is
12345.

Mobile network code Indicates the mobile network code of the external UTRAN cell.
A PLMN ID is comprised of an MCC and an MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, if the MCC is 123 and the MNC is 45, then the PLMN ID is
12345.

RNC ID Indicates the RNC ID of the external UTRAN cell. The 28-bit UTRAN cell ID
comprises the RNC cell ID and the RNC ID that are represented by the least
significant 16 bits and the most significant 12 bits, respectively. The formula for
calculating the UTRAN cell ID is as follows: UTRAN cell ID = RNC ID x
65536 + RNC cell ID. For details, see 3GPP TS 25.401.

RNC cell ID Indicates the RNC cell ID of an external UTRAN cell. It uniquely identifies a
cell within an RNC. The 28-bit UTRAN cell ID is comprised of the RNC cell ID
and the RNC ID that are represented by the least significant 16 bits and the most
Table 2 Related parameters

Parameter Description

significant 12 bits, respectively. The formula for calculating the UTRAN cell ID
is as follows: UTRAN cell ID = RNC ID x 65536 + RNC cell ID. For details,
see 3GPP TS 25.401.

Share mobile country Indicates the mobile country code of the external UTRAN cell that is shared
code
among multiple operators.
A PLMN ID is comprised of an MCC and an MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, if the MCC is 123 and the MNC is 45, then the PLMN ID is
12345.

Share mobile network Indicates the mobile network code of the external UTRAN cell that is shared
code
among multiple operators.
A PLMN ID is comprised of an MCC and an MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, if the MCC is 123 and the MNC is 45, then the PLMN ID is
12345.

5.7.1.6.3.175 UtranNCell
+-NE
+-eNodeBFunction
+-Cell
+-UtranNCell

Description

A UtranNCell MO consists of the parameters related to a neighboring UTRAN cell. It is used in


measurement control and cell reselection that is controlled by SIB6. For details, see 3GPP TS
36.331.

Effective Scenario

Immediately
Relations Between MOs

Possible parents:
Cell

Relation with the UtranExternalCell MO:


- Before adding a UtranNCell MO, ensure that the associated UtranExternalCell MO has
been configured.
- In all UtranNCell MOs of a local Cell MO, the combination of UtranDlArfcn and
PScrambCode in the UtranExternalCell MO corresponding to each UtranNCell MO must be
unique.
Relation with the UtranNFreq,UtranExternalCell MOs:
- UtranDlArfcn and UtranFddTddType in the UtranExternalCell MO associated with a
UtranNCell MO must have been configured in a UtranNFreq MO.
Relation with the Cell MO:
- A maximum of 128 UtranNCell MOs can be configured for each cell.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD UTRANNCELL Use this command to add the neighboring relation with a UTRAN cell.

DSP UTRANRIMINFO Use this command to query the status of the RAN Information Management
(RIM) function for neighboring UTRAN cells.

DSP Use this command to query the load information about neighboring UTRAN
UTRANRIMLOADINFO
cells, which are obtained through the RAN information management (RIM)
procedure.

LST UTRANNCELL Use this command to list the parameters of the neighboring relation with
UTRAN cell.

MOD UTRANNCELL Use this command to modify the neighboring relation with a UTRAN cell.

RMV UTRANNCELL Use this command to remove the neighboring relation with a UTRAN cell.

Related Parameters
Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the cell ID of the local cell. It uniquely identifies a cell within an
eNodeB.

Mobile country code Indicates the mobile country code of the neighboring UTRAN cell.
The PLMN consists of the MCC and the MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, MCC = 123, MNC = 45, PLMN = 12345.

Mobile network code Indicates the mobile network code of the neighboring UTRAN cell.
The PLMN consists of the MCC and the MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, MCC = 123, MNC = 45, PLMN = 12345.

RNC ID Indicates the RNC ID of the neighboring UTRAN cell. The 28-bit UTRAN cell
ID is comprised of the RNC cell ID and the RNC ID that are represented by the
least significant 16 bits and the most significant 12 bits, respectively. The
formula for calculating the UTRAN cell ID is as follows: UTRAN cell ID =
RNC ID x 65536 + RNC cell ID. For details, see 3GPP TS 25.401.

RNC cell ID Indicates the RNC cell ID of an external UTRAN cell. It uniquely identifies a
cell within an RNC. The 28-bit UTRAN cell ID is comprised of the RNC cell ID
and the RNC ID that are represented by the least significant 16 bits and the most
significant 12 bits, respectively. The formula for calculating the UTRAN cell ID
is as follows: UTRAN cell ID = RNC ID x 65536 + RNC cell ID. For details,
see 3GPP TS 25.401.

No handover indicator Indicates whether to allow handover of UEs to the neighboring cell that is
determined by the neighboring relation.

No remove indicator Indicates whether to permit or prohibit removal of the neighboring relationship
by ANR.

ANR flag Indicates whether this neighboring cell is automatically discovered by the ANR
algorithm.

Blind handover priority Indicates the priority of the neighboring cell during blind handovers. Blind
handover is a process in which the eNodeB instructs a UE to hand over to a
specified neighboring cell. There are 32 priorities altogether. The priority has a
Table 2 Related parameters

Parameter Description

positive correlation with the value of this parameter. Note that the value 0
indicates that blind handovers to the neighboring cell are not allowed.

Cell Measure Priority Indicates the priority of measurement on the neighboring UTRAN cell. The
eNodeB preferentially contains the information about a neighboring cell with
this priority set to HIGH_PRIORITY while delivering a measurement
configuration.

Local cell name Indicates the name of the local cell.

Neighbour cell name Indicates the name of the UTRAN neighboring cell.

Control Mode Indicates the control policy on ANR-related MOs, which can be defined by the
user or be based on the automatic neighbor relation (ANR) algorithm. When this
parameter is set to MANUAL_MODE, the ANR-related MOs can be modified
or removed by only the user. A failure message is displayed when the user adds
an existing MO. When this parameter is set to AUTO_MODE, the ANR-related
MOs can be modified or removed by the user or based on the ANR algorithm.
The MO removal is successful even if the MO does not exist. An MO can be
added both by the user and based on the ANR algorithm. If an existing MO is to
be added, the MO is modified when the user performs the addition, but it cannot
be added based on the ANR algorithm. When the ANR-related MOs are
automatically added based on the ANR algorithm, this parameter is set to
AUTO_MODE by default. When the ANR-related MOs are added by the user,
this parameter can be set to AUTO_MODE or MANUAL_MODE.

eNodeB ID Indicates the ID of the eNodeB, which uniquely identifies an eNodeB within a
PLMN.

Rim latest start time Indicates the time of the latest RIM request received by the neighboring
UTRAN cell.

RIM latest update time Indicates the latest updated time of the system information that the eNodeB
receives from the neighboring UTRAN cell through the RIM procedure.

cell load RIM latest Indicates the latest time that the eNodeB obtains the load information about the
update time
neighboring UTRAN cell through an RIM procedure.

Cell load Rim latest Indicates the latest time that the eNodeB initiates an RIM procedure to obtain
start time
the load information about the neighboring UTRAN cell.

UMTS cell load status Indicates the load status of the neighboring UTRAN cell, which is obtained by
the eNodeB through the latest RIM procedure.
5.7.1.6.3.176 UtranNFreq
+-NE
+-eNodeBFunction
+-Cell
+-UtranNFreq
+-UtranNFreqSCellOp[0~6]
+-UtranRanShare[0~4]

Description

A UtranNFreq MO consists of the parameters related to a neighboring UTRAN frequency. It is


used in measurement control for inter-RAT handover to UTRAN and also in SIB6-controlled cell
reselection to UTRAN. If no operator is configured to share the neighboring UTRAN frequency,
this frequency can be used by all operators of the current cell. If operators are configured to share
the neighboring UTRAN frequency, this frequency can be used only by the configured operators.
For details, see 3GPP TS 36.331.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
Cell

Possible children:
UtranNFreqSCellOp[0~6];UtranRanShare[0~4]

Relation with the UtranNCell,UtranExternalCell MOs:


- UtranDlArfcn and UtranFddTddType in the UtranExternalCell MO associated with a
UtranNCell MO must have been configured in a UtranNFreq MO.
Relation with the Cell MO:
- A maximum of 16 UtranNFreq MOs can be configured for each cell.
Relation with the EutranInterNFreq MO:
- If CellReselPriorityCfgInd in EutranInterNFreq MO and UtranNFreq MO is both set to
CFG, CellReselPriority cannot be set to a same value for each cell.
Relation with the CellResel MO:
- If CellReselPriorityCfgInd in UtranNFreq MO is set to CFG, CellReselPriority in
CellResel MO cannot be set same as CellReselPriority in UtranNFreq MO for each cell.
Relation with the Cdma2000BandClass MO:
- If CellReselPriorityCfgInd in UtranNFreq MO is set to CFG, and if
Cdma20001XrttCellReselInd in Cdma2000BandClass MO is set to CFG,
Cdma20001XrttCellReselPri in Cdma2000BandClass MO cannot be set same as
CellReselPriority in UtranNFreq MO for each cell, and if Cdma2000HrpdCellReselInd in
Cdma2000BandClass MO is set to CFG, Cdma2000HrpdCellReselPri in
Cdma2000BandClass MO cannot be set same as CellReselPriority in UtranNFreq MO for
each cell.
Relation with the GeranNfreqGroup MO:
- If CellReselPriorityCfgInd in UtranNFreq MO and GeranNfreqGroup MO is both set to
CFG, CellReselPriority cannot be set to a same value for each cell.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD UTRANNFREQ Use this command to add a neighboring UTRAN frequency.

LST UTRANNFREQ Use this command to list the neighboring UTRAN frequency information.

MOD UTRANNFREQ Use this command to modify the configuration of a neighboring UTRAN
frequency.

RMV UTRANNFREQ Use this command to remove a neighboring UTRAN frequency.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the cell ID of the local cell. It uniquely identifies a cell within an
eNodeB.
Table 2 Related parameters

Parameter Description

Downlink UARFCN Indicates the DL UARFCN of the neighboring cell on the UTRAN frequency.
The UARFCN range in each FDD frequency band is shown as follows:
Band 1:
Normal UARFCNs: [10562-10838]
Special UARFCNs: none
Band 2:
Normal UARFCNs: [9662-9938]
Special UARFCNs: (412,437,462,487,512,537,562,587,612,637,662,687)
Band 3:
Normal UARFCNs: [1162-1513]
Special UARFCNs: none
Band 4:
Normal UARFCNs: [1537-1738]
Special UARFCNs: (1887, 1912, 1937, 1962, 1987, 2012, 2037, 2062, 2087)
Band 5:
Normal UARFCNs: [4357-4458]
Special UARFCNs: (1007, 1012, 1032, 1037, 1062, 1087)
Band 6:
Normal UARFCNs: [4387-4413]
Special UARFCNs: (1037, 1062)
Band 7:
Normal UARFCNs: [2237-2563]
Special UARFCNs: (2587, 2612, 2637, 2662, 2687, 2712, 2737, 2762, 2787,
2812, 2837, 2862, 2887, 2912)
Band 8:
Normal UARFCNs: [2937-3088]
Special UARFCNs: none
Band 9:
Normal UARFCNs: [9237-9387]
Special UARFCNs: none
The UARFCN range in each TDD frequency band is shown as follows:
Band 1:
Normal UARFCNs: [9500-9600] and [10050-10125]
Special UARFCNs: none
Band 2:
Normal UARFCNs: [9250-9550] and [9650-9950]
Special UARFCNs: none
Band 3:
Table 2 Related parameters

Parameter Description

Normal UARFCNs: [9550-9650]


Special UARFCNs: none
Band 4:
Normal UARFCNs: [12850-13100]
Special UARFCNs: (2112, 2137, 2162, 2187, 2212, 2237, 2262, 2287, 2312,
2337)
Band 5:
Normal UARFCNs: [11500-12000]
Special UARFCNs: none
Band 6:
Normal UARFCNs: [9400-9600]
Special UARFCNs: none
For details, see 3GPP TS 25.104 and 3GPP TS 25.105.

UTRAN version Indicates the working mode supported by the UTRAN in the current UARFCN.

UTRAN cell type Indicates the TDD/FDD mode of the inter-RAT UTRAN.
indicator

Uplink UARFCN Indicates whether to set the UL UARFCN of the cell on the UTRAN frequency.
indicator
If the value of this parameter is not specified, the default UL UARFCN is used.
For an UTRAN FDD cell, the way to calculate the default UL UARFCN varies
depending on whether the DL frequency is a normal or special one.
The default UL UARFCN is calculated as follows if the DL frequency is a
normal one:
Band 1: UL UARFCN = DL UARFCN - 950;
Band 2: UL UARFCN = DL UARFCN - 400;
Band 3: UL UARFCN = DL UARFCN - 475;
Band 4: UL UARFCN = DL UARFCN - 2000;
Band 5: UL UARFCN = DL UARFCN - 225;
Band 6: UL UARFCN = DL UARFCN - 225;
Band 7: UL UARFCN = DL UARFCN - 600;
Band 8: UL UARFCN = DL UARFCN - 225;
Band 9: UL UARFCN = DL UARFCN - 475;
The default UL UARFCN is calculated as follows if the DL frequency is a
special one:
Band 2: UL UARFCN = DL UARFCN - 400;
Band 4: UL UARFCN = DL UARFCN - 300;
Band 5: UL UARFCN = DL UARFCN - 225;
Band 6: UL UARFCN = DL UARFCN - 225;
Table 2 Related parameters

Parameter Description

Band 7: UL UARFCN = DL UARFCN - 225;


For a TDD UTRAN cell, the UL UARFCN is the same as the DL UARFCN. For
details, see 3GPP TS 25.104 and 25.105.

Uplink UARFCN Indicates the UL UARFCN of the neighboring cell on the UTRAN frequency.
The UARFCN range in each FDD frequency band is shown as follows:
Band 1:
Normal UARFCNs: [9612-9888]
Special UARFCNs: none
Band 2:
Normal UARFCNs: [9262-9538]
Special UARFCNs: (12, 37, 62, 87, 112, 137, 162, 187, 212, 237, 262, 287)
Band 3:
Normal UARFCNs: [937-1288]
Special UARFCNs: none
Band 4:
Normal UARFCNs: [1312-1513]
Special UARFCNs: (1662, 1687, 1712, 1737, 1762, 1787, 1812, 1837, 1862)
Band 5:
Normal UARFCNs: [4132-4233]
Special UARFCNs: (782, 787, 807, 812, 837, 862)
Band 6:
Normal UARFCNs: [4162-4188]
Special UARFCNs: (812, 837)
Band 7:
Normal UARFCNs: [2012-2338]
Special UARFCNs: (2362, 2387, 2412, 2437, 2462, 2487, 2512, 2537, 2562,
2587, 2612, 2637, 2662, 2687)
Band 8:
Normal UARFCNs: [2712-2863]
Special UARFCNs: none
Band 9:
Normal UARFCNs: [8762-8912]
Special UARFCNs: none
The UARFCN range in each TDD frequency band is shown as follows:
Band 1:
Normal UARFCNs: [9500-9600] and [10050-10125]
Special UARFCNs: none
Table 2 Related parameters

Parameter Description

Band 2:
Normal UARFCNs: [9250-9550] and [9650-9950]
Special UARFCNs: none
Band 3:
Normal UARFCNs: [9550-9650]
Special UARFCNs: none
Band 4:
Normal UARFCNs: [12850-13100]
Special UARFCNs: (2112, 2137, 2162, 2187, 2212, 2237, 2262, 2287, 2312,
2337)
Band 5:
Normal UARFCNs: [11500-12000]
Special UARFCNs: none
Band 6:
Normal UARFCNs: [9400-9600]
Special UARFCNs: none
For details, see 3GPP TS 25.104 and 3GPP TS 25.105.

Reselection priority Indicates whether to set the priority of a cell assigned with the UARFCN used in
configure indicator
cell reselection to UTRAN.

Cell reselection priority Indicates the cell reselection priority of the neighboring UTRAN frequency. The
value 0 indicates the lowest priority. The UE decides whether to reselect a
neighboring cell on the UTRAN frequency based on the value of this parameter
and the absolute priority of the serving cell.
If the value of this parameter is larger than the absolute priority of the serving
cell, the UE starts measurements on neighboring cells on the UTRAN
frequency; then if the signal quality of some neighboring cells meets the related
conditions, the UE starts cell reselection.
If the value of this parameter is smaller than the absolute priority of the serving
cell, the UE starts the measurements only when the signal quality of the serving
cell is poor; then if the signal quality of some neighboring cells meets the related
conditions, the UE starts cell reselection. Frequencies used for different RATs
must be assigned different cell reselection priorities. For details, see 3GPP TS
36.331.

PMAX Indicates the maximum power that the UE can apply to transmission on the
UTRAN frequency. It is used in criteria S to calculate the compensated power.
For details, see 3GPP TS 25.104.

Frequency offset Indicates the frequency offset of the cell on the UTRAN frequency. It
Table 2 Related parameters

Parameter Description

determines the probability of triggering measurement reports for events B1 and


B2. For details, see 3GPP TS 36.331.

Minimum required Indicates the minimum quality level required for a cell on the UTRAN
quality level
frequency to become a candidate for reselection. This parameter is applied only
to reselection to UTRAN FDD cells. A neighboring cell on the UTRAN
frequency can become a candidate for reselection only when the signal quality
of the cell is better than the value of this parameter.

Minimum required RX Indicates the RX level required for a neighboring cell on the UTRAN frequency
level
to become a candidate for selection. It is included in criteria S and used in the
evaluation for cell selection. During the evaluation for cell reselection, the UE
performs the following calculation: Srxlev = Measured RSRP value of a
neighboring cell on the frequency - Value of this parameter - Compensated
power. If Srxlev for a neighboring cell is better than a threshold for a time-to-
trigger, reselection to the cell is started. For details, see 3GPP TS 25.304.

UTRAN high priority Indicates the minimum RX level required for a neighboring cell on the UTRAN
threshold
frequency to become a candidate for reselection if the priority of the frequency
is higher than that of the serving frequency. After measurements are started for
neighboring cells on the UTRAN frequency, the UE reselects to a neighboring
cell on the frequency only if the RX level of the cell is higher than the value
specified by this parameter for a time-to-trigger. For details, see 3GPP TS
36.331.

UTRAN lower priority Indicates the minimum RX level required for a neighboring cell on the UTRAN
threshold
frequency to become a candidate for reselection if the priority of the frequency
is lower than that of the serving frequency. After measurements are started for
neighboring cells on the UTRAN frequency, the UE reselects to a neighboring
cell on the frequency only if the RX level of the serving cell is lower than a
specified threshold and that of the cell is higher than the value specified by this
parameter for a time-to-trigger. For details, see 3GPP TS 36.331.

UTRAN high priority Indicates the RSRQ-based minimum RX level required for a neighboring cell on
RSRQ threshold
the frequency to become a candidate for reselection if the RSRQ-based priority
of the frequency is higher than that of the serving frequency.
After measurements are started for neighboring cells on the UTRAN frequency,
the UE reselects to a neighboring cell on the frequency only if the RSRQ-based
RX level of the cell is higher than the value specified by this parameter for a
time-to-trigger. For details, see 3GPP TS 36.331.

UTRAN low priority Indicates the RSRQ-based minimum RX level required for a neighboring cell on
RSRQ threshold
the frequency to become a candidate for reselection if the RSRQ-based priority
of the frequency is lower than that of the serving frequency.
Table 2 Related parameters

Parameter Description

After measurements are started for neighboring cells on the frequency, the UE
reselects to a cell on the frequency only if the RSRQ-based RX level of the
serving cell is lower than a specified threshold and that of the cell is higher than
the value specified by this parameter for a time-to-trigger. For details, see 3GPP
TS 36.331.

PS service priority Indicates the priority for the neighboring UTRAN frequency to carry PS
services. In coverage-based inter-RAT PS handovers, if
UtranFreqLayerMeasSwitch is turned on, the eNodeB determines the UTRAN
frequency to be delivered to a UE based on PS service priorities. The eNodeB
delivers the UTRAN frequency with the highest PS priority to the UE by
default.In blind handovers to UTRAN, the target cell for a blind handover is
selected based on PS service priorities. The cell on the UTRAN frequency with
the highest PS priority is selected by default.When this parameter is set to
Priority_0 for a UTRAN frequency, the UTRAN frequency is not included in PS
service priority arrangement.

CS service priority Indicates the priority for a neighboring UTRAN frequency to carry CS services.
In coverage-based inter-RAT SRVCC or CSFB to UTRAN, if
UtranFreqLayerMeasSwitch is turned on, the eNodeB determines the UTRAN
frequency to be delivered to a UE based on CS service priorities. The eNodeB
delivers the UTRAN frequency with the highest CS priority to the UE by
default.In blind handovers for CSFB to UTRAN, if UtranFreqLayerBlindSwitch
is turned on, the target cell for a blind handover is selected based on CS service
priorities. The cell on the UTRAN frequency with the highest CS priority is
selected by default.When this parameter is set to Priority_0 for a UTRAN
frequency, the UTRAN frequency is not included in CS service priority
arrangement.

Connect frequency Indicates the frequency priority based on which the eNodeB selects a target
priority
frequency for blind redirection or contains a frequency in a measurement
configuration. If a blind redirection is triggered and the target neighboring cell is
not specified, the eNodeB selects a target frequency based on this priority. If a
measurement configuration is to be delivered, the eNodeB preferentially delivers
a frequency with the highest priority. If this priority is set to 0 for a frequency,
this frequency is not selected as the target frequency for a blind redirection. A
larger value indicates a higher priority.

CS and PS mixed Indicates the priority for the neighboring UTRAN frequency to carry CS+PS
priority
combined services. In measurement-based CSFB to UTRAN, if
UtranCsfbSteeringSwitch and UtranFreqLayerMeasSwitch are turned on, the
eNodeB determines the UTRAN frequency to be delivered to a UE in
RRC_CONNECTED mode based on the CS+PS combined service priorities.
The eNodeB preferentially delivers the UTRAN frequency with the highest
Table 2 Related parameters

Parameter Description

CS+PS combined service priority to the UE. In blind CSFB to UTRAN, if


UtranCsfbSteeringSwitch and UtranFreqLayerBlindSwitch are turned on, the
target cell is selected based on the CS+PS combined service priorities. The cell
on the UTRAN frequency with the highest CS+PS combined service priority is
preferentially selected. If this parameter is set to Priority_0(Priority 0), the
UTRAN frequency is not included in CS+PS combined service priority
arrangement.

5.7.1.6.3.177 UtranNFreqSCellOp
+-NE
+-eNodeBFunction
+-Cell
+-UtranNFreq
+-UtranNFreqSCellOp

Description

The UtranNFreqSCellOp MO defines cell reselection dedicated priorities based on the PLMN of
the local cell for the UTRAN frequency.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
UtranNFreq

Relation with the CnOperator MO:


- CnOperatorID in a UtranNFreqSCellOp MO must have been set in the associated
CnOperator MO.
Relation with the
EutranNFreqSCellOp,GeranNFGroupSCellOp,Cdma2000BcSCellOp,EutranNFreqRanSh
are,UtranRanShare,GeranRanShare MOs:
- Cell reselection priorities based on operators of the local cell (which are specified in the
EutranNFreqSCellOp, UtranNFreqSCellOp, GeranNFGroupSCellOp, and
Cdma2000BcSCellOp MOs) cannot coexist with cell reselection priorities based on operators of
neighboring frequencies (which are specified in the EutranNFreqRanShare, UtranRanShare,
and GeranRanShare MOs).
Relation with the EutranNFreqSCellOp MO:
- Cell reselection priorities specified in the EutranNFreqSCellOp and UtranNFreqSCellOp
MOs for the same operator cannot be the same.
Relation with the GeranNFGroupSCellOp MO:
- Cell reselection priorities specified in the GeranNFGroupSCellOp and
UtranNFreqSCellOp MOs for the same operator cannot be the same.
Relation with the Cdma2000BcSCellOp MO:
- Cell reselection priorities specified in the UtranNFreqSCellOp and Cdma2000BcSCellOp
MOs for the same operator cannot be the same.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add an operator-specific configuration for the UTRAN
UTRANNFREQSCELL
OP frequency.

LST Use this command to list operator-specific configurations for the UTRAN
UTRANNFREQSCELL
OP frequency.

MOD Use this command to modify operator-specific configurations for the UTRAN
UTRANNFREQSCELL
OP frequency.

RMV Use this command to remove an operator-specific configuration for the UTRAN
UTRANNFREQSCELL
OP frequency.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

Local cell ID Indicates the cell ID of the local cell. It uniquely identifies a cell within an
eNodeB.

Downlink UARFCN Indicates the downlink UARFCN of the neighboring UTRAN frequency.

Cn operator ID Indicates the ID of the operator.

Cell reselection Indicates whether to configure a dedicated cell-reselection priority based on the
dedicated priority
configure indicator PLMN ID of the local cell for the UTRAN frequency.

Cell reselection Indicates the dedicated cell reselection priority for a UTRAN frequency based
dedicated priority
on the PLMN ID of the local cell. The value 0 indicates the lowest priority. If
the related SPID configuration is specified, set this priority to the one specified
in the SPID configuration. If no related SPID configuration is specified but this
parameter is set, the eNodeB delivers the cell reselection priorities of all PLMNs
supported by a UE by using the IE idleModeMobilityControlInfo in an RRC
Connection Release message to the UE. If no related SPID configuration is
specified and this parameter is not set, a UE uses the cell reselection priority of
the neighboring UTRAN frequency, which is broadcast in the system
information.

5.7.1.6.3.178 UtranRanShare
+-NE
+-eNodeBFunction
+-Cell
+-UtranNFreq
+-UtranRanShare

Description

A UtranRanShare MO consists of the parameters related to information about an operator that


shares a neighboring UTRAN frequency. In RAN sharing scenarios, operator-specific
neighboring UTRAN frequencies can be configured as required.

Effective Scenario

Immediately
Relations Between MOs

Possible parents:
UtranNFreq

Relation with the


EutranNFreqSCellOp,UtranNFreqSCellOp,GeranNFGroupSCellOp,Cdma2000BcSCellOp
,EutranNFreqRanShare,GeranRanShare MOs:
- Cell reselection priorities based on operators of the local cell (which are specified in the
EutranNFreqSCellOp, UtranNFreqSCellOp, GeranNFGroupSCellOp, and
Cdma2000BcSCellOp MOs) cannot coexist with cell reselection priorities based on operators of
neighboring frequencies (which are specified in the EutranNFreqRanShare, UtranRanShare,
and GeranRanShare MOs).
Relation with the UtranNFreq MO:
- A maximum of four UtranRanShare MOs can be configured for each UtranNFreq MO.
Relation with the GeranRanShare MO:
- If CellReselPriorityCfgInd in UtranRanShare MO and GeranRanShare MO is both set
to CFG, Mcc, Mnc and CellReselPriority can not set to a same value for each cell.
Relation with the EutranNFreqRanShare MO:
- If CellReselPriorityCfgInd in UtranRanShare MO and EutranNFreqRanShare MO is
both set to CFG, Mcc, Mnc and CellReselPriority can not set to a same value for each cell.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add information about an operator that shares a
UTRANRANSHARE
neighboring UTRAN frequency.

LST Use this command to list information about operators that share a neighboring
UTRANRANSHARE
UTRAN frequency.

MOD Use this command to modify information about an operator that shares a
UTRANRANSHARE
neighboring UTRAN frequency.

RMV Use this command to remove information about an operator that shares a
UTRANRANSHARE
neighboring UTRAN frequency.
Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Local cell ID Indicates the cell identity of the local cell. It uniquely identifies a cell within an
eNodeB.

Downlink UARFCN Indicates the DL UARFCN of the neighboring cell operating on the UTRAN
frequency. The UARFCN range in each FDD frequency band is shown as
follows:
Band 1:
Normal UARFCNs: [10562-10838]
Special UARFCNs: none
Band 2:
Normal UARFCNs: [9662-9938]
Special UARFCNs: (412, 437, 462, 487, 512, 537, 562, 587, 612, 637, 662, 687)
Band 3:
Normal UARFCNs: [1162-1513]
Special UARFCNs: none
Band 4:
Normal UARFCNs: [1537-1738]
Special UARFCNs: (1887, 1912, 1937, 1962, 1987, 2012, 2037, 2062, 2087)
Band 5:
Normal UARFCNs: [4357-4458]
Special UARFCNs: (1007, 1012, 1032, 1037, 1062, 1087)
Band 6:
Normal UARFCNs: [4387-4413]
Special UARFCNs: (1037, 1062)
Band 7:
Normal UARFCNs: [2237-2563]
Special UARFCNs: (2587, 2612, 2637, 2662, 2687, 2712, 2737, 2762, 2787,
2812, 2837, 2862, 2887, 2912)
Band 8:
Normal UARFCNs: [2937-3088]
Special UARFCNs: none
Band 9:
Normal UARFCNs: [9237-9387]
Special UARFCNs: none
The UARFCN range in each TDD frequency band is shown as follows:
Table 2 Related parameters

Parameter Description

Band 1:
Normal UARFCNs: [9500-9600] and [10050-10125]
Special UARFCNs: none
Band 2:
Normal UARFCNs: [9250-9550] and [9650-9950]
Special UARFCNs: none
Band 3:
Normal UARFCNs: [9550-9650]
Special UARFCNs: none
Band 4:
Normal UARFCNs: [12850-13100]
Special UARFCNs: (2112, 2137, 2162, 2187, 2212, 2237, 2262, 2287, 2312,
2337)
Band 5:
Normal UARFCNs: [11500-12000]
Special UARFCNs: none
Band 6:
Normal UARFCNs: [9400-9600]
Special UARFCNs: none
For details, see 3GPP TS 25.104 and 3GPP TS 25.105.

Mobile country code Indicates the mobile country code (MCC) of the neighboring UTRAN cell.
A public land mobile network (PLMN) ID is comprised of an MCC and a
mobile network code (MNC).
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, if the MCC is 123 and the MNC is 45, then the PLMN ID is
12345.

Mobile network code Indicates the mobile network code (MNC) of the neighboring UTRAN cell.
A public land mobile network (PLMN) ID is comprised of a mobile country
code (MCC) and an MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
For example, if the MCC is 123 and the MNC is 45, then the PLMN ID is
12345.

Cell reselection priority Indicates whether to configure the cell reselection priority of the operator that
configure indicator
shares the neighboring UTRAN frequency.
Table 2 Related parameters

Parameter Description

Cell reselection priority Indicates the cell reselection priority of the operator that shares the neighboring
UTRAN frequency. The value 0 indicates the lowest priority. If the related SPID
configuration is specified, set this priority to the one specified in the SPID
configuration. If no related SPID configuration is specified but this parameter is
set, the eNodeB delivers the cell reselection priorities of all PLMNs supported
by a UE by using the IE idleModeMobilityControlInfo in an RRC Connection
Release message to the UE. If no related SPID configuration is specified and
this parameter is not set, a UE uses the cell reselection priority of the
neighboring UTRAN frequency, which is broadcast in the system information.

5.7.1.6.3.179 VQMAlgo
+-NE
+-eNodeBFunction
+-VQMAlgo

Description

The VQMAlgo MO consists of the voice quality monitoring parameter, that is, the maximum UL
voice packet delay variation allowed on the Uu interface.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.


Table 1 Related MML commands

MML Command Function

LST VQMALGO Use this command to list voice quality monitoring (VQM) algorithm parameters.

MOD VQMALGO Use this command to modify voice quality monitoring (VQM) algorithm
parameters.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

UL Delay Jitter Indicates the maximum UL voice packet delay variation allowed on the Uu
interface. If the actual delay variation of a UL voice packet exceeds this limit,
this packet is regarded as lost during the evaluation of voice quality impact
(VQI). The delay variation is measured at the eNodeB PDCP layer.

5.7.1.6.3.180 X2
+-NE
+-eNodeBFunction
+-X2

Description

An X2 MO is used to configure transport resources for X2 interfaces. The configuration items


include the control-plane end point group ID, user-plane end point group ID, and the CN
operator that owns the X2 object.

Effective Scenario

Immediately

Relations Between MOs


Possible parents:
eNodeBFunction

Relation with the CnOperator MO:


- CnOperatorId in an X2 MO must have been configured in the associated CnOperator MO.
Relation with the EPGROUP MO:
- EPGROUP MO referenced by CpEpGroupId in an X2 MO must have been configured.
- EPGROUP MO referenced by CpEpGroupId in an X2 MO must have been configured.
And the SCTPHOST MO referenced by the EPGROUP MO must have been configured.
- EPGROUP MO referenced by CpEpGroupId in an X2 MO must have been configured.
And only one SCTPHOST MO referenced by the EPGROUP MO can be configured with an
IPv4 address.
- EPGROUP MO referenced by UpEpGroupId in an X2 MO must have been configured.
- EPGROUP MO referenced by UpEpGroupId in an X2 MO must have been configured.
And the USERPLANEHOST MO referenced by the EPGROUP MO must have been
configured.
- EPGROUP MO referenced by UpEpGroupId in an X2 MO must have been configured. At
most six USERPLANEHOST MOs referenced by the EPGROUP MO can be configured with
IPv4 addresses.
- EPGROUP MO referenced by CpEpGroupId in an X2 MO must have been configured.
And only one SCTPHOST MO referenced by the EPGROUP MO can be configured with an
IPv6 address.
- EPGROUP MO referenced by UpEpGroupId in an X2 MO must have been configured. At
most six USERPLANEHOST MOs referenced by the EPGROUP MO can be configured with
IPv6 addresses.
- In RAN sharing with dedicated carriers mode, the X2 MOs with different CnOperatorId
values cannot reference the EPGROUP MOs that contain theSCTPHOST MOs with the same
PN and IPv4 address.
- In RAN sharing with dedicated carriers mode, the X2 MOs with different CnOperatorId
values cannot reference the EPGROUP MOs that contain theSCTPHOST MOs with the same
PN and IPv6 address.
- In RAN sharing with dedicated carriers mode, the X2 MOs with different CnOperatorId
values cannot reference the EPGROUP MOs that contain theUSERPLANEHOST MOs with
the same PN and IPv4 address.
- In RAN sharing with dedicated carriers mode, the X2 MOs with different CnOperatorId
values cannot reference the EPGROUP MOs that contain theUSERPLANEHOST MOs with
the same PN and IPv6 address.
- The USERPLANEHOST MO in the EPGROUP MO referenced by the X2 MO cannot be
configured with an IPv4 address other than the DEVIP.
- The X2 MOs with the same CnOperatorId value cannot reference the EPGROUP MOs
that contain the SCTPHOST MOs in which the values of the SCTPHOSTID parameters are
different.
- The X2 MOs with the same CnOperatorId value cannot reference the EPGROUP MOs
that contain the USERPLANEHOST MOs in which the values of the UPHOSTID parameters
are different.
Relation with the S1e MO:
- CpEpGroupId in an X2 MO must be different from CpEpGroupId in any S1 MO.
- UpEpGroupId in an X2 MO must be different from UpEpGroupId in any S1 MO.
- CpEpGroupId in an X2 MO must be different from UpEpGroupId in any S1 MO.
- UpEpGroupId in an X2 MO must be different from CpEpGroupId in any S1 MO.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD X2 Use this command to add an X2 object.

DSP X2 Use this command to query the control-plane information about the X2 interface
under an X2 object.

LST X2 Use this command to list the X2 object information such as the X2 object ID,
CN operator ID, end point group config flag, control-plane end point group ID,
user-plane end point group ID, peer eNodeB release, and user label.

MOD X2 Use this command to modify the configuration of an X2 object.

RMV X2 Use this command to remove an X2 object.

Related Parameters

Table 2 describes the parameters related to this MO.


Table 2 Related parameters

Parameter Description

X2 ID Indicates the X2 object ID.

CN Operator ID Indicates the ID of the operator to which the X2 MO belongs.

Control Plane End Point Indicates the ID of the control-plane end point group used by the X2 object.
Group ID

User Plane End Point Indicates the ID of the user-plane end point group used by the X2 object.
Group ID

Target eNodeB Release Indicates the compliance protocol release of the neighboring eNodeBs to which
the local eNodeB are connected through the X2 interfaces managed by the X2
MO.

User Label Indicates the description of the X2 object.

End Point Group Config Indicates whether to configure the control-plane or user-plane end point group.
Flag

X2 Interface CP Bearer Indicates the status of the CP bearer for the X2 interface.
State

X2 Interface ID Indicates the X2 interface ID.

X2 Interface State Indicates the status of the X2 interface.

X2 Interface CP Bearer Indicates the ID of the CP bearer for the X2 interface.


ID

5.7.1.6.3.181 X2AutoSetupOperator
+-NE
+-eNodeBFunction
+-X2AutoSetupOperator

Description

An X2AutoSetupOperator MO defines the MCC and MNC of an operator. The MCC and MNC
constitute a public land mobile network (PLMN) ID, which uniquely identifies the operator.

Effective Scenario
Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add an operator that the target eNodeB supporting X2 self-
X2AUTOSETUPOPER
ATOR setup belongs to.

LST Use this command to list operator information that the target eNodeB supporting
X2AUTOSETUPOPER
ATOR X2 self-setup belongs to.

RMV Use this command to remove an operator that the target eNodeB supporting X2
X2AUTOSETUPOPER
ATOR self-setup belongs to.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Mobile country code Indicates the mobile country code (MCC) of an operator that the target eNodeB
supporting X2 self-setup belongs to.

Mobile network code Indicates the mobile network code (MNC) of an operator that the target eNodeB
supporting X2 self-setup belongs to. The value of this parameter is a string of
two or three characters, each of which must be a digit in the range of 0 to 9.

5.7.1.6.3.182 X2BlackWhiteList
+-NE
+-eNodeBFunction
+-X2BlackWhiteList

Description

An X2BlackWhiteList MO consists of the parameters for adding a neighboring eNodeB to the


X2 blacklist or whitelist. The blacklist or whitelist prohibits or allows configuration of X2
interfaces between the local eNodeB and neighboring eNodeBs, respectively.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD Use this command to add a neighboring eNodeB to the X2 blacklist or whitelist.
X2BLACKWHITELIST
If a neighboring eNodeB is added to the X2 blacklist, an X2 interface between
the local eNodeB and this neighboring eNodeB cannot be automatically set up
or the X2 interface set up between the local eNodeB and this neighboring
eNodeB is abnormal. If a neighboring eNodeB is added to the X2 whitelist, the
X2 interface between the local eNodeB and this neighboring eNodeB cannot be
automatically removed.

LST Use this command to query a neighboring eNodeB to the X2 blacklist or


X2BLACKWHITELIST
whitelist. If a neighboring eNodeB is added to the X2 blacklist, an X2 interface
between the local eNodeB and this neighboring eNodeB cannot be automatically
set up or the X2 interface set up between the local eNodeB and this neighboring
eNodeB is abnormal. If a neighboring eNodeB is added to the X2 whitelist, the
X2 interface between the local eNodeB and this neighboring eNodeB cannot be
automatically removed.

RMV Use this command to remove a neighboring eNodeB to the X2 blacklist or


X2BLACKWHITELIST
whitelist. If a neighboring eNodeB is added to the X2 blacklist, an X2 interface
between the local eNodeB and this neighboring eNodeB cannot be automatically
Table 1 Related MML commands

MML Command Function

set up or the X2 interface set up between the local eNodeB and this neighboring
eNodeB is abnormal. If a neighboring eNodeB is added to the X2 whitelist, the
X2 interface between the local eNodeB and this neighboring eNodeB cannot be
automatically removed.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

Mobile country code Indicates the mobile country code of the neighboring eNodeB to be added to the
list. The value of this parameter is a string of three characters, each of which
must be a digit in the range of 0 to 9.

Mobile network code Indicates the mobile network code of the neighboring eNodeB to be added to the
list. The value of this parameter is a string of two or three characters, each of
which must be a digit in the range of 0 to 9.

eNodeB ID Indicates the ID of the neighboring eNodeB to be added to the list.

X2 Black or White List Indicates whether the X2 list is a blacklist or whitelist. If a neighboring eNodeB
Type
is added to the X2 blacklist, an X2 interface between the local eNodeB and this
neighboring eNodeB cannot be automatically set up or the X2 interface set up
between the local eNodeB and this neighboring eNodeB is abnormal. If a
neighboring eNodeB is added to the X2 whitelist, the X2 interface between the
local eNodeB and this neighboring eNodeB cannot be automatically removed.

5.7.1.6.3.183 X2Interface
+-NE
+-eNodeBFunction
+-X2Interface

Description
An X2Interface MO consists of user-configured parameters related to an X2 interface between
the local eNodeB and a neighboring eNodeB. The parameters specify information about the X2
interface and the neighboring eNodeB, including the control port bearer used for the X2
interface, the operator to which the X2 interface belongs, and the ID of the neighboring eNodeB.

Effective Scenario

Immediately

Relations Between MOs

Possible parents:
eNodeBFunction

Relation with the X2Interface MO:


- S1CpBearerId in an S1Interface MO must be different from X2CpBearerId in any
X2Interface MO.
Relation with the CnOperator MO:
- CnOperatorId in an X2Interface MO must have been set in the associated CnOperator
MO.
Relation with the CPBEARER MO:
- X2CpBearerId in an X2Interface MO must have been set in the associated CPBEARER
MO, and must not have been set in the SAAL type.

Related MML Commands

Table 1 describes the MML commands related to this MO.

Table 1 Related MML commands

MML Command Function

ADD X2INTERFACE Use this command to add an X2 interface.

DSP X2INTERFACE Use this command to query the status of an X2 interface and the information
about the peer eNodeB. The information about the peer eNodeB includes the
eNodeB ID and its PLMN ID. If the status of an X2 interface is abnormal, the
execution result displays the information about the peer eNodeB in the last
normal connection with the local eNodeB.

MOD X2INTERFACE Use this command to modify an X2 interface.

RMV X2INTERFACE Use this command to remove an X2 interface.


Table 1 Related MML commands

MML Command Function

RST X2INTERFACE Use this command to reset an X2 interface.

Related Parameters

Table 2 describes the parameters related to this MO.

Table 2 Related parameters

Parameter Description

X2Interface ID Indicates the X2 interface ID.

X2 Interface CP Bearer Indicates the ID of the control port bearer for the X2 interface.
ID

CN Operator ID Indicates the ID of the operator that owns the X2 interface.

Target eNodeB release Indicates the protocol release with which the peer eNodeB complies.

Automatic removal flag Indicates whether the X2 interface can be automatically removed. This
parameter will be removed in later versions. In this version, the setting of this
parameter is still synchronized between the M2000 and the eNodeB, but it is no
longer used internally. Therefore, avoid using this parameter.

Control Mode Indicates the control mode of the X2 interface, which determines the control
policies of users and the SON function on the X2 interface. When it is set to
MANUAL_MODE, only users can control the X2 interface. When it is set to
AUTO_MODE, both users and the SON function can control the X2 interface.
When the SON function automatically sets up an X2 interface, this parameter is
set to AUTO_MODE by default. When users add or modify an X2 interface,
users can set this parameter to AUTO_MODE or MANUAL_MODE.

Auto Config Flag Indicates whether the X2 interface is created automatically or manually. This
parameter is set by the system. Users cannot modify the parameter setting. The
system sets this parameter to AUTO_CREATE when the X2 interface is created
automatically using the SON function and to MANUAL_CREATE when the X2
interface is created manually by using the CME or running an MML command.

Neighbor eNodeB ID Indicates the ID of the neighboring eNodeB to which the local eNodeB is
connected through the X2 interface. The combination of this parameter and
NbrEnbPlmnId uniquely identifies the neighboring eNodeB around the globe.
Table 2 Related parameters

Parameter Description

Neighbor eNodeB Indicates the PLMN ID of the neighboring eNodeB to which the local eNodeB is
PLMN ID
connected through the X2 interface.

X2Interface state Indicates the status of the X2 interface. If the status is normal, the X2 interface
has been successfully established. If the status is abnormal, the X2 interface
establishment fails.

X2Interface state Indicates the reason why the X2 interface is abnormal.


abnormal reason

Anda mungkin juga menyukai