IMSI Based Handover

5/20/2018 IMSI Based Handover

1/27

WCDMA RAN

IMSI-based HandoverFeature Parameter Description

Copyright Huawei Technolog ies Co., Ltd. 2010. All righ ts 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 the property of Huawei Technologies Co., Ltd. All other trademarksand trade names mentioned in this document are the property of their respective holders.

Notice

The purchased products, services and features are stipulated by the commercial contract made between

Huawei and the customer. All or partial products, services and features described in this document may not be

within the purchased scope or the usage scope. Unless otherwise agreed by 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, andrecommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd


2/27


3/27

WCDMA RAN

IMSI-based Handover Contents

Issue 01 (2010-03-30) Huawei Proprietary and Confidential


iii

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 Descrip tion ..............................................................................................................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


4/27


5/27

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 notdescribed in the earlier version.

Document Issues

The document issues are as follows:

01 (2010-03-30)

Draft (2009-12-05)

01 (2010-03-30)

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

Compared with issue Draft (2009-12-05) of RAN12.0, this issue optimizes the description.

Draft (2009-12-05)

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

Compared with 02 (2009-06-30) of RAN11.0, this issue incorporates the following feature changes.

Change Type Change Descrip tion Parameter Change

Feature change Principles of shared network support in connected mode isadded.

None.

Editorial change None. None.


6/27


7/27

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 beimplemented 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 ornot the UE is allowed to access the new SNA in compliance with the previously configured mappingbetween IMSIs and SNAs. If the RNC decides that the UE is not allowed to access the new SNA, thenthe UE cannot access the network in that area.

With this feature, the RNC can prevent the UE in connected mode from being moved to anun-subscribed area without CN support. This feature can also be used as a supplement for implementingshared networks solutions.


8/27


9/27

WCDMA RAN

IMSI-based Handover 3 Technical Description



3-1

3 Technical Description

This part will describe the princples of shared network support in connected mode and IMSI-basedhandover 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 inConnected Mode) enables the RNC to obtain shared network parameters and work with the CN to applythe access control over the UE in connected mode to the specified location area. This feature cansupport operation applications for network sharing solutions.

Based on R99 specifications, when the UE is in idle mode, the CN+UTRAN have mechanisms availableto provide UE-specific access restrictions for LAs of the current PLMN and other PLMNs by usingroaming agreement. But there is no mechanism to restrict UE behavior in connected mode, sinceUTRAN 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 connectedmode from the messages and information elements (IE), which are defined in 3GPP TS 25.413 and25.423 including:

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

The information of the SNAs that the LAs belong to, which is from CN through INFORMATIONTRANSFER message or from DRNC through RADIO LINK SETUP RESPONSE and UPLINKSIGNALING 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 newnetwork 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 toaccess 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.

HandoverDuring the soft handover or the hard handover, the RNC does not send measurement controlindication if the UE is not allowed to access a cell. Therefore, the UE does not trigger a measurementreport 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 theUE 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 RRCconnection is released.


10/27


WCDMA RAN

IMSI-based Handover

3-2 Huawei Proprietary and Confidential


Issue 01 (2010-03-30)

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

You may enable the feature by setting the switch 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 appliedwhen 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 ofIMSI-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 mayconsist of multiple LAs, and one LA may belong to multiple SNAs.

Figure 3-1shows 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 MCCand 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 therange are configured together. The range is set by ImsiMinand ImsiMax.

The IMSI ranges can be set the same but cannot overlap each other.


11/27

WCDMA RAN

IMSI-based Handover 3 Technical Description



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 existsbetween the SNA to which the LA of the target cell belongs and the SNA that the UE (that is, the IMSI) isallowed 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 correspondsto 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 controlon 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 RRCCONNECTION REQUEST message.

If this message carries IMSI information, the RNC decides whether to allow the UE to access the cellor 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 CONNECTIONREJECT 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 thetarget 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.


12/27


WCDMA RAN

IMSI-based Handover



Issue 01 (2010-03-30)

3.3.4 Handover

During a soft handover or a hard handover, the RNC does not send a MEASUREMENT CONTROLmessage if the UE does not have access to a cell. Therefore, the UE does not trigger a measurementreport 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 blindhandover is triggered.

3.3.5 Relocation

