SJ-20100603155704-001-ZXWR RNC (V3.09.30) Specifications and Requirements For Importing Radio Parameter Settings - 341298

ZXWR RNC
Radio Network Controller
Specifications and Requirements for

Importing Radio Parameter Settings
Version: V3.09.30
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 2011 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.0
20100714
First Edition (V3.09.30.03)
R2.0
20110216
Second Edition (V3.09.30.09)

1. The figures in section OMM have been modified
2. The information in section Detailed Relationships
of Radio Parameters have been modified.And
CelMPO,CfnOffset,EFach,Nbcom and NbDed have been
added
3. CelMPO,CfnOffset,EFach,Nbcom and NbDed have been
added in chapter Operation in Planning Radio Parameters
R2.1
20110322
Those sections have been modified:

1. 2.1 Relationships for MOC
2. 2.2.13 MBMS Configuration Information (Mbms)
3. 2.2.15.5 Access Control Related to Basic Priority (BPriAc)
4. 2.2.26.1 Utran Cell (utranCell)
5. 2.2.26.2 Neighbouring Cell (utranRelation)
R2.2
20110409
Those sections have been modified:

1. The table in 2.1 Relationships for MOC has been modified
2. A new section of 3.37 PriSel in chapter 3 has been added
3. All the form of tables and punctuation in chapter 2 have been
modified
Revision No.
Revision Date
Revision Reason
4. 1.3 Operations in CNO Software
5. 1.6.2 Import to OMM
Serial Number: SJ-20100603155704-001

Publishing Date: 2011-04-09(R2.2)
Contents
Preface............................................................................................................. I
Chapter 1 Flow of Importing Radio Parameter Settings ......................... 1-1
1.1 Overview ........................................................................................................... 1-1
1.2 Flow Chart ......................................................................................................... 1-1
1.3 Operations in CNO Software ............................................................................... 1-3
1.4 Live/Planned Data files ....................................................................................... 1-5
1.4.1 Naming Rule of Live/Planned File.............................................................. 1-5
1.4.2 Structure of Sheets in Live/Planned data File ............................................. 1-6
1.5 Delta files (script) ............................................................................................... 1-7
1.5.1 Naming Rule of Delta File (script) .............................................................. 1-7
1.5.2 Structure of Sheets in Delta File (script) ..................................................... 1-7
1.5.3 Modify Indicator........................................................................................ 1-8
1.6 OMM ................................................................................................................. 1-9
1.6.1 Export from OMM..................................................................................... 1-9
1.6.2 Import to OMM ........................................................................................1-11
Chapter 2 Relationships ............................................................................ 2-1

2.1 Relationships for MOC........................................................................................ 2-1
2.2 Detailed Relationships of Radio Parameters ........................................................ 2-8
2.2.1 RNC Configuration Information (rncFunction) ............................................. 2-8
2.2.2 RNC Configuration Supplement Information(rncBRnc).............................. 2-12
2.2.3 NodeB Configuration Information (nodeB)................................................ 2-12
2.2.4 UE Timers and Constants Information (ueCnst)........................................ 2-13
2.2.5 CN System Information (cnInfo) .............................................................. 2-13
2.2.6 Iu Interface Timers and Constants Information (iuCnst) ............................. 2-13
2.2.7 UL Scrambling Code Configuration Information In RCP (rcpSc)................. 2-13
2.2.8 FACH Traffic Control Information (trfCtl)................................................... 2-14
2.2.9 Dynamic Radio Bearer Control Information (drbc)..................................... 2-14
2.2.10 Global Access Control (GloAc) .............................................................. 2-17
2.2.11 Hspa Configuration Information (Hspa) .................................................. 2-17
2.2.12 Limiting HSDPA GBR Resource Consumption information (GbrRes)........ 2-18
2.2.13 MBMS Configuration Information (Mbms)............................................... 2-18
2.2.14 CFN Offset Configuration Information .................................................... 2-19
2.2.15 Qos Configuration ................................................................................ 2-19
2.2.16 Intra-frequency Measurement................................................................ 2-25

2.2.17 Inter-frequency Measurement................................................................ 2-30
2.2.18 Inter-Rat Measurement ......................................................................... 2-35
2.2.19 Service Basic Configuration Information (SubSrv)................................... 2-40
2.2.20 E-DCH Reference Configuration Information (EdchRc) ........................... 2-51
2.2.21 UE DTX-DRX Configuration Information (rncDtxDrx)............................... 2-51
2.2.22 Service Physical Layer Configuration Information (SrvPhy) ..................... 2-52
2.2.23 Power Control Related to Service and Diversity Mode (DivPc)................. 2-55
2.2.24 External Utran Cell (externalUtranCell) .................................................. 2-58
2.2.25 External Gsm Cell (externalGsmCell)..................................................... 2-62
2.2.26 Utran Cell ............................................................................................ 2-64
2.2.27 Traffic-Related Power Control (TrfPc).................................................... 2-117
2.2.28 NodeB Common Measurement ............................................................ 2-118
2.2.29 NodeB Dedicated Measurement ........................................................... 2-119
2.2.30 UE Traffic Volume Measurement ..........................................................2-121
2.2.31 GPS Global Configuration Information (GpsCfg) ....................................2-127
2.2.32 Transport Format Combination Set of SCCPCH (DlTfcs)........................2-127
2.2.33 Transport Format Combination Set of PRACH (UlTfcs) ..........................2-127
2.2.34 Transport Format Combination Set (Tfs) ...............................................2-127
2.2.35 User Authorized PLMN+SNAC Information (rncPnSnac) ........................2-128
2.2.36 LAC and SNAC Information (rncLcSnac)...............................................2-128
2.2.37 NE Information Configuration (rncNeInfo)..............................................2-128
Chapter 3 Operation in Planning Radio Parameters ............................... 3-1

3.1 Overview ........................................................................................................... 3-2
3.2 rncFucntion........................................................................................................ 3-3
3.3 rncBRnc ............................................................................................................ 3-3
3.4 nodeB ............................................................................................................... 3-3
3.5 ueCnst............................................................................................................... 3-4
3.6 cnInfo ................................................................................................................ 3-4
3.7 iuCnst................................................................................................................ 3-4
3.8 rcpSc................................................................................................................. 3-4
3.9 trfCtl .................................................................................................................. 3-5
3.10 drbc................................................................................................................. 3-5
3.11 GloAc .............................................................................................................. 3-5
3.12 Hspa ............................................................................................................... 3-5
3.13 GbrRes............................................................................................................ 3-6
3.14 Mbms .............................................................................................................. 3-6
II
3.15 CfnOffset ......................................................................................................... 3-6

3.16 QosSeg ........................................................................................................... 3-6
3.17 BasPri ............................................................................................................. 3-7
3.18 SchPri ............................................................................................................. 3-7
3.19 AppPri ............................................................................................................. 3-8
3.20 BPriAc ............................................................................................................. 3-8
3.21 Intra................................................................................................................. 3-9
3.22 CIntra ............................................................................................................ 3-10
3.23 Inter............................................................................................................... 3-10
3.24 CInter .............................................................................................................3-11
3.25 Rat .................................................................................................................3-11
3.26 CRat.............................................................................................................. 3-12
3.27 SubSrv .......................................................................................................... 3-12
3.28 EdchRc.......................................................................................................... 3-13
3.29 rncDtxDrx ...................................................................................................... 3-13
3.30 SrvPhy........................................................................................................... 3-13
3.31 DivPc............................................................................................................. 3-14
3.32 externalUtranCell............................................................................................ 3-14
3.33 externalGsmCell............................................................................................. 3-15
3.34 utranCell ........................................................................................................ 3-15
3.35 utranRelation ................................................................................................. 3-16
3.36 gsmRelation................................................................................................... 3-16
3.37 PriSel ............................................................................................................ 3-17
3.38 CelSel ........................................................................................................... 3-17
3.39 CHspa ........................................................................................................... 3-17
3.40 CMbms.......................................................................................................... 3-18
3.41 MbmsSa ........................................................................................................ 3-18
3.42 EFach............................................................................................................ 3-18
3.43 CelMPO......................................................................................................... 3-19
3.44 Psch .............................................................................................................. 3-19
3.45 Ssch .............................................................................................................. 3-19
3.46 Pcpich ........................................................................................................... 3-20
3.47 Pccpch .......................................................................................................... 3-20
3.48 Scpich ........................................................................................................... 3-20
3.49 Sccpch .......................................................................................................... 3-21
3.50 Pich............................................................................................................... 3-22
3.51 Prach............................................................................................................. 3-22
III
3.52 Aich............................................................................................................... 3-23

3.53 Mich .............................................................................................................. 3-23
3.54 Bch................................................................................................................ 3-23
3.55 Fach .............................................................................................................. 3-24
3.56 Pch................................................................................................................ 3-24
3.57 Rach ............................................................................................................. 3-24
3.58 PC................................................................................................................. 3-25
3.59 AC................................................................................................................. 3-25
3.60 LdCtrl ............................................................................................................ 3-25
3.61 SysMC........................................................................................................... 3-25
3.62 plBal .............................................................................................................. 3-26
3.63 TrfPc ............................................................................................................. 3-26
3.64 Nbcom........................................................................................................... 3-27
3.65 NbDed ........................................................................................................... 3-27
3.66 UeTrv ............................................................................................................ 3-27
3.67 CUeTrv .......................................................................................................... 3-27
3.68 GpsCfg .......................................................................................................... 3-28
3.69 DlTfcs............................................................................................................ 3-28
3.70 UlTfcs............................................................................................................ 3-29
3.71 Tfs................................................................................................................. 3-29
3.72 rncPnSnac ..................................................................................................... 3-30
3.73 rncLcSnac...................................................................................................... 3-30
3.74 rncNeInfo....................................................................................................... 3-30
Appendix A Searching Methods of Radio Parameters .......................... A-1

A.1 Intra-frequency Measurement Parameters ........................................................... A-1
A.2 Inter-frequency Measurement Parameters ........................................................... A-2
A.3 Inter-RAT Measurement Parameters ................................................................... A-2
A.4 Power Control Parameters Related to Service and Diversity Mode ........................ A-3
A.5 Power Control Parameters Related to Service ..................................................... A-8
A.6 Scheduling Priority Parameters........................................................................... A-9
A.7 Congestion Control Priority Parameters............................................................... A-9
A.8 Load Control Priority Parameters ........................................................................ A-9
A.9 UE Traffic Volume Measurement Parameters....................................................... A-9
A.10 Access Control Parameters Related to Basic Priority ........................................ A-10
A.11 Transport Format Combination Set Parameters of SCCPCH ............................. A-10
A.12 Transport Format Combination Set Parameters of PRACH ............................... A-10
A.13 Transport Format Set Parameters ................................................................... A-10
IV
A.14 NodeB Parameters......................................................................................... A-11

A.15 Ura Information .............................................................................................. A-11
A.16 Parameters of Other Objects .......................................................................... A-11
Appendix B CPC and CTC ........................................................................ B-1

B.1 CPC and CTC ................................................................................................... B-1
Figures............................................................................................................. I
Tables ............................................................................................................ III
Glossary .........................................................................................................V
VI
Preface
Manual Description
Describes the flow of importing radio parameter settings, the relationships for MOC and
the operations in planning radio parameters.
What Is in This Manual

Chapter
Summary
Chapter 1, Flow of Importing Radio Parameter
Introduces the flow of importing radio parameter
Settings
settings
Chapter 2, Relationships
Introduces the relationships for MOC
Chapter 3, Operation in Planning Radio
Introduces the operations in planning radio
Parameters
parameters
Appendix A, Searching Methods of Radio
Introduces the searching methods of radio
Parameters
parameters
Appendix B, CPC and CTC
Introduces the basic concept of CPC and CTC
Intended Audience
l
l
l
l
Network planners
Field engineers
System engineers
Shift operators
II
Chapter 1
Flow of Importing Radio

Parameter Settings
Table of Contents
Overview ....................................................................................................................1-1
Flow Chart..................................................................................................................1-1
Operations in CNO Software ......................................................................................1-3
Live/Planned Data files...............................................................................................1-5
Delta files (script) .......................................................................................................1-7
OMM ..........................................................................................................................1-9
1.1 Overview
The radio parameter settings batch importing function indicates that after editing
add/modify/delete a excel file with several sheets, the user can import managed objects
in batch.
1.2 Flow Chart

The flow chart of importing radio parameter settings is shown as Figure 1-1.
1-1
SJ-20100603155704-001|2011-04-09(R2.2)
ZTE Proprietary and Confidential
ZXWR RNC Specifications and Requirements for Importing Radio Parameter Settings
Figure 1-1 Flow of Importing Radio Parameter Settings
1. Create live data setting.

Freeze all change in RNC, export the full-set radio parameter settings from RNC. This
is the live data settings.
2. Create planned data setting.
The planned data contains the edited (added/modified/deleted) full-set radio
parameter settings by users.
3. Create planned-vs-live delta file (script).
Input the live data settings and planned data settings into CNO software, produce the
planned-vs-live delta file (script).
4. Import the planned-vs-live delta file (script) into OMM, synchronize the new parameter
settings to RNC.
1-2
SJ-20100603155704-001|2011-04-09(R2.2)
Chapter 1 Flow of Importing Radio Parameter Settings
1.3 Operations in CNO Software

Abstract
CNO software aims at comparing the live data and planned data, creating planned-vs-live
delta file (script).
The operations in CNO software are described in detail.
Steps
1. Open the CNO software, choose Data > Import Radio Parameters from Files on
the menu.
2. Choose planned data, as shown in Figure 1-2.
Figure 1-2 Choose Planned Data
3. Click Browser.
4. choose the planned data file (user can also choose several files by pressing Ctrl
button).
5. After importing the planned data, the result is shown as Figure 1-3.
1-3
SJ-20100603155704-001|2011-04-09(R2.2)
Figure 1-3 The Result of Importing
6. Choose live data, as shown in Figure 1-4.

Figure 1-4 Choose Live Data
7. Click Browser button, choose the live data file.

8. execute the importing.
9. Click Close button.
10. On the menu, choose Change Request > Generate Delta OMC Batch Scripts File
of Radio Parameter, choose all RNC object, as shown in Figure 1-5.
1-4
SJ-20100603155704-001|2011-04-09(R2.2)
Figure 1-5 Choose all RNC Object
11. Click OK button, create the delta file (script) of all RNC object.
End of Steps
1.4 Live/Planned Data files

1.4.1 Naming Rule of Live/Planned File
The naming rule of each sheet is shown as Figure 1-6, such as, utranRelation(1).
Figure 1-6 The Naming Rule of Script File
If the data of a certain MOC contains only one Sheet, (xxx) can be omitted. For example,
the name can be utranRelation. If the data of a certain MOC contains over one Sheet, the
name must be in the MOC (xxx) format.
1-5
SJ-20100603155704-001|2011-04-09(R2.2)
1.4.2 Structure of Sheets in Live/Planned data File

There are two types of sheets in live/planned data file:
l
l
Sheets of recording MOC data

Index sheets
1.4.2.1 Sheets of Recording MOC data

The structure of the sheets to record MOC data is shown as Table 1-1.
Table 1-1 The Structure of Sheet of Recording MOC Data
Column Name
Column Title
Data line
The example of the sheet to record MOC data is shown as Figure 1-7.
Figure 1-7 The Example of Sheet of Recording MOC Data
1.4.2.2 Index Sheets

The structure of the index sheet is shown as Table 1-2.
Table 1-2 The Structure of index sheet
Management Object Name
Index
The example of index sheet is shown as Figure 1-8.
1-6
SJ-20100603155704-001|2011-04-09(R2.2)
Figure 1-8 The example of index sheet
1.5 Delta files (script)

1.5.1 Naming Rule of Delta File (script)
Its the same as the one of live/planned data file, please refer to Naming Rule of
Live/Planned File.
1.5.2 Structure of Sheets in Delta File (script)

There are two types of sheets in live/planned data file:
l
Sheets of recording MOC data

Compared with the structure of sheets in live/planned data File, the first column of
delta file is ModInd, shown as Figure 1-9.
1-7
SJ-20100603155704-001|2011-04-09(R2.2)
Figure 1-9 Moc Data Sheet of Delta File (script)
Other columns structure description of recording MOC data refer to Sheets of

recording MOC data.
l
Index sheets
The structure of delta files index sheets is the same as the one of live/planned data
files, please refer to Index sheets.
1.5.3 Modify Indicator

The column ModInd in the script is a modify indicator.
Modify indicator of importing radio parameters falls into three types:
l
A: The abbreviation of Add, indicating to add one record.

When one record is being added, attribute values for all columns must be filled in the
script.
D: The abbreviation of Delete, indicating to delete one record.

When a record is being deleted, OMCRNCID, primary key, and alternative key must
be filled in the script.
M: The abbreviation of modify, indicating to modify one record.

When one record is being modified, OMCRNCID, primary key, and alternative key,
and the attribute value to be modified must be filled in the script.
In the column ModInd, the values must be filled in with A/M/D. For the null information,
The instance has not defined execute type or has error! message will appear in the log
file generated during the import.
1-8
SJ-20100603155704-001|2011-04-09(R2.2)
1.6 OMM
The operation in OMM software aims at exporting live data and importing planned-vs-live
delta file (script).
The operations in OMM software are described in detail.
1.6.1 Export from OMM

Steps
1. On the OMM software main menu, choose RNC Managed Element > Configuration
Data Export Tool, as shown in Figure 1-10.
Figure 1-10 Choose Configuration Data Export Tool
Note:
The RNC Managed Element on the main menu will not appeared until user selected
a RNC Config Set on the Configuration Resource Tree.
2. Data Export interface pops up, as shown in Figure 1-11.
1-9
SJ-20100603155704-001|2011-04-09(R2.2)
Figure 1-11 Data Export Interface
The default choice of Config Set identity is the master config set.
3. Select the target information from the drop-down menu of RNC Identity and Config
Set Identity.
4. Choose Radio Management Object tab.
5. Tick the target node information on this tab, or tick Select All, as shown in Figure 1-12.
Figure 1-12 Tick the Target Node Information
6. Click Export Data button and select the target path in the pop-up dialog box.
7. Click Save button, the ticked node information on the tab has been saved into a zip
file in the format of excel.
End of Steps
1-10
SJ-20100603155704-001|2011-04-09(R2.2)
1.6.2 Import to OMM

Steps
1. On the main menu of OMM configuration management interface, choose RNC
Managed Element > Configuration Guide, as shown in Figure 1-13.
Figure 1-13 Select Configuration Guide
Note:
The RNC Managed Element on the main menu will not appeared until user selected
a RNC Config Set on the Configuration Resource Tree.
2. Select config Set dialog box pops up.

3. Select the target information from the drop-down menu of Managed Element ID and
Config Set ID, as shown in Figure 1-14.
Figure 1-14 Select Config Set Dialog Box
The default choice of Config Set ID is the master config set.

4. Click OK button.
5. The Configuration Guide dialog box pops up.
1-11
SJ-20100603155704-001|2011-04-09(R2.2)
6. Click
on Configuration Guide dialog box and select CNO Radio Data Batch
Import, as shown in Figure 1-15.
Figure 1-15 Select CNO Radio Data Batch Import
7. The Radio Data-CNO Radio Data Batch Import tab pops up as shown inFigure 1-16.
Figure 1-16 CNO Radio Data Batch Import Tab
8. Click Choose File button.

9. Opendialog box pops up, select the delta file from the local disk and click Open button
.
10. Click Import Data button, after a while, a Confirm dialog box pops up.
11. Click OK button.
End of Steps
1-12
SJ-20100603155704-001|2011-04-09(R2.2)
Chapter 2
Relationships
Table of Contents
Relationships for MOC ...............................................................................................2-1
Detailed Relationships of Radio Parameters...............................................................2-8
2.1 Relationships for MOC

