IMSI-based Handover(RAN15.0_Draft a)

IMSI-based Handover RAN15.0

Feature Parameter Description

Issue

Draft A

Date

2013-01-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2013. 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]

Copyright © Huawei Technologies Co., Ltd. 2013. 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]

WCDMA RAN IMSI-based Handover

Contents

Contents ................................................................... ............................................ ............................................ ............................................. ......................... ..1-1 1.1 Scope ............................................. ................................................................. ............................................ ............................................. ......................... ..1-1 1.2 Intended I ntended Audience ........................................... ................................................................... ............................................ ............................................. ............................. ......1-1 1.3 Change History ............................................. ......................................3-1 3.1 Principles of Shared Network Support in Connected Mode ...................................... ................................................................. ........................................ .................3-2 3.2 Principles of IMSI-Based Handover .......................................... .............................................................. ..................3-3 3.3 Signaling Procedure of IMSI-Based Handover ............................................ ............................................................... ............................................. ............................................ .....................4-1 4.1 IMSI Based Handover ......................................... ............................................................... .....................4-3 4.2 Shared Network Support in Connected Mode ..........................................

Issue Draft A (2013-01-30)

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

i


1 Introduction

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

Draft A (2013-01-30)

Draft A(2013-01-30) This is the first draft of the document for RAN15.0. Compared with issue 02 (2012-07-20) of RAN14.0, this issue optimizes some descriptions.



1-1


2 Overview of IMSI-based Handover

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.



2-1


3 Technical Description

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 areas (SNAs), 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.



3-1



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 H o S w i t c h > 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 M CC and L A C . Each SNA is identified by S N A C .

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 I m s i M i n and I m s i M a x .

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



3-2



The SNA that the UE is allowed to access is specified by the combination of the following parameters: M CC , M NC , S n a E x i s t I n d , and S N A C .

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. The maximum number of different PLMNs in the SNA configuration is 6.

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.



3-3



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.



3-4


4 Engineering Guideline

4 Engineering Guideline 4.1 IMSI Based Handover This section describes how to activate, verify, and deactivate the optional feature WRFD-021303 IMSI Based Handover.

4.1.1 Prerequisites 

Dependencies on Hardware − This



Dependencies on Other Features − This



feature does not depend on the hardware. feature does not depend on other features.

License

The license " IMSI Based Handover" on the RNC side has been activated. For details about the license items and how to activate the license, see License Management Feature Parameter Description.

4.1.2 Procedure Activation Procedure 1. Run the RNC MML command SET URRCTRLSWITCH (CME single configuration: UMTS Radio Global Configuration Express > Process Switch Configuration > Process Switch; CME batch modification center: Modifying RNC Parameters in Batches). In this step, select RNCAP_IMSI_HO_SWITCH under the Process switch parameter to switch on IMSI Based Handover. 2. Run the RNC MML command ADD ULASNAMAP (CME single configuration: UMTS Global Configuration Express > Radio Basic Data Configuration > Mapping of LAC to SNA; CME batch modification center: not supported). In this step, set PLMN to 46000, LAC to 1234, and SNAC to 1. 3. Run the RNC MML command ADD UIMSISNAMAP (CME single configuration: UMTS Global Configuration Express > Radio Basic Data Configuration > Mapping of IMSI to SNA; CME batch modification center: not supported) to add an IMSI-to-SNA mapping relationship. In this step, set The start of IMSI to 460071234000000, The end of IMSI to 460071234500000, PLMN to 46000, and SNAC to 1.

Verification Procedure 1. Use the UE with the IMSI of 460071234000006 to access the cell with the LAC of H'1234. The UE is admitted to the cell. 2. Use the UE with the IMSI of 460071234000006 to access the cell with the LAC of H'1235. The LAC of H'1235 is mapped onto an SNA other than SNA 1. The IMSI of 460071234000006 is not within the IMSI range configured for the SNA. The UE is rejected by the cell. In this case, you can view the RRC CONNECTION REJECT message on the Uu interface. The restrictions on cell update, UTRAN registration area (URA) update, handovers, relocations, and handling COMMON ID messages are the same as that on RRC connection request.



