Você está na página 1de 2241

ZXG10 iBSC

Base Station Controller


Radio Parameter Reference

Version: V6.20.71

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 © 2012 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

Revision No. Revision Date Revision Reason

R1.5 2012–09–07 Add parameters: T23, T24, T3197, RttiAccess,


MITPrepMRRecInt, MITMRRecInt, CellAlarmDelay.

Update parameters: Info_7, Inc8PskPwrThs, Inc8PskPwrHys,


PwrAdjustThreshold, PwrAdmitThrldPunish, PwrAdmitThreshold.

R1.4 2012–07–31 Update to V6.20.713d

Add parameters: DualFreqNC2Sup, DualFreqNC2N,


DualFreqNC2P, DualFreqNC2TAThr, DualCellPsChanThr,
ULRxLevThr, DLRxLevThr, ULRxQualThr, DLRxQualThr,
TPingPang, NC2ResHys, NC2ResThr, NC2DistanceWindow,
PBGTHoBacktoSource, OtherHoBacktoSource,
HoAccessReqLevOffset, OtherHoAccessLevSel,
DualFreqOverLoadThs, CSAllocSC, IsDualFreqSup,
PBGTHoBacktoSource, OtherHoBacktoSource,
HoAccessReqLevOffset, OtherHoAccessLevSel, SC1LoadThs1,
SC1LoadThs2, TsBlockAlarmSwitch, INFO1_0_8, RMST3109,
RMST3111.

Update parameters: BCCHMaxPwrDec, CellShuttingDown,


Subcell2MeasureBcch, FrToAmrHrHoLoadThSC2, T3193,
PathLossRatio, HCS_Thr_0, HCS_Thr_1, HoControl_4,
ENBID, HRDfragSupport, CanBcchExch, P0, INFO1_5_1,

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Revision No. Revision Date Revision Reason

INFO1_5_2, IPAInterHo, DownPowerBmp, PwDownLoadInd,


DivCombMode, CSDHoIntraEnable, CSDHoInterEnable,
CSDHoOutEnable, HrToFrHoLoadThr, AmrHrToFrHoLoadThr,
HrToFrHoLoadThrSC2, AmrHrToFrHoLoadThSC2, HoControl_1,
HoControl_2, Info_4_5, TdHoEnable.

R1.3 2012–05–10 Update the chapter: About This Manual, Introduction to BSS
Radio Parameters, Method of Modifying Parameters in Batch,
Precautions on Parameter Adjustment.

Add new chapter Modify Parameters and new appendix Mutex


Right Management.

R1.2 2012–03–19 Update to V6.20.712c

Add new MO: New Power Control Attribute and parameters which
are belong to this MO.

Add parameters: TSDRelPeriod, TSDDeactDelay,


HrToFrHoLoadThr, AmrHrToFrHoLoadThr,
HoUlQualThsForAmrFr, HoUlQualAmrFrN, HoUlQualAmrFrP,
HoUlQualThsForAmrHr, HoUlQualAmrHrN, HoUlQualAmrHrP,
HoDlQualThsForAmrFr, HoDlQualAmrFrN, HoDlQualAmrFrP,
HoDlQualThsForAmrHr, HoDlQualAmrHrN, HoDlQualAmrHrP,
HoUlLevThsForAmrFr, HoUlLevAmrFrN, HoUlLevAmrFrP,
HoUlLevThsForAmrHr, HoUlLevAmrHrN, HoUlLevAmrHrP,
HoDlLevThsForAmrFr, HoDlLevAmrFrN, HoDlLevAmrFrP,
HoDlLevThsForAmrHr, HoDlLevAmrHrN, HoDlLevAmrHrP,
HrToFrHoLoadThrSC2, AmrHrToFrHoLoadThSC2, QSearchC,
WindowEutran, FDDRptOffset6bit, FDDRptOffset3bit,
TDDRptOffset6bit, TDDRptOffset3bit, FDDRptOffset_PS,
TDDRptOffset_PS, PwDownLoadInd, DownPowerBmp,
HRTFRHOSupport2, NccCfgPara, RQThreshold,
DualFreqNetTchThs, DivCombMode, IsDualFreqRltCell,
PwDownHoPriInd, DualFreqHoSup, DualFreqHoN, DualFreqHoP,
DualFreqHoTAThs, DualFreqHoDLThs, SubCell2N, SubCell2P,
SubCellHoDLThs, EUtranHighThreshQ, EUtranLowThreshQ,
EUtranQQUALMIN, RelEUtranStrategy, RelEUtranPrio,
ChanSelForIPAHo, SigTBFDlDelayTime, SigTBFExtUlTime,
DataTBFDlDelayTime, DataTBFExtUlTime, ISRSV,
CSDHoIntraEnable, CSDHoInterEnable, CSDHoOutEnable,
DynSdCheckDelay.

Update parameters: SubCell1N, SubCell1P, TsRel,


NCellIndOfChlRel, AmrThresholds, AmrHysteresis,
AmrStartMode, RMSTT3109, RMSTT3111, TargetTrafficThsSC2,
Info_2_0, IsDualFreqRltCell, PSPwrChgStep0, PSPwrChgStep1,
Revision No. Revision Date Revision Reason

HoControl_1, HoControl_2, HoControl_4, HoControl[1]_1,


HoControl[1]_2, HoControl[1]_4, HoControl[2]_1, HoControl[2]_2,
HoControl[2]_4, PcMinInterval, DLPcMinInterval, DLPwrRedStep.

R1.1 2011–09–30 Update to V6.20.711c

Add parameters: IPAInterHo, GetUtranClass,


EarlyDlTBFEstSupp, SuppReducePd, LmtThreshold_0,
LmtThreshold_1, LmtThreshold_2, LmtThreshold_3,
CsPagingPrefer, IsDirectRetryCell, CICAlarmSwitch,
BVCAlarmSwitch, MOSmsIntercept, MTSmsIntercept,
TCobcchWaitMR, PbgtHoStartThsSC2,
FrToAmrHrHoLoadThSC2, FrToHrHoLoadThrSC2, UseSC1Load,
MrCountForRlt, HoMarginPbgtSC2, HoMarginRxLevSC2,
HoMarginRxQualSC2, RxLevMinSC2, TargetTrafficThsSC2,
Info_3, Info_6 , Info_7, Info_3, Info_4, Info_5, Info_6, Info_7,
Info1_2, Info1_3.

Update parameters: HoMarginPbgt, HoMarginRxLev,


HoMarginRxQual, HoMarginPbgt, HoMarginRxLev,
HoMarginRxQual, ResourceAdjustThs, UtranCellPrio,
UtranCellPrio, ChlReqRejBmp, PcMinInterval, OldToNewctrl,
BtsId, AutoSToMEnable.

R1.0 2011–07–30 First Edition (V6.20.71)

Serial Number: SJ-20110531095035-017

Publishing Date: 2012-09-07 (R1.5)

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


About This Manual
About this Manual
This manual introduces the ZXG10 iBSC radio parameters for radio configuration and
commissioning.

Audience
l System Engineer
l Commissioning Engineer
l Maintenance Engineer

What Is in This Manual


This manual has the following chapters.

Chapter Name Summary

Chapter 1 Overview Introduces the scope, description methods, and adjustment cautions
for radio parameters.

Chapter 2 BSC Function Introduces the BSC function parameters.


Parameters

Chapter 3, External Cell Introduces the GERAN external cell parameters and UTRAN external
Parameters cell parameters.

Chapter 4, Cell Parameters Introduces the cell parameters in the BSS system.

Chapter 5, Cell Object Introduces the cell object parameters in the BSS system.
Parameters

Chapter 6, System Control Introduces the system control parameters in the BSS system.
Parameters

Appendix A, Flow Control Introduces the data values of Flow Control Policy.
Policy Values

Appendix B, Power Values Introduces the data values of Power

Appendix C, Setting of Cell Introduces the setting of Cell Layers


Layers

Appendix D, Corresponding Introduces the relationship between radio parameters on the interface
Relationship between and database values in the BSS system.
Parameter Interface and
Database Values

Appendix E, Mutex Right Introduces how to apply or release the mutex right.
Management

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


II

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Contents
About This Manual ......................................................................................... I
Chapter 1 Overview .................................................................................... 1-1
1.1 Introduction to BSS Radio Parameters................................................................. 1-1
1.2 Modify Parameters ............................................................................................. 1-2
1.3 Method of Modifying Parameters in Batch ............................................................ 1-4
1.4 The Format to Explain Parameters ...................................................................... 1-9
1.5 Precautions on Parameter Adjustment................................................................1-11

Chapter 2 BSC Function Parameters........................................................ 2-1


2.1 Radio Basic Property.......................................................................................... 2-1
2.1.1 DCS1800/PCS1900 support (FuncExt) ...................................................... 2-1
2.1.2 Load indication allowed (LoadInd) ............................................................. 2-2
2.1.3 Send confusion message allowed (ConfusionMsg) ..................................... 2-3
2.1.4 Inter-cell handover allowed (InHoEnable)................................................... 2-4
2.1.5 Send assignment failure allowed in outer direct retry procedure
(ExDRSendAssFail) ................................................................................ 2-6
2.1.6 Load indication Valid Time (LoadValidTime) ............................................... 2-7
2.1.7 Load Indication Period (LoadIndPrd).......................................................... 2-8
2.1.8 Congestion Threshold for Send Load Indication (LoadIndThs)..................... 2-9
2.1.9 Forbid Handover According to Resource Threshold of Load Indication
(LoadForbidHo) .................................................................................... 2-10
2.1.10 Resource Threshold of Load Indication for Forbid Handover
(LoadThsForbidHo) ................................................................................2-11
2.1.11 Support Precise Paging (PrecisePagSupport)......................................... 2-12
2.1.12 Use HPC for Precise Paging (PrecisepagUseHpc).................................. 2-13
2.1.13 Adopt Precise Paging for repaging of Circuit Switched Service
(CsRepagPrecise)................................................................................. 2-14
2.1.14 Adopt Precise Paging for repaging of Packet Switched Service
(PsRepagPrecise)................................................................................. 2-15
2.1.15 Allow Exceed area Precise Paging for Circuit Switched Service
(CsOutAreaPag) ................................................................................... 2-16
2.1.16 Allow Exceed area Precise Paging for Packet Switched Service
(PsOutAreaPag) ................................................................................... 2-17
2.1.17 Paging Repeat Time for Circuit Switched Service
(CsPagingRepeatTime) ......................................................................... 2-18

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


2.1.18 Paging Repeat Time for Packet Switched Service
(PsPagingRepeatTime) ......................................................................... 2-19
2.1.19 Automatic Resource Indication Threshold (ResourceIndThs)................... 2-20
2.1.20 BSC maximum reset number (BscMaxResetNum).................................. 2-22
2.1.21 MR report support (MrRptEnable).......................................................... 2-23
2.1.22 HBTS scan site number (HBTSScanSiteNum)........................................ 2-24
2.1.23 Range of Barang .................................................................................. 2-25
2.2 Functional Switch ............................................................................................. 2-26
2.2.1 RIM support (RIMSupport) ...................................................................... 2-26
2.2.2 RIM retry times (RIMRetryTimes) ............................................................ 2-27
2.2.3 Different reselection parameter in idle and transfer status support
(PSReselParam2) ................................................................................. 2-28
2.2.4 Handover synchronization indication support (Info_0_16).......................... 2-29
2.2.5 Switch of TRAU frame synchronized monitor (Info_4_5) ........................... 2-30
2.2.6 PS handover support (PSHoSupp) .......................................................... 2-31
2.2.7 Enable PS Handover Indications in Inter-BSS handover
(EnablePSHoIndi) ................................................................................. 2-32
2.2.8 Request SI/PSI (EnableRequestPSI) ....................................................... 2-33
2.2.9 Support EMLPP (SupportEMLPP) ........................................................... 2-34
2.2.10 DFCA support (DFCASupport) .............................................................. 2-35
2.2.11 Support resource optimizing by service (SuppResOpByService).............. 2-36
2.2.12 Identify of special service (SpecServiceIdentify) ..................................... 2-36
2.2.13 DTM Enhance Capability (DTMEnhanceCapa) ....................................... 2-37
2.2.14 E-UTRAN CCN support (EUtranCCN).................................................... 2-38
2.2.15 Duration of judging from concurrent to special service
(ConcurrentJudge0) .............................................................................. 2-39
2.2.16 Number of llc judging from concurrent to special service
(ConcurrentJudge1) .............................................................................. 2-40
2.2.17 Duration of judging from special to non-special service
(ConcurrentJudge2) .............................................................................. 2-41
2.2.18 Number of llc judging from special to non-special service
(ConcurrentJudge3) .............................................................................. 2-42
2.2.19 If get Utran classmrak information from UE (GetUtranClass) ................... 2-43
2.3 Other Parameters............................................................................................. 2-45
2.3.1 Supervision Timer of LCS (LcsSuperVision) ............................................. 2-45
2.3.2 Radio Timer of LCS (LcsRadio) ............................................................... 2-46
2.3.3 LCS wait intra BSS handover timer (LcsWaitInTraHO) .............................. 2-47
2.3.4 Monitor physical context request (RmsT9108) .......................................... 2-48
2.3.5 Timer for waiting message from A-interface (TWaitMsg) ........................... 2-48

II

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


2.3.6 Timer for RANCSEST waiting (TWaitRancsEst)........................................ 2-49
2.3.7 Timer for RANCSCLECOM waiting (TWaitRancsCleCom)......................... 2-51
2.3.8 Timer for CCM waiting (CcmWaitTimer) ................................................... 2-52
2.3.9 Get static parameter timer (GetStaticParamTimer).................................... 2-53
2.3.10 Starting time for oriented retry (RmsT10) ............................................... 2-54
2.3.11 TFO Enable (TFOControl_0) ................................................................. 2-55
2.3.12 External cell load notify (Info_0_0) ......................................................... 2-56
2.3.13 Neighbor cell load valid duration (Info_0_1)............................................ 2-57
2.3.14 LMU build request deal or not (Info_1_0) ............................................... 2-58
2.3.15 MBMS request deal or not (Info_1_1) .................................................... 2-59
2.3.16 Channel request reserved field deal or not (Info_1_2) ............................. 2-60
2.3.17 MS power hold in handover option (Info_0_9)......................................... 2-60
2.3.18 Signal level threshold of target cell (Info_0_10)....................................... 2-62
2.3.19 Iur-G interface support (IurgSupport) ..................................................... 2-63
2.3.20 Overload threshold of non real-time load (NRTThs_0)............................. 2-64
2.3.21 High threshold of non real-time load (NRTThs_1) ................................... 2-65
2.3.22 Low threshold of non real-time load (NRTThs_2) .................................... 2-66
2.3.23 On demand mode switch of information exchange
(IurgSwitchGroup_0) ............................................................................. 2-67
2.3.24 On modification mode switch of information exchange
(IurgSwitchGroup_1) ............................................................................. 2-68
2.3.25 On demand mode switch of common measurement
(IurgSwitchGroup_2) ............................................................................. 2-69
2.3.26 Periodic mode switch of common measurement (IurgSwitchGroup_3) ..... 2-70
2.3.27 Immediate assignment repeat (ImmAssRep) .......................................... 2-71
2.3.28 Immediate assignment priority (ImmAssPrio).......................................... 2-72
2.3.29 Paging repeat number (PagRep) ........................................................... 2-73
2.3.30 Timer of waiting for IPGB changing over (TIPGBChgWait) ...................... 2-74
2.3.31 restricted time after continuous IPGB changing over
(TIPGBConChglmt) ............................................................................... 2-75
2.3.32 Info_3 .................................................................................................. 2-76
2.3.33 Info_6 .................................................................................................. 2-77
2.3.34 Threshold of UPUDSP Dynamic Adjustment (Info_7) .............................. 2-77
2.4 Channel Allocation Control Parameters.............................................................. 2-78
2.4.1 Dynamic HR support indication (DynaHREnable) ..................................... 2-78
2.4.2 HR channel fragment repackaging support (HRDfragSupport)................... 2-79
2.4.3 User priority for EMLPP (PriThreshold) .................................................... 2-81
2.4.4 Preferred speech version (half) (PreferSpeechVer H) ............................... 2-82

III

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


2.4.5 Preferred speech version (full) (PreferSpeechVer F) ................................. 2-83
2.4.6 Reserved channel first (RsvChanFirst)..................................................... 2-84
2.4.7 EMLPP channel reserved rate (EMLPPThs)............................................. 2-85
2.4.8 TrxPSBusyThs (TrxPSBusyThs).............................................................. 2-86
2.4.9 Resource pool for PS rate (PsAbisThs).................................................... 2-88
2.4.10 Extended uplink dynamic allocation support (ExUpDynSupport) .............. 2-89
2.5 Timer 1 ............................................................................................................ 2-90
2.5.1 Blocking/Unblocking period (T1) .............................................................. 2-90
2.5.2 Global resetting period (T4)..................................................................... 2-92
2.5.3 Protective period for global resetting (T13) ............................................... 2-93
2.5.4 Circuit resetting period on BSS side (T19)................................................ 2-94
2.5.5 Circuit group blocking/unblocking period (T20) ......................................... 2-95
2.5.6 RLSD message receive protection timer (T9101)...................................... 2-96
2.5.7 Channel activation protection timer (RmsT9103) ...................................... 2-97
2.5.8 MSC clear command protection timer (T9104).......................................... 2-98
2.5.9 SCCP connection protection timer (T9105) .............................................. 2-99
2.5.10 Protective time waiting for access (RmsT1) ...........................................2-100
2.5.11 Protection time for applying to channel (RmsT2) ....................................2-102
2.5.12 Protection time for link establishment response (RmsT3) .......................2-103
2.5.13 Protective time that P0 confirms the message HO/ASS COM
(RmsT4) ..............................................................................................2-104
2.5.14 Encryption mode modification time (RmsT5) .........................................2-105
2.5.15 SAPI3 link establishment time (RmsT6) ................................................2-106
2.5.16 External handover protective time (RmsT8)...........................................2-107
2.5.17 Protective time for No.7 signal instantaneous disconnection (T3)............2-108
2.5.18 Protective time that PO responses external handover completion
message (RmsT7) ...............................................................................2-109
2.5.19 HBTS scan begin time (HBTSScanBT) ................................................. 2-110
2.5.20 HBTS scan cycle (HBTSScanCyc)........................................................ 2-111
2.5.21 IP ABIS Pool Band Width Push Down Protection (TBWPushDown) ........ 2-112
2.5.22 IP ABIS Pool Band Width Restore (TBWRestore) .................................. 2-113
2.5.23 Time of waiting an internal HO command (TWaitInternalHoCmd) ............ 2-114
2.5.24 Wait response of bts or btsgroup establish localswitch link
(TWaitLocalSwitch) .............................................................................. 2-116
2.5.25 Wait response of localswitch release link (TWaitLsReleaseAck).............. 2-117
2.5.26 Wait response of localswitch connect (TWaitLSBscConn) ...................... 2-118
2.5.27 Wait request of local switch release link (TWaitLSReleaseReq) .............. 2-119
2.6 Timer 2 ...........................................................................................................2-120

IV

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


2.6.1 Protective time for RF channel release (RmsT9)......................................2-120
2.6.2 Queue period of assignment (RmsT11)...................................................2-121
2.6.3 Acknowledgment interval for periodic status (RmsT12) ............................2-122
2.6.4 Mode modification process time (RmsT13)..............................................2-123
2.6.5 Protective time of UM assignment completion (RmsT14)..........................2-125
2.6.6 Waiting time for oriented retry (RmsT16).................................................2-126
2.6.7 Queue period for handover (RmsTqho)...................................................2-127
2.6.8 First overload period of flow traffic control (mT11)....................................2-128
2.6.9 Second overload period of flow traffic control (mT12)...............................2-129
2.6.10 Time of micro-micro handover delay (Tmicro) ........................................2-131
2.6.11 BSIC decoding period (Tbsic) ...............................................................2-132
2.6.12 Handover protecting timer to WCDMA/FDD (RmsT3121) .......................2-133
2.6.13 Immediate assignment period (RmsT3101) ...........................................2-134
2.6.14 Handover period of source cell (RmsT3103)..........................................2-135
2.6.15 Assignment period (RmsT3107) ...........................................................2-137
2.6.16 TCH Channel release period (RmsT3109).............................................2-138
2.6.17 TCH Channel deactivation delay (RmsT3111)........................................2-139
2.6.18 Continue timer for mode modify (TModeModifyConn) ............................2-140
2.6.19 Handover protecting time to UTRAN (mT7) ...........................................2-141
2.6.20 Time to wait A handover request (TWaitAHoReq) ..................................2-142
2.6.21 Time of destination instance waiting for available resources when forced
disconnection (RmsT15(TForceOccupy))...............................................2-143
2.6.22 Protecting time of FUC response to system message broadcast
(BcProtect) ..........................................................................................2-144
2.6.23 HO performed ack timer (TwaitHoPFMAck) ...........................................2-146
2.6.24 Timer of TRAU frame Synchronization (TuTrauSyn)...............................2-147
2.6.25 Round trip delay (RtdDefault) ...............................................................2-148
2.6.26 Timer to wait a relocation commit MSG from RNC
(TWaitRncRelocComm)........................................................................2-149
2.6.27 Subcell PingPong handover timer (TSCPingPang).................................2-150
2.6.28 Confirm BIPB fault time (TConfBIPBFault) ............................................2-152
2.6.29 Confirm BIPB DSP fault time (TConfBIPBDSPFault)..............................2-153
2.6.30 Confirm LAPD fault time (TConfLapdFault) ...........................................2-153
2.6.31 Confirm LAPD CPU fault time (TConfLapdCpuFault) .............................2-154
2.6.32 Confirm Sunit normal time (TConfSunitNor)...........................................2-155
2.6.33 Paging Interval (PagWaitTime) .............................................................2-156
2.6.34 Time of Cobcch Wait for MR Report (TCobcchWaitMR)..........................2-157
2.6.35 SDCCH Channel release period (TSDRelPeriod)...................................2-158

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


2.6.36 SDCCH Channel deactivation delay (TSDDeactDelay) ..........................2-159
2.7 GPRS Maximum Retrying Times ......................................................................2-160
2.7.1 Max times of BVC block retry (BVCBlkMax) ............................................2-160
2.7.2 Max times of BVC unblock retry (BVCUblkMax) ......................................2-162
2.7.3 MAX times of BVC reset retry (BVCRestMax) .........................................2-163
2.7.4 Max times of NS block retry (NSBlkMax).................................................2-164
2.7.5 Max times of NS unblock retry (NSUnblkMax) .........................................2-165
2.7.6 Max times of NS alive retry (NSAliveMax) ...............................................2-166
2.7.7 Max times of suspend retry (SuspendMax)..............................................2-167
2.7.8 Max times of resume retry (ResumeMax)................................................2-169
2.7.9 Max times of radio access capabilities update retry (UpdateMax) .............2-170
2.7.10 Max times of PFC create retry (DownLoadBssPFCMax) ........................2-171
2.7.11 Max times of PFC modify retry (ModifyBssPFCMax) ..............................2-173
2.7.12 Max of sending PS handover required (PSHoReqMaxNum) ...................2-174
2.8 GPRS Timer ...................................................................................................2-175
2.8.1 BVC block/unblock retry time (BssgpT1) .................................................2-175
2.8.2 BVC reset retry time (BssgpT2)..............................................................2-176
2.8.3 Suspend retry time (BssgpT3) ................................................................2-177
2.8.4 Resume retry time (BssgpT4).................................................................2-179
2.8.5 Access capability update retry time (BssgpT5) ........................................2-180
2.8.6 PFC creating retry time (BssgpT6)..........................................................2-182
2.8.7 PFC modifying retry time (BssgpT8) .......................................................2-183
2.8.8 RIR Timer (TRIR) ..................................................................................2-184
2.8.9 RI Timer (TRI) .......................................................................................2-185
2.8.10 RIAE Timer (TRIAE) ............................................................................2-186
2.8.11 BVC flow control period (CellFcPer) ......................................................2-187
2.8.12 MS flow control period (MsFcPer).........................................................2-189
2.8.13 Timer that monitors block/unblock procedure (NS_T1) ...........................2-190
2.8.14 Timer that monitors reset procedure (NS_T2) ........................................2-191
2.8.15 NC-cycle of NS-VC test process (NS_T3) .............................................2-192
2.8.16 Timer that monitors alive process of NSVC (NS_T4) ..............................2-193
2.8.17 Max attempt period of reset (NS_T5) ....................................................2-194
2.8.18 TFI and USF release timer (T3169) ......................................................2-195
2.8.19 TBF release timer (T3191) ...................................................................2-196
2.8.20 TBF release time of downlink transmission (T3193) ...............................2-198
2.8.21 TBF protect time when radio link failure (T3195) ....................................2-199
2.8.22 PS channel delay release timer (PSRelDelay) .......................................2-201

VI

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


2.8.23 Guards the PS handover required procedure (T12PsHo) .......................2-202
2.8.24 Guard resource release after sending PS HO command
(TwaitRelInPSHo) ................................................................................2-203
2.8.25 Downlink Delay time in signal TBF Mode (SigTBFDlDelayTime) .............2-204
2.8.26 Extendable uplink TBF time in signal TBF Mode (SigTBFExtUlTime) ......2-205
2.8.27 Synchronization timer that ensures source BSS receives both PS and
CS responses (T23) .............................................................................2-206
2.8.28 Synchronization timer that ensures target BSS receives both PS and
CS requests (T24)................................................................................2-206
2.8.29 T3197 (T3197) ....................................................................................2-206
2.9 AMR Half Method Parameters..........................................................................2-206
2.9.1 AMR Half Active Codec Set (AmrHalfAcs)...............................................2-206
2.9.2 Thresholds of AMR (AmrThresholds) ......................................................2-207
2.9.3 Hysteresis of AMR (AmrHysteresis)........................................................2-209
2.9.4 Initial codec mode (IsAmrlCM) ...............................................................2-210
2.9.5 Start mode (AmrStartMode) ................................................................... 2-211
2.9.6 Enable noise control (IsAmrNscb) ..........................................................2-213
2.10 AMR Full Method Parameters ........................................................................2-214
2.10.1 AMR full Active Codec Set (AmrFullAcs) ...............................................2-214
2.10.2 Thresholds of AMR (AmrThresholds) ....................................................2-215
2.10.3 Hysteresis of AMR (AmrHysteresis) ......................................................2-217
2.10.4 Initial codec mode (IsAmrICM) .............................................................2-218
2.10.5 Start mode (AmrStartMode) .................................................................2-219
2.10.6 Enable noise control (IsAmrNscb).........................................................2-221
2.11 GPRS Other Parameters 1 .............................................................................2-222
2.11.1 Cn (Cn) ...............................................................................................2-222
2.11.2 Nn (Nn) ...............................................................................................2-223
2.11.3 Xn (Xn) ...............................................................................................2-225
2.11.4 Max allowed number of continous losses of uplink data blocks
(N3101)...............................................................................................2-226
2.11.5 Times of packet uplink ACK/NACK retries (N3103) ................................2-228
2.11.6 Max allowed number of continous losses of uplink RLC/MAC control
message (N3105) ................................................................................2-229
2.12 GPRS Other Parameters 2.............................................................................2-231
2.12.1 NACC support (NACCSupport).............................................................2-231
2.12.2 Net operation mode (NMO) ..................................................................2-232
2.12.3 Page coordination support (PagCoordination) .......................................2-234
2.12.4 Satellite transmission at GB interface indication (IsStatelliteGB) .............2-235

VII

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


2.12.5 Extended RLC send window allowed (IsWindowExpend) .......................2-236
2.12.6 TBF establish support (TBF_EST) ........................................................2-237
2.12.7 Signal extended uplink TBF support (SIGNAL_EUTBF) .........................2-238
2.12.8 Highest coding scheme of signal TBF (SigTBFMaxCode).......................2-239
2.12.9 Optimized POC service support (PocSupport) .......................................2-240
2.12.10 Highest coding scheme of POC service in GPRS (PocAttSelt_0) ..........2-241
2.12.11 Highest coding scheme of POC service in EGPRS (PocAttSelt_1) ........2-242
2.12.12 Max users of POC service on shared PS channel0
(PSCAPATHS_UL)...............................................................................2-243
2.12.13 Max users of POC service on shared PS channel1
(PSCAPATHS_DL)...............................................................................2-244
2.12.14 Service UTRAN CCO support (PSUTRANCCOSupp) ..........................2-245
2.12.15 LLC Transfer Support (LLCTranSupport_0~LLCTranSupport_15) .........2-246
2.12.16 LLC Pre-Transfer on NACC (Info_1_10)..............................................2-248
2.12.17 PDU buffer time (Info_1_16)...............................................................2-248
2.12.18 Choose PS route by NSVC (PSRouteByNSVC)...................................2-250
2.12.19 Enable PS Uplink Power Control In Establishment Phase
(PSUlPwrCtlInEsta)..............................................................................2-251
2.13 BVC Flow Control Parameters........................................................................2-252
2.13.1 BVC flow control support (BVCFlowCtrl) ...............................................2-252
2.13.2 MS flow control support (MSFlowCtrl) ...................................................2-253
2.13.3 Flow control mode (FlowCtrlMode) .......................................................2-254
2.13.4 Parameter of Flow control mode 1 (FlowCtrlMode1Para) .......................2-255
2.13.5 Parameter of Flow control mode 2 (FlowCtrlMode2Para) .......................2-256
2.13.6 BVC flow control R MIN value (BVCFlowCtrlRMin) ................................2-258
2.13.7 MS flow control R MIN value (MSFlowCtrlRMin) ....................................2-259
2.13.8 Support of PFC flow control procedures (PFCFlowCtrl) ..........................2-260
2.13.9 Coefficient of BVC bucket size (Info_2_0) .............................................2-261
2.13.10 Coefficient of MS bucket (Info_2_16) ..................................................2-262
2.13.11 CBL in BVC/MS flow control (Info_1_9) ...............................................2-263
2.14 FUC Flow Control Map Parameters ................................................................2-264
2.14.1 Flow control reason (ChlReqRejBmp) ...................................................2-264
2.14.2 Emergency Call...................................................................................2-265
2.14.3 Call Rebuilt .........................................................................................2-266
2.14.4 Call Response.....................................................................................2-267
2.14.5 Calling ................................................................................................2-268
2.14.6 Location Update ..................................................................................2-269
2.14.7 GPRS Access .....................................................................................2-270

VIII

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


2.14.8 Restore...............................................................................................2-272
2.14.9 Flow Control Map Slim Adjust...............................................................2-273
2.15 EDGE Parameters.........................................................................................2-274
2.15.1 PFC support (PFCSupport) ..................................................................2-274
2.15.2 R99 Ind (R99Ind).................................................................................2-275
2.15.3 Support of enhanced radio status procedures (EnRadioStu)...................2-276
2.15.4 RS (RS) ..............................................................................................2-277
2.15.5 RR (RR) .............................................................................................2-279
2.15.6 RA (RA) ..............................................................................................2-280
2.15.7 RM (RM).............................................................................................2-281
2.15.8 RB (RB) ..............................................................................................2-282
2.15.9 RG (RG) .............................................................................................2-283
2.15.10 RE (RE) ............................................................................................2-285
2.15.11 ABIS resource dynamic manage (Info_1_8).........................................2-286
2.15.12 FANR in uplink TBF support (Info_4_0) ...............................................2-287
2.15.13 FANR in downlink TBF support (Info_4_1)...........................................2-288
2.15.14 DLDC support (Info_4_2) ...................................................................2-289
2.15.15 RTTI support (Info_4_3) .....................................................................2-290
2.15.16 EGPRS2-A support (Info_4_4) ...........................................................2-291
2.15.17 EGPRS prior to GPRS Support (Info_4_6) ..........................................2-292
2.15.18 Allocating weights of EGPRS (Info_4_7) .............................................2-293
2.16 eMLPP Set Parameters .................................................................................2-295
2.16.1 Strategy for preemption when assign (AssPreemptstrategy)...................2-295
2.16.2 Strategy for preemption when handover (HoPreemptstrategy) ................2-296
2.16.3 Max forced handover times when assign (AssForcedHoTry)...................2-297
2.16.4 Max forced handover times when handover (HoForcedHoTry)................2-298
2.16.5 Max forced release times when assign (AssForcedRelTry).....................2-299
2.16.6 Max forced release times when handover (HoForcedRelTry) ..................2-300
2.16.7 Preemption duration when assign (AssPreempTimer) ............................2-301
2.16.8 Preemption duration when handover (HoPreempTimer) .........................2-302
2.16.9 Timer for start forced release when assign (AssForceRelTimer)..............2-303
2.16.10 Timer for start forced release when handover (HoForceRelTimer).........2-305
2.16.11 Interval for search forced handover target when assign
(AssForceHoInterval) ...........................................................................2-306
2.16.12 Interval for search forced handover target when handover
(HoForceHoInterval).............................................................................2-307
2.16.13 Interval for search forced release target when assign
(AssForceRelInterval)...........................................................................2-308

IX

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


2.16.14 Interval for search forced release target when handover
(HoForceRelInterval) ............................................................................2-309
2.16.15 Queue timer for assign (RmsT11) .......................................................2-310
2.16.16 Queue timer for handover (RmsTqho) ................................................. 2-311
2.16.17 Queue indicate when assign (QueueIndAss) .......................................2-312
2.16.18 Queue allowed when handover (QueueIndHo) ....................................2-313
2.16.19 Forced release indicate when assign (PreemptionIndAss) ....................2-314
2.16.20 Forced release allowed when handover (PreemptionIndHo) .................2-315
2.16.21 Forced handover indication for assign (ForcedHolndAss) .....................2-316
2.16.22 Forced handover indication for handover (ForcedHolndHo) ..................2-317
2.16.23 Wait resource timer after forced release (ForceRelWait).......................2-318
2.16.24 Wait resource timer after forced handover (ForceHoWait, 100ms).........2-320
2.16.25 Enough low priority for preemption (LowestPriority)..............................2-321
2.16.26 Enough call duration for preemption (LongCallDuration).......................2-322
2.16.27 Forced handover target penalty time (ForceHoPenalty)........................2-323
2.16.28 Priority of emergency service (EmergServicelPrio)...............................2-324
2.17 User Access Flow Control Parameters............................................................2-325
2.17.1 Access class parameter config select (AccConfigSelect)........................2-325
2.17.2 First barred class 0 ~ First barred class 3
(FirstBarredClass_0~FirstBarredClass_3)..............................................2-326
2.17.3 Barred class windows 0 ~ Barred class windows 3
(BarredClassWindows_0~BarredClassWindows_3)................................2-327
2.17.4 Barred time step 0 ~ Barred time step 3
(BarredTimeStep_0~BarredTimeStep_3) ...............................................2-329
2.17.5 Access Control (AccessControl) ...........................................................2-330
2.18 UPPB Resource Alarm Parameters ................................................................2-331
2.18.1 Enable UPPB resource alarm (UppbResAlarmEnable)...........................2-331
2.18.2 Alarm threshold of failure ratio for allocating memory
(UppbResAlarmThs_0).........................................................................2-332
2.18.3 Alarm threshold of use ratio for mac instance (UppbResAlarmThs_1) ......2-333
2.18.4 Alarm threshold of use ratio for bssgp instance and tlli index
(UppbResAlarmThs_2).........................................................................2-334
2.18.5 Alarm threshold of use ratio for mac-tlli index (UppbResAlarmThs_3) ......2-335
2.18.6 Alarm threshold of use ratio for radio channel instance
(UppbResAlarmThs_4).........................................................................2-336
2.18.7 Alarm threshold of use ratio for TS instance (UppbResAlarmThs_5) .......2-337
2.18.8 Duration of exceeding alarm threshold (OverThsDuration) .....................2-339
2.19 AMR-WB Parameter ......................................................................................2-340
2.19.1 Thresholds of AMR-WB (AmrWBThresholds) ........................................2-340

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


2.19.2 Hysteresis of AMR-WB (AmrWBHysteresis) ..........................................2-341
2.20 Iur-g Parameter .............................................................................................2-342
2.20.1 Report characteristics (ReportType)......................................................2-342
2.20.2 Report periodicity unit (RepPeriodUnit) .................................................2-343
2.20.3 Report periodicity value (RepPeriodValue) ............................................2-344
2.20.4 Load/RT Load/NRT Load measurement threshold 1
(MeasThr1_0~MeasThr1_2) .................................................................2-345
2.20.5 Load/RT Load/NRT Load measurement threshold 2
(MeasThr2_0~MeasThr2_2) .................................................................2-346
2.20.6 Measurement hysteresis time (MeasHys,10ms).....................................2-347
2.20.7 Event report periodicity (EveRepPeriod,10ms) ......................................2-348
2.20.8 Measurement timer (MeasTimer,10ms) .................................................2-349
2.20.9 Measurement max retry number (MeasMaxRetryNum) ..........................2-350
2.20.10 Information report type (InfoReportType) .............................................2-351
2.20.11 Measurement type (MeasType)...........................................................2-352
2.20.12 Support of 2g request Iur-g (IurgOf2gReq) ..........................................2-352
2.21 Ater Timer Parameters...................................................................................2-353
2.21.1 Ater wait SCCP connection timer (TAterWaitConn) ................................2-353
2.21.2 Ater wait resource timer (TWaitAterRes) ...............................................2-355
2.21.3 Ater wait resource release timer (TAterWaitRel).....................................2-356
2.21.4 Ater handover monitor timer (TAterMoniterHO)......................................2-357
2.21.5 Ater wait resource acknowledge timer (TWaitAterResAck) .....................2-358
2.21.6 Ater block circuit timer (TAterCicBlk) .....................................................2-359
2.21.7 Ater block circuit group timer (TAterBlkCicGrp) ......................................2-360
2.21.8 Ater reset circuit timer (TAterRstCic) .....................................................2-361
2.21.9 Ater reset timer (TAterRst) ...................................................................2-362
2.21.10 Ater reset guard timer (TITCRst).........................................................2-363
2.21.11 Ater block a interface circuit timer (TBlkACic).......................................2-364
2.21.12 Ater block a interface circuit group timer (TBlkACicGrp) .......................2-366

Chapter 3 External Cell Parameters.......................................................... 3-1


3.1 GERAN External Cell Parameters ....................................................................... 3-1
3.1.1 User Label ............................................................................................... 3-1
3.1.2 External cell ID (Geran EcellID)................................................................. 3-2
3.1.3 Cell type (CellType) .................................................................................. 3-3
3.1.4 MCC (MCC)............................................................................................. 3-4
3.1.5 MNC (MNC)............................................................................................. 3-5
3.1.6 FreqBand (FreqBand)............................................................................... 3-6
3.1.7 BCCH arfcn (BcchArfcn) ........................................................................... 3-7

XI

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


3.1.8 LAC (LAC) ............................................................................................... 3-8
3.1.9 CI (CI) ..................................................................................................... 3-9
3.1.10 NCC (NCC).......................................................................................... 3-10
3.1.11 BCC (BCC) ...........................................................................................3-11
3.1.12 GPRS service support (PsSupport)........................................................ 3-12
3.1.13 Cell reselection offset (ReselOff_0)........................................................ 3-13
3.1.14 Cell reselection offset (ReselOff_1)........................................................ 3-14
3.1.15 Cell reselection temporary offset (TempOffset_0).................................... 3-15
3.1.16 Cell reselection temporary offset (TempOffset_1).................................... 3-17
3.1.17 Penalty time of cell reselection (PenalTime_0)........................................ 3-18
3.1.18 Penalty time of cell reselection (PenalTime_1)........................................ 3-20
3.1.19 HSC exist (HCS_EXIST_0) ................................................................... 3-21
3.1.20 HSC exist (HCS_EXIST_1) ................................................................... 3-22
3.1.21 Threshold of HSC signal level (HCS_THR_0)......................................... 3-23
3.1.22 Threshold of HSC signal level (HCS_THR_1)......................................... 3-24
3.1.23 HCS priority (PrioClass_0) .................................................................... 3-25
3.1.24 HCS priority (PrioClass_1) .................................................................... 3-26
3.1.25 Allow SOLSA MS to access (EXC_ACC) ............................................... 3-27
3.1.26 Cell reselection status (CellBarAc2) ....................................................... 3-28
3.1.27 LSA ID (LSA_Id)................................................................................... 3-31
3.1.28 RAC (RAC) .......................................................................................... 3-32
3.1.29 Access minimal signal level (RxLevAsMin_0) ......................................... 3-33
3.1.30 Access minimal signal level (RxLevAsMin_1) ......................................... 3-35
3.1.31 Maximum initial access signal level (MsTxMaxCCH_0) ........................... 3-36
3.1.32 Maximum initial access signal level (MsTxMaxCCH_1) ........................... 3-38
3.2 UTRAN External Cell Parameters...................................................................... 3-40
3.2.1 Basic property........................................................................................ 3-40
3.2.2 Others ................................................................................................... 3-54
3.3 LTE External Cell Parameters ........................................................................... 3-65
3.3.1 User label (UserLabel)............................................................................ 3-65
3.3.2 LTE CELL Identification (LTECELLID)...................................................... 3-66
3.3.3 MCC (MCC)........................................................................................... 3-67
3.3.4 MNC (MNC)........................................................................................... 3-68
3.3.5 LTE CELL Identification (ENBID) ............................................................. 3-69
3.3.6 LTE CELL TYPE (CellTypeLTE) .............................................................. 3-70
3.3.7 Tracking area code (TAC) ....................................................................... 3-71
3.3.8 Physical layer cell identity of LTE CELL (PCID) ........................................ 3-72

XII

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


3.3.9 The attribute of LTE NodeB (ENBInd) ...................................................... 3-72
3.3.10 specified EARFCN of E-UTRAN cells (ArfcnLTE).................................... 3-73
3.3.11 the minimum value of the channel bandwidth (MeasureBandwidth) .......... 3-74

Chapter 4 Cell Parameters......................................................................... 4-1


4.1 Basic Parameters 1 ............................................................................................ 4-1
4.1.1 User Label ............................................................................................... 4-1
4.1.2 Site ID ..................................................................................................... 4-2
4.1.3 BSC标识 (BSCID) .................................................................................... 4-3
4.1.4 BTS ID (BtsId).......................................................................................... 4-4
4.1.5 Cell Type (CellType) ................................................................................. 4-6
4.1.6 MCC (MCC)............................................................................................. 4-7
4.1.7 MNC (MNC)............................................................................................. 4-8
4.1.8 LAC (LAC) ............................................................................................... 4-9
4.1.9 CI (CI) ................................................................................................... 4-10
4.1.10 NCC (NCC)...........................................................................................4-11
4.1.11 BCC (BCC) .......................................................................................... 4-12
4.1.12 Frequency band (FreqBand) ................................................................. 4-13
4.1.13 Subcell used (SubCellUsed).................................................................. 4-14
4.1.14 Frequency Band of subcell (SubFreqBand) ............................................ 4-15
4.1.15 ARFCN list (CaArfcnList) ...................................................................... 4-16
4.1.16 GPRS service support (PsSupport)........................................................ 4-17
4.1.17 Dynamic HR support indication (DynaHREnable) ................................... 4-18
4.1.18 Dynamic HR channel allocation algorithm (DHRAlgrithm)........................ 4-19
4.1.19 CBC support (SmsCbUsed) .................................................................. 4-21
4.1.20 Threshold for TRX switched from FR to HR (HRThs) .............................. 4-22
4.1.21 PS busy threshold (Info_1_16) .............................................................. 4-23
4.1.22 Use cell AMR parameter (UseCellAMRParam) ....................................... 4-24
4.1.23 Support AMR-WB (SUPPORTAMRWB) ................................................. 4-25
4.1.24 Support CS paging prefer PS Assignment (CsPagingPrefer) ................... 4-26
4.1.25 Common control channel configuration (CcchConf) ................................ 4-27
4.1.26 Template file......................................................................................... 4-29
4.2 Basic Parameters 2 .......................................................................................... 4-30
4.2.1 TA Max (TaMax) ..................................................................................... 4-30
4.2.2 TA MIN (TaMin) ...................................................................................... 4-31
4.2.3 TA allowed (TaAllowed)........................................................................... 4-32
4.2.4 PCH load indication period (CcchLoadIndPrd).......................................... 4-33
4.2.5 Periodical location updating timer (T3212) ............................................... 4-34

XIII

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


4.2.6 Protection period for access attempt (T3122) ........................................... 4-36
4.2.7 Multi-band report indication (MulbandReport) ........................................... 4-37
4.2.8 Coefficient of BVC bucket size (Info_2_0) ................................................ 4-39
4.2.9 CCCH load indication (RACH) (CcchLoadINDThs_0)................................ 4-40
4.2.10 CCCH load indication (PCH) (CcchLoadINDThs_1) ................................ 4-41
4.2.11 8PSK modulating power attenuation level (Tn7Lowerlevel)...................... 4-42
4.2.12 Repeated ACCH support (RepeatACCH) ............................................... 4-43
4.2.13 Start PA power off (StartPAPowerOff) .................................................... 4-44
4.2.14 Switch flag of cell TRX power off (StartTRXPowerOff)............................. 4-45
4.2.15 Support intelligent cell shuttingdown (CellShuttingDown) ........................ 4-46
4.2.16 Upper Site Id (UPSITEID) ..................................................................... 4-48
4.2.17 Upper Cell Id (UPBTSID) ...................................................................... 4-49
4.2.18 AMR codec adjust mode (AmrAdjMode)................................................. 4-50
4.2.19 AMR codec adjust interval (AmrAdjInterval)............................................ 4-51
4.2.20 HR channel fragment repacking support (HRDfragSupport)..................... 4-52
4.2.21 Idle FR threshold For HR defrag (Info_0_8)............................................ 4-53
4.2.22 Busy threshold for HR defrag (Info_1_24) .............................................. 4-55
4.2.23 HR channel percentage threshold (HRTsPercentage) ............................. 4-56
4.2.24 Threshold of AMR HR (AmrHRThs) ....................................................... 4-57
4.2.25 Handover from FR to HR due to high load support (FRThrHoSupport) ..... 4-58
4.2.26 Intra-handover from HR to FR due to bad quality (HRTFRHOSupport) ..... 4-59
4.2.27 Start PA output voltage tuning (Info_0_0) ............................................... 4-60
4.2.28 Enable RRU of cell power off (RRUPowerOff) ........................................ 4-61
4.2.29 The switch of CIR report (ReportCIR) .................................................... 4-62
4.2.30 The L2 frame of Lapdm fill random value (LapdmL2Cfg) ......................... 4-63
4.2.31 NCC permitted (NccPermitted) .............................................................. 4-64
4.2.32 Support allocating channel by TA (AllocChlByTA) ................................... 4-65
4.2.33 The TA threshold of allocating channel in BCCH (TaThsOfBCCH)............ 4-66
4.2.34 Cell PowerOff based on traffic load (PwDownLoadInd)............................ 4-67
4.2.35 Support handover from HR to FR due to low load (HRTFRHOSupport2) ..... 4-68
4.2.36 TRX PowerOff time bitmap (DownPowerBmp)........................................ 4-69
4.3 Basic Parameters 3 .......................................................................................... 4-70
4.3.1 Average bursts count surveyed by RACH (AvgSlots) ................................ 4-70
4.3.2 RACH receiving signal level threshold for busy burst (RachBusyThs) ........ 4-71
4.3.3 RACH load indication period (OverloadPrd) ............................................. 4-72
4.3.4 BA show (BcchBaInd)............................................................................. 4-73
4.3.5 MIN received signal level to access (RxLevAccessMin) ............................ 4-74

XIV

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


4.3.6 MAX number of re-transmitting events times (MRetrans)........................... 4-76
4.3.7 Number of slots to spread transmission (TxInteger) .................................. 4-78
4.3.8 Control channel MAX power level (MsTxPwrMaxCch)............................... 4-79
4.3.9 Number of multi-frames of the PCH (BsPaMframs) ................................... 4-81
4.3.10 Interval of SDCCH re-sending PHY info message (T3105d) .................... 4-82
4.3.11 Interval of TCH re-sending PHY info message (T3105f) .......................... 4-84
4.3.12 MAX resending times for physical information (NY1)............................... 4-85
4.3.13 Number of blocks reserved for AGCH (BsAgBlkRes) .............................. 4-86
4.3.14 BSS radio link timer's max value for AMR FR
(BsRadioLkTmOutForAMRFR) .............................................................. 4-87
4.3.15 BSS radio link timer's max value for AMR HR
(BsRadioLkTmOutForAMRHR) .............................................................. 4-89
4.3.16 BSS radio link timer’s max value for AMR WFS
(BsRadioLkOutAMRWFS) ..................................................................... 4-90
4.3.17 BSS radio link timer's max value for AMR OWFS
(BsRadioLkOutAMROWFS)................................................................... 4-91
4.3.18 BSS radio link timer’s max value for AMR OWHS
(BsRadioLkOutAMROWHr) ................................................................... 4-93
4.3.19 LAPDM timer used for controlling the SDCCH channel. (T200_0)............ 4-94
4.3.20 Lapdm Timer for controlling FACCH/full rate channel (T200_1)................ 4-96
4.3.21 Lapdm Timer for controlling FACCH/half rate channel (T200_2)............... 4-97
4.3.22 Lapdm Timer for controlling SACCH with tch sapi0 channel (T200_3) ...... 4-98
4.3.23 Lapdm Timer for controlling SACCH with sdcch channel (T200_4)........... 4-99
4.3.24 Lapdm Timer for controlling sdcch sapi3 channel (T200_5) ....................4-100
4.3.25 Lapdm Timer for controlling SACCH with TCH sapi3 channel
(T200_6) .............................................................................................4-102
4.4 Optional Parameters........................................................................................4-103
4.4.1 Early class-mark sending control (ECSC)................................................4-103
4.4.2 IMSI attach/detach allowed (ImsIadAllowed) ...........................................4-104
4.4.3 Cell bar access (CellBarAccess).............................................................4-105
4.4.4 Call re-establishment allowed (CallReestablish) ......................................4-106
4.4.5 Downlink discontinuous transmission allowed (DtxDwlink) .......................4-107
4.4.6 Uplink discontinuous transmission (DtxUplinkBcch) .................................4-109
4.4.7 Emergency call allowed (EmergencyCall) ............................................... 4-110
4.4.8 Support Emergency call preemption (EmergCallPreempt)........................ 4-111
4.4.9 Cell bar qualify (CellBarQualify).............................................................. 4-113
4.4.10 Access class parameter config select (AccConfigSelect)........................ 4-114
4.4.11 Cell access control support (UseCellAcc) .............................................. 4-115

XV

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


4.4.12 Adopt Precise Paging for Circuit Switched Service (CsPrecisePag) ........ 4-116
4.4.13 Adopt Precise Paging for Packet Switched Service (PsPrecisePag)........ 4-117
4.4.14 VPC Age Time (VpcAgeTime) .............................................................. 4-118
4.4.15 HBTS proofread support (HBTSScanSupport)....................................... 4-119
4.4.16 RSSI threshold (RSSIThrd) ..................................................................4-120
4.4.17 Proofread freqband type (GSM1900Support) ........................................4-121
4.4.18 Access Control (AccessControl) ...........................................................4-122
4.4.19 Range of HBTS BARANG (HBTSRange) ..............................................4-124
4.4.20 Paging Hole Timer (PagHoleTimer) ......................................................4-125
4.4.21 Mobile Orignated Short Message intercept (MOSmsIntercept)................4-126
4.4.22 Mobile Terminated Short Message intercept (MTSmsIntercept) ..............4-127
4.4.23 NCC Config Parameter (NccCfgPara) ...................................................4-128
4.4.24 RxQual Threshlod (RQThreshold) ........................................................4-129
4.4.25 TCH Allocation Threshold For Dual-Frequency Network
(DualFreqNetTchThs) ...........................................................................4-130
4.4.26 Diversity Combine Mode (DivCombMode).............................................4-131
4.4.27 SubCell Channel Allocation Parameter (CSAllocSC)..............................4-131
4.4.28 Is Enhanced Dual-Frequency Network Support (IsDualFreqSup) ............4-132
4.5 Cell Selection Parameters................................................................................4-133
4.5.1 the maximum thresholds of Utran reselection (UtranHighThresh) .............4-133
4.5.2 the minimum thresholds of Utran reselection (UtranLowThresh) ...............4-134
4.5.3 Minimum RX level for Utran cells (UtranQRXLEVMIN) .............................4-135
4.5.4 The maximum thresholds of EUtran reselection (EUtranHighThresh) ........4-136
4.5.5 The minimum thresholds of EUtran reselection (EUtranLowThresh)..........4-137
4.5.6 Minimum RX level for EUtran cells (EUtranQRXLEVMIN) ........................4-138
4.5.7 The maximum RSRQ thresholds for EUtran reselection
(EUtranHighThreshQ) ..........................................................................4-139
4.5.8 The minimum RSRQ thresholds of EUtran reselection
(EUtranLowThreshQ) ...........................................................................4-140
4.5.9 Minimum RSRQ for EUtran cells (EUtranQQUALMIN) .............................4-141
4.5.10 Additional reselection parameter indication (AdditionReselPI).................4-142
4.5.11 Cell reselection parameter indication (CellReselPI) ................................4-143
4.5.12 Cell reselection offset (ReselOffset) ......................................................4-144
4.5.13 Temporary offset (TemporaryOffset)......................................................4-147
4.5.14 Penalty time (PenaltyTime) ..................................................................4-148
4.5.15 Cell reselecting hysteresis level (ReselHysteresis).................................4-149
4.5.16 New setup cause indication (NECI).......................................................4-151
4.5.17 Power offset indication (PowerOffsetInd)...............................................4-153

XVI

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


4.5.18 Power offset (PowerOffset) ..................................................................4-154
4.5.19 Based on priority Cell re-selection Switch (PrioReselSupport) ................4-155
4.5.20 Priority of GSM cells (ServCellPrio) ......................................................4-156
4.5.21 Threshold of serving cell that used by priority Cell re-selection algorithm
(THRESHPRIORYSEARCH) ................................................................4-156
4.5.22 Threshold that Allow MS re-select to lower priority Cell
(THRESHGSMLOW)............................................................................4-157
4.5.23 Hysteresis of priority reselection algorithm (HysteresisofPRiority) ...........4-158
4.5.24 Time hysteresis of priority reselection algorithm
(TimeHysteresisofReS) ........................................................................4-159
4.5.25 The default priority of Utran Cells (UtranDefaultPrio)..............................4-160
4.5.26 The default priority of EUtran Cells (EUtranDefaultPrio) .........................4-161
4.6 Service Process Additional Parameters ............................................................4-162
4.6.1 Directed retry indication (DrInd_0) ..........................................................4-162
4.6.2 External directed retry indication (DrInd_1)..............................................4-163
4.6.3 Queue allowed when assign (QueueInd_0) .............................................4-164
4.6.4 Queue allowed when handover (QueueInd_1).........................................4-165
4.6.5 Preemption allowed when assign (PreemptionInd_0) ...............................4-166
4.6.6 Preemption allowed when handover (PreemptionInd_1)...........................4-168
4.6.7 When assigned forced handover (ForcedHoInd_0) ..................................4-169
4.6.8 Forced handover allowed when handover (ForcedHoInd_1) .....................4-170
4.6.9 Number of candidate cells for handover (CandidateNum).........................4-171
4.6.10 Fast average indication (FastAvg) ........................................................4-172
4.6.11 BCCH switch allowed (CanBcchExch)...................................................4-173
4.6.12 SDCCH dynamic configuration allowed (CanSdcchDyn) ........................4-174
4.6.13 Minimal resource threshold (ResourceThs) ...........................................4-175
4.6.14 Base-band hopping TRX exchange support (Info_0_3) ..........................4-176
4.6.15 Support NCell of channel release (NCELLINDOFCHLREL) ....................4-177
4.6.16 RelEUtranStrategy (RelEUtranStrategy)................................................4-178
4.6.17 RelEUtranPrio (RelEUtranPrio).............................................................4-179
4.6.18 Allowed FACCH call setup after emergency call (FacchCallInd_0) ..........4-180
4.6.19 Allowed FACCH call setup when page respond (FacchCallInd_1) ...........4-181
4.6.20 Allowed call setup on FACCH (FacchCallInd_2) ....................................4-182
4.6.21 Allowed call reestablished on FACCH (FacchCallInd_3).........................4-183
4.7 System Parameters .........................................................................................4-184
4.7.1 Interference average period (InterfAvgPrd)..............................................4-184
4.7.2 Interference Band Boundary (InterfBoundary_0)......................................4-185
4.7.3 Interference Band Boundary (InterfBoundary_1)......................................4-187

XVII

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


4.7.4 Interference Band Boundary (InterfBoundary_2)......................................4-188
4.7.5 Interference Band Boundary (InterfBoundary_3)......................................4-190
4.7.6 Interference Band Boundary (InterfBoundary_4)......................................4-191
4.7.7 Interference Band Boundary (InterfBoundary_5)......................................4-193
4.7.8 MAX value of MS Radio link timeout (MsRadioLKTmOut) ........................4-194
4.7.9 Radio link failure criterion (ConFailCriterion) ...........................................4-195
4.7.10 MAX value of BSS Radio link timeout (BsRadioLKTmOut) .....................4-197
4.7.11 Receiving level threshold (RxLevThs) ...................................................4-198
4.7.12 Receiving quality threshold (RxQualThs)...............................................4-199
4.7.13 Radio link failure checking period (RxLevQualprd) .................................4-200
4.7.14 AMR FR (MsRadioLkTmOutAMRFR)....................................................4-201
4.7.15 AMR HR (MsRadioLkTmOutAMRHR) ...................................................4-203
4.7.16 AMR WFS (MsRadioLkOutAMRWFS)...................................................4-204
4.7.17 AMR-WB OWFS (MsRadioLkOutAMROWFS) .......................................4-205
4.7.18 AMR-WB OWHR (MsRadioLkOutAMROWHR)......................................4-206
4.8 AMR Half Method Parameters..........................................................................4-207
4.8.1 AMR Half Active Codec Set (AmrHalfAcs)...............................................4-207
4.8.2 Thresholds of AMR (AmrThresholds) ......................................................4-208
4.8.3 Hysteresis of AMR (AmrHysteresis)........................................................4-210
4.8.4 Initial codec mode (IsAmrlCM) ............................................................... 4-211
4.8.5 Start mode (AmrStartMode) ...................................................................4-212
4.8.6 Enable noise control (IsAmrNscb) ..........................................................4-214
4.9 AMR Full Method Parameters ..........................................................................4-215
4.9.1 AMR full Active Codec Set (AmrFullAcs) .................................................4-215
4.9.2 Thresholds of AMR (AmrThresholds) ......................................................4-216
4.9.3 Hysteresis of AMR (AmrHysteresis)........................................................4-218
4.9.4 Initial codec mode (IsAmrICM) ...............................................................4-219
4.9.5 Start mode (AmrStartMode) ...................................................................4-221
4.9.6 Enable noise control (IsAmrNscb) ..........................................................4-222
4.10 Other Parameters..........................................................................................4-223
4.10.1 Preprocessing indication (Preprocess) ..................................................4-223
4.10.2 Reserved rate of EMLPP (EMLPPThs) .................................................4-225
4.10.3 Use cell EMLPP Threshold (UseCellEmlppThs).....................................4-226
4.10.4 Frequency offset correct support (Info_0_1) ..........................................4-227
4.10.5 Maximum power on handover command support (Info_0_2)...................4-228
4.10.6 MR Report Time Bmp (MrRptTimeBmp)................................................4-229
4.10.7 Non Cipher Mode support (CipherMode_0_0) .......................................4-230

XVIII

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


4.10.8 Cipher Mode support A5/1 (CipherMode_0_1).......................................4-231
4.10.9 Cipher Mode support A5/2 (CipherMode_0_2).......................................4-232
4.10.10 Cipher Mode support A5/3 (CipherMode_0_3).....................................4-233
4.10.11 Cipher Mode support A5/4 (CipherMode_0_4) .....................................4-234
4.10.12 Cipher Mode support A5/5 (CipherMode_0_5).....................................4-235
4.10.13 Cipher Mode support A5/6 (CipherMode_0_6).....................................4-236
4.10.14 Cipher Mode support A5/7 (CipherMode_0_7).....................................4-237
4.10.15 Cipher mode priority1 ~ Cipher mode priority7 (CipherMode_1~
CipherMode_7) ....................................................................................4-238
4.10.16 Channel Select Strategy (ChanSelectStrategy)....................................4-239
4.10.17 Info_3 ...............................................................................................4-241
4.10.18 Info_4 ...............................................................................................4-241
4.10.19 Info_5 ...............................................................................................4-242
4.10.20 Info_6 ...............................................................................................4-243
4.10.21 Info_7 ...............................................................................................4-244
4.11 GPRS Basic Parameters ................................................................................4-245
4.11.1 SGSN ID (SGSNID) .............................................................................4-245
4.11.2 NSEI (NSEI)........................................................................................4-246
4.11.3 BVCI (BVCI)........................................................................................4-247
4.11.4 RAC (RAC) .........................................................................................4-248
4.11.5 PS service busy level (PsBusyLevel) ....................................................4-250
4.11.6 Enable cell PS push down (PSPushDown) ............................................4-251
4.12 GPRS Other Parameters 1.............................................................................4-252
4.12.1 Additional reselection parameter indicator (AddResPI2) .........................4-252
4.12.2 SI13 sending position (Si13Locate).......................................................4-253
4.12.3 Route area color code (RaColor) ..........................................................4-254
4.12.4 Minimal number of idle CS channel (CsChansThs) ................................4-255
4.12.5 Packet access priority threshold (PriAcThr) ...........................................4-256
4.12.6 Packet System Information Send Speed (SendSpeed (PSI2, PSI3,
PSI3BIS, PSI4, PSI5, PSI13, PSI3ter, PSI8, PSI3quater)).......................4-258
4.12.7 Overload report period on PRACH (OvLoadPer)....................................4-259
4.12.8 Link error counter (RLTimeout) .............................................................4-260
4.12.9 PRACH receiving signal level threshold (PrachBusyT) ...........................4-261
4.12.10 Average measuring bursts number on PRACH (MeaAvgSlot) ...............4-262
4.12.11 Buffer threshold of paging message (PccchIndTh_0)............................4-263
4.12.12 Queue length threshold in 64 multi-frame paging period
(PccchIndTh_1) ...................................................................................4-264
4.12.13 PRACH overload threshold ratio (PccchIndTh_2).................................4-265

XIX

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


4.13 GPRS Other Parameters 2.............................................................................4-266
4.13.1 DTM support (DTMSupport) .................................................................4-266
4.13.2 DTM Enhance Capability (DTMEnhanceCapa) ......................................4-267
4.13.3 CCN mode support (CCNActive) ..........................................................4-268
4.13.4 Cell support system message status flow (SIStatusInd) .........................4-269
4.13.5 Allow SOLSA MS to access (Exc_Acc) .................................................4-271
4.13.6 CCCH SplitPGCycle support (SpgcSuport) ...........................................4-272
4.13.7 Extended paging support (EpageMode) ................................................4-273
4.13.8 PSI status support (PsiStatInd).............................................................4-274
4.13.9 Cell support extendable uplink TBF (Ext_UTBF) ....................................4-276
4.13.10 Uplink delay time (UlDelayTime) .........................................................4-277
4.13.11 Interval number of GPRS TBF downlink’s RRBP
(GPRSDIRrbpInterVal) .........................................................................4-278
4.13.12 Interval number of downlink EGPRS TBF’s RRBP
(EGPRSDIRrbpInterVal) .......................................................................4-279
4.13.13 Interval number of uplink GPRS TBF’s ACK (GPRSUlAckInterVal)........4-280
4.13.14 Interval number of uplink EGPRS TBF’s ACK
(EGPRSUlAckInterVal) .........................................................................4-281
4.13.15 Single block assign offset (Info1_0_0) .................................................4-282
4.13.16 Polling retry times (Info1_0_8) ............................................................4-283
4.13.17 Uplink measurement report period (Ulmeasureperiod)..........................4-284
4.13.18 Calculating period of load on PPCH (LoadPer) ....................................4-285
4.13.19 PSI1 sending period (Psi1RepPer) .....................................................4-286
4.13.20 USF granularity (USFGranularity) .......................................................4-287
4.13.21 Extended uplink dynamic allocation support (ExUpDynSupport) ...........4-288
4.13.22 ABIS time slots reserved for packet service (Info_1_0).........................4-289
4.13.23 The MAX of ABIS for GPRS user (Info_1_8)........................................4-291
4.13.24 GPRS initial downlink allocation by multislot class 1 (Info1_1_4)...........4-292
4.13.25 Service UTRAN CCO support (UTRANCCOSupp)...............................4-293
4.13.26 Strategy of servic UTRAN CCO (CCOStrategy) ...................................4-295
4.13.27 Enable no data during extended uplink TBF mode (INFO1_5_0)...........4-296
4.13.28 Downlink TBF pre-establish support (EarlyDlTBFEstSupp)...................4-297
4.13.29 Downlink Delay time in data TBF Mode (DataTBFDlDelayTime) ...........4-298
4.13.30 Extendable uplink TBF time in data TBF Mode (DataTBFExtUlTime) ......4-299
4.14 GPRS Other Parameters 3.............................................................................4-300
4.14.1 C/I (Sc) ...............................................................................................4-300
4.14.2 ARP (Sa) ............................................................................................4-301
4.14.3 THP (St) .............................................................................................4-303

XX

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


4.14.4 PS queuing support (PsQueueInd) .......................................................4-304
4.14.5 Max PS Queue Count (PsMaxQueueInstNum) ......................................4-305
4.14.6 PS preemption support (PsPreemptionInd) ...........................................4-306
4.14.7 3G NACC support (Support3GCCN) .....................................................4-307
4.14.8 PS preempt CS support (PSPrmpCSSupport) .......................................4-308
4.14.9 Maximal resource for POC service (POCSrcThs)...................................4-309
4.14.10 Enable uplink interference decision in NC2 (INFO1_5_1) ..................... 4-311
4.14.11 Enable downlink interference decision in NC2 (INFO1_5_2) ................. 4-311
4.14.12 P of uplink interference decision in NC2 (INFO1_5_3)..........................4-312
4.14.13 N of uplink interference decision in NC2 (INFO1_5_8) .........................4-313
4.14.14 P of downlink interference decision in NC2 (INFO1_5_13)....................4-314
4.14.15 N of downlink interference decision in NC2 (INFO1_5_18) ...................4-315
4.14.16 Quality offset of uplink interference in NC2 (INFO1_5_23)....................4-316
4.14.17 Signal offset of uplink interference in NC2 (INFO1_6_0).......................4-317
4.14.18 Quality offset of downlink interference in NC2 (INFO1_6_5) .................4-318
4.14.19 Signal offset of downlink interference in NC2 (INFO1_6_10).................4-319
4.14.20 Num of samples that calculates average of uplink signal level in NC2
(INFO1_6_15)......................................................................................4-320
4.14.21 Num of samples that calculates average of downlink signal level in
NC2 (INFO1_6_20) ..............................................................................4-321
4.14.22 Num of samples that calculates average of uplink quality level in NC2
(INFO1_6_25)......................................................................................4-322
4.14.23 Num of samples that calculates average of downlink quality level in
NC2 (INFO1_7_0)................................................................................4-323
4.14.24 NC2 Distance Windows (NC2DistanceWindow)...................................4-324
4.14.25 Transform from uplink delay to extend (Info1_1_16).............................4-325
4.14.26 Max Num of resend packet assignment (Info1_1_8).............................4-326
4.14.27 Resource adjust for CS preempt (Info1_1_17) .....................................4-327
4.14.28 Subcell selection of PS channel allocation (PSALLOCSC_0) ................4-328
4.14.29 RXLEV threshold in subcell 1 (PSALLOCSC_1) ..................................4-330
4.14.30 RXLEV threshold in subcell 2 (PSALLOCSC_2) ..................................4-332
4.14.31 Multislot allocation of extended range cell support (Info1_7_13)............4-333
4.14.32 Support resource optimizing by service (SuppResOpByService)...........4-334
4.14.33 RxLev P Value (RxLevP)....................................................................4-335
4.14.34 RxLev N Value (RxLevN) ...................................................................4-336
4.14.35 TA P Value (TaP) ...............................................................................4-337
4.14.36 TA N Value (TaN)...............................................................................4-338
4.14.37 SubCell1 PS Busy Threshold (SubCell1PsChanThs) ...........................4-339

XXI

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


4.14.38 SubCell2 PS Busy Threshold (SubCell2PsChanThs) ...........................4-340
4.14.39 TA threshold for PS channel allocate in subcell1 (TaLevelThs1) ............4-341
4.14.40 TA threshold for PS channel allocate in subcell2 (TaLevelThs2) ............4-342
4.14.41 Resource adjust threshold (ResourceAdjustThs) .................................4-343
4.14.42 Info1_2 .............................................................................................4-344
4.14.43 Info1_3 .............................................................................................4-345
4.14.44 Is Dual-Frequency NC2 Support (DualFreqNC2Sup)............................4-346
4.14.45 Dual-Frequency NC2 Parameter N (DualFreqNC2N) ...........................4-347
4.14.46 Dual-Frequency NC2 Parameter P (DualFreqNC2P)............................4-348
4.14.47 Dual-Frequency NC2 TA Threshold (DualFreqNC2TAThr) ....................4-349
4.14.48 Dual-Frequency NC2 load Threshold (DualCellPsChanThr)..................4-350
4.14.49 NC2 UL RxLevel Threshold (ULRxLevThr) ..........................................4-351
4.14.50 NC2 DL RxLevel Threshold (DLRxLevThr) ..........................................4-352
4.14.51 NC2 UL RxQual Threshold (ULRxQualThr) .........................................4-353
4.14.52 NC2 DL RxQual Threshold (DLRxQualThr) .........................................4-354
4.14.53 avoid Ping-Pang cell reselection Timer (TPingPang) ............................4-355
4.14.54 NC2 Reselection hysteresis Threshold (NC2ResHys) ..........................4-356
4.14.55 NC2 reselection DL RxLevel Threshold (NC2ResThr) ..........................4-357
4.15 GPRS Cell Options Parameters......................................................................4-358
4.15.1 T3168 (T3168) ....................................................................................4-358
4.15.2 T3192 (T3192) ....................................................................................4-359
4.15.3 T3142 (Info1_0_2) ...............................................................................4-361
4.15.4 T3172 (Info1_0_3) ...............................................................................4-362
4.15.5 DRX mode holding timer (DrxTimeMax) ................................................4-364
4.15.6 MAX blocks transmittion in each TS (BsCvMax) ....................................4-365
4.15.7 Packet control acknowledgement type (CtraCKType).............................4-367
4.15.8 Access burst type (AccessType) ...........................................................4-368
4.15.9 N3102 descrease step (PanDec) ..........................................................4-369
4.15.10 N3102 increase step (PanInc) ............................................................4-371
4.15.11 N3102 max (PanMax) ........................................................................4-372
4.15.12 GPRS Phone Init Coding (GPRSInitattselt_0~GPRSInitattselt_3) .........4-374
4.15.13 GPRS phones init code can be changed (InitAttachExch_0) .................4-375
4.16 GPRS NC Survey Parameters........................................................................4-376
4.16.1 Packet idle mode (NcRepPerI) .............................................................4-376
4.16.2 Packet transmission mode (NcRerPerT) ...............................................4-377
4.16.3 Extended measurement report order (MeaOrder) ..................................4-378
4.16.4 Network control order (CtrlOrder)..........................................................4-379

XXII

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


4.16.5 NC2 mode between 2G and 3G (NC2For23G) ......................................4-380
4.16.6 Serving Cell Load Threshold (ServCellLoadThr) ....................................4-381
4.16.7 Serving Cell Capacity Threshold (ServCellCapaThr) ..............................4-382
4.16.8 Cell reselection control switch by serving cell traffic busy
(PsTrafResel) ......................................................................................4-383
4.16.9 NC hold time in non-drx mode (NcNoDrxPer) ........................................4-384
4.16.10 Extended measurement report order (ExMeaOrder).............................4-385
4.16.11 Type of extended measurement report (ExtRepType) ...........................4-386
4.16.12 Report period of extended measurement (ExtRepPer) .........................4-387
4.16.13 The size of test report's slip window (Wnd) ..........................................4-388
4.16.14 Minimum measurement reports in slip window to avoid penalty
(AllowedRepNum)................................................................................4-389
4.17 GPRS Power Control Parameters...................................................................4-391
4.17.1 Filter period in the packet idle mode (T_AVG_W)...................................4-391
4.17.2 Filter period in packet transmission mode (T_AVG_T)............................4-392
4.17.3 PSI4 sending mark (Psi4Send).............................................................4-393
4.17.4 Power control measurement channel (PcMeasChan).............................4-394
4.17.5 Power control parameter (Alpha) ..........................................................4-395
4.17.6 Filter constant of power control (N_AVG_I)............................................4-396
4.17.7 Power descending on PBCCH (Pb) ......................................................4-397
4.18 GPRS Cell Reselection Parameters................................................................4-398
4.18.1 Cell reselection offset (ReselOff_0).......................................................4-398
4.18.2 Cell reselection offset2 (ReselOff_1) .....................................................4-399
4.18.3 Temporary offset of cell reselection (TempOffset_0) ...............................4-400
4.18.4 Temporary offset of cell reselection2 (TempOffset_1) .............................4-401
4.18.5 Penalty time of cell reselection 0 (PenalTime_0)....................................4-402
4.18.6 Penalty time of cell reselection 1 (PenalTime_1)....................................4-404
4.18.7 Interval of reselecting the same cell (T_Resel_0)...................................4-405
4.18.8 Interval of reselecting the same cell 2 (T_Resel_1) ................................4-406
4.18.9 Threshold of HSC signal level (HCS_Thr_0)..........................................4-407
4.18.10 Threshold of HSC signal level 2 (HCS_Thr_1) .....................................4-408
4.18.11 HCS Priority (PrioClass_0) .................................................................4-409
4.18.12 HCS Priority 2 (PrioClass_1) ..............................................................4-410
4.18.13 C31 hysteresis (C31_Hyst_0) ............................................................. 4-411
4.18.14 C31 hysteresis 2 (C31_Hyst_1) ..........................................................4-412
4.18.15 GPRS cell reselection hysteresis (ReselHys_0) ...................................4-413
4.18.16 GPRS cell reselection hysteresis 2 (ReselHys_1) ................................4-415
4.18.17 Routing reselection hysteresis (RaReselHys_0)...................................4-416

XXIII

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


4.18.18 Routing reselection hysteresis 2 (RaReselHys_1)................................4-417
4.18.19 Random access attempt permitted (RadAcRetry_0).............................4-419
4.18.20 Random access attempt permitted 2 (RadAcRetry_1) ..........................4-420
4.18.21 Usage of cell reselection offset (C32_Qual_0) .....................................4-421
4.18.22 Usage of cell reselection offset 2 (C32_Qual_1) ..................................4-422
4.18.23 GPRS access minimal signal level 1 (RxLevAsMin_0)..........................4-423
4.18.24 GPRS access minimal signal level 2 (RxLevAsMin_1)..........................4-424
4.18.25 Priority threshold (Prio_Thr) ...............................................................4-426
4.18.26 HCS exist (HCS_Exist_0)...................................................................4-426
4.18.27 HCS exist 2 (HCS_Exist_1) ................................................................4-428
4.18.28 GPRS MAX initial access signal level (MsTxMaxCch_0) ......................4-429
4.18.29 GPRS MAX initial access signal level 2 (MsTxMaxCch_1)....................4-430
4.18.30 LSA ID (LSA_Id)................................................................................4-432
4.18.31 LSA Offset (LSA_Offset) ....................................................................4-433
4.19 GPRS Channel Parameters ...........................................................................4-434
4.19.1 PAGCH reserved blocks (PagBlkRes)...................................................4-434
4.19.2 PBCCH reserved blocks (PbcchBlks)....................................................4-435
4.19.3 PRACH reserved blocks (PrachBlks) ....................................................4-436
4.19.4 Interval range of packet access attempt (TxInt)......................................4-437
4.19.5 Interval period of packet access attempt (S) ..........................................4-438
4.19.6 MAX Times of Attempt (MaxRetrans) ....................................................4-439
4.19.7 Access control level (AccCtrlClass).......................................................4-440
4.19.8 Access Persistent Level (PersistLev) ....................................................4-442
4.19.9 Subscriber occupying other preference channel support
(HybridOccuSupp) ...............................................................................4-443
4.19.10 PS subscriber moving out of other preference channel support
(AllowPsMove).....................................................................................4-444
4.19.11 CS subscriber moving support (AllowCsMove).....................................4-445
4.19.12 Threshold of GPRS/GPRS,EDGE/EDGE service moving
(SfPreferBusyThs) ...............................................................................4-446
4.19.13 Threshold of GPRS/EDGE service moving (OpPreferBusyThs) ............4-447
4.19.14 PS channel expand (Info1_1_18)........................................................4-449
4.19.15 Idle TCH threshold for PS channel expand (Info1_1_24) ......................4-450
4.19.16 Maximum PS uplink user per ts (MaxPsUserPerTs_0)..........................4-451
4.19.17 Max PS downlink user per TS (MaxPsUserPerTs_1) ............................4-452
4.19.18 Support dynamic channel move (DynChMove) ....................................4-453
4.19.19 Idle static TCH THS for dynamic channel move
(IdleTCHForDChMove,%).....................................................................4-454

XXIV

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


4.19.20 PS channel alloc reduction support (SuppReducePd) ..........................4-455
4.19.21 Initial limit threshold of PDTCH alloc (LmtThreshold_0) ........................4-456
4.19.22 Medium limit threshold of PDTCH alloc (LmtThreshold_1) ....................4-457
4.19.23 Maximum limit threshold of PDTCH alloc (LmtThreshold_2) .................4-458
4.19.24 Damping of PDTCH alloc from limit to non-limit (LmtThreshold_3) ........4-459
4.20 PS Handover Parameters ..............................................................................4-460
4.20.1 PS handover support (HandoverSupp)..................................................4-460
4.20.2 ACK of PS handover command (HOCommandAck) ...............................4-461
4.20.3 Blind transmission support (BlindTransSupp) ........................................4-462
4.20.4 Optimised handover support (OptimizeHOSupp) ...................................4-463
4.20.5 Send handover access in synchronised handover (SendAccessSync) ......4-464
4.20.6 Send handover access in pre-synchronised handover
(SendAccessPreSync) .........................................................................4-465
4.20.7 Reset RLC (RlcStateReset)..................................................................4-466
4.20.8 Trigger PS handover by PCCN (EnablePCCNTrigHO) ...........................4-467
4.20.9 Early get system information in intra-BSS handover
(EarlyGetSysIntra) ...............................................................................4-468
4.21 EDGE Parameters.........................................................................................4-469
4.21.1 Max number of GTTP lapdm frame (GttpLapdmNum) ............................4-469
4.21.2 EGPRS packet channel request access program support
(EgprsPacketChreq).............................................................................4-470
4.21.3 Uplink LA+IR quality control support (IrSupportUp) ................................4-471
4.21.4 Take Preemptive transmit bit function (PreemptivetRans) .......................4-472
4.21.5 Average filter period for uplink BEP (BEPperiodUp) ...............................4-474
4.21.6 Average filter period for downlink BEP (BEPperiodDown).......................4-475
4.21.7 EGPRS phone quality measure mode (LinkQuameaMode) ....................4-476
4.21.8 EDGE initial downlink allocation by multislot class1 (Info1_1_0) .............4-477
4.21.9 Use parameter of ‘EGPRS Prior to GPRS' in Cell (Info1_7_5) ................4-478
4.21.10 Allocating weights of EGPRS (Info1_7_6) ...........................................4-479
4.21.11 EGPRS uplink init. Coding scheme/EGPRS downlink init. Coding
scheme/EGPRS uplink max. coding schme/EGPRS downlink max.
coding scheme (EGPRSInitAttSelt_0~EGPRSInitAttSelt_3) ....................4-481
4.21.12 EGPRS phones init. Code can be changed (InitAttachExch_1).............4-482
4.21.13 FANR in uplink TBF support (INFO1_4_0)...........................................4-483
4.21.14 FANR in downlink TBF support (INFO1_4_1) ......................................4-484
4.21.15 DLDC support (INFO1_4_2) ...............................................................4-485
4.21.16 RTTI support (INFO1_4_3).................................................................4-486
4.21.17 Enable event-based FANR in downlink TBF (INFO1_4_4) ....................4-487

XXV

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


4.21.18 Encoding mode of PAN in uplink TBF (INFO1_4_5) .............................4-488
4.21.19 Bep_Period2 of uplink (INFO1_4_6) ...................................................4-489
4.21.20 Bep_Period2 of downlink (INFO1_4_10) .............................................4-490
4.21.21 EGPRS2-A uplink initial coding scheme (EGPRS2AInitAttSelt_0) .........4-491
4.21.22 EGPRS2-A downlink initial coding scheme (EGPRS2AInitAttSelt_1) ......4-492
4.21.23 EGPRS2-A uplink maximum coding scheme
(EGPRS2AInitAttSelt_2) .......................................................................4-493
4.21.24 EGPRS2-A downlink maximum coding scheme
(EGPRS2AInitAttSelt_3) .......................................................................4-494
4.21.25 EGPRS2A MS initial code can be changed (InitAttachExch_2) .............4-495
4.21.26 Enable reduced latency access (RttiAccess) .......................................4-496
4.22 AMR-WB Parameter ......................................................................................4-497
4.22.1 Thresholds for AMR-WB
(AmrWBThresholds_0~AmrWBThresholds_7) .......................................4-497
4.22.2 Hysteresis for AMR-WB
(AmrWBHysteresis_0~AmrWBHysteresis_7) .........................................4-498
4.23 VAMOS Parameter ........................................................................................4-499
4.23.1 User label (UserLabel) .........................................................................4-499
4.23.2 BSC ID (OMCBSCID) ..........................................................................4-500
4.23.3 The identifier of the site (SITEID)..........................................................4-501
4.23.4 BTS ID (BTSID)...................................................................................4-502
4.23.5 Support VAMOS (SupportVAMOS) .......................................................4-503
4.23.6 Support MUTE SAIC detection (MuteSaicDetect) ..................................4-504
4.23.7 Support SAIC AFC detection (SaicAfcDetect)........................................4-505
4.23.8 The priority level of VAMOS pairing (PriorLevelOfPair) ...........................4-506
4.23.9 The load of start VAMOS FR pairing (FRPairLoadThr,%)........................4-507
4.23.10 The load of start VAMOS HR pairing (HRPairLoadThr,%) .....................4-508
4.23.11 The level threshold of Vamos paring (LevThrOfPair).............................4-509
4.23.12 The quality threshold of Vamos paring (QualThrOfPair) ........................4-510
4.23.13 The path loss ratio of candidates (PassLossRatio) ............................... 4-511
4.23.14 The expected received level (ExpectedLev) ........................................4-512
4.23.15 The uplink SCPIR threshold (SCPIR_Up) ............................................4-513
4.23.16 The downlink SCPIR threshold of NON-SAIC MS
(SCPIR_Dn_NoSaic)............................................................................4-514
4.23.17 The downlink SCPIR threshold of SAIC MS (SCPIR_Dn_Saic) .............4-515
4.23.18 The downlink SCPIR threshold of SAIC AFC MS
(SCPIR_Dn_SaicAfc) ...........................................................................4-517
4.23.19 The downlink SCPIR threshold of VAMOS I MS
(SCPIR_Dn_VAMOSI)..........................................................................4-518

XXVI

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


4.23.20 The downlink SCPIR threshold of VAMOS II MS
(SCPIR_Dn_VAMOSII).........................................................................4-519
4.23.21 P value of total power or SCPIR overflow (PowerOrScpirOverP)...........4-520
4.23.22 N value of total power or SCPIR overflow (PowerOrScpirOverN) ..........4-521
4.23.23 The detection quality threshold (SaicDetQual) .....................................4-522
4.23.24 P value of MUTE SAIC detection (MuteSaicDetectP) ...........................4-524
4.23.25 Thresholdof Frequecy Shift (FreqShiftThre,Hz) ....................................4-525
4.23.26 The time of SAIC AFC detection (SaicAfcDetectTime)..........................4-526
4.23.27 P value of SAIC AFC detection (SaicAfcDetectP).................................4-526
4.23.28 N value of SAIC AFC detection (SaicAfcDetectN) ................................4-528
4.24 Cell Power Parameter....................................................................................4-529
4.24.1 UpLink optimize method for immediate assignment (PwrOptCtrl_0) ........4-529
4.24.2 DownLink optimize method for immediate assignment
(PwrOptCtrl_4).....................................................................................4-530
4.24.3 UpLink optimize method for assignment or intracell handover
(PwrOptCtrl_8).....................................................................................4-531
4.24.4 DownLink optimize method for assignment or intracell handover
(PwrOptCtrl_12)...................................................................................4-532
4.24.5 UpLink optimize method for intercell handover (PwrOptCtrl_16) .............4-533
4.24.6 DownLink optimize method for intercell handover (PwrOptCtrl_20) .........4-534
4.24.7 Uplink target level (UlTargetLevel) ........................................................4-535
4.24.8 Downlink target level (DlTargetLevel) ....................................................4-536
4.24.9 Low RSSI threshold (LowRssiThs)........................................................4-537
4.24.10 High RSSI Threshold (HighRssiThs) ...................................................4-539
4.24.11 Ms power inherit threshold (MsPwrInheritThs) .....................................4-540
4.24.12 Power dynamic sharing (PwrDynShare) ..............................................4-541
4.24.13 Power reserved for present users (PwrPres) .......................................4-542
4.24.14 Power Adjusting Threshold (PwrAdjustThreshold)................................4-543
4.24.15 Power admitting threshold (PwrAdmitThreshold)..................................4-544
4.24.16 Power admitting threshold punishment (PwrAdmitThrldPunish).............4-546
4.24.17 Power admitting threshold punishment time (PwrAdmitPunishTime) ......4-547
4.24.18 Power adjustment methods priority 1 (PwrAdjPriority_0).......................4-548
4.24.19 Power adjustment methods priority2 (PwrAdjPriority_1) .......................4-549
4.24.20 Power adjustment methods priority3 (PwrAdjPriority_2) .......................4-550
4.24.21 Power adjustment methods priority4 (PwrAdjPriority_3) .......................4-551
4.24.22 Power adjustment methods priority5 (PwrAdjPriority_4) .......................4-552
4.24.23 Threshold for increase 8PSK power (Inc8PskPwrThs) .........................4-553
4.24.24 Hysteresis for increase 8PSK power (Inc8PskPwrHys).........................4-554

XXVII

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


4.24.25 Delay for increase 8PSK power (Inc8PskPwrDelay).............................4-555
4.25 GPRS Resource Control By Service ...............................................................4-556
4.25.1 Threshold of PS resource congestion (PSResourceThr0).......................4-556
4.25.2 Threshold of relieving PS resource congestion (PSResourceThr1) .........4-558
4.25.3 Scheduled priority of gold user's own service (SchedulePriority0) ...........4-559
4.25.4 Scheduled priority of silver user's own service (SchedulePriority1)..........4-560
4.25.5 Scheduled priority of bronze user's own service (SchedulePriority2) .......4-561
4.25.6 Scheduled priority of gold user's browse service (SchedulePriority3).......4-562
4.25.7 Scheduled priority of silver user's browse service (SchedulePriority4) ......4-563
4.25.8 Scheduled priority of bronze user's browse service
(SchedulePriority5) ..............................................................................4-564
4.25.9 Scheduled priority of gold user's download service
(SchedulePriority6) ..............................................................................4-565
4.25.10 Scheduled priority of silver user's download service
(SchedulePriority7) ..............................................................................4-566
4.25.11 Scheduled priority of bronze user's download service
(SchedulePriority8) ..............................................................................4-567
4.25.12 Scheduled priority of gold user's IM service (SchedulePriority9)............4-568
4.25.13 Scheduled priority of silver user's IM service (SchedulePriority10) ........4-569
4.25.14 Scheduled priority of bronze user's IM service (SchedulePriority11) ......4-570
4.25.15 TBF occupancy of gold user's own service (TBFNum0)........................4-571
4.25.16 TBF occupancy of silver user's own service (TBFNum1) ......................4-572
4.25.17 TBF occupancy of bronze user's own service (TBFNum2) ....................4-573
4.25.18 TBF occupancy of gold user's browse service (TBFNum3) ...................4-574
4.25.19 TBF occupancy of silver user's browse service (TBFNum4)..................4-575
4.25.20 TBF occupancy of bronze user's browse service (TBFNum5) ...............4-576
4.25.21 TBF occupancy of gold user's download service (TBFNum6)................4-577
4.25.22 TBF occupancy of silver user's download service (TBFNum7) ..............4-578
4.25.23 TBF occupancy of bronze user's download service (TBFNum8)............4-579
4.25.24 TBF occupancy of gold user's IM service (TBFNum9) ..........................4-580
4.25.25 TBF occupancy of silver user's IM service (TBFNum10).......................4-581
4.25.26 TBF occupancy of bronze user's IM service (TBFNum11).....................4-582
4.25.27 Max PDTCH num of gold user's own service in congestion
(MaxPdtchNum0) .................................................................................4-583
4.25.28 Max PDTCH num of silver user's own service in congestion
(MaxPdtchNum1) .................................................................................4-584
4.25.29 Max PDTCH num of bronze user's own service in congestion
(MaxPdtchNum2) .................................................................................4-585

XXVIII

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


4.25.30 Max PDTCH num of gold user's browse service in congestion
(MaxPdtchNum3) .................................................................................4-586
4.25.31 Max PDTCH num of silver user's browse service in congestion
(MaxPdtchNum4) .................................................................................4-587
4.25.32 Max PDTCH num of bronze user's browse service in congestion
(MaxPdtchNum5) .................................................................................4-588
4.25.33 Max PDTCH num of gold user's download service in congestion
(MaxPdtchNum6) .................................................................................4-589
4.25.34 Max PDTCH num of silver user's download service in congestion
(MaxPdtchNum7) .................................................................................4-590
4.25.35 Max PDTCH num of bronze user's download service in congestion
(MaxPdtchNum8) .................................................................................4-591
4.25.36 Max PDTCH num of gold user's IM service in congestion
(MaxPdtchNum9) .................................................................................4-592
4.25.37 Max PDTCH num of silver user's IM service in congestion
(MaxPdtchNum10) ...............................................................................4-593
4.25.38 Max PDTCH num of bronze user's IM service in congestion
(MaxPdtchNum11) ...............................................................................4-594
4.25.39 Downlink delay time of gold user's own service
(DlDelayTimeOfService0) .....................................................................4-595
4.25.40 Downlink delay time of silver user's own service
(DlDelayTimeOfService1) .....................................................................4-596
4.25.41 Downlink delay time of bronze user's own service
(DlDelayTimeOfService2) .....................................................................4-597
4.25.42 Downlink delay time of gold user's browse service
(DlDelayTimeOfService3) .....................................................................4-598
4.25.43 Downlink delay time of silver user's browse service
(DlDelayTimeOfService4) .....................................................................4-599
4.25.44 Downlink delay time of bronze user's browse service
(DlDelayTimeOfService5) .....................................................................4-600
4.25.45 Downlink delay time of gold user's download service
(DlDelayTimeOfService6) .....................................................................4-601
4.25.46 Downlink delay time of silver user's download service
(DlDelayTimeOfService7) .....................................................................4-602
4.25.47 Downlink delay time of bronze user's download service
(DlDelayTimeOfService8) .....................................................................4-603
4.25.48 Downlink delay time of gold user's IM service
(DlDelayTimeOfService9) .....................................................................4-604
4.25.49 Downlink delay time of silver user's IM service
(DlDelayTimeOfService10) ...................................................................4-605

XXIX

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


4.25.50 Downlink delay time of bronze user's IM service
(DlDelayTimeOfService11)....................................................................4-606
4.25.51 Preemption priority of gold user's own service (PreemptPriority0) .........4-607
4.25.52 Preemption priority of silver user's own service (PreemptPriority1)........4-608
4.25.53 Preemption priority of bronze user's own service (PreemptPriority2) ......4-609
4.25.54 Preemption priority of gold user's browse service (PreemptPriority3) ......4-610
4.25.55 Preemption priority of silver user's browse service
(PreemptPriority4)................................................................................ 4-611
4.25.56 Preemption priority of bronze user's browse service
(PreemptPriority5)................................................................................4-612
4.25.57 Preemption priority of gold user's download service
(PreemptPriority6)................................................................................4-613
4.25.58 Preemption priority of silver user's download service
(PreemptPriority7)................................................................................4-614
4.25.59 Preemption priority of bronze user's download service
(PreemptPriority8)................................................................................4-615
4.25.60 Preemption priority of gold user's IM service (PreemptPriority9)............4-616
4.25.61 Preemption priority of silver user's IM service (PreemptPriority10) ........4-617
4.25.62 Preemption priority of bronze user's IM service (PreemptPriority11) ......4-618

Chapter 5 Cell Object Parameters............................................................. 5-1


5.1 TRX Parameters ................................................................................................ 5-1
5.1.1 TRX Information Parameters..................................................................... 5-1
5.1.2 Channel Information Parameters ............................................................. 5-17
5.1.3 IP Parameters........................................................................................ 5-33
5.1.4 Panel Parameters .................................................................................. 5-36
5.2 Power Control Parameters ................................................................................ 5-41
5.2.1 Power Control Parameters ...................................................................... 5-41
5.2.2 Power Survey Parameters ...................................................................... 5-47
5.2.3 Power Adjustment Threshold Parameters ................................................ 5-57
5.2.4 Other Parameters................................................................................... 5-76
5.2.5 New Power Control Attribute .................................................................. 5-110
5.2.6 GPRS Power Control Parameters ..........................................................5-137
5.3 Handover Control Parameters ..........................................................................5-214
5.3.1 Handover Pretreatment Parameters .......................................................5-215
5.3.2 Handover Level Parameters...................................................................5-233
5.3.3 Handover Condition Parameters.............................................................5-289
5.3.4 Handover Control Parameters ................................................................5-317
5.3.5 Other Parameters..................................................................................5-392

XXX

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


5.3.6 Handover Arithmetic Parameters............................................................5-420
5.3.7 Subcell Parameters ...............................................................................5-440
5.3.8 Weight Average Parameters ..................................................................5-457
5.4 SDCCH Handover Control Parameters .............................................................5-459
5.4.1 Handover Pretreatment Parameters .......................................................5-460
5.4.2 Handover Threshold Parameters............................................................5-473
5.4.3 Handover Condition Parameters.............................................................5-491
5.4.4 Handover Control Parameters ................................................................5-498
5.5 UTRAN Handover Control Parameters .............................................................5-533
5.5.1 Basic Properties 1 .................................................................................5-533
5.5.2 Basic Properties 2 .................................................................................5-553
5.5.3 PS Handover Parameters ......................................................................5-565
5.6 UTRAN Cell Control Parameters ......................................................................5-582
5.6.1 Basic Parameters 1 ...............................................................................5-582
5.6.2 Basic Parameters 2 ...............................................................................5-602
5.6.3 GPRS Parameters 1..............................................................................5-621
5.6.4 GPRS Parameters 2..............................................................................5-641
5.7 Adjacent Cell Parameters ................................................................................5-663
5.7.1 Adjacent Interference Cell Parameters....................................................5-663
5.7.2 Adjacent Cell Handover and Reselection Parameters ..............................5-667
5.7.3 Adjacent Cell Handover Parameters .......................................................5-717
5.7.4 Adjacent Cell Reselection Parameters ....................................................5-759
5.7.5 UTRAN Adjacent Cell Handover and Reselection Parameters..................5-767
5.7.6 UTRAN Adjacent Cell Handover Parameters...........................................5-784
5.7.7 UTRAN Adjacent Cell Reselection Parameters........................................5-797
5.8 Frequency Hopping System Parameters ...........................................................5-805
5.8.1 Site ID ..................................................................................................5-805
5.8.2 BTS ID (BtsId).......................................................................................5-806
5.8.3 Frequency hopping ID (FhsId) ................................................................5-807
5.8.4 Hopping sequence No. (HSN)................................................................5-808
5.8.5 Frequency hopping mode (FreqHopMode) ..............................................5-809
5.8.6 Hopping group ID (BhGroupId)...............................................................5-810
5.8.7 MA Frequency List Number (MaFreqNum) .............................................. 5-811
5.9 PS Handover Control Parameters ....................................................................5-812
5.9.1 Handover Pretreatment Parameters .......................................................5-812
5.9.2 Handover Level Parameters...................................................................5-823
5.9.3 Handover Condition Parameters.............................................................5-855

XXXI

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


5.9.4 Handover Control Parameters ................................................................5-865
5.9.5 Other Parameters..................................................................................5-872
5.9.6 Handover Arithmetic Parameters............................................................5-878
5.10 LTE Cell Control Parameters ..........................................................................5-888
5.10.1 Site Id (SiteId) .....................................................................................5-888
5.10.2 BTS ID (BtsId).....................................................................................5-889
5.10.3 EUTRAN BTS ID (LTEBTSID) ..............................................................5-890
5.10.4 QSearchC (QSearchC) ........................................................................5-891
5.10.5 Initial parameter used before UE receiving qsearch_c (QSearchCInit) ......5-892
5.10.6 Class of reported quantities of E-UTRAN adjacent cells (RepQuant).......5-893
5.10.7 Max number of E-UTRAN adjacent cells in measurement report
(MulRatRrpt)........................................................................................5-894
5.10.8 FDD Measurement report threshold of RSRP or RSRQ in 6-bit
(FDDRptthresh) ...................................................................................5-895
5.10.9 FDD Measurement report threshold of RSRQ or RSRP in 6-bit reporting
(FDDRptthresh2) .................................................................................5-896
5.10.10 FDDRptOffset6bit (FDDRptOffset6bit).................................................5-897
5.10.11 FDDRptOffset3bit (FDDRptOffset3bit) .................................................5-898
5.10.12 TDD Measurement report threshold of RSRP or RSRQ in 6-bit
reporting (TDDRptthresh) .....................................................................5-899
5.10.13 TDD Measurement report threshold of RSRQ or RSRP in 6-bit
reporting (TDDRptthresh2) ...................................................................5-900
5.10.14 TDDRptOffset6bit (TDDRptOffset6bit).................................................5-901
5.10.15 TDDRptOffset3bit (TDDRptOffset3bit).................................................5-902
5.10.16 FDD Measurement report threshold of RSRP or RSRQ in 3-bit
reporting (FDDMeasRptOffset) .............................................................5-903
5.10.17 FDD Measurement report threshold of RSRQ or RSRP in 3-bit
reporting (FDDMeasRptthresh2) ...........................................................5-904
5.10.18 TDD Measurement report threshold of RSRP or RSRQ in 3-bit
reporting (TDDMeasRptOffset) .............................................................5-905
5.10.19 TDD Measurement report threshold of RSRQ or RSRP in 3-bit
reporting (TDDMeasRptthresh2) ...........................................................5-906
5.10.20 Measurement report threshold offset of RSRQ or RSRP in 3-bit
reporting (RptGranularity) .....................................................................5-907
5.10.21 Measurement threshold of UE performing GPRS E-UTRAN Cell
(QsearchP_PS) ...................................................................................5-908
5.10.22 GPRS max number of E-UTRAN adjacent cells in measurement report
(MulRatRpt_PS)...................................................................................5-909
5.10.23 GPRS class of reported quantities of E-UTRAN adjacent cells
(RepQuant_PS) ...................................................................................5-910

XXXII

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


5.10.24 GPRS FDD Measurement report threshold of RSRP or RSRQ
(FDDRptThresh_PS) ............................................................................ 5-911
5.10.25 GPRS FDD Measurement report threshold of RSRQ or RSRP
(FDDRptThresh2_PS) ..........................................................................5-912
5.10.26 FDDRptOffset_PS (FDDRptOffset_PS) ...............................................5-912
5.10.27 GPRS TDD Measurement report threshold of RSRP or RSRQ
(TDDRptThresh_PS) ............................................................................5-913
5.10.28 GPRS TDD Measurement report threshold of RSRQ or RSRP
(TDDRptThresh2_PS) ..........................................................................5-914
5.10.29 TDDRptOffset_PS (TDDRptOffset_PS) ...............................................5-915
5.10.30 WindowEutran (WindowEutran) ..........................................................5-916
5.11 LTE Cell Reselection Parameters ...................................................................5-917
5.11.1 User label (UserLabel) .........................................................................5-917
5.11.2 SITE ID (SITEID) .................................................................................5-918
5.11.3 BTS ID (BTSID)...................................................................................5-919
5.11.4 LTE Cell reselect Identification (LTERSID).............................................5-920
5.11.5 The priority of E-UTRAN cells (ArfcnLTEPrio) ........................................5-921
5.11.6 CCN mode support (CCNSUPPORT)....................................................5-922
5.11.7 The re-selecting flag of LTE Ncell (NCelBlackListInd) .............................5-923
5.11.8 MCC (MCC) ........................................................................................5-924
5.11.9 MNC (MNC) ........................................................................................5-925
5.11.10 LTE CELL Identification (ENBID).........................................................5-926
5.11.11 LTE CELL TYPE (CellTypeLTE) ..........................................................5-927
5.11.12 Tracking area code (TAC)...................................................................5-927
5.11.13 Physical layer cell identity of LTE CELL (PCID)....................................5-928
5.11.14 The attribute of LTE NodeB (ENBInd)..................................................5-929
5.11.15 Specified EARFCN of E-UTRAN cells (ArfcnLTE) ................................5-930
5.11.16 the minimum value of the channel bandwidth (MeasureBandwidth) .......5-931
5.11.17 Related Cell DN (RelationDN).............................................................5-932
5.12 VPC Cell Parameters.....................................................................................5-933
5.12.1 User label (UserLabel) .........................................................................5-933
5.12.2 Site identifier (SiteId) ...........................................................................5-934
5.12.3 BTS ID (BtsId).....................................................................................5-935
5.12.4 Vpc Identity (VpcId) .............................................................................5-936
5.12.5 Vpc Site Identity (VpcSiteId).................................................................5-937
5.12.6 Vpc Bts Identity (VpcBtsId)...................................................................5-938
5.13 Site Parameters ............................................................................................5-939
5.13.1 Inter subcell handover permitted (SUBCELLHO) ...................................5-939

XXXIII

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 6 System Control Parameters..................................................... 6-1
6.1 Operation Control Parameters............................................................................. 6-1
6.1.1 User Label ............................................................................................... 6-1
6.1.2 BSC ID .................................................................................................... 6-2
6.1.3 Assign queue enable (AssQueEnable)....................................................... 6-3
6.1.4 Internal redirection enable (InDrEnable)..................................................... 6-4
6.1.5 Outer redirection enable (OutDrEnable) ..................................................... 6-5
6.1.6 Assign preemption enable (AssPreEmpt) ................................................... 6-6
6.1.7 BSC intracell handover enable (HoIntraEnable).......................................... 6-7
6.1.8 BSC cell handover enable (HoInterEnable) ................................................ 6-8
6.1.9 BSC outer handover enable (HoOutEnable)............................................... 6-9
6.1.10 SDCCH handover enable (ShoEnable) .................................................. 6-10
6.1.11 TCH/F handover enable (TfHoEnable) ....................................................6-11
6.1.12 TCH/H handover enable (ThHoEnable).................................................. 6-12
6.1.13 Handover queue enable (HoQueEnable)................................................ 6-13
6.1.14 Handover preemption enable (HoPreEmpt) ............................................ 6-14
6.1.15 Handover check arithmetic choose (HoA)............................................... 6-15
6.1.16 Handover request response (HoAck) ..................................................... 6-16
6.1.17 Force FACCH (FacchOnly) ................................................................... 6-17
6.1.18 Continuous handover trigger (HoTrigger) ............................................... 6-18
6.1.19 Handover reason tip (HoCauseInd)........................................................ 6-19
6.1.20 Local cell position number (LAC) ........................................................... 6-20
6.1.21 Local cell identity (CI) ........................................................................... 6-21
6.1.22 Outer cell target number (OutCellNum) .................................................. 6-22
6.1.23 Outer cell position number 1 (OutLAC1)................................................. 6-23
6.1.24 Outer cell position number 2 (OutLAC2)................................................. 6-24
6.1.25 Outer cell position number 3 (OutLAC3)................................................. 6-25
6.1.26 Outer cell number 1 (OutCI1) ................................................................ 6-25
6.1.27 Outer cell number 2 (OutCI2) ................................................................ 6-26
6.1.28 Outer cell number 3 (OutCI3) ................................................................ 6-27
6.1.29 Outer RNC 1 (OutRNC1) ...................................................................... 6-28
6.1.30 Outer RNC 2 (OutRNC2) ...................................................................... 6-29
6.1.31 Outer RNC 3 (OutRNC3) ...................................................................... 6-30
6.1.32 Old BSS to new BSS information (OldToNewctrl).................................... 6-31
6.1.33 BSC Internal Handover Parameter of IPA (IPAInterHo)............................ 6-32
6.1.34 Send suspend message when GPRS suspension (ResumeSetOpt)......... 6-34
6.1.35 Queuing indicator in handover required message (HandOutQueInd)........ 6-35

XXXIV

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


6.1.36 Send cell prefer indication (SendCellPreferInd)....................................... 6-36
6.1.37 IPA AMR start mode (IpaAMRStartMode)............................................... 6-37
6.1.38 TDD cell handover enable (TdHoEnable) ............................................... 6-38
6.1.39 ICM optimize when intra BSC handover (AmrHoOpt_0) .......................... 6-39
6.1.40 ICM optimize when inter BSC handover (AmrHoOpt_1) .......................... 6-40
6.1.41 The switch of connection and radio channel activating synchronization
(CallDelayCtrl) ...................................................................................... 6-41
6.1.42 Include trace ID in handover required (HoRqdCtrl_0) .............................. 6-42
6.1.43 Inter BSC handover out on SDCCH permitted (InterBSCSDHOout) ......... 6-43
6.1.44 Use BER to average quality (RQAvgUseBER)........................................ 6-44
6.1.45 Check IMSI when access (CheckIMSIWhenAccess) ............................... 6-45
6.1.46 Allow assign according first measurement report when use cobcch
(CoBcchAssByOneMr) .......................................................................... 6-46
6.1.47 Use N/P when select neighbour cell for Pbgt handover in Sdcch
(NcellSelCtrlPbgt1) ............................................................................... 6-48
6.1.48 Use N/P when select neighbour cell for Pbgt handover in Tch
(NcellSelCtrlPbgt2) ............................................................................... 6-49
6.1.49 Use N/P when select neighbour cell for uplink quality handover in Sdcch
(NcellSelCtrlUlQ1)................................................................................. 6-50
6.1.50 Use N/P when select neighbour cell for uplink quality handover in Tch
(NcellSelCtrlUlQ2)................................................................................. 6-51
6.1.51 Use N/P when select neighbour cell for downlink quality handover in
Sdcch (NcellSelCtrlDlQ1) ...................................................................... 6-52
6.1.52 Use N/P when select neighbour cell for downlink quality handover in
Tch (NcellSelCtrlDlQ2) .......................................................................... 6-53
6.1.53 Use N/P when select neighbour cell for uplink level handover in Sdcch
(NcellSelCtrlUlLev1).............................................................................. 6-54
6.1.54 Use N/P when select neighbour cell for uplink level handover in Tch
(NcellSelCtrlUlLev2).............................................................................. 6-55
6.1.55 Use N/P when select neighbour cell for downlink level handover in
Sdcch (NcellSelCtrlDlLev1).................................................................... 6-56
6.1.56 Use N/P when select neighbour cell for downlink level handover in Tch
(NcellSelCtrlDlLev2).............................................................................. 6-57
6.1.57 Use Subcell 1 as Cell Load (UseSC1Load) ............................................ 6-58
6.1.58 MS Report Count for Rlt (MrCountForRlt)............................................... 6-58
6.1.59 BSC intracell handover enable for circuit switch data
(CSDHoIntraEnable) ............................................................................. 6-59
6.1.60 BSC cell handover enable for circuit switch data (CSDHoInterEnable) ..... 6-60
6.1.61 BSC outer handover enable for circuit switch data (CSDHoOutEnable) ..... 6-61
6.2 FUC Parameters .............................................................................................. 6-62

XXXV

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


6.2.1 Use system message method when MSC over loaded or link blocked
(MSCSysInfoFlc)................................................................................... 6-62
6.2.2 Start system message method (CPUSysInfoFlc) ...................................... 6-63
6.2.3 Start limit of system message method (CPUSysInfoCTLCPU) ................... 6-64
6.2.4 Start FUC flow control (CPUFucFlc) ........................................................ 6-65
6.2.5 Start limit of FUC flow control (CPUFucCtlCPU) ....................................... 6-66
6.2.6 If paging flow control due to high CPU (CpuPagingFlc) ............................. 6-67
6.2.7 CPU threshold of paging flow control (CpuPagingCtlCpu) ......................... 6-68
6.2.8 The maximum control level for MSC overload or link block
(MSCFlcMaxLevel) ............................................................................... 6-69
6.2.9 The number of channel requests permitted per second (ChlReqNum)........ 6-70
6.2.10 The number of paging messages permitted per second (PagingNum)...... 6-71
6.3 Exchange Parameters of BCCH ........................................................................ 6-72
6.3.1 BCCH switch (CanBCCHEx) ................................................................... 6-72
6.3.2 Scan BCCH (ScanBCCH) ....................................................................... 6-73
6.3.3 BCCH starting delay (BCCHDelay).......................................................... 6-74
6.3.4 BCCH finishing delay (ReBcchEx) ........................................................... 6-75
6.3.5 Delay of TRX forcible release (TrxRel) ..................................................... 6-76
6.3.6 The maximum cells' amount of simultaneously handover
(MaxChangeProc)................................................................................. 6-78
6.3.7 Cell Break Alarm Delay (CellAlarmDelay)................................................. 6-79
6.4 Exchange Parameters of SD ............................................................................. 6-80
6.4.1 Dynamic configuration SDCCH (CanSDCCHDyn) .................................... 6-80
6.4.2 Scan SDCCH (ScanSDCCH) .................................................................. 6-81
6.4.3 Delay of TS forcible release (TsRel)......................................................... 6-82
6.4.4 Delay protection (MaxDelay) ................................................................... 6-83
6.4.5 TCH->SDCCH limit (MinSDCCH) ............................................................ 6-84
6.4.6 SDCCH->TCH delay (TimeToTch) ........................................................... 6-85
6.4.7 Dynamic SDCCH Channel Check Delay (DynSdCheckDelay) ................... 6-86
6.5 Other Parameters............................................................................................. 6-87
6.5.1 B2 support AMR (V2TruSupportAMR) ..................................................... 6-87
6.5.2 NC2 support (NC2support) ..................................................................... 6-88
6.5.3 MR server IP (MRSvrIP) ......................................................................... 6-89
6.5.4 MR server port (MRSvrPort).................................................................... 6-90
6.5.5 Include BTS power in MR (MrIncludeBtsPwr) ........................................... 6-90
6.5.6 Enhanced and Preprocessde MR report (EnhanAndPrepMrRpt)................ 6-91
6.5.7 Power congest delay (PwrCongDelay)..................................................... 6-92
6.5.8 Enable power dynamic sharing (PwrDynShareSupport_0) ........................ 6-93

XXXVI

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


6.5.9 Reduction of TCH initial downlink power according to SDCCH enable
(PwrDynShareSupport_1)...................................................................... 6-94
6.5.10 Channel power adjustment based on power dynamic sharing enable
(PwrDynShareSupport_2)...................................................................... 6-95
6.5.11 Time interval of channel power adjustment based on power dynamic
sharing (ChannelPwrAdjItvl)................................................................... 6-96
6.5.12 Ts Block Alarm Swtich (TsBlockAlarmSwitch) ......................................... 6-97
6.5.13 BER Weight (VoiceQualWeight_0)......................................................... 6-98
6.5.14 FER Weight (VoiceQualWeight_1) ......................................................... 6-99
6.5.15 Handover frequence weight (VoiceQualWeight_2) .................................6-100
6.5.16 DTX weight (VoiceQualWeight_3).........................................................6-101
6.5.17 Coding decode weight (VoiceQualWeight_4) .........................................6-102
6.5.18 Abis transmission error code weight (VoiceQualWeight_5) .....................6-103
6.5.19 Delay weight (VoiceQualWeight_6).......................................................6-104
6.5.20 A port resource block threshold (Reslimit_0) .........................................6-105
6.5.21 NSVC resource block threshold (Reslimit_1) .........................................6-106
6.5.22 Channel resource block threshold (Reslimit_2) ......................................6-106
6.5.23 Subcell busy threshold (Reslimit_3) ......................................................6-107
6.5.24 Abis alarm delay time (AbisAlmDelayTime) ...........................................6-108
6.5.25 DTX factor (Info_0_8) ..........................................................................6-109
6.5.26 CS traffic threshold of slave to master (SToMTrafficThrs_0).................... 6-110
6.5.27 PS traffic threshold of slave to master (SToMTrafficThrs_1).................... 6-111
6.5.28 Baseband resource share support (BaseBandShare)............................. 6-113
6.5.29 TRX Selection priority for baseband share (BBSharePri)........................ 6-113
6.5.30 Close back up (CloseBackUp).............................................................. 6-114
6.5.31 Auto slave to master enable (AutoSToMEnable) .................................... 6-115
6.5.32 CIC Manual Block Alarm (CICAlarmSwitch)........................................... 6-116
6.5.33 BVC Manual Block Alarm (BVCAlarmSwitch) ........................................ 6-117
6.5.34 Slave to master time bitmap (SToMTimeBitMap).................................... 6-118
6.5.35 Measurement Result Recording Interval in MSC Invoke Trace
(MITMRRecInt) .................................................................................... 6-119
6.5.36 Preprocessed Measurement Result Recording Interval in MSC Invoke
Trace (MITPrepMRRecInt).................................................................... 6-119
6.6 IBS Parameters............................................................................................... 6-119
6.6.1 The method of intelligent TRX poweroff (Info_0_0) .................................. 6-119
6.7 Performance Management Parameters.............................................................6-120
6.7.1 Pingpong handover duration (PingPongDura) .........................................6-120

XXXVII

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


6.7.2 Number of measurement reports for dropped connections
(LatestMeasureRptNum) ......................................................................6-122
6.7.3 Uplink quality threshold (DropBadQualULThs).........................................6-123
6.7.4 Downlink quality threshold (DropBadQualDLThs) ....................................6-124
6.7.5 Uplink signal strength threshold (DropLowSigStrULThs) ..........................6-125
6.7.6 Downlink signal strength threshold (DropLowSigStrDLThs) ......................6-126
6.7.7 Excessive TA threshold (DropExcessiveTAThs).......................................6-127
6.8 Baseband Frequency Hopping TRX Exchange Parameters................................6-128
6.8.1 Baseband frequency hopping TRX exchange support (Info_0_1)..............6-128
6.8.2 Baseband frequency hopping TRX exchange scan timer (Info_1_0) .........6-129
6.8.3 Baseband frequency hopping TRX configuration timer (Info_1_16) ...........6-130
6.8.4 Baseband frequency hopping TRX exchange check delay timer
(Info_2_0)............................................................................................6-132
6.9 GPRS Operation Control Parameters ...............................................................6-133
6.9.1 Two-phase access (TwoPhaseAccess) ...................................................6-133
6.9.2 Send radio status to SGSN (GBMsgSndInd_0)........................................6-134
6.9.3 Send LLC discard to SGSN (GBMsgSndInd_1) .......................................6-135
6.9.4 Threshold of quality in radio status (RadStaQuaThs) ...............................6-136
6.9.5 Send packet TBF release to MS when BSS abnormal (PacketTBFRel) ......6-137
6.9.6 Initial retry interval in downlink buffer state (DwBufRetryInterval) ..............6-138
6.9.7 Retry number in downlink buffer state (DwBufRetryNum) .........................6-139

Appendix A Flow Control Policy Values.................................................. A-1


Appendix B Power Values ........................................................................ B-1
Appendix C Setting of Cell Layers........................................................... C-1
Appendix D Relationship between Parameter Interface and
Database Value...................................................................................... D-1
D.1 BSC Function Parameters Interface ....................................................................D-1
D.1.1 Basic Property Parameters.......................................................................D-1
D.1.2 Radio Basic Property Parameters .............................................................D-4
D.1.3 Other Parameters ....................................................................................D-4
D.1.4 AMR Half Method Parameters ..................................................................D-5
D.1.5 AMR Full Method Parameters...................................................................D-6
D.1.6 GPRS Property 1 Parameters...................................................................D-7
D.1.7 GPRS Property 2 Parameters...................................................................D-7
D.1.8 EDGE Parameters ...................................................................................D-8
D.2 GERAN External Cell Parameters.......................................................................D-8
D.3 UTRAN External Cell Parameters .......................................................................D-9

XXXVIII

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


D.4 Cell Parameters.................................................................................................D-9
D.4.1 Basic Parameters 1 .................................................................................D-9
D.4.2 Basic Parameters 2 ............................................................................... D-10
D.4.3 Other Parameters .................................................................................. D-10
D.4.4 System Parameters ............................................................................... D-11
D.4.5 GPRS Other Parameters 1 ..................................................................... D-11
D.4.6 GPRS Cell Options Parameters .............................................................. D-11
D.4.7 GPRS NC Survey Parameters ................................................................ D-14
D.4.8 GPRS Power Control Parameters ........................................................... D-15
D.4.9 GPRS Cell Reselection Parameters ........................................................ D-16
D.4.10 GPRS Channel Parameters.................................................................. D-17
D.4.11 EDGE Parameters ............................................................................... D-19
D.5 Cell Object Parameters Interface ...................................................................... D-19
D.5.1 TRX Info Parameters ............................................................................. D-19
D.5.2 Channel Info Parameters........................................................................ D-20
D.5.3 Power Control Parameters ..................................................................... D-21
D.5.4 Handover Control Parameters ................................................................ D-22
D.5.5 UTRAN Cell Control Parameters............................................................. D-23
D.5.6 UTRAN Handover Control Parameters .................................................... D-25
D.5.7 Adjacent Cell Handover and Reselection Parameters............................... D-25
D.5.8 Adjacent Cell Handover Parameters ....................................................... D-25
D.5.9 Frequency Hopping System Parameters ................................................. D-26

Appendix E Mutex Right Management .....................................................E-1


E.1 Applying for the Mutex Right ............................................................................... E-1
E.2 Releasing the Mutex Right.................................................................................. E-1

Figures............................................................................................................. I
Tables ............................................................................................................ III
Glossary .........................................................................................................V

XXXIX

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


XL

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 1
Overview
This chapter explains the definition and classification of radio parameters in GSM network,
modification methods of radio parameters, explanation format of radio parameters, and
precautions in radio parameters adjustment.
Table of Contents
Introduction to BSS Radio Parameters .......................................................................1-1
Modify Parameters .....................................................................................................1-2
Method of Modifying Parameters in Batch ..................................................................1-4
The Format to Explain Parameters .............................................................................1-9
Precautions on Parameter Adjustment .....................................................................1-11

1.1 Introduction to BSS Radio Parameters


Radio parameters in GSM network refer to parameters related to radio devices and radio
resources. These parameters have an important impact on coverage of cells, distribution of
signaling flow and service property of network, etc. Therefore, adjusting radio parameters
reasonably plays a very important part in GSM network optimization.
GSM radio parameters are classified into project parameters and resource (cell)
parameters.
1. Project parameters
Project parameters refer to parameters related to design, installation, and
commissioning of the project, like antenna height, antenna direction, antenna
gain, antenna download obliquity and cable loss, etc. These parameters must be
determined during network design and are seldom changed during the operation of
the network.

2. Resource (cell) parameters


Resource (cell) parameters refer to parameters related to configuration and utilization
of radio resources, which usually transmit on radio interface (Um) to keep the base
station and mobile station consistent. Radio parameters covered in this manual are
mainly resource parameters. Radio resource parameters in BSS contain:
l GERAN subnetwork parameters, BSC management NE parameters,
configuration set parameters;
l Global resource parameters for BSC, site parameters, GERAN external cell
parameters, UTRAN external cell parameters;
l Cell Parameters;

1-1

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

l TRX parameters, power control parameters, handover control parameters,


UTRAN handover control parameters, adjacent interference cell parameters,
adjacent handover cell parameters, adjacent reselection cell parameters,
adjacent handover and reselection cell parameters, UTRAN adjacent cell
handover and reselection parameters, UTRAN adjacent handover cell
parameters, UTRAN adjacent reselection cell parameters, frequency hopping
system parameters.

1.2 Modify Parameters


This section describes how to modify parameters in NetNumen.

Prerequisite
The mutex right have been applied.

Note:
The description of mutex right apply please refer to the Appendix E Mutex Right
Management in this manual.

Steps
1. In the left topology tree of NetNumen U31 main interface, right-click the shortcut menu
corresponding to the created GSM NE agent, select Start.
2. Right-click the started GSM NE and select Start, as shown in Figure 1-1.

1-2

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 1 Overview

Figure 1-1 Starting NE Agent

3. After the NE is started, in the left topology tree of NetNumen U31 main interface,
right-click shortcut menu corresponding to created GSM NE agent, select NE Agent
Management > Configuration Management, the Configuration Management tab
is displayed, as shown in Figure 1-2.

1-3

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Figure 1-2 Configuration Management tab

The tree in the left pane shows the objects to be created and maintained. User
can double-click the node whose parameters shall be modified, the corresponding
parameter interface occurs in right window.
– End of Steps –

1.3 Method of Modifying Parameters in Batch


This section describes how to modify parameters in batch in NetNumen, after successfully
import the data, the modified parameters will be synchronized to NE.
After successfully logging in to NetNumen U31, perform the following steps to modify
parameters in batch.

1. In the configure resource tree window, right-click OMC > GERAN subnet user ID
> BSC Management Element ID > Config Set ID > BSC Function ID > Export
Configuration Data > Export Network Plan Data, as shown in Figure 1-3.

1-4

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 1 Overview

Figure 1-3 Selecting Export Network Plan Data

2. Click Export Network Plan Data, and the Choose MOC to be Exported dialog box
appears. Select the parameter list to be exported, and click Next, as shown in Figure
1-4.

Figure 1-4 Selecting MOC to Be Exported

3. In the Choose Attributes of Each MOC to be Exported (RDN Excluded) dialog box,
select attribute of the parameter list to be exported, and click OK. Here, suppose the
MOC selected is IBSCFUNCTION_TABLE, as shown in Figure 1-5.

1-5

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Figure 1-5 Selecting Attributes to Be Exported for MOC

4. Select the file type to be exported, and click OK. Here, suppose the data is exported
to be an Excel file, as shown in Figure 1-6.

Figure 1-6 Selecting File Type to Be Exported

5. Set the saving path and file name for the exported data, and click Save.
The data export progress bar is displayed, and then the system prompts that the data
is exported successfully.
6. Open the exported data file, as shown in Figure 1-7.

Figure 1-7 Parameter Data

7. Modify the data file according to actual requirement, and save it.

1-6

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 1 Overview

The operation indications are described as follows.


a. D indicates deleting the managed object (MO). A indicates adding the MO. M
indicates modifying the MO (this command is issued only when the parameter
value is changed). Any value beyond D, A, and M (including the lower case form)
will be ignored by the system, and the corresponding data in that row will not be
processed.
b. For the same MO (such as cell, cell power control and cell handover control),
if the operation type (D, A or M) appears in multiple exported tables, then the
operation types of all columns must be the same; otherwise, the system will give
error prompt.
c. No matter how many records in the Excel table should be deleted, created or
modified, the system performs deletion first, then performs creation, and finally
performs modification.

Note:
The order of operations has nothing to do with the order of records being displayed
in the Excel file.

d.
l If multiple objects among which reference relationship exists should be
deleted, the system first deletes the active reference object (such as
sub-object), and then deletes the passive reference object (such as
parent-object).
l If multiple objects among which reference relationship exists should be
created, the system first creates the passive reference object (such as
parent-object), and then creates the active reference object (such as
sub-object).
l If multiple objects among which reference relationship exists should be
modified, the system first modifies the passive reference object (such as
parent-object), and then modifies the active reference object (such as
sub-object).

1-7

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Note:
The following lists the restriction conditions of Excel template:
l The exported Excel file is the import template.
l In the Excel template, the work sheet name cannot be modified.
l In the Excel template, the title row in the work sheet cannot be modified, the
frozen column cannot be modified, and the cell type cannot be modified. However,
common data columns and data rows can be deleted.
l The parameter that cannot be modified on the interface cannot be modified in the
batch modification.
l In the Excel template, the attributes USERLABEL, MCC, MNC, LAC and CI
appear in multiple work sheets, but only the modification in the network parameter
list is valid.
l The parameter MAIO of channels supporting baseband frequency hopping cannot
be modified.

8. In the configuration resource tree window, right-click OMC > GERAN Subnetwork ID
> BSC Managed Element ID > Config Set ID > BSC Function ID > Batch Apply
Network Plan Data, as shown in Figure 1-8.

Figure 1-8 Selecting Batch Apply Network Plan Data

9. Select the file type to be imported, and click OK, as shown in Figure 1-9.

1-8

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 1 Overview

Figure 1-9 Selecting File Type to Be Imported

10. In the Open dialog box, select the data file to be imported, and click Open.
11. In the Batch Network Plan Data Apply dialog box, select the object to which the data
is applied, and click OK, as shown in Figure 1-10.

Figure 1-10 Applying Network Planning Data in Batch

The progress bar is displayed, and then the system prompts that the instruction is
executed successfully.

Note:
If the number of successfully executed instructions is 0, it indicates that no data needs
to be modified. If the number is not 0, it indicates that the data in the file is inconsistent
with that at the server.

1.4 The Format to Explain Parameters


Each radio parameter in this manual is individually clarified in a table. For details, refer to
Table 1-1.

1-9

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Note:
1. Radio parameters in this system is modified through offline modification mode, that is,
the modification on interface only can be effective after the synchronization action to
NE is conducted.
2. Some parameter values in the interface are not fully the same as those in database,
with certain corresponding relationship between them. For specific corresponding
relationship, refer to appendixes.

Table 1-1 Format to Explain Radio Parameters

Full Name English Parameter Name on the Interface

Abbreviation Abbreviation for English parameters

3GPP Name Parameter name in 3GPP protocol

3GPP Reference 3GPP protocol version number for parameter reference

Description Descriptive text for this parameter

Managed Object Involved object by the parameter

Value Range and Value range and step of this parameter. If the parameter is in mapping form,
Step actual parameter value that corresponds to all indices will be enumerated

Unit Parameter unit

Default Value English Parameter Name on the Interface

Default Value
Configuration Reason The reason for setting the default value of this parameter

The factors that are taken into consideration during this parameter
configuration.
Configuration Rule The impact on the network performance and users’ feeling after this
and Adjustment parameter is adjusted to a larger or smaller value.
Suggestion The parameter related to scenarios specifies the adjustment suggestion.

Online = After a parameter’s value is modified, it is immediately synchronized


and takes effect.
Offline = After one or several parameters' values are modified, the
Change Mode modification takes effect after data synchronization.

Relevant functions and features of the network that correspond to this


Related Features parameter

Parameters which have data restriction relationship with the parameter.


For example, this parameter takes effect only after one or multiple relevant
parameters are enabled; this parameter's value has a restriction relationship
with one or multiple relevant parameters, such as larger than or smaller than
Related Parameters the relevant parameter.

1-10

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 1 Overview

Relationship Dependency among relevant parameters

Related Interfaces Interfaces related to this parameter

The impact on the equipment. after the modification of this parameter is


valid. The impact levels are described as follows:
Level 0: Modifying this parameter will bring an impact on the running of this
equipment. That is, during this parameter setting, the equipment is not
influenced.
Level 1: Modifying this parameter will cause the carrier deleted and
established, and the cell out of service.
Level 2: Modifying this parameter will cause the base station out of service.
Impact on Equipment Level 3 : Modifying this parameter will cause BSC out of service.

The impact on the services ( such as, services are interrupted) after the
modification of this parameter is valid. The impact levels are described as
follows:
Level 0: Modifying this parameter will not bring an impact on the idle state
and connection state of the services, but not on the usage and status of all
users. That is, the users cannot detect the change of network service.
Level 1: Modifying this parameter will bring an impact on the users in idle
state, but not on the users during communication or network connection.
Level 2: Modifying this parameter will cause the communication and service
interrupted, but restored in a short while. For example, you can initiate a
service immediately.
Level 3: Modifying this parameter will bring an impact on all users in idle
and connection modes, and will cause the network service interrupted, and
Impact on service restored for a period of time.

Negotiation With CN Whether this parameter should be negotiated with CN

OMC Access Path This parameter’s location on the network management interface

Parameter Modifying
Version Whether this parameter is modified in this version

Parameter Modifying
Detail Modification details of this parameter in this version

1.5 Precautions on Parameter Adjustment


Radio parameters adjustment, according to the type of the problem to be solved, falls into
two kinds.
l First is to solve static problem, that is, to correct traffic model in system design by
measuring actual average traffic and signaling flow in every district and to solve
common problems existing for long.
l Second is to solve problems at a particular time like traffic overload in some district,
channel congestion due to sudden events or random events.

1-11

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

For the first type, service providers must perform measurement and summarization on
actual operation regularly, and then perform appropriate adjustment on global or partial
parameters and configurations. For the second type, network operators adjust some radio
parameters at real time according to instant data from measurement results.
Most radio parameters in GSM system are based on one cell or one location area. It is
necessary to consider whether parameter adjustment in this cell will influence other cells,
especially the adjacent one, for parameters between cells are related to each other greatly.
Otherwise, it may cause negative influence.
Determine whether the problem results from equipment fault (including connections) first
when it occurs in some part of the network. Adjust radio parameters only when determined
that the problem does result from service.

1-12

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2
BSC Function Parameters
Table of Contents
Radio Basic Property..................................................................................................2-1
Functional Switch .....................................................................................................2-26
Other Parameters.....................................................................................................2-45
Channel Allocation Control Parameters ....................................................................2-78
Timer 1.....................................................................................................................2-90
Timer 2...................................................................................................................2-120
GPRS Maximum Retrying Times ............................................................................2-160
GPRS Timer...........................................................................................................2-175
AMR Half Method Parameters................................................................................2-206
AMR Full Method Parameters ................................................................................2-214
GPRS Other Parameters 1 .....................................................................................2-222
GPRS Other Parameters 2 .....................................................................................2-231
BVC Flow Control Parameters................................................................................2-252
FUC Flow Control Map Parameters ........................................................................2-264
EDGE Parameters..................................................................................................2-274
eMLPP Set Parameters..........................................................................................2-295
User Access Flow Control Parameters ...................................................................2-325
UPPB Resource Alarm Parameters........................................................................2-331
AMR-WB Parameter...............................................................................................2-340
Iur-g Parameter ......................................................................................................2-342
Ater Timer Parameters ...........................................................................................2-353

2.1 Radio Basic Property


2.1.1 DCS1800/PCS1900 support (FuncExt)
Full Name DCS1800/PCS1900 support

Abbreviation FuncExt

3GPP Name None

3GPP Reference None

This parameter indicates the supported frequency band. If you select


DCS1800, the DCS1800 frequency band will be supported. If you select
PCS1900, the PCS1900 frequency band will be supported. This param-
Description eter cannot be modified after you select a frequency band.

2-1

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Managed Object BSC

DCS1800
Value Range and Step PCS1900

Unit None

Default Value DCS1800

Default Value
Configuration Reason DCS1800 is a commonly-used frequency band.

Configuration Rule and You can set this parameter according to the actual frequency band
Adjustment Suggestion planning.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 1

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Radio Basic Property

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.1.2 Load indication allowed (LoadInd)


Full Name Load indication allowed

Abbreviation LoadInd

3GPP Name None

3GPP Reference None

2-2

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Load indication is a process in which adjacent BSCs can know the load
of the cells at the border so that more reference information can be
provided in normal handovers and intra-BSC handovers.
This parameter decides whether to enable load indication and whether
LoadValidTime and LoadIndPrd are valid. If the parameter is set to No
(load indication is disabled), LoadValidTime and LoadIndPrd are invalid.
Description Otherwise, they are valid.

Managed Object BSC

0: No
Value Range and Step 1: Yes

Unit None

Default Value No

Default Value
Configuration Reason This is a special functional switch, which is disabled by default.

Configuration Rule and This switch can be enabled upon request. Otherwise, it should be
Adjustment Suggestion disabled.

Change Mode Offline

Related features ZGO-02-02-007 Traffic Based Handover

Related Parameters None

Relationship None

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Radio Basic Property

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.1.3 Send confusion message allowed (ConfusionMsg)


Full Name Send confusion message allowed

Abbreviation ConfusionMsg

3GPP Name None

2-3

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

3GPP Reference None

A confusion message refers to a message that is sent by the SCCP to the


peer end when the SCCP receives a message at the local end but cannot
Description process it correctly and no suitable failure message can be fed back.

Managed Object BSC

0: No
Value Range and Step 1: Yes

Unit None

Default Value No

Default Value Confusion messages are sent only in the connection stage. After the
Configuration Reason BSC and the MSC are connected, such messages do not apply.

Configuration Rule and


Adjustment Suggestion Generally, the default value is recommended.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Radio Basic Property

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.1.4 Inter-cell handover allowed (InHoEnable)


Full Name Inter-cell handover allowed

Abbreviation InHoEnable

3GPP Name None

3GPP Reference None

2-4

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Two methods can be used to implement a handover between two cells in


the same BSC. In one method, the BSC controls the inter-cell handover,
and the MSC is not involved in the handover flow. In the other method,
the MSC is used to implement the inter-cell handover in the BSC, and the
handover flow is similar to an inter-BSC handover flow. This parameter
indicates which method is used for inter-cell handover in the BSC. Set
this parameter to 1 unless specially required. "The parameter value 1
indicates that the inter-cell handover flow is controlled by the BSC; while
the parameter value 0 indicates that inter-cell handover flow is controlled
Description by the MSC.

Managed Object BSC

0: No
Value Range and Step 1: Yes

Unit None

Default Value Yes

The default parameter value is set to 1 because an inter-cell handover


Default Value
controlled by the BSC costs fewer overheads and thus improves the
Configuration Reason
system efficiency when the inter-cell handover is within the same BSC.

Generally, you do not have to modify this paraemter. Note: The


Configuration Rule and
inter-cell handover in the BSC can only be enabled or disabled when
Adjustment Suggestion
HoInterEnable and InHoEnable are set to 1 or 0 at the same time.

Change Mode Offline

Related features ZGB-02-02-001 Basic Handover

Related Parameters [BSC]HoInterEnable

The inter-cell handover in the BSC can only be enabled or disabled


Relationship
when HoInterEnable and InHoEnable are set to 1 or 0 at the same time.

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Radio Basic Property

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-5

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

2.1.5 Send assignment failure allowed in outer direct retry


procedure (ExDRSendAssFail)
Full Name Send assignment failure allowed in outer direct retry procedure

Abbreviation ExDRSendAssFail

3GPP Name None

3GPP Reference None

This parameter decides whether to send the assignment failure message


during external directed retries. If you select Yes, the assignment failure
message will be sent to the MSC when an external directed retry fails. If
Description you select No, no assignment failure message will be sent.

Managed Object BSC

0: No
Value Range and Step 1: Yes

Unit None

Default Value No

Enabling this switch will increase the count of assignment failures


because the MS will still attempt directed retries after the assignment
Default Value
failure message is sent. Besides, some MSCs do not support the
Configuration Reason
sending of the assignment failure message during external directed
retries. The default value "No" can avoid affecting normal counting.

Enabling this switch will increase the count of assignment failures


because the MS will still attempt directed retries after the assignment
Configuration Rule and
failure message is sent. Besides, some MSCs do not support the
Adjustment Suggestion
sending of the assignment failure message during external directed
retries. The default value "No" can avoid affecting normal counting.

Change Mode Offline

Related features ZGB-03-01-002 Directed Retry

Related Parameters None

Relationship None

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN YES

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Radio Basic Property

2-6

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.1.6 Load indication Valid Time (LoadValidTime)


Full Name Load indication Valid Time

Abbreviation LoadValidTime

3GPP Name Time indication IE

48.008 Mobile Switching Centre -Base Station System (MSC-BSC) inter-


3GPP Reference face

In a load indication procedure, the BSC periodically sends a BSSAP


LOAD INDICATION message to the MSC, informing the MSC about the
load status. The BSSAP LOAD INDICATION message contains time
indication information, indicating the valid period of the service load. The
MSC forwards the load information to adjacent BSCs via BSSAP LOAD
INDICATION message. This parameter indicates the valid period of
the load information. 255The parameter value 255 means that the load
Description information is valid permanently.

Managed Object BSC

0..255
Value Range and Step Step: 1

Unit 10 s

Default Value 18

Generally, the validity of load information is acceptable in 180s with the


Default Value
consideration that the network load rarely fluctuates greatly in such a
Configuration Reason
period.

Generally, you do not have to modify this parameter and the default
value is recommended. If the parameter value is too large, the MSC
Configuration Rule and
regards that the current load has a long valid period, which cannot reflect
Adjustment Suggestion
the actual load variation of the BSC. If the parameter value is too small,
the reported load information becomes invalid in a short time.

Change Mode Offline

Related features ZGB-03-04-001 BSC Load Control

Related Parameters None

Relationship None

2-7

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Radio Basic Property

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.1.7 Load Indication Period (LoadIndPrd)


Full Name Load Indication Period

Abbreviation LoadIndPrd

3GPP Name None

3GPP Reference None

In a load indication procedure, the BSC periodically sends a BSSAP


LOAD INDICATION message to the MSC, informing the MSC about the
load status. The BSSAP LOAD INDICATION message contains time
indication information, indicating the valid period of the service load. The
MSC forwards the load information to adjacent BSCs via BSSAP LOAD
INDICATION message. This parameter specifies the period for the BSC
Description to send a BSSAP LOAD INDICATION message to the MSC.

Managed Object BSC

10..65530
Value Range and Step Step: 1

Unit 100 ms

Default Value 1500

Default Value Generally, the load information of a BSC needs an update every 150s. A
Configuration Reason longer update period may reduce the accuracy of load information.

Generally, you do not have to modify this parameter and the default
value is recommended. If the parameter value is too large, the load
Configuration Rule and
indication message cannot accurately reflect the load variation of the
Adjustment Suggestion
BSC. If the parameter value is too small, the frequent reporting of the
load indication message will cause the waste of signalling link resources.

Change Mode Offline

2-8

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Related features ZGB-03-04-001 BSC Load Control

Related Parameters None

Relationship None

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Radio Basic Property

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.1.8 Congestion Threshold for Send Load Indication (LoadIndThs)


Full Name Congestion Threshold for Send Load Indication

Abbreviation LoadIndThs

3GPP Name None

3GPP Reference None

If the cell load in this BSC is higher than the value of this parameter, the
system initiates a load indication process, which make adjacent BSCs
know the load of the cells at the border so that more reference information
Description can be provided in normal handovers and intra-BSC handovers.

Managed Object BSC

Value Range and Step 0..100

Unit %

Default Value 100

Default Value It is a functional parameter and is configured to 100 (no load indication is
Configuration Reason initiated) by default.

Configuration Rule and


Adjustment Suggestion Currently, this parameter is not used and need not be adjusted.

Change Mode Offline

Related features None

Related Parameters None

2-9

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Radio Basic Property

Parameter Modifying
Version iBSCV6.20.615

Parameter Modifying
Detail New

2.1.9 Forbid Handover According to Resource Threshold of Load


Indication (LoadForbidHo)
Full Name Forbid Handover According to Resource Threshold of Load Indication

Abbreviation LoadForbidHo

3GPP Name None

3GPP Reference None

This parameter determines whether to prohibit handover to an external


Description adjacent cell with the resource usage higher than that of load indication.

Managed Object BSC

0: No
Value Range and Step 1: Yes

Unit None

Default Value No

Default Value
Configuration Reason It is a functional parameter and is configured to "No" by default.

Configuration Rule and


Adjustment Suggestion Currently, this parameter is not used and need not be adjusted.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

2-10

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Radio Basic Property

Parameter Modifying
Version iBSCV6.20.615

Parameter Modifying
Detail New

2.1.10 Resource Threshold of Load Indication for Forbid Handover


(LoadThsForbidHo)
Full Name Resource Threshold of Load Indication for Forbid Handover

Abbreviation LoadThsForbidHo

3GPP Name None

3GPP Reference None

If the resource usage of an external adjacent cell is higher than the value
Description of this parameter, the system does not trigger handover to the cell.

Managed Object BSC

Value Range and Step 0..100

Unit %

Default Value 100

It is a functional parameter and is configured to 100 by default, which


Default Value
indicates that handover to the external adjacent cell initiating the load
Configuration Reason
indication process is not prohibited.

Configuration Rule and


Adjustment Suggestion Currently, this parameter is not used and need not be adjusted.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

2-11

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Radio Basic Property

Parameter Modifying
Version iBSCV6.20.615

Parameter Modifying
Detail New

2.1.11 Support Precise Paging (PrecisePagSupport)


Full Name Support Precise Paging

Abbreviation PrecisePagSupport

3GPP Name None

3GPP Reference None

This parameter determines the switch of BSC exact paging. This function
indicates that the system performs paging in the cells for exact paging. If
the system does not page any subscriber, it performs paging within the
paging range of the core network. The exact paging cells include the Visit
Paging Cell (VPC) and Home Paging Cell (HPC). The VPC indicates a
cell around the cell where the last service exists. It can be a handover
or reselection adjacent cell, or can be configured additionally. The HPC
indicates a group of cells calculated based on the cells where latest ser-
Description vices are triggered.

Managed Object BSC

0: No
Value Range and Step 1: Yes

Unit None

Default Value 0

Default Value
Configuration Reason This parameter is a functional switch, which disabled by default.

Generally, configure this parameter according to operator requirements.


Configuration Rule and
In the case of large paging volume, enable the exact paging function
Adjustment Suggestion
to save CCCH channels.

Change Mode Offline

Related features None

Related Parameters [Cell]CsPrecisePaging


[Cell]PsPrecisePaging

2-12

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Only when the BSC and cell exact paging switches are both enabled,
Relationship the system can perform exact paging. This function is applicable to
the client.

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Radio Basic Property

Parameter Modifying
Version iBSCV6.20.710

Parameter Modifying
Detail New

2.1.12 Use HPC for Precise Paging (PrecisepagUseHpc)


Full Name Use HPC for Precise Paging

Abbreviation PrecisepagUseHpc

3GPP Name None

3GPP Reference None

If this parameter is configured to "No", only the VPC is used for exact
paging. If this parameter is configured to "Yes", both the VPC and HPC
Description are used for exact paging.

Managed Object BSC

0: No
Value Range and Step 1: Yes

Unit None

Default Value 0

Default Value
Configuration Reason By default, the selection function is disabled.

Configuration Rule and For the fixed cells such as housing and residential areas, the HPC can
Adjustment Suggestion be used.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

2-13

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Radio Basic Property

Parameter Modifying
Version iBSCV6.20.710

Parameter Modifying
Detail New

2.1.13 Adopt Precise Paging for repaging of Circuit Switched


Service (CsRepagPrecise)
Full Name Adopt Precise Paging for repaging of Circuit Switched Service

Abbreviation CsRepagPrecise

3GPP Name None

3GPP Reference None

When the first paging is not responded for the CS service, the core net-
work may initiate paging for another time. This parameter determines
whether the exact paging policy is applied for subsequent paging opera-
Description tions of the CS service in the core network.

Managed Object BSC

0: No
Value Range and Step 1: Yes

Unit None

Default Value 0

Default Value
Configuration Reason The paging time must not be excessively long.

It is required to configure this parameter according to operator


Configuration Rule and
requirements. When subscribers can accept a relatively long connection
Adjustment Suggestion
time, enable this switch.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

2-14

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Radio Basic Property

Parameter Modifying
Version iBSCV6.20.710

Parameter Modifying
Detail New

2.1.14 Adopt Precise Paging for repaging of Packet Switched


Service (PsRepagPrecise)
Full Name Adopt Precise Paging for repaging of Packet Switched Service

Abbreviation PsRepagPrecise

3GPP Name None

3GPP Reference None

When the first paging is not responded for the PS service, the core net-
work may initiate paging for another time. This parameter determines
whether the exact paging policy is applied for subsequent paging opera-
Description tions of the PS service in the core network.

Managed Object BSC

0: No
Value Range and Step 1: Yes

Unit None

Default Value 0

Default Value
Configuration Reason The paging time must not be excessively long.

It is required to configure this parameter according to operator


Configuration Rule and requirements. When PS paging is mainly for non real-time services or
Adjustment Suggestion subscribers can accept a relatively long connection time, enable this
switch.

Change Mode Offline

Related features None

Related Parameters None

2-15

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Radio Basic Property

Parameter Modifying
Version iBSCV6.20.710

Parameter Modifying
Detail New

2.1.15 Allow Exceed area Precise Paging for Circuit Switched


Service (CsOutAreaPag)
Full Name Allow Exceed area Precise Paging for Circuit Switched Service

Abbreviation CsOutAreaPag

3GPP Name None

3GPP Reference None

This parameter determines whether the exact paging of CS service covers


the cells out of the paging range of core network. The paging of CS service
is usually applied for location cells. However, some VPCs and HPCs may
Description not in these location cells.

Managed Object BSC

0: No
Value Range and Step 1: Yes

Unit None

Default Value 0

Default Value
Configuration Reason Usually, subscribers are not out of the paging range of core network.

Usually, this function is disabled. When the location cell is updated and
Configuration Rule and
the BSC fails to acquire IMSI to record the subscriber location, this
Adjustment Suggestion
function can be enabled.

Change Mode Offline

Related features None

Related Parameters None

2-16

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Radio Basic Property

Parameter Modifying
Version iBSCV6.20.710

Parameter Modifying
Detail New

2.1.16 Allow Exceed area Precise Paging for Packet Switched


Service (PsOutAreaPag)
Full Name Allow Exceed area Precise Paging for Packet Switched Service

Abbreviation PsOutAreaPag

3GPP Name None

3GPP Reference None

This parameter determines whether the exact paging of PS service covers


the cells out of the paging range of core network. The paging of PS service
is usually applied for routing cells. However, some VPCs and HPCs may
Description not in these routing cells.

Managed Object BSC

0: No
Value Range and Step 1: Yes

Unit None

Default Value 0

Default Value
Configuration Reason Usually, subscribers are not out of the paging range of core network.

Usually, this function is disabled. When the routing cell is updated and
Configuration Rule and
the BSC fails to acquire IMSI to record the subscriber location, this
Adjustment Suggestion
function can be enabled.

Change Mode Offline

Related features None

Related Parameters None

2-17

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Radio Basic Property

Parameter Modifying
Version iBSCV6.20.710

Parameter Modifying
Detail New

2.1.17 Paging Repeat Time for Circuit Switched Service


(CsPagingRepeatTime)
Full Name Paging Repeat Time for Circuit Switched Service

Abbreviation CsPagingRepeatTime

3GPP Name None

3GPP Reference None

This parameter determines the maximum retry times of CS service paging


(exact paging excluded). When the first paging is not responded, the
system can initiate multiple paging operations according to the value of
Description this parameter.

Managed Object BSC

Value Range and Step 0..2

Unit times

Default Value 0

Default Value Usually, multiple paging operations are applied on the BSC only when
Configuration Reason this function is not applied in the core network.

Configuration Rule and Multiple paging operations are applied on the BSC only when this
Adjustment Suggestion function is not applied in the core network.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

2-18

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Impact on Equipment 0

Impact on service 0

Negotiation With CN YES

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Radio Basic Property

Parameter Modifying
Version iBSCV6.20.710

Parameter Modifying
Detail New

2.1.18 Paging Repeat Time for Packet Switched Service


(PsPagingRepeatTime)
Full Name Paging Repeat Time for Packet Switched Service

Abbreviation PsPagingRepeatTime

3GPP Name None

3GPP Reference None

This parameter determines the maximum retry times of PS service paging


(exact paging excluded). When the first paging is not responded, the
system can initiate multiple paging operations according to the value of
Description this parameter.

Managed Object BSC

Value Range and Step 0..2

Unit times

Default Value 0

Default Value Usually, multiple paging operations are applied on the BSC only when
Configuration Reason this function is not applied in the core network.

Configuration Rule and Multiple paging operations are applied on the BSC only when this
Adjustment Suggestion function is not applied in the core network.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

2-19

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Negotiation With CN YES

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Radio Basic Property

Parameter Modifying
Version iBSCV6.20.710

Parameter Modifying
Detail New

2.1.19 Automatic Resource Indication Threshold (ResourceIndThs)


Full Name Automatic Resource Indication Threshold

Abbreviation ResourceIndThs

3GPP Name None

3GPP Reference None

This parameter indicates the rate of available channels, which is used


as a threshold for determining whether the BSC automatically sends a
resource indication message to the MSC. When the rate of available
channels in a cell is lower than this threshold, the BSC is required to
inform the MSC about the resource status in the cell by sending a
resource indication message. O&M is used to configure this parameter.
The four modes of resource indication from BSC are as follows:
Automatic mode: Upon receiving a BSSAP RESOURCE REQUEST
message, the BSC immediately responds with a BSSAP RESOURCE
INDICATION message containing no resource information. After that,
the BSC automatically sends a BSSAP RESOURCE INDICATION
message to the MSC when the condition of automatic response is met,
which may be a threshold or message interval preset by the O&M of the
BSC. Periodicity IE in the BSSAP RESOURCE REQUEST message
is used to indicate the interval between messages when the value of
Periodicity IE is not 0. Periodicity IE with a value of 0 will be neglected
by the BSC. BSSAP RESUORCE INDICATION
One-time mode: Upon receiving a BSSAP RESOURCE REQUEST
message, the BSC immediately responds with a BSSAP RESOURCE
INDICATION message containing the resource information. If the
BSSAP RESOURCE REQUEST message does not contain Extended
Resource Indication IE, the BSC stops sending the resource information
and waits for the next BSSAP RESOURCE REQUEST message. If the
BSSAP RESOURCE REQUEST message contains Extended Resource
Indication IE, the BSC complies with the mode specified by Subsequent

Description Mode in the message, that is, mode 4. If the previous mode is 1 or 3,

2-20

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

the BSC will use mode 1 or 3. If the previous mode is not 1 or 3, the
BSC will use mode 4. .
Periodic mode: Upon receiving a BSSAP RESOURCE REQUEST
message, the BSC immediately responds with a BSSAP RESOURCE
INDICATION message containing the resource information, and then
periodically sends a BSSAP RESOURCE INDICATION message. If the
value of Periodicity IE in the BSSAP RESOURCE REQUEST message
is not 0, the period of sending the indication message is the product of
100ms and Periodicity IE. If the value of Periodicity IE is 0, the BSSAP
RESOURCE REQUEST message is regarded as an error message.
Stop mode: Upon receiving a BSSAP RESOURCE REQUEST message,
the BSC immediately responds with a BSSAP RESOURCE INDICATION
message containing no resource information. And then the BSC will not
send the resource information of the cell to the MSC any longer.

Managed Object BSC

0..100
Value Range and Step Step: 1

Unit %

Default Value 30

The default value is an experimental value based on the need when


Default Value the BSC should report a resource indication to the MSC. The report of
Configuration Reason resource indication is recommended when the rate of available channels
is lower than 30%.

Generally, the default value is recommended. The larger the parameter


Configuration Rule and value is, the more easily the automatic resource indication is triggered.
Adjustment Suggestion The smaller the parameter value is, the more difficultly the automatic
resource indication is triggered.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Radio Basic Property

2-21

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.1.20 BSC maximum reset number (BscMaxResetNum)


Full Name BSC maximum reset number

Abbreviation BscMaxResetNum

3GPP Name None

3GPP Reference None

This parameter indicates the maximum number of BSC resets. After the
BSC sends the BSSAP RESET message to the MSC, if the BSC does
not receive the BSSAP RESET ACKNOWLEDGE message from the
MSC in the specified time T4, the reset process will be repeated.
The BSSAP RESET message will be sent repeatedly at most N times. If
the BSC does not receive a response after N times, it will stop the reset
Description process and notify the OMS. N depends on this parameter.

Managed Object BSC

Value Range and Step 1..255; step: 1

Unit None

Default Value 3

Default Value
Configuration Reason Generally, It is enough to repeat the BSC reset process three times.

Generally, the default value is recommended. The higher the value is,
Configuration Rule and
the more the BSC will repeat the reset if it does not receive the BSSAP
Adjustment Suggestion
RESET ACKNOWLEDGE message from the MSC.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

2-22

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Radio Basic Property

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.1.21 MR report support (MrRptEnable)


Full Name MR report support

Abbreviation MrRptEnable

3GPP Name None

3GPP Reference None

This parameter decides whether to enable the data report function and
use it along with MrRptTimap. If this function is enabled, measurement
data will be reported to the NMS. The function is used to store the mea-
surement reports from NEs into the NMS for the purpose of analyzing MS
Description users' behaviors.

Managed Object BSC

Yes, No
Yes: Enable
Value Range and Step No: Disable

Unit None

Default Value No

Default Value
Configuration Reason This is a special functional switch, which is disabled by default.

Configuration Rule and When you enable the MR data collection function, you should enable
Adjustment Suggestion this parameter.

Change Mode Offline

Related features ZGO-06-01-005 Massive Measurement Report

Related Parameters None

Relationship None

Related Interfaces ABIS

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

2-23

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Radio Basic Property

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.1.22 HBTS scan site number (HBTSScanSiteNum)


Full Name HBTS scan site number

Abbreviation HBTSScanSiteNum

3GPP Name None

3GPP Reference None

This parameter indicates the number of S8001 sites in each scan. 0The
Description value 0 means disabling the fixed-time scan function.

Managed Object BSC

0..10
Value Range and Step Step: 1

Unit None

Default Value 10

Default Value Each CMP supports 256 sites at most. It is reasonable that the CMP
Configuration Reason should scan 10 sites each time due to its capacity limits.

Configuration Rule and The higher the value is, the more heavily the CMP is loaded. The default
Adjustment Suggestion value is recommended.

Change Mode Offline

Related features None

Related Parameters [BSC]HBTSScanBT


[BSC]HBTSScanCyc

If this parameter is set to 0, the parameters HBTSScanCyc and


Relationship
HBTSScanBT are configurable but invalid.

Related Interfaces Abis口

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed element ID->Config set


OMC Access Path
ID->BSC Function->Radio Basic Proerty

2-24

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.1.23 Range of Barang


Full Name Range of Barang

Abbreviation None

3GPP Name None

3GPP Reference None

The value of this parameter can be a single frequency or a frequency


range, which is sent to the MS in the CHANNEL RELEASE message.
When selecting a cell, the MS can detect some frequencies first.
You can add a frequency range by setting the minimum value and the
maximum value in the BARANGE pane and clicking Add. A same value
range can be shared by different global resources.
Description Frequency ranges must not have intersections.

Managed Object BSC

PGSM (1..124)
EGSM (0..124, 975..1023)
DCS1800 (512..885)
GSM1900 (512..810)
Value Range and Step GSM850 (128..251)

Unit None

Default Value 0&&0

Default Value Normal services can be ensured even if you set no frequency for the
Configuration Reason prioritized detection made by the MS.

Configuration Rule and


Adjustment Suggestion The default value is recommended.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces ABIS

Impact on Equipment 0

Impact on service 0

2-25

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Radio Basic Property

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.2 Functional Switch


2.2.1 RIM support (RIMSupport)
Full Name RIM support

Abbreviation RIMSupport

3GPP Name RIM

3GPP Reference 3GPP TS 48.018

This parameter is a switch to support RIM function.


The RIM function is used for fast cell reselection between two BSCs
(including BSC-RNC cell reselection). During an external Network
Assisted Cell Change (NACC), the BSC sends the system information
of the target cell to the MS in the source cell before the MS starts the
cell reselection. In this way, the MS can quickly get access to the target
cell because the time needed for receiving the system information of the
target cell is saved after the MS reselects the target cell.
The external NACC of the BSC needs to acquire the system information
of the cell outside the BSC through a RAN Information Management
(RIM) process between the SGSN and the BSC.
If the BSC supports the RIM function, an RIM process is triggered by
service to acquire, store, and update the system information of the
external cell. Accordingly, the BSC, which supports the RIM function,
shall provide the system information of a cell inside the BSC when
required by another BSC/RNC, and informs this BSC/RNC about the
Description change when the system information of the internal cell changes.

Managed Object BSC

Yes/No
Value Range and Step 0: No; 1: Yes

Unit None

Default Value No

2-26

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Default Value
Configuration Reason This is a special functional switch, which is disabled by default.

Enable this switch when the external NACC function is enabled. After
the switch is enabled, an RIM process can be initiated between the
Configuration Rule and
SGSN and the BSC to get the system information of a cell outside the
Adjustment Suggestion
BSC. In this way, the MS can get access to the target cell more quickly
during a cell reselection.

Change Mode Offline

Related features ZGO-02-02-011 Inter-BSC NACC

Related Parameters [BSC]RIMRetryTimes

Relationship The parameter RIMRetryTimes is valid only when this switch is enabled.

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Functional Switch

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.2.2 RIM retry times (RIMRetryTimes)


Full Name RIM retry times

Abbreviation RIMRetryTimes

3GPP Name None

3GPP Reference None

This parameter indicates the number of RIM retries. The maximum num-
Description ber of RIM retries is 3.

Managed Object BSC

0..3
Value Range and Step Step: 1

Unit None

Default Value 0

2-27

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Default Value
Configuration Reason The default value is 0 because the RIM function is disabled by default.

Set this parameter for external NACC when the RIM function is enabled.
Configuration Rule and
It is recommended to disable the RIM function because it requires the
Adjustment Suggestion
support of the CN.

Change Mode Offline

Related features ZGO-02-02-011 Inter-BSC NACC

Related Parameters [BSC]RIMSupport

Relationship This parameter can be set only when the RIM function is enabled.

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Functional Switch

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.2.3 Different reselection parameter in idle and transfer status


support (PSReselParam2)
Full Name Different reselection parameter in idle and transfer status support

Abbreviation PSReselParam2

3GPP Name None

3GPP Reference None

This parameter indicates whether two sets of measurement and reselec-


tion parameters can be used at the same time in idle state and packet
Description transmission state. This function is not in use currently.

Managed Object BSC

Value Range and Step 1: Yes; 0: No

Unit None

Default Value No

2-28

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Default Value
Configuration Reason This function is disabled by default because this parameter is not in use.

Configuration Rule and


Adjustment Suggestion The default value is recommended.

Change Mode Offline

ZGO-02-02-013 Different Cell Reselection Parameters for IDLE and AC-


Related features TIVE Status

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Functional Switch

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.2.4 Handover synchronization indication support (Info_0_16)


Full Name Handover synchronization indication support

Abbreviation Info_0_16

3GPP Name None

3GPP Reference None

This parameter decides whether the handover synchronization


information contains the synchronization indication bit and whether the
handover completion message contains the Mobile Time Difference unit
and normal cell indication.
Description
It indicates whether handover synchronization indication is supported.
If the parameter's value is Yes, handover synchronization indication is
supported. For both synchronization handover and asynchronization
handover, ROT in the handover completion message is 1.

Managed Object None

Value Range and Step Yes/No

2-29

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Unit None

Default Value No

Default Value
Configuration Reason None

Configuration Rule and


Adjustment Suggestion None

Change Mode Offline

Related Features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Functional Switch

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.2.5 Switch of TRAU frame synchronized monitor (Info_4_5)


Full Name Switch of TRAU frame synchronized monitor

Abbreviation Info_4_5

3GPP Name call release after loss of TRAU frame synchronization

3GPP Reference 3GPP TS 48.060, 3GPP TS 48.061

This parameter indicates whether you can release the call when TRAU
Description frame synchronization has been lost for a period.

Managed Object BSC

Value Range and Step Yes/No

Unit None

Default Value No

Default Value
Configuration Reason None

2-30

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Configuration Rule and


Adjustment Suggestion None

Change Mode Offline

Related Features None

Related Parameters [BSC]TuTrauSyn

The timer of TRAU frame synchronization takes effect only if Info_4_5


Relationship
is enabled.

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Functional Switch

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.2.6 PS handover support (PSHoSupp)


Full Name PS handover support

Abbreviation PSHoSupp

3GPP Name None

3GPP Reference None

Description This parameter determine whether PS handover is supported.

Managed Object BSC

Value Range and Step Yes/No

Unit None

Default Value No

Default Value
Configuration Reason None

Configuration Rule and


Adjustment Suggestion None

Change Mode Offline

Related Features None

2-31

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Functional Switch

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.2.7 Enable PS Handover Indications in Inter-BSS handover


(EnablePSHoIndi)
Full Name Enable PS Handover Indications in Inter-BSS handover

Abbreviation EnablePSHoIndi

3GPP Name None

3GPP Reference None


It determines whether PS Handover Indications is enabled during
Description inter-BSS handover.

Managed Object BSC

Value Range and Step Yes, No

Unit None

Default Value Yes

Default Value
Configuration Reason None

Configuration Rule and


Adjustment Suggestion None

Change Mode Offline

Related Features None

Related Parameters None

Relationship None

Related Interfaces None

2-32

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Functional Switch

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.2.8 Request SI/PSI (EnableRequestPSI)


Full Name Request SI/PSI

Abbreviation EnableRequestPSI

3GPP Name None

3GPP Reference None

Description It determine if request SI/PSI is enabled.

Managed Object BSC

Value Range and Step


Yes, No

Unit None

Default Value Yes

Default Value
Configuration Reason None

Configuration Rule and


Adjustment Suggestion None

Change Mode Offline

Related Features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

2-33

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Functional Switch

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.2.9 Support EMLPP (SupportEMLPP)


Full Name Support EMLPP

Abbreviation SupportEMLPP

3GPP Name None

3GPP Reference None

This parameter determine whether EMLPP is supported in this cell.


Description
This parameter is supported from version 6.20.61.

Managed Object BSC

Yes/No
Value Range and Step
0: No; 1: Yes

Unit None

Default Value 是

Default Value
Configuration Reason None

Configuration Rule and


Adjustment Suggestion None

Change Mode Offline

Related Features ZGO-01-03-001 eMLPP

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Functional Switch

Parameter Modifying
Version None

2-34

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Parameter Modifying
Detail None

2.2.10 DFCA support (DFCASupport)


Full Name DFCA support

Abbreviation DFCASupport

3GPP Name None

3GPP Reference None

This parameter determines whether to support the Dynamic Frequency


Description and Channel Allocation (DFCA) function.
Unsupported

Managed Object BSC

Value Range and Step Yes/No

Unit None

Default Value No

Default Value
Configuration Reason None

Configuration Rule and


Adjustment Suggestion None

Change Mode Offline

Related Features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Functional Switch

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-35

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

2.2.11 Support resource optimizing by service (SuppResOpBySe


rvice)
Full Name Support resource optimizing by service

Abbreviation SuppResOpByService

3GPP Name None

3GPP Reference None

This parameter determines whether to enable the function of resource


Description control based on the classification of subscriber services.

Managed Object BSC

0: No
Value Range and Step 1: Yes

Unit None

Default Value 0

Default Value
Configuration Reason This parameter is a functional switch, which is disabled by default.

Configuration Rule and


Adjustment Suggestion Enable this switch as required.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Functional Switch

Parameter Modifying
Version iBSCV6.20.710

Parameter Modifying
Detail New

2.2.12 Identify of special service (SpecServiceIdentify)


Full Name Identify of special service

2-36

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Abbreviation SpecServiceIdentify

3GPP Name None

3GPP Reference None

This parameter determines which solution (DSCP or BSSGP) is used to


Description identify the specific service.

Managed Object BSC

0: DSCP
Value Range and Step 1: BSSGP extend

Unit None

Default Value 0

Default Value
Configuration Reason By default, the DSCP solution is used.

Configuration Rule and This parameter requires negotiation with the core network and then
Adjustment Suggestion determines the solution used for identification.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN YES

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Functional Switch

Parameter Modifying
Version iBSCV6.20.710

Parameter Modifying
Detail New

2.2.13 DTM Enhance Capability (DTMEnhanceCapa)


Full Name DTM Enhance Capability

Abbreviation DTMEnhanceCapa

3GPP Name None

3GPP Reference None

2-37

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

This parameter determines whether the BSC supports enhanced DTM


functions. If yes, the MS establishes the DTM service without releasing
Description the current PS service.

Managed Object BSC

0: No
Value Range and Step 1: Yes

Unit None

Default Value No

Default Value
Configuration Reason These functions are not provided in the current version.

Configuration Rule and It is required to configure this parameter according to the DTM settings
Adjustment Suggestion and the functions supported by the current version.

Change Mode Offline

Related features None

Related Parameters [Cell]DTMEnhanceCap

This parameter is valid after the switch of enhanced DTM functions for
Relationship
the cell is enabled.

Related Interfaces Um Interface

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Functional Switch

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.2.14 E-UTRAN CCN support (EUtranCCN)


Full Name E-UTRAN CCN support

Abbreviation EUtranCCN

3GPP Name E-UTRAN_CCN_ACTIVE

3GPP Reference 3GPP TS 44018 V8.9.0

This parameter determines whether to enable the CCN function between


Description a GSM cell and an adjacent LTE cell.

2-38

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Managed Object BSC

Value Range and Step 1: Yes; 0: No

Unit None

Default Value 0

Default Value
Configuration Reason This parameter is a functional switch, which is disabled by default.

Configuration Rule and This function is not implemented in the current version. Hence, it is
Adjustment Suggestion recommended that this function be disabled.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Functional Switch

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.2.15 Duration of judging from concurrent to special service


(ConcurrentJudge0)
Full Name Duration of judging from concurrent to special service

Abbreviation ConcurrentJudge0

3GPP Name None

3GPP Reference None

TBF bears both normal service and specific service. If the time for re-
ceiving a data packet of specific service exceeds the configured time, the
Description system considers that the TBF bears only the specific service.

Managed Object BSC

Value Range and Step 0..60000

2-39

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Unit ms

Default Value 10000

Default Value The precision and timeliness of identification for the specific service are
Configuration Reason taken into consideration.

This parameter cannot be configured too low, which may cause the
ping-pong oscillation of service identification between the concurrent
Configuration Rule and
service and specific service. This parameter cannot be configured too
Adjustment Suggestion
high, which may affect the identification timeliness from the concurrent
service to the specific service.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Functional Switch

Parameter Modifying
Version iBSCV6.20.710

Parameter Modifying
Detail New

2.2.16 Number of llc judging from concurrent to special service


(ConcurrentJudge1)
Full Name Number of llc judging from concurrent to special service

Abbreviation ConcurrentJudge1

3GPP Name None

3GPP Reference None

If the number of LLC frames for the normal service is larger than the value
of this parameter during judgment from the concurrent service to the spe-
Description cific service, the system restarts this judgment process.

Managed Object BSC

Value Range and Step 0..1000

2-40

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Unit None

Default Value 20

Default Value The short-time complex service that may occur during conversion from
Configuration Reason the concurrent service to the specific service is taken into consideration.

The larger the value of this parameter, the higher the possibility of
being considered as the specific service but the lower the precision.
Configuration Rule and
The smaller the value of this parameter, the higher the requirement on
Adjustment Suggestion
conversion from the concurrent service to the specific service and the
higher the precision.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Functional Switch

Parameter Modifying
Version iBSCV6.20.710

Parameter Modifying
Detail New

2.2.17 Duration of judging from special to non-special service


(ConcurrentJudge2)
Full Name Duration of judging from special to non-special service

Abbreviation ConcurrentJudge2

3GPP Name None

3GPP Reference None

TBF bears both normal service and specific service. If the time for receiv-
ing a data packet of non-specific service exceeds the configured time,
the system considers that the TBF bears the concurrent service or nor-
Description mal service.

Managed Object BSC

2-41

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Value Range and Step 0..60000

Unit ms

Default Value 5000

Default Value The precision and timeliness of identification from the specific service to
Configuration Reason the concurrent service or normal service are taken into consideration.

This parameter cannot be configured too low, which may cause the
ping-pong oscillation of service identification between the specific
Configuration Rule and
service and non-specific service. This parameter cannot be configured
Adjustment Suggestion
too high, which may affect the identification timeliness from the specific
service to the concurrent service or normal service.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Functional Switch

Parameter Modifying
Version iBSCV6.20.710

Parameter Modifying
Detail New

2.2.18 Number of llc judging from special to non-special service


(ConcurrentJudge3)
Full Name Number of llc judging from special to non-special service

Abbreviation ConcurrentJudge3

3GPP Name None

3GPP Reference None

If the number of LLC frames for the specific service is larger than the
value of this parameter during judgment from the specific service to the
concurrent service or normal service, the system restarts this judgment
Description process.

2-42

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Managed Object BSC

Value Range and Step 0..1000

Unit None

Default Value 20

The short-time specific service that may occur during conversion from
Default Value
the specific service to the concurrent service or normal service is taken
Configuration Reason
into consideration.

The larger the value of this parameter, the higher the possibility of
being converted from the specific service to the concurrent service or
Configuration Rule and normal service but the lower the precision. The smaller the value of this
Adjustment Suggestion parameter, the higher the requirement on conversion from the specific
service to the concurrent service or normal service and the higher the
precision.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Functional Switch

Parameter Modifying
Version iBSCV6.20.710

Parameter Modifying
Detail New

2.2.19 If get Utran classmrak information from UE (GetUtranClass)


Full Name If get Utran classmrak information from UE

Abbreviation GetUtranClass

3GPP Name Null

3GPP Reference Null

2-43

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

If the UE performs handover from 3G network to 2G network, the


Handover Request message may not contain the UtranClassmark of the
MS, or the message contain the wrong information of UtranClassmark. If
the UE later performs a 2G-to-3G handover, the operation is easy to fail
due to lack of the correct UtranClassmark information.
If the switch is on, after the UE perform handover from the external
network to the BSC, the BSC will initiate a classmark request, requiring
Description the UE to report its UtranClassmark.

Managed Object BSC

0: No
Value Range and Step 1: Yes

Unit None

Default Value 0

Default Value The classmark request procedure increases the system load, so the
Configuration Reason switch is off generally.

If the connected RNC sends a handover request with incomplete or


Configuration Rule and
outdated information, which reduces the success rate for 2G-to-3G
Adjustment Suggestion
handover, enabling the feature is necessary.

Change Mode Offline

Related features Null

Related Parameters Null

Relationship Null

Related Interfaces Null

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Functional Switch

Parameter Modifying
Version iBSCV6.20.711a

Parameter Modifying
Detail New

2-44

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

2.3 Other Parameters


2.3.1 Supervision Timer of LCS (LcsSuperVision)
Full Name Supervision Timer of LCS

Abbreviation LcsSuperVision

3GPP Name None

3GPP Reference None

This parameter is a timer used for supervising a location process.


Start: When the BSC sends a location request to the SMLC.
Stop: When a location acknowledgement message is received.
Description At expiry: Terminate the location process.

Managed Object BSC

100..1000
Value Range and Step Step: 1

Unit 100 ms

Default Value 250

Default Value
Configuration Reason Generally, a location process can be completed in 25 seconds.

Generally, the default value is recommended. The larger the parameter


Configuration Rule and
value is, the longer the waiting time is after a location request is sent.
Adjustment Suggestion
Similarly, a smaller parameter value indicates a shorter waiting time.

Change Mode Offline

Related features ZGO-01-03-002 LCS with CGI+TA &ZGO-01-03-003 LCS with AGPS

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-45

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

2.3.2 Radio Timer of LCS (LcsRadio)


Full Name Radio Timer of LCS

Abbreviation LcsRadio

3GPP Name None

3GPP Reference None

This parameter is a timer used for supervising the sending of radio


information in the location process.
Start: When a location-related message is sent to the MS.
Stop: When an acknowledgement message is received from the MS.
Description At expiry: Terminate the location process.

Managed Object BSC

10..100
Value Range and Step Step: 1

Unit 100 ms

Default Value 50

Default Value Generally, the sending of radio information in the location process can
Configuration Reason be completed in five seconds.

Generally, the default value is recommended. The larger the parameter


Configuration Rule and value is, the longer the waiting time is after the MS sends a location
Adjustment Suggestion message. Similarly, a smaller parameter value indicates a shorter
waiting time.

Change Mode Offline

Related features ZGO-01-03-002 LCS with CGI+TA &ZGO-01-03-003 LCS with AGPS

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-46

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

2.3.3 LCS wait intra BSS handover timer (LcsWaitInTraHO)


Full Name LCS wait intra BSS handover timer

Abbreviation LcsWaitInTraHO

3GPP Name None

3GPP Reference None

This parameter specifies the waiting time for the completion of an


intra-BSC handover.
Start: An intra-BSC handover is initiated during service location.
Stop: A handover complete message is received.
Description At expiry: Terminate the location process.

Managed Object BSC

20..100
Value Range and Step Step: 1

Unit 100 ms

Default Value 60

Default Value
Configuration Reason Generally, six seconds are enough for an intra-BSC handover.

Generally, the default value is recommended. The larger the parameter


Configuration Rule and
value, the longer the waiting time is after a handover request is sent.
Adjustment Suggestion
Similarly, a smaller parameter value means a shorter waiting time.

Change Mode Offline

Related features ZGO-01-03-002 LCS with CGI+TA &ZGO-01-03-003 LCS with AGPS

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-47

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

2.3.4 Monitor physical context request (RmsT9108)


Full Name Monitor physical context request

Abbreviation RmsT9108

3GPP Name None

3GPP Reference None

This parameter indicates the timer T9108 that is not used currently and is
Description reserved to monitor physical context requests in future.

Managed Object BSC

Value Range and Step 20

Unit 100 ms

Default Value 20

Default Value
Configuration Reason None

Configuration Rule and


Adjustment Suggestion None

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.3.5 Timer for waiting message from A-interface (TWaitMsg)


Full Name Timer for waiting message from A-interface

Abbreviation TWaitMsg

2-48

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

3GPP Name None

3GPP Reference None

This parameter indicates the protection time to wait for messages in


WORK status in the RanAWorker process. The RanAWorker process
is the working process of the RANA module.
Start: A RANA instance is created.
Stop: A message is received from the MSC.
At expiry: The instance will be released.
Description Related timer: None

Managed Object BSC

5..20
Value Range and Step Step: 1

Unit 100 ms

Default Value 20

Default Value Two seconds are long enough for the A interface to transmit signalling
Configuration Reason and for the MSC to process signalling.

Configuration Rule and


Adjustment Suggestion Generally, the default value is recommended.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.3.6 Timer for RANCSEST waiting (TWaitRancsEst)


Full Name Timer for RANCSEST waiting

2-49

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Abbreviation TWaitRancsEst

3GPP Name None

3GPP Reference None

This parameter indicates the protection time to wait for a resource


request in the RANCS process. The RANCS process is a process to
handle CS services.
Start: The RANA module receives an external handover request and
asks the RANCS module for a channel.
Stop: A response is received from the RANCS module.
At expiry: The handover failure message will be sent to the A interface.
Description Related timer: None

Managed Object BSC

10..100
Value Range and Step Step: 1

Unit 100 ms

Default Value 100

Default Value Generally, ten seconds are long enough for channel request, activation,
Configuration Reason and connection in the BSC.

Configuration Rule and


Adjustment Suggestion Generally, the default value is recommended.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-50

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

2.3.7 Timer for RANCSCLECOM waiting (TWaitRancsCleCom)


Full Name Timer for RANCSCLECOM waiting

Abbreviation TWaitRancsCleCom

3GPP Name None

3GPP Reference None

This parameter indicates the time to wait for the RANCS process to
respond to ClearCom in the RanAWorker process. The RanAWorker
process is the working process of the RANA module.
Start: The clear command is sent to the RANCS module.
Stop: A response is received from the RANCS module.
At expiry: The release will continue.
Description Related timer: None

Managed Object BSC

10..30
Value Range and Step Step: 1

Unit 100 ms

Default Value 30

Default Value Generally, three seconds are long enough for channel release,
Configuration Reason activation, disconnection, and connection in the BSC.

Configuration Rule and


Adjustment Suggestion Generally, the default value is recommended.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-51

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

2.3.8 Timer for CCM waiting (CcmWaitTimer)


Full Name Timer for CCM waiting

Abbreviation CcmWaitTimer

3GPP Name None

3GPP Reference None

This parameter indicates a timer that is used when the BTS waits
for disconnection, connection, and deactivation in dynamic channel
switching.
Start: The CCM starts channel switching.
Stop: A response is received from the connecting module and the BTS.
At expiry: The message will be sent to the BTS again.
Description Related timer: None

Managed Object BSC

45..55
Value Range and Step Step: 1

Unit 100 ms

Default Value 45

Default Value The default value 4.5 seconds are long enough for the Abis interface to
Configuration Reason transmit signalling and for the BTS to carry out the disconnection.

Configuration Rule and


Adjustment Suggestion Generally, the default value is recommended.

Change Mode Offline

Related features ZGB-03-02-006 Dynamic Channel Management

Related Parameters None

Relationship None

Related Interfaces Abis

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-52

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

2.3.9 Get static parameter timer (GetStaticParamTimer)


Full Name Get static parameter timer

Abbreviation GetStaticParamTimer

3GPP Name None

3GPP Reference None

This is a statistical parameter that is used to regularly poll the UPU unit
under the CMP in the RancRrm process.
Start: The timer is set periodically after power on.
Stop: None.
At expiry: The RancRrm will query information about resource
occupation from the UPU unit.
Description Related timer: None

Managed Object BSC

60..600
Value Range and Step Step: 1

Unit 100 ms

Default Value 120

Default Value The default value 12 seconds can avoid both slow processing and
Configuration Reason system load increase.

Configuration Rule and


Adjustment Suggestion Generally, the default value is recommended.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-53

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

2.3.10 Starting time for oriented retry (RmsT10)


Full Name Starting time for oriented retry

Abbreviation RmsT10

3GPP Name None

3GPP Reference None

This parameter is a timer used to wait for the start of directed retry. The
timer is started to wait for queuing, forced handover, and forced release
actions when the cell fails to assign an available channel. When the
timer expires, a directed retry process is initiated.
Start: The cell fails to assign an available channel.
Stop: An available channel resource is obtained after queuing, forced
handover, and forced release.
Description At expiry: Initiate a directed retry.

Managed Object BSC

50..150
Value Range and Step Step: 1

Unit 100 ms

Default Value 60

Default Value Six seconds are enough for the cell to complete the queuing, forced
Configuration Reason handover, and forced release process.

Configuration Rule and Set the parameter value in consideration of the time needed for queuing
Adjustment Suggestion preemption.

Change Mode Offline

Related features ZGB-03-01-002 Directed_Retry

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-54

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

2.3.11 TFO Enable (TFOControl_0)


Full Name TFO Enable

Abbreviation TFOControl_0

3GPP Name None

3GPP Reference None

This parameter, used for TFO control, indicates whether TFO is enabled.
0: Disable; 1: Enable
When this switch is disabled, the other switches for TFO control are also
disabled. That is, when the value of TFOControl_0 is 0, the values of
TFOControl_1, TFOControl_2 and TFOControl_3 are 0 too.
TFO is a in-band protocol that is used by the TCs of both parties for
encoding/decoding negotiation after the setup of a call. To improve the
speech quality, the voice frames in the air interface are directly sent
to the receiving party with the decoder of the sending party and the
encoder of the receiving party bypassed.
If two cells do not support AMR version, a TFO call can be successfully
set up between them once they support the same voice version. If two
cells support AMR version, a TFO call can be successfully set up only
when they use the same voice encoding/decoding type too. If different
voice encoding/decoding types are used, the setup of a TFO call will fail.
In the case of IPA, the CN is responsible for the negotiation of voice
Description encoding.

Managed Object BSC

Value Range and Step Yes/No

Unit None

Default Value No

Default Value
Configuration Reason This is a special functional switch, which is disabled by default.

Enable this switch when TFO support is required. It is recommended


Configuration Rule and
to enable TFO in scenarios requiring high voice quality because TFO
Adjustment Suggestion
can improve the voice MOS.

Change Mode Offline

Related features ZGO-04-02-006 TFO

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

2-55

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed element ID->Config set


OMC Access Path
ID->BSC Function->Others

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.3.12 External cell load notify (Info_0_0)


Full Name External cell load notify

Abbreviation Info_0_0

3GPP Name None

3GPP Reference None

This parameter decides whether to include the load information of a cell


into the information element "Old BSS to New BSS Information" when the
services of the cell under the current BSC are handed over to a cell under
Description another BSC.

Managed Object BSC

Value Range and Step 1: Yes; 0: No

Unit None

Default Value No

Default Value
Configuration Reason This is a special functional switch, which is disabled by default.

Configuration Rule and Generally, the default value is recommended. However, you can enable
Adjustment Suggestion this function if necessary.

Change Mode Offline

Related features ZGB-03-03-003 LAPD Cluster

Related Parameters None

Relationship None

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

2-56

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.3.13 Neighbor cell load valid duration (Info_0_1)


Full Name Neighbor cell load valid duration

Abbreviation Info_0_1

3GPP Name None

3GPP Reference None

This parameter indicates the validity period of a neighbor cell's load infor-
Description mation.

Managed Object BSC

1..255
Value Range and Step Step: 1

Unit 10 s

Default Value 6

Generally, the validity of a neighbor cell's load information is acceptable


Default Value
in 60s with the consideration that the load in a cell rarely fluctuates
Configuration Reason
greatly in such a period.

Generally, the default value is recommended. If the parameter value


is too large, the neighbor cell deems that the load information has a
Configuration Rule and
long validity period, which cannot reflect the actual load information in
Adjustment Suggestion
time. If the parameter value is too small, the load information will be
reported frequently.

Change Mode Offline

Related features ZGB-03-03-003 LAPD Cluster

Related Parameters [BSC]Info_0_0

Relationship This parameter is valid only when the switch Info_0_0 is enabled.

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

2-57

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.3.14 LMU build request deal or not (Info_1_0)


Full Name LMU build request deal or not

Abbreviation Info_1_0

3GPP Name None

3GPP Reference None

This parameter decides whether to process the Location Measurement


Unit (LMU) establishment request.
No: Not to process
Description Yes: To process

Managed Object BSC

Value Range and Step 1: Yes; 0: No

Unit None

Default Value No

Default Value
Configuration Reason This is a special functional switch, which is disabled by default.

Configuration Rule and Generally, the default value is recommended. However, you can enable
Adjustment Suggestion this function if necessary.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

2-58

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.3.15 MBMS request deal or not (Info_1_1)


Full Name MBMS request deal or not

Abbreviation Info_1_1

3GPP Name None

3GPP Reference None

This parameter decides whether to process the Multimedia Broad-


Description cast/Multicast Service (MBMS) request.

Managed Object BSC

Value Range and Step 1: Yes; 0: No

Unit None

Default Value No

Default Value
Configuration Reason This is a special functional switch, which is disabled by default.

Configuration Rule and Generally, the default value is recommended. However, you can enable
Adjustment Suggestion this function if necessary.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-59

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

2.3.16 Channel request reserved field deal or not (Info_1_2)


Full Name Channel request reserved field deal or not

Abbreviation Info_1_2

3GPP Name None

3GPP Reference None

This parameter decides whether to process the reserved field Channel


Request. When this switch is enabled, if Random Access Reference in
the Channel Request message is 0x61, 0x63, or 0x65, the system will
Description not process the channel request.

Managed Object BSC

Value Range and Step 1: Yes; 0: No

Unit None

Default Value No

Default Value
Configuration Reason This is a special functional switch, which is disabled by default.

Configuration Rule and Generally, the default value is recommended. However, you can enable
Adjustment Suggestion this function if necessary.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Abis

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.3.17 MS power hold in handover option (Info_0_9)


Full Name MS power hold in handover option

2-60

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Abbreviation Info_0_9

3GPP Name None

3GPP Reference None

This parameter decides whether to support MS power optimization for


non-rescue handovers. Generally, when the handover command is is-
sued to an MS, the MS is required to use the maximum transmit power.
However, this will result in strong interferences. This switch is designed
to reduce the interferences when multiple MSs are handed over with the
maximum transmit power. When enabled, the switch serves as a thresh-
old. When the BSC sends a handover command to the MS for a non-res-
cue handover, such as PBGT handover, if the current level is higher than
the threshold, it means that the target cell has better signal quality. In this
case, the current transmit power, instead of the maximum transmit power,
Description should be used.

Managed Object BSC

Value Range and Step 1: Yes; 0: No

Unit None

Default Value No

Default Value
Configuration Reason This is a special functional switch, which is disabled by default.

Generally, the default value is recommended. However, you can enable


Configuration Rule and
this function if necessary. Enabling it can reduce interferences in the
Adjustment Suggestion
network.

Change Mode Offline

Related features ZGO-02-02-020 Power Optimization After Handover

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-61

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

2.3.18 Signal level threshold of target cell (Info_0_10)


Full Name Signal level threshold of target cell

Abbreviation Info_0_10

3GPP Name None

3GPP Reference None

This parameter is valid when the MS power optimization for non-rescue


handovers is enabled. When the BSC sends a handover command to the
MS for a non-rescue handover, such as PBGT handover, if the current
level is higher than the threshold, it means that the target cell has bet-
ter signal quality. In this case, the current transmit power, instead of the
Description maximum transmit power, should be used.

Managed Object BSC

0 ..63, step: 1
0: < -110 dBm
1: -110 dBm..-109 dBm
2: -109 dBm..-108 dBm
...
62: -49 dBm..-48 dBm
Value Range and Step 63: > -48 dBm

Unit None

Default Value 27

Default Value
Configuration Reason The level value -83 dB is enough for normal services.

Generally, the default value is recommended. The higher the value is,
Configuration Rule and the less likely the signals in the target cell are to reach the threshold.
Adjustment Suggestion Setting this parameter to a proper value can reduce uplink interferences
has good effect on network indicators.

Change Mode Offline

Related features ZGB-02-02-002 Basic Handover Decision

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

2-62

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.3.19 Iur-G interface support (IurgSupport)


Full Name Iur-G interface support

Abbreviation IurgSupport

3GPP Name None

3GPP Reference None

This parameter indicates whether to support the Iur-g interface. 0: No;


1: Yes
0: Disable
Description 1: enable

Managed Object BSC

0: No
Value Range and Step 1: Yes

Unit None

Default Value No

Default Value
Configuration Reason This is a special functional switch, which is disabled by default.

This switch can be enabled upon request. Otherwise, it should be


Configuration Rule and
disabled. Enabling Iur-g can increase the success rate of two thirds of
Adjustment Suggestion
handovers.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Iur-g

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

2-63

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.3.20 Overload threshold of non real-time load (NRTThs_0)


Full Name Overload threshold of non real-time load

Abbreviation NRTThs_0

3GPP Name None

3GPP Reference None

This parameter indicates the overload threshold of non-real-time services.


When the load of non-real-time services is equal to or higher than the
threshold, it is regarded that the scell is overloaded with non-real-time
services. Non-real-time services refer to PS services. The load is cal-
culated by dividing the number of occupied PDCHs (including dynamic
Description PDCHs and static PDCHs) by the number of available PDCHs.

Managed Object BSC

1..99
Value Range and Step Step: 1

Unit %

Default Value 90

Default Value Generally, it is regarded that the cell is overloaded if more than 90%
Configuration Reason of radio resources are occupied.

The higher the value is, the more likely the cell will be to be selected by
Configuration Rule and
the RNC as the target cell for re-direction.
Adjustment Suggestion
NRTThs_0>NRTThs_1>NRTThs_2

Change Mode Offline

Related features None

Related Parameters [BSC]IurgSupport

Relationship This parameter becomes valid when IurgSupport is set to Yes.

Related Interfaces Iur-g口

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork->BSC Managed Element->Config SetBSC


OMC Access Path
Function->Others

2-64

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.3.21 High threshold of non real-time load (NRTThs_1)


Full Name High threshold of non real-time load

Abbreviation NRTThs_1

3GPP Name None

3GPP Reference None

This parameter indicates the upper overload threshold of non-real-time


services. When the load of non-real-time services is equal to or higher
than the threshold but lower than NRTThs_0, it is regarded that the cell
is overloaded with non-real-time services. Non-real-time services refer to
PS services. The load is calculated by dividing the number of occupied
PDCHs (including dynamic PDCHs and static PDCHs) by the number of
Description available PDCHs.

Managed Object BSC

1..99
Value Range and Step Step: 1

Unit %

Default Value 60

Default Value Generally, it is regarded that the cell is overloaded if more than 60%
Configuration Reason of radio resources are occupied.

The higher the value is, the more likely the cell will be to be selected by
Configuration Rule and
the RNC as the target cell for re-direction.
Adjustment Suggestion
NRTThs_0>NRTThs_1>NRTThs_2

Change Mode Offline

Related features None

Related Parameters [BSC]IurgSupport

Relationship This parameter becomes valid when IurgSupport is set to Yes.

Related Interfaces Iur-g口

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

2-65

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

OMC->GERAN Subnetwork->BSC Managed Element->Config SetBSC


OMC Access Path
Function->Others

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.3.22 Low threshold of non real-time load (NRTThs_2)


Full Name Low threshold of non real-time load

Abbreviation NRTThs_2

3GPP Name None

3GPP Reference None

This parameter indicates the lower overload threshold of non-real-time


services. When the load of non-real-time services is equal to or higher
than the threshold but lower than NRTThs_1, it is regarded that the cell
is moderately loaded with non-real-time services. Otherwise, the load of
non-real-time services is regarded low. Non-real-time services refer to
PS services. The load is calculated by dividing the number of occupied
PDCHs (including dynamic PDCHs and static PDCHs) by the number of
Description available PDCHs.

Managed Object BSC

Value Range and Step 1..99

Unit %

Default Value 20

Default Value Generally, it is regarded that the cell load is low if less than 20% of radio
Configuration Reason resources are occupied.

The higher the value is, the more likely the cell will be to be selected by
Configuration Rule and
the RNC as the target cell for re-direction.
Adjustment Suggestion
NRTThs_0>NRTThs_1>NRTThs_2

Change Mode Offline

Related features None

Related Parameters [BSC]IurgSupport

Relationship This parameter becomes valid when IurgSupport is set to Yes.

Related Interfaces Iur-g口

Impact on Equipment 0

Impact on service 0

2-66

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Negotiation With CN NO

OMC->GERAN Subnetwork->BSC Managed Element->Config SetBSC


OMC Access Path
Function->Others

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.3.23 On demand mode switch of information exchange


(IurgSwitchGroup_0)
Full Name On demand mode switch of information exchange

Abbreviation IurgSwitchGroup_0

3GPP Name None

3GPP Reference None

This parameter decides whether to enable On Demand mode of infor-


mation exchange. Information exchange refers to the process in which
the RNC and the BSC exchange the capacity information of radio cell
resources. On Demand is a mode in which the information is reported
Description immediately when being requested for.

Managed Object BSC

0: No
Value Range and Step 1: Yes

Unit None

Default Value Yes

Default Value On Demand is one of the typical information exchange modes, so the
Configuration Reason default value is Yes.

Configuration Rule and


Adjustment Suggestion Generally, the default value is recommended.

Change Mode Offline

Related features None

Related Parameters [BSC]IurgSupport

Relationship This parameter becomes valid when IurgSupport is set to Yes.

Related Interfaces Iur-g

Impact on Equipment 0

Impact on service 0

2-67

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.3.24 On modification mode switch of information exchange


(IurgSwitchGroup_1)
Full Name On modification mode switch of information exchange

Abbreviation IurgSwitchGroup_1

3GPP Name None

3GPP Reference None

This parameter decides whether to enable On Modification mode of infor-


mation exchange. Information exchange refers to the process in which
the RNC and the BSC exchange the capacity information of radio cell re-
sources. On Modification is a mode in which the information is reported
Description immediately when it changes.

Managed Object BSC

0: No
Value Range and Step 1: Yes

Unit None

Default Value Yes

Default Value On Modification is one of the typical information exchange modes, so


Configuration Reason the default value is Yes.

Configuration Rule and


Adjustment Suggestion Generally, the default value is recommended.

Change Mode Offline

Related features None

Related Parameters [BSC]IurgSupport

Relationship This parameter becomes valid when IurgSupport is set to Yes.

Related Interfaces Iur-g

Impact on Equipment 0

Impact on service 0

2-68

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.3.25 On demand mode switch of common measurement


(IurgSwitchGroup_2)
Full Name On demand mode switch of common measurement

Abbreviation IurgSwitchGroup_2

3GPP Name None

3GPP Reference None

This parameter decides whether to enable On Demand mode of common


measurement. Common measurement refers to the process in which the
RNC and the BSC exchange the occupation information of radio cell re-
sources. On Demand is a mode in which the information is reported im-
Description mediately when being requested for.

Managed Object BSC

0: No
Value Range and Step 1: Yes

Unit None

Default Value Yes

Default Value On Demand is one of the typical common measurement modes, so the
Configuration Reason default value is Yes.

Configuration Rule and


Adjustment Suggestion Generally, the default value is recommended.

Change Mode Offline

Related features None

Related Parameters [BSC]IurgSupport

Relationship This parameter becomes valid when IurgSupport is set to Yes.

Related Interfaces Iur-g

Impact on Equipment 0

Impact on service 0

2-69

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.3.26 Periodic mode switch of common measurement


(IurgSwitchGroup_3)
Full Name Periodic mode switch of common measurement

Abbreviation IurgSwitchGroup_3

3GPP Name None

3GPP Reference None

This parameter decides whether to enable Periodic mode of common


measurement. Common measurement refers to the process in which the
RNC and the BSC exchange the occupation information of radio cell re-
sources. Periodic is a mode in which the information is reported periodi-
Description cally.

Managed Object BSC

0: No
Value Range and Step 1: Yes

Unit None

Default Value Yes

Default Value Periodic is one of the typical common measurement modes, so the
Configuration Reason default value is Yes.

Configuration Rule and


Adjustment Suggestion Generally, the default value is recommended.

Change Mode Offline

Related features None

Related Parameters [BSC]IurgSupport

Relationship This parameter becomes valid when IurgSupport is set to Yes.

Related Interfaces Iur-g

Impact on Equipment 0

Impact on service 0

2-70

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.3.27 Immediate assignment repeat (ImmAssRep)


Full Name Immediate assignment repeat

Abbreviation ImmAssRep

3GPP Name None

3GPP Reference None

This parameter indicates whether to re-send the immediate assignment


message. If it is set to 0, the message will not be re-sent. If it is set to 1,
Description the message will be re-sent once.

Managed Object BSC

0: No
Value Range and Step 1: Yes

Unit None

Default Value Yes

Default Value
Configuration Reason The message is re-sent once.

Configuration Rule and Enabling this parameter has positive effect on the success rate of
Adjustment Suggestion immediate assignments.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Abis

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

2-71

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.3.28 Immediate assignment priority (ImmAssPrio)


Full Name Immediate assignment priority

Abbreviation ImmAssPrio

3GPP Name None

3GPP Reference None

This parameter indicates the priority of the immediate assignment mes-


sage. The value range is 0 and 1. The value 1 stands for high priority
at which any PCH block can be preempted. Currently, this parameter is
Description invalid and the value is fixed to 1.

Managed Object BSC

0: Low, indicating low priority


Value Range and Step 1: High, indicating high priority

Unit None

Default Value High

Default Value
Configuration Reason The default value is fixed to 1 for the BTS.

Configuration Rule and


Adjustment Suggestion None

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Abis

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

2-72

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.3.29 Paging repeat number (PagRep)


Full Name Paging repeat number

Abbreviation PagRep

3GPP Name None

3GPP Reference None

This parameter indicates how many times a paging message will be


Description re-sent. 0: Indicates no resending; 1-4: Indicate the times of re-sending

Managed Object BSC

0..4
Value Range and Step Step: 1

Unit None

Default Value 1

Default Value
Configuration Reason The message is re-sent once.

The higher the value is, the more likely the MS is to be paged. In this
Configuration Rule and case, however, the load of the paging channel will increase, so you
Adjustment Suggestion should consider both the load of the paging channel and the success
rate of the paging when setting this parameter.

Change Mode Offline

Related features ZGB-02-01-001 Paging

Related Parameters None

Relationship None

Related Interfaces Abis

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

Parameter Modifying
Version None

2-73

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Parameter Modifying
Detail None

2.3.30 Timer of waiting for IPGB changing over (TIPGBChgWait)


Full Name Timer of waiting for IPGB changing over

Abbreviation TIPGBChgWait

3GPP Name None

3GPP Reference None

This parameter is a timer that records the time of the IPGB in waiting for
handover when the service initiates an IPGB board handover.
Enable condition: When all the NSVC states of the IPGB board are
not normal, the service can initiate active/standby handover based on
judgment.
Disable condition: Some NSVC states recover.
Description Timeout: The service initiates active/standby handover.

Managed Object BSC

Value Range and Step 6..600

Unit s

Default Value 60

Default Value Try to avoid the impact of instant NSVC break or connection, and
Configuration Reason long-time wait.

This parameter cannot be configured too low, so as to avoid the


Configuration Rule and impact of instant NSVC break or connection. This parameter cannot
Adjustment Suggestion be configured too high, so as to avoid long-time wait when the service
initiates the IPGB handover.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

2-74

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Parameter Modifying
Version iBSCV6.20.710

Parameter Modifying
Detail New

2.3.31 restricted time after continuous IPGB changing over


(TIPGBConChglmt)
Full Name restricted time after continuous IPGB changing over

Abbreviation TIPGBConChglmt

3GPP Name None

3GPP Reference None

This parameter is a timer that records the restricted time for continuous
IPGB handovers.
Enable condition: The service requires active/standby handover but the
number of continuous IPGB handovers reaches the upper threshold.
Disable condition: None
Timeout: The number of continuous IPGB active/standby handovers
Description is cleared.

Managed Object BSC

Value Range and Step 600..65535

Unit s

Default Value 3600

Default Value Try to avoid frequent handovers in case of unreachable NSVC links on
Configuration Reason the active and standby IPGB boards.

In normal cases with IPGB links, use the recommended value. In the
Configuration Rule and
case of unstable IPGB link, configure this parameter to a larger value, so
Adjustment Suggestion
as to avoid frequent handovers in case of unreachable NSC links.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

2-75

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

OMC->GERAN Subnetwork ID->BSC Managed element ID->Config


OMC Access Path
Set ID->BSC Function ID->Others

Parameter Modifying
Version iBSCV6.20.710

Parameter Modifying
Detail New

2.3.32 Info_3
Full Name Info_3

Abbreviation Info_3

3GPP Name None

3GPP Reference None

Description This parameter is currently not used.

Managed Object BSC

Value Range and Step 0..4294967295

Unit None

Default Value 0

Default Value
Configuration Reason This parameter is currently not used.

Configuration Rule and


Adjustment Suggestion This parameter is currently not used.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed element ID->Config


OMC Access Path
set ID->BSC Function ID->Others

Parameter Modifying
Version iBSCV6.20.711c

Parameter Modifying
Detail New

2-76

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

2.3.33 Info_6
Full Name Info_6

Abbreviation Info_6

3GPP Name None

3GPP Reference None

Description This parameter is currently not used.

Managed Object BSC

Value Range and Step 0..4294967295

Unit None

Default Value 0

Default Value
Configuration Reason This parameter is currently not used.

Configuration Rule and


Adjustment Suggestion This parameter is currently not used.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed element ID->Config


OMC Access Path
set ID->BSC Function ID->Others

Parameter Modifying
Version iBSCV6.20.711c

Parameter Modifying
Detail New

2.3.34 Threshold of UPUDSP Dynamic Adjustment (Info_7)


Full Name Threshold of UPUDSP Dynamic Adjustment

Abbreviation Info_7

3GPP Name None

3GPP Reference None

2-77

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

The threshold may affect the traffic balance after the UPUDSP dynamic
Description adjustment.

Managed Object BSC

Value Range and Step 1..100

Unit None

Default Value 10

Default Value
Configuration Reason Theoretically, if the threshold is set to 10, the traffic balance will be better.

The R_BSC.INFO[7] is used as the adjustment threshold for UPUDSP.


Configuration Rule and The default value is 10. The value ranges from 1 to 100. Generally, the
Adjustment Suggestion lower the threshold, the better balance of the DSP load. The default
value is recommended.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed element ID->Config


OMC Access Path
set ID->BSC Function ID->Others

Parameter Modifying
Version iBSCV6.20.711c

Parameter Modifying
Detail New

2.4 Channel Allocation Control Parameters


2.4.1 Dynamic HR support indication (DynaHREnable)
Full Name Dynamic HR support indication

Abbreviation DynaHREnable

3GPP Name None

3GPP Reference None

2-78

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

This parameter decides whether the BSC supports dynamic HR. The dy-
namic HR channel allocation function enables the network to allocate
full-rate or half-rate channels to MSs according to the traffic in the cell
when it allocate channels for the MSs. Allocating half-rate channels when
the channels in the cell are likely to be congested minimizes the duration
Description of possible congestions in peak hours.

Managed Object BSC

0: No
Value Range and Step 1: Yes

Unit None

Default Value 0

Default Value
Configuration Reason This is a special functional switch, which is disabled by default.

Configuration Rule and The dynamic HR function of the BSC cannot be enabled unless this
Adjustment Suggestion switch is enabled.

Change Mode Offline

Related features ZGO-03-02-005 Dynamic Half Rate Allocation

Related Parameters [Cell]DynaHREnable

Full-rate channels can be converted to half-rate channels only when the


Relationship
BSC-level and cell-level DynaHREnable is enabled.

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Channel Allocation Control parameters

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.4.2 HR channel fragment repackaging support (HRDfragSupport)


Full Name HR channel fragment repackaging support

Abbreviation HRDfragSupport

3GPP Name None

2-79

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

3GPP Reference None

This parameter is a switch to support the HR channel defragmentation


function and can be configured on both BSCs and cells. The HR channel
defragmentation function is enabled only when both BSC- and cell-level
switches are enabled and the proportion of the idle TCH/Fs in these cells is
not more than the threshold proportion of the TCH/Fs to the total available
Description service channels in the cell where the defragmentation is enabled.

Managed Object BSC

1: Yes
Value Range and Step 0: No

Unit None

Default Value 0: No

Default Value
Configuration Reason This is a special functional switch, which is disabled by default.

Enabling the HR channel defragmentation function in a cell where


dynamic half rate is used can increase full-rate channels and improve
Configuration Rule and voice quality. Enabling the function on dynamic channels can increase
Adjustment Suggestion available PS channels. The function can be enabled as needed. If it is
enabled, the corresponding switch in cell parameters must be enabled at
the same time. In this case, more handovers will occur in cells.

Change Mode Offline

Related features ZGO-03-02-004 HR Concentration

Related Parameters [BSC]HoIntraEnable


[Cell]HRDfragSupport

This function can be enabled only when HoIntraEnable and BSC- and
Relationship
cell-level HRDfragSupport in the system control parameters are enabled.

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Channel Allocation Control parameters

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-80

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

2.4.3 User priority for EMLPP (PriThreshold)


Full Name User priority for EMLPP

Abbreviation PriThreshold

3GPP Name None

3GPP Reference None

When you enable the eMLPP service function, which allows high-priority
users to access channels first, the system can reserve a certain number
of channels for high-priority users (currently, only full-rate TCHs can be
reserved channels)
When the CS instance invokes the database to request channels,
the user's PriorityLevel information will be sent to the database and
compared with the value of PriThreshold in the BSC table. If PriorityLevel
is not more than PriThreshold (That is to say, the priority of the user is
not lower than PriThreshold. The lower the priority value is, the higher
Description the priority will be. ), reserved channels can be used.

Managed Object BSC

1..15
Value Range and Step Step: 1

Unit None

Default Value 2

Default Value
Configuration Reason The default value "2" is suitable for most applications.

Configuration Rule and


Adjustment Suggestion You can adjust this parameter as needed.

Change Mode Offline

Related features ZGO-01-03-001 Emlpp

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Channel Allocation Control parameters

Parameter Modifying
Version None

2-81

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Parameter Modifying
Detail None

2.4.4 Preferred speech version (half) (PreferSpeechVer H)


Full Name Preferred speech version (half)

Abbreviation PreferSpeechVer H

3GPP Name None

3GPP Reference None

This parameter indicates the preferred half-rate speech version in the CS


channel allocation. Half rate version1 refers to HR and version3 refers to
Description AMR.

Managed Object BSC

0: No preferred version.
1: Half rate version1.
Value Range and Step 3: Half rate version3.

Unit None

Default Value 0: No preferred version.

Default Value No preferred version is specified at the BSC side. Instead, the MSC
Configuration Reason coding strategy is used.

It is recommended to use the default value and allow the MSC to decide
the speech version unless otherwise necessary.
If you modify the default value, the new value will decide the speech
version.
Configuration Rule and
Generally, AMR enables the adaptive switching of coding rates. In
Adjustment Suggestion
poor channel conditions, increasing the channel coding rate (increasing
redundant bits) and reducing the source (speech) coding rate can
ensure the conversation quality. In good channel conditions, increasing
the source coding rate can improve the voice quality.

Change Mode Offline

Related features ZGO-01-01-001 Half Rate

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

2-82

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Channel Allocation Control parameters

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.4.5 Preferred speech version (full) (PreferSpeechVer F)


Full Name Preferred speech version (full)

Abbreviation PreferSpeechVer F

3GPP Name None

3GPP Reference None

This parameter indicates the preferred full-rate speech version in the CS


channel allocation. Full rate version1 refers to FR. Full rate version2 refers
Description to EFR and version3 refers to AMR.

Managed Object BSC

0: No preferred version.
1: Full rate version1.
2: Full rate version2.
Value Range and Step 3: Full rate version3.

Unit None

Default Value 0: No preferred version.

Default Value No preferred version is specified at the BSC side. Instead, the MSC
Configuration Reason coding strategy is used.

It is recommended to use the default value and allow the MSC to decide
the speech version unless otherwise necessary.
If you modify the default value, the new value will decide the speech
version.
Configuration Rule and Generally, ERF can provide the best voice quality and user satisfaction.
Adjustment Suggestion AMR enables the adaptive switching of coding rates. In poor channel
conditions, increasing the channel coding rate (increasing redundant
bits) and reducing the source (speech) coding rate can ensure the
conversation quality. In good channel conditions, increasing the source
coding rate can improve the voice quality.

Change Mode Offline

Related features ZGB-01-01-001 Full Rate (FR) Speech Codec

2-83

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Channel Allocation Control parameters

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.4.6 Reserved channel first (RsvChanFirst)


Full Name Reserved channel first

Abbreviation RsvChanFirst

3GPP Name None

3GPP Reference None

This parameter indicates the order of preference of reserved and


non-reserved channels. If this functional switch is enabled, reserved
channels will be allocated to high-priority users first.
Yes: To allocate reserved channels first
Description No: To allocate non-reserved channels first

Managed Object BSC

0: No
Value Range and Step 1: Yes

Unit None

Default Value 1

Default Value Generally, reserved channels are used first to avoid the waste of channel
Configuration Reason resources.

Configuration Rule and


Adjustment Suggestion The default value is recommended unless otherwise necessary.

Change Mode Offline

Related features ZGO-01-03-001 Emlpp

2-84

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Channel Allocation Control parameters

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.4.7 EMLPP channel reserved rate (EMLPPThs)


Full Name EMLPP channel reserved rate

Abbreviation EMLPPThs

3GPP Name None

3GPP Reference None

This parameter decides the proportion of channels reserved for high-pri-


ority users when you enable the eMLPP service function, which allows
Description high-priority users to access channels first.

Managed Object BSC

0..100
Value Range and Step Step: 1

Unit %

Default Value 0

Default Value
Configuration Reason This is a characteristic parameter and no channel is reserved by default.

The higher the value is set to, the more channels will be reserved. In
this case, high-priority users are more likely to access a channel, but
Configuration Rule and
low-priority users have fewer available channels.
Adjustment Suggestion
The lower the value is set to, the fewer channels will be reserved. In this
case, high-priority users are less likely to access a channel.

Change Mode Offline

Related features ZGO-01-03-001 Emlpp

2-85

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Related Parameters [Cell]EMLPPThs

If the parameter UseCelleMLPPThs is enabled, the cell-level parameter


Relationship EMLPPThs should be enabled. If not, the BSC-level parameter
EMLPPThs should be enabled.

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Channel Allocation Control parameters

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.4.8 TrxPSBusyThs (TrxPSBusyThs)


Full Name TrxPSBusyThs

Abbreviation TrxPSBusyThs

3GPP Name None

3GPP Reference None

The degree of idleness of the PS service channels on a carrier is


calculated as follows:
If there are available uplink and downlink PS service channels on the
carrier, and if the number of available uplink channels is byUpNum and
the number of available downlink channels is byDwNum,
Total degree of idleness of all available uplink PS service channels =
∑100*(Abis/AbisMax)*(Qos/16)*((Usermax-Usernum)/Usermax)
——In this formula, the degrees of idleness of byUpNum uplink channels
are accumulated.
Total degree of idleness of all available downlink PS service channels =
∑100*(Abis/AbisMax)*(Qos/16)*((Usermax-Usernum)/Usermax)
——In this formula, the degrees of idleness of byDwNum downlink
channels are accumulated.
Where,
Abis is the number of Abis resources (IP Abis bandwidth or E1 Abis
timeslot) allocated to the channels.
AbisMax is the maximum number of Abis resources (IP Abis bandwidth

Description or E1 Abis timeslot) that can be allocated to the channels. For example,

2-86

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

at most four E1 Abis timeslots can be allocated to a PS service channel


on the EDGE carrier. 4
QoS is the number of available QoS quotas on the channels (the original
number is 16.)
Usermax is the maximum allowable number of users whose data is
multiplexed on the channels.
Usernum is the number of users on the current channel.
The degree of idleness of the carriers (TrxIdle, ranging from 0 to 100) is
calculated as follows:
If byUpNum == 0 and byDwNum != 0, TrxIdle = Total degree of idleness
of all available downlink PS service channels / byDwNum
If byUpNum != 0 and byDwNum == 0, TrxIdle = Total degree of idleness
of all available uplink PS service channels / byUpNum
If byUpNum != 0 and byDwNum != 0, TrxIdle = (Total degree of idleness
of all available downlink PS service channels * byDwNum + Total degree
of idleness of all available uplink PS service channels * byUpNum) / (2
* byDwNum * byUpNum)
If byUpNum == 0 and byDwNum == 0, TrxIdle = 0 (This is because there
are no available uplink or downlink PS service channels on the carriers. )
TRX controlled only by the degree of idleness of PS service channels is
selected according to the following principles:
If there are idle PS service channels on all TRXs, one TRX will be
selected and allocated at random. As long as the degree of idleness of
the PS service channels on the TRX is higher than the threshold, the
same TRX is always selected as a priority for the purpose of centralized
service allocation.
When the degree of idleness of the PS service channels on the TRX is
lower than the threshold, it is deemed that the TRX is overloaded with
PS services and an inter-TRX balance is required. In this case, another
idle TRX will be selected and new PS services will be allocated to the
TRX until it is overloaded.
3When all TRXs are overloaded with PS services, the TRX with higher
degree of idleness of PS service channels will be selected for the
purpose of inter-TRX balance of PS services.

Managed Object BSC

1..100
Value Range and Step Step: 1

Unit %

Default Value 50

When the default value is set to 50, PFC users occupy half channel Qos.
Default Value For non-PFC users, the number of current users on the channels is half
Configuration Reason the maximum number of users. In this way, the channel expansion is
controlled within a reasonable speed.

2-87

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

When there are sufficient PS channel resources and high rates are
Configuration Rule and required for PS services, you can set this parameter to a lower value to
Adjustment Suggestion expand the PS service channels to new carriers as quickly as possible.
Otherwise, set it to a higher value.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Um

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Channel Allocation Control parameters

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.4.9 Resource pool for PS rate (PsAbisThs)


Full Name Resource pool for PS rate

Abbreviation PsAbisThs

3GPP Name None

3GPP Reference None

This parameter indicates the upper limit of the rate of the Abis resources
that can be allocated to PS services in the full-dynamic Abis resource
pool. If this threshold value is exceeded, no Abis resources will be
allocated to PS services even when there are available Abis resources.
Rate of occupied PSABIS resources = Abis resources allocated to PS
Description services / Total available Abis resources in the resource pool

Managed Object BSC

0..100
Value Range and Step Step: 1

Unit %

Default Value 80

2-88

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Setting this parameter to "80" allows Abis resources to be allocated


Default Value
evenly to PS and CS services. In this case, CS services are given a
Configuration Reason
certain degree of priority.

If the PS traffic in the cell is high, you can set a higher value not more
Configuration Rule and
than 90. If the PS traffic is low and there is a shortage of Abis resources,
Adjustment Suggestion
you can lower the value appropriately to ensure CS services first.

Change Mode Offline

Related features ZGO-03-03-001 Full Dynamic Abis Allocation

Related Parameters None

Relationship None

Related Interfaces Abis

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Channel Allocation Control parameters

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.4.10 Extended uplink dynamic allocation support


(ExUpDynSupport)
Full Name Extended uplink dynamic allocation support

Abbreviation ExUpDynSupport

3GPP Name EXTENDED_DYNAMIC_ALLOCATION

TS44.060: "Radio Link Control/Medium Access Control (RLC/MAC) pro-


3GPP Reference tocol"

This parameter indicates whether the cell supports extended uplink dy-
namic allocation. When this function is used, the MS can decide whether
to send uplink blocks in all of the allocated uplink timeslots by only mon-
Description itoring the USF allocation in the lowest timeslot.

Managed Object BSC

Value Range and Step 1: Yes; 0: No

Unit None

2-89

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Default Value No

Default Value The default value is set according to the traffic model and resource
Configuration Reason occupation in the network.

When the MS supports this function and the uplink PS service


Configuration Rule and
transmission is a priority or there are sufficient uplink radio resources,
Adjustment Suggestion
enabling the function can increase the uplink transmission rate.

Change Mode Offline

Related features ZGO-03-02-007 Extended Dynamic Allocation

Related Parameters [Cell]ExUpDynSupport

This parameter is valid when the cell-level ExUpDynSupport parameter


Relationship
is enabled.

Related Interfaces Um

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->Channel Allocation Control parameters

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.5 Timer 1
2.5.1 Blocking/Unblocking period (T1)
Full Name Blocking/Unblocking period

Abbreviation T1

3GPP Name T1

3GPP Reference 3GPP TS 48.008 V5.12.0

2-90

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

This parameter is timer T1, which specifies a time period during which
the BSS needs to initiate a block/unblock a ground circuit process due to
some reasons, such as O&M intervene, equipment failure or restoration,
or radio resource available or unavailable. In the process, the BSS
sends a BLOCK/UNBLOCK message to the MSC. Upon receiving this
message, the MSC returns a BLOCK/UNBLOCK ACK message to the
BSS.
Start: A single circuit block/unblock message is sent to the MSC.
Stop: A single circuit block/unblock acknowledgement message is
received from the MSC.
At expiry: If the number of times that no acknowledgement message is
received from the MSC does not exceed the maximum number, the BSC
sends a single circuit block/unblock message to the MSC again. If the
number of times that no acknowledgement is received from the MSC
Description exceeds the maximum number, the instance is terminated.

Managed Object BSC

30..150
Value Range and Step Step: 1

Unit 100 ms

Default Value 80

Generally, an acknowledgement message can be received in eight


Default Value
seconds after the BSC sends a circuit block/unblock message to the
Configuration Reason
MSC.

Configuration Rule and


Adjustment Suggestion The default value is recommended.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer1

Parameter Modifying
Version None

2-91

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Parameter Modifying
Detail None

2.5.2 Global resetting period (T4)


Full Name Global resetting period

Abbreviation T4

3GPP Name T4

3GPP Reference 3GPP TS 48.008 V5.12.0

This parameter is timer T4, which is used to supervise the BSSAP


RESET message sent from the BSC to the MSC.
Start: The BSC initiates a global reset process.
Stop: A BSSAP RESET ACK message is received from the MSC.
Description At expiry: The BSC repeats the whole process.

Managed Object BSC

60..150
Value Range and Step Step: 1

Unit 100 ms

Default Value 100

Default Value Generally, an acknowledgement message can be received in 10


Configuration Reason seconds after the BSC sends a reset message to the MSC.

Configuration Rule and


Adjustment Suggestion The default value is recommended.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer1

Parameter Modifying
Version None

2-92

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Parameter Modifying
Detail None

2.5.3 Protective period for global resetting (T13)


Full Name Protective period for global resetting

Abbreviation T13

3GPP Name T13

3GPP Reference 3GPP TS 48.008 V5.12.0

This parameter is timer T13, which specifies the protection time for
a local call clear process.
Start: When the BSC receives a BSSAP RESET message from the MSC.
Stop: When an SSP/SPI (SubSystem Prohibited/Signalling Point
Inhibited) message is received from the SCCP.
Description At expiry: The BSS sends a BSSAP RESET ACK message to the MSC.

Managed Object BSC

30..60
Value Range and Step Step: 1

Unit 100 ms

Default Value 40

Default Value Generally, the BSC can receive a message from the SCCP in four
Configuration Reason seconds.

Configuration Rule and


Adjustment Suggestion The default value is recommended.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer1

Parameter Modifying
Version None

2-93

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Parameter Modifying
Detail None

2.5.4 Circuit resetting period on BSS side (T19)


Full Name Circuit resetting period on BSS side

Abbreviation T19

3GPP Name T19

3GPP Reference 3GPP TS 48.008 V5.12.0

This parameter is timer T19, which indicates the time period of a circuit
reset process on the BSS side.
Start: The BSS sends a BSSAP CIRCUIT RESET message to the
MSC for forcibly releasing the circuit due to an exception of BSC SCCP
connection.
Stop: Upon receiving the BSSAP CIRCUIT RESET message, the MSC
releases the related services and the circuit becomes idle. Then the
MSC sends a BSSAP CIRCUIT RESET ACK message to the BSC. The
timer is stopped when the BSC receives the RESET CIRCUIT ACK
message.
At expiry: If the number of timer expiries is less than the maximum
number of times that the BSSAP CIRCUIT RESET message is sent,
the BSC sends this message to the MSC again. If the number of timer
expiries reaches the maximum number, the BSC reports the reset failure
Description to the O&M, and then terminates the process and clears the instance.

Managed Object BSC

30..150
Value Range and Step Step: 1

Unit 100 ms

Default Value 80

Generally, an acknowledgement message can be received in eight


Default Value
seconds after the BSC sends a BSSAP CIRCUIT RESET message to
Configuration Reason
the MSC.

Configuration Rule and


Adjustment Suggestion The default value is recommended.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

2-94

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.5.5 Circuit group blocking/unblocking period (T20)


Full Name Circuit group blocking/unblocking period

Abbreviation T20

3GPP Name T20

3GPP Reference 3GPP TS 48.008 V5.12.0

This parameter specifies a time period during which the BSS initiates a
circuit group block/unblock process due to some reasons, such as O&M
intervene, equipment failure or restoration, or radio resource available or
unavailable. In this process, the BSS sends a BSSAP CIRCUIT GROUP
BLOCK/UNBLOCK message to the MSC. Upon receiving this message,
the MSC returns a BSSAP CIRCUIT GROUP BLOCK/UNBLOCK ACK
message to the BSS, informing the BSS that it has received the BSSAP
CIRCUIT GROUP BLOCK/UNBLOCK message.
Start: A BSSAP CIRCUIT GROUP BLOCK/UNBLOCK message is sent
to the MSC.
Stop: A BSSAP CIRCUIT GROUP BLOCK/UNBLOCK ACK message
is received from the MSC.
At expiry: If the number of times that no acknowledgement message is
received from the MSC does not exceed the maximum number, the
BSC sends the BSSAP CIRCUIT GROUP BLOCK/UNBLOCK message
again. If the number of times that no acknowledgement is received from
Description the MSC exceeds the maximum number, the instance is terminated.

Managed Object BSC

30..150
Value Range and Step Step: 1

Unit 100 ms

2-95

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Default Value 80

Generally, an acknowledgement message can be received in


Default Value
eight seconds after the BSC sends a BSSAP CIRCUIT GROUP
Configuration Reason
BLOCK/UNBLOCK message to the MSC.

Configuration Rule and


Adjustment Suggestion The default value is recommended.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.5.6 RLSD message receive protection timer (T9101)


Full Name RLSD message receive protection timer

Abbreviation T9101

3GPP Name None

3GPP Reference None

This parameter is timer T9101.


Start: When the BSC sends a BSSAP CLEAR COMPLETE message
to the MSC.
Stop: When an RLSD message is received from the MSC.
At expiry: The BSC sends an RLSD message to release the SCCP
Description connection.

Managed Object BSC

20..50
Value Range and Step Step: 1

2-96

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Unit 100 ms

Default Value 20

Default Value Generally, the BSC can receive a message from the MSC in two
Configuration Reason seconds.

Configuration Rule and


Adjustment Suggestion The default value is recommended.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.5.7 Channel activation protection timer (RmsT9103)


Full Name Channel activation protection timer

Abbreviation RmsT9103

3GPP Name None

3GPP Reference None

This parameter is timer T9103, which is used to supervise the channel


activation process.
Start: When the BSC sends a CHANNEL ACTIVATION message to
the BTS.
Stop: When the BSC receives a CHANNEL ACTIVATION ACK or
CAHNNEL ACTIVATION NACK message from the BTS.
At expiry: The BSC sends an RF CHANNEL RELEASE message to
Description the BTS.

Managed Object BSC

2-97

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Value Range and Step 20

Unit 100 ms

Default Value 20

Default Value Generally, the CHANNEL ACTIVATION ACK message can be received
Configuration Reason from the BTS in two seconds.

Configuration Rule and


Adjustment Suggestion Only the default value can be used.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Abis

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.5.8 MSC clear command protection timer (T9104)


Full Name MSC clear command protection timer

Abbreviation T9104

3GPP Name None

3GPP Reference None

This parameter is timer T9104, which is used to supervise the CLEAR


COMMAND sent from the MSC.
Start: When the BSC sends a CLEAR REQUEST message to the MSC.
Stop: When a CLEAR COMMAND message is received from the MSC.
At expiry: The BSC sends the CLEAR REQUEST again. The number of
Description times that the CLEAR REQUEST message is sent cannot exceed four.

Managed Object BSC

2-98

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

20..50
Value Range and Step Step: 1

Unit 100 ms

Default Value 30

Default Value Generally, the CLEAR COMMAND message can be received from the
Configuration Reason MSC in three seconds.

Configuration Rule and


Adjustment Suggestion The default value is recommended.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.5.9 SCCP connection protection timer (T9105)


Full Name SCCP connection protection timer

Abbreviation T9105

3GPP Name None

3GPP Reference None

This parameter is timer T9105, which is used to supervise the SCCP


connection process.
Start: When the BSC sends a SCCP CONNECTION REQ message
to the MSC.
Stop: When the BSC receives a SCCP CONNECTION CONFIRM or
SCCP CONNECTION REFUSED message from the BTS.
Description At expiry: The BSC sends a CHANNEL RELEASE message to the MS.

2-99

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Managed Object BSC

20..60
Value Range and Step Step: 1

Unit 100 ms

Default Value 30

Default Value Generally, the SCCP CONNECTION CONFIRM or SCCP CONNECTION


Configuration Reason REFUSED message can be received from the MSC in three seconds.

Configuration Rule and


Adjustment Suggestion The default value is recommended.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.5.10 Protective time waiting for access (RmsT1)


Full Name Protective time waiting for access

Abbreviation RmsT1

3GPP Name None

3GPP Reference None

2-100

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

This parameter is timer RmsT1, which specifies the protection time used
to wait for the access of the MS after the channel activation in the case
of assignment or handover.
Start: When the target channel sends a RADIO AVAILABLE message to
the source channel after receiving the CHL ACITIVATION ACK message.
Stop: The target channel receives an ASSIGNMENT COM or
HANDOVER COM message after the MS is accessed.
Description At expiry: Release the target channel instance.

Managed Object BSC

0..1000
Value Range and Step Step: 1

Unit 100 ms

Default Value 70

Default Value
Configuration Reason Generally, the MS can be accessed in seven seconds.

The default value is recommended. A too large parameter value will


Configuration Rule and cause long-time occupation of radio resources, which results in the
Adjustment Suggestion waste of resources. A too small parameter value may increase the
access failure rate.

Change Mode Offline

Related features None

Related Parameters [BSC]rmsT3107


[BSC]rmsT3103

For intra-cell handovers, RmsT1 (7s) > RmsT3107 (6s)


Relationship
For inter-cell handovers, RmsT1 (7s) > RmsT3103 (6s)

Related Interfaces Abis

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-101

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

2.5.11 Protection time for applying to channel (RmsT2)


Full Name Protection time for applying to channel

Abbreviation RmsT2

3GPP Name None

3GPP Reference None

This parameter is timer T2, which indicates the protection time for TCH
application when an assignment request is received from the A interface
or an intra-cell handover is initiated.
Start: An assignment request is received from the A interface or an
intra-cell handover is initiated.
Stop: The TCH activation succeeds. The TCH activation fails. Or the
TCH request is placed on the queue after request failure.
At expiry:
An assignment failure message is sent to the MSC in the case of
assignment request.
The service is shifted back to the source channel in the case of handover
Description request.

Managed Object BSC

20..50
Value Range and Step Step: 1

Unit 100 ms

Default Value 40

Default Value Generally, a request success or failure message can be received in


Configuration Reason four seconds.

Configuration Rule and


Adjustment Suggestion The default value is recommended.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer1

2-102

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.5.12 Protection time for link establishment response (RmsT3)


Full Name Protection time for link establishment response

Abbreviation RmsT3

3GPP Name None

3GPP Reference None

This parameter is timer T3, which indicates the protection time for an
A interface link establishment response in an immediate assignment
process.
Start: The BSC sends an ESTABLISH IND message for immediate
assignment.
Stop: The BSC receives an A interface link establishment
acknowledgement message.
Description At expiry: Release the service.

Managed Object BSC

30..100
Value Range and Step Step: 1

Unit 100 ms

Default Value 60

Default Value
Configuration Reason Generally, six seconds are enough for protection.

Configuration Rule and


Adjustment Suggestion The default value is recommended.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

2-103

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.5.13 Protective time that P0 confirms the message HO/ASS COM


(RmsT4)
Full Name Protective time that P0 confirms the message HO/ASS COM

Abbreviation RmsT4

3GPP Name None

3GPP Reference None

This parameter is timer T4, which indicates the protection time for the
OMP to acknowledge the HO COM or ASS COM message.
Start: The BSC receives an HO COM or ASS COM message from the
MS.
Stop: The BSC receives an acknowledgement on the HO COM or ASS
COM message.
Description At expiry: Release the service.

Managed Object BSC

10..80
Value Range and Step Step: 1

Unit 100 ms

Default Value 30

Default Value
Configuration Reason Generally, three seconds are enough.

Configuration Rule and


Adjustment Suggestion The default value is recommended.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

2-104

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.5.14 Encryption mode modification time (RmsT5)


Full Name Encryption mode modification time

Abbreviation RmsT5

3GPP Name None

3GPP Reference None

This parameter is timer T5, which is used to supervise the cipher mode
modify process, that is, wait for a response from the MS after the radio
cipher mode is set.
Start: When the BSC receives a CIPHER MODE COMMAND message
from the MSC.
Stop: When the BSC receives a CIPHER MODE COMPLETE message
from the MS.
At expiry: A BSSAP CIPHER MODE REJECT message is sent to the
Description MSC.

Managed Object BSC

30..120
Value Range and Step Step: 1

Unit 100 ms

Default Value 100

Default Value Generally, the CIPHER MODE COMPLETE message can be received
Configuration Reason from the MS in 10 seconds.

Configuration Rule and


Adjustment Suggestion The default value is recommended.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

2-105

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.5.15 SAPI3 link establishment time (RmsT6)


Full Name SAPI3 link establishment time

Abbreviation RmsT6

3GPP Name None

3GPP Reference None

This parameter is timer T6, which is used to supervise the establishment


of SAPI3 link.
Start: When the BSC receives a DTAP (SAPI=3) message from the
MSC, and no SAPI3 link exists.
Stop: When the BSC receives a ESTABLISH CONFIRM message from
the BTS.
Description At expiry: Send a BSSMAP SAPI"n"REJECT message to the MSC.

Managed Object BSC

10..300
Value Range and Step Step: 1

Unit 100 ms

Default Value 100

Default Value Generally, the ESTABLISH CONFIRM message can be received from
Configuration Reason the BTS in 10 seconds.

Configuration Rule and


Adjustment Suggestion The default value is recommended.

Change Mode Offline

Related features None

Related Parameters None

2-106

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Relationship None

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.5.16 External handover protective time (RmsT8)


Full Name External handover protective time

Abbreviation RmsT8

3GPP Name None

3GPP Reference None

This parameter is timer RmsT8, which is used to supervise the external


handover process.
Start: When the BSC sends an external handover command.
Stop: When the BSC receives an HO COMCLEAR CMD (handover
success) or UM HO FAIL (handover failure) message.
Description At expiry: Release the service.

Managed Object BSC

1..1000
Value Range and Step Step: 1

Unit 100 ms

Default Value 100

Default Value
Configuration Reason Generally, an external handover can be completed in 10 seconds.

The default value is recommended. If the external handover success


Configuration Rule and
rate is low, increase the parameter value. However, a too large
Adjustment Suggestion
parameter value will impact the user experience.

Change Mode Offline

Related features None

2-107

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.5.17 Protective time for No.7 signal instantaneous disconnection


(T3)
Full Name Protective time for No.7 signal instantaneous disconnection

Abbreviation T3

3GPP Name None

3GPP Reference None

This parameter is timer T3, which specifies a delay to avoid improper


actions caused by transient interruption of signallings.
A global reset is initiated when the interruption time of SS7 signallings
exceeds the protection time specified by timer T3. The SS7 signalling
link is deemed as broken if no signalling point reachable event is
received in the delay duration, and a global reset is initiated. If the
signalling point reachable event is received in the delay duration, it is
deemed that transient interruption of the SS7 link occurs.
Start: The periodic detection of MSC office status is interrupted. Or an
MSC/SLMC/iTC reset message is received.
Stop: An MSC reachable message is received from the MSC.
At expiry: If the opposite office is unreachable, clear the opposite office
block field and the opposite office un-equipped field, and send an MSC
Description RESET message to the global reset process.

Managed Object BSC

10..200
Value Range and Step Step: 1

2-108

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Unit 100 ms

Default Value 100

Generally, it is deemed that a transient interruption of SS7 signalling


Default Value link occurs when the failed SS7 signalling link restores in 10 seconds.
Configuration Reason The global reset is not needed in the case of transient interruption of
SS7 signalling link.

Configuration Rule and


Adjustment Suggestion The default value is recommended.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.5.18 Protective time that PO responses external handover


completion message (RmsT7)
Protective time that PO responses external handover completion mes-
Full Name sage

Abbreviation RmsT7

3GPP Name T7

3GPP Reference 3GPP TS 48.008 V5.12.0

This parameter is RmsT7, which specifies the protection time for the
OMP to acknowledge an assignment or handover complete message.
Start: The BSC sends a handover request.
Stop: The BSC receives the HO CMD message.
Description At expiry: Impose penalty to the external cell and terminate the process.

2-109

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Managed Object BSC

50..200
Value Range and Step Step: 1

Unit 100 ms

Default Value 150

Default Value
Configuration Reason Generally, an external handover can be completed in 15 seconds.

Configuration Rule and


Adjustment Suggestion The default value is recommended.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.5.19 HBTS scan begin time (HBTSScanBT)


Full Name HBTS scan begin time

Abbreviation HBTSScanBT

3GPP Name None

3GPP Reference None

Description This parameter indicates the starting time of the S8001 frequency scan.

Managed Object BSC

0..23
Value Range and Step Step: 1

Unit None

2-110

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Default Value 3 (indicating three o'clock)

Default Value Generally, the traffic is small at three o'clock in the morning, when the
Configuration Reason scan has the minimum effect on the system.

The default value is recommended. According to the actual network


Configuration Rule and
conditions, you can also set this parameter to the time when the traffic
Adjustment Suggestion
is the smallest.

Change Mode Offline

Related features None

Related Parameters [BSC]HBTSScanSiteNum

If HBTSScanSiteNum is set to 0, this parameter is configurable but


Relationship
invalid.

Related Interfaces Abis口

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed element ID->Config set


OMC Access Path
ID->BSC Function->Timer1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.5.20 HBTS scan cycle (HBTSScanCyc)


Full Name HBTS scan cycle

Abbreviation HBTSScanCyc

3GPP Name None

3GPP Reference None

This parameter indicates the period of the S8001 frequency scan.


Start: A new periodic frequency calibration message is received and a
calibration is started.
Description Stop: The old periodic frequency calibration message is killed.

Managed Object BSC

1..255
Value Range and Step Step: 1

Unit 3600s

2-111

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Default Value 24

Default Value
Configuration Reason By default, the scan is carried out once per 24 hours.

Configuration Rule and


Adjustment Suggestion The default value is recommended.

Change Mode Offline

Related features None

Related Parameters [BSC]HBTSScanSiteNum

If HBTSScanSiteNum is set to 0, this parameter is configurable but


Relationship
invalid.

Related Interfaces Abis口

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed element ID->Config set


OMC Access Path
ID->BSC Function->Timer1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.5.21 IP ABIS Pool Band Width Push Down Protection


(TBWPushDown)
Full Name IP ABIS Pool Band Width Push Down Protection

Abbreviation TBWPushDown

3GPP Name None

3GPP Reference None

This parameter is a protection timer for decreasing bandwidth of some


channels when the bandwidth resources are not enough. If the time since
the previous bandwidth decreasing is shorter than the time specified by
Description this timer, no bandwidth decreasing is allowed.

Managed Object BSC

1..10
Value Range and Step Step: 1

Unit s

2-112

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Default Value 5

The default value is set to avoid frequent decreasing of bandwidth. Five


Default Value
seconds are appropriate because the bandwidth is reported for five
Configuration Reason
times in this period.

The default value is recommended.


1) Decreasing the parameter value results in bandwidth decreasing at a
Configuration Rule and
high frequency.
Adjustment Suggestion
2) Increasing the parameter value results in bandwidth decreasing at a
low frequency.

Change Mode Offline

Related features ZGO-03-01-002 Transmission Based CAC

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.5.22 IP ABIS Pool Band Width Restore (TBWRestore)


Full Name IP ABIS Pool Band Width Restore

Abbreviation TBWRestore

3GPP Name None

3GPP Reference None

This parameter is a timer for increasing the bandwidth of some channels


whose bandwidth used to be decreased when the bandwidth resource
is enough. This timer should be set when the measured bandwidth is
Description smaller than the threshold for increasing the bandwidth.

Managed Object BSC

2-113

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

1..10
Value Range and Step Step: 1

Unit s

Default Value 2

Five seconds are appropriate during which the bandwidth is reported


Default Value
for five times. Such a period will not cause too frequent bandwidth
Configuration Reason
increasing or bandwidth increasing failure in a long time.

The default value is recommended.


1) Decreasing the parameter value results in bandwidth increasing at a
Configuration Rule and
high frequency.
Adjustment Suggestion
2) Increasing the parameter value results in bandwidth increasing at a
low frequency.

Change Mode Offline

Related features ZGO-03-01-002 Transmission Based CAC

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.5.23 Time of waiting an internal HO command


(TWaitInternalHoCmd)
Full Name Time of waiting an internal HO command

Abbreviation TWaitInternalHoCmd

3GPP Name None

3GPP Reference None

2-114

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

This parameter specifies the waiting time for an intra-BSC handover


command message from the MSC after the BSC sends an internal
handover request.
Start: The BSC sends an internal handover request to the MSC when
the handover criterion is fulfilled.
Stop: An internal handover command is received from the MSC.
At expiry: Send a RadioUnavail message to the target instance, and
terminate the instance.
Description Associated timer: None

Managed Object BSC

1..100
Value Range and Step Step: 1

Unit 100 ms

Default Value 20

The default value is set to 20 because two seconds are enough for
Default Value
signalling transfer at the A interface and signalling processing in the
Configuration Reason
MSC.

Generally, the default value is recommended. The waiting time can be


Configuration Rule and
appropriately prolonged if the timer expires when waiting for the internal
Adjustment Suggestion
handover command.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-115

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

2.5.24 Wait response of bts or btsgroup establish localswitch link


(TWaitLocalSwitch)
Full Name Wait response of bts or btsgroup establish localswitch link

Abbreviation TWaitLocalSwitch

3GPP Name None

3GPP Reference None

This parameter is a timer used to wait for a local switch setup


acknowledgement from the base station.
Start: A local switch setup request is sent to the base station.
Stop: A local switch setup acknowledgement is received from the base
station.
At expiry: In the case of local switch setup phase, a local switch setup
failure message is responded to the local switch management module.
In the case of local switch stop suspend phase, a local switch suspend
failure message is responded to the local switch management module,
Description and the instance is released.

Managed Object BSC

0..80
Value Range and Step Step: 1

Unit 100 ms

Default Value 20

Default Value Two seconds are long enough for the Abis interface to transmit signalling
Configuration Reason and for the BTS to process signalling.

Configuration Rule and


Adjustment Suggestion Generally, the default value is recommended.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Abis

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer1

2-116

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.5.25 Wait response of localswitch release link


(TWaitLsReleaseAck)
Full Name Wait response of localswitch release link

Abbreviation TWaitLsReleaseAck

3GPP Name None

3GPP Reference None

This parameter is a protection timer used to wait for a local switch link
connection release acknowledgement message.
Start: A request for releasing the old link connection is sent to the
connection module.
Stop: An acknowledgement of link connection release request is
received from the connection module.
At expiry: In the case of local switch setup phase, a local switch setup
failure message is responded to the local switch management module.
In the case of local switch stop suspend phase, a local switch suspend
failure message is responded to the local switch management module,
Description and the instance is released.

Managed Object BSC

0..80
Value Range and Step Step: 1

Unit 100 ms

Default Value 20

Default Value
Configuration Reason Two seconds are enough to complete the internal connection release.

Configuration Rule and


Adjustment Suggestion Generally, the default value is recommended.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

2-117

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.5.26 Wait response of localswitch connect (TWaitLSBscConn)


Full Name Wait response of localswitch connect

Abbreviation TWaitLSBscConn

3GPP Name None

3GPP Reference None

This parameter is a timer used to wait for a local switch connection


acknowledgement message from the connection module.
Start: A local switch connection message is sent to the connection
module.
Stop: A local switch connection acknowledgement message is received
from the connection module. The instance is terminated.
At expiry: A local switch setup failure message is returned to the local
Description switch management module. And timer TWaitLsReleaseAck is started.

Managed Object BSC

0..80
Value Range and Step Step: 1

Unit 100 ms

Default Value 20

Default Value
Configuration Reason Two seconds are enough to complete the internal connection.

Configuration Rule and


Adjustment Suggestion Generally, the default value is recommended.

Change Mode Offline

Related features None

Related Parameters None

2-118

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.5.27 Wait request of local switch release link (TWaitLSReleas


eReq)
Full Name Wait request of local switch release link

Abbreviation TWaitLSReleaseReq

3GPP Name None

3GPP Reference None

This parameter is a protection timer used to wait for a local switch link
release request message.
Start: A local switch set failure acknowledgement message is sent to the
local switch management module.
Stop: A local switch link release request message is received from the
local switch management module.
Description At expiry: Resume the switch status before the local switch request.

Managed Object BSC

0..80
Value Range and Step Step: 1

Unit 100 ms

Default Value 20

Default Value
Configuration Reason Two seconds are enough for internal interaction between CMP and OMP.

Configuration Rule and


Adjustment Suggestion Generally, the default value is recommended.

Change Mode Offline

Related features None

2-119

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6 Timer 2
2.6.1 Protective time for RF channel release (RmsT9)
Full Name Protective time for RF channel release

Abbreviation RmsT9

3GPP Name None

3GPP Reference None

This parameter is timer T9.


Start: An RF CHANNEL RELEASE message is sent to the BTS when
the RANCS instance is released.
Stop: The RANCS instance receives an RF CHANNEL RELEASE ACK
message from the BTS.
Description At expiry: Release the service instance.

Managed Object BSC

10..50
Value Range and Step Step: 1

Unit 100 ms

Default Value 20

Default Value Generally, the RF CHANNEL RELEASE ACK message can be received
Configuration Reason from the BTS in two seconds.

2-120

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

The larger the parameter value is, the longer the waiting time is, and the
Configuration Rule and longer the time needed for service release due to the occurrence of
Adjustment Suggestion exception. This parameter is invalid now. The RMST11 is set by the
setting of Emlpp.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Abis

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.2 Queue period of assignment (RmsT11)


Full Name Queue period of assignment

Abbreviation RmsT11

3GPP Name T11

3GPP Reference 3GPP TS 48.008 V5.12.0

This parameter is timer T11, which indicates the longest allowable


queuing time of assignment attempt.
Start: The assignment queuing switch is enabled. No channel is
assigned for an assignment request and the queuing for resources starts.
Stop: An available channel resource is assigned.
At expiry: Release the service instance on the target channel.
This parameter is invalid now. The RMST11 is set by the setting of
Description Emlpp.

Managed Object BSC

10..1000
Value Range and Step Step: 1

Unit 100 ms

2-121

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Default Value 60

Default Value Generally, it is no need to queue if no channel is assigned within six


Configuration Reason seconds.

The longer the queuing time for assignment is, the more likely the
assignment succeeds. However, too long queuing time increases the
Configuration Rule and
access time and impacts user experience. This parameter, locked in the
Adjustment Suggestion
network management system, cannot be modified. T11 is set by setting
RMST11 in eMLPP.

Change Mode Offline

Related features ZGB-03-01-003 Queuing

Related Parameters None

Relationship None

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.3 Acknowledgment interval for periodic status (RmsT12)


Full Name Acknowledgment interval for periodic status

Abbreviation RmsT12

3GPP Name None

3GPP Reference None

2-122

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

This parameter is timer T12, which indicates the interval of periodic


status confirmation.
Start: The timer is started for the first time when the RANCS decides to
detect the activity of the opposite end upon receiving a CONNECT CONF
message from the RANA. After that, the timer is periodically started.
Stop: The RANCS instance receives a release message.
At expiry: If the number of timer expiries does not exceed four, the timer
is started. If the number of timer expiries exceeds four, the service
Description instance is released.

Managed Object BSC

50..18000
Value Range and Step Step: 1

Unit 100 ms

Default Value 50

Default Value Generally, an acknowledgement message can be received from the


Configuration Reason MSC in five seconds.

The larger the parameter value is, the longer the time waiting for an
Configuration Rule and
acknowledgement message is. You can adjust the parameter value
Adjustment Suggestion
according to the actual situation.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.4 Mode modification process time (RmsT13)


Full Name Mode modification process time

2-123

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Abbreviation RmsT13

3GPP Name None

3GPP Reference None

This parameter is timer T13, which is used to supervise the mode modify
process of the BTS and MS. Mode modification refers to channel mode
modification. After the assignment of FACCH in the case of no SDCCH,
the channel mode is changed because no new channel will be allocated.
Start: The BSC sends a MODE MODIFY message to the BTS, and
sends a CHANNEL MODE MODIFY message to the MS.
Stop: The BSC receives a MODE MODIFY ACK/NACK message from
the BTS, and receives a CHANNEL MODE MODIFY ACK message
from the MS.
At expiry: Send a BSSMPA ASSIGNMENT FAILURE message to the
Description MSC.

Managed Object BSC

35..100
Value Range and Step Step: 1

Unit 100 ms

Default Value 60

Default Value
Configuration Reason The default value, being an experimental value, is recommended.

Increase the parameter value appropriately if the mode modification


Configuration Rule and
failure frequently occurs, that is, the number of times that the timer
Adjustment Suggestion
expires is large.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Abis

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

2-124

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Parameter Modifying
Detail None

2.6.5 Protective time of UM assignment completion (RmsT14)


Full Name Protective time of UM assignment completion

Abbreviation RmsT14

3GPP Name None

3GPP Reference None

This parameter is timer T14, which indicates the protection time for the
completion of UM assignment.
Start: The target child process sends ASS/HO COM to the source child
process.
Stop: The target child process receives ASS/HO COM ACK from the
source child process.
Description At expiry: Release the service.

Managed Object BSC

10..50
Value Range and Step Step: 1

Unit 100 ms

Default Value 20

Default Value This parameter is an internal parameter. The default value is


Configuration Reason recommended.

Configuration Rule and Increase the parameter value appropriately if the number of UM
Adjustment Suggestion assignment failures increases.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

2-125

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.6 Waiting time for oriented retry (RmsT16)


Full Name Waiting time for oriented retry

Abbreviation RmsT16

3GPP Name None

3GPP Reference None

This parameter is timer RmsT16. In a directed retry process, the timer


is used to wait for receiving measurement reports when no target cell
is detected. Upon the expiry of the timer, the directed retry process is
initiated again to find whether some target cell is available. This process
can be repeated for several times.
Start: The source instance initiates a directed retry process after
receiving a radio resource request failure.
Stop: None
At expiry: When the number of timer expiries exceeds three, an
assignment failure message is sent to the MSC to wait for a clear
message. If the number of timer expiries does not exceed three, the
Description directed retry process is initiated again.

Managed Object BSC

20..60
Value Range and Step Step: 1

Unit 100 ms

Default Value 20

Default Value This parameter is an internal parameter. The default value is


Configuration Reason recommended.

Configuration Rule and The longer the waiting time is, the more likely the directed retry
Adjustment Suggestion succeeds. However, a too long waiting time is meaningless.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

2-126

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.7 Queue period for handover (RmsTqho)


Full Name Queue period for handover

Abbreviation RmsTqho

3GPP Name Tqho

3GPP Reference TS48.008

This parameter indicates the longest allowable queuing time for a


handover attempt.
Start: When the handover queuing switch is enabled, and no channel is
allocated for the handover request.
Stop: An available channel resource is assigned.
At expiry: Release the service instance on the target channel.
This parameter is already invalid. It is replaced by the handover queuing
Description timer (Emlpp), which specifies the handover queuing time.

Managed Object BSC

10..1000
Value Range and Step Step: 1

Unit 100 ms

Default Value 50

Default Value Make sure that the handover queuing time is no longer than two
Configuration Reason handover criteria periods.

This parameter specifies the handover queuing time. The larger the
parameter value is, the longer the handover queuing time is. A longer
queuing time can effectively reduce the congestion ratio. However, too
Configuration Rule and
long queuing time may cause handover failure when the signal in the
Adjustment Suggestion
neighbor cell changes. This parameter is already invalid. It is replaced
by the handover queuing timer (Emlpp), which specifies the handover
queuing time.

2-127

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.8 First overload period of flow traffic control (mT11)


Full Name First overload period of flow traffic control

Abbreviation mT11

3GPP Name None

3GPP Reference None

The parameter is timer mT11, which is used for flow control in the case
of cell overload. mT11 works together with mT12 to modify the ACCESS
CONTROL parameter configured for the cell and inform the MS about
this modification through system information to achieve the flow control.
The RACH LOAD INDICATION message from the BTS is not processed
when the timer is started. The value set for timer mT11 must be smaller
than that for timer mT12.
Start: An RACH LOAD INDICATION message is received from the BTS.
Stop: None
At expiry: Continue processing the RACH LOAD INDICATION message
of the BTS.
Description Associated timer: mT12

Managed Object BSC

30..150
Value Range and Step Step: 1

Unit 100 ms

2-128

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Default Value 80

The fluctuation of overload indication is unlikely to cause the flow


Default Value
control fluctuation if new overload indication is not processed within
Configuration Reason
eight seconds.

The larger the parameter value is, the more stable the flow control is due
Configuration Rule and to lower sensitivity to load indication. The smaller the parameter value
Adjustment Suggestion is, the more likely the flow control fluctuates due to higher sensitivity to
load indication.

Change Mode Offline

Related features ZGB-03-04-001 BSC Load Control

Related Parameters [BSC]mT12

Relationship mT11<mT12

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.9 Second overload period of flow traffic control (mT12)


Full Name Second overload period of flow traffic control

Abbreviation mT12

3GPP Name None

3GPP Reference None

2-129

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

The parameter is timer mT12, which is used for flow control in the case
of cell overload. mT12 works together with mT11 to modify the ACCESS
CONTROL parameter configured for the cell and inform the MS about
this modification through system information to achieve the flow control.
The value of this timer must be larger than that of mT11 timer. The
process how mT11 and mT12 control the cell traffic is as follows: When
an overload message is received at the network side, the system
lowers the traffic level by one, and then starts mT11 and mT12. The
OVERLOAD message received before the expiry of mT11 is neglected.
If an OVERLOAD message is received after the expiry of mT11 but
before the expiry of mT12, the system lowers the traffic level by one
again, and restarts mT11 and mT12. If no OVERLOAD message is
received after the expiry of mT12, the system increases the traffic level
by one and then restarts mT12. The change of traffic level means
different traffic rejection ratio.
Start: An RACH LOAD INDICATION message is received from the BTS.
Stop: A RACH LOAD INDICATION message from the BTS is received
after the expiry of mT11.
At expiry: Lower the traffic level by one.
Description Associated timer: mT11

Managed Object BSC

50..200
Value Range and Step Step: 1

Unit 100 ms

Default Value 150

mT11 is used to prevent the fluctuation of load indication. mT12 is used


to adjust traffic level after a new load indication is received. If no load
Default Value
indication is received after the expiry of mT12, the system lowers the
Configuration Reason
flow control level. 150The default value is set to 150, which is almost
twice the value of

Configuration Rule and The larger the parameter value is, the greater the flow control fluctuation
Adjustment Suggestion is. Similarly, a smaller parameter value corresponds to less fluctuation.

Change Mode Offline

Related features ZGB-03-04-001 BSC Load Control

Related Parameters [BSC]mT11

Relationship mT11<mT12

Related Interfaces None

Impact on Equipment 0

Impact on service 0

2-130

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.10 Time of micro-micro handover delay (Tmicro)


Full Name Time of micro-micro handover delay

Abbreviation Tmicro

3GPP Name None

3GPP Reference None

This parameter is a timer used to prevent an MS travelling fast from


camping on the same layer. The timer is started when the MS is handed
over to a cell (or a call is set up). Before the expiry of the timer, the
MS cannot be handed over to a neighbour cell on the same layer. A
neighbour cell on the same layer can be a candidate only after the
expiry of the timer.
Start: A call is set up.
Stop: None
At expiry: Enable the handover on the same layer.
Description Associated timer: None

Managed Object BSC

1..200
Value Range and Step Step: 1

Unit 100 ms

Default Value 80

The purpose of this timer is to reduce the handover times of the


fast-travelling MS in a lower-layer network. Generally, it is sure that the
Default Value
MS still camping on the cell after eight seconds is not travelling fast. To
Configuration Reason
prevent the handover of the MS on the same layer, the default value
is set to 80.

Set the parameter value according to the geographic location and


Configuration Rule and
distribution of cells and the mobility of MSs in the area. The larger the
Adjustment Suggestion
parameter value is, the longer the limitation on handover is.

Change Mode Offline

2-131

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.11 BSIC decoding period (Tbsic)


Full Name BSIC decoding period

Abbreviation Tbsic

3GPP Name None

3GPP Reference None

This parameter specifies a time period starting from the setup of a call or
the completion of a handover (inter-cell or intra-cell) during which the
evaluation of C/I is deemed as unreliable and therefore the handover
to a specific TRX is not allowed. In this period, the MS can decode the
BSIC of the interfering (adjacent) cell before a handover decision.
This parameter is only valid in the case of concentric cell.
Start: Relevant parameters are initiated after the setup of a link to the
MS upon immediate assignment, assignment, or handover.
Stop: The timer expires.
Description At expiry: Reset the timer.

Managed Object BSC

20..640
Value Range and Step Step: 1

Unit 100 ms

Default Value 50

Default Value Generally, C/I value obtained within five seconds after the setup of a call
Configuration Reason is regarded as unreliable.

2-132

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Configuration Rule and The default value is recommended. The larger the parameter value is,
Adjustment Suggestion the longer the time used for BSIC decoding is.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Abis

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.12 Handover protecting timer to WCDMA/FDD (RmsT3121)


Full Name Handover protecting timer to WCDMA/FDD

Abbreviation RmsT3121

3GPP Name T3121

3GPP Reference 3GPP TS 44.018

This parameter is timer T3121, which specifies the protection time after
the inter-system to utran handover command (UM) is sent to the MS.
Start: When the BSC sends an INTER-SYSTEM TO UTRAN
HANDOVER COMMAND message to the MS.
Stop: When the BSC receives a CLEAR COMMAND from the MSC
(which is generally sent after the completion of handover), or receives a
HANDOVER FAILURE message from the MS.
At expiry: The BSC sends a CLEAR REQUEST message to the MSC.
The cause value is CAUSE_RI_MSG_FAIL, indicating a message failure
Description at the radio interface.

Managed Object BSC

1..650
Value Range and Step Step: 1

Unit 100 ms

2-133

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Default Value 100

Default Value The default value is set in consideration of the time needed for the MS to
Configuration Reason receive an inter-system handover command and complete the handover.

A too large parameter value may result in the waste of channel resources
Configuration Rule and
and traffic congestion. A too small parameter value may decrease the
Adjustment Suggestion
handover success rate.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.13 Immediate assignment period (RmsT3101)


Full Name Immediate assignment period

Abbreviation RmsT3101

3GPP Name T3101

3GPP Reference 3GPP TS 44.018

This parameter is timer T3101, which is used to supervise the immediate


assignment process.
Start: When the BSC sends an IMMEDIATE ASSIGNMENT COMMAND
message.
Stop: When an ESTABLISH INDICATION message is received from
the BSC.
At expiry: The BSC sends an RF CHANNEL RELEASE message to
Description the BTS.

Managed Object BSC

2-134

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

10..100
Value Range and Step Step: 1

Unit 100 ms

Default Value 30

The default value is set in consideration of the time needed for sending
Default Value
an immediate assignment message to the MS and the time needed
Configuration Reason
for the MS to access the network.

A too large parameter value may result in the waste of channel resources
Configuration Rule and
and traffic congestion. A too small parameter value may decrease the
Adjustment Suggestion
immediate assignment success rate.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.14 Handover period of source cell (RmsT3103)


Full Name Handover period of source cell

Abbreviation RmsT3103

3GPP Name T3103

3GPP Reference 3GPP TS 44.018

2-135

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

This parameter is timer T3103, which is used to supervise an intra-BSC


handover process.
Start: When the BSC sends an HANDOVER COMMAND message to
the MS.
Stop: When the BSC receives a HANDOVER COMPLETE message on
the new channel from the MS, or a HANDOVER FAILURE message
on the old channel from the MS.
At expiry: The BSC sends a CLEAR REQUEST message to the MSC.
The cause value is CAUSE_RI_FAIL, indicating a radio interface failure.
Description The new channel is released.

Managed Object BSC

0..1000
Value Range and Step Step: 1

Unit 100 ms

Default Value 60

The default value is set in consideration of the time needed for sending
Default Value
the handover command to the MS and the time needed for the MS to
Configuration Reason
complete the inter-cell handover.

A too large parameter value may result in the waste of channel resources
Configuration Rule and
and traffic congestion. A too small parameter value may decrease the
Adjustment Suggestion
handover success rate.

Change Mode Offline

Related features None

Related Parameters [BSC]rmst1

Relationship RmsT3103 < RmsT1

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-136

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

2.6.15 Assignment period (RmsT3107)


Full Name Assignment period

Abbreviation RmsT3107

3GPP Name T3107

3GPP Reference 3GPP TS 44.018

This parameter is timer T3107, which is used to supervise an assignment


process and an intra-cell handover process.
Start: When the BSC sends an RIL3_RR ASSIGNMENT COMMAND
message to the MS.
Stop: When the BSC receives an RIL3_RR ASSIGNMENT COMPLETE
or RIL3_RR ASSIGNMENT FAILURE message.
At expiry: In the case of an assignment process, both the new and old
channels are released, relevant connections to the MS are cleared, and
a BSSAP ASSIGNMENT FAILURE message is sent to the MSC. In the
case of an intra-cell handover process, a CLEAR REQUEST message
is sent to the MSC. The cause value is CAUSE_RI_FAIL, indicating a
Description radio interface failure.

Managed Object BSC

0..1000
Value Range and Step Step: 1

Unit 100 ms

Default Value 60

The default value is set in consideration of the time needed for sending
Default Value
the assignment command to the MS and the time needed for the MS to
Configuration Reason
complete the assignment.

A too large parameter value may result in the waste of channel resources
Configuration Rule and
and traffic congestion. A too small parameter value may decrease the
Adjustment Suggestion
assignment success rate.

Change Mode Offline

Related features None

Related Parameters [BSC]rmst1

Relationship RmsT3107 < RmsT1

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

2-137

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.16 TCH Channel release period (RmsT3109)


Full Name TCH Channel release period

Abbreviation RmsT3109

3GPP Name T3109

3GPP Reference 3GPP TS 44.018

This parameter is timer T3109, which is used to supervise a channel


release process.
Start: When the BSC send an RIL3_RR CHANNEL RELEASE message
to the MS.
Stop: When the BSC receives a RELEASE INDICATION message
from the BTS, which is sent by the BTS when a DISC frame from the
MS is received.
At expiry: The BSC sends an RF CHANNEL RELEASE message to the
Description BTS. The cause value is T3109OUT.

Managed Object BSC

0..1000
Value Range and Step Step: 1

Unit 100 ms

Default Value 50

The default value is set in consideration of the time needed for the
Default Value MS to complete the channel release after receiving a channel release
Configuration Reason command, and the time needed for the call drop of the MS caused by
the failure of receiving a channel release command.

To avoid crosstalk caused by network-side channel release before the


completion of channel release at the MS side, the value of T3109 must
Configuration Rule and
be larger than that of the radio link expiration timer at the MS side.
Adjustment Suggestion
However, a too large parameter value may result in the waste of channel
resources and traffic congestion.

Change Mode Offline

Related features None

2-138

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.17 TCH Channel deactivation delay (RmsT3111)


Full Name TCH Channel deactivation delay

Abbreviation RmsT3111

3GPP Name T3111

3GPP Reference 3GPP TS 44.018

This parameter is timer RmsTT3111, which specifies a protection time to


ensure that the radio link layer is disconnected after the radio link layer
at the Um interface is released. The release and deactivation of the
radio channel is performed upon the expiry of this timer.
Start: When the BSC receives a RELEASE INDICATION message.
At expiry: The BSC sends an RF CHANNEL RELEASE message to the
Description BTS. The cause value is T3111OUT.

Managed Object BSC

1..300
Value Range and Step Step: 1

Unit 100 ms

Default Value 3

Default Value The default value is set in consideration of the time needed for the BTS
Configuration Reason to send the UA message.

A too large parameter value may result in the waste of channel resources
Configuration Rule and and traffic congestion. If the parameter value is too small, the BTS
Adjustment Suggestion cannot send the UA message to the MS in time, and thus the MS may
fail to complete the channel release in a short time.

2-139

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.18 Continue timer for mode modify (TModeModifyConn)


Full Name Continue timer for mode modify

Abbreviation TModeModifyConn

3GPP Name None

3GPP Reference None

This parameter is a connection delay timer used in the mode change


process. This timer is used to wait for the complete of connection (Abis
connection and TC connection) after a connection request is sent.
Start: A connection request is sent.
Stop: All connections are completed.
Description At expiry: Clear this service instance.

Managed Object BSC

50..70
Value Range and Step Step: 1

Unit 100 ms

Default Value 50

Default Value The default value is set to 50 because five seconds are enough to
Configuration Reason complete all connections.

Configuration Rule and


Adjustment Suggestion Generally, the default value is recommended.

2-140

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.19 Handover protecting time to UTRAN (mT7)


Full Name Handover protecting time to UTRAN

Abbreviation mT7

3GPP Name None

3GPP Reference None

This parameter is a timer used to wait for a response from the MSC
after a HANDOVER REQUIRED message is sent to the MSC and the
target cell is a UTRAN cell.
Start: The BSC sends a HANDOVER REQUIRED message to the MSC,
and the target cell is a UTRAN cell.
Stop: The BSC receives a HANDOVER COMMAND message from
the MSC.
At expiry: Set a penalty time for the target UTRAN cell specified by the
HANDOVER REQUIRED message, during which the handover priority
of the target cell is decreased.
Description This timer is not in practical use.

Managed Object BSC

1..65535
Value Range and Step Step: 1

Unit 100 ms

Default Value 100

2-141

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

The default value is set to 100 because 10 seconds are generally


Default Value
enough for the transmission of signallings between the MSC and the
Configuration Reason
UTRAN and the preparation of handover resources in the UTRAN.

Increase the parameter value appropriately if the timer frequently expires


Configuration Rule and
when waiting for the handover command. Or else, the default value is
Adjustment Suggestion
recommended.

Change Mode Offline

Related features ZGO-02-03-009 GSM/WCDMA Interworking Phase II

Related Parameters None

Relationship None

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.20 Time to wait A handover request (TWaitAHoReq)


Full Name Time to wait A handover request

Abbreviation TWaitAHoReq

3GPP Name None

3GPP Reference None

This parameter specifies the waiting time for the handover through A
interface in a 2G/3G relocation process.
Start: A radio resource reservation success message is sent to the RNC.
Stop: A handover request is received from the MSC.
At expiry: Release the radio resource, and terminate the instance.
Description Associated timer: None

Managed Object BSC

4..50
Value Range and Step Step: 1

2-142

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Unit 100 ms

Default Value 10

The default value is set to 10 because one second is enough for the
Default Value
RNC to send a handover request to the MSC and for the MSC to forward
Configuration Reason
the handover request to the BSC.

Generally, the default value is recommended. The waiting time can


Configuration Rule and
be appropriately prolonged if the timer expires when waiting for the
Adjustment Suggestion
handover through A interface.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.21 Time of destination instance waiting for available resources


when forced disconnection (RmsT15(TForceOccupy))
Time of destination instance waiting for available resources when forced
Full Name disconnection

Abbreviation RmsT15(TForceOccupy)

3GPP Name None

3GPP Reference None

2-143

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

This parameter indicates the waiting time for the release of resource
when an instance is forcibly released.
Start: A PREEMPT APPLY message is sent to the object to be released
when the target instance is going to be forcibly released.
Stop: The target instance receives a response of RESOURCE
AVAILABLE from the object to be released.
At expiry: Search for another instance that can be forcibly released. If
the instance to be released exists, a forced release process is retried,
Description and RmsT15 (TForceOccupy) is started.

Managed Object BSC

10..50
Value Range and Step Step: 1

Unit 100 ms

Default Value 30

Default Value The default value is set to 30 because three seconds are enough for the
Configuration Reason forcibly-released instance to release the resource.

Configuration Rule and


Adjustment Suggestion Generally, the default value is recommended.

Change Mode Offline

Related features ZGO-01-03-001 eMLPP

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.22 Protecting time of FUC response to system message


broadcast (BcProtect)
Full Name Protecting time of FUC response to system message broadcast

2-144

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Abbreviation BcProtect

3GPP Name None

3GPP Reference None

This parameter is a protection timer used to wait for a response from


the FUC after the system information is broadcasted. A response from
the FUC indicates that the BTS has correctly received the system
information.
Start: The BSC sends the system information to the BTS.
Stop: The BSC receives a response to the system information from
the BTS.
At expiry: If the number of timer expiries does not exceed four (the
maximum number of allowable times), the BSC sends the system
information to the BTS again and the timer is restarted. If the number
of timer expiries exceeds four, the BSC stops sending the system
information to the BTS and clears the cell instance information of the
BTS.
Description This timer is not in practical use.

Managed Object BSC

30..100
Value Range and Step Step: 1

Unit 100 ms

Default Value 50

Default Value Five seconds are enough for the FUC to receive and process the system
Configuration Reason information.

Configuration Rule and


Adjustment Suggestion Generally, the default value is recommended.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Abis

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

2-145

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.23 HO performed ack timer (TwaitHoPFMAck)


Full Name HO performed ack timer

Abbreviation TwaitHoPFMAck

3GPP Name None

3GPP Reference None

When IP bearer is adopted on the user plane at the A interface, the BSC
needs to notify the CN to change its vocoder in an intra-BSC handover
process because TC is located in the MGW. The vocoder change in
the CN is triggered by a HANDOVER PERFORMED message. A
HANDOVER PERFORMED ACK message is required to ensure that
the MSC has successfully received the HANDOVER PERFORMED
message and required the MGW to change the vocoder and thus
avoid voice problems. This parameter is a timer used to wait for the
HANDOVER PERFORMED ACK message from the MSC.
Start: When the BSC sends a HANDOVER PERFORMED message
to the MSC.
Stop: The BSC receives a HANDOVER PERFORMED ACK message
from the MSC.
At expiry: Send a CLEAR REQUEST message to the MSC to release
the call. The cause value is 0x60, indicating a protocol error between the
Description BSC and the MSC.

Managed Object BSC

50..70
Value Range and Step Step: 1

Unit 100 ms

Default Value 60

Default Value Six seconds are enough for signalling transfer and the processing in
Configuration Reason the MSC.

Configuration Rule and


Adjustment Suggestion Generally, the default value is recommended.

Change Mode Offline

Related features ZGO-05-02-001 Remote Transcoder Support

2-146

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Related Parameters None

Relationship None

Related Interfaces A

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.24 Timer of TRAU frame Synchronization (TuTrauSyn)


Full Name Timer of TRAU frame Synchronization

Abbreviation TuTrauSyn

3GPP Name timer of TRAU frame synchronization

3GPP Reference 3GPP TS 48.060, 3GPP TS 48.061

This parameter is a timer indicating the loss of TRAU frame


synchronization. If the function of call release upon the loss of TRAU
frame synchronization is supported, the call will be released upon the
expiry of the timer.
Start: The MS is allocated a TCH.
Stop: The DSP detects that TRAU frame (voice frame) has been
synchronized.
At expiry: Release the call.
Description Associated timer: None

Managed Object BSC

10..600
Value Range and Step Step: 1

Unit 100 ms

Default Value 10

Generally, one second (corresponding to the default value 10) is enough


Default Value
for the MS to detect the media data of the TRAU frame after a TCH
Configuration Reason
is allocated to it.

2-147

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Generally, the default value is recommended. Increase the value of


this parameter appropriately and observe whether the rate of call drops
Configuration Rule and
caused by the detection of TRAU frames is reduced. If yes, set a larger
Adjustment Suggestion
value to the parameter until the call drop rate caused by TRAU frames
does not change greatly.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Abis

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.25 Round trip delay (RtdDefault)


Full Name Round trip delay

Abbreviation RtdDefault

3GPP Name Round Trip Delay

3GPP Reference 48.058

This parameter specifies the Round Trip Delay (RTD). In a handover


process when AMR voice encoding is adopted, the BSC sends a
PRE-HANDOVER NOTIFICATION message to the BTS. During the
RTD, the BTS negotiates with the TC to take some actions, such as
disable the voice rate adjustment and terminate TFO. After that, the BSC
sends a handover command to the MS. RTD is the transmission delay
caused by the round trip between the BTS and the TC. It is reported
by the BTS to the BSC through a ROUND TRIP DELAY REPORT
message. The BSC uses the default value of RTD (RtdDefault) before
receiving this message.
Start: The BSC sends a PRE-HANDOVER NOTIFICATION message
Description
to the BTS.

2-148

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Stop: The BSC receives a PRE-HANDOVER NOTIFICATION ACK


message (a user-defined message at the Abis interface) from the BTS.
At expiry: The BSC sends a handover command to the MS.

Managed Object BSC

1..20
Value Range and Step Step: 1

Unit 20 ms

Default Value 5

Default Value 100 ms is enough in consideration of the time needed for message
Configuration Reason transfer on the user plane between the BTS and the TC.

Generally, the default value is recommended. If the delay caused by


Configuration Rule and
message transfer on the user plane between the BTS and the TC is
Adjustment Suggestion
long, increase the parameter value appropriately.

Change Mode Offline

Related features ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)

Related Parameters None

Relationship None

Related Interfaces Abis

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.26 Timer to wait a relocation commit MSG from RNC


(TWaitRncRelocComm)
Full Name Timer to wait a relocation commit MSG from RNC

Abbreviation TWaitRncRelocComm

3GPP Name None

3GPP Reference None

2-149

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

This parameter specifies the time for the BSC to wait for a RELOACTION
COMMIT message from the RNC when the Iur-g interface configured
between 2G and 3G is used for relocation.
Start: A HandoverRequestAck message is sent to the MSC.
Stop: A RELOCATION COMMIT message is received from the RNC
at the Iur-g interface.
At expiry: Release the corresponding relocation instance and allocated
Description resources.

Managed Object BSC

0..200
Value Range and Step Step: 1

Unit 100 ms

Default Value 100

The default value is set in consideration of the maximum delay of the


Default Value
HandoverRequestAck message from the BSC to the MSC, and then
Configuration Reason
to the RNC.

Configuration Rule and The default value, already taking the message delay on site into
Adjustment Suggestion consideration, is recommended.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.27 Subcell PingPong handover timer (TSCPingPang)


Full Name Subcell PingPong handover timer

Abbreviation TSCPingPang

2-150

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

3GPP Name None

3GPP Reference None

This parameter indicates a time period after a subcell handover, in which


the MS is handed over between subcells frequently, for example, the MS is
handed over back and forth between two subcells within the same BSC, or
the MS is handed over back and forth between two subcells between two
BSCs. The fast inter-subcell handovers are counted in the performance
Description report.

Managed Object BSC

20..1000
Value Range and Step Step: 1

Unit 100 ms

Default Value 100

The default value is set based on a common radio environment.


Default Value
Generally, it is deemed that a ping-pong handover occurs if handover
Configuration Reason
occurs frequently between two subcells in 10 seconds.

The smaller the parameter value is, the less restrictive the criterion for
ping-pong handover is. Similarly, the larger the parameter is, the more
Configuration Rule and
restrictive the criterion for ping-pong handover is. This parameter can
Adjustment Suggestion
be used to evaluate whether inter-subcell handover parameters are
properly set.

Change Mode Offline

Related features ZGO-04-02-005 Co-BCCH

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-151

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

2.6.28 Confirm BIPB fault time (TConfBIPBFault)


Full Name Confirm BIPB fault time

Abbreviation TConfBIPBFault

3GPP Name None

3GPP Reference None

This parameter is a timer used to confirm that a BIPB failure occurs. The
timer is started when a BIPB failure occurs. Upon the expiry of the timer,
Description all DSPs of the BIPB board are switched to the standby ones.

Managed Object BSC

30..1200
Value Range and Step Step: 1

Unit 100 ms

Default Value 950

Default Value Generally, the restart of the BIPB board can be completed within 95
Configuration Reason seconds, which avoids the active/standby switchover.

The smaller the parameter value is, the shorter the service interruption
Configuration Rule and time is. If all sites in the system are IP-based sites, decrease the
Adjustment Suggestion parameter value appropriately to reduce the service interruption time. If
all sites are E1-based sites, the default value is recommended.

Change Mode Offline

Related features None

Related Parameters [BSC]TConfBIPBDSPFault

Relationship TConfBIPBDSPFault < TConfBIPBFault

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-152

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

2.6.29 Confirm BIPB DSP fault time (TConfBIPBDSPFault)


Full Name Confirm BIPB DSP fault time

Abbreviation TConfBIPBDSPFault

3GPP Name None

3GPP Reference None

This parameter is a timer used to confirm that a BIPB DSP failure occurs.
The timer is started when a BIPB DSP failure occurs. Upon the expiry of
Description the timer, the BIPB board switches the failed DSP to the standby one.

Managed Object BSC

5..600
Value Range and Step Step: 1

Unit 100 ms

Default Value 100

Default Value Generally, the BIPB DSP can be reset in 10 seconds, which avoids the
Configuration Reason active/standby switchover.

Configuration Rule and You can adjust the parameter value according to the actual situation after
Adjustment Suggestion measuring the time needed for DSP restoration after the DSP is reset.

Change Mode Offline

Related features None

Related Parameters [BSC]TConfBIPBFault

Relationship TConfBIPBDSPFault < TConfBIPBFault

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.30 Confirm LAPD fault time (TConfLapdFault)


Full Name Confirm LAPD fault time

2-153

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Abbreviation TConfLapdFault

3GPP Name None

3GPP Reference None

This parameter is a timer used to confirm that an LAPD failure occurs.


The timer is started when a LAPD failure occurs. Upon the expiry of the
Description timer, all CPUs of the LAPD board are switched to the standby ones.

Managed Object BSC

30..1200
Value Range and Step Step: 1

Unit 100 ms

Default Value 950

Default Value Generally, the restart of the LAPD board can be completed within 95
Configuration Reason seconds, which avoids the active/standby switchover.

The minimum value can be used according to the actual situation


Configuration Rule and
because 1+1 backup is adopted for the LAPD board to support the
Adjustment Suggestion
immediate active/standby switchover.

Change Mode Offline

Related features None

Related Parameters [BSC]TConfLapdCpuFault

Relationship TConfLapdCpuFault < TConfLapdFault

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.31 Confirm LAPD CPU fault time (TConfLapdCpuFault)


Full Name Confirm LAPD CPU fault time

Abbreviation TConfLapdCpuFault

2-154

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

3GPP Name None

3GPP Reference None

This parameter is a timer used to confirm that an LAPD CPU failure oc-
curs. The timer is started when a LAPD CPU failure occurs. Upon the ex-
piry of the timer, the LAPD board switches the failed CPU to the standby
one. In the case of CPU1 failure, all CPUs of the LAPD board need to be
switched to the standby ones. In the case of non-CPU1 failure, only the
Description failed CPU needs to be switched to the standby one.

Managed Object BSC

5..600
Value Range and Step Step: 1

Unit 100 ms

Default Value 50

Default Value A delay of five seconds is used to make sure that the LAPD CPU failure
Configuration Reason is not transient.

The minimum value can be used according to the actual situation


Configuration Rule and
because 1+1 backup is adopted for the LAPD board to support the
Adjustment Suggestion
immediate active/standby switchover.

Change Mode Offline

Related features None

Related Parameters [BSC]TConfLapdFault

Relationship TConfLapdCpuFault < TConfLapdFault

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.32 Confirm Sunit normal time (TConfSunitNor)


Full Name Confirm Sunit normal time

2-155

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Abbreviation TConfSunitNor

3GPP Name None

3GPP Reference None

This parameter is a timer used to determine whether IPRB DSP, BIPB


DSP, or LAPD CPU restores from a failure. The timer is started when
IPRB DSP, BIPB DSP, or LAPD CPU restores. Upon the expiry of the
timer, the system searches for failed board(s). If a failed board is found,
Description the system switches the board to the standby one.

Managed Object BSC

5..300
Value Range and Step Step: 1

Unit 100 ms

Default Value 100

Default Value
Configuration Reason 10 seconds are enough to confirm that the unit restores from a failure.

Configuration Rule and A value close to the default value can be used. A great modification is
Adjustment Suggestion not recommended.

Change Mode Offline

Related features None

Related Parameters [BSC]TconfBIPBFault


[BSC]TconfLapdFault

The parameter must be smaller than TconfBIPBFault and


Relationship
TconfLapdFault.

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.6.33 Paging Interval (PagWaitTime)


Full Name Paging Interval

2-156

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Abbreviation PagWaitTime

3GPP Name None

3GPP Reference None

This parameter determines the time of the BSC in waiting for a paging
response after sending a paging message. The paging mode includes
exact paging and common paging. If the BSC does not receive any re-
sponse within this time range, the BSC will initiate the paging operation
Description again according to the parameter configuration.

Managed Object Cell

Value Range and Step 20..80

Unit 100ms

Default Value 25

Default Value
Configuration Reason A paging response from the MS can be received within 2.5s.

Configuration Rule and It is required to configure this parameter by considering the configuration
Adjustment Suggestion of paging module and the transmission delay of Abit interface.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version iBSCV6.20.710

Parameter Modifying
Detail New

2.6.34 Time of Cobcch Wait for MR Report (TCobcchWaitMR)


Full Name Time of Cobcch Wait for MR Report

Abbreviation TCobcchWaitMR

3GPP Name Null

2-157

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

3GPP Reference Null

The parameter indicates the duration of waiting for MR report when


Description Cobcch assignment is performed.

Managed Object BSC

[0..30]
Value Range and Step step: 1

Unit 100ms

Default Value 0

Default Value
Configuration Reason Null

Configuration Rule and


Adjustment Suggestion Null

Change Mode Offline

Related features Null

Related Parameters Null

Relationship Null

Related Interfaces Null

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config


OMC Access Path
Set ID->BSC Function ID->Timer2

Parameter Modifying
Version iBSCV6.20.711b

Parameter Modifying
Detail New

2.6.35 SDCCH Channel release period (TSDRelPeriod)


Full Name SDCCH Channel release period

Abbreviation TSDRelPeriod

3GPP Name None

3GPP Reference None

Description This parameter specifies the release period of the SDCCH.

Managed Object BSC

2-158

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

0..1000
Value Range and Step Step: 1

Unit 100ms

Default Value 50

Default Value The SDCCH release period is consistent with the default value of the
Configuration Reason TCH.

Configuration Rule and The time for the abnormal release of the SDDCH can be reduced as
Adjustment Suggestion required by test.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork->BSC Managed Element->Config SetBSC


OMC Access Path
Function->Timer2

Parameter Modifying
Version iBSCV6.20.712b

Parameter Modifying
Detail New

2.6.36 SDCCH Channel deactivation delay (TSDDeactDelay)


Full Name SDCCH Channel deactivation delay

Abbreviation TSDDeactDelay

3GPP Name None

3GPP Reference None

Description This parameter specifies the deactivation delay of SDCCH .

Managed Object BSC

1..300
Value Range and Step Step: 1

Unit 100ms

2-159

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Default Value 3

Default Value The SDCCH release period is consistent with the default value of the
Configuration Reason TCH.

Configuration Rule and The parameter is a release protection delay, and a value less than
Adjustment Suggestion 1 second is enough.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork->BSC Managed Element->Config SetBSC


OMC Access Path
Function->Timer2

Parameter Modifying
Version iBSCV6.20.712b

Parameter Modifying
Detail New

2.7 GPRS Maximum Retrying Times


2.7.1 Max times of BVC block retry (BVCBlkMax)
Full Name Max times of BVC block retry

Abbreviation BVCBlkMax

3GPP Name BVC-BLOCK-RETRIES

3GPP Reference TS48.018: "BSS GPRS Protocol (BSSGP)"

2-160

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

When blocking a PTP BVC is required due to OAM intervene or device


failure, the BSS sets the status of the BVC to "Blocked" and then
discards uplink service data. It is not allowed to block or unblock a
signalling BVC.
To notify SGSN to stop sending downlink data, BSS initiates BVC
blocking process. After sending a "BVC BLOCK" message to the SGSN,
the BSS restarts the "BVC BLOCK" process if it fails to receive a "BVC
BLOCK ACK" message from the SGSN within BSSGP T1.
If no response is received from the SGSN after the BSS sends the "BVC
BLOCK" message for N times, the BSC stops sending the "BVC BLOCK"
message and informs the OMS about the failure. This parameter value,
Description N, indicates the maximum number of BVC BLOCK attempts.

Managed Object BSC

3..10
Value Range and Step Step: 1

Unit None

Default Value 3

Default Value
Configuration Reason The default value is recommended by the protocol.

Set the parameter in consideration of the default value, the link stability
Configuration Rule and
at Gb interface, and the round trip delay at Gb interface. The default
Adjustment Suggestion
value is recommended when Gb interface is normal.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS maximum Retrying Times

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-161

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

2.7.2 Max times of BVC unblock retry (BVCUblkMax)


Full Name Max times of BVC unblock retry

Abbreviation BVCUblkMax

3GPP Name BVC-UNBLOCK-RETRIES

3GPP Reference TS48.018: "BSS GPRS Protocol (BSSGP)"

When unblocking a PTP BVC is required due to OAM intervene or the


removal of a device failure, the BSS sets the status of the BVC to
"Unblocked". It is not allowed to block or unblock a signalling BVC.
To notify the SGSN to stop sending downlink data, the BSS initiates
a BVC blocking process. After sending a "BVC UNBLOCK" message
to the SGSN, the BSS restarts the "BVC UNBLOCK" process if it fails
to receive a "BVC UNBLOCK ACK" message from the SGSN within
BSSGP T1.
If no response is received from the SGSN after the BSS sends the "BVC
UNBLOCK" message for N times, the BSC stops sending the "BVC
UNBLOCK" message and informs the OMS about the failure. This
parameter value, N, indicates the maximum number of BVC UNBLOCK
Description attempts.

Managed Object BSC

3..10
Value Range and Step Step: 1

Unit None

Default Value 3

Default Value
Configuration Reason The default value is recommended by the protocol.

Set the parameter in consideration of the default value, the link stability
Configuration Rule and
at Gb interface, and the round trip delay at Gb interface. The default
Adjustment Suggestion
value is recommended when Gb interface is normal.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

2-162

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS maximum Retrying Times

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.7.3 MAX times of BVC reset retry (BVCRestMax)


Full Name MAX times of BVC reset retry

Abbreviation BVCRestMax

3GPP Name BVC-RESET-RETRIES

3GPP Reference TS48.018: "BSS GPRS Protocol (BSSGP)"

To ensure the BVC status at both sides (BSS and SGSN) is the same, a
"BVC RESET" process must be initiated in one of the following cases:
1) a system failure affecting BVC function in the BSS or SGSN, for
example, a restart upon power-on; 2) a network service entity failure on
the lower layer, for example, a frame relay failure; 3) a capability update
of a network service entity on the lower layer, for example, a change of
frame relay capability from 0kbps to greater than 0kbps; 4) a change of
relation between BVC and a cell.
A "Signalling BVC RESET" process shall be initiated in the occurrence of
a failure impacting NSE. A "PTP BVC RESET" process shall be initiated
in the occurrence of a failure impacting only one BVC. After a "Signalling
BVC RESET" process is successfully completed, a "PTP BVC RESET"
process must be initiated for all BVCs of the NSE.
After sending a "BVC RESET" message to the SGSN, the BSS restarts
the "BVC RESET" process if it fails to receive a "BVC RESET ACK"
message from the SGSN within BSSGP T2.
If no response is received from the SGSN after the BSS sends the "BVC
RESET" message for N times, the BSC stops sending the "BVC RESET"
message and informs the OMS about the failure. This parameter value,
N, indicates the maximum number of BVC RESET attempts.
Description This parameter is changed in V6.20.614a.

Managed Object BSC

0..255
Value Range and Step Step: 1

Unit None

Default Value 6

2-163

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Default Value
Configuration Reason The default value is recommended by the protocol.

Set the parameter in consideration of the default value, the link stability
Configuration Rule and
at Gb interface, and the round trip delay at Gb interface. The default
Adjustment Suggestion
value is recommended when Gb interface is normal.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS maximum Retrying Times

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.7.4 Max times of NS block retry (NSBlkMax)


Full Name Max times of NS block retry

Abbreviation NSBlkMax

3GPP Name NS-BLOCK-RETRIES

3GPP Reference TS48.016: "Network Service"

After the BSC sends an "NS BLOCK" message to the SGSN, the "NS
BLOCK" process is initiated again if the BSC does not receive an "NS
BLOCK ACKNOWLEDGE" message from the SGSN within the time
specified by NS_T1.
If no response is received from the SGSN after the BSC sends the "NS
BLOCK" message for N times, the BSC terminates the "NS BLOCK"
process and informs the OMS about the failure. This parameter value,
Description N, indicates the maximum number of NS BLOCK attempts.

Managed Object BSC

0..10
Value Range and Step Step: 1

2-164

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Unit None

Default Value 3

Default Value
Configuration Reason The default value is recommended by the protocol.

Set the parameter in consideration of the default value, the link stability
Configuration Rule and
at Gb interface, and the round trip delay at Gb interface. The default
Adjustment Suggestion
value is recommended when Gb interface is normal.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS maximum Retrying Times

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.7.5 Max times of NS unblock retry (NSUnblkMax)


Full Name Max times of NS unblock retry

Abbreviation NSUnblkMax

3GPP Name NS-UNBLOCK-RETRIES

3GPP Reference TS48.016: "Network Service"

After the BSC sends an "NS UNBLOCK" message to the SGSN, the "NS
UNBLOCK" process is initiated again if the BSC does not receive an
"NS UNBLOCK ACKNOWLEDGE" message from the SGSN within the
time specified by NS_T1.
If no response is received from the SGSN after the BSC sends the "NS
BLOCK" message for N times, the BSC terminates the "NS BLOCK"
process and informs the OMS about the failure. This parameter value,
Description N, indicates the maximum number of NS BLOCK attempts.

2-165

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Managed Object BSC

0..10
Value Range and Step Step: 1

Unit None

Default Value 3

Default Value
Configuration Reason The default value is recommended by the protocol.

Set the parameter in consideration of the default value, the link stability
Configuration Rule and
at Gb interface, and the round trip delay at Gb interface. The default
Adjustment Suggestion
value is recommended when Gb interface is normal.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS maximum Retrying Times

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.7.6 Max times of NS alive retry (NSAliveMax)


Full Name Max times of NS alive retry

Abbreviation NSAliveMax

3GPP Name NS-ALIVE-RETRIES

3GPP Reference TS48.016: "Network Service"

2-166

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

After the BSC sends an "NS Alive" message to the SGSN, the "NS
Alive" process is initiated again if the BSC does not receive an "NS
Alive ACKNOWLEDGE" message from the SGSN before the timeout
of NS_T4. The "NS Alive" process, being specified by the protocol, is
intended to test the connection between two ends of NSVC.
If no response is received from the SGSN after the BSC sends the
"NS Alive" message for N times, the BSC terminates the "NS Alive"
process and informs the OMS about the failure. This parameter value,
Description N, indicates the maximum number of NS Alive attempts.

Managed Object BSC

0..20
Value Range and Step Step: 1

Unit None

Default Value 10

Default Value
Configuration Reason The default value is recommended by the protocol.

Set the parameter in consideration of the default value, the link stability
Configuration Rule and
at Gb interface, and the round trip delay at Gb interface. The default
Adjustment Suggestion
value is recommended when Gb interface is normal.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS maximum Retrying Times

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.7.7 Max times of suspend retry (SuspendMax)


Full Name Max times of suspend retry

2-167

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Abbreviation SuspendMax

3GPP Name SUSPEND-RETRIES

3GPP Reference TS48.018: "BSS GPRS Protocol (BSSGP)"

When originating a voice service, the MS supporting Class B GPRS


sends a "SUSPEND" message to the BSS over SDCCH. Upon receiving
the "SUSPEND" message, the BSS initiates a "SUSPEND" process to
notify the SGSN to stop sending "PS Paging" and "Downlink Packet
Data".
After sending a "SUSPEND" message to the SGSN, the BSS restarts the
"SUSPEND" process if it fails to receive a "SUSPEND ACK" message
from the SGSN within BSSGP T3.
If no response is received from the SGSN after the BSS sends the
"SUSPEND" message for N times, the BSC terminates the "SUSPEND"
process and informs the OMS about the failure. This parameter value,
Description N, indicates the maximum number of SUSPEND attempts.

Managed Object BSC

0..10
Value Range and Step Step: 1

Unit None

Default Value 3

Default Value
Configuration Reason The default value is recommended by the protocol.

Set the parameter in consideration of the default value, the link stability
Configuration Rule and
at Gb interface, and the round trip delay at Gb interface. The default
Adjustment Suggestion
value is recommended when Gb interface is normal.

Change Mode Offline

Related features None

Related Parameters [BSC]ResumeSetOpt

This parameter is only valid when the switch of SUSPEND/RESUME


Relationship
process is enabled.

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS maximum Retrying Times

2-168

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.7.8 Max times of resume retry (ResumeMax)


Full Name Max times of resume retry

Abbreviation ResumeMax

3GPP Name RESUME-RETRIES

3GPP Reference TS48.018: "BSS GPRS Protocol (BSSGP)"

This parameter is a BSSGP-layer parameter. When a GPRS-attached


MS leaves the dedicated mode, the BSS can adopt one of the following
policies:
Notify the MS to update the routing area.
Notify the SGSN to resume the GPRS service support.
When the "Routing Area Update" policy is adopted, the MS negotiates
with the SGSN directly about "GMM Status". If the "RESUME" policy is
adopted, which is generally used for MS in packet transmission state,
the BSS initiates a "RESUME" process to notify the SGSN to start the
transport of downlink packets. After sending a "RESUME" message to
the SGSN, the "RESUME" process is initiated again if no "RESUME
ACK" or "RESUME NACK" message is received from the SGSN within
BSSGP T4.
If no response is received from the SGSN after the BSS sends the
"RESUME" message for N times, the BSC terminates the "RESUME"
process and informs the OMS about the failure. This parameter value,
Description N, indicates the maximum number of RESUME attempts.

Managed Object BSC

0..10
Value Range and Step Step: 1

Unit None

Default Value 3

Default Value
Configuration Reason The default value is recommended by the protocol.

Set the parameter in consideration of the default value, the link stability
Configuration Rule and
at Gb interface, and the round trip delay at Gb interface. The default
Adjustment Suggestion
value is recommended when Gb interface is normal.

Change Mode Offline

2-169

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Related features None

Related Parameters [BSC]ResumeSetOpt

This parameter is only valid when the switch of SUSPEND/RESUME


Relationship
process is enabled.

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS maximum Retrying Times

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.7.9 Max times of radio access capabilities update retry


(UpdateMax)
Full Name Max times of radio access capabilities update retry

Abbreviation UpdateMax

3GPP Name RA-CAPABILITY-UPDATE-RETRIES

3GPP Reference TS48.018: "BSS GPRS Protocol (BSSGP)"

This parameter is a BSSGP-layer parameter. When an MS sets up


uplink and downlink TBF, the BSS needs to know the "Radio Access
Capability" of the MS for allocating an appropriate packet channel to it.
If the BSS does not get this information (for example, in the case of
one-step access), a "Radio Access Capability Update" process can be
initiated to get the radio access capability of the MS from the SGSN.
After sending a "Radio Access Capability Update" message to the
SGSN, the "Radio Access Capability Update" process is initiated again if
no "Radio Access Capability Update ACK" or "Radio Access Capability
Update NACK" message is received from the SGSN within BSSGP
T5. "If no response is received from the SGSN after the BSS sends
the "Radio Access Capability Update" message for N times, the BSC
terminates the "Radio Access Capability Update" process and informs
the OMS about the failure. This parameter value, N, indicates the
Description maximum number of Radio Access Capability Update attempts.

2-170

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Managed Object BSC

0..10
Value Range and Step Step: 1

Unit None

Default Value 3

Default Value
Configuration Reason The default value is recommended by the protocol.

Set the parameter in consideration of the default value, the link stability
Configuration Rule and
at Gb interface, and the round trip delay at Gb interface. The default
Adjustment Suggestion
value is recommended when Gb interface is normal.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS maximum Retrying Times

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.7.10 Max times of PFC create retry (DownLoadBssPFCMax)


Full Name Max times of PFC create retry

Abbreviation DownLoadBssPFCMax

3GPP Name DOWNLOAD-BSS-PFC-RETRIES

3GPP Reference TS48.018: "BSS GPRS Protocol (BSSGP)"

2-171

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

This parameter indicates the maximum number of Create PFC attempts.


If the Create BSS PFC message is not received before the timeout of
timer BSSGPT6, the BSS sends the Download BSS PFC message again.
If the BSS does not receive the Create BSS PFC message after sending
the Download BSS PFC message for DownloadBSSPRCMax+1 times, it
terminates the Create BSS PFC process and informs the O&M about this
Description failure.

Managed Object BSC

0..10
Value Range and Step Step: 1

Unit None

Default Value 3

Default Value
Configuration Reason The default value is recommended by the protocol.

Set the parameter in consideration of the default value, the link stability
Configuration Rule and
at Gb interface, and the round trip delay at Gb interface. The default
Adjustment Suggestion
value is recommended when Gb interface is normal.

Change Mode Offline

ZGO-01-02-004 Streaming Service Policies


ZGO-01-02-003 Service based QoS
Related features ZGB-01-02-001 Quality of Service (QoS)

Related Parameters [BSC]PFCSupport

This parameter is only valid when the switch of PFC process is enabled
Relationship
in the BSC.

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS maximum Retrying Times

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-172

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

2.7.11 Max times of PFC modify retry (ModifyBssPFCMax)


Full Name Max times of PFC modify retry

Abbreviation ModifyBssPFCMax

3GPP Name MODIFY-BSS-PFC-RETRIES

3GPP Reference TS48.018: "BSS GPRS Protocol (BSSGP)"

This parameter indicates the maximum number of Modify BSS PFC at-
tempts. If the Modify BSS PFC Ack message is not received before the
timeout of timer BSSGPT8, the BSS sends the Modify BSS PFC message
again. If the BSS does not receive the Modify BSS PFC Ack message
after sending the Modify BSS PFC message for ModifyBssPFCMax+1
times, it terminates the Modify BSS PFC process and informs the O&M
Description about this failure.

Managed Object BSC

0..10
Value Range and Step Step: 1

Unit None

Default Value 3

Default Value
Configuration Reason The default value is recommended by the protocol.

Set the parameter in consideration of the default value, the link stability
Configuration Rule and
at Gb interface, and the round trip delay at Gb interface. The default
Adjustment Suggestion
value is recommended when Gb interface is normal.

Change Mode Offline

ZGO-01-02-004 Streaming Service Policies


ZGO-01-02-003 Service based QoS
Related features ZGB-01-02-001 Quality of Service (QoS)

Related Parameters [BSC]PFCSupport

This parameter is only valid when the switch of PFC process is enabled
Relationship
in the BSC.

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS maximum Retrying Times

Parameter Modifying
Version None

2-173

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Parameter Modifying
Detail None

2.7.12 Max of sending PS handover required (PSHoReqMaxNum)


Full Name Max of sending PS handover required

Abbreviation PSHoReqMaxNum

3GPP Name Internal

3GPP Reference None

This parameter indicates the maximum number of times that the PS


HANDOVER REQUIRED message is sent during PS handover. The PS
HANDOVER REQUIRED message is sent again upon the expiry of timer
Description T12PsHo.

Managed Object BSC

1..6
Value Range and Step Step: 1

Unit Time

Default Value 2

Default Value The default value is an experimental value obtained during the
Configuration Reason interaction of processes between network elements.

Configuration Rule and The default value is recommended. The parameters relevant to PS
Adjustment Suggestion handover, including this parameter, are not in commercial use currently.

Change Mode Offline

Related features ZGO-02-02-016 PS Handover

Related Parameters None

Relationship None

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS maximum Retrying Times

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-174

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

2.8 GPRS Timer


2.8.1 BVC block/unblock retry time (BssgpT1)
Full Name BVC block/unblock retry time

Abbreviation BssgpT1

3GPP Name T1

3GPP Reference TS48.018: "BSS GPRS Protocol (BSSGP)"

This parameter is a timer used to supervise the BSSGP block/unblock


process.
The BSS initiates a BVC BLOCK/UNBLOCK process when it is
required to block or unblock a point-to-point BVC due to OAM
intervene or equipment failure. If the SGSN does not return a BVC
BLOCK/UNBLOCK ACK message, the BVC BLOCK/UNBLOCK process
is repeated, and the number of times that the BVC BLOCK/UNBLOCK
message is sent increases by one. The interval between two BVC
BLOCK/UNBLOCK processes is defined as BVC BLOCK/UNBLOCK
RETRY TIME. The BSS tries to send the BVC BLOCK/UNBLOCK
message again when T1 expires but the number of retry times does
not exceed the maximum number of allowable retries. The BVC
block/unblock request is neglected if the number of retry times exceeds
the maximum one when T1 expires.
The following describes when the timer is started and stopped, as well
as the action at expiry of the timer.
Start: The BSC initiates a BVC BLOCK/UNBLOCK process.
Stop: A BVC BLOCK/UNBLOCK ACK/NACK message is received from
the SGSN.
At expiry: The BSC sends the SUSPEND SGSN message for N times.
N, the maximum number of times that the SUSPEND SGSN message
Description can be sent, can be set.

Managed Object BSC

10..300
Value Range and Step Step: 1

Unit 100 ms

Default Value 30

Default Value The default value is set according to the range specified by the protocol
Configuration Reason and the round trip delay at the Gb interface.

Set the parameter in consideration of the default value, the link stability
Configuration Rule and
at Gb interface, and the round trip delay at Gb interface. The default
Adjustment Suggestion
value is recommended when Gb interface is normal.

2-175

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Timer

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.8.2 BVC reset retry time (BssgpT2)


Full Name BVC reset retry time

Abbreviation BssgpT2

3GPP Name T2

3GPP Reference TS48.018: "BSS GPRS Protocol (BSSGP)"

This parameter is a timer used to supervise the BSSGP reset process.


The BSS initiates a BVC RESET process when a BVC (PTP BVC or
signalling BVC) needs to be reset due to some reasons, for example,
the connection to the Gb interface resumes, the GPRS or EDGE support
of a cell is enabled, or a reset command sent by the OMCR. If the SGSN
does not return a BVC RESET ACK message, the BVC RESET process
is repeated, and the number of times that the BVC RESET message is
sent increases by one. The interval between two BVC RESET processes
is defined as BVC RESET RETRY TIME. The BSS tries to send the BVC
RESET message again when T2 expires but the number of retry times
does not exceed the maximum number of allowable retries. The BSS
set the status of the BVC BLOCK in the database when T2 expires and
the number of times that the BVC RESET message is sent exceeds the
maximum number.
The following describes when the timer is started and stopped, as well
as the action at expiry of the timer.
Description Start: The BSC initiates a BVC RESET process.

2-176

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Stop: A BVC RESET ACK/NACK message is received from the SGSN.


At expiry: The BSC sends the BVC RESET message for N times. N,
the maximum number of times that the BVC RESET message can be
sent, can be set.
This parameter is changed in V6.20.614a.

Managed Object BSC

10..1200
Value Range and Step Step: 1

Unit 100 ms

Default Value 150

Default Value The default value is set according to the range specified by the protocol
Configuration Reason and the round trip delay at the Gb interface.

Set the parameter in consideration of the default value, the link stability
Configuration Rule and
at Gb interface, and the round trip delay at Gb interface. The default
Adjustment Suggestion
value is recommended when Gb interface is normal.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Timer

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.8.3 Suspend retry time (BssgpT3)


Full Name Suspend retry time

Abbreviation BssgpT3

3GPP Name T3

3GPP Reference TS48.018: "BSS GPRS Protocol (BSSGP)"

2-177

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

The Class-B MS shall notify the network to suspend the packet service
when it is going to start a voice service. Upon receiving the SUSPEND
message from the MS, the BSS initiates a SUSPEND SGSN process.
If the SGSN does not return a SUSPEND ACK/NACK message, the
SUSPEND SGSN process is repeated, and the number of times that
the SUSPEND SGSN message is sent increases by one. The interval
between two SUSPEND SGSN processes is defined as SUSPEND
RETRY TIME. The BSS tries to send the SUSPEND SGSN message
again when T3 expires but the number of times that the message is
sent does not exceed the maximum number. The BSS terminates the
SUSPEND SGSN process when T3 expires and the number of times that
the SUSPEND SGSN message is sent exceeds the maximum number.
The following describes when the timer is started and stopped, as well
as the action at expiry of the timer.
Start: The BSC initiates a SUSPEND SGSN process.
Stop: A SUSPEND ACK/NACK message is received from the SGSN.
At expiry: The BSC sends the SUSPEND SGSN message for N times.
N, the maximum number of times that the SUSPEND SGSN message
Description can be sent, can be set.

Managed Object BSC

1..100
Value Range and Step Step: 1

Unit 100 ms

Default Value 30

Default Value The default value is set according to the range specified by the protocol
Configuration Reason and the round trip delay at the Gb interface.

Set the parameter in consideration of the default value, the link stability
Configuration Rule and
at Gb interface, and the round trip delay at Gb interface. The default
Adjustment Suggestion
value is recommended when Gb interface is normal.

Change Mode Offline

Related features None

Related Parameters [BSC]ResumeSetOpt

This parameter is only valid when the switch of SUSPEND/RESUME


Relationship
process is enabled.

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

2-178

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Timer

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.8.4 Resume retry time (BssgpT4)


Full Name Resume retry time

Abbreviation BssgpT4

3GPP Name T4

3GPP Reference TS48.018: "BSS GPRS Protocol (BSSGP)"

This parameter is a timer used to supervise the BSSGP RESUME


process.
The BSS, which adopts the policy of "Notify SGSN to Resume
GPRS Service", initiates a RESUME process to the SGSN when the
GPRS-attached MS leaves the dedicated mode. If the SGSN does
not return a RESUME ACK/NACK message, the RESUME process
is repeated, and the number of times that the RESUME message is
sent increases by one. The interval between two RESUME processes
is defined as RESUME RETRY TIME. The BSS tries to send the
RESUME message again when T4 expires but the number of times
that the message is sent does not exceed the maximum number. The
BSS terminates the RESUME process and notifies the MS to initiate a
ROUTING AREA UPDATE process when T4 expires and the number of
times that the RESUME message is sent exceeds the maximum number.
The following describes when the timer is started and stopped, as well
as the action at expiry of the timer.
Start: The BSC initiates a RESUME process.
Stop: A RESUME ACK/NACK message is received from the SGSN.
At expiry: The BSC sends the MODIFY BSS PFC message for N times.
N, the maximum number of times that the MODIFY BSS PFC message
Description can be sent, can be set.

Managed Object BSC

1..100
Value Range and Step Step: 1

Unit 100 ms

Default Value 30

2-179

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Default Value The default value is set according to the range specified by the protocol
Configuration Reason and the round trip delay at the Gb interface.

Set the parameter in consideration of the default value, the link stability
Configuration Rule and
at Gb interface, and the round trip delay at Gb interface. The default
Adjustment Suggestion
value is recommended when Gb interface is normal.

Change Mode Offline

Related features None

Related Parameters [BSC]ResumeSetOpt

This parameter is only valid when the switch of SUSPEND/RESUME


Relationship
process is enabled.

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Timer

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.8.5 Access capability update retry time (BssgpT5)


Full Name Access capability update retry time

Abbreviation BssgpT5

3GPP Name T5

3GPP Reference TS48.018: "BSS GPRS Protocol (BSSGP)"

This parameter is a timer used to supervise the BSSGP RADIO ACCESS


CAPABILITY UPDATE process.
If no RADIO ACCESS CAPABILITY UPDATE ACK/NACK message is
received from the SGSN after the BSS initiates a RADIO ACCESS
CAPABILITY UPDATE process, the RADIO ACCESS CAPABILITY
UPDATE process shall be repeated. The interval between two processes
is defined as RADIO ACCESS CAPABILITY UPDATE RETRY TIME. The
BSS tries to send the RADIO ACCESS CAPABILITY UPDATE message
again when T5 expires but the number of times that the message is

Description sent does not exceed the maximum number. The BSS terminates the

2-180

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

RADIO ACCESS CAPABILITY UPDATE process when T5 expires and


the number of times that the RADIO ACCESS CAPABILITY UPDATE
message is sent exceeds the maximum number.
The following describes when the timer is started and stopped, as well
as the action at expiry of the timer.
Start: The BSC initiates a RADIO ACCESS CAPABILITY UPDATE
process.
Stop: A RADIO ACCESS CAPABILITY UPDATE ACK/NACK message
is received from the SGSN.
At expiry: The BSC sends the MODIFY BSS PFC message for N times.
N, the maximum number of times that the MODIFY BSS PFC message
can be sent, can be set.

Managed Object BSC

10..300
Value Range and Step Step: 1

Unit 100 ms

Default Value 30

Default Value The default value is set according to the range specified by the protocol
Configuration Reason and the round trip delay at the Gb interface.

Set the parameter in consideration of the default value, the link stability
Configuration Rule and
at Gb interface, and the round trip delay at Gb interface. The default
Adjustment Suggestion
value is recommended when Gb interface is normal.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Timer

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-181

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

2.8.6 PFC creating retry time (BssgpT6)


Full Name PFC creating retry time

Abbreviation BssgpT6

3GPP Name T6

3GPP Reference TS48.018: "BSS GPRS Protocol (BSSGP)"

This parameter indicates the retry time for creating PFC.


If no CREATE PFC ACK/NACK message is received from the SGSN
after the BSS initiates a CREATE PFC process, the CREATE PFC
process shall be repeated. The interval between two MODIFY PFC
processes is defined as PFC MODIFY RETRY TIME.
The following describes when the timer is started and stopped, as well
as the action at expiry of the timer.
Start: The BSC initiates a Download PFC process.
Stop: A SGSN CREATE PFC message is received.
At expiry: The BSC sends the MODIFY BSS PFC message for N times.
N, the maximum number of times that the MODIFY BSS PFC message
Description can be sent, can be set.

Managed Object BSC

1..100
Value Range and Step Step: 1

Unit 100 ms

Default Value 30

Default Value The default value is set according to the range specified by the protocol
Configuration Reason and the round trip delay at the Gb interface.

Set the parameter in consideration of the default value, the link stability
Configuration Rule and
at Gb interface, and the round trip delay at Gb interface. The default
Adjustment Suggestion
value is recommended when Gb interface is normal.

Change Mode Offline

Related features None

Related Parameters [BSC]PFCSupport

This parameter is only valid when the switch of PFC process is enabled
Relationship
in the BSC.

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

2-182

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Timer

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.8.7 PFC modifying retry time (BssgpT8)


Full Name PFC modifying retry time

Abbreviation BssgpT8

3GPP Name T8

3GPP Reference TS48.018: "BSS GPRS Protocol (BSSGP)"

If no MODIFY PFC ACK/NACK message is received from the SGSN


after the BSS initiates a MODIFY PFC process, the MODIFY PFC
process shall be repeated. The interval between two MODIFY PFC
processes is defined as PFC MODIFY RETRY TIME.
The following describes when the timer is started and stopped, as well
as the action at expiry of the timer.
Start: The BSC initiates a MODIFY BSS PFC process.
Stop: A SGSN MODIFY BSS PFC ACK message is received.
At expiry: The BSC sends the MODIFY BSS PFC message for N times.
N, the maximum number of times that the MODIFY BSS PFC message
Description can be sent, can be set.

Managed Object BSC

1..100
Value Range and Step Step: 1

Unit 100 ms

Default Value 30

Default Value The default value is set according to the range specified by the protocol
Configuration Reason and the round trip delay at the Gb interface.

Set the parameter in consideration of the default value, the link stability
Configuration Rule and
at Gb interface, and the round trip delay at Gb interface. The default
Adjustment Suggestion
value is recommended when Gb interface is normal.

Change Mode Offline

ZGO-01-02-004 Streaming Service Policies


ZGO-01-02-003 Service based QoS
Related features ZGB-01-02-001 Quality of Service (QoS)

2-183

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Related Parameters [BSC]PFCSupport

This parameter is only valid when the switch of PFC process is enabled
Relationship
in the BSC.

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Timer

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.8.8 RIR Timer (TRIR)


Full Name RIR Timer

Abbreviation TRIR

3GPP Name T(RIR)

3GPP Reference 3GPP TS48.018 V6.6.0

This parameter is an expiration timer waiting for the response from the
opposite end after a RAN INFORMATION REQUEST message is sent by
the control end. The timer is started when the control end sends a RAN IN-
FORMATION REQUEST message. It is stopped when a response mes-
sage is received from the opposite end. If no response is received before
the expiration of the timer, the control end sends a RAN INFORMATION
REQUEST message again, or informs the process failure after sending
Description the message for RIMRetryTimes times.

Managed Object BSC

50..300
Value Range and Step Step: 1

Unit 100 ms

Default Value 50

Default Value
Configuration Reason The default value is an experimental value.

Configuration Rule and


Adjustment Suggestion The default value is recommended.

2-184

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Change Mode Offline

Related features ZGO-02-02-011 Inter-BSC NACC_FG_20101030

Related Parameters None

Relationship None

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Timer

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.8.9 RI Timer (TRI)


Full Name RI Timer

Abbreviation TRI

3GPP Name T(RI)

3GPP Reference 3GPP TS48.018 V6.6.0

This parameter is an expiration timer waiting for the response from the op-
posite end after the serving BSS sends a RAN INFORMATION message.
This timer is started when the serving BSS sends a RAN INFORMATION
message, in which the indicator requiring response from the opposite is
set. It is stopped when a response is received from the opposite end. If no
response is received before the expiration of the timer, the serving BSS
sends a RAN INFORMATION message again, or informs the process fail-
Description ure after sending the message for RIMRetryTimes times.

Managed Object BSC

50..300
Value Range and Step Step: 1

Unit 100 ms

Default Value 50

Default Value
Configuration Reason The default value is an experimental value.

2-185

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Configuration Rule and


Adjustment Suggestion The default value is recommended.

Change Mode Offline

Related features ZGO-02-02-011 Inter-BSC NACC_FG_20101030

Related Parameters None

Relationship None

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Timer

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.8.10 RIAE Timer (TRIAE)


Full Name RIAE Timer

Abbreviation TRIAE

3GPP Name T(RIAE)

3GPP Reference 3GPP TS48.018 V6.6.0

This parameter is an expiration timer waiting for the response from the
opposite end after a RAN INFORMATION APPLICATION ERROR mes-
sage is sent by the control end. The timer is started when the control
end sends a RAN INFORMATION APPLICATION ERROR message. It is
stopped when a response message is received from the opposite end. If
no response is received before the expiration of the timer, the control end
sends the RAN INFORMATION APPLICATION ERROR message again,
or informs the process failure after sending the message for the specified
Description times.

Managed Object BSC

50..300
Value Range and Step Step: 1

Unit 100 ms

2-186

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Default Value 50

Default Value
Configuration Reason The default value is an experimental value.

Configuration Rule and


Adjustment Suggestion The default value is recommended.

Change Mode Offline

Related features ZGO-02-02-011 Inter-BSC NACC_FG_20101030

Related Parameters None

Relationship None

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Timer

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.8.11 BVC flow control period (CellFcPer)


Full Name BVC flow control period

Abbreviation CellFcPer

3GPP Name None

3GPP Reference None

This parameter indicates the period for the statistics of BVC leak rate in
the BVC Flow Control process, that is, the period of long BVC statistics.
To provide a reference for the BVC flow control at the SGSN side,
the BSSGP process at the BSS side performs a periodic statistics on
current BVC leak rate. When the timer used for long statistics times
out, a BVC Flow Control process is initiated without condition. If the
difference between two statistical leak rates exceeds CellFcThs, an
acknowledgement from the SGSN is required before the BVC Flow
Control process is initiated. When the timer used for short statistics

Description times out, and the difference between two leak rates exceeds CellFcThs,

2-187

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

a BVC Flow Control process is initiated after an acknowledgement is


received from the SGSN.
The following describes when the timer is started and stopped, as well
as the action at expiry of the timer.
Start: When a cell is created.
Stop: When the cell is blocked or deleted.
At expiry: Initiate a BVC FLOW CONTROL process without condition.

Managed Object BSC

2..65535
Value Range and Step Step: 1

Unit 10 ms

Default Value 3000

Default Value
Configuration Reason It is recommended to set the default value to 1000.

The default value 1000 is recommended. A shorter period may increase


the load at the Gb interface. A longer period may cause the failure of
the BVC flow control.
Configuration Rule and A too large parameter value may result in a delay of flow control.
Adjustment Suggestion An improperly-set parameter value will cause intermittent download and
influence indexes relevant to throughput efficiency.
Set an appropriate period according to the settings of the SGSN. Make
sure that the parameter value is matching with the SGSN.

Change Mode Offline

Related features ZGB-03-05-016 Downlink BVC Flow Control

Related Parameters None

Relationship None

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Timer

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-188

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

2.8.12 MS flow control period (MsFcPer)


Full Name MS flow control period

Abbreviation MsFcPer

3GPP Name None

3GPP Reference None

This parameter indicates the period for the statistics of MS leak rate
in the MS Flow Control process.
To provide a reference for the flow control at the SGSN side, the BSSGP
process at the BSS side performs a periodic statistics on current leak
rate for each MS. When the timer times out, an MS Flow Control process
is initiated without condition.
The following describes when the timer is started and stopped, as well
as the action at expiry of the timer.
Start: When a downlink LLC frame is received in BSSGP idle state.
Stop: When the transmission of downlink LLC frames is completed.
Description At expiry: Initiate an MS FLOW CONTROL process without condition.

Managed Object BSC

2..65535
Value Range and Step Step: 1

Unit 10 ms

Default Value 3000

Default Value
Configuration Reason It is recommended to set the default value to 600.

The default value 600 is recommended. A shorter period may increase


Configuration Rule and
the load at the Gb interface. A longer period may cause the failure of
Adjustment Suggestion
the MS flow control.

Change Mode Offline

Related features ZGB-03-05-017 Downlink MS Flow Control

Related Parameters None

Relationship None

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Timer

2-189

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.8.13 Timer that monitors block/unblock procedure (NS_T1)


Full Name Timer that monitors block/unblock procedure

Abbreviation NS_T1

3GPP Name Tns-block

3GPP Reference 3GPP TS48.016 V5.4.0

This parameter is a timer used to supervise the NSVC block/unblock


process on the NS layer. The following describes when the timer is
started and stopped, as well as the action at expiry of the timer.
Start: When the BSC initiates an NS block/unblock process.
Stop: When a block/unblock acknowledgement message is received
from the SGSN.
At expiry: Initiate the NSVC block/unblock process for N times, and
restart the timer. (N depends on NS-BLICK-RETRIES specified by the
Description protocol).

Managed Object BSC

10..1200
Value Range and Step Step: 1

Unit 100 ms

Default Value 100

Default Value The default value is set according to the range specified by the protocol
Configuration Reason and the round trip delay at the Gb interface.

10 seconds are long enough as the time delay of a block/unblock


Configuration Rule and
process when the Gb interface is normal. If the delay at the Gb interface
Adjustment Suggestion
is long, it is recommended to increase the parameter value.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

2-190

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Timer

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.8.14 Timer that monitors reset procedure (NS_T2)


Full Name Timer that monitors reset procedure

Abbreviation NS_T2

3GPP Name Tns-reset

3GPP Reference 3GPP TS48.016 V5.4.0

This parameter is a timer used to supervise the NSVC reset process on


the NS layer. The following describes when the timer is started and
stopped, as well as the action at expiry of the timer.
Start: When the BSC initiates an NSVC reset process.
Stop: When a reset acknowledgement message is received from the
SGSN.
At expiry: Repeat the NSVC reset process until the maximum reset retry
Description period (NS_T5) is reached, and then restart the timer.

Managed Object BSC

10..120
Value Range and Step Step: 1

Unit 100 ms

Default Value 100

Default Value The default value is set according to the range specified by the protocol
Configuration Reason and the round trip delay at the Gb interface.

10 seconds are long enough as the time delay of a reset process when
Configuration Rule and
the Gb interface is normal. If the delay at the Gb interface is long, it is
Adjustment Suggestion
recommended to increase the parameter value.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Gb

2-191

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Timer

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.8.15 NC-cycle of NS-VC test process (NS_T3)


Full Name NC-cycle of NS-VC test process

Abbreviation NS_T3

3GPP Name Tns-test

3GPP Reference 3GPP TS48.016 V5.4.0

This parameter is a timer used to supervise the NSVC link test process
on the NS layer. The following describes when the timer is started and
restarted, as well as the action at expiry of the timer.
Start: When the NSVC Reset process is completed (FR), or the
Configuration process is completed (IPGb).
Restart: When an ALIVE ACK message is received from the SGSN.
Description At expiry: Send an NS ALIVE message.

Managed Object BSC

10..600
Value Range and Step Step: 1

Unit 100 ms

Default Value 300

Default Value The default value is set according to the range specified by the protocol
Configuration Reason and the round trip delay at the Gb interface.

A time period within 30 seconds indicates a normal NSVC link when the
Configuration Rule and
Gb interface is normal. If the NSVC link is not stable, the parameter
Adjustment Suggestion
value can be appropriately decreased.

Change Mode Offline

Related features None

Related Parameters None

2-192

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Relationship None

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Timer

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.8.16 Timer that monitors alive process of NSVC (NS_T4)


Full Name Timer that monitors alive process of NSVC

Abbreviation NS_T4

3GPP Name Tns-alive

3GPP Reference 3GPP TS48.016 V5.4.0

This parameter is a timer used to supervise the NSVC alive process on


the NS layer. The following describes when the timer is started and
stopped, as well as the action at expiry of the timer.
Start: When an NS ALIVE message is sent in the test process.
Stop: When an ALIVE ACK message is received from the SGSN.
At expiry: Repeat the alive process for N times (N depends on
Description NS-ALIVE-RETRIES specified by the protocol).

Managed Object BSC

30..30
Value Range and Step Step: 1

Unit 100 ms

Default Value 30

Default Value The default value is set according to the range specified by the protocol
Configuration Reason and the round trip delay at the Gb interface.

Three seconds are long enough as the time delay of an NS alive process
Configuration Rule and
when the Gb interface is normal. If the delay at the Gb interface is long,
Adjustment Suggestion
it is recommended to increase the parameter value.

Change Mode Offline

Related features None

2-193

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Related Parameters None

Relationship None

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Timer

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.8.17 Max attempt period of reset (NS_T5)


Full Name Max attempt period of reset

Abbreviation NS_T5

3GPP Name None

3GPP Reference None

This parameter is a timer used to indicate the maximum retry period of


the NSVC reset process. The following describes when the timer is
started and stopped, as well as the action at expiry of the timer.
Start: When an NSVC reset process is started.
Stop: When a reset acknowledgement is received from the SGSN.
Description At expiry: Terminate the NSVC reset process.

Managed Object BSC

1800..1800
Value Range and Step Step: 1

Unit 100 ms

Default Value 1800

Default Value The default value is set according to the range specified by the protocol
Configuration Reason and the round trip delay at the Gb interface.

18 seconds are long enough as the time delay of a reset process when
Configuration Rule and
the Gb interface is normal. If the delay at the Gb interface is long, it is
Adjustment Suggestion
recommended to increase the parameter value.

Change Mode Offline

2-194

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Related features None

Related Parameters None

Relationship None

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Timer

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.8.18 TFI and USF release timer (T3169)


Full Name TFI and USF release timer

Abbreviation T3169

3GPP Name T3169

3GPP Reference 3GPP TS44.060 V5.19.0

This parameter is timer T3169. In an uplink packet transmission process,


if counter N3101 or N3103 overflows, the BSS starts timer T3169. When
timer T3169 expires, TFI and USF resources are released for reuse.
Start: When the value of counter N3101 equals N3101_MAX, or the
value of counter N3103 equals N3103_MAX.
Stop: None
At expiry: Release the USF and TFI resources.
The counter N3101 equal to N3101_MAX or the counter N3103 equal
to N3103_MAX indicates that the MS does not respond to the BSC any
Description longer. TFI and USF resources shall be released for reuse in the BSC.

Managed Object BSC

0..65535
Value Range and Step Step: 1

Unit 10 ms

Default Value 500

Default Value
Configuration Reason The default value is recommended by the protocol.

2-195

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

TFI and USF resources are released for reuse on the network side
when timer T3169 expires. The TBF is forcibly released when the
value of N3101 reaches N3101_MAX or the value of N3103 reaches
Configuration Rule and
N3103_MAX. It is unnecessary to set a large parameter value, which
Adjustment Suggestion
results in a long waiting time and even influences the utilization of
TFI and USF resources. Set the parameter value according to the
recommendation in the protocol.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Um

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Timer

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.8.19 TBF release timer (T3191)


Full Name TBF release timer

Abbreviation T3191

3GPP Name T3191

3GPP Reference 3GPP TS44.060 V5.19.0

This parameter is timer T3191. The following describes when the timer
is started, restarted, and stopped, as well as the action at the expiry
of the timer.
Start/restart: If the RLC data block to be sent is the last downlink data
block in a downlink packet transmission process, the BSC initiates a
downlink TBF release process by sending an RLC data block, in which
the value of the Final Block Indicator (FBI) equals 1 and the RRBP field
is valid. In this case, the network starts or restarts timer T3191.
Description Stop:

2-196

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

If the RLC is in ACK mode and the MS finds all downlink blocks have
been received, the MS sends a "Packet Downlink Ack" message whose
FAI equals 1 through the uplink block specified by the RRBP field. The
BSC stops timer T3191 if it receives the "Packet Downlink Ack" message
before the expiry of timer T3191.
If the RCL is in NACK mode, the MS sends a "Packet Control Ack"
message through the uplink block specified by the RRBP field. The
BSC stops timer T3191 if it receives the "Packet Control Ack" message
before the expiry of timer T3191.
At expiry: The BSC releases the TBF.

Managed Object BSC

0..65535
Value Range and Step Step: 1

Unit 10 ms

Default Value 500

Default Value
Configuration Reason The default value is recommended by the protocol.

When sending the last RLC data block of downlink TBF, the BSC sets
FBI (to 1) and RRBP, requires the MS to return a "Packet Downlink
Ack/Nack" message, and starts timer T3191 at the same time. Timer
T3191 is stopped if a response from the MS is received from the required
block. And the downlink transmission is normally completed. If timer
Configuration Rule and T3191 expires, the downlink TBF is released due to radio failure.
Adjustment Suggestion A large parameter value can reduce the downlink TBF failure rate.
Keeping TBF for a long time may result in the waste of channel
resources and TFI resources and impacts user experience. Therefore,
in-time release of TBF is recommended.
Use the recommended value specified in Table 13.2.1: Specification of
timers used in GPRS on the Network side of 3GPP TS 04.60.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Um

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Timer

2-197

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.8.20 TBF release time of downlink transmission (T3193)


Full Name TBF release time of downlink transmission

Abbreviation T3193

3GPP Name T3193

3GPP Reference 3GPP TS44.060 V5.19.0

This parameter is timer T3193, which is used for protection purpose


when TBF is released in a packet downlink transmission process. For
more information of T3193, refer to the description of T3191. The
following describes when the timer is started, restarted, and stopped,
as well as the action at the expiry of the timer.
Start/Restart: T3193 is started when the BSC receives a PACKET
DOWNLINK ACK/NACK message with FAI=1 (in RLC ACK mode), or
when T3191 is stopped after the BSC receives a PACKET CONTROL
ACKNOWLEDGE message (in RLC NACK mode).
Stop: The same TFI is used by the newly-established downlink TBF.
At expiry: Release the TFI resource. .
This parameter must be larger than T3192 to ensure that the MS
Description releases the TFI prior to the BSC.

Managed Object BSC

0..65535
Value Range and Step Step: 1

Unit 10 ms

Default Value 51

Default Value
Configuration Reason This timer is slightly larger than T3192.

2-198

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Although the delay policy used by T3192/T3193 causes the waste of


some downlink resources, the network can establish a new downlink
TBF in a short time by directly sending a Packet Downlink Assignment
message. If T3192/T3193 expires, the network can only establish a TBF
by initiating a paging process or immediate assignment process (when
the MS is in Ready state). In this case, more time is needed for the
Configuration Rule and
establishment of a downlink TBF.
Adjustment Suggestion
Take the service load in a cell into account when setting T3192/T3193. In
the case of sufficient network resources, set a large parameter value to
reduce the TBF establishment time, increase the data transmission rate,
and thus improve indexes relevant to downlink throughput efficiency.
T3193 must be slightly larger than T3192 because T3193 is a parameter
on the network side.

Change Mode Offline

Related features None

Related Parameters [Cell]T3192

Timer T3193 of global resources must be longer than timer T3192 of


Relationship
all cells.

Related Interfaces Um

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Timer

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.8.21 TBF protect time when radio link failure (T3195)


Full Name TBF protect time when radio link failure

Abbreviation T3195

3GPP Name T3195

3GPP Reference 3GPP TS44.060 V5.19.0

2-199

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

This parameter is timer T3195, which determines the time for protecting
downlink TBF when the MS stops responding due to radio link failure
or cell change.
Start: T3195 is started when the value of N3105 reaches N3105_MAX.
Stop: None
Description At expiry: The BSC can reuse the TFI.

Managed Object BSC

0..65535
Value Range and Step Step: 1

Unit 10 ms

Default Value 500

Default Value
Configuration Reason The default value is recommended by the protocol.

TFI is released for reuse on the network side when timer T3195
expires. The TBF is forcibly released when the value of N3105 reaches
N3105_MAX. It is unnecessary to set a large parameter value, which
Configuration Rule and
results in a long waiting time and even influences the utilization of TFI
Adjustment Suggestion
resource.
Use the recommended value specified in Table 13.2.1: Specification of
timers used in GPRS on the Network side of 3GPP TS 04.60.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Um

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Timer

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-200

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

2.8.22 PS channel delay release timer (PSRelDelay)


Full Name PS channel delay release timer

Abbreviation PSRelDelay

3GPP Name None

3GPP Reference None

This parameter is a timer indicating the delay time for dynamic


PDCH-to-TCH conversion. The following describes when the timer is
started and stopped, as well as the action at expiry of the timer.
Start: All services (including uplink and downlink) on the PDCH are
released.
Stop: The PDCH is occupied by TBF again.
Description At expiry: Release PDTCH, and convert it into TCH.

Managed Object BSC

50..600
Value Range and Step Step: 1

Unit 100 ms

Default Value 300

The default value 300 can ensure that the dynamic PS channel can be
Default Value
converted back into TCH when no service exists on the PS channel
Configuration Reason
for five seconds.

Configuration Rule and


Adjustment Suggestion The default value is recommended.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Um

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Timer

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-201

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

2.8.23 Guards the PS handover required procedure (T12PsHo)


Full Name Guards the PS handover required procedure

Abbreviation T12PsHo

3GPP Name T12

3GPP Reference 3GPP TS 48.018

This parameter is a timer used to control the time of a PS HANDOVER


REQUIRED process. The timer is started when a PS Handover Required
message is sent. It is stopped when a PS HANDOVER REQUIRED ACK
message or PS HANDOVER REQUIRED NACK message is received.
Upon the expiry of the timer, the PS HANDOVER REQUIRED message
Description is sent again.

Managed Object BSC

50..1200
Value Range and Step Step: 1

Unit 10 ms

Default Value 300

Default Value The default value is an experimental value obtained during the
Configuration Reason interaction of processes between network elements.

The default value is recommended for this process monitoring timer.


Configuration Rule and
The parameters relevant to PS handover, including this parameter, are
Adjustment Suggestion
not in commercial use currently.

Change Mode Offline

Related features ZGO-02-02-016 PS Handover

Related Parameters None

Relationship None

Related Interfaces Gb

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Timer

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-202

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

2.8.24 Guard resource release after sending PS HO command


(TwaitRelInPSHo)
Full Name Guard resource release after sending PS HO command

Abbreviation TwaitRelInPSHo

3GPP Name Internal

3GPP Reference None

The parameter specifies the waiting time for the release of resources
after a PS Handover Command message is sent.
This timer is started after a PS HANDOVER COMMAND message
is sent to the MS. It is stopped after a DELETE BSS PFC message
is received from the SGSN, or a HANDOVER COMPLETE message
is received from the target cell. Upon the expiry of the timer, a PS
Description HANDOVER CANCEL message is sent to the SGSN.

Managed Object BSC

100..1000
Value Range and Step Step: 1

Unit 10 ms

Default Value 300

Default Value The default value is an experimental value obtained during the
Configuration Reason interaction of processes between network elements.

The default value is recommended for this process monitoring timer.


Configuration Rule and
The parameters relevant to PS handover, including this parameter, are
Adjustment Suggestion
not in commercial use currently.

Change Mode Offline

Related features ZGO-02-02-016 PS Handover

Related Parameters None

Relationship None

Related Interfaces None

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Timer

Parameter Modifying
Version None

2-203

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Parameter Modifying
Detail None

2.8.25 Downlink Delay time in signal TBF Mode (SigTBFDlDelay


Time)
Full Name Downlink Delay time in signal TBF Mode

Abbreviation SigTBFDlDelayTime

3GPP Name None

TS 44.060: “Radio Link Control/Medium Access Control (RLC/MAC) pro-


3GPP Reference tocol"

Description This parameter specifies the downlink delay of the signaling TBF.

Managed Object BSC

500..4000
Value Range and Step Step: 1

Unit ms

Default Value 1000

The DL delay in signaling TBF mode is set to half the DL delay in data
Default Value
TBF mode, because the traffic transmitted by the signaling TBF is low
Configuration Reason
and longer delay can lead to a waste of resources.

Configuration Rule and It is not recommended to modify the value. Modification can affect the
Adjustment Suggestion service quality.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Um

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed element ID->Config


OMC Access Path
SetBSC Function->GPRS Timer2

Parameter Modifying
Version iBSCV6.20.712b

2-204

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Parameter Modifying
Detail New

2.8.26 Extendable uplink TBF time in signal TBF Mode


(SigTBFExtUlTime)
Full Name Extendable uplink TBF time in signal TBF Mode

Abbreviation SigTBFExtUlTime

3GPP Name None

TS 44.060: “Radio Link Control/Medium Access Control (RLC/MAC) pro-


3GPP Reference tocol"

This parameter specifies the extendable uplink TBF time in signal TBF
Description Mode.

Managed Object BSC

0..3000
Value Range and Step Step: 1

Unit ms

Default Value 800

The UL extension time in signaling TBF mode is set to half the same
Default Value
time in data TBF mode, because the traffic transmitted by the signaling
Configuration Reason
TBF is low and longer extension time can lead to a waste of resources.

Configuration Rule and It is not recommended to modify the value. Modification can affect the
Adjustment Suggestion service quality.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Um

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed element ID->Config


OMC Access Path
SetBSC Function->GPRS Timer2

Parameter Modifying
Version iBSCV6.20.712b

2-205

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Parameter Modifying
Detail New

2.8.27 Synchronization timer that ensures source BSS receives


both PS and CS responses (T23)
The parameter is not used in this version.

2.8.28 Synchronization timer that ensures target BSS receives both


PS and CS requests (T24)
The parameter is not used in this version.

2.8.29 T3197 (T3197)


The parameter is not used in this version.

2.9 AMR Half Method Parameters


2.9.1 AMR Half Active Codec Set (AmrHalfAcs)
Full Name AMR Half Active Codec Set

Abbreviation AmrHalfAcs

3GPP Name AMR Active Codec Set

3GPP Reference 45.009

The code has eight bits. Bits 6 to 8 are reserved. 7.40 kbit/s is bit 5,
6.70 kbit/s bit 4, 5.9 kbit/s is bit 3, 5.15 kbit/s is bit 2, and 4.75 kbit/s
bit 1. Yes stands for 1, that is, including this speech coding mode. No
stands for 0, that is, excluding this speech coding mode. At most four
coding modes can be set.
When interface A is in IP mode, ACS is decided by the MSC and this
Description parameter is invalid.

Managed Object BSC

The value is Yes or No for 4.75 kbit/s, 5.15 kbit/s, 5.90 kbit/s, 6.70 kbit/s,
Value Range and Step and 7.40 kbit/s.

Unit None

The default value is "Yes, No, Yes, No, Yes", that is, 00010101. In this
case, you can export the decimal number "21" from the network planning
Default Value and optimization table.

2-206

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Under TrFO configuration, 5.15k is unavailable to the rate set supported


Default Value
by CN. This default value is configured so as to not affect the success
Configuration Reason
rate of TFO establishment when AMR+TFO is configured.

Generally, high rates are used along with low rates. When a cell has
Configuration Rule and
good radio signal quality, you can select high rates only. Otherwise, you
Adjustment Suggestion
can select low rates only.

Change Mode Offline

Related features ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)

Related Parameters [BSC]AmrStartMode

When only one of the five bits of this parameter is set to No, the value
range is 1 to 4.
When two of the five bits of this parameter are set to No, the value
range is 1 to 3.
When three of the five bits of this parameter are set to No, the value
Relationship
range is 1 to 2.
When four of the five bits of this parameter are set to No, the value
range is 1.
When the five bits of this parameter are all set to No, the value range is
null.

Related Interfaces Um

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->AMR Half Method Paras

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.9.2 Thresholds of AMR (AmrThresholds)


Full Name Thresholds of AMR

Abbreviation AmrThresholds

3GPP Name threshold

3GPP Reference 45.009

2-207

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

The parameter AmrThresholds includes five elements: AmrThresholds1,


AmrThresholds2, AmrThresholds3, AmrThresholds4, and
AmrThresholds5, which meet the following requirements:
AmrThresholds1 ≤ AmrThresholds2 ≤ AmrThresholds3 ≤
AmrThresholds4 ≤ AmrThresholds5
AmrThresholds1 + AmrHysteresis1 ≤ AmrThresholds2 +
AmrHysteresis2≤AmrThresholds3 + AmrHysteresis3 ≤ AmrThresholds4
+ AmrHysteresis4 ≤ AmrThresholds5 + AmrHysteresis5
When CIR is more than AmrThresholdsN+AmrHysteresisN, the speech
coding rate will be changed to mode N+1. When CIR is less than
Description AmrThresholdsN, the speech coding rate will be changed to mode N.

Managed Object BSC

The value rage is 0 to 63 in modes 1, 2, 3, 4, and 5.


0: 0.0 dB
1: 0.5 dB
2: 1.0 dB
...
Value Range and Step 63: 31.5 dB

Unit 0.5 dB

Default Value [18, 20, 23, 26, 30]

Default Value The default value is set to improve the performance of AMR function.
Configuration Reason

Configuration Rule and Generally, you do not have to adjust the setting of this parameter unless
Adjustment Suggestion the FER measured by the BTS exceeds 1%.

Change Mode Offline

Related features ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)

Related Parameters [BSC]AmrHysteresis

AmrThresholds1 ≤ AmrThresholds2 ≤ AmrThresholds3 ≤


AmrThresholds4 ≤ AmrThresholds5
Relationship AmrThresholds1 + AmrHysteresis1 ≤ AmrThresholds2 +
AmrHysteresis2≤AmrThresholds3 + AmrHysteresis3 ≤ AmrThresholds4
+ AmrHysteresis4 ≤ AmrThresholds5 + AmrHysteresis5

Related Interfaces Um, Abis

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->AMR Half Method Paras

2-208

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.9.3 Hysteresis of AMR (AmrHysteresis)


Full Name Hysteresis of AMR

Abbreviation AmrHysteresis

3GPP Name hysteresis

3GPP Reference 45.009

The parameter AmrThresholds includes five elements: AmrThresholds1,


AmrThresholds2, AmrThresholds3, AmrThresholds4, and
AmrThresholds5, which meet the following requirements:
AmrThresholds1 ≤ AmrThresholds2 ≤ AmrThresholds3 ≤
AmrThresholds4 ≤ AmrThresholds5
AmrThresholds1 + AmrHysteresis1 ≤ AmrThresholds2 +
AmrHysteresis2≤AmrThresholds3 + AmrHysteresis3 ≤ AmrThresholds4
+ AmrHysteresis4 ≤ AmrThresholds5 + AmrHysteresis5
When CIR is more than AmrThresholdsN+AmrHysteresisN, the speech
coding rate will be changed to mode N+1. When CIR is less than
Description AmrThresholdsN, the speech coding rate will be changed to mode N.

Managed Object BSC

The value rage is 0 to 15 in modes 1, 2, 3, 4, and 5.


0: 0.0 dB
1: 0.5 dB
2: 1.0 dB
...
Value Range and Step 15: 7.5 dB

Unit 0.5 dB

Default Value [3, 3, 3, 4, 4]

Default Value
Configuration Reason The default value is set to improve the performance of AMR function.

By checking the frequency of rate adjustments (through tests, analyses,


Configuration Rule and or AMR rate monitoring tools), you can decide whether this parameter
Adjustment Suggestion is set properly. When the rate is adjusted too frequently, you can set
the parameter to a higher value.

Change Mode Offline

Related features ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)

2-209

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Related Parameters [BSC]AmrThresholds

AmrThresholds1 + AmrHysteresis1 ≤ AmrThresholds2 + AmrHysteresis2


Relationship ≤ AmrThresholds3 + AmrHysteresis3 ≤ AmrThresholds4 +
AmrHysteresis4 ≤ AmrThresholds5 + AmrHysteresis5

Related Interfaces Um, Abis

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->AMR Half Method Paras

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.9.4 Initial codec mode (IsAmrlCM)


Full Name Initial codec mode

Abbreviation IsAmrlCM

3GPP Name Initial Codec Mode Indicator

3GPP Reference 45.009

This parameter decides which one, the coding mode specified in


Startmode or the default initial coding mode specified in the protocol
45.009, is used as the initial AMR speech coding mode.
When one mode is used, the corresponding rate is used as the initial
coding mode.
When two or three modes are used, the lowest rate is used as the
initial coding mode.
When four modes are used, the second lowest rate is used as the initial
coding mode.
When interface A is in IP mode, this parameter is not used. The initial
coding mode depends on IpaAMRStartMode in the system control
Description parameters.

Managed Object BSC

Value Range and Step Start-mode codec, Initial codec mode

Unit None

Default Value Start-mode codec

2-210

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Default Value
Configuration Reason In the default mode, the initial coding mode can be set as needed.

In good radio network conditions, Start-mode codec and high-rate


Configuration Rule and coding modes are recommended.
Adjustment Suggestion In poor radio network conditions, you can set this parameter to "Initial
codec mode", that is, the default initial rate specified in the protocol.

Change Mode Offline

Related features ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)

Related Parameters [BSC]AmrStartMode

Relationship AmrStartMode is valid only when IsAmrlCM is set to "Start-mode codec".

Related Interfaces Um, Abis

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->AMR Half Method Paras

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.9.5 Start mode (AmrStartMode)


Full Name Start mode

Abbreviation AmrStartMode

3GPP Name Start Mode

3GPP Reference 44.018

Description Startmode codec mode

Managed Object BSC

2-211

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

The value range is described as follows:


1: The coding mode with the lowest code rate is selected as the initial
coding mode.
2: If there is more than one coding mode, the coding mode with the
second lowest code rate will be selected.
3: If there are more than two coding modes, the coding mode with the
third lowest code rate will be selected.
4: If there are more than three coding modes, the coding mode with the
Value Range and Step fourth lowest code rate will be selected.

Unit None

This parameter is set as the maximum rate in accordance with the number
of the current selected rates. For example, it is set to 4 if the full rate
is configured with 4 coding modes, and the maximum coding mode is
Default Value selected as the initial rate.

Previously, the minimum coding mode is used in which the MOS value
increased from the lower value to the stabilized value takes a long period
Default Value
of time, which is due to the limitation of the current rate adjustment
Configuration Reason
mechanision of the version. In this case, the initial coding mode is
changed into the maximum coding mode.

Configuration Rule and In good radio network conditions, high initial rates can be used to
Adjustment Suggestion improve voice quality.

Change Mode Offline

Related features ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)

Related Parameters [BSC]AmrHarfAcs


[BSC]IsAmrlCM

When only one of the five bits of the parameter AmrHarfAcs is set to No,
the value range is 1 to 4.
When two of the five bits of the parameter AmrHarfAcs are set to No,
the value range is 1 to 3.
When three of the five bits of the parameter AmrHarfAcs are set to No,
Relationship the value range is 1 to 3.
When four of the five bits of the parameter AmrHarfAcs are set to No,
the value range is 1.
When the five bits of the parameter AmrHarfAcs are all set to No, the
value range is null.
AmrStartMode is valid only when IsAmrlCM is set to "Start-mode codec".

Related Interfaces Um, Abis

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

2-212

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->AMR Half Method Paras

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.9.6 Enable noise control (IsAmrNscb)


Full Name Enable noise control

Abbreviation IsAmrNscb

3GPP Name Noise Suppression Control Bit

3GPP Reference 44.018

This parameter decides whether to disable the AMR noise control


function at the MS side, that is, whether to suppress the background
noise and keep the original voice quality. Noise suppression is a function
at the MS side.
No: Noise suppression enabled.
Description Yes: Noise suppression disabled.

Managed Object BSC

Value Range and Step 1: Yes; 0: No

Unit None

Default Value No

Default Value Enabling noise suppression can minimize noise and improve voice
Configuration Reason quality.

Generally, it is recommended to enable the noise suppression function.


Configuration Rule and
When voice quality problems occur, you should check the setting of
Adjustment Suggestion
this parameter.

Change Mode Offline

Related features ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)

Related Parameters None

Relationship None

Related Interfaces Um, Abis

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

2-213

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->AMR Half Method Paras

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.10 AMR Full Method Parameters


2.10.1 AMR full Active Codec Set (AmrFullAcs)
Full Name AMR full Active Codec Set

Abbreviation AmrFullAcs

3GPP Name AMR Active Codec Set

3GPP Reference 45.009

The code has eight bits. 12.2 kbit/s is bit 8, 10.2 kbit/s bit 7, 7.95 kbit/s
bit 6, 7.40 kbit/s bit 5, 6.70 kbit/s bit 4, 5.9 kbit/s bit 3, 5.15 kbit/s bit 2,
and 4.75 kbit/s bit 1. Yes stands for 1, that is, including this speech
coding mode. No stands for 0, that is, excluding this speech coding
mode. At most four coding modes can be set.
When interface A is in IP mode, ACS is decided by the MSC and this
Description parameter is invalid.

Managed Object BSC

The value is Yes or No for 4.75 kbit/s, 5.15 kbit/s, 5.90 kbit/s, 6.70 kbit/s,
Value Range and Step 7.40 kbit/s, 7.95 kbit/s, 10.2 kbit/s, and 12.2 kbit/s.

Unit None

The default value is "Yes, No, Yes, No, Yes, No, No, Yes", that is,
10010101. In this case, you can export the decimal number "149" from
Default Value the network planning and optimization table.

Under TrFO configuration, 5.15k is unavailable to the rate set supported


Default Value
by CN. This default value is configured so as to not affect the success
Configuration Reason
rate of TFO establishment when AMR+TFO is configured.

Generally, high rates are used along with low rates. When a cell has
Configuration Rule and
good radio signal quality, you can select high rates only. Otherwise, you
Adjustment Suggestion
can select low rates only.

Change Mode Offline

Related features ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)

2-214

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Related Parameters [BSC]AmrStartMode

When four of the eight bits of this parameter are set to No, the value
range is 1 to 4.
When five of the eight bits of this parameter are set to No, the value
range is 1 to 3.
When six of the eight bits of this parameter are set to No, the value
Relationship
range is 1 to 2.
When seven of the eight bits of this parameter are set to No, the value
range is 1.
When the eight bits of this parameter are all set to No, the value range is
null.

Related Interfaces Abis

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->AMR Full Method Paras

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.10.2 Thresholds of AMR (AmrThresholds)


Full Name Thresholds of AMR

Abbreviation AmrThresholds

3GPP Name threshold

3GPP Reference 45.009

This parameter includes seven elements: AmrThresholds1,


AmrThresholds2, AmrThresholds3, AmrThresholds4, AmrThresholds5,
AmrThresholds6, and AmrThresholds7, which meet the following
requirements:
AmrThresholds1 ≤ AmrThresholds2 ≤ AmrThresholds3 ≤
AmrThresholds4 ≤ AmrThresholds5 ≤ AmrThresholds6 ≤
AmrThresholds7, AmrThresholds1 + AmrHysteresis1 ≤ AmrThresholds2
+ AmrHysteresis2 ≤ AmrThresholds3 + AmrHysteresis3 ≤
AmrThresholds4 + AmrHysteresis4 ≤ AmrThresholds5 + AmrHysteresis5
≤ AmrThresholds6 + AmrHysteresis6 ≤ AmrThresholds7 +
Description AmrHysteresis7

2-215

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Managed Object BSC

The value rage is 0 to 63 in modes 1, 2, 3, 4, 5, 6 and 7.


0: 0.0 dB
1: 0.5 dB
2: 1.0 dB
...
Value Range and Step 63: 31.5 dB

Unit 0.5 dB

Default Value [13, 14, 15, 17, 18, 20, 23]

Default Value
Configuration Reason The default value is set to improve the performance of AMR function.

Configuration Rule and Generally, you do not have to adjust the setting of this parameter unless
Adjustment Suggestion the FER measured by the BTS exceeds 1%.

Change Mode Offline

Related features ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)

Related Parameters [BSC]AmrHysteresis

This parameter includes seven elements: AmrThresholds1,


AmrThresholds2, AmrThresholds3, AmrThresholds4, AmrThresholds5,
AmrThresholds6, and AmrThresholds7, which meet the following
requirements:
AmrThresholds1 ≤ AmrThresholds2 ≤ AmrThresholds3 ≤
Relationship AmrThresholds4 ≤ AmrThresholds5 ≤ AmrThresholds6 ≤
AmrThresholds7, AmrThresholds1 + AmrHysteresis1 ≤ AmrThresholds2
+ AmrHysteresis2 ≤ AmrThresholds3 + AmrHysteresis3 ≤
AmrThresholds4 + AmrHysteresis4 ≤ AmrThresholds5 + AmrHysteresis5
≤ AmrThresholds6 + AmrHysteresis6 ≤ AmrThresholds7 +
AmrHysteresis7

Related Interfaces Um, Abis

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->AMR Full Method Paras

Parameter Modifying
Version None

Parameter Modifying
Detail None

2-216

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

2.10.3 Hysteresis of AMR (AmrHysteresis)


Full Name Hysteresis of AMR

Abbreviation AmrHysteresis

3GPP Name hysteresis

3GPP Reference 45.009

This parameter includes seven elements: AmrHysteresis1,


AmrHysteresis2, AmrHysteresis3, AmrHysteresis4, AmrHysteresis5,
AmrHysteresis6, and AmrHysteresis7, which meet the following
requirements:
AmrThresholds1 + AmrHysteresis1 ≤ AmrThresholds2 + AmrHysteresis2
≤ AmrThresholds3 + AmrHysteresis3 ≤ AmrThresholds4 +
AmrHysteresis4 ≤ AmrThresholds5 + AmrHysteresis5 ≤ AmrThresholds6
Description + AmrHysteresis6 ≤ AmrThresholds7 + AmrHysteresis7

Managed Object BSC

The value rage is 0 to 15 in modes 1, 2, 3, 4, 5, 6 and 7.


0: 0.0 dB
1: 0.5 dB
2: 1.0 dB
...
Value Range and Step 15: 7.5 dB

Unit 0.5 dB

Default Value [3, 3, 3, 3, 3, 4, 4]

Default Value
Configuration Reason The default value is set to improve the performance of AMR function.

By checking the frequency of rate adjustments, you can decide whether


Configuration Rule and
this parameter is set properly. When the rate is adjusted too frequently,
Adjustment Suggestion
you can set the parameter to a higher value.

Change Mode Offline

Related features ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)

Related Parameters [BSC]AmrThresholds

This parameter includes seven elements: AmrHysteresis1,


AmrHysteresis2, AmrHysteresis3, AmrHysteresis4, AmrHysteresis5,
AmrHysteresis6, and AmrHysteresis7, which meet the following
requirements:
Relationship
AmrThresholds1 + AmrHysteresis1 ≤ AmrThresholds2 + AmrHysteresis2
≤ AmrThresholds3 + AmrHysteresis3 ≤ AmrThresholds4 +
AmrHysteresis4 ≤ AmrThresholds5 + AmrHysteresis5 ≤ AmrThresholds6
+ AmrHysteresis6 ≤ AmrThresholds7 + AmrHysteresis7

2-217

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Related Interfaces Um, Abis

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->AMR Full Method Paras

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.10.4 Initial codec mode (IsAmrICM)


Full Name Initial codec mode

Abbreviation IsAmrICM

3GPP Name Initial Codec Mode Indicator

3GPP Reference 45.009

This parameter decides which one, the coding mode specified in


Startmode or the default initial coding mode specified in the protocol
45.009, is used as the initial AMR speech coding mode.
When one mode is used, the corresponding rate is used as the initial
coding mode.
When two or three modes are used, the lowest rate is used as the
initial coding mode.
When four modes are used, the second lowest rate is used as the initial
coding mode.
When interface A is in IP mode, this parameter is not used. The initial
coding mode depends on IpaAMRStartMode in the system control
Description parameters.

Managed Object BSC

Value Range and Step Start-mode codec, Initial codec mode

Unit None

Default Value Start-mode codec

Default Value
Configuration Reason In the default mode, the initial coding mode can be set as needed.

Configuration Rule and Generally, you can set this parameter to "Initial codec mode", that is, the
Adjustment Suggestion default initial rate specified in the protocol.

Change Mode Offline

2-218

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Related features ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)

Related Parameters [BSC]AmrStartMode

Relationship AmrStartMode is valid only when IsAmrlCM is set to "Start-mode codec".

Related Interfaces Um, Abis

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->AMR Full Method Paras

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.10.5 Start mode (AmrStartMode)


Full Name Start mode

Abbreviation AmrStartMode

3GPP Name Start Mode

3GPP Reference 44.018

Description Startmode codec mode

Managed Object BSC

When four of the eight bits of the parameter AmrFullAcs are set to No,
the value range is 1 to 4.
When five of the eight bits of the parameter AmrFullAcs are set to No,
the value range is 1 to 3.
When six of the eight bits of the parameter AmrFullAcs are set to No,
the value range is 1 to 2.
When seven of the eight bits of the parameter AmrFullAcs are set to
No, the value range is 1.
When the eight bits of the parameter AmrFullAcs are all set to No, the
value range is null.
The value range is described as follows:
1: The coding mode with the lowest code rate is selected as the initial
coding mode.
2: If there is more than one coding mode, the coding mode with the
Value Range and Step
second lowest code rate will be selected.

2-219

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

3: If there are more than two coding modes, the coding mode with the
third lowest code rate will be selected.
4: If there are more than three coding modes, the coding mode with the
fourth lowest code rate will be selected.

Unit None

This parameter is set as the maximum rate in accordance with the number
of the current selected rates. For example, it is set to 4 if the full rate
is configured with 4 coding modes, and the maximum coding mode is
Default Value selected as the initial rate.

Previously, the minimum coding mode is used in which the MOS value
increased from the lower value to the stabilized value takes a long period
Default Value
of time, which is due to the limitation of the current rate adjustment
Configuration Reason
mechanision of the version. In this case, the initial coding mode is
changed into the maximum coding mode.

Configuration Rule and High initial rates can be used in cells that have good radio network
Adjustment Suggestion conditions.

Change Mode Offline

Related features ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)

Related Parameters [BSC]AmrHarfAcs


[BSC]IsAmrlCM

When four of the eight bits of this parameter are set to No, the value
range is 1 to 4.
When five of the eight bits of this parameter are set to No, the value
range is 1 to 3.
When six of the eight bits of this parameter are set to No, the value
Relationship range is 1 to 2.
When seven of the eight bits of this parameter are set to No, the value
range is 1.
When the eight bits of this parameter are all set to No, the value range is
null.
AmrStartMode is valid only when IsAmrlCM is set to "Start-mode codec".

Related Interfaces Um, Abis

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->AMR Full Method Paras

Parameter Modifying
Version None

2-220

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Parameter Modifying
Detail None

2.10.6 Enable noise control (IsAmrNscb)


Full Name Enable noise control

Abbreviation IsAmrNscb

3GPP Name Noise Suppression Control Bit

3GPP Reference 44.018

This parameter decides whether to disable the AMR noise control


function at the MS side, that is, whether to suppress the background
noise and keep the original voice quality. Noise suppression is a function
at the MS side.
No: Noise suppression enabled.
Description Yes: Noise suppression disabled.

Managed Object BSC

Value Range and Step 1: Yes; 0: No

Unit None

Default Value No

Default Value Enabling noise suppression can minimize noise and improve voice
Configuration Reason quality.

Generally, it is recommended to enable the noise suppression function.


Configuration Rule and
When voice quality problems occur, you should check the setting of
Adjustment Suggestion
this parameter.

Change Mode Offline

Related features ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)

Related Parameters None

Relationship None

Related Interfaces Um, Abis

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->AMR Full Method Paras

Parameter Modifying
Version None

2-221

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

Parameter Modifying
Detail None

2.11 GPRS Other Parameters 1


2.11.1 Cn (Cn)
Full Name Cn

Abbreviation Cn

3GPP Name None

3GPP Reference None

This parameter is a counter used as a criterion for increasing the channel


coding level.
Being different from CS channels, for which only one coding scheme
can be used, GPRS data blocks can use four channel-coding schemes
(CS-1 to CS-4). The data rates corresponding to these four coding
schemes (CS-1, CS-2, CS-3, and CS-4) are 9.05 kbps, 13.4 kbps, 15.6
kbps, and 21.4 kbps. The lower-level coding scheme provides higher
error correction capability and lower data throughput. Different coding
schemes can be used for different timeslots and even different TBFs.
The network selects the coding mode dynamically according to the data
rate requirement and radio transmission quality at the transmission of
the GPRS data, to reach maximum radio throughput. The probability
of retransmission of error radio blocks is small when the radio
transmission quality in the network is good. In this case, a coding
scheme accommodating more information (that is, a higher-level coding
scheme) is recommended.
Increase the coding scheme by one level when the count of continuous
correctly-transmitted data blocks of the TBF (uplink and downlink) , for
which the coding scheme CSn (1≤n≤3) is used, exceeds the preset value
of the parameter Cn[n-1].
The subscripts 1, 2, and 3 correspond to three parameters for coding
scheme switching between CS1 and CS2, CS2 and CS3, and CS3 and
Description CS4.

Managed Object BSC

0..100
Value Range and Step Step: 1

Unit None

Default Value 85

2-222

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Based on the result of system emulation, it is deemed that a BLER in the


Default Value
range from 15% to 25% is acceptable. Increasing the coding scheme
Configuration Reason
level when a BLER is lower than 15% can improve the transmission rate.

A large parameter value, making it difficult to increase the coding scheme


level, can prevent rate decrease caused by improper increasing of
coding scheme level and facilitate the reduction of GPRS TBF drop rate.
A small parameter value makes it easy to fulfill the criterion for increasing
Configuration Rule and
the coding scheme level.
Adjustment Suggestion
A large parameter value is recommended to ensure that the increase of
coding scheme level is only allowed when the BLER is low. In this case,
the increasing of coding scheme level can improve the indexes relevant
to GPRS service throughput (not EDGE).

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Um

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Other Parameters 1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.11.2 Nn (Nn)
Full Name Nn

Abbreviation Nn

3GPP Name None

3GPP Reference None

2-223

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

This parameter is a counter used as a criterion for decreasing the


channel coding level. It is used on the RLC/MAC layer of BRP.
Being different from CS channels, for which only one coding scheme
can be used, GPRS data blocks can use four channel-coding schemes
(CS-1 to CS-4). The data rates corresponding to these four coding
schemes (CS-1, CS-2, CS-3, and CS-4) are 9.05 kbps, 13.4 kbps, 15.6
kbps, and 21.4 kbps. The lower-level coding scheme provides higher
error correction capability and lower data throughput.
User can choose different coding modes for each timeslot or even each
TBF. In the GPRS data transport process, the network should select
appropriate coding modes in a dynamic manner depending on the
requirement for data rate and the radio transmission quality to achieve
the maximum radio throughput.
The coding mode with stronger anti-interference capability (that is, low
level coding mode) must be used when the radio transmission quality
is poor. Decrease the coding scheme by one level when the count of
lost continuous data blocks reaches Xn[n-2]% of Nn[n-2] data blocks
on the TBF (uplink and downlink), for which the coding scheme CSn
(2≤n≤4) is used.
The subscripts 1, 2, and 3 correspond to three parameters for coding
scheme switching between CS1 and CS2, CS2 and CS3, and CS3 and
Description CS4.

Managed Object BSC

0..255
Value Range and Step Step: 1

Unit None

Default Value 20

Default Value The parameter value 20 is recommended in consideration of the


Configuration Reason sensitivity and precision of rate adjustment.

If the parameter value is large, more transmitted data blocks are involved
and the stability of coding scheme adjustment can be improved.
Configuration Rule and If the parameter value is small, the coding scheme can be adjusted in
Adjustment Suggestion time with the change of the radio environment.
An appropriate parameter value can improve the indexes relevant to
GPRS service throughput (not EDGE).

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Um

2-224

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Other Parameters 1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.11.3 Xn (Xn)
Full Name Xn

Abbreviation Xn

3GPP Name None

3GPP Reference None

This parameter indicates the threshold used as a criterion for decreasing


the channel coding level. It is used on the RLC/MAC layer of BRP.
Being different from CS channels, for which only one coding scheme
can be used, GPRS data blocks can use four channel-coding schemes
(CS-1 to CS-4). The data rates corresponding to these four coding
schemes (CS-1, CS-2, CS-3, and CS-4) are 9.05 kbps, 13.4 kbps, 15.6
kbps, and 21.4 kbps. The lower-level coding scheme provides higher
error correction capability and lower data throughput.
User can choose different coding modes for each timeslot or even each
TBF. In the GPRS data transport process, the network should select
appropriate coding modes in a dynamic manner depending on the
requirement for data rate and the radio transmission quality to achieve
the maximum radio throughput.
The coding mode with stronger anti-interference capability (that is, low
level coding mode) must be used when the radio transmission quality
is poor. Decrease the coding scheme by one level when the count of
lost continuous data blocks reaches Xn[n-2]% of Nn[n-2] data blocks
on the TBF (uplink and downlink), for which the coding scheme CSn
(2≤n≤4) is used.
The subscripts 1, 2, and 3 correspond to three parameters for coding
scheme switching between CS1 and CS2, CS2 and CS3, and CS3 and
Description CS4.

Managed Object BSC

2-225

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

0..100
Value Range and Step Step: 1

Unit %

Default Value 25

Default Value In a common radio environment, a retransmission rate within the range
Configuration Reason from 15% to 25% is acceptable.

A large parameter value makes it difficult to fulfill the criterion for


decreasing the coding scheme level.
A small parameter value makes it easy to fulfil the criteria for decreasing
the coding scheme level.
Configuration Rule and A small parameter value is recommended to ensure that the coding
Adjustment Suggestion scheme level can be decreased when the BLER is high, preventing too
low transmission rate caused by the delay of coding scheme adjustment.
The in-time adjustment of coding scheme can reduce the GPRS TBF
drop rate and improve the indexes relevant to GPRS service throughput
(not EDGE).

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Um

Impact on Equipment 0

Impact on service 0

Negotiation With CN No

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Other Parameters 1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.11.4 Max allowed number of continous losses of uplink data


blocks (N3101)
Full Name Max allowed number of continous losses of uplink data blocks

Abbreviation N3101

3GPP Name N3101

2-226

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

3GPP Reference 3GPP TS44.060 V5.19.0

This parameter is counter N3101, which is used on the RLC/MAC layer


of PCU.
In a packet uplink transmission process, the BSS allocates a USF
to each uplink block (corresponding to a uplink TBF). If the network
correctly receives data from the specified uplink block for a USF, N3101
is cleared for the TBF. If the number of times that the lost of data in
the specified uplink block occurs exceeds N3101, timer T3169 will be
started. The network can use the TFI and USF resources again after
Description T3169 expires.

Managed Object BSC

Value Range and Step 9...255

Unit None

Default Value 50

Default Value The default value is set to reduce the number of exception TBF releases
Configuration Reason caused by the overflow of N3101 and thus improve the network quality.

The smaller the parameter value is, the higher tolerance on uplink
exception the network has, and the higher the probability of exception
uplink TBF release is. If the parameter value is too large, the network
still allocates uplink resources to the MS because the uplink block
receiving failure is caused by the MS itself, which results in the waste
of system resources. In the basic measurement of PS, the number of
Configuration Rule and
exception uplink TBF releases upon N3101 overflow records some
Adjustment Suggestion
causes of these uplink TBF releases, which generally are poor link
quality at Abis interface, poor radio interface quality, improper network
coverage, and some actions of the MS (for example, cell reselection).
After the radio environment is improved, the overflow threshold of N3101
can be appropriately increased to reduce the number of exception uplink
TBF releases and thus improve the network quality at a certain extent.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Um

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

2-227

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Other Parameters 1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.11.5 Times of packet uplink ACK/NACK retries (N3103)


Full Name Times of packet uplink ACK/NACK retries

Abbreviation N3103

3GPP Name N3103

3GPP Reference 3GPP TS44.060 V5.19.0

This parameter is counter N3101, which is used on the RLC/MAC layer


of PCU.
In a packet uplink transmission process, after detecting the completion
of uplink TBF (CV=0, V(Q)=V(R)) and receiving all RLC data blocks,
the network sends a "Packet Uplink ACK/NACK" message with FAI=1,
inserts a valid RRBP field in the header of the RLC/MAC control block,
and then clears counter N3103.
Upon receiving a "Packet Uplink ACK/NACK" message with FAI=1 from
the network side, the MS sends a "Packet Control ACK" message in the
block specified by RRBP and release the TBF.
If the network fails to receive the "Packet Control ACK" message from
the radio block specified by RRBP, N3103 increases by 1 and the
"Packet Uplink ACK/NACK" is retransmitted.
The network starts T3169 timer if the value of N3103 exceeds the
limiting N3103max. The network can use the TFI and USF resources
Description again after T3169 expires.

Managed Object BSC

Value Range and Step 0...255

Unit None

Default Value 10

The default value 10 is recommended in consideration of improving


Default Value
the network quality by reducing the number of exception uplink TBF
Configuration Reason
releases due to N3103 overflow, and reducing the delay of TBF release.

2-228

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

The smaller the parameter value is, the higher tolerance on uplink
exception the network has, and the higher the probability of exception
uplink TBF release is. If the parameter value is too small, the network
still allocates uplink resources to the MS because the network fails
to receive the correct PACKET CONTROL ACKKNOWLEDGEMENT
Configuration Rule and
message due to poor radio interface quality or some actions of the
Adjustment Suggestion
MS, which results in the waste of system resources. Adjust the value
of N3103 appropriately according to the actual situation of the network
(for example, radio interface quality, transmission link quality, and the
factor of the MS itself) to reduce the number of exception TBF releases
caused by N3103 overflow.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Um

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Other Parameters 1

Parameter Modifying
Version None

Parameter Modifying
Detail None

2.11.6 Max allowed number of continous losses of uplink RLC/MAC


control message (N3105)
Max allowed number of continous losses of uplink RLC/MAC control mes-
Full Name sage

Abbreviation N3105

3GPP Name N3105

3GPP Reference 3GPP TS44.060 V5.19.0

2-229

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


ZXG10 iBSC Radio Parameter Reference

This parameter is counter N3105, which is used on the RLC/MAC layer


of PCU.
When the network sends the downlink RLC block or RLC/MAC control
block of the allocated RRBP and receives a valid RLC/MAC control
message from the MS in a TBF, the counter N3105 is reset. If the
network does not receive the RLC/MAC control block from the allocated
block, the counter N3105 is increased by 1. When N3105 reaches
N3105_MAX, the TBF is released. N3105_MAX depends on the settings
Description on the network side.

Managed Object BSC

Value Range and Step 0...255

Unit None

Default Value 15

The default value is set to reduce the number of exception downlink


Default Value
TBF releases caused by the overflow of N3105 and thus improve the
Configuration Reason
network quality.

The smaller the parameter value is, the higher tolerance on uplink
exception the network has, and the higher the probability of exception
downlink TBF release is. If the parameter value is too small, the network
still allocates radio resources to the MS because the network fails to
Configuration Rule and receive the correct PACKET (EGPRS) DOWNLINK ACK message due to
Adjustment Suggestion some actions of the MS, which results in the waste of system resources.
Adjust the value of N3105 appropriately according to the actual situation
of the network (for example, radio interface quality, transmission link
quality, and the factor of the MS itself) to reduce the number of exception
TBF releases caused by N3105 overflow.

Change Mode Offline

Related features None

Related Parameters None

Relationship None

Related Interfaces Um

Impact on Equipment 0

Impact on service 0

Negotiation With CN NO

OMC->GERAN Subnetwork ID->BSC Managed Element ID->Config Set


OMC Access Path
ID->BSC Function ID->GPRS Other Parameters 1

Parameter Modifying
Version None

2-230

SJ-20110531095035-017|2012-09-07 (R1.5) ZTE Proprietary and Confidential


Chapter 2 BSC Function Parameters

Parameter Modifying
Detail None

2.12 GPRS Other Parameters 2


2.12.1 NACC support (NACCSupport)
Full Name NACC support

Abbreviation NACCSupport

3GPP Name NACC

3GPP Reference 3GPP TS44.060 V5.19.0

On the MS side, the Network Assisted Cell Change (NACC) function is a


part of GERAN feature package 1. When this function is supported,
1, the MS can receive system information needed for accessing the
target cell in packet transmission state.
2, the MS informs the network side about the cell change decision in
CCN mode.
Generally, NACC and CCN mode are used together.
At the network side, NACC means that: