RAN

IMSI-based Handover
Parameter Description

Issue

02

Date

2009-06-30

Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd. 2009. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.

Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided AS IS without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address:

Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China

Website:

http://www.huawei.com

Email:

support@huawei.com

Huawei Proprietary and Confidential

RAN
IMSI-based Handover

Contents

Contents
1 Introduction to This Document .......................................................................................... 1-1
1.1 Scope ..................................................................................................................................................... 1-1
1.2 Intended Audience.................................................................................................................................. 1-1
1.3 Change History ...................................................................................................................................... 1-1

2 Overview of IMSI-based Handover ................................................................................... 2-1

3 Technical Description........................................................................................................... 3-1
3.1 Principles of IMSI-Based Handover........................................................................................................ 3-1
3.1.1 Mapping Between LAs and SNAs.................................................................................................. 3-1
3.1.2 Mapping Between IMSIs and SNAs............................................................................................... 3-2
3.1.3 Example of the IMSI-Based Handover ........................................................................................... 3-2
3.2 Signaling Procedure of IMSI-Based Handover ........................................................................................ 3-2
3.2.1 RRC Establishment ....................................................................................................................... 3-2
3.2.2 Cell Update ................................................................................................................................... 3-3
3.2.3 URA Update.................................................................................................................................. 3-3
3.2.4 Handover....................................................................................................................................... 3-3
3.2.5 Relocation ..................................................................................................................................... 3-3
3.2.6 Common ID Handling ................................................................................................................... 3-3

4 Engineering Guidelines ....................................................................................................... 4-1

5 Parameters.............................................................................................................................. 5-1
6 Counters ................................................................................................................................. 6-1
7 Glossary.................................................................................................................................. 7-1
8 Reference Documents.............................................................................................................. 2

Issue 02 (2009-06-30)

Huawei Proprietary and Confidential

iii

RAN
IMSI-based Handover

1 Introduction to This Document

Introduction to This Document

1.1 Scope
This document describes the principles and signaling procedure of IMSI-based handover.

1.2 Intended Audience

It is assumed that users of this document are familiar with WCDMA basics and have a
working knowledge of 3G telecommunication.
This document is intended for:
l

Personnel working on Huawei WCDMA products or systems

System operators who need a general understanding of IMSI-based handover feature

1.3 Change History

This section provides information on the changes in different document versions.
There are two types of changes, which are defined as follows:
l

Feature change: refers to the change in the IMSI-based handover feature.

Editorial change: refers to the change in wording or the addition of the information that
was not described in the earlier version.

Document Issues
The document issues are as follows:
l

02 (2009-06-30)

01 (2009-03-30)

Draft (2009-03-10)

Draft (2009-01-15)

Issue 02 (2009-06-30)

Huawei Proprietary and Confidential

1-1

RAN
IMSI-based Handover

1 Introduction to This Document

02 (2009-06-30)
This is the document for the second commercial release of RAN11.0.
Compared with 01 (2009-03-30) of RAN11.0, this issue adjusts the structure of the document.

01 (2009-03-30)
This is the document for the first commercial release of RAN11.0.
Compared with draft (2009-03-10) of RAN11.0, 01(2009-03-30) optimizes the description.

Draft (2009-03-10)
This is the second draft release of RAN11.0.
Compared with draft (2009-01-15) of RAN11.0, draft (2009-03-10) optimizes the description.

Draft (2009-01-15)
This is the first draft release of RAN11.0.

Issue 02 (2009-06-30)

Huawei Proprietary and Confidential

1-2

RAN
IMSI-based Handover

2 Overview of IMSI-based Handover

Overview of IMSI-based Handover

The function of shared network in connected mode is introduced in the 3GPP R5. This
function can be implemented at the CN (Core Network) or be substituted by the handover
based on the IMSI (International Mobile Subscriber Identity) through the RNC.
When a UE moves from one SNA (Shared Network Areas) to a new SNA, the RNC decides
whether or not the UE is allowed to access the new SNA in compliance with the previously
configured mapping between IMSIs and SNAs. If the RNC decides that the UE is not allowed
to access the new SNA, then the UE cannot access the network in that area.
With this feature, the RNC can prevent the UE in connected mode from being moved to an
un-subscribed area without CN support. This feature can also be used as a supplement for
implementing shared networks solutions.

Issue 02 (2009-06-30)

Huawei Proprietary and Confidential

2-1

RAN
IMSI-based Handover

3 Technical Description

Technical Description

This part will describe the princples of IMSI-based handover and signaling procedure of
IMSI-based handover.

3.1 Principles of IMSI-Based Handover

The IMSI-based handover is an alternative solution applied when the CN does not support the
function of shared network in connected mode.
The following mappings must be configured on the RNC to implement the IMSI-based
handover feature:
l