4-1



Deactivation Procedure 1. Run the RNC MML command SET URRCTRLSWITCH (CME single configuration: UMTS Radio Global Configuration Express > Process Switch Configuration > Process Switch; CME batch modification center: Modifying RNC Parameters in Batches). In this step, clear RNCAP_IMSI_HO_SWITCH under the Process switch parameter to switch off IMSI Based Handover. 2. Run the RNC MML command RMV ULASNAMAP (CME single configuration: UMTS Global Configuration Express > Radio Basic Data Configuration > Mapping of LAC to SNA; CME batch modification center: not supported) to remove a mapping relationship between LAC and SNA. 3. Run the RNC MML command RMV UIMSISNAMAP (CME single configuration: UMTS Global Configuration Express > Radio Basic Data Configuration > Mapping of IMSI to SNA; CME batch modification center: not supported) to remove a mapping relationship between IMSI and SNA.

4.1.3 Example //Activating IMSI-Based Handover

//Enabling IMSI-Based Handover SET URRCTRLSWITCH: PROCESSSWITCH = RNCAP_IMSI_HO_SWITCH-1;

//Adding PLMN, LAN, and SNAC ADD ULASNAMAP: MCC="460", MNC="00", LAC=H'1234, SNAC=1;

//Adding the PLMN and SNAC of the SNA ADD UIMSISNAMAP: ImsiMin = "460071234000000", ImsiMax = "460071234500000" , MCC="460", MNC="07", SnaExistInd=TRUE, SNAC=1;

//Deactivating IMSI-Based Handover

//Switching off IMSI-based handover

SET URRCTRLSWITCH: PROCESSSWITCH = RNCAP_IMSI_HO_SWITCH-0;

//Removing a mapping relationship between IMSI and SNA RMV ULASNAMAP: MCC="460", MNC="00", LAC=1234, SNAC=1;

//Removing a mapping relationship between IMSI and SNA RMV UIMSISNAMAP: ImsiMin="460071234000000", ImsiMax="460071234500000", MCC="460", MNC="07", SnaExistInd=TRUE, SNAC=1;



4-2



4.2 Shared Network Support in Connected Mode This section describes how to activate, verify, and deactivate the basic feature WRFD-021301 Shared Network Support in Connected Mode. (This feature cannot be configured using the CME. )

4.2.1 Prerequisites 

Dependencies on Hardware − This



Dependencies on Other Features − This



feature does not depend on other features.

License − This



feature does not have any special requirements for hardware.

feature is not under license control.

Other Prerequisites − The

CN supports the shared network area (SNA) function.

4.2.2 Procedure Activation Procedure 1. For the CS service, configure two SNAs (for example, SNA1 and SNA2) on the MSC. 2. For the PS service, run the MML command ADD SNA on the SGSN to add SNA, SNA1, and SNA2. 3. Run the RNC MML command MOD UCELLACINFO to modify the RACs of CELL1 and CELL2. 4. Set up a cell. For details, see the RNC UMTS Initial Configuration Guide. 5. Run the RNC MML command SET UCORRMALGOSWITCH to enable the SNA function.

Verifying the SNA Function of the CS Service 1.

On the RNC LMT, click Trace > UMTS Services, and then double-click Iu Interface Trace. The Iu Interface Trace dialog box is displayed.

