Huawei IMSI based Handover

IMSI-based Handover RAN13.0

Feature Parameter Description

Issue 01

Date 2011-04-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2011. 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: [email protected]

http://www.huawei.com/

mailto:[email protected]

WCDMA RAN

IMSI-based Handover Contents

Issue 01 (2011-04-30) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd

i

Contents

1 Introduction ................................................................................................................................ 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 Shared Network Support in Connected Mode .......................................................... 3-1

3.2 Principles of IMSI-Based Handover .............................................................................................. 3-2

3.2.1 Mapping Between LAs and SNAs ........................................................................................ 3-2

3.2.2 Mapping Between IMSIs and SNAs ..................................................................................... 3-2

3.2.3 Example of the IMSI-Based Handover ................................................................................. 3-3

3.3 Signaling Procedure of IMSI-Based Handover ............................................................................. 3-3

3.3.1 RRC Establishment .............................................................................................................. 3-3

3.3.2 Cell Update ........................................................................................................................... 3-3

3.3.3 URA Update .......................................................................................................................... 3-3

3.3.4 Handover .............................................................................................................................. 3-4

3.3.5 Relocation ............................................................................................................................. 3-4

3.3.6 Common ID Handling ........................................................................................................... 3-4

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

5 Parameters ................................................................................................................................. 5-1

6 Counters ...................................................................................................................................... 6-1

7 Glossary ...................................................................................................................................... 7-1

8 Reference Documents ............................................................................................................. 8-1

WCDMA RAN

IMSI-based Handover 1 Introduction



1-1

1 Introduction

1.1 Scope

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

1.2 Intended Audience

This document is intended for:

Personnel who are familiar with WCDMA basics

Personnel who need to understand IMSI-based handover

Personnel who work with Huawei products

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:

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:

01 (2011-04-30)

Draft B (2011-03-30)

Draft A (2010-12-30)

01 (2011-04-30)

This is the document for the first commercial release of RAN13.0.

Compared with issue Draft B (2011-03-30) of RAN13.0, this issue optimizes the description.

Draft B (2011-03-30)

This is the draft of the document for RAN13.0.

Compared with issue Draft A (2010-12-30) of RAN13.0, this issue optimizes the description.

Draft A (2010-12-30)

This is the draft of the document.

Compared with issue 01 (2010-03-30) of RAN12.0, this issue optimizes the description.

WCDMA RAN

IMSI-based Handover 2 Overview of IMSI-based Handover



2-1

2 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.

WCDMA RAN

IMSI-based Handover 3 Technical Description



3-1

3 Technical Description

This part will describe the principles of shared network support in connected mode and IMSI-based handover and signaling procedure of IMSI-based handover.

3.1 Principles of Shared Network Support in Connected Mode

The feature of shared network support in connected mode (WRFD-021301 Shared Network Support in Connected Mode) enables the RNC to obtain shared network parameters and work with the CN to apply the access control over the UE in connected mode to the specified location area. This feature can support operation applications for network sharing solutions.

Based on R99 specifications, when the UE is in idle mode, the CN+UTRAN have mechanisms available to provide UE-specific access restrictions for LAs of the current PLMN and other PLMNs by using roaming agreement. But there is no mechanism to restrict UE behavior in connected mode, since UTRAN does not have enough information to handle the UE as CN does to UE in idle mode. Accordingly, this feature is introduced in 3GPP R5 and used to provide an access restriction mechanism for UE in connected mode.

To support this function, the RNC obtains the parameters of the shared network support in connected mode from the messages and information elements (IE), which are defined in 3GPP TS 25.413 and 25.423 including:

The information of the PLMN/SNA that allows the UE to connect to, which is acquired from CN through RELOCATION REQUEST or COMMON ID message.

The information of the SNAs that the LAs belong to, which is from CN through INFORMATION TRANSFER message or from DRNC through RADIO LINK SETUP RESPONSE and UPLINK SIGNALING TRANSFER messages.

Each LA belongs to one or several shared network area (SNA), and one UE can belong to one or several SNAs. Based on the information, the RNC decides whether the UE is allowed to get services in the new network or not according to the information.

The following procedures have connection with this feature:

Cell update

When the UE initiates cell update in the destination cell, the RNC decides whether the UE is allowed to access the destination cell.

