ZTE UMTS Load Balance Feature Guide U9.2

Operator Logo
Load Balance
WCDMA RAN
Feature Guide
Load Balance Feature Guide
Version Date Author Approved By Remarks
V4.0 2010-06-29 Wang Kunhuang Zheng Dan Not open to the Third Party
2010 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains propriet ary information of ZTE and is not to be
disclosed or used without the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document
is subjected to change without notice.
ZTE Confidential Proprietary 2010 ZTE Corporation. All rights reserved. I

TABLE OF CONTENTS
1 Function Attribute ...............................................................................................1
2 Overview .............................................................................................................1
2.1 Overview of the Functions.....................................................................................1
2.1.1 Load Balancing ....................................................................................................1
2.1.2 Frequency Priority ................................................................................................1
2.1.3 Load Balance for HS DPA Service .........................................................................2
2.1.4 Directed Ret ry Between HS -DS CH and DCH .........................................................2
2.1.5 Load Balance for HS UPA Service .........................................................................2
2.1.6 Directed Ret ry Between HS -DS CH and DCH .........................................................2
3 Load-based Multi-carrier Interoperation .............................................................2

3.1 Load E valuating Factors .......................................................................................3
3.1.1 Uplink interference ...............................................................................................3
3.1.2 Downlink power....................................................................................................4
3.1.3 Code res ources ....................................................................................................4
3.1.4 HSDPA throughput per user..................................................................................5
3.1.5 Coupling Operation Between These Factors ..........................................................6
3.2 Load-based Multi-carrier Int eroperation in Initial RRC procedure .............................7
3.3 Load-based Multi-carrier Int eroperation in RAB assignment ....................................7
3.4 Load-Bas ed Multi-carrier Interoperation in Call holding procedure ...........................9
4 Service-based Multi-carrier Interoperation .........................................................9

4.1 Service-based Multi-carrier Interoperation in Initial RRC procedure .......................10
4.2 Service-based Multi-carrier Interoperation in RAB Assignment ..............................11
4.3 Service-based Multi-carrier Interoperation in Call holding procedure ......................13
5 Coupling of Load-ba sed and Service-based Multi-carrier Interoperations........13
6 Inter-RAT Load Balance Strategy......................................................................13

6.1 Directed Ret ry Triggered by Inter-RA T Balancing .................................................14
6.2 Directed Ret ry Triggered by Admission Failure .....................................................14
7 Configuration and Parameters..........................................................................14

7.1 Parameter List ...................................................................................................14
7.2 Parameter Configuration .....................................................................................15
7.2.1 Load Balance Switch of Initial RRC Procedure .....................................................15
7.2.2 Load Balance Switch of RAB Assignment Proc edure ............................................16
7.2.3 Load Balance Switch of Call holding procedureing Procedure ...............................16
7.2.4 Load balance switch for downlink power ..............................................................16
7.2.5 Load Balance Switch for Uplink Int erferenc e ........................................................17
7.2.6 Load Balance Switch for Code ............................................................................17
7.2.7 Load Balance Switch for HS DPA Throughput .......................................................17
7.2.8 Downlink Power Weight for Load Balance ............................................................17
7.2.9 Uplink Interference Weight for Load Balance ........................................................18
7.2.10 Code Weight for Load Balance............................................................................18
7.2.11 HSDPA Throughput Weight for Load Balance .................................................18
7.2.12 UTRA N Downlink A vailable Load Balance Threshold (Power ) for CS ....................19
7.2.13 Inter-System Downlink A vailable Load Balanc e Threshold (Power) for CS .............19
7.2.14 UTRA N Downlink A vailabl e Load Balance Threshold (Power) for R99 PS ..............19
7.2.15 UTRA N Downlink A vailable Load Balance Threshold (Power) for HSDPA ..............20
ZTE Confidential Proprietary 2010 ZTE Corporation. All rights reserved. II

7.2.16 Permitted Payload Differenc e Downlink A vailable Load Threshold in Int er -

frequency Cells-P ower........................................................................................20
7.2.17 UTRA N Uplink A vailable Load Balance Threshold (Interference ) for CS ................20
7.2.18 Inter-system Uplink A vailable Load Balance Thres hold (Interference) for CS ..........21
7.2.19 UTRA N Uplink A vailable Load Balance Threshold (Interference) for R99 PS ..........21
7.2.20 UTRA N Uplink A vailable Load Balance Threshold (Interference) for HS UPA ..........21
7.2.21 Permitted Payload Differenc e Uplink A vailable Load Threshold in Int er-frequency
Cells-Interference ...............................................................................................22
7.2.22 UTRA N Downlink A vailable Load Balance Threshold (Code) for CS ......................22
7.2.23 UTRA N Downlink A vailable Load Balance Threshold (Code) for R99 PS ...............22
7.2.24 UTRA N Downlink A vailable Load Balance Threshold (Code) for HS DPA ...............23
frequency Cells-Code .........................................................................................23
7.2.26 UTRA N Downlink A vailable HSDPA Load Balanc e Threshold (HS DPA Throughput)
for HSDPA .........................................................................................................23
frequency Cells-HS DPA Throughput....................................................................24
7.2.28 Service B alance S witch of Initial RRC Procedure .................................................24
7.2.29 Service B alance S witch of RAB Assignment Procedure ........................................24
7.2.30 Service B alance S witch of Call holding procedureing Procedure ............................24
7.2.31 Preferred Traffic Type.........................................................................................25
7.2.32 Share Cover Indication (utranRelation) ................................................................25
7.2.33 Share Cover Indication (gsmRelation)..................................................................25
7.2.34 HSPA Support Method(utranCell) ........................................................................25
7.2.35 HSPA Support Method(externalUt ranCell) ...........................................................26
7.2.36 CS Balance S witch of RAB Assignment Procedure ...............................................26
7.2.37 Switch of CS Handover for CS+PS in Multi-Carrier Scenario .................................26
8 Counter And Alarm ...........................................................................................27

8.1 Counter List .......................................................................................................27
8.2 Alarm List ..........................................................................................................27
9 Glossary ...........................................................................................................27
ZTE Confidential Proprietary 2010 ZTE Corporation. All rights reserved. III
TABLES
Table 1 Services and target cell types which can carry the services .......................................8
Table 2 List of Preferred Target Cells Table of Sequence of Cells of Services ......................10
Table 3 Table of Cell Types Supported by Current Services of UE .......................................11
Table 4 Table of Sequence of Cells of Services ..................................................................12
ZTE Confidential Proprietary 2010 ZTE Corporation. All rights reserved. IV

