ZTE UMTS Service-Based Handover Feature Guide

Service-Based Handover
Feature Guide
Version Date Author Reviewer Notes
V1.00 2014/03/12 Feng Hong Ma Yongchao First edition
© 2014 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary 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 1

TABLE OF CONTENTS
1 Feature Attribute ............................................................................................... 4
2 Overview ............................................................................................................ 4
2.1 Feature Introduction ............................................................................................. 4
2.1.1 ZWF21-05-022 Service-Based Handover ............................................................ 4
2.2 License Control .................................................................................................... 6
2.3 Correlation with Other Features ........................................................................... 6
3 Technical Description ....................................................................................... 6

3.1 ZWF21-05-022 Service-Based Handover ............................................................ 6
3.1.1 Principle of Confirming the Attribute “Service Handover” ...................................... 7
3.1.2 Service-Based Handover Strategy ..................................................................... 10
4 Parameters....................................................................................................... 13
5 Related Counters and Alarms ........................................................................ 20

5.1 Related Counters ............................................................................................... 20
5.2 Related Alarms .................................................................................................. 21
6 Engineering Guide .......................................................................................... 21

6.1 Application Scenario .......................................................................................... 21
6.2 Feature Activation Procedure ............................................................................. 21
6.3 Feature Validation Procedure............................................................................. 23
6.4 Feature Deactivation Procedure......................................................................... 24
6.5 Impact on the Network ....................................................................................... 25
7 Abbreviation .................................................................................................... 25
8 Reference Document....................................................................................... 26

FIGURES
Figure 6-1 Parameter Configuration Window 1 ..................................................................22

TABLES
Table 2-1 License Control List ............................................................................................ 6

Table 3-1 Control Parameters that srvHoInd is Configured for the Respective Services ..... 8
Table 3-2 Control Parameters that “service handover by RNC” is Configured for the
Respective Services .............................................................................................................. 9
Table 4-1 Parameter List ...................................................................................................13
Table 5-1 Counter List .......................................................................................................20
Table 6-1 Feature Validation Procedure.............................................................................23
Table 6-2 RNC Parameter List 2 ........................................................................................24

1 Feature Attribute
RNC version: [ZXWR RNC V3.13.10.15/ZXUR 9000 V4.13.10.15]
Node B version: [ZXSDR V4.13.10.20]
Attribute: [Optional]
Involved NEs:
NE Name Related or Not Special Requirement
UE √ -
Node B √ -
RNC √ -
MSC - -
MGW - -
SGSN - -
GGSN - -
HLR - -
“√”: involved
“-”: not involved
2 Overview
2.1 Feature Introduction
2.1.1 ZWF21-05-022 Service-Based Handover
This feature determines whether to hand over and when to hand over services to a GSM
network according to the attribute “service handover” in the RAB assignment message:
 Handover to GSM should be performed: It means that it is necessary to hand

over the service to a GSM network as soon as possible after the service is set
up successfully.

 Handover to GSM should not be performed: It means that the service has to be
handed over to a GSM network when the UMTS network cannot carry the
service. The RNC will trigger inter-RAT handover when the quality of the
UMTS network degrades.
 Handover to GSM shall not be performed: It means that this kind of service
cannot be handed over to a GSM network or handover to a GSM network
cannot be triggered.
Regarding concurrent services, the RAN network can combine the attribute “service
handover” of multiple services based on the priority of the attribute “service handover”
configured through the OMC. For example, one operator wants CS voice services to be
carried in the GSM network and PS services kept in the WCDMA network as long as
possible. The attribute “service handover” for CS voice services is set to “Handover to
GSM should be performed”, and the attribute “service handover” for PS services is set to
“Handover to GSM should not be performed”. Meanwhile, the priority of “Handover to
GSM should not be performed” is higher than “Handover to GSM should be performed”.
When one UE has both CS voice service and PS services, the WCDMA network is still
selected to provide both CS and PS services for the user in order to guarantee PS
service experience. The CS voice service cannot be handed over to the GSM network
until PS services are released.
Basically, the load of GSM cells is high in some hot spots. If service-based handover is
enabled and the load of GSM cells is not considered, it brings more load to GSM cells. To
avoid this, a configurable switch per cell is provided to disable service-based handover.
When the switch is set to “Off”, the attribute “service handover” is not checked by RAN.
After introduction of LTE, information element of “E-UTRAN Service Handover” in RAB