If the UE is not allowed to access the destination cell, the cell update fails.

URA update

The URA update is the same as the cell update.

Handover

During the soft handover or the hard handover, the RNC does not send measurement control indication if the UE is not allowed to access 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.

Relocation

When the target RNC (TRNC) receives a RELOCATION REQUEST message, it decides whether the UE is allowed to access the destination cell.

If the UE is not allowed to access the destination cell, the relocation failure procedure is triggered.

Handling common ID message

The RNC obtains the IMSI information of the UE in the common ID message and decides whether the UE is allowed to access the current cell. If the UE is not allowed to access the current cell, the RRC connection is released.

WCDMA RAN




3-2

CN must support this feature. When the Iur interface is used, the RNC connected over the interface must also support this feature.

You may enable the feature by setting the switch HoSwitch > HO_MC_SNA_RESTRICTION_SWITCH.

3.2 Principles of IMSI-Based Handover

The IMSI-based handover (WRFD-021303 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:

Mapping Between LAs and SNAs

Mapping Between IMSIs and SNAs

An example is provided in Example of the IMSI-Based Handover to describe the principles of IMSI-based handover.

3.2.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,

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.

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.2.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.

../RNCParaHtml/mbsc/m-para/ucorrmalgoswitch_hoswitch.html

../RNCParaHtml/mbsc/m-para/ulasnamap_mcc.html

../RNCParaHtml/mbsc/m-para/ulasnamap_lac.html

../RNCParaHtml/mbsc/m-para/ulasnamap_snac.html

../RNCParaHtml/mbsc/m-para/uimsisnamap_imsimin.html

../RNCParaHtml/mbsc/m-para/uimsisnamap_imsimax.html

WCDMA RAN




3-3

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

3.2.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,

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



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.3 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.3.1 RRC Establishment

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

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.3.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.3.3 URA Update

The URA update is the same as the cell update.

../RNCParaHtml/mbsc/m-para/uimsisnamap_mcc.html

../RNCParaHtml/mbsc/m-para/uimsisnamap_mnc.html

../RNCParaHtml/mbsc/m-para/uimsisnamap_snaexistind.html

../RNCParaHtml/mbsc/m-para/uimsisnamap_snac.html

WCDMA RAN




3-4

3.3.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.3.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.3.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.

WCDMA RAN

IMSI-based Handover 4 Engineering Guidelines



4-1

4 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 URRCTRLSWITCH.

../RNCParaHtml/mbsc/m-para/urrctrlswitch_processswitch.html

WCDMA RAN

IMSI-based Handover 5 Parameters



5-1

5 Parameters

Table 5-1 Parameter description

Parameter ID NE MML Command Description

HoSwitch BSC6900

SET UCORRMALGOSWITCH(Optional)

Meaning:HandOver switch group.

1) HO_ALGO_HCS_SPEED_EST_SWITCH: When the switch is on, the RNC evaluates the UE's moving speed in the HCS and initiates fast intra-layer or slow inter-layer handover.

2) HO_ALGO_LDR_ALLOW_SHO_SWITCH: When the switch is on, the LDR inter-frequency handover is allowed during soft handover.

3) HO_ALGO_MBMS_FLC_SWITCH: When the switch is on, the UE requires that the redirection strategy be used for frequency layer convergence.

4) HO_ALGO_OVERLAY_SWITCH: When the switch is on, the associated receiving and mobility algorithms of the overlay network are used. When the switch is not on, the associated algorithms are not used. Overlay network is an UTRAN network covering present network, it supports HSPA, MBMS and other new features. To satisfy new requirements of operator and restrictions of present network, overlay network realizes operation distribution and load sharing between new network and present network, also gives special handling for mobility management of network verge.

5) HO_INTER_FREQ_HARD_HO_SWITCH: When the switch is on, the RNC is allowed to initiate inter-frequency measure control or the load-based inter-frequency hard handover upon the handover decision on inter-frequency load.

6) HO_INTER_RAT_CS_OUT_SWITCH: When the switch is on, the RNC is allowed to initiate inter-frequency measure control and the CS inter-RAT hard handover from the 3G network to the 2G network.

