HO PD

RAN

Handover Parameter Description

Issue01

Date2009-03-30

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any assistance, please contact our local office or company headquarters.

Huawei Technologies Co., Ltd.

Address:Huawei Industrial BaseBantian, LonggangShenzhen 518129People's Republic of China

Website:http://www.huawei.com

Email:[email protected]

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

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

NoticeThe 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 Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

About This DocumentAuthorPrepared byHu Lianfang, Wang YiyunDate2008-10-20

Edited byWang DeyangDate2008-12-09

Reviewed by-Date-

Translated byTong ArunaDate2008-12-09

Tested byTang MinDate2009-01-10

Approved byDuan ZhongyiDate2009-03-30

RANHandover Parameter DescriptionAbout This Document

Issue 01 (2009-03-30)Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltdiii

Content1 Change History1-22 Handover Introduction2-23 Handover Overview3-23.1 Handover Types3-23.2 Intra-Frequency Handover3-23.3 Inter-Frequency Handover3-23.4 Inter-RAT Handover (3G to 2G)3-23.4.1 Inter-RAT Handover Introduction3-23.4.2 Rules for Enabling 3G-to-2G Handover3-24 Intra-Frequency Handover Algorithms4-24.1 Intra-Frequency Handover Procedure4-24.2 Intra-Frequency Handover Measurement4-24.2.1 Intra-Frequency Handover Measurement Quantities4-24.2.2 Intra-Frequency Handover Measurement Events4-24.2.3 Intra-Frequency Handover Neighboring Cell Combination Algorithm4-24.3 Intra-Frequency Handover Decision and Execution4-24.3.1 Decision and Execution4-24.3.2 Rate Reduction After an SHO Failure4-24.4 Intra-Frequency Handover of HSDPA4-24.4.1 Decision and Execution of Intra-Frequency Handover4-24.4.2 F-DPCH Handover Protection4-24.5 Intra-Frequency Handover of HSUPA4-24.5.1 Decision and Execution of Intra-Frequency Handover4-24.5.2 Handover Between E-DCHs of 10 ms TTI and 2 ms TTI4-24.6 Signaling Procedures for Intra-Frequency Handover4-24.6.1 Intra-NodeB Intra-Frequency Soft Handover Signaling Procedure4-24.6.2 Intra-RNC Inter-NodeB Intra-Frequency Soft Handover Signaling Procedure4-24.6.3 Inter-RNC Intra-Frequency Soft Handover Signaling Procedure4-24.6.4 Intra-RNC Inter-NodeB Intra-Frequency Hard Handover Signaling Procedure4-24.6.5 Inter-RNC Intra-Frequency Hard Handover Signaling Procedure4-25 Inter-Frequency Handover Algorithms5-25.1 Inter-Frequency Handover Procedure5-25.1.1 Coverage- or QoS-based Inter-Frequency and Inter-RAT Handover Procedure5-25.1.2 Load-based Inter-Frequency Handover Procedure5-25.1.3 Speed-based Inter-Frequency Handover Procedure5-25.2 Inter-Frequency Handover Measurement5-25.2.1 Inter-Frequency Handover Measurement Switches5-25.2.2 Inter-Frequency Handover Measurement Report Modes5-25.2.3 Inter-Frequency Handover Measurement Quantity5-25.2.4 Inter-Frequency Handover Measurement Events5-25.2.5 Inter-Frequency Handover Neighboring Cell Combination Algorithm5-25.2.6 Inter-Frequency Handover Compressed Mode5-25.3 Inter-Frequency Handover Decision and Execution5-25.3.1 Coverage- and QoS-based Inter-Frequency Handover Decision and Execution5-25.3.2 Load-based Inter-Frequency Handover Decision and Execution5-25.3.3 Speed-based Inter-Frequency Handover Decision and Execution5-25.3.4 Blind Handover Decision and Execution Based on Event 1F5-25.3.5 Inter-Frequency Anti-Ping-Pong Algorithm5-25.3.6 Inter-Frequency Handover Retry5-25.4 Inter-Frequency Handover of HSDPA5-25.5 Inter-Frequency Handover of HSUPA5-25.6 Signaling Procedures for Inter-Frequency Handover5-25.6.1 Inter-Frequency Handover Within One RNC5-25.6.2 Inter-Frequency Handover Between RNCs5-26 Inter-RAT Handover Algorithms6-26.1 3G-to-2G Handover Procedure6-26.1.1 Coverage-based 3G-to-2G Handover Procedure6-26.1.2 Load-based 3G-to-2G Handover Procedure6-26.1.3 Service-based 3G-to-2G Handover Procedure6-26.1.4 Speed-based 3G-to-2G Handover Procedure6-26.2 3G-to-2G Handover Measurement6-26.2.1 3G-to-2G Handover Measurement Switches6-26.2.2 3G-to-2G Handover Measurement Report Modes6-26.2.3 3G-to-2G Handover Measurement Quantity6-26.2.4 3G-to-2G Handover Measurement Events6-26.2.5 3G-to-2G Handover Neighboring Cell Combination Algorithms6-26.2.6 3G-to-2G Handover Compressed Mode6-26.2.7 BSIC Verification Requirements for 2G Cells6-26.3 3G-to-2G Handover Decision and Execution6-26.3.1 Coverage and QoS-based UMTS-to-GSM Handover Decision and Execution6-26.3.2 Load- and Service-based 3G-to-2G Handover Decision and Execution6-26.3.3 3G-to-2G Handover Retry6-26.3.4 3G-to-2G Multimedia Fallback6-26.3.5 3G-to-2G Handover in the PS Domain with NACC6-26.4 Inter-RAT Handover of HSDPA6-26.5 Inter-RAT Handover of HSUPA6-26.6 2G-to-3G Handover6-26.7 Interoperability Between Inter-RAT Handover and Inter-Frequency Handover6-26.8 Signaling Procedures for Inter-RAT Handover6-26.8.1 3G-to-2G Handover in CS Domain6-26.8.2 3G-to-2G Handover in PS Domain6-26.8.3 3G-to-2G Handover in Both CS Domain and PS Domain6-26.8.4 2G-to-3G Handover in CS Domain6-26.8.5 2G-to-3G Handover in PS Domain6-27 HCS Handover Algorithms7-27.1 HCS Handover Overview7-27.2 HCS Handover Phases7-27.2.1 UE Speed Estimation7-27.2.2 HCS Handover Execution7-27.3 Signaling Procedure of HCS Handover7-27.4 Interoperability Between HCS Handover and Other Handovers7-28 Handover Parameters8-28.1 Parameters Description8-28.2 Values and Ranges8-29 Reference Documents9-2

Content RANHandover Parameter Description

RANHandover Parameter DescriptionContent

viHuawei Proprietary and Confidential Copyright Huawei Technologies Co., LtdIssue 01 (2009-03-30)

Issue 01 (2009-03-30)Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltdvii

Change HistoryThe change history provides information on the changes in different document versions.Document and Product VersionsDocument VersionRAN Version

01 (2009-03-30)11.0

Draft (2009-03-10)11.0

Draft (2009-01-15)11.0

This document is based on the BSC6810 and 3900 series NodeBs.The available time of each feature is subject to the RAN product roadmap.There are two types of changes, which are defined as follows:Feature change: refers to the change in the handover feature.Editorial change: refers to the change in the information that was inappropriately described or the addition of the information that was not described in the earlier version.01 (2009-03-30)This is the document for the first commercial release of RAN11.0.Compared with draft (2009-03-10), this issue optimizes the description.Draft (2009-03-10)This is the second draft of the document for RAN11.0.Compared with draft (2009-01-15), draft (2009-03-10) optimizes the description.Draft (2009-01-15)This is the initial draft of the document for RAN11.0.Compared with issue 02 (2008-07-30) of RAN10.0, draft (2009-01-15) incorporates the following changes:Change TypeChange DescriptionParameter Change

Feature change None.The name of SIGNAL_HO_SWITCH is changed to HO_MC_SIGNAL_SWITCH.The name of ACT_SET_QUAL_SWITCH is changed to HO_INTER_FREQ_RPRT_2D2F_SWITCH.The name of INTER_FREQ_HHO_SWITCH is changed to HO_INTER_FREQ_HARD_HO_SWITCH.The name of HO_BEYOND_UE_CAP_ADD_TO_MC_SWITCH is changed to HO_MC_MEAS_BEYOND_UE_CAP_SWITCH.

The function CS Voice over HSPA is added.The added parameter is as follows: CSVoiceoverHSPASuppInd

Editorial changeThe Handover Parameter Description combines the contents of the following documents:Intra-frequency Handover DescriptionInter-frequency Handover DescriptionInter-RAT Handover DescriptionHCS Handover DescriptionNone.

Error! Use the Home tab to apply 1 to the text that you want to appear here.Error! Use the Home tab to apply 1 to the text that you want to appear here. RANHandover Parameter Description

RANHandover Parameter DescriptionError! Use the Home tab to apply 1 to the text that you want to appear here.Error! Use the Home tab to apply 1 to the text that you want to appear here.

8-10Huawei Proprietary and Confidential Copyright Huawei Technologies Co., LtdIssue 01 (2009-03-30)

Issue 01 (2009-03-30)Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd4-18