1 Function Attribute
System version: [RNC V3.09, OMMR V3. 09, Node B V4.09, OMMB V4. 09]
Attribute: Mandatory function
Relat ed NE:
UE NodeB RNC MSCS MGW SGSN GGSN HLR
- - - - -
Note:
*-: Non-related NE
*: Related NE
Dependency: [None]
Exclusion: None
Remarks: None.
2 Overview
2.1 Overview of the Functions
2.1.1 Load Balancing
Load balancing includes the intra-system load balancing (load-based multi-carrier

interoperation, service-bas ed multi-carrier interoperation) and Int er-RA T load balancing.
Its chief principal is to deploy the inter-cell traffic based on the load of cell and the
neighboring cell configuration (ShareCover, GsmShareCover) reasonably, and use the
system resources effectively to enhance the system capacity and QoS.
2.1.2 Frequency Priority
The feature provides the function that each cell supports HSDPA or HS UPA or not
(HspaSpt Meth), and each cell can be set to be preferred to voice service preferred, data
service preferred or no preferred(PrefTrafType). During RRC connection setup, RAB
assignment, handover, cell reselection and channel migration procedures, RNC will
choose appropriate cell as target cell according to service type and UE capability.
The frequency priority feature considers the current load of each cell in each frequency
layer, avoiding congestion because of heavy traffic in a cell.
ZTE Confidential Proprietary 2010 ZTE Corporation. All rights reserved. 1

2.1.3 Load Balance for HSDPA Service
RNC supports HS DPA load balance bet ween carriers in UMTS network or between
UMTS and GSM when HSDPA function is introduced. Besides downlink power factor,
the HS DPA capability of Node B and UE are also c onsidered for HS DPA service load
balance.
2.1.4 Directed Retry Between HS-DSCH and DCH
RNC supports that eac h cell is configurated to different attribute, for example, some cells
do not support R99 sevice but HS DPA service, that is service is carried on HS -DS CH
but not DCH. If network is deployed with two or more carriers, one of which is set to be
equipped with one dedic ated HSDPA carrier and one dedicated R99 c arrier at least,
radio resources should be allocat ed into different carriers according to services
attributes. If users access frequency is different from the one which service needs, RNC
will perform handover between carriers to retry services into frequency which service
needs.
2.1.5 Load Balance for HSUPA Service
RNC supports HS UPA load balance bet ween carriers in UMTS network or between
UMTS and GSM when HSUPA function is introduced. Besides RTWP factor, the HS UPA
capability of Node B and UE are also considered for HSUPA service load balance.
2.1.6 Directed Retry Between HS-DSCH and DCH
If net work is deployed with two or more carriers, one of which is set to be equipped with
one dedicated HS DPA carrier and one dedic ated R99 carrier at least, radio resources
should be allocated into different carriers according to services attributes. If users
access frequency is different from the one which service needs, RNC will perform
handover bet ween carriers to retry services into frequency which service needs.
3 Load-based Multi-carrier Interoperation

Load-based multi-carrier interoperation selects a target cell preferably in Initial RRC
procedure, RAB assignment, and call holding proc edure, rat her than triggering the
handover actively. That is, if a cell whe re the UE resides is overloaded, when selecting a
target cell in Initial RRC procedure, RAB assignment, and call holding procedure, RNC
will include the cell and its neighboring cells which are with Overlap or
Covers(ShareCover) relationship into the target cell list. The cell with lowest overall
load in the list is selected as the target cell for access or handover. Its application
scenarios are classified into three types:
Initial RRC procedure: involving Initial RRC procedure.
RAB assignment: involving RAB assignment.

Call holding procedure: involving handover, relocation from other system or RNC to
local RNC, call re-establishment triggered by CELL UP DA TE, state transition from
non-CE LL_DCH to CELL_DCH.
In the three scenarios, related functions a re controlled by three switches: Init RrcLBS w,
RabAssLBS w, CallHoldLBSw.
Principles of target cell selection in load-based multi-carrier interoperation:
1) Combine the target cell of UE for access/handover and its neighboring cells which are
with Overlap or Covers(ShareCover) relationship into a target cell set (named Set );
2) Pick a set (named S et1) of cells which the UE frequency-band supports from the
target cell set;
3) Select the cell with the lowest overall load which can provide the requested s ervice
from the cell Set1.
3.1 Load Evaluating Factors

The cell load is evaluated by four factors: uplink interference (RTWP), downlink power
(TCP ), downlink code resources, and HS DPA throughput per us er(only for HSPA cell).
The related functions of the four factors are controlled by four switches:
UlLdB alP wrS wch, DlLdB alP wrS wch, LdB alCdS wch, and LdBalHsS wch. The restricted
resource may be different in different scenarios. For example, for cells in some areas,
downlink power is frequently limited, while in cells of another area, the code resource is
frequently limited. Therefore, different weights can be configured according to the four
factors, so as to adapt to different application scenarios.
3.1.1 Uplink interference
The uplink interference of a cell us es the RTWP (HSPA cells use uplink payload) as the
load evaluating criterion.
The uplink interference is measured by the uplink payload:
Uplink payload (UlRtwpE ffLoad) = Load generat ed by uplink DCH + Load generated by
non-scheduling E -DCH + Load generated by the throughput of GB R services of
scheduling E-DCH
Load generated by uplink DCH + Load generated by non-scheduling E-DCH can be

measured by NodeB RSEPS, while Load generated by the throughput of GBR services
of scheduling E-DCH can be calculated by the uplink interference predictive formula.
See <ZTE UMTS Admission Control Feature Guide>.
Define uplink available intereference as:
Uplink available intereference(A vailableLoad 1 )=100%-uplink payload(UlRtwpEffLoad)
When the uplink load is heavy, load balancing is required, that is, the traffic is balanced
to cells of other carriers to reduce the cell load. Thus, the stability of the system is
ensured.

When the uplink available interference is less than the preset threshold (for CS, R99 PS,
HSDPA and HSUPA service, the threshold is UlLdThdCs, UlLdThdR99Ps,
UlLdThdR99Ps and UlLdThdHse4U resepectively), the available interference of the cell
is little, namely the current load of the cell is heavy. The load-based multi-carrier
interoperation should be triggered.
3.1.2 Downlink power
The downlink power of a cell uses the CTCP (HSPA cells use downlink payload) as the
load evaluating criterion.
The downlink power is measured by the downlink payload:
Snum
downlink payload NOHSDSCHPower HSDSCHRequiredPower
i 0
i
Where,
NOHSDS CHPower refers to the Transmitted carrier power of all codes not used for HS-
PDSCH or HS-SCCH transmission that is report ed by the NodeB.
HSDSCHRequiredPoweri It indicates the HS-DSCH Required Power of the

scheduling priority of the current cell.
Define downlink available power as:
Downlink available power(A vailableLoad2)=100%-downlink payload
When the uplink load is heavy, load balancing is required, that is, the traffic is balanced
to cells of other carriers to reduce the cell load. Thus, the stability of the system is
ensured.
When the downlink available power is less than the preset threshold (for CS, R99 PS,
HSDPA and HSUPA service, the threshold is DlPwrThdCs, DlP wrThdR99Ps,
DlP wrThdHsd and DlP wrThdHsd resepectively), it means that available the power is
small and the current load of the cell is heavy. The load-based multi-carrier
interoperation should be triggered.
3.1.3 Code resources
By using load measuring method of the downlink channelization code resources,

