Load Control

7/18/2019 Load Control

1/143

Contents

1 About This Document

1.1 Scope

1.2 Intended Audience

1.3 Change History

2 Overview

2.1 Load Control in Different Scenarios

2.2 Functions of Load Control

2.3 Priorities Involved in Load Control

2.3.1 User Priority

2.3.2 Integrated RAB Priority

2.3.3 Integrated User Priority

WCDMA RAN

RAN15.0

Load Control Feature Parameter Description

Issue 01

Date 2013-04-28

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 tr ademarks an d trade na mes ment ioned in th is document a re the prope rty of their r espective hold ers.

NoticeThe purchased products, services and features are stipulated by the contract made between H uawei and the customer. All or part of the p roducts, services and features described in this documentmay 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 a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Ind ustrial Base Ba ntian, Lon ggang She nzhen 518 129 People 's Republic o f China

Website: http://www.huawei.com

Email: [email protected]

Page 1 of 143Load Control Feature Parameter Description

6/3/2014http://localhost:7890/pages/GEC0207J/02/GEC0207J/02/resources/en-us_...
http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22


2/143

3 Load Measurement

3.1 Load-related Measurement Quantities

3.2 Reporting Period

3.3 Load Measurement Filtering

3.3.1 Layer 3 Filtering on the NodeB Side

3.3.2 Smooth Filtering on the RNC Side

3.4 Auto-Adaptive Background Noise Update Algorithm

4 Intelligent Access Control

4.1 Overview of Intelligent Access Control

4.2 IAC During RRC Connection Setup

4.2.1 Procedure of IAC During RRC Connection Setup

4.2.2 Inter-RAT RRC Redirection Based on Weak Coverage

4.2.3 RRC Redirection Based on Distance

4.2.4 RRC Redirection for Service Steering

4.2.5 RRC DRD

4.2.6 RRC Redirection After DRD Failure

4.2.7 FACH Power Control During RRC Phase

4.3 Directed Retry Decision

4.4 Rate Negotiation at Admission Control

4.4.1 PS MBR Negotiation

4.4.2 PS GBR Negotiation

4.4.3 Initial Rate Negotiation

4.4.4 Target Rate Negotiation

4.5 Admission Decision

4.6 Preemption

4.7 Queuing

4.8 Low-Rate Access of the PS BE Service

4.9 IAC for Emergency Calls

4.9.1 RRC Connection Setup Procedure of Emergency Calls

4.9.2 RAB Process of Emergency Calls

5 Intra-Frequency Load Balancing

5.1 Overview

5.2 TCP-based Intra-Frequency Load Balancing

5.3 RTWP-based Intra-Frequency Load Balancing

6 Load Reshuffling

6.1 Basic Congestion Triggering

6.1.1 Power Resource

6.1.2 Code Resource

6.1.3 Iub Resource

6.1.4 NodeB Credit Resource

6.2 LDR Procedure

6.3 LDR Actions

6.3.1 Load-based Inter-Frequency Handover

6.3.2 BE Rate Reduction

6.3.3 QoS Renegotiation for Uncontrollable Real-Time Services

6.3.4 Inter-RAT Handover in the CS Domain

6.3.5 Inter-RAT Handover in the PS Domain

6.3.6 AMR Rate Reduction

6.3.7 Code Reshuffling

6.3.8 MBMS Power Reduction

6.3.9 PS Inter-RAT Handover from UMTS to LTE

6.3.10 LDR Actions for a UE in the Uplink and Downlink

7 Network Impact

7.1 RRC Redirection for Service Steering

7.1.1 System Capacity7.1.2 Network Performance

7.2 FACH Power Control of RRC Phase

7.2.1 System Capacity

7.2.2 Network Performance

8 Engineering Guidelines

8.1 WRFD-021104 Emergency Call

8.1.1 Deployment

8.2 WRFD-010506 RAB Quality of Service Renegotiation over Iu Interface

8.2.1 Deployment

8.3 WRFD-020102 Load Measurement

8.3.1 Deployment

8.4 WRFD-020106 Load Reshuffling

8.4.1 Deployment

8.5 WRFD-020108 Code Resource Management

8.5.1 Deployment8.6 WRFD-020401 Inter-RAT Redirection Based on Distance

8.6.1 Deployment

8.7 WRFD-02040003 Inter System Redirect


http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22


3/143

8.7.1 When to Use Inter System Redirect

8.7.2 Required Information

8.7.3 Deployment

8.8 WRFD-020120 Service Steering and Load Sharing in RRC Connection Se tup

8.8.1 When to Use Service Steering and Load Sharing in RRC Connection Setup


8.8.3 Planning

8.8.4 Deployment

8.8.5 Performance Monitoring

8.8.6 Parameter Optimization

8.8.7 Troubleshooting

8.9 FACH Power Control of RRC Phase

8.9.1 When to Use FACH Power Control of RRC Phase


8.9.3 Planning

8.9.4 Deployment

8.9.5 Performance Monitoring

8.9.6 Parameter Optimization

8.9.7 Troubleshooting

8.10 WRFD-020104 Intra Frequency Load Balance

8.10.1 When to Use Intra Frequency Load Balance


8.10.3 Deployment

8.11 WRFD-010505 Queuing and Preemption

8.11.1 When to Use Queuing and Preemption8.11.2 Required Information

8.11.3 Deployment

8.12 WRFD-010507 Rate Negotiation at Admission Control

8.12.1 When to Use Rate Negotiation at Admission Control


8.12.3 Deployment

9 Parameters

10 Counters

11 Glossary

12 Reference Documents

1 About This Document

1.1 Scope

This document describes features related to load control and the related parameters.

1.2 Intended Audience

This document is intended for personnel who:

l Are familiar with WCDMA basics

l Work with Huawei WCDMA 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:

l Feature change: refers to a change in the Load Control feature.

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

Document Versions

The document issue is as follows:

l 01 (2013-04-28)

l Draft A (2013-01-30)

01 (2013-04-28)

This is a first commercial release of RAN15.0.

Compared with Draft A(2013-01-30) of RAN15.0, 01 (2013-04-28) of RAN15.0 includes the following changes.

Change Type Change Description Parameter Change

Feature change None None

Editorial change Added Table 3-1. None

WRFD-020103 Inter-Frequency Load Balancing (Load-based Inter-Frequency Handover) is taken out to form aseparate document Inter-Frequency Load Balancing Feature Parameter Description.

None

WRFD-150216 Load Based PS Redirection from UMTS to LTE feature and WRFD-150217 Load Based PSHandover from UMTS to LTE are taken out to form a separate document Interoperability Between UMTS and LTEFeature Parameter Description.

None

Anti-Imbalance of the Different Antenna is taken out to form a separate documentAnti-Imbalance of the DifferentAntenna Feature Parameter Description.

None

WRFD-140217 Inter-Frequency Load Balancing Based on Configurable Load Threshold is taken out to form aseparate document Inter-Frequency Load Balancing Based on Configurable Load Threshold Feature ParameterDescription.

None


http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22


4/143

Draft A (2013-01-30)

This is a draft for RAN15.0.

Compared with issue 02 (2012-07-20) of RAN14.0, Draft A (2012-12-30) of RAN15.0 includes the following changes.

2 Overview

The WCDMA system is a self-interfering system. As the load of the system increases, the interference rises. A relatively high interference can affect the coverage of cells and QoSof ongoing services. To solve this problem, the load control function is introduced to control the load in a cell.

Load control aims to maximize the system capacity while ensuring coverage and QoS by controlling the key resources, such as power, downlink channelization codes, channelelements (CEs), and Iub transmission resources.

Each cell has its own set of load control functions that are responsible for monitoring and controlling the resources of the cell. The load control functions monitor the load of a cellthrough load measurement, make the admission decision for services through intelligent access control and call admission control, and reduce congestion in the cell.

2.1 Load Control in Different Scenarios

Different load control functions are used, as shown in the following figure.

Figure 2-1 Load control functions in different UE access phases

The load control functions that are applied are as follows:

l Before UE access: Potential User Control (PUC)

l During UE access: Intelligent Access Control (IAC) and Call Admission Control (CAC)

l After UE access: Inter-Frequency Load Balancing Based on Configurable Load Threshold(CLB), intra-frequency Load Balancing (LDB), Load Reshuffling (LDR), and OverloadControl (OLC)

The following sections provide detailed information about the load control functions performed in these phases.

2.2 Functions of Load Control

Load control is implemented on the RNC after obtaining measurement reports from the NodeB.

WRFD-02040005 Inter-Frequency Redirection Based on Distance is taken out to form a separate document Inter-Frequency Redirection Based on Distance Feature Parameter Description.

None

WRFD-150236 Load Based Dynamic Adjustment of PCPICH is taken out to form a separate document LoadBased Dynamic Adjustment of PCPICH Feature Parameter Description.

None

WRFD-020107 Overload Control is taken out to form a separate document Overload Control Feature ParameterDescription.

None

WRFD-020105 Potential User Control is taken out to form a separate document Potential User Control FeatureParameter Description.

None

Change Type Change Description Parameter Change

Feature change Optimized the RRC Redirection for Service Steering feature. Added network impact andengineering guidelines for this feature. For details, see following sections:

l 4.2.4 RRC Redirection for Service Steering

l 7.1 RRC Redirection for Service Steeringin 7 Network Impact