7) HO_INTER_RAT_PS_3G2G_CELLCHG_NACC_SWITCH: When the switch is on, the NACC function is supported during the PS inter-RAT handover from the 3G network to the 2G network in the cell change order process. When the switch is not on, the

../RNCParaHtml/mbsc/m-para/ucorrmalgoswitch_hoswitch.html

../RNCParaHtml/mbsc/m-mml/set-ucorrmalgoswitch.html



WCDMA RAN




5-2


NACC function is not supported. When PS_3G2G_RELOCATION_SWITCH is ON, this switch is useless. When the NACC function is supported, the UE skips the reading procedure as the SI/PSI of the target cell is provided after the UE accesses the 2G cell. Thus, the delay of inter-cell handover is reduced.

8) HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH: When the switch is on, the PS inter-RAT handover from the 3G network to the 2G network is performed in the relocation process. When the switch is not on, the PS inter-RAT handover from the 3G network to the 2G network is performed in the cell change order process.

9) HO_INTER_RAT_PS_OUT_SWITCH: When the switch is on, the RNC is allowed to initiate inter-frequency measure control and the PS inter-RAT hard handover from the 3G network to the 2G network.

10) HO_INTER_RAT_RNC_SERVICE_HO_SWITCH: When the switch is on, the attributes of inter-RAT handover of the services are based on the configuration of RNC parameters. When the switch is not on, the attributes are set on the basis of the CN. If no information is provided by the CN, the attributes are then based on the RNC parameters.

11) HO_INTRA_FREQ_DETSET_INTO_ACTSET_SWITCH: When the switch is on, the cells in the detected set from which the RNC receives their valid event reports can be added to the active set. The cells allowed to be added to the active set must be the neighboring cells of the cells in the active set.

12) HO_INTRA_FREQ_DETSET_RPRT_SWITCH: When the switch is on, statistics on the intra-frequency measurement reports of the detected set are taken.

13) HO_INTRA_FREQ_HARD_HO_SWITCH: When the switch is on, the RNC is allowed to initiate the intra-frequency hard handover.

14) HO_INTRA_FREQ_RPRT_1J_SWITCH: When the switch is on, the event 1J is

WCDMA RAN




5-3


included in the delivery of intra-frequency measurement control if the UE version is R6.

15) HO_INTRA_FREQ_SOFT_HO_SWITCH: When the switch is on, the cells on the RNC can active the soft handover. When the RNC receives reports on the events 1A, 1B, 1C, or 1D, associated addition, removal, and replacement of handover cell of the soft handover are initiated.

16) HO_MC_MEAS_BEYOND_UE_CAP_SWITCH: When the switch is on, the neighboring cell whose frequency band is beyond the UE's capabilities can also be delivered in the inter-frequency measurement list.

17) HO_MC_NCELL_COMBINE_SWITCH: When the switch is on, the neighboring cell combined algorithm is used during the delivery of the objects to be measured. When the switch is not on, the optimal cell algorithm is used.

18) HO_MC_SIGNAL_IUR_INTRA_SWITCH: When the switch is on, intra-frequency handover is allowed over the Iur interface if the UE has only signaling.

19) HO_MC_SIGNAL_SWITCH: When the switch is on, quality measurement on the active set is delivered after signaling setup but before service setup. If the UE is at the cell verge or receives weak signals after accessing the network, the RNC can trigger inter-frequency or inter-RAT handover when the UE sets up the RRC.

20) HO_MC_SNA_RESTRICTION_SWITCH: When the switch is on, the RNC controls the UEs in the connected state based on the configurations on the CN. The UEs can only access and move in authorized cells.

21) HO_LTE_PS_OUT_SWITCH:This bit field is added under "Handover Algorithm Switch". HO_LTE_PS_OUT_SWITCH is the switch for the handover from UMTS to LTE. The meaning of the bit field is as follows:

When this bit field is selected, this switch is set to ON. In this case, the RNC is allowed to send an LTE MEASUREMENT CONTROL message to the UE and to initiate an inter-RAT PS handover from UMTS to LTE.

WCDMA RAN




5-4


When this bit field is not selected, this switch is set to OFF. In this case, the RNC is not allowed to send an LTE MEASUREMENT CONTROL message to the UE or to initiate an inter-RAT PS handover from UMTS to LTE.