The complete primary keys and alternative keys of management objects are shown as
Table 2-1.
Table 2-1 Primary Keys and Alternative Key of MOC
Sheet Name
rncFunction
MOC Name
RNC Configuration
Complete Primary
Complete Alternative
Key of MO (A+B
Key (A+B means the
means the Complete
Primary Key is
Key is consisted of A
consisted of A and B)
and B)
OMCRNCID
N/A
Information
QosSeg
Qos Configuration
OMCRNCID
N/A
BasPri
Basic Priority
OMCRN-
N/A
Management
CID+ARPSeg+TrafficClass
SchPri
Scheduling Priority
OMCRNCID+SchPriIn
Management
dex+BasicPrio+Bearer
N/A
Type
AppPri
BPriAc
nodeB
Application Priority
OMCRNCID+AppPriIn
N/A
Configuration
dex+BPSeg+BearerTy
Information
pe+RateSeg
Access Control Related
OMCRNCID+BPriAcIn
to Basic Priority
dex+BasicPrio
NodeB Configuration
OMCRNCID+NodebNo
N/A
OMCRNCID
N/A
N/A
Information
ueCnst
UE Timers and
Constants Information
2-1
SJ-20100603155704-001|2011-04-09(R2.2)
Sheet Name
cnInfo
MOC Name
CN System Information
Complete Primary
Key of MO (A+B
Key (A+B means the
means the Complete
Primary Key is
and B)
OMCRNCID+MCC+M
N/A
NC
iuCnst
Iu Interface Timers and
OMCRNCID
N/A
OMCRNCID+Module
N/A
OMCRNCID
N/A
OMCRNCID
N/A
OMCRNCID
N/A
Constants Information
rcpSc
UL Scrambling
Code Configuration
Information In RCP
trfCtl
FACH Traffic Control

Information
drbc
Dynamic Radio Bearer

Control Information
Mbms
MBMS Configuration
Information
GloAc
Global Access Control
OMCRNCID
N/A
Hspa
Hspa Configuration
OMCRNCID
N/A
UE Intra-frequency
OMCRNCID+IntraMea
N/A
Measurement
sCfgNo
Information
Intra
Configuration
CIntra
UE Intra-frequency
OMCRNCID+TrfCatIntr
Measurement
aMIdx+TrfCategory
N/A
Relative to Traffic
Category Configuration
Information
Inter
UE Inter-frequency
OMCRNCID+InterMea
Measurement
sCfgNo
N/A
Configuration
CInter
UE Inter-frequency
OMCRNCID+TrfCatInt
Measurement Relative
erMIdx+TrfCategory
N/A
to Traffic Category
DivPc
Power Control Related
OMCRNCID+DivPcInd
to Service and Diversity
ex+SrvType+TxDivMo
Mode
N/A
2-2
SJ-20100603155704-001|2011-04-09(R2.2)
Chapter 2 Relationships
Sheet Name
SubSrv
MOC Name
Complete Primary
Key of MO (A+B
Key (A+B means the
means the Complete
Primary Key is
and B)
OMCRNCID+SrvType
N/A
UE Inter-Rat
OMCRNCID+InterRat
N/A
Measurement
CfgNo
Service Basic
Configuration
Information
Rat
Configuration
Information
CRat
UE Inter-Rat
OMCRNCID+TrfCatRa
Measurement Relative
tMIdx+TrfCategory
N/A
to Traffic Category
externalUtranCell
External Utran Cell
OMCRNCID+MCC+M
N/A
NC+RncId+CId
externalGsmCell
External Gsm Cell
OMCRNCID+MCC+M
N/A
NC+LAC+CI
utranCell
Utran Cell
OMCRNCID+CId
N/A
utranRelation
Neighbouring Cell
OMCRNCID+CId+NM
N/A
CC+NMNC+NRncId+N
CId
gsmRelation
Gsm Neighbouring Cell
OMCRNCID+CId+MC
N/A
C+MNC+LAC+CI
PriSel
Cell Frequency
OMCRNCID+CId
N/A
Cell Selection and
OMCRNCID+CId+Sib3
N/A
Reselection
orSib4
Psch
PSCH
OMCRNCID+CId
N/A
Ssch
SSCH
OMCRNCID+CId
N/A
Pcpich
PCPICH
OMCRNCID+CId
N/A
Scpich
SCPICH
OMCRNCID+CId+CP
N/A
Reselection and
Priority
CelSel
CId
Pccpch
PCCPCH
OMCRNCID+CId
N/A
Prach
PRACH
OMCRNCID+CId+CP
N/A
CId
2-3
SJ-20100603155704-001|2011-04-09(R2.2)
Sheet Name
Aich
MOC Name
AICH
Complete Primary
Key of MO (A+B
Key (A+B means the
means the Complete
Primary Key is
and B)
OMCRNCID+CId+CP
N/A
CId
Bch
BCH
OMCRNCID+CId
N/A
Rach
RACH
OMCRNCID+CId+CTC
OMCRNCID+CId+Prac
Id
hCPCId+CTCId
OMCRNCID+CId+CTC
OMCRNCID+CId+Scc
Id
pchCPCId+CTCId
OMCRNCID+CId+CTC
OMCRNCID+CId+Scc
Id
pchCPCId+CTCId
OMCRNCID+CId+CP
N/A
Pch
Fach
Pich
PCH
FACH
PICH
CId
Mich
MICH
OMCRNCID+CId
N/A
Sccpch
SCCPCH
OMCRNCID+CId+CP
N/A
CId
AC
Cell-Related Access
OMCRNCID+CId
N/A
OMCRNCID+CId
N/A
OMCRNCID+CId
N/A
Control
PC
Power Control not

Related to Service
LdCtrl
Load Control
Relationship
plBal
Balance Information
OMCRNCID+CId
N/A
SysMC
UE Measurement
OMCRNCID+CId+Sib1
N/A
Configuration In
1orSib12
System Information
Block
CHspa
Hspa Configuration
OMCRNCID+CId
N/A
UtranCell Information
OMCRNCID+MCC+M
N/A
in MBMS Service Area
NC+MbmsSac+FreqBa
Information In A Cell
MbmsSa
ndInd+DUARFCN
CMbms
MBMS Configuration
OMCRNCID+CId
N/A
Traffic-Related Power
OMCRNCID+TrfPcInd
N/A
Control
ex+SrvType
TrfPc
2-4
SJ-20100603155704-001|2011-04-09(R2.2)
Sheet Name
UeTrv
MOC Name
Complete Primary
Key of MO (A+B
Key (A+B means the
means the Complete
Primary Key is
and B)
UE Traffic Volume
OMCRNCID+UeTrvM
N/A
Measurement
CfgNo
Configuration
CUeTrv
UE Traffic Volume
OMCRNCID+CId
N/A
OMCRNCID
N/A
Transport Format
OMCRNCID+TfcsInde
N/A
Combination Set of
Measurement
Configuration
GpsCfg
GPS Global
Configuration
Information
DlTfcs
SCCPCH
UlTfcs
Transport Format
OMCRNCID+TfcsInde
Combination Set of
N/A
PRACH
Tfs
Transport Format Set
OMCRNCID+TfsIndex
N/A
rncPnSnac
User Authorized
OMCRNCID+MCC+M
N/A
PLMN+SNAC
NC+ExtInfoDgtNum+E
Information
xtInfo+SMCC+SMNC
+SNAC
rncLcSnac
rncNeInfo
Srvphy
LAC and SNAC
OMCRNCID+MCC+M
N/A
Information
NC+LAC+SNAC
NE Information
OMCRNCID+GloPhyN
Configuration
eId
Service Physical
OMCRNCID+SRVTYP
OMCRNCID+SIGSRV
Layer Configuration
E+SIGSRVNO
NO+SRVTYPE
Limiting HSDPA
OMCRNCID+HSGBR
N/A
GBR Resource
RESLIMITIDX
N/A
Information
GbrRes
Consumption
information
EdchRc
E-DCH Reference
OMCRNCID+EDCHRE
Configuration
FCONFIGIDX
N/A
Information
2-5
SJ-20100603155704-001|2011-04-09(R2.2)
Sheet Name
rncDtxDrx
MOC Name
Complete Primary
Key of MO (A+B
Key (A+B means the
means the Complete
Primary Key is
and B)
UE DTX-DRX
OMCRNCID+DTXDRX
N/A
Configuration
CONFIGIDX
Information
rncBRnc
RNC Configuration
OMCRNCID
N/A
HS-PDSCH
OMCRNCID+CId+App
N/A
Measurement Power
HsdpaEInd
Supplement
Information
CelMPO
Offset
CfnOffset
CFN Offset
OMCRNCID+SigType
Configuration
+FstRecfgInd+RetranR
N/A
Information
ate
EFach
Cell Enhanced Fach
OMCRNCID+CId
N/A
Nbcom
NodeB Common
OMCRNCID+NbCMCf
OMCRNCID+NbCMCf
Measurement
gNo
gNote+NbCMCfgNo
NodeB Dedicated
OMCRNCID+NbDMCf
N/A
Measurement
gNote
Configuration
Information
NbDed
Configuration
Information
The relationships of ZXWR RNC Radio Resource Management Object are shown as
Figure 2-1 and Figure 2-2.
2-6
SJ-20100603155704-001|2011-04-09(R2.2)
Figure 2-1 Relationship 1 of Radio Resource Management Objects
2-7
SJ-20100603155704-001|2011-04-09(R2.2)
Figure 2-2 Relationship 2 of Radio Resource Management Objects
l
l
The startpoint of arrow is the son object.

The endpoint of arrow is the father object.
The index of arrow is the related index between two related tables, and it may not be a
complete primary key of any object.
2.2 Detailed Relationships of Radio Parameters

The relationships of radio resource parameters are shown as the following. In the following,
the value range [A, B] means the value of parameter can be taken from A to B.
2.2.1 RNC Configuration Information (rncFunction)
2-8
SJ-20100603155704-001|2011-04-09(R2.2)
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
Relationship description
GsmLRange[32]
rncFunction
GsmURange[32]
GsmLRange[32] and GsmURange[32] are both arrays. The maximum of array elements
is 32 and the valid number of array elements is GsmBARangeNum
GsmLRange[i] <GsmURange[i], i=[0,GsmBARangeNum-1]
GsmLRange[i] value range should keep consistent with GsmURange[i]
if GsmLRange[i] value is within [512,885] range, then GsmURange[i] value also must
be [512,885] range
if GsmLRange[i] value is within [0,124] range, then GsmURange[i] value must be within
[0,124] range
if GsmLRange[i] value is within [955,1023] range, then GsmURange[i] also must be
within [955,1023] range
if GsmLRange[i] value is within [259, 293] range, then GsmURange[i] also must be
within [259, 293] range
2-9
if GsmLRange[i] value is within [128, 251) range, then GsmURange[i] also must be
rncFunction
Uuarfcn[8]
Luarfcn[8] and Uuarfcn[8] are both arrays. The maximum of array elements is is 8 and
the valid number of array elements is FDDFreqRngNum
Luarfcn[i] <Uuarfcn[i], i=[0,FDDFreqRngNum-1]
Luarfcn[i] value range should keep consistent with Uuarfcn[i]
if Luarfcn[i] value is within [10562,10838] range, then Uuarfcn[i] value also must be
within [10562,10838] range
if Luarfcn[i] value is within ([9662,9938],412, 437, 462, 487, 512, 537, 562, 587, 612,
637, 662, 687), then Uuarfcn[i] value also must be within ([9662,9938],412, 437, 462,
487, 512, 537, 562, 587, 612, 637, 662, 687) range
Luarfcn[8]
Related Object
Related Parameter
if Luarfcn[i] value is within [1162,1513], then Uuarfcn[i] value also must be within
[1162,1513] range
if Luarfcn[i] value is within ([4357,4458],1007, 1012, 1032, 1037, 1062, 1087), then
Uuarfcn[i] value also must be within ([4357,4458],1007, 1012, 1032, 1037, 1062, 1087)
range
if Luarfcn[i] value is within [2937,3088], then Uuarfcn[i] value also must be within
[2937,3088] range
if Luarfcn[i] value is within ([4387,4413], 1037, 1062), then Uuarfcn[i] value also must be
within ([4387,4413], 1037, 1062) range
If Luarfcn[i] value range is within[1537, 1738]1887, 1912, 1937, 1962, 1987, 2012, 2037,
2062, 2087 then Uuarfcn[i] value also must be within[1537, 1738]1887, 1912, 1937,
1962, 1987, 2012, 2037, 2062, 2087 range
2-10
GPSDataCiperPre
rncFunction
DesCiphKeyFlag
Only when GPSDataCiperPre value is "1: True", related parameters is valid
CiphSerNum
EndSfFactor
rncFunction
StartSfFactor
EndSfFactor16.8< StartSfFactor30.8
QosNegRenegSwi
rncFunction
UlLowLimNegGBR
Only when QosNegRenegSwi value is not "0: QoS Negotiation Closed, QoS
DlLowLimNegGBR
Renegotiation Closed", related field is valid.
NegGBRLevNum
UlLowLimNegGBR
SubSrv
MaxBitRate
UlLowLimNegGBR must have the corresponding uplink MaxBitRate in SubSrv
Direction
DlLowLimNegGBR
SubSrv
MaxBitRate
DlLowLimNegGBR must have the corresponding downlink MaxBitRate in SubSrv
Direction
PriRedirectRat
rncFunction
Twait
When PriRedirectRat value is 1 or 2Twait value can not be 0
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
SharedNetMode
rncNeInfo
NeType
If SharedNetMode is 0XFF (no networking sharing), PlmnNum should be 1 in all the ex-
PlmnNum
change records for MSCServer (NeTypeBit9=1) and SGSN (NeTypeBit12=1) in table rnc-
MCC[i]
NeInfo; CC[], MNC[] and NEID[] should be unique
MNC[i]
NeId[i]
InitRrcOnDch
drbc
CsRrcOnFachSwch
If InitRrcOnDch is 2(foeced FACH), CsRrcOnFachSwch can not be 0
AmrRncAdjust
drbc
DrbcSwch
if AmrRncAdjust is 0 and DrbcSwch is 0 or 2 in drbc, DtcpEaThd and DtcpEbThd are invalid
DtcpEaThd
DtcpEbThd
PlmnSelectMethod
rncFunction
SharedNetMode
Only if SharedNetMode is 1(MOCN), PlmnSelectMethod is valid
2-11
2.2.2 RNC Configuration Supplement Information(rncBRnc)

Original Pa-
Related Ob-
Related Parame-
rameter
ject
ter
X1
rncBRnc
X2
X1<=X2
Y1
rncBRnc
Y2
Y1<=Y2
PsInter-
rncBRnc
DtmSuppInd
Only when PsInterSysHoSupp value is 1, then DtmSuppInd
SysHoSupp
RrcSetupRe-
value is 1. Otherwise, DtmSuppInd value is 0

rncBRnc
TRrcSetupRetran
traNum
If RrcSetupRetraNum value is larger than 0, then related field

can not be 0
MaxBerTar-
rncBRnc
MinBerTarget
MaxBerTarget >= MinBerTarget
get
2.2.3 NodeB Configuration Information (nodeB)

Original
Related Ob-
Related Parame-
rameter
Pa-
ject
ter
NodebNo
NdbAlc
NodebNo
The parameters in this table must be in NdbAlc
NodebNo(Tar-
utrallCell
NodebNo(Source
The related parameters in utrallCell must be in this table
get Index)
NodebType
Index)
nodeB
FuncVer
When NodebType value is 0 General NodeB or 2 Home

NodeB then FuncVer is invalid
NodebNo
NdbPort
NodebNo
The parameters in this table are valid only when at least one
UseType
NCP link and one CCP link are configured in the related
CCPId
tables
That is to say, the corresponding records are valid only
when there are one USET_CTRLPORT link and one
USET_COMPORT link in the related tables.
HsSharMet-
nodeB
HsSharUptPrd
hod
HsSharMet-
Only when HsSharMethod value is 1: RNC controlHsSharUptPrd is valid
CHspa
HsShareInd
hod
The HsShareInd field of the cells under the Node B is valid only
when the HsSharMethod field of the Node B is set to 1(RNC
Control)
PlmnNum
nodeB
MCC4RANShar-
Only if PlmnNum is not 0, the related parameters is valid
ing[]
MNC4RANSharing[]
MinCEPercent[]
2-12
SJ-20100603155704-001|2011-04-09(R2.2)
2.2.4 UE Timers and Constants Information (ueCnst)

Null
2.2.5 CN System Information (cnInfo)

Original Pa-
Related Ob-
Related Parame-
rameter
ject
ter
MCC
rncNeInfo
PlmnNum
MCC+MNC of the cnInfos record must be selected from valid
MCC[]
MCC[i] + MCC[i] (i= [0, PlmnNum-1]) of the rncNeInfos recor
MNC[]
ds which NeType is RNC
Kcs
MbmsModPrdCoeff=max(Kcs, Kps)
MNC
MbmsMod-
cnInfo
PrdCoeff
Kps
2.2.6 Iu Interface Timers and Constants Information (iuCnst)

Original Pa-
Related Ob-
Related Parame-
rameter
ject
ter
TigOR
iuCnst
TinTR
TigOR<=TinTR
2.2.7 UL Scrambling Code Configuration Information In RCP

(rcpSc)
Original
Related
Related
Parameter
Object
Parameter
Module
MODULE
Module
The parameters in this table must be in MODULE, and the

record numbers of ModuleType must be MT_3G_CMP_RNC
in MODULE
MbmsRcpInd
rcpSc
null
The record number that MbmsRcpInd is 1(MBMS RCP) can

not be exceed 1
RcpScrStartId
rcpSc
RcpScrEndId
1. RcpScrEndId > RcpScrStartId, and RcpScrEndId-RcpS

crStartId >5000
2. Segments of scrambling codes of different RCPs can
not overlap
2-13
SJ-20100603155704-001|2011-04-09(R2.2)
2.2.8 FACH Traffic Control Information (trfCtl)

Original Pa-
Related Ob-
Related Parame-
rameter
ject
ter
MacCFlowC-
trfCtl
MacCDTimer
2* MacCFlowCtrlPrd<= SlideWinSize < MacCDTimer
trlPrd
SlideWinSize
2.2.9 Dynamic Radio Bearer Control Information (drbc)
2-14
SJ-20100603155704-001|2011-04-09(R2.2)
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
DrbcSwch
drbc
FachE4aThd
Only when DrbcSwch is 0(Ul Closed &Dl Closed), related parameters are invalid
DchE4aThd
DchE4bThd
PchHoldTimeThr
ToFtimesThr
FachSwch
PchSwch
DchAdjRateSwch
InitialRateUl
InitialRateDl
ETtiEaThd
ETtiEbThd
2-15
drbc
AmrRncAdjust
rncFunction
ToFtimesThr
drbc
DxHsBo0E4bThd
ToFtimesThr<= DxHsBo0E4bThd
PsRateLmtLowC
SubSrv
MaxBitRate
The association table must contains the corresponding rate for the uplink / downlink con-
Direction
nection
MaxBitRate
Direction
nection
PsRateLmtHighC
SubSrv
DtcpEaThd
If DrbcSwch is 0 or 2, and AmrRncAdjust is 0, related parameters are invalid
DtcpEbThd
FToPchThd
drbc
FToIdleThd
FToPchThd < FToIdleThd
ToFtimesThr
drbc
DToPchThd
ToFtimesThr < =DToPchThd
DToPchThd
drbc
DToIdleThd
DToPchThd < DToIdleThd
ToFtimesThr
drbc
DToIdleThd
ToFtimesThr <= DToIdleThd
DToPchThd
drbc
DToIdleThd
DToPchThd < DToIdleThd
DrbcSwch
Related Object
Related Parameter
UlPwrDasf
drbc
DchAdjRateSwch
If UlPwrDasf or DlPwrDasf is Open, then DchAdjRateSwch must be Open
QosSeg
UlRateAdjLevNum
UlRateAdjLev[UlRateAdjLevNum-1]>=InitialRateUl>= UlRateAdjLev[0]
DlPwrDasf
InitialRateUl
UlRateAdjLev[i]
InitialRateDl
QosSeg
DlRateAdjLevNum
DlRateAdjLev[DlRateAdjLevNum-1]>=InitialRateDl>= DlRateAdjLev[0]
DlRateAdjLev[i]
InitialRateUl
SubSrv
InitialRateDl
EttiTraffVolSwch
CsRrcOnFachSwch
drbc
rncFunction
MaxBitRate
Direction
nection
ETtiEaThd
If EttiTraffVolSwch is 0(OFF), then the associated fields ETtiEaThd and ETtiEabThd are
ETtiEbThd
invalid
InitRrcOnDch
if InitRrcOnDch is 2 (Forced FACH)CsRrcOnFachSwch can not be 0
2-16
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
2.2.10 Global Access Control (GloAc)

Null
2.2.11 Hspa Configuration Information (Hspa)

Original Pa-
Related Ob-
Related Parame-
rameter
ject
ter
CqiCycle
Hspa
CqiRepFactor
If CqiCycle is 0, CqiRepFactor is invalid; if CqiCycle is not 0,

this equation is satisfied: CqiCycle >= 2* CqiRepFactor
MaxNu-
rncFunction
MaxNumOfAct
MaxNumOfEdchAct<=MaxNumOfAct
Hspa
EdpcchPOTti10
EdpcchPOTti2>EdpcchPOTti10
Hspa
ScheInfoPOTti10
ScheInfoPOTti2>=ScheInfoPOTti10
DtxDrxSwch
Hspa
RtDtxDrxSwch
RtDtxDrxSwch is valid only if DtxDrxSwch is 1
HsscLessS-
Hspa
NVHsscLessS-
NVHsscLessSwch is valid only if HsscLessSwch is 1 (Open)
mOfEdchAct
EdpcchPOTti2
ScheInfoPOTti2
wch
HsscPwrOfst-
wch
SubSrv
HsscchPwrOffset
HsscchPwrOffset is valid only if HsscPwrOfstPre is TRUE
CHspa
HspaPwrRatio
HspaPwrRatio is valid only if HsdschTotPwrMeth is 0 (RNC
Pre
HsdschTotPwrMeth
HsdschTotP-
Static Assigning Mode) or 1 (RNC Dynamic Assigning Mode)

CHspa
MinHspaPwrRto
MinHspaPwrRto and MaxHspaPwrRto are valid only if Hsd-
MaxHspaPwrRto
schTotPwrMeth is 1 (RNC Dynamic Assigning Mode)
Rnc64QAMInd
Rnc64QAMInd and RncMIMOInd are valid only if RncEnL2Ind
RncMIMOInd
is 1 (Support)
Hspa
CodeReAssPrd
CodeReAssPrd is valid only if CodeReAssInd is 1 (Support)
CHspa
CodeReAssHy
CodeReAssHy is valid only if CodeReAssInd is 1 (Support)
Hspa
DtxDrxSwch
NrtDtxDrxSwch is valid only if DtxDrxSwch is 1 (Open)
rncDtxDrx
DtxCyc2Tti10
DtxCyc2Tti10 and DtxCyc2Tti2 must be divided exactly by the
DtxCyc2Tti2
half value of CqiCycle (CqiCycle/2)
HsdpaCmAsso-
HsupacmAssoMode can be 1 (Parallel) only if HsdpaCmAs-
Mode
soMode is 1 (Parallel)
REtfciTti2T2[i]
At least one node in the related field array has the same value
wrMeth
RncEnL2Ind
CodeRe-
Hspa
AssInd
CodeReAssInd
NrtDtxDrxSwch
CqiCycle
HsupaCmAs-
Hspa
soMode
EtfciBstTti2T2
EdchRc
with the corresponding field in the table
2-17
SJ-20100603155704-001|2011-04-09(R2.2)
Original Pa-
Related Ob-
Related Parame-
rameter
ject
ter
EtfciBstTti2T3
EdchRc
REtfciTti2T3[i]
At least one node in the related field array has the same value
with the corresponding field in the table
EDchAct-
Hspa
SizeInd
RncFdpch-
Hspa
MaxNumOfEd-
When EDchActSizeInd in this table is true, MaxNumOfEd-
chAct
chAct in the Hspa is 3
RncEfdpchSupInd
When RncFdpchSupInd is support, RncEfdpchSupInd can
SupInd
be support
2.2.12 Limiting HSDPA GBR Resource Consumption information

(GbrRes)
Original Parame-
Related Object
Related Parameter
CHspa
CHsGBRResLmtIdx
The field in CHspa must have existed in GbrRes
SubSrv
MaxBitRate
The valid HsGBRLev[MAX_NUM_HS_GBR]
Direction
must have the corresponding downlink match-
ter
HsGBRResLimitIdx
HsGBRLevNum
HsGBRLev[MAX_
NUM_HS_GBR]
HsGBRLevNum
ing rate in the association table

GbrRes
HsGBRLev[]
When HsGBRLevNum is larger than 1, the

following limits apply to the valid array element: HsGBRLev[0]< HsGBRLev[1]< HsGBRLev[2]<< HsGBRLev[HsGBRLevNum-1]
2.2.13 MBMS Configuration Information (Mbms)

Original Parame-
Related Object
Related Parameter
AccInfoPrdCoeff
Mbms
RepPrdCoeff
AccInfoPrdCoeff>= RepPrdCoeff
MinSccpchforMtch
Mbms
MaxSccpchforMtch
MaxSccpchforMtch>= MinSccpchforMtch
MinFachIdforMtch
Mbms
MaxFachIdforMtch
MaxFachIdforMtch>= MinFachIdforMtch
MaxMFPLc
Mbms
MFPIncStep
MFPIncStep <=MaxMFPLc
MaxMFPLc
Mbms
MFPDecStep
MFPDecStep <=MaxMFPLc
ThreshForHalfIsd
Mbms
ThreshForIsd
ThreshForHalfIsd>ThreshForIsd
ter
2-18
SJ-20100603155704-001|2011-04-09(R2.2)
2.2.14 CFN Offset Configuration Information

Original
Related
Related
Pa-
Parameter
Object
rameter
SigType
CfnOffset
RetranRate
When SigType=2&FstRecfgInd=0, the records of Re-
FstRecfg-
tranRate=0 10 20 50 70 100 must be configured, and
Ind
there can be only one record correspond to one value

of RetranRate
SigType
CfnOffset
RetranRate
Only
if
the
two
parameters
are
Sig-
FstRecfg-
Type=2&FstRecfgInd=0, the corresponding fields is
Ind
valid
2.2.15 Qos Configuration

2.2.15.1 Qos Configuration(QosSeg)
2-19
SJ-20100603155704-001|2011-04-09(R2.2)
Related Object
Related Parameter
ARPThresh[15]
QosSeg
ARPSegNum
ARPThresh[15] is an array. The maximum number of array elements is 15. The valid
number of array elements is ARPSegNum-1
When ARPSegNum is larger than 2, ARPThresh[0]<ARPThresh[1]<ARPThresh[2]<
<ARPThresh[ARPSegNum-2]
THPThresh[15]
QosSeg
THPSegNum
THPThresh[15] is an array. The maximum number of array elements is 15. The valid
number of array elements is THPSegNum-1
When THPSegNum is larger than 2, THPThresh[0]<THPThresh[1]<THPThresh[2]<<
THPThresh[THPSegNum-2]
BPThresh[15]
QosSeg
BPSegNum
BPThresh[15] is an array. The maximum number of array elements is 15. The valid
number of array elements is BPSegNum -1
When BPSegNum equals to 1, BPThresh is invalid and fixed to 15; when BPSegNum is
larger than 2, BPThresh can not equal to 15 and BPThresh [0]<BPThresh [1]< BPThresh
2-20
[2]<<BPThresh [BPSegNum-2]
UlRateAdjLevNum
SubSrv
UlRateAdjLev[6]
DlRateAdjLevNum
MaxBitRate
Valid UlRateAdjLev[i] must have the corresponding uplink MaxBitRate in SubSrv
Direction
SubSrv
DlRateAdjLev[6]
MaxBitRate
Valid DlRateAdjLev[i] must have the corresponding downlink MaxBitRate in SubSrv
Direction
DlRateAdjLevNum
AppPri
RateSeg
value of RateSeg in AppPri must be within [1, DlRateAdjLevNum+1]
UlRateAdjLevNum
QosSeg
UlRateAdjLev[6]
UlRateAdjLev[6] is an array, The maximum number of array elements is 6. The valid

number of array elements is UlRateAdjLevNum
When UlRateAdjLevNum is larger than 1, for valid elements of UlRateAdjLev[6],
UlRateAdjLev [0]< UlRateAdjLev [1]< UlRateAdjLev [2]<< UlRateAdjLev
[UlRateAdjLevNum-1]
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
DlRateAdjLevNum
QosSeg
DlRateAdjLev
DlRateAdjLev[6] is an array, The maximum number of array elements is 6. The valid

number of array elements is DlRateAdjLevNum
When DlRateAdjLevNum is larger than 1, for valid elements of DlRateAdjLev[6],
DlRateAdjLev [0]< DlRateAdjLev [1]< DlRateAdjLev [2]<< DlRateAdjLev
[DlRateAdjLevNum-1]
2-21
2.2.15.2 Basic Priority Management (BasPri)

Original Pa-
Related Ob-
Related Parame-
rameter
ject
ter
ARPSeg
QosSeg
ARPSegNum
The value of ARPSeg must be within [1, ARPSegNum]

Each record corresponding to the vaule of ARPSeg in the
range of [1, ARPSegNum] must be configured
TrafficClass
QosSeg
THPSegNum
The value range [4, 18] of TrafficClass corresponds to the

value range [1, 15] of THPSegNum for interactive services
Each record corresponding to each value of TrafficClass in
the range of [4~THPSegNum+3] must be configured
TrafficClass
LdCtrl
UlHighLd
DchUlAcThresh in the BPriAc corresponds to the BasicPrio
BasicPrio
BPriAc
BasicPrio
in the BasPri that satisfied TrafficClass=0 must more than
DchUlAcThresh
UlHighLd in LdCtrl
TrafficClass
LdCtrl
DlHighLd
DchUlAcThresh in the BPriAc corresponds to the BasicPrio
BasicPrio
BPriAc
BasicPrio
in the BasPri that satisfied TrafficClass=0 must more than
DchDlAcThresh
UlHighLd in LdCtrl
2.2.15.3 Scheduling Priority Management (SchPri)

Null
2.2.15.4 Application Priority Configuration Information (AppPri)

Original Pa-
Related Ob-
Related Parame-
rameter
ject
ter
BPSeg
QosSeg
BPSegNum
The value of BPSeg must be within [1, BPSegNum]. For one

AppPriIndex, records that contain all vaules of BPSeg must be
configured
RateSeg
QosSeg
Direction
DlRateAd-
The value of RateSeg in AppPri must be within [1,
jLevNum
DlRateAdjLevNum+1]
For one AppPriIndex, records that contain all vaules of
RateSeg must be configured
RateSeg
QosSeg
Direction
UlRateAd-
The value of RateSeg in AppPri must be within [1,
jLevNum
UlRateAdjLevNum+1]
For one AppPriIndex, records that contain all vaules of
RateSeg must be configured
Direction
AppPri
BearerType
Direction is 0(Uplink), then BearerType can not be 2(MBMS).

Consistent to the MBMS service, the uplink application priority
is an invalid field
2-22
SJ-20100603155704-001|2011-04-09(R2.2)
2.2.15.5 Access Control Related to Basic Priority (BPriAc)
2-23
SJ-20100603155704-001|2011-04-09(R2.2)
Related Object
Related Parameter
BPriAcIndex
UtranCell
BPriAcIndex
BPriAcIndex of UtranCell must have the corresponding BPriAcIndex with the same value
in BPriAc
BasicPrio
BPriAc
null
For one BPriAcIndex, records that contain all values of BasicPrio must be configured in
BPriAc
ThreshRefCount
BPriAc
MbmsAcThresh
HsdpaAcThresh
UtranCell
BPriAcIndex
DchUlAcThresh
LdCtrl
NodeBSafeThr
UtranCell
BPriAcIndex
LdCtrl
UlOverLd
ThreshRefCount <= MbmsAcThresh

NodeBSafeThr > Values of all the records of HsdpaAcThresh of BPriAc which has the
same BPriAcIndex as that in UtranCell
UlSeriousOverLd > UlOverLd > Values of all the records of DchUlAcThresh of BPriAc which
has the same BPriAcIndex as that in UtranCell
UlSeriousOverLd
2-24
DchDlAcThresh
UtranCell
BPriAcIndex
LdCtrl
DlOverLd
DlSeriousOverLd > DlOverLd >Values of all the records of DchDlAcThresh of BPriAc which
has the same BPriAcIndex as that in UtranCell
DlSeriousOverLd
MbmsAcThresh
UtranCell
BPriAcIndex
LdCtrl
DlOverLd
DlSeriousOverLd
BasicPrio
DchUlAc-
Thresh
LdCtrl
UlHighLd
BasPri
TrafficClass
ThreshRefCount <= MbmsAcThresh

DlSeriousOverLd > DlOverLd > Values of all the records of MbmsAcThresh of BPriAc
which has the same BPriAcIndex as that in UtranCell > DlAlrmLd
DchUlAcThresh in the BPriAc corresponds to the BasicPrio in the BasPri that satisfied
TrafficClass=0 must more than UlHighLd in LdCtrl
BasicPrio
BasicPrio
Thresh
DchDlAc-
LdCtrl
UlHighLd
BasPri
TrafficClass
BasicPrio
DchUlAcThresh in the BPriAc corresponds to the BasicPrio in the BasPri that satisfied
TrafficClass=0 must more than UlHighLd in LdCtrl
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
2.2.16 Intra-frequency Measurement

2.2.16.1 UE Intra-frequency Measurement Configuration (Intra)
2-25
SJ-20100603155704-001|2011-04-09(R2.2)
Related Object
Related Parameter
IntraMeasCfgNo
CIntra
EvtMeasEcNo
The values of parameters in CIntra must exist in this table
EvtMeasRSCP
PrdMeasEcNo
PrdMeasRSCP
EvtMeasEcNo2
EvtMeasRSCP2
IntraMeasCfgNo
Intra
IntraMeasCfgNote
For each value of IntraMeasCfgNote, there must be at least one corresponding record to
be configured
IntraMeasCfgNote
Intra
MeasQuantity
The values of InterMeasCfgNote , MeasQuantity and RptCrt must be according to:
RptCrt
When IntraMeasCfgNote is 0(UE Period Report Parameters for CPICH Ec/No),

MeasQuantity must be 0(CPICH Ec/No) and RptCrt must be 3(Periodical Reporting
Criteria)
2-26
When IntraMeasCfgNote is 3(UE Inter-Freq Event Measurement Cofiguration Number

for CPICH EcN0), MeasQuantity must be 0(CPICH Ec/No) and RptCrt must be
2(Inter-frequency Event Reporting Criteria)
When IntraMeasCfgNote is 4(UE Period Measurement Cofiguration Number for CPICH
RSCP), MeasQuantity must be 1(CPICH RSCP) and RptCrt must be 3(Periodical
Reporting Criteria)
When IntraMeasCfgNote is 7(UE Inter-Freq Event Measurement Cofiguration Number

for CPICH RSCP), MeasQuantity must be 1(CPICH RSCP) and RptCrt must be
When IntraMeasCfgNote is 8(UE Inter-frequency Event Report Parameters for
CPICH Ec/No(GSM)), MeasQuantity must be 0(CPICH Ec/No) and RptCrt must be
When IntraMeasCfgNote is 9(UE Inter-frequency Event Report Parameters for
CPICH Ec/No(GSM)), MeasQuantity must be 1(CPICH RSCP) and RptCrt must be
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
RptCrt
Intra
MeasEvtNum
Only when the value of RptCrt is 1(Event Reporting Criteria), related parameters are valid
MeaEvtId[]
Hysteresis[]
TrigTime[]
RptCrt
RptCrt
Intra
Intra
PrdRptAmount
Only when the value of RptCrt is 3(Periodical Reporting Criteria), related parameters are
PrdRptInterval
valid
ThreshUsedFreq[]
Only when the value of RptCrt is 2(Event Reporting Criteria) and MeaEvtId is 2b/2d/2f,
MeaEvtId[]
related parameter is valid
MeasQuantity
And when MeasQuantity is CPICH RSCP, the value range of ThreshUsedFreq is [-115,
-25] dBm. When MeasQuantity is CPICH Ec/No, the value range of ThreshUsedFreq
is [-24, 0] dB
2-27
RptCrt
Intra
Wused[]
MeaEvtId[]
RptCrt
Only when the value of RptCrt is 2(Event Reporting Criteria) and MeaEvtId is 2a/2b/2d/2f,
related parameters are valid
Intra
ThreshNoUsedFreq[]
Only when the value of RptCrt is 2(Event Reporting Criteria) and MeaEvtId is 2b/2c/2e),
MeaEvtId[]
MeasQuantity
And when MeasQuantity is CPICH RSCP, the value range of ThreshUsedFreq is [-115,
-25] dBm. When MeasQuantity is CPICH Ec/No, the value range of ThreshUsedFreq
RptCrt
Intra
WnoUsed[]
MeaEvtId[]
RptCrt
MeasQuantity
Only when the value of RptCrt is 2(Event Reporting Criteria) and MeaEvtId is 2a/2b/2c/2e,
Intra
EcN0RptInd
Only when the value of RptCrt is 2(Event Reporting Criteria) and MeasQuantityis CPICH
RscpRptInd
Ec/No, EcN0RptInd and RscpRptInd must all be TRUE
is [-24, 0] dB
2.2.16.2 UE Intra-frequency Measurement Relative to Traffic Category Configuration

Information (CIntra)
2-28
SJ-20100603155704-001|2011-04-09(R2.2)
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
TrfCatIntraMIdx
UtranCell
TrfCatIntraMIdx
EvtMeasEcNo
Intra
IntraMeasCfgNo
CIntra
TrfCategory
When TrfCategory is 0xff, PrdMeasEcNo, PrdMeasRSCP, EvtMeasDctEcNo and
EvtMeasRSCP
PrdMeasEcNo
PrdMeasRSCP
EvtMeasDctEcNo
EvtMeasDctRSCP
EvtMeasEcNo
EvtMeasRSCP
EvtMeasDctRSCP are valid, but EvtMeasEcNo and EvtMeasRSCP are invalid
PrdMeasEcNo
When TrfCategory is not 0xffPrdMeasEcNo, PrdMeasRSCP, EvtMeasDctEcNo and
PrdMeasRSCP
EvtMeasDctRSCP is invalidbut EvtMeasEcNo and EvtMeasRSCP are valid
EvtMeasDctEcNo
2-29
EvtMeasDctRSCP
PrdMeasEcNo
Intra
IntraMeasCfgNote
The corresponding parameters in Intra must be 2(Period Report Parameters for CPICH
Ec/No)
EvtMeasEcNo
Intra
IntraMeasCfgNote
The corresponding parameters in Intra must be 2(Event Report Parameters for CPICH
Ec/No)
R7Intra
IntraMeasCfgNote
The corresponding parameters in Intra must be 5(Period Report Parameters for CPICH
RSCP)
EvtMeasRSCP
Intra
IntraMeasCfgNote
The corresponding parameters in Intra must be 7(Event Report Parameters for CPICH
RSCP)
EvtMeasDctEcNo
Intra
IntraMeasCfgNote
The corresponding parameters in Intra must be 10(Detected Set Measearment Parameters

for CPICH Ec/No)
EvtMeasDctRSCP
Intra
IntraMeasCfgNote
The corresponding parameters in Intra must be 11(Detected Set Measearment Parameters

for CPICH RSCP)
TrfCategory
CIntra
All the values of TrfCategory should be configured
PrdMeasRSCP
2.2.17 Inter-frequency Measurement

2.2.17.1 UE Inter-frequency Measurement Configuration (Inter)
2-30
SJ-20100603155704-001|2011-04-09(R2.2)
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
InterMeasCfgNo
CInter
EvtMeasEcNo
Before the record of Inter is deleted, It must be ensured that there is no CInters record
EvtMeasRSCP
which quotes the InterMeasCfgNo. Otherwise, this record with the InterMeasCfgNo
PrdMeasEcNo
in Inter is not allowed to delete
(Target Index)
PrdMeasRSCP
(Source Index)
IntraMeasCfgNo
Intra
IntraMeasCfgNo
RptCrt
InterMeasCfgNo
When RptCrt is 1(Intra-frequency Event Reporting Criteria), There must be a record with
corresponding IntraMeasCfgNo in Intra
Inter
InterMeasCfgNote
For each value of InterMeasCfgNote, there must be at least one corresponding record to
be configured
InterMeasCfgNote
Inter
MeasQuantity
When InterMeasCfgNote is 0(UE Period Report Parameters for CPICH Ec/No),
RptCrt
MeasQuantity must be 0(CPICH Ec/No) and RptCrt must be 3(Periodical Reporting
2-31
Criteria)
When InterMeasCfgNote is 3(UE Inter-frequency Event Report Parameters for CPICH
Ec/No), MeasQuantity must be 0(CPICH Ec/No) and RptCrt must be 2(Inter-frequency
Event Reporting Criteria)
When InterMeasCfgNote is 4(UE Period Report Parameters for CPICH RSCP),
MeasQuantity must be 1(CPICH RSCP) and RptCrt must be 3(Periodical Reporting
When InterMeasCfgNote is 7(UE Inter-frequency Event Report Parameters for CPICH
RSCP), MeasQuantity must be 1(CPICH RSCP) and RptCrt must be 2(Inter-frequency
RptCrt
Inter
IntraMeasCfgNo
RptCrt
Inter
MeasEvtNum
Only when RptCrt is 2(Inter-frequency Event Reporting Criteria), related parameters
MeaEvtId[6]
are valid
Hysteresis[6]
TrigTime[6]
Only when RptCrt is 1(Intra-frequency Event Reporting Criteria), IntraMeasCfgNo is valid
Criteria)
Related Object
Related Parameter
RptCrt
Inter
PrdRptAmount,
Only when RptCrt is 3(Periodical Reporting Criteria), related parameters are valid
PrdRptInterval
RptCrt
Inter
ThreshUsedFreq[6]
Only when RptCrt is 2(Inter-frequency Event Reporting Criteria) and MeaEvtId[i] (i= [1,
MeaEvtId[6]
MeasEvtNum]) is 1(2b) /3(2d)/ 5(2f), related parameters are valid
MeasQuantity
And when MeasQuantity is 1(CPICH RSCP), the value range of ThreshUsedFreq is [-115,
-25] dBm; when MeasQuantity is 0(CPICH Ec/No), thevalue range of ThreshUsedFreq
is [-24, 0] dB
RptCrt
Inter
Wused[6]
MeaEvtId[6]
RptCrt
Only when RptCrt is 2(Inter-frequency Event Reporting Criteria) and MeaEvtId[i]( i=[1,
MeasEvtNum]) is 0(2a) / 1(2b) / 3(2d) / 5(2f), related parameters are valid
Inter
ThreshNoUsedFreq[6]
2-32
MeaEvtId[6]
MeasEvtNum]) is 1(2b) /2(2c)/ 4(2e), related parameters are valid
MeasQuantity
And when MeasQuantity is 1(CPICH RSCP), the value range of ThreshUsedFreq is [-115,
-25] dBm; when MeasQuantity is 0(CPICH Ec/No), thevalue range of ThreshUsedFreq
is [-24, 0] dB
RptCrt
Inter
WnoUsed[6]
MeaEvtId[6]
RptCrt
MeasEvtNum]) is 0(2a) /1(2b) /2(2c)/ 4(2e), related parameters are valid
Inter
MeasQuantity
EcN0RptInd,
When RptCrt is 2(Inter-frequency Event Reporting Criteria), if MeasQuantity is 0(CPICH
RscpRptInd
Ec/No), EcN0RptInd must be 1(True)

if MeasQuantity is 1(CPICH RSCP), RscpRptInd must be 1(True)
UTRACarrierRSSI
Inter
null
Accoriding to TS 25.331, UTRACarrierRSSI must be fixed to 0(False)
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
2.2.17.2 UE Inter-frequency Measurement Relative to Traffic Category (CInter)
2-33
SJ-20100603155704-001|2011-04-09(R2.2)
Related Object
Related Parameter
TrfCatInterMIdx
UtranCell
TrfCatInterMIdx
The values of parameters in this table must be in UtranCell
EvtMeasEcNo
Inter
InterMeasCfgNo
The values of parameters in this table must be in Inter
CInter
TrfCategory
When TrfCategory is 0xffPrdMeasEcNo and PrdMeasRSCP are valid but EvtMeasEcNo,
EvtMeasRSCP
PrdMeasEcNo
PrdMeasRSCP
EvtMeasEcNo2
EvtMeasRSCP2
EvtMeasEcNo
EvtMeasRSCP
EvtMeasRSCP, EvtMeasEcNo2 and EvtMeasRSCP2 are invalid
PrdMeasEcNo
When TrfCategory is not 0xff PrdMeasEcNo and PrdMeasRSCP are invalid but
PrdMeasRSCP
EvtMeasEcNo, EvtMeasRSCP, EvtMeasEcNo2 and EvtMeasRSCP2 are valid
EvtMeasEcNo2
2-34
EvtMeasRSCP2
PrdMeasEcNo
Inter
InterMeasCfgNote
The related parameters must be 0(UE Period Report Parameters for CPICH Ec/No)
EvtMeasEcNo
Inter
InterMeasCfgNote
The related parameters must be 3(UE Inter-Freq Event Report Parameters for CPICH
Ec/No)
PrdMeasRSCP
Inter
InterMeasCfgNote
The related parameters must be 4(UE Period Report Parameters for CPICH RSCP)
EvtMeasRSCP
Inter
InterMeasCfgNote
The related parameters must be 7(UE Inter-Freq Event Report Parameters for CPICH
RSCP)
EvtMeasRSCP2
Inter
InterMeasCfgNote
The InterMeasCfgNotemust be 9(UE Inter-frequency Event Report Parameters for CPICH

RSCP)
EvtMeasEcNo2
Inter
InterMeasCfgNote
The InterMeasCfgNotebe 8(UE Inter-frequency Event Report Parameters for CPICH

Ec/No)
TrfCategory
CInter
TrfCatInterMIdx
For one TrfCatInterMIdx, records corresponding to all values of TrfCategory must be configured in CInter
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
2.2.18 Inter-Rat Measurement

2.2.18.1 UE Inter-Rat Measurement Configuration Information (Rat)
2-35
SJ-20100603155704-001|2011-04-09(R2.2)
Related Object
Related Parameter
InterRatCfgNo
CRat
EvtMeasEcNo
The values of related parameters in CRat must be in this table
EvtMeasRSCP
PrdMeasEcNo
PrdMeasRSCP
InterRatCfgNo
Rat
InterRatCfgNote
For each value of InterRatCfgNote, there must be at least one corresponding record to
be configured
InterRatCfgNote
Rat
OwOMMeasQuantity
When InterRatCfgNote is 0(Period Report Parameters for Own System CPICH Ec/No),
RptCrt
OwOMMeasQuantity must be 0(CPICH Ec/No) and RptCrt must be 2(Periodical

Reporting Criteria)
When InterRatCfgNote is 2(UE Event Report Parameters for Own System CPICH
Ec/No), OwOMMeasQuantity must be 0(CPICH Ec/No) and RptCrt must be 1(Inter-RAT
2-36
When InterRatCfgNote is 3(Period Report Parameters for Own System CPICH RSCP),
OwOMMeasQuantity must be 1(CPICH RSCP) and RptCrt must be 2(Periodical
Reporting Criteria)
When InterRatCfgNote is 5(UE Event Report Parameters for Own System CPICH
RSCP), OwOMMeasQuantity must be 1(CPICH RSCP) and RptCrt must be 1(Inter-RAT
Event Reporting Criteria).
UtranEstQual
Rat
null
According to TS 25.331, UtranEstQual must be 0(False)
RptCrt
Rat
EventNum
Only when RptCrt is 1(Inter-RAT Event Reporting Criteria), related parameters are valid
EventId[]
Thresh[]
W[]
ThreshSys[]
Hysteresis[]
TrigTime[]
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
RptCrt
Rat
Thresh[]
Only when RptCrt is 1(Inter-RAT Event Reporting Criteria) and EventId [i] (i= [1,
EventId[]
EventNum]) is 0(3a), related parameters are valid
OwOMMeasQuantity
And when OwOMMeasQuantity is 1(CPICH RSCP), the value range of Thresh is [-115,
-25] dBm; when OwOMMeasQuantity is 0(CPICH Ec/No), the value range of Thresh
is [-24, 0] dB
RptCrt
Rat
W[]
EventId[]
RptCrt
EventId[]
Only when RptCrt is 1(Inter-RAT Event Reporting Criteria) and EventId [i]( i=[1,
EventNum]) is 0(3a), related parameters are valid
Rat
ThreshSys[]
Only when RptCrt is 1(Inter-RAT Event Reporting Criteria) and EventId [i]( i=[1,
EventNum]) is 0(3a)/1(3b)/2(3c), related parameters are valid
2-37
2.2.18.2 UE Inter-Rat Measurement Relative to Traffic Category (CRat)
2-38
SJ-20100603155704-001|2011-04-09(R2.2)
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
TrfCatRatMIdx
UtranCell
TrfCatRatMIdx
The related parameters in this table must be in UtranCell
EvtMeasEcNo
Rat
InterRatCfgNo
The related parameters in this table must be in UtranCell
Rat
TrfCategory
When TrfCategory is 0xffPrdMeasEcNo and PrdMeasRSCP is valid EvtMeasEcNo and
EvtMeasRSCP
PrdMeasEcNo
PrdMeasRSCP
EvtMeasEcNo
EvtMeasRSCP
EvtMeasRSCP is invalid
PrdMeasEcNo
When TrfCategory is not 0xffPrdMeasEcNo and PrdMeasRSCP is invalid EvtMeasEcNo
PrdMeasRSCP
and EvtMeasRSCP is valid
PrdMeasEcNo
Rat
InterRatCfgNote
The related parameters in Rat must be 0Period Report Parameters for Own System CPICH
Ec/No)
2-39
EvtMeasEcNo
Rat
InterRatCfgNote
The related parameters in Rat must be 2 UE Event Report Parameters for Own System
CPICH Ec/No
PrdMeasRSCP
Rat
InterRatCfgNote
The related parameters in Rat must be 3Period Report Parameters for Own System CPICH
RSCP
EvtMeasRSCP
Rat
InterRatCfgNote
The related parameters in Rat must be 5 UE Event Report Parameters for Own System
TrfCategory
CRat
TrfCatRatMIdx
For one TrfCatRatMIdx, records corresponding to all values of TrfCategory must be configured in CRat
CPICH RSCP
2.2.19 Service Basic Configuration Information (SubSrv)
2-40
SJ-20100603155704-001|2011-04-09(R2.2)
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
SrvType
SrvTfs
SrvType
The associated field in the association table must exist in this table
SrvPhy
The associated field in the association table must exist in this table. When SrvType
RlcAm
value is [6,250], then the record in this table must exist in RlcAm or RlcTU, and RlcMode
Pdcp
corresponds to records in RlcTU must be TM or UM, and RlcMode corresponds to
TrfPc
records in RlcAm must be AM
DivPc
TrfAc
DivAc
SubflowNum
RlcTU
SubflowId
SrvTfs
In the association table, the SubflowId value should be fewer than the SubflowNum value
in this table, and the number of the records of the same service sub-class must be the
same value as the SubflowNum value in this table
SrvType
SrvPhy
SigSrvNo
When the associated field SigSrvNo in the association table is not 0xff, then it must exist
2-41
in this table
SrvType
SubSrv
Direction
When SrvType is an even number, the Direction is Uplink; When SrvType is an odd number,
the Direction is Downlink
SrvType
SubSrv
RlcMode
Only when SrvType value is [6,250], then the associated field is valid
Domain
SubSrv
Alfa
Only when Domain is CS Domain and TrafficClass is conversational, Alfa is 1. Otherwise

Alfa must be 1
SrvType
SubSrv
HsscchPwrOffset
If SrvType is odd number, the related parameters are valid
RbParaCfgType
SubSrv
Domain
When Domain value is 0(CS Domain), RbParaCfgType, PreRbCfgId, PreConfValTag fields
PreRbCfgId
PreConfValTag
are valid
TrafficClass
Related Object
Related Parameter
PreRbCfgId
SubSrv
MaxBitRate
When with the same MaxBitRate, Domain(CS), TrafficClass value, and the
Domain
RbParaCfgType is True, two record's PreRbCfgId value must be the same (i.e., the
TrafficClass
uplink/downlink service with the same MaxBitRate, Domain, TrafficClass, must have
RbParaCfgType
the same pre-defined configuration tag.)