Handover IntroductionHandover is a basic function of the cellular mobile network. The purpose of handover is to ensure that a UE in CELL_DCH state is served continuously when it moves.Handover can be classified into the following types:Intra-frequency handoverInter-frequency handoverInter-RAT handoverIntended AudienceThis document is intended for:System operators who need a general understanding of handover.Personnel working on Huawei products or systems.ImpactImpact on system performanceIntra-frequency soft handover provides seamless connection services for moving UEs, but it uses more downlink code resources and transmission resources. In the network, resource utilization is determined by controlling the number of UEs involved in intra-frequency soft handover.Inter-frequency handover and inter-RAT handover are implemented in compressed mode. When too many UEs stay at the cell edge, the downlink capacity and uplink coverage of the system may decrease. These two types of handover may introduce delay, thus impacting on delay-sensitive services. HCS handover improves the voice quality of fast-moving UEs, enhances system capacity, and reduces signaling load.Impact on other featuresNone.Network Elements InvolvedTable 2-1 lists the Network Elements (NEs) involved in handover.NEs involved in handoverHandover TypeUENodeBRNCMSC ServerMGWSGSNGGSNHLR

Intra-frequency handover

Inter-frequency handover

Inter-RAT handover

HCS handover

NOTE: : not involved: involvedUE = User Equipment, RNC = Radio Network Controller, MSC Server = Mobile Service Switching Center Server, MGW = Media Gateway, SGSN = Serving GPRS Support Node, GGSN = Gateway GPRS Support Node, HLR = Home Location Register

Handover OverviewHandover TypesFigure 3-1 shows the handovers supported by the Universal Mobile Telecommunications System (UMTS), which include intra-frequency handover, inter-frequency handover, and inter-RAT handover.Handovers supported by the UMTS

Intra-Frequency HandoverIntra-frequency handover is of the following two types: Intra-frequency soft handover: means that multiple radio links are connected to the UE at the same time.Intra-frequency hard handover: means that only one radio link is connected to the UE at the same time.Intra-Frequency Soft HandoverIntra-frequency soft handover is more commonly used than intra-frequency hard handover. The types of intra-frequency soft handover are as follows:Intra-NodeB soft handover (also known as softer handover) Intra-RNC inter-NodeB soft handover Inter-RNC soft handover Intra-frequency soft handover is characterized by the function that the UE can be connected to multiple Universal Terrestrial Radio Access Network (UTRAN) access points at the same time. Addition and/or release of radio links are controlled by the ACTIVE SET UPDATE procedure.Differences between soft handover and softer handoverItemSofter HandoverSoft Handover

ScenarioWhen the UE is in the overlapped coverage area of multiple neighboring cells of a NodeB with combined RLsWhen the UE communicates with multiple cells by setting up multiple channels over the Uu interfaceWhen the UE is in the overlapped coverage area of two neighboring cells of different NodeBs When the UE communicates with different cells by setting up multiple channels over the Uu interface

Uplink signalUsing maximum-ratio combinationUsing selection combination

Downlink signalUsing maximum-ratio combinationUsing maximum-ratio combination

Resource useOccupying less Iub bandwidthOccupying more Iub bandwidth

The HO_INTRA_FREQ_SOFT_HO_SWITCH parameter is used to determine whether to enable both soft handover and softer handover. By default, this switch is set to ON, indicating that both soft handover and softer handover are enabled. After the RNC receives the event 1A, 1B, 1C, or 1D report, it initiates the corresponding soft handover procedure for the UE. For example, the RNC can add or delete links.The DivCtrlField parameter indicates whether maximum-ratio combination is enabled in the uplink during softer handover.Intra-Frequency Hard HandoverIntra-frequency hard handover refers to a handover where all the old radio links are released before the new radio links are established. Compared with soft handover, intra-frequency hard handover uses fewer resources.The scenarios of intra-frequency hard handover are as follows:No Iur interface is present between RNCs. In this scenario, intra-frequency hard handover instead of soft handover can be performed between two RNCs.The Iur interface is congested between RNCs. In this scenario, also intra-frequency hard handover instead of soft handover can be performed between two RNCs.There is a high-speed Best Effort (BE) service.Compared with soft handover, intra-frequency hard handover is used to save downlink bandwidth for a high-speed BE service.The intra-frequency soft handover fails and intra-frequency hard handover is allowed.When intra-frequency soft handover fails because of a congestion problem of the target cell, the RNC tries an intra-frequency hard handover with a lower service bit rate.The HO_INTRA_FREQ_HARD_HO_SWITCH parameter is used to determine whether to enable intra-frequency hard handover. By default, this switch is set to ON.Inter-Frequency HandoverInter-frequency handover provides supplementary coverage for inter-frequency cells to share load with each other and to ensure service continuity.From the UE point of view, inter-frequency handover is the same as intra-frequency hard handover, because for both cases, the old connection is released before a new connection is set up. For detailed information, see Intra-Frequency Hard Handover.The types of inter-frequency handover are as follows:Types of inter-frequency handoverTypeDescription

Coverage-based inter-frequency handoverIf a moving UE leaves the coverage of the current frequency, the RNC needs to trigger the coverage-based inter-frequency handover to avoid call drops.

QoS-based inter-frequency handoverAccording to the Link Stability Control Algorithm, the RNC needs to trigger the QoS-based inter-frequency handover to avoid call drops.

Load-based inter-frequency blind handoverTo balance the load between inter-frequency con-coverage cells, the RNC chooses some UEs and performs the inter-frequency blind handover according to user priorities and service priorities.

Speed-based inter-frequency handoverWhen the Hierarchical Cell Structure (HCS) applies, the cells are divided into different layers according to coverage. The macro cell has a larger coverage and a lower priority, whereas the micro cell has a smaller coverage and a higher priority.Inter-frequency handover can be triggered by the UE speed estimation algorithm of the HCS. To reduce frequent handovers, the UE at a higher speed is handed over to a cell under a larger coverage, whereas the UE at a lower speed is handed over to a cell under a smaller coverage. For detailed information about the cooperation between HCS handover and inter-frequency handover, see Interoperability Between HCS Handover and Inter-Frequency Handover.

The coverage-based inter-frequency measurement and the QoS-based inter-frequency measurement can coexist.The InterFreqHOSwitch parameter is used to determine the type of inter-frequency handover. According to the switch, the RNC chooses the inter-frequency measurement control parameters to implement handover measurement based on coverage, QoS, speed, and other types.INTER_FREQ_COV: The cell supports coverage-based inter-frequency handover.INTER_FREQ_COV_NCOV: The cell supports coverage-based and speed-estimation-triggered inter-frequency handover.INTER_FREQ_TA: The inter-frequency handover is triggered by HCS traffic absorption. This function itself contains the coverage-based function.The HO_INTER_FREQ_HARD_HO_SWITCH parameter is used to determine whether to allow load-based inter-frequency handover.For detailed description of QoS-based inter-frequency blind handover switches, see the Rate Control Parameter Description.Inter-RAT Handover (3G to 2G)Inter-RAT Handover IntroductionInter-RAT handover refers to the handover performed between 3G network and 2G network. The handover causes can be coverage limitation, link stability, or load limitation of the UMTS network. This document mainly describes the 3G-to-2G handover.Inter-RAT handover provides continuous coverage, load sharing, and HCS services, which fully utilizes the existing 2G network resources and thus reduces operator's cost.Based on the handover triggering causes, the 3G-to-2G handover can be categorized as five types, as described in Table 3-3.3G-to-2G handover typesTypeDescription

Coverage-based 3G-to-2G handoverThe coverage of the 3G network is in continuous at the initial stage. On the border of the coverage, the poor signal quality of the 3G network triggers the 3G-to-2G measurement. If the signal quality of the 2G network is good enough and all the services of the UE are supported by the 2G network, the coverage-based 3G-to-2G handover is triggered.

QoS-based 3G-to-2G handoverAccording to the Link Stability Control Algorithm, the RNC needs to trigger the QoS-based 3G-to-2G handover to avoid call drops.

Load-based 3G-to-2G handoverIf the load of the 3G network is heavy and all the RABs of the UE are supported by the 2G network, the load-based 3G-to-2G handover is triggered.

Service-based 3G-to-2G handoverBased on layered services, the traffic of different classes is handed over to different systems. For example, when an Adaptive Multi Rate (AMR) speech service is requested, this service can be handed over to the 2G network.

Speed-based 3G-to-2G handoverWhen the Hierarchical Cell Structure (HCS) applies, the cells are divided into different layers according to coverage. The macro cell has a larger coverage and a lower priority, whereas the micro cell has a smaller coverage and a higher priority.The 3G-to-2G handover can be triggered by the UE speed estimation algorithm of the HCS. To reduce the frequencies of handover, the UE at a higher speed is handed over to a cell under a larger coverage, whereas the UE at a lower speed is handed over to a cell under a smaller coverage. For detailed information, see HCS Handover Algorithms.Note: The principles of the 3G-to-2G handover based on HCS speed estimation are similar to those of inter-frequency handover.

Rules for Enabling 3G-to-2G HandoverBefore handover, the RNC checks whether all the preconditions for the 3G-to-2G handover are met. The preconditions include service handover indicators, service requirements, and handover rules.Before deciding the 3G-to-2G handover, the RNC considers 2G cell capability, service capability and UE capability.2G cell capability2G cell capability is configured through the parameter RATCELLTYPE. This parameter indicates whether the cell supports the GSM, GPRS, or EDGE.Service capabilityThe Required 2G Capability (Req2GCap) specifies the capability of 2G cells required by inter-RAT handover. This indicates whether the service is supported by the GSM, GPRS, or EDGE. For the default value provided by the RNC, see Table 3-6.UE capabilityUpon the reception of the UE capability information message, the RNC decides whether to start the inter-RAT measurement. The information indicates whether the UE supports the GSM, GPRS, or EDGE.The rules for enabling the 3G-to-2G handover are based on the Service Handover Indicator and the three types of capability. The rules vary according to the types of inter-RAT handover.Rules for Enabling Coverage- and QoS-based 3G-to-2G HandoverThe RNC initiates the coverage- or QoS-based UMTS-to-GSM handover only when Service Handover Indicator is set as follows:HO_TO_GSM_SHOULD_BE_PERFORM HO_TO_GSM_SHOULD_NOT_BE_PERFORMThe following tables describe the impacts of different types of capability on handover decision. If the capability of all 2G neighboring cells does not meet the requirement, the inter-RAT measurement will not be triggered.Impacts of different types of capability on handover decisionCell CapabilityUE CapabilityService Capability (Required by 2G)