22) HO_LTE_SERVICE_PS_OUT_SWITCH :This bit field is added under "Handover Algorithm Switch". HO_LTE_SERVICE_PS_OUT_SWITCH is the switch for the service-based handover from UMTS to LTE. The meaning of the bit field is as follows:

When this bit field is selected, this switch is set to ON. In this case, the RNC is allowed to send an LTE MEASUREMENT CONTROL message to the UE based on service and to initiate an inter-RAT PS service-based handover from UMTS to LTE. When this bit field is not selected, this switch is set to OFF. In this case, the RNC is not allowed to send an LTE MEASUREMENT CONTROL message to the UE based on service or to initiate an inter-RAT PS service-based handover from UMTS to LTE.

23) HO_H2G_SRVCC_SWITCH :This bit is a Single Radio Voice Call Continuity (SRVCC) switch for the VoIP service that is handed over to GERAN. SRVCC ensures the continuity of voice services that are handed over between the CS domain and the IP Multimedia Subsystem (IMS).

The meaning of the bit is as follows:

When it is set to "ON", it indicates that the VoIP service can be handed over to GERAN through SRVCC procedure.

When it is set to "OFF", it indicates that the VoIP service cannot be handed over to GERAN through SRVCC procedure

GUI Value Range:HO_ALGO_HCS_SPEED_EST_SWITCH, HO_ALGO_LDR_ALLOW_SHO_SWITCH, HO_ALGO_MBMS_FLC_SWITCH, HO_ALGO_OVERLAY_SWITCH, HO_INTER_FREQ_HARD_HO_SWITCH, HO_INTER_RAT_CS_OUT_SWITCH, HO_INTER_RAT_PS_3G2G_CELLCHG_NACC_SWITCH, HO_INTER_RAT_PS_3G2G_RELOCATION

WCDMA RAN




5-5


_SWITCH, HO_INTER_RAT_PS_OUT_SWITCH, HO_INTER_RAT_RNC_SERVICE_HO_SWITCH, HO_INTRA_FREQ_DETSET_INTO_ACTSET_SWITCH, HO_INTRA_FREQ_DETSET_RPRT_SWITCH, HO_INTRA_FREQ_HARD_HO_SWITCH, HO_INTRA_FREQ_RPRT_1J_SWITCH, HO_INTRA_FREQ_SOFT_HO_SWITCH, HO_MC_MEAS_BEYOND_UE_CAP_SWITCH, HO_MC_NCELL_COMBINE_SWITCH, HO_MC_SIGNAL_IUR_INTRA_SWITCH, HO_MC_SIGNAL_SWITCH, HO_MC_SNA_RESTRICTION_SWITCH, HO_LTE_PS_OUT_SWITCH, HO_LTE_SERVICE_PS_OUT_SWITCH, HO_H2G_SRVCC_SWITCH

Actual Value Range:HO_ALGO_HCS_SPEED_EST_SWITCH, HO_ALGO_LDR_ALLOW_SHO_SWITCH, HO_ALGO_MBMS_FLC_SWITCH, HO_ALGO_OVERLAY_SWITCH, HO_INTER_FREQ_HARD_HO_SWITCH, HO_INTER_RAT_CS_OUT_SWITCH, HO_INTER_RAT_PS_3G2G_CELLCHG_NACC_SWITCH, HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH, HO_INTER_RAT_PS_OUT_SWITCH, HO_INTER_RAT_RNC_SERVICE_HO_SWITCH, HO_INTRA_FREQ_DETSET_INTO_ACTSET_SWITCH, HO_INTRA_FREQ_DETSET_RPRT_SWITCH, HO_INTRA_FREQ_HARD_HO_SWITCH, HO_INTRA_FREQ_RPRT_1J_SWITCH, HO_INTRA_FREQ_SOFT_HO_SWITCH, HO_MC_MEAS_BEYOND_UE_CAP_SWITCH, HO_MC_NCELL_COMBINE_SWITCH, HO_MC_SIGNAL_IUR_INTRA_SWITCH, HO_MC_SIGNAL_SWITCH, HO_MC_SNA_RESTRICTION_SWITCH, HO_LTE_PS_OUT_SWITCH, HO_LTE_SERVICE_PS_OUT_SWITCH, HO_H2G_SRVCC_SWITCH