When with the different MaxBitRate, Domain(CS), TrafficClass value, and the
RbParaCfgType is True, two record's PreRbCfgId value must be different (i.e., the
different service must have the different PreRbCfgId value.)
PreRbCfgId
SubSrv
PreConfValTag
PreConfValTag
SubSrv
Domain
When Domain value is 0(CS Domain), RbParaCfgType, PreRbCfgId, PreConfValTag
RbParaCfgType
fields are valid
MaxBitRate
MaxBitRate,Domain and TrafficClass are have the same values
Domain
The two records of RbParaCfgType which is true must be same
TrafficClass
2-42
RbParaCfgType
RbParaCfgType
PreConfValTag
RbParaCfgType
SubSrv
SrvTfs
BLERtarget
When RbParaCfgType is true and BLERtarget is modified, the value of PreConfValTag
PreConfValTag
must be changed
TfNum
If the RbParaCfgType in this table is TRUE, when the fields in SrvTfs change, including
TBNum[]
TfNum, TBNum[], RlcSize[], TTI,CodingRate, RM, CRCSize, the field in this table PreCon-
RlcSize[]
fValTag value must change too
TTI
CodingRate
RM
CRCSize
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
PreConfValTag
SrvPhy
CtfcNum
If RbParaCfgType in this table is TRUE, CtfcNum, Ctfc[] in table SrvPhy change or UlD-
Ctfc[]
pcchSlotFmt,, TfciPresence, MplexPos, GainFactorCfg[i],BetaC[i], BetaD[], RefTfc[] fields
UlDpcchSlotFmt
change, the PreConfValTag field value must change too in this table
RbParaCfgType
TfciPresence
MplexPos
GainFactorCfg[]
BetaC[]
BetaD[]
RefTfc[]
PreConfValTag
R8RlcTU
RbParaCfgType
RlcMode
If RbParaCfgType in this table is true, RlcMode is TM or UM, RlcDiscdPre and SegInd
RlcDiscdPre
in RlcTU are changed or RlcDiscdPre is True, TmrDiscd[] is changed, then the value of
SegInd
PreConfValTag must be changed
2-43
TmrDiscd[]
PreConfValTag
RbParaCfgType
RlcAm
If RbParaCfgType in this table is TRUE, RlcMode is AM, and in table RlcAm,DiscdType,
DiscdType
TmrMRW[], TmrDiscd[], MaxMRW, MaxDAT, TxWndSize[], TmrRst[], MaxRst, PollingInfo-
TmrMRW[]
Pre, InSeqDlv, RxWndSize[], TmrStProhPre, MissPduInd or TmrStPrdPre changes or Tm-
TmrDiscd[]
rPollProhPre, TmrPollProh[], TmrPollPre, TmrPoll[], PollPDUPre, PollPDU, PollSDUPre,
MaxMRW
PollSDU, LstTxPDUPoll, LstRetxPDUPoll, PollWndPre, PollWnd, TmrPollPrdPre, TmrPoll-
MaxDAT
Prd[], TmrStProh[], TmrStPrd[] changes within the valid range, then the field in this table
TxWndSize[i]
PreConfValTag value must change too
TmrRst[]
MaxRst
PollingInfoPre
InSeqDlv
RxWndSize[]
TmrStProhPre
MissPduInd
TmrStPrdPre
RlcMode
Related Object
Related Parameter
TmrPollProhPre
TmrPollProh[]
TmrPollPre
TmrPoll[]
PollPDUPre
PollPDU
PollSDUPre
PollSDU
LstTxPDUPoll
LstRetxPDUPoll
PollWndPre
PollWnd
2-44
TmrPollPrdPre
TmrPollPrd[]
TmrStProh[]
TmrStPrd[]
MinBitRate
SubSrv
MaxBitRate
MinBitRate<= MaxBitRate
SrvType
SubSrv
MinBitRate
When SrvType value is 05, MinBitRate is an invalid field
MaxRetransEdch
SubSrv
NhrThrDownTti10[3]
For the nodes of NhrThrUpTti10 and NhrThrDownTti10 i from 0 to 2 they must satisfied
NhrThrUpTti10[3]
:100*MaxRetransEdch >= NhrThrDownTti10[i]>= NhrThrDownTti10[i]
NhrThrUpTti2[3]
For the nodes of NhrThrUpTti2 and NhrThrDownTti2i from 0 to 2 they must satisfied :
NhrThrDownTti2[3]
100*MaxRetransEdch >= NhrThrUpTti2[i]= NhrThrDownTti2[i]
NhrThrUpTti10[3]
NhrThrUpTti10[0]<= NhrThrUpTti10[1]<= NhrThrUpTti10[2]
NhrThrDownTti10[3]
NhrThrDownTti10 [0]<= NhrThrDownTti10 [1]<= NhrThrDownTti10 [2]
NhrThrUpTti2[3]
NhrThrUpTti2 [0]<= NhrThrUpTti2 [1]<= NhrThrUpTti2 [2]
NhrThrDownTti2[3]
NhrThrDownTti2 [0]<= NhrThrDownTti2 [1]<= NhrThrDownTti2 [2]
MaxRetransEdch
NhrThrUpTti10[3]
SubSrv
SubSrv
NhrThrDownTti10[3]
NhrThrUpTti2[3]
NhrThrDownTti2[3]
SubSrv
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
SrvType
SubSrv
MaxRetransEdch
SrvType is an even number, the associated field is valid
PeriodSING
PeriodSIG
EdchHarqPOFdd
ThrHarqFailNum
NhrThrUpTti10[3]
NhrThrUp
NhrThrDownTti10[3]
NhrThrDown
HappyBitDelCond
StatWinSize
EdchTrGrantType
2-45
ETTI
DeltaT2TP
NhrThrUpTti2[3]
NhrThrDownTti2[3]
QeCntThres
QeValidTimeWin
UpThrSampNuTti10[3]
DwThrSampNuTti10[3]
UpThrSampNumTti2[3]
DwThrSampNumTti2[3]
PrdRptValidTime
Related Object
Related Parameter
SrvType
SubSrv
BLERtarget
Only in the service sub-class whose MbmsInd is 0 (not MBMS), the associated field is valid
MbmsInd
QeTrchBerTarget
QePhychBerTarget
SubflowNum
BLERPeriodFactor
BLERTimeWinSize
GoodThresPhyBer
BadThresPhyBer
GoodThres
BadThres
ValidTimeWin
ErrorThresh
2-46
BLERAccpPeriod
HsscchPwrOffset
EdchHarqPOFdd
ThrHarqFailNumUp
ThrHarqFailNumDn
NhrThrUpTti10[3
NhrThrDownTti10[3]
NhrThrUp
NhrThrDown
NhrThrUpTti2[3]
NhrThrDownTti2[3]
StatWinSize
MaxRetransEdch
HappyBitDelCond
PeriodSING
PeriodSIG
Alfa
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
RbParaCfgType
PreRbCfgId
PreConfValTag
T1
DiscardTimerPre
DiscardTimer
MachsWinSize
QePhyBerTarNorm
QePhyBerTarSil
DiscardTimerPre
SubSrv
DiscardTimer
When DiscardTimerPre is True, the associated field is valid
SrvType
SubSrv
PtmRlsPerm
Only in the service sub-class whose MbmsInd is 1 ( MBMS), the associated field is valid
MbmsInd
MbmsComType
2-47
FreqConvSwch
SrvType
SubSrv
MbmsInd
Direction
In the service sub-class whose MbmsInd is 1(MBMS), Direction can be only 1 (Downlink),
Domain
Domain can be only 1 (PS Domain), TrafficClass can be only 1 (streaming) or 3 (back-
TrafficClass
ground), RlcMode can be only 2(Unacknowledged Mode)
RlcMode
SubSrv
MbmsInd
SrvType is 0~5, then MbmsInd value must be 0(False)
ThrHarqFailNumUp
SubSrv
ThrHarqFailNumDn
ThrHarqFailNumUp >=ThrHarqFailNumDn
UlBlerBadThresh
SubSrv
SrvType
When SrvType is an odd number, UlBlerBadThresh, UlBlerBadTimeThr, UlBlerNor-
UlBlerBadTimeThr
TimeThr, ThrHarqFailTti2[3], ThrHarqFailTti10[3]fields are valid , so the fields above is
UlBlerNorTimeThr
valid with uplink service only
ThrHarqFailTti2[3]
ThrHarqFailTti10[3]
HsscchPwrOffset
Hspa
HsscPwrOfstPre
Only when HsscPwrOfstPre is True, HsscchPwrOffset is valid
SrvType
Related Object
Related Parameter
MaxBitRate
rncFunction
UlLowLimNegGBR
UlLowLimNegGBR Must have the corresponding matching UL rate in this table
rncFunction
DlLowLimNegGBR
DlLowLimNegGBR Must have the corresponding matching DL rate in this table
QosSeg
UlRateAdjLevNum
Valid UlRateAdjLev[] must have the corresponding matching UL rate in this table
Direction
MaxBitRate
Direction
MaxBitRate
Direction
MaxBitRate
UlRateAdjLev[i]
QosSeg
Direction
MaxBitRate
DlRateAdjLevNum
Valid DlRateAdjLev[] must have the corresponding matching DL rate in this table
DlRateAdjLev[i]
externalUtranCell
NrtMaxDlRateDchD
NrtMaxDlRateDchD must have the corresponding matching UL rate in this table
externalUtranCell
NrtMaxUlRateDchD
NrtMaxUlRateDchD must have the corresponding matching DL rate in this table
externalUtranCell
RtMaxDlRateDchD
RtMaxDlRateDchD must have the corresponding matching UL rate in this table
externalUtranCell
RtMaxUlRateDchD
RtMaxUlRateDchD must have the corresponding matching DL rate in this table
externalUtranCell
NrtMaxRateEdchD
NrtMaxRateEdchD must have the corresponding matching UL rate in this table
externalUtranCell
RtMaxRateEdchD
RtMaxRateEdchD must have the corresponding matching UL rate in this table
utranCell
NrtMaxDlRateDch
NrtMaxDlRateDch must have the corresponding matching UL rate in this table
utranCell
NrtMaxUlRateDch
NrtMaxUlRateDch must have the corresponding matching DL rate in this table
Direction
MaxBitRate
2-48
Direction
MaxBitRate
Direction
MaxBitRate
Direction
MaxBitRate
Direction
MaxBitRate
Direction
MaxBitRate
Direction
MaxBitRate
Direction
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
MaxBitRate
UtranCell
RtMaxDlRateDch
RtMaxDlRateDch must have the corresponding matching UL match rate in this table
UtranCell
RtMaxUlRateDch
RtMaxUlRateDch must have the corresponding matching DL rate in this table
UtranCell
NrtMaxRateEdch
NrtMaxRateEdch must have the corresponding matching UL rate in this table
UtranCell
RtMaxRateEdch
RtMaxRateEdch must have the corresponding matching UL rate in this table
drbc
PsRateLmtLowC
PsRateLmtLowC must have the corresponding matching DL/UL rate in this table
drbc
PsRateLmtHighC
PsRateLmtHighC must have the corresponding matching DL/UL rate in this table
GbrRes
HsGBRLevNum
Valid HsGBRLev[MAX_NUM_HS_GBR] must have the corresponding matching DL rate in
HsGBR-
association table
Direction
MaxBitRate
Direction
MaxBitRate
Direction
MaxBitRate
Direction
MaxBitRate
Direction
MaxBitRate
2-49
Direction
MaxBitRate
Direction
Lev[MAX_NUM_HS_GBR]
MaxBitRate
InitialRateDl
InitialRateDl must have the corresponding matching DL/UL rate in this table
drbc
InitialRateUl
InitialRateUl must have the corresponding matching DL/UL rate in this table
UtranCell
DlControledMBR
DlControledMBR must have the corresponding matching DL rate in this table
UtranCell
UlControledMBR
UlControledMBR must have the corresponding matching UL rate in this table
SubSrv
SrvType
Only if SrvType is 10 or 28, ErrorThreshHLd is valid
Direction
MaxBitRate
Direction
MaxBitRate
Direction
MaxBitRate
Direction
ErrorThreshHLd
drbc
Related Object
Related Parameter
BLERAccpPerHLd
SubSrv
SrvType
Only if SrvType is 10 or 28, BLERAccpPerHLd is valid
BLERtargetHLd
SubSrv
SrvType
Only if SrvType is 11 or 29, BLERtargetHLd is valid
2-50
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
2.2.20 E-DCH Reference Configuration Information (EdchRc)

Related Ob-
Related Parame-
rameter
ject
ter
EdchRefCon-
SrvPhy
EdchRefConfigIdx
The field in the SrvPhy has existed in EdchRc
Hspa
EtfciBstTti2T2
At least one elements in REtfciTti2T2[] must be equal to the
Original
Pa-
figIdx
REtfciTti2T2[i]
related parameter
REtfciTti2T2[]
Hspa
EtfciBstTti2T2
The nodes of REtfciTti2T2[] is correspond to REtfciPOTti2T2[],
REtf-
and when REtfciTti2T2[] equal to related parameters, the cor-
ciPOTti2T2[]
reaponding value in REtfciPOTti2T2[] must not more than 29
REtfciTti2T3[]
Hspa
EtfciBstTti2T3
At least one elements in REtfciTti2T3[] must be equal to the

related parameter
REtfciTti2T3 []
Hspa
EtfciBstTti2T3
The nodes of REtfciTti2T3[] is correspond to REtfciPOTti2T3[],
REtf-
and when REtfciTti2T3[]equal to related parameters, the cor-
ciPOTti2T3
reaponding value in REtfciPOTti2T3[] must not more than 29
[]
2.2.21 UE DTX-DRX Configuration Information (rncDtxDrx)

Original
Pa-
Related Ob-
Related Parame-
rameter
ject
ter
DtxDrxCon-
SrvPhy
DtxDrxConfigIdx
The field in the SrvPhy has existed in rncDtxDrx
Hspa
CqiCycle
DtxCyc2Tti10 and DtxCyc2Tti2 must be integral times of Cqi-
figIdx
DtxCyc2Tti10
DtxCyc2Tti2
DtxCyc1Tti2
Cycle divided by two or quotient of CqiCycle divided by two

rncDtxDrx
DtxCyc2Tti2
The DtxCyc2Tti2 under the same DtxDrxConfigIdx must be
DpcchBurst1
integral times of DtxCyc1Tti2
MacDtxCycTti2
The DpcchBurst1 under the same DtxDrxConfigIdx must not
DrxCycle
be larger than DtxCyc1Tti2

DtxCyc1Tti2 under the same DtxDrxConfigIdx must be
integral times of MacDtxCycTti2 or quotient of MacDtxCycTti2
DrxCycle under the same DtxDrxConfigIdx must be integral
times of DtxCyc1Tti2 or quotient of DtxCyc1Tti2
2-51
SJ-20100603155704-001|2011-04-09(R2.2)
Original
Related Ob-
Related Parame-
rameter
Pa-
ject
ter
DtxCyc1Tti10
rncDtxDrx
DtxCyc2Tti10
DpcchBurst1
MacDtxCycTti10
DrxCycle
be larger than DtxCyc1DtxCyc1Tti10

DtxCyc1Tti10 under the same DtxDrxConfigIdx must
be integral times of MacDtxCycTti10 or quotient of
MacDtxCycTti10
DrxCycle under the same DtxDrxConfigIdx must be integral
times of DtxCyc1Tti10 or quotient of DtxCyc1Tti10
DtxCyc2Tti2
rncDtxDrx
DtxCyc1Tti2
DpcchBurst2

be larger than DtxCyc2Tti2
DtxCyc2Tti10
rncDtxDrx
DpcchBurst2
DtxCyc1Tti10

The DpcchBurst2 under the same DtxDrxConfigIdx must be
not larger than DtxCyc2Tti10
DtxLong-
rncDtxDrx
PreLegth
DtxCyc2InactTrd2
Under the same DtxDrxConfigIdx, when DtxLongPreLegth is
DtxCyc2Inact-
4 or 15, the DtxCyc2InactTrd2 value must be not less than 8
Trd10
TTIs, and the DtxCyc2InactTrd10 value must be not less than

4 TTIs
2.2.22 Service Physical Layer Configuration Information (SrvPhy)

Original Pa-
Related Ob-
Related Parame-
rameter
ject
ter
SrvType
SubSrv
SrvType
SigSrvNo
SubSrv
SrvType
If the field that belongs to SrvPhy is not 0xff, then it must exist
in SubSrv
SrvType
SrvType
SrvPhy
SrvPhy
TfciPresence
The associated field is valid only when SrvType is an odd num-
MplexPos
ber
SigSrvNo
If SigSrvNo is not equal to 0xff, SigSrvNo must be an odd number when SrvType is an odd number; and SigSrvNo must be
an even number when SrvType is an even number
SrvType
SrvPhy
GainFactorCfg[i]
The associated field is valid only when SrvType is an even

number
2-52
SJ-20100603155704-001|2011-04-09(R2.2)
Original Pa-
Related Ob-
Related Parame-
rameter
ject
ter
SrvType
SrvPhy
BetaC
BetaD
number and GainFactorCfg is Signalled. And at least one of
GainFactorCfg
SrvType
BetaC and BetaD must be 15

SrvPhy
RefTfc[i]

number
SrvType
SrvPhy
SigSrvNo
When the SrvType value is 0.5, the SigSrvNo value must be

SrvType
SrvType
SrvPhy
TfciPresence
The associated field (TfciPresence) is valid only when SrvType

is an odd number
SrvType
SrvPhy
RefTfc[i]
When SrvType is an even number, traverse all the valid
GainFactor-
GainFactorCfg[i] elements. If all the valid GainFactorCfg[i]
Cfg[i]
are Signalled, then all the RefTfc [i] elements must be 0xff
Otherwise (in other words, at least one GainFactorCfg[i]
element is Computed), the RefTfc [i] value must be unique
and can not be 0xff in the RefTfc [i] elements corresponding
to the GainFactorCfg[i] elements of value Signalled
SrvType
SrvPhy
RefTfc[i]
When SrvType is an even number and GainFactorCfg[i] is
GainFactor-
Computed, the RefTfc [i] value must exist in the GainFactor-
Cfg[]
Cfg[i] which is the RefTfc [i] corresponding to Signalled. And

not all the valid GainFactorCfg[i] elements are computed
CtfcNum
SubSrv
Ctfc[i]
RbParaCfgType
When the RbParaCfgType is TRUE in R8SubSrv, the Sub-
PreConfValTag
Srv field PreConfValTag must change when the CtfcNum,
TfciPresence
Ctfc[i] in this table change, or the following values has valid
MplexPos
changes:
GainFactor-
taC[i],BetaD[i],RefTfc[i]
TfciPresence, MplexPos, GainFactorCfg[i],Be-
Cfg[i]
BetaC[i]
BetaD[i]
RefTfc[i]
SrvType
SigSrvNo
SrvPhy
SubSrv
ETInd
EdchRefConfigIdx
number
SrvType
The MbmsInd is 1(MBMS). The fields in the association table
MbmsInd
are constantly 0xff
2-53
SJ-20100603155704-001|2011-04-09(R2.2)
Original Pa-
Related Ob-
Related Parame-
rameter
ject
ter
TfciPresence
SubSrv
SrvType
When the MbmsInd is 0 (not MBMS), the fields in the associ-
MbmsInd
ation table are valid
EdchRc
EdchRefConfigIdx
DtxDrx
DtxDrxConfigIdx
SrvTfs
SrvType
If SrvType=11 or 29 and SubflowId=0 in the relation table
MplexPos
ETInd
EdchRefConfigIdx
GainFactorCfg[MAX_
SINGLESRV_TFC]
BetaC[MAX_
SINGLESRV_TFC]
BetaD[MAX_
SINGLESRV_TFC]
RefTfc[MAX_
SINGLESRV_TFC]
EdchRefConfigIdx
DtxDrxConfigIdx
TfciPresence
TfciPresence
SrvTfs
SubFlowId
SrvTfs, TfciPresence can be Not Present only if the Cod-
CodingRate
ingRate=0 (Convolutional 1/2) or 1 (Convolutional 1/3) and
CRCSize
CRCSize0 in the record of the service subflow
SrvType
If SrvType value is odd except for 11 and 29, TfciPresence
TfNum
can be Not Present only if the parameters of service subflow
TBNum[]
corresponding to SryType in the related table meet the
RlcSize1[]
following conditions:
RlcSize2[]
In the array TBNum[0]RlcSize1[0] TBNum[1]Rlc-
RlcSize3[]
Size1[1]...TBNum[TfNum -1]RlcSize1[TfNum -1], there is at
CRCSize
most one group valued other than 0

In the array TBNum[0]RlcSize2[0] TBNum[1]RlcSize2[1]...TBNum[TfNum -1]RlcSize2[TfNum -1], there is at
most one group valued other than 0
In the array TBNum[0]RlcSize3[0] TBNum[1]RlcSize3[1]...TBNum[TfNum -1]RlcSize3[TfNum -1], there is at
most one group valued other than 0. 4) CRCSize0
2-54
SJ-20100603155704-001|2011-04-09(R2.2)
2.2.23 Power Control Related to Service and Diversity Mode (DivPc)
2-55
SJ-20100603155704-001|2011-04-09(R2.2)
Related Object
Related Parameter
DivPcIndex(Target In-
UtranCell
DivPcIndex(Source Index)
Before the set of records with one DivPcIndex in DivPc is deleted, it must be ensured that
dex)
there is no utrallCells record which quotes the DivPcIndex. Otherwise, this set of records
with the DivPcIndex in DivPc is not allowed to delete entirely, at least a record with the
DivPcIndex in DivPc must exist
SrvType(Source
In-
SubSrv
SrvType(Target Index)
There must be a record with corresponding SrvType in SubSrv
DivPc
DpchPO1
Only when the value of SrvType is odd, the related parameters are valid
dex)
SrvType
DpchPO2
DpchPO3
SrvType
DivPc
MinDlDpchPwr
Only when the value of SrvType is odd, the related parameters are valid. And the
MaxDlDpchPwr
following resctriction must be comply with :
2-56
MaxDlDpchPwr> MinDlDpchPwr
SrvType
DivPc
DpcchPilotEbN0
Only when the value of SrvType is even, the related parameters are valid
MaxUlDpchPwr
SrvType
SrvType
DivPc
DivPc
ULMaxSIR
Only when the value of SrvType is even, the related parameters are valid.And the
ULInitSIR
following resctriction must be comply with :
ULMinSIR
ULMaxSIR>ULInitSIR >ULMinSIR
EagchPOTti2
Only when the value of SrvType is odd, the related parameters are valid
EagchPOTti10
ErgchPOTti2
ErgchPOTti10
EhichPOTti2
EhichPOTti10
EagchPOTti2
DivPc
EagchPOTti10
When SrvType is an odd number, EagchPOTti2> EagchPOTti10
ErgchPOTti2
DivPc
ErgchPOTti10
When SrvType is an odd number, ErgchPOTti2> ErgchPOTti10
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
EhichPOTti2
DivPc
EhichPOTti10
When SrvType is an odd number, EhichPOTti2> EhichPOTti10
PwrForSglCell
SubSrv
SrvType
Only when SrvType is an odd number and in the association table the MbmsInd value is
MbmsInd
1(MBMS), then the field in this table is valid
PwrForHalfIsd
2-57
2.2.24 External Utran Cell (externalUtranCell)
2-58
SJ-20100603155704-001|2011-04-09(R2.2)
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
URA
Ura
URA
The fields in this table must exist in the association table
AdjPhyCId
SelfPhyRncCInd
PhyCId
AdjPhyCId
MCC[i]
utranRelation
externalUtranCell
SelfPhyRncCInd
If the adjacent cell in the association table is not a cell controlled by this
PhyCId
RNC(SelfPhyRncCInd is False), then the assocated fields exist in this table
MCC[i]
MCC+MNC+RncId+CId is unique in this table
MNC[i]
MNC[i]
RncId
RncId
CId
CId
MCC[i]
2-59
MCC[i]
MCC+MNC+RncId in this table does not exist in the MCC[i]+MNC[i]+NeId[i] record whose
MNC[i]
rncNeInfo
MNC[i]
ANI is 0 in the rncNeInfo table
RncId
Neld
CId
ANI
MNCBcdCodeLen[]
externalUtranCell
MNC[]
If MNCBcdCodeLen is 2the value of MNC[] must be from 0 to 99
UUARFCN
externalUtranCell
DUARFCN
DUARFCN>UUARFCN;
FreqBandInd
When FreqBandInd is 0 (Band I), DUARFCN takes the value of Band I: [10562,
10838]. UUARFCN = DUARFCN-950
When FreqBandInd is 1 (Band II), DUARFCN takes the value of Band II: [9662,
9938], 412, 437, 462, 487, 512, 537, 562, 587, 612, 637, 662, and 687. UUARFCN
= DUARFCN-400
When FreqBandInd is 2 (Band III), DUARFCN takes the value of Band III: [1162,
When FreqBandInd is 4 (Band V), DUARFCN takes the value of Band V: [4357,
4458], 1007, 1012, 1032, 1037, 1062, and 1087. UUARFCN = DUARFCN-225
When FreqBandInd is 5 (Band VI), DUARFCN takes the value of Band VI: [4387,
4413], 1037, 1062. UUARFCN = DUARFCN-225
Related Object
Related Parameter
l
When FreqBandIn is 7 (Band VIII), DUARFCN takes the value of BandVIII:[2937,

FreqBandInd value is 3 (Band IV), DUARFCN value must be frequency band

4 1537. 1738, 1887, 1912, 1937, 1962, 1987, 2012, 2037, 2062, 2087,
UUARFCN=DUARFCN-225
PcpichPwrPre
externalUtranCell
PcpichPwr
Only when PcpichPwrPre is 1(True), PcpichPwr is valid
CellDescripType
externalUtranCell
PolygonPointNum
Only when the value of CellDescripType is 1(Polygon), related parameter are valid
PolyLatitudeSign[15]
PolyLatitude[15]
PolyLongitude[15]
AnteType
externalUtranCell
OffsetAngle
Only when the value of AnteType is 1(Beam Antenna), related parameter are valid
2-60
InnerAngle
CellDescripType
externalUtranCell
AnteType
When CellDescripType is 2(Arc), AnteType must be 1(Beam Antenna)
SACB
externalUtranCell
SACBPre
SCAB is valid only when SACBPre is 1(True)
LAC
The following restriction must be satisfied:
PlmnNum+MCC[i]+MNC[i]
In the same PLMN, one LAC+SACB in PLMN can only contain one cell
UtranCell
LAC
SACBPre
SACB
i.e. In the same PLMN, for SACBPre is 1(True), if there is a record corresponding to
MCC+MNC+LAC+ SACBPre+SACB in externalUtranCell, then the record corresponding
to MCC+MNC+LAC+ SACBPre+SACB can not exist in UtranCell
PlmnNum+MCC[i]+MNC[i]
QrxLevMinSib11
externalUtranCell
DtQrxLvMnSib11Pr
If the value of QrxLevMinSib11 is not 0(-115dBm), DtQrxLvMnSib11Pr must be 0(False)
QrxLevMinSib12
externalUtranCell
DtQrxLvMnSib12Pr
PlmnNum+MCC[i]+
externalUtranCell
DivCtrlFld
DivCtrlFld of all externalUtranCells records for one neighboring RNC must be same
MNC[i]+RncId, CId
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
PlmnNum+MCC[i]+
externalUtranCell
DIurCmbInd
DIurCmbInd of all externalUtranCells records for one neighboring RNC must be same
DtQrxLvMnSib11Pr
externalUtranCell
DtQrxLvMnSib11
Only when DtQrxLvMnSib11Pr is 1(True), DtQrxLvMnSib11 is valid
DtQrxLvMnSib12Pr
externalUtranCell
DtQrxLvMnSib12
NrtMaxDlRateDchD
SubSrv
MaxBitRate
NrtMaxDlRateDchD must have the corresponding uplink MaxBitRate in SubSrv
MNC[i]+RncId, CId
Direction
NrtMaxUlRateDchD
SubSrv
MaxBitRate
NrtMaxUlRateDchD must have the corresponding uplink MaxBitRate in SubSrv
Direction
RtMaxDlRateDchD
SubSrv
MaxBitRate
RtMaxDlRateDchD must have the corresponding uplink MaxBitRate in SubSrv
Direction
2-61
RtMaxUlRateDchD
SubSrv
MaxBitRate
RtMaxUlRateDchD must have the corresponding uplink MaxBitRate in SubSrv
Direction
NrtMaxRateEdchD
SubSrv
MaxBitRate
NrtMaxRateEdchD must have the corresponding uplink MaxBitRate in SubSrv
Direction
RtMaxRateEdchD
SubSrv
MaxBitRate
RtMaxRateEdchD must have the corresponding uplink MaxBitRate in SubSrv
Direction
externalUtranCell
SndSvrCelID
If IurDcHsdsSuptInd is "Support", then SndSvrCelID must be configured; if

IurDcHsdsSuptInd is "Not Support", then SndSvrCelID is in valid
FDpchSuptInd
externalUtranCell
EfdpchSupInd
Only when FDpchSuptInd is support, EfdpchSupInd can be configured to support
IurDcHsdsSuptInd
2.2.25 External Gsm Cell (externalGsmCell)
2-62
SJ-20100603155704-001|2011-04-09(R2.2)
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
AdjPhyGsmCId
gsmRelation
NPhyGsmCId
Before the record of externalGsmCell is deleted, it must be ensured that there is no gsmRelations record which quotes the MCC+MNC+LAC+CI. Otherwise, the record of externalGsmCell is not allowed to delete
Bandindicator
externalGsmCell
BCCHARFCN
When Bandindicator takes value of 0(DCS 1800 Band Used), the value range of
BCCHARFCN is [512, 885]
When Bandindicator takes value of 1(PCS 1900 Band Used), the value range of
When Bandindicator takes value of 2(GSM 900 Band Used), the value range of
BCCHARFCN is [0, 124] and [955, 1023]
2-63

externalGsmCell
DtQrxLvMnSib11Pr
QrxLevMinSib12
externalGsmCell
DtQrxLvMnSib12Pr
DtQrxLvMnSib11Pr
externalGsmCell
DtQrxLvMnSib11
DtQrxLvMnSib12Pr
externalGsmCell
DtQrxLvMnSib12
GeranCellInd
externalGsmCell
RAC
Only when GeranCellInd is 1(GERAN Cell), RAC is valid
MCC[i]MNC[i]LACCI
externalGsmCell
MCC[i]MNC[i]LACCI
MCC+MNC+LAC+CI is unique in the table
MNCBcdCodeLen[]
externalGsmCell
MNC[]
When MNCBcdCodeLen is 2the values of MNC[] must be from 0 to 99
QrxLevMinSib11
2.2.26 Utran Cell

2.2.26.1 Utran Cell (utranCell)
2-64
SJ-20100603155704-001|2011-04-09(R2.2)
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
NodebNo(Source In-
nodeB
NodebNo(Target Index)
There must be a record in the nodeB corresponding to NodebNo
CelSel
Sib3orSib4
In this table, the corresponding cells SIB4Ind is True, the association table must have SIB4
dex)
SIB4Ind
record
UseOfHCS
CelSel
HcsSrvCelInfoPre
If UseOfHCS is Not Used, the associated field in the association table value must be False
SIB6Ind
Sccpch
Sib5orSib6
In this table, the corresponding cell's SIB6Ind is True, the association table must have SIB6
record
SIB6Ind
Prach
Sib5orSib6
In this table, the corresponding cell's SIB6Ind is True, the association table must have SIB6
record
SIB12Ind
SysMC
Sib11orSib12
in this table, the corresponding cell's SIB12Ind is True, the association table must have
SIB12 record
2-65
TrfPcIndex
TrfPc
TrfPcIndex
The field in this table must exist in the association table
DivPcIndex(Source
DivPc
DivPcIndex(Target Index)
There must be a record in the DivPc corresponding to DivPcIndex
TrfAcIndex
TrfAc
TrfAcIndex
DivAcIndex
DivAc
DivAcIndex
TrfCatIn-
CIntra
TrfCatIntraMIdx(Target
Index)
In-
There must be a record in the CIntra corresponding to TrfCatIntraMIdx
In-
There must be a record in the CInter corresponding to TrfCatInterMIdx
In-
There must be a record in the CRat corresponding to TrfCatRatMIdx
dex)
dex)
TrfCatInter-
CInter
MIdx(Source Index)
TrfCatRatMIdx(Source Index)
TrfCatInterMIdx(Target
dex)
CRat
TrfCatRatMIdx(Target
dex)
traMIdx(Source
In-
Related Object
Related Parameter
SchPriIndex(Source
SchPri
SchPriIndex(Target Index)
There must be a record in the SchPri corresponding to SchPriIndex
AppPri
AppPriIndex(Target Index)
There must be a record in the AppPri corresponding to LdCtlPriIndex
AppPri
AppPriIndex(Target Index)
There must be a record in the AppPri corresponding to CgtCtlPriIndex
BPriAc
BPriAcIndex(Target Index)
There must be a record in the BPriAc corresponding to BPriAcIndex
utranRelation
CId
When the record of utranCell is deleted, records of related objects which quotes the CId
Index)
LdCtlPriIndex(Source Index)
CgtCtlPriIndex(Source Index)
BPriAcIndex(Source
Index)
CId
GsmRelation
celSel
2-66
Psch
Ssch
Pcpich
Scpich
Pccpch
Sccpch
Pich
Prach
Aich
Bch
Fach
Pch
Rach
CHsdpa
LdCtrl
Pc
are deleted at the same time
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
DUARFCN
DUARFCN>UUARFCN;
PlBal
Ac
CUeTrv
SysMC
CMbms
UUARFCN
utranCell
FreqBandInd
When FreqBandInd is 0 (Band I), DUARFCN takes the value of Band I: [10562,
When FreqBandInd is 1 (Band II), DUARFCN takes the value of Band II: [9662, 9938],
412, 437, 462, 487, 512, 537, 562, 587, 612, 637, 662, 687. UUARFCN = DUARFCN400
2-67
When FreqBandInd is 2 (Band III), DUARFCN takes the value of Band III: [1162,
When FreqBandInd is 4 (Band V), DUARFCN takes the value of Band V: [4357, 4458],
1007, 1012, 1032, 1037, 1062, 1087. UUARFCN = DUARFCN-225
When FreqBandInd is 5 (Band VI), DUARFCN takes the value of Band VI: [4387,
4413], 1037, 1062. UUARFCN = DUARFCN-225
When FreqBandIn is 7 (Band VIII), DUARFCN takes the value of Band VIII:[2937,
FreqBandInd value is 3(Band IV), DUARFCN value must be frequency band 4: 1537..
1738, 1887, 1912, 1937, 1962, 1987, 2012, 2037, 2062, 2087, UUARFCN=DUARFCN-225
CellDescripType
utranCell
PolygonPointNum
PolyLatitudeSign[15]
PolyLatitude[15]
PolyLongitude[15]
Only when the value of CellDescripType is 1(Polygon), the related parameter are valid
Related Object
Related Parameter
AnteType
utranCell
OffsetAngle
Only when the value of AnteType is 1(Beam Antenna), the related parameter are valid
InnerAngle
CellDescripType
utranCell
AnteType
When CellDescripType is 2(Arc), AnteType must be 1(Beam Antenna)
SACB
utranCell
MCC
SACB is valid only when SACBPre is 1(True).
MNC
The following restriction must be comply with :
SACBPre
One LAC+SACB in PLMN can only contain one cell
LAC
i.e. For SACBPre is 1(True), if there is a record corresponding to MCC+MNC+LAC+
externalUtranCell
MCC
MNC
SACBPre+SACB in utranCell, then the record corresponding to MCC+MNC+LAC+

SACBPre+SACB can not exist in externalUtranCell
SACBPre
LAC
2-68
SAC
SIB6Ind
HspaSptMeth
utranCell
CHspa
PccpchInfSib6Pre
Only when SIB6Ind is True, then the associated field is valid, SIB6Ind value is False, then
PrachSib6Pre
PrachSib6Pre value must be False
HsdpaScramCode
Only when HspaSptMeth value is 1(Support HSDPA and DCH) or 2(Support HSDPA only)
NumofHspdsch
or 3(Support HSUPA, HSDPA and DCH) or 4(Support HSUPA and HSDPA), the related
NumofHsscch
field is valid
HsdschTrafLimit
MinNumofHspdsch
MaxNumofHspdsch
DpchCodeHy
CodeUptHyA
HspdschBitRate
MinHspaPwrRto
MaxHspaPwrRto
HspaPwrRatio
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
HspaSptMeth
CelMPO
MeasPwrOffset
Only when HspaSptMeth is 1(Support HSDPA and DCH) or 2(Support HSDPA only) or
3(Support HSUPA , HSDPA and DCH) or 4(Support HSUPA and HSDPA)the related field
is valid
HspaSptMeth
CHspa
NumofEagch
Only when HspaSptMeth value is 3(Support HSUPA, HSDPA and DCH) or 4(Support
NumofErgHich
HSUPA and HSDPA), the related field is valid
NServToTotalPwr
EdchTrafLimit
MaxRTWP
Ergch2IdxStepThr
Ergch3IdxStepThr
2-69
CLTAMPre
utranCell
CLTAM
CLTAMPre is True, then CLTAM field is valid
GARptType
utranCell
CellDescripType
When the value of CellDescripType is 0 (Center Point with Altitude and Cell Radius),
GARptType can take values of 0 (Ellipsoid point),1 (Ellipsoid point with uncertainty
circle),2 (Ellipsoid point with uncertainty Ellipse), 3(Ellipsoid point with altitude),4 (Ellipsoid
point with altitude and uncertainty Ellipsoid)
When the value of CellDescripType is 1 (Polygon), GARptType can be take the value of 5
(List of Ellipsoid points)
MAXDlTxPwr
nodeB
NodeBType
If, in the nodeB list, the NodeBType is PicoNodeB, then the MAXDlTxPwr background
value can not be larger than 24dBm in this table
CId
utranCell
NodeBNo
The maximum number of cell in a Node B is 36
HspaSptMeth
rncNeInfo
ProVer
When ProVer of nodeBs record that the cell belongs to in rncNeInfo is 10(R98), 20(R99),
30(R4), HspaSptMeth must be 0(Not Support HSUPA and HSDPA)
MbmsSuptInd
rncNeInfo
ProVer
When ProVer of NodeBs record that the cell belongs to in rncNeInfo is 10(R98), 20(R99),
30(R4), MbmsSuptInd must be 0(Not Support)
When the value of CellDescripType is 2, GARptType can take the value of 6 (Ellipsoid Arc)
Related Object
Related Parameter
Cld
nodeB
Nodeb
If the NodeB's NodebType value in the nodeB list in this cell is 2(Home NodeB), then this
NodebType
NodeB has this cell only, i.e., one Home NodeB supports one cell only
Nodeb
If the nodeB's NodebType value in the nodeB list in this cell is 2(Home NodeB), then ,
NodebNo
UUARFCN
nodeB
DUARFCN
NodebType
in this cell, the UUARFCN, DUARFCN, PrimScraCode, FreqBandInd are all invalid fields,
PrimScraCode
i.e., the corresponding HNodeB UUARFCN, DUARFCN, PrimScraCode, FreqBandInd are
FreqBandInd
all invalid fields. They are non-configurable fields which are always set to 0xffff
CellDescripType
PolygonPointNum
PolyLatitudeSign[MAX_POINT_NUM]
PolyLatitude[MAX_
POINT_NUM]
2-70
PolyLongitude[MAX_
POINT_NUM]
LatitudeSign
Latitude
Longitude
Altitude
AltitudeDir
AltitudeAcc
UncertAltitude
Confidence
CellRadius
UncertCode
GARptType
AnteType
AnteLatitudeSign
AnteLatitude
nodeB
Nodeb
If the NodeB's NodebType value in the nodeB list in this cell is 2 (Home NodeB), then the
NodebType
fields in this cell are all invalid fields, i.e., the corresponding HNodeBs cell LCS information
fields are all invalid fields
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
rncNeInfo
PlmnNum,
MCC+MNC+ RncId of the utranCells record must be selected from valid MCC[i]+
MCC[8], MNC[8], NeId[8]
MCC[i]+NeId[i] (i=[0, PlmnNum-1]) of the rncNeInfos records which ANI=0
MaxBitRate
NrtMaxDlRateDchD must have the corresponding uplink MaxBitRate in SubSrv
AnteLongitude
AnteAltitude
AnteAltitudeDir
OffsetAngle
InnerAngle
ClassZoneInd
PlmnNum
MCC[i]
MNC[i]
RncId[i]
NrtMaxDlRateDch
SubSrv
Direction
2-71
NrtMaxUlRateDch
SubSrv
MaxBitRate
NrtMaxUlRateDchD must have the corresponding uplink MaxBitRate in SubSrv
Direction
CommonPlmnInd[i]
utranCell
CId
For one physical cell, i.e., one piece of local table record, there is only PLMN whoseCommonPlmnInd is True, and this PLMN is located as the first element in the PLMN number
groups
rncFunction
SharedNetMode
When SharedNetMode is Oxff, CommonPlmnInd is an invalid field
PLmnNum
rncFunction
SharedNetMode
When SharedNetMode in rncFunction is 0/1, the value of PLmnNum can be more than 1
CommonPlmnInd[i]
2.2.26.2 Neighbouring Cell (utranRelation)
2-72
SJ-20100603155704-001|2011-04-09(R2.2)
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
NCToSelf-
utranCell
Cld
If neighboring cell is a utrancell, there must be a record in the related objectutranCell
PhyRnc+NPhyCId
corresponding to NCToSelfPhyRnc+NPhyCId
If neighboring cell is an external utrancell, there must be a record in the related
objectexternalUtranCell corresponding to NCToSelfPhyRnc+NPhyCId
CId
utranCell
Cid
Before the record of utranRelation with the cell is created, it must be ensured that there
exists the corresponding cell record in utranCell
NCToSelf-
externalUtranCell
PhyCld
When the field NCToSelfPhyRnc in this table is False,(i.e., the adjacent cell is not a local
PhyRnc+NPhyCId
PenaltyTimeSib11
PenaltyTimeSib12
2-73
CId
RNC cell.It must exist in the association table

utranRelation
utranRelation
utranRelation
TempOffset1Sib11
When the value of PenaltyTimeSib11 is 1(Not used), then TempOffset1Sib11 and Tem-
TempOffset2Sib11
pOffset2Sib11 is invalid
TempOffset1Sib12
When the value of PenaltyTimeSib12 is 1(Not used), then TempOffset1Sib12 and Tem-
TempOffset2Sib12
pOffset2Sib12 is invalid
NCToSelfPhyRnc+
CId
NPhy-
The intra-system adjacent cells in the cell is not more than 63

The intra frequency adjacent cells are not more than 31. The inter frequency adjacent
cells are not more than 32
UseOfHCS
utranRelation
QhcsEcN0Sib11
When UseOfHCS is Used, the associated field is valid
QhcsEcN0Sib12
QhcsRscpSib12
PenaltyTimeSib11
PenaltyTimeSib12
QhcsRscpSib11
Related Object
Related Parameter
CId
UtranCell
PrimScraCode
PrimScraCode must be different for all intra-frequency neighboring cells (including the
NCToSelf-
DUARFCN
serving cell)
PhyRnc+NPhyCId
UUARFCN
If there have same PrimScraCode for neighboring cells (including the serving cell), then
externalUtranCell
PrimScraCode
DUARFCN of these neighboring cells (including the serving cell) must be different
DUARFCN
UUARFCN
ReadSFNInd
utranRelation
NCToSelfPhyRnc+NPhyCId
ReadSFNInd is only valid for inter-frequency neighboring cells. It is invalid for intra-frequency neighboring cells
Sib11orSib11bis
utranRelation
StateMode
If StateMode is 1 (Cell_DCH State only) then Sib11orSib11bis is invalid
Sib11orSib11bis
utranRelation
StateMode
If in table utranCell, SIB12Ind is 1True, then the StateMode in this table is 2(Connected
utranCell
SIB12Ind
State, Non-Cell_DCH) 5(Cell_DCH State + Connected State, Non-Cell_DCH), and
2-74
Sib11orSib11bis is invalid
CId
utranCell
DUARFCN
NCToSelf-
If DUARFCN is modified in utranCell, the restriction for number of neighboring cells must
be satisfied. The restriction is refered to remark 1
PhyRnc+NPhyCId
CId
gsmRelation
CId
There are at most 31 intra-frequency neighboring cells and 32 inter-frequency
neighboring cells, 32 GSM neighboring cells

Supposing that SIB11IntraFreqNbrCellNum is the number of intra-frequency
neighboring cells that are broadcasting in SIB11 (excluding the local utrancell),
SIB11InterFreqNbrCellNum is the number of inter-frequency neighboring cells of utran
cell that are broadcasting in SIB11, and SIB11IntraRatNbrCellNum is the number of
inter-rat neighboring cells of utran cell that are broadcasting in SIB11, the total number of
neighboring cells that can be configured is:
1. If there is only intra-frequency neighboring cell but no inter-frequency or inter-rat neighboring cell, 117+48*SIB11IntraFreqNbrCellNum<=3330
2. If there is only inter-frequency neighboring cell but no intra-frequency or inter-rat neighboring cells, 124+79*(SIB11InterFreqNbrCellNum-1)<=3330
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
3. If there are only intra-frequency and inter-frequencyneighboring cell but no inter-rat
neighboring cell, 204+48* SIB11IntraFreqNbrCellNum+79*(SIB11InterFreqNbrCellNum-1)<=3330
4. If there are only intra-frequency and inter-rat neighboring cell but no inter-frequency
neighboring cell, 200 + 48* SIB11IntraFreqNbrCellNum + 75*(SIB11InterRatNbrCellNum - 1) <=3330
5. If there are only inter-frequency and inter-rat neighboring cell but no intra-frequency
neighboring cell, 207 + 79*(SIB11InterFreqNbrCellNum-1)+ 75*(SIB11InterRatNbrCellNum - 1) <=3330
6. If all the three types of neighboring cells exist, 287+ 48* SIB11IntraFreqNbrCellNum
+ 79*(SIB11InterFreqNbrCellNum-1)+ 75*( SIB11InterRatNbrCellNum - 1) <=3330
The steps to judge whether to broadcast this neighbouring cell in SIB11
2-75
See SIB12Ind in UtranCell and check whether SIB12 is configured. If SIB12Ind is 1

(True), in Non Cell_DCH state, you can read the neighboring cell list in SIB12. That
is, the system configures the neighboring cell lists in Idle state and Non Cell_DCH
state separately
0(Idle State only)
3(Idle State + Cell_DCH State)
4(Idle State + Connected State, Non-Cell_DCH)
6(Idle State + Cell_DCH State+ Connected State, Non-Cell_DCH)
If SIB12Ind in utranCell is 0 (False), in Non Cell_DCH state, you can read the neighboring cell list in SIB11. That is, the system configures the neighboring cell lists in
Idle state and Non Cell_DCH state together
In this case, the neighbouring cell whose StateMode takes the following values
will be broadcasted in SIB11
0(Idle State only)
Related Object
Related Parameter
2(Connected State, Non-Cell_DCH)
5(Cell_DCH State + Connected State, Non-Cell_DCH)
The judging of SIB11 broadcast adjacent cell is shown in Note 1

utranCell
SIB12Ind
Set the SIB11bisIntraFreqNbrCellNum is the nuber of the intra-frequency adjacent cells in

the SIB11bis broadcast service cell, not including the local service cell; SIB11bisInterFreqNbrCellNum is the nuber of the inter-frequency adjacent cells in the SIB11bis broadcast
service cell; SIB11bisInterRatNbrCellNum is the nuber of the inter-system adjacent cells
2-76
in the SIB11bis broadcast service cell; The limit to to total number of adjacent cell is:
1. If only adjacent cell of intra-frequency exists with no adjacent cell of inter-frequency or
inter-system; 117+48*SIB11bisIntraFreqNbrCellNum<=3330, otherwise the interface
prompts the total number of adjacent cells are over sized
2. If only adjacent cell of inter-frequency exists with no of intr-frequency adjacent cell
or inter-system adjacent cell; 124+79* SIB11bisInterFreqNbrCellNum-1 <=3330, oth-
erwise the interface prompts the total number of adjacent cells are over sized
3. If only inter-frequency adjacent cells and intra-frequency adjacent cell exist with no inter-system adjacent cell; 204+48* SIB11bisIntraFreqNbrCellNum+79* SIB11bisInterFreqNbrCellNum-1<=3330, otherwise the interface prompts the total number of adjacent cells are over sized
4. If only inter-system adjacent cells and intra-frequency adjacent cell exist with no inter-frequency adjacent cell; 200 + 48* SIB11bisIntraFreqNbrCellNum + 75*( SIB11bisInterRatNbrCellNum - 1) <=3330, otherwise the interface prompts the total number of
adjacent cells are over sized
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
5. If only inter-system adjacent cells and inter-frequency adjacent cell exist with no intrafrequency adjacent cell; 207 + 79*SIB11bisInterFreqNbrCellNum-1+ 75*( SIB11bisInterRatNbrCellNum - 1) <=3330, otherwise the interface prompts the total number of
6. If all three types of adjacent cells exist, then 287+ 48* SIB11bisIntraFreqNbrCellNum +
79*SIB11bisInterFreqNbrCellNum-1+ 75*(SIB11bisInterRatNbrCellNum - 1) <=3330,
otherwise the interface prompts the total number of adjacent cells are over sized
The judging of SIB11bis broadcast adjacent cell is shown in Note 2
utranRelation
Sib11orSib11bis
Set the SIB12bisIntraFreqNbrCellNum is the nuber of the intra-frequency adjacent cells in

the SIB12bis broadcast service cell, not including the local service cell; SIB12bisInterFreqNbrCellNum is the number of the inter-frequency adjacent cells in the SIB12bis broadcast
service cell; SIB12bisInterRatNbrCellNum is the number of the inter-system adjacent cells
2-77
in the SIB12bis broadcast service cell; The limit to total number of adjacent cell is:
1.
If only intra-system adjacent cells exists with no inter-frequency adjacent cell and
intra-frequency adjacent cell; then 117+48*SIB12IntraFreqNbrCellNum<=3330, otherwise the interface prompts the total number of adjacent cells are over sized
2. If only inter-system adjacent cells exists with no intra-frequency adjacent cell and intra-frequency adjacent cell, then 124+79*SIB12InterFreqNbrCellNum-1<=3330, oth3. If only inter-frequency adjacent cells and intra-frequency adjacent cell exist with no
inter-system adjacent cell, then 204+48* SIB12IntraFreqNbrCellNum+79*SIB12InterFreqNbrCellNum-1<=3330, otherwise the interface prompts the total number of adjacent cells are over sized
4. If only inter-system adjacent cells and intra-frequency adjacent cell exist with no interfrequency adjacent cell, then 200 + 48* SIB12IntraFreqNbrCellNum + 75*( SIB12InterRatNbrCellNum - 1) <=3330, otherwise the interface prompts the total number of
erwise the interface prompts the total number of adjacent cells are over sized
Related Object
Related Parameter
5. If only inter-system adjacent cells and inter-frequency adjacent cell exist with no intrafrequency adjacent cell, then 207 + 79*SIB12InterFreqNbrCellNum-1+ 75*( SIB12InterRatNbrCellNum - 1) <=3330, otherwise the interface prompts the total number of
6. If all three types of adjacent cells exist, then 287+ 48* SIB12IntraFreqNbrCellNum +
79* SIB12InterFreqNbrCellNum-1 + 75*(SIB12InterRatNbrCellNum - 1) <=3330, otherwise the interface prompts the total number of adjacent cells are over sized
The judging of SIB12 broadcast adjacent cell is shown in Note 3
2-78
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Note:
1. Note 1
In SIB11, the computing method of inter-system cells, inter-frequency cells and
intra-frequency cells SIB11IntraFreqNbrCellNum, SIB11InterFreqNbrCellNum and
SIB11InterRatNbrCellNum:
a. According to the location record in CId to utranCell table, get the record's SIB12Ind
field and DUARFCN field.
b. According to the vague location of CId in utranRelation, find the record of all the
UTRAN adjacent cells in this servic cell. According to the location record of the
adjacent cell ID in the utranCell and externalUtranCell table, get the DUARFCN
field information of the adjacent cell.
c.
If SIB12Ind in utranCell table is 1(True) SIB11IntraFreqNbrCellNum is

Sib11orSib11bis 0(SIB11)in utranRelation table, and the StateMode field is
0(Idle State only), 3(Idle State + Cell_DCH State), 4(Idle State + Connected
State, Non-Cell_DCH), 6(Idle State + Cell_DCH State+ Connected State,
Non-Cell_DCH). It is the total of the adjacent cells with identical DUARFCN as
the service cell.
SIB11InterFreqNbrCellNum is Sib11orSib11bis 0(SIB11)in utranRelation, and
the StateMode field value is 0 (Idle State only), 3(Idle State + Cell_DCH State),
4(Idle State + Connected State, Non-Cell_DCH), 6(Idle State + Cell_DCH State+
Connected State, Non-Cell_DCH). It is the total of the adjacent cells with different
DUARFCN as the service cell.
d. If in utranCell table, the SIB12Ind is 0 False), SIB11IntraFreqNbrCellNum is

the Sib11orSib11bis 0 SIB11 in utranRelation, and the StateMode field is 0(Idle
State only), 2(Connected State, Non-Cell_DCH), 3(Idle State + Cell_DCH
State), 4(Idle State + Connected State, Non-Cell_DCH), 5(Cell_DCH State +
Connected State, Non-Cell_DCH), 6(Idle State + Cell_DCH State+ Connected
State, Non-Cell_DCH)It is the total of the adjacent cells with the same DUARFCN
as the service cell.
SIB11InterFreqNbrCellNum is Sib11orSib11bis 0(SIB11) in utranRelation and
StateMode field is 0(Idle State only), 2(Connected State, Non-Cell_DCH), 3(Idle
State + Cell_DCH State), 4(Idle State + Connected State, Non-Cell_DCH),
5(Cell_DCH State + Connected State, Non-Cell_DCH) 6(Idle State + Cell_DCH
State+ Connected State, Non-Cell_DCH)It is the total of the number of the
adjacent cells with the same DUARFCN as the service cell.
e. According to the vague location of CId in gsmRelation, find the record of all the
GSM adjacent cells in this servic cell.
f.
If in table utranCell, the SIB12Ind is 1(True) and SIB11InterRatNbrCellNum

is Sib11orSib11bis 0(SIB11) in gsmRelation, and GsmStateMode value is
0(Idle State only) 3(Idle State + Cell_DCH State), 4(Idle State + Connected
2-79
SJ-20100603155704-001|2011-04-09(R2.2)

Non-Cell_DCH). It is the total of all the record number.
g. If in table utranCell, SIB12Ind is 0(False), SIB11InterRatNbrCellNum is
Sib11orSib11bis 0(SIB11)in utranRelation, and GsmStateMode value i s 0(Idle
State only), 2(Connected State, Non-Cell_DCH), 3(Idle State + Cell_DCH
State), 4(Idle State + Connected State, Non-Cell_DCH), 5(Cell_DCH State +
Connected State, Non-Cell_DCH), 6(Idle State + Cell_DCH State+ Connected
State, Non-Cell_DCH). It is the total number of all the records.
2. Note 2
intra-frequency cells SIB11bisIntraFreqNbrCellNum, SIB11bisInterFreqNbrCellNum
and SIB11bisInterRatNbrCellNum:
c.
If SIB12Ind in utranCell table is 1(True) SIB11isIntraFreqNbrCellNumis

Sib11orSib11bis 1(SIB11is)in utranRelation table, and the StateMode field is
0(Idle State only), 3(Idle State + Cell_DCH State), 4(Idle State + Connected
Non-Cell_DCH). It is the total of the adjacent cells with identical DUARFCN as
the service cell.
SIB11bisInterFreqNbrCellNum is Sib11orSib11bis 1(SIB11bis)in utranRelation,
and the StateMode field value is 0 (Idle State only), 3(Idle State + Cell_DCH
State), 4(Idle State + Connected State, Non-Cell_DCH), 6(Idle State + Cell_DCH
State+ Connected State, Non-Cell_DCH). It is the total of the adjacent cells with
different DUARFCN as the service cell.
d. If in utranCell table, the SIB12Ind is 0(False),SIB11isIntraFreqNbrCellNum is

the Sib11orSib11bis 1 SIB11is in utranRelation, and the StateMode field is
0(Idle State only) 2(Connected State, Non-Cell_DCH) 3(Idle State + Cell_DCH
State) 4(Idle State + Connected State, Non-Cell_DCH) 5(Cell_DCH State +
Connected State, Non-Cell_DCH) 6(Idle State + Cell_DCH State+ Connected
State, Non-Cell_DCH)It is the total of the adjacent cells with the same DUARFCN
as the service cell.
SIB11bisInterFreqNbrCellNum
is
Sib11orSib11bis
1(SIB11bis)in
utranRelation and StateMode field is 0(Idle State only) 2(Connected State,
Non-Cell_DCH) 3(Idle State + Cell_DCH State) 4(Idle State + Connected State,
Non-Cell_DCH) 5(Cell_DCH State + Connected State, Non-Cell_DCH) 6(Idle
State + Cell_DCH State+ Connected State, Non-Cell_DCH)It is the total of the
number of the adjacent cells with the same DUARFCN as the service cell.
2-80
SJ-20100603155704-001|2011-04-09(R2.2)
e. According to the vague location of CId in gsmRelation, find the record of all the
f.
If in table utranCell, the SIB12Ind is 1(True) and SIB11bisInterRatNbrCellNum

is Sib11orSib11bis 1 SIB11bis in gsmRelation, and GsmStateMode value is
0(Idle State only) 3(Idle State + Cell_DCH State), 4(Idle State + Connected
Non-Cell_DCH). It is the total of all the record number.
g. If in table utranCell, SIB12Ind is 0(False) SIB11bisInterRatNbrCellNum is

Sib11orSib11bis 1 SIB11bis in utranRelation, and GsmStateMode value i s
0(Idle State only) 2(Connected State, Non-Cell_DCH) 3(Idle State + Cell_DCH
State) 4(Idle State + Connected State, Non-Cell_DCH) 5(Cell_DCH State +
Connected State, Non-Cell_DCH) 6(Idle State + Cell_DCH State+ Connected
State, Non-Cell_DCH). It is the total number of all the records.
3. Note 3
intra-frequency cells SIB12IntraFreqNbrCellNum, SIB12InterFreqNbrCellNum and
SIB12InterRatNbrCellNum:
c.
If SIB12Ind in utranCell table is 1(True)SIB12IntraFreqNbrCellNum is StateMode

field value 2 (Connected State, Non-Cell_DCH) in utranRelation 4(Idle State
+ Connected State, Non-Cell_DCH) 5(Cell_DCH State + Connected State,
Non-Cell_DCH)6(Idle State + Cell_DCH State+ Connected State, Non-Cell_DCH).
It is the total of the adjacent cells with identical DUARFCN as the service cell.
In utranRelation, the SIB12InterFreqNbrCellNum is StateMode field value
2(Connected State, Non-Cell_DCH) 4(Idle State + Connected State,
Non-Cell_DCH) 5(Cell_DCH State + Connected State, Non-Cell_DCH) 6(Idle
State + Cell_DCH State+ Connected State, Non-Cell_DCH). It is the total of the
adjacent cells with different DUARFCN as the service cell.
d. According to the vague location of CId in gsmRelation, find the record of all the
e. If in table utranCell, SIB12Ind is 1(True) the SIB12InterRatNbrCellNum is
GsmStateMode field value 2(Connected State, Non-Cell_DCH) 4(Idle State
+ Connected State, Non-Cell_DCH) 5(Cell_DCH State + Connected State,
Non-Cell_DCH)6(Idle State + Cell_DCH State+ Connected State, Non-Cell_DCH).
It is the total number of all the records.
2-81
SJ-20100603155704-001|2011-04-09(R2.2)
2.2.26.3 GSM Neighbouring Cell (gsmRelation)
2-82
SJ-20100603155704-001|2011-04-09(R2.2)
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
NPhyGsmCId
externalGsmCell
AdjPhyGsmCId
There must be a record in the related object externalUtranCell corresponding to

MCC+MNC+LAC+CI
CId
utranCell
CId
Before the record of gsmRelation with the cell is created, it must be ensured that there
exists the corresponding cell record in utranCell
PenaltyTimeSib11
gsmRelation
TempOffset1Sib11
When the value of PenaltyTimeSib11 is 1(Not used), then TempOffset1Sib11 and TempOffset2Sib11 is invalid
PenaltyTimeSib12
gsmRelation
TempOffset1Sib12
When the value of PenaltyTimeSib12 is 1(Not used), then TempOffset1Sib12 and TempOffset2Sib12 is invalid
Cld
gsmRelation
MCC+MNC+LAC+CI
A cell has up to 32 adjacent GSM cell
UseOfHCS
gsmRelation
QhcsSib11
Only when the value of UseOfHCS is 2(Used), related parameters are valid
QhcsSib12
2-83
PenaltyTimeSib11
PenaltyTimeSib12
Sib11orSib11bis
gsmRelation
GsmStateMode
If GsmStateMode is 1 (Cell_DCH State only) then Sib11orSib11bis is invalid
Sib11orSib11bis
gsmRelation
GsmStateMode
If in table utranCell, SIB12Ind is 1 True , then the GsmStateMode in this table is 2(Con-
utranCell
SIB12Ind
nected State, Non-Cell_DCH)5(Cell_DCH State + Connected State, Non-Cell_DCH), and
Sib11orSib11bis is invalid
Related Object
Related Parameter
CIdNPhyGsmCId
utranRelation
CId
There are at most 31 intra-frequency neighboring cells and 32 inter-frequency
NCToSelfPhyRnc+NPhy-
neighboring cells, 32 GSM neighboring cells
CId
Supposing that SIB11IntraFreqNbrCellNum is the number of intra-frequency

neighboring cells that are broadcasting in SIB11l (excluding the local utran cell),
SIB11InterFreqNbrCellNum is the number of inter-frequency neighboring cells of utran
cell that are broadcasting in SIB11, and SIB11IntraRatNbrCellNumis the number of
inter-rat neighboring cells of utran cell that are broadcasting in SIB11, the total number of
neighboring cells that can be configured is:
1. If there is only inter-rat neighboring cell and no intra-frequency or inter-frequency
neighboring cell, 120+75*(SIB11InterRatNbrCellNum -1)<=3330
2. If there are only intra-frequency and inter-frequency neighboring cell but no inter-rat
neighboring cell, 200 + 48* SIB11IntraFreqNbrCellNum + 75*(SIB11InterRatNbrCell-
2-84
Num - 1) <=3330
3. If there are only inter-frequency and inter-rat neighboring cell but no intra-frequency
neighboring cell, 207 + 79*(SIB11InterFreqNbrCellNum-1)+ 75*(SIB11InterRatNbrCellNum - 1) <=3330
4. If all the three types of neighboring cells exist, 287+ 48* SIB11IntraFreqNbrCellNum
+ 79*(SIB11InterFreqNbrCellNum-1)+ 75*(SIB11InterRatNbrCellNum - 1) <=3330
The steps to judge whether to broadcast this neighbouring cell in SIB11

l
See SIB12Ind in utranCell and check whether SIB12 is configured. If SIB12Ind is 1

(True), in Non Cell_DCH state, you can read the neighboring cell list in SIB12. That
is, the system configures the neighboring cell lists in Idle state and Non Cell_DCH
state separately
0(Idle State only)
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
If SIB12Ind in UtranCell is 0 (False), in Non Cell_DCH state, you can read the neighboring cell list in SIB11. That is, the system configures the neighboring cell lists in
Idle state and Non Cell_DCH state together
2-85
utranCell
SIB12Ind
0(Idle State only)
2(Connected State, Non-Cell_DCH)
5(Cell_DCH State + Connected State, Non-Cell_DCH)
6 (Idle State + Cell_DCH State+ Connected State, Non-Cell_DCH)
Set the SIB11bisIntraFreqNbrCellNum is the nuber of the intra-frequency adjacent cells

in the SIB11bis broadcast service cell, not including the local service cell;
SIB11bisInterFreqNbrCellNum is the nuber of the inter-frequency adjacent cells in the
SIB11bis broadcast service cell

The limit to to total number of adjacent cell is:
1.
If only inter-system adjacent cells exists with no inter-frequency adjacent cell and
intra-frequency adjacent cell; then 120+75* SIB11bisInterRatNbrCellNum -1 <=3330,
otherwise the interface prompts the total number of SIB11bis adjacent cells are over
sized
2. If only inter-system adjacent cells and intra-frequency adjacent cell exist with no inter-frequency adjacent cell; 200 + 48* SIB11bisIntraFreqNbrCellNum + 75*( SIB11bis-
SIB11bis broadcast service cell

SIB11bisInterRatNbrCellNum is the nuber of the inter-system adjacent cells in the
Related Object
Related Parameter
InterRatNbrCellNum - 1) <=3330, otherwise the interface prompts the total number of
SIB11bis adjacent cells are over sized
3. If only inter-system adjacent cells and inter-frequency adjacent cell exist with no intrafrequency adjacent cell; 207 + 79*SIB11bisInterFreqNbrCellNum-1+ 75*( SIB11bisInterRatNbrCellNum - 1) <=3330, otherwise the interface prompts the total number of
SIB11bis adjacent cells are over sized
4. If all three types of adjacent cells exist, then 287+ 48* SIB11bisIntraFreqNbrCellNum +
79*SIB11bisInterFreqNbrCellNum-1+ 75*(SIB11bisInterRatNbrCellNum - 1) <=3330,
otherwise the interface prompts the total number of adjacent adjacent cells are over
sized
gsmRelation
Sib11orSib11bis
Set the SIB12IntraFreqNbrCellNum is the nuber of the intra-frequency adjacent cells in

the SIB12 broadcast service cell, not including the local service cell;
2-86
SIB12InterFreqNbrCellNum is the nuber of the inter-frequency adjacent cells in the

SIB12 broadcast service cell
SIB12InterRatNbrCellNum is the nuber of the inter-system adjacent cells in the SIB12
broadcast service cell
The limit to to total number of adjacent cell is:
1.
If only inter-system adjacent cells exists with no inter-frequency adjacent cell and
intra-frequency adjacent cell; then 120+75*SIB12InterRatNbrCellNum -1<=3330, otherwise the interface prompts the total number of SIB12 adjacent cells are over sized
2. If only inter-system adjacent cells and intra-frequency adjacent cell exist with no interfrequency adjacent cell, then 200 + 48* SIB12IntraFreqNbrCellNum + 75*( SIB12InterRatNbrCellNum - 1) <=3330, otherwise the interface prompts the total number of
SIB12 adjacent cells are over sized
3. If only inter-system adjacent cells and inter-frequency adjacent cell exist with no intrafrequency adjacent cell, then 207 + 79*SIB12InterFreqNbrCellNum-1+ 75*( SIB12InterRatNbrCellNum - 1) <=3330, otherwise the interface prompts the total number of
SIB12 adjacent cells are over sized
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
4. If all three types of adjacent cells exist, then 287+ 48* SIB12IntraFreqNbrCellNum +
79* SIB12InterFreqNbrCellNum-1 + 75*(SIB12InterRatNbrCellNum - 1) <=3330, otherwise the interface prompts the total number of SIB12 adjacent cells are over sized
2-87
2.2.26.4 Cell Frequency Reselection and Priority (PriSel)
2-88
SJ-20100603155704-001|2011-04-09(R2.2)
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
CId
utranCell
CId
The field should also be created in another related table
UtranPriority[i]
PriSel
UtranPriority[i]
Among the three systems, the priorities are mutually exclusive. If a priority level in the
EutranPriority[i]
EutranPriority[i]
interval [0,7] has been applied to a node of UTRAN/EUTRAN system frequency or of cell
GeranPriority [i]
GeranPriority [i]
group priority array, the level cannot be applied in any other system. Systems cannot share
a priority level, but different frequency points or cell groups can have the same level
2-89
2.2.26.5 Cell Selection and Reselection (CelSel)
2-90
SJ-20100603155704-001|2011-04-09(R2.2)
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
CId
utranCell
CId
Before the record of CelSel with the cell is created, It must be ensured that there exists the
corresponding cell record in utranCell
HcsSrvCelInfoPre
utranCell
UseOfHCS
When UseOfHCS is 1(Not Used), HcsSrvCelInfoPre must be set to 0(False)
SIntraSearchPre
CelSel
SIntraSearch
Only when the value of SintraSearchPre is 1(True), SintraSearch is valid
SInterSearchPre
CelSel
SInterSearch
Only when the value of SinterSearchPre is 1(True), SinterSearch is valid
SSearchHCSPre
CelSel
SSearchHCS
Only when the value of SSearchHCSPre is 1(True), SSearchHCS is valid
OtherRATInfoPre
CelSel
SSearchRat
Only when the value of OtherRATInfoPre is 1(True), related parameters are valid
SHCSRatPre
SLimitRat
OtherRATInfoPre
2-91
CelSel
SHCSRat
Only when OtherRATInfoPre and SHCSRatPre are 1(True), SHCSRat is valid
HcsSrvCelInfoPre
CelSel
TCrMax
Only when the value of HcsSrvCelInfoPre is 1(True), TCrMax is valid
HcsSrvCelInfoPre
CelSel
NCr
Only when HcsSrvCelInfoPre is 1(True) and TcrMax is not 1(not used), related parameters
TCrMaxHyst
are valid
QHyst1SPch,
Only when Sib3orSib4 is 1(SIB4), related parameter are valid
SHCSRatPre
TCrMax
Sib3orSib4
CelSel
Sib3orSib4
CelSel
TReselectionPch,
TReselectionFach
Sib3orSib4
CelSel
QqulmnOffstPre
QqualminOffset
QrxlvmnOffstPre
QrxlevminOffset
Sib3orSib4
QualMeas
CelSel
QHyst2SPch,
Only when Sib3orSib4 is 1(SIB4) and QualMeas is 1(CPICH Ec/No), related parameter
QHyst2SFach,
are valid
QHyst1SFach
Related Object
Related Parameter
QualMeas
CelSel
QHyst2S
Only when QualMeas is 1(CPICH Ec/No), QHyst2S is valid
NoHcsTCrMax
CelSel
NoHcsNCr
Only when NoHcsTcrMax is not 1(Not Used), related parameter are valid
NoHcsTCrMaxHyst
2-92
SpSfPre
CelSel
SpSf
Only when SpSfPre is 1(True), SpSf is valid
InterFreqSfPre
CelSel
InterFreqSf
Only when InterFreqSfPre is 1(True), InterFreqSf is valid
InterRatSfPre
CelSel
InterRatSfPre
Only when InterRatSfPre is 1(True), InterRatSf is valid
QRxLevMin
CelSel
DltaQRxLevMinPr
When QRxLevMin is not 0(-115dBm), DltaQRxLevMinPrmust be 0(False)
DltaQRxLevMinPr
CelSel
DeltaQrxlevmin
Only when DltaQRxLevMinPr is 1(True), DeltaQrxlevmin is valid
QqulmnOffstPre
CelSel
QqualminOffset
Only when QqulmnOffstPre is True, QqualminOffset is valid
QrxlvmnOffstPre
CelSel
QrxlevminOffset
Only when QrxlvmnOffstPre is True, QrxlevminOffset is valid
Sib3orSib4
null
null
There must be one record that Sib3orSib4 equals to 0(SIB3) for each cell
DefSibSuptSwch
CelSel
IntraRptQSib3
When DefSibSuptSwch is 1(open), the relsted field is valid
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
2.2.26.6 HSPA Configuration Information in a Cell (CHspa)
2-93
SJ-20100603155704-001|2011-04-09(R2.2)
Related Object
Related Parameter
CId
utranCell
CId
Before the record of CHspa with the cell is created, it must be ensured that there exists
the corresponding cell record in utranCell
HsdpaScramCode
utranCell
HspaSptMeth
NULL
utranCell
HspaSptMeth
Only when, in the association table, the HspaSptMeth value is 3(Support HSUPA, HSDPA
NumofHspdsch
NumofHsscch
HsdschTrafLimit
MinNumofHspdsch
MaxNumofHspdsch
DpchCodeHy
CodeUptHyA
HspdschBitRate
MinHspaPwrRto
2-94
MaxHspaPwrRto
HspaPwrRatio
NumofEagch
NumofErgHich
and DCH);4(Support HSUPA and HSDPA), the fields in this table are valid
NServToTotalPwr
EdchTrafLimit
MaxRTWP
Ergch2IdxStepThr
Ergch3IdxStepThr
HspaPwrRatio
CHspa
MinHspaPwrRto
MinHspaPwrRto<= HspaPwrRatio <=MaxHspaPwrRto
MaxHspaPwrRto
NumofHspdsch
CHspa
MinNumofHspdsch
MinNumofHspdsch<= NumofHspdsch<= MaxNumofHspdsch
MaxNumofHspdsch
DpchCodeHy
CHspa
CodeUptHyA
DpchCodeHy >= CodeUpHyA >= 0
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Ergch2IdxStepThr
HspaPwrRatio
Hspa
Related Parameter
Ergch3IdxStepThr
Ergch2IdxStepThr> =Ergch3IdxStepThr
HsdschTotPwrMeth
Only when the value of HsdschTotPwrMeth is 0(RNC Static Assigning Mode) or 1(RNC
Dynamic Assigning Mode), HspaPwrRatio is valid
MinHspaPwrRto,
Hspa
HsdschTotPwrMeth
MaxHspaPwrRto
HsShareInd
Only when the value of HsdschTotPwrMeth is 1(RNC Dynamic Assigning Mode), MinHspaPwrRto and MaxHspaPwrRto are valid
NodeB
HsSharMethod
Only when HsSharMethod which is in the corresponding cell is 1(RNC controlled),

HsShareInd is valid
CodeReAssHy
Hspa
CodeReAssInd
Only when CodeReAssInd value is 1(Support), then CodeReAssHy is valid
CHsGBRResLmtIdx
GbrRes
HsGBRResLimitIdx
The fields in this table must exist in the association table
2-95
2.2.26.7 MBMS Configuration Information in a Cell (CMbms)

Related Ob-
Related Parame-
rameter
ject
ter
CId
utranCell
CId
All the parameters in this table must exist in utranCell
All fields in the
utranCell
MbmsSuptInd
The fields in the table are valid only if the corresponding field
Original
Pa-
table
MbmsSuptInd is 1 (Support MBMS and not MBMS) or 2 (Only

Support MBMS) in the related table
TfsIndex
(Source
Tfs
In-
TfsIndex (Target
There must be a record in Tfs corresponding to TfsIndex
Index)
dex)
TfsIndex
(Source
Tfs
ChType
In-
There must be a record in Tfs corresponding to TfsIndex, and

ChType of the record in Tfs must be 1(FACH)
dex)
2.2.26.8 UtranCell Information in MBMS Service Area (MbmsSa)
2-96
SJ-20100603155704-001|2011-04-09(R2.2)
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
MCC
utranCell
MCC
There must be a record in utranCell corresponding to MCC+ MNC+CId
MNC
MNC
CId
CId
MCC
utranCell
MCC,
One cell can belong to different MBMS service area
MNC
MNC
The values of FreqBandInd in utranCell for the cells belonging to one frequency layer of
MbmsSac
CId
one MBMS service area must be the same and equal to the FreqBandInd of MbmsSa.
DUARFCN
DUARFCN
And the corresponding cells must support MBMS
FreqBandInd
FreqBandInd
MbmsSuptInd
MbmsSac
MbmsSa
null
The maximum number of frequency layers of the same MBMS service area is 4
MbmsSa
DUARFCN
When the value of FreqBandInd is 0(Band I), the value range of DUARFCN must be
FreqBandInd
DUARFCN
2-97
FreqBandInd
[10562, 10838]
When the value of FreqBandInd is 1(Band II), the value range of DUARFCN must be
([9662, 9938], 412, 437, 462, 487, 512, 537, 562, 587, 612, 637, 662, 687)
When the value of FreqBandInd is 2(Band III), the value range of DUARFCN must be
When the value of FreqBandInd is 4(Band V), the value range of DUARFCN must be
([4357, 4458] , 1007, 1012, 1032, 1037, 1062, 1087)
When the value of FreqBandInd is 5(Band VI), the value range of DUARFCN must be
([4387,4413], 1037, 1062)
When the value of FreqBandInd is 7(Band VIII), the value range of DUARFCN must
be [2937, 3088]
FreqPLInd
MbmsSa
null
One MBMS SAC can contain only one or none preferred frequency layer
The preferred frequency can cover the whole MBMS SA district
[1162, 1513]
2.2.26.9 Cell Enhanced Fach(EFach)

Original
Related
Related
Pa-
Parameter
Object
rameter
CID
utranCell
CID
The field in this table must exist in utranCell
MACehsQI-
EFach
EFACHSpptInd
When the Related Parameter is 1, the field in this table
D[]
is valid
ChTypeInd[
]
SPI[]
DlEFACHT1[]
DLEFACHTreset[]
MACehsWinSize[]
DTCfgInd[]
DiscardTimer[]
MaxMacPDUSize[]
EFACHHSSCCHPwr
EFACHHSPDSCHPwr
DTCfgInd[]
EFach
DiscardTimer[]
When the corresponding DTCfgInd is 1(yes), DiscardTimer is valid
MACehsQI-
EFach
NULL
The different value of the nodes in MACehsQID[] must
D[]
SPI []
be different
EFach
NULL
The different value of the nodes in SPI[] must be different
2.2.26.10 HS-PDSCH Measurement Power Offset(CelMPO)

Original
Related
Related
Parameter
Object
rameter
CID
utranCell
CID
Pa-
2-98
SJ-20100603155704-001|2011-04-09(R2.2)
Original
Related
Related
Parameter
Object
rameter
Pa-
MeasP-
utranCell
HspaSptMeth
wrOffset
Only when HspaSptMeth in utranCell take the value

1(Support HSDPA and DCH) or 2(Support HSDPA
only) or 3(Support HSUPA , HSDPA and DCH) or
4(Support HSUPA and HSDPA), MeasPwrOffset in
CelMPO is valid
2.2.26.11 Physical Channel

2.2.26.11.1 PSCH (Psch)
Original Pa-
Related
Ob-
Related Parame-
rameter
ject
ter
CId
utranCell
CId
Before the record of Psch with the Cell is created, it must be

ensured that there exist the corresponding cell record in utranCell
TstdInd
utranCell
CId
If, in the nodeB list, the NodeBType is PicoNodeB, then Tst-
nodeB
NodebType
dInd value is always set to inactive
2.2.26.11.2 SSCH (Ssch)

Original Pa-
Related Ob-
Related Parame-
rameter
ject
ter
Cid
utranCell
CId
The parameters in this table must be exist in utranCell
2.2.26.11.3 PCPICH (Pcpich)

Original Pa-
Related Ob-
Related Parame-
rameter
ject
ter
Cid
utranCell
CId
Before the record of Pcpich with the Cell is created, it must

be ensured that there exist the corresponding cell record in
utranCell
TxDivInd
PcpichPwr
utranCell
CId
If, in the nodeB list, the NodeBType is PicoNodeB, then the
node B
NodebType
TxDivInd value in this table is always set to inactive
utranCell
MAXDlTxPwr
For the physical value, PcpichPwr<= MAXDlTxPwr
2-99
SJ-20100603155704-001|2011-04-09(R2.2)
2.2.26.11.4 PCCPCH (Pccpch)

Original Pa-
Related Ob-
Related Parame-
rameter
ject
ter
Cid
utranCell
CId
Before the record of Pccpch with the Cell is created, it must

be ensured that there exists the corresponding cell record in
utranCell
SttdInd
utranCell
CId
nodeB
NodebType
SttdInd value in this table is always set to inactive
2.2.26.11.5 SCPICH (Scpich)

Original Pa-
Related Ob-
Related Parame-
rameter
ject
ter
CId
utranCell
CID
Before the record of Scpich with the Cell is created, it must

be ensured that there exists the corresponding cell record in
utranCell
SttdInd
Psch
TstdInd
Pcpich
TxDivInd
all active, then TxDivInd in this table may take the value as
Pccpch
SttdInd
active
utranCell
CId Nodeb
nodeB
Type
ScpichPwr
Scpich
ScpichPwr
The configured range of ScpichPwr in this table is in [-6..0]dB
CID
utranCell
CID
IF there are no records of cell, ScpichSupInd correspond to
ScpichSupInd
cell in utranCell can not be TRUE
SttdInd
Only when Psch TstdInd, Pcpich TxDivInd, Pccpch SttdInd are
2.2.26.11.6 SCCPCH (Sccpch)
2-100
SJ-20100603155704-001|2011-04-09(R2.2)
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
CId
utranCell
CId
PichCPCId
Pich
CPCId
CPCId
Fach
SccpchCPCId
CPCId
Pch
SccpchCPCId
TfcsIndex
DlTfcs
TfcsIndex
PCHInd
Sccpch
DlScraCode
When PCHInd is 1(True), DlScraCode must be 0. The SCCPCH bearing PCH uses main
scrabble code only
PCHInd
Sccpch
PichCPCId
Only when PCHInd is TRUE, then PichCPCId is valid
SlotFmt
Sccpch
DlChCodeNo
When the value of SlotFmt is [0, 3], the value range of DlChCodeNo is [0, 255]
2-101
When the value of SlotFmt is [10,11], the value range of DlChCodeNo is [0, 31]
When the value of SlotFmt is [14, 15], the range value of DlChCodeNo is [0, 7]
Sib5orSib6
Sccpch
SccpchUsage
For each cell, there must be one SIB5 record(i.e Sib5orSib6 takes the value of 0(SIB5) or
SttdInd
Psch
TstdInd
Only when TstdInd of Psch is 0(Active), TxDivIndof Pcpich and SttdInd of Pccpch are 1(Ac-
Pcpich
TxDivInd
tive), SttdInd of Sccpch can be taken the value of 1(Active)
Pccpch
SttdInd
CId
utranCell
CId
If, in the nodeB list, the NodeBType is PicoNodeB, then DlScraCode value is always set
DlScraCode
nodeB
NodeBType
to 0; SlotFmt value can be only 0, 2, 4, 6, 8, 10, 12 or 14
utranCell
CId
If, in the nodeB list, the NodeBType is PicoNodeB, then the SttdInd value in this table is
nodeB
NodeBType
always set to inactive
SlotFmt
SttdInd
2(SIB5 and SIB6))
Related Object
Related Parameter
TfcsIndex
utranCell
CId
If, in the nodeB list, the NodeBType is PicoNodeB, then local tables TfcsIndex correspond-
NodeB
NodeBType
ing DlTfcs tables CtfcNum value is up to 64
DITfcs
CtfcNum
SccpchUsage
Sccpch
MplexPos
When SccpchUsage is 1(Used for MCCH), MplexPos must be 1(Flexible)
SccpchUsage
Sccpch
Sib5OrSib6
When SccpchUsage is 1(Used for MCCH), Sib5OrSib6 must be 0(SIB5)
SccpchUsage
Sccpch
PCHInd
When SccpchUsage is 1(Used for MCCH), PCHInd must be 0(False)
SccpchUsage
Sccpch
PichCPCId
When SccpchUsage is Used for MCCHPichCPCId must be invalid
SccpchUsage
Sccpch
null
For each cell, there is at most one record that SccpchUsage of the record is 1(Used for
MCCH) or 2(Use for MCCH and R99)
CPCId
Mich
SccpchCPCId
2-102
SccpchUsage
If SCCPCH is used to carry MCCH (i.e. SccpchUsage of the record is 1(Use for MCCH)
or 2(Use for MCCH and R99)), the CPCId of this SCCPCH must be 35 and there exists
only one MICH that corresponds to this SCCPCH for the cell
SccpchUsage
Sccpch
SlotFmt
If SccpchUsage is 1(Used for MCCH), the value range of SlotFmt is 2, 6, 8, 10, 12, 14, or
16
CPCId
UtranCell
MbmsSuptInd
SccpchUsage
CPCId
If the cell supports MBMS, the SCCPCH with SccpchUsage value of 1(Used for MCCH)
or 2(Used for MCCH and R99) in Sccpch cannot be deleted
Sccpch
SccpchUsage
If in this table, the SccpchUsage is 1(Use for MCCH) or 2(Use for MCCH and R99), then
CPCId is 35
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
2.2.26.11.7 PICH (Pich)

Original Pa-
Related
rameter
ject
ter
CId
utranCell
CId
PchCTCId
Pch
CTCId
SttdInd
Psch
TstdInd
Only when TstdInd of Psch is 0(Active), TxDivInd of Pcpich and
Pcpich
TxDivInd
SttdInd of Pccpch are 1(Active), SttdInd of Pich can take the
Pccpch
SttdInd
value of 1(Active)
utranCell
CId
nodeB
NodebType
SttdInd
Ob-
Related Parame-
2.2.26.11.8 PRACH (Prach)
2-103
SJ-20100603155704-001|2011-04-09(R2.2)
Related Object
Related Parameter
CId
utranCell
CId
Before the record of Prach with the Cell is created, It must be ensured that there exists the
CPCId
Rach
PrachCPCId
Before the record of Prach is deleted, It must be ensured that there is no record in Rach
which quotes the CId+CPCId. Otherwise, this record with the CId+CPCId in Prach is not
allowed to delete
TfcsIndex (Source In-
UlTfcs
TfcsIndex (Target Index)
There must be a record in UlTfcs corresponding to TfcsIndex
Prach
AsigStIdx
AsigStIdx<= AsigEndIdx<=(the number of Signature bit that equals to1) - 1
dex)
Signature
AsigEndIdx
2-104
AsigStIdx
Prach
AsigEndIdx
AsigStIdx<= AsigEndIdx
PermitMaxASC
Prach
PsfNum
PsfNum<= PermitMaxASC-2; if PermitMaxASC-2 is a negativePsfNum must be 0
NB01min
Prach
NB01max
NB01min< =NB01max
Sib5orSib6
null
null
For each cell, there must be one SIB5 record (i.e Sib5orSib6 takes the value of 0(SIB5) or
2(SIB5 and SIB6))
AvailSubChanNum
Prach
null
For AvailSubChanNum of different PRACHs in a cell, the corresponding bit must be different
ConstVal
Tfs
Rach
TfsIndex
If TTI of Tfs recordswith RACHs carrying on PRACHs in a cell is same, then ConstVal must
TTI
be same for these PRACHs
TfsIndex
PrachCPCId
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
TfcsIndex
ulTfcs
TfcsIndex
If TTI of Tfs records with RACHs carrying on PRACHs in a cell is same, then BetaC[i], Be-
CtfcNum
taD[i], POPpm[i] of ulTfcs recordsmust be same for these PRACHs and TrBlkNum[j]*Rlc-
BetaC[32]
Size[j] of Tfs recordsmust be same for these RACHs.(i=[1,CtfcNum], j=[1, TfNum])
BetaD[32]
POPpm[32]
Tfs
TfsIndex
TfNum
TrBlkNum[32]
RlcSize[32]
TTI
Rach
TfsIndex
2-105
PrachCPCId
2.2.26.11.9 AICH (Aich)

Original Pa-
Related Ob-
Related Parame-
rameter
ject
ter
CId
utranCell
CId
The field in this table must be in utranCell
PrachCPCId
Prach
CPCId
The field in this table must be in Prach
SttdInd
Psch
TstdInd
Only when TstdInd of Psch is 0(Active), TxDivInd of Pcpich
Pcpich
TxDivInd
Pccpch
SttdInd
utranCell
CId
nodeB
NodebType
utranCell
CId
nodeB
NodebType
and SttdInd of Pccpch are 1(Active), SttdInd of Aich can be

taken the value of 1(Active)
SttdInd
AichTranTime
If, in the nodeB list, the NodeBType is PicoNodeB, then this

lists SttdInd value is always set to inactive
If, in the nodeB list, the NodeBType is PicoNodeB, then this
lists AichTranTime value is always set to 1
2.2.26.11.10 MICH (Mich)

Original
Related
Related
Parameter
Object
Parameter
CId
utranCell
CId
SttdInd
Psch
TstdInd
The field in this table must be in utranCell
Only when TstdInd of Psch is 0(Active), SttdInd of Pcpich
and TxDivInd of Pccpch are 1(Active), SttdInd of Mich can be
SttdInd
SccpchCPCId
Pcpich
TxDivInd
Pccpch
SttdInd
utranCell
CId
taken the value of 1(Active)

nodeB
NodebType
Sccpch
CPCId
The field in this table must exist in the association table, and
SccpchUsage
in the corresponding association record, the SccpchUsage

must be Use for MBMS
2.2.26.12 Transport Channel

2.2.26.12.1 BCH (Bch)
Original Pa-
Related Ob-
Related Parame-
rameter
ject
ter
CId
utranCell
CId
2.2.26.12.2 FACH (Fach)
2-106
SJ-20100603155704-001|2011-04-09(R2.2)
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
CId
utranCell
CId
SccpchCP-
Sccpch
CId+CPCId
There must be a record in Sccpch corresponding to CId+SccpchCPCId
CId(Source Index)
TfsIndex (Source In-
(Target Index)
Tfs
dex)
CtchInd
Tfs
TfsIndex (Target Index)
There must be a record in Tfs corresponding to TfsIndex, and ChType of the record in Tfs
ChType
must be 1(FACH)
TTI
TfsIndex
If CtchInd is 1(True), then values of CtchAllocPrd and CbsFrameOffset must be a multiple

of TTI/10
CtchAllocPrd
CbsFrameOffset
2-107
CId
Fach
CtchInd
There is at most one Fach that CtchInd of the Fach is 1(True) in a cell
CtchInd
Fach
CtchAllocPrd
Only when CtchInd is True, related parameters are valid, and CtchAllocPrd>
CbsFrameOffset
CbsFrameOffset
TfNum
If Multiple FACHs are beared on the same SCCPCH, RlcSize[i]of Tfs record must be dif-
RlcSize[32]
ferent for these FACHs. (i=[1, TfNum])
utranCell
CId
When, in the nodeB, the NodeBType is PicoNodeB, the Fach channel on one Sccpch can
nodeB
NodebType
UtranCell
CId
nodeB
NodebType
Sccpch
SccpchUsage
CId
Tfs
SccpchCPCId
TfsIndex
CTCId
ToAWS
ToAWE
CtchInd
CtchAllocPrd
CbsFrameOffset
not be more than two

When, in the nodeB table, the NodeBType is PicoNodeB, ToAWSToAWE<=100ms in this
table
If SccpchUsage of SCCPCH that carries this FACHis 1(Use for MCCH), CtchInd, CtchAllocPrd and CbsFrameOffset are invalid
SccpchCPCId
Related Object
Related Parameter
SignalFach
Sccpch
SccpchUsage
If SccpchUsage of SCCPCH that carries this FACH takes the value of 1(Used for
MCCH), SignalFach of Fach must be 3(MCCH), and there can only be one FACH on
the corresponding SCCPCH
If SccpchUsage of the SCCPCH that carries this FACH takes the value of 2(Used for
MCCH and R99), there can only be one FACH whose SignalFach is 2(R99 Signaling+MCCH) on the corresponding SCCPCH.
SignalFach
BMCSCHMSGPRDPRE
Fach
Fach
SccpchCPCId
If the value of SignalFach is 2(R99 Signaling+MCCH) or 3(MCCH), then SccpchCPCId
CTCId
must be 35 and CTCId must be 32
BmcSchMsgPrd
The related field is valid only if BMCSCHMSGPRDPRE is TRUE
2-108
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
2.2.26.12.3 PCH (Pch)

Original Pa-
Related Ob-
Related Parame-
rameter
ject
ter
CId
utranCell
CId
SccpchCP-
Sccpch
CPCId
There must be a record in the Sccpch corresponding to Sc-
CId
CTCId
cpchCPCId
Pich
PCHCTCId
Before the record of Pch is deleted, it must be ensured that

there is no Pichs record which quotes the CTCId. Otherwise,
this record with the CTCId in Pch is not allowed to delete
TfsIndex
Tfs
TfsIndex
There must be a record in the Tfs corresponding to TfsIndex,

and ChType of the record in Tfs must be 2(PCH)
TfsIndex
Tfs
ChType
There must be a record in the Tfs corresponding to TfsIndex,

and ChType of the record in Tfs must be 2(PCH)
ToAWS
ToAWE
utranCell
CId
nodeB
NodebType
If, in the nodeB list, the NodeBType is PicoNodeB, then in this

table, ToAWSToAWE<=100ms
2.2.26.13 RACH (Rach)

Original Pa-
Related Ob-
Related Parame-
rameter
ject
ter
CId
utranCell
Cid
PrachCPCId
Prach
CPCId
The field in this table must exist in Prach
TfsIndex
Tfs
TfsIndex
The field in this table must exist in Tfs
TfsIndex
Tfs
ChType
There must be a record in Tfs corresponding to TfsIndex, and

ChType of the record in Tfs must be 0(RACH)
2.2.26.14 Power Control

2.2.26.14.1 Power Control not Related to Service (PC)
Original Pa-
Related
rameter
ject
Ob-
Related Parameter
CId
utranCell
CId
2-109
SJ-20100603155704-001|2011-04-09(R2.2)
2.2.26.15 Access Control

2.2.26.15.1 Cell-Related Access Control (AC)
Original
Pa-
Related Ob-
Related Parame-
rameter
ject
ter
CId
utranCell
CId
MinOrthog-
AC
MaxOrthogFactor
MaxOrthogFactor>= MinOrthogFactor
AC
BckNoiMaxStep
BckNoiThr < BckNoiMaxStep< BckNoiMaxAdjAst
Factor
BckNoiThr
BckNoiMaxAdjAst
StaWinNum
AC
EffUnldCntThr
StaWinNum<= EffUnldCntThr
LdFactCal-
AC
BgNoiUptSrvNum
LdFactCalSrvNum>= BgNoiUptSrvNum
SrvNum
2.2.26.16 Load Control Relationship (LdCtrl)
2-110
SJ-20100603155704-001|2011-04-09(R2.2)
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
CId
utranCell
CId
Before the record of LdCtrl with the Cell is created, it must be ensured that there exists the
UlOverLd
LdCtrl
UlSeriousOverLd
UlSeriousOverLd>UlOverLd>UlAlrmLd
UlAlrmLd
DlOverLd
LdCtrl
DlSeriousOverLd
DlSeriousOverLd>DlOverLd>DlAlrmLd
DlAlrmLd
UlOverLd
UlSeriousOverLd
DlOverLd
utranCell
BPriAcIndex
BPriAc
DchUlAcThresh
utranCell
BPriAcIndex
BPriAc
DchDlAcThresh
utranCell
BPriAcIndex
DlSeriousOverLd
2-111
DlOverLd
same BPriAcIndex as that in the utranCell

DlSeriousOverLd>DlOverLd> DchDlAcThresh of all the records in BPriAc which have the
DlSeriousOverLd
HsdsOverLdThr
UlSeriousOverLd>UlOverLd> DchUlAcThresh of all the records in BPriAc which have the
DlSeriousOverLd>DlOverLd> MbmsAcThresh of all the records in BPriAc which have the

BPriAc
MbmsAcThresh
LdCtrl
HsdsOverLdThr
HsdsOverLdThr> HsdsRecoverThr
DlOverLd
LdCtrl
DlAlrmLd
HsdsOverLdThr
HsdsOverLdThr> HsdsRecoverThr> DlOverLd> DlAlrmLd
HsdsRecoverThr
NodeBSafeThr
LdCtrl
HsdsRecoverThr DlOverLd
HsdsRecoverThr >= NodeBSafeThr> =DlOverLd
NodeBSafeThr
utranCell
BPriAcIndex
NodeBSafeThr> HsdpaAcThresh of all the records in BPriAc which have the same
BPriAc
HsdpaAcThresh
LCMeasWinSize
LdCtrl
LcTrigTimes
LCMeasWinSize>=LcTrigTimes
DecGbrSw
LdCtrl
MaxGbrDecNum
Only when DecGbrSw is 1(Open), the associated field is valid
BPriAcIndex as that in the utranCell
HsdsRecoverThr
Related Object
Related Parameter
DecGbrSw
rncFunction
QosNegRenegSwi
Only when QosNegRenegSwi value is 1(Switch Off QoS Negotiation, Switch On QoS
Renegotiation ) or 3 (Switch On QoS Negotiation, Switch On QoS Renegotiation ), it is
valid
UlHighLd
BasPri
BPriAc
TrafficClass
UlHighLd is fewer than DchUlAcThresh which is in BPriAc and corresponds to BasicPrio .
BasicPrio
The BasicPrio corresponds to TrafficClass=0 in BasPri
BasicPrio
DchUlAcThresh
DlHighLd
BasPri
BPriAc
TrafficClass
DlHighLd is fewer than DchDlAcThresh which is in BPriAc and corresponds to BasicPrio .
BasicPrio
The BasicPrio corresponds to TrafficClass=0 in BasPri
BasicPrio
DchDlAcThresh
2-112
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
2.2.26.17 UE Measurement Configuration In System Information Block (SysMC)

Original Pa-
Related Ob-
Related Parame-
rameter
ject
ter
CId
utranCell
CId
The field value in this table must exist in the association table
IntraMeasCf-
Intra
IntraMeasCfgNo
The field value in this table must exist in the association table
UeTrv
UeTrvMCfgNo
When TrfVolMSInfoPre value is True, the TrfVolMeasCfgNo
Measobj
value in this table must exist in the association table and the
gNo
TrfVolMSInfoPre
TrfVolMeasC-
Measobj value in the association table must be 2 (RACH)
fgNo
FDDIn-
utranRelation
CId
terFMeasInd
If there is no inter-frequency adjacent cell of this cell in UtranRelation,the value of FDDInterFMeasInd must be 1(False)
utranCell
UUARFCN
DUARFCN
InterRatMInd-
externalU-
UUARFCN
tranCell
DUARFCN
gsmRelation
CId
Pre
IntraMSysIn-
If there is no adjacent GSM cell of this cell in gsmRelation, the

value of InterRatMIndPre must be 1(False)
SysMC
foPre
IntraMeasId
IntraMSysInfoPre value is TRUE, then the associated field is
IntraMeasCfgNo
valid
DchRptInfoPre
IntraRachRptQPre
RachMaxRptCelPre
IntraMSysIn-
SysMC
foPre
OTDRptInd
IntraMSysInfoPre and IntraRachRptQPre value are all TRUE,
RptQuan
then the associated field is valid
RachMaxRptCell
IntraMSysInfoPre and RachMaxRptCelPre value are all
IntraRachRptQPre
IntraMSysIn-
SysMC
foPre
TRUE, then the associated field is valid
RachMaxRptCelPre
TrfVolMSInfo-
SysMC
Pre
TVMeasId
TrfVolMSInfoPre value is TRUE, then the associated field is
TrfVolMeasCfgNo
valid
IntraMeasId
SysMC
TVMeasId
the two fields values can not be the same in one record
Sib11orSib12
null
null
There must be one record that Sib11orSib12 equals to

0(SIB11) for each cell
2-113
SJ-20100603155704-001|2011-04-09(R2.2)
2.2.26.18 Balance Information (plBal)
2-114
SJ-20100603155704-001|2011-04-09(R2.2)
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
Related Object
Related Parameter
CId
utranCell
CId
Before the record of plBal with the Cell is created, It must be ensured that there exists the
UlLdBalPwrSwch
plBal
ExtraCDeltaTru
When the value of UlLdBalPwrSwch is 0(Closed), related parameters are invalid
UlLdThdCs
UlLdThdCs4G
UlLdThdR99Ps
UlLdThdHse4U
UlLdBalPwrWeight
DlLdBalPwrSwch
plBal
ExtraCDeltaTrd
When the value of DlLdBalPwrSwch is 0(Closed), related parameters are invalid
DlPwrThdCs4G
DlLdBalPwrWeight
2-115
DlPwrThdCs
DlPwrThdR99Ps
DlPwrThdHsd
LdBalCdSwch
plBal
LdBalCdWeight
When the value of LdBalCdSwch is 0(Closed), related parameters are invalid
DlCdLdNeedBal2U
ExtraCDeltaCdTrd
utranCell
HspaSptMeth
When HspaSptMeth takes value "0: not support HSUPA and HSDPA(Not Support HSUPA
and HSDPA)", then LdBalHsSwch is invalid
LdBalHsSwch
plBal
ExtraCDeltaHsTrd
When LdBalHsSwch is 0, ExtraCDeltaHsTrd and DlLdBalHsWeight ate invalid
DlLdBalHsWeight
DlLdHsThdHsd
HspaPluBalCapPri
plBal
HspaPluBalCapPri
The value of HspaPluBalCapPri[x] is unique
HspaPlusCapInd
plBal
HspaPlusCapInd
The value of HspaPlusCapInd [x] is unique
LdBalHsSwch
Related Object
Related Parameter
HspaPluBalCapPri
plBal
RabHspaPluBalSw
When RncMimo64QamInd is not supportor CelMimo64QamInd in this cell is not
HoldHspaPluBalSw
support:
If RabHspaPluBalSw[0], RabHspaPluBalSw[2] and RabHspaPluBalSw[4] are all 1(open)it
must satisfy the conditionHspaPluBalCapPri[0]>HspaPluBalCapPri[2]>HspaPluBalCapPri[4]
If HoldHspaPluBalSw[0], HoldHspaPluBalSw [2] and HoldHspaPluBalSw [4] are all
1(open)
And if one of the conditions above is satisfied, then HspaPluBalCapPri[0]>
HspaPluBalCapPri[2]>HspaPluBalCapPri[4]
HspaPluBalCapPri
Hspa
RncMimo64QamInd
utranCell
CelMimo64QamInd
plBal
RabHspaPluBalSw
When RncMimo64QamInd is not supportor CelMimo64QamInd in this cell is not

support:
If RabHspaPluBalSw[2] and RabHspaPluBalSw[4] are all 1(open), HspaPluBalCap-
2-116
HoldHspaPluBalSw
Pri[2]must be more than HspaPluBalCapPri[4]

If HoldHspaPluBalSw[2] and HoldHspaPluBalSw [4] are all 1(open), And if one of
the conditions above is satisfied, then HspaPluBalCapPri[2] must be more than
HspaPluBalCapPri[4]
SJ-20100603155704-001|2011-04-09(R2.2)
Original Parameter
2.2.27 Traffic-Related Power Control (TrfPc)

Original Pa-
Related
Ob-
Related Parame-
rameter
ject
ter
TrfPcIndex
utranCell
TrfPcIndex
The related field in utranCell must exist in this table
SrvType
SubSrv
SrvType
There must be a record with corresponding SrvType in

SubSrv
SrvType
TrfPc
UlIlPcAlg
Only when the value of SrvType is even, related parameters
UlOlPcSwitch
are valid
OlPCPrioSwitch
OLPCUpdatePrd
OlPcAlg
UlSirTargUpStep
UlSirTargDnStep
UlOlPcQESwitch
UlOlPcQESwchNorm
UlOlPcQESwchSil
SwchAdaptiveStep
MaxSirTargDnStep
BerErrorTbThresh
BerTbThresh
BerTargDnStep
BerTargUpStep
SrvType
TrfPc
TpcDlStep
Only when the value of SrvType is odd, related parameters

are valid
SrvType
TrfPc
TpcStepSize
UlIlPcAlg
Only when the value of SrvType is even, related parameter

is valid
And when the value of UlIlPcAlg is 1(Algorithm 1), the value
range of TpcStepSize is [0, 1](correspongding to [1, 2]dB)
when the value of UlIlPcAlg is 2(Algorithm 2), the value of
TpcStepSize must 0(1dB)
MaxSir-
TrfPc
UlSirTargDnStep
UlSirTargDnStep< MaxSirTargDnStep
TargDnStep
2-117
SJ-20100603155704-001|2011-04-09(R2.2)
2.2.28 NodeB Common Measurement

2.2.28.1 NodeB Common Measurement Configuration Information(Nbcom)
Original
Related
Related
Parameter
Object
rameter
NbCM-
CNbCom
NbCPrdRtwp
CfgNo
Pa-
The related field in CNbCom must exist in this table
NbCPrdTcp
NbCPrdTUGps
NbCModTUGps
NbCPrdHrp
NbCPrdNHTcp
NbCPrdRSEPS
NbCM-
NbCom
NbCMCfgNote
CfgNo
NbCMCfgNote
There is at least one record correspond to every value

of the related parameter
NbCom
ComMeasType
When NbCMCfgNote is 0(Period Report Parameters
RptType
for RTWP), ComMeasType must be 0(Received total

wide band power), and RptType must be 2Periodic
When NbCMCfgNote is 1( Period Report Parameters
for TCP), ComMeasType must be 1(Transmitted
Carrier Power), and RptType must be 2Periodic
When NbCMCfgNote is 2(Period NodeB
Common Measurement Report Parameters For
TUTRAN-GPS), ComMeasType must be 6(UTRAN
GPS Timing of Cell Frames for UE Positioning), and
RptType must be 2Periodic
When NbCMCfgNote is 3(On Modification NodeB
Common Measurement Report Parameters For
TUTRAN-GPS), ComMeasType must be 6(UTRAN
GPS Timing of Cell Frames for UE Positioning), and
RptType must be 9(On Modification)
2-118
SJ-20100603155704-001|2011-04-09(R2.2)
Original
Related
Related
Parameter
Object
rameter
Pa-
When NbCMCfgNote is 54(Period Report Parameters

for HS-DSCH Required Power), ComMeasType must
be 9(HS-DSCH Required Power), and RptType must
be 2(Periodic)
When NbCMCfgNote is 65( Period Report Parameters
for NotusedHS-DSCH_TCP), ComMeasType must be
8(Transmitted carrier power of all codes not used for
HS-PDSCH or HS-SCCH transmission), and RptType
must be 2(Periodic)
When NbCMCfgNote is 106(Period NodeB Common
Measurement Report Parameters for Received
Scheduled E-DCH Power Share), ComMeasType
must be 20(Received Scheduled E-DCH Power
Share), and RptType must be 2(Periodic)
Com-
NbCom
MeasObjType
MeasType
When ComMeasType is RTWP or TCP or

TUTRAN-GPS or HRP, the related field must be cell
When ComMeasType is APP, the related field must
be RACH
RptType
NbCom
RptPrdUnit
Only when it is Periodic, the related field is valid
RptPrd
RptType
NbCom
OnModChang-
When ComMeasType is UTRAN GPS Timing of Cell
Com-
Time
Frames for UE Positioning and RptType is On Modifi-
MeasType
OnMod-
cation, the related field is valid
DeviTime
Com-
NbCom
GpsMeasAcc-
When ComMeasType is UTRAN GPS Timing of Cell
Class
Frames for UE Positioning, the related field is valid
CNbCom
NULL
The reporting period more than or equals 100 times
Rach
TfsIndex
Tfs
TTI
MeasType
NbCMCfgNo
of the maximum TTI of all the RACH in cell
RptPrd
RptPrd>=100*MaxTTIAll the RACH
2.2.29 NodeB Dedicated Measurement

2.2.29.1 NodeB Dedicated Measurement Configuration Information(NbDed)
Original
Related
Related
Parameter
Object
rameter
NbDMCfg-
NbDed
DedMeasType
When NbDMCfgNote is 0(Period Report Parameters
RptType
for TCP in Power Balance ), DedMeasType must be
Note
Pa-
2-119
SJ-20100603155704-001|2011-04-09(R2.2)
Original
Related
Related
Parameter
Object
rameter
Pa-
2(TCP), and RptType must be 2(Periodic)

for TCP in AMR or DASF-PS), DedMeasType must
be 2(TCP), and RptType must be 2(Periodic)
When NbDMCfgNote is 2(Event A Report Parameters
for TCP in DASF-PS ), DedMeasType must be
2(TCP), and RptType must be 3(Event A)
When NbDMCfgNote is 3(Event B Report Parameters
for TCP in DASF-PS ), DedMeasType must be
2(TCP), and RptType must be 4(Event B)
for RTT in LCS), DedMeasType must be 5(RTT), and
RptType must be 2(Periodic)
When NbDMCfgNote is 5(Event E Report Parameters
for SIR Error in Threshold Power Control),
DedMeasType must be 1(SIR Error), and RptType
must be 7(Event E)
When NbDMCfgNote is 6(Event F Report Parameters
for SIR Error in Threshold Power Control),
DedMeasType must be 1(SIR Error), and RptType
must be 8(Event F)
for TCP in AMR), DedMeasType must be 2(TCP),
and RptType must be 3(Event A)
When NbDMCfgNote is 8(Event B Report Parameters
for TCP in AMR), DedMeasType must be 2(TCP),
and RptType must be 4(Event B)
for TCP in Handover Control), DedMeasType must
be 2(TCP), and RptType must be 3(Event A)
When NbDMCfgNote is 10(Event B Report
Parameters for TCP in Handover Control),
DedMeasType must be 2(TCP), and RptType must
be 4(Event B)
RptType
NbDed
EvtEfSirEThrd1
When RptType is E/F, and DedMeasType is SIR ERROR, the related field is valid
DedMeasType
RptType
NbDed
EvtAbTcpThrd[]
DedMeasT-
When RptType is A/B, and DedMeasType is TCP, the