EDGEGPRSGSM

EDGEEDGEAllowedAllowedAllowed

GPRSAllowedAllowedAllowed

GSMNot allowedNot allowedAllowed

Not supported by 2GNot allowedNot allowedNot allowed

GPRSEDGEAllowedAllowedAllowed

GPRSAllowedAllowedAllowed



GSMEDGENot allowedNot allowedAllowed

GPRSNot allowedNot allowedAllowed



Rules for Enabling Load- and Service-based 3G-to-2G HandoverThe RNC initiates the load-based 3G-to-2G handover only when Service Handover Indicator is set as follows:HO_TO_GSM_SHOULD_BE_PERFORM HO_TO_GSM_SHOULD_NOT_BE_PERFORMThe RNC initiates the service-based 3G-to-2G handover only when the Service Handover Indicator is set to HO_TO_GSM_SHOULD_BE_PERFORM.The following three tables describe the impacts of different types of capability on handover decision.Impacts of different types of capability on handover decisionCell CapabilityUE CapabilityService Capability (Required by 2G)

EDGEGPRSGSM

EDGEEDGEAllowedAllowedAllowed

GPRSNot allowedAllowedAllowed



GPRSEDGENot allowedAllowedAllowed

GPRSNot allowedAllowedAllowed



GSMEDGENot allowedNot allowedAllowed

GPRSNot allowedNot allowedAllowed



If the capability of all neighboring 2G cells does not meet the requirement, the inter-RAT measurement will not be triggered.Switches for Service-based 3G-to-2G HandoverTo perform the service-based 3G-to-2G handover, the RNC must turn on the related switches for services in the CS and PS domains.When a single CS service is initially set up by the UE, the RNC allows the 3G-to-2G service-based handover if CSServiceHOSwitch is set to ON.When a single PS service is initially set up by the UE, the RNC allows the service-based 3G-to-2G handover if PSServiceHOSwitch is set to ON.For the CS and PS combined services, no service-based handover is triggered.Service Handover IndicatorThe IE Service Handover Indicator indicates the CN policy for the service handover to the 2G network. This IE is indicated in the Radio Access Bearer (RAB) assignment signaling assigned by the CN, or in Table 3-6 provided by the RNC side.The algorithm switch HoSwitch: HO_INTER_RAT_RNC_SERVICE_HO_SWITCH decides whether the service attribute of inter-RAT handover is based on the RNC or the CN.If the switch is set to ON, the service attribute of inter-RAT handover is based on the parameter configured on the RNC side.If the switch is set to OFF, the service attribute of inter-RAT handover is first based on the CN when the indicator is contained in the RAB assignment signaling assigned by the CN. If the CN does not allocate a service indicator, the service attribute of inter-RAT handover is based on the RNC side.Through the SHIND parameter, the service handover indicators are set as follows:HO_TO_GSM_SHOULD_BE_PERFORM: means that the handover to the 2G network is performed when 2G signals are available.HO_TO_GSM_SHOULD_NOT_BE_PERFORM: means that the handover to the 2G network is performed when 3G signals are weak but 2G signals are strong.HO_TO_GSM_SHALL_NOT_BE_PERFORM: means that the handover to the 2G network is not performed even when 3G signals are weak but 2G signals are strong.Figure 3-2 shows an example of rules for the indicator of the 3G-to-2G handover based on load and service.Example of rules for indicator of 3G-to-2G handover based on load and service

By default, the RNC does as follows:For a UE with a single signaling RAB, the RNC supports the handover to the GSM. But it is not recommended.For the UE accessing combined services (with CS services), the RNC sets the service handover indicator of the UE to that of the CS service, because the CS service has the highest QoS priority.For the UE accessing combined services (with only PS services), the RNC sets the service handover indicator of the UE to that of the PS service, because the PS service has the highest QoS priorityIf the service handover indicators are not configured by the CN, each indictor can be set to the service parameter index of a service on the RNC. Each service parameter index is the index of one typical service RAB, which involves a set of service type, source description, CN domain ID, and maximum rate (bit/s).Table 3-6 describes the service handover indicators recommended by Huawei.Service handover indicators (default values)RAB IndexTraffic DirectionCN Domain IDTraffic ClassMax Rate (bit/s)Source DescriptionService Handover IndicatorRequired 2G Capability

0Uplink and downlinkCS_DOMAINCONVERSATIONAL12200SPEECHHO_TO_GSM_SHOULD_NOT_BE_PERFORMGSM

1Uplink and downlinkCS_DOMAINCONVERSATIONAL23850SPEECHHO_TO_GSM_SHOULD_NOT_BE_PERFORMGSM

2Uplink and downlinkCS_DOMAINCONVERSATIONAL28800UNKNOWNHO_TO_GSM_SHALL_NOT_BE_PERFORMGSM




6Uplink and downlinkCS_DOMAINSTREAMING57600UNKNOWNHO_TO_GSM_SHALL_NOT_BE_PERFORMGSM

11Uplink and downlinkPS_DOMAINCONVERSATIONAL8000UNKNOWNHO_TO_GSM_SHALL_NOT_BE_PERFORMGSM

12Uplink and downlinkPS_DOMAINCONVERSATIONAL16000UNKNOWNHO_TO_GSM_SHALL_NOT_BE_PERFORMEDGE







21Uplink and downlinkPS_DOMAINSTREAMING8000UNKNOWNHO_TO_GSM_SHALL_NOT_BE_PERFORMEDGE








40Uplink and downlinkPS_DOMAININTERACTIVE0UNKNOWNHO_TO_GSM_SHOULD_NOT_BE_PERFORMGPRS





45Uplink and downlinkPS_DOMAININTERACTIVE128000UNKNOWNHO_TO_GSM_SHOULD_NOT_BE_PERFORMEDGE




49UplinkPS_DOMAININTERACTIVE608000UNKNOWNHO_TO_GSM_SHALL_NOT_BE_PERFORMEDGE

50DownlinkPS_DOMAININTERACTIVE768000UNKNOWNHO_TO_GSM_SHALL_NOT_BE_PERFORMEDGE





55Uplink and downlinkPS_DOMAININTERACTIVE2048000UNKNOWNHO_TO_GSM_SHALL_NOT_BE_PERFORMEDGE









70Uplink and downlinkPS_DOMAINBACKGROUND0UNKNOWNHO_TO_GSM_SHOULD_NOT_BE_PERFORMGPRS





75Uplink and downlinkPS_DOMAINBACKGROUND128000UNKNOWNHO_TO_GSM_SHOULD_NOT_BE_PERFORMEDGE




79UplinkPS_DOMAINBACKGROUND608000UNKNOWNHO_TO_GSM_SHALL_NOT_BE_PERFORMEDGE

80DownlinkPS_DOMAINBACKGROUND768000UNKNOWNHO_TO_GSM_SHALL_NOT_BE_PERFORMEDGE





85Uplink and downlinkPS_DOMAINBACKGROUND2048000UNKNOWNHO_TO_GSM_SHALL_NOT_BE_PERFORMEDGE









Note:Rows without RAB index are all NA.

Intra-Frequency Handover AlgorithmsIntra-Frequency Handover ProcedureThe intra-frequency handover procedure is divided into three phases: handover measurement, handover decision, and handover execution.After the UE transits to the CELL_DCH state in connected mode during a call, the RNC sends a MEASUREMENT CONTROL message to instruct the UE to take measurements and report the measurement event results.The MEASUREMENT CONTROL message carries the following information:Event trigger thresholdHysteresis valueEvent trigger delay timeNeighboring cell listUpon the reception of an event report from the UE, the RNC makes a handover decision and performs the corresponding handover, as shown in Figure 4-1.Intra-frequency handover procedure

Intra-Frequency Handover MeasurementIn the measurement phase, the UE takes measurements according to the MEASUREMENT CONTROL message received from the RNC. When the event triggering conditions are met, the UE sends measurement reports to the RNC according to the rules defined in the MEASUREMENT CONTROL message.Intra-Frequency Handover Measurement QuantitiesIntra-frequency handover uses Ec/No or RSCP of the CPICH as the measurement value. Intra-frequency handover measurement events can be configured through the parameter IntraFreqMeasQuantity.The UE performs layer 3 filtering on measurement values before it decides measurement events and sends measurement reports. The measurement model, as shown in Figure 4-2, is defined in 3GPP25.302. Figure 4-2 shows the position of layer 3 filtering in the measurement procedure.Measurement model in the WCDMA system

Figure 4-2 also shows the measurement points of the model, whereA: measurement value of the physical layer B: measurement value obtained after layer-1 filtering. The value is weighted by the layer 3 filtering coefficient.C: measurement value obtained after layer 3 filtering. This value is controlled by the higher layer. Filtering coefficient C is applicable to event reports and periodic reports.C': another measurement value. C' and C are measured in the same way.D: measurement report information (message) of Uu or Iub transmission. Parameters (a) include the layer 3 filtering system and Parameters (b) include the measurement report configuration.The calculation is based on the following formula:Fn = (1 - ) x Fn-1 + x MnFn: measurement value obtained after the nth filteringFn-1: measurement value obtained after the (n-1)th filteringMn: measurement value of the nth physical layer = 1/2(k/2): k is determined by the parameter FilterCoef, which is the layer 3 filtering coefficient of intra-frequency handover measurement.When is set to 1, k = 0 and layer 3 filtering is not performed.Intra-Frequency Handover Measurement EventsIn intra-frequency handover, the UE reports measurement results to the RNC through event reporting.EventDescription