assignment message is also introduced to indicate whether a UE could be handed over
to LTE. ZTE RAN can obey the indication in the information element from CN.
Handover strategies based on services actually need to be configured in CN.

2.2 License Control
Table 2-1 License Control List
License Configured
Feature ID Feature Name Unit
Control Item NE
Service-Based Service-Base
ZWF21-05-022 RNC RNC
Handover d Handover
2.3 Correlation with Other Features
1. Required Features
ZWF21-03-004 Inter-RAT Mobility
ZWF21-03-110 Handover with LTE
2. Mutually Exclusive Features
None
3. Affected Features
None
3 Technical Description
3.1 ZWF21-05-022 Service-Based Handover
This feature is controlled by the switch of ULogicalRnc.srvBasedHoInd in the RNC level

and switch of UCelInfoFDD.ServHoSwch in the cell level. This feature is enabled only
when the two switches are set to “On”.

3.1.1 Principle of Confirming the Attribute “Service Handover”
Service-based handover determines whether to hand over and when to hand over
service to GSM or E-UTRAN according to the attribute “service handover” or “E-UTRAN
service handover”. As the strategies for the handover from UMTS to GSM is different
from the handover from UMTS to E-UTRAN, they are described separately as follows.
Firstly, define the following variables to avoid confusing the attribute “service handover”
given by each network element:
“Service handover by CN”: means the service handover/E-UTRAN service handover IE

in the RAB ASSIGNMENT REQUEST message sent by the CN.
“Service handover by RNC”: means the service handover configured in OMC by the
RNC.
“Service handover for used”: means the final service handover used for service-based
handover according to the control strategy of RNC.
3.1.1.1 UMTS > GSM
The 3GPP protocol defines a service handover IE in the IU interface for GSM, which
indicates which handover the UMTS RNC should perform.
“Service handover by CN” has three kinds of values:
 Handover to GSM should be performed: It means that it is necessary to hand over

the service to a GSM network as soon as possible after the service is set up
successfully.
 Handover to GSM should not be performed: It means that the service has to be
handed over to a GSM network when UMTS cannot carry the service, and the RNC
will trigger an inter-RAT handover when UMTS quality degrades.
 Handover to GSM shall not be performed: It means that this kind of service cannot
be handed over to a GSM network or handover to a GSM network cannot be
triggered.

Generally, the RNC performs the handover according to “service handover by CN”. But
there are some limitations if the RNC performs the handover only according to “service
handover by CN” in some special situations. In order to make operators apply
service-based handover more flexibility, ZTE introduces a control strategy about service
handover at the RNC side.
The strategy to determine the attribute “service handover for used” controlled by the RNC
is described as follows:
The RNC determines “service handover for used” according to “service handover by CN”
or “service handover by RNC” which is indicated by srvHoInd.
 If srvHoInd is “0: Ignore service handover IE”, “service handover for used” is equal
to “service handover by RNC”.
 If srvHoInd is “1: Apply service handover IE”, “service handover for used” is equal to
“service handover by CN”.
There is one special situation, however, in which “service handover by CN” is not carried
in the RAB ASSIGNMENT REQUEST message sent by the CN. Then, “service handover
for used” is equal to “service handover by RNC” no matter what srvHoInd is.
Where:
As different services have different requirements for the inter-RAT handover, srvHoInd
can be configured for different services respectively and obtained from the parameters
listed in Table 3-1 for the AMR, CS 64K, PS RT, and PS NRT service respectively.
“Service handover by RNC” is also configured for different services respectively and
obtained from the parameters listed in Table 3-2 for the AMR, CS 64K, PS RT, and PS
NRT service respectively. That is, each service among the AMR, CS 64K, PS RT, and
PS NRT service can get a suitable “service handover for used” for its own based on the
above control strategy.
Table 3-1 Control Parameters that srvHoInd is Configured for the Respective Services
GUI Name srvHoInd

Service Handover Strategy Indicator (AMR) USrvBasedHo.srvHoIndAmr

GUI Name srvHoInd
Service Handover Strategy Indicator (CS

USrvBasedHo.srvHoIndCs64
64K)
Service Handover Strategy Indicator (PS

USrvBasedHo.srvHoIndPsRT
RT)
Service Handover Strategy Indicator (PS

USrvBasedHo.srvHoIndPsNRT
NRT)
Table 3-2 Control Parameters that “service handover by RNC” is Configured for the
Respective Services
GUI Name service handover by RNC
Service Handover Strategy of RNC for AMR USrvBasedHo.amrSrvHoStra
Service Handover Strategy of RNC for CS64 USrvBasedHo.cs64SrvHoStra
Service Handover Strategy of RNC for PS