Mapping Between LAs and SNAs

Mapping Between IMSIs and SNAs

An example is provided in Example of the IMSI-Based Handover

of IMSI-based handover.

to describe the principles

3.1.1 Mapping Between LAs and SNAs

The relationship between LAs and SNAs is a multiple-to-multiple one. In other words, one
SNA may consist of multiple LAs, and one LA may belong to multiple SNAs.
Figure 3-1 shows an example of the mapping between LAs and SNAs.
Figure 3-1 Mapping between LAs and SNAs

In Figure 3-1,
l

SNA 1 consists of LA 1, LA 2, LA 3 and LA 4.

SNA 2 consists of LA 3, LA 4, LA 5 and LA 6.

Issue 02 (2009-06-30)

Huawei Proprietary and Confidential

3-1

RAN
IMSI-based Handover

3 Technical Description

LA 3 belongs to SNA 1 and SNA 2.

LA 4 belongs to SNA 1 and SNA 2.

Each LA is identified by MCC and LAC.

Each SNA is identified by SNAC.

3.1.2 Mapping Between IMSIs and SNAs

The SNA that a UE is allowed to access is configured on the RNC side. Each UE is identified
by an IMSI. To configure more than one UE at the same time, set a range of IMSIs so that all
the UEs within the range are configured together. The range is set by ImsiMin and ImsiMax.
The IMSI ranges can be set the same but cannot overlap each other.

The SNA that the UE is allowed to access is specified by the combination of the following
parameters: MCC, MNC, SnaExistInd, and SNAC.

3.1.3 Example of the IMSI-Based Handover

When a UE is moving, the RNC allows the UE to access the target cell if an overlapped area
exists between the SNA to which the LA of the target cell belongs and the SNA that the UE
(that is, the IMSI) is allowed to access. Otherwise, the RNC does not allow the UE to access
the target cell.
For example,
l

Cell 1 belongs to LA 1, and LA 1 belongs to SNA 1.

Cell 2 belongs to LA 2, and LA 2 belongs to SNA 2.

Cell 3 belongs to LA 3, and LA 3 belongs to SNA 3.

A range of IMSIs, 460001234100000 to 460001234200000, are mapped to SNA 1 and

SNA 2.

The IMSI of the UE is 460001234150001, and the UE camps on cell 1 currently.

In this situation, when the UE moves, the UE is allowed to access cell 2 but cannot access cell
3.
Each UE belongs to a maximum of 6 PLMNs (Public Land Mobile Networks). Each PLMN
corresponds to a maximum of 32 SNAs. Each LA belongs to a maximum of 32 SNAs.

3.2 Signaling Procedure of IMSI-Based Handover

The procedures affected by the IMSI-based handover are RRC establishment, cell update,
URA update, handover, relocation, and common ID handling. In these procedures, the RNC
performs access control on the UE in compliance with the mapping between IMSIs and
SNAs.

3.2.1 RRC Establishment

The UE initiates the RRC (Radio Resource Control) establishment procedure by using an
RRC CONNECTION REQUEST message.

Issue 02 (2009-06-30)

Huawei Proprietary and Confidential

3-2

RAN
IMSI-based Handover
l

3 Technical Description

If this message carries IMSI information, the RNC decides whether to allow the UE to
access the cell or not.

If the RNC allows the UE to access the cell, the UE can access the cell.

If the RNC does not allow the UE to access the cell, the RNC sends an RRC
CONNECTION REJECT message to the UE.

If this message does not carry IMSI information, the RRC connection is established
normally.

3.2.2 Cell Update

When the UE initiates a cell update in the target cell, the RNC decides whether the UE has
access to the target cell or not.
If the UE does not have access to the target cell, the cell update fails.

3.2.3 URA Update

The URA update is the same as the cell update.

3.2.4 Handover
During a soft handover or a hard handover, the RNC does not send a MEASUREMENT
CONTROL message if the UE does not have access to a cell. Therefore, the UE does not
trigger a measurement report of that cell. As a result, the UE cannot be handed over to that
cell.
The RNC does not select the cell that the UE is not allowed to access as the target cell when a
blind handover is triggered.

3.2.5 Relocation
When the Target RNC receives a RELOCATION REQUEST message, it decides whether the
UE has access to the target cell or not.
If the UE does not have access to the target cell, the relocation failure procedure is triggered.

3.2.6 Common ID Handling

The RNC obtains the IMSI information of the UE from the COMMON ID message and
decides whether the UE has access to the current cell or not.
If the UE does not have access to the current cell, the RRC connection is released.

Issue 02 (2009-06-30)

Huawei Proprietary and Confidential

3-3

RAN
IMSI-based Handover

