ZXUR 9000 UMTS (V4.12.10) Radio Network Controller Radio Parameter Reference_522769

CoverOperatorLOGOZXUR 9000 UMTS Radio ParameterVersion: RNCV4.12.10

IntroductionIntroduction1, Manual DescriptionThis document lists and gives information about ZTE UMTS Radio Network Parameters. It contains the description of the parameter, such as name, unit, value, range, default value, OMC Access path and etc. 2, Structure Sheet of Radio Parameters gives information for all parameters. The following information is presented for each parameter in Radio Parameters Sheet.

3, Intended AudienceNetwork plannersField engineersSystem engineersShift operatorsColumn Name In Radio Network Parameters sheetColumn DescriptionManaged ObjectManaged object class the parameters belongs to.Logical NameParameter Name defined in Managed Object3GPP NameParameter name which is defined in 3GPP3GPP ProtocolIndication which 3GPP protocol defines the parameterGUI NameOMC GUI name of the parameterParameter DescriptionA brief introduction of the parameterInstanceThe instance for which the parameter is configured.Related FGThe Feature Guide Doc in which the parameter is introducedValue Range and StepThe value range and step of the parameterUnitThe value unit of the parameterDefault ValueThe default value, as initially set by the system, if not explicitly set at MO creation.Related ParametersThe related parametersRestriction with Related ParametersDefine the relationship with the related parametersTYPEThe parameter is divided into the following four category:Fixed: the parameter value can be set default and need not adjust normally;Fixed-keep monitoring: the parameter value can be initially set default and adjust later according to network performance;Network Planing&Optimization: the value is set according to Network planning and optimization;Don't Care: the parameter need not care ;Negotiation With CNIndication whether the parameter should negotiate with core network settingFunction SwitchIndication whether the parameter is a switch parameterConfiguration Rule and Adjustment SuggestionA brief configuration rule introduction for the parameterDefault Value Configuration ReasonThe reason for the default value settingChange take effectIndicate when the new value will take effect after the parameter value is modifiedService or node impactIndicate whether the service or node is affected when the parameter valued is modifiedEquipment Impaction LevelThe equipment impaction when the parameter value is modified can be divided into four level according to the object impacted0: indicate no impaction when the parameter is modified1: indicate impaction on the cell when the parameter is modified2: indicate impaction on the nodeb when the parameter is modified3: indicate impaction on the RNC when the parameter is modifiedService Impaction LevelThe service impaction when the parameter value is modified can be divided into four level0: indicate no impaction on the active user and idle user when the parameter is modified1: indicate impaction on the idle user but no impaction on the active user2: indicate no impaction on the idle user and impaction on the active user. The ongoing service will interrupt but the service can be resume in short time (60s) for example the user can reinitialize the service at once; 3: indicate impaction on the idle user and the active user. The network service will interrupt for some time and will resume laterHow to ImpactThe detail description of the impaction after the parameter value is modifiedAccessIndication whether the parameter can be read (Read), written (Write) or modified after created (Restricted)OMC Access pathPath for how to Access the parameter in OMCParameter Modifying VersionWhether this parameter is modified in this versionParameter Modifying DetailModification details of this parameter in this version

&L&G&R&10Document Title&L&10ZTE Confidential Proprietary&C&10&A&R&10&P/&N