1AA primary CPICH enters the reporting range. This indicates that the quality of a cell is close to the quality of the best cell in the active set. A relatively high combined gain can be achieved when the cell is added to the active set.

1BA primary CPICH leaves the reporting range. This indicates that a cell has a lower quality than the best cell in the active set. The cell has to be deleted from the active set.

1CA non-active primary CPICH becomes better than an active primary CPICH. This indicates that the quality of a cell is better than the quality of the worst cell in the active set. The RNC replaces a cell in the active set with a cell in the monitored set.

1DThe best cell changes.

1JRAN10.0 provides the solution to the issue of how to add an HSUPA cell in a DCH active set to an E-DCH active set. Event 1J is added to the 3GPP protocol. This event is triggered when a non-active E-DCH but active DCH primary CPICH becomes better than an active E-DCH primary CPICH.

Triggering of Event 1AEvent 1A is triggered under the following condition:

10 x Log(MNew) + CIONew W x 10 x Log() + (1 - W) x 10 x Log(MBest) - (R1a - H1a/2)MNew is the measurement value of the cell in the reporting range.CIONew is equal to the sum of CIO and CIOOffset, which adjusts the cell boundary in the handover algorithms. This parameter is determined by network planning according to actual environment configuration. To facilitate handover in neighboring cell configuration, the parameter is set as a positive value; otherwise, the parameter is set as a negative value.W represents Weighted factor, which is determined by the parameter Weight. The total quality of the best cell and the active set is specified by W.Mi is the measurement value of a cell in the active set.NA is the number of cells not forbidden to affect the reporting range in the active set. The parameter CellsForbidden1A indicates whether adding the cell to the active set affects the relative threshold of event 1A.MBest is the measurement value of the best cell in the active set.R1a is the reporting range or the relative threshold of soft handover. The threshold parameters of the CS non-VP service, VP service, and PS service are as follows:IntraRelThdFor1ACSVPIntraRelThdFor1ACSNVPIntraRelThdFor1APS

For the PS and CS combined services, the threshold for CS services is used.For the single signaling connection of the UE, the threshold for CS services is used.H1a represents 1A hysteresis, the hysteresis value of event 1AFigure 4-3 shows the triggering of event 1A. In this procedure, the default parameter values are used.If the signal quality of a cell that is not in the active set is higher than Th1A for a period of time specified by TrigTime1A (that is, Time to trigger in Figure 4-3), the UE reports event 1A.Th1A = (CPICH Ec/No of the best cell in the active set) - (reporting range for event 1A)If Weighted factor > 0, then Th1A = (general signal quality of all the cells in the active set) - (reporting range for event 1A).Reporting range for event 1A is equal to the value of IntraRelThdFor1ACSVP, IntraRelThdFor1ACSNVP, or IntraRelThdFor1APS.Triggering of event 1A

A: signal quality curve of the best cell in the active setB: signal quality curve of a cell in the monitored setC: curve of Th1ATriggering of Event 1BEvent 1B is triggered under the following condition:

10 x Log(Mold) + CIOold W x 10 x Log() + (1-W) x 10 x Log(MBest) - (R1b-H1b/2)MOld is the measurement value of the cell that becomes worse. CIOOld is equal to the sum of CIO and CIOOffset, which is the offset between the cell in the reporting range and the best cell in the active set.W represents Weighted factor, used to weight the quality of the active set. The total quality of the best cell and the active set is specified by the parameter Weight.Mi is the measurement value of a cell in the active set.NB is the number of cells not forbidden to affect the reporting range in the active set. The parameter CellsForbidden1B indicates whether adding the cell to the active set affects the relative threshold of event 1B.MBest is the measurement value of the best cell in the active set.R1b is the reporting range or the relative threshold of soft handover. The threshold parameters of the CS non-VP service, VP service, and PS services are as follows: IntraRelThdFor1BCSVPIntraRelThdFor1BCSNVPIntraRelThdFor1BPS

For the PS and CS combined services, the threshold for CS services is used.If the UE currently has only signaling connections, the threshold for CS services is used.H1b is the hysteresis value of event 1B, which is determined by the parameter Hystfor1B. Configuration rule and restrictionThe value of IntraRelThdFor1BCSNVP has to be larger than that of IntraRelThdFor1ACSNVP.The value of IntraRelThdFor1BCSVP has to be larger than that of IntraRelThdFor1ACSVP.The value of IntraRelThdFor1BPS has to be larger than that of IntraRelThdFor1APS.Figure 4-4 shows the triggering of event 1B. In this procedure, the default parameter values are used.Triggering of event 1B

A: signal quality curve of the best cell in the active setB: signal quality curve of the best cell in the monitored setC: curve of Th1BTh1B = (CPICH Ec/No of the best cell in the active set) - (reporting range for event 1B)whereReporting range for event 1B is equal to the value of IntraRelThdFor1BCSVP, IntraRelThdFor1BCSNVP, or IntraRelThdFor1BPS.If Weight > 0, then Th1B = (general signal quality of all the cells in the active set) - (reporting range for event 1B).If the signal quality of a cell in the active set is lower than Th1B for a period of time specified by TrigTime1B (Time to trigger in the figure), the UE reports event 1B.Triggering of Event 1CEvent 1C is triggered under the following condition:10 x Log(MNew) + CIONew 10 x Log(MInAS) + CIOInAS + H1c/2MNew is the measurement value of the cell in the reporting range.CIONew is the cell individual offset value of the cell in the reporting range. It is equal to the sum of CIO and CIOOffset, which is the offset between the cell in the reporting range and the best cell in the active set.MInAS is the measurement value of the worst cell in the active set.H1c is the hysteresis value of event 1C, which is determined by the parameter Hystfor1C.Figure 4-5 shows the triggering of event 1C. In this procedure, the default parameter values are used.Triggering of event 1C

A: signal quality curve of the best cell in the active setB: signal quality curve of a cell in the active setC: signal quality curve of the worst cell in the active setD: signal quality curve of a cell in the monitored setE: curve of Th1CTh1C = (CPICH Ec/No of the worst cell in the active set) + (hysteresis/2)whereHysteresis is equal to the value of Hystfor1C.If the signal quality of a cell not in the active set is higher than Th1C for a period of time specified by TrigTime1C (Time to trigger in the figure), the UE reports event 1C, as shown in the figure.The UE reports event 1C for qualified cells after the number of cells in the active set reaches the maximum value. The maximum number of cells in the active set can be set by the MaxCellInActiveSet parameter.Triggering of Event 1DEvent 1D is triggered under the following condition:10 x Log(MNotBest) + CIONotBest 10 x Log(MBest) + CIOBest + H1d/2MNotBest is the measurement value of a cell that is not the best cell.CIONotBest is equal to the sum of CIO and CIOOffset, which is the offset between the cell in the reporting range and the best cell in the active set.MBest is the measurement value of the best cell in the active set.CIOBest is the cell individual offset value of the best cell. This parameter is not used for event 1D.H1d is the hysteresis value of event 1D, which is determined by the parameter Hystfor1D.Figure 4-6 shows the triggering of event 1D. In this procedure, the default parameter values are used.Triggering of event 1D

A: signal quality curve of the best cell in the active setB: signal quality curve of a cell in the active set or the monitored setC: curve of Th1DHysteresis is equal to the value of Hystfor1D.If the signal quality of a cell not in the active set is higher than Th1D for a period of time specified by TrigTime1D (Time to trigger in the figure), the UE reports event 1D.Triggering of Event 1JEvent 1J is triggered under the following condition:10 x Log(MNew) + CIONew 10 x Log(MInAS) + CIOInAS + H1j/2MNew is the measurement result of the cell not in the E-DCH active set but in the DCH active set.CIONew and CIOInAS refer to the offset of each cell.MInAS is the measurement result of the cell in the E-DCH active set with the lowest measurement result.H1J is the hysteresis parameter for event 1J and is determined by Hystfor1J.If the measurement result is CPICH-Ec/No, MNew and MInAS are expressed as ratios.If the measurement result is CPICH-RSCP, MNew and MInAS are expressed in mW.Triggering of event 1J