2. Keep UE1 and UE2 in idle mode in CELL1. 3. Run the RNC MML command SET UCORRMALGOSWITCH to disable the SNA function. 4. Use UE1 to call UE2. The RANAP_COMMON_ID message from UE1 should be displayed in Iu trace data, and it should include the SNA ACCESS information IE. 5. Move UE1 to CELL2 to trigger soft handover. The RRC_ACTIVE_SET_UPDATE message from the RNC to UE1 and the RRC_ACTIVE_SET_UPDATE_CMP message from UE1 to the RNC should be displayed in Uu trace data. 6. End the calling. UE1 and UE2 return to the idle mode in CELL1. 7. Run the RNC MML command SET UCORRMALGOSWITCH to enable the SNA function. 8. Add a mapping relationship between IMSI of UE1 and SNA1 on the MSC. 9. Use UE1 to call UE2. The RANAP_COMMON_ID message from UE1 should be displayed in Iu trace data, and it should include the SNA ACCESS information IE. CELL2 belongs to SNA2 but not SNA1. Therefore, the RRC_MEAS_CTRL message sent from the RNC to UE1 on the Uu interface should indicate that CELL2 is not in the monitoring cell.

10. Move UE1 to CELL2, which will not trigger soft handover because UE1 does not belong to SNA_2. 11. End the calling. UE1 and UE2 return to the idle mode in CELL1.



4-3



Verifying the SNA Function of the PS Service 1. Run the MML command ADD SNA on the SGSN to add SNA information. 2. Run the RNC MML command SET UCORRMALGOSWITCH to disable the SNA function. 3. Keep the UE in idle mode in CELL1. 4. Establish a PS service on UE1. The RANAP_COMMON_ID message from UE1 should be displayed in Iu trace data, and it should include the SNA ACCESS information IE. 5. Move UE1 to CELL2 to trigger soft handover. The RRC_ACTIVE_SET_UPDATE message from the RNC to UE1 and the RRC_ACTIVE_SET_UPDATE_CMP message from UE1 to the RNC should be displayed in Uu trace data. 6. End the PS service of UE1. UE1 returns to the idle mode in CELL1. 7. Run the RNC MML command SET UCORRMALGOSWITCH to enable the SNA function. 8. Establish a PS service on UE1. The RANAP_COMMON_ID message from UE1 should be displayed in Iu trace data, and it should include the SNA ACCESS information IE. 9. CELL2 belongs to SNA2 but not SNA1. Therefore, the RRC_MEAS_CTRL message sent from the RNC to UE1 on the Uu interface should indicate that CELL2 is not in the monitoring set. 10. Move UE1 to CELL2, which will not trigger soft handover because UE1 does not belong to SNA_2. 11. End the PS service of UE1. UE1 returns to the idle mode in CELL1.

Deactivation Procedure 1. Run the RNC MML command SET UCORRMALGOSWITCH to disable the SNA function.

4.2.3 Example //Adding two SNAs (for example, SNA1 and SNA2) on the MSC ADD LOCNOLAI: LOCNONAME="SNA_1", LAI="460020001"; ADD LOCSNA: LOCNONAME=" SNA_1", SNAC=1; ADD SNAGRPCODE: SNAGRPN="1", SNAC=1; ADD LOCNOLAI: LOCNONAME="SNA_2", LAI="460020002"; ADD LOCSNA: LOCNONAME=" SNA_2", SNAC=2; ADD SNAGRPCODE: SNAGRPN="2", SNAC=2; //Activating the SNA function of the CS Service MOD UCELLACINFO: CellId=1, LAC=1, SAC=0, CfgRacInd=REQUIRE, RAC=1; MOD UCELLACINFO: CellId=2, LAC=2, SAC=0, CfgRacInd=REQUIRE, RAC=2; SET UCORRMALGOSWITCH: HoSwitch=HO_MC_SNA_RESTRICTION_SWITCH-1; //Verifying the SNA function of the CS Service SET UCORRMALGOSWITCH: HoSwitch=HO_MC_SNA_RESTRICTION_SWITCH-0; SET UCORRMALGOSWITCH: HoSwitch=HO_MC_SNA_RESTRICTION_SWITCH-1; ///Add a mapping relationship between IMSI and SNA1 on the MSC ADD IMSIGRP: IMSIPRE=K'460071104008338, MCCMNC1=K'46002, SNAGRPN1="1"; MOD RNC: RNCID=1, CAPABILITY=SNA-1; //Deactivating the SNA function SET UCORRMALGOSWITCH: HoSwitch=HO_MC_SNA_RESTRICTION_SWITCH-0; //Adding two SNAs (for example, SNA1 and SNA2) on the SGSN ADD SNA: PLMN="46002", LAC="1", SNAC=1; ADD SNA: PLMN="46002", LAC="2", SNAC=2;