related field is valid
ype
2-120
SJ-20100603155704-001|2011-04-09(R2.2)
Original
Related
Related
Parameter
Object
rameter
Pa-
RptType
NbDed
EvtEfSirEThrd2
DedMeasT-
When RptType is E/F, and DedMeasType is SIR ERROR, the related field is valid
ype
RptType
NbDed
EvtAbcdefTime
When RptType is A/B/C/D/E/F, the related field is valid
RptType
NbDed
RptPrdUnit
When RptType is Periodic or E/F, the related field is
RptPrd
valid
NbDed
NULL
DlRateLevel [0]< DlRateLevel [1]
NbDed
DlRateLevel[]
When NbDMCfgNote is 2 or 3, DlRateLevel[2] is valid
DlRateLevel []
NbDMCfgNote
2.2.30 UE Traffic Volume Measurement

2.2.30.1 UE Traffic Volume Measurement Configuration (UeTrv)
Original
Related
Related
Parameter
Object
Parameter
UeTrvM-
CUeTrv
DrbcDchUeEvt
Before the record of UeTrv is deleted, it must be
CfgNo (Tar-
DrbcDchUp
ensured that there is no CUeTrvs record which
get Index)
Dr-
quotes the UeTrvMCfgNo. Otherwise, this record with
bcRachUeEvt
the UeTrvMCfgNo in UeTrv is not allowed to delete
DrbcFachUp
DrbcSHsUp
DrbcIBHsUp
DrbcEDchUpThpt
(Source Index)
ETtiUpThpt
UeTrvM-
SysMC
TrfVolMSInfo-
In the association table, the associated field
CfgNo
Pre
TrfVolMSInfoPre value is True, then the associated
Measobj
Tr-
field in the association table TrfVolMeasCfgNo must
fVolMeasCfgNo
exist in this table , and the Measobj field value