calculate the proportion of the quantity of code words in use to the total quantity of code
words to indicate the load of the downlink channelization code resources.
Then, take SF = 128 as the statistic granularity of the code resources. Because the
HSDPA is shared, herein we just calculate the occupancy of code resource of non-
HSPDS CH and minimum necessary HSPDS CH.
The code load is measured by the channel code usage:
Code Usage=(number of Non HS-P DSCH occupied SF128+MinHspdschNum*8)/128

Where,
MinHspdschNum = Max(MinHspdschNum in OMCR, MinHspdschNumbyGB R). See

<ZTE UMTS Code Resource Feature Guide V3.0 CHS>.
Define downlink available code resource as:
Downlink available code resource (A vailableLoad 3)=100%-code usage
When the downlink available code resources is less than t he preset threshold (for CS,
R99 PS, HSDPA and HSUPA service, the threshold is DlCdThdCs, DlCdThdR99Ps,
DlCdThdHsd and DlCdThdHsd resepectively), the load of the cell is heavy. The load-
based multi-carrier interoperation should be triggered.
3.1.4 HSDPA throughput per user
As power surplus can be used maximumly in HSDPA cells, the effective power can not
reflect the difference of load between cells. So HSDPA throughput per user is selected
as HSDPA load evaluation criterion, details are following:
HsOcuCodeNum*HspdschBitRate
Available throughput per user(CapOfEachHsUser)=
NumOfHsdpaUser+1
Where,
HsOcuCodeNum, the number of SF16 can be occupied by HS-P DSCH in cell, which is
statisticsed by SF128 as granularity.
HsOcuCodeNum=min{ (128-number of SF128 occupied by non-HSPDSCH )/8 ,MaxNumofHspdsch}

where,
MaxNumofHspdsch is the maximum number of HSP DSCH channels configured in

OMCR.
HspdschBitRate indicates the average data speed of a HS-P DSCH channel, which can
be configured in OMCR.
NumOfHsdpaUs er is the number of HSDPA on-line users in cell.
In order to be consistent with other factors, HSDPA available throughput per user is
transformed to percent format:
CapOfEachHsUser
HS available throughput per user ratio(AvailableLoad 4 )= *100%
MaxCapHsUser
where,
MaxCapHs User is the maximum value of HS DPA throughput per user.
When HSDPA available throughput per user ratio is less than the preset threshold(for
HSDPA and HSUPA service, the thrshold is DlLdHsThdHsd), it means that the
available HS throughput resource is limited and the HSPA load is heavy. The load-
based multi-carrier interoperation should be triggered.

3.1.5 Coupling Operation Between These Factors
Four factors should be taken into consideration when evaluating the load: uplink
interference, downlink power, downlink code resources, and HS DPA throughput per
user. The restricted resources vary in different scenarios. For example, for cells in
some areas, downlink power is restricted usually, while in cells of another area, the code
resources are restricted instead. Therefore, different weights can be configured as
required according to the four factors, so as to adapt to different application scenarios.
When evaluating the load of cell, the load weight, load, and load threshold of the four
factors are t acken into account to calc ulate the cell overall load. See the following
calculation method.
k
LoadWeight AvailableLoad i AvailableLoadThrd i* Weight i
i 1
The meanings of the parameters are as follows:
k indicates the number of factors that are considered in load balancing. The value is 4 at
present, which indicates code resources, downlink power, uplink interference, and
HSDPA throughput per user.
AvailableLoad, the available load of estimated cell
If the estimated cell is source cell, it equals to actual available load plus Delta;
otherwise it equals to actual available load.
If the estimated cell is HSDPA dual-carrier cell and HS-S CCH less is not
activated, it equals to the sum of available load of primary and secondary
carrier(for uplink interferenc e factor, it equals to the available load of primary
carrier); if the estimated cell is HSDPA dual -carrier cell and HS-S CCH less not
activated, it equals to the available load of primary carrier.
AvailableThrdLoad, the available load balancing threshold configured by OMC.
The threshold is differentiated by service, for CS, R99 PS, HS/D and HS/E, the
corresponding threshold is taken.
For source cell, the threshold of source cell is taken; for target cell, the threshold
of target cell is taken; for HSDPA dual-carrier cell, the available load balance
threshold of primary carrier is considered.
Delta indicates the load balancing threshold difference (corresponds to ExtraCDeltaTrd,

ExtraCDeltaTru, Ext raCDeltaCdTrd, and E xtraCDeltaHsTrd c onfigured in the source c ell)
of the source cell configured by OMC. If source cell is HSDPA dual-carrier cell and HS-
SCCH less is not activat ed, it equals to sum of the value of primary and secondary
carrier (for uplink interferenc e factor, it equals to the value of primary carrier); if source
cell is not HSDPA dual-carrier cell, it equals to the corresponding configured
value.Weight indicates the weight (corresponds to DlLdBalP wrWeight,
UlLdB alP wrWeight, LdBalCdWeight, and DlLdBalHsWeight configured in the source cell)
of each factor.
LoadWeight indicates the evaluation value. The value is larger which means the actual
load of target cell is lower, and vice versa.

The four factors - code resources, downlink power, uplink interference, and HS DPA
throughput per user - can be controlled by four switches: LdBalCdS wc h,
DlLdB alP wrS wch, UlLdB alP wrS wch, and LdBalHsS wch. When a factor is switched to
OFF, it will not be t aken into consideration in load balancing, and the corresponding
weight is invalid (0). The sum of weights ( DlLdB alP wrWeight, UlLdBalP wrWeight,
LdBalCdWeight, and DlLdBalHsWeight) of each factor is 1, which is ensured by the
configuration. If all of the four factors are switched to OFF, load balancing is not
performed.
If the available load of the code resources of some service is less than its threshold of
load balancing , or the available load of downlink power of some service is less than its
threshold of load balancing , or the uplink available interference of some service is less
than its threshold of load balancing , or HS DPA available throughput per user is less
than its threshold of load balancing the load of t he cell is heavy. Otherwise, the load is
light. According to this principle, the serving cells and their UE -supporting neighboring
cells which are with Overlap or Covers(S hareCover) relationship are included into
two cell lists, one for the heavy load cells and the other for the light load cells. Weight
calculations are performed for each cell in the two lists according to the above formula,
and weights are sorted in an descending order. The larger the weight is, the lower the
load is. The multi-carrier operation is triggered when the target cell of UE for
access/handover is overloaded. That is, in Initial RRC proc edure, RAB assignment, and
call holding procedure, select a cell with the largest weight (lowest evaluating of load)
from target cell and its neighboring cells which are with Overlap or
Covers(S hareCover) relations hip to access, and the cell should be supported by UE,
and can be carried by services.
3.2 Load-based Multi-carrier Interoperation in Initial

RRC procedure
In the initial RRC procedure, if InitRrcLBSw switch is set to ON, the load of the s erving
cell meet the requirements of load -based multi-carrier interoperation (see 3.1 Load
E valuating Crit erion), and the serving cell ha ve inter-frequency neighboring cells with
Overlap or Covers (ShareCover)relationship, the load-based multi-carrier
interoperation in Initial RRC procedure will be t riggered, and a cell wit h the lowest load
will be selected for access
Note: In the initial RRC procedure, the specific services and some capabilities of the UE
are not known. To avoid the balance failure due to balancing UE to the band that the UE
does not support, the neighboring cell whose frequency band is different from the
current serving cell will not be taken int o account as the target cell of the load balancing.
3.3 Load-based Multi-carrier Interoperation in RAB