4-4



//Activating the SNA function of the PS Service MOD UCELLACINFO: CellId=1, LAC=1, SAC=0, CfgRacInd=REQUIRE, RAC=1; MOD UCELLACINFO: CellId=2, LAC=2, SAC=0, CfgRacInd=REQUIRE, RAC=2; SET UCORRMALGOSWITCH: HoSwitch=HO_MC_SNA_RESTRICTION_SWITCH-1; //Adding SNA information on the SGSN ADD SNAA: BEGIMSI="460071104008338", ENDIMSI="460071104008338", PLMN="46002", SNAC=1; //Verifying the SNA function of the PS Service SET UCORRMALGOSWITCH: HoSwitch=HO_MC_SNA_RESTRICTION_SWITCH-0; SET UCORRMALGOSWITCH: HoSwitch=HO_MC_SNA_RESTRICTION_SWITCH-1; //Deactivating the SNA function SET UCORRMALGOSWITCH: HoSwitch=HO_MC_SNA_RESTRICTION_SWITCH-0;



4-5


5 Parameters

5 Parameters Table 5-1 Parameter description Paramete NE r ID

MML Command Feature ID

Feature Name Description

HoSwitch BSC6900/ SET WRFD-010610 HSDPA Meaning:1. BSC6910 UCORRMALGOS Introduction HO_ALGO_HCS_SPEED_EST WRFD-010610 Package WITCH _SWITCH: When the switch is 06 on, the RNC evaluates the UE's HSDPA Mobility moving speed in the HCS and WRFD-010612 Management initiates fast intra-layer or slow WRFD-010612 HSUPA 04 Introduction

inter-layer handover.

2. HO_ALGO_LDR_ALLOW_SH O_SWITCH: When the switch is WRFD-020201 HSUPA Mobility on, the LDR inter-frequency Management handover is allowed during soft WRFD-020202 Inter Frequency handover. WRFD-020203 Load Balance 3. WRFD-020301 Intra Node B HO_ALGO_MBMS_FLC_SWIT Softer Handover CH: When the switch is on, the WRFD-020302 UE requires that the redirection Intra RNC Soft strategy be used for frequency WRFD-020303 Handover layer convergence. WRFD-020304 Inter RNC Soft 4. WRFD-020305 Handover HO_ALGO_OVERLAY_SWITC H: When the switch is on, the WRFD-020306 Intra Frequency associated receiving and Hard Handover mobility algorithms of the WRFD-020308 Inter Frequency overlay network are used. WRFD-020308 Hard Handover When the switch is not on, the 01 Based on associated algorithms are not Coverage used. Overlay network is an WRFD-020308 UTRAN network covering 02 Inter-RAT present network, it supports Handover HSPA, MBMS and other new WRFD-020309 Based on features. To satisfy new Coverage WRFD-021200 requirements of operator and restrictions of present network, WRFD-020129 Inter Frequency overlay network realizes Hard Handover operation distribution and load WRFD-070005 Based on DL sharing between new network QoS WRFD-070006 and present network, also gives Inter-RAT special handling for mobility WRFD-070007 Handover management of network verge. Based on WRFD-020106 5. Service HO_INTER_FREQ_HARD_HO WRFD-140102 Inter-RAT _SWITCH: When the switch is Handover on, the RNC is allowed to initiate inter-frequency measure WRFD-020103 Package



5-1


Paramete NE r ID

5 Parameters