recorded in this table must be 2(RACH)
2-121
SJ-20100603155704-001|2011-04-09(R2.2)
Original
Related
Related
Parameter
Object
Parameter
UeTrvM-
UeTrv
UeTrvMCfg-
has at least one matching record for any value of the
Note
associated field
Measobj
The following limits apply to the UeTrvMCfgNote and
RptCrt
Measobj, RptCrt values:
CfgNo
UeTrvMCfgNote
UeTrv
When the UeTrvMCfgNote value is 0(UE Traffic

volume Period Measurement Configuration Number
for DCH), the Measobj value must be 1(DCH), and the
RptCrt value must be 2(Periodical reporting criteria)
volume Event Measurement Configuration Number
for DCH), the Measobj value must be 1(DCH), RptCrt
value must be 1(UE traffic volume measurement
reporting criteria)
When the UeTrvMCfgNote value is 2(UP Traffic
volume Measurement Configuration Number for
DCH), the Measobj value must be 1(DCH), and
the RptCrt value must be 1(UE traffic volume
measurement reporting criteria)
When the UeTrvMCfgNote value is 3( UE Traffic
volume Period Measurement Configuration Number
for RACH), the Measobj value must be 2(RACH),
and the RptCrt value must be 2(Periodical reporting
criteria)
volume Event Measurement Configuration Number
for RACH), the Measobj value must be 2(RACH),
and the RptCrt value must be 1(UE traffic volume
FACH), the Measobj value must be 51(FACH), RptCrt
value must be 1(UE traffic volume measurement
reporting criteria)
Streaming Class on HS-DSCH), 7(UP Traffic volume
Measurement Configuration Number for Interactive
and Background Class on HS-DSCH), the Measobj
2-122
SJ-20100603155704-001|2011-04-09(R2.2)
Original
Related
Related
Parameter
Object
Parameter
value must be 52(HS-DSCH), RptCrt value must be

