Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Feature Guide
Service-Based Handover
Service-Based Handover
Version Date Author Reviewer Notes
TABLE OF CONTENTS
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
4 Parameters....................................................................................................... 13
7 Abbreviation .................................................................................................... 25
8 Reference Document....................................................................................... 26
FIGURES
TABLES
1 Feature Attribute
RNC version: [ZXWR RNC V3.13.10.15/ZXUR 9000 V4.13.10.15]
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
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 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.
License Configured
Feature ID Feature Name Unit
Control Item NE
Service-Based Service-Base
ZWF21-05-022 RNC RNC
Handover d Handover
1. Required Features
None
3. Affected Features
None
3 Technical Description
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 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.
The 3GPP protocol defines a service handover IE in the IU interface for GSM, which
indicates which handover the UMTS RNC should perform.
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
Table 3-2 Control Parameters that “service handover by RNC” is Configured for the
Respective Services
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 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.
The 3GPP protocol defines a service handover IE in the IU interface for E-UTRAN, which
indicates which handover the UMTS RNC should perform.
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”.
The strategies of service-based handover for UMTS > GSM and UMTS > E-UTRAN are
different, so they are described by chapter as follows.
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.
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.
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.
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
4 Parameters
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
Recomme
Paramet Value Default
GUI Name Parameter Description Unit nded
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
property value defined by
the RNC. Otherwise the
RNC will perform a policy
based on the value of
"service handover IE"
included in the requested
RAB.
Recomme
Paramet Value Default
GUI Name Parameter Description Unit nded
er Name Range Value
Value
Recomme
Paramet Value Default
GUI Name Parameter Description Unit nded
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
property value defined by
the RNC. Otherwise the
RNC will perform a policy
based on the value of
"service handover IE"
included in the requested
RAB.
Recomme
Paramet Value Default
GUI Name Parameter Description Unit nded
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
requested RAB, the RNC
will also perform a policy
based on
Cs64ServHoStra.
Otherwise the RNC will
perform a policy based on
the value of "service
handover IE" included in
the requested RAB.
Recomme
Paramet Value Default
GUI Name Parameter Description Unit nded
er Name Range Value
Value
requested RAB, the RNC
will also perform a policy
based on
R99RtServHoStra.
Otherwise the RNC will
perform a policy based on
the value of "service
handover IE" included in
the requested RAB.
Recomme
Paramet Value Default
GUI Name Parameter Description Unit nded
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
Paramet Value Default
GUI Name Parameter Description Unit nded
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
Counter ID Name
6 Engineering Guide
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.
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.
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
Deactivation
No GUI Name Default Value
Value
For the description and configuration of these parameters, refer to Section 6.2 Feature
Activation Procedure.
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.
None
7 Abbreviation
Abbreviation Full Name
CN Core Network
CS Circuit Switched
PS Packet Switched
RT Real Time
UE User Equipment
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