assignment
In the RAB assignment procedure, if RabAssLBSw switch is set to ON, the load of
the serving cell meet the requirements of load-based multi-carrier interoperation (see 3.1
Load E valuating Criterion), and the serving cell have inter -frequency neighboring cells
which have Overlap or Covers(S hareCover) relationship with the serving cell, the
load-based multi-carrier interoperation in RAB assignment procedure will be triggered,
that is the target cell selection is triggered by the load balancing in RAB assignment
procedure. For CS Service, CsBalSwch should be extra indicated whether the balance

function is open for CS service during RAB assignment procedure. If CsBalSwch switch
is set to Closed, the load balance will not be triggered for CS service ,and vice versa.
After the int roduction of HS DPA and HSUPA, the cells can be categorized into multiple
types:
1) Cells supporting HSUPA and HS DPA.
2) Cells supporting HSUPA, HSDPA and DCH.
3) Cells supporting HSDPA and DCH.
4) Cells supporting HSDPA only.
5) Cells whic h do not support HSUPA and HSDPA. There are also UMTS2100 and
UMTS 900 cells of different bands. The UE provides different support to t hese cells.
Therefore, in the load-based multi-carrier interoperation in RAB assignment, the service
properties and UE capabilities should be taken into consideration to select the target cell.
The specific principles are as follows:
(1) Combine the target cell of UE for access/handover and its neighboring cells which
are with Overlap or Covers(ShareCover) relationship into a target cell Set;
(2) Pick a set (named as Set1) of cells which the UE band supports from the target cell
set in step (1);
(3) Pick a set (named as Set2) of cells which the UE currently originated service
supports from Set1 in step (2);
(4) Select the lowest load cell as the final target cell for access/handover in Set2.
See services and target cell types which can carry the services in the following table:
Table 1 Services and target cell types which can carry the services
Service Type DCH/DCH HS-DSCH/DCH HS-DSCH/E-DCH

Target cell types Cells which do not Cells supporting Cells supporting
which can carry support HSUPA and HSDPA and DCH HSUPA and HSDPA
the servic es HSDPA Cells supporting Cells supporting
Cells supporting HSUPA, HS DPA, HSUPA, HS DPA,
HSDPA and DCH and DCH and DCH
Cells supporting
HSUPA, HS DPA,
and DCH
That is to say, the cell whose service type is not included in t he above table will be
considered as an unsupported cell, and excluded out of the cell list.

3.4 Load-Based Multi-carrier Interoperation in Call

holding procedure
In handover, relocation from other system or RNC to local RNC, call re-establishment
triggered by CELL UP DA TE, state transition from non-CELL_DCH to CE LL_DCH, if
CallHoldLBS w is set to ON, the judgment of load -based multi-carrier interoperation in
call holding procedure is performed. Its handling proc edure is the same as that of the
load-based multi-carrier interoperation in RAB assignment.
4 Service-based Multi-carrier Interoperation

The serving cells can be categorized by service type (HspaS ptMeth) into five types:
1) Cells supporting HSUPA and HS DPA;
2) Cells supporting HSUPA, HSDPA and DCH;
3) Cells supporting HSDPA and DCH;
4) Cells supporting HSDPA only;
5) Cells which do not support HS UPA and HS DPA.
And by frequency-band, the cells can be divided into UMTS 900, UMTS1800 and so on.
The services carried by the cells may vary according to cell types. For example, the cells
which do not support HS UPA and HSDPA mainly carry voice services, while cells
supporting HSDPA and DCH mainly carry data services. As a result, the parameter
PrefTrafType is defined for each cell to instruct which type of servic e is preferred for
that cell. The operator can set the parameter flexibly to satisfy the requirements in
different scenarios.
PrefTrafType definition:
Cs prefer is designed for receiving voice services.
R99 Ps prefer is designed for receiving R99 data services.
HS Ps prefer is designed for receiving HS data services.
Service-based multi-carrier interoperation selects a target cell preferably in Initial RRC

procedure, RAB assignment, and call holding proc edure, rat her than triggering the
handover actively. That is, when selecting a target cell in Initial RRC procedure, RAB
assignment, and call holding procedure, RNC will select a proper cell as the target cell
for access or handover based on specific service originated by the user equipment (UE ).
Its application scenarios are classified into three types:
Initial RRC procedure: involving Initial RRC procedure.
RAB assignment: involving RAB assignment.

Call holding procedure: involving handover, relocation from other system or RNC to
local RNC, call re-establishment triggered by CELL UP DA TE, state transition from
non-CE LL_DCH to CELL_DCH.
In the three scenarios, related functions are cont rolled by three switches configured by
OMC: InitRrcSBS w, RabAssSBSw, CallHoldSBS w.
4.1 Service-based Multi-carrier Interoperation in Initial

RRC procedure
In Initial RRC procedure, if Init RrcSBS w is set to ON, and the cell where the UE currently
resides has inter-frequency neighboring cells which are with Overlap or
Covers(S hareCover) relationship, the most suitable cell is selected from the currently
cell and these neighboring cells based on the establish cause of RRC request, UE
supporting status, and cell properties (PrefTrafType, HspaSpt Meth) to access.
For detailed preference rules of the target cell is as follows:
For the Establishment cause of Originating Conversational Call, Terminating

Conversational Call, Emergency Call, Registration, Detach, Call re-
establishment,Originating Low Priority Signalling, Terminating Low Priority Signall ing:
Determine whether the following preferred cells exist in the light loaded target cells:
Cs preferred cells which do not support HSUPA and HS DPA is preferred
If no light loaded cell is selected in the step above, select the first cell in the load ranki ng
list for access(see 3.1.5 Coupling Operation Between These Factors).
For the Establishment cause of MBMS reception, MBMS ptp RB request:
The current cell is the target cell.
For the Establishment cause of Originating Streaming Call,Originating Interacti ve

Call,Originating Background Call, Terminating Streaming Call, Terminating Interactive
Call, Terminating Background Call,Originating High Priority Signalling, Terminating High
Priority Signalling, Call Re-establishment, Inter-RA T Cell Reselection, Inter-RA T Cell
Change Order, Originating Subscribed Traffic Call:
The table 2 is the target cell selection rules for these calls.
Table 2 List of Preferred Target Cells Table of Sequence of Cells of Services
DCH/DCH HS-DSCH/DCH,
HS-DSCH/E-DCH
Establishment causes: Determine whether the Determine whether the
Originating Streaming following preferred cells following preferred cells exist
Call, Originating exist in the lightly loaded in the lightly loaded target
Interactive Call, target cells: cells:
Originating Background R99 Ps preferred cells HS Ps preferred cells which
Call, Terminating which do not support can support the R5

Streaming Call, HSUPA and HSDPA