1(UE traffic volume measurement reporting criteria)
When the UeTrvMCfgNote value is 9(UP Thruput
Event Measurement Configuration Number for
E-DCH), Measobj value must be 53(E-DCH), and
the RptCrt value must be 1(UE traffic volume
When the UeTrvMCfgNote value is 10(E-DCH UP
Throughput Measurement Configuration Number for
E-TTI Switching), Measobj value must be 53(E-DCH),
and the RptCrt value must be 1(Event Reporting
Criteria)
2-123
SJ-20100603155704-001|2011-04-09(R2.2)
Original
Related
Related
Parameter
Object
Parameter
MeasQuan-
UeTrv
AverageTime
tity
RptCrt
RptCrt
value is 1(RLC buffer payload), then the associated

field is invalid
UeTrv
UeTrv
PrdRptAmount
RptCrt value is 2 (periodical report), then the
PrdRptInterval
associated field is valid
MeasEvtNum
RptCrt value is 1 (event report), then the associated
MeaEvtId[i]
field is valid
TrigTime[i]
PendingTime[i]
TxInterCfgPre[i]
RptCrt
UeTrv
RptThres[i]
Only when RptCrt value is 1(event report), then the

RptRl-
UeTrv
MeasQuantity
MeasQuantity value is 1(RLC buffer payload), then
cBufInd
RptRlcBufInd must be True; When it is 2(Average
RptRl-
RLC buffer payload), RptRlcAveInd must be True;
cAveInd
When it is 3(Variance of RLC buffer payload),
RptRl-
RptRlcVarInd must be True
cVarInd
RptCrt
UeTrv
TxInterruption[i]
Only when RptCrt value is 1(event report) and the
TxInterCfg-
TxInterCfgPre value is TRUE, then the associated
Pre[i]
field is valid
RptCrt
UeTrv
RptThres0
Only when RptCrt value is 1(event report), then the
RptThres1
RptThres2
RptThres3
RptThres4
RptThres5
RptThres6
ThoughThres
2-124
SJ-20100603155704-001|2011-04-09(R2.2)
Original
Related
Related
Parameter
Object
Parameter
Measobj
UeTrv
RptThres0
Only when Measobj is 1(DCH), the associated field
RptThres1
is an valid field ; when Measobj is other value, the
RptThres2
associated field is an invalid field
RptThres3
RptThres4
RptThres5
RptThres6
Measobj
UeTrv
RptThres
Measobj is 1(DCH), the associated field is an invalid

field ; Only when when Measobj is other value, the
associated field is an valid field
Measobj
UeTrv
ThoughThres
Only when Measobj is 53(E-DCH), then the

associated field is valid; when Measobj is other value,
the associated field is an invalid field
2.2.30.2 UE Traffic Volume Measurement Configuration Information in a Cell (CUeTrv)

Original Pa-
Related
rameter
ject
Ob-
Related Parameter
CId
utranCell
CId
DrbcD-
UeTrv
UeTrvMCfgNo
The field in this table must exist in UeTrv
chUePrd
DrbcDchUeEvt
DrbcDchUp
DrbcRachUePrd
DrbcRachUeEvt
DrbcFachUp
DrbcSHsUp
2-125
SJ-20100603155704-001|2011-04-09(R2.2)
Original Pa-
Related
rameter
ject
Ob-
Related Parameter
UeTrv
UeTrvMCfgNote
DrbcIBHsUp
ETtiUpThpt
DrbcEDchUpThpt
DrbcDchUePrd
the associated field value in the association table must be

0(UE Traffic volume Period Measurement Configuration Number for DCH )
DrbcD-
UeTrv
chUeEvt
UeTrvMCfgNo
There must be a record in the UeTrv corresponding to
(Target Index)
DrbcDchUeEvt
UeTrvMCfgNo
(Target Index)
DrbcDchUp
UeTrvMCfgNote
UE Traffic volume Period Measurement Cofiguration Number
(Source
Index)
DrbcDchUp
UeTrv
(Source
Index)
DrbcRachUe-
UeTrv
Prd
Dr-
for RACH
UeTrv
bcRachUeEvt
UeTrvMCfgNo
(Target Index)
DrbcRachUeEvt
(Source
Index)
DrbcFachUp
UeTrv
(Source
UeTrvMCfgNo
(Target Index)
DrbcFachUp
UeTrvMCfgNo
(Target Index)
DrbcSHsUp
UeTrvMCfgNo
(Target Index)
DrbcIBHsUp
UeTrvMCfgNo
(Target Index)
DrbcEDchUpThpt
UeTrvMCfgNote
the associated field in the association table value must be
Index)
DrbcSHsUp
UeTrv
(Source
Index)
DrbcIBHsUp
UeTrv
(Source
Index)
DrbcED-
UeTrv
chUpThpt
(Source
Index)
ETtiUpThpt
UeTrv
10(UP Throughput Event Measurement Configuration Number for E-TTI Switching)
2-126
SJ-20100603155704-001|2011-04-09(R2.2)
2.2.31 GPS Global Configuration Information (GpsCfg)

Original Pa-
Related Ob-
Related Parame-
rameter
ject
ter
GpsInfoRoot
GpsCfg
GpsCardType
Only when the value of GpsInfoRoot is 0(Self), GpsCardType

is valid
2.2.32 Transport Format Combination Set of SCCPCH (DlTfcs)

Original Pa-
Related Ob-
Related Parame-
rameter
ject
ter
TfcsIndex
Sccpch
TfcsIndex
The related field in Sccpch must exist in this table
2.2.33 Transport Format Combination Set of PRACH (UlTfcs)

Original
Related
Related
Parameter
Object
Parameter
TfcsIndex
Prach
TfcsIndex
The related field in Prach must in this table
BetaC[]
UlTfcs
BetaD[]
Either BetaC[i] or BetaD[i] must take the value of 15.(i=[1,

CtfcNum])
2.2.34 Transport Format Combination Set (Tfs)

Original Pa-
Related
rameter
ject
Ob-
Related Parameter
TfsIndex
Rach
TfsIndex
The related field in Related Object must exist in this table
CodingRate
When ChType takes the value of 2(PCH) or 0(RACH),
Pch
Fach
CMbms
ChType
Tfs
CodingRate can only take the vaue of 0(Convolutional 1/2)

ChType
Tfs
RlcSize[32]
When ChType takes the value of 1(FACH) or 0(RACH),

RlcSize[i] must take the value of times of 8.( i=[1, TfNum])
ChType
Tfs
TTI
When ChType takes the value of 0(RACH), TTI can only

takes the value of 0(10ms) or 1(20ms)
ChType
Tfs
TfNum
When ChType takes the value of 1(FACH), RlcSize[i] can
RlcSize[32]
take at most two values, and RlcSize[i] >=20. If there are

two RlcSize, the difference of these two RlcSize must be
16. ( i=[1, TfNum])
2-127
SJ-20100603155704-001|2011-04-09(R2.2)
2.2.35 User Authorized PLMN+SNAC Information (rncPnSnac)

Original Pa-
Related Ob-
Related Parame-
rameter
ject
ter
MCC
rncPnSnac
SMCC
There are at most 10 SMCC+ SMNC+SNAC for these
MNC
SMNC
records that have same MCC+MNC+ ExtInfoDgtNum+
ExtInfoDgt-
SNAC
ExtInfo[i].(i=[1, ExtInfoDgtNum])
Num
ExtInfo[10]
2.2.36 LAC and SNAC Information (rncLcSnac)

Original Pa-
Related Ob-
Related Parame-
rameter
ject
ter
MCC+MNC+
rncLcSnac
SNAC
LAC
MCC+MNC+
There are at most 4 SNAC that same MCC+ MNC+ LAC can
belong to
rncLcSnac
LAC
SNAC
There are at most 10 LAC that same MCC+ MNC+ SNAC

can belong to
2.2.37 NE Information Configuration (rncNeInfo)

Original Pa-
Related Ob-
Related Parame-
rameter
ject
ter
ANI
R_ATMOF-
ANI
FICE
Officeld
R_OFFICE
The lower layer bearer is ATM, then the field in this table must
exist in the association table
Officeld
The NE type is CN/RNC adjacent NE. The lower layer bearer

is IP, the field in this table must exist in the association table
officeld
rncNeInfo
ANI
When filed OfficeId is valid, ANI must be consistent with OfficeId
Neld
rncNeInfo
NeType
NodeB is connected through BME, then RNC and NodeB's

NeId on BME must be consistent
2-128
SJ-20100603155704-001|2011-04-09(R2.2)
Original Pa-
Related Ob-
Related Parame-
rameter
ject
ter
ProfileIndex
QoSProfile
ProfileIndex
When the ProfileIndex field in this table is valid, it must exist
R_IubBrsInfo
TbType
in the association table
IubSrvBrsType
If the adjacent NE is RNC and the IurSrvBrsType is IP, then

the TbType recorded in R_IubBrsInfotable must all be IP,
likewisely
if IurSrvBrsType is ATM, then the TbType recorded in the
association table must are all be ATM
If the adjacnet NE is NodeB and the IubSrvBrsType is IP, then
the TbType recorded in the association table must all be IP
Likewisely, if IubSrvBrsType is ATM, then the TbType
recorded in the association table must are all be ATM
CsReDelay-
rncNeInfo
RncFeatSwitch
Timer
If the Bit10 of RncFeatSwitch field is 0 (The switch is irrelevant

to UEs without CS services), CsReDelayTimer is invalid. If the
Bit10 of RncFeatSwitch field is 1 (The switch is irrelevant to
UEs with CS services), CsReDelayTimer cannot be 0
PsReDelay-
rncNeInfo
RncFeatSwitch
Timer
If the Bit11 of RncFeatSwitch field is 0 (The switch is irrelevant

to UEs without PS services), PsReDelayTimer is invalid. If the
Bit11 of RncFeatSwitch field is 1 (The switch is irrelevant to
UEs with PS services), PsReDelayTimer cannot be 0
NeType
rncFunction
SharedNetMode
If the related filed is 0XFF (no network sharing), PlmnNum
PlmnNum
should be 1 in all the exchange records for MSCServer
MCC[]
(NeType Bit9=1) and SGSN (NeType Bit12=1) in table
MNC[]
R5NeInfo. CC[], MNC[] and NEID[] should be unique
NeId[]
If SharedNetMode is 0XFF (no network sharing), the

foreground protects the two PLMN configurations from being
mismatched. Currently the PLMN for NE cannot be modified
through Network Management Server
2-129
SJ-20100603155704-001|2011-04-09(R2.2)
This page intentionally left blank.
2-130
SJ-20100603155704-001|2011-04-09(R2.2)
Chapter 3
Operation in Planning Radio

Parameters
Table of Contents
Overview ....................................................................................................................3-2
rncFucntion ................................................................................................................3-3
rncBRnc .....................................................................................................................3-3
nodeB ........................................................................................................................3-3
ueCnst .......................................................................................................................3-4
cnInfo .........................................................................................................................3-4
iuCnst.........................................................................................................................3-4
rcpSc..........................................................................................................................3-4
trfCtl ...........................................................................................................................3-5
drbc............................................................................................................................3-5
GloAc .........................................................................................................................3-5
Hspa ..........................................................................................................................3-5
GbrRes ......................................................................................................................3-6
Mbms .........................................................................................................................3-6
CfnOffset....................................................................................................................3-6
QosSeg ......................................................................................................................3-6
BasPri ........................................................................................................................3-7
SchPri ........................................................................................................................3-7
AppPri ........................................................................................................................3-8
BPriAc........................................................................................................................3-8
Intra ...........................................................................................................................3-9
CIntra .......................................................................................................................3-10
Inter .........................................................................................................................3-10
CInter .......................................................................................................................3-11
Rat ...........................................................................................................................3-11
CRat.........................................................................................................................3-12
SubSrv .....................................................................................................................3-12
EdchRc ....................................................................................................................3-13
rncDtxDrx .................................................................................................................3-13
SrvPhy .....................................................................................................................3-13
DivPc .......................................................................................................................3-14
externalUtranCell .....................................................................................................3-14
externalGsmCell.......................................................................................................3-15
utranCell ..................................................................................................................3-15
3-1
SJ-20100603155704-001|2011-04-09(R2.2)
utranRelation............................................................................................................3-16
gsmRelation .............................................................................................................3-16
PriSel .......................................................................................................................3-17
CelSel ......................................................................................................................3-17
CHspa......................................................................................................................3-17
CMbms ....................................................................................................................3-18
MbmsSa...................................................................................................................3-18
EFach ......................................................................................................................3-18
CelMPO ...................................................................................................................3-19
Psch.........................................................................................................................3-19
Ssch.........................................................................................................................3-19
Pcpich ......................................................................................................................3-20
Pccpch .....................................................................................................................3-20
Scpich ......................................................................................................................3-20
Sccpch .....................................................................................................................3-21
Pich..........................................................................................................................3-22
Prach .......................................................................................................................3-22
Aich..........................................................................................................................3-23
Mich .........................................................................................................................3-23
Bch ..........................................................................................................................3-23
Fach.........................................................................................................................3-24
Pch ..........................................................................................................................3-24
Rach ........................................................................................................................3-24
PC............................................................................................................................3-25
AC............................................................................................................................3-25
LdCtrl .......................................................................................................................3-25
SysMC .....................................................................................................................3-25
plBal.........................................................................................................................3-26
TrfPc ........................................................................................................................3-26
Nbcom .....................................................................................................................3-27
NbDed......................................................................................................................3-27
UeTrv .......................................................................................................................3-27
CUeTrv.....................................................................................................................3-27
GpsCfg.....................................................................................................................3-28
DlTfcs.......................................................................................................................3-28
UlTfcs.......................................................................................................................3-29
Tfs............................................................................................................................3-29
rncPnSnac ...............................................................................................................3-30
rncLcSnac ................................................................................................................3-30
rncNeInfo .................................................................................................................3-30
3.1 Overview
This section describes operations of MOC that need special treatment.
3-2
SJ-20100603155704-001|2011-04-09(R2.2)
Chapter 3 Operation in Planning Radio Parameters
The OMCRNCID, CONFSETID, primary key, and alternative key are not allowed to be
modified in the planned data of all objects.
For the description of MOC operation is Null, fill in the data according to the restriction
relationship described in the Detailed Relationships of Radio Parameter.
Note:
In all operations of MOC, all primary key and alternatinve key must be existed.
3.2 rncFucntion
For the restriction relationship, refer to RNC Configuration Information (rncFunction).
Name
Description
Delete
The operation is not allowed. Reason: There is only one record in the table
Add
Modify
IntegrityAlg is not allowed to be modified
3.3 rncBRnc
For the restriction relationship, refer to RNC Configuration Supplement Information
(rncBRnc).
Name
Description
Delete
Add
Modify
Refer to the restriction relationship
3.4 nodeB
For the restriction relationship, refer to NodeB Configuration Information (nodeB).
Name
Description
Delete
If the Node B is not quoted by the utranCell, delete the Node B directly
If the Node B is quoted by the utranCell, delete both the record of the Node B
and records of all cells that have quoted the Node B
Add
Null
Modify
Null
3-3
SJ-20100603155704-001|2011-04-09(R2.2)
3.5 ueCnst
For the restriction relationship, refer to UE Timers and Constants Information (ueCnst).
Name
Description
Delete
Add
Modify
Null
3.6 cnInfo
For the restriction relationship, refer to CN System Information (cnInfo).
Name
Description
Delete
Null
Add
Null
Modify
Null
3.7 iuCnst
For the restriction relationship, refer to Iu Interface Timers and Constants Information
(iuCnst).
Name
Description
Delete
Add
Modify
Null
3.8 rcpSc
For the restriction relationship, refer to UL Scrambling Code Configuration Information In
RCP (rcpSc).
Name
Description
Delete
Null
Add
Null
Modify
Null
3-4
SJ-20100603155704-001|2011-04-09(R2.2)
3.9 trfCtl
For the restriction relationship, refer to FACH Traffic Control Information (trfCtl).
Name
Description
Delete
Add
Modify
Null
3.10 drbc
For the restriction relationship, refer to Dynamic Radio Bearer Control Information (drbc).
Name
Description
Delete
Add
Modify
Null
3.11 GloAc
For the restriction relationship, refer to Global Access Control (GloAc).
Name
Description
Delete
Add
Modify
Null
3.12 Hspa
For the restriction relationship, refer to Hspa Configuration Information (Hspa).
Name
Description
Delete
Add
Modify
Null
3-5
SJ-20100603155704-001|2011-04-09(R2.2)
3.13 GbrRes
For the restriction relationship, refer to Limiting HSDPA GBR Resource Consumption
Information (GbrRes).
Name
Description
Delete
Add
If this entry is quoted by the HsGBRResLimitIdx property of CHspa, it can not

be deleted before deleting the quoting relation
Modify
3.14 Mbms
For the restriction relationship, refer to MBMS Configuration Information (Mbms).
Name
Description
Delete
Add
Modify
Null
3.15 CfnOffset
Name
Description
Delete
Null
Add
Null
Modify
Null
3.16 QosSeg
For the restriction relationship, refer to Qos Configuration(QosSeg).
Name
Description
Delete
Add
3-6
SJ-20100603155704-001|2011-04-09(R2.2)
Name
Description
Modify
The ARPThresh and ARPSegNum should be modified at the same time, Make
sure that the number of ARPThresharray elements in the planning data is equal
to ARPSegNum-1.
The THPThresh and THPSegNum should be modified at the same time, Make
sure that the number of the THPThresh array elements in the planning data is
equal to THPSegNum-1
The BPThresh and BPSegNum should be modified at the same time, Make
sure that the number of the BPThresh array elements in the planning data is
equal to BPSegNum -1
If reduce the value of ARPSegNum, corresponding records of BasPri should
be delete at the same time
If increase the value of ARPSegNum, corresponding records of BasPri should
be add at the same time
If reduce the value of THPSegNum, corresponding records of BasPri should
If increase the value of THPSegNum, corresponding records of BasPri should
be add at the same time
If reduce the value of BPSegNum, corresponding records of Apppri should
If increase the value of BPSegNum, corresponding records of Apppri should be
add at the same time
If reduce the value of DlRateAdjLevNum, corresponding records of Apppri
should be delete at the same time
If increase the value of DlRateAdjLevNum, corresponding records of Apppri
should be delete at the same time
3.17 BasPri
For the restriction relationship, refer to Basic Priority Management (BasPri).
Name
Description
Delete
Modify ARPSegNum and THPSegNum of QosSeg, and delete the record of

BasPri
Add
Modify ARPSegNum and THPSegNum of QosSeg, and add the record of BasPri
Modify
Null
3.18 SchPri
For the restriction relationship, refer to Scheduling Priority Management (SchPri).
3-7
SJ-20100603155704-001|2011-04-09(R2.2)
Name
Description
Delete
If the SchPri is not quoted by the utranCell, delete the SchPri directly
If the SchPri is quoted by the utranCell, refer to steps below:
1. Modify the SchPriIndex of utranCell in planned data setting,
2. Release the quotation relationship
3. Generate the script according to the data planned in Step 1
4. Import the script into OMM for execution
5. Delete the record of the SchPri in planned data setting
6. Generate the script according to the data planned in Step 3 and import
the script into OMM for execution
Add
Null
Modify
Null
3.19 AppPri
For the restriction relationship, refer to Application Priority Configuration Information
(AppPri).
Name
Delete
Description
If the AppPri is not quoted by the utranCell,delete the record of AppPri
If the AppPri is quoted by the utranCell, refer to the steps below:
1. Modify the LdCtrlPriIndex and CgtCtlPriIndex of utranCell
2. Release quotation relationship
4. Import the OMM for execution
5. Delete the record of AppPri
the OMM for execution
Add
Null
Modify
Null
3.20 BPriAc
For the restriction relationship, refer to Access Control Related to Basic Priority (BPriAc).
3-8
SJ-20100603155704-001|2011-04-09(R2.2)
Name
Description
Delete
If the local object is not quoted by the utranCell, delete the BPriAc directly
If the local object is quoted by the utranCell, refer to the steps below:
1. Modify the BPriAcIndex data of utranCell in planned data setting
5. Delete the record of BpriAc in planned data setting
Add
Null
Modify
Null
3.21 Intra
For the restriction relationship, refer to UE Intra-frequency Measurement Configuration
(Intra).
Name
Description
Delete
If the Intra is not quoted by CIntra, SysMC, or Inter objects, delete the record of
the Intra directly
If the Intra is quoted by CIntra, SysMC, or Inter objects, refer to steps below:
1. Modify the data of the CIntra that has quoted the Intra, the data of the
SysMC that has quoted the Intra, and the data of the Inter that has quoted
the Intra in planned datasetting
4. Import the script into OMM, and execute successfully
5. Delete the record of the Intra in planned datasetting
Add
Null
Modify
If quoted by the CIntra, SysMC, or Inter objects, the attribute of the

IntraMeasCfgNote, MeasQuantity and RptCrt can not be modified directly.
Please refer to steps below:
1. Modify tthe data of the CIntra that has quoted the Intra, the data of the
SysMC and the data of the Inter in planned datasetting
3. Generate the script according to the data planned in Step 1 and
5. Modify the data of Intra in planned datasetting
3-9
SJ-20100603155704-001|2011-04-09(R2.2)
Name
Description
3.22 CIntra
For the restriction relationship, refer to UE Intra-frequency Measurement Relative to Traffic
Category Configuration Information (CIntra).
Name
Description
Delete
If the CIntra is not quoted by utranCell object, delete the record of the CIntra
directly
If the CIntra is quoted by the utranCell object, refer to steps below:
1. Modify the TrfCatIntraMIdx data of utranCell in planned data setting
5. Delete the record of Clntra in planned datasetting
Add
Null
Modify
Null
3.23 Inter
For the restriction relationship, refer to UE Inter-frequency Measurement Configuration
(Inter).
Name
Description
Delete
If the Inter is not quoted by the CInter object, delete the record of the Inter
directly
If the Inter is quoted by the CInter object, refer to steps below:
1. Modify the data of the CInter in planned datasetting.
5. Delete the record of the Inter in planned datasetting
Add
Null.
3-10
SJ-20100603155704-001|2011-04-09(R2.2)
Name
Description
Modify
If quoted by the CInter object, the attribute of the InterMeasCfgNote,

MeasQuantity and RptCrt can not be modified directly, please refer to the
steps below:
1. Modify the data of CInter that has quoted Inter in planned datasetting
2.
Release the quotation relationship

4.
Import the script into OMM for execution
5. Modify the data of Inter in planned datasetting

3.24 CInter
For the restriction relationship, refer to UE Inter-frequency Measurement Relative to Traffic
Category (CInter).
Name
Description
Delete
If the CInter is not quoted by the utranCell object, delete the CInter directly
If the CInter is quoted by the utranCell, refer to steps below:
1. Modify the TrfCatInterMIdx of utranCell in planned datasetting
2. release the quotation relationship
5. Delete the record of Clnter in planned datasetting
Add
Null
Modify
Null
3.25 Rat
For the restriction relationship, refer to UE Inter-Rat Measurement Configuration
Information (Rat).
3-11
SJ-20100603155704-001|2011-04-09(R2.2)
Name
Description
Delete
If the Rat is not quoted by the CRat object, delete the record of the Rat
If the Rat is quoted by the CRat object, refer to steps below:
1. Modify the data of the CRat in planned datasetting
5. Delete the record of Rat in planned datasetting
Add
Null.
Modify
If quoted by the CRat, InterRatCfgNotecan, OwOMMeasQuantity and RptCrt

can not be modified directly, refer to the steps below:
1. Modify the data of CRat that has quoted Rat in planned datasetting
3. Generate the script according to the data planned in Step 1 and
5. Modify the data of Rat in planned datasetting
3.26 CRat
For the restriction relationship, refer to UE Inter-Rat Measurement Relative to Traffic
Category (CRat).
Name
Description
Delete
If the CRat is not quoted by the utranCell, delete the record of CRat directly.
1. Modify the data of the utranCell in planned datasetting
5. Delete the record of CRat in planned datasetting
Add
Null
Modify
Null
3.27 SubSrv
or the restriction relationship, refer to Service Basic Configuration Information (SubSrv).
3-12
SJ-20100603155704-001|2011-04-09(R2.2)
Name
Description
Delete
The operation is not allowed. Reason:Only default service records are

supported in RNC
Add
The operation is not allowed. Reason:Only default service records are

supported in RNC
Modify
Direction DomainMaxBitRateTrafficClass can not be modified.Reason:They are

character parameters of SrvType and must be matched to SrvType
3.28 EdchRc
For the restriction relationship, refer to E-DCH Reference Configuration Information
(EdchRc).
Name
Description
Delete
Add
If this entry is quoted by the DtxDrxConfigIdx property of SrvPhy, it can not be

deleted before the quoting relation is deleted
Modify
3.29 rncDtxDrx
For the restriction relationship, refer to UE DTX/DRX Configuration Information
(rncDtxDrx).
Name
Description
Delete
Add
If this entry is quoted by the DtxDrxConfigIdx property of SrvPhy, it can not be

deleted before deleting the quoting relation
Modify
3.30 SrvPhy
For the restriction relationship, refer to Service Physical Layer Configuration Information
(SrvPhy).
Name
Delete
Description
The operation is not allowed. Reason: Only default service records are
supported in RNC
3-13
SJ-20100603155704-001|2011-04-09(R2.2)
Name
Description
Add
The operation is not allowed. Reason: Only default service records are
supported in RNC
Modify
3.31 DivPc
For the restriction relationship, refer to Power Control Related to Service and Diversity
Mode (DivPc).
Name
Description
Delete
If the DivPc is not quoted by the utranCell, delete the record of DivPc directly.
If the DivPc is quoted by the utranCell, refer to the steps below:
1. Modify the data of the utranCell in planned datasetting
5. Delete the record of the DivPc in planned datasetting
Add
Null
Modify
Null
3.32 externalUtranCell
For the restriction relationship, refer to External Utran Cell (externalUtranCell).
Name
Delete
Description
If the externalUtranCell is not quoted by the utranRelation, delete the record
of externalUtranCell directly
If the externalUtranCell is quoted by utranRelation, both the record of the
externalUtranCell and records of the utranRelation that have quoted the
externalUtranCell should be deleted
Add
Null
Modify
When modify DivCtrlFld or DiurCmbInd of a certain externalUtranCell, DivCtrlFld

or DiurCmbInd of all externalUtranCell that belong to same neighboring RNC
must be modified to the same value
3-14
SJ-20100603155704-001|2011-04-09(R2.2)
3.33 externalGsmCell
For the restriction relationship, refer to External Gsm Cell (externalGsmCell).
Name
Delete
Description
If the externalGsmCell is not quoted by the gsmRelation, delete the record of
the externalGsmCell directly
If the externalGsmCell is quoted by the gsmRelation, both the record of
the externalGsmCell and records of gsmRelation that have quoted the
externalGsmCell should be deleted
Add
Null
Modify
Null
3.34 utranCell
For the restriction relationship, refer to Utran Cell (utranCell).
Name
Description
Delete
If the utranCell is not quoted by the utranRelation or MbmsSa, delete records

of utranCell and records of utranRelation, GsmRelation, celSel, Psch, Ssch,
Pcpich, Scpich, Pccpch, Sccpch, Pich, Prach, Aich, Bch, Fach, Pch ,Rach,
CHsdpa, LdCtrl, Pc,PlBal, Ac, CUeTrv, SysMC, CMbms of this cell
If the utranCell is quoted by utranRelation and MbmsSa, delete all objects
and data related to this cell
1. Delete the record of utranCell and records of utranRelation, GsmRelation,
celSel, Psch, Ssch, Pcpich, Scpich, Pccpch, Sccpch, Pich, Prach, Aich,
Bch, Fach, Pch ,Rach, CHsdpa, LdCtrl, Pc,PlBal, Ac, CUeTrv, SysMC,
CMbms
2. Delete records of utranRelation that have quoted this utranCell
3. Delete records of MbmsSa that have quoted this utranCell
Note:
When the cell is deleted successfully, all records of utrancell, utranRelation,GsmRelation, celSel, Psch, Ssch, Pcpich, Scpich, Pccpch, Sccpch, Pich, Prach,
Aich,Bch, Fach, Pch, Rach, CHsdpa, LdCtrl, Pc,PlBal, Ac, CUeTrv, SysMC,
CMbms corresponding to this cell are deleted
Add
Null
3-15
SJ-20100603155704-001|2011-04-09(R2.2)
Name
Description
Modify
When modifying FreqBandInd, duarfcn, and MbmsSuptInd, if the utranCell is

quoted by the Mbmssa, refer to the steps below:
1. Modify the data of the Mbmssa in planned data setting
5. Modify the data of the utranCell in planned data setting
When modifying USEOFHCS of utranCell from 2 (used) to 1 (not used),
HCSSRVCELINFOPRE of the CelSel needs be modified into 0 (False)
3.35 utranRelation
For the restriction relationship, refer to Neighbouring Cell (utranRelation).
Name
Description
Delete
Null
Add
If (NPhyCId) of the utranRelation to be added has existed in utranCell or

externalUtranCell, add the record of utranRelation directly
If (NPhyCId) of the utranRelation to be added has not existed in the utranCell
or externalUtranCell, add the record of utranRelation and utranCell (or
externalUtranCell)
If CId of the utranRelation to be added has existed in uranCell, add the record
of utranRelation directly
If CId of the utranRelation to be added has not existed in uranCell, add the
record of utranRelation and uranCell
Modify
Null
3.36 gsmRelation
For the restriction relationship, refer to Gsm Neighbouring Cell (gsmRelation).
Name
Description
Delete
Null
3-16
SJ-20100603155704-001|2011-04-09(R2.2)
Name
Description
Add
If (NPhyGsmCId) of the gsmRelation to be added has existed in

externalGsmCell, add the record of gsmRelation directly
If (NPhyGsmCId) of the gsmRelation to be added has not existed in
externalGsmCell, add the record of gsmRelation and externalGsmCell
If CID of the gsmRelation to be added has existed in uranCell, add the record of
gsmRelation directly
If CID of the gsmRelation to be added has not existed in uranCell, add the
record of gamRelation and uranCell
Modify
Null
3.37 PriSel
For the restriction relationship, refer to Cell Frequency Reselection and Priority (PriSel).
Name
Description
Delete
Null
Add
Null
Modify
Null
3.38 CelSel
For the restriction relationship, refer to Cell Selection and Reselection (CelSel).
Name
Description
Delete
The record of SIB3ORSIB4=0(SIB3) is not allowed to be deleted
Add
If CID of the CelSel to be added has existed in uranCell, add the record of
CelSel directly
If CID of the CelSel to be added has not existed in uranCell, add the record
of CelSel and uranCell
Modify
Null
3.39 CHspa
For the restriction relationship, refer to Hspa Configuration Information In A Cell (CHspa).
Name
Description
Delete
Null
3-17
SJ-20100603155704-001|2011-04-09(R2.2)
Name
Description
Add
If CID of the CHspa to be added has existed in uranCell, add the record of
CHspa directly
If CID of the CHspa to be added has not existed in uranCell, add the record of
CHspa and uranCell
Modify
Null
3.40 CMbms
For the restriction relationship, refer to MBMS Configuration Information In A Cell
(CMbms).
Name
Description
Delete
Null
Add
If CID of the CMbms to be added has existed in uranCell, add the record of
CMbms directly
If CID of the CMbms to be added has not existed in uranCell, add the record of
CMbms and uranCell
Modify
Null
3.41 MbmsSa
For the restriction relationship, refer to UtranCell Information in MBMS Service Area
(MbmsSa).
Name
Description
Delete
Null
Add
Null
Modify
Null
3.42 EFach
Name
Discription
Delete
The utranCell object must be deleted when this object is deleted
Add
If utranCell corresponds to cid is already exist, then add this object. Or utranCell
must be added first
Modify
Null
3-18
SJ-20100603155704-001|2011-04-09(R2.2)
3.43 CelMPO
Name
Discription
Delete
Null
Add
If utranCell corresponds to cid is already exist, then add this object. Or utranCell
must be added first
Modify
Null
3.44 Psch
For the restriction relationship, refer to PSCH (Psch).
Name
Description
Delete
When deleting the Psch of a certain cell, refer to steps below:

1. Delete the record of Psch
2. Modify STTDIND=0 of Sccpch for the corresponding cell
3. Modify STTDIND=0 of Pich for the corresponding cell
4. Modify STTDIND=0 of Aich for the corresponding cell
5. Modify STTDIND=0 of Mich for the corresponding cell
Add
If CID of the Psch to be added has existed in uranCell, add the record of
Psch directly
If CID of the Psch to be added has not existed in uranCell, add the record
of Psch and uranCell
Modify
Null
3.45 Ssch
For the restriction relationship, refer to SSCH (Ssch).
Name
Description
Delete
Null
Add
If CID of the Ssch to be added has exist in uranCell, add the record of Ssch
directly
If CID of the Ssch to be added has not exist in uranCell, add the record of
Ssch and uranCell
Modify
Null
3-19
SJ-20100603155704-001|2011-04-09(R2.2)
3.46 Pcpich
For the restriction relationship, refer to PCPICH (Pcpich).
Name
Description
Delete
When deleting the Pcpich of a certain cell, refer to steps below:

1. Delete the record of the Pcpich
Add
If CID of the Pcpich to be added has existed in uranCell, add the record of
Pcpich directly
If CID of the Pcpich to be added has not existed in uranCell, add the record
of Pcpich and uranCell
Modify
Null
3.47 Pccpch
For the restriction relationship, refer to PCCPCH (Pccpch).
Name
Description
Delete
When deleting the Pcpich of a certain cell refer to steps below:

1. Delete the record of Pccpch
2. Modify STTDIND=0 of Psch for the corresponding cell
3. Modify STTDIND=0 of Pcpich for the corresponding cell
Add
If CID of Pccpch to be added has existed in uranCell, add the record of Pccpch
directly
If CID of Pccpch to be added has not existed in uranCell, add the record of
Pccpch and uranCell
Modify
Null
3.48 Scpich
For the restriction relationship, refer to SCPICH (Scpich).
Name
Description
Delete
The operation is not allowed. Reason:Scpich is not supported

3-20
SJ-20100603155704-001|2011-04-09(R2.2)
Name
Description
Add
Modify
3.49 Sccpch
For the restriction relationship, refer to SCCPCH (Sccpch).
Name
Description
Delete
If the local cell contains only one record of the SIB5ORSIB6=0/2, the record
can not be deleted
When the CPCId of Sccpch to be deleted equals to 35, refer to steps below:
1. Delete record of Sccpch
2. Delete the Mich that has quoted this Sccpch
When the CPCId of Sccpch to be deleted doesnt equals to 35, refer to steps
below:
1. As PCHInd of the Sccpch to be deleted equals to 0 (false), delete the
record of Sccpch and the record of Fach that has quoted this Sccpch
2. As PCHInd of the Sccpch to be deleted equals to 1 (true), and the value
of PichCPCId is effective:
a. Delete the record of Sccpch
b. Delete the record of Pch that has quoted the this Sccpch
c.
Delete the record of Fach that has quoted the local Sccpch
d. Delete the Pich corresponding to PichCPCId of this Sccpch
Note:
l
When PCHInd of the Sccpch to be deleted is 1(True) and the script is

executed successfully, Fach and Pch objects related to this Sccpch are
deleted, too
When CPCId of the Sccpch to be deleted equals to 35 and the script is

executed successfully, the Mich object related to this Sccpch is deleted, too
Add
If CID of the Sccpch to be added has existed in uranCell, add the record of
Sccpch directly
If CID of the Sccpch to be added has not existed in uranCell, add the record of
Sccpch and uranCell
Modify
Null
3-21
SJ-20100603155704-001|2011-04-09(R2.2)
3.50 Pich
For the restriction relationship, refer to PICH (Pich).
Name
Description
Delete
When deleting the Pich,refer to steps below:

1. Delete the record of Pich
2. Delete the record of Pch that is quoted by PchCTCId of Pich
3. Modify PichCpcId to 255 and PCHInd to 0 in the record of Sccpch that
quotes this Pich
Add
When adding the Pich, the Pch that is quoted by this Pich has existed, refer
to below:
1. Add the record of Pich
2. Modify the value PichCPCId of Sccpch that corresponding to the Pch to
equal to the value of CPCId of this Pich
When adding the Pich, the Pch that is quoted by this Pich has not existed,
refer to below:
1. Add the record of Pich
2. Add the record of Pch
3. Modify PchInd of Sccpch corresponding to the Pch to 1(true) and modify
the PichCPCId equals to Pich.CPCID
Modify
When modifying the PCHCTCID of Pich( It means to transfer the Pich from one
Sccpch to another Sccpch), modify the data below:
1. Modify the data of the Pich
2. Modify the value of PichCPCId to 255 in the record of Sccpch that quotes
this Pich
3.51 Prach
For the restriction relationship, refer to PRACH (Prach).
Name
Description
Delete
If the Prach is quoted by Aich, refer to steps below:

1. Delete the record of Aich that quotes this Prach
2. Delete the record of Prach that quotes this Prach
3. Delete the record of Prach
If the Prach is not quoted by Aich, refer to steps below:
1. Delete the record of Rach that quotes ths Prach
2. Delete the record of Prach
Add
If CID of the Prach to be added has existed in uranCell, add the record of
Prach directly
If CID of the Prach to be added has not existed in uranCell, add the record
of Prach and uranCell
3-22
SJ-20100603155704-001|2011-04-09(R2.2)
Name
Description
Modify
Null
3.52 Aich
For the restriction relationship, refer to AICH (Aich).
Name
Description
Delete
Null
Add
If the Prach that is quoted by CID+PrachCPCId of the Aich has existed, add the
record of Aich directly
If the Prach that is quoted by CID+PrachCPCId of the Aich has not existed, add
the record of Aich and Prach
Modify
Null
3.53 Mich
For the restriction relationship, refer to MICH (Mich).
Name
Description
Delete
Delete the record of Mich ,and delete the record of the Sccpch whose CPCID
is 35 at the same time
Add
If the Sccpch that is quoted by CID+SccpchCPCId of the Mich has existed,

add the record of Mich directly
If the Sccpch that is quoted by CID+SccpchCPCId of the Mich has not existed,
add the record of Aich and Sccpch
Modify
Null
3.54 Bch
For the restriction relationship, refer to BCH (Bch).
Name
Description
Delete
Null
Add
If CID of Bch to be added has existed in uranCell, add the record of Bch directly
If CID of Bch to be added has not existed in uranCell, add the record of Bch
and uranCell
Modify
Null
3-23
SJ-20100603155704-001|2011-04-09(R2.2)
3.55 Fach
For the restriction relationship, refer to FACH (Fach).
Name
Description
Delete
Null
Add
If Sccpch that is quoted by CID+SccpchCPCId of the Fach has not existed,

add the record of Fach and Sccpch
If Sccpch that is quoted by CID+SccpchCPCId of the Fach has existed, add the
record of Fach directly
Modify
Null
3.56 Pch
For the restriction relationship, refer to PCH (Pch).
Name
Description
Delete
If the Pch is quoted by Pich,refer to steps below:

1. Delete the record of Pch
2. Delete the record of Pich that quotes this Pch
3. Modify PchInd of Sccpch that is quoted by this Pch to 0(false)
Add
If the Sccpch that is quoted by this Pch has not existed, add the record of
Pch and Sccpch
If the Sccpch that is quoted by this Pch has existed, add the record of Pch and
modify the PchInd of Sccpch to 1(true)
Modify
The field SCCPCHCPCID is not allowed to be modified
3.57 Rach
For the restriction relationship, refer to RACH (Rach).
Name
Description
Delete
Null
Add
If the Prach quoted by cid+PrachCPCId has not existed, add the record of
Rach and Prach
If the Prach quoted by cid+PrachCPCId has existed, add the record of Rach
Modify
Null
3-24
SJ-20100603155704-001|2011-04-09(R2.2)
3.58 PC
For the restriction relationship, refer to Power ControlPower Control not Related to Service
(PC).
Name
Description
Delete
Null
Add
If CID of the PC to be added has existed in uranCell, add the record of PC

directly
If CID of the PC to be added has not existed in uranCell, add the record of
PC and uranCell
Modify
Null
3.59 AC
For the restriction relationship, refer to Cell-Related Access Control (AC).
Name
Description
Delete
Null
Add
If CID of the AC to be added has existed in uranCell, add the record of AC

If CID of the AC to be added has not existed in uranCell, add the record of
AC and uranCell
Modify
Null
3.60 LdCtrl
For the restriction relationship, refer to Load Control Relationship(LdCtrl).
Name
Description
Delete
Null
Add
If CID of the LdCtrl to be added has existed in uranCell, add the record of LdCtrl
If CID of the LdCtrl to be added has not existed in uranCell, add the record
of LdCtrl and uranCell
Modify
Null
3.61 SysMC
For the restriction relationship, refer to UE Measurement Configuration In System
Information Block (SysMC).
3-25
SJ-20100603155704-001|2011-04-09(R2.2)
Name
Description
Delete
The record of SIB11ORSIB12=0 can not be deleted separately and it can be

deleted only with the utranCell
Add
If CID of the SysMC to be added has existed in uranCell, add the record of
SysMC
If CID of the SysMC to be added has not existed in uranCell, add the record of
SysMC and uranCell
Modify
Null
3.62 plBal
For the restriction relationship, refer to Balance Information (plBal).
Name
Description
Delete
Null
Add
If CID of the plBal to be added has existed in uranCell, add the record of plBal
If CID of the plBal to be added has not existed in uranCell, add the record
of plBal and uranCell
Modify
Null
3.63 TrfPc
For the restriction relationship, refer to Traffic-Related Power Control (TrfPc).
Name
Delete
Description
If the TrfPc is not quoted by the utranCell, delete the record of TrfPc directly
If the TrfPc is quoted by the utranCell, refer to the steps below:
1. Modify the data of utranCell that has quoted the TrfPc in planned data
settings
2. Release the quote relationship
5. Delete the record of the TrfPc in planned data settings
Add
Null
Modify
Null
3-26
SJ-20100603155704-001|2011-04-09(R2.2)
3.64 Nbcom
Name
Discription
Delete
If this object is quoted by CNbom, then it only can be deleted after the
relationship is moved
If this object is not quoted by CNbom, it can be deleted directly
Add
Null
Modify
Null
3.65 NbDed
Name
Discription
Delete
Null
Add
Null
Modify
Null
3.66 UeTrv
For the restriction relationship, refer to UE Traffic Volume Measurement Configuration
(UeTrv).
Name
Description
Delete
The operation is not allowed

Reason: Only default UeTrv records are supported in RNC, so default
UeTrvMCfgNo can not be deleted
Add
The operation is not allowed

Only default UeTrv records are supported in RNC
Modify
Null
3.67 CUeTrv
For the restriction relationship, refer to UE Traffic Volume Measurement Configuration
Information In A Cell (CUeTrv).
Name
Description
Delete
Null
3-27
SJ-20100603155704-001|2011-04-09(R2.2)
Name
Description
Add
If CID of the CUeTrv to be added has existed in uranCell, add the record of
CUeTrv directly
If CID of the CUeTrv to be added has not existed in uranCell, add the record of
CUeTrv and uranCell
Modify
All parameters are not allowed to modify. Reason:

Only default UeTrv records are supported in RNC,so default UeTrvMCfgNo
must be quoted and can not be modified
3.68 GpsCfg
For the restriction relationship, refer to GPS Global Configuration Information (GpsCfg).
Name
Description
Delete
Add
Modify
Null
3.69 DlTfcs
For the restriction relationship, refer to Transport Format Combination Set of SCCPCH
(DlTfcs).
Name
Description
Delete
If the DlTfcs is not quoted by Sccpch, delete the record of the DlTfcs directly
If the DlTfcs is quoted by the Sccpch, refer to the steps below:
1. Modify the data of the Sccpch that has quoted the DlTfcs in planned data
settings
5. Delete the record of the DlTfcs in planned data settings
Add
Null
Modify
Null
3-28
SJ-20100603155704-001|2011-04-09(R2.2)
3.70 UlTfcs
For the restriction relationship, refer to Transport Format Combination Set of PRACH
(UlTfcs).
Name
Description
Delete
If the UlTfcs is not quoted by Prach, delete the record of the UlTfcs directly
If the UlTfcs is quoted by the Prach, refer to the steps below:
1. Modify the data of the Prach that quotes the UlTfcs in planned data
settings
5. Delete the record of the UlTfcs in planned data settings
Add
Null
Modify
Null
3.71 Tfs
For the restriction relationship, refer to Transport Format Combination Set (Tfs).
Name
Description
Delete
If the Tfs is not quoted by the Rach, Pch, Fach, or CMbms, delete the record
of the Tfs directly
If the Tfs is quoted by the Rach, Pch, Fach, or CMbms, refer to the steps below:
1. Modify the data of the Rach, Pch, Fach, and CMbms that have quoted
the Tfs in planned data settings
5. Delete the record of the Tfs in planned data settings
Add
Null.
3-29
SJ-20100603155704-001|2011-04-09(R2.2)
Name
Description
Modify
If the Tfs is not quoted by the Rach, Pch, Fach, and CMbms, modify the data
of the Tfs directly
If the Tfs is quoted by the Rach, Pch, Fach, or CMbms, refer to the steps below
to modify the filed CHTYPE:
1. Modify the data of the Rach, Pch, Fach, and CMbms that have quoted
the Tfs in planned data settings
5. Modify the data of the Tfs in planned data settings
3.72 rncPnSnac
For the restriction relationship, refer to User Authorized PLMN+SNAC Information
(rncPnSnac).
Name
Description
Delete
Null
Add
Null
Modify
The operation is not allowed. Reason: Every parameter is an integral part

of the complete primary keys
3.73 rncLcSnac
For the restriction relationship, refer to LAC and SNAC Information (rncLcSnac).
Name
Description
Delete
Null
Add
Null
Modify
The operation is not allowed. Reason: Every parameter is an integral part

of the complete primary keys
3.74 rncNeInfo
For the restriction relationship, refer to NE Information Configuration (rncNeInfo).
3-30
SJ-20100603155704-001|2011-04-09(R2.2)
Name
Description
Delete
Null
Add
Null
Modify
Null
3-31
SJ-20100603155704-001|2011-04-09(R2.2)
3-32
SJ-20100603155704-001|2011-04-09(R2.2)
Appendix A
Searching Methods of Radio

Parameters
Table of Contents
Intra-frequency Measurement Parameters.............................................................. A-1
Inter-frequency Measurement Parameters.............................................................. A-2
Inter-RAT Measurement Parameters ...................................................................... A-2
Power Control Parameters Related to Service and Diversity Mode ......................... A-3
Power Control Parameters Related to Service ........................................................ A-8
Scheduling Priority Parameters............................................................................... A-9
Congestion Control Priority Parameters .................................................................. A-9
Load Control Priority Parameters............................................................................ A-9
UE Traffic Volume Measurement Parameters ......................................................... A-9
Access Control Parameters Related to Basic Priority ............................................ A-10
Transport Format Combination Set Parameters of SCCPCH ................................ A-10
Transport Format Combination Set Parameters of PRACH................................... A-10
Transport Format Set Parameters......................................................................... A-10
NodeB Parameters ............................................................................................... A-11
Ura Information..................................................................................................... A-11
Parameters of Other Objects ................................................................................ A-11
A.1 Intra-frequency Measurement Parameters

Search UtranCell by CIdGet Utrancell.TrfCatIntraMIdxSearch CIntra by
TrfCatIntraMIdxGet CIntra.EvtMeasEcNoSearch Intra by EvtMeasEcNoGet the
related Intra-frequency measurement parameters.
TrfCatIntraMIdxGet CIntra. EvtMeasRSCPSearch Intra by EvtMeasRSCPGet the
TrfCatIntraMIdxGet CIntra.PrdMeasEcNoSearch Intra by PrdMeasEcNoGet the
A-1
SJ-20100603155704-001|2011-04-09(R2.2)

TrfCatIntraMIdxGet CIntra.PrdMeasRSCPSearch Intra by PrdMeasRSCPGet the
Search
UtranCell
by
CIdGet
Utrancell.TrfCatIntraMIdxSearch
CIntra
by
TrfCatIntraMIdxGet
CIntra.EvtMeasDctRSCPSearch
Intra
by
EvtMeasDctRSCPGet the related Intra-frequency measurement parameters.
A.2 Inter-frequency Measurement Parameters

Search UtranCell by CIdGet Utrancell.TrfCatRatMIdxSearch CInter by
TrfCatInterMIdxGet CInter.EvtMeasEcNoSearch Inter by EvtMeasEcNoGet the
related Inter-frequency measurement parameters.
TrfCatInterMIdxGet CInter. EvtMeasRSCPSearch Inter by EvtMeasRSCPGet the
TrfCatInterMIdxGet CInter.PrdMeasEcNoSearch Inter by PrdMeasEcNoGet the
TrfCatInterMIdxGet CInter.PrdMeasRSCPSearch Inter by PrdMeasRSCPGet the
A.3 Inter-RAT Measurement Parameters

Search UtranCell by CIdGet Utrancell.TrfCatRatMIdxSearch CRat by
TrfCatRatMIdxGet CRat.EvtMeasEcNoSearch Rat by EvtMeasEcNoGet the
related Inter-RAT measurement parameters.
TrfCatRatMIdxGet CRat. EvtMeasRSCPSearch Rat by EvtMeasRSCPGet the
TrfCatRatMIdxGet CRat.PrdMeasEcNoSearch Rat by PrdMeasEcNoGet the
TrfCatRatMIdxGet CRat.PrdMeasRSCPSearch Rat by PrdMeasRSCPGet the
A-2
SJ-20100603155704-001|2011-04-09(R2.2)
Appendix A Searching Methods of Radio Parameters
A.4 Power Control Parameters Related to Service and

Diversity Mode
Search UtranCell by CIdGet Utrancell.DivPcIndexSearch DivPc by DivPcIndexGet
a set of power control parameters related to service and diversity mode.
The complete primary key of DivPc is consisted of DivPcIndex + SrvType + TxDivMod.
A set of power control parameters related to service and diversity mode should include
records of all sub-services in SubSrv. Sub-Service information is shown as Table A-1
Table A-1 Sub-Service information
Sub-Service
Traffic Class
Maximum Bit Rate
Conversational (no meaning for this
UL 3.4kbps Signaling(AM)
service)
1
DL 3.4kbps Signaling(AM)
service)
2
service)
3
service)
4
service)
5
service)
7
DL 1.5kbps sub-service used by
service)
F-DPCH
10
Conversational
UL AMR 6.60~23.85kbps
11
Conversational
DL WAMR 6.60~23.85kbps
20
Conversational
UL 64kbps(PS Conversational Video)
21
Conversational
DL 64kbps(PS Conversational Video)
22
Conversational
UL 38.8kbps(PS Conversational)
23
Conversational
DL 38.8kbps(PS Conversational)
24
Conversational
UL 30.8kbps(PS Conversational)
25
Conversational
27
Conversational
28
Conversational
UL NAMR4.75~12.2kbps
29
Conversational
DL NAMR4.75~12.2kbps
30
Streaming
UL PS 64kbps
A-3
SJ-20100603155704-001|2011-04-09(R2.2)
Sub-Service
Traffic Class
Maximum Bit Rate
31
Streaming
DL PS 64kbps
32
Streaming
UL PS 144kbps
33
Streaming
DL PS 144kbps
34
Streaming
UL PS 384kbps
35
Streaming
DL PS 384kbps
36
Streaming
UL PS 128kbps
37
Streaming
DL PS 128kbps
38
Streaming
UL PS 32kbps
39
Streaming
DL PS 32kbps
40
Interactive
UL PS 64kbps
41
Interactive
DL PS 64kbps
42
Interactive
UL PS 144kbps
43
Interactive
DL PS 144kbps
44
Interactive
UL PS 384kbps
45
Interactive
DL PS 384kbps
46
Interactive
UL PS 128kbps
47
Interactive
DL PS 128kbps
48
Interactive
UL PS 32kbps
49
Interactive
DL PS 32kbps
50
Background
UL PS 64kbps
51
Background
DL PS 64kbps
52
Background
UL PS 144kbps
53
Background
DL PS 144kbps
54
Background
UL PS 384kbps
55
Background
DL PS 384kbps
56
Background
UL PS 128kbps
57
Background
DL PS 128kbps
58
Background
UL PS 32kbps
59
Background
DL PS 32kbps
60
Conversational
UL CS 14.4kbps
61
Conversational
DL CS 14.4kbps
62
Conversational
UL CS 28.8kbps
63
Conversational
DL CS 28.8kbps
A-4
SJ-20100603155704-001|2011-04-09(R2.2)
Sub-Service
Traffic Class
Maximum Bit Rate
64
Conversational
UL CS 57.6kbps
65
Conversational
DL CS 57.6kbps
66
Conversational
UL CS 64kbps
67
Conversational
DL CS 64kbps
68
Conversational
UL CS 32kbps
69
Conversational
DL CS 32kbps
70
Streaming
UL CS 14.4kbps
71
Streaming
DL CS 14.4kbps
72
Streaming
UL CS 28.8kbps
73
Streaming
DL CS 28.8kbps
74
Streaming
UL CS 57.6kbps
75
Streaming
DL CS 57.6kbps
76
Streaming
UL CS 64kbps
77
Streaming
DL CS 64kbps
80
Streaming
UL PS 8kbps
81
Streaming
DL PS 8kbps
82
Streaming
UL PS 256kbps
83
Streaming
DL PS 256kbps
84
Streaming
UL PS 16kbps
85
Streaming
DL PS 16kbps
90
Interactive
UL PS 8kbps
91
Interactive
DL PS 8kbps
92
Interactive
UL PS 256kbps
93
Interactive
DL PS 256kbps
94
Interactive
UL PS 16kbps
95
Interactive
DL PS 16kbps
100
Background
UL PS 8kbps
101
Background
DL PS 8kbps
102
Background
UL PS 256kbps
103
Background
DL PS 256kbps
104
Background
UL PS 16kbps
105
Background
DL PS 16kbps
141
Interactive
DL PS 768kbps
A-5
SJ-20100603155704-001|2011-04-09(R2.2)
Sub-Service
Traffic Class
Maximum Bit Rate
143
Interactive
DL PS 900kbps
145
Interactive
DL PS 1.2Mbps
147
Interactive
DL PS 1.8Mbps
149
Interactive
DL PS 3.65Mbps
151
Interactive
DL PS 7.2Mbps
153
Interactive
DL PS 10.1Mbps
155
Interactive
DL PS 14.0Mbps
157
Interactive
DL PS 1.024Mbps
159
Interactive
DL PS 2.048Mbps
161
Interactive
DL PS 4.096Mbps
163
Interactive
DL PS 6.144Mbps
165
Interactive
DL PS 8.192Mbps
167
Interactive
DL PS 8.640Mbps
171
Background
DL PS 768kbps
173
Background
DL PS 900kbps
175
Background
DL PS 1.2Mbps
177
Background
DL PS 1.8Mbps
179
Background
DL PS 3.65Mbps
181
Background
DL PS 7.2Mbps
183
Background
DL PS 10.1Mbps
185
Background
DL PS 14.0Mbps
187
Background
DL PS 1.024Mbps
189
Background
DL PS 2.048Mbps
191
Background
DL PS 4.096Mbps
193
Background
DL PS 6.144Mbps
195
Background
DL PS 8.192Mbps
197
Background
DL PS 8.640Mbps
201
Streaming
DL PS 768kbps
203
Streaming
DL PS 900kbps
205
Streaming
DL PS 1.2Mbps
207
Streaming
DL PS 1.8Mbps
209
Streaming
DL PS 3.65Mbps
211
Streaming
DL PS 7.2Mbps
A-6
SJ-20100603155704-001|2011-04-09(R2.2)
Sub-Service
Traffic Class
Maximum Bit Rate
213
Streaming
DL PS 10.1Mbps
215
Streaming
DL PS 14.0Mbps
217
Streaming
DL PS 1.024Mbps
219
Streaming
DL PS 2.048Mbps
221
Streaming
DL PS 4.096Mbps
223
Streaming
DL PS 6.144Mbps
225
Streaming
DL PS 8.192Mbps
227
Streaming
DL PS 8.640Mbps
229
Interactive
DL PS 17.6Mbps
231
Interactive
DL PS 21.096Mbps
233
Background
DL PS 17.6Mbps
235
Background
DL PS 21.096Mbps
237
Streaming
DL PS 17.6Mbps
239
Streaming
DL PS 21.096Mbps
140
Interactive
UL PS 512kbps
142
Interactive
UL PS 711kbps
144
Interactive
UL PS 1024kbps
146
Interactive
UL PS 1.399Mbps
148
Interactive
UL PS 1.448Mbps
150
Interactive
UL PS 2.048Mbps
152
Interactive
UL PS 2. 886Mbps
154
Interactive
UL PS 3. 072Mbps
156
Interactive
UL PS 4.096Mbps
158
Interactive
UL PS 5.76Mbps
170
Background
UL PS 512kbps
172
Background
UL PS 711kbps
174
Background
UL PS 1024kbps
176
Background
UL PS 1.399Mbps
178
Background
UL PS 1.448Mbps
180
Background
UL PS 2.048Mbps
182
Background
UL PS 2. 886Mbps
184
Background
UL PS 3. 072Mbps
186
Background
UL PS 4.096Mbps
A-7
SJ-20100603155704-001|2011-04-09(R2.2)
Sub-Service
Traffic Class
Maximum Bit Rate
188
Background
UL PS 5.76Mbps
200
Streaming
UL PS 512kbps
202
Streaming
UL PS 711kbps
204
Streaming
UL PS 1024kbps
206
Streaming
UL PS 1.399Mbps
208
Streaming
UL PS 1.448Mbps
210
Streaming
UL PS 2.048Mbps
212
Streaming
UL PS 2. 886Mbps
214
Streaming
UL PS 3. 072Mbps
216
Streaming
UL PS 4.096Mbps
218
Streaming
UL PS 5.76Mbps
113
Background
MBMS DL PS 8kbps
115
Background
MBMS DL PS16kbps
117
Background
MBMS DL PS 32kbps
119
Background
MBMS DL PS64kbps
121
Background
MBMS DL PS 128kbps
123
Background
MBMS DL PS 144kbps
125
Background
MBMS DL PS 256kbps
127
Streaming
MBMS DL PS 8kbps
129
Streaming
MBMS DL PS16kbps
131
Streaming
MBMS DL PS 32kbps
133
Streaming
MBMS DL PS64kbps
135
Streaming
MBMS DL PS 128kbps
137
Streaming
MBMS DL PS 144kbps
139
Streaming
MBMS DL PS 256kbps
A.5 Power Control Parameters Related to Service

