Академический Документы
Профессиональный Документы
Культура Документы
Guide
WCDMA RAN
Control
Feature
Date
Author
Reviewer
Revision History
1.
Added
Section
ZWF21-03-050
2.1.24
Added
Section
Special
6.4.1
Events
4.
5.
6.
7.
V7.0
2012-3-30
Feng
Zhao
Hong
Dapeng
9.
Modified
the
description
of
parameters
the
following
new
parameters:
CelReturnLteSwch,
fastRetEUtranSwch,
RncFeatSwitchBit18,
RncFeatSwitchBit9,
RncFeatSwitchBit15,
RncFeatSwitchBit10,
RncFeatSwitchBit11,
RncFeatSwitchBit0,
RncFeatSwitchBit19,
RncFeatSwitchBit7,
RncFeatSwitchBit4,
RncFeatSwitchBit1,
RncFeatSwitchBit2,
HcsSupportInd,
and
ParallelSoftHO.
11. Deleted
the
following
RncFeatSwitch,
UseofHcs(UtranRelation),
parameters:
UseofHcs(UtranCell),
and
UseofHcs(gsmRelation).
the
following
RncFeatSwitchBit16,
parameters:
RncFeatSwitchBit17,,
srvHoIndPsRT,
BSCPSFeatSwitch,
BSCDTMFeatSwitch,
UIntraMeasProfile,
UIntraMeasSrvSpec,
UIntraMeasNoSrvSpec,
UInterMeaSrvSpec,
UInterMeasProfile,
UInterMeasNoSrvSpec,
URatMeasProfile,
URatMeasSrvSpec,
URatMeasNoSrvSpec,
IurgFeatSwitch,
imsiMatchedDgtNum,
imsiMatchedDigit,
BoardPwrOffHoTmr,
UtraSISwitch,
intialHoCelSelScene,
UUeIntMeasProfile,
the
following
MeasQuantity(Intra),
parameters:
MeasQuantity(Inter),
IntRatHoMth,
InterHoMth,
MeasQuantity(UeInt),
RptTxPwrInd,
EvtMeasRTT2,
power
off/on
and
inter-frequency
Added
Section
8.5
EUTRAN
Blacklist
Management.
2.
3.
Added
Section
EUTRAN
8.7
Detection
Supported
4.
Strategy
based
on
the
Indoor
Neighboring Cell.
5.
6.
7.
V8.0
2012-11-2
Feng
Zhao
Hong
Dapeng
Added
Section
ZWF21-03-050
2.1.24
Modified
Section
Processing
7.1.2.4
of
Modified
Section
Configuration
5.1.2.7
Strategies,
and
Parameter
separated
Section
5.11
Inter-frequency
and
the
following
parameters:
EutranNCblstSwch, StateMode(UENbrBlkList),
LdBsdEutranHOInd,
EutranDlLdThrd,
IndoorCellInd,
EutranUlLdThrd,
EutraDetectionInd,
RncTxPwrHoSwch,
RncUlBlerHoSwch,
RatCelInfoSwch,
IntraHoEcNoThrd,
IntraHoRscpThrd,
EnhanceHoSwch,
HoToEutraPenTimer,
sonTransReqPeriod,
sonTransReqNumThrd,
sonTransRespSwitch,
rxlevNecellInd,
sonTransRespNumThrd,
RNCFEATSWITCHBit24,
CResPara5,
the
following
parameters:
EcNoThrAddNRLSHO
and
RSCPThrAddNRLSHO.
1.
Modified
Section
Scenarios
4.3.14
of
3.
EutranPsHoMode,
Modified
Section
Processing
5.1.2.4
of
Added
Section
Judgement
2013-7-4
Meiqing
Zhao
Feng
Dapeng
Hong
Strategy
Minimum
in
Quality
Inter-frequency
Handover.
Huang
V8.5
5.1.2.5
6.
7.
Modified
Section
UTRAN<->LTE PS
8.1
UE
E-UTRA
Capability
before
and
SRVCC,
added
timer for
10. Added
feature
IDs,
supplemented
some
TABLE OF CONTENTS
1
Feature Attributes............................................................................................ 14
2
2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8
2.9
2.10
2.11
2.12
2.13
2.14
2.15
2.16
2.17
2.18
2.19
2.20
2.21
2.22
2.23
2.24
2.25
2.26
2.27
2.28
2.29
2.30
2.31
2.32
2.33
2.34
2.35
Overview .......................................................................................................... 14
ZWF21-03-001 Soft/Softer Handover ................................................................. 16
ZWF21-03-002 Intra-Frequency Hard Handover ................................................ 16
ZWF21-03-003 Inter-Frequency Hard Handover ................................................ 16
ZWF21-03-004 Inter-RAT Mobility (GSM) .......................................................... 17
ZWF21-03-006 Inter-RNC Handover with Iur Support ........................................ 19
ZWF21-03-008 Directed Signalling Connection Re-establishment ..................... 20
ZWF21-03-009 Coverage Based Handover ....................................................... 20
ZWF21-03-010 Compressed Mode .................................................................... 20
ZWF21-03-011 Neighboring Cells Priorities ....................................................... 20
ZWF21-03-012 Handover Based on Dedicated Downlink Transmit Power ......... 21
ZWF21-03-012 Handover Based on Dedicated Uplink Transmit Power (UE) ..... 21
ZWF21-03-013 Quality-Based Handover ........................................................... 21
ZWF21-03-020 SRNS Relocation ...................................................................... 21
ZWF21-03-022 IMSI-based Handover ............................................................... 22
ZWF21-03-023 Inter-RAT PS Handover (GSM) ................................................. 22
ZWF21-03-024 DTM Handover .......................................................................... 22
ZWF21-03-025 NACC ........................................................................................ 22
ZWF21-03-026 Target Cell Load Based Inter-RAT Handover ............................ 23
ZWF21-05-022 Handover Strategy Based on Service Type ............................... 23
ZWF21-03-014 Enhanced Iur-g.......................................................................... 23
ZWF21-03-110 UTRAN<->LTE PS Handover Strategy ...................................... 23
ZWF21-03-120 Single Radio Voice Call Continuity (SRVCC)............................. 24
ZWF21-03-101 CS Fallback (CSFB) .................................................................. 24
ZWF21-03-050 Handover Optimization in Weak-Coverage................................ 24
ZWF23-03-001 HS-DSCH Serving Cell Change ................................................ 24
ZWF23-03-002 HS-DSCH handover to/from DCH ............................................. 25
ZWF23-03-003 HS-DSCH Inter-RAT Reselection .............................................. 25
ZWF23-03-004 HSDPA Soft/Softer Handover of A-DPCH ................................. 25
ZWF23-03-005 HSDPA over Iur......................................................................... 25
ZWF25-03-001 HSUPA Soft/Softer Handover .................................................... 25
ZWF25-03-002 E-DCH Serving Cell Change Inside Active Set .......................... 26
ZWF25-03-003 E-DCH Intra-frequency Hard Handover ..................................... 26
ZWF25-03-004 E-DCH Inter-frequency Hard Handover ..................................... 26
ZWF25-03-005 HSUPA over Iur......................................................................... 26
ZWF25-03-012 HSUPA Inter-RAT Reselection .................................................. 27
3
3.1
3.2
3.3
4
4.1
4.1.1
4.1.2
4.1.3
4.2
4.3
4.3.1
4.3.2
4.3.3
4.3.4
4.3.5
4.3.6
4.3.7
4.3.8
4.3.9
4.3.10
4.3.11
4.3.12
4.3.13
4.3.14
4.3.15
4.4
4.4.1
4.4.2
4.4.3
4.4.4
4.4.5
4.4.6
5
5.1
5.1.1
5.1.2
5.1.3
5.2
5.3
5.4
5.5
5.6
5.7
5.8
5.9
5.10
5.11
5.11.1
5.11.2
5.12
6
6.1
6.1.1
6.1.2
6.2
6.2.1
6.2.2
6.2.3
6.3
6.4
6.4.1
6.4.2
7
7.1
7.1.1
7.1.2
7.1.3
7.2
7.3
7.4
7.5
7.6
7.7
7.8
7.8.1
7.8.2
7.9
7.10
7.11
7.11.1
7.11.2
8
8.1
8.1.1
8.1.2
8.1.3
8.1.4
8.1.5
8.2
8.3
8.4
8.4.1
8.4.2
8.4.3
8.4.4
8.5
8.6
8.7
8.8
8.8.1
8.8.2
9
9.1
9.2
10
10.1
10.2
10.3
10.4
11
11.1
11.2
11.3
11.4
12
12.1
12.2
13
13.1
13.1.1
13.1.2
13.2
13.2.1
13.2.2
13.3
13.3.1
13.3.2
13.4
13.4.1
13.4.2
13.5
13.5.1
13.5.2
13.6
13.6.1
13.6.2
13.7
13.7.1
13.7.2
13.8
13.8.1
13.8.2
13.9
13.9.1
13.9.2
14
14.1
14.1.1
14.1.2
14.1.3
14.1.4
14.1.5
14.1.6
14.1.7
10
14.1.8
14.1.9
14.1.10
14.1.11
14.1.12
14.2
15
11
FIGURES
Figure 3-1 Transmission Gap (TG) Position .......................................................................28
Figure 3-2 Parameters of Compressed Mode ....................................................................29
Figure 3-3 Procedure for E-DCH Fallback to DCH Prior to Initiation of Compressed Mode 31
Figure 3-4 Procedure for Configuring Accompanying Compressed Mode ..........................32
Figure 3-5 Procedure for Configuring Dedicated Compressed Mode .................................33
Figure 4-1 Intra-frequency Handover Index Quotations ......................................................40
Figure 4-2 Cell Priority Configuration .................................................................................43
Figure 4-3 Time-To-Trigger mechanism .............................................................................52
Figure 4-4 Intra-RNC Soft Handover (Adding a Radio Link) ...............................................65
Figure 4-5 Intra-RNC Soft Handover (Deleting a Radio Link) .............................................66
Figure 4-6 Intra-RNC Soft Handover (Swapping a Radio Link) ..........................................67
Figure 4-7 Intra-RNC Hard Handover ................................................................................68
Figure 4-8 Inter-RNC Hard Handover Through lur Interface ...............................................69
Figure 4-9 Inter-RNC Hard Handover Without lur Interface ................................................70
Figure 5-1 Inter-Frequency Handover Index Quotations ....................................................87
Figure 5-2 Cell Priority Configuration .................................................................................91
Figure 6-1 Relocation Triggered by Soft Handover ..........................................................105
Figure 6-2 Relocation Triggered by Hard Handover .........................................................108
Figure 7-1 Indexing relations for inter-RAT handover .......................................................123
Figure 7-2 Priority Settings of Cells ..................................................................................126
Figure 7-3 3G to 2G CS Service Handover ......................................................................134
Figure 7-4 3G to 2G CS Service Handover Procedure via IUR-G ....................................135
Figure 7-5 PS service reselection initiated by an UE in the case of 3G to 2G handover ...138
Figure 7-6 PS service reselection initiated by the RNC in the case of 3G to 2G handover
...........................................................................................................................................139
Figure 8-1 Indexing relation for inter-RAT handover.........................................................143
Figure 8-2 UTRAN->EUTRAN PS Handover Process ......................................................147
Figure 8-3 SRVCC from E-UTRAN to UTRAN .................................................................148
12
TABLES
Table 2-1 Correspondence between Handover and Compressed Mode ............................15
Table 3-1 Parameters of Compressed Mode......................................................................30
Table 12-1 Table of Principle ...........................................................................................176
Table 13-1 Service Type Related UE Inter-frequency Measurement Parameter
Configuration Default Value ................................................................................................267
Table 13-2 Service Type Related UE Inter-RAT Measurement Parameter Configuration
Default Value ......................................................................................................................304
13
Feature Attributes
System version: [RNCV3.12.10/RNCV4.12.10, Node B V4.12.10, OMMR V12.12.41,
OMMB V12.12.40]
Attribute: [Mandatory + Optional]
Involved NEs:
UE
Node B
RNC
MSC
-
MGW
-
SGSN
-
GGSN
-
HLR
-
Note:
*-: Not involved.
*: Involved.
Dependency: [None]
Mutual exclusion: [None]
Note: [None]
Overview
The cell handover strategy is required in WCDMA to implement mobility management of
RRC connections due to UE mobility. It is also required to balance traffic among cells to
lower traffic in heavily-loaded cells. Service connections must not be interrupted and
QoS must be guaranteed during handover.
In the process of a handover:
If a UE retains the radio connection with the current cell while establishing a radio
connection in a new cell, the handover is called soft handover.
If the new and current cells belong to the same Node B during a soft handover, the
handover is called softer handover.
14
Table 2-1
Soft
Handover
Hard
Require Compressed
Handover
Mode to Activate or
Not
Intra-frequency
Inter-frequency
Inter-RAT
15
2.1
Soft and softer handovers are seamless handovers and no service will be
interrupted during handover.
Macro diversity gain: When a UE maintains radio links with several cells, the
receiver may enhance the accuracy of data reception and link receiving quality and
lower the transmit power of all links by combining the signal receiving results of
several links.
The best cell where a UE registers may establish a radio connection with the UE in
time to lower the transmit power of the UE.
In view of these features, for intra-frequency handover, soft and softer handovers are
conducted whenever possible, a hard handover is only conducted when the soft/softer
handover is unavailable.
2.2
2.3
16
The factors triggering an inter-frequency hard handover include radio quality, cell load,
and moving speed of the UE.
Inter-frequency hard handover
triggered
by radio quality:
An inter-frequency
measurement is initiated when the quality of the frequency where the UE is currently
located worsens, and then the UE is handed over to the frequency with better quality
based on the inter-frequency measurement result. The quality of the carrier frequency
where the UE is currently located is measured according to the following four standards
(For details, see Chapter 5 Inter-Frequency Handover Strategy):
Inter-frequency hard handover triggered by cell load: When the load of a cell on the
current frequency is too heavy, the system switches partial services of the cell to an
adjacent cell on another frequency.
Inter-frequency hard handover triggered by moving speed of the UE: It is mainly used on
the HCS network. UEs with quick moving speed are carried in macro cells and those with
slow moving speed in micro cells for appropriate traffic distribution in cells, making full
use of system resources and enhancing system performance.
For non-double-receiver terminals in WCDMA, compressed mode must be initiated for
inter-frequency measurement. However, initiation of compressed mode has impact on
the performance of both the system and the UE. Therefore, compressed mode must not
be initiated unless absolutely necessary (for example, when the quality of the current
serving carrier frequency worsens).
2.4
17
switch from UTRAN to RATx (the mobility management from RATx to UTRAN belongs to
the strategy of RATx).
This feature requires the UE to support both WCDMA and RATx. Moreover, the RATx
also needs to offer related features to support inter-RAT handover. The features required
by WCDMA are described below.
WCDMA-to-GSM handover supports the following services:
Conversational services
PS transferred to GPRS/GERAN
For a WCDMA-to-GSM handover combining CS and PS RAB, the system first switches
CS services to GERAN first, and then the RNC releases the PS on lu interface upon
receiving the context request message from the CN. The UE activates the PS service on
GERAN upon the release of CS services.
In WCDMA:
The factors triggering a WCDMA-to-GSM handover include radio quality and cell load.
18
Inter-RAT handover triggered by cell load: When the load of a cell in the current UTRAN
system is too heavy, the system switches partial services of the cell to an adjacent cell in
GERAN.
For non-double-receiver terminals in WCDMA, compressed mode must be initiated for
inter-RAT measurement. However, initiation of compressed mode has impact on the
performance of both the system and the UE. Therefore, compressed mode must not be
initiated unless absolutely necessary (for example, when the quality of the current
serving carrier frequency worsens).
2.5
19
2.6
2.7
2.8
2.9
20
2.10
2.11
2.12
2.13
21
2.14
2.15
2.16
2.17
ZWF21-03-025 NACC
The PS service will be interrupted when it is handed over to GERAN via cell reselection
procedure, which leads to bad user experience. Network Assisted Cell Change (NACC)
reduces the duration of UE inter-RAT cell reselection procedure by sending system
information to the RNC in advance.
22
2.18
2.19
2.20
2.21
23
2.22
2.23
2.24
2.25
24
2.26
2.27
2.28
2.29
2.30
25
2.31
2.32
2.33
2.34
26
2.35
3.1
27
Figure 3-1
#0
#Nfirst-1
Radio frame
#Nlast+1
#14
#0
Transmission gap
#Nfirst-1
#Nlast+1
#14
In the protocol TS 25.212, the Transmission Gap Length (TGL) can be set to 3, 4, 5, 7,
10 and 14 timeslots. The TG may start from any timeslot in a frame. When the TG spans
two consecutive frames, each frame at least has 8 non-compressed timeslots.
Figure 3-2 shows the parameters involved in compressed mode. The Transmission Gap
Pattern Sequence (TGPS) consists of consecutive TG patterns (TG pattern 1). One or
two TGs are defined in a TG pattern. The starting timeslot No. of the first TG is
determined by the parameter TGSN. The number of timeslots between starting timeslots
of two TGs in the TG pattern is determined by the parameter TGD. The first TGL is
determined by the parameter TGL1, and the second by the parameter TGL2. If the
parameter TGD is not defined, it means that there is only one TG in the TG pattern. The
length of a TG pattern is determined by the parameter TGPL1. The number of repeats of
a TG pattern is determined by the parameter TGPRC.
28
Figure 3-2
#1
#2
#3
#4
#5
#TGPRC
TG pattern 1
TG pattern 1
TG pattern 1
TG pattern 1
TG pattern 1
TG pattern 1
TG pattern 1
Transmission
Transmission
gap 1
gap 2
TGL1
TGL2
TGSN
TGD
TGPL1
3.2
29
Compressed mode of all services on ZTE networks use identical parameters as listed
below:
Table 3-1
Measurement
TGSN
4 (Slots)
3 (Slots)
TGL1
7 (Slots)
7 (Slots)
TGD
Not configured
Not configured
TGPL1
8 (Frames)
8 (Frames)
As shown in the table, when the TGSN is 4 (GSM) or 3 (FDD), TGL1=7, all GAPs of
compressed mode on ZTE networks in the same radio frame (one radio frame in FDD
has 15 slots), that is, single frame mode is uniformly used.
For all commercial terminals in the current market, compressed mode can be initiated
directly when services are carried on HS-DSCH. Whether HS-DSCH falls back to DCH
before the initiation of compressed mode is controlled through the parameter
HsdpaCmAssoMode. If the parameter value is Serial, HS-DSCH needs to fall back to
DCH before the initiation of compressed mode. If the parameter value is Parallel,
compressed mode is initiated directly.
Moreover, whether E-DCH falls back to DCH before the initiation of compressed mode is
controlled through the parameter HsupaCmAssoMode (UHspa). If the parameter value is
Serial, E-DCH needs to fall back to DCH (the reconfigured target rate is min (max
(DRBC lowest of rate grades, GBR), MaxBR), for DRBC rate grades, see ZTE UMTS
DRBC Algorithm Feature Guide) before the initiation of compressed mode. If the
parameter value is Parallel, compressed mode is initiated directly. Figure 3-3 shows
the procedure in which E-DCH falls back to DCH before the initiation of compressed
mode.
30
Figure 3-3
Mode
RNC
NodeB
UE
HS-DSCH/E-DCH
Measurement Report (Event 2d)
E-DCH Downgrade to
DCH, configure
compressed mode
Measurement Control
For a part of commercial terminals in the current market, compressed mode cannot be
initiated when services are carried on E-DCH. Whether a UE supports Initiate
compressed mode for services carried on E-DCH is not specified in 3GPP. Therefore,
when services are carried on E-DCH, the RNC does not know whether a UE can Initiate
compressed mode for services carried on E-DCH. To deal with these UEs, when
HsupaCmAssoMode is set to Parallel and the current services involve HSUPA services,
the RNC executes the safeguarded strategy after the initiation of HSUPA parallel
compressed mode fails as follows:
When the RNC forwards the Measurement Control message to a UE for initiating
compressed mode and the UE returns the Measurement Control Failure message, the
RNC will reconfigure E-DCH to DCH before initiating compressed mode. Afterwards, if
the UE need switch from DL HS-DSCH/UL DCH to DL HS-DSCH/UL E-DCH based on
traffic volume measurement reports during a call process, the RNC will not allow it if the
UE is in compressed mode.
In the procedure of a service setup, state transition, call re-establishment and relocation
from other RNCs to the local RNC, the RNC will configure accompanying compressed
31
mode
by
default
through
RADIO
BEARER
SETUP/RADIO
BEARER
Figure 3-4
NodeB
RNC
CN
Service setup,
configure
accompanying
compressed mode
Measurement Control
Active
compressed mode
32
Figure 3-5
UE
NodeB
RNC
CN
Configure Dedicated
compressed mode
Measurement Control
Active compressed
mode
Note: TGCFN is the connection frame number of the first frame of the first pattern within
the Transmission Gap Pattern Sequence (TGPS).
3.3
33
simultaneously.
CompMdCfgStra
(ULogicalRnc)
indicates
the
strategy
of
The DRNC does not allow the compressed mode command via Iur to activate
compressed mode
Some vendors do not allow the compressed mode command via Iur to activate
compressed mode, RncFeatSwitchBit17 indicates the strategy for this situation. When
CS traffic and Iur link exist, if RncFeatSwitchBit17 is 0, the DRNC does not activate
compressed mode even when needed (if compressed mode is already activated, the
DRNC does not take account of RncFeatSwitchBit17). When CS traffic and Iur link exist,
if RncFeatSwitchBit17 is 1, the DRNC activates compressed mode when needed.
measurement
through
the
parameter
IntraMeasQuan
(UUtranCellFDD).
34
The active set refers to a set of cells retaining a radio connection with the UE.
The monitored set refers to a set of cells retaining no radio connection with the UE but
requesting a measurement by sending an intra-frequency measurement control message
to the UE.
The detected set refers to a set of intra-frequency cells other than those in the active set
and monitored set.
4.1
Intra-Frequency Measurement
When conducting an intra-frequency measurement, the UE needs to implement layer 3
filtering for the measurement results to avoid measurement fluctuations, and then make
event decisions and report by using filtered values. The layer 3 filter formula is as follows:
Fn (1 a) Fn1 a Mn
Where,
Fn-1 refers to the result of the last filter.
Fn refers to the result of the current measurement filter.
Mn refers to the current measurement result.
a = 1/2
(k/2)
refers to the filter coefficient calculated based on the filter factor K (FilterCoeff
the
measurement
quantity
is
RSCP,
this
parameter
is
obtained
from
35
4.1.1
4.1.2
4.1.2.1
Measurement Setup
Intra-frequency measurement parameters are configured for the UE and intra-frequency
measurements are initiated through the measurement control setup message in the
following cases:
36
4.1.2.2
Measurement Modification
If an intra-frequency measurement is enabled, an intra-frequency measurement
modification is triggered in the following cases:
After the best cell changes (Event 1D), a change of intra-frequency measurement
parameters will trigger a modification of intra-frequency measurement to update
handover parameters.
4.1.2.3
Measurement Deletion
Upon receiving an exceptional intra-frequency measurement report (for example, the
measurement report belongs to a non-existent measurement task), or before making a
decision about the relocation triggered by a soft handover, the RNC will voluntarily
release the corresponding intra-frequency measurement. When the RNC sends a
MEASUREMENT CONGROL RELEASE message for a measurement ID, the time stamp
will be recorded. If the RNC receives a measurement report for the ID, the report will be
compared between the current time and recorded time. If the difference between the
current time and recorded time exceed the threshold TResndMeaCtrlRel (URncFunction)
configured, the MEASUREMENT CONTROL RELEASE message will be resent.
Otherwise, this measurement report is ignored.
4.1.2.4
37
There are seven intra-frequency measurement events (1A, 1B, 1C, 1D, 1E, 1F and
1J) in total. The number of events configured depends on the parameter
MeasEvtNum (If the measurement quantity is EcNo, this parameter is obtained from
UIntraEcNoEvMeas. If the measurement quantity is RSCP, this parameter is
obtained from UIntraRscpEvMeas), and the intra-frequency events configured
depends on the parameter MeaEvtId (If the measurement quantity is EcNo, this
parameter is obtained from UIntraEcNoEvMeas. If the measurement quantity is
RSCP, this parameter is obtained from UIntraRscpEvMeas). MeaEvtId is defined
through array, and the dimension of array is equal to MeasEvtNum, which is seven
at most.
IntraMeasQuan(UUtranCellFDD)
38
UIntraEcNoPrdMeas
(UIntraEcNoPrdMeas),
UIntraRscpPrdMeas
(srvCategory (UIntraMeasSrvSpec))
Notes:
(1). When concurrent services exist and include CS+PS services, the Multi RAB
Including CS and PS configuration is indexed.
(2). When concurrent services exist and include non-CS services, the RT RAB
Excluding Voice configuration is indexed.
39
(3). When the above principles are met simultaneously, the first one prevails.
To facilitate parameter modification and optimization, the intra-frequency parameters are
index-organized. The index quotations are listed as follows:
Figure 4-1
UIntraMeasProfile(UIntraMeasProfile)
UIntraMeasSrvSpec(UIntraMeasSrvS
pec)
UIntraMeasNoSrvSpec(UIntraMeasNo
SrvSpec)
srvCategory
intraMeasQuan
intraMeasQuan
UIntraEcNoEvM
eas(UIntraEcNo
EvMeas)
UIntraRscpEvM
eas(UIntraRscp
EvMeas)
UIntraEcNoPrd
Meas(UIntraEc
NoPrdMeas)
UIntraRscpPrd
Meas(UIntraRsc
pPrdMeas)
UIntraEcNoEvM
easForD(UIntra
EcNoEvMeasFo
rD)
UIntraRscpEvM
easForD(UIntra
RscpEvMeasFo
rD)
intraMeasCfgNo
(UIntraEcNoEv
Meas)
intraMeasCfgNo
(UIntraRscpEvM
eas)
intraMeasCfgNo
(UIntraEcNoPrd
Meas)
intraMeasCfgNo
(UIntraRscpPrd
Meas)
intraMeasCfgNo
(UIntraEcNoEv
MeasForD)
intraMeasCfgNo
(UIntraEcNoEv
MeasForD)
Note: When a new cell is set up, the value of intialHoCelSelScene (UIntraMeasProfile)
(0:Outdoor Scene, 1:High-Mobility Outdoor Scene, 2:Indoor Scene, 3:Subway/tunnel
Scene)
is
determined
according
to
the
actual
cell
scene
(indicated
by
Before
intra-frequency
profileId(UIntraMeasProfile)
handover
of
the
parameters
cell
is
are
found
obtained,
based
on
40
ref1UintraMeasProfile(UUtranCellFDD),
and
then,
in
UintraMeasProfile
configuration items, the next level managed object is obtained according to the
current measurement application type: For event-triggered measurements,
Intra-frequency Measurement Configuration Related to Traffic Category Object
ID(UIntraMeasSrvSpec) is selected. For periodical measurements or detected set
tracing applications, Intra-frequency Measurement Configuration Unrelated to
Traffic Category Object ID (UIntraMeasNoSrvSpec) is selected.
In
the
managed
object
decided
Intra-Frequency
above,
Measurement
related
to
the
managed
object
UIntraEcNoPrdMeas
or
41
Measurement Quantity and Measurement Report Criteria are automatically filled by the
system based on IntraMeasCfgNote.
For the cells of the neighbor RNC, if the value of Primary CPICH Power Configuration
Tag (PcpichPwrPre(UExternalUtranCellFDD)) is TURE, the cell information of the
intra-freq measurement should include the Primary CPICH Power for this cell. Otherwise
the cell information of the intra-freq measurement should not include the Primary CPICH
Power for this cell.
4.1.3
4.1.3.1
42
geographical location of adjacent cells. For example, for the configuration of cells
adjacent to the innermost gray cell, there are three layers of adjacent cells surrounding
the gray cell, and they are differentiated from one another with yellow (0: Top priority),
blue (1: Medium priority) and red (2: Low priority).
Figure 4-2
Source Cell
Priority 0
Priority 1
Priority 2
4.1.3.2
If a cell is adjacent to several cells in the active set, that is, the priority levels configured
for this cell may vary, the priority levels of this cell are combined and the highest priority
is taken as the priority of the cell.
Sorting strategy
If the total number of adjacent cells in the active set is 32, the system prioritizes them in
descending order and places the cells in excess of 32 into the adjacent cell reserve list,
43
4.2
44
4.3
4.3.1
NA
10 LogMNew CIONew W 10 Log Mi (1 W) 10 LogMBest (R1a H1a /2)
i1
The meanings of all parameters are described as follows:
R1a: Refers to the reporting range of Event 1A. It is used to control the extent of difficulty
in adding a cell into the active set (RptRange [MAX_INTRA_MEAS_EVENT] (For
event-triggered measurements, if the measurement quantity is EcNo, this parameter is
obtained from UIntraEcNoEvMeas, if the measurement quantity is RSCP, this parameter
is obtained from UIntraRscpEvMeas. For detected set measurements, if the
measurement quantity is EcNo, this parameter is obtained from UIntraEcNoEvMeasForD,
if
the
measurement
quantity
is
RSCP,
this
parameter
is
obtained
from
UIntraRscpEvMeasForD)).
H1a: Refers to the reporting hysteresis of Event 1A. It is used to control the extent of
difficulty in adding a cell into the active set (Hysteresis[MAX_INTRA_MEAS_EVENT]
(For event-triggered measurements, the measurement quantity is EcNo, this parameter
is obtained from UIntraEcNoEvMeas, if the measurement quantity is RSCP, this
parameter is obtained from UIntraRscpEvMeas. For detected set measurements, if the
measurement quantity is EcNo, this parameter is obtained from UIntraEcNoEvMeasForD,
if
the
measurement
quantity
is
RSCP,
this
parameter
is
obtained
from
UIntraRscpEvMeasForD)).
MNew: Refers to the measurement of the to-be-evaluated cell outside the active set.
CIONew: Refers to the offset of the cell outside the active set in relation to other cells
(CellIndivOffset (UUtranRelation)).
45
Mi: Refers to the mean measurement value of the cells other than the best cell in the
active set.
NA: Refers to the number of cells other than the best cell in the active set.
MBest: Refers to the measurement of the best cell in the active set.
W: Refers to the weight (W[MAX_INTRA_MEAS_EVENT] (For event-triggered
measurements, if the measurement quantity is EcNo, this parameter is obtained from
UIntraEcNoEvMeas., if the measurement quantity is RSCP, this parameter is obtained
from UIntraRscpEvMeas. For detected set measurements, if the measurement quantity
is EcNo, this parameter is obtained from UIntraEcNoEvMeasForD, if the measurement
quantity is RSCP, this parameter is obtained from UIntraRscpEvMeasForD)) of the best
cell to the rest cells in the active set in evaluation standards.
From the formula, it can be concluded that the probability of triggering Event 1A can be
increased by either increasing R1a (Event 1A meets the reporting range conditions) or
decreasing H1a (Decision hysteresis range. Otherwise, probability of triggering Event 1A
can be reduced.
Event 1A supports event-triggered periodical reporting, that is, once Event 1A meets the
reporting range of quality standards, the UE reports Event 1A periodically
(EvtRptInterval[MAX_INTRA_MEAS_EVENT] (For event-triggered measurements, if the
measurement quantity is EcNo, this parameter is obtained from UIntraEcNoEvMeas, if
the measurement quantity is RSCP, this parameter is obtained from UIntraRscpEvMeas.
For detected set measurements, if the measurement quantity is EcNo, this parameter is
obtained from UIntraEcNoEvMeasForD, if the measurement quantity is RSCP, this
parameter is obtained from UIntraRscpEvMeasForD)) until this event does not meet
reporting conditions or the reporting times reach the maximum allowed times
(EvtRptAmount[MAX_INTRA_MEAS_EVENT] (For event-triggered measurements, if the
measurement quantity is EcNo, this parameter is obtained from UIntraEcNoEvMeas, if
the measurement quantity is RSCP, this parameter is obtained from UIntraRscpEvMeas.
For detected set measurements, if the measurement quantity is EcNo, this parameter is
obtained from UIntraEcNoEvMeasForD, if the measurement quantity is RSCP, this
parameter is obtained from UIntraRscpEvMeasForD)).
46
There is a restriction on the number of radio links in active set, so Event 1A will not be
reported once the number of cells in the active set reaches the threshold
(RptDeactThr[MAX_INTRA_MEAS_EVENT](For event-triggered measurements,, if the
measurement quantity is EcNo, this parameter is obtained from UIntraEcNoEvMeas, if
the measurement quantity is RSCP, this parameter is obtained from UIntraRscpEvMeas.
For detected set measurements, if the measurement quantity is EcNo, this parameter is
obtained from UIntraEcNoEvMeasForD, if the measurement quantity is RSCP, this
parameter is obtained from UIntraRscpEvMeasForD)).
4.3.2
NA
10 LogMOld CIOOld W 10 Log Mi (1 W) 10 LogMBest (R1b H1b /2)
i1
R1b: Refers to the reporting range of Event 1B. It is used to control the extent of difficulty
in dropping a cell from the active set (RptRange [MAX_INTRA_MEAS_EVENT] (For
event-triggered measurements, if the measurement quantity is EcNo, this parameter is
obtained from UIntraEcNoEvMeas, if the measurement quantity is RSCP, this parameter
is obtained from UIntraRscpEvMeas. For detected set measurements, if the
measurement quantity is EcNo, this parameter is obtained from UIntraEcNoEvMeasForD,
if
the
measurement
quantity
is
RSCP,
this
parameter
is
obtained
from
UIntraRscpEvMeasForD)).
H1b Refers to the reporting hysteresis of Event 1B. It is used to control the extent of
difficulty in dropping a cell from the active set (Hysteresis[MAX_INTRA_MEAS_EVENT]
(For event-triggered measurements, if the measurement quantity is EcNo, this parameter
is obtained from UIntraEcNoEvMeas, if the measurement quantity is RSCP, this
parameter is obtained from UIntraRscpEvMeas. For detected set measurements, if the
measurement quantity is EcNo, this parameter is obtained from UIntraEcNoEvMeasForD,
if
the
measurement
quantity
is
RSCP,
this
parameter
is
obtained
from
UIntraRscpEvMeasForD)).
47
MOld: Refers to the measurement of the to-be-evaluated cell in the active set.
CIOOld: Refers to the offset of the cell in active set in relation to other cells
(CellIndividualOffset (UUtranCellFDD)).
Mi: Refers to the mean measurement value of the cells other than the best cell in the
active set.
NA: Refers to the number of cells other than the best cell in the active set.
MBest: Refers to the measurement of the best cell in the active set.
W: Refers to the weight (W[MAX_INTRA_MEAS_EVENT] (For event-triggered
measurements, if the measurement quantity is EcNo, this parameter is obtained from
UIntraEcNoEvMeas, if the measurement quantity is RSCP, this parameter is obtained
from UIntraRscpEvMeas. For detected set measurements, if the measurement quantity
is EcNo, this parameter is obtained from UIntraEcNoEvMeasForD, if the measurement
quantity is RSCP, this parameter is obtained from UIntraRscpEvMeasForD)) of the best
cell to the rest cells in the active set in evaluation standards.
From the above formula, it can be concluded that the probability of triggering Event 1B
can be decreased by either increasing R1b (Event 1B meets the reporting range
conditions) or decreasing H1b (Decision hysteresis range). Otherwise, the probability of
triggering Event 1B can be increased.
4.3.3
48
the
measurement
quantity
is
RSCP,
this
parameter
is
obtained
from
UIntraRscpEvMeasForD)).
MNew: Refers to the measurement of the to-be-evaluated cell outside the active set.
MInAS: Refers to the cell with poorest quality in the active set.
CIONew: Refers to the offset of the to-be-evaluated cell outside the active set in relation to
other cells (CellIndivOffset (UUtranRelation)).
CIOInAS: Refers to the offset of cell with poorest quality in the active set in relation to other
cells (CellIndividualOffset (UUtranCellFDD)).
From the above formula, it can be concluded that the probability of triggering Event 1C
can be decreased by increasing H1c (decision hysteresis range). Otherwise, the
probability of triggering Event 1C can be increased.
Event 1C supports event-triggered periodical reporting, that is, once Event 1C meets the
reporting range of quality standards, the UE will report Event 1C periodically
(EvtRptInterval[MAX_INTRA_MEAS_EVENT](For event-triggered measurements,, if the
measurement quantity is EcNo, this parameter is obtained from UIntraEcNoEvMeas, if
the measurement quantity is RSCP, this parameter is obtained from UIntraRscpEvMeas.
For detected set measurements, if the measurement quantity is EcNo, this parameter is
obtained from UIntraEcNoEvMeasForD, if the measurement quantity is RSCP, this
parameter is obtained from UIntraRscpEvMeasForD)) until this event does not meet
reporting conditions or the reporting times reach the maximum allowed times
(EvtRptAmount[MAX_INTRA_MEAS_EVENT] (For event-triggered measurements, if the
measurement quantity is EcNo, this parameter is obtained from UIntraEcNoEvMeas, if
the measurement quantity is RSCP, this parameter is obtained from UIntraRscpEvMeas.
For detected set measurements, if the measurement quantity is EcNo, this parameter is
obtained from UIntraEcNoEvMeasForD, if the measurement quantity is RSCP, this
parameter is obtained from UIntraRscpEvMeasForD)).
49
To ensure the gain of macro diversity, the reporting of Event 1C is only allowed when the
number of cells in the active set reaches a certain threshold (RplcActThr
[MAX_INTRA_MEAS_EVENT] (If the measurement quantity is EcNo, this parameter is
obtained from UIntraEcNoEvMeas. If the measurement quantity is RSCP, this parameter
is obtained from UIntraRscpEvMeas)).
4.3.4
A cell is added into the active set (The cell outside the active set reports Event 1D
and the number of links in the active set does not reach the maximum limit).
The cell with poor quality in the active set is replaced (The cell outside the active set
reports Event 1D but the number of links in the active set reaches the maximum
limit).
When the cell meets the conditions in the following formula, the UE reports Event 1D to
the RNC:
50
the
measurement
quantity
is
RSCP,
this
parameter
is
obtained
from
UIntraRscpEvMeasForD)).
From the above formula, it can be concluded that the probability of triggering Event 1D
can be decreased by increasing H1d (decision hysteresis range). Otherwise, the
probability of triggering Event 1D can be increased.
4.3.5
If there is a neighboring relationship between the target cell and the best cell, the
CIO is CellIndivOffset (For a UTRAN cell, this parameter is obtained from
UUtranRelation. For a GSM cell, this parameter is obtained from UExternalGsmCell)
selected from the best cell. If there is not any neighboring relationship between the
target cell and the best cell, the CIO is the minimum absolute value of
CellIndivOffset selected from the cells in the active set. If there is not any
neighboring relationship between the target cell and the cells in the active set, the
CIO is set to zero.
If the target cell is the best cell, the CIO is CellIndividualOffset (UUtranCellFDD)
selected from the serving cell.
If the best cell changes, the RNC will inform UEs to update the CIO.
51
4.3.6
quantity
is
EcNo,
this
parameter
is
obtained
from
meets
this
reporting
range
condition
within
Time-To-Trigger mechanism
Measurement
quantity
P CPICH 1
RptRange
[MAX_INTRA_
MEAS_EVENT]
P CPICH 2
P CPICH 3
TrigTime[MAX_INTRA_MEAS_EVENT]
Reporting
event 1A
4.3.7
Time
52
1.
If the current service is a DCH service, R99, R5+R99, and R6+R5+R99 cells can be
in the same active set.
2.
If the current service is an HS/D service, R99, R5, R6+R5, R5+R99, and
R6+R5+R99 cells can be in the same active set.
3.
If the current service is an HS/E service, R6+R5 and R6+R5+R99 cells can be in the
same active set.
4.
4.3.8
Links are added into the active set if the number of links in the DCH active set is
less than 3. Event 1A will not be processed if the total number of links in the active
set reaches the maximum limit.
If a link to be added into the active set is rejected in Event 1A, the handover
punishment timer (5s) is initiated, so that Event 1A reported by this rejected cell will
not be processed until the timer expires.
If the cell reporting Event 1A is the target cell traced by the detected set, no link will
be added into the active set. For details, see Detected set Tracing.
If the measurement report contains several target cells, the cell with best quality
(EcNo) will be selected as the target cell to be added in the active set.
If the cell reporting Event 1A is the cell of the SRNC side, and the parallel softer
handover switch of Iub and Uu ParallelSoftHO is open, the RL ADD procedure of
the Iub interface and the ACTIVE SET UPDATA procedure of the Uu interface will
be processed in parallel.
Processing of Event 1B
The link of the related cell is deleted based on Event 1B reported by the UE.
53
If the measurement report contains several target cells, the cell with worst quality
(EcNo) will be selected as the target cell to be deleted from the active set.
Processing of Event 1C
The cell is replaced if the radio links in the active set are equal to 3.
If a link to be added into the active set is rejected in Event 1C, the handover
punishment timer is initiated, so that Event 1C reported by this rejected cell will not
be processed until the timer expires.
The parallel processing of the Iub and Uu interfaces when adding a radio link in
softer handover is the same as that of Event 1A.
Processing of Event 1D
If the cell triggering Event 1D is an intra-frequency adjacent cell outside the active
set, and if the criterion described in 4.3.14 Scenarios of Intra-Frequency Hard
Handover is fulfilled, the RNC will perform an intra-frequency hard handover.
If the cell triggering Event 1D is an intra-frequency adjacent cell outside the active
set, and if the DCH active set is full, Event 1D will be processed as Event 1C. If the
DCH active set is not full, Event 1D will be processed as Event 1A. If event 1A or 1C
fails due to admission control failure, the RNC will perform an intra-frequency hard
handover.
If the cell triggering Event 1D is inside the active set, the best cell in the active set
changes.
4.3.8.1
54
4.3.8.2
55
vendors equipment. In response, the SRNC executes Special Events Handling via IUR
for CS+PS if the following conditions are met:
(1). RncFeatSwitchBit15 is set to 0.
(2). Concurrent services exist and include CS+PS services, being indexed to the
configuration of Multi RAB Including CS and PS.
If these conditions are met, the SRNC will not process Event 1A/1C/1D of the DRNC's
cells.
4.3.8.3
4.3.8.4
56
4.3.9
4.3.9.1
4.3.9.2
57
4.3.10
(srvCategory
(UIntraMeasSrvSpec)), see
4.1.2.4
Parameter
Configuration
Strategies.).
4.3.10.1
The measurement of detected set tracing is controlled through the detected set
tracing task in the performance measurement of the OMCR. A detected set
measurement is started after a detected set tracing task is created and initiated if
the parameter NbrCellMonSupInd (ULogicalRnc) is 1. During the configuration of
the measurement control, Triggering condition 2 is set to Detected set cells, and
Reporting cell status is set to Report cells within detected set on used frequency.
2.
The measurement parameters of the detected set are indexed to the cell, and the
parameters of the best cell will be selected in macro diversity state. If the
parameters of the best cell are different from those used by the UE, the
measurement information needs to be modified through the measurement control
message.
3.
After the detected set tracing task stops, the detected set tracing is disabled and the
related measurement task is released.
4.3.11
58
6F event: The UE Rx-Tx time difference for a link in the active set is greater than an
absolute threshold.
6G event: The UE Rx-Tx time difference for a link in the active set is less than an
absolute threshold.
The rlRefTimeAjtSw (ULogicalRnc) parameter controls the policy of the UE Rx-Tx
time difference in macro diversity. If the switch is on, the RNC removes the
corresponding link from macro diversity when the UE reports a 6F or 6G event
(indicating that the downlink receiving time falls out of the UE transmitting time
window). If the switch is off, the function is disabled.
4.3.11.1
When the radio link reference time adjustment switch of the best cell
(rlRefTimeAjtSw (ULogicalRnc)) is on and the number of links in macro diversity
changes from one to multiple, the 6F/6G measurement parameters will be issued to
the
UE.
Furthermore,
the
parameter
TxRxTDThres
reporting
threshold
in
chips
in
event
6F/6G.
The internal measurement parameters (6F/6G) of the UE are configured per cell
according to the index, and are subject to the parameters of the best cell. When the
UE internal measurement parameters are obtained, profileId (UUeIntMeasProfile) of
the cell is found based on refUUeIntMeasProfile (UUtranCellFDD), and then
according to the current measurement purpose UE Rx-Tx Time Difference Event
Measurement for RL Timing Adjustment, the managed object URlEvtRttUeInt is
obtained from UUeIntMeasProfile configuration items. Finally, the internal
59
ueIntMCfgNo(URlEvtRttUeInt)
MeasRptTrMod(URlEvtRttUeInt)
Filter coefficient
FilterCoeff(URlEvtRttUeInt)
MeaEvtId(URlEvtRttUeInt)
3.
When the number of links in macro diversity changes from multiple to one and the
internal measurement function (6F/6G) is enabled on the UE, a release of internal
measurement will be triggered on the UE.
4.3.12
60
For DCH users, if the GBR of DCH users is higher than the rate limitation
RtMaxUlRateDch / RtMaxDlRateDch of the new neighboring cell, it does not add a radio
link. Otherwise, it adds a radio link.
For EDCH users, if the rate of E-DCH users is higher than the E-DCH rate limitation
RtMaxRateEdch / NrtMaxRateEdch of the new neighboring cell, it reduces E-DCH
Maximum Bitrate by radio link reconfiguration, and then adds the corresponding
neighboring cell into macro diversity.
For DCH users, a radio link is deleted from macro diversity. If the UE rate is less than the
DCH rate limitation of the cells in macro diversity, the RNC will perform RB
reconfiguration.
For E-DCH users, a radio link is deleted from macro diversity. If the UE rate is less than
E-DCH rate limitation of the cells in macro diversity, the RNC will perform RL
reconfiguration to enhance E-DCH Maximum Bitrate.
4.3.13
61
handover. Otherwise, the UE does not perform any handover. If a DRNC cell
reported has no configuration relationship with SRNC cells, the cell supports CS64k
by default.
4.3.14
The intra-frequency measurement report excludes the OFF and TM of the target
cell.
The types of the target and source cells are different, for example, the UE is handed
over from a DCH-capable cell to an HSPA-capable cell.
The signal RB is carried on HS-DSCH in the active cell, while F-DPCH is not
supported in the adding target cell
The capability of the target cell is not consistent with that of the source cell,
including:
The UE uses transmit diversity in an active set cell, but the target cell does not
support transmit diversity.
The UE uses multi-user detection in an active set cell, but the target cell does not
support multi-user detection
The UE uses DTX-DRX in an active set cell, but the target cell does not support the
capability
Uplink 16QAM is configured but the target cell does not support it
A TTI 2ms service is set up in the source cell, but the target cell does not support
The transmission delay TimeDelay(UIubLink) reported during an intra-frequency
handover for the Node B where the neighboring cell of the current RNC resides is
62
inconsistent with the transmission delay of the cells in the current active set, or the
transmission
delay
ATimeDelay(UExternalUtranCellFDD)
reported
during
intra-frequency handover for the neighboring cell that is a DRNC cell is inconsistent
with the transmission delay of the cells in the current active set.
There are two synchronization modes for intra-frequency hard handover: Timing
re-initialised and Timing-maintained, which are controlled by the parameter
gRESPARA47.bit14 (URncFunction).
4.3.15
1B
1C
1D
the
scrambling
code in the
new 1A event
is
identical
with that in
the
New
1A
measurement
old
event,
the
1A
then
old
event
report
replaced
1A
The 1A event
is cached.
The 1A event
is cached.
is
by
is
cached.
1B
The 1B event
The old 1B
event
is
1B event is
If
the
scrambling
63
1B
replaced
1C
by
1D
cached
code in the
1B event is
identical with
the
existing
by
the 1B event.
Otherwise,
the 1B event
is cached.
If
the
replaced
scrambling
code in the
1C event is
identical with
1C
The old 1C
the
The 1C event
event
one in the 1D
is cached.
replaced
is
by
existing
event,
then
the 1D event
is
replaced
by
the
1C
event.
Otherwise,
the 1C event
is cached.
1D
The 1D event
is cached.
If scrambling
If
code in the
scrambling
1D event is
code in the
identical with
1D event is
the
in
identical with
the 1B event,
the replaced
then the 1B
scrambling
event
code in the
one
replaced
is
by
1C
the
The old 1D
event
replaced
is
by
event,
the 1D event.
then the 1C
Otherwise,
event
is
64
1B
1C
1D
the 1D event
replaced
by
is cached.
the 1D event.
Otherwise,
the 1D event
is cached.
4.4
4.4.1
Node B
Drift RNS
Drift
RNC
Serving
RNC
Decision to setup
new RL
RNSAP
NBAP
1. Radio Li nk Setup
Request
RNSAP
NBAP
Start RX
description
NBAP
NBAP
4. Radio Link Setup
Response
RNSAP
NBAP
RN SAP
NBAP
RNSAP
RNSAP
8. Downlink Synchronisation
DCH - FP
DCH - FP
DCH - FP
9. Uplink Synchronisation
DCH - FP
Start TX
description
10. DCCH : Active Set Update
RRC
RRC
[Radio Link Addition]
11. DCCH : Active Set Update Complete
RRC
RRC
65
4.4.2
Node B
Drift RNS
Drift
RNC
Serving
RNC
Decision to delete
old RL
RRC
[Radio Link Deletion]
2. DCCH : Active Set Update Complete
RRC
RRC
RNSAP
NBAP
NBAP
Stop RX and TX
NBAP
NBAP
RNSAP
66
4.4.3
N ode B
S ervin g R N S
D rift
RNC
S erving
RNC
D ecisio n to setup
new R L and
release o ld R L
RN SAP
NBAP
1 . R ad io L ink S etup
R eq uest
RN SAP
NBAP
S tart R X
d escrip tio n
NBAP
NBAP
RN SAP
4 . R ad io L ink S etup
R esp o nse
7 . R ad io L ink R esto re
Ind icatio n
D C H -F P
D C H -F P
RN SAP
RN SAP
D C H -F P
D C H -F P
S tart T X
d escrip tio n
1 0 . D C C H : A ctive S et U p d ate C o m m and
RRC
RRC
[R a d io L in k A d d itio n & D eletio n ]
RRC
NBAP
RRC
NBAP
S to p R X and T X
NBAP
NBAP
67
4.4.4
UE
NODEB2
NODEB1
RNC
68
4.4.5
UE
Node B
Source
Node B
Target
RNC
Source
RNC
target
SRNC
1. Radio Link
Setup Request
RNSAP
NBAP
NBAP
NBAP
RNSAP
NBAP
RNSAP
RNSAP
RRC
NBAP
NBAP
RNSAP
NBAP
RNSAP
NBAP
RNSAP
11. RL Restore
Indication
RNSAP
RRC
RNS AP
NBAP
NBAP
RNSAP
NBAP
NBAP
RNSAP
RNSAP
If the cells belonging to different RNCs are adjacent and the lur interface is available, the
SRNC performs an inter-RNC hard handover. An SRNC relocation is triggered after the
hard handover.
69
4.4.6
N ode B
T a rg e t
RNC
S o u rc e
RANAP
RNC
T a rg e t
M S C /S G S N
1 . R e lo c a tio n R e q u ire d
RANAP
2 . R e lo c a tio n R e q u ire d
RANAP
RANAP
S G S N /M S C
RANAP
3 . R e lo c a tio n R e q u e st
RANAP
4 . R e lo c a tio n R e q u e st
RANAP
RANAP
5 . A L C A P Iu D a ta
T ra n sp o rt B e a re r S e tu p
NBAP
NBAP
6 . R a d io L in k S e tu p R e q u e st
NBAP
7 . R a d io L in k S e tu p R e sp o n se
NBAP
8 . A L C A P Iu b D a ta T ra n sp o rt B e a re r S e tu p
9 . R e lo c a tio n R e q u e st
A c k n o w le d g e
RANAP
RANAP
1 0 . R e lo c a tio n R e q u e st
A c k n o w le d g e
RANAP
RANAP
1 1 . R e lo c a tio n C o m m a n d
RRC
NBAP
RANAP
1 2 . R e lo c a tio n C o m m a n d
RANAP
1 3 . D C C H : P h ysic a l C h a n n e l R e c o n fig u ra tio n N o te 1
NBAP
1 5 . R e lo c a tio n
D e te c t
RANAP
1 6 . R e lo c a tio n D e te c t
RRC
1 7 . R a d io L in k F a ilu re In d ic a tio n
RANAP
RRC
1 4 . R a d io L in k R e sto re In d ic a tio n
RANAP
NBAP
RANAP
RANAP
RANAP
NBAP
RRC
RANAP
1 9 . R e lo c a tio n
C o m p le te
RANAP
RANAP
RANAP
RANAP
2 0 . R e lo c a tio n C o m p le te
2 1 . Iu R e le a se C o m m a n d
2 2 . Iu R e le a se C o m m a n d
RANAP
RANAP
RANAP
2 3 . A L C A P Iu D a ta T ra n sp o rt B e a re r
R e le a se
RANAP
RANAP
2 4 . Iu R e le a se C o m p le te
2 5 . Iu R e le a se C o m p le te
RANAP
RANAP
If inter-frequency cells between RNCs are adjacent and the lur interface is unavailable,
the hard-handover-triggered SRNS relocation is performed. The procedure is described
as follows:
The SRNC sets up a radio link at the DRNC through an lu interface relocation, and then
reconfigure the UE to a cell of the DRNC through a relocation. Upon receiving the
reconfiguration response message from the UE, the DRNC informs the CN to complete
70
the relocation and changes into SRNC. The CN then releases the resources of the UE at
the original SRNC through the lu interface release command.
71
another cell, the relation between them is called Covers). The blind handover based on
ShareCover (Overlap or Covers) is primarily used in load control, load balancing and
handover based on moving speed.
In the load balancing mechanism, if the load of the target cell for access or
handover is too heavy, you can access or hand over the service into another less
loaded cell that has ShareCover (Overlap or Covers) relation with the target cell.
In the load control mechanism, if the load of the current cell is too heavy, you can
forcedly hand over partial services into another less loaded cell that has
ShareCover (Overlap or Covers) relation with the target cell.
In a handover based on the moving speed, when the UE changes from a low to a
high moving speed, the UE can be directly handed over from a micro cell into a
macro cell that contains this micro cell.
5.1
Inter-Frequency Measurement
When conducting an inter-frequency measurement, the UE needs to implement layer 3
filter for the measurement results to avoid measurement fluctuations, and then make
event decisions and reports by using filtered values. The layer 3 filter factor is FilterCoeff
(If the measurement is an event-triggered measurement and the measurement quantity
is EcNo, for Event 2D/2F used for the EUTRAN system, this parameter is obtained from
UInterEcNoEvMeasforE. For Event 2D/2F used for the GSM system, this parameter is
obtained from UInterEcNoEvMeasforG. For inter-frequency measurement events used
for the UTRAN system, this parameter is obtained from UInterEcNoEvMeasforU. If the
measurement is an event-triggered measurement and the measurement quantity is
RSCP, for Event 2D/2F used for the EUTRAN system, this parameter is obtained from
UInterRscpEvMeasforE. For Event 2D/2F used for the GSM system, this parameter is
obtained from UInterRscpEvMeasforG. For inter-frequency measurement events used
for the UTRAN system, this parameter is obtained from UInterRscpEvMeasforU. If the
measurement is a periodical measurement and the measurement quantity is EcNo, this
parameter is obtained from UInterEcNoPrdMeas. If the measurement quantity is RSCP,
this parameter is obtained from UInterRscpPrdMeas). For the inter-frequency
measurement formula, see Intra-frequency Measurement.
72
NA j
Where,
Qfrequency j: Refers to the (virtual) active set quality of carrier j, that is, the measurement
result of carrier j (dB for Ec/No; dBm for RSCP).
Mfrequency j: Refers to the physical measurement value (ratio for Ec/No; mW for RSCP) of
the (virtual) active set of carrier j.
Mi j: Refers to the physical measurement value of cell i of carrier j.
NA j: Refers to the number of cells (excluding the best cell) in the (virtual) active set of
carrier j.
MBest j: Refers to the measurement result of the best cell in the (virtual) active set of
carrier j.
Wj: Refers to the weight (WNoUsed (If the measurement quantity is EcNo, this parameter
is obtained from UInterEcNoEvMeasforU. If the measurement quantity is RSCP, this
parameter is obtained from UInterRscpEvMeasforU) or Wused (If the measurement
quantity is EcNo, for Event 2D/2F used for the EUTRAN system, this parameter is
obtained from UInterEcNoEvMeasforE. For event 2D/2F used for the GSM system, this
parameter is obtained from UInterEcNoEvMeasforG. For inter-frequency measurement
events
used
for
the
UTRAN
system,
this
parameter
is
obtained
from
UInterEcNoEvMeasforU. If the measurement quantity is RSCP, for Event 2D/2F used for
the EUTRAN system, this parameter is obtained from UInterRscpEvMeasforE. For event
2D/2F
used
for
the
GSM
system,
this
parameter
is
obtained
from
73
5.1.1
the
measurement
quantity
is
RSCP,
this
parameter
is
obtained
from
2b
H2b /2
Where,
74
QNon used: Refers to the measurement result of the current non-working carrier frequency.
TNon used 2b: Refers to the absolute threshold (ThreshNoUsedFreq (If the measurement
quantity is EcNo, this parameter is obtained from UInterEcNoEvMeasforU. If the
measurement
quantity
is
RSCP,
this
parameter
is
obtained
from
the
measurement
quantity
is
RSCP,
this
parameter
is
obtained
from
quantity
is
RSCP,
this
parameter
is
obtained
from
the
measurement
quantity
is
RSCP,
this
parameter
is
obtained
from
75
Event 2D: The quality of the working carrier frequency is lower than a threshold.
2e
H2e /2
Where,
QNon used: Refers to the measurement result of the current non-working carrier frequency.
76
TNon used 2e: Refers to the absolute threshold (ThreshNoUsedFreq (If the measurement
quantity is EcNo, this parameter is obtained from UInterEcNoEvMeasforU. If the
measurement
quantity
is
RSCP,
this
parameter
is
obtained
from
the
measurement
quantity
is
RSCP,
this
parameter
is
obtained
from
77
system, this parameter is obtained from UInterRscpEvMeasforG. For Event 2F used for
the UTRAN system, this parameter is obtained from UInterRscpEvMeasforU)) of Event
2F.
If a carrier frequency meets the reporting range or threshold of a certain event, the
condition must be met within a period of time (TrigTime (If the measurement quantity is
EcNo, for Event 2D/2F used for the EUTRAN system, this parameter is obtained from
UInterEcNoEvMeasforE. For Event 2D/2F used for the GSM system, this parameter is
obtained from UInterEcNoEvMeasforG. For inter-frequency measurement events used
for the UTRAN system, this parameter is obtained from UInterEcNoEvMeasforU. If the
measurement quantity is RSCP, for Event 2D/2F used for the EUTRAN system, this
parameter is obtained from UInterRscpEvMeasforE. For Event 2D/2F used for the GSM
system, this parameter is obtained from UInterRscpEvMeasforG. For inter-frequency
measurement events used for the UTRAN system, this parameter is obtained from
UInterRscpEvMeasforU)) before the reporting of this event to avoid an inter-frequency
event misreport due to the fluctuation of radio quality.
5.1.2
5.1.2.1
Measurement Setup
An inter-frequency measurement is only set up only when the inter-RAT measurement is
not initiated, and it can be triggered in either of the following scenarios:
1.
The radio quality of the current serving carrier frequency deteriorates and there are
inter-frequency adjacent cells that have no ShareCover (Covers) relation (judged
78
The UE meets the slow moving conditions and there is a micro cell with higher HCS
level in the coverage of the current cell (based on moving speed).
The Radio Quality Deterioration of Current Serving Carrier Frequency can be judged
through any of the following four indexes:
Uplink BLER: The uplink BLER value exceeds a certain threshold (1.25%) and the
Sirtarget value (real-time measurement result) reaches the maximum value of SIR
(ULMaxSIR) configured in the OMCR. The BLER is measured and judged by the
RNC.
Uplink transmit power of UE: The transmit power of the UE exceeds a certain
threshold (100%, in relation to the maximum transmit power of the UE). The uplink
transmit power is measured by the UE and reported to the RNC through the internal
measurement report 6A/6B. The threshold parameter of Event 6A and Event 6B
(txPowerThres(UHoEvtTPUeInt)) is a delta value relative to min(UE maximum
transmitted power, uplink DPCH maximum transmission power).
Downlink transmit power: The downlink transmit power exceeds a certain threshold
(90%, in relation to MaxDlDpchPwr of services). The downlink transmit power is
measured by the Node B and reported to the RNC through the dedicated Node B
measurement report.
5.1.2.2
Measurement Modification
If the inter-frequency measurement is enabled, an inter-frequency measurement
modification is triggered in the following cases:
79
5.1.2.3
Measurement Deletion
When the following inter-frequency measurement setup conditions are no longer met, the
corresponding inter-frequency measurement will be deleted (released).
There is no inter-frequency adjacent cell in the active set after a handover and
inter-frequency measurement is initiated.
80
report for the ID, it compares the current time and the recorded time. If the difference
between the current time and the recorded time exceed the threshold TResndMeaCtrlRel
(URncFunction) configured, the MEASUREMENT CONTROL RELEASE will be resent.
Otherwise, this measurement report will be ignored.
5.1.2.4
If a measurement report contains several target cells, those with good quality
(RSCP) are preferentially selected as target cells. If there is any inter-frequency
adjacent cell that has ShareCover (Overlap or Covers) relation with the target cell,
inter-frequency load balancing is performed based on the cells load. (For details,
see ZTE UMTS Load Balance Feature Guide).
For PS users, a hard handover tends to fail due to admission failure in the event of
heavy cell load because a majority of resources are occupied by PS services. The
following strategies are required:
If the current channel type is DCH and the channel assigned for the target cell
is also DCH after a handover, a handover attempt is made first according to
the current rate. If the handover fails, another handover attempt is made
according to the GBR of the current services or the minimum rate grade of
DRBC (for details, see ZTE UMTS DRBC Algorithm Feature Guide), to
improve the handover success rate.
81
2.
Processing of Event 2D
3.
Processing of Event 2E
All non-working carrier frequencies report Event 2E, indicating that the radio quality
of all inter-frequency adjacent cells is poor and the 3G system quality deteriorates. If
there is any Inter-RAT adjacent cell that has cover relation (GsmShareCover
(UGsmRelation) value is 2 GSM neighboring cell covers the serving cell) with the
current serving cell, an inter-RAT blind handover is implemented.
All non-working carrier frequencies report Event 2E, indicating that the radio quality
of all inter-frequency adjacent cells is poor and the 3G system quality deteriorates. If
the serving cell does not have any inter-RAT neighboring cell with cover relation
(GsmShareCover (UGsmRelation) value is not 2 GSM neighboring cell covers the
serving cell), an inter-RAT measurement Event 3A/3C is issued.
4.
Processing of Event 2F
82
5.1.2.5
2.
3.
If these conditions are met, the RNC will not process Event 2A/2B/2C reported by the
UE.
5.1.2.6
There are six inter-frequency measurement events and six inter-RAT measurement
events in the buffer at most.
For
event
2D/2F,
if
the
measurement
quantity
(NonIntraMeasQuan
(UUtranCellFDD)) is CPICH EcNo or CPICH RSCP, the RNC will only buffer the
measurement
events
NonIntraMeasQuan
with
the
same
(UUtranCellFDD).
measurement
If
the
quality
defined
measurement
by
quantity
83
If Event 2A/2B/2C/2E or 3A/3C measurement event exists in the buffer and the
newly
reported
Event
2F
has
the
same
measurement
quantity
as
5.1.2.7
84
Note:
When NonIntraMeasQuan (UUtranCellFDD) is configured to EcNo or RSCP,
only the 2D/2F events corresponding measurement quality are issued.
When NonIntraMeasQuan (UUtranCellFDD) is configured to EcNo and RSCP,
two categories of 2D/2F measurement events about CPICH EcNo and CPICH
85
RSCP are configured and one of 2D measurement events can trigger compressed
mode. After compressed mode is triggered, the inter-frequency event of the
corresponding measurement quantity will be issued according to that of 2D event.
For example, if the measurement quantity of triggering 2D event is CPICH EcNo,
only an inter-frequency event of CPICH EcNo will be issued.
Measurement reporting mode
Note:
(1)
When concurrent services exist and include CS+PS services, the Multi RAB
Including CS and PS configuration is indexed.
(2)
When concurrent services exist and include non-CS services, the RT RAB
Excluding Voice configuration is indexed.
(3)
When the above principles are met simultaneously, the first one prevails.
86
To facilitate
parameter
modification
and
optimization,
the
inter-frequency
Figure 5-1
UInterMeaSrvSpec(UInterMeaSrvSpe
c)
UInterMeasNoSrvSpec(UInterMeasNo
SrvSpec)
srvCategory
NonIntraMeasQuan
NonIntraMeasQuan
UInterEcNoEvM UInterRscpEvM
easforU(UInterE easforU(UInterR
cNoEvMeasforU scpEvMeasforU
)
)
UInterEcNoEvM UInterRscpEvM
easforG(UInterE easforG(UInterR
cNoEvMeasforG scpEvMeasforG
)
)
UInterEcNoEvM
easforG(UInterE
cNoEvMeasforE
)
UInterRscpEvM
easforG(UInterR
scpEvMeasforE)
UInterEcNoPrd
Meas(UInterEc
NoPrdMeas)
UInterEcNoPrd
Meas(UInterEc
NoPrdMeas)
InterMeasCfgNo InterMeasCfgNo
(UInterEcNoEv (UInteRscpEvM
easforU)
MeasforU)
InterMeasCfgNo InterMeasCfgNo
(UInterEcNoEv (UInteRscpEvM
MeasforG)
easforG)
InterMeasCfgNo
(UInterEcNoEv
MeasforE)
InterMeasCfgNo
(UInteRscpEvM
easforE)
interMeasCfgNo
(UInterEcNoPrd
Meas)
interMeasCfgNo
(UInterRscpPrd
Meas)
Note: When a new cell is set up, the value of intialHoCelSelScene (UInterMeasProfile)
(0:Outdoor Scene, 1:High-Mobility Outdoor Scene, 2:Indoor Scene, 3:Subway/tunnel
Scene) is determined according to the actual cell scene (indicated by HoCelSelScene
(UUtranCellFDD)), and the available inter-frequency measurement profile corresponding
to intialHoCelSelScene is configured for the cell.
Before
inter-frequency
(UInterMeasProfile)
of
handover
the
cell
is
parameters
found
based
are
on
obtained,
profileId
refUinterMeasProfile
87
In
the
managed
Configuration
No.
object
decided
above,
(InterMeasCfgNo)
is
Category(srvCategory(UInterMeaSrvSpec))
Inter-Frequency
found
based
and
Measurement
on
Traffic
Measurement
88
Switch
AMR
amrIfHoSw (ULogicalRnc)
R99 RT
r99RtIfHoSw (ULogicalRnc)
R99 NRT
r99NrtIfHoSw (ULogicalRnc)
HSDPA
hsdpaIfHoSw (ULogicalRnc)
HSUPA
hsupaIfHoSw (ULogicalRnc)
89
5.1.3
5.1.3.1
90
Figure 5-2
Source Cell
Priority 0
Priority 1
Priority 2
5.1.3.2
If a cell is adjacent to several inter-frequency cells in the active set, that is, the priority
levels configured for this cell may vary, the priority levels of this cell are combined and
the highest priority level prevails.
Sorting strategy
If the total number of inter-frequency adjacent cells in the active set is 32, the system
prioritizes them in descending order and places the cells in excess of 32 into the
inter-frequency adjacent cell reserve list, which can buffer at most 8 truncated
inter-frequency cells.
The priority levels of adjacent cells in the inter-frequency adjacent cell list will be updated
whenever Event 1A/1B/1C/1D is triggered. If Event 1B is triggered and the number of
91
inter-frequency adjacent cells is less than 32, the system selects cells from the reserve
list in descending order of priority and places them into the inter-frequency adjacent cell
list. The number of cells that can be selected: min (32 Number of existing cells in the
inter-frequency adjacent cell list, Number of cells in the reserve list).
5.2
the
measurement
quantity
is
EcNo,
this
parameter
is
obtained
from
92
5.3
mode
and
inter-frequency
measurement
setup/release,
see
5.4
93
5.5
obtaining
the
UEs
internal
measurement
parameters,
the
profileId
measRptTrMod(UHoEvtTPUeInt)
Filter Coefficient
filterCoeff(UHoEvtTPUeInt)
measEvtNum(UHoEvtTPUeInt)
meaEvtId(UHoEvtTPUeInt)
Time to Trigger(ms)
trigTime(UHoEvtTPUeInt)
When the transmit power of the UE meets these threshold requirements, the UE will
report the corresponding events. After receiving an Event 6A report (The uplink power of
the UE exceeds txPowerThres(UHoEvtTPUeInt)) or an Event 6B report (The uplink
power of the UE is less than txPowerThres(UHoEvtTPUeInt)), the RNC uses the same
processing strategy as that of 2D or 2F, respectively. For details, see the Events 2D and
2F processing strategies in Processing of Inter-Frequency Events.
94
5.6
DedMeasType (UNbDedMeas)
Time
Measurement Filter Coefficient
MeasFilterCoeff (UNbDedMeas)
Report Period
RptPrd(UNbDedMeas)
RptPrdUnit (UNbDedMeas)
Report Characteristics
RptType(UNbDedMeas)
Code Power
NbDed Measure Configuration No
NbDMCfgNo(UNbDedMeas)
When the DTCP value reaches the threshold of Event A, it indicates that the downlink
power is very high. In such a case, the UE is handed over to its inter-frequency adjacent
95
cell that has ShareCover (Covers) relation with the current cell, or an inter-frequency
measurement is initiated. The processing strategy is the same as that of Event 2D. When
the DTCP value reaches the threshold of Event B, the processing strategy is the same as
that of Event 2F. For details, see Event 2D/2F processing in Processing of
Inter-Frequency Events
5.7
5.8
96
reports.
5.9
Load control
Uplink BLER
Moving speed of UE
The load control-based handover aims to quickly reduce system loads and ensure
system stability, and it has the top priority. The handovers based on downlink coverage
events, uplink transmit power, uplink BLER or downlink transmit power aim to guarantee
the call QoS and user experience, and they have lower priority. The moving speed-based
handover in the HSC is used to appropriately allocate traffic for different cells, make full
use of system resources and enhance system performance. The moving speed-based
handover is a system optimization function and has the lowest priority.
The handover with top priority will shield the handovers with comparatively lower priority.
For example, if a load control-based handover occurs in a cell, the RNC can no longer
hand over or access new services into the cell. In the case of a poor carrier quality, the
RNC needs to hand over the UE into the cell with good quality through radio quality
measurement, without taking account of the moving speed of UE.
97
5.10
If
inter-frequency
neighboring
cells
exist,
the
parameters
of
is
EcNo,
the
parameters
are
obtained
from
are
obtained
from
UInterRscpEvMeasforU).
When
98
If only both GSM and EUTRAN neighboring cells exist, the parameters of
inter-RAT 2D/2F events are initially issued. When compressed mode is
activated, only RATx measurements according to ChoStraMulRatHo
(UCelInfoFDD) are issued by the RNC.
If both inter-frequency and inter-RAT neighboring cells exist, the RNC will
initially issue the parameters of inter-frequency 2D/2F events, and then
configure the inter-frequency measurement first when compressed mode
is activated and start the timer T4StpIfMeaActRat (URncFunction), when
a 2E event is reported or T4StpIfMeaActRat (URncFunction) expires, the
RNC will reconfigure the inter-frequency measurement to inter-RAT
measurement.
99
5.11
5.11.1
The RNC issues period measurement configuration for both inter-frequency and
inter-RAT measurements. (For details about issuing inter-frequency measurements or
100
b)
c)
When compressed mode is initiated by the value of service handover IE, if the
current frequency quality is good, only inter-RAT period measurement configuration
is issued and the corresponding compressed mode is activated. Otherwise, the
same strategy described in a) is performed.
Note:
1)
When the period measurement algorithm is used, Event 2D/2F is still reported by
using the event-triggered method.
2)
3)
101
5.11.2
(1). For inter-frequency measurements, the target cell is judged according to the Event
2C triggering rule.
QTarget_Freq_Cell+ CIOTarget_Freq_Cell>= TTarget_Freq_Cell+H/2
Where:
QTarget_Freq_Cell: Refers to the quality of the target carrier frequency.
CIOTarget_Freq_Cell: Refers to the cell individual offset of the target carrier frequency
especially defined for periodical measurement, whose value isCellIndivOffset
(UUtranRelation).
TTarget_Freq_Cell: Refers to the absolute threshold (ThreshNoUsedFreq (If the measurement
quantity is EcNo, this parameter is obtained from UInterEcNoEvMeasforU. If the
measurement
quantity
is
RSCP,
this
parameter
is
obtained
from
the
measurement
quantity
is
RSCP,
this
parameter
is
obtained
from
102
Where:
QTarget_Rat_Cell: Refers to the quality of the target system cell.
CIOTarget_Rat_Cell: Refers to the cell individual offset of the target system cell
(CellIndivOffset (UExternalGsmCell)).
TTarget_Rat_Cell: Refers to the absolute threshold of other systems (ThreshSys (for
E-UTRAN cell, if the measurement quantity is EcNo, this parameter is obtained from
URatEcNoEvMeasforE. If the measurement quantity is RSCP, this parameter is obtained
from URatRscpEvMeasforE; for GSM cell, if the measurement quantity is EcNo, this
parameter is obtained from URatEcNoEvMeasforG. If the measurement quantity is
RSCP, this parameter is obtained from URatRscpEvMeasforG));
H: Refers to the hysteresis parameter (Hysteresis (For E-UTRAN cells, if the
measurement quantity is EcNo, this parameter is obtained from URatEcNoEvMeasforE.
If
the
measurement
quantity
is
RSCP,
this
parameter
is
obtained
from
Note:
1)
5.12
103
Inter-RNC Mobility
6.1
SRNS Relocation
SRNS relocation can be categorized into relocation of UE not involved (soft
handover-triggering) and relocation of UE involved (hard handover-triggering),
depending on UE relevance.
It belongs to the soft handover relocation, and the UE can use radio resources in the
DRNC and connect with the CN through the SRNC. The triggering conditions are
described as follows:
links
are
handed
over
to
the DRNC,
the
timer
Relocation of UE involved
It belongs to the hard handover relocation. The triggering conditions are described as
follows:
104
If the UE has CS and PS services simultaneously and the DRNC of network vendor does
not support PS relocation, the PS services will be released before an SRNC relocation
with hard handover is performed when the parameter RncFeatSwitchBit4 is set to 1.
The CS service will begin relocation as soon as the PS service is released. As a result,
the CS service will be kept, but the PS service will be reestablished by the UE
automatically.
6.1.1
Source
RNC
Target
RNC
SGSN
1.Relocation Required
2.Relocation Request
3.Relocation Request Ack
4.Relocation Command
5.Relocation Commit
6.Relocation Detect
7.UTRAN Mobility
Information
8.UTRAN Mobility
Information Confirm
UE
9.Relocation Complete
10.Iu Release Command
11.Iu Release Complete
Procedure description:
1.
Upon detecting that all links already exist in a DRNC, the SRNC initiates the
relocation procedure and sends a Relocation Required message to the CN. If the
SRNC connects with CS and PS domains, it needs to send the Relocation
Required message to the CS and PS domains. When the SRNC sends the
Relocation Required message, it starts the timer Trelocprep(UIuCnst). Upon
receiving the Relocation Command message, the SRNC stops the timer and
terminates the Relocation Preparation procedure. If there is no response from the
105
The CN sends a Relocation Request message to the DRNC, carrying the RAB
SETUP IE.
3.
After the RAB of DRNC is established successfully, the DRNC sends a Relocation
Request Ack message to the CN.
4.
initiated
towards
the
SRNC
from
the
CN
before
the
expiry
of
The SRNC sends a Relocation Commit message to the DRNC through the lur
interface.
6.
The DRNC sends a Relocation Detect message to the CN and is converted into a
new SRNC through role exchange.
7.
8.
9.
The new SRNC sends a Relocation Complete message to inform the CN of the
successful relocation.
10. Upon receiving the message from the new SRNC, the CN sends an Iu Release
Command message to the original SRNC to release all the resources in the original
SRNC.
106
11. Upon releasing the lu resource, the original SRNC sends an Iu Release Complete
message to the CN.
There may be some exceptional procedures during a relocation.
Note:
Whether to initialize the RNC data forwarding function during a relocation can be
controlled
by
the
parameter
RncFeatSwitchBit25
(UIurLink).
When
107
6.1.2
Target
RNC
SGSN
1.Relocation Required
2.Relocation Request
3.Relocation Request Ack
5.Physical Channel
Reconfiguration
4.Relocation Command
UE
6.UE detected by target RNC
7.Relocation Detect
8.Physical Channel
Reconfiguration Complete
UE
9.Relocation Complete
10.Iu Release Command
11.Iu Release Complete
Procedure description:
1
Upon receiving the message, the CN sends a Relocation Request message to the
DRNC. When the SRNC sends the Relocation Required message, it starts the timer
Trelocprep(UIuCnst). Upon receiving the Relocation Command message, the
SRNC stops the timer and terminates the Relocation Preparation procedure. If there
is no response from the CN to the Relocation Required message before the timer
Trelocprep(UIuCnst) expires, the SRNC cancels the Relocation Preparation
procedure by initiating the Relocation Cancel procedure with the Cause Trelocprep
expiry.
After the bearer on the lu interface and the radio link are established, the DRNC
returns a Relocation Request Ack message to inform the CN that the DRNC is
ready.
The CN sends a Relocation Command message to the SRNC, requiring the SRNC
to start a relocation.
108
The DRNC initiates a UE Detect message to imply that the DRNC already detects
the UE.
Upon detecting the UE, the DRNC sends a Relocation Detect message to the CN,
and then the DRNC is converted into a new SRNC through role exchange.
Upon receiving the message, the new SRNC sends a Relocation Complete
message to the CN.
10 Upon receiving the message from the new SRNC, the CN sends a Iu Release
Command message to the original SRNC to release all the resources in the original
SRNC.
11
Upon releasing the lu resource, the original SRNC sends a Iu Release Complete
message to the CN.
109
6.2
DSCR
6.2.1
R99 DSCR
Like relocation, R99 DSCR is categorized into hard handover DSCR and soft handover
DSCR. The triggering conditions of R99 DSCR are described as follows.
No CS service is included.
6.2.2
No CS service is included.
HSPA DSCR
In response to the incompatibility that may occur when equipment from different vendors
is interconnected via IUR, the RNC introduces HSPA DSCR for HSPA S/I/B services. If
the switch RncFeatSwitchBit15 is 0, the RNC will not process 1A/1C events of the
DRNC's cells. When Event 1D of the DRNC's cells is reported, the RNC will perform a
hard handover DSCR. Otherwise, HSPA DSCR is the same as R99 DSCR.
110
6.2.3
6.3
If there are only PS services, when the conditions of DSCR are met, a DSCR
is performed.
6.4
6.4.1
111
6.4.2
112
enabled only when the current UTRAN system has poor radio quality. The radio quality of
the current UTRAN system can be measured by four indicators, namely, uplink BLER,
uplink transmit power of the UE, downlink transmit power, and inter-frequency
measurement (quality measurement on the PCPICH by the UE). When receiving the
inter-RAT measurement result reported by the UE, the RNC makes an inter-RAT
handover decision and handovers the UE to the target cell specified in the measurement
result.
7.1
Inter-RAT Measurement
To avoid measurement fluctuations, the UE must perform layer 3 filtering on the
measurement result, and then use the filtered value for event decision and reporting. The
FilterCoeff (If the measurement is an event-triggered measurement and the
measurement quantity is EcNo, this parameter is obtained from URatEcNoEvMeasforG.
If the measurement is an event-triggered measurement and the measurement quantity is
RSCP, this parameter is obtained from URatRscpEvMeasforG. For a periodical
measurement, if the measurement quantity is EcNo, this parameter is obtained from
URatEcNoPrdMeas. If the measurement quantity is RSCP, this parameter is obtained
from URatRscpPrdMeas) is used as the layer 3 filtering factor for intra-system
measurements, and the GsmFilterCoeff(For an event-triggered measurement, if the
measurement quantity is EcNo, this parameter is obtained from URatEcNoEvMeasforG.
If
the
measurement
quantity
is
RSCP,
this
parameter
is
obtained
from
NA
QUTRAN 10 LogMUTRAN W 10 Log Mi (1 W) 10 LogMBest
i1
Where:
QUTRAN indicates the measurement result of the currently used UTRAN frequency (dB for
Ec/No; dBm for RSCP).
113
MUTRAN indicates the measured physical value of the currently used UTRAN frequency
(ratio for Ec/No; mV for RSCP).
Mi indicates the measured physical value of cell I in the current active set.
NA indicates the number of the cells (excluding best cells) in the active set.
MBest indicates the measurement result of the best cells in the active set.
W (If the measurement quantity is EcNo, this parameter is obtained from
URatEcNoEvMeasforG. If the measurement quantity is RSCP, this parameter is obtained
from URatRscpEvMeasforG) indicates the weight of the best cells in the active set in the
frequency quality evaluation of the currently used UTRAN.
7.1.1
and
MOther
RAT
RAT
H3a /2
Where:
QUsed indicates the estimated quality of the used frequency of the UTRAN.
TUsed indicates the absolute threshold (Thresh (If the measurement quantity is EcNo, this
parameter is obtained from URatEcNoEvMeasforG. If the measurement quantity is
114
quantity
is
RSCP,
this
parameter
is
obtained
from
URatRscpEvMeasforG)).l
3C: The quality of other radio systems is higher than a threshold. It can be used for a
inter-RAT handover decision.
MOther
RAT
CIOOther
RAT
TOther
RAT
H3c /2
Where:
MOther RAT is the quality measurement result of other systems.
CIOOther RAT is the quality offset of other system cells (CellIndivOffset(UExternalGsmCell).
TOther RAT is the absolute threshold of other systems (ThreshSys (If the measurement
quantity is EcNo, this parameter is obtained from URatEcNoEvMeasforG. If the
measurement
quantity
is
RSCP,
this
parameter
is
obtained
from
URatRscpEvMeasforG)).
H3c is the hysteresis parameter (Hysteresis (If the measurement quantity is EcNo, this
parameter is obtained from URatEcNoEvMeasforG. If the measurement quantity is
RSCP, this parameter is obtained from URatRscpEvMeasforG)) for a 3C event decision.
During an inter-RAT event decision, the carrier must keep meeting the reporting scope or
threshold of an event for a certain period of time (TrigTime (If the measurement quantity
115
7.1.2
7.1.2.1
Measurement Setup
The principles for setting up an inter-RAT measurement (service-based Inter-RAT
handover) depend on the value of the service handover IE in the RAB assignment
request message.
i.
ii.
When the value of the service handover IE is Handover to GSM should not be
performed, it indicates that the RAB can switch to the GSM only when it exceeds
the bearing capability of the UMTS. For such a service, the RNC enables the
inter-RAT measurement only when the quality of the UMTS system is poor. The
specific scenarios are described as follows:
116
enabled or the conditions for inter-RAT blind handover are met but the blind
handover fails, an inter-RAT measurement is set up.
When the value of the service handover IE is Handover to GSM shall not be
performed, it indicates that the service cannot be switched to the GSM. For such a
service, the RNC does not enable the inter-RAT measurement or trigger a handover
to GSM.
perform
the
service
handover
strategy
by
using
the
parameter
srvHoIndAmr/srvHoIndCs64/srvHoIndPsNRT/srvHoIndPsRT(USrvBasedHo):
If the parameter is set to Ignore service handover IE, the RNC will ignore
service handover IE in requested RAB, and perform the strategy according to
the value of amrSrvHoStra/cs64SrvHoStra/psRtSrvHoStra/psNrtSrvHoStra
(USrvBasedHo). If the parameter is set to Apply service handover IE and
service handover is not included in the requested RAB, the RNC will also
perform the corresponding service handover strategy according to the value of
amrSrvHoStra/cs64SrvHoStra/psRtSrvHoStra/psNrtSrvHoStra
(USrvBasedHo). Otherwise, the RNC will perform the strategy based on the
value of service handover IE in the requested RAB.
117
Four service types (AMR/CS64/PS RT/PS NRT) are classified in this strategy
and the RNC performs service handovers according to the parameter
amrSrvHoStra/cs64SrvHoStra/psRtSrvHoStra/psNrtSrvHoStra(USrvBasedHo.
7.1.2.2
Measurement Modification
After the inter-RAT measurement is enabled, the measurement is changed in the
following cases:
When a service is added or deleted, if the handover parameters for a single service
or concurrent services are different, the inter-RAT measurement parameters must
be updated by means of measurement modification.
7.1.2.3
Measurement Deletion
The cell in the active set does not have inter-RAT neighboring cells.
118
The inter-RAT neighboring cells and the cells in the current active set are
neighboring cells with GsmShareCover(Covers).
cells
in
the
current
active
set
are
neighboring
cells
with
GsmShareCover(Covers).
When the service handover value of the service is Handover to GSM should not be
performed and the quality of the working carries becomes better (the measurement
method is the same as that described in 5.1.2.3 Measurement Deletion),
compressed mode is closed, and the GSM measurement is terminated.
the
current
time
and
TResndMeaCtrlRel(URncFunction)
the
recorded
configured,
the
time
exceed
the
MEASUREMENT
threshold
CONTROL
7.1.2.4
1)
2)
For GSM handover, when the inter-RAT handover fails, the penalty timer
HoToGsmPenTimer, which is specific to the UE, is started. The RNC will not
process the reported inter-RAT measurement reports before the timer expires, and
will issue new inter-RAT measurement control messages after the timer expires.
When PS service exists, if the UE supports inter-RAT PS service handover and the
parameters psInterSysHoSuppInd(ULogicalRnc) and BSCPSFeatSwitch(UIurgLink)
in the OMCR indicates that the RNC and adjacent BSCs support PS service
119
handover
and
the
parameters
DtmSuppInd(ULogicalRnc)
and
7.1.2.5
120
events to be configured. The EventId parameter is defined through array, and the
dimensions of array are equal to EventNum, which is 4 at most.
NonIntraMeasQuan(UUtranCellFDD)
of them)
Note:
When NonIntraMeasQuan is configured as EcNo or RSCP, only the 2D/2F
events corresponding to the measurement quality are issued.
When NonIntraMeasQuan is configured to EcNo and RSCP, two categories of
2D/2F measurement events about CPICH EcNo and CPICH RSCP are configured
and one of 2D measurement events can trigger compressed mode. After
compressed mode is triggered, inter-RAT events of corresponding measurement
quantity will be issued according to that of 2D event. For example, if the
measurement quantity of triggering 2D event is CPICH Ec/No, only inter-RAT events
121
(srvCategory (URatMeasSrvSpec))
(1). When concurrent services exist and include CS+PS services, the Multi RAB
Including CS and PS configuration is indexed.
(2). When concurrent services exist and include non-CS services, the RT RAB
Excluding Voice configuration is indexed.
(3). When the above principles are met simultaneously, the first one prevails.
For ease of parameter modification and optimization, inter-RAT handover parameters
are arranged by indexes. The indexing relations are shown in the figure below.
122
Figure 7-1
UUtranCellFDD(UUtran
CellFDD)
refURatMeasProfile
URatMeasProfile(URatMeasProfile)
URatMeasNoSrvSpec(URatMeasNoS
rvSpec)
URatMeasSrvSpec(URatMeaSrvSpec)
srvCategory
NonIntraMeasQuan
NonIntraMeasQuan
URatEcNoEvMe URatRscpEvMe
asforG(URatEc asforG(URatRsc
NoEvMeasforG) pEvMeasforG)
URatEcNoPrdM
eas(URatEcNoP
rdMeas)
URatEcNoPrdM
eas(URatRscpP
rdMeas)
InterRatCfgNo(
URatRscpEvMe
asforG)
InterRatCfgNo(
URatEcNoPrdM
eas)
InterRatCfgNo(
URatRscpPrdM
eas)
InterRatCfgNo(
URatEcNoEvMe
asforG)
is
determined
according
to
the
actual
cell
scene
(indicated
by
Configuration
Unrelated
to
Traffic
Category
Object
ID
(URatMeasNoSrvSpec) is selected.
123
is
found
based
Category(srvCategory(URatMeasSrvSpec))
and
Traffic
on
Measurement
quality
estimation
indication
GSM cell RSSI reporting indication
reporting
MeasRptTrMod
BSICVeriReq
UtranEstQual
GsmCarrRSSIInd
124
There are several switches for different services to control whether different
measurement-based RATx handovers can be performed. When such a switch is
open, it is allowed to perform RATx handovers for the corresponding service.
Otherwise, the RNC forbids inter-RAT handovers for the service by not activating
the inter-RAT measurement. The switches for different services are described as
followed:
Service
7.1.3
Switch
AMR
amrRatHoSw(ULogicalRnc)
R99 RT
r99RtRatHoSw(ULogicalRnc)
R99 NRT
r99NrtRatHoSw(ULogicalRnc)
HSDPA
hsdpaRatHoSw(ULogicalRnc)
HSUPA
hsupaRatHoSw(ULogicalRnc)
7.1.3.1
125
inter-RAT neighboring cells, marked respectively in yellow, blue, and red. The inter-RAT
neighboring cells in yellow have the highest priority level, namely, 0. Those in blue have
the secondary highest priority level, namely, 1. Those in red have the lowest priority level,
namely, 2.
Figure 7-2
Source Cell
Priority 0
Priority 1
Priority 2
7.1.3.2
Priority combination
If a cell is a common neighboring cell of multiple cells in the active set, it may be
configured with different priority levels in different cells. In this case, the multiple priority
levels of this cell must be combined, using the highest priority level as the priority of this
cell.
Neighboring cell list update and deletion in the case of more than 32 neighboring
cells
126
If the inter-RAT neighboring cell list of an active list contains more than 32 cells, the cells
are sorted in descending order based on priority. The first 32 cells remain unchanged,
and all other cells are put into the reserved inter-RAT neighboring cell list, which can
buffer at most 8 truncated inter-RAT cells.
Each time when the 1A, 1B, 1C, or 1D event is triggered, the priority levels of the
neighboring cells in the inter-RAT neighboring cell list are updated. If there are less than
32 cells in the inter-RAT neighboring cell list after the 1B event is triggered, the cells with
the highest priority in the reserved inter-RAT neighboring cell list are put into the
inter-RAT neighboring cell list. The number of the cells from the reserved inter-RAT
neighboring cell list equals: min(32 number of existing cells in the inter-RAT
neighboring cell list).
7.2
blind
handover
first
if
inter-RAT
neighboring
cells
with
7.3
127
7.4
items.
Finally,
UE
Index(UeIntMCfgNo(UHoEvtTPUeInt))
and
Internal
the
Measurement
following
Configuration
corresponding
internal
measRptTrMod(UHoEvtTPUeInt)
Filter Coefficient
filterCoeff(UHoEvtTPUeInt)
measEvtNum(UHoEvtTPUeInt)
meaEvtId(UHoEvtTPUeInt)
128
Time to Trigger(ms)
trigTime(UHoEvtTPUeInt)
When the transmit power of the UE meets the above threshold requirements, the UE
reports the corresponding events. After receiving an Event 6A report (Uplink power of UE
exceeds txPowerThres(UHoEvtTPUeInt)) or an Event 6B report (Uplink power of UE is
less than txPowerThres(UHoEvtTPUeInt)), the RNC uses the same processing strategy
as that of 2D or 2F, respectively. For details, see the Events 2D and 2F processing
strategies in Inter-RAT Handover Based on Downlink Coverage.
7.5
Change
Time
DedMeasType (UNbDedMeas)
/Measurement
EvtAbcdefTime (UNbDedMeas)
Hysteresis Time
Measurement Filter Coefficient
MeasFilterCoeff (UNbDedMeas)
Report Period
RptPrd(UNbDedMeas)
RptPrdUnit (UNbDedMeas)
Report Characteristics
RptType(UNbDedMeas)
129
Code Power
NbDed Measure Configuration No
NbDMCfgNo(UNbDedMeas)
If the DTCP reaches the threshold of Event A, it indicates the downlink power is very high,
the processing strategy is the same as that of Event 2D. If the DTCP reaches the
threshold of Event B, the processing strategy is the same as that of Event 2F. For details,
see inter-RAT handover based on downlink coverage.
7.6
When the load (transmitted carrier power (TCP) or received total wideband power
(RTWP)) of a cell is rather high.
If the current neighboring cell does not have any inter-frequency neighboring cell
with ShareCover (Overlap or Covers), but has inter-RAT neighboring cells with
GsmShareCover (Overlap or Covers), the RNC selects some users with lower
priority levels in the cell and switches them to the neighboring cells with
GsmShareCover (Overlap or Covers) blindly.
In this way, the system load can be reduced quickly and the system reliability can be
guaranteed. For details about the inter-system handover based on load, refer to the ZTE
UMTS Load Balance Feature Guide.
7.7
130
Whether a board is powered off is indicated by a notification flag (the flag for UE based
on saving energy or property changed, for details see ZTE UMTS Intelligent Carrier
Power Control Feature Guide).
When the notification flag is True, the timer BoardPwrOffHoTmr(URncFunction) is
started. For CS services, if there are 2G neighboring cells and all the relative inter-RAT
switches are open, Event 3C will be used in inter-RAT measurements to make the
service handovers to 2G network as soon as possible. For the other CS services that do
not meet the conditions of inter-RAT handovers, are released immediately. For PS
services, a DSCR is directly performed. After the timer expires, all the services in the
system will be released.
7.8
7.8.1
Defining the RT overload cell list and GSM overload cell list, the RNC saves and updates
the two lists in time, and sets up the overload valid timer CellLdInfoVldTim
(URncFunction). When the duration of a cells overload information before an update
exceeds
CellLdInfoVldTim(URncFunction),
the
cell
will
be
deleted
from
the
131
GsmUlRtLdThrd (UExternalGsmCell), it means that the load in the GSM cell is heavy and
RT services cannot be accessed. The cell will be kept in the RT overload cell list. If the
reported uplink/downlink RT Load is smaller than the corresponding threshold in a cell
and the cell exists in the RT overload cell list, the cell will be deleted from the RT
overload cell list.
When the reported downlink load in a GSM cell is not less than GsmDlLdThrd
(UExternalGsmCell) or the reported uplink load in a GSM cell is not less than
GsmUlLdThrd (UExternalGsmCell), it means that any service cannot be accessed, and
the cell will be kept in the GSM overload cell list. If the reported uplink/downlink load is
smaller than the corresponding threshold in a cell and the cell exists in the GSM overload
cell list, the cell will be deleted from the GSM overload cell list.
For RT services, if the RT Load is reported, it is used to decide the load conditions of the
GSM cell. Otherwise, the Load Value is used to decide the conditions. For NRT services,
the Load Value is used to decide the load conditions of the GSM cell.
7.8.2
Note: For RT services, if the GSM reports RT information, the overload-cell list stands for
the RT overload-cell list. Otherwise, if the GSM does not report RT information, the
overload cell list stands for the GSM overload-cell list. For NRT services, the
overload-cell list means the GSM overload-cell list.
132
7.9
7.10
133
Handovers based on load control aim to reduce the system load quickly to ensure
system stability. Therefore, handovers based on load control has the highest priority. The
handover triggered by radio quality causes such as downlink coverage event, uplink
transmit power, uplink BLER, and downlink transmit power aim to ensure the QoS and
user experience. Handovers of this kind have the second highest priority.
The handover of higher priority shields the handover of lower priority, for example, a cell
handed over based on load control cannot admit new services.
7.11
7.11.1
UE
3G to 2G CS Service Handover
NODE B
RNC
CN
BSC
RELOCATION REQUIRED
HANDOVER REQUEST
HANDOVER REQUEST ACK
RELOCATION COMMAND
HANDOVER FROM UTRAN COMMAND
HANDOVER DETECT
HANDOVER COMPLETE
HANDOVER COMPLETE
IU RELEASE COMMAND
RADIO LINK DELETION REQUEST
134
Figure 7-4
UE
NODE B
RNC
CN
BSC
1 MEASUREMENT REPORT
2 ENHANCED RELOCATION
RESOURCE REQUEST
3 ENHANCED RELOCATION
RESOURCE RESPONSE
5 HANDOVER FROM
UTRAN COMMAND
4 RELOCATION REQUIRED
6 HANDOVER REQUEST
7 HANDOVER
REQUEST ACK
8 RELOCATION COMMAND
9 RELOCATION COMMIT
10 HANDOVER ACCESS
11 HANDOVER DETECT
12HANDOVER COMPLETE
13 HANDOVER COMPLETE
14 IU RELEASE COMMAND
15 IU RELEASE COMPLETE
135
procedure is the part of the previous CN procedure between the RNC and the BSC to
reserve resources in advance. The procedure is described as follows:
1
Upon receiving the measurement report of the UE, the RNC decides to handover
the UE to a GSM cell.
Upon receiving the message, the BSC reserves resources in advance for the UE
and sends an ENHANCED RELOCATION RESOURCE RESPONSE message to
the RNC.
Described in step 4.
After the resources are established, the BSC sends a HANDOVER REQUEST ACK
message to CN.
10 Upon receiving the message HANDOVER ACCESS from the UE, if the BSC has
already received the message RELOCATION COMMIT from the CN, the BSC will
send a HANDOVER DETECT to the CN. Otherwise, the BSC will not send
HANDOVER DETECT to the CN until receiving the message RELOCATION
COMMIT from the CN.
11
Described in step 4.
136
12 The UE returns HANDOVER COMPLETE to the BSC to inform the BSC that the
handover is finished.
13 After receiving HANDOVER COMPLETE from the UE, the BSC sends a
HANDOVER COMPLETE message to the CN.
14 Upon receiving the message HANDOVER COMPLETE, the CN sends an IU
RELEASE COMMAND message to the RNC to release all the Iu resources.
15 Upon releasing the lu resources, the RNC returns IU RELEASE COMPLETE to the
CN.
Note: In the process of a 3G->2G CS service handover, the parameter rxlevNecellInd
(URncInfo)
is
used to
control
whether
to fill the IE
RXLEV-NECELL
in
7.11.2
The UE selects a GPRS cell to dwell through the cell reselection process, sets up a
connection with the target cell, and then initiates route area update. This case applies to
an UE in CELL_FACH or URA_PCH state.
137
Figure 7-5
UE
S erving
RNC
CN
1 . C ell R eselectio n
trig g ered
RANAP
RANAP
2 . Iu R elease C o m m and
2 . Iu R elease C o m p lete
RANAP
RANAP
The RNC decides to switch the UE to another RAT cell according to handover decision
results. This case applies to an UE in CELL_DCH state. The RNC sends a handover
command CELL CHANGE ORDER FROM UTRAN to the UE. After receiving the
command, the UE sets up a connection with the target cell, and then initiates route area
update.
138
Figure 7-6
handover
BTS
UE
RRC
BSC
CN
(SGSN)
RNC
Serving
Node B
RRC
GMM
GMM
RANAP
4. SRNS Context
Request
RANAP
RANAP
5. SRNS Context
Response
RANAP
RANAP
7. Forwarding of PDUs
RANAP
8. Iu Release Command
RANAP
9. Iu Release Complete
RANAP
GMM
GMM
GMM
GMM
RANAP
Procedure description:
1.
2.
The UE reselects to the target GPRS cell and establishes the radio connection to
the GSM/BSS.
139
3.
The UE initiates the GPRS Routing Area Update procedure by sending the GMM
message Routing Area Update Request to the SGSN.
4.
The SGSN sends the RANAP message SRNS Context Request to the SRNC listing
the PS RABs for which context transfer shall be performed.
5.
SRNC responds to the SGNS with the RANAP message SRNS Context Response
containing the context information of all referenced PS RABs whose transfer is
successful and starts the timer TWaitDataFwd(URncFunction). Upon reception of
the SRNS Data Forward Command message, SRNC shall stop the timer. If
TWaitDataFwd expires, SRNC starts the timer TWaitRelCmd(URncFunction).
6.
The SGSN asks the SRNC to forward its buffered data back to the SGSN by
sending the RANAP message SRNS Data Forward Command, and starts the timer
Tdatafwd(UiuCnst) and TWaitRelCmd(URncFunction). If Tdatafwd expires, the
SRNC releases the resource used to forward buffered data. Upon reception of the
IU RELEASE COMMAND message, the SRNC shall stop the timer TWaitRelCmd. If
TWaitRelCmd expires, the SRNC releases IU connection. For each PS RAB
indicated by the SRNS Data Forward Command, the SRNC starts duplicating and
tunneling the buffered data back to the SGSN.
7.
The SGSN sends the RANAP message Iu Release Command to initiate the release
of the Iu connection with UTRAN.
8.
At the expiration of the RNC data forwarding timer (i.e. TDATAfwd), the SRNC
sends the RANP message Iu Release Complete message to the SGSN.
9.
The SGSN validates the UEs presence in the new RA by sending the GMM
message Routing Area Update Accept to the UE. The message may contain a new
P-TMSI that the network assigns to the UE.
10. The UE acknowledges the assignment of a new P-TMSI by sending the GMM
message Routing Area Update Complete to the UE.
140
8.1
2.
3.
The switch for current service to control whether LTE based on measurement could
be performed is open.
Service
4.
Switch
R99 RT
r99RtEutraHoSw (ULogicalRnc)
R99 NRT
r99NrtEtraHoSw (ULogicalRnc)
HSDPA
hsdpaEutraHoSw (ULogicalRnc)
HSUPA
hsupaEutraHoSw (ULogicalRnc)
The system which RNC allows UE to hand over to is EUTRAN, that is judged by
cell level switch IfOrRatHoSwch, ChoStraMulRatHo and the conditions of neighbor
cell exiting (See 5.10 Inter-frequency and Inter-RAT Measurement Choice).
5.
The switch of whether to check the UE E-UTRA Capability before initiating the PS
handover procedure from UMTS to LTE, GresPara52 (bit11) is Off or GresPara52
(bit11) is On with UE E-UTRA Capability IE acquired.
141
8.1.1
8.1.1.1
142
Figure 8-1
UUtranCellFDD(UUtran
CellFDD)
refURatMeasProfile
URatMeasProfile(URatMeasProfile)
URatMeasSrvSpec(URatMeaSrvSpec)
URatMeasNoSrvSpec(URatMeasNoS
rvSpec)
srvCategory
NonIntraMeasQuan
NonIntraMeasQuan
URatEcNoEvMe URatRscpEvMe
asforE(URatEc asforE(URatRsc
pEvMeasforE)
NoEvMeasforE)
URatEcNoPrdM
eas(URatEcNoP
rdMeas)
URatEcNoPrdM
eas(URatRscpP
rdMeas)
InterRatCfgNo(
URatRscpEvMe
asforE)
InterRatCfgNo(
URatEcNoPrdM
eas)
InterRatCfgNo(
URatRscpPrdM
eas)
InterRatCfgNo(
URatEcNoEvMe
asforE)
The parameters in below table, for event measurement and measurement quantity is
EcNo, gained from the object URatEcNoEvMeasforE, for event measurement and
measurement quantity is RSCP, gained from the object URatRscpEvMeasforE.
Absolute Threshold of the Quality of UTRAN Cell for 3A
Thresh
Hysteresis(dB)
hysteresis
ThreshSys
3A/3B/3C
Time To Trigger
TrigTime
EventNum
EventId
FilterCoeff
143
eUtranFilterCoeff
InterRatCfgNo
Note: Inter-RAT period measurement does not discriminate between EUTRAN and GSM.
The other parameter to be entered in the inter-RAT measurement control message:
Maximum bandwidth allowed to measure on the single frequency of EUTRANEutranNMeasBand
(for
FDD
cell,
this
parameter
is
obtained
from
MO
8.1.1.2
Setting up a measurement
The principles for setting up an inter-RAT measurement depend on the value of the
E-UTRAN service handover IE in the RAB assignment request message.
1. When the value of the E-UTRAN service handover IE is Handover to E-UTRAN
shall not be performed, it indicates that the service cannot be switched to the
E-UTRAN. For such these services, the RNC does not enable inter-RAT
measurement or trigger the handover to LTE.
2. When the value of the E-UTRAN service handover IE is not Handover to E-UTRAN
shall not be performed, it indicates that the service can be switched to the E-UTRAN.
RNC enables inter-RAT measurement in the following scenarios:
a)
b)
8.1.1.3
Modifying a measurement
Same as 7.1.2.2 Modifying a measurement.
144
8.1.1.4
Deleting a measurement
1. When the E-UTRAN service handover value of the service is Handover to E-UTRAN
shall not be performed and the quality of the working carries becomes better, the
compressed mode is closed, and E-UTRAN measurement is terminated.
2. Other deleting scenarios seen in 7.1.2.3 Deleting a measurement.
8.1.1.5
8.1.1.6
8.1.2
145
measured inter-frequency neighboring cell is also poor), the RNC needs to configure and
start inter-RAT measurement 3A or 3C event to the UE if inter-RAT neighboring cells
exist, and then performs the corresponding decision process for inter-RAT handover
according to the 3A, or 3C event subsequently reported by the UE. The choice strategy
of events 3A, 3C is the same as the related policy of GSM inter-RAT handover, controlled
by inter-RAT handover tactic RatHoTactic (UUtranCellFDD).
8.1.3
8.1.4
The handovers triggered by radio quality causes such as downlink coverage event,
uplink transmit power, uplink BLER, and downlink transmit power aim to ensure the QoS
and user experience. The handovers of these kinds has the same priority.
146
8.1.5
UE
NODE B
RNC
CN
eNB
RELOCATION REQUIRED
HANDOVER REQUEST
HANDOVER REQUEST ACK
RELOCATION COMMAND
HANDOVER FROM UTRAN COMMAND
HANDOVER DETECT
HANDOVER COMPLETE
HANDOVER COMPLETE
IU RELEASE COMMAND
RADIO LINK DELETION REQUEST
8.2
SRVCC
Due to the continuity of voice service between the UTRAN and the LTE, the RNC is
needed to transition a voice call from the VoIP/IMS packet domain to the legacy circuit
domain during an inter-RAT handover. This mechanism is named SRVCC (Single Radio
Voice Call Continuity).
ZTE supports SRVCC, which is controlled by RncSrvccSw(ULogicalRnc), from LTE to
UTRAN.
ZTE supports IMS voice and IMS Voice+Data SRVCC. The procedure is described as
follows:
147
1. RncSrvccSw(ULogicalRnc) is On.
2. The UE connects with the EUTRAN and sets up IMS voice traffic.
3. The UE reports a measurement report.
4. The EUTRAN decides an SRVCC handover to the UTRAN due to measurement
reports.
5. The EUTRAN sends a message for the PS-CS handover procedure to the CN.
6. The CN initiates the PS-CS handover to the UTRAN procedure.
1)
7. The CN informs the EUTRAN of the handover result (maybe including the result of
inter-RAT PS handovers).
8. The EURAN sends a Handover from E-UTRAN Command message to the UE after
receiving the handover result.
Figure 8-3
UE
E-UTRAN
MME
MSC Server
Target UTRAN
UE initiates IMS
voice service
Measurement Reports
Handover Required
PS to CS Req
Handle PS to PS HO for
non-voice if needed
CS Handover Preparation
IMS Service Continuity Procedure
PS to CS Resp
Handover Command
Handover From
EUTRAN Command
Handover execution
148
IMS
8.3
CSFB
Due to the continuity of voice service between UTRAN and EUTRAN, the CSFB service
can initial the PS handover from EUTRAN to UTRAN, and the corresponding CS service
can be set up in the UTRAN later.
ZTE supports CSFB, which is controlled by PSL2USWCHBYCS (ULogicalRnc), from
EUTRAN to UTRAN right now.
Procedure description: (1)The UE triggers voice traffic for originating call or terminated
call after setting up PS traffic in the EUTRAN. (2) If CS Fallback Indicator is received, PS
handover is supported and the EUTRAN will trigger a PS handover to the UTRAN. (3)
The UTRAN sets up traffic for originating call and terminated call.
Figure 8-4
UE
eNB
CN
RNC
(CSFB information)
RELOCATION REQUEST ACK
HANDOVER COMMAND
HANDOVER FROM EUTRAN COMMAND
Handover execution
UE sets up CS service in UTRAN
149
Procedure description: (1) The UE triggers voice traffic for originating call or terminated
call in idle mode or after setting up PS traffic (PS handover is not supported) in the
EUTRAN. (2) If CS Fallback Indicator is received, the EUTRAN will trigger a redirection
to the UTRAN. (3) The UTRAN sets up traffics.
8.4
3)
8.4.1
CSFB
1.
service is released for Multi-RAB, if the following conditions are met, EUTRANs
compressed mode is activated, and the inter-RAT measurement is configured. After the
measurement reports are received, the PS handover procedure is performed and the UE
150
2)
3)
4)
5)
6)
EutranPsHoMode is PS handover.
SRVCC
1.
After the UE is from EUTRAN to UTRAN due to SRVCC, when the CS service is
released for Multi-RAB, if the following conditions are met, EUTRANs compressed mode
is activated, and the inter-RAT measurement is configured. After measurement reports
are received, the PS handover procedure is performed and the UE is handed over to the
EUTRAN.
1)
2)
3)
4)
5)
6)
GresPara52:bit10 is PS handover.
151
Note:
1.
compressed
mode
will
not
be
activated.
Otherwise,
8.4.2
CSFB
1.
After the UE is from EUTRAN to UTRAN due to CSFB, when CS service is released for
Multi-RAB, if the following conditions are met, EUTRANs compressed mode is activated,
and the inter-RAT measurement is configured. After the measurement reports are
received, the Redirection procedure is performed and downlink central frequency
information of the EUTRAN cell whose quality meets inter-RAT measurement event is
filled in Redirection info of RRC Connection Release, the UE is redirected to EUTRAN.
1)
2)
3)
4)
152
SRVCC
1.
After the UE is from EUTRAN to UTRAN due to SRVCC, when CS service is released for
Multi-RAB, if the following conditions are met, then activate EUTRAN compressed mode,
configure inter-RAT measurement, and after measurement reports are received, perform
the Redirection procedure, fill downlink central frequency information of the EUTRAN cell
whose quality meets inter-RAT measurement event in Redirection info of RRC
Connection Release, the UE is redirected to EUTRAN.
1)
2)
3)
4)
Note:
1.
compressed
mode
will
not
be
activated.
Otherwise,
153
8.4.3
CSFB
1.
After the UE is handed over from EUTRAN to UTRAN due to CSFB, when the CS
service is released for Multi-RAB, if the following conditions are met, theEUTRAN cells
downlink central frequency information is filled in Redirection info of RRC Connection
Release, the UE is redirected to EUTRAN.
1)
2)
3)
2.
Only CS Service
After the UE is from EUTRAN to UTRAN due to CSFB, when the CS service is released
for Single-RAB, if the following conditions are met, the EUTRAN cells downlink central
frequency information is filled in Redirection info of RRC Connection Release, the UE is
redirected to EUTRAN.
1)
2)
3)
4)
CelReturnLteSwch is On.
154
SRVCC
1.
After the UE is handed over from EUTRAN to UTRAN due to SRVCC, when the CS
service is released for Multi-RAB, if the following conditions are met, the EUTRAN cells
downlink central frequency information is filled in Redirection info of RRC Connection
Release, the UE is redirected to EUTRAN.
1)
2)
3)
2.
Only CS Service
After the UE is handed over from EUTRAN to UTRAN due to SRVCC, when the CS
service is released for Single-RAB, if the following conditions are met, the EUTRAN cells
downlink central frequency information is filled in Redirection info of RRC Connection
Release, the UE is redirected to EUTRAN.
1)
2)
3)
4)
CresPara7:bit2 is On.
Note:
1.
Eight downlink central frequencies can be filled at most, four frequencies for FDD
and four frequencies for TDD.
155
8.4.4
When the SRNC has no radio links and EUTRAN neighbor cells exist, the SRNC will
save the frequency information of EUTRAN neighbor cells returned by the DRNC, and
the union of the saved and the frequency information of EUTRAN neighbor cells
configured for the SRNC is filled in Redirection info if the redirection conditions are met.
Currently, only the Redirection way without measurement is supported.
When the SRNC sends Relocation Request to the DRNC, if the UE is identified as a
CSFB user, the SRNC needs to fill CSFB in CSFB Information of Source To Target
Transparent Container to enable the target SRNC to identify the CSFB user and apply
the function of Fast Return to EUTRAN after the relocation procedure finished.
8.5
EUTRAN
neighboring
blacklist
management
object
(UENbrBlkList:
156
8.6
8.7
8.8
RIM
The function of RIM is intended to exchanging information via CN between BSS, RNC,
and eNodeB. RIM information is transferred on Iu interface through Direct Information
Transfer message.
157
Procedure description: The controlling BSC sends a request to the Serving BSC, asking
for some concerned information and demanding the Serving BSC to respond in the form
of report (where Controlling BSC and Serving BSC can be BSC, RNC or ENodeB). The
report form can be single report or multiple reports.
The signalling flow charts corresponding to the two kinds of report form are described as
follows:
Single Report
Controlling BSC
Serving BSC
RAN-INFORMATION-REQUEST/Single Report
RAN-INFORMATION/Single Report
Multiple Report
Controlling BSC
Serving BSC
RAN-INFORMATION-REQUEST/Multiple Report
RAN-INFORMATION/Multiple Report-Initial
Different from the simple procedure in single report form, which only has one time
information exchange between the Controlling BSC and Serving BSC, in multiple report
form, when the information that the Controlling BSC concerns does change or the
Serving BSC cannot provide information any more, the Serving BSC needs to inform the
Controlling BSC through the update process shown below:
158
Controlling BSC
Serving BSC
RAN-INFORMATION-ACK
Moreover, in multiple report form, if the Controlling BSC does not need the Serving BSC
to provide information any more, it should inform the Serving BSC through the
termination process shown below:
Controlling BSC
Serving BSC
RAN-INFORMATION-REQUEST/Stop
RAN-INFORMATION/Stop
8.8.1
UTRA SI
UTRA SI is one application of RIM, mainly used for ENB gaining the UTRAN cell system
information from the UTRAN network. Then ENB will transfer these SIs to the UE
accompanying the existing message between ENB and the UE to make the UE be
reselected from LTE to UTRAN faster.
Report
or
159
8.8.2
SON Transfer
The function of SON Transfer is to exchange load information of the cell among UTRAN,
ENB, and GERAN. The target system will respond the load information of cell to source
system after receiving the RIM request message of SON Transfer Function. Currently,
only the form of single report and single cell in SON Transfer are supported.
The function is currently mainly used in obtaining the load information between UTRAN
and EUTRAN. The process is bidirectional, both of the UTRAN and EUTRAN can trigger
the process, which is explained in detail as below.
with
the
requested
cell
ID,
and
then
structure
the
IMSI-based handover
The parameter BasedImsiHoInd (ULogicalRnc) indicates whether the RNC supports
IMSI-based handover.
160
The IMSI-based handover can limit the range of cells for allowed for handover according
to IMSI of the UE with the following principle:
While a measurement control message is not delivered before the CommonID message
is received in the signaling stage, the RNC does not know the cells authorized to the user.
Therefore, the RNC delivers a measurement control message regardless of the
authorization status of the cells.
While delivering a measurement control message after receiving the CommonID
message, the RNC queries whether the cells are authorized according to the IMSI
information carried in the CommonID message of the lu interface and also the
authorization information configured on the network side. If the SNAC list of the PLMN
carried in CommonID is empty, all the cells of that PLMN will be considered as
authorized ones. Only the authorized neighbor cells will be included in the neighbor cell
list of the measurement control message.
In the process of RAB assignment of service, a decision of whether the current service
cell is authorized is made according to the IMSI information carried in the CommonID
message and the authorization information configured in the network side.
If none of the cells in the active set is authorized
If the best cells in the active set are like the coverage neighbor cells
(ShareCover (UUtranRelation)) and are also authorized cells,
then the inter-frequency handover is performed along with service
establishment
Otherwise,
If the best cells in the active set are like the coverage GSM neighbor
cells (GsmShareCover (UGsmRelation)) and are authorized cells,
and also the current service is AMR,
then Inter-RAT directional retry is performed
Otherwise,
The RAB assignment failure procedure is performed.
161
Otherwise,
The service is established normally. If some of the cells in the active set are
unauthorizedcells, delete the unauthorized cells from the active set through the
active set update flow.
9.1
The MCC, MNC and other number information (10 digits at most, in the name of
ExtendInformation below) are resolved according to the IMSI carried in the
CommonID message of the lu interface. The number of digits depends on
imsiMatchedDgtNum(UImsiSnacFilter).
2.
The information (MCC, MNC and ExtendInformation) resolved and also the
authorized network information imsiMatchedDgtNum(UImsiSnacFilter) configured in
the network side are used to query whether the IMSI of the UE is authorized or not.
If MCC, MNC and Extend Information of the UE does not have a configuration item
in UImsiSnacFilter, no neighbor cell authorized is returned. Otherwise, the MCC
(SMCC), MNC (SMNC) and SNAC that are authorized are obtained.
3.
According to the relationships between MCC (SMCC), MNC (SMNC), SNAC and
LAC (USnac) and also the cell information including MCC (UUtranCellFDD), MNC
(UUtranCellFDD), LAC (UUtranCellFDD), whether the cell belongs to the MCC
(USnac), MNC (USnac, and LAC (USnac) that are already authorized is queried. If
there is much authorization information, the cell which has configuration item will be
authorized.
162
Note: The UImsiSnacFilter parameter can have 1000 configuration items at most and
different configuration items can have the same MNC+MNC.
Example:
1.
Configuration of UImsiSnacFilter
MCC
460
460
460
MNC
99
99
99
imsiMatchedDgtNum
ExtendInformation
[0]
[1]
[2]
SMCC
460
460
460
SMNC
99
99
100
SNAC
60
61
62
The IMSI of UE1 is 460991234567890, and the authorized PLMN+SNAC for UE1 are
46099+60, 46099+61, and 460100+62.
The IMSI of UE2 is 460990987654321, and the authorized PLMN+SNAC for UE1 are
460+99+60.
2.
3.
Configuration of USnac
MCC
460
460
460
460
MNC
99
99
99
100
SNAC
60
60
61
62
LAC
01
02
02
03
If there are three cells: the PLMN+LAC configuration of Cell1 is 46099+01, the
PLMN+LAC configuration of Cell2 is 46099+02, and the PLMN+LAC configuration
of Cell3 is 46099+03. As shown in the above table, the authorized IMSI of
CELL1/CELL2 is from 460990000000000 to 46099999999999, and the authorized
IMSI of Cell3 is from 460991200000000 to 46099129999999.So UE1 can be
authorized by CELL1/CELL2/CELL3, and UE2 can be authorized by CELL1/CELL2.
163
Figure 9-1
According to IMSI
CommonID:
MCC
MNC
ExtendInformation
UImsiSnacFilter:
MCC
MNC
ExtendInformation
SNAC
Authorized:
MCC
MNC
SNAC
Authorized
MCC
MNC
LAC
USnac
Whether the
neighbor
cell is
authorized
MCC
MNC
SNAC
LAC
UUtranCellFDD
MCC
MNC
LAC
9.2
The MCC, MNC and other number information (10 digits at most, in the name of
ExtendInformation below) are resolved according to the IMSI carried in the
CommonID message of the lu interface. The number of digits depends on
imsiMatchedDgtNum(UImsiSnacFilter).
2.
The information (MCC, MNC and ExtendInformation) resolved and also the
authorized network information imsiMatchedDigit(UImsiSnacFilter) configured in the
network side are used to query whether the IMSI of the UE is authorized or not. If
MCC, MNC and Extend Information of the UE does not have a configuration item in
UImsiSnacFilter, no neighbor cell authorized is returned. Otherwise, the MCC
(SMCC), MNC (SMNC) and SNAC that are authorized are obtained.
164
3.
For
UTRAN
cells,
this
parameter
is
obtained
from
For
UTRAN
cells,
this
parameter
is
obtained
from
For
UTRAN
cells,
this
parameter
is
obtained
from
UExternalUtranCellFDD).
Figure 9-2
According to IMSI
CommonID:
MCC
MNC
ExtendInformation
UImsiSnacFilter:
MCC
MNC
ExtendInformation
SNAC
Authorized:
MCC
MNC
SNAC
Whether the
neighbor
cell is
authorized
UExternalUtranCellFDD
UExternalGsmCell
MCC
MNC
SNAC
10
165
10.1
Overview
The cells are classified in three types according to the support capability of HSDPA
(HspaSptMeth(For serving cells, this parameter is obtained from UUtranCellFDD. For
neighboring cells, this parameter is obtained from UExternalUtranCellFDD)) after
HSDPA is introduced: (1) support HSDPA and DCH; (2) do not support HSUPA or
HSDPA; (3) support HSDPA only. The services are classified in two types: HSDPA
service and NHSDPA service. The HSDPA handover is similar to R99 handover in terms
of measurement and handover decision, except that the decisions of cell capacity during
a handover and the service type are added. For the HSDPA service, the handover is
accepted through HS-DSCH to the cells that support HSDPA and DCH and cells that
support HSDPA only as much as possible. If the HS-DSCH fails, the handover to the
cells that support HSDPA and DCH and cells that do not support HSUPA or HSDPA
through DCH is accepted. For the NHSDPA service, the handover can only be accepted
through DCH to the cells that support HSDPA and DCH and cells that do not support
HSUPA or HSDPA.
After HSDPA is introduced, the inter-RNC handover also depends on the capability of
office direction RNC to support HSDPA (RncFeatSwitchBit1) because neighbor cells
feature varying support capabilities (HspaSptMeth(UExternalUtranCellFDD)). That is,
only if both the target cell and target RNC (office direction RNC) support HSDPA, the
HS-
handover flow cannot be originated until HS-DSCH falls back to DCH. The channel
transfer is performed along with a handover. Different channel transfer situations are
described in the following based on different handover types.
10.2
Intra-frequency Handover
The intra-frequency handover of HDSPA includes soft add/soft drop/soft replacement of
HS-DSCH associated channel, HS-DSCH service cell change, channel type change due
to different capabilities between source cell and target cell during the handover process.
The strategy of soft add/soft drop/soft replacement of HS-DSCH associated channel is
described in strategy of intra-frequency handover. The HS-DSCH service cell change
166
and channel type change are special handover strategies that make HSDPA different
from the R99 (DCH) handover. The specific principles are:
1
HS-DSCH->DCH
If the HS-DSCH is used before the handover and the link to be deleted for 1B event
triggering/radio link failure happens to be the service cell of HS-DSCH, and also the
cells in the active set do not support acceptance through HS-DSCH, a decision of
soft handover together with HS-DSCH transferring to DCH is made.
If the HS-DSCH is used before the handover and the 1C event is triggered, the cell
to be replaced is the HS-DSCH service cell and also the cells in the new active set
do not support acceptance through HS-DSCH, a decision of soft handover together
with HS-DSCH transferring to DCH is made.
If the HS-DSCH is used before the handover and the 1D event triggers
intra-frequency hard handover and the target cell does not support acceptance
through HS-DSCH, a decision of intra-frequency hard handover together with
HS-DSCH transferring to DCH is made.
DCH->HS-DSCH
The current service of the UE includes HSDPA and also the DCH is used before the
handover. If the 1D event triggers intra-frequency hard handover and the target cell
supports acceptance through HS-DSCH, a decision of intra-frequency hard
handover together with DCH transferring to HS-DSCH is made.
The current service of the UE includes HSDPA, the DCH is used before the
handover and also the best cell in the active set supports HSDPA. If the downlink
traffic increases to trigger the 4A event (refer to ZTE UMTS DRBC Algorithm
Feature Guide for details), a decision of handover from DCH to HS-DSCH is made.
HS->DSCH->HS-DSCH
If the HS-DSCH is used before the handover and the 1D event triggers
intra-frequency hard handover and the target cell supports acceptance through
HS-DSCH, a decision of intra-frequency hard handover together with HS-DSCH
service cell change is made.
167
If the HS-DSCH is used before the handover and the link to be deleted for 1B event
triggering/radio link failure happens to be the service cell of HS-DSCH, and also
there are cells in the active set that support acceptance through HS-DSCH, a
decision of soft handover together with HS-DSCH change is made. If the 1C/1D
event triggers a soft handover, the cell to be replaced is the HS-DSCH service cell
and also the cells in the new active set support acceptance through HS-DSCH, a
decision of soft handover together with HS-DSCH change is made.
In the above described processes, the 1D event may trigger a ping-pong handover that
leads to frequent change of service cell. To avoid this, a time threshold (T1d(UHspa)) is
configured and changes of service cell should occur at an interval longer than this
threshold.
10.3
Inter-frequency Handover
The conditions for triggering the inter-frequency handover of HDSPA are described in
inter-frequency handover strategy. The HS-DSCH service cell change or channel type
change always happens in the handover process. The principles are as follow:
1
HS-DSCH->DCH
The current service of the UE includes HSDPA and also the HS-DSCH is used
before the handover. If the original decision is to trigger an inter-frequency handover
(measurement-based or blind handover) and also the target cell does not support
acceptance through HS-DSCH, a decision of inter-frequency hard handover
together with HS-DSCH transferring to DCH is made.
DCH->HS-DSCH
The current service of the UE includes HSDPA and also the DCH is used before the
handover. If the original decision is to trigger an inter-frequency handover
(measurement-based or blind handover) and also the target cell supports
acceptance through HS-DSCH, a decision of inter-frequency hard handover
together with DCH transferring to HS-DSCH is made.
HS-DSCH->HS-DSCH
168
The current service of the UE includes HSDPA and also the HS-DSCH is used
before the handover. If the original decision is to trigger an inter-frequency handover
(measurement-based or blind handover) and also the target cell supports
acceptance through HS-DSCH, a decision of inter-frequency hard handover
together with HS-DSCH service cell change is made.
4
10.4
Inter-RAT Handover
Two
strategies
are
available
for
handovers
between
HSDPA
systems:
UTRAN->GSM/GERAN/LTE
The HSDPA service is included and then the same handover flow as that for
between R99 systems is performed.
11
169
11.1
Overview
HSUPA is developed on the basis of HSDPA. An HSUPA network element (UE, RNC or
Node B) that supports HSUPA will also supports HSDPA. That is, if the E-DCH is used in
uplink, HS-DSCH is used in downlink without doubt. Therefore, HSUPA supports five
types of cells (HspaSptMeth (For serving cells, this parameter is obtained from
UUtranCellFDD.
For
neighboring
cells,
this
parameter
is
obtained
from
UExternalUtranCellFDD)): (1) cells that support HSUPA and HSDPA; (2) cells that
support HSUPA, HSDPA and DCH; (3) cells that support HSDPA and DCH; (4) cells that
support HSDPA only; (5) cells that do not support HSUPA or HSDPA. For the cells that
support HSUPA and HSDPA, the E-DCH is used in uplink and the HS-DSCH is used in
downlink. The DPCH is used as associated channel. For the cells that support HSUPA,
HSDPA and DCH, the E-DCH or DCH is used in uplink and the HS-DSCH or DCH is
used in downlink. The DPCH is used as associated channel or allocated to users who do
not use HSUPA or HSDPA.
The service types supported by HSUPA are HSPA services if they can be carried by
HSUPA or HSDPA (HSUPA and HSDPA are equivalent as far as the services are
concerned). Otherwise, they are NHSPA services. The HSPA services should be
accepted first through E-DCH and HS-DSCH in cells that support HSUPA and HSDPA,
cells that support HSDPA only, cells that support HSUPA, HSDPA and DCH and cells
that support HSDPA and DCH (HspaSptMeth (For serving cells, this parameter is
obtained from UUtranCellFDD. For neighboring cells, this parameter is obtained from
UExternalUtranCellFDD)). If E-DCH and HS-DSCH fail to accept the services, the HSPA
services should be accepted through DCH in cells that support HSUPA, HSDPA and
DCH, cells that support HSDPA and DCH or cells that do not support HSUPA or HSDPA.
The NHSPA services can only be accepted through DCH in cells that support HSUPA,
HSDPA and DCH, cells that support HSDPA and DCH or cells that do not support
HSUPA or HSDPA.
The maximum number of cells allowed in the E-DCH active set in the process of HSUPA
soft handover is 3.
After HSUPA is introduced, the inter-RNC handover also depends on the capability of
office direction RNC to support HSUPA (RncFeatSwitchBit2) because neighbor cells
170
11.2
Intra-frequency Handover
The intra-frequency handover of HSUPA includes soft add/soft drop/soft replacement of
E-DCH associated channel, E-DCH service cell change, channel type change due to
different capabilities between source cell and target cell during the handover process.
The strategy of soft add/soft drop/soft replacement of E-DCH associated channel is
described in strategy of intra-frequency handover. The E-DCH service cell change and
channel type change are special handover strategies that make HSUPA different from
the R99 (DCH) handover. The specific principles are:
1
HS-DSCH/E-DCH->DCH/DCH
The current service of the UE includes HSPA and also the HS-DSCH/E-DCH is
used before the handover. If the 1A event is triggered and the target cell supports
DCH/DCH instead of HS-DSCH/E-DCH, HS-DSCH/E-DCH is transferred to
DCH/DCH firstly, and then a soft handover is performed.
If the 1D event is triggered, the best cell changes from HS-DSCH/E-DCH service
cell to a cell that does not support HS-DSCH/E-DCH, a decision of intra-frequency
hard handover with HS-DSCH/E-DCH transferring to DCH/DCH is made.
DCH/DCH->HS-DSCH/E-DCH
171
The current service of the UE includes HSPA and also the DCH/DCH is used before
the handover. If the 1D event triggers intra-frequency hard handover and the target
cell supports acceptance through HS-DSCH/E-DCH, a decision of intra-frequency
hard handover with DCH/DCH transferring to HS-DSCH/E-DCH is made.
The current service of the UE includes HSPA, the current channel type is DCH/DCH,
and also the best cell in the active set supports HSDPA. If the downlink or uplink
traffic increases to trigger the 4A event (refer to ZTE UMTS DRBC Algorithm
Feature Guide for details), a decision of handover from DCH/DCH to
HS-DSCH/E-DCH is made.
HS-DSCH/E-DCH->HS-DSCH/E-DCH
If the 1D event triggers intra-frequency hard handover and the target cell supports
acceptance through HS-DSCH/E-DCH, a decision of intra-frequency hard handover
together with HS-DSCH/E-DCH service cell change is made. Refer to 2.1.2
Intra-frequency Hard Handover for the scenario where the intra-frequency hard
handover is triggered.
If the link to be deleted for 1B event triggering/radio link failure happens to be the
service cell of HS-DSCH/E-DCH, and also there are cells in the active set that
support acceptance through HS-DSCH/E-DCH, a decision of soft handover
together with HS-DSCH/E-DCH service cell change is made. If the 1C/1D event
triggers soft handover, the cell to be replaced is the HS-DSCH/E-DCH service cell
and also the cells in the new active set support acceptance through
HS-DSCH/E-DCH, a decision of soft handover together with HS-DSCH/E-DCH
change is made.
HS-DSCH/E-DCH->HS-DSCH/DCH
The current service of the UE includes HSPA and also the HS-DSCH/E-DCH is
used before the handover. If the 1A event is triggered, and the target cell supports
HS-DSCH/DCH instead of HS-DSCH/E-DCH, HS-DSCH/E-DCH is transferred to
HS-DSCH/DCH firstly, and then a soft handover is performed.
172
If the 1D event is triggered, the best cell changes from HS-DSCH/E-DCH service
cell to a cell that supports HS-DSCH/DCH instead of HS-DSCH/E-DCH, a decision
of
intra-frequency
hard
handover
with
HS-DSCH/E-DCH
transferring
to
HS-DSCH/DCH is made.
5
HS-DSCH/DCH->HS-DSCH/E-DCH
The current service of the UE includes HSPA service and also the HS-DSCH/DCH
is used before the handover. If the 1D event is triggered, the best cell changes from
HS-DSCH/DCH service cell to a cell that supports HS-DSCH/E-DCH, a decision of
intra-frequency
hard
handover
with
HS-DSCH/DCH
transferring
to
HS-DSCH/E-DCH is made.
11.3
Inter-frequency Handover
The conditions for triggering the inter-frequency handover of HSPA are described in
inter-frequency handover strategy. The HS-DSCH service cell change or channel type
change always happens in the handover process. The principles are as follow:
1
HS-DSCH/E-DCH->DCH/DCH
The current service of the UE includes HSPA and also the HS-DSCH/E-DCH is used
before the handover. If the original decision is to trigger an inter-frequency handover
(measurement-based or blind handover) and also the target cell does not support
acceptance
through
HS-DSCH/E-DCH
or
HS-DSCH/DCH,
decision
of
DCH/DCH->HS-DSCH/E-DCH
The current service of the UE includes HSPA and also the DCH/DCH is used before
the handover. If the original decision is to trigger an inter-frequency handover
(measurement-based or blind handover) and also the target cell supports
acceptance through HS-DSCH/E-DCH, a decision of inter-frequency hard handover
173
HS-DSCH/E-DCH->HS-DSCH/E-DCH
The current service of the UE includes HSPA and also the HS-DSCH/E-DCH is used
before the handover. If the original decision is to trigger an inter-frequency handover
(measurement-based or blind handover) and also the target cell supports
acceptance through HS-DSCH/E-DCH, a decision of inter-frequency hard handover
with HS-DSCH/E-DCH service cell change is made.
HS-DSCH/E-DCH->HS-DSCH/DCH
The current service of the UE includes HSPA and also the HS-DSCH/E-DCH is used
before the handover. If the original decision is to trigger an inter-frequency handover
(measurement-based or blind handover) and also the target cell supports
acceptance through HS-DSCH/DCH instead of HS-DSCH/E-DCH, a decision of
inter-frequency
hard
handover
with
HS-DSCH/E-DCH
transferring
to
HS-DSCH/DCH is made.
5
HS-DSCH/DCH->HS-DSCH/E-DCH
The current service of the UE includes HSPA and also the HS-DSCH/DCH is used
before the handover. If the original decision is to trigger an inter-frequency handover
(measurement-based or blind handover) and also the target cell supports
acceptance through HS-DSCH/E-DCH, a decision of inter-frequency hard handover
with HS-DSCH/DCH transferring to HS-DSCH/E-DCH is made.
174
11.4
Inter-RAT Handover
1
UTRAN->GSM/GERAN/LTE
The HSPA service is included, and then the same handover flow as that for between
R99 systems is performed.
GSM/GERAN/LTE-> UTRAN
Similar to the handover between R99 systems, if the target cell support
HS-DSCH/E-DCH, the service is established directly on HS-DSCH/E-DCH.
12
12.1
Cells that support both MBMS and non-MBMS (Support MBMS and not MBMS).
Intra-frequency Handover
1
The soft add strategy does not consider whether the soft add cell belongs to the
service area or whether it supports the MBMS in the case of 1A/1C soft add. That is,
the strategy is similar to that for the non-MBMS case.
For the MBMS service that has set up p-t-p bearer but the link is deleted, if the best
cell does not belong to MBMS service area, the best cell does not support the
MBMS service, the best cell has set up the p-t-m bearer, or the best cell is not the
convergence carrier of the service, then p-t-p RB is released.
175
For the MBMS service that has not set up p-t-p bearer but the MBMS service
connection already exists, the best cell belongs to MBMS service area, the best cell
supports the MBMS service, the bearer type strategy needs to set up the p-t-m
bearer and the carrier can set up the bearer of the service, then p-t-p RB is set up.
The principle of the type change in the bearer of the MBMS service in the active set
under the macro diversity.
Table 12-1
Table of Principle
Cell Type
Principles of Change
Best cell
No change
p-t-p->p-t-m
Set up p-t-p: If the channel of the service is DCH,
Best cell
p-t-m ->p-t-p
then set up p-t-p for all cells in the active set. If the
channel of the service is HS-DSCH, then set up
p-t-p in the best cell.
No change
To avoid ping-pong switch between p-t-p and p-t-m, a time threshold (T1d(UHspa)) is
configured and any switchover should occur at an interval longer than this threshold.
12.2
Inter-frequency Handover
When the UE reports MBMS MODIFIED REQUEST and the information of MBMS
preferred frequency request is carried,
1
If the target carrier comes with a cell with the same coverage (included: the
expected frequency layer cell includes the current working frequency cell) and the
cell belongs to the service area and supports the MBMS, and also the target cell is
able to allocate the resource of currently established dedicated bearer, then the cell
with the same coverage at the frequency layer can be taken as the target cell to
perform the hard handover.
If the target carrier does not come with a cell with the same coverage (included), the
neighbor cell of the current cell in the UEs active set includes the neighbor cell
176
13
13.1
13.1.1
Parameter List
No.
Field Name
1.
MeasPrio
2.
DetSetHoSwch
3.
RptRange
[MAX_INTRA_MEAS_EVE
NT] (UIntraEcNoEvMeas)
4.
RptRange
[MAX_INTRA_MEAS_EVE
NT]
(UIntraEcNoEvMeasForD)
5.
RptRange
[MAX_INTRA_MEAS_EVE
NT] (UIntraRscpEvMeas)
6.
RptRange
[MAX_INTRA_MEAS_EVE
NT]
(UIntraRscpEvMeasForD)
7.
W[MAX_INTRA_MEAS_EV
ENT] (UIntraEcNoEvMeas)
177
8.
W[MAX_INTRA_MEAS_EV
ENT]
(UIntraEcNoEvMeasForD)
9.
W[MAX_INTRA_MEAS_EV
ENT] (UIntraRscpEvMeas)
10.
W[MAX_INTRA_MEAS_EV
ENT]
(UIntraRscpEvMeasForD)
11.
Hysteresis[MAX_INTRA_M
EAS_EVENT]
Hysteresis
(UIntraEcNoEvMeas)
12.
Hysteresis[MAX_INTRA_M
EAS_EVENT]
Hysteresis
(UIntraEcNoEvMeasForD)
13.
Hysteresis[MAX_INTRA_M
EAS_EVENT]
Hysteresis
(UIntraRscpEvMeas)
14.
Hysteresis[MAX_INTRA_M
EAS_EVENT]
Hysteresis
(UIntraRscpEvMeasForD)
15.
FilterCoeff(UIntraEcNoEvM
eas)
16.
FilterCoeff(UIntraEcNoEvM
easForD)
17.
FilterCoeff(UIntraEcNoPrd
Meas)
18.
FilterCoeff(UIntraRscpEvM
eas)
19.
FilterCoeff(UIntraRscpEvM
easForD)
20.
FilterCoeff(UIntraRscpPrdM
eas)
21.
Filter Coefficient
Filter Coefficient
Filter Coefficient
Filter Coefficient
Filter Coefficient
Filter Coefficient
TrigTime[MAX_INTRA_ME
AS_EVENT]
Time to Trigger
(UIntraEcNoEvMeas)
178
22.
TrigTime[MAX_INTRA_ME
AS_EVENT]
Time to Trigger
(UIntraEcNoEvMeasForD)
23.
TrigTime[MAX_INTRA_ME
AS_EVENT]
Time to Trigger
(UIntraRscpEvMeas)
24.
TrigTime[MAX_INTRA_ME
AS_EVENT]
Time to Trigger
(UIntraRscpEvMeasForD)
25.
PrdRptAmount(UIntraEcNo
PrdMeas)
26.
PrdRptAmount(UIntraRscp
PrdMeas)
27.
PrdRptInterval(UIntraEcNo
PrdMeas)
28.
PrdRptInterval(UIntraRscp
PrdMeas)
29.
CellIndividualOffset(UUtran
CellFDD)
30.
CellIndivOffset(UUtranRelat
ion)
31.
RptDeactThr(UIntraEcNoEv
Meas)
1A
RptDeactThr(UIntraEcNoEv
MeasForD)
1A
RptDeactThr(UIntraRscpEv
Meas)
1A
RptDeactThr(UIntraRscpEv
MeasForD)
1A
RplcActThr
(UIntraEcNoEvMeas)
1C and 1J
RplcActThr
(UIntraRscpEvMeas)
1C and 1J
37.
profileId(UIntraMeasProfile)
Profile Id
38.
profileId(UUeIntMeasProfile
32.
33.
34.
35.
36.
Profile Id
179
39.
ref1UIntraMeasProfile
40.
refUUeIntMeasProfile
41.
IntraMeasCfgNo(UIntraEcN
oEvMeas)
Index
IntraMeasCfgNo(UIntraEcN
oEvMeasForD)
Index
IntraMeasCfgNo(UIntraEcN
oPrdMeas)
Index
IntraMeasCfgNo(UIntraRsc
pEvMeas)
Index
IntraMeasCfgNo(UIntraRsc
pEvMeasForD)
Index
IntraMeasCfgNo(UIntraRsc
pPrdMeas)
Index
42.
43.
44.
45.
46.
47.
MeaEvtId[MAX_INTRA_ME
AS_EVENT]
(UIntraEcNoEvMeas)
48.
MeaEvtId[MAX_INTRA_ME
AS_EVENT]
(UIntraRscpEvMeas)
49.
srvCategory
50.
IntraMeasCfgNote
51.
MeasEvtNum
(UIntraEcNoEvMeas)
Measurement
MeasEvtNum
(UIntraRscpEvMeas)
Measurement
52.
53.
ThreshUsedFreq[MAX_INT
RA_MEAS_EVENT]
(UIntraEcNoEvMeas)
54.
ThreshUsedFreq[MAX_INT
RA_MEAS_EVENT]
(UIntraRscpEvMeas)
55.
StateMode(UUtranRelation)
180
56.
57.
IntraMeasQuan
EvtRptInterval(UIntraEcNo
EvMeas)
58.
EvtRptInterval(UIntraEcNo
EvMeasForD)
59.
EvtRptInterval(UIntraRscpE
vMeas)
60.
EvtRptInterval(UIntraRscpE
vMeasForD)
61.
EvtRptAmount(UIntraEcNo
EvMeas)
62.
EvtRptAmount(UIntraEcNo
EvMeasForD)
63.
EvtRptAmount(UIntraRscp
EvMeas)
64.
EvtRptAmount(UIntraRscp
EvMeasForD)
65.
PcpichPwrPre
66.
primaryCpichPower
67.
rlRefTimeAjtSw
68.
TimeDelay
69.
ATimeDelay(UExternalUtra
nCellFDD)
70.
71.
72.
73.
74.
75.
RncFeatSwitchBit4
NrtMaxUlRateDch
NrtMaxDlRateDch
RtMaxUlRateDch
RtMaxDlRateDch
RtMaxRateEdch
181
76.
77.
78.
79.
80.
81.
82.
83.
84.
85.
86.
NrtMaxRateEdch
NrtMaxUlRateDchD
NrtMaxDlRateDchD
RtMaxUlRateDchD
RtMaxDlRateDchD
NrtMaxRateEdchD
RtMaxRateEdchD
Cs64Switch
AdjCs64Switch
NbrCellMonSupInd
UeIntMCfgNo(URlEvtRttUeI
nt)
Index
87.
88.
TxRxTDThres[MAX_UE_IN
TER_MEAS_EVENT]
(URlEvtRttUeInt)
89.
90.
91.
92.
93.
AddNRLSHOSwch
IntraHoEcNoThrd
IntraHoRscpThrd
HOCELSELSCENE
TWAITACTSETUPCMP
182
94.
MeasRptTrMod(URlEvtRttU
eInt)
95.
FilterCoeff(URlEvtRttUeInt)
Filter coefficient
96.
MeaEvtId(URlEvtRttUeInt)
97.
TrigTime[MAX_UE_INTER
Time to Trigger
_MEAS_EVENT]
(URlEvtRttUeInt)
98.
99.
100.
101.
MeasEvtNum(URlEvtRttUeI
nt)
Measurement
RncFeatSwitchBit18
RncFeatSwitchBit15
DRNC's Cell
NotUse/Use DSCR for PS Service When UE
RncFeatSwitchBit7
102.
ParallelSoftHO
Handover
103.
104.
105.
CsIntraEvtSwch
RncFeatSwitchBit16
intialHoCelSelScene(UIntra
MeasProfile)
106.
EnhanceHoSwch
107.
CResPara5
108.
gRESPARA47
13.1.2
Parameter Configurations
13.1.2.1
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->UTRAN
183
Parameter configuration
This parameter indicates the measurement priority of the neighbouring cell. The priority
of the neighbouring cell can be set to 0, 1, or 2, of which, 0 represents the highest priority
and 2 represents the lowest priority. The priority of the neighbouring is set by the
configuration personnel according to the signal strength and distance of the neighboring
cell.
The neighbouring cells with the priority ranked the 33
rd
neighboring cell reservation list. When the number of cells in the neighbouring cell list is
less than 32, the cell(s) with higher priority in the neighbouring cell reservation list are
placed to the neighbouring cell list.
13.1.2.2
OMC path
Parameter configuration
The measurement control message that contains the detected set information is sent
only when the DetSetHO switch of the best cell in the current active set is set to 1 and the
current number of intra-frequency neighbouring cells is less than 32.
13.1.2.3
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Related
Measurement
to
Traffic
Parameter configuration
Event 1A is easier to be triggered when the reporting range constant for event 1A is set to
a larger value; and vice verse.
184
Event 1B is easier to be triggered when the reporting range constant for event 1B is set
to a smaller value; and vice verse.
13.1.2.4
GUI:
OMC path
Managed
Element
->UMTS
Configuration->Measurement
Profile->Intra-frequency
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Measurement
Unrelated
to
Traffic
Parameter configuration
Event 1A is easier to be triggered when the reporting range constant for event 1A is set to
a larger value; and vice verse.
Event 1B is easier to be triggered when the reporting range constant for event 1B is set
to a smaller value; and vice verse.
13.1.2.5
GUI:
OMC path
Managed
Element
->UMTS
Configuration->Measurement
Profile->Intra-frequency
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Related
Measurement
to
Traffic
Parameter configuration
Event 1A is easier to be triggered when the reporting range constant for event 1A is set to
a larger value; and vice verse.
Event 1B is easier to be triggered when the reporting range constant for event 1B is set
to a smaller value; and vice verse.
185
13.1.2.6
GUI:
OMC path
Managed
Element
->UMTS
Configuration->Measurement
Profile->Intra-frequency
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Unrelated
Measurement
to
Traffic
Parameter configuration
Event 1A is easier to be triggered when the reporting range constant for event 1A is set to
a larger value; and vice verse.
Event 1B is easier to be triggered when the reporting range constant for event 1B is set
to a smaller value; and vice verse.
13.1.2.7
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Related
Measurement
to
Traffic
Parameter configuration
This parameter is used for the quality judgment of event 1A and 1B. This parameter
indicates the weight of the best cell in the quality judgment and is related to the
measurement quantity and the event type.
See the description of the formula for triggering event 1A/1B in section 4.3 for the effects
of this parameter on the quality judgment.
13.1.2.8
OMC path
186
GUI:
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Unrelated
Measurement
to
Traffic
Parameter configuration
This parameter is used for the quality judgment of event 1A and 1B. This parameter
indicates the weight of the best cell in the quality judgment and is related to the
measurement quantity and the event type.
See the description of the formula for triggering event 1A/1B in section 4.3 for the effects
of this parameter on the quality judgment.
13.1.2.9
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Related
Measurement
to
Traffic
Parameter configuration
This parameter is used for the quality judgment of event 1A and 1B. This parameter
indicates the weight of the best cell in the quality judgment and is related to the
measurement quantity and the event type.
See the description of the formula for triggering event 1A/1B in section 4.3 for the effects
of this parameter on the quality judgment.
13.1.2.10
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
187
Profile->Intra-frequency
Measurement
Configuration
Unrelated
to
Traffic
Parameter configuration
This parameter is used for the quality judgment of event 1A and 1B. This parameter
indicates the weight of the best cell in the quality judgment and is related to the
measurement quantity and the event type.
See the description of the formula for triggering event 1A/1B in section 4.3 for the effects
of this parameter on the quality judgment.
13.1.2.11
Hysteresis(UIntraEcNoEvMeas)
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Related
Measurement
to
Traffic
Parameter configuration
This parameter indicates the hysteresis when judging whether to trigger the event. This
parameter avoids the change of the trigger status due to very small change. This
parameter is related to the measurement quantity and the event type.
If a small hysteresis is configured, the corresponding event will be reported in a higher
probability; and vice versa.
13.1.2.12
Hysteresis(UIntraEcNoEvMeasForD)
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Unrelated
Measurement
to
Traffic
188
Parameter configuration
This parameter indicates the hysteresis when judging whether to trigger the event. This
parameter avoids the change of the trigger status due to very small change. This
parameter is related to the measurement quantity and the event type.
If a small hysteresis is configured, the corresponding event will be reported in a higher
probability; and vice versa.
13.1.2.13
Hysteresis(UIntraRscpEvMeas)
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Related
Measurement
to
Traffic
Parameter configuration
This parameter indicates the hysteresis when judging whether to trigger the event. This
parameter avoids the change of the trigger status due to very small change. This
parameter is related to the measurement quantity and the event type.
If a small hysteresis is configured, the corresponding event will be reported in a higher
probability; and vice versa.
13.1.2.14
Hysteresis(UIntraRscpEvMeasForD)
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Unrelated
Measurement
to
Traffic
Parameter configuration
189
This parameter indicates the hysteresis when judging whether to trigger the event. This
parameter avoids the change of the trigger status due to very small change. This
parameter is related to the measurement quantity and the event type.
If a small hysteresis is configured, the corresponding event will be reported in a higher
probability; and vice versa.
13.1.2.15
Filter Coefficient(UIntraEcNoEvMeas)
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Related
Measurement
to
Traffic
Parameter configuration
This parameter indicates the filtering factor that the UE performs the L3 filtering on the
measurement results of the intra-frequency measurement. The smaller the value of the
filtering factor is, the larger effect the current measurement result will have on the
measurement result reported to RNC (periodical report) or the judgment (event report).
13.1.2.16
Filter Coefficient(UIntraEcNoEvMeasForD)
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Unrelated
Measurement
to
Traffic
Parameter configuration
This parameter indicates the filtering factor that the UE performs the L3 filtering on the
measurement results of the intra-frequency measurement. The smaller the value of the
filtering factor is, the larger effect the current measurement result will have on the
190
measurement result reported to RNC (periodical report) or the judgment (event report).
13.1.2.17
Filter Coefficient(UIntraEcNoPrdMeas)
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Unrelated
Measurement
to
Traffic
Parameter configuration
This parameter indicates the filtering factor that the UE performs the L3 filtering on the
measurement results of the intra-frequency measurement. The smaller the value of the
filtering factor is, the larger effect the current measurement result will have on the
measurement result reported to RNC (periodical report) or the judgment (event report).
13.1.2.18
Filter Coefficient(UIntraRscpEvMeas)
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Related
Measurement
to
Traffic
Parameter configuration
This parameter indicates the filtering factor that the UE performs the L3 filtering on the
measurement results of the intra-frequency measurement. The smaller the value of the
filtering factor is, the larger effect the current measurement result will have on the
measurement result reported to RNC (periodical report) or the judgment (event report).
13.1.2.19
Filter Coefficient(UIntraRscpEvMeasForD)
OMC path
191
GUI:
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Unrelated
Measurement
to
Traffic
Parameter configuration
This parameter indicates the filtering factor that the UE performs the L3 filtering on the
measurement results of the intra-frequency measurement. The smaller the value of the
filtering factor is, the larger effect the current measurement result will have on the
measurement result reported to RNC (periodical report) or the judgment (event report).
13.1.2.20
Filter Coefficient(UIntraRscpPrdMeas)
OMC path
GUI:
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Unrelated
Measurement
to
Traffic
Parameter configuration
This parameter indicates the filtering factor that the UE performs the L3 filtering on the
measurement results of the intra-frequency measurement. The smaller the value of the
filtering factor is, the larger effect the current measurement result will have on the
measurement result reported to RNC (periodical report) or the judgment (event report).
13.1.2.21
Time to Trigger(UIntraEcNoEvMeas)
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Related
Measurement
to
Traffic
192
Parameter configuration
This parameter indicates the time difference between the time that the event generation
is detected and the time that the event is reported. The event is triggered and the
measurement report is reported only when the event generation is detected and still
meets the requirements of event triggering after Time to trigger.
The larger the value is, the stricter the judgment is for the event to be triggered. The
parameter should be configured according to the actual requirements.
13.1.2.22
Time to Trigger(UIntraEcNoEvMeasForD)
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Unrelated
Measurement
to
Traffic
Parameter configuration
This parameter indicates the time difference between the time that the event generation
is detected and the time that the event is reported. The event is triggered and the
measurement report is reported only when the event generation is detected and still
meets the requirements of event triggering after Time to trigger.
The larger the value is, the stricter the judgment is for the event to be triggered. The
parameter should be configured according to the actual requirements.
13.1.2.23
Time to Trigger(UIntraRscpEvMeas)
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Related
Measurement
to
Traffic
193
Parameter configuration
This parameter indicates the time difference between the time that the event generation
is detected and the time that the event is reported. The event is triggered and the
measurement report is reported only when the event generation is detected and still
meets the requirements of event triggering after Time to trigger.
The larger the value is, the stricter the judgment is for the event to be triggered. The
parameter should be configured according to the actual requirements.
13.1.2.24
Time to Trigger(UIntraRscpEvMeasForD)
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Unrelated
Measurement
to
Traffic
Parameter configuration
This parameter indicates the time difference between the time that the event generation
is detected and the time that the event is reported. The event is triggered and the
measurement report is reported only when the event generation is detected and still
meets the requirements of event triggering after Time to trigger.
The larger the value is, the stricter the judgment is for the event to be triggered. The
parameter should be configured according to the actual requirements.
13.1.2.25
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Unrelated
Measurement
to
Traffic
194
Parameter configuration
This parameter indicates the times of the periodical reports to be reported. In the case of
the UE side, the value is used for the determination of whether to report the
measurement report in reporting the periodical report. If the UE detects that the times of
event reporting exceeds the value of Amount of reporting, the UE stops reporting the
measurement results.
13.1.2.26
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Measurement
Unrelated
to
Traffic
Parameter configuration
This parameter indicates the times of the periodical reports to be reported. In the case of
the UE side, the value is used for the determination of whether to report the
measurement report in reporting the periodical report. If the UE detects that the times of
event reporting exceeds the value of Amount of reporting, the UE stops reporting the
measurement results.
13.1.2.27
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Unrelated
Measurement
to
Traffic
Parameter configuration
This parameter indicates the interval of periodical reporting specified in the periodical
195
reporting criteria. In the case of the periodical reporting, the UE reports the measurement
reports in the period indicated by the parameter.
13.1.2.28
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Unrelated
Measurement
to
Traffic
Parameter configuration
This parameter indicates the interval of periodical reporting specified in the periodical
reporting criteria. In the case of the periodical reporting, the UE reports the measurement
reports in the period indicated by the parameter.
13.1.2.29
OMC path
Parameter configuration
This parameter defines the individual offset of cells in the active set relative to other cells.
When the value is positive, a positive value is added to the measurement result. If the
value is negative, a negative value is added to the measurement result. Refer to the
description of the formula for triggering event 1B/1C/1d in section 4.3 for the effect of this
parameter on the measurement report.
Through the configuration of the individual offset of a single cell, the trigger difficulty of
the cell can be adjusted to meet the practical requirements of network planning without
the need to modify the global handover parameters.
196
13.1.2.30
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->UTRAN
Parameter configuration
This parameter defines the individual offset of cells outside the active set relative to other
cells. When the value is positive, a positive value is added to the measurement result. If
the value is negative, a negative value is added to the measurement result. Refer to the
description of the formula for triggering event 1A/1C/1d in section 4.3 for the effect of this
parameter on the measurement report.
Through the configuration of the individual offset of a single cell, the trigger difficulty of
the cell can be adjusted to meet the practical requirements of network planning without
the need to modify the global handover parameters.
13.1.2.31
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Related
Measurement
to
Traffic
Parameter configuration
This parameter indicates the maximum number of the cells allowed in the active set.
When the UE detects that one cell in the monitoring set satisfies the trigger threshold of
event 1A, it determines whether the number of the cells in the current active set greater
than the value indicated by this parameter at first. If yes, the event 1A is not triggered.
13.1.2.32
OMC path
197
GUI:
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Unrelated
Measurement
to
Traffic
Parameter configuration
This parameter indicates the maximum number of the cells allowed in the active set.
When the UE detects that one cell in the monitoring set satisfies the trigger threshold of
event 1A, it determines whether the number of the cells in the current active set greater
than the value indicated by this parameter at first. If yes, the event 1A is not triggered.
13.1.2.33
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Related
Measurement
to
Traffic
Parameter configuration
This parameter indicates the maximum number of the cells allowed in the active set.
When the UE detects that one cell in the monitoring set satisfies the trigger threshold of
event 1A, it determines whether the number of the cells in the current active set greater
than the value indicated by this parameter at first. If yes, the event 1A is not triggered.
13.1.2.34
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Unrelated
Measurement
to
Traffic
198
Parameter configuration
This parameter indicates the maximum number of the cells allowed in the active set.
When the UE detects that one cell in the monitoring set satisfies the trigger threshold of
event 1A, it determines whether the number of the cells in the current active set greater
than the value indicated by this parameter at first. If yes, the event 1A is not triggered.
13.1.2.35
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Related
Measurement
to
Traffic
Parameter configuration
This parameter indicates the minimum number of the cell allowed in the DCH active set
when triggering event 1C or in the E-DCH active set when triggering event 1j. When the
UE detects that the measurement result of a cell satisfies the trigger threshold of event
1c/1j, it first judges whether the number of cells in the current active set is smaller than
the value indicated by this parameter. If yes, event 1C/1j is not triggered.
13.1.2.36
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Related
Measurement
to
Traffic
Parameter configuration
199
This parameter indicates the minimum number of the cell allowed in the DCH active set
when triggering event 1C or in the E-DCH active set when triggering event 1j. When the
UE detects that the measurement result of a cell satisfies the trigger threshold of event
1c/1j, it first judges whether the number of cells in the current active set is smaller than
the value indicated by this parameter. If yes, event 1C/1j is not triggered.
13.1.2.37
Profile Id(UIntraMeasProfile)
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
13.1.2.38
Profile Id(UUeIntMeasProfile)
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
13.1.2.39
OMC path
Parameter configuration
200
13.1.2.40
OMC path
Parameter configuration
13.1.2.41
GUI:
OMC path
Managed
Element
->UMTS
Configuration->Measurement
Profile->Intra-frequency
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Related
Measurement
to
Traffic
Parameter configuration
is,
the
parameter
Intra-frequency
Measurement
Profile
Identity(namely
13.1.2.42
OMC path
201
GUI:
Managed
Element
->UMTS
Configuration->Measurement
Profile->Intra-frequency
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Unrelated
Measurement
to
Traffic
Parameter configuration
is,
the
parameter
Intra-frequency
Measurement
Profile
Identity(namely
13.1.2.43
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Unrelated
Measurement
to
Traffic
Parameter configuration
202
That
is,
the
parameter
Intra-frequency
Measurement
Profile
Identity(namely
13.1.2.44
GUI:
OMC path
Managed
Element
->UMTS
Configuration->Measurement
Profile->Intra-frequency
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Related
Measurement
to
Traffic
Parameter configuration
is,
the
parameter
Intra-frequency
Measurement
Profile
Identity(namely
13.1.2.45
OMC path
203
GUI:
Managed
Element
->UMTS
Configuration->Measurement
Profile->Intra-frequency
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Unrelated
Measurement
to
Traffic
Parameter configuration
is,
the
parameter
Intra-frequency
Measurement
Profile
Identity(namely
13.1.2.46
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Unrelated
Measurement
to
Traffic
Parameter configuration
204
That
is,
the
parameter
Intra-frequency
Measurement
Profile
Identity(namely
13.1.2.47
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Related
Measurement
to
Traffic
Parameter configuration
This parameter indicates the identity of the event triggered by the intra-frequency
measurement (1A~1D).
13.1.2.48
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Related
Measurement
to
Traffic
Parameter configuration
This parameter indicates the identity of the event triggered by the intra-frequency
measurement (1A~1D).
205
13.1.2.49
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Parameter configuration
All the services are classified into eight categories according to the real-time attribute of
services, channel type, and service quantity. This parameter indicates the service and
bearer type. The handover parameters can be configured flexibly for different scenarios
and the parameters may have different handover triggering thresholds and hysteresis.
The value 0xff (Not Related to Service Type) is exclusive used in the measurement of
the detected set.
13.1.2.50
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
This parameter indicates the purpose and functions of the set of intra-frequency
measurement configuration parameters.
13.1.2.51
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Related
Measurement
to
Traffic
206
Parameter configuration
This parameter indicates the number of events that should be configured for the set of
the intra-frequency measurement parameters for a certain purpose. The value is related
to the purpose of the measurement and the judgment method and the algorithm of the
soft handover.
13.1.2.52
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Related
Measurement
to
Traffic
Parameter configuration
This parameter indicates the number of events that should be configured for the set of
the intra-frequency measurement parameters for a certain purpose. The value is related
to the purpose of the measurement and the judgment method and the algorithm of the
soft handover.
13.1.2.53
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Related
Measurement
to
Traffic
Parameter configuration
This parameter indicates the absolute threshold used for judging event 1e/1f by using
carrier frequency.
207
13.1.2.54
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Related
Measurement
to
Traffic
Parameter configuration
This parameter indicates the absolute threshold used for judging event 1e/1f by using
carrier frequency.
13.1.2.55
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->UTRAN
Parameter configuration
This parameter indicates the UE status used for the neighboring cell. When the
neighbouring cell is configured by the status, the neighbouring cell list used for
reselection in non-dedicated mode and the neighbouring cell list used for handover in
dedicated mode are differentiated as follows:
When SIB11/SIB12/SIB11bis is to be sent, the UE selects the cell whose state is only
cell selection/reselection or cell selection/reselection and handover from the
neighboring cells list and fills in SIB11/SIB12/SIB11bis;
When the measurement control message is to be sent, the UE selects the cell whose
state is only cell handover from the neighboring cells list.
208
13.1.2.56
OMC path
Parameter configuration
This parameter indicates the measurement quantity (Ec/No or RSCP) for the
intra-frequency measurement of the cell. The measurement quantity Ec/No is
recommended.
13.1.2.57
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Related
Measurement
to
Traffic
Parameter configuration
This parameter indicates the reporting interval for event 1A/1B/1C/1J. Once Event 1A/1C
meets the reporting range of quality standards, the UE will report Event 1A/1C
periodically (EvtRptInterval) until this event does not meet reporting conditions or the
reporting times reach the maximum allowed times (EvtRptAmount).
13.1.2.58
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Unrelated
Measurement
to
Traffic
Parameter configuration
209
This parameter indicates the reporting interval for event 1A/1B/1C/1J. Once Event 1A/1C
meets the reporting range of quality standards, the UE will report Event 1A/1C
periodically (EvtRptInterval) until this event does not meet reporting conditions or the
reporting times reach the maximum allowed times (EvtRptAmount).
13.1.2.59
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Related
Measurement
to
Traffic
Parameter configuration
This parameter indicates the reporting interval for event 1A/1B/1C/1J. Once Event 1A/1C
meets the reporting range of quality standards, the UE will report Event 1A/1C
periodically (EvtRptInterval) until this event does not meet reporting conditions or the
reporting times reach the maximum allowed times (EvtRptAmount).
13.1.2.60
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Unrelated
Measurement
to
Traffic
Parameter configuration
This parameter indicates the reporting interval for event 1A/1B/1C/1J. Once Event 1A/1C
meets the reporting range of quality standards, the UE will report Event 1A/1C
periodically (EvtRptInterval) until this event does not meet reporting conditions or the
reporting times reach the maximum allowed times (EvtRptAmount).
210
13.1.2.61
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Measurement
Related
to
Traffic
Parameter configuration
This parameter indicates the reporting amount for event 1A/1B/1C/1J. Once Event 1A/1C
meets the reporting range of quality standards, the UE will report Event 1A/1C
periodically (EvtRptInterval) until this event does not meet reporting conditions or the
reporting times reach the maximum allowed times (EvtRptAmount).
13.1.2.62
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Measurement
Unrelated
to
Traffic
Parameter configuration
This parameter indicates the reporting amount for event 1A/1B/1C/1J. Once Event 1A/1C
meets the reporting range of quality standards, the UE will report Event 1A/1C
periodically (EvtRptInterval) until this event does not meet reporting conditions or the
reporting times reach the maximum allowed times (EvtRptAmount).
13.1.2.63
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
211
Profile->Intra-frequency
Measurement
Configuration
Related
to
Traffic
Parameter configuration
This parameter indicates the reporting amount for event 1A/1B/1C/1J. Once Event 1A/1C
meets the reporting range of quality standards, the UE will report Event 1A/1C
periodically (EvtRptInterval) until this event does not meet reporting conditions or the
reporting times reach the maximum allowed times (EvtRptAmount).
13.1.2.64
GUI:
OMC path
Managed
Element
Configuration->Measurement
Profile->Intra-frequency
->UMTS
Logical
Function
Configuration->Service
Configuration->Intra-frequency
Measurement
Configuration
Unrelated
Measurement
to
Traffic
Parameter configuration
This parameter indicates the reporting amount for event 1A/1B/1C/1J. Once Event 1A/1C
meets the reporting range of quality standards, the UE will report Event 1A/1C
periodically (EvtRptInterval) until this event does not meet reporting conditions or the
reporting times reach the maximum allowed times (EvtRptAmount).
13.1.2.65
OMC path
Parameter configuration
212
13.1.2.66
OMCR Interface
Parameter configuration
13.1.2.67
OMCR Interface
Parameter configuration
When the switch is closed, RNC will not send measurement control of 6F/6G to UE;
when it is open, RNC may send measurement control of 6F/6G.
13.1.2.68
OMCR Interface
Parameter configuration
This parameter indicates the Iub transport time delay, it could be 20ms/100ms/250ms.
213
13.1.2.69
OMCR Interface
Parameter configuration
This parameter indicates the Iub transport time delay of external UTRAN cell. It could be
20ms/100ms/250ms.
13.1.2.70
OMCR Interface
Parameter configuration
This parameter indicates whether to use DSCR in inter-RNC handover of HSPA service.
RncFeatSwitchBit4=0: not use; RncFeatSwitchBit4=1: use.
13.1.2.71
OMCR Interface
Parameter configuration
This parameter indicates the maximum bit rate on UL DCH allowed in serving cell for an
NRT PS domain RAB.
13.1.2.72
OMCR Interface
214
Parameter configuration
This parameter indicates the maximum bit rate on DL DCH allowed in serving cell for an
NRT PS domain RAB.
13.1.2.73
GUI:
OMCR Interface
Managed
Element
->UMTS
Logical
Function
Configuration->UTRAN
Parameter configuration
This parameter indicates the maximum bit rate on UL DCH allowed in serving cell for an
RT PS domain RAB.
13.1.2.74
GUI:
OMCR Interface
Managed
Element
->UMTS
Logical
Function
Configuration->UTRAN
Parameter configuration
This parameter indicates the maximum bit rate on DL DCH allowed in serving cell for an
RT PS domain RAB.
13.1.2.75
GUI:
OMCR Interface
Managed
Element
->UMTS
Logical
Function
Configuration->UTRAN
215
Parameter configuration
This parameter indicates the maximum bit rate on E-DCH allowed in serving cell for an
RT PS domain RAB.
13.1.2.76
GUI:
OMCR Interface
Managed
Element
->UMTS
Logical
Function
Configuration->UTRAN
Parameter configuration
This parameter indicates the maximum bit rate on E-DCH allowed in serving cell for an
RT PS domain RAB.
13.1.2.77
Maximum Bit Rate on UL DCH for NRT PS RAB in External UTRAN Cell
OMCR Interface
Parameter configuration
This parameter indicates the maximum bit rate on UL DCH allowed in the DRNC cell for
an NRT PS domain RAB.
13.1.2.78
Maximum Bit Rate on DL DCH for NRT PS RAB in External UTRAN Cell
OMCR Interface
Parameter configuration
216
This parameter indicates the maximum bit rate on DL DCH allowed in the DRNC cell for
an NRT PS domain RAB.
13.1.2.79
OMCR Interface
Parameter configuration
This parameter indicates the maximum bit rate on UL DCH allowed in the DRNC cell for
an RT PS domain RAB.
13.1.2.80
OMCR Interface
Parameter configuration
This parameter indicates the maximum bit rate on DL DCH allowed in the DRNC cell for
an RT PS domain RAB.
13.1.2.81
Maximum Bit Rate on E-DCH for NRT PS RAB in External UTRAN Cell
OMCR Interface
Parameter configuration
This parameter indicates the maximum bit rate on UL E-DCH allowed in the DRNC cell
for an NRT PS domain RAB.
217
13.1.2.82
OMCR Interface
Parameter configuration
This parameter indicates the maximum bit rate on UL E-DCH allowed in the DRNC cell
for an RT PS domain RAB.
13.1.2.83
OMCR Interface
Parameter configuration
This parameter indicates whether establishing traffic CS 64kbps in serving cell is allowed
or not.
13.1.2.84
OMCR Interface
Parameter configuration
This parameter indicates whether establishing traffic CS 64kbps in external UTRAN cell
is allowed or not.
13.1.2.85
OMC path
218
Parameter configuration
13.1.2.86
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
13.1.2.87
The Time Threshold that the RNC May Resend the MEASUREMENT
CONTROL RELEASE
OMC path
Parameter configuration
This parameter indicates the time threshold that the RNC may resend the
MEASUREMENT CONTROL RELEASE.
When RNC send MEASUREMENT CONGROL RELEASE message for a measurement
ID, the time stamp will be recorded. If RNC receive the measurement report for the ID, it
will be compared between current time and recorded time. If difference between current
219
time and recorded time exceed the threshold configured, the MEASUREMENT
CONTROL RELEASE will be resent, otherwise ignore this measurement report.
13.1.2.88
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
This parameter indicates the UE Rx-Tx time difference reporting threshold in chips in
event 6f/6g.
13.1.2.89
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->UTRAN
Parameter configuration
This parameter indicates whether RNC handle the adding new radio link in soft handover,
when the signal quality of new radio link is lower than IntraHoEcNoThrd or
IntraHoRscpThrd.
13.1.2.90
OMC path
Parameter configuration
220
The parameter indicates the Cpich EcNo minimum threshold for intra frequency
handover. If reported Cpich EcNo is less than this threshold, intra frequency handover
will not be triggered.
13.1.2.91
OMC path
Parameter configuration
The parameter indicates the Cpich RSCP minimum threshold for intra frequency
handover. If reported Cpich RSCP is less than this threshold, intra frequency handover
will not be triggered.
13.1.2.92
OMC path
Parameter configuration
13.1.2.93
OMC path
The
Parameter configuration
parameter
indicates
time
of
Waiting
for
CELL
UPDATE
After
RB
221
Stop: When the RNC receives the CELL UDPATE from UE. At expiry: The RNC releases
all RRC connection of UE.
13.1.2.94
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
This parameter indicates the RLC mode of the UE internal measurement report.
13.1.2.95
Filter coefficient(URlEvtRttUeInt)
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
This parameter indicates the filtering factor that the UE performs the L3 filtering on the
measurement results of the internal measurement.
13.1.2.96
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
222
13.1.2.97
Time to Trigger(URlEvtRttUeInt)
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
This parameter indicates the period of time during which the event condition has to be
satisfied before sending a measurement report.
13.1.2.98
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
13.1.2.99
OMC path
Parameter configuration
223
This parameter indicates whether adjacent RNC supports PS0/0 service or not.
RncFeatSwitchBit18=0: not support; RncFeatSwitchBit18=1: support.
OMC path
Parameter configuration
This parameter indicates whether to process 1A/1C/1D event of DRNCs cell or not when
CS and PS are concurrent via IUR.
RncFeatSwitchBit15=0: not process; RncFeatSwitchBit15=1: process.
13.1.2.101 NotUse/Use DSCR for PS Service When UE all RLs Have Moved to DRNC
OMC path
Parameter configuration
This parameter indicates whether to use DSCR for PS service or not when all RLs have
moved to DRNC.
13.1.2.102 Switch of RNC Send RL SETUP and ACTIVE SET UPDATE parallel when
Soft Add Handover
OMC path
Parameter configuration
224
This parameter indicates whether to process the procedures of RL ADD in Iub interface
and ACTIVE SET UPDATA in Uu interface parallelly when adding radio link in softer
handover.
OMC path
GUI:
Managed
Element
->UMTS
Logical
Function
Configuration->UTRAN
Parameter configuration
This parameter indicates whether event 1A/1C/1D of DRNCs cells is processed for CS
or not.
OMC path
Parameter configuration
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
225
The parameter indicates handover and cell reselection scenarios. For each scenario, the
corresponding parameters can be set as different values.
OMC path
Parameter configuration
The parameter indicates license which to control several enhanced handover features as
follows:
1 When RNC is waiting reconfiguration complete message from UE, if RNC receives the
ACK of AM RLC, then RNC consider the UU procedure completed.
2 When the signal quality of current used frequency is bad, whether intra-frequency
handover will be performed.
3 When the signal quality of current used frequency is bad, whether HSPA serving cell
change will be performed.
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->UTRAN
Parameter configuration
The parameter is the switch of indicating whether to judge the signal quality of target cell
when 1D event is reported.0: Off, 1: On.
226
OMC path
Parameter configuration
The bit14 of this parameter indicates the synchronous mode in intra-frequency hard
handover.
bit14=0, Timing re-initialised; bit14=1, Timing-maintained.
13.2
13.2.1
Parameter List
No.
Field Name
1.
MeasPrio
2.
ULMaxSIR
3.
UlBlerHoSwch
4.
UlPwrHoSwch
5.
DlPwrHoSwch
6.
HcsPrio(UUtranCellFDD)
HCS_PRIO
7.
HcsPrio(UExternalUtranC
ellFDD)
8.
InterHoTactic
9.
FilterCoeff(UInterEcNoEv
MeasforE)
10.
FilterCoeff(UInterEcNoEv
MeasforG)
11.
FilterCoeff(UInterEcNoEv
MeasforU)
12.
FilterCoeff(UInterEcNoPrd
Meas)
HCS_PRIO
Inter- frequency Handover Tactic
Filter Coefficient
Filter Coefficient
Filter Coefficient
Filter Coefficient
227
13.
FilterCoeff(UInterRscpEv
MeasforE)
14.
FilterCoeff(UInterRscpEv
MeasforG)
15.
FilterCoeff(UInterRscpEv
MeasforU)
16.
FilterCoeff(UInterRscpPrd
Meas)
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
Filter Coefficient
Filter Coefficient
Filter Coefficient
ThreshUsedFreq(UInterE
cNoEvMeasforE)
ThreshUsedFreq(UInterE
cNoEvMeasforG)
ThreshUsedFreq(UInterE
cNoEvMeasforU)
ThreshUsedFreq(UInterR
scpEvMeasforE)
ThreshUsedFreq(UInterR
scpEvMeasforG)
ThreshUsedFreq(UInterR
scpEvMeasforU)
Wused(UInterEcNoEvMe
asforE)
2A/2B/2D/2F
Wused(UInterEcNoEvMe
asforG)
2A/2B/2D/2F
Wused(UInterEcNoEvMe
asforU)
2A/2B/2D/2F
Wused(UInterRscpEvMea
sforE)
2A/2B/2D/2F
Wused(UInterRscpEvMea
sforG)
2A/2B/2D/2F
Wused(UInterRscpEvMea
sforU)
2A/2B/2D/2F
hysteresis(UInterEcNoEv
MeasforE)
30.
Filter Coefficient
hysteresis(UInterEcNoEv
MeasforG)
Hysteresis
Hysteresis
228
31.
hysteresis(UInterEcNoEv
MeasforU)
32.
hysteresis(UInterRscpEv
MeasforE)
33.
hysteresis(UInterRscpEv
MeasforG)
34.
hysteresis(UInterRscpEv
MeasforU)
35.
TrigTime(UInterEcNoEvM
easforE)
36.
TrigTime(UInterEcNoEvM
easforG)
37.
TrigTime(UInterEcNoEvM
easforU)
38.
TrigTime(UInterRscpEvM
easforE)
39.
TrigTime(UInterRscpEvM
easforG)
40.
TrigTime(UInterRscpEvM
easforU)
41.
42.
43.
44.
45.
Hysteresis
Time to Trigger
Time to Trigger
Time to Trigger
Time to Trigger
Time to Trigger
Time to Trigger
Absolute Threshold of the Quality of the
Non-used Frequency for 2B/2C/2E
ThreshNoUsedFreq(UInte
rRscpEvMeasforU)
WNoUsed(UInterEcNoEvM
easforU)
2A/2B/2C/2E
WNoUsed(UInterRscpEvMe
asforU)
2A/2B/2C/2E
PrdRptAmount(UInterEcN
PrdRptAmount(UInterRsc
PrdRptInterval(UInterEcN
oPrdMeas)
48.
Hysteresis
rEcNoEvMeasforU)
pPrdMeas)
47.
Hysteresis
ThreshNoUsedFreq(UInte
oPrdMeas)
46.
Hysteresis
PrdRptInterval(UInterRsc
pPrdMeas)
229
49.
PrdRptAmount(URatEcNo
PrdMeas)
50.
PrdRptAmount(URatRscp
PrdMeas)
51.
PrdRptInterval(URatEcNo
PrdMeas)
52.
PrdRptInterval(URatRscp
PrdMeas)
53.
ShareCover
54.
MaxDlDpchPwr
55.
profileId(UInterMeasProfil
e)
56.
profileId(UUeIntMeasProfi
le)
Profile Id
Profile Id
57.
refUInterMeasProfile
58.
refUUeIntMeasProfile
59.
InterMeasCfgNo(UInterEc
NoEvMeasforE)
Index
InterMeasCfgNo(UInterEc
NoEvMeasforG)
Index
InterMeasCfgNo(UInterEc
NoEvMeasforU)
Index
InterMeasCfgNo(UInterEc
NoPrdMeas)
Index
InterMeasCfgNo(UInterRs
cpEvMeasforE)
Index
InterMeasCfgNo(UInterRs
cpEvMeasforG)
Index
InterMeasCfgNo(UInterRs
cpEvMeasforU)
Index
InterMeasCfgNo(UInterRs
cpPrdMeas)
Index
60.
61.
62.
63.
64.
65.
66.
67.
meaEvtId
(UInterEcNoEvMeasforE)
68.
meaEvtId
(UInterEcNoEvMeasforG)
230
69.
meaEvtId
(UInterEcNoEvMeasforU)
70.
meaEvtId
(UInterRscpEvMeasforE)
71.
meaEvtId
(UInterRscpEvMeasforG)
72.
meaEvtId
(UInterRscpEvMeasforU)
73.
srvCategory
74.
InterMeasCfgNote
75.
MeasEvtNum
(UInterEcNoEvMeasforE)
Measurement
MeasEvtNum
(UInterEcNoEvMeasforG)
Measurement
MeasEvtNum
(UInterEcNoEvMeasforU)
Measurement
MeasEvtNum
(UInterRscpEvMeasforE)
Measurement
MeasEvtNum
(UInterRscpEvMeasforG)
Measurement
MeasEvtNum
(UInterRscpEvMeasforU)
Measurement
StateMode(UUtranRelatio
n)
76.
77.
78.
79.
80.
81.
82.
NonIntraMeasQuan
83.
PcpichPwrPre
84.
primaryCpichPower
85.
amrIfHoSw
86.
r99RtIfHoSw
87.
r99NrtIfHoSw
88.
hsdpaIfHoSw
89.
hsupaIfHoSw
90.
CompMdCfgStra
231
91.
92.
IfOrRatHoSwch
UeIntMCfgNo(UHoEvtTP
UeInt)
Index
93.
94.
HOCELSELSCENE
95.
txPowerThres(UHoEvtTP
UeInt)
96.
Accompanying Compressed
RncFeatSwitchBit9
97.
HcsSupportInd
98.
NotActivate/Activate
Compressed Mode for CS
RncFeatSwitchBit17
Service When Radio Link
via IUR Exists
99.
intialHoCelSelScene(UInt
erMeasProfile)
100.
101.
RncUlBlerHoSwch
RncTxPwrHoSwch
102.
InterHoMth
103.
IntRatHoMth
104.
PeriodTriggerTime
measRptTrMod(UHoEvtTPU
eInt)
Mode(UHoEvtTPUeInt)
106.
filterCoeff(UHoEvtTPUeInt)
Filter Coefficient(UHoEvtTPUeInt)
107.
measEvtNum(UHoEvtTPUeI
nt)
Measurement(UHoEvtTPUeInt)
105.
108.
meaEvtId(UHoEvtTPUeInt)
232
109.
trigTime(UHoEvtTPUeInt)
110.
GResPara14
111.
GResPara6
112.
CResPara6
113.
GResPara2
114.
GResPara5
115.
DedMeasType
116.
117.
(UNbDedMeas)
EvtAbcdefTime
(UNbDedMeas)
Hysteresis Time
MeasFilterCoeff
(UNbDedMeas)
118.
RptPrd(UNbDedMeas)
Report Period
119.
RptPrdUnit
(UNbDedMeas)
120.
RptType(UNbDedMeas)
Report Characteristics
121.
EvtAbTcpThrd(UNbDedM
eas)
122.
NbDMCfgNo(UNbDedMe
as)
13.2.2
Parameter Configurations
13.2.2.1
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->UTRAN
Parameter configuration
The priority of a neighbouring cell can be set to 0, 1, and 2, of which, 0 represents the
highest priority and 2 represents the lowest priority. The priority of the neighbouring is set
by the configuration personnel according to the signal strength and the distance of the
neighboring cell.
233
13.2.2.2
OMC path
GUI:
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
This parameter indicates the maximum target signal-to-interference ratio (SIR) of the
uplink.
When the uplink SIR is already in the maximum threshold, if certain error packets are still
detected, the power control will become invalid because the SIR cannot be further
adjusted upwards. If the UL BLER switch for handover has been opened, the RNC will
initiate the compressed mode and the inter-frequency measurement.
13.2.2.3
OMC path
Parameter configuration
This parameter indicates the handover switch based on uplink block error rate (BLER).
When the switch is on, if the uplink BLER arrives at the threshold, RNC will initiate
compressed mode and the inter-frequency measurement.
13.2.2.4
OMC path
Parameter configuration
234
This parameter indicates the handover switch based on uplink transmit power. When the
switch is on, if the uplink transmit power arrives at the threshold, RNC will initiate the
compressed mode and the inter-frequency measurement.
13.2.2.5
OMC path
Parameter configuration
This parameter indicates the handover switch based on downlink transmit power. When
the switch is on, if the downlink transmit power arrives at the threshold, RNC will initiate
the compressed mode and the inter-frequency measurement.
13.2.2.6
HCS_PRIO(UUtranCellFDD)
OMC path
Parameter configuration
This parameter indicates the HCS priority level of the UTRAN cell. 7 represents the
highest priority and 0 represents the lowest priority. A cell with a higher priority often
provides a smaller coverage and a cell with a lower priority offers a larger coverage.
13.2.2.7
HCS_PRIO(UExternalUtranCellFDD)
OMC path
Parameter configuration
235
This parameter indicates the HCS priority level of the neighbouring cell. 7 represents the
highest priority and 0 represents the lowest priority. A cell with a higher priority often
provides a smaller coverage and a cell with a lower priority often offers a larger coverage.
13.2.2.8
OMC path
Parameter configuration
This parameter indicates the event that is used to trigger the inter-frequency handover.
The default value of the parameter is 2A, that is, the handover can be triggered when the
conditions for best carrier frequency change are satisfied.
13.2.2.9
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the filtering factor that the UE performs the L3 filtering on the
measurement results of the inter-frequency measurement. The smaller the value of the
filtering factor is, the larger effect the current measurement result will have on the
measurement result reported to RNC (periodical report) or the judgment (event report).
13.2.2.10
Filter Coefficient(UInterEcNoEvMeasforG)
OMC path
236
GUI:
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the filtering factor that the UE performs the L3 filtering on the
measurement results of the inter-frequency measurement. The smaller the value of the
filtering factor is, the larger effect the current measurement result will have on the
measurement result reported to RNC (periodical report) or the judgment (event report).
13.2.2.11
Filter Coefficient(UInterEcNoEvMeasforU)
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the filtering factor that the UE performs the L3 filtering on the
measurement results of the inter-frequency measurement. The smaller the value of the
filtering factor is, the larger effect the current measurement result will have on the
measurement result reported to RNC (periodical report) or the judgment (event report).
13.2.2.12
Filter Coefficient(UInterEcNoPrdMeas)
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
237
Parameter configuration
This parameter indicates the filtering factor that the UE performs the L3 filtering on the
measurement results of the inter-frequency measurement. The smaller the value of the
filtering factor is, the larger effect the current measurement result will have on the
measurement result reported to RNC (periodical report) or the judgment (event report).
13.2.2.13
Filter Coefficient(UInterRscpEvMeasforE)
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the filtering factor that the UE performs the L3 filtering on the
measurement results of the inter-frequency measurement. The smaller the value of the
filtering factor is, the larger effect the current measurement result will have on the
measurement result reported to RNC (periodical report) or the judgment (event report).
13.2.2.14
Filter Coefficient(UInterRscpEvMeasforG)
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the filtering factor that the UE performs the L3 filtering on the
measurement results of the inter-frequency measurement. The smaller the value of the
filtering factor is, the larger effect the current measurement result will have on the
238
measurement result reported to RNC (periodical report) or the judgment (event report).
13.2.2.15
Filter Coefficient(UInterRscpEvMeasforU)
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the filtering factor that the UE performs the L3 filtering on the
measurement results of the inter-frequency measurement. The smaller the value of the
filtering factor is, the larger effect the current measurement result will have on the
measurement result reported to RNC (periodical report) or the judgment (event report).
13.2.2.16
Filter Coefficient(UInterRscpPrdMeas)
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the filtering factor that the UE performs the L3 filtering on the
measurement results of the inter-frequency measurement. The smaller the value of the
filtering factor is, the larger effect the current measurement result will have on the
measurement result reported to RNC (periodical report) or the judgment (event report).
239
13.2.2.17
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the absolute threshold that should be configured for event
2b/2d/2f (used when judging the quality of the currently used carrier frequency).
In the case of event 2B, the less the threshold configured, the more difficult the event 2B
been triggered.
In the case of event 2D, the less the threshold configured, the more difficult the event 2D
been triggered.
In the case of event 2F, the less the threshold configured, the easier the event 2B is
triggered.
13.2.2.18
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the absolute threshold that should be configured for event
2b/2d/2f (used when judging the quality of the currently used carrier frequency).
240
In the case of event 2B, the less the threshold configured, the more difficult the event 2B
been triggered.
In the case of event 2D, the less the threshold configured, the more difficult the event 2D
been triggered.
In the case of event 2F, the less the threshold configured, the easier the event 2B is
triggered.
13.2.2.19
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the absolute threshold that should be configured for event
2b/2d/2f (used when judging the quality of the currently used carrier frequency).
In the case of event 2B, the less the threshold configured, the more difficult the event 2B
been triggered.
In the case of event 2D, the less the threshold configured, the more difficult the event 2D
been triggered.
In the case of event 2F, the less the threshold configured, the easier the event 2B is
triggered.
13.2.2.20
OMC path
241
GUI:
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the absolute threshold that should be configured for event
2b/2d/2f (used when judging the quality of the currently used carrier frequency).
In the case of event 2B, the less the threshold configured, the more difficult the event 2B
been triggered.
In the case of event 2D, the less the threshold configured, the more difficult the event 2D
been triggered.
In the case of event 2F, the less the threshold configured, the easier the event 2B is
triggered.
13.2.2.21
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the absolute threshold that should be configured for event
2b/2d/2f (used when judging the quality of the currently used carrier frequency).
In the case of event 2B, the less the threshold configured, the more difficult the event 2B
been triggered.
242
In the case of event 2D, the less the threshold configured, the more difficult the event 2D
been triggered.
In the case of event 2F, the less the threshold configured, the easier the event 2B is
triggered.
13.2.2.22
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the absolute threshold that should be configured for event
2b/2d/2f (used when judging the quality of the currently used carrier frequency).
In the case of event 2B, the less the threshold configured, the more difficult the event 2B
been triggered.
In the case of event 2D, the less the threshold configured, the more difficult the event 2D
been triggered.
In the case of event 2F, the less the threshold configured, the easier the event 2B is
triggered.
13.2.2.23
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
243
Parameter configuration
This parameter is used for quality judgment of the currently used carrier frequency. It
indicates the weight of the best RNC in the quality judgment (only for event 2a/2b/2d/2f)
and is related to the measurement quantity and the event type.
13.2.2.24
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter is used for quality judgment of the currently used carrier frequency. It
indicates the weight of the best RNC in the quality judgment (only for event 2a/2b/2d/2f)
and is related to the measurement quantity and the event type.
13.2.2.25
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter is used for quality judgment of the currently used carrier frequency. It
244
indicates the weight of the best RNC in the quality judgment (only for event 2a/2b/2d/2f)
and is related to the measurement quantity and the event type.
13.2.2.26
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter is used for quality judgment of the currently used carrier frequency. It
indicates the weight of the best RNC in the quality judgment (only for event 2a/2b/2d/2f)
and is related to the measurement quantity and the event type.
13.2.2.27
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter is used for quality judgment of the currently used carrier frequency. It
indicates the weight of the best RNC in the quality judgment (only for event 2a/2b/2d/2f)
and is related to the measurement quantity and the event type.
245
13.2.2.28
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter is used for quality judgment of the currently used carrier frequency. It
indicates the weight of the best RNC in the quality judgment (only for event 2a/2b/2d/2f)
and is related to the measurement quantity and the event type.
13.2.2.29
Hysteresis (UInterEcNoEvMeasforE)
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the hysteresis used when judging whether to trigger the event.
This parameter avoids the trigger status change due to very small change. Different
events are configured separately and the events can be configured with different values.
If a small hysteresis is configured, the corresponding event will be reported in a higher
probability; and vice versa.
13.2.2.30
Hysteresis(UInterEcNoEvMeasforG)
OMC path
246
GUI:
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the hysteresis used when judging whether to trigger the event.
This parameter avoids the trigger status change due to very small change. Different
events are configured separately and the events can be configured with different values.
If a small hysteresis is configured, the corresponding event will be reported in a higher
probability; and vice versa.
13.2.2.31
Hysteresis(UInterEcNoEvMeasforU)
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the hysteresis used when judging whether to trigger the event.
This parameter avoids the trigger status change due to very small change. Different
events are configured separately and the events can be configured with different values.
If a small hysteresis is configured, the corresponding event will be reported in a higher
probability; and vice versa.
13.2.2.32
Hysteresis(UInterRscpEvMeasforE)
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
247
Parameter configuration
This parameter indicates the hysteresis used when judging whether to trigger the event.
This parameter avoids the trigger status change due to very small change. Different
events are configured separately and the events can be configured with different values.
If a small hysteresis is configured, the corresponding event will be reported in a higher
probability; and vice versa.
13.2.2.33
Hysteresis(UInterRscpEvMeasforG)
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the hysteresis used when judging whether to trigger the event.
This parameter avoids the trigger status change due to very small change. Different
events are configured separately and the events can be configured with different values.
If a small hysteresis is configured, the corresponding event will be reported in a higher
probability; and vice versa.
13.2.2.34
Hysteresis(UInterRscpEvMeasforU)
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
248
Parameter configuration
This parameter indicates the hysteresis used when judging whether to trigger the event.
This parameter avoids the trigger status change due to very small change. Different
events are configured separately and the events can be configured with different values.
If a small hysteresis is configured, the corresponding event will be reported in a higher
probability; and vice versa.
13.2.2.35
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the time difference between the time that the event generation
is detected and the time that the event is reported. The event is triggered and the
measurement report is reported only when the event generation is detected and still
meets the requirements of event triggering after Time to trigger.
The larger the value is, the stricter the judgment is for the event to be triggered. The
parameter should be set according to the actual requirements.
13.2.2.36
Time to Trigger(UInterEcNoEvMeasforG)
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
249
This parameter indicates the time difference between the time that the event generation
is detected and the time that the event is reported. The event is triggered and the
measurement report is reported only when the event generation is detected and still
meets the requirements of event triggering after Time to trigger.
The larger the value is, the stricter the judgment is for the event to be triggered. The
parameter should be set according to the actual requirements.
13.2.2.37
Time to Trigger(UInterEcNoEvMeasforU)
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the time difference between the time that the event generation
is detected and the time that the event is reported. The event is triggered and the
measurement report is reported only when the event generation is detected and still
meets the requirements of event triggering after Time to trigger.
The larger the value is, the stricter the judgment is for the event to be triggered. The
parameter should be set according to the actual requirements.
13.2.2.38
Time to Trigger(UInterRscpEvMeasforE)
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
250
This parameter indicates the time difference between the time that the event generation
is detected and the time that the event is reported. The event is triggered and the
measurement report is reported only when the event generation is detected and still
meets the requirements of event triggering after Time to trigger.
The larger the value is, the stricter the judgment is for the event to be triggered. The
parameter should be set according to the actual requirements.
13.2.2.39
Time to Trigger(UInterRscpEvMeasforG)
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the time difference between the time that the event generation
is detected and the time that the event is reported. The event is triggered and the
measurement report is reported only when the event generation is detected and still
meets the requirements of event triggering after Time to trigger.
The larger the value is, the stricter the judgment is for the event to be triggered. The
parameter should be set according to the actual requirements.
13.2.2.40
Time to Trigger(UInterRscpEvMeasforU)
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
251
This parameter indicates the time difference between the time that the event generation
is detected and the time that the event is reported. The event is triggered and the
measurement report is reported only when the event generation is detected and still
meets the requirements of event triggering after Time to trigger.
The larger the value is, the stricter the judgment is for the event to be triggered. The
parameter should be set according to the actual requirements.
13.2.2.41
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the absolute threshold that should be configured for event
2b/2c/2e (used when judging the quality of the non-used frequency).
In the case of event 2b, the less the threshold configured, the more difficult the event 2B
been triggered.
In the case of event 2c, the larger the threshold configured, the more difficult the event 2c
been triggered.
In the case of event 2E, the larger the threshold configured, the easier the event 2E been
triggered.
13.2.2.42
OMC path
252
GUI:
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the absolute threshold that should be configured for event
2b/2c/2e (used when judging the quality of the non-used frequency).
In the case of event 2b, the less the threshold configured, the more difficult the event 2B
been triggered.
In the case of event 2c, the larger the threshold configured, the more difficult the event 2c
been triggered.
In the case of event 2E, the larger the threshold configured, the easier the event 2E been
triggered.
13.2.2.43
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter is used for quality judgment of the currently non-used frequency. It
indicates the weight of the best RNC in the quality judgment (only for event 2a/2b/2c/2e)
and is related to the measurement quantity and the event type.
253
13.2.2.44
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter is used for quality judgment of the currently non-used frequency. It
indicates the weight of the best RNC in the quality judgment (only for event 2a/2b/2c/2e)
and is related to the measurement quantity and the event type.
13.2.2.45
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the times of the periodical reports to be reported. In the case of
the UE side, the value is used for the determination of whether to report the
measurement report in reporting the periodical report. If the UE detects that the times of
event reporting exceeds the value of Amount of reporting, the UE stops reporting the
measurement results.
13.2.2.46
OMC path
254
GUI:
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the times of the periodical reports to be reported. In the case of
the UE side, the value is used for the determination of whether to report the
measurement report in reporting the periodical report. If the UE detects that the times of
event reporting exceeds the value of Amount of reporting, the UE stops reporting the
measurement results.
13.2.2.47
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the interval of periodical reporting specified in the periodical
reporting criteria. In the case of the periodical report, the UE reports the inter-frequency
measurement results in the period indicated by the parameter.
13.2.2.48
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
255
Parameter configuration
This parameter indicates the interval of periodical reporting specified in the periodical
reporting criteria. In the case of the periodical report, the UE reports the inter-frequency
measurement results in the period indicated by the parameter.
13.2.2.49
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
13.2.2.50
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
13.2.2.51
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Inter-RAT
Configuration->Service
Measurement
256
Parameter configuration
This parameter indicates the interval of periodical reporting specified in the periodical
reporting criteria.
13.2.2.52
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Inter-RAT
Configuration->Service
Measurement
Parameter configuration
This parameter indicates the interval of periodical reporting specified in the periodical
reporting criteria.
13.2.2.53
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->UTRAN
Parameter configuration
This parameter describes the neighboring relationship of the current cell and the
neighboring cell. The relationship between the neighbouring cell and the current cell may
be Neighbor, Overlap, Covers, or Contained in.
13.2.2.54
OMC path
257
GUI:
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
13.2.2.55
Profile Id(UInterMeasProfile)
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
13.2.2.56
Profile Id(UUeIntMeasProfile)
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
258
13.2.2.57
OMC path
Parameter configuration
13.2.2.58
OMC path
Parameter configuration
13.2.2.59
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
259
13.2.2.60
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
13.2.2.61
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
260
Parameter configuration
13.2.2.62
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
261
13.2.2.63
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
13.2.2.64
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
262
Parameter configuration
13.2.2.65
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
263
13.2.2.66
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
13.2.2.67
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
264
This parameter indicates the identity of the event triggered by the inter-frequency
measurement (2a~2f).
13.2.2.68
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the identity of the event triggered by the inter-frequency
measurement (2a~2f).
13.2.2.69
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the identity of the event triggered by the inter-frequency
measurement (2a~2f).
13.2.2.70
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
265
Parameter configuration
This parameter indicates the identity of the event triggered by the inter-frequency
measurement (2a~2f).
13.2.2.71
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the identity of the event triggered by the inter-frequency
measurement (2a~2f).
13.2.2.72
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the identity of the event triggered by the inter-frequency
measurement (2a~2f).
266
13.2.2.73
OMC path
GUI:
Managed
Element
->UMTS
Configuration->Measurement
Logical
Function
Configuration->UE
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
All the services are classified into eight categories according to the real-time attribute of
services, channel type, and service quantity. This parameter indicates the service and
bearer type. The handover parameters can be configured flexibly for different scenarios
and the parameters may have different handover triggering thresholds and hysteresis.
The value 0xff (Not Related to Service Type) is exclusively used in the measurement of
the detected set.
Table 13-1
Defa
Defa
Defa
Defa
Defa
Defa
Defa
Defa
Def
ult
ult
ult
ult
ult
ult
ult
ult
ault
Valu
Valu
Valu
Valu
Valu
Valu
Valu
Valu
Val
e1
e2
e3
e4
e5
e6
e7
e8
ue 9
profileId(UInte
rMeasProfile)
srvCategory
0xff
UInterEcNoPr
dMeas
UInterEcNoEv
MeasforU
UInterRscpPrd
Meas
UInterRscpEv
MeasforU
267
13.2.2.74
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
This parameter indicates the purpose and functions of the set of inter-frequency
measurement configuration parameters.
13.2.2.75
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the number of events that should be configured for the index of
the inter-frequency measurement configuration for a certain purpose.
13.2.2.76
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the number of events that should be configured for the index of
268
13.2.2.77
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the number of events that should be configured for the index of
the inter-frequency measurement configuration for a certain purpose.
13.2.2.78
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the number of events that should be configured for the index of
the inter-frequency measurement configuration for a certain purpose.
13.2.2.79
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
269
Parameter configuration
This parameter indicates the number of events that should be configured for the index of
the inter-frequency measurement configuration for a certain purpose.
13.2.2.80
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->UE
Function
Configuration->Service
Inter-frequency
Measurement
Parameter configuration
This parameter indicates the number of events that should be configured for the index of
the inter-frequency measurement configuration for a certain purpose.
13.2.2.81
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->UTRAN
Parameter configuration
This parameter indicates the UE status applied to the neighboring cell. When the
neighbouring cell is configured by status, the neighbouring cells list used for reselection
in non-dedicated mode and the neighbouring cells list for handover in dedicated mode
are differentiated as follows:
When SIB11/SIB12/SIB11bis is to be sent, the UE selects the cell whose state is only
cell selection/reselection or cell selection/reselection and handover from the
270
13.2.2.82
OMC path
Parameter configuration
This parameter indicates the UTRAN measurement quantity (Ec/No or RSCP) for the
inter-frequency and inter-RAT measurements. The measurement quantity RSCP is
recommended.
13.2.2.83
OMC path
Parameter configuration
13.2.2.84
OMC path
271
Parameter configuration
13.2.2.85
OMC path
Parameter configuration
13.2.2.86
OMC path
Parameter configuration
13.2.2.87
OMC path
Parameter configuration
This parameter indicates whether R99 NRT inter-frequency handover allowed or not.
272
13.2.2.88
OMC path
Parameter configuration
13.2.2.89
OMC path
Parameter configuration
13.2.2.90
OMCR Interface
Parameter configuration
This parameter indicates whether inter-frequency and inter-rat compressed mode will be
configured to the UE simultaneously or not, when inter-frequency cells and inter-rat
neighboring cells exist.
0: Configure Inter-Frequency and Inter-Rat Compressed Mode Simultaneously
1: Configure Inter-Frequency and Inter-Rat Compressed Mode Individually
273
13.2.2.91
GUI:
OMCR Interface
Managed
Element
->UMTS
Logical
Function
Configuration->UTRAN
Parameter configuration
This parameter indicates how to perform neighbor measurement if a cell has both
inter-frequency and inter-RAT cells as its neighbors.
0: Turn off Inter-frequency and Inter-RAT Handover
1: Only Inter Frequency
2: Only Inter Rat
3: Inter Frequency is Prior to Inter Rat
13.2.2.92
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
13.2.2.93
The Time Threshold that the RNC May Resend the MEASUREMENT
CONTROL RELEASE
OMC path
Parameter configuration
274
This parameter indicates the time threshold that the RNC may resend the
MEASUREMENT CONTROL RELEASE.
When RNC send MEASUREMENT CONGROL RELEASE message for a measurement
ID, the time stamp will be recorded. If RNC receive the measurement report for the ID, it
will be compared between current time and recorded time. If difference between current
time and recorded time exceed the threshold configured, the MEASUREMENT
CONTROL RELEASE will be resent, otherwise ignore this measurement report.
13.2.2.94
OMC path
Parameter configuration
13.2.2.95
OMC path
GUI:
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
13.2.2.96
OMC path
Parameter configuration
275
not
support,
use
dedicated
compressed
mode;
RncFeatSwitchBit9=1: support.
13.2.2.97
OMC path
Parameter configuration
This parameter indicates whether to process the handover judgement based on moving
speed or not.
HcsSupportInd=2/3: support HCS in handover; HcsSupportInd=0/1: not support HCS in
handover.
13.2.2.98
OMC path
Parameter configuration
This parameter indicates whether to activate compressed mode for CS service when
radio link via IUR exists.
13.2.2.99
OMC path
276
GUI:
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
The parameter indicates handover and cell reselection scenarios. For each scenario, the
corresponding parameters can be set as different values.
OMC path
Parameter configuration
The parameter indicates the RNC switch for handover based on uplink BLER. When the
switch is "Off", the function is turned off; when the switch is "On", judge the cell switch
UlBlerHoSwch to decide whether the function is turned on.
OMC path
Parameter configuration
The parameter indicates the RNC switch for handover based on transmit power. When
the switch is "Off", the function is turned off; when the switch is "On", judge the cell switch
UlPwrHoSwch/DlPwrHoSwch to decide whether the function is turned on.
OMC path
277
Parameter configuration
OMC path
Parameter configuration
The parameter indicates the inter-RAT handover method is periodical method or event
method.
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->UTRAN
Parameter configuration
The parameter indicates interval between reception of periodical reports and triggering of
the inter-frequency or inter-rat handover. Only the neighboring cell in which the signal
quality is above a certain threshold in all periodic reports during a time equal to this
parameter can be selected as the target cell for the inter-frequency or inter-rat handover.
If this parameter is set to a greater value, the probability of incorrect decision becomes
low; however, the handover algorithm becomes slow in responding to signal change.
278
13.2.2.105
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
The parameter indicates the RLC mode of the UE internal measurement report.
13.2.2.106
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
The parameter indicates the filtering factor that the UE performs the L3 filtering on the
measurement results of the internal measurement.
13.2.2.107
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
279
13.2.2.108
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
13.2.2.109
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
The parameter indicates the period of time during which the event condition has to be
satisfied before sending a measurement report.
OMC path
Parameter configuration
The parameter is the switch of associated compressed mode when the UE leaves
common state. 0: closed, do not configure accompanying compressed mode; 1: open,
configure accompanying compressed mode.
280
OMC path
Parameter configuration
The parameter is the penlty timer. When inter frequency handover is failed, the timer is
initialization, and RNC will not handle inter-frequency measurement report until the timer
expires.
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->UTRAN
Parameter configuration
This parameter indicates whether RNC judge the minimu quality threshold of target cells
in inter-frequency handover. If the switch is On, when the signal quality of target cells'
quality is lower than GresPara2 or GresPara5, RNC will not perform the inter frequency
handover.
OMC path
Parameter configuration
281
This parameter indicates the CPICH EcNo minimum threshold for inter frequency
handover. If reported CPICH EcNo is less than GresPara2 or CPICH RSCP is less than
GresPara5, inter frequency handover will not be triggered.
OMC path
Parameter configuration
This parameter indicates the CPICH RSCP minimum threshold for inter frequency
handover. If reported CPICH EcNo is less than GresPara2 or CPICH RSCP is less than
GresPara5, inter frequency handover will not be triggered.
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
OMC path
282
GUI:
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
For event A/B, this parameter is measurement hysteresis time and the measurement
hysteresis time provides the duration during which a reporting criterion has to be fulfilled
for the Measurement Reporting procedure to be triggered.
Configuration Rule: according to the measurement type and event of the dedicated
measurement.
The larger this parameter is, the more difficult to trigger the measurement event.
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
OMC path
283
GUI:
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
This parameter indicates the time unit of measurement report transmitted by Node B.
Configuration Rule: According to the measurement period which is determined according
to the contribution to the system load and the timeliness of the measurement report.
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
284
Parameter configuration
This parameter indicates the report characteristics of measurement results, which can be
on demand, periodic or by triggering all kinds of events.
Configuration Rule: according to the measurement type and event of the dedicated
measurement.
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
The parameter indicates the power offset of the DPCH maximum DL power, which
defines which threshold that shall trigger event A, B for transmitted carrier power
measurement.
This parameter is a ternary array, which is fixed to the first element evtAbTcpThrd[0] for
handover control.
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
285
13.3
13.3.1
Parameter List
No.
1.
2.
Trelocoverall
3.
CsReDelayTimer
4.
PsReDelayTimer
5.
6.
7.
8.
9.
RncFeatSwitchBit10
RncFeatSwitchBit11
RncFeatSwitchBit0
RncFeatSwitchBit19
12.
Support/Support
not
Involved
UE
not
Involved
Support/Support
dscrInCmnToDedSwch
Switch
of
DSCR
in
Transferring
Unsuccessfully from Common Status to
CELL_DCH status
RNCFEATSWITCHBit24
RncFeatSwitchBit25
13.3.2
Parameter Configurations
13.3.2.1
UE
GresPara48
10.
11.
Not
for
OMC path
286
Parameter configuration
This parameter specifies the maximum time for Relocation Preparation procedure in the
source RNC after the SRNC successfully sends the RELOCATION REQUIRED
message to the CN. If the SRNC fails to receive the RELOCATION COMMAND message
within the time specified by the parameter, the timer is judged as expiry and the
relocation is canceled.
13.3.2.2
OMC path
Parameter configuration
This parameter specifies the maximum time for the initiation of the Iu release by the CN
after the SRNC receives the RELOCATION COMMAND message. If the CN fails to
initiate the Iu release within the time specified by the parameter, the timer is judged as
expiry and the SRNC initiates the Iu release instead.
13.3.2.3
OMC path
Parameter configuration
13.3.2.4
OMC path
287
Parameter configuration
13.3.2.5
OMC path
Parameter configuration
This parameter indicates whether to support the relocation which the UE is not involved
for CS service or not.
13.3.2.6
OMC path
Parameter configuration
This parameter indicates whether to support the relocation which UE is not involved for
PS service or not.
13.3.2.7
OMC path
288
Parameter configuration
This parameter indicates whether hard handover can accompany with the relocation for
CS service or not.
13.3.2.8
OMC path
Parameter configuration
This parameter indicates whether hard handover can accompany with the relocation for
PS service or not.
13.3.2.9
OMC path
Parameter configuration
This parameter bit11 indicates what moment should send Relocation Detect
message to CN in soft handover relocation procedure.
Bit11=0: when the DRNC receives a UTRAN Mobility Information Confirm message
from UE, then send Relocation Detect message to CN;
Bit11=1: When the DRNC receives a Relocation Commit message from SRNC, then
send Relocation Detect message to CN.
289
13.3.2.10
OMC path
Parameter configuration
This parameter indicates whether RNC should execute DSCR procedure when
transferring unsuccessfully from common connected RRC status to dedicated connected
RRC status with the UE returning configuration related failure cause.
13.3.2.11
OMC path
Parameter configuration
This parameter indicates whether RNC supports HSPA fallback procedure for
inter-frequency handover via IUR. If compatibility problem between vendors exists, this
parameter should be set "1".
13.3.2.12
OMC path
Parameter configuration
This parameter indicates whether the RNC forwarding date when Relocation.
290
13.4
13.4.1
Parameter List
No.
Field Name
1.
MeasPrio
2.
RatHoTactic
3.
UlBlerHoSwch
4.
DlPwrHoSwch
5.
UlPwrHoSwch
6.
Thresh(URatEcNoEvMea
sforG)
3A
Thresh(URatRscpEvMeas
forG)
3A
7.
8.
W(URatEcNoEvMeasforG
)
9.
W(URatRscpEvMeasforG
)
10.
11.
12.
MeasforG)
3A/3B/3C
ThreshSys(URatRscpEvM
easforG)
3A/3B/3C
hysteresis(URatEcNoEvM
hysteresis(URatRscpEvM
easforG)
14.
TrigTime(URatEcNoEvMe
asforG)
15.
TrigTime(URatRscpEvMe
asforG)
16.
profileId(URatMeasProfile
)
17.
profileId(UUeIntMeasProfi
le)
18.
ThreshSys(URatEcNoEv
easforG)
13.
refURatMeasProfile
Hysteresis
Hysteresis
Time to Trigger
Time to Trigger
Profile Id
Profile Id
Used Inter-RAT Measurement Profile
291
19.
20.
21.
refUUeIntMeasProfile
srvCategory
InterRatCfgNo(URatEcNo
EvMeasforG)
22.
InterRatCfgNo(URatEcNo
PrdMeas)
23.
InterRatCfgNo(URatRscp
EvMeasforG)
24.
InterRatCfgNo(URatRscp
PrdMeas)
25.
InterRatCfgNote
26.
FilterCoeff(URatEcNoEvM
easforG)
27.
FilterCoeff(URatEcNoPrd
Meas)
28.
FilterCoeff(URatRscpEvM
easforG)
29.
FilterCoeff(URatRscpPrd
Meas)
30.
GsmFilterCoeff(URatEcN
oEvMeasforG)
31.
GsmFilterCoeff(URatEcN
oPrdMeas)
32.
GsmFilterCoeff(URatRscp
EvMeasforG)
33.
GsmFilterCoeff(URatRscp
PrdMeas)
34.
GeranCellInd
35.
EventNum(URatEcNoEv
MeasforG)
36.
EventNum(URatRscpEvM
easforG)
292
37.
EventId
[MAX_RAT_MEAS_EVEN
T]
(URatEcNoEvMeasforG)
38.
EventId
[MAX_RAT_MEAS_EVEN
T]
(URatRscpEvMeasforG)
39.
CellIndivOffset
(UExternalGsmCell)
40.
41.
42.
43.
GsmStateMode
GsmShareCover
NonIntraMeasQuan
HcsPrio
(UExternalGsmCell)
44.
psInterSysHoSuppInd
45.
DtmSuppInd
46.
47.
BSCPSFeatSwitch
BSCDTMFeatSwitch
48.
LdBsdIntSysHOInd
49.
CellLdInfoVldTim
50.
GsmUlRtLdThrd
51.
GsmDlRtLdThrd
52.
GsmUlLdThrd
53.
GsmDlLdThrd
54.
NaccSuppInd
55.
HoToGsmPenTimer
56.
srvBasedHoInd
57.
ServHoSwch
58.
srvHoComStra
59.
amrRatHoSw
293
60.
r99RtRatHoSw
61.
r99NrtRatHoSw
62.
hsdpaRatHoSw
63.
hsupaRatHoSw
64.
T4StpIfMeaActRat
65.
srvHoIndAmr
66.
srvHoIndCs64
67.
srvHoIndPsNRT
68.
srvHoIndPsRT
69.
amrSrvHoStra
70.
cs64SrvHoStra
71.
72.
73.
74.
75.
psRtSrvHoStra
psNrtSrvHoStra
Tdatafwd
TWaitContextReq
TWaitDataFwd
76.
TWaitRelCmd
77.
UeIntMCfgNo(UHoEvtTP
UeInt)
78.
TResndMeaCtrlRel
79.
HOCELSELSCENE
80.
IurgFeatSwitch
81.
82.
BoardPwrOffHoTmr
intialHoCelSelScene(URa
tMeasProfile)
83.
txPowerThres(UHoEvtTP
UeInt)
294
84.
RncUlBlerHoSwch
85.
RncTxPwrHoSwch
86.
measRptTrMod(UHoEvtTPU
eInt)
Mode(UHoEvtTPUeInt)
87.
filterCoeff(UHoEvtTPUeInt)
Filter Coefficient(UHoEvtTPUeInt)
88.
measEvtNum(UHoEvtTPUeI
nt)
Measurement(UHoEvtTPUeInt)
89.
meaEvtId(UHoEvtTPUeInt)
90.
trigTime(UHoEvtTPUeInt)
91.
RatCelInfoSwch
92.
rxlevNecellInd
93.
DedMeasType
94.
95.
(UNbDedMeas)
EvtAbcdefTime
(UNbDedMeas)
Hysteresis Time
MeasFilterCoeff
(UNbDedMeas)
96.
RptPrd(UNbDedMeas)
Report Period
97.
RptPrdUnit
(UNbDedMeas)
98.
RptType(UNbDedMeas)
Report Characteristics
99.
EvtAbTcpThrd(UNbDedM
eas)
100.
NbDMCfgNo(UNbDedMe
as)
13.4.2
Parameter Configurations
13.4.2.1
OMC path
295
GUI:
Managed
Element
->UMTS
Logical
Function
Configuration->UTRAN
Parameter configuration
This parameter indicates the measurement priority of the neighboring cell. 0 presents the
highest priority and 2 presents the lowest priority. This parameter should be configured
by the network planning engineer according to the actual conditions of the current
network, including the quality and geographic position of the inter-RAT neighbouring cell.
13.4.2.2
OMC path
Parameter configuration
This parameter indicates the measurement event type (3A or 3C) that is used to trigger
the inter-RAT handover.
Event 3C can be triggered when the quality of the inter-RAT carrier frequency signal is
higher than a certain value. In contrast, the trigger of event 3A requires an additional
condition, that is, the quality of the carrier frequency signal of the current RAT must be
less than a certain value. Hence, the inter-RAT handover can be triggered more easily
when the parameter is set to 3C Event Trigger.
13.4.2.3
OMC path
Parameter configuration
This parameter indicates the handover switch based on uplink BLER. When the switch is
on, the RNC will initiate compressed mode and inter-RAT measurement if the uplink
BLER quality arrives at the threshold.
296
13.4.2.4
OMC path
Parameter configuration
This parameter indicates the handover switch based on downlink transmit power. When
the switch is on, the RNC will initiate compressed mode and inter-RAT measurement if
the downlink transmit power arrives at the threshold.
13.4.2.5
OMC path
Parameter configuration
This parameter indicates the handover switch based on uplink transmit power. When the
switch is on, the RNC will initiate compressed mode and inter-RAT measurement if the
uplink transmit power arrives at the threshold.
13.4.2.6
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
297
This parameter indicates the absolute threshold of the UTRAN cell quality that is used by
the UE to judge event 3a. The range and unit of the parameter are related to the
measurement quantity of the cells of the UTRAN system.
The smaller the value configured, the more difficult the event 3a been reported.
13.4.2.7
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the absolute threshold of the UTRAN cell quality that is used by
the UE to judge event 3a. The range and unit of the parameter are related to the
measurement quantity of the cells of the UTRAN system.
The smaller the value configured, the more difficult the event 3a been reported.
13.4.2.8
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the weight of the best cell in the quality judgment of event 3a. It
is used in judging the quality of the UTRAN system in inter-RAT measurement.
298
See the description of the formula in Section 7.1 for the effect of this parameter on the
inter-RAT measurement.
13.4.2.9
GUI:
OMC path
Managed
Element
->UMTS
Configuration->Measurement
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the weight of the best cell in the quality judgment of event 3a. It
is used in judging the quality of the UTRAN system in inter-RAT measurement.
See the description of the formula in Section 7.1 for the effect of this parameter on the
inter-RAT measurement.
13.4.2.10
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the absolute threshold used when judging the quality of other
RAT configured for event 3a/3b/3c. The value range and unit of this parameter are
related to the measurement quantity of the cells of other systems. At present, the
measurement quantity can only be GSM Carrier RSSI of the GSM system, which
299
corresponds to the CPICH RSCP of the UMTS system. Hence, the value range and unit
of this parameter correspond to CPICH RSCP.
The larger the value is configured, the more difficult it is to report event 3a/3b/3c.
13.4.2.11
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the absolute threshold used when judging the quality of other
RAT configured for event 3a/3b/3c. The value range and unit of this parameter are
related to the measurement quantity of the cells of other systems. At present, the
measurement quantity can only be GSM Carrier RSSI of the GSM system, which
corresponds to the CPICH RSCP of the UMTS system. Hence, the value range and unit
of this parameter correspond to CPICH RSCP.
The larger the value is configured, the more difficult it is to report event 3a/3b/3c.
13.4.2.12
Hysteresis(URatEcNoEvMeasforG)
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
300
This parameter indicates the hysteresis used when judging whether the event meets the
conditions of been triggered.
This parameter is related to the measurement quantity and the event type. If a small
hysteresis is configured, the corresponding event will be reported in a high probability;
and vice versa.
13.4.2.13
Hysteresis(URatRscpEvMeasforG)
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the hysteresis used when judging whether the event meets the
conditions of been triggered.
This parameter is related to the measurement quantity and the event type. If a small
hysteresis is configured, the corresponding event will be reported in a high probability;
and vice versa.
13.4.2.14
Time to Trigger(URatEcNoEvMeasforG)
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the time difference between the time that the event generation
is detected and the time that the event is reported. The event can be triggered and
301
reported only when the event is detected and still meets all requirements of event
triggering after Time to trigger.
The larger the value is, the stricter the judgment is for the event to be triggered. The
parameter should be configured according to the actual requirements.
13.4.2.15
Time to Trigger(URatRscpEvMeasforG)
GUI:
OMC path
Managed
Element
->UMTS
Configuration->Measurement
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the time difference between the time that the event generation
is detected and the time that the event is reported. The event can be triggered and
reported only when the event is detected and still meets all requirements of event
triggering after Time to trigger.
The larger the value is, the stricter the judgment is for the event to be triggered. The
parameter should be configured according to the actual requirements.
13.4.2.16
Profile Id(URatMeasProfile)
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
302
13.4.2.17
Profile Id(UUeIntMeasProfile)
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
13.4.2.18
OMC path
Parameter configuration
13.4.2.19
OMC path
Parameter configuration
13.4.2.20
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
303
Parameter configuration
All the services are classified into eight categories according to the real-time attribute of
the services, channel type, and service quantity. This parameter indicates the service
and bearer type. The handover parameters can be configured flexibly for different
scenarios and the parameters may have different handover triggering thresholds and
hysteresis.
The value 0xff (Not Related to Service Type) is exclusively used in the measurement of
the detected set.
Table 13-2
Default Value
Field Name
13.4.2.21
Defa
Defa
Defa
Defa
Defa
Defa
Defa
Defa
Def
ult
ult
ult
ult
ult
ult
ult
ult
ault
Valu
Valu
Valu
Valu
Valu
Valu
Valu
Valu
Valu
e1
e2
e3
e4
e5
e6
e7
e8
e9
profileId(URat
MeasProfile)
srvCategory
0xff
URatEcNoPrd
Meas
URatEcNoEv
MeasforG
URatRscpPrd
Meas
URatRscpEv
MeasforG
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Inter-RAT
Configuration->Service
Measurement
304
Parameter configuration
is,
the
parameter
Inter-RAT
Measurement
Profile
Identity
(namely
13.4.2.22
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
is,
the
parameter
Inter-RAT
Measurement
Profile
Identity
(namely
305
13.4.2.23
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
is,
the
parameter
Inter-RAT
Measurement
Profile
Identity
(namely
13.4.2.24
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Inter-RAT
Configuration->Service
Measurement
306
Parameter configuration
is,
the
parameter
Inter-RAT
Measurement
Profile
Identity
(namely
13.4.2.25
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
This parameter indicates the purpose and functions of the set of inter-RAT measurement
configuration parameters.
13.4.2.26
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
307
This parameter indicates the filtering factor that the UE performs the L3 filtering on the
UTRAN measurement results of the inter-RAT measurement. The smaller the filtering
factor, the larger the effect of the measurement on the final result.
13.4.2.27
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the filtering factor that the UE performs the L3 filtering on the
UTRAN measurement results of the inter-RAT measurement. The smaller the filtering
factor, the larger the effect of the measurement on the final result.
13.4.2.28
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the filtering factor that the UE performs the L3 filtering on the
UTRAN measurement results of the inter-RAT measurement. The smaller the filtering
factor, the larger the effect of the measurement on the final result.
13.4.2.29
OMC path
308
GUI:
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the filtering factor that the UE performs the L3 filtering on the
UTRAN measurement results of the inter-RAT measurement. The smaller the filtering
factor, the larger the effect of the measurement on the final result.
13.4.2.30
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the filtering factor that the UE performs the L3 filtering on the
GSM measurement results of the inter-RAT measurement. The smaller the filtering factor,
the larger the effect of the measurement on the final result.
13.4.2.31
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Inter-RAT
Configuration->Service
Measurement
Parameter configuration
This parameter indicates the filtering factor that the UE performs the L3 filtering on the
309
GSM measurement results of the inter-RAT measurement. The smaller the filtering factor,
the larger the effect of the measurement on the final result.
13.4.2.32
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the filtering factor that the UE performs the L3 filtering on the
GSM measurement results of the inter-RAT measurement. The smaller the filtering factor,
the larger the effect of the measurement on the final result.
13.4.2.33
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Inter-RAT
Configuration->Service
Measurement
Parameter configuration
This parameter indicates the filtering factor that the UE performs the L3 filtering on the
GSM measurement results of the inter-RAT measurement. The smaller the filtering factor,
the larger the effect of the measurement on the final result.
13.4.2.34
OMC path
310
Parameter configuration
13.4.2.35
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the number of events that should be configured for the
inter-RAT measurement configuration index for a certain purpose.
13.4.2.36
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the number of events that should be configured for the
inter-RAT measurement configuration index for a certain purpose.
13.4.2.37
OMC path
311
GUI:
Managed
Element
->UMTS
Configuration->Measurement
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the identity of the event triggered by the inter-RAT
measurement (3a~3d).
13.4.2.38
GUI:
OMC path
Managed
Element
->UMTS
Configuration->Measurement
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the identity of the event triggered by the inter-RAT
measurement (3a~3d).
13.4.2.39
OMC path
Parameter configuration
This parameter indicates the individual offset of GSM cells. When the value is positive, a
positive value is added to the measurement result to be judged. If the value is negative, a
negative value is added to the measurement result to be judged. See the introduction to
inter-RAT measurement in section 7.1.1 for the effect of this parameter on the
measurement report.
312
Through the configuration of the individual offset of a single cell, the trigger difficulty of
the cell can be adjusted to meet the actual requirements of network planning, thus
avoiding the need to modify the global handover parameters.
13.4.2.40
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->UTRAN
Parameter configuration
This parameter indicates the UE status applied to the GSM neighboring cell. When the
neighbouring cell is configured by status, the neighbouring cells list used for reselection
in non-dedicated mode and the neighbouring cells list used for handover in dedicated
mode are differentiated as follows:
When SIB11/SIB12/SIB11bis is to be sent, the UE selects the cell whose state is only
cell selection/reselection or cell selection/reselection and handover from the
neighboring cells list and fills in SIB11/SIB12/SIB11bis;
When the measurement control message is to be sent, the UE selects the cell whose
state is only cell handover from the neighboring cells list.
13.4.2.41
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->UTRAN
Parameter configuration
This parameter indicates the neighboring relationship of the current cell and GSM
neighboring cell, including Neighbor, Overlap, Covers, and Contained in.
313
13.4.2.42
OMC path
Parameter configuration
This parameter indicates the UTRAN measurement quantity (Ec/No or RSCP) for
inter-frequency and inter-RAT measurements. The measurement quantity RSCP is
recommended.
13.4.2.43
HCS_PRIO (UExternalGsmCell)
OMC path
Parameter configuration
This parameter indicates the HCS priority level of the GSM cell. 7 represents the highest
priority and 0 represents the lowest priority. A cell with a higher priority often provides a
smaller coverage and a cell with a lower priority often offers a larger coverage
IMSI-Based Handover Parameters
13.4.2.44
OMC path
Parameter configuration
This parameter indicates whether RNC supports PS inter-RAT handover. 0 indicates not
support, 1 indicates support.
314
13.4.2.45
OMC path
Parameter configuration
This parameter indicates whether the RNC supports DTM mode, that is, whether
supports inter-RAT handover both for CS domain services and PS domain services at the
same time. 0 indicates not support, 1 indicates support.
13.4.2.46
GUI:
OMC path
Managed
Element->UMTS
Logical
Function
Configuration->Link
Configuration->Iurg Link
Parameter configuration
13.4.2.47
GUI:
OMC path
Managed
Element->UMTS
Logical
Function
Configuration->Link
Configuration->Iurg Link
Parameter configuration
13.4.2.48
OMC path
315
Parameter configuration
This parameter indicates whether the target cell load information is taken into
consideration during the inter system handover procedure.
13.4.2.49
OMC path
Parameter configuration
This parameter indicates the duration of inter-sys cells load information which is valid to
use before updating.
13.4.2.50
OMC path
Parameter configuration
This parameter indicates the uplink overload threshold for RT service in GSM system.
13.4.2.51
OMC path
Parameter configuration
316
This parameter indicates the downlink overload threshold for RT service in GSM system.
13.4.2.52
OMC path
Parameter configuration
13.4.2.53
OMC path
Parameter configuration
13.4.2.54
OMC path
Parameter configuration
13.4.2.55
OMC path
317
Parameter configuration
When handover from UMTS to GSM is failed, the timer initiates, and RNC will not handle
inter-RAT measurement report until the timer expires.
13.4.2.56
OMC path
Parameter configuration
13.4.2.57
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->UTRAN
Parameter configuration
This parameter indicates whether service handover is allowed or not. When the Service
Handover IE is included in RAB assignment request, if the switch is open, RNC will
perform related process according to the value of Service Handover IE, otherwise RNC
will ignore the Service Handover IE.
13.4.2.58
OMC path
318
Parameter configuration
This parameter indicates the service handover combination strategy in multi-RAB, and
RNC will perform related process according to the highest priority value of IE service
handover.
13.4.2.59
OMC path
Parameter configuration
13.4.2.60
OMC path
Parameter configuration
13.4.2.61
OMC path
Parameter configuration
This parameter indicates whether R99 NRT inter-Rat handover is allowed or not.
13.4.2.62
OMC path
319
Parameter configuration
13.4.2.63
OMC path
Parameter configuration
13.4.2.64
OMCR Interface
Parameter configuration
This parameter indicates the time interval of issuing inter-frequency measurement and
inter-RAT measurement. When RNC issues inter-frequency measurement, the timer is
start. If the quality of non-used frequency is bad during the time length indicated by this
parameter, RNC will issue inter-RAT measurement if there is an inter-RAT neighboring
cell.
The larger the value is, the slower the inter-RAT measurement is initialized, and vice
versa.
13.4.2.65
OMCR Interface
320
Parameter configuration
13.4.2.66
OMCR Interface
Parameter configuration
13.4.2.67
OMCR Interface
Parameter configuration
13.4.2.68
OMCR Interface
321
Parameter configuration
13.4.2.69
OMCR Interface
Parameter configuration
13.4.2.70
OMCR Interface
Parameter configuration
322
13.4.2.71
OMCR Interface
Parameter configuration
13.4.2.72
OMCR Interface
Parameter configuration
This parameter indicates the service handover strategy for PS NRT service.
0:should be performed(should be performed)
1:should not be performed(should not be performed)
2: shall not be performed(shall not be performed)
13.4.2.73
OMC path
Parameter configuration
323
This parameter specifies the maximum time for GTP-PDU forwarding at the source RNC
during relocation of SRNS.
13.4.2.74
OMCR Interface
Parameter configuration
This parameter indicates timer length waiting for SRNS CONTEXT REQUEST.
13.4.2.75
OMCR Interface
Parameter configuration
This parameter indicates timer length waiting for SRNS DATA FORWARD COMMAND.
13.4.2.76
OMCR Interface
Parameter configuration
This parameter indicates timer length that waiting for IU RELEASE COMMAND.
13.4.2.77
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
324
Parameter configuration
13.4.2.78
The Time Threshold that the RNC May Resend the MEASUREMENT
CONTROL RELEASE
OMC path
Parameter configuration
This parameter indicates the time threshold that the RNC may resend the
MEASUREMENT CONTROL RELEASE.
When RNC send MEASUREMENT CONGROL RELEASE message for a measurement
ID, the time stamp will be recorded. If RNC receive the measurement report for the ID, it
will be compared between current time and recorded time. If difference between current
time and recorded time exceed the threshold configured, the MEASUREMENT
CONTROL RELEASE will be resent, otherwise ignore this measurement report.
13.4.2.79
OMC path
Parameter configuration
13.4.2.80
GUI:
OMC path
Managed
Element->UMTS
Logical
Function
Configuration->Link
Configuration->Iurg Link
Parameter configuration
325
This parameter indicates whether adjacent BSC supports Iur-g signaling procedure.
13.4.2.81
OMC path
Parameter configuration
This parameter indicates timer length that waiting for UE handover when boards power
is off.
The value of this parameter is smaller, the time of turn off the power is shorter, and the
user experience is worse; the value of this parameter is larger, the time of turn off the
power is longer, and the user experience is better.
13.4.2.82
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
The parameter indicates handover and cell reselection scenarios. For each scenario, the
corresponding parameters can be set as different values.
13.4.2.83
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
326
13.4.2.84
OMC path
Parameter configuration
The parameter indicates the RNC switch for handover based on uplink BLER. When the
switch is "Off", the function is turned off; when the switch is "On", judge the cell switch
UlBlerHoSwch to decide whether the function is turned on.
13.4.2.85
OMC path
Parameter configuration
The parameter indicates the RNC switch for handover based on transmit power. When
the switch is "Off", the function is turned off; when the switch is "On", judge the cell switch
UlPwrHoSwch/DlPwrHoSwch to decide whether the function is turned on.
13.4.2.86
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
327
The parameter indicates the RLC mode of the UE internal measurement report.
13.4.2.87
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
The parameter indicates the filtering factor that the UE performs the L3 filtering on the
measurement results of the internal measurement.
13.4.2.88
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
13.4.2.89
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
328
13.4.2.90
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
The parameter indicates the period of time during which the event condition has to be
satisfied before sending a measurement report.
13.4.2.91
OMC path
Parameter configuration
The parameter indicates whether to deal with the inter-RAT measurement report when
the value of inter-rat cell info indication in inter-RAT measurement report reported by
the UE is different from that filled in measurement control message. The value is 1, deal
with the report, the value is 0, do not deal with the report.
13.4.2.92
OMC path
Parameter configuration
329
13.4.2.93
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
13.4.2.94
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
For event A/B, this parameter is measurement hysteresis time and the measurement
hysteresis time provides the duration during which a reporting criterion has to be fulfilled
for the Measurement Reporting procedure to be triggered.
Configuration Rule: according to the measurement type and event of the dedicated
measurement.
The larger this parameter is, the more difficult to trigger the measurement event.
13.4.2.95
OMC path
330
GUI:
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
13.4.2.96
Report Period
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
13.4.2.97
OMC path
331
GUI:
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
This parameter indicates the time unit of measurement report transmitted by Node B.
Configuration Rule: According to the measurement period which is determined according
to the contribution to the system load and the timeliness of the measurement report.
13.4.2.98
Report Characteristics
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
This parameter indicates the report characteristics of measurement results, which can be
on demand, periodic or by triggering all kinds of events.
Configuration Rule: according to the measurement type and event of the dedicated
measurement.
13.4.2.99
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
332
The parameter indicates the power offset of the DPCH maximum DL power, which
defines which threshold that shall trigger event A, B for transmitted carrier power
measurement.
This parameter is a ternary array, which is fixed to the first element evtAbTcpThrd[0] for
handover control.
OMC path
GUI:
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter configuration
13.5
13.5.1
Parameter List
No.
Field Name
Thresh(URatEcNoEvMeasfor
E)
Cell for 3A
Thresh(\URatRscpEvMeasfor
E)
Cell for 3A
3.
W(URatEcNoEvMeasforE)
4.
W(\URatRscpEvMeasforE)
5.
ThreshSys(URatEcNoEvMea
sforE)
ThreshSys(\URatRscpEvMea
sforE)
1.
2.
6.
333
7.
hysteresis(URatEcNoEvMea
sforE)
8.
hysteresis(\URatRscpEvMea
sforE)
9.
TrigTime(URatEcNoEvMeasf
orE)
10.
TrigTime(\URatRscpEvMeasf
orE)
11.
InterRatCfgNo(URatEcNoEv
MeasforE)
12.
InterRatCfgNo(URatRscpEv
MeasforE)
13.
FilterCoeff(URatEcNoEvMea
sforE
14.
FilterCoeff(URatRscpEvMea
sforE)
15.
EventNum(URatEcNoEvMea
sforE)
16.
EventNum(\URatRscpEvMea
sforE)
17.
Hysteresis
Hysteresis
Time to Trigger
Time to Trigger
EventId
[MAX_RAT_MEAS_EVENT]
(URatEcNoEvMeasforE)
18.
EventId
[MAX_RAT_MEAS_EVENT]
(\URatRscpEvMeasforE)
19.
ChoStraMulRatHo
20.
RncPsHoLteSw
21.
22.
23.
24.
r99RtEutraHoSw
r99NrtEtraHoSw
hsdpaEutraHoSw
hsupaEutraHoSw
334
25.
RncSrvccSw
26.
eUtranFilterCoeff(URatEcNo
EvMeasforE)
27.
eUtranFilterCoeff(URatEcNo
PrdMeas)
28.
eUtranFilterCoeff(URatRscp
EvMeasforE)
29.
eUtranFilterCoeff(URatRscp
PrdMeas)
30.
31.
PSL2USWCHBYCS
EutranNMeasBand(UExterna
lEUtranCellFDD)
32.
EutranNMeasBand(UExterna
lEUtranCellTDD)
33.
CelReturnLteSwch
34.
fastRetEUtranSwch
35.
UtraSISwitch
UTRA SI Switch
36.
EutranNCblstSwch
37.
38.
StateMode(UENbrBlkList)
LdBsdEutranHOInd
39.
EutranDlLdThrd
40.
EutranUlLdThrd
41.
EutraDetectionInd
42.
IndoorCellInd
43.
HoToEutraPenTimer
44.
sonTransReqPeriod
45.
46.
47.
48.
sonTransReqNumThrd
sonTransRespSwitch
sonTransRespNumThrd
LteCellIdenFlag
335
49.
MulSrvRePsHoLteSw
Service
50.
51.
EutranPsHoMode
PsHoLteMeasTimer
52.
53.
GresPara52
54.
CresPara7
55.
GresPara7
56.
PsSigForImsInd
57.
EutranFreqBandInd
58.
59.
60.
in specific Frequency
NeutranCId
13.5.2
Parameter Configurations
13.5.2.1
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
336
This parameter indicates the absolute threshold of the UTRAN cell quality that is used by
the UE to judge event 3a. The range and unit of the parameter are related to the
measurement quantity of the cells of the UTRAN system.
The smaller the value configured, the more difficult the event 3a been reported.
13.5.2.2
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the absolute threshold of the UTRAN cell quality that is used by
the UE to judge event 3a. The range and unit of the parameter are related to the
measurement quantity of the cells of the UTRAN system.
The smaller the value configured, the more difficult the event 3a been reported.
13.5.2.3
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the weight of the best cell in the quality judgment of event 3a. It
is used in judging the quality of the UTRAN system in inter-RAT measurement.
337
See the description of the formula in Section 7.1 for the effect of this parameter on the
inter-RAT measurement.
13.5.2.4
GUI:
OMC path
Managed
Element
->UMTS
Configuration->Measurement
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the weight of the best cell in the quality judgment of event 3a. It
is used in judging the quality of the UTRAN system in inter-RAT measurement.
See the description of the formula in Section 7.1 for the effect of this parameter on the
inter-RAT measurement.
13.5.2.5
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the absolute threshold used when judging the quality of other
RAT configured for event 3a/3b/3c. The value range and unit of this parameter are
related to the measurement quantity of the cells of other systems. At present, the
measurement quantity can only be GSM Carrier RSSI of the GSM system, which
338
corresponds to the CPICH RSCP of the UMTS system. Hence, the value range and unit
of this parameter correspond to CPICH RSCP.
The larger the value configured, the more difficult event 3a/3b/3c be reported.
13.5.2.6
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the absolute threshold used when judging the quality of other
RAT configured for event 3a/3b/3c. The value range and unit of this parameter are
related to the measurement quantity of the cells of other systems. At present, the
measurement quantity can only be GSM Carrier RSSI of the GSM system, which
corresponds to the CPICH RSCP of the UMTS system. Hence, the value range and unit
of this parameter correspond to CPICH RSCP.
The larger the value configured, the more difficult event 3a/3b/3c be reported.
13.5.2.7
Hysteresis (URatEcNoEvMeasforE)
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
339
This parameter indicates the hysteresis used when judging whether the event meets the
conditions of been triggered.
This parameter is related to the measurement quantity and the event type. If a small
hysteresis is configured, the corresponding event will be reported in a high probability;
and vice versa.
13.5.2.8
Hysteresis(URatRscpEvMeasforE)
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the hysteresis used when judging whether the event meets the
conditions of been triggered.
This parameter is related to the measurement quantity and the event type. If a small
hysteresis is configured, the corresponding event will be reported in a high probability;
and vice versa.
13.5.2.9
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the time difference between the time that the event generation
is detected and the time that the event is reported. The event can be triggered and
340
reported only when the event is detected and still meets all requirements of event
triggering after Time to trigger.
The larger the value is, the stricter the judgment is for the event to be triggered. The
parameter should be configured according to the actual requirements.
13.5.2.10
Time to Trigger(URatRscpEvMeasforE)
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the time difference between the time that the event generation
is detected and the time that the event is reported. The event can be triggered and
reported only when the event is detected and still meets all requirements of event
triggering after Time to trigger.
The larger the value is, the stricter the judgment is for the event to be triggered. The
parameter should be configured according to the actual requirements.
13.5.2.11
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
341
This parameter indicates the index of the inter-RAT measurement configuration. This
configuration index is cited in the table Inter-RAT measurement configuration
relationship of the service type-related UE.
That
is,
the
parameter
Inter-RAT
Measurement
Profile
Identity
(namely
13.5.2.12
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
is,
the
parameter
Inter-RAT
Measurement
Profile
Identity
(namely
342
13.5.2.13
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the filtering factor that the UE performs the L3 filtering on the
UTRAN measurement results of the inter-RAT measurement. The smaller the filtering
factor, the larger the effect of the measurement on the final result.
13.5.2.14
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the filtering factor that the UE performs the L3 filtering on the
UTRAN measurement results of the inter-RAT measurement. The smaller the filtering
factor, the larger the effect of the measurement on the final result.
13.5.2.15
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
343
Parameter configuration
This parameter indicates the number of events that should be configured for the
inter-RAT measurement configuration index for a certain purpose.
13.5.2.16
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the number of events that should be configured for the
inter-RAT measurement configuration index for a certain purpose.
13.5.2.17
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the identity of the event triggered by the inter-RAT
measurement (3a~3d).
13.5.2.18
OMC path
344
GUI:
Managed
Element
->UMTS
Configuration->Measurement
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the identity of the event triggered by the inter-RAT
measurement (3a~3d).
13.5.2.19
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->UTRAN
Parameter configuration
This parameter indicates which inter-RAT will be selected in priority for handover in
multi-RAT scenario.
13.5.2.20
OMC path
Parameter configuration
13.5.2.21
OMC path
345
Parameter configuration
This parameter indicates whether R99 RT inter-Rat handover to EUTRAN allowed or not.
13.5.2.22
OMC path
Parameter configuration
This parameter indicates whether R99 NRT inter-Rat handover to EUTRAN allowed or
not.
13.5.2.23
OMC path
Parameter configuration
This parameter indicates whether HSDPA inter-Rat handover to EUTRAN allowed or not.
13.5.2.24
OMC path
Parameter configuration
This parameter indicates whether HSUPA inter-Rat handover to EUTRAN allowed or not.
13.5.2.25
OMC path
346
Parameter configuration
13.5.2.26
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the value of the filtering factor is when the UE executes an LTE
measurement.
13.5.2.27
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Inter-RAT
Configuration->Service
Measurement
Parameter configuration
This parameter indicates the value of the filtering factor is when the UE executes an LTE
measurement.
13.5.2.28
OMC path
347
GUI:
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the value of the filtering factor is when the UE executes an LTE
measurement.
13.5.2.29
GUI:
OMC path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Function
Configuration->Service
Configuration->Inter-RAT
Measurement
Parameter configuration
This parameter indicates the value of the filtering factor is when the UE executes an LTE
measurement.
13.5.2.30
PSL2USWCHBYCS
OMC path
Parameter configuration
This parameter indicates is the switch of permit PS handover from LTE to UTRAN
because of CSFB.
13.5.2.31
OMC path
348
Parameter configuration
This parameter indicates is the maximum bandwidth allowed to measure on the single
frequency of EUTRAN in inter-RAT measurement.
13.5.2.32
OMC path
Parameter configuration
This parameter indicates is the maximum bandwidth allowed to measure on the single
frequency of EUTRAN in inter-RAT measurement.
13.5.2.33
OMC path
Parameter configuration
This parameter indicates cell switch of fast return to EUTRAN for CS service based on
the EUTRAN CSFB.
13.5.2.34
OMC path
Parameter configuration
349
This parameter is a RNC switch, which indicates whether to enable the function of fast
return to EUTRAN or not.
13.5.2.35
UTRA SI Switch
OMC path
Parameter configuration
This parameter indicates whether RNC supports the UTRA SI function of RIM.
13.5.2.36
OMC path
Parameter configuration
The parameter indicates cell switch of support the EUTRAN nbr blacklist.
13.5.2.37
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->UTRAN
Parameter configuration
The parameter indicates UE state which RNC can configure the EUTRAN nbr blacklist in
accordance with.
There are two kinds of UE state: 0, Cell Selection/Reselection; 1, Handover.
350
13.5.2.38
OMC path
Parameter configuration
The parameter indicates if consider the target cell load Information during the inter
system handover procedure.
13.5.2.39
OMC path
Parameter configuration
The parameter indicates the downlink overload threshold in the EUTRAN system.
13.5.2.40
OMC path
Parameter configuration
The parameter indicates the uplink overload threshold in the EUTRAN system.
351
13.5.2.41
OMC path
Parameter configuration
The parameter is the E-UTRA detection indicator. If this indicator exists and is set to
TRUE, and the UE is in CELL_PCH, URA_PCH state or idle mode, the UE may detect
the presence of an E-UTRA cell on a frequency with a priority lower than the current
UTRA cell and report the information to the NAS.
13.5.2.42
OMC path
Parameter configuration
13.5.2.43
OMC path
Parameter configuration
When handover from UMTS to LTE is failed, the timer initiates, and RNC will not handle
inter-RAT measurement report until the timer expires.
352
The parameter is larger, next handover interval is longer, which may increase call-drop
possibility due to worsening quality. The parameter is smaller, next handover interval is
shorter and handover attempt is more frequent, which will occupy more system resource.
13.5.2.44
OMC path
Parameter configuration
The parameter indicates the period of RNC starting the SON Transfer.
13.5.2.45
OMC path
Parameter configuration
The parameter indicates Son Transfer Request Number Threshold in one second, is
used for controlling volume of messages.
13.5.2.46
OMC path
Parameter configuration
The parameter is the switch of response the LTE Son Transfer request.
13.5.2.47
OMC path
353
Parameter configuration
The parameter indicates Response the Son Transfer message Number Threshold in one
second, is used for controlling volume of messages.
13.5.2.48
GUI:
OMC path
Managed
Element->UMTS
Logical
Function
Configuration->Link
Configuration->Iups Link
Parameter configuration
The parameter indicates the Method of Identify EUTRAN cell. If SGSN do not recognize
eNodeBID of EUTRAN CELL, RNCID/LAC/RAC should be used for EUTRAN CELL, and
this parameter should be set as 1, otherwise 0.
13.5.2.49
OMC path
Parameter configuration
The parameter indicates whether EUTRAN compressed mode and measurement are
initialized for PS service to provide service fast return to EUTRAN as soon as possible or
redirection to EUTRAN without measurement when CS service is released for Multi-RAB
with CSFB from EUTRAN.
13.5.2.50
OMC path
354
Parameter configuration
This parameter indicates PS Handover Mode when CS is released for EUTRAN CSFB
Multi-RAB Service. PS handover or redirection can be used based on the UE capability.
13.5.2.51
OMC path
Parameter configuration
The parameter indicates timer of deactivate compressed mode for Fast Return to
EUTRAN. If compressed mode is initialized due to fast return to EUTRAN, the timer
activates. When the timer expires, if event(3C) doesnt report, RNC will judge whether
compressed mode is deactivate or not based on current signal quality.
13.5.2.52
OMC path
Parameter configuration
This parameter will be used for deciding how many users are allowed to activate the
compressed mode for Balance Strategy Based on Measurement simultaneously.
13.5.2.53
OMC path
355
Parameter configuration
Bit10: This parameter indicates PS Handover Mode when CS is released for EUTRAN
SRVCC Multi-RAB Service. PS handover or redirection can be used based on UE
capability.
Bit11: This parameter is the switch of checking the UE E-UTRA Capability before
initiating the PS handover procedure from UMTS to LTE.
13.5.2.54
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->UTRAN
Parameter configuration
Bit0~Bit1: When CS service is released for Multi-RAB with SRVCC from EUTRAN, the
parameter indicates whether EUTRAN compressed mode and measurement are
initialized for PS service to provide service fast return to EUTRAN as soon as possible or
redirection to EUTRAN without measurement.
Bit2: This parameter indicates cell switch of fast return to EUTRAN for CS service based
on the EUTRAN SRVCC.
13.5.2.55
OMC path
Parameter configuration
356
When pre-redirection information is not indicated in RRC Connection Request, if the time
between RRC Connection Request and CS RAB establish is not greater than this
parameter, the service is indicated CSFB.
13.5.2.56
OMC path
Parameter configuration
13.5.2.57
GUI:
OMC path
Managed
Cell->Adjacent
Element
Relation
->UMTS
Logical
Function
Configuration->EUTRAN
Configuration->UTRAN
Neighbouring
Cell
Black
Parameter configuration
13.5.2.58
GUI:
OMC path
Managed
Cell->Adjacent
Element
Relation
->UMTS
Logical
Function
Configuration->EUTRAN
Configuration->UTRAN
Neighbouring
Cell
Black
Parameter configuration
The parameter indicates the downlink E-UTRAN Absolute Radio Frequency Channel
Number (EARFCN).
357
13.5.2.59
GUI:
OMC path
Managed
Cell->Adjacent
Element
Relation
->UMTS
Logical
Function
Configuration->EUTRAN
Configuration->UTRAN
Neighbouring
Cell
Black
Parameter configuration
13.5.2.60
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->UTRAN
Parameter configuration
The parameter is used to identify an EUTRAN physical cell. There are 504 unique physical-layer
cell identities. The physical-layer cell identities are grouped into 168 unique physical-layer
cell-identity groups, each group containing three unique identities.
13.6
13.6.1
Parameter List
No.
Field Name
1.
BasedImsiHoInd
2.
MCC(UImsiSnacFilter)
MCC
3.
MNC(UImsiSnacFilter)
MNC
4.
imsiMatchedDgtNum
5.
imsiMatchedDigit
6.
SMCC
7.
SMNC
358
8.
SNAC
9.
MCC(USnac)
MCC
10.
MNC(USnac)
MNC
11.
LAC(USnac)
12.
SNAC(USnac)
13.
MCC(UUtranCellFDD)
14.
MCC(UExternalUtranCellF
DD)
15.
MCC(UExternalGsmCell)
16.
MNC(UUtranCellFDD)
17.
MNC(UExternalUtranCellF
DD)
18.
MNC(UExternalGsmCell)
19.
LAC(UUtranCellFDD)
20.
LAC(UExternalUtranCellF
DD)
21.
SNAC[MAX_NUM_SNAC_
PER_UTRANCEL]( UExter
nalUtranCellFDD)
22.
SNACNum(UExternalUtra
nCellFDD)
23.
SNAC[MAX_NUM_SNAC_
PER_GSMCEL]( UExternal
GsmCell)
24.
SNACNum(UExternalGsm
Cell)
13.6.2
Parameter Configurations
13.6.2.1
OMC path
359
Parameter configuration
This parameter indicates whether RNC supports handover based IMSI or not.
13.6.2.2
MCC(UImsiSnacFilter)
OMC path
Parameter configuration
This parameter indicates the mobile country code (MCC) of the IMSI card. See 0 in the
text for the use case.
13.6.2.3
MNC(UImsiSnacFilter)
OMC path
Parameter configuration
This parameter indicates the mobile network code (MNC) of the IMSI card. See 0 in the
text for the use case.
13.6.2.4
OMC path
360
Parameter configuration
The parameter indicates the number of IMSI digit, the maximum value of which is 15.
13.6.2.5
OMC path
Parameter configuration
The parameter indicates the digit of IMSI, including MCC, MNC and extend information.
13.6.2.6
OMC path
Parameter configuration
The parameter indicates the MCC of the shared network, namely the MCC of the target
location area code (LAC) that the handover is allowed in.
13.6.2.7
MNC of Shared
Network
OMC path
Parameter configuration
The parameter indicates the MNC of the shared network, namely the MNC of the target
LAC that the handover is allowed in.
361
13.6.2.8
OMC path
Parameter configuration
This parameter indicates the shared network area code (SNAC). It is defined by the
customer.
13.6.2.9
MCC(USnac)
OMC path
Parameter configuration
13.6.2.10
MNC(USnac)
OMC path
Parameter configuration
362
13.6.2.11
OMC path
Parameter configuration
13.6.2.12
OMC path
Parameter configuration
13.6.2.13
OMC path
Parameter configuration
363
13.6.2.14
OMC path
Parameter configuration
This parameter indicates the MCC of UTRAN cells that do not belong to the RNC.
13.6.2.15
OMC path
Parameter configuration
13.6.2.16
OMC path
Parameter configuration
13.6.2.17
OMC path
364
Parameter configuration
This parameter indicates the MNC of the cells that do not belong to the RNC.
13.6.2.18
OMC path
Parameter configuration
13.6.2.19
OMC path
Parameter configuration
13.6.2.20
OMCR Interface
Parameter configuration
This parameter indicates the LAC of UTRAN cells that do not belong to the RNC.
13.6.2.21
OMC path
365
Parameter configuration
This parameter indicates the shared network area code that the neighboring cell belongs
to. One cell can belong to at most four SNACs (shared network area code).
13.6.2.22
OMC path
Parameter configuration
This parameter indicates the number of shared network area code that the neighboring
cell belongs to.
13.6.2.23
OMC path
Parameter configuration
This parameter indicates the shared network area code that the neighboring cell belongs
to. One cell can belong to at most four SNACs (shared network area code).
13.6.2.24
OMC path
366
Parameter configuration
This parameter indicates the number of shared network area code that the neighboring
cell belongs to.
13.7
13.7.1
Parameter List
No.
1.
Field Name
HspaSptMeth(UUtranCellFD
D)
2.
3.
T1d
RncFeatSwitchBit1
4.
HsdpaCmAssoMode
5.
HspaSptMeth(UExternalUtra
nCellFDD)
13.7.2
Parameter Configurations
13.7.2.1
OMC path
Parameter configuration
13.7.2.2
OMC path
367
GUI:
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Configuration->Hspa Configuration
Parameter configuration
For HSPA, this parameter indicates the minimum interval required for the change of the
HSPA serving cell or the transition between the HS and DCH channels. A large value of
this parameter helps to avoid too frequent HSPA serving cell change and channel
transition.
13.7.2.3
OMC path
Parameter configuration
This parameter indicates whether the IUR interface supports the HSDPA feature.
13.7.2.4
GUI:
OMCR Interface
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Configuration->Hspa Configuration
Parameter configuration
368
13.7.2.5
OMC path
Parameter configuration
13.8
13.8.1
Parameter List
No.
1.
2.
Field Name
HspaSptMeth(UUtranCellFDD)
RncFeatSwitchBit2
3.
HsupaCmAssoMode
4.
HspaSptMeth(UExternalUtran
CellFDD)
Iur
Interface Process
HSUPA Associate CM Method
HSPA Support Method
13.8.2
Parameter Configurations
13.8.2.1
HSUPA
OMC path
Parameter configuration
369
13.8.2.2
OMC path
Parameter configuration
This parameter indicates whether the IUR interface supports the HSUPA feature.
13.8.2.3
GUI:
OMCR Interface
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Configuration->Hspa Configuration
Parameter configuration
13.8.2.4
OMC path
Parameter configuration
370
13.9
13.9.1
Parameter List
No.
Field Name
1.
MbmsSuptInd
2.
T1d
13.9.2
Parameter Configurations
13.9.2.1
OMC path
Parameter configuration
This parameter indicates whether to support the MBMS. When the parameter is set to 0
(Not Support), the cell does not support the MBMS service.
When the parameter is set to 1 (Support MBMS and not MBMS), the cell supports both
the MBMS service and the mixed R99, R5, and R6 service. In this case, the cell can
either use a separate carrier frequency for establishing the co-coverage relationship or
HSC structure with other cells, or use the same carrier frequency as the neighboring cell.
When the parameter is set to 2 (Only Support MBMS), the cell supports only the MBMS
service. In this case, non-S-CCPCHs can neither be allocated separately for users nor
exist as the DCH channel of the concurrent service. The purpose of such a cell is to
share the load of the MBMS service.
13.9.2.2
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Configuration->Hspa Configuration
371
Parameter configuration
For HSPA, this parameter indicates the minimum interval required for the change of the
HSPA serving cell or the transition between the HS and DCH channels. A large value of
this parameter helps to avoid too frequent HSPA serving cell change and channel
transition.
For MBMS, this parameter indicates the minimum interval required for changing the best
cell of the MBMS service for two times caused by event 1d. This parameter helps to
avoid too frequent change between the PTP and PTM bearer types.
14
14.1
Counter List
14.1.1
Description
C310322211
C310322212
C310322213
C310322214
C310322215
C310322216
C310322217
C310322218
C310322219
C310322220
C310322221
C310322222
C310322223
Number of active set update failed to add cell, by cause
C310322224
C310322225
372
C310322226
C310322227
C310322228
C310322229
C310322230
C310322231
C310322232
C310322233
C310322234
C310326690
C310326691
C310326692
C310322235
C310322236
C310322237
C310322238
C310322239
Number of active set update failed to delete cell, by cause
C310322240
C310322241
C310322242
C310322243
C310322244
C310322245
C310322246
Number of active set update attempted to add cell, by traffic class
C310322247
C310322248
C310322249
C310322250
Number of active set update failed to add cell, by traffic class
C310322251
C310322252
C310322253
Number of active set update attempted to delete cell, by traffic class
C310322254
373
C310322255
C310322256
C310322257
C310322258
Number of active set update failed to delete cell, by traffic class
C310322259
C310322260
C310322261
C310322262
C310322263
C310322264
C310322265
DCH
C310322266
C310322267
C310322268
C310322269
C310322270
C310322271
C310322272
Number of active set update failed to add cell, by traffic class in DCH
C310322273
C310322274
C310322275
C310322276
C310322277
C310322278
C310322279
C310322280
C310322281
DCH
C310322282
C310322283
C310322284
C310322285
C310322286
DCH
374
C310322287
C310322288
C310322289
C310322290
C310322291
C310322292
C310322293
C310322294
Statistics of active set update for HS-DSCH
C310322295
C310322296
C310322297
C310322298
C310322299
C310322300
C310322301
C310322302
C310322303
C310322304
C310322305
C310322306
C310322307
Number of active set update failed to add cell for E-DCH, by cause
C310322308
C310322309
C310322310
C310322311
C310322312
C310322313
C310322314
C310322315
C310322316
C310322317
Number of active set update failed to delete cell for E-DCH, by cause
C310322318
375
C310322319
C310322320
C310322321
C310322322
C310322323
C310322324
C310322325
C310322326
C310322327
C310322328
traffic class
C310322329
C310322330
C310322331
Number of active set update failed to delete cell for E-DCH, by traffic
C310322332
class
C310322333
C310322334
C310322335
C310322336
traffic class
C310322337
C310322338
C310322339
Number of active set update failed to delete cell for E-DCH, by traffic
C310322340
class
C310322341
C310322342
C310322343
Number of active set update for attempted add cell with multi-traffic
C310322344
C310322345
C310322346
with multi-traffic
C310322347
C310322348
C310322349
C310322350
376
C310322351
C310322352
C310322353
C310322354
C310322355
C310322356
C310322357
C310322358
C310322359
C310322360
C310322361
C310322362
Soft handover rate of E-DCH user
C310322363
C310322364
C310322379
C310322380
C310322381
C310322382
C310322383
C310322384
C310322385
C310322386
C310322387
C310322388
C310322389
C310322390
C310322391
C310322392
C310322393
C310322394
C310322395
C310322396
377
C310322397
C310322398
C310322399
C310322400
C310322401
C310322402
C310322403
C310322404
C310322405
C310322406
C310322407
C310322408
C310322409
C310322410
C310322475
C310322476
C310322477
C310322478
C310322479
C310322480
Number of UE having E-DCH active set cell in cell
C310322481
C310322482
C310322483
C310322484
C310322485
C310322486
C310322487
C310322488
C310322489
Statistics of active set update, by traffic
C310322490
C310322491
C310322492
378
C310322493
C310322494
C310322495
C310322496
C310322497
C310322498
Statistics of active set update, by domain
C310322499
C310322500
C310322501
C310322502
14.1.2
Description
C310336836
C310336837
C310336838
C310336839
C310336840
C310336841
C310336842
C310336843
C310336844
C310336845
C310336846
C310336847
C310336848
C310336849
C310336850
C310336851
C310336852
C310336853
C310336854
379
C310336855
C310336856
C310336857
C310336858
C310336859
C310336860
C310336861
C310336862
C310336863
C310336864
C310336865
C310332503
C310332504
C310332505
C310332506
C310332507
C310332508
C310332509
C310332510
C310332511
C310332512
C310332513
C310332514
C310332515
C310332516
C310332517
C310332518
C310332519
C310332520
C310332521
C310332522
C310332523
380
C310332524
C310332525
C310332526
C310332527
C310332528
C310332529
C310332530
C310332531
C310332532
C310332533
C310332534
C310332535
Number of inter-Node B hard handover statistics
C310332536
C310332537
C310332538
C310332539
C310332540
C310332541
C310332542
C310332543
C310332544
C310332545
C310332546
C310332547
C310332548
C310332549
C310332550
C310332551
C310332552
C310332553
C310332554
C310332555
381
C310332556
C310332557
C310332558
C310332559
C310332560
C310332561
C310332562
C310332563
C310332564
C310332565
C310332566
C310332567
C310332568
C310332569
C310332570
C310332571
C310332572
C310332573
C310332574
C310332575
C310332576
C310332577
C310332578
C310332579
C310332580
C310332581
C310332582
C310332583
C310332584
C310332585
C310332586
C310332587
382
C310332588
C310332589
C310332590
C310332591
C310332592
C310332593
C310332594
C310332595
C310332596
C310332597
C310332598
C310332599
C310332600
Number of hard handover statistics, by source cause
C310332601
C310332602
C310332603
C310332604
C310335701
C310335702
C310335703
C310335704
C310335705
C310335706
C310335707
C310335708
C310335738
C310332605
C310332606
C310332607
Number of CS hard handover statistics, by measurement quality
C310332608
C310332609
C310332610
383
C310332611
C310332612
C310332613
C310332614
C310332615
C310332616
C310332617
C310332618
C310332619
C310332620
C310332621
C310332622
C310332623
C310332624
C310332625
C310332626
C310332627
C310332628
C310332629
C310332630
C310332631
C310332632
C310332633
C310332634
Number of PS hard handover statistics, by measurement quality
C310332635
C310332636
C310332637
C310332638
C310332639
C310332640
C310332641
C310332642
384
C310332643
C310332644
C310332645
C310332646
C310332647
C310332648
C310332649
C310332650
C310332651
C310332652
C310332653
C310332654
C310332655
C310332656
Number of hard handover statistics, by traffic class
C310332657
C310332658
C310332659
C310332660
C310332661
C310332662
C310332663
C310332664
C310332665
C310332666
C310332667
C310332668
C310332669
C310332670
C310332671
C310332672
C310336605
C310336606
385
C310336607
C310336608
C310336609
C310336610
C310336611
C310336612
C310336613
C310336614
C310336615
C310336616
C310336617
C310336618
C310336619
C310336620
C310332673
C310332674
C310332675
C310332676
C310332677
C310332678
C310332679
C310332680
C310332681
C310332682
C310332683
C310332684
C310332685
C310332686
C310332687
C310332688
C310332689
C310332690
386
C310332691
C310332692
C310332693
C310332694
C310332695
C310332696
C310332697
C310332698
C310332699
C310332700
C310336076
C310336077
C310336078
C310336079
C310336080
C310336081
C310336082
C310336083
C310336084
C310336085
C310336086
C310336087
C310336088
C310336089
C310336090
C310336091
C310336092
C310336093
C310336094
C310336095
C310336096
C310336097
387
C310336098
C310336099
C310336100
C310336101
C310336102
C310336103
C310336104
C310336105
C310336106
C310336107
C310336108
C310336109
C310336110
C310336111
C310336112
C310336113
C310336114
C310336115
C310336116
C310336117
C310336118
C310336119
C310336120
C310336121
C310336122
C310336123
C310336124
Statistics of hard handover outgoing by siganlling
C310336125
C310336126
C310336127
C310336128
C310336129
388
C310336130
C310336131
C310336132
C310336133
C310336134
C310336135
C310336136
C310336137
C310336138
C310336139
C310336140
C310336141
C310336142
C310336143
C310336144
C310336145
C310336146
C310336147
C310336148
C310336149
C310336150
C310336151
C310336152
C310336153
C310336154
C310336155
C310336156
C310336157
C310336158
C310336159
C310336160
C310336161
389
C310336162
C310336163
C310336164
C310336165
C310336166
C310336167
C310336168
C310336169
C310336170
C310336171
C310336172
C310336173
C310336174
C310336175
C310336176
C310336177
C310336178
C310336179
C310336180
C310336181
C310336182
C310336183
C310336184
C310336185
C310336186
C310336187
C310336188
C310336189
Statistics of hard handover outgoing by siganlling
C310336190
C310336191
C310336192
C310336193
390
C310336194
C310336195
C310336196
C310336197
C310336198
C310336199
C310336200
C310336201
C310336202
C310336203
C310336204
C310336205
C310336206
C310336207
C310336208
C310336209
C310336210
C310336211
C310336212
C310336213
C310336214
C310336215
C310336216
C310336217
C310336218
C310336219
C310336220
C310336221
C310336222
C310336223
C310336224
C310336225
391
C310336226
C310336227
C310336228
C310336229
C310336230
C310336231
C310336232
C310336233
C310336234
C310336235
C310336236
C310336237
C310336238
C310336239
C310336240
C310336241
C310336242
C310336243
C310336244
C310336245
C310336246
C310336247
C310336248
C310336249
C310336250
C310336251
C310336252
C310336253
C310336254
Statistics of hard handover outgoing by siganlling
C310336255
C310336256
C310336257
392
C310336258
C310336259
C310336260
C310336261
C310336262
C310336263
C310336264
C310336265
C310336266
C310336267
C310336268
C310336269
C310336270
C310336271
C310336272
C310336273
C310336274
C310336275
C310336276
C310336277
C310336278
C310336279
C310336280
C310336281
C310336282
C310336283
C310336284
C310336285
C310336286
C310336287
C310336288
C310336289
393
C310336290
C310336291
C310336292
C310336293
C310336294
C310336295
14.1.3
Description
C310342701
C310342702
C310342703
C310342704
C310342705
C310342706
C310342707
Statistics of attempted relocation preparation, by channel type
C310342708
C310342709
C310342710
C310342711
C310342712
C310342713
C310342714
C310342715
C310342716
C310342717
C310342718
C310342719
C310342720
C310342721
C310342722
C310342723
394
C310342724
C310342725
C310342726
C310342727
C310342728
C310342729
C310342730
C310342731
C310342732
Number of attempted relocation preparation, by traffic class
C310342733
C310342734
C310342735
C310342736
C310342737
C310342738
C310342739
C310342740
Number of attempted outgoing relocation, by traffic class
C310342741
C310342742
C310342743
C310342744
C310342745
C310342746
C310342747
C310342748
C310342749
C310342750
C310342751
C310342752
C310342753
C310342754
domain, by cause
C310342755
395
C310342756
C310342757
C310342758
C310342759
C310342760
C310342761
C310342762
C310342763
domain, by cause
C310342764
C310342765
C310342766
C310342767
C310342768
C310342769
C310342770
C310342771
C310342772
C310342773
C310342774
C310342775
C310342776
C310342777
C310342778
C310342779
C310342780
C310342781
C310342782
C310342783
C310342784
C310342785
C310342786
396
C310342787
C310342788
C310342789
C310342790
C310342791
C310342792
C310342793
C310342794
C310342795
C310342796
C310342797
C310342798
C310342799
C310342800
C310342801
C310342802
C310342803
domain, by cause
C310342804
C310342805
C310342806
C310342807
C310342808
C310342809
domain, by cause
C310342810
C310342811
C310342812
C310342813
domain, by cause
C310342814
C310342815
C310342816
C310342817
397
C310342818
domain, by cause
C310342819
C310342820
C310342821
C310342822
C310342823
C310342824
C310342825
C310342826
C310342827
C310342828
C310342829
C310342830
C310342831
C310342832
by cause
C310342833
C310342834
C310342835
C310342836
C310342837
C310342838
C310342839
C310342840
domain, by cause
C310342841
C310342842
C310342843
C310342844
C310342845
C310342846
C310342847
C310342848
398
C310342849
C310342850
domain, by cause
C310342851
C310342852
C310342853
C310342854
C310342855
C310342856
C310342857
C310342858
C310342859
C310342860
C310342861
C310342862
C310342863
C310342864
domain, by cause
C310342865
C310342866
C310342867
C310342868
C310342869
C310342870
C310342871
C310342872
C310342873
C310342874
C310342875
C310342876
involved for PS
domain, by cause
C310342877
C310342878
C310342879
C310342880
399
C310342881
by cause
C310342882
C310342883
C310342884
C313780279
C313780280
Statistics of outgoing relocation preparation for Adjacent RNC
C313780281
C313780282
C313780283
C313780284
C313780285
C313780286
Statistics of outgoing relocation for Adjacent RNC
C313780287
C313780288
C313780289
C313780290
14.1.4
Description
C310352885
C310352886
C310352887
C310352888
C310352889
C310352890
C310352891
C310352892
C310352893
C310352894
C310352895
C310352896
C310352897
400
C310352898
C310352899
C310352900
C310352901
C310352902
C310352903
C310352904
C310352905
C310352906
C310352907
C310352908
C310352909
C310352910
Number
of
attempted
incoming
inter-RAT
handover
for
PS
for
PS
domain(Cell Re-selection)
Number
domain(Cell Re-selection)
C310352911
C310352912
C310352913
C310352914
C310352915
C310352916
C310352917
C310352918
C310352919
C310352920
C310352921
C310352922
C310352923
C310352924
C310352925
C310352926
C310352927
C310352928
handovers
401
C310352929
C310352930
C310352931
C310352932
C310352933
C310352934
C310352935
C310352936
C310352937
C310352938
handovers
C310352939
C310352940
C310352941
C310352942
C310352943
Statistics of outgoing CS and PS inter-RAT handovers(DTM)
C310352944
C310352945
C310352946
C310352947
C310352948
Number of failed outgoing CS inter-RAT handovers
C310352949
C310352950
C310352951
C310356583
C310352952
C310352953
C310352954
C310352955
Number of failed outgoing PS inter-RAT handovers
C310352956
C310352957
C310352958
C310352959
402
Order)
C310352960
C310352961
C310352962
C310352963
C310352964
C310352965
C310352966
C310352967
C310352968
C310352969
C310352970
C310352971
C310352972
C310352973
C310352974
C310352975
C310352976
C310352977
C310352978
C310352979
C310352980
C310352981
C310352982
C310352983
C310352984
C310352985
C310352986
C310352987
C310352988
C310352989
C310352990
403
C310352991
C310352992
C310352993
C310352994
C310352995
C310352996
C310352997
C310352998
C310352999
C310353000
C310353001
C310353002
C310353003
C310353004
C310353005
C310353006
C310353007
C310353008
C310353009
C310353010
by channel type
C310353011
C310353012
C310353013
C310353014
C310353015
C310353016
C310353017
C310353018
C310353019
by channel type
C310353020
C310353021
C310353022
404
C310353023
C310353024
C310353025
C310353026
C310353027
C310353028
C310353029
C310353030
C310353031
C310353032
C310353033
C310353034
C310353035
C310353036
C310353037
C310353038
C310353039
C310353040
by channel type
C310353041
C310353042
C310353043
C310353044
C310353045
C310353046
C310353047
C310353048
C310353049
C310353050
by channel type
C310353051
C310353052
C310353053
C310353054
405
C310353055
C310353056
C310353057
C310353058
C310353059
C310353060
C310353061
C310353062
C310353063
C310353064
C310353065
C310353066
C310353067
C310353068
C310353069
C310353070
C310353071
C310353072
C310353073
C310353074
C310353075
C310353076
C310353077
C310353078
C310353079
C310353080
C310353081
C310353082
C310353083
C310353084
C310353085
C310353086
406
C310353087
C310353088
C310353089
C310353090
C310353091
C310353092
C310353093
C310353094
C310353095
C310353096
C310353097
C310353098
C310353099
C310353100
C310353101
C310353102
C310353103
C310353104
C310353105
C310353106
C310353107
C310353108
C310353109
C310353110
C310353111
C310353112
C310353113
C310353114
C310353115
C310353116
C310353117
C310353118
407
C310353119
quality
C310353120
C310353121
C310353122
C310353123
C310353124
C310353125
C310353126
C310353127
C310353128
C310353129
C310353130
C310353131
C310353132
C310353133
C310353134
C310353135
C310353136
C310353137
C310353138
C310353139
C310353140
C310353141
C310353142
C310353143
C310353144
C310353145
C310353146
quality
C310353147
C310353148
C310353149
C310353150
408
C310353151
Quality
C310353152
C310353153
C310353154
C310353155
C310353156
C310353157
C310353158
C310353159
C310353160
C310353161
Number
C310353162
measurement Quality
of
DCH
other
RT
outgoing
inter-RAT
handover,by
C310353163
C310353164
C310353165
C310353166
C310353167
C310353168
C310353169
C310353170
Quality
C310353171
C310353172
C310353173
C310353174
C310353175
C310353176
C310353177
C310353178
Quality
C310353179
C310353180
C310353181
C310353182
409
C310353183
Quality
C310353184
C310353185
C310353186
C310353187
C310353188
C310353189
C310353190
C310353191
C310353192
C310353193
C310353194
C310353195
C310353196
C310353197
C310353198
C310353199
C310353200
C310353201
C310353202
C310353203
C310353204
C310353205
C310353206
C310353207
C310353208
C310353209
C310353210
C310353211
C310353212
C310353213
C310353214
410
C310353215
C310353216
C310353217
C310353218
C310353219
C310353220
C310353221
C310353222
C310353223
C310353224
C310353225
C310353226
C310353227
C310353228
C310353229
14.1.5
Description
C310363230
C310363231
C310363232
C310363233
C310363234
C310363235
C310363236
C310363237
C310363238
C310363239
C310363240
C310363241
C310363242
C310363243
411
C310363244
C310363245
C310363246
C310363247
C310363248
C310363249
C310363250
C310363251
C310363252
C310363253
C310363254
C310363255
C310363256
C310363257
C310363258
C310363259
C310363260
C310363261
C310363262
C310366700
C310366701
C310366702
C310366703
C310366704
C310366705
C310366706
C310366707
C310366708
C310366709
C310366710
C310366711
C310366712
412
C310366713
C310366714
C310366715
C310366716
C310366717
C310366718
C310366719
C310366720
C310366721
C310363263
C310363264
C310363265
C310363266
C310363267
C310363268
C310363269
C310363270
C310363271
C310363272
C310363273
C310363274
C310363275
C310363276
C310363277
C310363278
C310363279
C310363280
C310363281
C310363282
C310363283
C310363284
C310363285
413
C310363286
C310363287
C310363288
C310363289
C310363290
C310363291
C310363292
C310363293
C310363294
C310363295
C310366722
C310366723
C310366724
C310366725
C310366726
C310366727
C310366728
C310366729
C310366730
C310366731
C310366732
Statistics of E-DCH serving cell change in Iur
C310366733
C310366734
C310366735
C310366736
C310366737
C310366738
C310366739
C310366740
C310366741
C310366742
C310366743
414
14.1.6
Description
C310890001
C310890002
C310890003
C310890004
C310890005
C310890006
C310890007
C310890008
C310890009
C310890010
C310890011
C310890012
C310890013
C310890014
C310890015
C310890016
C310890017
C310890018
C310890019
C310890020
C310890021
C310890022
C310890023
C310890024
Stattistics of outgoing inter-NodeB,intra-RNC hard handover
C310890025
C310890026
C310890027
C310890028
C310890029
C310890030
415
C310890031
C310890032
C310890033
C310890034
C310890035
C310890036
C310890037
C310890038
C310890039
C310890040
C310890041
C310890042
C310890043
C310890044
C310890045
Stattistics of outgoing inter-RNC hard handover via Iur
C310890046
C310890047
C310890048
C310890049
C310890050
C310890051
C310890052
C310890053
C310890054
C310890055
C310890056
C310890057
C310890058
Stattistics of outgoing inter-RNC hard handover switching in the CN
C310890059
C310890060
C310890061
C310890062
416
C310890063
C310890064
C310890065
C310890066
C310890067
C310890068
C310890069
C310890070
C310890071
C310890072
C310890073
C310890074
C310890075
C310890076
C310890077
C310890078
C310890079
C310890080
Stattistics of outgoing hard handover,by channel and traffic
C310890081
C310890082
C310890083
C310890084
C310890085
C310890086
C310890087
C310890088
C310890089
C310890090
C310890091
C310890092
C310890093
C310890094
417
C310890095
C310890096
C310890097
C310890098
C310890099
C310890100
C310890101
C310890102
C310890103
C310890104
C310890105
C310890106
C310890107
C310890108
C310890109
C310890110
C310890111
C310890112
C310890113
C310890114
C310890115
C310890116
C310890117
C310890118
C310890119
C310890120
C310890121
C310890122
C310890123
C310890124
C310890125
Statistics of outgoing hard handover,by domain
C310890126
418
C310890127
C310890128
C310890129
C310890130
C310890131
C310890132
C310890133
C310890134
C310890135
C310890136
14.1.7
Description
C310880137
Stattistics of radio link addition for soft handover between cells
C310880138
C310880139
C310880140
C310880141
C310880142
Number of failed radio link addition for soft handover between cells,by
C310880143
cause
C310880144
C310880145
C310880146
C310880147
Stattistics of radio link deletion for soft handover between cells
C310880148
C310880149
C310880150
C310880151
C310880152
Number of failed radio link deletion for soft handover between cells,by
cause
C310880153
C310880154
C310880155
419
C310880156
C310880157
Stattistics of soft handover between cells
C310880158
C310880159
C310880160
C310880161
C310880162
C310880163
C310880164
C310880165
C310880166
C310880167
C310880168
C310880169
C310880170
C310880171
C310880172
C310880173
C310880174
C310880175
C310880176
C310880177
C310880178
C310880179
C310880180
C310880181
C310880182
C310880183
C310880184
C310880185
Statistics of soft handover,delete Radio link,by channel and traffic
C310880186
C310880187
420
C310880188
C310880189
C310880190
C310880191
C310880192
C310880193
C310880194
C310880195
C310880196
C310880197
C310880198
C310880199
14.1.8
14.1.9
Description
Statistics of detected set
Description
C310900001
C310900002
C310900003
C310900004
inter-RAT handovers
C310900005
C310900006
C310900007
C310900008
C310900009
C310900010
C310900011
inter-RAT handovers
C310900012
C310900013
421
C310900014
C310900015
C310900016
C310900017
C310900018
C310900019
C310900020
Stattistics of failed outgoing CS inter-RAT handovers
C310900021
C310900022
C310900023
C310900024
C310900025
C310900026
C310900027
C310900028
C310900029
C310900030
C310900031
C310900032
C310900033
C310900034
C310900035
C310900036
C310900037
C310900038
C310900039
C310900040
Stattistics
of
attempted
outgoing
PS
inter-RAT
C310900041
C310900042
C310900043
C310900044
422
C310900045
C310900046
C310900047
C310900048
C310900049
C310900050
C310900051
C310900052
C310900053
C310900054
C310900055
C310900056
C310900057
C310900058
C310900059
C310900060
C310900061
traffic
C310900062
C310900063
C310900064
C310900065
C310900066
C310900067
C310900068
C310900069
C310900070
C310900071
C310900072
Stattistics of incoming inter-RAT handovers
C310900073
C310900074
C310900075
C310900076
423
C310900077
C310900078
C310900079
C310900080
C310900081
C310900082
14.1.10
Description
C312190211
C312190212
C312190213
C312190214
C312190215
C312190216
C312190217
C312190218
C312190219
C312190220
C312190221
Statistics of active set update ,Iur
C312190222
C312190223
C312190224
C312190225
C312190226
C312190227
C312190228
C312190229
C312190230
C312190231
C312190232
C312190233
424
C312190234
C312190235
C312190236
C312190237
C312190238
C312190239
C312190240
C312190241
C312190242
C312190243
C312190244
C312190245
C312190246
C312190247
C312190248
C312190249
C312190250
C312190251
C312190252
C312190253
C312190254
14.1.11
Description
Number of attempted incoming inter-RAT handover for SRVCC
C312106765
C312106766
C312106767
C312106768
C312106769
C312106770
425
C312106771
C312106772
C312106773
C312106774
C312106775
C312106776
C312106777
C312106778
C312106779
C312106780
C312106781
C312106782
C312106783
C312106784
C312106785
C312106786
C312106787
C312106788
C312106789
C312106790
Eutran)
C312106791
C312106792
C312103530
C312103531
C312103532
C312103533
to UTRAN)
C312103534
C312103535
14.1.12
Description
426
C310605484
C310760044
C310615519
C310585292
C310585293
C310585294
C310585295
C310585296
C310585297
C310585298
C310585299
C310585300
C310585301
C310585302
C310585303
C310585304
C310585305
C310585306
C310585307
C310585308
C310585309
427
C310585310
C310585311
C310585312
C310585313
C310585314
14.2
Alarm List
This feature has no related alarm.
15
Glossary
B
BLER
BSC
C
CIO
CN
Core Network
CPICH
CS
Circuit switched
CSFB
CS Fallback
CTCP
428
DCH
Dedicated Channel
DL
DPCCH
DPDCH
DRBC
DRNC
DSCR
DTCP
DTM
E
Ec/No
Received energy per chip divided by the power density in the band
E-DCH
E-UTRA
E-UTRAN
F
FDD
GBR
GGSN
GPRS
GSM
429
GERAN
H
HCS
HLR
HSDPA
HS-DSCH
HSPA
HS-PDSCH
HSUPA
I
IMS
IP Multimedia Sub-system
IMSI
LTE
M
MBMS
MGW
Media GateWay
MSC
NACC
NRT
Non-Real Time
430
O
OLPC
P-CPICH
PS
Packet switched
Q
Qos
Quality of Service
R
RAB
RIM
RL
Radio Link
RNC
RNS
RRC
RSCP
RSRP
RSSI
RT
Real Time
RTWP
S
SF
Spreading Factor
431
SGSN
SI
System Information
SIR
SON
SRNC
SRNS
Serving RNS
SRVCC
T
TCP
TDD
TFCS
TG
Transmission Gap
TGD
TGL
TGSN
TGPL
TTI
U
UE
User equipment
UL
Uplink
UMTS
Universal
Mobile
Telecommunications
System
432
UTRA
UTRAN
W
WCDMA
433