A: signal quality curve of a cell in the E-DCH active setB: signal quality curve of the worst cell in the E-DCH active setC: signal quality curve of a cell not in the E-DCH active set but included in DCH active setD: signal quality curve of a cell not in the E-DCH active set but included in DCH active setIn Figure 4-7, the hysteresis and the cell individual offsets for all cells equal 0.The first measurement report is sent when primary CPICH D becomes better than primary CPICH B. The "cell measurement event result" of the measurement report contains the information of primary CPICH D and CPICH B.On the assumption that the E-DCH active set has been updated after the first measurement report (E-DCH active set is now primary CPICH A and primary CPICH D), the second report is sent when primary CPICH C becomes better than primary CPICH A. The "cell measurement event result" of the second measurement report shows that primary CPICH C is better than primary CPICH A in quality.The following parameters need to be set on the RNC LMT:Hystfor1J: hysteresis of event 1FTrigTime1J: time to trigger event 1JPeriodMRReportNumfor1J: number of periodic reports for event 1JReportIntervalfor1J: report interval for event 1J after change to the periodic reportHO_INTRA_FREQ_RPRT_1J_SWITCH: measurement control switch for event 1J. When the switch is ON, the UE version is R6 and event 1J is included in the intra-frequency measurement control message.After receiving the intra-frequency measurement report from the UE, the RNC decides whether to go to the execution phase, depending on the information in the report.Intra-Frequency Handover Neighboring Cell Combination AlgorithmAfter the active set is updated, the RNC updates the neighboring cell list by using the neighboring cell combination algorithm according to the status of the active set. This list includes the new intra-frequency, inter-frequency, and inter-RAT neighboring cells. The combination methods of intra-frequency handover, inter-frequency handover, and inter-RAT handover are the same.If the radio link of the Drift RNC (DRNC) is added to the active set, the Source RNC (SRNC) buffers the intra-frequency, inter-frequency, and inter-RAT neighboring cell lists of the DRNC until the radio link of the DRNC is released.The neighboring cell combination result is contained in the MEASUREMENT CONTROL message and sent to the UE, which instructs the UE to perform intra-frequency, inter-frequency, and inter-RAT measurement and handover procedures.The number of inter-frequency neighboring cells is configured as follows:A maximum of 32 intra-frequency neighboring cells are configured.A maximum of 32 single-carrier inter-frequency neighboring cells are configured.A maximum of 64 multi-carrier inter-frequency neighboring cells are configured.A maximum of 32 inter-RAT neighboring cells are configured.Neighboring Cell Combination SwitchHO_MC_NCELL_COMBINE_SWITCH is the neighboring cell combination switch.If the switch is set to ON, measurement objects are chosen from the neighboring cells of all the cells in the active set. If the switch is set to OFF, measurement objects are chosen from the neighboring cells of the best cell.HO_MC_NCELL_COMBINE_SWITCH is set to ON by default.Description of the Neighboring Cell Combination AlgorithmAfter obtaining the intra-frequency neighboring cells of each cell in the active set, the RNC calculates the union neighboring cell set of the intra-frequency cells, which is referred as Sall, by using the following method. This method can also be used to generate the Sall of inter-frequency or inter-RAT cells.The intra-frequency, inter-frequency, and inter-RAT neighboring cells of each cell in the current active set are obtained.The RNC sequences the cells in the active set in descending order of CPICH Ec/No according to the latest measurement report (event 1A, 1B, 1C, or 1D) from the UE. The best cell is based on event 1D, whereas other cells are based on the latest measurement report.The cells in the active set are added to Sall.The neighboring cells of the best cell in the active set are added to Sall. NprioFlag (the flag of the priority) and Nprio (the priority of the neighboring cell), which are set for each neighboring cell, are used to change the order of adding the neighboring cells to Sall.When NprioFlag is switched to FALSE, NPrio is cleared.When NprioFlag is switched to TRUE, NPrio is set simultaneously.The neighboring cells of other cells in the active set are added to Sall in descending order by CPICH Ec/No values of these cells in the active set. The neighboring cells of the same cell in the active set are added according to Nprio and the number of repeated neighboring cell is recorded.If there are more than 32 intra-frequency neighboring cells in Sall, delete the repeated neighboring cells whose number in Sall is less. The top 32 neighboring cells are grouped into the final Sall.If there are more than 64 (multi-carrier) or 32 (single-carrier) inter-frequency neighboring cells in Sall, the top 64 or 32 neighboring cells are grouped into the final Sall.Intra-Frequency Handover Decision and ExecutionThe intra-frequency handover decision and execution procedure depends on the different measurement events that the RNC receives.Decision and ExecutionTable 4-1 lists different types of intra-frequency handover decision and execution based on different events.Intra-frequency handover decision and executionEventDecision and Execution

1AWhen receiving an event 1A report, the RNC decides whether to add a cell.For event 1A, the UE can report more than one cell in the event list in one measurement report. These cells are in the list of the MEASUREMENT CONTROL message, and they are sequenced in descending order of measurement quantity.For the cells in the list, the RNC adds the radio link to the active set only if the number of cells in the active set does not reach the maximum value. This operation is not required if the number of cells in the active set reaches a specified value.

1BWhen receiving an event 1B report, the RNC decides whether to delete a cell.For event 1B, if there is more than one radio link in the active set, the RNC decides whether to delete a radio link. This operation is not required if there is only one radio link in the active set.

1CWhen receiving an event 1C report, the RNC decides whether to change the worst cell.For event 1C, the UE reports a list that contains good cells and the cells to be replaced, and sequences the cells in descending order by measurement quantity. After receiving the list from the UE, the RNC replaces the bad cells in the active set with the good cells in the list.

1DAs stipulated in related protocols, an event 1D report includes information about only one cell. This cell can be listed in an active set or a monitored set. The RNC learns that the quality of this cell is better than that of the serving cell and takes one of the following actions:If the reported cell is in the active set, the RNC decides whether to change the best cell or reconfigure measurement control.If the reported cell is in the monitored set, then:If the number of cells in the active set has not reached the maximum value, the RNC adds the cell to the active set.If the number of cells in the active set has reached the maximum value, the RNC replaces the worst cell in the active set with the reported cell.The best cell is changed to the reported cell.The RNC determines whether the intra-frequency hard handover scenarios are applicable. For detailed information, see Intra-Frequency Handover Types in section 3.1 Handover Types. If any scenario is applicable, the RNC performs an intra-frequency hard handover.

1JWhen receiving an event 1J report with information about the good cells and the cells to be replaced, the RNC proceeds as follows:If the current number of cells in the E-DCH active set is smaller than the value of MaxEdchCellInActiveSet, the uplink of the cell where event 1J is triggered is reconfigured to E-DCH.If the current number of cells in the E-DCH active set is equal to the value of MaxEdchCellInActiveSet, the RNC searches the measurement report for the non-serving E-DCH with the lowest measured quality in the E-DCH active set. Then, the uplink of the cell where event 1J is triggered is reconfigured from DCH to E-DCH.

Minimum Quality Threshold for Soft HandoverWhen receiving an event 1A, 1C, or 1D report, the RNC adds a target cell to the active set only when the CPICH Ec/No of the target cell is higher than the absolute threshold SHOQualmin.

SHO: soft handoverSwitch for Cross-Iur Intra-Frequency HandoverIf the RRC connection has been set up but the Radio Bearers (RBs) have not, whether a cross-Iur soft handover can be executed is determined by HO_MC_SIGNAL_IUR_INTRA_SWITCH of the SET CORRMALGOSWITCH parameter. Only if the switch is set to ON, can the cross-Iur soft handover be executed.Rate Reduction After an SHO FailureIf the radio link addition for a soft handover fails, the rate reduction is triggered for R99 NRT (Non Real Time) services to increase the probability of a successful soft handover.Estimation Procedure for Rate ReductionIf the RNC receives a 1A, 1C, or 1D measurement report, the RNC tries to add the corresponding cell to the active set. If the addition fails, the RNC performs the estimation procedure for rate reduction.Estimation procedure for rate reduction

0. The RNC evaluates whether the measurement quantity of the cell failing to be admitted meets the condition of rate reduction.If the condition is met, the RNC performs a rate reduction process for the access service immediately, as described in Procedure of Rate Reduction Execution.If the condition is not met, the RNC performs the next step (Step 2).The condition of rate reduction is as follows: Mnew > Mbest_cell - RelThdForDwnGrdMnew is the CPICH Ec/No measurement value of the cell failing to be admitted.Mbest_cell is the CPICH Ec/No measurement value of the best cell in the active set.RelThdForDwnGrd is configured through the parameter Relative threshold of SHO failure.The RNC evaluates whether the number of SHO failures in the cell exceeds the Threshold number of SHO failure.If the number of SHO failures in the cell is smaller than the ShoFailNumForDwnGrd: If the timer has not been started, the RNC starts it.If the timer has been started, the RNC increments the SHO failure counter by one.The timer length is set through the parameter ShoFailPeriod.The SHO failure counter of a cell is used to record the number of SHO failures in this cell. For each UE, the RNC records the number of SHO failures in three cells at most. For SHO failures in any other cells, the RNC does not record the number.Before the SHO failure evaluation timer expires, no action is taken and the RNC waits for the next measurement report period.When the SHO failure evaluation timer expires, the RNC sets the SHO failure counter of the corresponding cell to 0 and ends the evaluation.If the number of SHO failures in the cell is larger than or equal to the parameter ShoFailNumForDwnGrd, the RNC performs a rate reduction process for the access service, Procedure of Rate Reduction ExecutionProcedure of rate reduction execution

0. The RNC performs a rate reduction process for the access service. The method of determining the access rate after the rate reduction is the same as that described in Rate Negotiation of Load Control Parameter Description.After the rate reduction succeeds, the RNC immediately attempts to add this cell to the active set without measurement:If the cell succeeds in admitting the UE, the RNC adds the radio link and sets the SHO failure counter of the cell to 0 and ends the execution.If the cell fails to admit the UE, the RNC starts the Period of penalty timer for SHO failure after down rate to avoid an increase in the rate triggered by DCCC within the period. Also in this period, the RNC sets the SHO failure counter of the cell to 0 and ends the execution.If the RNC fails to perform a soft handover again, it performs the estimation procedure and the execution procedure, as previously described.Intra-Frequency Handover of HSDPAThis section describes the decision and execution of intra-frequency handover, and the handover between a cell supporting the F-DPCH and a cell not supporting the F-DPCH after the introduction of HSDPA.Decision and Execution of Intra-Frequency HandoverHandling of Event 1AAfter receiving an event 1A report, the RNC proceeds as follows:If the number of cells in the active set does not reach the maximum value, the RNC adds the cell to the active set.If the number of cells in the active set reaches the maximum value, the RNC does not add the radio link to the active set.Handling of Event 1BAfter receiving an event 1B report, the RNC determines whether to delete a cell.If the cell to be deleted is not an HSDPA serving cell, the cell is directly removed.If the cell to be deleted is an HSDPA serving cell, then:If the new best cell supports HSDPA, the new best cell is reconfigured to be an HSDPA serving cell. If the reconfiguration fails, the service is reconfigured onto DPCH.If the new best cell does not support HSDPA, the service is reconfigured onto DPCH to ensure the continuity of the service.Handling of Event 1CAfter receiving an event 1C report, the RNC decides whether to change the worst cell.If the cell to be replaced is not an HSDPA serving cell, the cell is directly removed.If the cell to be replaced is an HSDPA serving cell, then:If the best cell supports HSDPA, the best cell is reconfigured to be an HSDPA serving cell. If the reconfiguration fails, the service is reconfigured onto DPCH.If the best cell does not support HSDPA, the service is reconfigured onto DPCH to ensure the continuity of the service.Handling of Event 1DAfter receiving an event 1D report, the RNC proceeds as follows:If the downlink service is carried on the HSDPA, then:If the new best cell in the active set supports HSDPA and the HSPA hysteresis timer expires, the new best cell is reconfigured to be an HSDPA serving cell. The HSPA hysteresis timer is restarted after the serving cell change and is to avoid frequent updates at the boundary between two HSDPA cells. The timer length is specified by the parameter HspaTimerLen.Figure 4-10 shows an example of how to handle event 1D in this situation. Assume that the UE moves from HSDPA cell 1 to HSDPA cell 2, that the two cells are intra-frequency neighboring cells, and that all the cells in the active set support HSDPA. The RNC updates the HSDPA serving cell according to the reported event and keeps the HSDPA serving cell consistent with the best cell.If the new best cell in the active set does not support HSDPA, the downlink service is directed to the DCH through the reconfiguration.Intra-frequency handover between HSDPA cells when the best cell changes