4 Engineering Guidelines

Engineering Guidelines

The subparameter RNCAP_IMSI_HO_SWITCH of PROCESSSWITCH controls the

functionality of IMSI-based handover. The subparameter can be set on through the command
SET RRCTRLSWITCH.

Issue 02 (2009-06-30)

Huawei Proprietary and Confidential

4-1

RAN
IMSI-based Handover

5 Parameters

Parameters

The following describes the parameters related to IMSI-based Handover.

For the meaning of each parameter, see Table 5-1. For the default value, value ranges, and
MML commands of each parameter, see Table 5-2.
Table 5-1 IMSI-based handover parameter description (1)
Parameter ID

Description

LAC

Identifying a location area code for a PLMN. It is defined by the operator.

For detailed information of this parameter, refer to 3GPP TS 23.003.

SNAC

Sharing Network Area Code.

ImsiMin

The minimum of one IMSI range.

ImsiMax

The maximum of one IMSI range.

SnaExistInd

Indicating whether the SNAC need be configured.

TRUE: The SNAC need be configured.
FALSE: The SNAC need not be configured.UE can access any cell of the
PLMN.

PROCESSSWITCH

1) INVOKE_TRACE_SWITCH. When it is checked, RNC will start

Invoke Trace procedure upon receiving INVOKE TRACE Message form
CN, otherwise, RNC won't start the Invoke Trace procedure though it
receives the INVOKE TRACE message.
2) SYS_INFO_UPDATE_FOR_IU_RST. When it is checked, RNC will
broadcast SYSTEM INFORMATION messages to UE when Iu reset,
otherwise, RNC won't broadcast SYSTEM INFORMATION messages to
UE when IU reset.
3) DRNC_DIRECT_DSCR. When it is checked, DRNC will start DSCR
procedure directly in RRC states other than CELL_DCH, otherwise, DRNC
will transfer RRC CELL UPDATE message to SRNC.
4) RNC_SHARE_SWITCH. When it is checked, RNC traffic share
function will be valid, otherwise, RNC traffic function cannot be used.
5)RNCAP_IMSI_HO_SWITCH.When it is checked, Imsi handover
function will be used,otherwise it will be not used.
6) TERMINAL_VERSION_DEBASE_SWITCH. When it is checked,
terminal version R4 will debase to R99.
7)SYS_HO_OUT_CIPHER_SWITCH.When it is checked ,the RNC will

Issue 02 (2009-06-30)

Huawei Proprietary and Confidential

5-1

RAN
IMSI-based Handover

Parameter ID

5 Parameters

Description
add ciphering byte at GSM HANDOVER COMMAND if the GSM system
do not add any cipher information at that message.
8)SYS_HO_CIPHER_CONFIG.When it is checked , the cipher
configuration in the added cipher byte in GSM will be A5/1.When it is no
checked ,the cipher configuration is A5/0.
9)BARRED_CELL_FOR_CSDOMAIN_RST.When it is checked, cell will
be bared when CS domain is invalid, otherwise the CS domain will be
bared when CS domain is invalid. It is invalid If
SYS_INFO_UPDATE_FOR_IU_RST is not checked.
10)CR2284R1_SWITCH.in section 8.6.6.28 of TS25.331 of R5 Before
2006, it describes that the HFN should add one when UE is ciphering in the
situation of Timing re-initialized hard handover,while not specified in RB
SETUP process in the section of 8.6.4.3. so it is not clear whether to add
or not in RB SETUP in DRD scenarios.
CR2284R1 clarify that HFN should add one in RB SETUP process with
Timing re-initialized hard handover.
when it is checked ,RNC accepts this CR2284R1;
when it is not checked ,RNC does not accept this CR2284R1.
11)CR2284R1_COMPATIBLE_SWITCH.CR2284R1 causes the
compatible problem.if UE is not consistent with RNC regarding whether
accept the CR2284R1 or not,it will cause the problem of streaming when
UEs are communicating with each other.So RNC creates this switch .
when it is checked, RNC is auto-adaptive to accept the CR2284R1
according to UE version information.
The principles that RNC judges UE whether to accept the CR2284R1 are as
follows:
R5 and above UE accepts the CR;
R99/R4 UE ,if it receives the START LIST value from RB SETUP
COMPLETE,RNC figures that UE accepts the CR;
R99/R4 UE ,if it only receives the START value from RB SETUP
COMPLETE,RNC figures that UE does not accept the CR ;
when it is not checked, whether RNC accept the CR or not is according to
CR2284R1_SWITCH.
The relations between these two switches CR2284R1_SWITCH and
CR2284R1_COMPATIBLE_SWITCH are as follows:
(1)CR2284R1_COMPATIBLE_SWITCH is checked, RNC is
self-compatible,so the CR2284R1_SWITCH is invalid;
(2)CR2284R1_COMPATIBLE_SWITCH is not checked, the
CR2284R1_SWITCH is valid.
12)CDT_MSG_FULL_TRACE:When it is checked,CDT trace function
which starts tracing from message RRC CONNECT REQUEST.
13)COMBINE_OPERATION_DRD_SWITCH.When it is on,RNC will not
reject the message RB SETUP CMP without the IE active time.
14)UL_INTER_PROTECT_SWITCH.When the switch is off,RNC will not
do integrity protection check for
uplink RRC messages.