l 8.8 WRFD-020120 Service Steering and Load Sharing in RRC Connection Setupin 8Engineering Guidelines.

Added the RedirEcN0Thd(BSC6900,BSC6910)parameter

Added the FACH power control of RRC phase function. For details, see following sections:

l 4.2.7 FACH Power Control During RRC Phase

l 7.2 FACH Power Control of RRC Phasein 7 Network Impact

l 8.9 FACH Power Control of RRC Phasein 8 Engineering Guidelines.

Added the following parameters:

l T381(BSC6900,BSC6910)

l N381(BSC6900,BSC6910)

l T300(BSC6900,BSC6910)

l RrcCause(BSC6900,BSC6910)

l FACHPower4RRCRepEcNoThd(BSC6900,BSC6910)

l MaxFachPower(BSC6900,BSC6910)

l SIGRBIND(BSC6900,BSC6910)

l TrChId(BSC6900,BSC6910)

l OffsetFACHPower(BSC6900,BSC6910)

Added the initial rate negotiation for CS+PS BE combined services function. For details, seeInitial Rate Negotiation for the PS BE Service in CS+PS Combined Servicesin section 4.4Rate Negotiation at Admission Control.

Added the following parameters:

l BeInitBitrateTypeforCsPs(BSC6900,BSC6910)

l ReservedSwitch0(BSC6900,BSC6910):RESERVED_SWITCH_0_BIT11



Added descriptions about the Macro & Micro Joint Inter-frequency Redirection feature. Fordetails, see 4.2.1 Procedure of IAC During RRC Connection Setup.

None

Updated descriptions about queuing and preemption for DB-HSDPA and 4C-HSDPA services.For details, see section 4.6 Preemptionand section 4.7 Queuing.

None

Introduced the CE resource preemption enhancement function. For details, see the following

(sub)sections:

l Forced Preemptionin section 4.6 Preemption.

l 8.11 WRFD-010505 Queuing and Preemption

Added the PreemptEnhSwitch(BSC6900,BSC6910):

PREEMPT_ENH_NODEB_PREEMPT_CE_SWITCHparameter

Changed the algorithm of the WRFD-020104 Intra-Frequency Load Balance feature to TCP-based intra-frequency load balancing. For details, see section 5 Intra-Frequency LoadBalancing.

None

Editorial change None None


http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22


5/143

Figure 2-2 Load control function in the WCDMA system

The load control functions are described as follows:

l PUC

The function of PUC is to balance traffic load among cells on different frequencies. The RNC uses PUC to modify cell selection and reselection parameters, and broadcaststhem through system information. In this way, UEs are directed to the lightly loaded cells. The UEs can be in idle mode, CELL_FACH state, CELL_PCH state, or URA_PCHstate.

For the details of PUC, see Potential User Control Feature Parameter Description.

l IAC

The function of IAC is to increase the access success rate with the current QoS guaranteed through rate negotiation, queuing, preemption, and directed retry decision (DRD).For details about DRD, see Directed Retry Decision Feature Parameter Description.

l CAC

The function of CAC is to decide whether to accept resource requests from UEs, such as access, reconfiguration, and handover requests, depending on the resource status ofthe cell.

For details about CAC, see Call Admission Control Feature Parameter Description.

l CLB

The function of CLB is to initiate the procedure of inter-frequency load balancing when a cell is not congested, thereby ensuring load balancing among cells. This functionsupports intra- and inter-RNC load balancing. CLB may occur before LDR. That is, the RNC can perform inter-frequency load balancing before a cell is congested.

For details, see Inter-Frequency Load Balancing Based on Configurable Load Threshold Feature Parameter Description.

l LDB

The function of intra-frequency LDB is to balance the cell load between intra-frequency neighboring cells to improve resource utilization. When the load of a cell increases, thecell reduces its coverage to decrease its load. When the load of a cell decreases, the cell extends its coverage so that that cell can take over some traffic from its neighboringcells.

l LDR

The function of LDR is to reduce the cell load when the cell enters the basic congestion state. The purpose of LDR is to increase the access success rate by taking thefollowing actions:

n Load-based inter-frequency handover

n BE service rate reduction

n QoS renegotiation for uncontrollable real-time services

n Load-based CS inter-RAT handover

n Load-based PS inter-RAT handover

n AMR voice service rate reduction

n Code reshuffling

n MBMS power reduction

n PS inter-RAT handover from UMTS to LTE

l OLC

The function of OLC is to reduce the cell load rapidly when the cell is overloaded. The purpose of OLC is to ensure the system stability and the QoS of most UEs in thefollowing ways:

n Restricting the Transport Format (TF) of the BE service

n Switching BE services to common channels

n Adjusting the maximum transmit power of FACHs

n Releasing RABs

For details about OLC, see Overload Control Feature Parameter Description.

Table 2-1lists the resources that are involved in different load control functions.

Table 2-1 Resources involved in different load control functions

2.3 Priorities Involved in Load Control

Different types of priorities are used in load control to preferentially ensure the QoS of high priority services or users.

The priorities involved in load control are user priority, integrated radio access bearer (RAB) priority, and integrated user priority.

Load Control Function Resources

Power Code NodeB Credit Iub Bandwidth

CAC

IAC

PUC - - -

CLB -

LDB - - -

LDR

OLC - -

NOTE:

-: not involved

: involved


http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22


6/143

2.3.1 User Priority

User priorities are adopted to provide differentiated services for users. For ease of application, the RNC maps the 15 levels of Allocation/Retention Priority (ARP) that is carried inthe RAB ASSIGNMENT REQUEST message from the core network (CN) onto three user priorities, that is, gold (high priority), silver (medium priority), and copper (low priority).The relationship between user priority and ARP can be set by running the SET UUSERPRIORITYcommand. Table 2-2shows the typical relationship between user priorities and

ARPs.

Table 2-2 Typical relationship between user priorities and ARPs

NOTE:

If ARP is not received in messages from the Iu interface, the user priority is copper.

2.3.2 Integrated RAB Priority

The priority of an RAB is determined by its traffic class, ARP, and carrier type. Such a priority is called integrated RAB priority. When resources are insufficient, services with thehighest integrated priority are preferentially processed.

The values of integrated RAB priority are determined based on the integrated priority configuration reference parameter PriorityReference(BSC6900,BSC6910):

l If PriorityReference(BSC6900,BSC6910)is set to Traffic Class, the integrated priority abides by the following rules:

n Traffic classes: conversational > streaming > interactive > background

n Services of the same traffic class are prioritized based on ARP, that is, ARP1 > ARP2 > ARP3 > ... > ARP14 >ARP15

n Service of the same traffic class and ARP (only for interactive services) are prioritized based on Traffic Handling Priority (THP) that is carried in the RAB ASSIGNMENTREQUEST message, that is, THP1 > THP2 > THP3 > ... > THP14 > THP15

n Services of the same traffic class, ARP and THP (only for interactive services) are prioritized as follows: High Speed Packet Access (HSPA) or Dedicated Channel (DCH)service are preferred depending on CarrierTypePriorInd(BSC6900,BSC6910).

l If PriorityReference(BSC6900,BSC6910)is set to ARP, the integrated priority abides by the following rules:

n ARP: ARP1 > ARP2 > ARP3 > ... > ARP14 >ARP15

n Services of the same ARP: priority based on traffic classes, that is, conversational > streaming > interactive > background

n Only for the interactive service of the same ARP value: priority based on Traffic Handling Priority (THP), that is, THP1 > THP2 > THP3 > ... > THP14 >THP15

n Services of the same ARP, traffic class and THP (only for interactive services): HSPA or DCH service are preferred depending on CarrierTypePriorInd(BSC6900,BSC6910).

2.3.3 Integrated User Priority

A user may have multiple RABs, and the RABs may have different priorities. In this case, the highest priority is considered as the priority of this user. Such a priority is called theintegrated user priority. Integrated user priority is used in user-specific load control. For example, the selection of R99 users during preemption, the selection of users during load-based inter-frequency handover for LDR, and the selection of users during switching of BE services to common channels are performed based on the integrated user priority.

3 Load Measurement

This chapter describes the WRFD-020102 Load Measurement feature.

The load control functions, such as OLC and CAC, use load measurement values in the uplink and the downlink. A common Load Measurement (LDM) function is used to control

load measurement in the uplink and the downlink separately.Load measurement is implemented by the NodeB. The filtering of measurement quantities is implemented by the NodeB and the RNC.

3.1 Load-related Measurement Quantities

The major load-related measurement quantities are as follows:

l Uplink Received Total Wideband Power (RTWP)

n When the feature WRFD-020137 Dual-Threshold Scheduling with HSUPA Interference Cancellation is not enabled, the RNC uses the measured RTWP value.

n When the feature WRFD-020137 Dual-Threshold Scheduling with HSUPA Interference Cancellation is enabled, the RNC uses the RTWP value after interferencecancellation if UlIcLdcOptSwitch(BSC6900,BSC6910)is set to OFF; the RNC uses the larger one between the following if UlIcLdcOptSwitch(BSC6900,BSC6910)isset to ON:

Measured RTWP value MaxDeltaOfTargetRoT

RTWP value after interference cancellation

For details about the feature WRFD-020137 Dual-Threshold Scheduling with HSUPA Interference Cancellation, see HSUPA Feature Parameter Description.