Terminating Interactive The first cell that meets the
Call, Terminating The first cell that meets preference rule is the
Background Call, the preference rule is the preferred cell. If no cell is
Originating High Priority preferred cell. If no cell selected in the step above,
Signaling, Terminating is selected in the step select the first cell in the load
High Priority Signaling, above, select the first cell ranking list for access.
Call Re-establishment, in the load ranking list for
Inter-RAT Cell access. Cells supporting R5
Reselection, Inter-RAT
indicates:
Cell Change Order,
Originating Subscribed Cells supporting HS UPA and
Traffic Call HSDPA;
Cells supporting HS UPA,
HSDPA, and DCH;
Cells supporting HS DPA and
DCH;
Cells supporting HS DPA only.
The four types share the
same priority.
Note: The lightly-loaded cell in the table 2 refers to the cell: whose code resource load is
not less than the threshold of code load balancing , and downlink power is not less than
the threshold of download load balancing , and uplink interference is not less than the
threshold of uplink load balancing ., and HSDPA available throughput per user is not
less than the threshold of HS DPA load balancing.
4.2 Service-based Multi-carrier Interoperation in RAB

Assignment
In RAB assignment, if RabAssSBS is set to ON, the system will perform the judgment of
the service-based multi-carrier interoperation in RAB assignment. After the introduction
of HS DPA and HSUPA, the cells (HspaSpt Meth) can be categorized into multiple types:
1) Cells supporting HS UPA and HS DPA. 2) Cells supporting HSUPA, HS DPA and DCH.
3) Cells supporting HSDPA and DCH. 4) Cells supporting HS DPA only. 5) Cells which
do not support HS UPA and HS DPA. And by band, the cells can be divided into
UMTS900 and UMTS1800. The supporting capabilities of UE vary by type of the cell.
Cons equently, the sorting and selection of the target cell should be based on the UE
capabilities, current established services, and the Prefer property of each cell. The
detailed procedure is as follows:
1) Combine t he current cell where UE resides and its neighboring c ells which are with
Overlap or Covers(ShareCover) relationship into a target cell set (named Set);
(2) Exclude the cells whose bands are not supported by UE, and the cells which are not
supported by the current service originated by UE from the S et in step (1). The remained
cells form the a target set named Set1. The cell types which are supported by the
current services of UE are as follows:
Table 3 Table of Cell Types Supported by Current Services of UE
Service Type DCH/DCH HS-DSCH/DCH HS-DSCH/E-DCH

Target cell types Cells which do not Cells supporting Cells supporting
which can carry support HSUPA and HSDPA and DCH HSUPA and HSDPA
the servic es HSDPA Cells supporting Cells supporting
Cells supporting HSUPA, HS DPA, HSUPA, HS DPA,
HSDPA and DCH and DCH and DCH
Cells supporting
HSUPA, HS DPA,
and DCH
That is to say, the cell whose service type is not included in t he above table will be
considered as an unsupported cell, and excluded out of the cell list.
(3) Cells in Set1 in step (2) will be sorted according to specific service types and the
Prefer property of cells (PrefTrafType). See below table.
Table 4 Table of Sequence of Cells of Services
Sequence of Cells
CS service Cells that only CS preferred is configurated
The rest cells that CS preferred configuration is
included
Cells that CS preferred is not configurated
R99 PS service Cells that only R99 PS preferred is configurated
The rest cells that R99 PS preferred configuration is
included
Cells that R99 PS preferred is not configurated
HS PS service Cells that only HS PS preferred is configurated
The rest cells that HS PS preferred configuration is
included
Cells that HS PS preferred is not configurated
CS + R99 PS services Cells that only CS and R99 PS preferred are
configurated
The rest cells that CS and R99 PS preferred
configuration are included
Cells that CS and R99 PS preferred are not
configurated
CS + HS PS services Cells that only CS and HS PS preferred are
configurated
The rest cells that CS and HS PS preferred
configuration are included
Cells that CS and HS PS preferred are not
configurated
(4) If the HCS function is introduced for cells, the cells should be sorted based on the
HCS priorities of target cells in the descending order in the sorting in step (3). (The
HCS priority ranges from 0 to 7. 0 is the lowest priority with relatively wide coverage,
while 7 is the highest priority with relatively small coverage). That is to say, sort the
listed cells based on the HCS properties in the precondition of meeting the prefer
property.

Based on the deletion and prefere nce sorting procedures on the listed target cells in the
above steps, select the first cell in the list as the target cell for access or handover.
When the type of a cell is R99+R5+R6 or R99+R5, and only HS PS preferred is

configurated, PS service is released first for R99 CS+PS service, CsHo4MulRabS wch is
used to controlled whether UE is handover to a cell which is overlap or co-located, R99
service available and not only HS PS preferred.
4.3 Service-based Multi-carrier Interoperation in Call

holding procedure
In handover, relocation from other system or RNC to local RNC, call re-establishment
triggered by CELL UP DA TE, state transition from non-CELL_DCH to CE LL_DCH, if
CallHoldLBS w is set to ON, the judgment of service-based multi-carrier interoperation in
call holding procedure is performed. Its handling proc edure is the same as that of the
service-based multi-carrier interoperation in RAB assignment.
5 Coupling of Load-based and Service-

based Multi-carrier Interoperations
Handover is not initiatively triggered but only cell reordering is performed when bot h the
load-based balance strategy and the service-based balance strategy are applied in the
initial access phase and the call reservation phase. Because the system load greatly
affects the system stability, the load-based balance strategy has a higher priority than
the service-based balance strategy, that is, load-based cell reordering is preferred to
service-based cell reordering. For example, first the cells are reordered in the sequence
from lower to higher loads according t o the "load-based multi-carrier interoperation"
strategy, and are classified into a low-load cell group and a high-load cell group. Then
the two groups of cells are reordered by the service category and the cell Prefer attribute
(PrefTrafType) according to the "service-based multi-carrier interoperation" strategy.
6 Inter-RAT Load Balance Strategy

The Inter-RA T load balance indicates that if the cell where the UE resides is overloaded
during RAB assignment, the UE will be assigned to 2G system through Inter-RA T
directed retry.
According to the 3GPP 25.413 regulations, the directed retry indicates that RNC fails to
reassign the CS service assigned by CN due to Directed ret ry, and RNC originates
immediat ely the relocation from 3G to 2G in CS d omain due to Directed retry, and then
the CS service assigned by CN is relocat ed to 2G system. Currently, the CS service
supported by 2G is mainly the AMR voice, Therefore, the directed retry refers to the
directed retry of AMR voice.

6.1 Directed Retry Triggered by Inter-RAT Balancing

When RNC receives the AMR service assignment message from CN, if the downlink
available load of the cell is less than its Int er-RA T threshold of load balancing
(DlP wrThdCs4G), or the uplink available interference of the cell is less than its Inter-RA T
threshold of load balancing (UlLdThdCs4G), and the UE supports 2G system and the
current cell has neighboring cells which are with Overlap or Covers(ShareCover)
relationship, the RNC will trigger the directed ret ry to try to hand over the service to 2G
neighboring cells.
6.2 Directed Retry Triggered by Admission Failure