MCC

Mobile country code of the RNC.

MNC

Mobile network code of the RNC.

Issue 02 (2009-06-30)

Huawei Proprietary and Confidential

5-2

RAN
IMSI-based Handover

5 Parameters

Table 5-2 IMSI-based handover parameter description (2)

Parameter
ID

Default
Value

LAC

SNAC

ImsiMin

ImsiMax

SnaExistInd

PROCESSS
WITCH

Issue 02 (2009-06-30)

GUI Value Range

1~65533,65535

0~65535

Actual Value
Range
{1~65533},
{65535}

0~65535

TRUE, FALSE

INVOKE_TRACE_S
WITCH,
SYS_INFO_UPDATE
_FOR_IU_RST,
DRNC_DIRECT_DSC
R,
RNC_SHARE_SWITC
H,
RNCAP_IMSI_HO_S

Unit
None

None

15-bit decimal
numerals

None

15-bit decimal
numerals

None

TRUE,FALSE

None

This
parameter is set
to 0 or 1
according to the
related
domains.

None

Huawei Proprietary and Confidential

MML Command
ADD
LAC(Mandatory)
ADD
RAC(Mandatory)
ADD
CELLSETUP(Mandat
ory)
ADD
QUICKCELLSETUP
(Mandatory)
ADD
SAC(Mandatory)
ADD
NRNCCELL(Mandat
ory)
ADD
GSMCELL(Mandator
y)
ADD
CZ(Mandatory)
ADD
LASNAMAP(Mandat
ory)
ADD
LASNAMAP(Mandat
ory)
ADD
IMSISNAMAP(Mand
atory)

NE

RNC

RNC

ADD
IMSISNAMAP(Mand
atory)

RNC

ADD
IMSISNAMAP(Mand
atory)

RNC

ADD
IMSISNAMAP(Mand
atory)

RNC

SET
RRCTRLSWITCH(M
andatory)

RNC

5-3

RAN
IMSI-based Handover

Parameter
ID

5 Parameters

Default
Value

GUI Value Range

Actual Value
Range

Unit

MML Command

NE

SET
MBMSPERF(Mandat
ory)

RNC

SET
MBMSPERF(Mandat
ory)

RNC

WITCH,
TERMINAL_VERSIO
N_DEBASE_SWITCH
,
SYS_HO_OUT_CIPH
ER_SWITCH,
SYS_HO_CIPHER_C
ONFIG,
BARRED_CELL_FO
R_CSDOMAIN_RST,
CR2284R1_SWITCH,
CDT_MSG_FULL_TR
ACE,
CR2284R1_COMPAT
IBLE_SWITCH,
COMBINE_OPERATI
ON_DRD_SWITCH,
UL_INTER_PROTEC
T_SWITCH,
UPLINK_MDC_ENH
ENCEMENT_SWITC
H,
NODEB_PRIVATE_I
NTERFACE_SWITC
H
MCC

MNC

000~999

None

None
00~99,000~999

The Default Value column is valid for only the optional parameters.
The "-" symbol indicates no default value.

Issue 02 (2009-06-30)

Huawei Proprietary and Confidential

5-4

RAN
IMSI-based Handover

6 Counters

Counters

The following describes the counters related to IMSI-based Handover.

For details, see the RNC Performance Counter Reference.

Issue 02 (2009-06-30)

Huawei Proprietary and Confidential

6-1

RAN
IMSI-based Handover

7 Glossary

Glossary

For the acronyms, abbreviations, terms, and definitions, see the Glossary.

Issue 02 (2009-06-30)

Huawei Proprietary and Confidential

7-1

RAN
IMSI-based Handover

8 Reference Documents

Reference Documents

The following lists the reference documents related to the feature:

1.

3GPP TS 25.413: UTRAN Iu interface RANAP Signalling

2.

3GPP TS 25.423: UTRAN Iur Interface RNSAP Signalling

3.

Basic Feature Description of Huawei UMTS RAN11.0 V1.5

4.

Optional Feature Description of Huawei UMTS RAN11.0 V1.5

Issue 02 (2009-06-30)

Huawei Proprietary and Confidential

8-1