USrvBasedHo.psRtSrvHoStra
RT Service
Service Handover Strategy of RNC for PS

USrvBasedHo.psNrtSrvHoStra
NRT Service
Because each service can get a suitable “service handover for used” for its own and
UMTS allows a UE to have multi-RAB, the strategy of combining “service handover for
used” for multi-RAB is needed, which is described as follows:
 First, the RNC gets the “service handover for usedi” of each service, where, i=1,…,n,
and n is the number of concurrent services.
 Second, the “service handover for usedi” which has the highest priority is regarded
as the combined “service handover for used”. Where, the priority of service
handover is indicated by USrvBasedHo.srvHoComStra.
The following is an example for understanding the strategy mentioned above:
If the parameter of USrvBasedHo.srvHoComStra is set to “2: Priority should not be

performed>should be performed>shall not be performed”.
The UE has concurrent services of an AMR and a PS NRT, “service handover for used”
of the AMR service is “Handover to GSM should be performed”, “service handover for
used” of the PS NRT service is “Handover to GSM should not be performed”.

The final “service handover for used” for this UE is “Handover to GSM should not be
performed” after combining based on the priority.
3.1.1.2 UMTS > E-UTRAN
The 3GPP protocol defines a service handover IE in the IU interface for E-UTRAN, which
indicates which handover the UMTS RNC should perform.
“Service handover by CN” only has one value:
 Handover to E-UTRAN shall not be performed: It means that this kind of service
cannot be handed over to E-UTRAN or handover to E-UTRAN cannot be
triggered.
Considering the particularity of this scene, the value of “service handover for used” for
E-UTRAN is obtained according to the CN’s instruction. The RNC has no control strategy.
The “service handover for used” is equal to “service handover by CN”. If the “service
handover by CN” is not obtained from the CN, which means the handover from UMTS to
E-UTRAN of this service is not restricted by the CN, the RNC can start an E-UTRAN
inter-RAT measurement based on UMTS coverage, and perform a handover procedure
according to the reported results. (For details, refer to ZTE UMTS Handover with LTE
Feature Guide.)
The strategy of combining “service handover for used” for concurrent services:
For concurrent PS services, if the “service handover for used” of one service among the
concurrent services is “Handover to E-UTRAN shall not be performed”, the final “service
handover for used” for this UE is “Handover to E-UTRAN shall not be performed”.
3.1.2 Service-Based Handover Strategy
The strategies of service-based handover for UMTS > GSM and UMTS > E-UTRAN are
different, so they are described by chapter as follows.

3.1.2.1 UTRAN > GSM
Service-based handover is performed according to the following principles after “service

handover for used” is determined.
 If the “service handover for used” is “Handover to GSM should be performed” or “0:
should be performed”
It indicates that the RAB should be handed over to GSM as soon as possible. For
such a service, after the service setup or intra-system handover is successful, if the
serving cell of the UE has a GSM neighboring cell and the inter-frequency
measurement for the UE is not enabled, the RNC enables the inter-RAT
measurement for GSM immediately, and then performs a handover procedure
based on the reported results.
 If the “service handover for used” is “Handover to GSM should not be performed” or
“1: should not be performed”
It indicates that the RAB can be handed over to GSM only when it exceeds the
bearing capability of UMTS. For such a service, the RNC enables the inter-RAT
measurement only when the quality of UMTS is poor. The specific scenarios are
described as follows:
 The current working carrier is in poor quality, but the conditions for enabling
inter-frequency measurements (that is, the inter-frequency neighboring cell is
not configured) or for the inter-frequency blind handover are not met. In this
case, if the inter-RAT measurement is not enabled or the conditions for the
inter-RAT blind handover are met but the blind handover fails, an inter-RAT
measurement is set up.
 The inter-frequency measurement is enabled and all non-working carriers

trigger 2E events. In this case, if the conditions for the inter-RAT blind
handover are not met and inter-RAT neighboring cells exist, or the conditions
for the inter-RAT blind handover are met, but the blind handover fails, the
inter-frequency measurement is disabled, and an inter-RAT measurement is
set up.

 If the “service handover for used” is “Handover to GSM shall not be performed” or “2:
shall not be performed”
It indicates that the RAB cannot be handed over to GSM. For such a service, the
RNC does not enable the inter-RAT measurement or trigger a handover to GSM.
For details about the strategy of UMTS > GSM inter-RAT measurement and handover,
refer to ZTE UMTS Handover Control Feature Guide.
3.1.2.2 UTRAN > E-UTRAN
Service-based handover is performed according to the following principle after “service

handover for used” is determined.
 If the “service handover for used” is “Handover to E-UTRAN shall not be performed”
It indicates that the RAB cannot be handed over to E-UTRAN. For such a service,
the RNC does not enable the inter-RAT measurement or trigger a handover to
E-UTRAN.
Otherwise, the RNC can start an E-UTRAN inter-RAT measurement based on

UMTS coverage, and perform a handover procedure according to the reported
results.
3.1.2.3 Coupling Strategy for UTRAN > GSM and UTRAN > E-UTRAN
For a PS service can be handed over to GSM or E-UTRAN based on service handover,
when both of them are permitted, the RNC chooses a system according to the principle
as follows:
 If the “service handover for used” for GSM is “Handover to GSM should be
performed” or “0: should be performed”, the handover from UMTS to GSM is
selected preferentially.
 If the “service handover for used” for GSM is “Handover to GSM should not be
performed” or “1: should not be performed”, and “service handover by CN” for
E-UTRAN is not obtained from the CN, the preferred system for the inter-RAT

handover is determined by the selection strategy of multi-RAT handover. For details

about the selection strategy, refer to ZTE UMTS Handover with LTE Feature Guide.
4 Parameters
Table 4-1 Parameter List
Recomme
Paramet Value Default
GUI Name Parameter Description Unit nded
er Name Range Value
Value
Service-Bas 0: Not
ULogicalR This parameter indicates 0: Not
ed Handover Supported 1:
nc.srvBas whether an RNC supports N/A Support
Support 1: Supported
edHoInd a service-based handover. ed
Indicator Supported
This parameter indicates

whether a service
handover is allowed or not.
If the "service handover" is
included in RAB
UCelInfoF Service
assignment request, and 0: Off
DD.ServH Handover N/A 1: On 1: On
the switch is "On", the 1: On
oSwch Switch
RNC will process the field
based on the value of
"service handover",
otherwise the RNC will
ignore the field.

0: Ignore
the AMR service handover
service
policy controlled by the
handover
RNC. 1:
IE for 1: Apply
Service If the bit is set to 0, the Apply
AMR service
USrvBase Handover RNC will ignore "service service
service handover
dHo.srvHo Strategy handover IE" in the N/A handov
1: Apply IE for
IndAmr Indicator requested RAB, and er IE for
service AMR
(AMR) perform a corresponding AMR
handover service
policy based on the service service
IE for
property value defined by
AMR
the RNC.
service
If the bit is set to 1, and

Recomme
er Name Range Value
Value
"service handover IE" is
not included in the
requested RAB, the RNC
will also perform a policy
based on the service
the RNC. Otherwise the
RNC will perform a policy
"service handover IE"
included in the requested
RAB.

the CS64 service handover
RNC.
If the bit is set to 0, the
RNC will ignore "service
handover IE" in the
0: Ignore
requested RAB, and
service
perform a corresponding
handover
policy based on the service 1:
IE for 1: Apply
Service property value defined by Apply
CS64 service
USrvBase Handover the RNC. service
service handover
dHo.srvHo Strategy If the bit is set to 1, and N/A handov
1: Apply IE for
IndCs64 Indicator "service handover IE" is er IE for
service CS64
(CS 64K) not included in the CS64
handover service
requested RAB, the RNC service
IE for
CS64
service
RAB.

Recomme
er Name Range Value
Value

the PS RT service
handover policy controlled
by the RNC.
If the bit is set to 0, the
RNC will ignore "service
handover IE" in the
requested RAB, and
0: Ignore
perform a corresponding
service
policy based on the service 1:
handover
Service property value defined by Apply 1: Apply
IE for PS
USrvBase Handover the RNC. service service
RT service
dHo.srvHo Strategy If the bit is set to 1, and N/A handov handover
1: Apply
IndPsRT Indicator "service handover IE" is er IE for IE for PS
service
(PS RT) not included in the PS RT RT service
handover
requested RAB, the RNC service
IE for PS
RT service
RAB.