When RNC receives the AMR service assignment message from CN, and is not
admitted by the cell (see ZTE UMTS Admission Control Feat ure Guide), if the UE
supports 2G system and the current cell has neighboring cells which are with Overlap
or Covers(S hareCover) relationship, RNC will trigger the directed retry to try to hand
over the service to 2G neighboring cells.
7 Configuration and Parameters
7.1 Parameter List

Abbreviated name Parameter name
InitRrcLBSw Load Balance Switch of Initial RRC Procedure
RabAssLBS w Load Balance Switch of RAB Assignment Procedure
CallHoldLBSw Load Balance Switch of Call holding procedureing Procedure
DlLdB alPwrSwch Load Balance Switch for Downlink Power
UlLdB alPwrSwch Load Balance Switch for Uplink Int erferenc e
LdBalCdS wch Load balance switch for code
LdBalHsSwch Load Balance switch for HS DPA throughput
DlLdB alPwrWeight Downlink Power weight for load balanc e
UlLdB alPwrWeight Uplink Interference Weight for Load Balanc e
LdBalCdWeight Code weight for load balance
DlLdB alHsWeight HSDPA Throughput weight for load balance
DlPwrThdCs UTRA N Downlink A vailable Load Balance Threshold (Power)
for CS
DlPwrThdCs4G Inter-System Downlink A vailable Load Balance Thres hold
(Power) for CS
DlPwrThdR99Ps UTRA N Downlink A vailable Load Balance Threshold (Power)
for R99 PS
DlPwrThdHsd UTRA N Downlink A vailable Load Balance Threshold (Power)
for HSDPA
ExtraCDeltaTrd Permitted Payload Difference Downlink A vailable Load
Thres hold in Inter-frequency Cells Power

Abbreviated name Parameter name

UlLdThdCs UTRA N Uplink A vailable Load Balance Threshold
(Interference) for CS
UlLdThdCs4G Inter-system Uplink A vailable Load Balance Threshold
(Interference) for CS
UlLdThdR99Ps UTRA N Uplink A vailable Load Balance Threshold
(Interference) for R99 PS
UlLdThdHse4U UTRA N Uplink A vailable Load Balance Threshold
(Interference) for HSUPA
ExtraCDeltaTru Permitted Payload Difference Uplink A vailable Load Thres hold
in Inter-frequency Cells-Interference
DlCdThdCs UTRA N Downlink A vailable Load Balance Threshold (Code) for
CS
DlCdThdR99Ps UTRA N Downlink A vailable Load Balance Threshold (Code) for
R99 PS
DlCdThdHsd UTRA N Downlink A vailable Load Balance Threshold (Code) for
HSDPA
ExtraCDeltaCdTrd Permitted Payload Difference Downlink A vailable Load
Thres hold in Inter-frequency Cells-Code
DlLdHs ThdHsd UTRA N Downlink A vailable HS DPA Load Balance Threshold

(HS DPA Throughput) for HS DPA
ExtraCDeltaHs Trd Permitted Payload Difference Downlink A vailable Load

Thres hold in Inter-frequency Cells-HS DPA throughput
InitRrcSBSw Service B alance S witch of Initial RRC Procedure
RabAssSBSw Service B alance S witch of RAB Assignment Proc edure

CallHoldSBS w Service B alance S witch of Call holding procedureing
Procedure
PrefTrafType Preferred Traffic Type
ShareCover Share Cover Indication (utranRelation)
GsmShareCover Share Cover Indication (gsmRelation)
HspaSptMeth(utranC HSPA Support Method(utranCell)
ell)
HspaSptMeth(extern HSPA Support Method(externalUt ranCell)
alUtranCell)
CsBalSwch CS Balance S witch of RAB Assignment Procedure
CsHo4MulRabSwch Switch of CS Handover for CS+PS in Multi-Carrier Scenario
7.2 Parameter Configuration
7.2.1 Load Balance Switch of Initial RRC Procedure
OMC Path

Path: View->Configuration Managem ent-> RNC NE-> RNC Radio Res ource
Management-> Utran Cell->Ut ran Cell XXX->Modify Advanced Paramet er->B alance
Information->Load Balanc e Switch of Initial RRC Procedure
Parameter Configuration
This parameter is a load balancing switch for RRC initial access.
7.2.2 Load Balance Switch of RAB Assignment Procedure
OMC Path
Path: View->Configuration Management-> RNC NE-> RNC Radio Res ource

Information->Load Balanc e Switch of RAB Assignment Procedu re
This parameter is a load balance switch which indicates whether the load balance
function is open for RAB assignment procedure.
7.2.3 Load Balance Switch of Call holding procedureing Procedure
OMC Path
Information-> Load Balance Switch of Call holding proc edureing Procedure
This parameter is a load balance switch which indicates whether load balanc e function is
open for call holding procedureing procedure. The application scenes include handover,
relocation, RAB re-establishment and FACH-> DCH.
7.2.4 Load balance switch for downlink power
OMC Path

Information-> Load Balance Switch for Downlink Power
This parameter is a switch indicating whether load balance based on downli nk power is
open or not.

7.2.5 Load Balance Switch for Uplink Interference
OMC Path

Information-> Load Balance Switch for Uplink Interference
This parameter is a switch indicating whet her load balance based on uplink interference
is open or not.
7.2.6 Load Balance Switch for Code
OMC Path

Information-> Load Balance Switch for Code
This parameter is a switch indicating whether load balance based on code resources is
open or not.
7.2.7 Load Balance Switch for HSDPA Throughput
OMC Path

Information-> Load Balance Switch for HSDPA Throughput
This parameter is a switch indicating whether load balance based on HS DPA throughput
per user is open or not.
7.2.8 Downlink Power Weight for Load Balance
OMC Path

Information-> Downlink Power Weight for Load Balance(%)

This parameter indicates the weight of downlink power res ourc es in several factors of
load balance. When evaluating the cell load, several factors such as code resources,
downlink power, uplink interference, and HS DPA throughput per user are taken into
account for load balance. The sum of each factors (whos e switch is open) weight is 1.
7.2.9 Uplink Interference Weight for Load Balance
OMC Path

Information-> Uplink Interference weight for Load Balance(% )
This parameter indicat es the weight of uplink interference in several factors of load
balance. When evaluating the cell load, several factors such as code resources,
7.2.10 Code Weight for Load Balance
OMC Path

Information-> Code weight for Load Balance(%)
This parameter indicates the weight of code resources in several factors of load balance.
When evaluating the cell load, several factors such as code resources, downlink power,
uplink interference, and HSDPA throughput per user are taken into account for load
balance. The sum of each factors (whose switch is open) weight is 1.
7.2.11 HSDPA Throughput Weight for Load Balance
OMC Path

Information-> HSDPA Throughput weight for Load Balance(%)
This parameter indicat es the weight of uplink interference in several factors of load
balance. When evaluating the cell load, se veral factors such as code resources,

7.2.12 UTRAN Downlink Available Load Balance Threshold (Power ) for CS
OMC Path