If the downlink service is carried on the DCH, then:To avoid frequent handovers at the boundary between an HSDPA cell and an R99 cell, a protection timer is used. After an intra-frequency handover, the timer starts. After this timer expires, the RNC reconfigures the service of the UE onto the HS-PDSCH of the HSDPA cell if either of the following two conditions is met:The target cell supports HSDPA.The target cell does not support HSDPA but has a DRD neighboring cell.The timer length is specified by the parameter ChannelRetryHoTimerLen.In the execution procedure mentioned above, CMP_UU_SERV_CELL_CHG_WITH_ASU_SWITCH of the CmpSwitch parameter is used to determine whether the update of the active set and the change of the serving cell are synchronized. This switch is applicable to only R6 UEs.If the switch is ON, the UE supports the synchronization of the update of the active set and the change of the serving cell.If the switch is OFF, the UE reconfigures the change of the serving cell by allocating physical channels after updating the active set.During the update of the HSDPA serving cell, set the NBMMachsResetAlgoSelSwitch parameter to determine whether to reset the UE MAC-hs.F-DPCH Handover ProtectionIf all the cells in the active set support the F-DPCH after the active set is updated and the Signaling Radio Bearer (SRB) is carried on the DCH, the timer ChannelRetryHoTimerLen starts. After this timer expires, the RNC decides whether to switch the SRB to the HS-DSCH.After the UE is handed over to an HSDPA cell from an R99 cell, the D2HRetryTimer starts. After this timer expires, the RNC decides whether to switch the SRB to the HS-DSCH and whether to set up the F-DPCH.D2HRetryTimer is set through ChannelRetryHoTimerLen.Intra-Frequency Handover of HSUPAThis section describes the decision and execution of intra-frequency handover, and the handover between E-DCHs of 10 ms TTI and 2 ms TTI after the introduction of HSUPA.Decision and Execution of Intra-Frequency HandoverHandling of Event 1AAfter receiving the measurement report, the RNC proceeds as follows:If the target cell supports HSUPA and the uplink service is carried on the E-DCH, then:If the current number of cells in the E-DCH active set is smaller than the value of MaxEdchCellInActiveSet, the target cell is added to both the DCH and E-DCH active sets.Otherwise, the target cell is added to only the DCH active set.After deciding that a cell can be added to the E-DCH active set,If the admission in the downlink fails, the cell is added to neither the E-DCH active set nor the DCH active set. It waits for the next event 1A report for retry.Otherwise, if the admission in the downlink succeeds, the RNC perform the HSUPA admission in the uplink.If HSUPA admission in the uplink succeeds, the cell is added to the E-DCH active set and the DCH active set.If HSUPA admission in the uplink fails, the cell is added only to the DCH active set. If the DCH admission in the uplink still fails, the cell is added to neither the E-DCH active set nor the DCH active set. It waits for the next event 1A report for retry.Handling of Event 1BIf the number of radio links in the DCH active set is larger than one, then:If the cell to be removed is not an HSUPA serving cell, the cell is directly removed.If the cell to be removed is an HSUPA serving cell, then:If the new best cell supports HSUPA, the new best cell is reconfigured to be an E-DCH serving cell.If the new best cell does not support HSUPA, the uplink service is redirected to the DCH through the RB reconfiguration.If the current service is CS Voice over HSPA and the cell to be removed is an E-DCH serving cell, then:If the new best cell supports both HSDPA and HSUPA, the cell is reconfigured to be an HS-DSCH serving cell or an E-DCH serving cell.If the new best cell supports HSDPA but not HSUPA, the current service is changed from CS Voice over HSPA to CS Voice over DCH. If there remain other HSDPA services, the serving cell should be updated and the new best cell should be the HS-PDSCH serving cell.If the new best cell supports neither HSUPA nor HSDPA, the current service is reconfigured to be CS Voice over DCH.Whether the cells under the adjacent RNC support CS Voice over HSPA is determined by the RNC-level parameter CSVoiceoverHSPASuppInd.After the best cell of a UE changes, if the size of the DCH or E-DCH active set of the new best cell is different from those of the old best cell, the RNC removes or reconfigures radio links to adapt to the size and configuration of the new best cell.Handling of Event 1CWhen event 1C is triggered, the UE reports the event-triggered list that contains good cells and the cells to be replaced, and sequences the cells from the highest to the lowest quality according to measurement quantity.After receiving the measurement report, the RNC proceeds as follows:If the new cell supports HSUPA, then:If the current number of cells in the E-DCH active set is smaller than the value of MaxEdchCellInActiveSet, the new cell is added to the E-DCH active set.If the current number of cells in the E-DCH active set is equal to the value of MaxEdchCellInActiveSet and the cell to be replaced is also included in the E-DCH active set, the new cell joins the E-DCH active set through replacement.If the current number of cells in the E-DCH active set is equal to the value of MaxEdchCellInActiveSet and the cell to be replaced is not included in the E-DCH active set, the new cell is added only to the DCH active set.If the current service is CS Voice over HSPA and the cell to be removed is an E-DCH serving cell, then:If the new best cell supports both HSDPA and HSUPA, the cell is reconfigured to be an HS-DSCH serving cell or an E-DCH serving cell.If the new best cell supports HSDPA but not HSUPA, the current service is changed from CS Voice over HSPA to CS Voice over DCH through the reconfiguration. If there remain other HSDPA services, the serving cell should be updated and the new best cell should be the HS-PDSCH serving cell.If the new best cell supports neither HSUPA nor HSDPA, the current service is reconfigured to be CS Voice over DCH. If the cell to be removed is an E-DCH serving cell, the HS-DSCH serving cell must be removed at the same time. Thus, a new E-DCH serving cell or HS-DSCH serving cell must be determined. The method is the same as that of removing the serving cell, as described in Handling of Event 1B.If the new cell does not support HSUPA, the cell is added to only the DCH active set.Handling of Event 1DIf the criteria for intra-frequency hard handover are fulfilled, the RNC performs intra-frequency hard handover after receiving the event 1D report. If the criteria for intra-frequency hard handover are not fulfilled, the RNC performs intra-frequency soft handover based on the measurement report.If the uplink service is carried on the E-DCH, then:If the new best cell in the active set supports HSUPA and the HSPA hysteresis timer expires, the E-DCH serving cell becomes the best cell. The HSPA hysteresis timer is restarted after the cell change. The length of the HSPA hysteresis timer is defined by the HspaTimerLen parameter.The HSPA hysteresis timer is defined to reduce the probability of the frequent change of the serving cell, which is caused by the frequent change of the best cell. Thus, the serving cell cannot change before the timer expires. The ping-pong effect has been considered in the triggering conditions of event 1D; and therefore, the timer is set to 0 by default. This means that the serving E-DCH cell is updated immediately when the best cell changes.If the new best cell in the active set does not support HSUPA,The uplink service is directed to the DCH through the reconfiguration. If the reconfiguration fails, the service is still carried on the E-DCH. The UE is connected to the new best cell only on the DPCH.If the uplink service is carried on the DCH, then:If the new best cell in the active set supports HSUPA or the new best cell has an HSUPA-capable and DRD-applicable neighboring cell, and if the uplink service is suitable to be mapped to HSUPA, the RNC starts a timer whose length is defined by the ChannelRetryHoTimerLen parameter.After this timer expires, the service is directed to the E-DCH through the reconfiguration. If the admission fails during the reconfiguration, the timer whose length is defined by the ChannelRetryTimerLen parameter is started. Periodic retries of DCH to E-DCH are performed.If the new best cell in the active set does not support HSUPA, the uplink service is still carried on the DCH.If the current service is CS Voice over HSPA, then:If the new best cell supports both HSUPA and HSDPA, the cell is reconfigured to be an HSPA serving cell.Otherwise, the service is changed from CS Voice over HSPA to CS Voice over DCH through the reconfiguration.Handling of Event 1JWhen event 1J is triggered, the UE reports the event-triggered list that contains good cells and the cells to be replaced, and sequences the cells from the highest to the lowest quality according to measurement quantity.After receiving the measurement report, the RNC proceeds as follows:If the current number of cells in the E-DCH active set is smaller than the value of MaxEdchCellInActiveSet, the cell where event 1J is triggered is reconfigured to E-DCH.If the current number of cells in the E-DCH active set is equal to the value of MaxEdchCellInActiveSet, the RNC searches the measurement report for the non-serving Cell_EDCH with the lowest measured quality in the E-DCH active set. Then, the uplink of the cell where event 1J is triggered is reconfigured from DCH to E-DCH, and the uplink of CELL-EDCH is reconfigured from E-DCH to DCH.In addition, for BE services, if the current bit rate is higher than HsupaBeShoRateThd, the bandwidth on the E-DCH is reduced to this parameter value.Handover Between E-DCHs of 10 ms TTI and 2 ms TTIFor HSUPA, 2 ms TTI and 10 ms TTI are applicable but not all the cells support 2 ms TTI. When both 2ms-TTI-capable and 2ms-TTI-incapable cells exist in a network, a UE may undergo handovers between E-DCHs of 10 ms TTI and 2 ms TTI.Only when all the cells in the E-DCH active set support 2 ms TTI can the services be configured to the E-DCH with 2 ms TTI. If any cell in the E-DCH active set does not support 2 ms TTI, the services are configured on the E-DCH with 10 ms TTI.The detailed principles are as follows:When the uplink service is carried on the E-DCH with 2 ms TTI, if a cell that supports only 10 ms TTI is to be added to the E-DCH active set, the source cell undergoes a radio bearer reconfiguration to 10 ms TTI. A soft handover to the target cell is performed.Upon each handover, if a radio link needs to be added, removed, or replaced, the RNC judges whether all the cells in the E-DCH active set and the UE support 2 ms TTI.If they all support 2 ms TTI and the uplink service is currently carried on the E-DCH with 10 ms TTI, the RNC reconfigures the service to the E-DCH with 2 ms TTI.If the reconfiguration fails, a timer is started for periodic retries to the E-DCH with 2 ms TTI.If the handover is performed before the timer expires, the timer is stopped.After the handover, the RNC decides whether to start the timer, based on the handover result.Signaling Procedures for Intra-Frequency HandoverIntra-NodeB Intra-Frequency Soft Handover Signaling ProcedureThis section describes the signaling procedure for intra-frequency soft handover within a NodeB.Figure 4-11 shows the procedure for intra-frequency soft handover when the UE moves from one cell to another cell within the same NodeB.Procedure for intra-NodeB intra-frequency soft handover