0: Ignore
the PS NRT service
service
handover 1:
by the RNC.
IE for PS Apply 1: Apply
Service If the bit is set to 0, the
NRT service service
USrvBase Handover RNC will ignore "service
service handov handover
dHo.srvHo Strategy handover IE" in the N/A
1: Apply er IE for IE for PS
IndPsNRT Indicator requested RAB, and
service PS NRT
(PS NRT) perform a corresponding
handover NRT service
policy based on the service
IE for PS service
NRT
the RNC.
service
If the bit is set to 1, and

Recomme
er Name Range Value
Value
"service handover IE" is
not included in the
RAB.

the AMR service handover
RNC. If srvHoIndAmr is set
to “Ignore service
handover IE”, the RNC will
ignore "service handover
IE" in the requested RAB, 0: should
and perform a be
Service corresponding policy performed
should
USrvBase Handover based on AmrServHoStra. 1: should should not
not be
dHo.amrSr Strategy of If srvHoIndAmr is set to not be N/A be
perform
vHoStra RNC for “Apply service handover performed performed
ed
AMR IE” and "service handover 2: shall not
IE" is not included in the be
requested RAB, the RNC performed
based on AmrServHoStra.
Otherwise the RNC will
perform a policy based on
the value of "service
handover IE" included in
the requested RAB.
Service This parameter indicates 0: should should

USrvBase should not
Handover the CS64 service handover be N/A not be
dHo.cs64S be
Strategy of policy controlled by the performed perform

Recomme
er Name Range Value
Value
rvHoStra RNC for RNC. If srvHoIndCs64 is 1: should ed performed
CS64 set to “Ignore service not be
handover IE”, the RNC will performed
ignore "service handover 2: shall not
IE" in the requested RAB, be
and perform a performed
corresponding policy
based on
Cs64ServHoStra. If
srvHoIndCs64 is set to
“Apply service handover
IE” and "service handover
IE" is not included in the
based on
Cs64ServHoStra.
the requested RAB.

the PS RT service
by the RNC. If
0: should
srvHoIndPsRT is set to
be
“Ignore service handover
Service performed
IE”, the RNC will ignore should
USrvBase Handover 1: should should not
"service handover IE" in not be
dHo.psRtS Strategy of not be N/A be
the requested RAB, and perform
rvHoStra RNC for PS performed performed
perform a corresponding ed
RT Service 2: shall not
policy based on
be
R99RtServHoStra. If
performed
srvHoIndPsRT is set to
“Apply service handover
IE” and "service handover
IE" is not included in the

Recomme
er Name Range Value
Value
based on
R99RtServHoStra.
the requested RAB.

the PS NRT service
by the RNC. If
srvHoIndPsNRT is set to
“Ignore service handover
IE”, the RNC will ignore
"service handover IE" in
the requested RAB, and 0: should
perform a corresponding be
Service policy based on performed
should
USrvBase Handover PsNrtServHoStra. If 1: should should not
not be
dHo.psNrt Strategy of srvHoIndPsNRT is set to not be N/A be
perform
SrvHoStra RNC for PS “Apply service handover performed performed
ed
NRT Service IE” and "service handover 2: shall not
IE" is not included in the be
requested RAB, the RNC performed
based on
PsNrtServHoStra.
the requested RAB.
This parameter indicates 0: Priority 0: 0: Priority

USrvBase Service
the service handover should be Priority should be
dHo.srvHo Handover N/A
combination criteria in performed should performed
ComStra Combination
multi-RAB. The RNC will >should be >should

Recomme
er Name Range Value
Value
Strategy perform related processes not be perform not be
based on the highest performed ed>sho performed
priority value of "service >shall not uld not >shall not
handover IE". be be be
performed perform performed
1: Priority ed>sha
should be ll not be
performed perform
>shall not ed
be
performed
>should
not be
performed
2: Priority
should not
be
performed
>should
be
performed
>shall not
be
performed
3: Priority
should not
be
performed
>shall not
be
performed
>should
be
performed
4: Priority
shall not
be
performed

Recomme
er Name Range Value
Value
>should
be
performed
>should
not be
performed
5: Priority
shall not
be
performed
>should
not be
performed
>should
be
performed
5 Related Counters and Alarms
5.1 Related Counters
Table 5-1 Counter List
Counter ID Name
Number of attempted outgoing CS inter-RAT handovers, due

C310353205
to CN required
Number of successful outgoing CS inter-RAT handovers, due