Information-> UTRA N Downlink A vailable Load Balance Threshold (Power) for CS(% )
This parameter indicates the downlink available Power load threshold of CS service for
load balance bet ween UTRAN cells. If the downlink available Power load of local
UTRA N cell is less than the threshold indicated by this parameter, the downlink load
balance judgment is performed and UE in local cell may be balanced to ot her UTRAN
cell.
7.2.13 Inter-System Downlink Available Load Balance Threshold (Power)

for CS
OMC Path

Information-> Inter-System Downlink A vailable Load Balance Threshold (Power) for
CS(%)
This parameter indicat es the downlink power available load threshold of CS service for
load balance between different RA T systems. If the downlink available load of the local
cell is less than the threshold indicat ed by this parameter, the downlink load balance
judgment is performed and UE of local cell may be balanc ed to other RA T systems.
7.2.14 UTRAN Downlink Available Load Balance Threshold (Power) for R99
PS
OMC Path

Information-> UTRA N Downlink Available Load Balance Threshold (Power) for R99
PS(%)
This parameter indicates the downlink power available load t hreshold of R99 PS service
for load balance bet ween UTRAN cells. If the downlink available load of local UTRAN
judgment is performed and UE in local cell may be balanced to other UTRA N cell.

7.2.15 UTRAN Downlink Available Load Balance Threshold (Power) for

HSDPA
OMC Path
Information-> UTRA N Downlink A vailable Load Balance Threshold (P ower) for HS DPA
(%)
This parameter indicates the downlink power available load threshold of HSDPA service
for load balance bet ween UTRAN cells. If the downlink available load of local UTRAN
judgment is performed and UE in local cell may be balanced to other UTRA N cell.
7.2.16 Permitted Payload Difference Downlink Available Load Threshold in

Inter-frequency Cells-Power
OMC Path

Information->Permmited P ayload Differenc e Downlink A vailable Load Threshold in Int er-
frequency Cells Power(% )
This parameter indicates the permitted downlink available TCP load differenc e threshold
between inter-frequency cells. It is used to evaluate the load of a cell.
7.2.17 UTRAN Uplink Available Load Balance Threshold (Interference ) for

CS
OMC Path

Information-> UTRA N Uplink A vailable Load Balance Threshold (Interference) for CS (%)
This parameter indicates the uplink available load threshold of CS service for load
balance between UTRA N cells. If the uplink available load of local UTRAN cell is less
than the threshold indicated by this parameter, the uplink load balance judgment is
performed and UE in local cell may be balanced to other UTRA N cell.

7.2.18 Inter-system Uplink Available Load Balance Threshold (Interference)

for CS
OMC Path

Information-> Inter-system Uplink A vailable Load Balance Thres hold (Interference) for
CS(%)
This parameter indicates the uplink available load threshold of CS service for load
balance bet ween different RA T systems. If the uplink available load local cell is less than
the threshold indicated by this parameter, performs the uplink load balance judgment
and UE of loc al cell may be balanced to ot her RA T systems.
7.2.19 UTRAN Uplink Available Load Balance Threshold (Interference) for

R99 PS
OMC Path

Information-> UTRA N Uplink Available Load Balance Threshold (Int erference) for R99
PS(%)
This parameter indicat es the uplink available load thres hold of R99 PS service for load
7.2.20 UTRAN Uplink Available Load Balance Threshold (Interference) for

HSUPA
OMC Path

Information-> UTRA N Uplink A vailable Load Balanc e Threshold (Interference) for
HSUPA (%)
This parameter indicates the uplink available load threshold of HS UPA service for load

7.2.21 Permitted Payload Difference Uplink Available Load Threshold in

Inter-frequency Cells-Interference
OMC Path

Information->Permmited Payload Difference Uplink A vailable Load Threshold in Int er-
frequency Cells-Interferenc e(%)
This parameter indicates the permitted uplink available RTWP load difference threshold
between inter-frequency cells. It is used to evaluate the load (Weight ) of a cell.
7.2.22 UTRAN Downlink Available Load Balance Threshold (Code) for CS
OMC Path

Information-> UTRA N Downlink A vailable Load Balance Threshold (Code) for CS(% )
This parameter indic ates the available channellization code load balance threshold of
CS service. If the downlink available channelliztion code usage ratio is less than the
threshold indicated by this parameter, the downlink load balance judgment is performed
and some UEs may be balanced to other UTRAN cell.
7.2.23 UTRAN Downlink Available Load Balance Threshold (Code) for R99
PS
OMC Path

Information-> UTRA N Downlink A vailable Load Balance Threshold (Code) for R99 PS(%)
This paramet er indicates the downlink available channellization c ode load balance
threshold of R99 PS service. If the local UTRAN cells downlink available channellization
code usage ratio is less than the threshold indicated by this parameter, the downlink
load balance judgment is performed and some UEs may be balanced to other UTRAN
cell.

7.2.24 UTRAN Downlink Available Load Balance Threshold (Code) for

HSDPA
OMC Path

Information-> UTRA N Downlink A vailable Load Balance Threshold (Code) for HS DPA (%)
This paramet er indicates the downlink available channellization c ode load balance
threshold of HSDPA service. If the local UTRAN cells downlink available channellization
code usage ratio is less than the threshold indicated by this parameter, the downlink
load balance judgment is performed and some UEs may be balanced to other UTRAN
cell.

Inter-frequency Cells-Code
OMC Path

frequency Cells-Code(%)
This parameter indicates the code resource available load difference threshold between
inter-frequency cells. It is used to evaluate the load(Weight) of a cell.
7.2.26 UTRAN Downlink Available HSDPA Load Balance Threshold (HSDPA

Throughput) for HSDPA
OMC Path

Information-> UTRA N Downlink Available Load Balance Threshold (HS DPA Throughput)
for HSDPA (% )
This parameter indicat es the downlink available HS DPA throughput threshold for load
balance between UTRAN cells. If the downlink available HS DPA throughput of local
UTRA N cell is less than the threshold indicated by this parameter, the downlink load
balance judgment is performed and UE in local cell may be balanced to ot her UTRAN
cell.


Inter-frequency Cells-HSDPA Throughput
OMC Path

frequency Cells-HS DPA Throughput(%)
This parameter indicates the HSDPA throughput available load difference threshold
between inter-frequency cells. It is used to evaluate the load(Weight) of a cell.
7.2.28 Service Balance Switch of Initial RRC Procedure
OMC Path

Information->Service Balance S witch of Initial RRC Procedure
This parameter is a service balance s witch which indicates whether the RRC service
balance function is open for initial RRC procedure used for accessing.
7.2.29 Service Balance Switch of RAB Assignment Procedure
OMC Path

Information->Service Balance S witch of RAB Assignment Procedure
This parameter is a load balance switch which indicates whether the load service
function is open for RAB assignment procedure.
7.2.30 Service Balance Switch of Call holding procedureing Procedure
OMC Path

Information->Service Balance S witch of Call holding procedureing Procedure