Default Value:None

ImsiMax BSC6900

ADD UIMSISNAMAP(Mandator

Meaning:The maximum of one IMSI range

../RNCParaHtml/mbsc/m-para/uimsisnamap_imsimax.html

../RNCParaHtml/mbsc/m-mml/add-uimsisnamap.html


WCDMA RAN




5-6


y)

RMV UIMSISNAMAP(Mandatory)

GUI Value Range:None

Actual Value Range:15-bit decimal numerals

Default Value:None

ImsiMin BSC6900

ADD UIMSISNAMAP(Mandatory)


Meaning:The minimum of one IMSI range


Actual Value Range:15-bit decimal numerals

Default Value:None

LAC BSC6900

ADD ULASNAMAP(Mandatory)

Meaning:Identifies a location area code for a Public Land Mobile Network (PLMN) of the GSM-MAP type. It is defined by the operator.

The LAC is used to uniquely identify an LA within a PLMN.

The LAC is a 2-byte hexadecimal code. It ranges from 0000 to FFFE. The codes 0000 and FFFE are reserved. The LAC is presented in the format of h'X1X2X3X4 or H'X1X2X3X4. h' and H' are the hexadecimal symbols. For detailed information about this parameter, see 3GPP TS 23.003

GUI Value Range:1~65533, 65535

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

Default Value:None

MCC BSC6900


RMV ULASNAMAP(Mandatory)

Meaning:The code of the country to which the RNC belongs


Actual Value Range:000~999

Default Value:None

MCC BSC6900


Meaning:Mobile country code. This parameter identifies the country where a mobile subscriber is located, for example, the Chinese MCC is 460


Actual Value Range:3 digits

Default Value:None

MNC BSC6900


Meaning:Mobile network code. This parameter identifies the public land mobile network (PLMN) to which a mobile subscriber belongs.

During parameter configuration, the PLMN value tags of different value ranges should be assigned to any neighboring areas after

../RNCParaHtml/mbsc/m-mml/rmv-uimsisnamap.html



../RNCParaHtml/mbsc/m-para/uimsisnamap_imsimin.html







../RNCParaHtml/mbsc/m-para/ulasnamap_lac.html

../RNCParaHtml/mbsc/m-mml/add-ulasnamap.html


../RNCParaHtml/mbsc/m-para/ulasnamap_mcc.html



../RNCParaHtml/mbsc/m-mml/rmv-ulasnamap.html


../RNCParaHtml/mbsc/m-para/uimsisnamap_mcc.html




../RNCParaHtml/mbsc/m-para/uimsisnamap_mnc.html




WCDMA RAN




5-7


negotiation. There is no intersection between the value ranges. The area can be an LA(Location Area) or RA(Routing Area). The PLMN value tags of LAs or RAs vary within the specified range. As a result, a UE can always read different PLMN value tags when moving across the areas and thus correctly reads the SIB1


Actual Value Range:2~3 digits

Default Value:None

PROCESSSWITCH

BSC6900

SET URRCTRLSWITCH(Optional)

Meaning: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.

5)RNC_SHARE_SWITCH. When it is checked, RNC traffic share function will be valid, otherwise, RNC traffic function cannot be used.

6)RNCAP_IMSI_HO_SWITCH. When it is checked, Imsi handover function will be used, otherwise it will be not used.

7)TERMINAL_VERSION_DEBASE_SWITCH. When it is checked, terminal version R4 will debase to R99.

8)SYS_HO_OUT_CIPHER_SWITCH. When it is checked, the RNC will add ciphering byte at GSM HANDOVER COMMAND if the GSM system do not add any cipher information at that message.

9)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.



../RNCParaHtml/mbsc/m-mml/set-urrctrlswitch.html



WCDMA RAN




5-8


10)ARRED_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.

11)CR2284R1_SWITCH.in section 8.6.6.28 of TS25.331 of R5 Before2006, 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.

12)CDT_MSG_FULL_TRACE: When it is checked, CDT trace function which starts tracing from message RRC CONNECT REQUEST.

13)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;

WCDMA RAN




5-9


(2)CR2284R1_COMPATIBLE_SWITCH is not checked, the CR2284R1_SWITCH is valid.