C310353213
to CN required
Number of attempted outgoing PS inter-RAT handovers, due

C310353221
to CN required
Number of successful outgoing PS inter-RAT handovers, due

C310353229
to CN required

Number of attempted relocation preparation for outgoing PS

C312106776
inter-RAT handovers(Utran to EUtran)
Cell Inter-RAT CS Outgoing Handover Success
300476
Rate(WCDMA->GSM)
Cell Inter-RAT PS Outgoing Handover Success

300478
Rate(WCDMA->GPRS)
5.2 Related Alarms
This feature has no related alarm.
6 Engineering Guide
6.1 Application Scenario
In an actual network, if the network load, service distribution and requirements of users
with different priorities need to be considered, the operator may apply different handover
strategies for different service types. In this case, it is recommended to enable this
feature, to balance the service distribution among networks and improve the distribution
of network load.
6.2 Feature Activation Procedure
This procedure describes how to locate the parameters related to this feature in the GUI.
The parameter values on the screenshots in the procedure are for reference only. Refer
to Chapter 4 for the recommended values of the related parameters. In the configuration
resource tree, select Modify Area > Managed Element > UMTS Logical Function
Configuration and set Service-Based Handover Support Indicator, see the following
figure.

Figure 6-1 Parameter Configuration Window 1
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > UTRAN Cell > Extended Info of UTRAN Cell .Set
Service Handover Switch and Choice Strategy in Multi-RAT Handover, see the
following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > PLMN Relating Configuration > Handover

Configuration Based on Service. Set Service Handover Combination Strategy,

Service Handover Strategy Indicator (AMR), Service Handover Strategy Indicator
(CS 64K), Service Handover Strategy Indicator (PS RT), Service Handover Strategy
Indicator (PS NRT), Service Handover Strategy of RNC for AMR, Service Handover
Strategy of RNC for CS64, Service Handover Strategy of RNC for PS RT Service,
and Service Handover Strategy of RNC for PS NRT Service, see the following figure.
6.3 Feature Validation Procedure
Table 6-1 Feature Validation Procedure
Test Item Service-Based Handover
1. WCDMA and GSM systems are ready.

2. UMTS 2100M Cell 1 supports HSUPA, HSDPA, and DCH. It belongs
to RNC 1/NodeB 1. GSM Cell2 belongs to BSC 1/BTS 1.
Prerequisi
3. Cell 1 and Cell 2 are adjacent cells with different coverage.
te
4. Dual-mode UE 1 camps on Cell 1 in Idle mode.
5. UE 1 supports R99 and subscribes interactive or background service,
MBR = UL2 Mbps/ DL2 Mbps.

Test Item Service-Based Handover
1. Set service handoverto Handover to GSM should be performed.

2. UE 1 activates a PS call in Cell 1 and starts data transferring. After
service setup, the RNC enables compressed mode of Inter-RAT
measurement immediately.
3. UE 1 moves to Cell 2 to trigger event 3A/3C and performs the
inter-RAT handover to Cell 2.
4. Deactivate the PDP.
5. Set service handover to Handover to GSM should not be
performed.
Steps 6. UE 1 activates a PS call in Cell 1 and starts data transferring.
7. UE 1 moves from Cell 1 to Cell 2 to trigger event 2D and activate the
compressed mode. UE 1 moves further to Cell 2 to trigger event
3A/3C and performs the inter-RAT handover to Cell 2.
9. Set service handover to Handover to GSM shall not be
performed.
10. UE 1 activates a PS call in Cell 1 and starts data transferring.
11. UE 1 moves from Cell 1 to Cell 2 and doesn’t trigger handover.
Expected 1. With different value of “service handover”, UE 1’s performance is

Result different.
6.4 Feature Deactivation Procedure
Table 6-2 RNC Parameter List 2
Deactivation
No GUI Name Default Value
Value
Service-Based Handover Support

1 0: Not Supported 0: Not Supported
Indicator
For the description and configuration of these parameters, refer to Section 6.2 Feature
Activation Procedure.