MO DescriptionAbbreviationManaged ObjectsDescriptionManagedElementManaged ElementThis managed element needs to be configured with a netwrok element (such as single module XX, and dual-module XX+YY).URncFunctionUMTS Logical Function ConfigurationThis managed element indicates the parent node of RNC functional configuration. It needs to be configured with protocol parameters.URncInfoExtended Info of RNCThis managed element indicates the extended information of RNC.UQosFunctionQOS FunctionThis managed element indicates the virtual node of Qos function.UBasPriQos Basic ConfigurationThis managed element indicates the parameter configuration information related to basic priorities.USchPriMappingProfileScheduling Priority Mapping Relationship ProfileThis managed element indicates the profile of scheduling priority.USchPriMappingScheduling Priority Mapping RelationshipThis managed element indicates the configuration information of scheduling priority.UAppPriMappingProfileApplication Priority Mapping Relationship ProfileThis managed element indicates the profile of application priority.UAppPriMappingApplication Priority Mapping RelationshipThis managed element indicates the configuration information of application priority.UBPriAcProfileAccess Control Profile Related to Basic PriorityThis managed element indicates the access control profile related to basic priorities.UBPriAcAccess Control Related to Basic PriorityThis managed element indicates the access control relationship related to basic priorities.UTbTypeProfileTransport Bearer Type Profile Related to Basic PriorityThis managed element indicates the profile of transport bearer types and I/B transport preserved bandwidth that are related to basic priorities.UTbTypeTransport Bearer Type Related to Basic PriorityThis managed element indicates the transport bearer types and I/B transport preserved bandwidth that are related to basic priorities.UDedSrvTbProfileDedicated Service Transport Bearer Qos ProfileThis managed element indicates the profile of dedicated services and transport Qos configuration.UDedSrvTbDedicated Service Transport Bearer Qos ConfigurationThis managed element indicates the corresponding relationship between dedicated services and Qos configuration.UPlmnSpecFunctionPlmn Specific FunctionThis managed element indicates the common PLMN information shared with this RNC. It is a virtual node of radio services.UBasPriMappingBasic Priority Mapping RelationshipThis managed element indicates the mapping relationship among ARP, THP, Traffic Class, and basic priorities.UDpiDrbcDynamic Radio Bearer Control Information of DPI ServiceThis managed element indicates the Dynamic Radio Bearer Control (DRBC) policy of DPI application services related to PLMN.USrvBasedHoHandover Configuration Based on ServiceThis managed element indicates the handover policy based on services when network elements are under the single-module and dual-module conditions.UIuCnstIu Interface Timers and Constants InformationThis managed element indicates the Iu-interface timers and constants information related to PLMN.UCnInfoCN NAS System InformationThis managed element indicates the CN NAS information related to PLMN.ULogicalRncLogic RNC ConfigurationThis managed element indicates the global RNC configuration information related to PLMN.ULogicalCellLogic Cell ConfigurationThis managed element indicates such information as the DSAR parameter in a cell related to PLMN, and the Qos priority index.ULogicalIubLinkLogic Iub Link ConfigurationThis managed element indicates such information as the CE parameter in a Node B related to PLMN, and the Qos index transmitted.ULogicalIurQosQos Configuration Related to Logical Iur LinkThis managed element indicates the transmitted Qos index in the adjacent RNC related to PLMN.UMbmsSaMBMS Service Area ConfigurationThis managed element indicates the MBMS service area information.UMbmsPLFreqMBMS Preferred Frequency Layer ConfigurationThis managed element indicates the serving cell information of the preferential frequency layer at the MBMS service area.UMbmsNPLFreqMBMS Non Preferred Frequency Layer ConfigurationThis managed element indicates the serving cell information of the non-preferential frequency layer at the MBMS service area.USnacLAC and SNAC InformationThis managed element indicates the relationship between LAC and SNAC when CN is not shared across the network.UHspaHspa ConfigurationThis managed element indicates the global information of HSPA.UCommEdchCommon EDCH ConfigurationThis managed element indicates the global information of common EDCH.UDrbcProfileDynamic Radio Bearer Control Information ProfileThis managed element indicates the configuration information of dynamic radio bearer control related to PLMN.UDrbcDynamic Radio Bearer Control InformationThis managed element indicates the configuration information of dynamic radio bearer control related to PLMN.UMbmsMBMS ConfigurationThis managed element indicates the global configuration information of MBMS.UDpiBasPriMappingDPI Basic Priority Mapping RelationshipThis managed element indicates the mapping relationship among basic priorities when the application DPI is obtained after the priority of application services is mapped to its basic priorities.UImsiSnacFilterUser Authorized PLMN+SNAC InformationThis managed element indicates the relationship between two managed objects (PLMN+ extended code, and PLMN+SNAC) authorized to users.UMRMR ConfigurationThis managed element indicates the switch parameter of MR functions.UGloAcGlobal Access Control InformationThis managed element indicates the global configuration information of access control.UUeCnstUE Timers and Constants InformationThis managed element indicates the UE timers and constants information.UAppSrvTypeApplication Service Type ConfigurationThis managed element indicates the configuration information related to application service types.UQChatQChat Service ConfigurationThis managed element indicates the global configuration of Qchat services.UWhiteImsiListUser Configuration in White ListThis managed element indicates the user configuration in the white list.UDtxDrxProfileUE DTX/DRX ProfileThis managed element indicates the configuration profile discontinuously sent by and received by the UE in HSPA+.UDtxDrxUE DTX/DRX ConfigurationThis managed element indicates the table of configuration information discontinuously sent by and received by the UE in HSPA+.USrvFunctionService FunctionThis managed element indicates the container of information tables related to a service sub-category.USubSrvService Basic ConfigurationThis managed element indicates the functional node information of a service subtype.USrvPcProfilePower Control Profile Related to ServiceThis managed element indicates the container of information tables related to the power control of a service subtype.USrvPcPower Control Related to ServiceThis managed element indicates the power control information related to a service subtype.USrvDivPcPower Control Related to Service and Diversity ModeThis managed element indicates the power control information related to service subtypes and diversities.UWhiteSrvPcPower Control Related to Service for White ListThis managed element indicates the power control information related to dedicated service subtypes of users that are added to the white list.UTrvMeasProfileTraffic Volume Measurement ProfileThis managed element indicates the profile of traffic measurement.URachEvtUeTrvUE Traffic Volume Event Measurement Configuration for RACHThis managed element indicates the event measurement of UP traffic on RACH.URachPrdUeTrvUE Traffic Volume Period Measurement Configuration for RACHThis managed element indicates the periodical measurement of UE traffic on RACH.UFachEvUpTrvUP Traffic Volume Event Measurement Configuration for FACHThis managed element indicates the event measurement of UP traffic on RACH.UDchEvUeTrvUE Traffic Volume Event Measurement Configuration for DCHThis managed element indicates the event measurement of UE traffic on DCH.UDchEvUpTrvUP Traffic Volume Event Measurement Configuration for DCHThis managed element indicates the event measurement of UP traffic on DCH.UDchPrdUeTrvUE Traffic Volume Period Measurement Configuration for DCHThis managed element indicates the periodical measurement of UE traffic on DCH.UDedSHsdschEvUpTrvUP Traffic Volume Measurement Configuration Number for Streaming Class on HS-DSCHThis managed element indicates the event measurement of UP traffic on HS-DSCH.UDedIBHsdschEvUpTrvUP Traffic Volume Measurement Configuration for Interactive and Background Class on HS-DSCHThis managed element indicates the event measurement of UP background-and-interactive services on HS-DSCH.UComHsdschEvUpTrvUP Traffic Volume Measurement Configuration for HS-DSCH in CELL_FACHThis managed element indicates the event measurement of UP traffic in the CELL_FACH state on HS-DSCH.UETTIEdchEvUpTrvUP Throughput Event Measurement Configuration for E-TTI SwitchingThis managed element indicates the event measurement of UP traffic switched by ETTI on E-DCH.UDedEdchEvUpTrvUP Traffic Volume Measurement Configuration for E-DCHThis managed element indicates the event measurement of UP traffic on E-DCH.UComEdchEvUpTrvUP Traffic Volume Measurement Configuration for E-DCH in CELL_FACHThis managed element indicates the event measurement of UP traffic in the CELL_FACH state on E-DCH.UEdchtoDchUpTrvE-DCH Throughput Measurement Configuration for HS-DSCH/E-DCH to HS-DSCH/DCH SwitchingThis managed element indicates the E-DCH throughput measurement configuration for HS-DSCH/E-DCH to HS-DSCH/DCH switching.UIntraMeasProfileIntra-frequency Measurement ProfileThis managed element indicates the intra-frequency measurement profile.UIntraMeasSrvSpecIntra-frequency Measurement Configuration Related to Traffic CategoryThis managed element indicates the intra-frequency measurement related to service types.UIntraEcNoEvMeasUEIntra-frequency Event Measurement Configuration for CPICH Ec/NoThis managed element indicates the intra-frequency measurement of the Ec/No of events that are related to service types.UIntraRscpEvMeasUEIntra-frequency Event Measurement Configuration for CPICH RSCPThis managed element indicates the intra-frequency measurement of the RSCP of events that are related to service types.UIntraMeasNoSrvSpecIntra-frequency Measurement Configuration Unrelated to Traffic CategoryThis managed element indicates the intra-frequency measurement unrelated to service types.UIntraEcNoPrdMeasUEIntra-frequency Period Measurement Configuration for CPICH Ec/NoThis managed element indicates the intra-frequency measurement of the Ec/No of periods that are related to service types.UIntraRscpPrdMeasUEIntra-frequency Period Measurement Configuration for CPICH RSCPThis managed element indicates the intra-frequency measurement of the RSCP of periods that are unrelated to service types.UIntraEcNoEvMeasForDDetected Set Measurement Configuration for CPICH Ec/NoThis managed element indicates the intra-frequency measurement of the Ec/No of detection-set events that are unrelated to service types.UIntraRscpEvMeasForDDetected Set Measurement Configuration for CPICH RSCPThis managed element indicates the intra-frequency measurement of the RSCP of detection-set events that are unrelated to service types.UInterMeasProfileUE Inter-frequency Measurement ProfileThis managed element indicates the intra-frequency measurement profile.UInterMeaSrvSpecInter-frequency Measurement Configuration Related to Traffic CategoryThis managed element indicates the intra-frequency measurement related to service types.UInterEcNoEvMeasforUUE Inter-frequency Event Measurement Configuration for CPICH Ec/No(UTRAN)This managed element indicates the inter-frequency measurement (UTRAN) of the Ec/No of events that are related to service types.UInterRscpEvMeasforUUE Inter-frequency Event Measurement Configuration for CPICH RSCP(UTRAN)This managed element indicates the inter-frequency measurement (UTRAN) of the RSCP of events that are related to service types.UInterEcNoEvMeasforGUE Inter-frequency Event Measurement Configuration for CPICH Ec/No(GSM)This managed element indicates the inter-frequency measurement (GSM) of the Ec/No of events that are related to service types.UInterRscpEvMeasforGUE Inter-frequency Event Measurement Configuration for CPICH RSCP(GSM)This managed element indicates the inter-frequency measurement (GSM) of the RSCP of events that are related to service types.UInterEcNoEvMeasforEUE Inter-frequency Event Measurement Configuration for CPICH Ec/No(EUTRAN)This managed element indicates the inter-frequency measurement (EUTRAN) of the Ec/No of events that are related to service types.UInterRscpEvMeasforEUE Inter-frequency Event Measurement Configuration for CPICH RSCP(EUTRAN)This managed element indicates the inter-frequency measurement (EUTRAN) of the RSCP of events that are related to service types.UInterMeasNoSrvSpecInter-frequency Measurement Configuration Unrelated to Traffic CategoryThis managed element indicates the inter-frequency measurement unrelated to service types.UInterEcNoPrdMeasUEInter-frequency Period Measurement Configuration for CPICH Ec/NoThis managed element indicates the intra-frequency measurement of the Ec/No of periods that are unrelated to service types.UInterRscpPrdMeasUEInter-frequency Period Measurement Configuration for CPICH RSCPThis managed element indicates the intra-frequency measurement of the RSCP of periods that are unrelated to service types.URatMeasProfileInter-RAT Measurement ProfileThis managed element indicates the inter-system measurement profile.URatMeasSrvSpecInter-RAT Measurement Configuration Related to Traffic CategoryThis managed element indicates the inter-system measurement related to service types.URatEcNoEvMeasforGUE Inter-RAT Event Measurement Configuration for CPICH Ec/No(GSM)This managed element indicates the inter-system measurement (GSM) of the Ec/No of events that are related to service types.URatRscpEvMeasforGUE Inter-RAT Event Measurement Configuration for CPICH RSCP(GSM)This managed element indicates the inter-system measurement (GSM) of the RSCP of events that are related to service types.URatEcNoEvMeasforEUE Inter-RAT Event Measurement Configuration for CPICH Ec/No(EUTRAN)This managed element indicates the inter-system measurement (EUTRAN) of the Ec/No of events that are related to service types.URatRscpEvMeasforEUE Inter-RAT Event Measurement Configuration for CPICH RSCP(EUTRAN)This managed element indicates the inter-system measurement (EUTRAN) of the RSCP of events that are related to service types.URatMeasNoSrvSpecInter-RAT Measurement Configuration Unrelated to Traffic CategoryThis managed element indicates the inter-system measurement unrelated to service types.URatEcNoPrdMeasUEInter-RAT Period Measurement Configuration for CPICH Ec/NoThis managed element indicates the inter-system measurement of the Ec/No of periods that are unrelated to service types.URatRscpPrdMeasUEInter-RAT Period Measurement Configuration for CPICH RSCPThis managed element indicates the inter-system measurement of the RSCP of periods that are unrelated to service types.UUeIntMeasProfileUE Internal Measurement ProfileThis managed element indicates the internal measurement relationship among a set of UEs, including the Tcp/RTT event measurement and RTT period measurement.UAmrEvtTPUeIntUE Transmitted Power Event Measurement Configuration for AMRThis managed element indicates measurements used for AMR adjustment. Those measurements are the internal measurement relationship of UE transmitted power.UPsEvtTPUeIntUE Transmitted Power Event Measurement Configuration for PSThis managed element indicates measurements used by PS services. Those measurements are the internal measurement relationship of UE transmitted power.UHoEvtTPUeIntUE Transmitted Power Event Measurement Configuration for HandoverThis managed element indicates measurements used for triggering handover. Those measurements are the internal measurement relationship of UE transmitted power.UPrdRttUeIntUE Rx-Tx Time Difference Period Measurement Configuration for LocationThis managed element indicates measurements used for location. Those measurements are the periodical internal measurement relationship of UE Rx-Tx time difference.UEvtRttUeIntUE Rx-Tx Time Difference Event Measurement Configuration for UTRANThis managed element indicates the internal measurement relationship of UTRAN judgement events of UE Rx-Tx time difference.URlEvtRttUeIntUE Rx-Tx Time Difference Event Measurement Configuration for RL Timing AdjustmentThis managed element indicates measurements used for radio-link timing adjustment. Those measurements are the internal measurement relationship of UE Rx-Tx time difference.UPwrLimTPUeIntUE Transmitted Power Event Report for Power Limitation JudgementThis managed element indicates UE transmitted power event report for power limitation judgement.UNbComMeasProfileNodeB Common Measurement ProfileThis managed element indicates the common measurement relationship among a set of Node Bs, including the measurement of periodical RTWP/TCP/TUtranGps/HRP/NHTCP/RSEPS, and the measurement of changed TUtranGps.UNbComMeasNodeB Common Measurement ConfigurationThis managed element indicates the measurement of periodical RTWP/TCP/TUtranGps/HRP/NHTCP/RSEPS, and the measurement of changed TUtranGps.UNbDedMeasProfileNodeB Dedicated Measurement ProfileThis managed element indicates the dedicated measurement profile of a set of Node Bs.UNbDedMeasNodeB Dedicated Measurement ConfigurationThis managed element indicates the dedicated measurement relationship of Node Bs.UGbrResLimitProfileLimiting HSDPA GBR Resource Consumption ProfileThis managed element indicates the parameter information profile of HSDPA GBR resource consumption limiting.UGbrResLimitLimiting HSDPA GBR Resource Consumption ConfigurationThis managed element indicates the parameter information of HSDPA GBR resource consumption limiting.UCfnOffsetCFN Offset ConfigurationThis managed element indicates the CFN offset configuration.ULocationAreaLocation Area ConfigurationThis managed element indicates the LA information of an RNC. The maximum number of LAs is 100.URoutingAreaRouting Area ConfigurationThis managed element indicates the RA information of an RNC. The maximum number of SAs is 2560.UServiceAreaService Area Configuration in CS+PS DomainThis managed element indicates the SA information of an RNC.UServiceAreaBcService Area Configuration in BC DomainThis managed element indicates the SA information in the BC domain of an RNC.UUtranRegAreaUTRAN Registration AreaThis managed element indicates the cell information of a URA.UIubLinkIub Link ConfigurationThis managed element indicates the configuration information of Node Bs of an RNC.UIurLinkIur Link ConfigurationThis managed element indicates the configuration information of Node Bs of an RNC.UUtranCellFDDUTRAN CellThis managed element indicates the serving cell information and configuration parameters defined in the 3GPP UTRAN resource information model.UCelInfoFDDExtended Info of UTRAN CellThis managed element indicates the supplementary information of a cell.UUtranRelationNeighbouring CellThis managed element indicates the relationship of the internal and external cells of UTRAN.UGsmRelationGSM Neighbouring CellThis managed element indicates the relationship of UTRAN cells and external GSM cells.UEUtranRelationEUTRAN Neighbouring CellThis managed element indicates the adjacent relationship of UTRAN cells and EUTRAN cells. It is configured with protocol parameters.UENbrBlkListEutran Neighbouring Cell Black ListThis managed element indicates the black list of Eutran Neighbouring Cell.UAichAICH ConfigurationThis managed element indicates the AICH configuration.UPrachPRACH ConfigurationThis managed element indicates the PRACH configurationUSccpchSCCPCH ConfigurationThis managed element indicates the SCCPCH configuration.UPichPICH ConfigurationThis managed element indicates the PICH configuration.UMichMICH ConfigurationThis managed element indicates the MBMS configuration.UScpichSCPICH ConfigurationThis managed element indicates the SCPICH configuration.UCelSelCell Selection and Reselection InformationThis managed element indicates the relationship between cell selection and reselection.UPriSelCell Reselection Frequency and Priority InformationThis managed element indicates the cell reselection frequency and priority information.UCHspaHspa Configuration In A CellThis managed element indicates the HSPA configuration in a cell.UCMbmsMBMS Configuration In A CellThis managed element indicates the MBMS configuration in a cell.UEFachEFACH ConfigurationThis managed element indicates the EFACH configuration.UPlBalLoad Balance InformationThis managed element indicates the power load balance information.ULdCtrlLoad Control InformationThis managed element indicates the load control relationship.UCMRCell MR ConfigurationThis managed element indicates the parameter of the MR functional switch that is related to cells.UExternalRncFunctionExternal RNC FunctionThis managed element indicates the adjacent RNC of this RNC.UExternalUtranCellFDDExternal UTRAN CellThis managed element indicates the information about adjacent cells that are not belong to this RNC. It is configured with protocol parameters.UExternalGsmCellExternal GSM CellThis managed element indicates the cell configuration information of GSM. It is configured with protocol parameters.UExternalENBFunctionExternal ENodeB FunctionThis managed element indicates the NodeB configuration information of EUTRAN.UExternalEUtranCellFDDExternal EUTRAN Cell FDDThis managed element indicates the cell configuration information of EUTRAN.UExternalEUtranCellTDDExternal EUTRAN Cell TDDThis managed element indicates the cell configuration information of EUTRAN.UCNPoolRoutingFunctionCS/PS Pool Routing FunctionThis managed element indicates the configuration for the route information of CS/PS POOL.UIDNNSRoutingConfiguration of IDNNS route to Cs/Ps PoolThis managed element indicates the configuration for the route information from IDNNS to CS/PS POOL.UIMSIRoutingConfiguration of IMSI route to Cs/Ps PoolThis managed element indicates the configuration for the route information from IMSI to CS/PS POOL.UImeiBlkListImei for Black ListThis managed element indicates the black list of IMEI.UImeiTacSPIDImei TAC List for SPIDThis managed element indicates the IMEI TAC list for SPID.UDePriRAN Priority When UE in Dedicated StateThis managed element indicates the RAN priority when UE in dedicated state.UMPOProfileHS-PDSCH Measurement Power Offset ProfileThis managed element indicates the HS-PDSCH measurement power offset profile.UMPOHS-PDSCH Measurement Power Offset ConfigurationThis managed element indicates the HS-PDSCH measurement power offset configuration.