NOTE:

OLC always uses the measured RTWP value regardless of if the RNC uses the measured RTWP value. For details about OLC, see Overload Control Feature Parameter

Description.

l Downlink Transmitted Carrier Power (TCP)

l Non-HSPA power: TCP excluding the power used for transmission on HSPA channels. For detailed information about HSPA channels, see HSDPA Feature ParameterDescriptionand HSUPA Feature Parameter Description.

NOTE:

l Power load states are used to determine downlink cell load as show in Table 3-1.Downlink load in an HSDPA cell is the proportion of non-HSPA power consumption asagainst the maximum transmit power of this cell MaxTxPower(BSC6900,BSC6910). Downlink load in an R99 cell is the proportion of TCP as against the maximum transmitpower of this cell.

Table 3-1 Downlink power load state

ARP 1 2 3 4 5 6 7 8

User Priority Gold Gold Gold Gold Gold Silver Silver Silver

ARP 9 10 11 12 13 14 15

User Priority Silver Silver Copper Copper Copper Copper Copper

Load State Load State Transition

(Transitions of load state are controlled by thresholds. A 10% hysteresis is added to the thresholds to avoid ping-pong state transitions)

Light State If the load is larger than 30%+10%, the state transits from light state to normal state.

Normal State If the load is smaller than 30%-10%, the state transits from normal state to light state.

If the load is larger than 50%+10%, the state transits from normal state to loaded state.

Loaded State If the load is smaller than 50%-10%, the state transits from loaded state to normal state.

If the load is larger than 50%+10%, the state transits from loaded state to heavy state.

Heavy State If the load is smaller than 70%-10%, the state transits from heavy state to loaded state.


http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22


7/143

l Provided Bit Rate (PBR) on HS-DSCH. For details about PBR, see 3GPP25.321.

l Power Requirement for GBR (GBP) on HS-DSCH: minimum power required to ensure the GBR on HS-DSCH

l PBR on E-DCH Light State, Normal State, Loaded State, Heavy State, Overload State

l Received Scheduled E-DCH Power Share (RSEPS): power of the E-DCH scheduling service in the serving cell

l Uplink total load: sum of R99 service load, HSUPA service load, and control channel load. The uplink total load measurement depends on the NodeB hardware.

l Uplink minimum guaranteed load: sum of R99 service load, HSUPA service load required by the HSUPA GBR, and control channel load. The uplink minimum guaranteed loadmeasurement depends on the NodeB hardware.

The HSUPA GBR is calculated as follows:

n If the function uplink enhanced L2 is disabled, GBR = max (bit rate of one RLC PDU, GBR).

n If the function uplink enhanced L2 is enabled, GBR = max (bit rate of the smallest RLC PDU, GBR).

The NodeB measures the major factors related to load control. After layer 1 and layer 3 filtering, the measurement values are reported to the RNC through the COMMONMEASUREMENT REPORT message.

The RNC performs smooth filtering of the measurement values reported from the NodeB and then obtains the measurement values, which further serve as data input for the loadcontrol algorithms.

The RNC calculates the actual uplink load based on the filtered RTWP, uplink total load, and uplink minimum guaranteed load. The actual uplink load is one of the factors for theuplink load-related algorithms.

NOTE:

If the interference of antennas in one NodeB is imbalanced, the measured RTWP may be inaccurate. In this situation, the anti-imbalance of the different antenna algorithm can beused to correct the inaccurate measurement results and reflect the actual cell load. For details, see Anti-Imbalance of the Different Antenna Feature Parameter Description

Figure 3-1shows the LDM procedure.

Figure 3-1 LDM procedure

3.2 Reporting Period

The NodeB periodically reports each measurement quantity to the RNC. The following table lists the reporting period parameters for setting different measurement quantities.

3.3 Load Measurement Filtering

3.3.1 Layer 3 Filtering on the NodeB Side

The following figure shows the measurement model at the physical layer, which complies with 3GPP 25.302.

Figure 3-2 Measurement model at the physical layer

If the load is larger than 95%, the state transits from heavy state to overload state.

Overload State If the load is smaller than 95%-10%, the state transits from overload state to heavy state.

Measurement Quantity Reporting Period Parameter

RTWP ChoiceRprtUnitForUlBasicMeas(BSC6900,BSC6910)

TenMsecForUlBasicMeas(BSC6900,BSC6910)

MinForUlBasicMeas(BSC6900,BSC6910)

ChoiceRprtUnitForDlBasicMeas(BSC6900,BSC6910)

TenMsecForDlBasicMeas(BSC6900,BSC6910)

MinForDlBasicMeas(BSC6900,BSC6910)

RSEPS

TCP

Non-HSPA power

Uplink total load

Uplink minimum guaranteed load

GBP ChoiceRprtUnitForHsdpaPwrMeas(BSC6900,BSC6910)

TenMsecForHsdpaPwrMeas(BSC6900,BSC6910)MinForHsdpaPwrMeas(BSC6900,BSC6910)

HS-DSCH PBR ChoiceRprtUnitForHsdpaRateMeas(BSC6900,BSC6910)

TenMsecForHsdpaPrvidRateMeas(BSC6900,BSC6910)

MinForHsdpaPrvidRateMeas(BSC6900,BSC6910)

E-DCH PBR ChoiceRprtUnitForHsupaRateMeas(BSC6900,BSC6910)

TenMsecForHsupaPrvidRateMeas(BSC6900,BSC6910)

MinForHsupaPrvidRateMeas(BSC6900,BSC6910)




8/143

In Figure 3-2:

l A is the sampling value of the measurement.

l B is the measurement value after layer 1 filtering.

l C is the measurement value after layer 3 filtering.

l C' is another measurement value (if any) for measurement evaluation.

l D is the reported measurement value.

Layer 1 filtering is not standardized by protocols. It depends on vendor equipment. Layer 3 filtering is standardized. The filtering effect is controlled by a higher layer. The alphafiltering that applies to layer 3 filtering is calculated using the following formula:

where

l Fnis the new post-filtering measurement value.

l Fn-1is the last post-filtering measurement value.

l Mnis the new measurement value from the physical layer.

l = (1/2)k/2, k is the measure filter coefficient which is specified as follows:

n For load control algorithms (excluding OLC), k is specified by the UlBasicCommMeasFilterCoeff(BSC6900,BSC6910)or DlBasicCommMeasFilterCoeff(BSC6900,BSC6910)parameter.

n For OLC algorithm, k is specified by the UlOlcMeasFilterCoeff(BSC6900,BSC6910)or DlOlcMeasFilterCoeff(BSC6900,BSC6910)parameter.

3.3.2 Smooth Filtering on the RNC Side

After the RNC receives the measurement report, it filters the measurement value using the smooth window method.

If the reported measurement value is Qnand the length of the smooth window is N, then the filtered measurement value is

LDM must apply different smooth window length and measurement periods to PUC, CAC, LDR, and OLC to obtain appropriate filtered values.

The following table lists the smooth window length parameters that are used to set different functions.Table 3-2 The smooth window length parameters for setting different functions

NOTE:

GBP measurements have the same smooth window length in all related functions. The filter length for GBP measurement is specified by the HsdpaNeedPwrFilterLen

(BSC6900,BSC6910)parameter.The length of the PBR smooth filter window is specified by the HsdpaPrvidBitRateFilterLen(BSC6900,BSC6910)/ HsupaPrvidBitRateFilterLen(BSC6900,BSC6910)parameter.

CLB measurements have the same smooth window length as LDR.

3.4 Auto-Adaptive Background Noise Update Algorithm

Uplink (UL) background noises are sensitive to environmental conditions, and the fluctuation of the background noises has a negative impact on the RTWP measurement value.Therefore, the LDM function uses an auto-adaptive update algorithm to restrict the background noise within a specified range.

l If the temperature in the equipment room is constant, the background noise changes slightly. In this case, the background noise requires no adjustment after initial correction.

l If the temperature in the equipment room varies with the ambient temperature, the background noise changes greatly. In this case, the background noise requires auto-adaptive upgrade.

The following figure shows the flow chart of auto-adaptive background noise update, which is enabled by the BGNSwitch(BSC6900,BSC6910)parameter.

NOTE:

BGNSwitch(BSC6900,BSC6910)is set to ONby default.

Figure 3-3 Flow chart of auto-adaptive background noise update

FunctionSmooth Window Length Parameter Function

PucAvgFilterLen(BSC6900,BSC6910) PUC

UlCacAvgFilterLen(BSC6900,BSC6910)

DlCacAvgFilterLen(BSC6900,BSC6910)

CAC

LdbAvgFilterLen(BSC6900,BSC6910) LDB

UlLdrAvgFilterLen(BSC6900,BSC6910)

DlLdrAvgFilterLen(BSC6900,BSC6910)

LDR

UlOlcAvgFilterLen(BSC6900,BSC6910)

DlOlcAvgFilterLen(BSC6900,BSC6910)

OLC




9/143

NOTE:

l The Alpha filter formula is: Fn = (1 - ) x Fn-1+ x Mn (n1). For details about this formula, see section 3.3.1 Layer 3 Filtering on the NodeB Side

l Counting threshold = (Duration of background noise)/(RTWP reporting period). The duration of background noise is used in auto-adaptive upgrade decision and is set by theBGNAdjustTimeLen(BSC6900,BSC6910)parameter. For the setting of RTWP reporting period, see section 3.2 Reporting Period.

The procedure for auto-adaptive background noise update is as follows:

1. The RNC initializes the counter and filter that are used for auto-adaptive upgrade and sets the initial value (F0) of the filter to BackgroundNoise(BSC6900,BSC6910).

2. The RNC receives the latest RTWP measurement value and uplink total load measurement value from the physical layer.

3. The RNC checks whether the current time is within the effective period of the algorithm, that is, whether the current time is later thanBgnStartTime(BSC6900,BSC6910)andearlier than BgnEndTime(BSC6900,BSC6910).

If the current time is within the effective period, then:

l If BGNOptSwitch(BSC6900,BSC6910) is set to OFF, Mn= the latest RTWP measurement value. The procedure goes to 4 (a).

l If BGNOptSwitch(BSC6900,BSC6910)is set to ON, Mn= the latest RTWP measurement value - uplink total load measurement value. The procedure goes to 4 (b).

If the current time is not within the effective period, the RNC waits for the next RTWP measurement value and uplink total load measurement value.

NOTE:The uplink total load measurement depends on the NodeB hardware. For details, see 3.1 Load-related Measurement Quantities. When the uplink total load measurement isinvalid, background noise update is not performed. The initial value of the filter is set to the current background noise.




10/143

4. The RNC does the following:

(a). The RNC determines whether the current Equivalent Number of Users (ENU) in the cell is greater than the value of BGNEqUserNumThd(BSC6900,BSC6910):

l If the current ENU is greater than the value of BGNEqUserNumThd(BSC6900,BSC6910), the RNC infers that Mnincludes other noises in addition to the background

noise, and does not feed Mnto the filter. In addition, the RNC sets t he counter to zero, retains the current background noise, and sets the initial value of the filter to the

current background noise. The background noise update procedureends. The RNC waits for the next RTWP measurement value and uplink total load measurementvalue.

l If the current ENU in the cell is smaller than or equal to the value of BGNEqUserNumThd(BSC6900,BSC6910), the RNC feeds Mnto the filter and performs the next

step.

(b). The RNC determines whether the uplink total load measurement value is greater than the value of BGNULLoadThd(BSC6900,BSC6910):

l If the latest uplink total load measurement value is greater than the value of BGNULLoadThd(BSC6900,BSC6910), the RNC sets the counter to zero, retains the currentbackground noise, and sets the initial value of the filter to the current background noise. The background noise update procedure ends. The RNC waits for the nextRTWP measurement value and uplink total load measurement value.

l If the latest uplink total load measurement value is smaller than or equal to the value of BGNULLoadThd(BSC6900,BSC6910), the RNC feeds Mnto the filter and

performs the next step.

5. The RNC checks whether Mn

- Fn-1

is smaller than the value of BgnAbnormalThd(BSC6900,BSC6910). If it is smaller than this threshold value, the RNC increments the

counter by one, calculates Fnaccording to the Alpha filter formula, and performs the next step. Otherwise, the RNC waits for the next RTWP measurement value.

6. The RNC checks whether the counter reaches the counting threshold. If it reaches the counting threshold, the RNC performs the next step. Otherwise, the RNC waits for thenext RTWP measurement value.

7. The RNC checks whether Fn - BackgroundNoise(BSC6900,BSC6910) is smaller than the value of BgnAbnormalThd(BSC6900,BSC6910). The purpose is to prevent

burst interference and RTWP spike. If it is smaller than the value of BgnAbnormalThd(BSC6900,BSC6910), the RNC performs the next step. Otherwise, the RNC sets thecounter to zero and waits for the next RTWP measurement value.

8. The RNC checks whether Fn- current background noise is greater than the value of BgnUpdateThd(BSC6900,BSC6910). The purpose is to prevent frequent background

noise upgrades on the Iub interface. If it is greater than the value of BgnUpdateThd(BSC6900,BSC6910)the RNC sets the current background noise to Fn, sets the counter

to zero, and waits for the next RTWP measurement value. Otherwise, the RNC sets the counter to zero and waits for the next RTWP measurement value.

4 Intelligent Access Control

4.1 Overview of Intelligent Access Control

IAC is used to increase the access success rate, that is, RRC connection success rate and RAB setup success rate.

There are two types of IAC, namely, IAC for RRC connection processing and IAC for RAB connection processing.

l IAC for RRC connection processing is used to select a suitable cell for a UE to access through redirection and RRC DRD. It also implements load balancing and servicesteering.

l IAC for RAB connection processing is used to select a suitable cell for a UE to access through DRD and CAC. It also implements load balancing and service steering.Features such as preemption, queuing, and low-rate access are used to further improve the RAB setup success rate.

In addition, IAC provides differentiated services for users with different priorities. For example, when the system resources are insufficient, procedures such as direct admission,preemption, and redirection can be performed to ensure access for emergency calls to the network.

Figure 4-1shows a typical procedure for service access control.

Figure 4-1 Service access control procedure

As shown in Figure 4-1, the procedure for service access includes the procedures for RRC connection setup and RAB setup. The successful setup of the RRC connection is one ofthe prerequisites for the RAB setup.

During the RRC connection processing, the RNC performs the following steps.

1. Performs RRC redirection based on distance (only for UE-originating AMR services). For details, see 4.2.3 RRC Redirection Based on Distance. If the RNC decides toimplement UE access from another cell, it sends an RRC connection reject message to the UE; otherwise, the RNC performs the next step.

2. Performs RRC redirection for service steering. For details, see section 4.2.4 RRC Redirection for Service Steering.

l If the RNC decides to implement UE access from the current cell, it then makes a resource-based admission decision. If the resource-based admission fails, the RNCperforms DRD and redirection.

l If the RNC decides to implement UE access from another cell, it then sends an RRC connection reject message to the UE. The message carries the information aboutthe cell and instructs the UE to set up an RRC connection to the cell.

For details, see section 4.2 IAC During RRC Connection Setup.

During the RAB connection processing, the RNC performs the following steps:

1. Performs inter-frequency DRD to select a suitable cell for service steering or load balancing. For details about DRD, see Directed Retry Decision Feature ParameterDescription.

2. Performs rate negotiation according to the service requested by the UE. For details, see section 4.4 Rate Negotiation at Admission Control.


http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22


11/143

3. Makes cell resource-based admission decision. If the admission is successful, UE access is granted. Otherwise, the RNC performs the next step. For details about admissiondecision, see Call Admission Control Feature Parameter Description.

4. Selects a suitable cell from the cells where no admission attempt has been made, based on the inter-frequency DRD, and then performs step 5. If all the attempts fail, theRNC performs the next step.

5. Selects a suitable cell according to the inter-RAT DRD. If the inter-RAT admission is successful, UE access is granted in the inter-RAT cell. If the inter-RAT DRD fails or is notsupported, the RNC performs the next step.

6. Makes a preemption attempt. For details about preemption, see section 4.6 Preemption. If the preemption is successful, UE access is granted. If the preemption fails or is notsupported, the RNC performs the next step.

7. Makes a queuing attempt. For details about queuing, see section 4.7 Queuing.

8. If the queuing is successful, UE access is granted. If the queuing fails or is not supported, the RNC performs the next step.

9. Performs low-rate access. For details about low-rate access, see section 4.8 Low-Rate Access of the PS BE Service. If the low-rate access is admitted, UE access is granted.If the low-rate access fails, the RNC performs the next step.

10. Rejects UE access.

NOTE:

After the admission attempts of an HSPA service request fail in all candidate cells, the service falls back to the DCH for network access.

Table 4-1 IAC procedure supported by services

4.2 IAC During RRC Connection Setup

4.2.1 Procedure of IAC During RRC Connection Setup

Before a new service is admitted to the network, an RRC connection must be set up.

As shown in Figure 4-2, when the switch DrSwitch(BSC6900,BSC6910): DR_RRC_DRD_SWITCHis set to ON, the RRC connection setup procedure is performed as follows:

NOTE:

Inter-RAT RRC redirection based on weak coverage is controlled by the switch PerfEnhanceSwitch: PERFENH_RRC_WEAK_REDIR_SWITCH, not by the switch DrSwitch:DR_RRC_DRD_SWITCH.

Figure 4-2 RRC connection setup procedure

Service Type Low-RateAccess

Rate Negotiation Preemption Queuing DRD

MBRNegotiation

GBRNegotiation

Initial RateNegotiation

Target RateNegotiation

Inter-

Frequency

Inter-RAT

DCH

HSUPA - -

HSDPA - - - -




12/143

After receiving an RRC CONNECTION REQUEST message from the UE, the RNC performs inter-RAT RRC redirection based on weak coverage ifPERFENH_RRC_WEAK_REDIR_SWITCHunder the PerfEnhanceSwitch(BSC6900,BSC6910)parameter is selected. If this check box is not selected, the RNC performs theRRC redirection based on distance (only for UE-originating AMR services). For details, see section 4.2.3 RRC Redirection Based on Distance. If the RNC decides to implement UEaccess from another cell, it sends an RRC connection reject message to the UE; otherwise, the RNC performs the next step.

Then, the RNC uses the RRC redirection algorithm for service steering and Macro & Micro Joint Inter-Frequency Redirection to determine whether the UE can access the networkfrom the current cell:

l If the UE can access the network from the current cell according to the decision result, the RNC uses the CAC algorithm to determine whether an RRC connection can be setup between the UE and the current cell.

n If the RRC connection can be set up between the UE and the current cell, the RNC sends an RRC CONNECTION SETUP message to the UE.




13/143

n If the RRC connection cannot be set up between the UE and the current cell, the RNC attempts to select a cell for RRC connection setup through RRC DRD. If the RRCDRD fails, RRC redirection will be performed.

l If the RNC determines to implement access for the UE from another cell, the RNC sends an RRC CONNECTION REJECT message to the UE. The message carries theinformation about this cell.

DrSwitch(BSC6900,BSC6910): DR_RRC_DRD_SWITCHis the general switch of the following six algorithms:

l Inter-RAT RRC Redirection Based on Distance

l Inter-Frequency RRC Redirection Based on Distance

l 4.2.4 RRC Redirection for Service Steering

l Macro & Micro Joint Inter-frequency Redirection

l 4.2.5 RRC DRD

l 4.2.6 RRC Redirection After DRD Failure

Before enabling the six algorithms, set DrSwitch(BSC6900,BSC6910): DR_RRC_DRD_SWITCHto ON.

NOTE:

For details about the Macro and Micro Joint Inter-Frequency Redirection feature, see Macro and Micro Co-carrier Uplink Interference Control.

4.2.2 Inter-RAT RRC Redirection Based on Weak Coverage

In weak-coverage areas, the UE access success rate is low and the call drop possibility is high. In areas where the GSM coverage is better than the UMTS coverage, using inter-RAT RRC redirection based on weak coverage can redirect UEs from the UMTS to the GSM network to improve the UE access success rate and reduce the call drop rate.

Inter-RAT RRC redirection based on weak coverage is recommended when there is only a small proportion of UEs that do not support inter-RAT redirections. The parameterPerfEnhanceSwitch(BSC6900,BSC6910): PERFENH_RRC_WEAK_REDIR_SWITCHspecifies whether to enable inter-RAT RRC redirection based on weak coverage.

The procedure for inter-RAT RRC redirection based on weak coverage is as follows:

1. Upon receiving an RRC CONNECTION REQUEST message from a UE, the RNC checks the setting of PerfEnhanceSwitch(BSC6900,BSC6910):PERFENH_RRC_WEAK_REDIR_SWITCH.

l If PERFENH_RRC_WEAK_REDIR_SWITCHunder the PerfEnhanceSwitch(BSC6900,BSC6910) parameter is not selected, the RNC does not perform inter-RAT RRCredirection based on weak coverage. The RRC connection setup request is then processed in the current cell.

l If PERFENH_RRC_WEAK_REDIR_SWITCHunder the PerfEnhanceSwitch(BSC6900,BSC6910) parameter is selected, the procedure goes to the next step.

2. The RNC obtains the Ec/N0 value of the current cell from the RACH Measurement Report IE in the RRC CONNECTION REQUEST message.

l If the Ec/N0 value is greater than or equal to the value of WeakCovRrcRedirEcNoThs, the RNC does not perform inter-RAT RRC redirection based on weak coverage.The RRC connection setup request is then processed in the current cell.

l If the Ec/N0 value is smaller than the value of WeakCovRrcRedirEcNoThs(BSC6900,BSC6910), the procedure goes to the next step.

3. The RNC sends the UE an RRC CONNECTION REJECT message containing information on the neighboring GSM cells of the current cell.

NOTE:

If the current cell does not have any neighboring GSM cell or the IE "RACH Measurement Report" does not contain the Ec/N0 value, inter-RAT RRC redirection based on weakcoverage is not performed.

4.2.3 RRC Redirection Based on Distance

Inter-RAT RRC Redirection Based on Distance

This section describes the WRFD-020401 Inter-RAT Redirection Based on Distance feature.A UE may receive signals from a distant cell and subsequently accesses the cell. The cells that are adjacent to this cell, however, are not configured as its neighboring cells.Therefore, if the UE moves out of this cell, call drops may occur. To solve this problem, RRC Inter-RAT redirection based on distance is introduced.

The RRC Inter-RAT redirection based on distance technique estimates the distance between the UE and the cell center by considering the propagation delay. Based on theestimation, the RNC determines whether to perform RRC Inter-RAT redirection. The propagation delayis the one-way propagation delay of the radio signal from the UE to theNodeB. The NodeB measures the propagation delay and then reports it to the RNC. The propagation delay is in direct proportion to the distance between the UE and the NodeB.

The switch of RRC Inter-RAT redirection based on distance can be set through the RedirSwitch(BSC6900,BSC6910)parameter. RRC Inter-RAT redirection based on distance isapplicable only to the UE-originating AMR services.

The procedure for RRC Inter-RAT redirection based on distance is as follows:

1. Upon receiving an RRC CONNECTION REQUEST message from the UE, the RNC checks whether the requested service is a UE-originating AMR service. If yes, the RNCperforms the next step. Otherwise, the RNC does not perform RRC Inter-RAT redirection based on distance, and handles the RRC connection setup request of the UE in thecurrent cell.

2. The RNC obtains the propagation delay from the NodeB and compares it withDelayThs(BSC6900,BSC6910).

l If the propagation delay is greater than DelayThs(BSC6900,BSC6910), the RNC performs the next step.

l If the propagation delay is equal to or less than DelayThs(BSC6900,BSC6910), the RNC does not perform RRC Inter-RAT redirection based on distance, and handlesthe RRC connection setup request of the UE in the current cell.

3. The RNC checks the load status of the current cell to determine whether to perform RRC Inter-RAT redirection based on distance.

l If the cell is in the normal state, the RNC generates a random value ranging from 0 to 1 and compares the value with the RedirFactorOfNorm(BSC6900,BSC6910)parameter. If the random value is equal to or smaller than the parameter, the RNC performs the next step. Otherwise, the RNC does not perform RRC Inter-RATredirection based on distance, and handles the RRC connection setup request of the UE in the current cell.

l If the cell is in the basic congestion state or is overloaded, the RNC generates a random value ranging from 0 to 1 and compares the value with the RedirFactorOfLDR(BSC6900,BSC6910)parameter. If the random value is equal to or smaller than the parameter, the RNC performs the next step. Otherwise, the RNC does not performRRC Inter-RAT redirection based on distance, and handles the RRC connection setup request of the UE in the current cell.

4. The RNC sends the UE an RRC CONNECTION REJECT message containing information about the neighboring GSM cells of the current cell.

NOTE:

If the current cell does not have any neighboring GSM cell, the UE selects a proper cell without the RNC participation.

Inter-Frequency RRC Redirection Based on Distance

For details of the WRFD-02040005 Inter-Frequency Redirection Based on Distance, see Inter-Frequency Redirection Based on Distance Feature Parameter Description .

4.2.4 RRC Redirection for Service Steering

Overview

This section describes the WRFD-020120 Service Steering and Load Sharing in RRC Connection Setup feature.RRC redirection for service steering is used to enable successful RRC connection setup by selecting an appropriate cell for the UE based on the requested service. This algorithmdoes not apply to combined services.

During the RRC connection setup, the RNC implements service steering between inter-frequency or inter-RAT cells according to the service type requested by the UE. In addition,


http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22


14/143

the RNC considers the load of the cell for access and the redirection factors t o control the percentages for load sharing.

Procedure of RRC Redirection for Service Steering

The procedure for RRC redirection for service steering is as follows:

1. The RNC obtains the information about the service requested by the UE and the capability of the UE.

l If DR_RRC_DRD_SWITCHof the parameter DrSwitch(BSC6900,BSC6910)is set to 1, the RNC tries to identify the service type requested by the UE. If the RNCsucceeds in identifying the service type requested by the UE and the switch of RRC direction for service steering RedirSwitch(BSC6900,BSC6910)is set toONLY_TO_INTER_FREQUENCYor ONLY_TO_INTER_RAT, the RNC performs the next step. Otherwise, the RNC handles the RRC connection setup request of theUE in the current cell.

l If the DR_ RRC_DRD_SWITCH of the parameter DrSwitch(BSC6900,BSC6910)is set to 0, the RNC handles the RRC connection setup request of the UE in the currentcell.

2. The RNC takes the corresponding actions based on the settings of RedirSwitch(BSC6900,BSC6910)and SCellLoadBsdRedirSwitch(BSC6900,BSC6910):

l If RedirSwitch(BSC6900,BSC6910)is set to ONLY_TO_INTER_FREQUENCYand SCellLoadBsdRedirSwitch(BSC6900,BSC6910)to ON

- The RNC handles the RRC connection setup request of the UE in the current cell if the uplink power load of the cell is lower than the value of UlLdrTrigThd(BSC6900,BSC6910)multiplied by OffloadRelativeThd(BSC6900,BSC6910)and the downlink power load is lower than the value of DlLdrTrigThd(BSC6900,BSC6910)multiplied by OffloadRelativeThd(BSC6900,BSC6910).

- The RNC performs the next step if the uplink power load of the cell is not lower than the value of UlLdrTrigThd(BSC6900,BSC6910)multiplied by OffloadRelativeThd(BSC6900,BSC6910)or the downlink power load is not lower than the value of DlLdrTrigThd(BSC6900,BSC6910)multiplied by OffloadRelativeThd(BSC6900,BSC6910).