This parameter is a load balance switch which indicates whether load balanc e function is
open for call holding procedureing procedure. The application scenes are including
handover, relocation, RAB re-establishment and FACH-> DCH.
7.2.31 Preferred Traffic Type
OMC Path
Management-> Utran Cell->Ut ran Cell XXX->Modify Advanced Parameter->Ultran Cell-
>Preferred Traffic Type
This parameter indicates which traffic type is preferred in the cell. CS service will be
accessed the cell with attribute of CS Preferred , and PS Service will be accessed the
cell with attribute of PS Preferred, and CS+PS service will be accessed the cell with
attribute of CS+PS Preferred.
7.2.32 Share Cover Indication (utranRelation)
OMC Path

Management-> Utran Cell-> Utran Cell XXX-> Neighboring Cell->Neighboring Cell XXX-
>Modify Advanced Parameter-> Share Cover Indication
This parameter describes the location of the serving cell and neighboring cell.
7.2.33 Share Cover Indication (gsmRelation)
OMC Path
Path: View-> Configuration Management ->RNC NE-> RNC Radio Res ource
Management-> Utran Cell-> Utran Cell XXX->GSM Neighbouring Cell->GSM
Neighbouring Cell XXX->Modify Advanc ed Paramet er-> Share Cover Indication
This parameter describes the location of the serving cell and Gsm neighboring cell.
7.2.34 HSPA Support Method(utranCell)
OMC Path


Management-> Utran Cell-> Utran Cell XXX->Cell Ability and Cell Reselection-> HSPA
Support Method
This parameter indicates the support of HSPA in the cell.
7.2.35 HSPA Support Method(externalUtranCell)
OMC Path

Management->External Utran Cell->External Utran Cell XXX-> Global Other Parameters
-> HSPA Support Method
This parameter indicates the support of HSPA in the cell.
7.2.36 CS Balance Switch of RAB Assignment Procedure
OMC Path
Path: View->Configuration Management->RNC NE ->RNC Radio Resource

Management-> Utran Cell-> Utran Cell XXX->Modify Advanced Parameter->Balance
Information-> CS Balance Switch of RAB Assignment Procedure
This parameter is a CS balance switch which indicates whether the balanc e function is
open for CS service during RAB assignment procedure.
7.2.37 Switch of CS Handover for CS+PS in Multi-Carrier Scenario
OMC Path

Information->Switch of CS Handover for CS+PS in Multi-Carrier Scenario
This parameter is used in the following scenario: For multi-RAB service, PS service is
released and only R99 CS servic e remains, if the cell is R5+R6+ R99 or R5+ R99 and
only HS PS is preferred traffic, UE will be balanced to a cell with shared coverage
relation, R99 service available and not only HS PS preferred when the parameter value
is open.

8 Counter And Alarm
8.1 Counter List

This feat ure has no relative counter.
8.2 Alarm List

This feat ure has no relative alarm.
9 Glossary
CS Circuit switched
HCS Hierarchical Cell Structure
HSDPA High speed downlink packet access
HSUPA High speed uplink packet access
PS Packet switched
RAB Radio access bearer
RNC Radio net work controller
RRC Radio res ource control
RSCP Received Signal Code Power
RTWP Received total wide band power
SF Spreading Factor
UE User equipment
UMTS Universal mobile telecommunication system

ZTE UMTS Load Balance Feature Guide U9.2

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

ZTE UMTS Load Balance Feature Guide U9.2

Caricato da

Copyright:

Formati disponibili

Operator Logo

Load Balance Feature Guide

Version Date Author Approved By Remarks

2010 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary 2010 ZTE Corporation. All rights reserved. I

1 Function Attribute ...............................................................................................1

3 Load-based Multi-carrier Interoperation .............................................................2

4 Service-based Multi-carrier Interoperation .........................................................9

5 Coupling of Load-ba sed and Service-based Multi-carrier Interoperations........13

6 Inter-RAT Load Balance Strategy......................................................................13

7 Configuration and Parameters..........................................................................14

ZTE Confidential Proprietary 2010 ZTE Corporation. All rights reserved. II

7.2.16 Permitted Payload Differenc e Downlink A vailable Load Threshold in Int er -

8 Counter And Alarm ...........................................................................................27

ZTE Confidential Proprietary 2010 ZTE Corporation. All rights reserved. IV

Attribute: Mandatory function

2.1 Overview of the Functions

2.1.1 Load Balancing

Load balancing includes the intra-system load balancing (load-based multi-carrier

2.1.2 Frequency Priority

ZTE Confidential Proprietary 2010 ZTE Corporation. All rights reserved. 1

2.1.3 Load Balance for HSDPA Service

2.1.4 Directed Retry Between HS-DSCH and DCH

2.1.5 Load Balance for HSUPA Service

2.1.6 Directed Retry Between HS-DSCH and DCH

3 Load-based Multi-carrier Interoperation

Initial RRC procedure: involving Initial RRC procedure.

RAB assignment: involving RAB assignment.

ZTE Confidential Proprietary 2010 ZTE Corporation. All rights reserved. 2

Principles of target cell selection in load-based multi-carrier interoperation:

3.1 Load Evaluating Factors

3.1.1 Uplink interference

The uplink interference is measured by the uplink payload:

Load generated by uplink DCH + Load generated by non-scheduling E-DCH can be

Define uplink available intereference as:

Uplink available intereference(A vailableLoad 1 )=100%-uplink payload(UlRtwpEffLoad)

ZTE Confidential Proprietary 2010 ZTE Corporation. All rights reserved. 3

3.1.2 Downlink power

The downlink power is measured by the downlink payload:

HSDSCHRequiredPoweri It indicates the HS-DSCH Required Power of the

Define downlink available power as:

Downlink available power(A vailableLoad2)=100%-downlink payload

3.1.3 Code resources

By using load measuring method of the downlink channelization code resources,

The code load is measured by the channel code usage:

Code Usage=(number of Non HS-P DSCH occupied SF128+MinHspdschNum*8)/128

ZTE Confidential Proprietary 2010 ZTE Corporation. All rights reserved. 4

MinHspdschNum = Max(MinHspdschNum in OMCR, MinHspdschNumbyGB R). See

Define downlink available code resource as:

Downlink available code resource (A vailableLoad 3)=100%-code usage

3.1.4 HSDPA throughput per user

HsOcuCodeNum=min{ (128-number of SF128 occupied by non-HSPDSCH )/8 ,MaxNumofHspdsch}

MaxNumofHspdsch is the maximum number of HSP DSCH channels configured in

NumOfHsdpaUs er is the number of HSDPA on-line users in cell.

MaxCapHs User is the maximum value of HS DPA throughput per user.

ZTE Confidential Proprietary 2010 ZTE Corporation. All rights reserved. 5

3.1.5 Coupling Operation Between These Factors

The meanings of the parameters are as follows:

AvailableLoad, the available load of estimated cell

AvailableThrdLoad, the available load balancing threshold configured by OMC.

Delta indicates the load balancing threshold difference (corresponds to ExtraCDeltaTrd,

ZTE Confidential Proprietary 2010 ZTE Corporation. All rights reserved. 6

3.2 Load-based Multi-carrier Interoperation in Initial

3.3 Load-based Multi-carrier Interoperation in RAB