Feature Name Description Based on Load control or the load-based inter-frequency hard handover Inter-RAT upon the handover decision on Handover inter-frequency load. Phase 2 6. NACC(Network HO_LTE_SERVICE_PSHO_O Assisted Cell UT_SWITCH: Whether to Change) enable service-based PS handover from UMTS to LTE. PS Handover Between UMTS When this switch is turned on, the RNC can send LTE and GPRS MEASUREMENT CONTROL Inter-RAT message based on service and Handover initiate service-based PS Based on DL handover from UMTS to LTE. QoS When this switch is turned off, the RNC cannot initiate HCS service-based PS handover (Hierarchical from UMTS to LTE. Cell Structure) 7. PS Service HO_INTER_RAT_CS_OUT_S Redirection from WITCH: When the switch is on, UMTS to LTE the RNC is allowed to initiate inter-frequency measure NACC control and the CS inter-RAT Procedure hard handover from the 3G Optimization Based on Iur-g network to the 2G network. GSM and UMTS 8. Load Balancing HO_INTER_RAT_PS_3G2G_C Based on Iur-g ELLCHG_NACC_SWITCH: When the switch is on, the GSM and UMTS NACC function is supported Traffic Steering during the PS inter-RAT Based on Iur-g handover from the 3G network to the 2G network in the cell Load change order process. When Reshuffling the switch is not on, the NACC function is not supported. When CS Fallback Guarantee for PS_3G2G_RELOCATION_SWI LTE Emergency TCH is ON, this switch is useless. When the NACC Calls 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. 9. HO_INTER_RAT_PS_3G2G_R ELOCATION_SWITCH: When



5-2


Paramete NE r ID

5 Parameters


Feature Name Description 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. 10. HO_INTER_RAT_PS_OUT_S WITCH: 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. 11. HO_INTER_RAT_RNC_SERVI CE_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. 12. HO_INTRA_FREQ_DETSET_I NTO_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. 13. HO_INTRA_FREQ_DETSET_ RPRT_SWITCH: When the switch is on, the intra-frequency measurement reports of the detected set can be reported by UE. 14.



5-3


Paramete NE r ID

5 Parameters


Feature Name Description HO_INTRA_FREQ_HARD_HO _SWITCH: When the switch is on, the RNC is allowed to initiate the intra-frequency hard handover. 15. HO_INTRA_FREQ_RPRT_1J_ SWITCH: When the switch is on, the event 1J is included in the delivery of intra-frequency measurement control if the UE version is R6. 16. 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. 17. 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. 18. HO_MC_NCELL_COMBINE_S WITCH: 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. 19. 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. 20.



5-4


Paramete NE r ID

5 Parameters


Feature Name Description 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. 21. 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. 22. HO_LTE_PS_OUT_SWITCH: Whether to enable handover from UMTS to LTE. When this switch is turned on, the RNC can send LTE MEASUREMENT CONTROL message and initiate PS handover or redirection from UMTS to LTE. When this switch is turned off, the RNC cannot perform the preceding procedures. 23. HO_LTE_SERVICE_PS_OUT_ SWITCH: Whether to enable service-based redirection from UMTS to LTE. When this switch is turned on, the RNC can send LTE MEASUREMENT CONTROL message based on service and initiate service-based PS redirection from UMTS to LTE. When this switch is turned off, the RNC cannot initiate service-based PS redirection from UMTS to LTE. 24. HO_H2G_SRVCC_SWITCH :T his bit is a Single Radio Voice Call Continuity (SRVCC) switch



5-5


Paramete NE r ID

5 Parameters


Feature Name Description 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. 25. HO_INTRA_FREQ_HIGHPRIO R_2D2F_SWITCH: This switch controls which event to be preferentially processed when both an intra- frequency measurement report event and event 2D or 2F need to be processed. Turning on this switch allows the intra-frequency measurement report event to be preferentially processed. Turning off this switch allows event 2D or 2F to be preferentially processed. 26. HO_CIO_1D_USED: Whether the RNC instructs the UE to use the cell individual offset (CIO) parameter when reporting event 1D. If this field is selected, the RNC instructs the UE to use the CIO parameter when reporting event 1D. If this field is not selected, the RNC does not instruct the UE to use the CIO parameter when reporting event 1D. The call drop rate will increase if the switch is opened when the CIO is configured to a big value. 27. HO_HCS_SPD_INI_BSD_UE_ SWITCH: Whether the RNC