l If RedirSwitch(BSC6900,BSC6910)is set to ONLY_TO_INTER_FREQUENCYand SCellLoadBsdRedirSwitch(BSC6900,BSC6910)to OFF, the RNC performs thenext step.

NOTE:

l The frequency information carried in the message can be set by running the SET UREDIRECTIONcommand.

l SCellLoadBsdRedirSwitch(BSC6900,BSC6910)is effective when RedirSwitch(BSC6900,BSC6910)is set to ONLY_TO_INTER_FREQUENCY.

l The calculation method for the uplink/downlink power load of a cell is the same as that for the power load in the load reshuffling algorithm.

l If RedirSwitch(BSC6900,BSC6910)is set to ONLY_TO_INTER_RAT, the RNC performs the next step.

3. Based on the cell load and the redirection factors, the RNC decides whether to perform RRC redirection for service steering.

l If the cell is in the normal state, the RNC generates a random number between 0 and 1 and compares it with the corresponding unconditional redirection factorRedirFactorOfNorm(BSC6900,BSC6910). If the random number is smaller than this factor, the RNC performs the next step. Otherwise, the RNC handles the RRCconnection setup request of the UE in the current cell.

l If the cell is in the basic congestion or overload state, the RNC generates a random number between 0 and 1 and compares it with the value of RedirFactorOfLDR(BSC6900,BSC6910). If the random number is smaller than this factor, the RNC performs the next step. Otherwise, the RNC handles the RRC connection setup requestof the UE in the current cell.

4. If RedirSwitch(BSC6900,BSC6910)is set to ONLY_TO_INTER_FREQUENCY, RNC selects target cells as following:

If RedirBandInd(BSC6900,BSC6910)is set to a value ranging from Band1to Band9, the RNC takes the following actions:

l If the measured CPICH Ec/N0 is contained in the RRC CONNECTION REQUEST message and the value of CPICH Ec/N0 is larger than or equal to the value forRedirEcN0Thd(BSC6900,BSC6910), the RNC proceeds with the next step. If the value of CPICH Ec/N0 is smaller than the value for RedirEcN0Thd(BSC6900,BSC6910), the RNC processes the RRC CONNECTION REQUEST message in the current cell.

l If the measured CPICH Ec/N0 is not contained in the RRC CONNECTION REQUEST message, the RNC proceeds with the next step.

If RedirBandInd(BSC6900,BSC6910)to DependOnNCell, the target cell must meets the following conditions:

l The target cell must be intra-band inter-frequency cell under the same RNC with the current cell

l The BlindHoFlag(BSC6900,BSC6910)for the target cell is set to TRUE

l If RRCRedirConsiderBarSwitch(BSC6900,BSC6910)is set to ON, the IdleCellBarred(BSC6900,BSC6910)of the target cell must no be BARRED.

l The target cell is not in the OLC state.

If none of the cells in the inter-frequency neighboring cell list meets the preceding requirements, the RNC processes the RRC CONNECTION REQUEST message in thecurrent cell. Otherwise, the RNC proceeds with the next step.

NOTE:

If parameter settings do not meet the requirements in this step, the RNC skips this step and proceeds with the next step.

5. The RNC performs RRC redirection.

l If RedirSwitch(BSC6900,BSC6910)is set to ONLY_TO_INTER_FREQUENCY, the RNC sends an RRC CONNECTION REJECT message to the UE, redirecting theUE to the target frequency carried in the message.

l If RedirSwitch(BSC6900,BSC6910)is set to ONLY_TO_INTER_RAT, the RNC sends an RRC CONNECTION REJECT message to the UE, redirecting the UE to aninter-RAT neighboring cell carried in the message.

Service Identification Rule

The RNC identifies requested services according to the relevant information elements (IEs) in the RRC Connection Request message received from the UE. The identification is

successful only when all the conditions described in Table 4-2are met.

NOTE:

TerminTrfcBsdRedirSwitch(BSC6900,BSC6910)specifies whether the RNC needs to identify UE terminating services.

l If TerminTrfcBsdRedirSwitch(BSC6900,BSC6910)is set to ON, the RNC identifies both UE originating services and UE terminating services.

l If TerminTrfcBsdRedirSwitch(BSC6900,BSC6910)is set to OFF, the RNC identifies only UE originating services.

Table 4-2 Service identification rule

Identified ServiceType

Reference IE

Establishment cause Domain indicator Call type UE capability indication Access stratum releaseindicator

AMR Originating Conversational Call

Terminating Conversational Call

CS domain Speech N/A REL-6

REL-7

AMR/VP Originating Conversational Call


N/A N/A N/A R99

REL-4

REL-5

VP Originating Conversational Call


CS domain Video N/A REL-6

REL-7


http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22


15/143

NOTE:

PS R99 and PS HSPA services for UEs of the REL-5 version cannot be identified by the RNC because these UEs do not carry the Domain indicator, Call type, or UE capabilityindication IEs in the RRC CONNECTION REQUEST message.

UEs of REL-5 and earlier versions do not carry the Domain indicator, Call type, or UE capability indication IEs. Therefore, the RNC cannot differentiate between AMR services andVP services. The RNC implements VP service redirection the same way it implements AMR service redirection.

4.2.5 RRC DRD

If the UE fails to access the current cell, the RNC performs RRC DRD. The purpose is to instruct the UE to set up an RRC connection in an inter-frequency neighboring cell withbetter signal quality.

For details about RRC DRD, see Directed Retry Decision Feature Parameter Description.

4.2.6 RRC Redirection After DRD Failure

This section describes the WRFD-02040003 Inter System Redirect feature.

The purpose of RRC redirection after DRD failure is to instruct the UE to set up RRC connections in an inter-frequency or an inter-RAT cell.When the RRC DRD fails, the RNC performs RRC redirection as follows:

The RNC selects another frequency for redirection based on the setting of the ReDirBandInd(BSC6900,BSC6910)parameter. If the ReDirBandInd(BSC6900,BSC6910)parameter is set toa specific band, the RNC selects the configured target frequency number and redirects the UE. The target frequency number is configured by the followingparameters: ReDirUARFCNUplinkInd(BSC6900,BSC6910), ReDirUARFCNUplink(BSC6900,BSC6910), ReDirUARFCNDownlink(BSC6900,BSC6910).

If the ReDirBandInd(BSC6900,BSC6910)parameter is set to DependOnNCell,the RNC selects the target frequency number from the target frequency numbers corresponding tothe intra-band inter-frequency neighboring cells of the current cell. In addition, the RNC excludes the target frequency corresponding to the cells that have carried out inter-frequency RRC DRD attempts. And if the RRCRedirConsiderBarSwitch(BSC6900,BSC6910)is set to on, the RNC excludes the target frequency of the cells of whichIdleCellBarred(BSC6900,BSC6910)is set to BARRED.

l If more than one target frequency number is available, the RNC selects a target frequency number randomly. Then, the RNC sends an RRC CONNECTION REJECTmessage to the UE, redirecting the UE to the selected target frequency carried in the message.

l If no target frequency number is available, the RNC continues to perform RRC redirection according to the setting of the ConnectFailRrcRedirSwitch(BSC6900,BSC6910)parameter.

n If ConnectFailRrcRedirSwitch(BSC6900,BSC6910)is set to Only_To_Inter_Frequency, the RRC connection setup fails.

n If ConnectFailRrcRedirSwitch(BSC6900,BSC6910)is set to Allowed_To_Inter_RAT and there is a neighboring GSM cell, the RNC sends the information about theneighboring GSM cell to the UE and redirects the UE to GSM system.

n If ConnectFailRrcRedirSwitch(BSC6900,BSC6910)is set to Allowed_To_Inter_RAT but there is no neighboring GSM cell, the UE automatically searches for availableGSM cells and then selects one of them for RRC connection setup attempts.

4.2.7 FACH Power Control During RRC Phase

During the RRC connection setup procedure, coverage in the live network may be imbalanced and UEs in weak coverage areas cannot correctly parse messages from thenetwork. This leads to RRC connection setup failures. To address this problem, the FACH power control of RRC phase function is introduced to increase the downlink transmitpower of the FACH so that UEs can correctly parse messages.

When a UE attempts to access a cell, the RNC checks the cause value and the Ec/N0 value contained in the RRC CONNETCTION REQUEST message. The RRC connectionsetup cause is specified by the RrcCause(BSC6900,BSC6910)parameter. The RNC then compares the Ec/N0 value with the value for FACHPower4RRCRepEcNoThd(BSC6900,BSC6910)corresponding to the RrcCause(BSC6900,BSC6910)parameter.

If the value of Ec/N0 is smaller than the value for FACHPower4RRCRepEcNoThd(BSC6900,BSC6910), the FACH power control of RRC phase function is triggered. This functionincreases the FACH transmit power as follows:

l If the T381(BSC6900,BSC6910)timer expires, the RNC increases the downlink transmit power of the FACH when retransmitting the RRC CONNECTION SETUP message tothe UE. The number of times this message is retransmitted is determined by the N381(BSC6900,BSC6910)timer.

l If the T300(BSC6900,BSC6910)timer expires, after the UE retransmits the RRC CONNETCTION REQUEST message, the RNC increases the downlink transmit power of theFACH when transmitting the RRC CONNECTION SETUP message. The number of times the RRC CONNETCTION REQUEST message is retransmitted is determined by theN300(BSC6900,BSC6910)timer.