Search UtranCell by CIdGet Utrancell.TrfPcIndexSearch TrfPc by TrfPcIndexGet a
set of power control parameters related to service.
The complete primary key of TrfPc is consisted of SrvType + TxDivMod. A set of power
control parameters related to service should include records of all sub-services in SubSrv.
A-8
SJ-20100603155704-001|2011-04-09(R2.2)
A.6 Scheduling Priority Parameters

Search UtranCell by CIdGet Utrancell.SchPriIndexSearch
SchPriIndexGet scheduling priority parameters.
SchPri
by
AppPri
by
AppPri
by
A.7 Congestion Control Priority Parameters

Search UtranCell by CIdGet Utrancell.CgtCtlPriIndexSearch
CgtCtlPriIndexGet Congestion control priority parameters.
A.8 Load Control Priority Parameters

Search UtranCell by CIdGet Utrancell.LdCtlPriIndexSearch
LdCtlPriIndexGet load control priority parameters.
A.9 UE Traffic Volume Measurement Parameters

Search
CUeTrv
by
CIdGet
CUeTrv.DrbcDchUeEvtSearch
UeTrv
DrbcDchUeEvtGet the related UE Traffic Volume Measurement parameters.
by
Search CUeTrv by CIdGet CUeTrv. DrbcDchUpSearch UeTrv by DrbcDchUpGet