Radio ParametersManaged ObjectLogical Name3GPP Name3GPP ReferenceGUI NameParameter DescriptionInstanceRelated FGValue Range and StepUnitDefault ValueRelated ParameterRestriction with Related ParametersTypeNegotiation With CNFunction SwitchConfiguration Rule and Adjustment SuggestionDefault Value Configuration ReasonChange take effectService or Node ImpactEquipment Impaction LevelService Impaction LevelHow to ImpactAccessOMC Access pathParameter Modifying VersionParameter Modifying DetailURncFunctionURncFunctionN/AN/ARNC Configuration Object IDThis parameter is RNC Configuration Object IDRNCBasic Identification Parameter0..2147483647N/AN/AN/AN/ANetwork Planing&OptimizationNoNoParameter Function: This parameter is RNC Configuration Object ID.It is unique under its parent object.N/Acan not be modifiedNo00N/ARestrictedGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctiondescriptionN/AN/ADescriptionThe description of Object and defined by MO designer, Generally it is composed of some business key, such as "RNCID=1001".N/AN/A300 charN/AN/AN/AN/AFixedNoN/ADefined By MO ModelN/AN/ANo00N/AReadGUI: Managed Element->UMTS Logical Function ConfigurationN/AN/AURncFunctionuserLabelN/AN/AUser LabelUser Friendly NameN/AN/A80 charN/AN/AN/AN/AFixedNoN/AUser Planning DataN/AN/ANo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationN/AN/AURncFunctionrncidN/AN/ARNC IdentityThe parameter is the network element identifier and coded in one NE type. When NE type is MSCSERVER, SGSN, MSCSERVER& SGSN, the value range is 0~4095. MCC[]+MNC[]+NeId[] can't be same for different CN nodes.When NE type is alone MGW, the value range is 4096~65535.When NE type is RNC, the value range is 0~4095.When NE type is NODEB, the value range is 0~65535.When NE type is BME, the value range is 0~65535.NE OfficeIu Flex0..4095N/AN/APLmnNum of rncNeInfo, MCC[8] of rncNeInfo, MNCBcdCodeLen[8] of rncNeInfo, MNC[8] of rncNeInfo, NeId[8] of rncNeInfoMCC[8], MNCBcdCodeLen[8], MNC[8], NeId[8] is a list. the max element number of list is 8. the valid element number is PlmNum .Network Planing&OptimizationNoNofunction of this parameter: Configure NEID of NEFactors of consideration: it's configured according to the netork planning resultN/ANew usersNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctionsharedNetModeN/AN/AShared Network ModeThis parameter indicates the shared network mode. There are two modes of shared network: GWCN (Gateway Core Network) and MOCN Multi-Operator Core Network. Both radio access network and core network are shared in GWCN mode. Only radio access network is shared by in MOCN mode.RNCRAN Sharing0: GWCN1: MOCN2: Multi Plmn0xFF: No Shared NetworkN/A0xffN/AN/ANetwork Planing&OptimizationNoNoFunction of this parameter: configure the network sharing modeFactors of consideration: network sharing mode . MOCN: support shared carrier sharing and dedicated carrier sharing, RNC connect multi operator CN, and RNC select operator for non-supporting UEGWCN: support shared carrier sharing and dedicated carrier sharing, The CN can be shared by multi operator, and CN select operator for non-supporting UEMultiPlmn: only support dedicated carrier sharing, RNC route UE to the operator the cell belong to0xFF: network sharing is not used. the value must be 0xFF when the network sharing feature is not licensedThe default value is decided by the factor that no network sharing is used in most networksNew usersNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationN/AN/AURncFunctionplmnSelectMethodN/AN/APlmn Select Method for MOCN Network SharingThis parameter indicates the method of PLMN selection , when MOCN is used for network sharingRNCRAN Sharing0: IMSI-based CS & PS Coordination 1: Random SelectionN/A0SharedNetMode of rncFunctionN/AFixed-keep monitoringNoNoParameter Function: This parameter indicates the method of PLMN selection , when MOCN is used for network sharingFactors of consideration: when MOCN is used for network sharing, if PS and CS domain registration coordination is implemented by CN, this parameter is set 1; otherwise, this parameter is set 0in most networks, CN don't implemented PS and CS domain registration coordinationNew connectionNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctioninitRrcOnDchN/AN/AType of Transport Channel for Initial RRC Connection SetupThis parameter indicates the type of transport channel and signalling rate for initial RRC connection setup.RNCDynamic Radio Bearer Control0: Forced to CELL_DCH and Using DCH/DCH with Low Rate Signaling1: Forced to CELL_DCH and Using DCH/DCH with 13.6k Signaling2: Forced to CELL_FACH3: Not Forced, Using Low Rate Signaling on Cell_DCH State4: Not Forced, Using DCH/DCH with 13.6k Signaling on Cell_DCH State5: (Forced to CELL_DCH and Using DCH/DCH with 27.2k Signaling6: Not Forced, Using DCH/DCH with 27.2k Signaling on Cell_DCH State7: Forced to HSPA8: Not Forced, Using HSPA signaling on CELL_DCH stateN/A1N/AN/AFixed-keep monitoringNoNoFunction: Used for indicating the type of transport channel and signalling rate for initial RRC connection setup.Configuration Rule: It needs to consider the utilization of radio resource and the call time delay.Adjustment Suggestion: High rate signalling can effective speed up the establishment process of RRC connection, it can decrease the call time delay, but it also occupies more radio resource than low rate signalling. It is recommended to use high rate signalling because the alone signalling process is very short.The reason of the parameter's default value is to try best to decrease the call time delay.At next useNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationN/AN/AURncFunctiongpsInfoRootN/AN/AGPS Information RootThis parameter indicates where RNC can get GPS information from.RNCLocation Service0: Self1: Neighbouring RNC; 2: Exterior NetworkN/A0GpsInfoRoot, GpsCardTypeOnly when GpsInfoRoot set 0 (self) , GpsCardType is valid.FixedNoNoIt is used in AGPS positioning. It is configured according to AGPS information attainment from RNC or reference network.N/Anot updtae except power onNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctioncellLdInfoVldTimN/ATS 25.413Duration of Valid Cell Load InfoThis parameter indicates the duration of the inter-sys cell's load information which is valid to use.before updating.RNCHandover Control0..65535, Step 1s300N/AN/AFixed-keep monitoringNoNowhen this parameter is configured, it needs to think of the Load information Validity in the configured duration.If the duration is too long, the load information validity is not guaranteed, and if the duration is too short, the load information can't be fully used.consider both the Validity and synchronization frequency of the cell load.At next use (i.e., shall not affect ongoing connections)No00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctionnonCMaxPduSizeMaximum MAC-d PDU Size ExtendedTS 25.423; TS 25.433Downlink Non-Conversational Service Maximum MAC-d PDU Size ExtendedThis parameter indicates the downlink Non-Conversational service maximum size in octets of the MAC level PDU when an extended MAC level PDU size is required.RNCHSPA Evolution1..1505, Step 1bytes600N/AN/AFixed-keep monitoringNoNoFunction: Non-Conversational service Maximum MAC-d PDU Size ExtendedConfiguration Rule: It needs to consider the header consumption and the quality of service.The value of the parameter is larger, the header consumption is smaller, and it save resource; but it is easier to result in PDU transmission mistake when the radio channel quality becomes bad.The value of the parameter is smaller, the header consumption is larger, and it's a waste of resource.The reason of the parameter's default value is to consider the header consumption and the quality of service.New service setup or reconfigurationNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationN/AN/AURncFunctioncMaxPduSizeMaximum MAC-d PDU Size ExtendedTS 25.423; TS 25.433Downlink Conversational Service Maximum MAC-d PDU Size ExtendedThis parameter indicates the downlink Conversational service maximum size in octets of the MAC level PDU when an extended MAC level PDU size is required.RNCHSPA Evolution1..1505, Step 1bytes65N/AN/AFixed-keep monitoringNoNoFunction: Conversational service Maximum MAC-d PDU Size ExtendedConfiguration Rule: It needs to consider the header consumption and the quality of service.The value of the parameter is larger, the header consumption is smaller, and it save resource; but it is easier to result in PDU transmission mistake when the radio channel quality becomes bad.The value of the parameter is smaller, the header consumption is larger, and it's a waste of resource.The reason of the parameter's default value is to consider the header consumption and the quality of service.ImmediatelyNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctioncMaxUlPduSizeLargest UL RLC PDU sizeTS 25.331Uplink Conversational Service Maximum Uplink RLC PDU SizeThis parameter indicates the Uplink Conversational service maximum size in octets of the uplink RLC PDU in the flexible RLC PDU size mode.RNCHSPA Evolution2..1505, Step 1bytes124CMinUlPduSize of rncFunctionCMaxUlPduSize > CMinUlPduSizeFixed-keep monitoringNoNoFunction: Uplink conversational service maximum MAC-d PDU size extendedRelated Factor: The header consumption and the quality of service.The value of the parameter is larger, the header consumption is smaller, and it saves resources; but it is easier to result in PDU transmission mistake when the radio channel quality becomes bad.The value of the parameter is smaller, the header consumption is larger, and it's a waste of resources.The header consumption and the quality of service are considered to define this parameter.New connectionNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctioncMinUlPduSizeMinimum UL RLC PDU sizeTS 25.331Uplink Conversational Service Minimum Uplink RLC PDU SizeThis parameter indicates the Uplink Conversational service minimum size in octets of the uplink RLC PDU in the flexible RLC PDU size mode.RNCHSPA Evolution2..1505, Step 1bytes7CMaxUlPduSize of rncFunctionCMaxUlPduSize > CMinUlPduSizeFixed-keep monitoringNoNoFunction: Uplink conversational service minimum MAC-d PDU size extendedRelated Factor: The header consumption and the quality of service.The value of the parameter is larger, the header consumption is smaller, and it saves resources; but it is easier to result in PDU transmission mistake when the radio channel quality becomes bad.The value of the parameter is smaller, the header consumption is larger, and it's a waste of resources.The header consumption and the quality of service are considered to define this parameter.New connectionNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctionnonCMaxUlPduSizeLargest UL RLC PDU sizeTS 25.331Uplink Non-Conversational Service Maximum Uplink RLC PDU SizeThis parameter indicates the Uplink Non-Conversational service maximum size in octets of the uplink RLC PDU in the flexible RLC PDU size mode.RNCHSPA Evolution2..1505, Step 1bytes244NonCMinUlPduSize of rncFunctionNonCMaxUlPduSize > NonCMinUlPduSizeFixed-keep monitoringNoNoFunction: Uplink non-conversational service maximum MAC-d PDU size extendedRelated Factor: The header consumption and the quality of service.The value of the parameter is larger, the header consumption is smaller, and it saves resources; but it is easier to result in PDU transmission mistake when the radio channel quality becomes bad.The value of the parameter is smaller, the header consumption is larger, and it's a waste of resources.The header consumption and the quality of service are considered to define this parameter.New connectionNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctionnonCMinUlPduSizeMinimum UL RLC PDU sizeTS 25.331Uplink Non-Conversational Service Minimum Uplink RLC PDU SizeThis parameter indicates the Uplink Non-Conversational service minimum size in octets of the uplink RLC PDU in the flexible RLC PDU size mode.RNCHSPA Evolution2..1505, Step 1bytes21NonCMaxUlPduSize of rncFunctionNonCMaxUlPduSize > NonCMinUlPduSizeFixed-keep monitoringNoNoFunction: Uplink non-conversational service minimum MAC-d PDU size extendedRelated Factor: The header consumption and the quality of service.The value of the parameter is larger, the header consumption is smaller, and it saves resources; but it is easier to result in PDU transmission mistake when the radio channel quality becomes bad.The value of the parameter is smaller, the header consumption is larger, and it's a waste of resources.The header consumption and the quality of service are considered to define this parameter.New connectionNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctionharqRvConfigHARQ RV Configuration; HARQ Info for E-DCHTS 25.331; TS 25.433; TS25.423HARQ RV ConfigurationThis parameter indicates the RV configuration selected by RNC when the E-DCH Harq Combining Capability IE in AUDIT RESPONSE returned by NodeB takes the value of 'IR and Chase Combining Capable'RNCHSUPA Introduction0: RV01: RV TableN/A1N/AN/AFixedNoNoFunction: This parameter indicates the RV configuration selected by RNC when the E-DCH Harq Combining Capability IE in AUDIT RESPONSE returned by NodeB takes the value of 'IR and Chase Combining Capable'.Configuration Rule: According to the gain comparison between CC and IR.It is concluded by simulation that using IR obtains more retransmission combination gain than using CC.It is concluded by simulation that using IR obtains more retransmission combination gain than using CC. So default value is set to 'RV Table'.At next use (i.e., shall not affect ongoing connections)No00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationN/AN/AURncFunctionmaxRateWithNVHsN/AN/AMaximum Bit Rate with HS-SCCH Less for Non-VoIP/AMRThis parameter indicates the maximum bit rate with HS-SCCH Less for Non-VoIP/AMR. Non-VoIP/AMR services are allowed to use HS-SCCH Less function only when the following conditions are all satisfied: (1) HS-SCCH Less Switch is "On"; (2) HS-SCCH Less Switch for Non-VoIP/AMR is "On"; (3) The assigned maximum bit rate is less than Max Bit Rate with HS-SCCH Less for Non-VoIP/AMR.RNCHSPA Evolution0: 161: 322: 643: 1284: 2565: 384kbps2N/AN/AFixedNoNoFunction: This parameter indicates the maximum bit rate with HS-SCCH Less for Non-VoIP/AMR. Configuration Rule: Considering together cell and service throughput, gain brought by HS-SCCH Less.If This parameter is set too large, code number will become the bottleneck and transmission power will increase so as to make the user throughput and cell throughput decrease.If the parameter is too small, the advantage of the HS-SCCH less will be not obvious.Considering together cell and service throughput, gain brought by HS-SCCH Less.At next use (i.e., shall not affect ongoing connections)No00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationN/AN/AURncFunctionemgCallRdtSwitchN/AN/AEmergency Call Redirect SwitchThis parameter specifies the RRC Redirect for emergency call function switch.RNCConnection Management0: Off1: OnN/A0N/AN/AFixed-keep monitoringNoYesParameter function: the switch of the emergency call RRC redirection function.Parameter controlling factor: If GSM can provide more accurate location service, this parameter can be set to 1 for higher location quality, or else it shall be set to 0.N/AAt next useNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationN/AN/AURncFunctioninterRatV1V2AmrCutN/AN/AInter-RAT V1+V2 Amr Cut DecisionSpecifies the Amr cut decision when IuUP version including V1+V2 in the inter-RAT caseRNCAMR-NB & AMR-WB1: Cut2: Not CutN/A1N/AN/AFixed-keep monitoringYesNoFunction: This parameter specifies the Amr cut decision when IuUP version including V1+V2 in the inter-RAT case.Configuration Rule: The parameter indicates whether to cut AMR set or not when both Verion1 and Version2 are supported by the CN during the 2G to 3G Relocation procedure.Cutting Amr set is more compatible for inter-RAT cases.Take effect for the next callNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctionintraRatV1V2AmrCutN/AN/AIntra-RAT V1+V2 Amr Cut DecisionSpecifies the Amr cut decision when IuUP version including V1+V2 in the intra-RAT caseRNCAMR-NB & AMR-WB1: Cut2: Not CutN/A2N/AN/AFixed-keep monitoringYesNoFunction: This parameter specifies the Amr cut decision when IuUP version including V1+V2 in the intra-RAT case.Configuration Rule: The parameter indicates whether to cut AMR set or not when both Verion1 and Version2 are supported by the CN in the RAB assignment or intra system Relocation procedure.For intra-RAT cases, usually, the related equipment are our products, so not cutting Amr is selected.Take effect for the next callNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctioncsRrcOnFachSwchN/AN/ASwitch of Non Emergency CS Service Access to CELL_FACH On RRCThis parameter indicates whether non emergency CS service access to CELL_FACH on RRC process. If this switch is " Off" , It means non emergency CS service will not access to FACH/RACH or HS-DSCH/RACH on RRC process.RNCDynamic Radio Bearer Control0: Off1: OnN/A1InitRrcOnDch of rncFunctionWhen InitRrcOnDch is set to 2 (Forced to FACH) , this parameter is invalid.Fixed-keep monitoringNoYesFunction: Switch of Non Emergency CS Service Access to CELL_FACH On RRCConfiguration Rule: It needs to consider the user experience and the successful ratio of RRC connection.The reason of adding the parameter is for IPHONE, if RRC is established on the Cell_FACH state for IPHONE, it will have noise voice when it triggers a CS service and transfers from Cell_FACH to Cell_DCH.To turn on the function, if the admission for RRC connection on DCH is failed, RRC connection is allowed to be established on the Cell_FACH state, and it can increase the successful ratio of RRC connection, but it can't avoid the noise voice for IPHONE.To turn off the function, if the admission for RRC connection on DCH is failed, only emergency RRC connection is allowed to be established on the Cell_FACH state, and it will decrease the successful ratio of RRC connection, but it can avoid the noise voice for IPHONE.The reason of the parameter's default value is to try best to increase the successful ratio of RRC connection.ImmediatelyNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctiont4StpIfMeaActRatN/AN/ATimer for Stopping Inter-frequency Measurement and Activating Inter-RAT MeasurementThis parameter indicates the time interval of issuing inter-frequency measurement and inter-RAT measurement. When RNC issues inter-frequency measurement, the timer is start. If the quality of non-used frequency is bad during the time length indicated by this parameter, RNC will issue inter-RAT measurement if there is an inter-RAT neighboring cell.RNChandover control1..20, Step 1s5N/AN/AFixed-keep monitoringNoNoFunction: inter-frequency measurement timerConfiguration Rule: service performanceWhen IFORRATHOSWCH is "3", If the parameter value is smaller, RNC will stop inter-frequency measurement and start inter-handover easily.adjustment suggestion: For some scenario, UE can't report inter-frequency, then this parameter should be set suitable value, which can handover UE to GSM and avoid call drop.Network planning is taken into account in default value.At next useNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctiondcRedirectStaSwN/AN/ADual Carrier Redirection Strategy SwitchThis parameter indicates DC redirection strategy switch. When the switch is " On" , if UE supports DC and the access cell don't support DC, RNC will redirect UE to other frequency with DC capability via the RRC Connection Reject procedure.RNCload balance0: Off1: OnN/A0N/AN/AFixed-keep monitoringNoYesFunction: Dual Carrier Redirection Strategy Switch.Configuration Rule: To turn on the function, UE can be redirected to adjacent cell that support DC-HSDPA, it can provide better user experience.To turn off the function, UE can't be redirected to adjacent cell that support DC-HSDPA.The parameter should be set based on the actual scene.ImmediatelyNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctionbwOvldRelUeNumN/AN/Athe Release UE Number when Band Exceeds LimitThis parameter indicates the maximum number of UE in a cell whose transport resource will be released while transport path is overload.RNCTransport Resource Release Control0..255N/A5N/AN/AFixedNoNoFunction: This parameter indicates the maximum number of UE in a cell whose transport resource will be released while transport path is overload.Configuration Rule: The parameter should be set according to the actual configuration of the transport resource.The parameter should be set according to the actual configuration of the transport resource.At next usageNo00It will be changed that the maximum number of UE in a cell whose transport resource will be released while transport path is overload.Read/WriteGUI: Managed Element->UMTS Logical Function ConfigurationN/AN/AURncFunctionrrcSetupRetraNumN/AN/AMaximum Number of Retransmissions of the RRC CONNECTION SETUPThe parameter indicates maximum number of retransmissions of the RRC CONNECTION SEUTP messageRNCConnection Management0..10N/A2N/AN/AFixed-keep monitoringNoNOMain function: This parameter indicates the maximum number of retransmissions of the RRC CONNECTION SETUP.Influence factor: The probability of UE receiving RRC CONNECTION SETUP; the number of RRC CONNECTION SETUP message; system cost.The bigger the parameter is, the bigger the number of RRC CONNECTION SETUP message is and the higher the system cost is, However, The probability of UE receiving RRC CONNECTION SETUP and the rate of setting the RRC CONNECTION successfully can be increased.The smaller the parameter is, the smaller the number of RRC CONNECTION SETUP message is and the lower the system cost is, However, The probability of UE receiving RRC CONNECTION SETUP and the rate of setting the RRC CONNECTION successfully can be decreased.If the number of the RNC resent the RRC CONNECTION SETUP message is equal to RrcSetupRetraNum and the RNC hasn't receive RRC CONNECTION SETUP COMPLETE, the RNC consider the RRC CONNECTION SETUP procedure failed.The default value is 2, considering all factors: The probability of UE receiving RRC CONNECTION SETUP; the number of RRC CONNECTION SETUP message; system cost.ImmediatelyNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationN/AN/AURncFunctiontRrcSetupRetranN/AN/AInterval of Retransmission of RRC CONNECTION SETUPThe parameter indicates the interval of retransmission of RRC CONNECTION SETUP message.Start: Transmission of RRC CONNECTION SETUP.Stop: Reception of RRC CONNECTION SETUP COMPLETE.At expiry: Retransmit RRC CONNECTION REQUEST if the times of transmit RRC CONNECTION REQUEST =< RrcSetupRetraNum, else release the RRC connection of UERNCConnection Management0..100, Step 1100ms7N/AN/AFixed-keep monitoringNoNOMain function: This parameter indicates the time gap between current time of sending the RRC CONNECTION SETUP and the retransmissions time.Influence factor: The probability of UE receiving RRC CONNECTION SETUP; the number of RRC CONNECTION SETUP message; system cost.The smaller the parameter is, the bigger the number of RRC CONNECTION SETUP message is and the higher the system cost is, However, The probability of UE receiving RRC CONNECTION SETUP can be increased.The bigger the Main function: This parameter indicates the time gap between current time of sending the RRC CONNECTION SETUP and the retransmissions time.Influence factor: The probability of UE receiving RRC CONNECTION SETUP; the number of RRC CONNECTION SETUP message; system cost.The smaller the parameter is, the bigger the number of RRC CONNECTION SETUP message is and the higher the system cost is, However, The probability of UE receiving RRC CONNECTION SETUP and the rate of setting the RRC CONNECTION successfully can be increased.The bigger the parameter is, the smaller the number of RRC CONNECTION SETUP message is and the lower the system cost is, However, The probability of UE receiving RRC CONNECTION SETUP and the rate of setting the RRC CONNECTION successfully can be decreased.The default value is 700ms, considering all factors: The probability of UE receiving RRC CONNECTION SETUP; the number of RRC CONNECTION SETUP message; system cost.ImmediatelyNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationN/AN/AURncFunctionn308N308TS 25.331Maximum Number of Retransmissions of the RRC CONNECTION RELEASE COMPLETE Message (N308)This parameter indicates the maximum number of retransmissions of the RRC CONNECTION RELEASE COMPLETE.RNCConnection Management1..8N/A1N/AN/AFixedNoNoParameter function: the maximum number of retransmissions of the RRC CONNECTION RELEASE COMPLETE. For details, please refer to "Parameter Description".Parameter controlling factor: the success rate and time delay of the RRC connection release.The larger parameter value helps to increase the success rate of the RRC connection release, but may cause excessive message retransmission in the Uu and increase the time delay of the RRC connection release.The smaller parameter value helps to decrease the Uu messages, decrease the time delay of the RRC connection release and let UE going to IDLE a.s.a.p., but it may decrease the success rate of the RRC connection release.The default value is comprehensively set by the success rate and time delay of the RRC connection release.At CommitNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationN/AN/AURncFunctionnReTranN/AN/AMaximum Number of Retransmissions of the RRC CONNECTION RELEASE MessageThis parameter indicates the maximum number of retransmissions of the RRC CONNECTION RELEASE.RNCConnection Management1..10N/A3N/AN/AFixedNoNOMain function: This parameter indicates the maximum number of retransmissions of the RRC CONNECTION RELEASE.Influence factor: The probability of UE receiving RRC CONNECTION RELEASE; the number of RRC CONNECTION RELEASE message; system cost.The bigger the parameter is, the bigger the number of RRC CONNECTION RELEASE message is and the higher the system cost is, However, The probability of UE receiving RRC CONNECTION RELEASE can be increased.The smaller the parameter is, the smaller the number of RRC CONNECTION RELEASE message is and the lower the system cost is, However, The probability of UE receiving RRC CONNECTION RELEASE can be decreased.If the number of the RNC resent the RRC CONNECTION RELEASE message is equal to NreTran and the RNC doesn't receive RRC CONNECTION RELEASE COMPLETE until waiting for 500ms, and the RNC consider the RRC CONNECTION has released.The default value is considering all factors: The probability of UE receiving RRC CONNECTION RELEASE; the number of RRC CONNECTION RELEASE message; system cost.apply when RNC send RRC CONNECTION RELEASENo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationN/AN/AURncFunctionmaxCsDelayMax CS DelayTS 25.331Max CS DelayThis parameter indicates the time of determining the maximum buffering of the voice frames in PDCP when CS voice maps on HS-DSCH/E-DCH. If data can not be transferred in time when CS counter expires, the data will be discarded.RNCCS over HSPA20..200, step 10ms60N/AN/AFixed-keep monitoringNoNoFunction: Max CS Delay when CS over HSPA.Configuration Rule: It needs to consider the quality of service .This parameter is used to help UE managing the de-jitter buffer.If the value of this parameter is too large, the time of the maximum buffering of the voice frames in PDCP is longer, but because CS service is very sensitive for time delay, it can't guarantee the quality of CS service. If the value of this parameter is too small, the time of the maximum buffering of the voice frames in PDCP is shorter.Because CS12.2K service is generally sended with the period 20ms, and 3 data packages are allowed to send by one time, so the parameter's value is set to "60ms".At next useNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctiondToHsDelayThrN/AN/ADelay Time Threshold of D/D->HS/D or HS/E after HS/D or HS/E ->D/DThis parameter indicates that after switching from HS-DSCH/DCH or HS-DSCH/E-DCH to DCH/DCH triggered by channel quality or traffic volume, this timer starts. When it expires, switching from DCH/DCH to HS-DSCH/DCH or HS-DSCH/E-DCH is allowed.RNCDynamic Radio Bearer Control0..65535, Step 1s10N/AN/AFixed-keep monitoringNoN/AFunction: Delay time threshold of D/D->HS/D or HS/E after HS/D or HS/E ->D/D triggering by channel quality.Configuration Rule: It needs to consider the user experiences and the ratio of call drops.The value of this parameter is smaller, it will be easier to trigger HS/D or HS/E->D/D based on traffic volume measurement after HS/D or HS/E->D/D, but it also will be easier to result in ping-pong adjustmen; And the reconfiguration will increase the risk of call drops.The value of this parameter is larger, it will be more difficult to trigger HS/D or HS/E->D/D based on traffic volume measurement, and influence user experiences.The reason of the parameter's default value is to consider the user experiences and the risk of call drops.At next useNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctionupUdRecfgTimerN/AN/AWait Timer for Adjusting Uplink and Downlink Reconfiguration by One Step UpwardThis parameter indicates when uplink or downlink meets the requirements for rate adjustment (upswitching) first, the wait timer for waiting the opposite direction reconfiguration by one step.RNCDynamic Radio Bearer Control0..65535, Step 1100ms30N/AN/AFixed-keep monitoringNoNoFunction: Wait timer for increase rate of uplink and downlink reconfiguration by one step, it can reduce the times of reconfiguration.Configuration Rule: It needs to consider the times of reconfiguration and user's experiences.The value of this parameter is larger, it will be easier to trigger uplink and downlink reconfiguration by one step, and reduce the times of reconfigurations, but the response to user's traffic need is also slower, so it will be more difficult to trigger rate increase, and it will influence the user's experiences.The value of this parameter is smaller, it will be more difficult to trigger uplink and downlink reconfiguration by one step, and the response to user's traffic need is also faster, so it is easier to trigger rate increase, the user's experiences is good.The reason of the parameter's default value is to consider the times of reconfiguration and user's experiences.At next useNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctiondnUdRecfgTimerN/AN/AWait Timer for Adjusting Uplink and Downlink Reconfiguration by One Step DownwardThis parameter indicates when uplink or downlink meets the requirements for rate adjustment (downswitching) first, the wait timer for waiting the opposite direction reconfiguration by one step.RNCDynamic Radio Bearer Control0..65535, Step 1100ms30N/AN/AFixed-keep monitoringNoNoFunction: Wait timer for decrease rate of uplink and downlink reconfiguration by one step, it can reduce the times of reconfiguration.Configuration Rule: It needs to consider the times of reconfiguration and utilization ratio of radio resource.The value of this parameter is larger, it will be easier to trigger uplink and downlink reconfiguration by one step, and reduce the times of reconfigurations, but the response to user's traffic need is also slower, so it will be more difficult to trigger rate decrease, and it will influence the utilization of radio resources.The value of this parameter is smaller, it will be more difficult to trigger uplink and downlink reconfiguration by one step, and the response to user's traffic need is also faster, so it is easier to trigger rate decrease, the utilization of radio resource is high.The reason of the parameter's default value is to consider the times of reconfiguration and utilization ratio of radio resource.At next useNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctiontRbRecfgCmpDtoFN/AN/AWait Time for RADIO BEARER RECONFIGURATION COMPLETE when CELL_DCH to CELL_FACHThis parameter defines the time period the RNC has to wait before receiving the RADIO BEARER RECONFIGURATION COMPLETE when the RNC orders the UE Leaving CELL_DCH to CELL_FACH.RNCconnection management1..60, Step 1s15N/AN/AFixed-keep monitoringNoNoParameter function: the wait time for RADIO BEARER RECONFIGURATION COMPLETE when CELL_DCH to CELL_FACH.Parameter controlling factor: the round-trip time delay between UE and UTRAN, the success rate of the RRC status transferring.The larger value means the longer waiting time and the higher success rate of the RRC status transferring, but it may cause the longer time delay.The smaller value means the shorter waiting time and the shorter time delay, but it may cause lower success rate of the RRC status transferring.The default value is comprehensively set by the round-trip time delay between UE and UTRAN, and the success rate and time delay of the status transferring.At Commit/New usersNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationN/AN/AURncFunctioniuUlInSeqDlvIndN/AN/AIU Uplink in Sequence Delivery Indicator whether According to Indication from CNThis parameter indicates whether Iu uplink data is delivered in sequence based on indication of RAB assignment from CN.RNCIP UTRAN0: False1: TrueN/A1N/AN/AFixed-keep monitoringNoYesThe function of the parameter is to get configuration of sending IUPS data in order from CN The parameter is configured to be consistent with CN configuration of sending IUPS dataIf the value of the parameter is up to cn, RNC will follow CN's indication of IUPS data in orderIf the value of the parameter is not up to cn, RNC will decide to send IUPS data in order by OMCR's configurationPackets of IU service are defined by CN is preferred.New SessionNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationN/AN/AURncFunctionrncLcsOverIurSwN/AN/ALcs over Iur Support Indicatorhis parameter indicates if RNC supports UE location measurement over Iur interface in LCS Function.RNCLocation Service0: Not Supported1: SupportedN/A0N/AN/AFixedNoNowhen this parameter is configured, it needs to consider that if RNC require ue to report the location measurement result when the UE has radio link in DRNC.This function is decided by Users.ImmediatelyNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctionmulticastSupIndN/ATS 25.331; TS 25.413MBMS Multicast Mode Support IndicatorThis parameter indicates if RNC supports MBMS Multicast ModeRNCMBMS0: Not Supported1: SupportedN/A0N/AN/AFixedNoYesFunction: This parameter indicates if RNC supports MBMS Multicast Mode.Configuration: If RNC supports MBMS Multicast function, the value should be set to "Support"N/ATake effect after the change is loaded to the RNCNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctioneBroadcastSupIndN/ATS 25.331; TS 25.413MBMS Enhanced Broadcast Mode Support IndicatorThis parameter indicates if RNC supports MBMS Enhanced Broadcast ModeRNCMBMS0: Not Supported1: SupportedN/A0N/AN/ANetwork Planing&OptimizationNoYesFunction of this parameter: it indicates if RNC supports MBMS Enhanced Broadcast Mode.If the MBMS is not used, this parameter is invalidN/AImmediatelyNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctionmbmsIurSupIndN/ATS 25.331; TS 25.413MBMS over Iur Support IndicatorThis parameter indicates if RNC supports MBMS UE registration over Iur function.RNCMBMS0: Not Supported1: SupportedN/A0N/AN/AFixedNoYesFunction: This parameter indicates whether RNC supports MBMS UE registration over Iur function.Configuration Rule: If RNC supports MBMS UE registration over Iur function, the value should be set to "Support"N/ATake effect after the change is loaded to the RNCNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctionmbms8kRateSwitchN/AN/AMBMS Channel Rate Support Indicator (8kbps)This parameter is used to indicate whether 8 kbps MBMS service is supported or notRNCMBMS0: Not Supported1: SupportedN/A0N/AN/AFixed-keep monitoringNoNoFunction: This parameter is used to indicate whether MBMS service of 8 kbps is supported or notConfiguration Rule: It should be set according to the provided MBMS service data rateN/ATake effect for the next MBMS serviceNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctionmbms16kRateSwitchN/AN/AMBMS Channel Rate Support Indicator (16kbps)This parameter is used to indicate whether 16 kbps MBMS service is supported or notRNCMBMS0: Not Supported1: SupportedN/A0N/AN/AFixed-keep monitoringNoNoFunction: This parameter is used to indicate whether MBMS service of 16 kbps is supported or notConfiguration Rule: It should be set according to the provided MBMS service data rateN/ATake effect for the next MBMS serviceNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctionmbms32kRateSwitchN/AN/AMBMS Channel Rate Support Indicator (32kbps)This parameter is used to indicate whether 32 kbps MBMS service is supported or notRNCMBMS0: Not Supported1: SupportedN/A0N/AN/AFixed-keep monitoringNoNoFunction: This parameter is used to indicate whether MBMS service of 32 kbps is supported or notConfiguration Rule: It should be set according to the provided MBMS service data rateN/ATake effect for the next MBMS serviceNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctionmbms64kRateSwitchN/AN/AMBMS Channel Rate Support Indicator (64kbps)This parameter is used to indicate whether 64 kbps MBMS service is supported or notRNCMBMS0: Not Supported1: SupportedN/A0N/AN/AFixed-keep monitoringNoNoFunction: This parameter is used to indicate whether MBMS service of 64 kbps is supported or notConfiguration Rule: It should be set according to the provided MBMS service data rateN/ATake effect for the next MBMS serviceNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctionmbms128kRateSwitchN/AN/AMBMS Channel Rate Support Indicator (128kbps)This parameter is used to indicate whether 128 kbps MBMS service is supported or notRNCMBMS0: Not Supported1: SupportedN/A0N/AN/AFixed-keep monitoringNoNoFunction: This parameter is used to indicate whether MBMS service of 128 kbps is supported or notConfiguration Rule: It should be set according to the provided MBMS service data rateN/ATake effect for the next MBMS serviceNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctionmbms256kRateSwitchN/AN/AMBMS Channel Rate Support Indicator (256kbps)This parameter is used to indicate whether 256 kbps MBMS service is supported or notRNCMBMS0: Not Supported1: SupportedN/A0N/AN/AFixed-keep monitoringNoNoFunction: This parameter is used to indicate whether MBMS service of 256 kbps is supported or notConfiguration Rule: It should be set according to the provided MBMS service data rateN/ATake effect for the next MBMS serviceNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctionintraHoEcNoThrdN/AN/ACpich Ec/N0 Minimum Threshold for Intra-Frequency HandoverThis parameter indicates the Cpich EcNo minimum threshold for intra frequency handover. If reported Cpich EcNo is less than IntraHoEcNoThrd or Cpich RSCP is less than IntraHoRscpThrd, intra frequency handover will not be triggered.RNCHandover Control-24..0, step 1dB-13N/AN/AFixed-keep monitoringNoNoFunction: This parameter indicates the Cpich Ec/N0 minimum threshold for intra frequency handover. If reported Cpich EcNo is less than IntraHoEcNoThrd or Cpich RSCP is less than IntraHoRscpThrd, intra frequency handover will not be triggered.Parameter controlling factor: user experience and network featureIf this parameter is small , UE will handover more easily and may cause the calldrop.This default value be set according to network planning and user experienceImmediatelyNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctionintraHoRscpThrdN/AN/ACpich Rscp Minimum Threshold for Intra-Frequency HandoverThis parameter indicates the Cpich RSCP minimum threshold for intra frequency handover. If reported Cpich EcNo is less than IntraHoEcNoThrd or Cpich RSCP is less than IntraHoRscpThrd, intra frequency handover will not be triggered.RNCHandover Control-115..-25, step 1dBm-108N/AN/AFixed-keep monitoringNoNoFunction: This parameter indicates the Cpich RSCP minimum threshold for intra frequency handover. If reported Cpich EcNo is less than IntraHoEcNoThrd or Cpich RSCP is less than IntraHoRscpThrd, intra frequency handover will not be triggered.Parameter controlling factor: user experience and network featureIf this parameter is small , UE will handover more easily and may cause the calldrop.This default value be set according to network planning and user experienceImmediatelyNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctiontcnqueryN/AN/ATimer for State QuerySpecifies the timer for State Query.When in FAIL status, the CN Monitor Module should check the signalling point and user service status periodically according to the timer Tcnquery.RNCIU RESOURCE RESET10..6000, Step 1100ms1800N/AN/AFixedNoNoParameter function: the timer for CN Restore.Parameter controlling factor: IU port interfacing parameter.The larger parameter value means the longer responsive time when CN is unaccessible. The smaller parameter value means the shorter responsive time when CN is unaccessible.The default value corresponds with the ZTE-CN default valueAt next use (i.e., shall not affect ongoing connections)No00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationN/AN/AURncFunctioncbsSwitchN/AN/ACBS Function SwitchSpecifies the switch for the CBS function.RNCCBS0: Off1: OnN/A0N/AN/ANetwork Planing&OptimizationNoYesParameter function: RNC level switch of Cell Broadcast Service functionParameter controlling factor: the function turns on or off.N/AAt CommitNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctionpchToAWSToAWSTS 25.433Time of Arrival Window Startpoint for PCHThis parameter is one factor of the protocolparameter that indicates the window startpoint of the PCH FP. DL data frames are expected to be received after this window startpoint. Time of Arrival Window Startpoint (ToAWS) is defined with a positive value relative Time of Arrival Window Endpoint (ToAWE). ToAWS and ToAWE together define the size of the arrival window in Node B. A data frame arriving outside the arrival window gives a Timing Adjustment Control Frame Response from Node B.RncNode B Management0..1279, step 1ms44TOAWS of FACHThe FACH TOAWS and PCH TOAWS MUST be configured to be the same value in one CELL.FixedNoNoThe protocol parameter TOAWS is configured according to the OMCR parameters of TOAWS and jitter. The function of the protocolparameter TOAWS is to control the earliest acceptable arrival time of a FACH DATA FP in a NodeB.The parameter of TOAWS is configured according to the faculty of processing FACH FPs in a RNC.The parameter of jitter is configured according to the transport delay jitter from a RNC to a related NodeB.If the value of the parameter is too small, NodeB can not response a Timing Adjustment Control Frame to RNC in time , the probability that a PCH data can not be sent on uu interface would be increased and the quality of service with PCH channel such as a paging type1 would be dropped.If the value of the parameter is too large, The NodeB would store more PCH DATA FPs and the delay of service with PCH channel such as a paging type1 would be increased more.The protocol parameter TOAWS is configured according to adjusting the value of the parameter of jitter because the RNC's process faculty is more steady.according to the faculty of processing FACH DATA FPs in a RNC.ImmediatelyNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctionpchToAWEToAWETS 25.433Time of Arrival Window Endpoint for PCHThis parameter indicates the window endpoint of the PCH FP. DL data frames are expected to be received before this window endpoint. Time of Arrival Window Endpoint (ToAWE) is defined with a positive value relative Latest Time of Arrival (LToA). ToAWS and ToAWE together define the size of the arrival window in Node B. A data frame arriving outside the arrival window gives a Timing Adjustment Control Frame Response from Node B.RncNode B Management0..2559, step 1ms8TOAWE of FACHThe FACH TOAWE and PCH TOAWE MUST be configured to be the same value in one CELL.FixedNoNoThe function of the parameter is to control the latest acceptable arrival time of a PCH DATA FP in a NodeB.The parameter is configured according to the Transmission jitter tolerance time errors from RNC to a related NodeB.If the value of the parameter is too small, NodeB can not response a Timing Adjustment Control Frame to RNC in time , the probability that a PCH data can not be sent on uu interface would be increased and the quality of service with PCH channel such as a paging type1 would be dropped.If the value of the parameter is too large, The NodeB would store more PCH DATA FPs and the delay of service with PCH channel such as a paging type1 would be increased more.The parameter can not be configured too small.according to the faculty of processing PCH DATA FPs in a related NodeB.ImmediatelyNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctionfachToAWSToAWSTS 25.433Time of Arrival Window Startpoint for FACHThis parameter is one factor of the protocolparameter that indicates the window startpoint of the FACH FP. DL data frames are expected to be received after this window startpoint. Time of Arrival Window Startpoint (ToAWS) is defined with a positive value relative Time of Arrival Window Endpoint (ToAWE). ToAWS and ToAWE together define the size of the arrival window in Node B. A data frame arriving outside the arrival window gives a Timing Adjustment Control Frame Response from Node B.RncNode B Management0..1279, step 1ms44TOAWS of PCHThe FACH TOAWS and PCH TOAWS MUST be configured to be the same value in one CELL.Fixed-keep monitoringNoNoThe protocol parameter TOAWS is configured according to the OMCR parameters of TOAWS and jitter. The function of the protocolparameter TOAWS is to control the earliest acceptable arrival time of a FACH DATA FP in a NodeB.The parameter of TOAWS is configured according to the faculty of processing FACH FPs in a RNC.The parameter of jitter is configured according to the transport delay jitter from a RNC to a related NodeB.If the value of the parameter is too small, the probability that a FACH DATA FP may be received out of the arrival window in a NodeB would be increased and the quality of service with FACH channel would be dropped.If the value of the parameter is too large, The NodeB would store more FACH DATA FPs and the delay of service with FACH channel would be increased more.The protocol parameter TOAWS is configured according to adjusting the value of the parameter of jitter because the RNC's process faculty is more steady.according to the faculty of processing FACH DATA FPs in a RNC.ImmediatelyNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctionfachToAWEToAWETS 25.433Time of Arrival Window Endpoint for FACHThis parameter indicates the window endpoint of the FACH FP. DL data frames are expected to be received before this window endpoint. Time of Arrival Window Endpoint (ToAWE) is defined with a positive value relative Latest Time of Arrival (LToA). ToAWS and ToAWE together define the size of the arrival window in Node B. A data frame arriving outside the arrival window gives a Timing Adjustment Control Frame Response from Node B.RncNode B Management0..2559, step 1ms8TOAWE of PCHThe FACH TOAWE and PCH TOAWE MUST be configured to be the same value in one CELL.Fixed-keep monitoringNoNoThe function of the parameter is to control the latest acceptable arrival time of a FACH DATA FP in a NodeB.The parameter is configured according to the Transmission jitter tolerance time errors from RNC to a related NodeB.If the value of the parameter is too small, NodeB can not response a Timing Adjustment Control Frame to RNC in time , the probability that a FACH DATA FP can not be sent on uu interface would be increased and the quality of service with FACH channel would be dropped.If the value of the parameter is too large, The NodeB would store more FACH DATA FPs and the delay of service with FACH channel would be increased more.The parameter can not be configured too small.according to the faculty of processing FACH DATA FPs in a related NodeB.ImmediatelyNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctiont321T321TS 25.331Inactivity Time of E_FACH Transmission (T321)Inactivity Time of E-DCH Transmission, UE Should Go Into E-FACH DRX State when times out.RNCHSPA Evolution0: 1001: 2002: 4003: 800ms1N/AN/AFixed-keep monitoringNoNoFunction: Inactivity Time of E_FACH Transmission.Configuration Rule: It needs to consider the transmission bandwidth of UE battery consumption and the user experience.The value of this parameter is larger, the more difficult to enter DRX state, and the more battery consumption for UE.The value of this parameter is smaller, the easier to enter DRX state, and it can save the battery consumption, but it also may influence the user experience.The reason of the parameter's default value is to consider UE battery consumption and the user experience.ImmediatelyNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctiondrxCycleLengthHS-DSCH DRX cycleFACHTS 25.331Cycle Length of Discontinue Receiving of E-FACHOn the State Of E-FACH DRX, This Parameter Indicates Cycle Length of Discontinue Receiving of E-FACH.RNCHSPA Evolution0: 4 frames1: 8 frames2: 16 frames3: 32 framesN/A1RxBurstlength of rncFunctionRxBurstlengthUMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctionueDrxIndN/AN/AIndication of UE with Enhanced DRXThe Parameter Indicates Whether DRX Operation Can Be Used By All E_FACH Users. The value "0" means only UL E_FACH UE Could Use Enhanced DRX, And The Value "1" Means All E_FACH UE Could Use Enhanced DRX.RNCHSPA Evolution0: only UL E_Fach UE support1: support all E_FACHN/A1N/AN/AFixed-keep monitoringNoNoFunction: Indication of UE with Enhanced DRX.Configuration Rule: The recommended value is 1, it can make all ue in enhanced cell_FACH state use DRX and save battery consumption, when Enhanced DRX is used.The reason of the parameter's default value is to consider UE battery consumption in E-FACH state.ImmediatelyNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctiontiureldelayN/AN/ATimer for IU Release ResourceSpecifies the time delay of IU Release Resource.Start: RNC receives a DOWNLINK DIRECT TRANSFER message from CN at Time1, or RNC receives a UPLINK DIRECT TRANSFER message from UE at Time1 Then RNC receives a IU RELEASE COMMAND from the CN at Time2. If Time2 minus Time1 is less then Tiureldelay, RNC start timer which length is equal to Tiureldelay - (Time2-Time1), else RNC release the Iu resource immediately.Stop: If Timer is started, it needn't stop until it expired.At expiry: Rnc will release the Iu resource.RNCIU RESOURCE RELEASE1..50, Step 1100ms3N/AN/AFixedNoNOMain function: This parameter indicates the time delay of IU Release Resource.Influence factor: the time gap between the RNC receives DIRECT TRANSFER message from CN and IU RELEASE COMMAND.The smaller the parameter is, the faster the RNC release IU resource, which may cause the Location Area Update procedure failed in the UE, and also may cause the RNC can't paging the UE.The bigger the parameter is, the slower the RNC release IU resource, which may decrease the utilization ratio of IU resource.The default value is300ms, and is get by test result of outfields.At next use (i.e., shall not affect ongoing connections)No00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationN/AN/AURncFunctionkUtranUTRAN DRX cycle length coefficientTS 25.331UTRAN DRX Cycle Length CoefficientThis parameter is used for the difficult reception of UE in the connection mode. This parameter is used to calculate the paging occasion, that is, a constant required in monitoring the PICH cycle. The difficult reception cycle is 2k frames. In the connection mode, k is the minimum value in CS domain DRX cycle length coefficient, PS domain DRX cycle length coefficient, and UTRAN DRX cycle length coefficient.RNCConnection Management3..9N/A6N/AN/AFixedNoNoFunction: This parameter is used for the difficult reception of UE in the connection moden and is a constant required in monitoring the PICH cycle. The difficult reception cycle is 2^k frames. In the connection mode, k is the minimum value among the DRX cycle length coefficient of the attached domains, and UTRAN DRX cycle length coefficient.Configuration Rule: Considering UE's paging occasion and power consumption of UE.The smaller value means the more UE paging occasion, but more power will be consumed. And the vice versa.Considering UE's paging occasion and power consumption of UE.At next use (i.e., shall not affect ongoing connections)No00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationN/AN/AURncFunctionrabMeaBalStaSwchN/AN/AInter-Frequency Balance Switch Based on MeasurementThis parameter indicates balance switch based on measurement. If this switch is on, neighboring cells with "neighbor" or "contained in" relation use measurement-based balance; neighboring cells with "Overlap" or "Covers" relation may also use measurement-based balance only if CoverMeaBalSwch is on too. Otherwise, only blind handover-based balance will be performed to the neighboring cells with "Overlap" or "Covers" relation.RNCLoad Balance0: Off1: OnN/A0N/AN/AFixedNoYesFunction: Inter-Frequency Balance Switch Based on MeasurementRelated factor: coverage of neighboring cellIf this switch is on, neighboring cells with "neighbor" or "contained in" relation use measurement-based balance; neighboring cells with "Overlap" or "Covers" relation may also use measurement-based balance only if CoverMeaBalSwch is on too. If the switch is off, only blind handover-based balance will be performed to the neighboring cells with "Overlap" or "Covers" relation.The coverage of neighboring cell is considered to define this default value.At Next UseNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctioncoverMeaBalSwchN/AN/AInter-Frequency Balance Switch Based on Measurement with Overlapping or Covering RelationThis parameter indicates balance switch based on measurement. If the RabMeaBalStaSwch and CoverMeaBalSwch is on, balance based on measurement will be performed to the neighboring cells with overlapping or covering relation, otherwise, balance based on blind handover will be performed to the neighboring cells with overlapping or covering relation.RNCLoad Balance0: Off1: OnN/A0N/AN/AFixedNoYesFunction: Inter-Frequency Balance Switch Based on Measurement with Overlapping or Covering RelationRelated factor: success rate of blind HO based balance If RabMeaBalStaSwch and CoverMeaBalSwch are on, measurement-based balance will be performed for neighboring cells with overlapping or covering relation; otherwise, blind HO based balance will be performed for neighboring cells with overlapping or covering relation. Measurement-based balance can improve the successful rate of balance for UE on cell's boundary, but the procedure is more complicated and delay is longer than that of blind HO based balance.The success rate of blind HO based balance is considered to define this default value.At Next UseNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctionmeasBalTimerN/AN/ATimer of Deactivate Compressed Mode for Balance Strategy Based On MeasurementThis parameter indicates timer of deactivate compressed mode for balance strategy based on measurement. When the timer expired, if inter-frequency event (2C) doesn't report, RNC will judge whether compressed mode is deactivate or not based on current signal quality.RNCLoad Balance1..255, step 1s6N/AN/AFixedNoNoFunction: Timer of Deactivate Compressed Mode for Balance Strategy Based On MeasurementRelated factor: the time of compressed mode active and UE measurementThis parameter is smaller, the activation time of compressed mode is shorter and UE may not finish measurement. Otherwise, this parameter is bigger, the activation time of compressed mode is longer but which impact cell throughput.The time of compressed mode active and UE measurement is considered to define this default value.At Next UseNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctiontResndMeaCtrlRelN/AN/AThe Time Threshold that the RNC May Resend the MEASUREMENT CONTROL RELEASEThis parameter indicates the time threshold that the RNC may resend the MEASUREMENT CONTROL RELEASE.When RNC sends MEASUREMENT CONGROL RELEASE message for a measurement ID, the time stamp will be recorded. If RNC receives the measurement report for the ID, it will be compared between current time and recorded time. If difference between current time and recorded time exceed the threshold configured, the MEASUREMENT CONTROL RELEASE will be resent, otherwise ignore this measurement report.RNCHandover Control1..255, Step 1s30N/AN/AFixed-keep monitoringNoNoParameter function: indicates the time threshold that the RNC may resend the MEASUREMENT CONTROL RELEASE. Parameter controlling factor: the round trip time between UE and UTRAN, the MEASUREMENT CONTROL FAILURE message number in Uu interface.The smaller parameter value means the shorter time delay for RNC resending measurement control release, it helps to let UE receive measurement control release message sooner and release specified measurement sooner, but it may increase the MEASUREMENT CONTROL FAILURE message number in Uu interface. The larger parameter value means the longer time delay for RNC resending measurement control release, it helps to decrease the MEASUREMENT CONTROL FAILURE message number in Uu interface, but it may let UE receive measurement control release message too late and release specified measurement too late.The default value is comprehensively set by the round trip time between UE and UTRAN, the MEASUREMENT CONTROL FAILURE message number in Uu interface.At Commit/New usersNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctionheartBeatUeVerR4N/AN/AThe Target of UE Version for Heart Beat (R4)This parameter indicates the UE of Release 4 and before Release 4 Version whether to be performed heart beat detection.RNCDynamic Radio Bearer Control0: False1: TrueN/A0N/AN/AFixed-keep monitoringNoNoParameter Function: This parameter indicates the valid UE version for heart beat.Configuration Rule: It is mainly used for signalling storm scene, indicates the valid UE version for heart beat.When the signalling load is not high, it's not recommended to perform heart beat detection to UE.it's not recommended to perform heart beat detection to UE.At Next UseNo00N/ARead/WriteGUI: Managed Element->UMTS Logical Function ConfigurationVersions earlier than V4.12.10.08 (V3.12.10.08)N/AURncFunctionheartBeatUeVerR5N/AN/AThe Target of UE Version for Heart Beat (R5)This parameter indicates the UE of Release 5 Version whether to be performed heart beat detection.RNCDynamic Radio Bearer Control0: False1: TrueN/A0N/AN/AFixed-keep monitoringNoNoParameter Function: This parameter indicates the valid UE version for heart beat.Configuration Rule: It is mainly used for signalling storm scene, indicates the valid UE version for heart beat.When the signalling load is not high, it's not recommended to perform heart beat detection to UE.it's not recommended to perform heart beat detection to UE.A