6.5 Impact on the Network
The advantages of this feature:
The strategy of UMTS > GSM/E-UTRAN handover based on service handover can be
determined according to the configuration of CN or the control strategy of RNC, which is
convenient for operators to control the service distribution among networks according to
the network load and users’ priority.
The disadvantages of this feature:
None
7 Abbreviation
Abbreviation Full Name
AMR Adaptive Multi-Rate
CN Core Network
CS Circuit Switched
E-UTRAN Evolved UTRAN
GSM Global System for Mobile communication
LTE Long Term Evolution
OMC Operations & Maintenance Center
NRT Non-Real Time
PS Packet Switched
RAB Radio Access Bearer
RAN Radio Access Network
RNC Radio Network Controller
RT Real Time
UE User Equipment
UMTS Universal Mobile Telecommunications System
UTRAN UMTS Terrestrial radio access network
WCDMA Wideband CDMA, Code Division Multiple Access

8 Reference Document
[1] ZXUR 9000 UMTS (V4.13.10.15) Radio Network Controller Radio Parameter
Reference
[2] ZXWR RNC (V3.13.10.15) Radio Network Controller Radio Parameter Reference
[3] ZXUR 9000 UMTS (V4.13.10.15) Radio Network Controller Performance Counter
Reference
[4] ZXWR RNC (V3.13.10.15) Radio Network Controller Performance Counter

Reference
[5] ZTE UMTS Handover Control Feature Guide
[6] ZTE UMTS Handover with LTE Feature Guide

ZTE UMTS Service-Based Handover Feature Guide

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

ZTE UMTS Service-Based Handover Feature Guide

Diunggah oleh

Hak Cipta:

Format Tersedia

Service-Based Handover

V1.00 2014/03/12 Feng Hong Ma Yongchao First edition

© 2014 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary 1

1 Feature Attribute ............................................................................................... 4

3 Technical Description ....................................................................................... 6

5 Related Counters and Alarms ........................................................................ 20

6 Engineering Guide .......................................................................................... 21

ZTE Confidential Proprietary 2

Figure 6-1 Parameter Configuration Window 1 ..................................................................22

Table 2-1 License Control List ............................................................................................ 6

ZTE Confidential Proprietary 3

Node B version: [ZXSDR V4.13.10.20]

2.1 Feature Introduction

2.1.1 ZWF21-05-022 Service-Based Handover

 Handover to GSM should be performed: It means that it is necessary to hand

ZTE Confidential Proprietary 4

After introduction of LTE, information element of “E-UTRAN Service Handover” in RAB

Handover strategies based on services actually need to be configured in CN.

ZTE Confidential Proprietary 5

2.2 License Control

Table 2-1 License Control List

2.3 Correlation with Other Features

ZWF21-03-004 Inter-RAT Mobility

ZWF21-03-110 Handover with LTE

2. Mutually Exclusive Features

3.1 ZWF21-05-022 Service-Based Handover

This feature is controlled by the switch of ULogicalRnc.srvBasedHoInd in the RNC level

ZTE Confidential Proprietary 6

3.1.1 Principle of Confirming the Attribute “Service Handover”

“Service handover by CN”: means the service handover/E-UTRAN service handover IE

3.1.1.1 UMTS > GSM

“Service handover by CN” has three kinds of values:

 Handover to GSM should be performed: It means that it is necessary to hand over

ZTE Confidential Proprietary 7

GUI Name srvHoInd

ZTE Confidential Proprietary 8

GUI Name srvHoInd

Service Handover Strategy Indicator (CS

Service Handover Strategy Indicator (PS

Service Handover Strategy Indicator (PS

GUI Name service handover by RNC

Service Handover Strategy of RNC for AMR USrvBasedHo.amrSrvHoStra

Service Handover Strategy of RNC for CS64 USrvBasedHo.cs64SrvHoStra

Service Handover Strategy of RNC for PS

Service Handover Strategy of RNC for PS

The following is an example for understanding the strategy mentioned above:

If the parameter of USrvBasedHo.srvHoComStra is set to “2: Priority should not be

ZTE Confidential Proprietary 9

3.1.1.2 UMTS > E-UTRAN

“Service handover by CN” only has one value:

3.1.2 Service-Based Handover Strategy

ZTE Confidential Proprietary 10

3.1.2.1 UTRAN > GSM

Service-based handover is performed according to the following principles after “service

 The inter-frequency measurement is enabled and all non-working carriers

ZTE Confidential Proprietary 11

3.1.2.2 UTRAN > E-UTRAN

Service-based handover is performed according to the following principle after “service

Otherwise, the RNC can start an E-UTRAN inter-RAT measurement based on

ZTE Confidential Proprietary 12

handover is determined by the selection strategy of multi-RAT handover. For details

Table 4-1 Parameter List

This parameter indicates