14)COMBINE_OPERATION_DRD_SWITCH. When it is on, RNC will not reject the message RB SETUP CMP without the IE active time.

15)UL_INTER_PROTECT_SWITCH. When the switch is off, RNC will not do integrity protection check for uplink RRC messages.

16)FAST_DORMANCY_SWITCH. When it is checked, RNC will apply FAST DORMANCY function.

17)SYS_HO_IN_CIPHER_SWITCH. When it is checked, don't receive the encrypted ability information from RELOC REQ ,default configured of encrypted parameter are UIA1 and UEA0.

18)PTT_EARLY_TRANS_SWITCH_OFF. When it is checked, PTT user will not apply the early transmission function, otherwise, PTT user will apply the early transmission function.

19)UPLINK_MDC_ENHENCEMENT_SWITCH. This switch has become invalid.

20)NODEB_PRIVATE_INTERFACE_SWITCH. When it is checked, the NodeB private interface data can be taken to the NodeB through the IUB protocol message.

21)PTT_SPEC_LI_SWITCH_OFF. When it is checked, special LI will not be used for PTT user, otherwise, special LI will be used for PTT user.

22)RNC_DF_2_URA_PCH_SWITCH. When it is checked, RNC will support transferring Fast Dormancy UE from CELL_DCH or CELL_FACH to URA_PCH. When it is not checked, RNC will not support transferring Fast Dormancy UE from CELL_DCH or CELL_FACH to URA_PCH.

23)FD_TAC_MATCH_SWITCH. When it is checked, RNC will apply FAST DORMANCY function for UE whose TAC is configured in database. When it is not checked, RNC will apply FAST DORMANCY function for UE whose version is R5 or later

GUI Value Range:INVOKE_TRACE_SWITCH, SYS_INFO_UPDATE_FOR_IU_RST, DRNC_DIRECT_DSCR,

WCDMA RAN




5-10


RNC_SHARE_SWITCH, RNCAP_IMSI_HO_SWITCH, TERMINAL_VERSION_DEBASE_SWITCH, SYS_HO_OUT_CIPHER_SWITCH, SYS_HO_CIPHER_CONFIG, BARRED_CELL_FOR_CSDOMAIN_RST, CR2284R1_SWITCH, CDT_MSG_FULL_TRACE, CR2284R1_COMPATIBLE_SWITCH, COMBINE_OPERATION_DRD_SWITCH, UL_INTER_PROTECT_SWITCH, FAST_DORMANCY_SWITCH, SYS_HO_IN_CIPHER_SWITCH, PTT_EARLY_TRANS_SWITCH_OFF, UPLINK_MDC_ENHENCEMENT_SWITCH, NODEB_PRIVATE_INTERFACE_SWITCH, PTT_SPEC_LI_SWITCH_OFF, RNC_DF_2_URA_PCH_SWITCH, FD_TAC_MATCH_SWITCH

Actual Value Range:This parameter is set to 0 or 1 according to the related domains

Default Value:None

SNAC BSC6900



Meaning:Sharing Network Area Code

GUI Value Range:0~65535


Default Value:None

SNAC BSC6900


RMV ULASNAMAP(Mandatory)

Meaning:Sharing Network Area Code

GUI Value Range:0~65535


Default Value:None

SnaExistInd BSC6900



Meaning: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

GUI Value Range:TRUE, FALSE

Actual Value Range:TRUE, FALSE

Default Value:None

../RNCParaHtml/mbsc/m-para/uimsisnamap_snac.html







../RNCParaHtml/mbsc/m-para/ulasnamap_snac.html





../RNCParaHtml/mbsc/m-para/uimsisnamap_snaexistind.html







WCDMA RAN

IMSI-based Handover 6 Counters



6-1

6 Counters

There are no specific counters associated with this feature.

WCDMA RAN

IMSI-based Handover 7 Glossary



7-1

7 Glossary

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

Glossary.htm

WCDMA RAN

IMSI-based Handover 8 Reference Documents



8-1

8 Reference Documents

[1] 3GPP TS 25.413: UTRAN Iu interface RANAP Signalling

[2] 3GPP TS 25.423: UTRAN Iur Interface RNSAP Signalling