Version: V3.12.10
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2013 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
II
III
Tables .............................................................................................................. I
IV
Intended Audience
This manual is intended for:
l Network planning engineers
l Network optimization engineers
l Field engineers
l System engineers
l Network operators
Chapter Summary
Related Documents
The following documentation is related to this manual:
ZXWR RNC (V3.12.10) Radio Network Controller Radio Parameter Reference
Complete Alternative
Complete Primary
Key
Key of MO
(A+B Indicates
(A+B Indicates That
Sheet Name MOC Name That the Complete
the Complete Primary
Alternative Key
Key Consists of A
Consists of A and
and B)
B)
1-1
Complete Alternative
Complete Primary
Key
Key of MO
(A+B Indicates
(A+B Indicates That
Sheet Name MOC Name That the Complete
the Complete Primary
Alternative Key
Key Consists of A
Consists of A and
and B)
B)
1-2
Complete Alternative
Complete Primary
Key
Key of MO
(A+B Indicates
(A+B Indicates That
Sheet Name MOC Name That the Complete
the Complete Primary
Alternative Key
Key Consists of A
Consists of A and
and B)
B)
1-3
Complete Alternative
Complete Primary
Key
Key of MO
(A+B Indicates
(A+B Indicates That
Sheet Name MOC Name That the Complete
the Complete Primary
Alternative Key
Key Consists of A
Consists of A and
and B)
B)
1-4
Complete Alternative
Complete Primary
Key
Key of MO
(A+B Indicates
(A+B Indicates That
Sheet Name MOC Name That the Complete
the Complete Primary
Alternative Key
Key Consists of A
Consists of A and
and B)
B)
1-5
Complete Alternative
Complete Primary
Key
Key of MO
(A+B Indicates
(A+B Indicates That
Sheet Name MOC Name That the Complete
the Complete Primary
Alternative Key
Key Consists of A
Consists of A and
and B)
B)
1-6
Complete Alternative
Complete Primary
Key
Key of MO
(A+B Indicates
(A+B Indicates That
Sheet Name MOC Name That the Complete
the Complete Primary
Alternative Key
Key Consists of A
Consists of A and
and B)
B)
1-7
Complete Alternative
Complete Primary
Key
Key of MO
(A+B Indicates
(A+B Indicates That
Sheet Name MOC Name That the Complete
the Complete Primary
Alternative Key
Key Consists of A
Consists of A and
and B)
B)
1-8
Complete Alternative
Complete Primary
Key
Key of MO
(A+B Indicates
(A+B Indicates That
Sheet Name MOC Name That the Complete
the Complete Primary
Alternative Key
Key Consists of A
Consists of A and
and B)
B)
1-9
Complete Alternative
Complete Primary
Key
Key of MO
(A+B Indicates
(A+B Indicates That
Sheet Name MOC Name That the Complete
the Complete Primary
Alternative Key
Key Consists of A
Consists of A and
and B)
B)
1-10
Complete Alternative
Complete Primary
Key
Key of MO
(A+B Indicates
(A+B Indicates That
Sheet Name MOC Name That the Complete
the Complete Primary
Alternative Key
Key Consists of A
Consists of A and
and B)
B)
1-11
Complete Alternative
Complete Primary
Key
Key of MO
(A+B Indicates
(A+B Indicates That
Sheet Name MOC Name That the Complete
the Complete Primary
Alternative Key
Key Consists of A
Consists of A and
and B)
B)
1-12
Complete Alternative
Complete Primary
Key
Key of MO
(A+B Indicates
(A+B Indicates That
Sheet Name MOC Name That the Complete
the Complete Primary
Alternative Key
Key Consists of A
Consists of A and
and B)
B)
1-13
Complete Alternative
Complete Primary
Key
Key of MO
(A+B Indicates
(A+B Indicates That
Sheet Name MOC Name That the Complete
the Complete Primary
Alternative Key
Key Consists of A
Consists of A and
and B)
B)
For the associations among ZXWR RNC radio resource managed objects, refer to the
Radio Managed Object Association section of ZXWR RNC (V3.12.10) Radio Network
Controller Radio Parameter Reference.
1-14
1-15
Luarfcn ULogicalRnc Uuarfcn Uuarfcn is larger than Luarfcn and these two
parameters should in the same frequency band.
If the value range of Luarfcn is [10562.10838,
24], the value range of the associated parameters
must be [10562, 10838].
If the value range of Luarfcn is [9662, 9938], 412,
437, 462, 487, 512, 537, 562, 587, 612, 637, 662
or 687, the value range of associated parameters
must be [9662, 9938], 412, 437, 462, 487, 512,
537, 562, 587, 612, 637, 662 or 687.
If the value range of Luarfcn is [1162, 1513], the
value range of the associated parameters must
be [1162, 1513].
If the value range of Luarfcn is [4357, 4458],
1007, 1012, 1032, 1037, 1062 or 1087, the value
range of associated parameters must be [4357,
4458], 1007, 1012, 1032, 1037, 1062 or 1087.
If the value range of Luarfcn is [2937, 3088], the
value range of the associated parameters must
be [2937, 3088].
If the value range of Luarfcn is [4387, 4413],
1037 or 1062, the value range of the associated
parameters must be [4387, 4413],1037 or 1062.
If the value range of Luarfcn is [1537, 1738]
, 1887 ,1912 ,1937 ,1962 ,1987 ,2012 ,2037
,2062 or 2087, the value range of associated
parameters must be [1537, 1738] ,1887 ,1912
,1937 ,1962 ,1987 ,2012 ,2037 ,2062 or 2087.
MCC, MNC rncLocalOff PlmnNum, The parameters in this table must exist in the
MCC[], MNC[] association table.
1-16
CsNullNri rncIuOff CsNri Except that the value of 0XFFFF is invalid, the
value of CsNullNri should not be equal to that of
CsNri configured in the rncIuOff table.
PsNullNri rncIuOff PsNri Except that the value of 0XFFFF is invalid, the
value of PsNullNri should not be equal to that of
PsNri configured in the rncIuOff table.
UlPsRateLmt- USubSrv MaxBitRate The corresponding uplink rate and downlink rate
LowC Direction must be available to the association table.
DlPsRateLmt-
LowC
UlPsRateLmt- USubSrv MaxBitRate The corresponding uplink rate and downlink rate
HighC Direction must be available to the association table.
DlPsRateLmt-
HighC
InitialRateUl USubSrv MaxBitRate The corresponding uplink rate and downlink rate
InitialRateDl Direction must be available to the association table.
1-17
NodebNo UUtran- NodebNo Parameters in the association table must exist in this
CellFDD table.
NodebNo R_NeInfo NeId For NEs of Node B type, if the value of NodebNo is
PlmnNum PlmnNum consistent with that of Neld, parameters in this table
MCC4RAN- NeType are valid.
Sharing[] PlmnIndex The value of MCC4RANSharing[]\MNC4RANShar-
MNC4RAN- ing[] must be consistent with that of MCC[]\MNC[].
Sharing[] MCC[]\MNC[] must be the valid MCC[]\MNC[] of
R_PlmnInfo MCC[] the corresponding parameter in the association
MNC[] table (in accordance with PlmnIndex to the index
of R_PlmnInfo in R_NeInfo) (MCC4RANShar-
ing[]\MNC4RANSharing[] are obtained from the same
NMS objects: IubLink and LogicIubLink.
MCC rncNeInfo PlmnNum MCC+MNC of the cnInfo's record must be selected from valid
MNC MCC[] MCC[i] + MCC[i] (i= [0, PlmnNum-1]) of the rncNeInfo's recor
MNC[] ds which NeType is RNC
MCC and rncLocRnc MCC and MNC Parameters in this table must exit in the association
MNC table.
1-18
1-19
1-20
URA, Self- UUtran- URA, CId URA and CId in the association table must be
PhyRncCInd, CellFDD available to this table, and SelfPhyRncCInd is
PhyCId true.
1-21
1-22
NhrThrUpTti1 UWhiteSrvPc NhrThrDownT- When the value of SrvType is the uplink service
0[] ti10[] subtype (an even number), three array nodes
of NhrThrUpTti10 and NhrThrDownTti10 (i :
from 0 to 2) must satisfy the following condition:
NhrThrUpTti10[i] >= NhrThrDownTti10[i].
NhrThrUpTti2 UWhiteSrvPc NhrThrDownT- When the value of SrvType is the uplink service
[] ti2[] subtype (an even number), three array nodes
of NhrThrUpTti2 and NhrThrDownTti2 (i: from
0 to 2) must satisfy the following condition:
NhrThrUpTti2[i] >= NhrThrDownTti2[i].
1-23
1-24
MCC and ULogical- MCC and MNC Parameters in this table must exit in the association
MNC Rnc table.
1-25
BasicPrio USch- BearerType During the record configuration, the records of all the
PriMapping value combinations that BasicPrio is [0, 15] and Bear-
erType is [0, 2] must be configured.
RateSeg QosSeg BPSegNum When the value of BasicPrio is from 0 to 15, the value
Direction DlRateAd- combination ([<=16kbps;(<16&<=64)kbps;(<64&<=1
BPSeg jLevNum 28)kbps;(<128&<=384)kbps;>384kbps]) of downlink
RateClass must be configured.
BasicPrio UBPriAc Null All values of BasicPrio must be configured in this table.
1-26
1-27
RptCrt Intra UIntraMea- MeasEvtNum Only when RptCrt is 1 (event report), the associated
sProfile parameter is valid.
MeaEvtId[]
Hysteresis[]
TrigTime[]
1-28
RptCrt UIntraMea- PrdRptAmount Only when RptCrt is 2 (period report), the associated
sProfile parameter is valid.
PrdRptInterval
RptCrt UIntraMea- RptRange[] Only when RptCrt is 1 (event report) and MeaEvtId is
MeaEvtId[] sProfile 1a/1b, the associated parameter is valid.
RptCrt UIntraMea- W[] Only when RptCrt is 1 (event report) and MeaEvtId is
MeaEvtId[] sProfile 1a/1b, the associated parameter is valid.
RptCrt UIntraMea- ThreshUsed- Only when RptCrt is 1 (event report) and MeaEvtId is
MeaEvtId[] sProfile Freq[] 1e/1f, the associated parameter is valid. Moreover,
MeasQuan- the value range must meet the following conditions:
tity MeasQuantity is CPICHRSCP and ThreshUsedFreq
is (-115~25) .
MeasQuantity is CPICH Ec/No and ThreshUsedFreq
is (-24~0)dB.
MeasQuantity is Pathloss and ThreshUsedFreq is
(30~165)dB.
RptCrt UIntraMea- RptDeactThr[] Only when RptCrt is 1 (event report) and MeaEvtId is
MeaEvtId[] sProfile 1a, the associated parameter is valid.
RptCrt UIntraMea- RplcActThr[] Only when RptCrt is 1 (event report) and MeaEvtId is
MeaEvtId[] sProfile 1c/1J, the associated parameter is valid. Moreover,
JRplcActThr must be 0, 1, 2, 3 and 4 when MeaEvtId
is 1.
RptCrt UIntraMea- EvtRptAmount[] Only when RptCrt is 1 (event report) and MeaEvtId is
MeaEvtId[] sProfile 1a/1b/1c/1j, the associated parameter is valid.
RptCrt UIntraMea- EvtRptInterval[] Only when RptCrt is 1 (event report) and MeaEvtId is
MeaEvtId[] sProfile 1a/1b/1c/1j, the associated parameter is valid.
TrfCatIn- UUtran- TrfCatIntraMIdx The values of parameters in CIntra must exist in this
traMIdx CellFDD table
Evt- UIntraMea- In- The values of parameters in CIntra must exist in this
MeasEcNo sProfile traMeasCfgNo table
Evt-
MeasRSCP
Prd-
MeasEcNo
Prd-
MeasRSCP
EvtMeasD-
ctEcNo
1-29
EvtMeasD-
ctRSCP
1-30
Inter- UInterMea- InterMeasCfg- Each value of the associated field must correspond
MeasCfgNo sProfile Note to each record.
1-31
1-32
RptCrt UInterMea- PrdRptAmount Only when RptCrt is 3 (Periodical Reporting), the as-
sProfile PrdRptInterval sociated field is valid.
Evt- UInterMea- Inter- The values of parameters in this table must be in Inter
MeasEcNo sProfile MeasCfgNo
Evt-
MeasRSCP
Prd-
MeasEcNo
Prd-
MeasRSCP
EvtMeasEc-
No2
EvtMeasR-
SCP2
1-33
EvtMeasEc-
No3
EvtMeasR-
SCP3
Prd- UInterMea- InterMeasCfg- The associated parameters must be 0(UE Period Re-
MeasEcNo sProfile Note port Parameters for CPICH Ec/No)
Prd- UInterMea- InterMeasCfg- The associated parameters must be 4(UE Period Re-
MeasRSCP sProfile Note port Parameters for CPICH RSCP)
1-34
1-35
InterRatCfgNo URatMeasProfile EvtMeasEcNo The values of associated parameters in CRat must be in this table
EvtMeasRSCP
PrdMeasEcNo
PrdMeasRSCP
EvtMeasEcNo2
EvtMeasRSCP2
InterRatCfgNo URatMeasProfile InterRatCfgNote For each value of InterRatCfgNote, there must be at least one corresponding record to
be configured
InterRatCfgNote URatMeasProfile OwOMMeasQuantity When InterRatCfgNote is 0(Period Report Parameters for Own System CPICH Ec/No),
RptCrt OwOMMeasQuantity must be 0(CPICH Ec/No) and RptCrt must be 2(Periodical
Reporting Criteria)
When InterRatCfgNote is 2(UE Event Report Parameters for Own System CPICH
1-36
RptCrt URatMeasProfile EventNum Only when RptCrt is 1(Inter-RAT Event Reporting Criteria), associated parameters are
EventId[] valid
Thresh[]
W[]
ThreshSys[]
Hysteresis[]
TrigTime[]
RptCrt URatMeasProfile Thresh[] Only when RptCrt is 1(Inter-RAT Event Reporting Criteria) and EventId [i] (i= [1,
EventId[] EventNum]) is 0(3a), associated parameters are valid
OwOMMeasQuantity And when OwOMMeasQuantity is 1(CPICH RSCP), the value range of Thresh is [-115,
-25] dBm; when OwOMMeasQuantity is 0(CPICH Ec/No), the value range of Thresh
is [-24, 0] dB
1-37
RptCrt URatMeasProfile W[] Only when RptCrt is 1(Inter-RAT Event Reporting Criteria) and EventId [i]( i=[1,
EventId[] EventNum]) is 0(3a), associated parameters are valid
RptCrt URatMeasProfile ThreshSys[] Only when RptCrt is 1(Inter-RAT Event Reporting Criteria) and EventId [i]( i=[1,
EventId[] EventNum]) is 0(3a)/1(3b)/2(3c), associated parameters are valid
TrfCatRatMIdx UUtranCellFDD TrfCatRatMIdx The associated parameters in this table must be in UtranCell
ZTE Proprietary and Confidential
EvtMeasEcNo URatMeasProfile InterRatCfgNo The associated parameters in this table must be in UtranCell
EvtMeasRSCP
PrdMeasEcNo
Chapter 1 Relationships
PrdMeasRSCP
EvtMeasEcNo2
EvtMeasRSCP2
ZXWR RNC Radio Parameter Constraints Reference
SJ-20121213161606-014|2013-01-25 (R1.0)
EvtMeasEcNo URatMeasProfile TrfCategory When TrfCategory is 0xff, PrdMeasEcNo and PrdMeasRSCP is valid, EvtMeasEcNo,
EvtMeasRSCP EvtMeasRSCP, EvtMeasEcNo2 and EvtMeasRSCP2 are invalid
PrdMeasEcNo When TrfCategory is not 0xff, PrdMeasEcNo and PrdMeasRSCP is invalid, EvtMeasEcNo
PrdMeasRSCP , EvtMeasRSCP, EvtMeasEcNo2 and EvtMeasRSCP are valid
EvtMeasEcNo2
EvtMeasRSCP2
PrdMeasEcNo URatMeasProfile InterRatCfgNote The associated parameters in Rat must be 0(Period Report Parameters for Own System
CPICH Ec/No)
EvtMeasEcNo URatMeasProfile InterRatCfgNote The associated parameters in Rat must be 2(UE Event Report Parameters for Own System
CPICH Ec/No)
PrdMeasRSCP URatMeasProfile InterRatCfgNote The associated parameters in Rat must be 3(Period Report Parameters for Own System
CPICH RSCP)
1-38
EvtMeasRSCP URatMeasProfile InterRatCfgNote The associated parameters in Rat must be 5(UE Event Report Parameters for Own System
CPICH RSCP)
TrfCategory URatMeasProfile TrfCatRatMIdx For one TrfCatRatMIdx, records corresponding to all values of TrfCategory must be con-
figured in CRat
EvtMeasEcNo2 URatMeasProfile InterRatCfgNote The associated parameters in the association table must be 6 (UE Event Report Parame-
ZTE Proprietary and Confidential
EvtMeasRSCP2 URatMeasProfile InterRatCfgNote The associated parameters in the association table must be 7 (UE Event Report Parame-
ters for Own System CPICH RSCP (EUTRAN FDD)).
Chapter 1 Relationships
SrvType USubSrv MaxRe- Only when SrvType is an even number and SrvInd is
SrvInd transEdch 0 (non-MBMS), the associated parameter is valid.
SrvType USubSrv PtmRlsPerm Only when SrvInd is 1 (MBMS), the associated param-
SrvInd eter is valid.
1-39
1-40
MaxBitRate ULogical- InitialRateUl InitialRateUl must have the corresponding uplink and
Direction Rnc downlink matching rate in this table.
DtxDrxCon- UDtxDrx DtxDrxCon- Parameters in this table must exit in the association
figIdx figIdx table.
DtxDrxCon- USubSrv DtxDrxConfigIdx The parameter in the SrvPhy has existed in rncDtxDrx
figIdx
DtxCyc2Tti10 UHspa CqiCycle DtxCyc2Tti10 and DtxCyc2Tti2 must be integral times of all el-
DtxCyc2Tti2 UCommEdch ement of CqiCycle[3] divided by two or quotient of all element
of CqiCycle[3] divided by two
DtxCyc1Tti2 UDtxDrx DtxCyc2Tti2 The DtxCyc2Tti2 under the same DtxDrxConfigIdx must be
DpcchBurst1 integral times of DtxCyc1Tti2
MacDtxCycTti2 The DpcchBurst1 under the same DtxDrxConfigIdx must not
DrxCycle be larger than DtxCyc1Tti2
DtxCyc1Tti2 under the same DtxDrxConfigIdx must be
integral times of MacDtxCycTti2 or quotient of MacDtxCycTti2
DrxCycle under the same DtxDrxConfigIdx must be integral
times of DtxCyc1Tti2 or quotient of DtxCyc1Tti2
DtxCyc1Tti10 UDtxDrx DtxCyc2Tti10 The DtxCyc2Tti10 under the same DtxDrxConfigIdx must be
DpcchBurst1 integral times of DtxCyc1Tti10
MacDtxCycTti10 The DpcchBurst1 under the same DtxDrxConfigIdx must not
DrxCycle be larger than DtxCyc1DtxCyc1Tti10
DtxCyc1Tti10 under the same DtxDrxConfigIdx must
be integral times of MacDtxCycTti10 or quotient of
MacDtxCycTti10
DrxCycle under the same DtxDrxConfigIdx must be integral
times of DtxCyc1Tti10 or quotient of DtxCyc1Tti10
1-41
DtxCyc2Tti2 UDtxDrx DtxCyc1Tti2 The DtxCyc2Tti2 under the same DtxDrxConfigIdx must be
DpcchBurst2 integral times of DtxCyc1Tti2
The DpcchBurst2 under the same DtxDrxConfigIdx must not
be larger than DtxCyc2Tti2
DtxCyc2Tti10 UDtxDrx DpcchBurst2 The DtxCyc2Tti10 under the same DtxDrxConfigIdx must be
DtxCyc1Tti10 integral times of DtxCyc1Tti10
The DpcchBurst2 under the same DtxDrxConfigIdx must be
not larger than DtxCyc2Tti10
1-42
DivPcIndex(Target In- UUtranCellFDD DivPcIndex(Source Index) Before the set of records with one DivPcIndex in DivPc is deleted, it must be ensured that
dex) there is no utrallCell's record which quotes the DivPcIndex. Otherwise, this set of records
with the DivPcIndex in DivPc is not allowed to delete entirely, at least a record with the
DivPcIndex in DivPc must exist
SrvType(Source In- USubSrv SrvType(Target Index) There must be a record with corresponding SrvType in SubSrv
dex)
SrvType USrvDivPc DpchPO1 Only when the value of SrvType is odd, the associated parameters are valid
DpchPO2
DpchPO3
SrvType USrvDivPc MinDlDpchPwr Only when the value of SrvType is odd, the associated parameters are valid. And the
MaxDlDpchPwr following resctriction must be comply with :
MaxDlDpchPwr[i] > MinDlDpchPwr[i], i=0..8
1-43
SrvType USrvDivPc DpcchPilotEbN0 Only when the value of SrvType is even, the associated parameters are valid
MaxUlDpchPwr
SrvType USrvDivPc ULMaxSIR Only when the value of SrvType is even, the associated parameters are valid.And the
ULInitSIR following restriction must be comply with :
ULMinSIR ULMaxSIR[i] >ULInitSIR[i] >ULMinSIR[i], i=0..8
ZTE Proprietary and Confidential
SrvType USrvDivPc EagchPOTti2 Only when the value of SrvType is odd, the associated parameters are valid
EagchPOTti10
ErgchPOTti2
Chapter 1 Relationships
ErgchPOTti10
EhichPOTti2
EhichPOTti10
PwrForSglCell USubSrv SrvType Only when SrvType is an odd number and in the association table the MbmsInd value is
PwrForHalfIsd MbmsInd 1(MBMS), then the parameter in this table is valid
initBlerSIR[] USrvDivPc ulMinSIR[] Only when the value of SrvType is even, ulMinSIR[i] <=initBlerSIR[i] +initSirAdd[i] <=ul-
initSirAdd[] ulMaxSIR[] MaxSIR[i] (i=0..8)
1-44
ZTE Proprietary and Confidential
Chapter 1 Relationships
URA UUtranRe- URA Parameters in this table must be available to the as-
AdjPhyCId gArea SelfPhyRnc- sociation table.
CInd
PhyCId
AdjPhyCId UUtranRe- SelfPhyRnc- If the adjacent cell in the association table is not a cell
lation CInd controlled by this RNC(SelfPhyRncCInd is False), the
PhyCId associated parameters must exist in this table.
MCC[] rncNeInfo MCC[] MCC+MNC+RncId in this table does not exist in the
MNC[] MNC[] MCC[i]+MNC[i]+NeId[i] record whose ANI is 0 in the
RncId NeId rncNeInfo table.
ANI
1-45
AnteType UExternal- OffsetAngle Only when AnteType is 1(Beam Antenna), the associ-
RncFunc- InnerAngle ated parameter is valid.
tionD
1-46
1-47
AdjPhyGsmCId UGsmRelation NPhyGsmCId Before the record of externalGsmCell is deleted, it must ensure that there is no gsmRe-
lation's record which quotes the MCC+MNC+LAC+CI. Otherwise, the record of external-
GsmCell is not allowed to delete
Bandindicator UExternalGsmCell BCCHARFCN When Bandindicator takes value of 0(DCS 1800 Band Used), the value range of
BCCHARFCN is [512, 885]
When Bandindicator takes value of 1(PCS 1900 Band Used), the value range of
BCCHARFCN is [512, 812]
When Bandindicator takes value of 2(GSM 900 Band Used), the value range of
BCCHARFCN is [0, 124] and [955, 1023]
When Bandindicator takes value of 3(GSM 450 Band Used), the value range of
BCCHARFCN is [259, 293]
When Bandindicator takes value of 4(GSM 480 Band Used), the value range of
1-48
QrxLevMinSib11 UExternalGsmCell DtQrxLvMnSib11Pr If the value of QrxLevMinSib11 is not 0(-115dBm), DtQrxLvMnSib11Pr must be 0(False)
ZTE Proprietary and Confidential
QrxLevMinSib12 UExternalGsmCell DtQrxLvMnSib12Pr If the value of QrxLevMinSib12 is not 0(-115dBm), DtQrxLvMnSib12Pr must be 0(False)
GeranCellInd UExternalGsmCell RAC Only when GeranCellInd is 1(GERAN Cell), RAC is valid
MCC[i], MNC[i], LAC UExternalGsmCell MCC[i], MNC[i], LAC and CI MCC+MNC+LAC+CI is unique in the table
and CI
MNCBcdCodeLen[] UExternalGsmCell MNC[] When MNCBcdCodeLen is 2, the values of MNC[] must be from 0 to 99
Chapter 1 Relationships
PhyEutran- UExternalE- ENodeBId When ENodeBIds are the same, PhyEutranCId must
CId NBFunction be different.
1-49
1-50
1-51
1-52
NEutranCId UExter- EutranCId The ID of the corresponding cell must exist in the
nalENBFunc- corresponding parameter of the association table.
tion
CId UUtran- CId The ID of the corresponding cell must exist in the
CellFDD corresponding parameter of the association table.
Cid UUtran- Cid Parameters in the association table must exit in this
CellFDD table.
URA and UUtranRe- URA Parameters in this table must exist in the association
Cid gArea SelfPhyRnc- table. Q and SelfPhyRncCInd are TRUE.
CInd
PhyCId
1-53
NodebNo UIubLink NodebNo Parameters in this table must exit in the association
table.
NodebNo+ NdbAlc NodebNo+Mo- The relationship between NodebNo and Module in this
Module dule table must be consistent with that in the association
table.
UseOfHCS UCelSel HcsSrvCelInfo- If UseOfHCS is Not Used, the value of associated pa-
Pre rameters in the association table must be FALSE.
SIB12Ind SysMC Sib11orSib12 When SIB12Ind of the corresponding cell in this table
is TRUE, the record related to SIB12 must exist in the
association table.
TrfPcIndex UTrfPc TrfPcIndex Parameters in this table must exit in the association
table.
DivPcIndex USrvDivPc DivPcIndex Parameters in this table must exit in the association
table.
TrfCatIn- UIntraMea- TrfCatIntraMIdx Parameters in this table must exit in the association
traMIdx sProfile table.
TrfCatInter- UInterMea- TrfCatInterMIdx Parameters in this table must exit in the association
MIdx sProfile table.
TrfCatRat- URatMea- TrfCatRatMIdx Parameters in this table must exit in the association
MIdx sProfile table.
SchPriIndex USch- SchPriIndex Parameters in this table must exit in the association
MCC[] PriMapping MCC table.
MNC[] MNC
LdCtlPriIn- UApp- AppPriIndex Parameters in this table must exit in the association
dex PriMapping MCC table.
MCC[] MNC
MNC[]
CgtCtlPriIn- UApp- AppPriIndex Parameters in this table must exit in the association
dex PriMapping MCC table.
MCC[] MNC
MNC[]
BPriAcIn- UBPriAc BPriAcIndex Parameters in this table must exit in the association
dex MCC table.
MCC[] MNC
MNC[]
1-54
Cid UUtranRe- CId Parameters in the association table must exit in this
lation table.
UGsmRela-
tiongsmRe-
lation
UcelSel
UScpich
USccpch
UPich
UMich
UPrach
UAich
UFach
UPch
CHsdpa
ULdCtrl
UPlBal
UNbCom-
Meas
UUeInt-
MeasProfile
UTrvMea-
sProfile
UEFach
UEUtran-
Relation
UCMbms
1-55
AnteType UUtran- OffsetAngle Only when AnteType is 1 (Beam Antenna), the asso-
CellFDD InnerAngle ciated parameter is valid.
SACB UUtran- SACBPre The associated parameter is valid only when SACBPre
CellFDD LAC is 1 (True). The following restriction must be satis-
externalU- SACBPre fied: In the same PLMN, one LAC+SACB in PLMN
tranCell LAC SAC can only correspond to one cell. That is to say, in the
same PLMN, there is only one record corresponding
to LAC+ SACBPre+ SACB in this table. Moreover, in
the same PLMN, there is no record corresponding to
LAC+ SACBPre +SACB in the externalUtranCell table.
SIB6Ind UUtran- PccpchInf- The associated parameters are valid only when
CellFDD Sib6Pre SIB6Ind is True. When SIB6Ind is False, Prach-
PrachSib6Pre Sib6Pre must be FALSE.
Cid RcAsData CId When the record in this table is deleted, the cor-
responding record in the RcAsData table must be
deleted. This restriction takes effect on RCP.
1-56
HspaSpt- UUtran- hsdStat The associated parameters are valid only when
Meth CellFDD HspaSptMeth is 1 (Support HSDPA and DCH), 2
(Support HSDPA only), 3 (Support HSUPA, HSDPA
and DCH) or 4 (Support HSUPA and HSDPA).
HspaSpt- UUtran- hsuStat The parameters in the association table are valid only
Meth CellFDD when HspaSptMeth is 3 (Support HSUPA, HSDPA and
DCH) or 4 (Support HSUPA and HSDPA).
MAXDlTx- UIubLink NodeBType If, in the nodeB table, the NodeBType is PicoNodeB,
Pwr the MAXDlTxPwr background value can not be larger
than 24dBm in this table.
MbmsSupt- UUtran- mbmsStat Only when MbmsSuptInd is 1 (Support MBMS and not
Ind CellFDD MBMS) or 2 (Only Support MBMS), mbmsStat is valid.
MbmsSupt- UCMbms All parameters Only when MbmsSuptInd in this table is 1 (Support
Ind of the associa- MBMS and not MBMS) or 2 (Only Support MBMS),
tion table the associated parameters in the association table is
valid.
CId UIubLink NodebNo If NodebType of the NodeB in the R8Nodeb table cor-
NodebNo NodebType responding to this cell is 2(Home NodeB), this NodeB
has this cell only. That is to say, one Home NodeB
supports one cell only.
1-57
PlmnNum rncNeInfo PlmnNum The parameters in this table must exist in the
MCC[] MCC[] Plmn+MCC[]+MNC+RncId[] array corresponding to
MNC[] MNC[] the record (ANI=0) in the R5NeInfo table.
RncId[] NeId[]
Common- UUtran- CId For one physical cell (one piece of local table record),
PlmnInd[] CellFDD there is only one PLMN whose CommonPlmnInd is
True, and this PLMN is located as the first element in
the PLMN arrays.
AppCfgIn- UDpiApp- SystemMode AppCfgIndex defined in this table must exist in the Sys-
dex SrvPri AppCfgIndex temMode = 64 (UMTS) record in UDpiAppSrvPri.
1-58
PagingLo- UUtran- CSDsarSwh[] When not all parameters corresponding to the PLMN
caBarSwh[] CellFDD PSDsarSwh[] are 0, PagingLocaBarSwh is valid.
R99PwrPer- UUtran- PlmnNum The sum of R99PwrPercent in all valid PLMNs must
cent[] CellFDD be 100%.
PlmnCod- UUtran- PlmnNum The sum of PlmnCodShaRat in all valid PLMNs must
ShaRat[] CellFDD be 100%.
Cs64Switch UUtranRe- CId If the same cell has multiple adjacent cells that
lation NCToSelf- are the intra-cells (NCToSelfPhyRnc is 1) of the
PhyRnc RNC and ShareCover is 1, Cs64Switch of the cell
NPhyCId corresponding to NPhyCId must be the same. This
restrictions are guaranteed by the configuration
engineer.
RtMaxUl- USubSrv MaxBitRate The corresponding uplink matching rate must exist in
RateDch Direction the association table of RtMaxUlRateDch.
RtMaxUl- USubSrv MaxBitRate The corresponding uplink matching rate must exist in
RateDch Direction the association table of RtMaxUlRateDch.
1-59
NrtMaxRa- USubSrv MaxBitRate The corresponding uplink matching rate must exist in
teEdch Direction the association table of NrtMaxRateEdch.
DlCon- USubSrv MaxBitRate The corresponding downlink matching rate must exist
troledMBR Direction in the association table of DlControledMBR.
UlCon- USubSrv MaxBitRate The corresponding uplink matching rate must exist in
troledMBR Direction the association table of UlControledMBR.
MimoPilot- UUtran- CId When MimoSuptInd of this cell is set to Support and
Mode CId CellFDD SchTstdInd MimoPilotMode is "P-CPICH + S-CPICH", SchTstdInd
in the UutranCellFDD table is set to "Un-activated".
ULEFACH- UCHspa Dedi- The key parameters are valid only when
Support ComEAGCH- ULEFACHSupport is "1: Yes".
Swi
CellBarAc- UUtran- CellBar- The key parameters are valid only when
Swh CellFDD PollingSwh CellBarAcSwh is not 0.
CellBar- UUtran- CellBarAcNum The key parameters are valid only when
PollingSwh CellFDD CellBarPollingSwh is 1 (poll).
1-60
DlThrputS- UUtran- DlCacSwitch The value of DlThrputSwitch can be 1 only when Dl-
witch CellFDD CacSwitch is 1.
DefSib- UUtran- IntraRptQSib3 The key parameters are valid only when
SuptSwch CellFDD DefSibSuptSwch is 1 (Open).
UExter- UUARFCN,
nalUtran- DUARFCN
CellFDD
1-61
SchPriIndex USch- SchPriIndex Parameters in this table must exit in the association
PriMapping table.
LdCtlPriIn- UApp- AppPriIndex Parameters in this table must exit in the association
dex PriMapping table.
CgtCtlPriIn- UApp- AppPriIndex Parameters in this table must exit in the association
dex PriMapping table.
BPriAcIn- UBPriAc BPriAcIndex Parameters in this table must exit in the association
dex table.
VipTrfCatIn- UIntraMea- TrfCatIntraMIdx Parameters in this table must exit in the association
traIdx sProfile table.
Cid UUtran- Cid Parameters in this table must exit in the association
CellFDD table.
1-62
CId and UUtran- PrimScraCode For all intra-frequency adjacent cells of a service cell,
NCToSelf- CellFDD DUARFCN the PrimScraCode (including service cell) must be
PhyRnc+ UUARFCN different.For the adjacent cells of a service cell, if
NPhyCId the PrimScraCodes are the same, the DUARFCN of
UExter- PrimScraCode
these neighbouring cells (including the serving cell)
nalUtran- DUARFCN
must be different.
CellFDD UUARFCN
CId and UUtran- DUARFCN When DUARFCN of one service cell in the association
NCToSelf- CellFDD table is modified, check the table to see the restriction
PhyRnc+ on the number of the inter-frequency, intra-frequency
NPhyCId and inter-system neighbouring cells.
For the corresponding restriction check, refer to the
following note information.
Note:
1-63
1-64
CId UUtran- CId Parameters in this table must exit in the association
CellFDD table.
NPhyGsm- UExternal- AdjPhyGsmCId Parameters in this table must exit in the association
CId GsmCell table.
CId UGsmRela- NPhyGsmCId Each cell has up to 96 adjacent GSM cells towards
tion GsmStateMode which handover can be performed. These 96
adjacent GSM cells are:
l GsmStateMode is 1: handover only.
l GsmStateMode is 2: cell selection/reselection
and handover.
Each cell has up 32 adjacent GSM cells towards
which handover can be performed. These 32
adjacent GSM cells are:
l GsmStateMode is 1: cell selection/reselection
only.
l GsmStateMode is 1: cell selection/reselection
and handover.
1-65
CId UUtranCellFDD CId The parameter should also be created in another association table
EutranPriority[] UPriSel ThreshRsrqInd[] If ThreshRsrqInd[X] is False or ThreshRsrqInd[Y] is True and the EutranPriority[X]!=
EutranPriority[Y]
ThreshRsrqInd switch could be open or closed, the priority of the corresponding
configuration could be different.
UtranPriority[i] UPriSel UtranPriority[i] Among the three systems, the priorities are mutually exclusive. If a priority level in the
EutranPriority[i] EutranPriority[i] interval [0,7] has been applied to a node of UTRAN/EUTRAN system frequency or of cell
GeranPriority [i] GeranPriority [i] group priority array, the level cannot be applied in any other system. Systems cannot share
a priority level, but different frequency points or cell groups can have the same level
1-66
ZTE Proprietary and Confidential
Chapter 1 Relationships
1-67
CId UUtranCellFDD CId Before the record of CelSel with the cell is created, It must be ensured that there exists the
corresponding cell record in utranCell
HcsSrvCelInfoPre UUtranCellFDD UseOfHCS When UseOfHCS is 1(Not Used), HcsSrvCelInfoPre must be set to 0(False)
SIntraSearchPre UCelSel SIntraSearch Only when the value of SintraSearchPre is 1(True), SintraSearch is valid
SInterSearchPre UCelSel SInterSearch Only when the value of SinterSearchPre is 1(True), SinterSearch is valid
SSearchHCSPre UCelSel SSearchHCS Only when the value of SSearchHCSPre is 1(True), SSearchHCS is valid
OtherRATInfoPre UCelSel SSearchRat Only when the value of OtherRATInfoPre is 1(True), associated parameters are valid
SHCSRatPre
SLimitRat
OtherRATInfoPre UCelSel SHCSRat Only when OtherRATInfoPre and SHCSRatPre are 1(True), SHCSRat is valid
SHCSRatPre
1-68
HcsSrvCelInfoPre UCelSel TCrMax Only when the value of HcsSrvCelInfoPre is 1(True), TCrMax is valid
HcsSrvCelInfoPre UCelSel NCr Only when HcsSrvCelInfoPre is 1(True) and TcrMax is not 1(not used), associated param-
TCrMax TCrMaxHyst eters are valid
QualMeas UCelSel QHyst2S Only when QualMeas is 1(CPICH Ec/No), QHyst2S is valid
QHyst2SPch
ZTE Proprietary and Confidential
QHyst2SFach
NoHcsTCrMax UCelSel NoHcsNCr Only when NoHcsTcrMax is not 1(Not Used), associated parameter are valid
NoHcsTCrMaxHyst
Chapter 1 Relationships
ZXWR RNC Radio Parameter Constraints Reference
CId UUtran- CId Parameters in this table must exit in the association
CellFDD table.
NumofH- UUtran- HspaSptMeth The parameter is valid only when HspaSptMeth in the
spdsch CellFDD association table is 1 (Support HSDPA and DCH), 2
MinNu- (Support HSDPA only), 3 (Support HSUPA, HSDPA
mofH- and DCH) or 4 (Support HSUPA and HSDPA).
spdsch
MaxNu-
mofH-
spdsch
CHsGBR- UGbrRes- HsGBRResLim- Parameters in this table must exit in the association
ResLmtIdx Limit itIdx table.
DediComE- UUtran- ULEFACHSup- DediComEAGCHSwi is valid only when the key pa-
AGCHSwi CellFDD port rameter is 1.
1-70
CId UUtran- CId All parameters in this table must exist in utranCell
CellFDD
MCC UUtran- MCC One cell can belong to different MBMS service areas.
MNC CellFDD MNC For the cells belonging to the same frequency
MbmsSac CId under the same MBMS service area, the values
DUARFCN DUARFCN of DUARFCN and FreqBandInd in the utranCell
Fre- FreqBandInd table must be the same and are equal to that in this
qBandInd MbmsSuptInd table. Moreover, MbmsSuptInd in the record of the
corresponding cell must be 1 (support MBMS and
non-MBMS) or 2 (support MBMS).
1-71
FreqPLInd UMbmsSa None One MBMS SAC can contain only one or none pre-
ferred frequency layer.
FreqPLInd UMbmsSa None The preferred frequency can cover the whole MBMS
SA district.
CID UUtran- CID The parameter in this table must exist in utranCell
CellFDD
1-72
DTCfgInd[]
Discard-
Timer[]
MaxMacP-
DUSize[]
EFACHHS-
SCCHPwr
EFACHH-
SPDSCH-
Pwr
MACehsQI- UEFach MACehsQID[] The different value of the nodes in MACehsQID[] must
D[] be different
SPI [] UEFach SPI [] The different value of the nodes in SPI[] must be differ-
ent
Cid UUtran- Cid Associated parameters in this table must exist in the
CellFDD association table.
1-73
TxDivInd UUtran- SchTstdInd The value of TxDivInd is active only when the values
CellFDD PcpichTxDivInd of SchTstdInd, PcpichTxDivInd and PccpchSttdInd are
PccpchSttdInd active.
CID UUtran- CID If no cell record exist in the cell, ScpichSupInd of the
CellFDD ScpichSupInd corresponding cell in the UutranCellFDD table cannot
be TRUE.
CID UScpich CPCId The same cell has one Scpich channel at most.
Cid UUtran- CId Parameters in this table must exit in the association
CellFDD table.
SttdInd UUtran- SchTstdInd The value of SttdInd is active only when the values
CellFDD PcpichTxDivInd of SchTstdInd, PcpichTxDivInd and PccpchSttdInd are
PccpchSttdInd active.
Sc- USccpch None For one cell, there is only one SCCPCH for bearing
cpchUsage MCCH.That is to say, the maximum number of the SC-
CPCH channel is one when the value of SccpchUsage
is 5: Carrying MCCH FACH & R99 FACH, not Sup-
porting CBS, 6: Carrying MCCH FACH & R99 FACH,
Supporting CBS or 7:Carrying MCCH FACH.
1-74
Sc- USccpch SccpchUsage For each cell, there is one corresponding SCCPCH
cpchUsage record at most when the value of SccpchUsage is
as follows:
5: Carrying MCCH FACH & R99 FACH, not
Supporting CBS
6: Carrying MCCH FACH & R99 FACH, Supporting
CBS
7: Carrying MCCH FACH
CPCId USccpch SccpchUsage In the same cell, only one SCCPCH supports CBS.
This restriction is determined by the value of Sc-
cpchUsage in the Sccpch table. That is to say, in the
same cell, SccpchUsage of only one SCCPCH is 2, 4
or 6. SccpchUsage of other SCCPCH could be 0, 1,
3, 5 or 7.
Sc- USccpch SccpchUsage One SccpchUsage of the same cell only has one cor-
cpchUsage responding record at most.
CId USccpch CPCId The same cell has four Sccpch channels at most.
Cid UUtran- CId Parameters in this table must exit in the association
CellFDD table.
SttdInd UUtran- SchTstdInd The value of SttdInd is active only when the values
CellFDD PcpichTxDivInd of SchTstdInd, PcpichTxDivInd and PccpchSttdInd are
PccpchSttdInd active.
SccpchCP- USccpch CPCId Parameters in this table must exist in the association
CId SccpchUsage table. Moreover, SccpchUsage in the corresponding
associated records must be 0 (Carrying PCH), 3 (Car-
rying R99 FACH & PCH, not Supporting CBS) or 4(
Carrying R99 FACH & PCH, Supporting CBS) .
CId UPich CPCId The same cell has two Pich channels at most.
1-75
CId UUtran- CId Parameters in this table must exit in the association
CellFDD table.
ConstVal UPrach RachTti For all PRACH channels of the same cell, if TTI of
TFS corresponding to RACH carrying on PRACH is
the same, ConstVal of these PRACH channels must
be the same.
CId UPrach CPCId The same cell has five PRach channels at most.
AichCPCId UAich CPCId AichCPCId in this table must exist in CPCId (config-
ured under the same cell) in the UAich table.
Cid UUtran- CId Parameters in this table must exit in the association
CellFDD table.
PrachCP- UPrach CPCId Parameters in this table must exit in the association
CId table.
SttdInd UUtran- SchTstdInd The value of SttdInd is active only when the values
CellFDD of SchTstdInd, PcpichTxDivInd and PccpchSttdInd are
PcpichTxDivInd
active.
PccpchSttdInd
1-76
CId UAich CPCId The same cell has four Aich channels at most.
Cid UUtran- CId Parameters in this table must exit in the association
CellFDD table.
SttdInd UUtran- SchTstdInd The value of SttdInd is active only when the values
CellFDD of SchTstdInd, PcpichTxDivInd and PccpchSttdInd are
PcpichTxDivInd
active.
PccpchSttdInd
CId UUtran- CId Parameters in this table must exit in the association
CellFDD table.
1-77
HsdsRecover-
Thr
DecGbrSw ULdCtrl MaxGbrDec- The key parameters are valid only when DecGbrSw is
Num 1 (On).
CId UUtran- CId Parameters in this table must exit in the association
CellFDD table.
UlLdBalP- UPlBal ExtraCDeltaTru If UlLdBalPwrSwch is off, the key parameters are in-
wrSwch UlLdThdCs valid.
UlLdThdCs4G
UlLdThdR99Ps
DlLdBalP- UPlBal ExtraCDeltaTrd If DlLdBalPwrSwch is off, the key parameters are in-
wrSwch DlPwrThdCs4G valid.
LdBal- UPlBal LdBalCdWeight If LdBalCdSwch is off, the key parameters are invalid.
CdSwch Ex-
traCDeltaCdTrd
DlCdThdCs
DlCdThdR99Ps
1-78
HspaPlus- UPlBal HspaPlus- The value of HspaPlusCapInd [x] is unique. That is,
CapInd CapInd the capability coordinate of the nodes corresponding
to different arrays should be different.
TrfPcInde UUtran- TrfPcIndex Parameters in the association table must exit in this
CellFDD table.
SrvType USubSrv SrvType Parameters in this table must exit in the association
table.
SrvType USrvPc UlIlPcAlg Only when SrvType is an even number, the associated
UlSirTargUp- parameter is valid.
Step
UlSir-
TargDnStep
SwchAdap-
tiveStep
MaxSir-
TargDnStep
QeCntThres
NhrThrUpTti10[
]
NhrThrDownTt-
i10[]
NhrThrUpTti2[]
NhrThrDownTti-
2[]
1-79
UpThrSamp-
NuTti10[]
DwThrSamp-
NuTti10[]
UpThrSamp-
NumTti2[]
DwThrSamp-
NumTti2[]
BerErrorTbThr-
esh
BerTbThresh
BerTargDnStep
BerTargUpStep
SrvType USrvPc TpcDlStep Only when SrvType is an odd number, the associated
parameter is valid.
SrvType USrvPc TpcStepSize Only when SrvType is an even number, the associated
UlIlPcAlg parameters are valid. When UlIlPcAlg is algorithm 1,
the value of associated parameter is (1, 2)dB. When
UlIlPcAlg is algorithm 2, the value of associated pa-
rameter is only 1dB.
MaxSir- USrvPc UlSir- When SrvType is the uplink service subtype (an even
TargDnStep TargDnStep number), UlSirTargDnStep[i] ≤ MaxSirTargDnStep[i] i
= 0–8
NhrThrUpT- USrvPc NhrThrUpTti2[] When SrvType is the uplink service subtype (an even
ti2[] NhrThrDownTti- number)
NhrThrDo- 2[] NhrThrUpTti2 [0] ≤ NhrThrUpTti2 [1] ≤ NhrThrUpTti2
wnTti2[] [2]
NhrThrUpTti2 [3] ≤ NhrThrUpTti2 [4] ≤ NhrThrUpTti2
[5]
NhrThrUpTti2 [6] ≤ NhrThrUpTti2 [7] ≤ NhrThrUpTti2
[8]
NhrThrUpTti2 [0] ≤ NhrThrUpTti2 [3] ≤ NhrThrUpTti2
[6]
NhrThrUpTti2 [1] ≤ NhrThrUpTti2 [4] ≤ NhrThrUpTti2
[7]
1-80
NhrThrUpT- USrvPc NhrThrUpTti10[ When SrvType is the uplink service subtype (an even
ti10[] ] number)
NhrThrDo- NhrThrDownTt- NhrThrUpTti10 [0] ≤ NhrThrUpTti10 [1] ≤
wnTti10[] i10[] NhrThrUpTti10 [2]
NhrThrUpTti10 [3] ≤ NhrThrUpTti10 [4] ≤
NhrThrUpTti10 [5]
NhrThrUpTti10 [6] ≤ NhrThrUpTti10 [7] ≤
NhrThrUpTti10 [8]
NhrThrUpTti10 [0] ≤ NhrThrUpTti10 [3] ≤
NhrThrUpTti10 [6]
NhrThrUpTti10 [1] ≤ NhrThrUpTti10 [4] ≤
NhrThrUpTti10 [7]
NhrThrUpTti10 [2] ≤ NhrThrUpTti10 [5] ≤
NhrThrUpTti10 [8]
NhrThrDownTti10 [0] ≤ NhrThrDownTti10 [1] ≤
NhrThrDownTti10 [2]
NhrThrDownTti10 [3] ≤ NhrThrDownTti10 [4] ≤
NhrThrDownTti10 [5]
NhrThrDownTti10 [6] ≤ NhrThrDownTti10 [7] ≤
NhrThrDownTti10 [8]
NhrThrDownTti10 [0] ≤ NhrThrDownTti10 [3] ≤
NhrThrDownTti10 [6]
NhrThrDownTti10 [1] ≤ NhrThrDownTti10 [4] ≤
NhrThrDownTti10 [7]
NhrThrDownTti10 [2] ≤ NhrThrDownTti10 [5] ≤
NhrThrDownTti10 [8]
1-81
NhrThrUpT- USrvPc NhrThrDownTti- When SrvType is the uplink service subtype (an
ti10[] 10[] even number), nine array nodes (from 0 to 8) of
NhrThrUpTti10 and NhrThrDownTti10 must satisfy:
NhrThrUpTti10[i] ≥ NhrThrDownTti10[i].
NhrThrUpT- USrvPc NhrThrDownTti- When SrvType is the uplink service subtype (an
ti2[] 2[] even number), nine array nodes (from 0 to 8) of
NhrThrUpTti2 and NhrThrDownTti2 must satisfy:
NhrThrUpTti2[i] ≥ NhrThrDownTti2[i].
SrvType USrvPc EdchHar- The associated fields are valid for the subtype with
SrvInd qPOFdd SrvInd being 0 (non MBMS) when SrvType is an
even number.
1-82
1-83
1-84
RptType UNbDed- EvtEfSirEThrd1 When RptType is E/F, and DedMeasType is SIR ER-
DedMeasT- Meas ROR, the associated parameter is valid
ype
RptType UNbDed- EvtAbTcpThrd[] When RptType is A/B, and DedMeasType is TCP, the
DedMeasT- Meas associated parameter is valid
ype
RptType UNbDed- EvtEfSirEThrd2 When RptType is E/F, and DedMeasType is SIR ER-
DedMeasT- Meas ROR, the associated parameter is valid
ype
RptType UNbDed- RptPrdUnit When RptType is Periodic or E/F, the associated pa-
Meas RptPrd rameter is valid
1-85
UeTrvM- UTrvMea- UeTrvMCfg- It has at least one matching record for any value of
CfgNo sProfile Note the associated parameter.
UeTrvMCfg- UTrvMea- Measobj The following limits apply to the UeTrvMCfgNote and
Note sProfile RptCrt Measobj, RptCrt values:
When the UeTrvMCfgNote value is 0(UE Traffic
volume Period Measurement Configuration Number
for DCH), the Measobj value must be 1(DCH), and the
RptCrt value must be 2(Periodical reporting criteria)
When the UeTrvMCfgNote value is 1(UE Traffic
volume Event Measurement Configuration Number
for DCH), the Measobj value must be 1(DCH), RptCrt
value must be 1(UE traffic volume measurement
reporting criteria)
1-86
1-87
MeasQuan- UTrvMea- AverageTime If the value is 1(RLC buffer payload), then the
tity sProfile associated parameter is invalid
RptCrt UTrvMea- MeasEvtNum RptCrt value is 1 (event report), then the associated
sProfile MeaEvtId[i] parameter is valid
TrigTime[i]
PendingTime[i]
TxInterCfgPre[i]
RptCrt UTrvMea- RptThres[i] Only when RptCrt value is 1(event report), then the
sProfile associated parameter is valid
RptCrt UTrvMea- TxInterruption[i] Only when RptCrt value is 1(event report) and the
TxInterCfg- sProfile TxInterCfgPre value is TRUE, then the associated
Pre[i] parameter is valid
RptCrt UTrvMea- RptThres0 Only when RptCrt value is 1(event report), then the
sProfile RptThres1 associated parameter is valid
RptThres2
RptThres3
RptThres4
RptThres5
RptThres6
ThoughThres
1-88
CId UUtran- CId The parameter in this table must exist in UUtran-
CellFDD CellFDD
DrbcD- UTrvMea- UeTrvMCfgNo The parameter in this table must exist in UeTrv
chUePrd sProfile
DrbcD-
chUeEvt
DrbcDchUp
DrbcRach-
UePrd
DrbcRach-
UeEvt
Drbc-
FachUp
DrbcSHsUp
DrbcIBH-
sUp
ETtiUpThpt
DrbcED-
chUpThpt
DrbcC-
FachHsUp
DrbcD- UTrvMea- UeTrvMCfg- The associated parameter value in the association ta-
chUePrd sProfile Note ble must be 0(UE Traffic volume Period Measurement
Configuration Number for DCH )
1-89
DrbcC- UTrvMea- UeTrvMCfg- The value of related parameters in the association ta-
FachHsUp sProfile Note ble must be 11(UP Traffic Volume Measurement Con-
figuration Number for HS-DSCH in CELL_FACH)
DrbcC- UTrvMea- UeTrvMCfg- The value of related parameters in the association ta-
FachED- sProfile Note ble 12( UP Traffic Volume Measurement Configuration
chUp Number for E-DCH in CELL_FACH)
1-90
1-91
FilterCoeff UUeIntMea- MeasQuantity This parameter is invalid when the value of related
sProfile parameter is 2 (UE Rx-Tx Time Difference).
1-92
ImsiMatched- UImsiSnacFil- SMCC There are at most 10 SMCC+ SMNC+SNAC for these
DgtNum ter SMNC records that have same MCC+MNC+ ExtInfoDgtNum+
ImsiMatched- SNAC ExtInfo[i].(i=[1, ExtInfoDgtNum])
Digit[15]
MCC+MNC+ USnac SNAC There are at most 4 SNAC that same MCC+ MNC+ LAC can
LAC belong to
MCC+MNC+ USnac LAC There are at most 10 LAC that same MCC+ MNC+ SNAC
SNAC can belong to
RNCSPID UDePri RNCSPID The value of RNCSPID must exist in the value of RNC-
SPID of UDePri.
1-93
1-94
1-95
1-96
2-1
UMPOProfile ............................................................................................................2-15
UScpich ...................................................................................................................2-15
USccpch ..................................................................................................................2-15
UPich .......................................................................................................................2-15
UPrach.....................................................................................................................2-16
UAich .......................................................................................................................2-16
UMich.......................................................................................................................2-17
ULdCtrl.....................................................................................................................2-17
UPlBal......................................................................................................................2-17
USrvPc.....................................................................................................................2-18
UNbComMeas..........................................................................................................2-18
UNbDedMeas...........................................................................................................2-18
UTrvMeasProfile.......................................................................................................2-18
UImsiSnacFilter........................................................................................................2-19
USnac ......................................................................................................................2-19
UUeIntMeasProfile ...................................................................................................2-19
UCommEdch............................................................................................................2-19
UExternalENBFunction.............................................................................................2-20
UEUtranRelation ......................................................................................................2-20
ULogicalRnc.............................................................................................................2-20
ULogicalIurQos ........................................................................................................2-20
UDedSrvTb ..............................................................................................................2-20
UIDNNSRouting .......................................................................................................2-21
UIMSIRouting...........................................................................................................2-21
UWhiteSrvPc............................................................................................................2-21
WhiteList ..................................................................................................................2-21
UDePri .....................................................................................................................2-22
UImeiTacSPID..........................................................................................................2-22
UImeiBlkList .............................................................................................................2-22
UENbrBlkList............................................................................................................2-22
2.1 Overview
This section describes operations of MOC that need a special treatment.
The primary key and the alternative key are not allowed to be modified in the planned data
of all objects.
For the description of MOC operation is Null, fill in the data according to the restriction
relationship described in the Associations chapter.
Note:
In all operations of MOC, all primary key and alternative key must exsit.
2-2
2.2 URncFunction
Name Description
Delete The operation is not allowed. Reason: There is only one record in the table
Add The operation is not allowed. Reason: There is only one record in the table
Modify NULL
2.3 UIubLink
Name Description
Delete If the Node B is not quoted by the UutranCellFDD, delete the Node B directly
If the Node B is quoted by the UutranCellFDD, delete both the record of the
Node B and records of all cells that have quoted the Node B
Add Null
Modify Null
2.4 UUeCnst
Name Description
Delete The operation is not allowed. Reason: There is only one record in the table
Add The operation is not allowed. Reason: There is only one record in the table
Modify Null
2.5 UcnInfo
Name Description
Delete Null
Add Null
Modify Null
2.6 UIuCnst
Name Description
2-3
Name Description
Modify Null
2.7 UDrbc
Name Description
Modify Null
2.8 UGloAc
Name Description
Delete The operation is not allowed. Reason: There is only one record in the table
Add The operation is not allowed. Reason: There is only one record in the table
Modify Null
2.9 UHspa
Name Description
Delete The operation is not allowed. Reason: There is only one record in the table
Add The operation is not allowed. Reason: There is only one record in the table
Modify Null
2.10 GbrRes
Name Description
Add If this entry is quoted by the HsGBRResLimitIdx property of UCHspa, it can not
be deleted before deleting the quoting relation
2-4
Name Description
2.11 UMbms
Name Description
Delete The operation is not allowed. Reason: There is only one record in the table
Add The operation is not allowed. Reason: There is only one record in the table
Modify Null
2.12 UCfnOffset
Name Description
Modify Null
2.13 UBasPri
Name Description
Modify The ARPThresh and ARPSegNum should be modified at the same time. Make
sure that the number of ARPThresharray elements in the planning data is equal
to ARPSegNum-1.
The THPThresh and THPSegNum should be modified at the same time. Make
sure that the number of the THPThresh array elements in the planning data is
equal to THPSegNum-1
The BPThresh and BPSegNum should be modified at the same time. Make
sure that the number of the BPThresh array elements in the planning data is
equal to BPSegNum -1
If reduce the value of ARPSegNum, corresponding records of BasPri should
be delete at the same time
If increase the value of ARPSegNum, corresponding records of BasPri should
be add at the same time
2-5
Name Description
2.14 UBasPriMapping
Name Description
Delete Null
Add Null
Modify Null
2.15 USchPriMapping
Name Description
Delete If the SchPri is not quoted by the utranCell, delete the SchPri directly
If the SchPri is quoted by the utranCell, follow the following steps:
1. Modify the SchPriIndex of UutranCellFDD in "planned data" setting,
2. Release the quotation relationship
3. Generate the script according to the data planned in Step 1
4. Import the script into NetNumen for execution
5. Delete the record of the SchPri in "planned data" setting
6. Generate the script according to the data planned in Step 3 and import the
script into NetNumen for execution
Add Null
Modify Null
2-6
2.16 UAppPriMapping
Name Description
Delete If the AppPri is not quoted by the utranCell,delete the record of AppPri
If the AppPri is quoted by the utranCell, follow the following steps:
1. Modify the LdCtrlPriIndex and CgtCtlPriIndex of utranCell
2. Release quotation relationship
3. Generate the script according to the data planned in Step 1
4. Import the NetNumen for execution
5. Delete the record of AppPri
6. Generate the script according to the data planned in Step 3 and import
the NetNumen for execution
Add Null
Modify Null
2.17 UBPriAc
Name Description
Delete If the local object is not quoted by the UutranCellFDD, delete the UBPriAc
directly
If the local object is quoted by the UutranCellFDD, follow the following steps:
1. Modify the BPriAcIndex data of UutranCellFDD in "planned data" setting
2. Release the quotation relationship
3. Generate the script according to the data planned in Step 1
4. Import the script into NetNumen for execution
5. Delete the record of UBpriAc in "planned data" setting
6. Generate the script according to the data planned in Step 3 and import the
script into NetNumen for execution
Add Null
Modify Null
2.18 UIntraMeasProfile
Name Description
2-7
Name Description
Add Null
2.19 UInterMeasProfile
Name Description
Delete If the Inter is not quoted by the CInter object, delete the record of the Inter
directly
If the Inter is quoted by the CInter object, follow the following steps:
1. Modify the data of the CInter in "planned data"setting.
2. Release the quotation relationship
3. Generate the script according to the data planned in Step 1
4. Import the script into OMM, and execute successfully
5. Delete the record of the Inter in "planned data"setting
6. Generate the script according to the data planned in Step 3 and import the
script into NetNumen for execution
Add Null.
2-8
Name Description
2.20 URatMeasProfile
Name Description
Delete If the Rat is not quoted by the CRat object, delete the record of the Rat
If the Rat is quoted by the CRat object, follow the following steps:
1. Modify the data of the CRat in "planned data"setting
2. Release the quotation relationship
3. Generate the script according to the data planned in Step 1
4. Import the script into OMM, and execute successfully
5. Delete the record of Rat in "planned data"setting
6. Generate the script according to the data planned in Step 3 and import the
script into NetNumen for execution
Add Null.
2.21 USubSrv
Name Description
Delete The operation is not allowed. Reason: Only default service records are
supported in RNC
2-9
Name Description
Add The operation is not allowed. Reason: Only default service records are
supported in RNC
Modify Direction, Domain, MaxBitRate and TrafficClass can not be modified. Reason:
They are character parameters of SrvType and must be matched to SrvType
2.22 UrncDtxDrx
Name Description
Delete If this record is cited by DtxDrxConfigIdx of USubSrv, users need to delete the
cite relationship before deleting this record.
2.23 USrvDivPc
Name Description
Delete If the USrvDivPc is not quoted by the utranCell, delete the record of USrvDivPc
directly.
If the USrvDivPc is quoted by the utranCell, follow the following steps:
1. Modify the data of the UutranCellFDD in "planned data" setting
2. Release the quotation relationship
3. Generate the script according to the data planned in Step 1
4. Import the script into OMM, and execute successfully
5. Delete the record of the USrvDivPc in "planned data"setting
6. Generate the script according to the data planned in Step 3 and import the
script into NetNumen for execution
Add Null
Modify Null
2.24 UExternalRncFunction
For the restriction relationship, refer to External Utran Cell (externalUtranCell).
2-10
Name Description
Delete If the externalUtranCell is not quoted by the utranRelation, delete the record
of externalUtranCell directly
If the externalUtranCell is quoted by utranRelation, both the record of the
externalUtranCell and records of the utranRelation that have quoted the
externalUtranCell should be deleted
Add Null
2.25 UExternalGsmCell
Name Description
Delete If the UExternalGsmCell is not quoted by the UGsmRelation, delete the record
of the UExternalGsmCell directly
If the UExternalGsmCell is quoted by the UGsmRelation, both the record of
the UExternalGsmCell and records of UGsmRelation that have quoted the
UExternalGsmCell should be deleted
Add Null
Modify Null
2.26 UUtranCellFDD
Name Description
Create Null
2-11
Name Description
2.27 UutranRelation
Name Description
Delete Null
Modify Null
2.28 UGmRelation
Name Description
Delete Null
2-12
Name Description
Modify Null
2.29 UPriSel
Name Description
Delete Null
Add Null
Modify Null
2.30 UCelSel
Name Description
Add If CID of the UCelSel to be added has existed in UranCellFDD, add the record
of UCelSel directly
If CID of the UCelSel to be added has not existed in UranCellFDD, add the
record of UCelSel and UranCellFDD
Modify Null
2.31 UCHspa
Name Description
Delete Null
2-13
Name Description
Add If CID of the UCHspa to be added has existed in UranCellFDD, add the record
of UCHspa directly
If CID of the UCHspa to be added has not existed in UranCellFDD, add the
record of UCHspa and uranCell
Modify Null
2.32 UCMbms
Name Description
Delete Null
Add If CID of the UCMbms to be added has existed in UranCellFDD, add the record
of UCMbms directly.
If CID of the UCMbms to be added has not existed in UranCellFDD, add the
record of UCMbms and UranCellFDD.
Modify Null
2.33 UMbmsSa
Name Description
Delete Null
Add Null
Modify Null
2.34 UEFach
Name Description
Delete The UUtranCellFDD object must be deleted when this object is deleted
Add If UUtranCellFDD corresponding to cid already exists, then add this object. Oth-
erwise, UUtranCellFDD must be added first.
Modify Null
2-14
2.35 UMPOProfile
Name Description
Delete 如果UMPOProfile被小区引用,如果删除UMPOProfile,必须先删除引用它的小
区If UMPOProfile is quoted by UUtranCellFDD, then the UUtranCellFDD must
be deleted before delete this UMPOProfile.
Add If UUtranCellFDD corresponding to cid already exists, then add this object. Oth-
erwise, UUtranCellFDD must be added first.
Modify Null
2.36 UScpich
Name Description
2.37 USccpch
Name Description
Delete Null
Create If CID of the Sccpch to be added has existed in UranCellFDD, add the record of
Sccpch directly.
If CID of the Sccpch to be added does not exist in UranCellFDD, add the record
of Sccpch and UranCellFDD directly.
Modify Null
2.38 UPich
Name Description
2-15
Name Description
Modify When modifying the PCHCTCID of Pich( It means to transfer the Pich from one
Sccpch to another Sccpch), modify the data below:
1. Modify the data of the Pich
2. Modify the value of PichCPCId to 255 in the record of Sccpch that quotes
this Pich
2.39 UPrach
Name Description
Add If CID of the Prach to be added has existed in uranCell, add the record of
Prach directly
If CID of the Prach to be added has not existed in uranCell, add the record
of Prach and uranCell
Modify Null
2.40 UAich
Name Description
Delete Null
Add If the Prach that is quoted by CID+PrachCPCId of the UAich has existed, add
the record of Aich directly.
If the Prach that is quoted by CID+PrachCPCId of the UAich has not existed,
add the record of Aich and Prach.
The addition of this common channel will trigger the deletion and re-setup of
the serving cell.
Modify Null
2-16
2.41 UMich
Name Description
Delete Delete the record of Mich, and delete the record of the Sccpch whose CPCID is
35 at the same time.
Add If the USccpch that is quoted by CID+SccpchCPCId of the Mich has existed,
add the record of Mich directly.
If the USccpch that is quoted by CID+SccpchCPCId of the Mich has not existed,
add the record of Aich and Sccpch.
Add Mich channel if SCCPCH channels with SccpchUsage as 5/6/7 exist in
the cells listed in the Sccpch table.
Add SCCPCH and Mich channels if SCCPCH channels with SccpchUsage as
5/6/7 do no exist in the cells listed in the USccpch table.
The addition of this common channel will trigger the deletion and re-setup of the
serving cel.
Modify Null
2.42 ULdCtrl
Name Description
Delete Null
Add If CID of the LdCtrl to be added has existed in UUtranCellFDD, add the record
of LdCtrl.
If CID of the LdCtrl to be added has not existed in UUtranCellFDD add the
record of LdCtrl and UUtranCellFDD.
Modify Null
2.43 UPlBal
Name Description
Delete Null
Add If CID of the UPplBal to be added has existed in UutranCell, add the record
of UPlBal
If CID of the UPlBal to be added has not existed in UutranCell, add the record
of UPlBal and UutranCell
Modify Null
2-17
2.44 USrvPc
Name Description
Delete If the USrvPc is not quoted by the UutranCell, delete the record of USrvPc
directly.
If the USrvPc is quoted by the UutranCell, follow the following steps:
1. Modify the data of UutranCell that has quoted the USrvPc in "planned data"
settings.
2. Release the quote relationship.
3. Generate the script according to the data planned in Step 1.
4. Import the script into OMM, and execute successfully.
5. Delete the record of the TrfPc in "planned data" settings.
6. Generate the script according to the data planned in Step 3 and import the
script into NetNumen for execution.
Add Null
Modify Null
2.45 UNbComMeas
Name Description
Delete If this object is quoted by CNbom, then it only can be deleted after the quotation
relationship is moved
If this object is not quoted by CNbom, it can be deleted directly
Add Null
Modify Null
2.46 UNbDedMeas
Name Description
Delete Null
Add Null
Modify Null
2.47 UTrvMeasProfile
Name Description
Delete Null
2-18
Name Description
Add Null
Modify Null
2.48 UImsiSnacFilter
Name Description
Delete Null
Add Null
Modify The operation is not allowed. Reason: Every parameter is an integral part
of the complete primary keys
2.49 USnac
Name Description
Delete Null
Add Null
Modify The operation is not allowed. Reason: Every parameter is an integral part
of the complete primary keys
2.50 UUeIntMeasProfile
Name Description
Delete If this object is quoted, users need to delete the quotation relationship before
deleting the object.
Add Null
Modify Null
2.51 UCommEdch
Name Description
Delete Null
Add Null
Modify Null
2-19
2.52 UExternalENBFunction
Name Description
Delete Null
Add Null
Modify Null
2.53 UEUtranRelation
Name Description
Delete Null
Add Null
Modify Null
2.54 ULogicalRnc
Name Description
Delete Null
Add Null
Modify Null
2.55 ULogicalIurQos
Name Description
Delete Null
Add Null
Modify Null
2.56 UDedSrvTb
Name Description
Delete If this object is quoted by the ProfileIndex parameter of the UDedSrvTb object,
users need to delete the quotation relationship before deleting this object.
2-20
Name Description
Add Null
Modify Null
2.57 UIDNNSRouting
Name Description
Delete Null
Add Null
Modify Null
2.58 UIMSIRouting
Name Description
Delete Null
Add Null
Modify Null
2.59 UWhiteSrvPc
Name Description
Delete Null
Add Null
Modify Null
2.60 WhiteList
Name Description
Delete Null
Add Null
Modify Null
2-21
2.61 UDePri
Name Description
Delete Null
Add Null
Modify Null
2.62 UImeiTacSPID
Name Description
Delete Null
Add Null
Modify Null
2.63 UImeiBlkList
Name Description
Delete Null
Add Null
Modify Null
2.64 UENbrBlkList
Name Description
Delete Null
Modify Null
2-22