When the Target RNC receives a RELOCATION REQUEST message, it decides whether the UE hasaccess 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 whetherthe 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.


13/27

WCDMA RAN

IMSI-based Handover 4 Engineering Guidelines



4-1

4 Engineering Guidelines

The subparameter RNCAP_IMSI_HO_SWITCHof PROCESSSWITCHcontrols the functionality ofIMSI-based handover. The subparameter can be set on through the command SET RRCTRLSWITCH.


14/27


15/27

WCDMA RAN

IMSI-based Handover 5 Parameters



5-1

5 Parameters

Table 5-1 Parameter description

ParameterID NE MML Descrip tion

LAC BSC6900

ADDUCBSAREA(Mandatory)

Meaning: Code of a location area, where the MS canmove without location update. Proper division of locationarea facilitates load balance, and improves call setupsuccess rate. This parameter is presented in hexadecimalformat, for example, H'1214.

GUI Value Range: 1~65533,65535Actual Value Range: 1~65533, 65535Unit: NoneDefault Value: None

LAC BSC6900

RMVUCBSAREA(Mandatory)

Meaning: Code of a location area, where the MS canmove without location update. Proper division of locationarea facilitates load balance, and improves call setupsuccess rate. This parameter is presented in hexadecimalformat, for example, H'1214.


LAC BSC69

00

MOD

UCELLACINFO(Optional)

Meaning: Identifies a location area code for a Public Land

Mobile Network (PLMN) of the GSM-MAP type. It isdefined by the operator. For detailed information aboutthis parameter, see 3GPP TS 23.003.

GUI Value Range: 1~65533,65535Actual Value Range: {1~65533}, {65535}Unit: NoneDefault Value: None

LAC BSC6900

ADDUCELLQUICKSETUP(Mandator

y)

Meaning: Identifies a location area code for a Public LandMobile Network (PLMN) of the GSM-MAP type. It isdefined by the operator. For detailed information about

this parameter, see 3GPP TS 23.003.



16/27

5 Parameters

WCDMA RAN

IMSI-based Handover



Issue 01 (2010-03-30)

Parameter NE MML DescriptionID

LAC BSC6900

ADDUCELLSETUP(Mandatory)

Meaning: Identifies a location area code for a Public LandMobile Network (PLMN) of the GSM-MAP type. It isdefined by the operator. For detailed information aboutthis parameter, see 3GPP TS 23.003.


LAC BSC6900

ADDUCZ(Mandatory)



LAC BSC6900

ADDUEXT2GCELL(Mandatory)MODUEXT2GCELL(Optional)

Meaning: Location Area Code (LAC) of the GSM cell.Note: H'0000 and H'FFFE are reserved values.


LAC BSC6900


Meaning: This parameter identifies a location area code.


LAC BSC6900

ADDULAC(Mandatory)RMVULAC(Mandatory)



LAC BSC6900

ADDULASNAMAP(Mandatory)

Meaning: Identifies a location area code for a Public LandMobile Network (PLMN) of the GSM-MAP type. It isdefined by the operator. For detailed information aboutthis parameter, see 3GPP TS 23.003.GUI Value Range: 1~65533,65535Actual Value Range: {1~65533}, {65535}Unit: None

Default Value: None


17/27

WCDMA RAN




5-3


LAC BSC6900

RMVULASNAMAP(Mandatory)

Meaning: Identifying a location area within the PLMN ofGSM-MAP type. It is defined by the operator. H'0000 andH'FFFE are reserved.


LAC BSC6900

MODUPLMNVALTAGRANGE(Mandatory)

Meaning: Identifying a location area within the PLMN ofGSM-MAP type. It is defined by the operator. H'0000 andH'FFFE are reserved.

GUI Value Range: 1~65533,65535

Actual Value Range: {{1~65533}, {65535}}Unit: NoneDefault Value: None

LAC BSC6900

ADDURAC(Mandatory)RMVURAC(Mandatory)



LAC BSC6900

ADDUSAC(Mandatory)RMVUSAC(Mandatory)



SNAC BSC6900

ADDUIMSISNAMAP(Mandatory)RMVUIMSISNAMAP(Mandatory)

Meaning: Sharing Network Area Code.

GUI Value Range: 0~65535Actual Value Range: 0~65535Unit: NoneDefault Value: None

SNAC BSC6900