The connections involved in the intra-NodeB intra-frequency softer handover change are as follows:Before the softer handover, only cell 1 is connected to the UE.During the softer handover, both cell 1 and cell 2 are connected to the UE.Before the softer handover, only cell 2 is connected to the UE. Cell 1 is removed from the active set.Signaling procedure for intra-NodeB intra-frequency soft handover

Intra-RNC Inter-NodeB Intra-Frequency Soft Handover Signaling ProcedureProcedure for intra-RNC inter-NodeB intra-frequency soft handover

Before the soft handover, only NodeB 1 is connected to the UE. During the soft handover, both NodeBs are connected to the UE. After the soft handover, only NodeB 2 is connected to the UE. The active set of NodeB 1 is removed.Signaling procedure for intra-RNC inter-NodeB intra-frequency soft handover

Inter-RNC Intra-Frequency Soft Handover Signaling ProcedureProcedure for inter-RNC intra-frequency soft handover

Before the soft handover, the UE is connected to NodeB 1 and NodeB 2. After the SRNC makes a soft handover decision, it sets up a connection between NodeB 3 under another RNC and the UE, and releases the connection between NodeB 1 and the UE.Signaling procedure for inter-RNC intra-frequency soft handover

Intra-RNC Inter-NodeB Intra-Frequency Hard Handover Signaling ProcedureProcedure for intra-RNC inter-NodeB intra-frequency hard handover

Signaling procedure for intra-RNC inter-NodeB intra-frequency hard handover

In Figure 4-18, NodeB 1 is the source NodeB, and NodeB 2 is the target NodeB. Inter-RNC Intra-Frequency Hard Handover Signaling ProcedureFigure 4-19 shows the procedure for intra-frequency hard handover when a UE moves from one NodeB in an SRNC to another NodeB in a DRNC.Procedure for inter-RNC intra-frequency hard handover

Signaling procedure for inter-RNC intra-frequency hard handover

As shown in Figure 4-20, NodeB 1 is the source NodeB and NodeB 2 is the target NodeB.

Inter-Frequency Handover AlgorithmsInter-Frequency Handover ProcedureThe inter-frequency handover procedure is divided into four phases: handover triggering, handover measurement, handover decision, and handover execution. The procedure varies according to handover types.Coverage- or QoS-based Inter-Frequency and Inter-RAT Handover ProcedureThe procedure for the coverage- or QoS-based inter-frequency handover is the same as that for the coverage- or QoS-based inter-RAT handover, as shown in Figure 5-1.Coverage- or QoS-based inter-frequency and inter-RAT handover procedure

In the triggering phaseFor the coverage-based handover, the RNC requests the UE to measure through an inter-frequency measurement control message. If the CPICH Ec/No or CPICH RSCP of the current cell is lower than the corresponding threshold, the UE reports event 2D.For the QoS-based handover, if the service quality of the current cell deteriorates, the Link Stability Control Algorithm makes a handover measurement decision. In the measurement phaseThe RNC sends an inter-frequency measurement control message to the UE, requesting the NodeB and UE to start the compressed mode. The RNC also requests the UE to perform the inter-frequency or inter-RAT handover measurement .In this phase, the method of either periodical measurement report or event-triggered measurement report can be used.In the decision phaseAfter the UE reports event 2B, the RNC performs the handover. Otherwise, the UE periodically generates measurement reports, and the RNC makes a decision after evaluation.In the execution phaseThe RNC executes the handover procedure.Load-based Inter-Frequency Handover ProcedureThe load-based inter-frequency handover suits best in the case of the co-sited cells covering the same area.In the triggering phaseThe Load Reshuffling (LDR) module directly determines whether the current cell is overloaded and whether an inter-frequency handover needs to be performed. The LDR module provides the target cell information for the current cell, and the RNC performs the handover procedure.In the decision phaseThe RNC decides to trigger an inter-frequency blind handover if the conditions are met.If the inter-frequency blind handover can be triggered, the RNC enters the decision phase.If the inter-frequency blind handover cannot be triggered, the RNC does not perform the handover.After the inter-frequency handover is triggered, the RNC chooses a decision algorithm according to whether the conditions of direct blind handover are met. In the execution phaseThe RNC performs the blind handover according to the decision result.Speed-based Inter-Frequency Handover ProcedureFigure 5-2 shows speed-based inter-frequency handover procedure. For HCS speed estimation, see HCS Handover Algorithms.Speed-based inter-frequency handover procedure

In the triggering phaseThe RNC receives the handover request according to the HCS speed estimation. The handover based on HCS speed estimation is of two types: handover from the macro cell to the micro cell and handover from the micro cell to the macro cell. For different types of handover, the RNC acts differently.In the measurement and decision phasesIf the handover is performed from a macro cell to a micro cell, the RNC sends an inter-frequency measurement control message. After the UE reports event 2C, the RNC performs the handover decision. For inter-RAT handover, the UE reports event 3C.If the handover is performed from a micro cell to a macro cell, the RNC directly performs blind handover, ignoring the measurement procedure.In the execution phaseThe RNC initiates a handover procedure.If the handover is performed from a micro cell to a macro cell and the target cell of blind handover is configured (through the parameter BlindHOFlag), the RNC performs blind handover to the target cell.If the blind handover fails or the handover is performed from a macro cell to a micro cell, the RNC starts the inter-frequency (or inter-RAT) measurement procedure. If the inter-frequency measurement mode is employed, the RNC performs the inter-frequency handover procedure to the cell with the best quality after receiving event 2C from the UE.Inter-Frequency Handover MeasurementIn the measurement phase of inter-frequency handover, the UE takes measurement according to the MEASUREMENT CONTROL message received from the RNC. When the measurement report conditions are met, the UE sends measurement reports to the RNC according to the rules defined in the MEASUREMENT CONTROL message.Inter-Frequency Handover Measurement SwitchesSome switches are important for inter-frequency handover because they decide whether the handover can be performed successfully. These switches are the parameter values of Handover algorithm switch in the command SET CORRMALGOSWITCH, as described below.HO_INTER_FREQ_RPRT_2D2F_SWITCH: The switch decides whether the RNC enables the active set quality measurement.If the switch is set to ON, the RNC allows the UE to perform the active set quality measurement.If the switch is set to OFF, the RNC forbids the UE to perform the active set quality measurement.The switch is set to ON by default.HO_MC_SIGNAL_SWITCH: The switch decides when the RNC performs the active set signal quality measurement.If the switch is set to ON, the RNC initiates the active set quality measurement after the RRC connection setup is completed (before the RB setup).If the switch is set to OFF, the RNC initiates the active set quality measurement after the RB setup is completed.The switch is set to OFF by default.HO_INTER_FREQ_HARD_HO_SWITCH: The switch decides whether to enable the inter-frequency handover measurement.If the switch is set to ON, the RNC enables the inter-frequency handover measurement and the load-based inter-frequency handover.If the switch is set to OFF, the RNC disables the inter-frequency handover measurement.The switch is set to ON by default.HO_MC_MEAS_BEYOND_UE_CAP_SWITCH: The switch decides whether the neighboring cell will be sent in the inter-frequency measurement control message when the frequency of the neighboring cell is not included in the measurement capability of the UE. The reported measurement capability of the UE is not the same as the actual measurement capability of the UE. Measurement capability at some frequencies may not be reported due to the limitation of the version of UE protocol.If the switch is set to ON, the RNC sends the inter-frequency measurement control message with the neighboring cell, whose frequency is not included in the measurement capability of the UE.If the switch is set to OFF, the RNC sends the inter-frequency measurement control message without the neighboring cell, whose frequency is not included in the measurement capability of the UE.The switch is set to OFF by default.Inter-Frequency Handover Measurement Report ModesThe event-triggered measurement report mode applies to various handovers. The periodical measurement report mode applies to only load-based and speed-based inter-frequency handovers.The measurement report mode of inter-frequency handover is configured through the parameter InterFreqReportMode.The interval of the measurement reports is configured through the parameter PrdReportInterval.The advantage of periodical measurement report is that if the handover fails, the RNC reattempts the handover to the same cell after receiving the periodical measurement report from the UE. This increases the probability of the success of inter-frequency handover.Based on the measurement control message received from the RNC, the UE periodically reports the measurement quality of the target cell. Then, based on the measurement report, the RNC makes the handover decision and performs handover.Inter-Frequency Handover Measurement QuantityMeasurement quantities vary according to the types of inter-frequency handover.In inter-frequency handover based on coverage, event 2B/2D/2F or periodical measurement takes both CPICH Ec/No and RSCP as measurement quantities. In the triggering phase, events 2D and 2F that correspond to CPICH_Ec/No and CPICH_RSCP are sent from the UE.In the measurement phase, event 2B or periodical measurement that correspond to CPICH_Ec/No and CPICH_RSCP are sent from the UE.In inter-frequency handover based on coverage, the system delivers both CPICH Ec/No and RSCP as measurement quantities to perform 2D/2F measurement. To restrict the types of reported measurement quantities, set the measurement triggering threshold to the minimum value. For example, if the reporting of event 2D of CS service Ec/No is allowed but that of RSCP is restricted, you can set InterFreqCSThd2DRSCP to the minimum value, that is, 115.In inter-frequency handover based on QoS, event 2B or periodical measurement takes both CPICH Ec/No and RSCP as measurement quantities.In inter-frequency handover based on speed, event 2C takes only CPICH Ec/No as measurement quantity.In inter-frequency handover based on load, CPICH RSCP is measured.The UE performs the layer 3 (L3) filtering of measurement values before it judges the measurement event and sends the measurement report. The inter-frequency measurement model is similar to the intra-frequency measurement model. For detailed information, see4.2.1 Intra-Frequency Handover Measurement Quantities for Intra-Frequency Handover. The parameter InterFreqFilterCoef is the filtering coefficient of the inter-frequency measurement value, which is configured on the basis of inter-frequency handover types.Inter-Frequency Handover Measurement EventsWhen the measurement thresholds are reached, the UE reports the events to the RNC to trigger related handover procedures.Table 5-1 describes the measurement events involved in inter-frequency handover.Measurement events involved in inter-frequency handoverEventDescription