the related UE Traffic Volume Measurement parameters.
Search CUeTrv by CIdGet CUeTrv.
DrbcRachUeEvtSearch UeTrv
DrbcRachUeEvtGet the related UE Traffic Volume Measurement parameters.
by
Search CUeTrv by CIdGet CUeTrv. DrbcFachUpSearch UeTrv by DrbcFachUpGet

Search CUeTrv by CIdGet CUeTrv. DrbcSHsUpSearch UeTrv by DrbcSHsUpGet
Search CUeTrv by CIdGet CUeTrv. DrbcIBHsUpSearch UeTrv by DrbcIBHsUpGet
Search CUeTrv by CIdGet CUeTrv.
DrbcEDchUpThptSearch UeTrv by
DrbcEDchUpThptGet the related UE Traffic Volume Measurement parameters.
UE Traffic Volume Measurement information is shown as Table A-2, and only the default
records of UeTrv are supported in current version.
Table A-2 Function of Defaut records in UeTrv
UeTrvMCfgNo
Function of Default Configuration
UE Traffic Volume Event Measurement Configuration Number for DCH
UP Traffic Volume Measurement Configuration Number for DCH
UE Traffic Volume Event Measurement Configuration Number for RACH
UP Traffic Volume Measurement Configuration Number for FACH

A-9
SJ-20100603155704-001|2011-04-09(R2.2)
UeTrvMCfgNo
Function of Default Configuration
UP Traffic Volume Measurement Configuration Number for Streaming Class

on HS-DSCH
UP Traffic Volume Measurement Configuration Number for Interactive and

Background Class on HS-DSCH
UP Throughput Event Measurement Configuration Number for E-DCH
A.10 Access Control Parameters Related to Basic

Priority
Search UtranCell by CIdGet Utrancell.BPriAcIndexSearch
BPriAcIndexGet access control parameters related to basic priority.
BPriAc
by
A.11 Transport Format Combination Set Parameters

of SCCPCH
Search Sccpch by CId + CPCIdGet Sccpch.TfcsIndexSearch
TfcsIndexGet transport format combination set parameters of SCCPCH.
DlTfcs
by
A.12 Transport Format Combination Set Parameters

of PRACH
Search Prach by CId + CPCIdGet Prach.TfcsIndexSearch UlTfcs by TfcsIndexGet
Transport format combination set parameters of PRACH.
A.13 Transport Format Set Parameters

Search Rach by CId + CTCIdGet Rach.TfsIndexSearch Tfs by TfsIndexGet
Transport format set parameters of RACH.
Search Pch by CId + CTCIdGet Pch.TfsIndexSearch Tfs by TfsIndexGet Transport
format set parameters of PCH.
Search Fach by CId + CTCIdGet Fach.TfsIndexSearch Tfs by TfsIndexGet
Transport format set parameters of FACH.
Search CMbms by CIdGet CMbms.TfsIndexSearch Tfs by TfsIndexGet Transport
format set parameters of FACH carrying MSCH.
A-10
SJ-20100603155704-001|2011-04-09(R2.2)
A.14 NodeB Parameters

Search UtranCell by CIdGet UtranCell.NodeNoSearch nodeB by NodeNoGet
NodeB parameters.
A.15 Ura Information

One URA can contains 32 cells at most. The cell list of a URA is needed in PAGING
process.
There are URANum and URA in object utranCell and externalUtranCell. The two
parameters describe the URA list that cell belongs to. One cell can belong to at most four
URAs. The URA list is needed in SIB2 and UE moving state Cell_PCH to URA_PCH.
A.16 Parameters of Other Objects

The parameters of other objects except Intra-frequency Measurement Parameters
NodeB Parameters are obtained by the primary keys of those objects.
For example, we can get cell selection parameters in SIB3 by searching CelSel according
to CId + SIB3.
A-11
SJ-20100603155704-001|2011-04-09(R2.2)
A-12
SJ-20100603155704-001|2011-04-09(R2.2)
Appendix B
CPC and CTC

Table of Contents
CPC and CTC ........................................................................................................ B-1
B.1 CPC and CTC

CPCId (Common physical channel ID) is the unique identifier allocated to one common
physical channel within a cell. So the global CPCId is CId + CPCId in RNC.
CTCId (Common Transport Channel ID) is the unique identifier allocated to one common
transport channel within a cell. So the global CTCId is CId + CPTId in RNC.
CPCId value range and maximum number of channels are shown as Table B-1
Table B-1 CPCId value range and maxium number of channels
Common Physical Channel
CPCIdValueRange
Type
Maximum Number of
Channels in a Cell
PCCPCH
PCPICH
PSCH
SSCH
SCCPCH
4..35
SCPICH
36..67
PRACH
68..99
PICH
100..131
AICH
132..163
MICH
164
CTCId value range and maximum number of channels are shown as Table B-2
Table B-2 CTCId value range and maxium number of channels
Common Transport Channel
CTCIdValueRange
Type
Maximum Number of Channel

in a Cell
BCH
FACH
9..32
16
B-1
SJ-20100603155704-001|2011-04-09(R2.2)
Common Transport Channel
CTCIdValueRange
Type
Maximum Number of Channel

in a Cell
PCH
1..8
RACH
65..96
SCCPCH can carry PCH, FACH. PCHInd in object Sccpch indicates whether SCCPCH
carries PCH.
SccpchUsage in object Sccpch describes the usage of SCCPCH. SCCPCH can be used
for R99 or MCCH or MCCH & R99.
SignalFach in object Fach describes the usage of FACH. SCCPCH can be used for R99
Data or R99 Signaling or R99 Signaling & MCCH or MCCH.
If FACH is used for R99 Data or R99 Signaling, then SCCPCH carrying the FACH must
be used for R99. If FACH is used for R99 Signaling & MCCH, then SCCPCH carrying the
FACH must be used for MCCH & R99. If FACH is used for MCCH, then SCCPCH carrying
the FACH must be used for MCCH. There can be only one FACH used for carrying MCCH
in a cell.
We can see which SCCPCH carries the FACH and PCH by the SccpchCPCId of object
Fach and Pch.
SCCPCH corresponding to MICH (MBMS notification Indicator Channel) can be obtained
by the SccpchCPCId of object Mich. And the SCCPCH must be used for MCCH or MCCH
& R99.
One PICH corresponds to one PCH. One SCCPCH can carry one PCH at most. One
SCCPCH can carry eight FACH at most.
One PRACH can carry one RACH only. One AICH corresponds to one RACH.
B-2
SJ-20100603155704-001|2011-04-09(R2.2)
Figures
Figure 1-1 Flow of Importing Radio Parameter Settings ............................................ 1-2
Figure 1-2 Choose Planned Data.............................................................................. 1-3
Figure 1-3 The Result of Importing............................................................................ 1-4
Figure 1-4 Choose Live Data .................................................................................... 1-4
Figure 1-5 Choose all RNC Object ............................................................................ 1-5
Figure 1-6 The Naming Rule of Script File ................................................................ 1-5
Figure 1-7 The Example of Sheet of Recording MOC Data ....................................... 1-6
Figure 1-8 The example of index sheet ..................................................................... 1-7
Figure 1-9 Moc Data Sheet of Delta File (script)........................................................ 1-8
Figure 1-10 Choose Configuration Data Export Tool ................................................. 1-9
Figure 1-11 Data Export Interface ........................................................................... 1-10
Figure 1-12 Tick the Target Node Information ......................................................... 1-10
Figure 1-13 Select Configuration Guide .................................................................. 1-11
Figure 1-14 Select Config Set Dialog Box ............................................................... 1-11
Figure 1-15 Select CNO Radio Data Batch Import .................................................. 1-12
Figure 1-16 CNO Radio Data Batch Import Tab ...................................................... 1-12
Figure 2-1 Relationship 1 of Radio Resource Management Objects.......................... 2-7
Figure 2-2 Relationship 2 of Radio Resource Management Objects.......................... 2-8
Figures
Tables
Table 1-1 The Structure of Sheet of Recording MOC Data ........................................ 1-6
Table 1-2 The Structure of index sheet...................................................................... 1-6
Table 2-1 Primary Keys and Alternative Key of MOC ................................................ 2-1
Table A-1 Sub-Service information ............................................................................A-3
Table A-2 Function of Defaut records in UeTrv ..........................................................A-9
Table B-1 CPCId value range and maxium number of channels ................................B-1
Table B-2 CTCId value range and maxium number of channels ................................B-1
III
Tables
Glossary
CNO
- Communication Network Optimization
OMM
- Operation & Maintenance Module
RNC
- Radio Network Controller

SJ-20100603155704-001-ZXWR RNC (V3.09.30) Specifications and Requirements For Importing Radio Parameter Settings - 341298

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

SJ-20100603155704-001-ZXWR RNC (V3.09.30) Specifications and Requirements For Importing Radio Parameter Settings - 341298

Caricato da

Copyright:

Formati disponibili

ZXWR RNC

Radio Network Controller

Specifications and Requirements for

Additionally, the contents of this document are protected by

contractual confidentiality obligations.

First Edition (V3.09.30.03)

Second Edition (V3.09.30.09)

Those sections have been modified:

Those sections have been modified:

Serial Number: SJ-20100603155704-001

Chapter 2 Relationships ............................................................................ 2-1

2.2.16 Intra-frequency Measurement................................................................ 2-25

Chapter 3 Operation in Planning Radio Parameters ............................... 3-1

3.15 CfnOffset ......................................................................................................... 3-6

3.52 Aich............................................................................................................... 3-23

Appendix A Searching Methods of Radio Parameters .......................... A-1

A.14 NodeB Parameters......................................................................................... A-11

Appendix B CPC and CTC ........................................................................ B-1

What Is in This Manual

Chapter 1, Flow of Importing Radio Parameter

Introduces the flow of importing radio parameter

Introduces the relationships for MOC

Chapter 3, Operation in Planning Radio

Introduces the operations in planning radio

Appendix A, Searching Methods of Radio

Introduces the searching methods of radio

Appendix B, CPC and CTC

Introduces the basic concept of CPC and CTC

Flow of Importing Radio

1.2 Flow Chart

ZTE Proprietary and Confidential

Figure 1-1 Flow of Importing Radio Parameter Settings

1. Create live data setting.

ZTE Proprietary and Confidential

Chapter 1 Flow of Importing Radio Parameter Settings

1.3 Operations in CNO Software

ZTE Proprietary and Confidential

Figure 1-3 The Result of Importing

6. Choose live data, as shown in Figure 1-4.

7. Click Browser button, choose the live data file.

ZTE Proprietary and Confidential

Chapter 1 Flow of Importing Radio Parameter Settings

Figure 1-5 Choose all RNC Object

1.4 Live/Planned Data files

ZTE Proprietary and Confidential

1.4.2 Structure of Sheets in Live/Planned data File

Sheets of recording MOC data

1.4.2.1 Sheets of Recording MOC data

1.4.2.2 Index Sheets

The example of index sheet is shown as Figure 1-8.

ZTE Proprietary and Confidential

Chapter 1 Flow of Importing Radio Parameter Settings

Figure 1-8 The example of index sheet

1.5 Delta files (script)

1.5.2 Structure of Sheets in Delta File (script)

Sheets of recording MOC data

ZTE Proprietary and Confidential

Figure 1-9 Moc Data Sheet of Delta File (script)

Other columns structure description of recording MOC data refer to Sheets of

1.5.3 Modify Indicator

A: The abbreviation of Add, indicating to add one record.

D: The abbreviation of Delete, indicating to delete one record.

M: The abbreviation of modify, indicating to modify one record.