5-6


Paramete NE r ID

5 Parameters


Feature Name Description determines the initial speed state of a UE based on the enUeMobilityStateInd information element (IE) sent by the UE. If this switch is turned on, the initial UE speed state is determined by this IE carried in the RRC_RRC_CONNECT_REQ or RRC_CELL_UPDATE message. If this switch is turned off, the RNC determines the UE mobility state as before based on how frequently the UE sends an event 1D measurement report. 28. HO_L2U_EMGCALL_SWITCH: Whether to activate CS Fall Back. When this switch is turned on, CS Fall Back is activated. When this switch is turned off, CS Fall Back is deactivated. 29. HO_UMTS_TO_LTE_FAST_R ETURN_SWITCH: Switch for preferentially moving to an LTE cell after a call release. When this switch is turned on, the RNC includes the neighboring frequency information in the RRC CONNECTION RELEASE message for UEs that can measure signal quality of the frequency band including the LTE cells' frequencies. As a result of these operations, these UEs can preferentially move to LTE cells after entering the idle state. 30. HO_HHO_WITH_INTRA_FRE Q_MR_SWITCH: When this switch is turned on, the RNC sends periodical inter-frequency and intra-frequency measurement control messages, and includes the information element (IE)



5-7


Paramete NE r ID

5 Parameters


Feature Name Description measurementIdentiy in the inter-frequency measurement control message to instruct a UE to report signal quality in an active set cell in a periodical inter-frequency measurement report. When this switch is turned off, the RNC sends only a periodical inter-frequency measurement control message without this IE. 31. HO_MULTIRAB_CSPS_HO_C OV_PARA_SWITCH (Algorithm Switch for Coverage-based Inter-frequency or inter-RAT Handover Parameters Dedicated to CS and PS Combined Services): When this switch is turned on, the handover parameters dedicated to CS and PS combined services are used when CS and PS combined services are processed. When this switch is turned off, the thresholds for CS or PS services, whichever are larger, are used for the handover parameters. GUI Value Range:HO_ALGO_HCS_SPEE D_EST_SWITCH, HO_ALGO_LDR_ALLOW_SH O_SWITCH, HO_ALGO_MBMS_FLC_SWIT CH, HO_ALGO_OVERLAY_SWITC H, HO_INTER_FREQ_HARD_HO _SWITCH, HO_LTE_SERVICE_PSHO_O UT_SWITCH, HO_INTER_RAT_CS_OUT_S WITCH, HO_INTER_RAT_PS_3G2G_C ELLCHG_NACC_SWITCH, HO_INTER_RAT_PS_3G2G_R ELOCATION_SWITCH, HO_INTER_RAT_PS_OUT_S WITCH, HO_INTER_RAT_RNC_SERVI



5-8


Paramete NE r ID

5 Parameters


Feature Name Description CE_HO_SWITCH, HO_INTRA_FREQ_DETSET_I NTO_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_S WITCH, 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, HO_INTRA_FREQ_HIGHPRIO R_2D2F_SWITCH, HO_CIO_1D_USED, HO_HCS_SPD_INI_BSD_UE_ SWITCH, HO_L2U_EMGCALL_SWITCH, HO_UMTS_TO_LTE_FAST_R ETURN_SWITCH, HO_HHO_WITH_INTRA_FRE Q_MR_SWITCH, HO_MULTIRAB_CSPS_HO_C OV_PARA_SWITCH Actual Value Range:HO_ALGO_HCS_SPEE D_EST_SWITCH, HO_ALGO_LDR_ALLOW_SH O_SWITCH, HO_ALGO_MBMS_FLC_SWIT CH, HO_ALGO_OVERLAY_SWITC H, HO_INTER_FREQ_HARD_HO _SWITCH, HO_LTE_SERVICE_PSHO_O UT_SWITCH, HO_INTER_RAT_CS_OUT_S WITCH, HO_INTER_RAT_PS_3G2G_C