The FACH downlink transmit power is specified by the MaxFachPower(BSC6900,BSC6910)parameter. When the FACH downlink transmit power exceeds the OLC thresholdDlOlcTrigThd(BSC6900,BSC6910), the RNC does not adjust the FACH downlink transmit power.

The FACH is a common channel. When the FACH power control of RRC phase function is enabled, the FACH downlink transmit power for UEs with no power increaserequirements is the difference between the MaxFachPower(BSC6900,BSC6910)andOffsetFACHPower(BSC6900,BSC6910)parameters.

4.3 Directed Retry Decision

Traffic steering and load sharing during RAB setup are performed based on DRD.

During the RAB connection processing, non-periodic DRD is used to select a suitable cell for a UE to access according to the HSPA+ technological implementation, servicepriority, and cell load. Non-periodic DRD is performed during RAB setup, RAB modification, or DCCC channel reconfiguration.

Non-periodic DRD involves inter-frequency DRD and inter-RAT DRD.

Using inter-frequency DRD, the RNC selects the qualified candidate cells based on HSPA+ technological implementation, cell service priority, and cell load. Then, the RNCsequences the candidate cells by the priority. The UE tries accessing the cells in descending order of priority until it is admitted or it fails to access any cell.

If the UE fails to access any cell in inter-frequency DRD, inter-RAT DRD will be triggered.

For details about non-periodic DRD, see Directed Retry Decision Feature Parameter Description.

4.4 Rate Negotiation at Admission Control

Rate negotiation at admission control (WRFD-010507 Rate Negotiation at Admission Control) includes MBR negotiation, GBR negotiation, initial rate negotiation, and target ratenegotiation.

For a streaming service, the RNC performs resource admission based on the negotiated MBR.

For a new PS BE service, the RNC performs resource admission based on the negotiated initial rate.

For AMR and AMR-WB speech services in the CS domain, seeAMR Feature Parameter Description.

4.4.1 PS MBR Negotiation

If the IE "Alternative RAB Parameter Values" is present in the RANAP RAB ASSIGNMENT REQUEST or the RELOCATION REQUEST message when a PS service is set up,

PS R99 Originating Interactive Call

Originating Background Call

Terminating Interactive Call

Terminating Background Call

N/A N/A N/A R99

REL-4

PS R99 Originating Interactive Call

Originating Background Call

Terminating Interactive Call


PS domain N/A Not HS-DSCH or HS-DSCH

+E-DCH

REL-6

REL-7

PS HSPA Originating Interactive Call

Originating Background CallTerminating Interactive Call


PS domain N/A HS-DSCH or HS-DSCH

+E-DCH

REL-6

REL-7




16/143

reconfigured, or handed over, the RNC and the CN will negotiate the rate based on the UE capability to obtain the MBR while ensuring a proper QoS.

l For the PS streaming service, when the PS_STREAM_IU_QOS_NEG_SWITCHsub-parameter of the PsSwitch(BSC6900,BSC6910)parameter is set to 1, the Iu QoSnegotiation function is enabled for MBR negotiation.

l For the PS BE service:

n When the PS_BE_IU_QOS_NEG_SWITCH and PS_BE_STRICT_IU_QOS_NEG_SWITCH sub-parameters of the PsSwitch(BSC6900,BSC6910)parameter are bothset to 1, the Iu QoS negotiation function is enabled, and the RNC determines the MBR of Iu QoS negotiation based on the information about UE capability, cell capabilityand rate requested by the CN.

n When PS_BE_IU_QOS_NEG_SWITCHis set to 1and PS_BE_STRICT_IU_QOS_NEG_SWITCHis set to 0, the Iu QoS negotiation function is enabled, and the RNCdetermines the MBR of Iu QoS negotiation based on the maximum rate supported by the UE rather than the cell capability or other settings.

4.4.2 PS GBR Negotiation

During the setup, reconfiguration, or handover of a PS real-time service, if the PS_STREAM_IU_QOS_NEG_SWITCHsub-parameter of the PsSwitch(BSC6900,BSC6910)parameter is set to 1, the RNC and the CN negotiate the GBR as follows:

l If the IE "Type of Alternative Guaranteed Bit Rate Information" in the RAB ASSIGNMENT REQUEST message is set to "unspecified", the GBR negotiation will not beperformed. In such a case, the GBR contained in the IE "RAB Parameters" of the RAB ASSIGNMENT REQUEST message is used. In addition, the subsequent RAB

ASSIGNMENT RESPONSE message does not contain the GBR.

l If the IE "Type of Alternative Guaranteed Bit Rate Information" in the RAB ASSIGNMENT REQUEST message is set to "value range", the only GBR contained in the IE"Alternative Guaranteed Bit Rates" is used. In addition, the subsequent RAB ASSIGNMENT RESPONSE message contains this GBR.

l If the IE "Type of Alternative Guaranteed Bit Rate Information" in the RAB ASSIGNMENT REQUEST message is set to "Discrete values", the largest GBR contained in the IE"Alternative Guaranteed Bit Rates" is used. In addition, the subsequent RAB ASSIGNMENT RESPONSE message contains this GBR.

If the PS_STREAM_IU_QOS_NEG_SWITCHsub-parameter of the PsSwitch(BSC6900,BSC6910)parameter is set to 0, the GBR negotiation will be not performed. In such acase, the GBR contained in the IE "RAB Parameters" of the RAB ASSIGNMENT REQUEST message is used.

For details about GBR negotiation, see 3GPP 25.413.

4.4.3 Initial Rate Negotiation

Overview

Initial rate is classified into initial admission rate and initial access rate.

l Initial admission rate: The RNC allocates bandwidths based on the initial admission rate and then performs admission according to the initial admission rate.

l Initial access rate: Initial access rate is the initial rate of the UE after service admission is successful. This rate is the maximum rate of the service before the service isreconfigured.

For PS BE services, the RNC performs initial rate negotiation when a new service is being set up or the UE is changing from the CELL_FACH state to the CELL_DCH state. Theinitial rate negotiation policy varies, depending on the services carried on channels.

Initial Rates for DCH Services

For DCH services, the initial admission rate and the initial access rate are the same.

Table 4-3describes the initial rate negotiation.

Table 4-3 Initial rate negotiation

NOTE:

If the DCCC function is enabled and the PS_RAB_Downsizing_Switchsub-parameter of the PsSwitch(BSC6900,BSC6910)parameter is set to 1, the RNC can decrease therate through the RAB rate decrease function when the admission based on the initial rate fails.

The PS BE service mentioned in this section can be pure PS BE service or a part of combined services.

Initial Rates for HSPA Services

For the HSUPA service,

l The initial admission rate is GBR.

l The initial access rate is defined as follows:

n If the DRA_HSUPA_DCCC_SWITCH sub-parameter of the DraSwitch(BSC6900,BSC6910)parameter is set to 1, the initial access rate is the initial rate of the HSUPABE service HsupaInitialRate(BSC6900,BSC6910).

n If the DRA_HSUPA_DCCC_SWITCHsub-parameter of the DraSwitch(BSC6900,BSC6910)parameter is set to 0, the initial access rate is the MBR for there is no rateupsizing reconfiguration when the DRA_HSUPA_DCCC_SWITCH sub-parameter of the DraSwitch(BSC6900,BSC6910)parameter is set to 0.

For the HSDPA service, the initial admission rate and the initial access are both GBR.

Initial Rate Negotiation for the PS BE Service in CS+PS Combined Services

The PS BE service in CS+PS combined services has low data transmission requirements. In most cases, the PS BE service does not need to transmit data when the UE isperforming CS services. If the PS BE service in CS+PS combined services has high data transmission requirements, the transmission rate of the PS BE service increases or the

DCCC Switch(DCCC_SWITCH)

PS BE Initial Rate Dynamic ConfigurationSwitch(PS_BE_INIT_RATE_DYNAMIC_CFG_SWITCH)

Actual Initial Rate

ON ON In the uplink, the initial rate is the MBR or 384 kbit/s, whichever is the smaller value.

In the downlink, the initial rate is dynamically set on the basis of Ec/N0. The specific method is asfollows:

When the RNC receives an RRC connection setup request, it starts the timer EcN0EffectTime(BSC6900,BSC6910).

Before the timer expires, the RNC dynamically sets the initial rate based on the Ec/N0. The value ofEc/N0 comes from the latest RACH measurement report or latest intra-frequency measurement report.

l If the cell Ec/N0 reported from the UE is above the Ec/N0 threshold EcN0Ths(BSC6900,BSC6910), the RNC sets the actual initial rate to the smaller one of the MBR and 384kbit/s.

Note that if the UE is in the soft handover state, the RNC sets the actual initial rate to the smallerone of the MBR and 384 kbit/s when any of the cells in the active set meets the threshold.

l If the cell Ec/N0 is lower than or equal to the Ec/N0 threshold EcN0Ths(BSC6900,BSC6910)or theRRC CONNECTION REQUEST message does not carry information about Ec/N0, the RNC setsthe actual initial rate to the smaller one of the MBR and the initial rate of the downlink BE serviceDlBeTraffInitBitrate(BSC6900,BSC6910).

ON OFF DlBeTraffInitBitrate(BSC6900,BSC6910).