ADDULASNAMAP(Mandatory)RMVULASNAMAP(Mandatory)

Meaning: Sharing Network Area Code.

GUI Value Range: 0~65535Actual Value Range: 0~65535Unit: NoneDefault Value: None


18/27

5 Parameters

WCDMA RAN

IMSI-based Handover



Issue 01 (2010-03-30)


ImsiMin BSC6900


Meaning: The minimum of one IMSI range.

GUI Value Range: NoneActual Value Range: 15-bit decimal numeralsUnit: NoneDefault Value: None

ImsiMax BSC6900


Meaning: The maximum of one IMSI range.

GUI Value Range: NoneActual Value Range: 15-bit decimal numeralsUnit: NoneDefault Value: None

SnaExistInd BSC6900 ADDUIMSISNAMAP(Mandatory)RMVUIMSISNAMAP(Mandatory)

Meaning: Indicating whether the SNAC need beconfigured.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, FALSEActual Value Range: TRUE, FALSEUnit: NoneDefault Value: None

PROCESSSWITCH

BSC6900

SETURRCTRLSWIT

CH(Optional)

Meaning: 1) INVOKE_TRACE_SWITCH. When it ischecked, RNC will start Invoke Trace procedure upon

receiving INVOKE TRACE Message form CN, otherwise,RNC won't start the Invoke Trace procedure though itreceives the INVOKE TRACE message.2) SYS_INFO_UPDATE_FOR_IU_RST. When it ischecked, RNC will broadcast SYSTEM INFORMATIONmessages to UE when Iu reset, otherwise, RNC won'tbroadcast SYSTEM INFORMATION messages to UEwhen IU reset.3) DRNC_DIRECT_DSCR. When it is checked, DRNCwill start DSCR procedure directly in RRC states otherthan CELL_DCH, otherwise, DRNC will transfer RRCCELL UPDATE message to SRNC.

4) RNC_SHARE_SWITCH. When it is checked, RNCtraffic share function will be valid, otherwise, RNC trafficfunction cannot be used.5)RNCAP_IMSI_HO_SWITCH.When it is checked, Imsihandover function will be used,otherwise it will be notused.6) TERMINAL_VERSION_DEBASE_SWITCH. When it ischecked, terminal version R4 will debase to R99.7)SYS_HO_OUT_CIPHER_SWITCH.When it ischecked ,the RNC will add ciphering byte at GSMHANDOVER COMMAND if the GSM system do not addany cipher information at that message.8)SYS_HO_CIPHER_CONFIG.When it is checked , thecipher configuration in the added cipher byte in GSM will


19/27

WCDMA RAN




5-5


be A5/1.When it is no checked ,the cipher configuration isA5/0.

9)BARRED_CELL_FOR_CSDOMAIN_RST.When it ischecked, cell will be bared when CS domain is invalid,otherwise the CS domain will be bared when CS domainis invalid. It is invalid IfSYS_INFO_UPDATE_FOR_IU_RST is not checked.10)CR2284R1_SWITCH.in section 8.6.6.28 of TS25.331of R5 Before 2006, it describes that the HFN should addone when UE is ciphering in the situation of Timingre-initialized hard handover,while not specified in RBSETUP process in the section of 8.6.4.3. so it is not clearwhether 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 thisCR2284R1.11)CR2284R1_COMPATIBLE_SWITCH.CR2284R1causes the compatible problem.if UE is not consistentwith RNC regarding whether accept the CR2284R1 ornot,it will cause the problem of streaming when UEs arecommunicating with each other.So RNC creates thisswitch .when it is checked, RNC is auto-adaptive to accept theCR2284R1 according to UE version information.

The principles that RNC judges UE whether toaccept 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 UEaccepts the CR;

R99/R4 UE ,if it only receives the START valuefrom RB SETUP COMPLETE,RNC figures that UE doesnot accept the CR ;when it is not checked, whether RNC accept the CR ornot is according to CR2284R1_SWITCH.The relations between these two switchesCR2284R1_SWITCH and

CR2284R1_COMPATIBLE_SWITCH are as follows:(1)CR2284R1_COMPATIBLE_SWITCH is checked, RNCis 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,CDTtrace function which starts tracing from message RRCCONNECT REQUEST.13)COMBINE_OPERATION_DRD_SWITCH.When it ison,RNC will not reject the message RB SETUP CMPwithout the IE active time.14)UL_INTER_PROTECT_SWITCH.When the switch is