5-9


Paramete NE r ID

5 Parameters


Feature Name Description ELLCHG_NACC_SWITCH, HO_INTER_RAT_PS_3G2G_R ELOCATION_SWITCH, HO_INTER_RAT_PS_OUT_S WITCH, HO_INTER_RAT_RNC_SERVI CE_HO_SWITCH, HO_INTRA_FREQ_DETSET_I NTO_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_S WITCH, 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, HO_INTRA_FREQ_HIGHPRIO R_2D2F_SWITCH, HO_CIO_1D_USED, HO_HCS_SPD_INI_BSD_UE_ SWITCH, HO_L2U_EMGCALL_SWITCH, HO_UMTS_TO_LTE_FAST_R ETURN_SWITCH, HO_HHO_WITH_INTRA_FRE Q_MR_SWITCH, HO_MULTIRAB_CSPS_HO_C OV_PARA_SWITCH Unit:None Default Value:HO_ALGO_HCS_SPEE D_EST_SWITCH-0&HO_ALG O_LDR_ALLOW_SHO_SWITC H-1&HO_ALGO_MBMS_FLC_ SWITCH-0&HO_ALGO_OVER LAY_SWITCH-0&HO_INTER_



5-10


Paramete NE r ID

5 Parameters


Feature Name Description FREQ_HARD_HO_SWITCH-0 &HO_LTE_SERVICE_PSHO_ OUT_SWITCH-0&HO_INTER_ RAT_CS_OUT_SWITCH-1&H O_INTER_RAT_PS_3G2G_CE LLCHG_NACC_SWITCH-0&H O_INTER_RAT_PS_3G2G_RE LOCATION_SWITCH-0&HO_I NTER_RAT_PS_OUT_SWITC H-1&HO_INTER_RAT_RNC_S ERVICE_HO_SWITCH-0&HO_ INTRA_FREQ_DETSET_INTO _ACTSET_SWITCH-1&HO_IN TRA_FREQ_DETSET_RPRT_ SWITCH-1&HO_INTRA_FREQ _HARD_HO_SWITCH-1&HO_I NTRA_FREQ_RPRT_1J_SWIT CH-0&HO_INTRA_FREQ_SOF T_HO_SWITCH-1&HO_MC_M EAS_BEYOND_UE_CAP_SWI TCH-0&HO_MC_NCELL_COM BINE_SWITCH-1&HO_MC_SI GNAL_IUR_INTRA_SWITCH-0 &HO_MC_SIGNAL_SWITCH-0 &HO_MC_SNA_RESTRICTIO N_SWITCH-0&HO_LTE_PS_O UT_SWITCH-0&HO_LTE_SER VICE_PS_OUT_SWITCH-0&H O_H2G_SRVCC_SWITCH-0& HO_INTRA_FREQ_HIGHPRIO R_2D2F_SWITCH-0&HO_CIO _1D_USED-0&HO_HCS_SPD_ INI_BSD_UE_SWITCH-0&HO_ L2U_EMGCALL_SWITCH-0&H O_UMTS_TO_LTE_FAST_RET URN_SWITCH-0&HO_HHO_W ITH_INTRA_FREQ_MR_SWIT CH-0&HO_MULTIRAB_CSPS_ HO_COV_PARA_SWITCH-0

ImsiMax

BSC6900/ ADD BSC6910 UIMSISNAMAP RMV UIMSISNAMAP

WRFD-021303 IMSI Based Handover

Meaning:The maximum of one IMSI range. GUI Value Range:15-bit decimal numerals Actual Value Range:15-bit decimal numerals Unit:None Default Value:None



5-11


Paramete NE r ID ImsiMin