In the uplink, the initial rate is the smaller one of the MBR and the initial rate of the uplink BE service

In the downlink, the initial rate is the smaller one of the MBR and the initial rate of the downlink BEservice DlBeTraffInitBitrate(BSC6900,BSC6910).

OFF - MBR




17/143

PS BE service is switched to an HSDPA channel. As a result, the signaling load increases, and the CS call drop rate may also increase. The initial rate negotiation function isrecommended when most PS BE services in CS+PS combined services havelow data transmission requirements.

The BeInitBitrateTypeforCsPs(BSC6900,BSC6910) parameter specifies thebearing policy for the PS BE service and the initial rate for the PS BE service when the UE is in theCELL_DCH state or transitions to this state. BeInitBitrateTypeforCsPs(BSC6900,BSC6910)applies only to the PS BE service in CS+PS combined services in the followingscenarios:

l Scenario 1: A UE is in the CELL_DCH state and is processing CS services or CS+PS combined services (any PS service). Then, the UE initiates PS BE services.

l Scenario 2: A UE is in the CELL_DCH state and is processing PS BE services. Then, the UE initiates CS services.

l Scenario 3: A UE is in the CELL_FACH state and is processing PS BE services. Then, the UE initiates CS services. (The UE must transition to the CELL_DCH state beforeestablishing CS services.)

l

Scenario 4: A UE is in the CELL_PCH state and is processing PS BE services. Then, the UE initiates CS services. (The UE must transition to the CELL_FACH or CELL_DCHstate before establishing CS services.)

NOTE:

This section describes the initial rate negotiation function only for the PS BE service in CS+PS combined services in the preceding scenarios. For details about the initial ratenegotiation function for the PS BE service in other scenarios, see Initial Rates for DCH Servicesand Initial Rates for HSPA Services.

The BeInitBitrateTypeforCsPs(BSC6900,BSC6910)parameter can be set to OFF, DCH 0k, DCH 8k, or DCH 8k/HSDPA.

l OFF: indicates that the initial rate negotiation function is disabled for the PS BE service in CS+PS combined services in the preceding scenarios.

l DCH 0k: indicates that the initial uplink and downlink rates for the DCH are both 0 kbit/s.

l DCH 8k: indicates that the initial uplink and downlink rates for the DCH are both 8 kbit/s.

l DCH 8k/HSDPA: indicates that the initial uplink rate for the DCH is 8 kbit/s and that downlink services are carried on HSDPA channels.

The implementation of the initial rate negotiation function for the PS BE service in CS+PS combined services varies depending on the protocol version that the UE complies with.

l For UEs complying with versions later than 3GPP Release 5, the following rules apply:

n If theBeInitBitrateTypeforCsPs(BSC6900,BSC6910) parameter is not set to OFF and the following switches are turned off:

ReservedSwitch0(BSC6900,BSC6910):RESERVED_SWITCH_0_BIT11 (RAN14.0)

MapSwitch(BSC6900,BSC6910):MAP_CSPS_PS_UL_USE_DCH_SWITCH (RAN15.0)

ReservedSwitch0(BSC6900,BSC6910): RESERVED_SWITCH_0_BIT15 (RAN14.0)

MapSwitch(BSC6900,BSC6910): MAP_CSPS_PS_DL_USE_DCH_SWITCH (RAN15.0)

ReservedSwitch0(BSC6900,BSC6910):RESERVED_SWITCH_0_BIT28(RAN14.0)

OptimizationSwitch(BSC6900,BSC6910): CS_SETUP_P2D_SWITCH (RAN15.0)

Then, the initial uplink and downlink rates for the PS BE service in CS+PS combined services are as listed in Table 4-4.

Table 4-4 Initial uplink and downlink rates for the PS BE service in CS+PS combined services

n If MapSwitch(BSC6900,BSC6910): MAP_CSPS_PS_UL_USE_DCH_SWITCH is turned on and BeInitBitrateTypeforCsPs(BSC6900,BSC6910) is not set toOFF, theinitial uplink rates for the PS BE service in CS+PS combined services are as listed in Table 4-5Table 4-5 Initial uplink rates for the PS BE service in CS+PS combined services

n If MapSwitch(BSC6900,BSC6910):MAP_CSPS_PS_DL_USE_DCH_SWITCHis turned on and BeInitBitrateTypeforCsPs(BSC6900,BSC6910) is not set toOFF, theinitial downlink rates for the PS BE service in CS+PS combined services are as listed in Table 4-6.

Table 4-6 Initial downlink rates for the PS BE service in CS+PS combined services

In scenario 4, if OptimizationSwitch(BSC6900,BSC6910):CS_SETUP_P2D_SWITCHis turned on, the UE transitions from the CELL_PCH state to the CELL_DCH state beforeestablishing CS services. In this situation:

l If PerfEnhanceSwitch1(BSC6900,BSC6910): PERFENH_CS_TRIG_PS_P2D_ZERO_SWITCH is set to0, the initial uplink and downlink rates for the PS BE service are 8kbit/s.

l If PerfEnhanceSwitch1(BSC6900,BSC6910): PERFENH_CS_TRIG_PS_P2D_ZERO_SWITCH is set to1, the initial uplink and downlink rates for the PS BE service are 0kbit/s.

Table 4-7lists the initial uplink and downlink rates for the PS BE service in CS+PS combined services when OptimizationSwitch(BSC6900,BSC6910):CS_SETUP_P2D_SWITCH is turned on.


Value of BeInitBitrateTypeforCsPs(BSC6900,BSC6910) Initial Uplink and Downlink Rates for the PS BE Service

DCH 0k DCH 0 kbit/s

DCH 8k DCH 8 kbit/s

DCH 8k/HSDPA DCH 8 kbit/s; HSDPA

Setting of MapSwitch(BSC6900,BSC6910):MAP_CSPS_PS_ULL_USE_DCH_SWITCH

Value of BeInitBitrateTypeforCsPs(BSC6900,BSC6910)

Initial Uplink Rate for the PS BE Service

Turned on DCH 0k DCH 0 kbit/s


Turned on DCH 8k/HSDPA DCH 8 kbit/s

Setting of MapSwitch(BSC6900,BSC6910):MAP_CSPS_PS_DL_USE_DCH_SWITCH

Value ofBeInitBitrateTypeforCsPs(BSC6900,BSC6910)

Initial Downlink Rate for the PS BE Service



Turned on DCH 8k/HSDPA DCH 8 kbit/s

Setting of PerfEnhanceSwitch1(BSC6900,BSC6910):PERFENH_CS_TRIG_PS_P2D_ZERO_SWITCH

Value of BeInitBitrateTypeforCsPs(BSC6900,BSC6910) Initial Uplink and Downlink Rates for the PSBE Service

1 DCH 0k DCH 0 kbit/s


1 DCH 8k/HSDPA DCH 0 kbit/s



http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22


18/143

l For UEs complying with versions earlier than 3GPP Release 5, the following rules apply:

n Versions earlier than 3GPP Release 5 support neither HSDPA nor HSUPA. If OptimizationSwitch(BSC6900,BSC6910): CS_SETUP_P2D_SWITCHis turned on, theinitial uplink and downlink rates for the PS BE service in CS+PS combined services are as listed in Table 4-8.

n If OptimizationSwitch(BSC6900,BSC6910): CS_SETUP_P2D_SWITCHis turned off, the initial uplink and downlink rates for the PS BE service in CS+PS combinedservices are as listed in Table 4-8.


l For UEs complying with 3GPP Release 5, MapSwitch(BSC6900,BSC6910): MAP_CSPS_PS_DL_USE_DCH_SWITCHdoes not take effect. This is because 3GPP Release5 supports HSDPA but does not support HSUPA.

In scenario 2, as long as BeInitBitrateTypeforCsPs(BSC6900,BSC6910) is not set to OFF,the PS BE service is always carried on HSDPA channels in the downlink and the initialuplink rate for the PS BE service is 8 kbit/s.

In scenario 2, as long as BeInitBitrateTypeforCsPs(BSC6900,BSC6910) is not set to OFF,the initial uplink and downlink rates for PS BE service is always carried on DCH arelisted in Table 4-9.

In scenario 3, when the uplink and downlink services can be carried on the DCH or HS-DSCH, the initial uplink and downlink rates for the PS BE service in CS+PS combinedservices are as listed in Table 4-9.


In scenario 1, BeInitBitrateTypeforCsPs(BSC6900,BSC6910)can be set to DCH 0k, DCH 8k, or DCH 8k/HSDPA. The initial uplink rate for the PS BE service is 8 kbit/s, anddownlink services are carried on HSDPA channels.

In scenario 4, when OptimizationSwitch(BSC6900,BSC6910): CS_SETUP_P2D_SWITCHis turned on, the initial uplink and downlink rates for the PS BE service in CS+PScombined services are as listed in Table 4-10.


4.4.4 Target Rate Negotiation

For a BE service in the PS domain, if the cell resource-based admission at the initial rate fails, the RNC selects a target rate to allocate bandwidth for the service based on cellresources in following situations:

l Service setup

l Soft handover

l DCCC rate upsizing

If the cell has sufficient code and CE resource, the RNC sets the candidate target rate to the one that matches the available cell resources. Then, the RNC sets the target rate tothe greater one of the candidate target rate and the GBR.