2DThe estimated quality of the currently used frequency is below a certain threshold.

2FThe estimated quality of the currently used frequency is above a certain threshold.

2BThe estimated quality of the currently used frequency is below a certain threshold and the estimated quality of a non-used frequency is above a certain threshold.

2CThe estimated quality of a non-used frequency is above a certain threshold.

1FA Primary CPICH becomes worse than an absolute threshold.

Frequency Quality Estimation for Inter-Frequency HandoverIn inter-frequency handover, the reporting criteria of measurement events are based on the frequency quality estimation. The parameter Weight for used frequency specifies the frequency weighing factor that is used to measure the quality of the current frequency. This parameter is used for all event-triggered inter-frequency measurements but not for periodical inter-frequency measurements. The event-triggered measurement events include events 2D, 2F, 2B, and 2C.For detailed information on the quality estimation formula, see section "Frequency Quality Estimate" in 3GPP TS 25.331.Triggering of Event 2DAfter the conditions of event 2D are fulfilled and maintained until the TimeToTrig2D is reached, the UE sends the event 2D measurement report message.Event 2D is triggered on the basis of the following formula:QUsed TUsed2d - H2d/2QUsed is the measured quality of the used frequency.TUsed2d is the absolute quality threshold of the cell that uses the current frequency. Based on the service type and measurement quantity, this threshold can be configured through one of the following parameters:InterFreqCSThd2DEcN0InterFreqR99PsThd2DEcN0InterFreqHThd2DEcN0InterFreqCSThd2DRSCPInterFreqR99PsThd2DRSCPInterFreqHThd2DRSCPThe parameters InterFreqHThd2DRSCP and InterFreqHThd2DEcN0 are valid only when the switch HO_ALGO_OVERLAY_SWITCH is set to ON. Otherwise, the PS domain services will take InterFreqR99PsThd2DEcN0 or InterFreqR99PsThd2DRSCP as a measurement event threshold.For the PS and CS combined services, the threshold is set to the higher one of CS or PS services.If the UE has only signaling connections currently, the thresholds for CS services are used.H2d is the event 2D hysteresis value set through the parameter HystFor2D.Triggering of Event 2FAfter the conditions of event 2F are fulfilled and maintained until the parameter TimeToTrig2F is reached, the UE reports the event 2F measurement report message.Event 2F is triggered on the basis of the following formula:QUsed TUsed2f + H2f/2whereQUsed is the measured quality of the used frequency.TUsed2f is the absolute quality threshold of the cell that uses the current frequency. Based on the service type and measurement quantity, this threshold can be configured through one of the following parameters:InterFreqCSThd2FEcN0InterFreqCSThd2FRSCPInterFreqR99PsThd2FEcN0InterFreqR99PsThd2FRSCPInterFreqHThd2FEcN0InterFreqHThd2FRSCPThe parameters InterFreqHThd2FEcN0 and InterFreqHThd2FRSCP are valid only when the switch HO_ALGO_OVERLAY_SWITCH is set to ON. Otherwise, the PS domain services will take InterFreqR99PsThd2FEcN0 or InterFreqR99PsThd2FRSCP as a measurement event threshold.For the PS and CS combined services, the threshold is set to the higher one of CS or PS services.If the UE has only signaling connections currently, the thresholds for CS services are used.H2f is the event 2F hysteresis value set through the parameter HystFor2F.Conditions of event 2F are as follows: TUsed2d - H2d/2 < TUsed2f + H2f/2, for example, (InterFreqCSThd2DEcN0HystFor2D/ 2) < (InterFreqCSThd2FEcN0+ HystFor2F / 2).Triggering of Event 2BAfter the conditions of event 2B are fulfilled and maintained until the parameter TimeToTrig2B is reached, the UE reports the event 2B measurement report message.Event 2B is triggered on the basis of the following formula:QNoused TNoused2b + H2b/2QUsed TUsed2b - H2b/2whereQNoused is the measured quality of the cell that uses the other frequencies.QUsed is the measured quality of the used frequency.H2b is the event 2B hysteresis value set through the parameter HystFor2B.TNoused2b is the absolute quality threshold of the cell that uses the other frequencies. Based on the service type and measurement quantity, this threshold can be configured through one of the following parameters:TargetFreqCsThdEcN0TargetFreqCsThdRscpTargetFreqR99PsThdEcN0TargetFreqR99PsThdRscpTargetFreqHThdEcN0TargetFreqHThdRscpTUsed2b is the absolute quality threshold of the cell that uses the current frequency.TUsed2b is set in the following way:Based on the service type and measurement quantity, this threshold can be configured through one of the following parameters:If event 2D with the CPICH RSCP value is received by the RNC:TUsed2b of event 2B with the CPICH RSCP value can be:UsedFreqCSThdRSCPUsedFreqR99PsThdRSCPUsedFreqHThdRSCPTUsed2b of event 2B with the CPICH Ec/No value is configured as the maximum value 0 dB.According to 3GPP specifications, TUsed2b of event 2B with the CPICH Ec/No value should be configured as the maximum value 0 dB. If the event 2F with the CPICH Ec/No value is received by the RNC and TUsed2b of event 2B with the CPICH Ec/No value is modified, TUsed2b is reset to 0 dB.If event 2D with the CPICH Ec/No value is received by the RNC:TUsed2b of event 2B with the CPICH Ec/No value can be:UsedFreqCSThdEcN0UsedFreqR99PsThdEcN0UsedFreqHThdEcN0 TUsed2b of event 2B with the CPICH RSCP value is configured as the maximum value 25 dBm.According to 3GPP specification, TUsed2b of event 2B with the CPICH RSCP value should be configured as the maximum value 25 dBm. If event 2F with the CPICH RSCP value is received by the RNC and TUsed2b of event 2B with the CPICH RSCP value is modified, TUsed2b is reset to 25 dBm.

For the PS and CS combined services, the threshold is set to the higher one of CS or PS services.If the UE has only signaling connections currently, the thresholds for CS services are used.

The parameters TargetFreqHThdEcN0, TargetFreqHThdRscp, UsedFreqHThdRSCP, and UsedFreqHThdEcN0 are valid only when the switch HO_ALGO_OVERLAY_SWITCH is set to ON. Otherwise, the PS domain R99 services take UsedFreqR99PsThdEcN0, UsedFreqR99PsThdRSCP, TargetFreqR99PsThdEcN0, or TargetFreqR99PsThdRscp as a measurement event threshold.Triggering of Event 2CAfter the conditions of event 2C are fulfilled and maintained until the parameter TrigTime2C is reached, the UE reports the event 2C measurement report message..Event 2C is triggered on the basis of the following formula:QNoused TNoused2c + H2c/2whereQNoused is the measured quality of the cell that uses the other frequencies.TNoused2c is the absolute quality threshold of the cell that uses the other frequencies, namely

Date post:	06-Nov-2015
Category:	Documents
Upload:	muhammad-abdur-razzaqe
View:	223 times
Download:	9 times