5 Parameters


BSC6900/ ADD BSC6910 UIMSISNAMAP


WRFD-021303 IMSI Based Handover

RMV UIMSISNAMAP

Meaning:The minimum of one IMSI range. GUI Value Range:15-bit decimal numerals Actual Value Range:15-bit decimal numerals Unit:None Default Value:None

LAC

BSC6900/ ADD BSC6910 ULASNAMAP RMV ULASNAMAP

None

None

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 Unit:None Default Value:None

MCC


WRFD-021301 Shared Network Meaning:The code of the Support in country to which the RNC MRFD-211401 Connected belongs. MRFD-211402 Mode GUI Value Range:000~999 NACC MRFD-211403 Actual Value Range:000~999 Procedure MRFD-211404 Optimization Unit:None MRFD-211502 MBSC Load Default Value:None Balancing WRFD-021304 01 MBSC Service



5-12


Paramete NE r ID

5 Parameters



WRFD-021311 Distribution WRFD-070004 MBSC Handover based on Load Enhancement IP-Based BSC and RNC Co-Transmissio n on MBSC Side Dedicated Carrier for Each Operator MOCN Introduction Package Load Based GSM and UMTS Handover Enhancement Based on Iur-g MCC


WRFD-021301 Shared Network Meaning:The code of the Support in country to which the RNC MRFD-211401 Connected belongs. MRFD-211402 Mode GUI Value Range:000~999 MRFD-211403 NACC Actual Value Range:000~999 Procedure MRFD-211404 Optimization Unit:None MRFD-211502 MBSC Load Default Value:None Balancing WRFD-021304 01 MBSC Service Distribution WRFD-021311 MBSC WRFD-070004 Handover based on Load Enhancement IP-Based BSC and RNC Co-Transmissio n on MBSC Side Dedicated Carrier for Each Operator MOCN



5-13


Paramete NE r ID

5 Parameters


Feature Name Description Introduction Package Load Based GSM and UMTS Handover Enhancement Based on Iur-g

MNC


WRFD-021301 Shared Network Meaning:The code of the Support in mobile communication network MRFD-211401 Connected to which the RNC belongs. MRFD-211402 Mode GUI Value Range:00~99, 000~999 MRFD-211403 NACC Procedure Actual Value Range:00~99, MRFD-211404 Optimization 000~999 MRFD-211502 MBSC Load Unit:None Balancing WRFD-021304 01 MBSC Service Default Value:None Distribution WRFD-021311 MBSC WRFD-070004 Handover based on Load Enhancement IP-Based BSC and RNC Co-Transmissio n on MBSC Side Dedicated Carrier for Each Operator MOCN Introduction Package Load Based GSM and UMTS Handover Enhancement Based on Iur-g

SNAC


WRFD-021301 Shared Network Meaning:Sharing network area Support in code, used to mark a sharing Connected network area. Mode GUI Value Range:0~65535 Actual Value Range:0~65535



5-14


Paramete NE r ID

5 Parameters


Feature Name Description Unit:None Default Value:None

SNAC


WRFD-021301 Shared Network Meaning:Sharing network area Support in code, used to mark a sharing Connected network area. Mode GUI Value Range:0~65535 Actual Value Range:0~65535 Unit:None Default Value:None

SnaExistI BSC6900/ ADD nd BSC6910 UIMSISNAMAP RMV UIMSISNAMAP

WRFD-021301 Shared Network Meaning:Indicating whether the Support in SNAC need be configured. WRFD-021303 Connected TRUE: The SNAC need be Mode configured. IMSI Based FALSE: The SNAC need not be Handover configured. UE can access any cell of the PLMN. GUI Value Range:TRUE, FALSE Actual Value Range:TRUE, FALSE Unit:None Default Value:None



5-15


6 Counters

6 Counters There are no specific counters associated with this feature.



6-1


7 Glossary

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



7-1

IMSI-based Handover(RAN15.0_Draft a)

Recommend Documents