off,RNC will not do integrity protection check for


20/27

5 Parameters

WCDMA RAN

IMSI-based Handover



Issue 01 (2010-03-30)


uplink RRC messages.15)SYS_HO_IN_CIPHER_SWITCH.When it is checked,

don't receive the encrypted ability infomation fromRELOC REQ ,default configured of encrypted parameterare UIA1 and UEA0.16)UPLINK_MDC_ENHENCEMENT_SWITCH.When it ischecked ,uplink MDC enhancement function will be used.17)NODEB_PRIVATE_INTERFACE_SWITCH.When it ischecked ,the NodeB private interface data can be takento the NodeB or DRNC through the IUB or IUR protocolmessage.18)RNC_QUERY_UE_IMEI_SWITCH.when it ischecked,RNC send Identity Request Message to UE andsave the IMEI information of UE if RNC receive the

Identity Response Message.

GUI Value Range: INVOKE_TRACE_SWITCH,SYS_INFO_UPDATE_FOR_IU_RST,DRNC_DIRECT_DSCR, 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,SYS_HO_IN_CIPHER_SWITCH,UPLINK_MDC_ENHENCEMENT_SWITCH,NODEB_PRIVATE_INTERFACE_SWITCHActual Value Range: This parameter is set to 0 or 1according to the related domains.Unit: NoneDefault Value: None

MCC BSC6900

ADDUCNOPERATOR(Mandatory)

Meaning: Mobile country code. This parameter identifiesthe country where a mobile subscriber is located, forexample, the Chinese MCC is 460.

GUI Value Range: NoneActual Value Range: 3 digitUnit: NoneDefault Value: None

MCC BSC6900


Meaning: The code of the country to which the RNCbelongs.

GUI Value Range: NoneActual Value Range: 000~999Unit: NoneDefault Value: None


21/27

WCDMA RAN




5-7


MCC BSC6900

ADDUIMSISNAMAP(Mandatory)



MCC BSC6900

RMVUIMSISNAMAP(Mandatory)


GUI Value Range: NoneActual Value Range: 000~999

Unit: NoneDefault Value: None

MCC BSC6900

ADDULASNAMAP(Mandatory)



MCC BSC69

00

RMV

ULASNAMAP(Mandatory)

Meaning: The code of the country to which the RNC

belongs.


MCC BSC6900

SETUMBMSPERF(Mandatory)



MNC BSC6900

ADDUCNOPERATOR(Mandatory)

Meaning: Mobile network code. This parameter identifiesthe public land mobile network (PLMN) where a mobilesubscriber is homed.

GUI Value Range: NoneActual Value Range: 2~3 digitUnit: NoneDefault Value: None


22/27

5 Parameters

WCDMA RAN

IMSI-based Handover



Issue 01 (2010-03-30)


MNC BSC6900


Meaning: The code of the mobile communication networkto which the RNC belongs.

GUI Value Range: NoneActual Value Range: 00~99, 000~999Unit: NoneDefault Value: None

MNC BSC6900

ADDUIMSISNAMAP(Mandatory)

Meaning: Mobile network code. This parameter identifiesthe public land mobile network (PLMN) where a mobilesubscriber is homed.

GUI Value Range: NoneActual Value Range: 2~3 digit

Unit: NoneDefault Value: None

MNC BSC6900

RMVUIMSISNAMAP(Mandatory)



MNC BSC6900

ADDULASNAMAP(M

andatory)

Meaning: Mobile network code. This parameter identifiesthe public land mobile network (PLMN) where a mobile

subscriber is homed.

GUI Value Range: NoneActual Value Range: 2~3 digitUnit: NoneDefault Value: None

MNC BSC6900

RMVULASNAMAP(Mandatory)



MNC BSC6900

SETUMBMSPERF(Mandatory)




23/27

WCDMA RAN

IMSI-based Handover 6 Counters



6-1

6 Counters

For details, see the BSC6900 UMTS Performance Counter Reference.


24/27


25/27

WCDMA RAN

IMSI-based Handover 7 Glossary



7-1

7 Glossary

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


26/27


27/27

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

IMSI Based Handover

Documents

Transcript of IMSI Based Handover