RAN Feature Documentation

WCDMA RANRAN15.0

Call Admission Control Feature ParameterDescriptionIssue 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 trademarks and trade names mentioned in this document are the property of their respective holders.

NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in thisdocument may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document areprovided "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 Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Contents

1 About This Document1.1 Scope1.2 Intended Audience1.3 Change History

2 Overview2.1 CAC Policy

2.1.1 System Resources2.1.2 Resource Requests2.1.3 Channels2.1.4 Service Priorities

2.2 CAC Procedure

3 NodeB Credit Resource-based CAC3.1 NodeB Credit Resources3.2 Admission Decisions

3.2.1 Admission Decisions on RRC Connection Setup Requests3.2.2 Admission Decisions on Other Resource Requests

4 Iub Transmission Resource-based CAC5 Cell Code Resource-based CAC

5.1 Admission Decisions on RRC Connection Setup Requests5.2 Admission Decisions on Other Resource Requests

6 CAC Based on the Number of HSPA Users6.1 CAC for HSDPA Users6.2 CAC for HSUPA Users

7 Cell Power Resource-based CAC7.1 Overview7.2 Admission Control Algorithm 1

7.2.1 Uplink Admission Control Algorithm 17.2.2 Downlink Admission Control Algorithm 1

7.3 Admission Control Algorithm 27.3.1 ENU7.3.2 Uplink Admission Control Algorithm 27.3.3 Downlink Admission Control Algorithm 2

7.4 Admission Control Algorithm 37.5 Admission Control Algorithm 4

8 Common Channel Admission8.1 CAC on Traditional Common Channels8.2 CAC on the E-FACH or E-RACH

9 Follow-up Processing in the Case of Admission Failures10 Engineering Guidelines

10.1 Deployment of WRFD-020101 Admission Control10.1.1 Requirements10.1.2 Activation (Using MML Commands)10.1.3 MML Command Examples10.1.4 Activation (Using the CME)10.1.5 Activation Observation10.1.6 Deactivation (Using MML Commands)10.1.7 MML Command Examples10.1.8 Deactivation (Using the CME)

10.2 Deployment of WRFD-01061003 HSDPA Admission Control10.2.1 Requirements10.2.2 Activation (Using MML Commands)10.2.3 MML Command Examples10.2.4 Activation (Using the CME)10.2.5 Activation Observation10.2.6 Deactivation

10.3 Deployment of WRFD-01061202 HSUPA Admission Control10.3.1 Requirements10.3.2 Activation (Using MML Commands)10.3.3 MML Command Examples10.3.4 Activation (Using the CME)10.3.5 Activation Observation10.3.6 Deactivation

11 Parameters12 Counters13 Glossary14 Reference Documents

1 About This Document

1.1 ScopeThis document describes the Call Admission Control (CAC) feature, including the basic principles, engineering guidelines, and parameters.

This document covers the features WRFD-020101 Admission Control, WRFD-01061003 HSDPA Admission Control, and WRFD-01061202 HSUPA Admission Control.

1.2 Intended AudienceThis document is intended for personnel who:

Are familiar with WCDMA basics

Work with Huawei WCDMA products

1.3 Change HistoryThis section provides information about the changes in different document versions.

There are two types of changes, which are defined as follows:

Feature change: refers to a change in the CAC feature of a specific product version.

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

Document Versions

01 (2013-04-28)

Draft A (2013-01-30).

01 (2013-04-28)

This is the first release of RAN15.0. There is no change.

Draft A (2013-01-30)

This is a draft of RAN15.0.

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

Change Type Change Description Parameter Change

Feature change Added the impact on CAC from the DB-HSDPA, 4C-HSDPA, and Flexible DC/DB-HSDPA features introduced in RAN15.0. Fordetails, see 7 Cell Power Resource-based CAC.

None

Editorial change Optimized document organization and descriptions to improve readability.Added descriptions of the CAC policies. For details, see section 2.1 CAC Policy.Added descriptions of admission control on common channels. For details, see8 Common Channel Admission.Added descriptions of following-up processing in case of service admission failures. For details, see 9 Follow-upProcessing in the Case of Admission Failures.

None

2 Overview

Call Admission Control (CAC) is used to determine whether system resources in a cell are sufficient to accept a service request. The service request will be rejected if the systemresources are insufficient. System resources include NodeB credit resources, Iub transmission resources, cell code resources, cell power resources, and the number of HSPA users.

The RNC triggers CAC upon receipt of a service request such as service setup, service change, handover, and cell update. When CAC is being implemented, the RNC also considersthe cell load reported by the load measurement module.

CAC aims to increase the use of system resources and guarantee the quality of service (QoS) for existing users.

NOTE:For details about cell load measurements, see Load Control Feature Parameter Description.

2.1 CAC PolicyThe RNC implements differentiated CAC based on system resources, resource requests, channels, and service priorities.

2.1.1 System ResourcesThe system resources involved in CAC are as follows:

NodeB credit resources

Iub transmission resources

Cell code resources

Number of users, including HSDPA/HSUPA and E-FACH/E-RACH users

Cell power resources

The RNC implements differentiated CAC based on system resources requested by users.

2.1.2 Resource RequestsThe resource requests involved in CAC are as follows:

Cell updates

Service setup: new radio resource control (RRC) setup and radio access bearer (RAB) setup

Service change: RAB reconfiguration and service rate increase or decrease

Handovers: soft handovers, hard handovers, inter-RAT incoming handovers, and circuit switched fallback (CSFB)

State transitions: P2D, F2D, and D2D transitions

NOTE:For details about state transitions of UEs, see State Transition Feature Parameter Description. P2D is short for a state transition from CELL_PCH/URA_PCH to CELL_DCH, F2D forCELL_FACH to CELL_DCH, and D2D for CELL_DCH to CELL_DCH.

The CAC policies based on resource requests are as follows:

For service rate decrease requests, admission succeeds since some system resources are released.

For service setup requests, admission is implemented in the RRC connection setup phase and RAB setup phase in sequence. In the RRC connection setup phase,admission is implemented based on the system resources requested by signaling radio bearers (SRBs). In the RAB setup phase, admission is implemented based on thesystem resources requested by SRBs and traffic radio bearers (TRBs) in total.

For other service requests, admission is implemented based on the system resources requested by SRBs and TRBs in total.

NOTE:This document separately describes admission decisions on RRC connection setup requests and other resource requests. For details, see 3 NodeB Credit Resource-based CAC, 5Cell Code Resource-based CAC, and 7 Cell Power Resource-based CAC. Admission decision in the RAB setup phase is included in other resource requests.

2.1.3 ChannelsThe amount of consumed resources is channel-specific, and therefore the RNC implements differentiated CAC based on channels.

Dedicated Channels

Generally, users consume more resources on dedicated channels than they do on common channels. Therefore, CAC focuses on service requests on DCH channels and HSPAchannels, which will be described in the corresponding chapters.

Common Channels

Users consume relatively smaller amount of resources on common channels. Therefore, the RNC reserves some resources for certain common channels and does not implement CACfor specific requests.

For details about the CAC policy on common channels, see 8 Common Channel Admission.

2.1.4 Service PrioritiesThe RNC implements differentiated CAC for resource requests other than RRC during NodeB credit resource-based, cell code resource-based, and power resource-based admissionsas follows:

The RNC preferentially admits high-priority service requests such as emergency calls, detachments, or registrations. For details, see sections 3.2.1 Admission Decisionson RRC Connection Setup Requests and 7.2 Admission Control Algorithm 1.

The RNC provides differentiated admission thresholds for handovers, adaptive multirate (AMR) services, non-AMR services, and other services because these service typeshave different QoS requirements. A special admission threshold is used for handover-related resource requests and differentiated admission thresholds are used for non-handover-related resource requests. For details, see the following sections:

3.2.2 Admission Decisions on Other Resource Requests

5.2 Admission Decisions on Other Resource Requests

7.2.1 Uplink Admission Control Algorithm 1

7.2.2 Downlink Admission Control Algorithm 1

7.3.2 Uplink Admission Control Algorithm 2

This document does not describe admission control for Multimedia Broadcast Multicast Service (MBMS), which is detailed in MBMS Feature Parameter Description.

2.2 CAC ProcedureFigure 2-1shows the basic CAC procedure. If admission succeeds, the RNC admits the service request. If admission fails, the RNC implements relevant functions to increase theaccess success rate, which is described in 9 Follow-up Processing in the Case of Admission Failures.

Figure 2-1 Basic CAC procedure

The following table describes the resource-based CAC methods in Figure 2-1 .

Table 2-1 Resource-based CAC methods

SN Admission Control Method Applicable Service Uplink/Downlink Mandatory/Optional DecisionCriteria

Detailed In

1 NodeB credit resource-basedCAC

R99, HSDPA, and HSUPAservices

Uplink and downlink OptionalIt is controlled by switches.

3 NodeB Credit Resource-basedCAC

2 Iub transmission resource-based CAC


Uplink and downlink Mandatory 4 Iub Transmission Resource-basedCAC

3 Cell code resource-basedCAC

R99 services Downlink Mandatory 5 Cell Code Resource-based CAC

4 CAC based on the number ofHSDPA users

HSDPA services Downlink Mandatory 6 CAC Based on the Number ofHSPA Users

CAC based on the number ofHSUPA users

HSUPA services Uplink Mandatory

5 Cell power resource-basedCAC


Uplink and downlink OptionalIt is controlled by switches.

7 Cell Power Resource-based CAC

3 NodeB Credit Resource-based CAC

NodeB credit resource-based CAC applies to R99, HSDPA, and HSUPA services in uplink and downlink.

This admission mode takes effect for a specific cell only when both NODEB_CREDIT_CAC_SWITCH of CacSwitch and CRD_ADCTRL of NBMCacAlgoSwitch are selected.

3.1 NodeB Credit ResourcesThe NodeB credit resource is an RNC-related concept. It is referred to as the channel element (CE) on the NodeB side, indicating the channel demodulation capability of a NodeB.

CE Consumption

CEs are classified into uplink and downlink CEs:

An uplink 12.2 kbit/s voice service (SF = 64) plus 3.4 kbit/s signaling traffic consume one uplink CE.

A downlink 12.2 kbit/s voice service (SF = 128) plus 3.4 kbit/s signaling traffic consume one downlink CE.

One CE is required even when the DCH or HSPA channel carries the 3.4 kbit/s signaling traffic. For details about CEs and number of CEs consumed by different types of service,seeCE Resource Management Feature Parameter Description.

CE Capability Reporting

CEs are counted at NodeB level, local cell group (LCG) level (if any), and local cell (LC) level. The NodeB sends the RNC an AUDIT RESPONSE message to report different levels ofCE capabilities. The NodeB considers physical and licensed CEs when reporting the CE capability to the RNC. See Table 3-1.

NOTE:

A group of local cells are configured to form an LCG. If a NodeB is not configured with an LCG, the NodeB will not report the LCG-level CEs to the RNC.

Table 3-1 Meaning of CEs at different levels

Level Meaning

NodeB-level CEs The NodeB-level CEs are the licensed CEs supported by the NodeB.

LCG-level CEs In uplink, the LCG-level CEs are the LCG-level physical CEs. In downlink, the LCG-level CEs are the sum of downlink CEs on all boards ofthe LCG.

LC-level CEs In uplink, the LC-level CEs are the physical CEs of the uplink resource group to which the cell belongs. In downlink, the LC-level CEs arethe physical CEs of the baseband processing board to which the cell belongs.

Relationship Between NodeB Credit Resources and CEs

The relationship between NodeB credit resources and CEs is as follows:

In uplink, the quantity of NodeB credit resources is twice the CE quantity.

In downlink, the quantity of NodeB credit resources equals CE quantity.

Remaining NodeB Credit Resources

The RNC calculates the remaining NodeB credit resources at NodeB, LCG, and LC levels based on three factors:

Reported NodeB-level, LCG-level, and LC-level CE capabilities

Relationship between NodeB credit resources and CEs

CE consumption rule

3.2 Admission DecisionsThe RNC implements NodeB credit resource-based admission control based on the remaining NodeB credit resources at NodeB, LCG (if any), and LC levels. NodeB credit resource-based admission succeeds only when the remaining NodeB credit resources at the three levels are sufficient for the service to be admitted.

Uplink and downlink CEs are independent from each other. Therefore, NodeB credit resource-based admission control is implemented separately in uplink and downlink with the sameadmission criteria.

3.2.1 Admission Decisions on RRC Connection Setup RequestsFigure 3-1 shows the NodeB credit resource-based admission control procedure for RRC connection setup requests.

Figure 3-1 NodeB credit resource-based admission control procedure for RRC connection setup requests

For an RRC connection setup request, NodeB credit resource-based admission control is implemented as follows:

When RRCCeCodeCacChoice is set to LOOSE_CAC, NodeB credit resource-based admission succeeds if the remaining NodeB credit resources at NodeB, LCG (if any),and LC levels are sufficient for setting up an RRC connection.

When RRCCeCodeCacChoice is set to STRICT_CAC, the RNC implements NodeB credit resource-based admission control based on the cause value carried in the RRCconnection setup request:

If the cause value is "Emergency Call" or "Detach", NodeB credit resource-based admission succeeds if the remaining NodeB credit resources at NodeB, LCG(if any), and LC levels are sufficient for setting up the RRC connection.

For other causes, NodeB credit resource-based admission succeeds if the remaining NodeB credit resources at NodeB, LCG (if any), and LC levels are greaterthan the reserved credit resource plus the resource for setting up the RRC connection. The reserved credit resource and the spreading factor (SF) have amapping relationship, which means the reserved credit resource threshold is determined once the SF is specified. The SF is specified by DlRRCCeCodeResvSf(for the downlink) or UlRRCCeResvSf (for the uplink). For details about the mapping relationship, see CE Resource Management Feature Parameter Description.

3.2.2 Admission Decisions on Other Resource RequestsThis section describes the NodeB credit resource-based admission decisions on other resource requests from different services.

Handovers

Handover requests have a high service priority on a mobile communication network. Therefore, NodeB credit resource-based admission succeeds if the remaining NodeB creditresources at NodeB, LCG (if any), and LC levels are greater than or equal to the resource requested by the handover. The RNC does not reserve extra resources for handovers.

AMR Services

Figure 3-2 shows the NodeB credit resource-based admission control procedure for AMR service requests.

Figure 3-2 NodeB credit resource-based admission control procedure for AMR service requests

For an AMR service request, NodeB credit resource-based admission control is implemented as follows:

If CSRABCacOptSwitch is set to ON, NodeB credit resource-based admission succeeds if the remaining NodeB credit resources at NodeB, LCG (if any), and LC levels aregreater than or equal to the resource requested by the AMR service. The RNC does not reserve extra resources for the AMR service.

If CSRABCacOptSwitch is set to OFF, NodeB credit resource-based admission succeeds if the remaining NodeB credit resources at NodeB, LCG (if any), and LC levelsare greater than or equal to the reserved credit resource plus the resource requested by the AMR service.

The reserved credit resource and the SF have a mapping relationship. The SF is specified by DlHoCeCodeResvSf (for the downlink) or UlHoCeResvSf (for the uplink). For details aboutthe mapping relationship, see CE Resource Management Feature Parameter Description.

PS Services or CS Services (Non-AMR Services)

For PS or CS service (non-AMR service) requests, NodeB credit resource-based admission succeeds if the remaining NodeB credit resources at NodeB, LCG (if any), and LC levelsare greater than or equal to the reserved credit resource plus the resource requested by the service.

The reserved credit resource and the SF have a mapping relationship. The SF is specified by DlHoCeCodeResvSf (for the downlink) or UlHoCeResvSf (for the uplink).

4 Iub Transmission Resource-based CAC

Iub transmission resource-based CAC applies to R99, HSDPA, and HSUPA services in both uplink and downlink.

For details about Iub transmission resource-based CAC, see Transmission Resource Management Feature Parameter Description.

5 Cell Code Resource-based CAC

Cell code resource-based CAC applies to R99 services only in downlink.

NOTE:Cell code resource-based CAC does not apply to HSDPA services because code resources have been reserved for HSDPA services. In addition, these resources can be shared byHSDPA services. For details about code resource allocation for HSDPA services, see HSDPA Feature Parameter Description.

5.1 Admission Decisions on RRC Connection Setup RequestsFigure 5-1 shows the cell code resource-based admission control procedure for RRC connection setup requests.

Figure 5-1 Cell code resource-based admission control procedure for RRC connection setup requests

For an RRC connection setup request, cell code resource-based admission control is implemented as follows:

When RRCCeCodeCacChoice is set to LOOSE_CAC, cell code resource-based admission succeeds if the remaining cell code resources (the remaining minimum SF forthe cell) are sufficient for setting up an RRC connection.

When RRCCeCodeCacChoice is set to STRICT_CAC, the RNC implements code resource-based admission control based on the cause value carried in the RRCconnection setup request:

If the cause value is "Emergency Call" or "Detach", cell code resource-based admission succeeds if the remaining code resources are sufficient for setting upan RRC connection.

For other cause values, cell code resource-based admission succeeds if the remaining code resources are greater than or equal to the resource reservedby DlRRCCeCodeResvSf plus the resource required by the RRC.

5.2 Admission Decisions on Other Resource RequestsThis section describes the admission decisions on other resource requests from different services.

Handovers

Handover requests have a high service priority on a mobile communication network. Therefore, cell code resource-based admission succeeds if the remaining code resources aresufficient for the handover request to be admitted.

AMR Services

Figure 5-2 shows the cell code resource-based admission control procedure for AMR service requests.

Figure 5-2 Cell code resource-based admission control procedure for AMR service requests

For an AMR service request, cell code resource-based admission control is implemented as follows:

If CSRABCacOptSwitch is set to ON, cell code resource-based admission succeeds if the remaining code resources are sufficient for the AMR service to be admitted.

If CSRABCacOptSwitch is set to OFF, cell code resource-based admission succeeds if the remaining code resources are greater than or equal to the resource reservedby DlHoCeCodeResvSf plus the resource requested by the AMR service.

PS Services or CS Services (Non-AMR Services)

For PS or CS service (non-AMR service) requests, cell code resource-based admission succeeds if the remaining code resources are greater than or equal to the resource reserved byDlHoCeCodeResvSf plus the resource requested by the service.

6 CAC Based on the Number of HSPA Users

This section describes CAC based on the number of HSDPA and HSUPA users in a cell.

6.1 CAC for HSDPA UsersFor HSDPA service requests such as service setup and handovers, admission based on the number of HSPA users succeeds when all the following conditions are met:

The number of HSDPA users in the cell is less than or equal to the threshold specified by MaxHsdpaUserNum once the HSDPA service is admitted.

The number of HSDPA users in the cell is less than or equal to the licensed limit once the HSDPA service is admitted.

The number of HSDPA users in the NodeB is less than or equal to the threshold specified by NodeBHsdpaMaxUserNum once the HSDPA service is admitted.

A multi-carrier HSDPA user, such as DC-HSDPA, DB-HSDPA, and 4C-HSDPA user, is counted for an HSDPA user on the primary cell. It is not counted for an HSDPA user on thesecondary cells. Therefore, CAC based on the number of HSPA users is implemented only on the primary cell.

NOTE:Huawei's 4C-HSDPA feature includes three-carrier and four-carrier applications.

6.2 CAC for HSUPA UsersHSUPA service requests include service setup and handovers. Admission based on the number of HSPA users succeeds when all the following conditions are met:

The number of HSUPA users in the cell is less than or equal to the threshold specified by MaxHsupaUserNum once the HSUPA service is admitted.

The number of HSUPA users in the cell is less than or equal to the licensed limit once the HSUPA service is admitted.

The number of HSUPA users in the NodeB is less than or equal to the threshold specified by NodeBHsupaMaxUserNum once the HSUPA service is admitted.

A DC-HSUPA user is counted for an HSUPA user on the primary cell. Therefore, CAC based on the number of HSPA users is implemented only on the primary cell.

7 Cell Power Resource-based CAC

Cell power resource-based CAC applies to R99, HSDPA, and HSUPA services.

R99 and HSPA services (uplink and downlink data carried on HSPA channels): Cell power resource-based CAC is enabled when the algorithm switch in section 7.1Overview is turned on.

HSDPA services (uplink data carried on DCH channels and downlink data carried on HSDPA channels): Cell power resource-based CAC is enabled whenHSDPA_UU_ADCTRL of NBMCacAlgoSwitch is selected and the algorithm switch in section 7.1 Overview is turned on.

HSUPA services (uplink data carried on HSUPA channels and downlink data carried on DCH channels): Cell power resource-based CAC is enabled whenHSUPA_UU_ADCTRL of NBMCacAlgoSwitch is selected and the algorithm switch in section 7.1 Overview is turned on.

Section 7.2 Admission Control Algorithm 1 through 7.5 Admission Control Algorithm 4 describe four algorithms used for cell power resource-based CAC on dedicated channels. 8

Common Channel Admission describes cell power resource-based CAC on common channels.

7.1 OverviewCell power resource-based CAC is performed by using one of four algorithms, which are referred to as algorithm 1, algorithm 2, algorithm 3, and algorithm 4 in this document.Algorithms 1, 2, and 3 apply to admission control in uplink and downlink. Algorithm 4 applies only to admission control in uplink. Table 7-1 describes these algorithms.NBMUlCacAlgoSelSwitch and NBMDlCacAlgoSelSwitch specify the algorithms used in uplink and downlink, respectively. For resource requests from intra-frequency handovers, theRNC performs cell power resource-based CAC only in downlink; for resource requests from other services, the RNC does that first in uplink and then in downlink.

Table 7-1 Algorithms used for cell power resource-based CAC

Algorithm GUI Value inNBMUlCacAlgoSelSwitchandNBMDlCacAlgoSelSwitch

Uplink/Downlink Description

7.2 Admission ControlAlgorithm 1

ALGORITHM_FIRST Uplink and downlink In algorithm 1, admission control is based on the cell power load and the expected power loadincrease caused by a new service.If the RNC determines that the expected power load exceeds the preset threshold once the newservice is admitted, the RNC rejects the service request. Otherwise, the RNC admits theservice.


ALGORITHM_SECOND Uplink and downlink In algorithm 2, admission control is based on the equivalent number of users (ENU) and theexpected power load increase caused by a new service.If the RNC determines that the expected ENU will exceed the preset threshold once the newservice is admitted, the RNC rejects the service request. Otherwise, the RNC admits theservice.


ALGORITHM_THIRD Uplink and downlink In algorithm 3, the RNC performs admission control without considering the power load increasecaused by a new service.Algorithm 3 is similar to algorithm 1. The only difference is that algorithm 3 assumes that theexpected power load increase caused by the new service is 0.The RNC determines whether the current cell power load exceeds the preset threshold. If yes,the RNC rejects the service request. Otherwise, the RNC admits the service.


ALGORITHM_FOURTH Uplink In algorithm 4, admission control is based on the actual uplink service load and the expectedservice load increase caused by a new service.Depending on the actual uplink service load in the cell, the RNC determines whether the actualuplink service load will exceed the preset threshold once the new service is admitted. If yes, theRNC rejects the service request. Otherwise, the RNC admits the service.

7.2 Admission Control Algorithm 1Algorithm 1 performs admission control based on the cell power load and the expected power load increase caused by a new service. The measurement quantities relevant to the cellpower load are processed and reported by the load measurement module on the RNC. For details about cell load measurements, see Load Control Feature Parameter Description.

Algorithm 1 applies to admission control in uplink and downlink.

7.2.1 Uplink Admission Control Algorithm 1In uplink, algorithm 1 makes admission decisions based on resource requests and cell types (R99 cells, SC-HSUPA cells, or DC-HSUPA cells). The load measurement module of theRNC calculates the uplink power load factor based on received total wideband power (RTWP).

Calculation of Uplink Power Load for a Cell

The following describes how to calculate the uplink power load factor for an R99 cell, SC-HSUPA cell, and DC-HSUPA cell.

For an R99 CellFor an R99 cell, the uplink power load factor is represented by UL,R99-Total and calculated using the following formula:UL,R99-Total = 1 PN/RTWP + UL,CCHWhere,

PN is the uplink background noise and the unit is mw. PN is set by BackgroundNoise and the unit of the paramter is dBm. The relation between dBm and mw is1dBm=10*log(1mw). If the auto-adaptive background noise update algorithm is enabled, PN is updated in real time. For details about the auto-adaptive background noiseupdate algorithm, see Load Control Feature Parameter Description.

RTWP is the received total wideband power in uplink. It is measured by the NodeB and periodically reported to the RNC.

UL,CCH is the reserved load factor on the uplink common channels, which is set by UlCCHLoadFactor.For an SC-HSUPA CellIn an SC-HSUPA cell, algorithm 1 uses the following three types of uplink power load factor:

RTWP-based uplink power load factor

For an SC-HSUPA cell, it is represented by UL,HSUPA-Total and calculated using the following formula:UL,HSUPA-Total = 1 PN/RTWP + UL,CCH + HS-DPCCHWhere,

HS-DPCCH is the reserved load factor on the uplink HS-DPCCH. It is set by UlHsDpcchRsvdFactor.The other variables are defined the same way as for UL,R99-Total in an R99 cell.

Uncontrollable uplink load factor

The uncontrollable uplink load factor is the load factor for the receive power of a cell excluding the receive power used for scheduling services. It is represented by UL,NonCtrland calculated using the following formula:

UL,NonCtrl = UL,HSUPA-Total UL,CtrlWhere,

UL,Ctrl is the controllable uplink load factor and equals the received scheduled E-DCH power share (RSEPS). RSEPS is the ratio of the receive power of allscheduled users to RTWP in the current cell. RSEPS is measured by the NodeB and periodically reported to the RNC.

NOTE:The algorithm for calculating UL,NonCtrl depends on the periodic RSEPS measurement according to the above formula. If NBMUlCacAlgoSelSwitch is set to ALGORITHM_FIRST orALGORITHM_THIRD and HSUPA_EDCH_RSEPS_MEAS of NBMCacAlgoSwitch is set to 0, the RNC performs admission control for the cell using algorithm 2. For details aboutalgorithm 2, see 7.3 Admission Control Algorithm 2.

Total uplink load factor for preferential admission of R99 services

It is represented by UL,R99Prefer-Total.When the guaranteed bit rate (GBR) for HSUPA services is too high, the RTWP-based uplink power load may also be too high, and therefore R99 service admission isdifficult. In this case, UL,R99Prefer-Total ensures that R99 services are preferentially admitted. UL,R99Prefer-Total is calculated using the following formula:UL,R99Prefer-Total = UL,NonCtrl + ThdHSUPAMaxGBPWhere,

ThdHSUPAMaxGBP is the maximum guaranteed load threshold for HSUPA services when the RNC makes an admission decision on an R99 service. It is set byHsupaMaxGBPThd.

For a DC-HSUPA CellIn a DC-HSUPA cell group, the uplink power load factor is calculated on the primary and secondary cells. The calculation method is the same as that for an SC-HSUPA cell.

The RTWP reported by the NodeB contain the power load consumed by existing DC-HSUPA services.

Uplink Admission Decisions Based on Algorithm 1

Figure 7-1 shows the procedure for an uplink admission decision based on algorithm 1.

Figure 7-1 Procedure for an uplink admission decision based on algorithm 1

This procedure is implemented as follows:

1. The RNC calculates the uplink power load for the cell based on the result from the load measurement module.

2. The RNC calculates the uplink power load increase (UL) based on the initial admission rate of the new service.

NOTE:

For details about the initial admission rate, see Load Control Feature Parameter Description.In admission control on an RRC connection setup request, the RNC calculates the load increase based on the signaling radio bearer (SRB) rate carried in theRRC connection setup request. The SRB rate of an RRC connection setup request is set by running the SET URRCESTCAUSE command.

3. The RNC makes an admission decision.

In algorithm 1, uplink admission criteria vary according to the resource request type, cell type, and bearer type. For details about the uplink admission criteria, see Table 7-2 . If the admission criteria are met, uplink admission based on algorithm 1 succeeds. Otherwise, the RNC performs the next step.

Table 7-2 Uplink admission criteria in algorithm 1

Resource Request Type Cell Type Bearer Type Admission Criteria Described In

RRC connection setup requests R99 cellHSUPA cell

N/A Admission Criteria for RRC Connection Setup Requests

Other resource requests (such as RABsetup, RAB reconfiguration, handover,and cell update)

R99 cell DCH RAB Admission Criteria for Other Resource Requests in an R99Cell

SC-HSUPA cell DCH RAB Admission Criteria for Other Resource Requests in an SC-HSUPA Cell (for the DCH RAB)

SC-HSUPA RAB Admission Criteria for Other Resource Requests in an SC-HSUPA Cell (for the SC-HSUPA RAB)

DC-HSUPA cell DCH RAB, SC-HSUPA RAB, andDC-HSUPA RAB

Admission Criteria for Other Resource Requests in a DC-HSUPA Cell

4. If the RTWP anti-interference function switch is turned on (RTWP_RESIST_DISTURB of NBMCacAlgoSwitch is selected), the RNC checks whether the total uplink loadof ENU on the cell is less than CellUlEquNumCapacity.

If yes, uplink admission based on algorithm 1 succeeds.

Otherwise, uplink admission based on algorithm 1 fails.

NOTE:For details about the total uplink load of ENU on the cell, see 7.3 Admission Control Algorithm 2.

Admission Criteria for RRC Connection Setup Requests

In algorithm 1, the uplink admission criteria for RRC connection setup requests are as follows:

For R99 cells, uplink admission based on algorithm 1 succeeds if the following formula is satisfied:

UL,R99-Total + UL ThdUL,RRCFor HSUPA cells, uplink admission based on algorithm 1 succeeds if the following formula is satisfied:

UL,NonCtrl + UL ThdUL,RRCThdUL,RRC is the uplink admission threshold for RRC connection setup requests. Algorithms 1, 2, 3, and 4 use the same threshold in uplink. The RNC performs either loose or strictadmission control on RRC connection setup requests according to the value of RRCCacChoice:

If RRCCacChoice is set to LOOSE_CAC, the RNC uses the loose admission thresholds listed in Table 7-3.

If RRCCacChoice is set to STRICT_CAC, the RNC uses the strict admission thresholds listed in Table 7-4 .

Table 7-3 Loose uplink admission thresholds for RRC connection setup requests

Cause of RRC Connection Setup Request Uplink Admission Threshold (ThdUL,RRC)

Emergency callDetachmentRegistration

The RRC connection is set up without admission control.

Other services When UL_UU_OLC of NBMLdcAlgoSwitch is set to 1:If the cell is overloaded, the RNC rejects the RRC connection setup request.If the cell is not overloaded, theuplink OLC triggering threshold (UlOlcTrigThd) is used as ThdUL,RRC.When UL_UU_OLC of NBMLdcAlgoSwitch is set to 0, the uplink OLC triggering threshold UlOlcTrigThd isused as ThdUL,RRC.

NOTE:For details about the overload state of a cell and overload control (OLC), see Load Control Feature Parameter Description.

Table 7-4 Strict uplink admission thresholds for RRC connection setup requests

Cause of RRC Connection Setup Request Uplink Admission Threshold (ThdUL,RRC)

Emergency callDetachment


Real-time services UlNonCtrlThdForAMR + RTRRCCacThdOffset (admission threshold offset for the RRC connection setup request of a real-timeservice)

Non-real-time services UlNonCtrlThdForOther + NRTRRCCacThdOffset (admission threshold offset for the RRC connection setup request of a non-real-time service)

Other services UlOlcTrigThd + OtherRRCCacThdOffset (admission threshold offset for the RRC connection setup request of the other service)

Admission Criteria for Other Resource Requests in an R99 Cell

When algorithm 1 is used for an R99 cell, the uplink admission criteria for resource requests other than RRC connection setup requests are as follows:

1. If UL_UU_OLC of NBMLdcAlgoSwitch is selected and the cell is overloaded, service admission fails. If UL_UU_OLC of NBMLdcAlgoSwitch is deselected or the cell isnot overloaded, the RNC performs the next step.

2. The RNC checks whether the sum of UL,R99-Total and UL is less than or equal to ThdUL,Nonctl. If yes, uplink admission based on algorithm 1 succeeds. Otherwise,admission fails.

ThdUL,Nonctl is the admission threshold for the uplink power load of non-HSPA services. The threshold varies according to resource request types, as described in Table 7-5 .

Table 7-5 Admission thresholds for the uplink power load of non-HSPA services

Resource Request Type Admission Threshold for the Uplink Power Load of Non-HSPA Services (ThdUL,Nonctl)

AMR services If CSRABCacOptSwitch is set to OFF, UlNonCtrlThdForAMR is used as ThdUL,Nonctl.If CSRABCacOptSwitch is set to ON:When the OLC algorithm is enabled (UL_UU_OLC of NBMLdcAlgoSwitch is selected), the uplink OLC triggering threshold(UlOlcTrigThd) is used as ThdUL,Nonctl.When the OLC algorithm is disabled (UL_UU_OLC of NBMLdcAlgoSwitch isdeselected), ThdUL,Nonctl is 100%.

Non-AMR services UlNonCtrlThdForNonAMR

Handovers UlNonCtrlThdForHo

Other services UlNonCtrlThdForOther

Admission Criteria for Other Resource Requests in an SC-HSUPA Cell (for the DCH RAB)

In an SC-HSUPA cell, if the bearer type is the DCH RAB, uplink admission based on algorithm 1 succeeds when both the following criteria are met:

(UL,NonCtrl + UL) ThdUL,NonctlThdUL,Nonctl is the admission threshold for the uplink power load of non-HSPA services. For details about the admission threshold, see Table 7-5.

Either of the two inequations applies: (UL,HSUPA-Total + UL) ThdUL,total or (UL,R99Prefer-Total + UL) ThdUL,totalThdUL,total is the admission threshold for the total uplink power of the cell. See Table 7-6 for details.

Table 7-6 Admission thresholds for the total uplink power of the cell

Resource Request Type Admission Threshold for the Total Uplink Power of the Cell (ThdUL,total)

AMR services If CSRABCacOptSwitch is set to OFF, UlCellTotalThd is used as ThdUL,total.If CSRABCacOptSwitch is set to ON:When the OLC algorithm is enabled (UL_UU_OLC of NBMLdcAlgoSwitch is selected), the uplink OLC triggering threshold (UlOlcTrigThd)is used as ThdUL,total.When the OLC algorithm is disabled (UL_UU_OLC of NBMLdcAlgoSwitch is deselected), ThdUL,total is 100%.

Other services UlCellTotalThd

Admission Criteria for Other Resource Requests in an SC-HSUPA Cell (for the SC-HSUPA RAB)

In an SC-HSUPA cell, if the bearer type is the SC-HSUPA RAB, uplink admission based on algorithm 1 succeeds when either PBR-based admission or load-based admissionsucceeds.

The RNC admits the IP multimedia subsystem (IMS) signaling services carried on HSUPA RABs directly.

PBR-based Admission DecisionsThe RNC performs PBR-based admission control only when the HSUPA PBR measurement switch is turned on (HSUPA_PBR_MEAS of NBMCacAlgoSwitch is set to 1).

The uplink provided bit rate (PBR) is the effective uplink throughput on all users corresponding to a scheduling priority indicator (SPI) successfully received by the NodeB. PBR isperiodically reported by the NodeB to the RNC.

If the sum of PBRs of some users is greater than the sum of their GBRs multiplied by a certain factor, the RNC determines that the QoS requirements of the cell are met. In this case,the RNC can admit new users. PBR-based admission succeeds if any of the criteria described in Table 7-7 is met.

Table 7-7 PBR-based admission criteria

SN User Range Admission Criteria Parameter Description

1 All HSUPA users whose schedulingpriorities are lower than the priority of theuser being admitted

ThdL is HsupaLowPriorityUserPBRThd

2 All HSUPA users whose schedulingpriorities equal the priority of the userbeing admitted

ThdE is HsupaEqualPriorityUserPBRThd

3 All HSUPA users whose schedulingpriorities are higher than the priority of theuser to be admitted

ThdGE is HsupaHighPriorityUserPBRThd

Load-based Admission Decisions

For HSUPA scheduling services, load-based admission succeeds if the following formula is satisfied:

UL,HSUPA-Total + UL UlCellTotalThdOtherwise, load-based admission fails.

For HSUPA non-scheduling services. load-based admission succeeds only when both the following criteria are met:

(UL,HSUPA-Total + UL) UlCellTotalThd(UL,NonCtrl + UL) ThdUL,NonctlThdUL,Nonctl is the admission threshold for the uplink power load of non-HSPA services. See Table 7-5 for details.

Admission Criteria for Other Resource Requests in a DC-HSUPA Cell

In a DC-HSUPA cell, if the bearer type is the DCH RAB or SC-HSUPA RAB, uplink admission decisions based on algorithm 1 are the same as those in an SC-HSUPA cell. Fordetails, see Admission Criteria for Other Resource Requests in an SC-HSUPA Cell (for the DCH RAB) and Admission Criteria for Other Resource Requests in an SC-HSUPA Cell (forthe SC-HSUPA RAB).

In a DC-HSUPA cell, if the bearer type is the DC-HSUPA RAB, the RNC performs load-based admission control.

For DC-HSUPA non-scheduling services

The RNC makes load-based admission decisions only on the primary cell. The admission decision method is the same as that for an SC-HSUPA non-scheduling service.

For DC-HSUPA scheduling services

The RNC makes load-based admission decisions on the primary or secondary cell. Uplink admission based on algorithm 1 succeeds if load-based admission succeeds oneither the primary or secondary cell. The admission decision method is the same as that for an SC-HSUPA scheduling service.

7.2.2 Downlink Admission Control Algorithm 1In downlink, algorithm 1 makes admission decisions based on resource requests and cell types (R99 cells, SC-HSDPA cells, and multi-carrier HSDPA cells such as DC-HSDPA cells,DB-HSDPA, or 4C-HSDPA cells).

Calculation of Downlink Power Load for a Cell

The following describes how to calculate the downlink power load for an R99 cell, SC-HSDPA cell, and multi-carrier HSDPA cell.

For an R99 CellIn an R99 cell, the RNC makes downlink admission decisions according to the TCP-based total downlink load, which is calculated in real time by the load measurement module of theRNC.

For an R99 cell, the TCP-based total downlink load factor is represented by DL,R99-Total and calculated using the following formula:DL,R99-Total = TCP + DL,CCHWhere,

TCP is the transmitted carrier power (TCP), which is the ratio of the total TCP value on one downlink carrier to the maximum downlink transmission power MaxTxPower.DL,CCH is the load factor reserved for the downlink common channels. It is set by DlCCHLoadRsrvCoeff.

For an SC-HSDPA CellIn an SC-HSDPA cell, algorithm 1 uses the following downlink power load factors:

TCP-based total downlink load factor

For an SC-HSDPA cell, it is represented by DL,HSDPA-Total and calculated using the following formula:DL,HSDPA-Total = TCP + DL,CCH + DL,HSUPAResWhere,

DL,HSUPARes is the power load factor reserved for HSUPA downlink control channels (E-AGCH/E-RGCH/E-HICH). It is set by DlHSUPARsvdFactor.The other variables are defined the same way as for an R99 cell.

Downlink non-HSPA power load factor

It is represented by DL,NonHSPA. DL,NonHSPA is the ratio of the total transmitted power for the codes not used in HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH, and E-HICHchannels on one downlink carrier to the maximum transmission power MaxTxPower.

DL,NonHSPA is measured by the NodeB and periodically reported to the RNC.HSDPA GBP load factor

It is represented by DL,GBP. Guaranteed Bit rate Power (GBP) is the power required to reach the GBR of HSDPA users in a cell.DL,GBP is calculated based on the GBR of HSDPA users in a cell. The NodeB periodically reports DL,GBP to the RNC.HSDPA GBP-based total downlink load factor

It is represented by DL,GBP-Total and calculated using the following formula:DL,GBP-Total = DL,NonHSPA + min (DL,GBP + DL,HSUPARes, DL,MaxHSPA) + DL,CCHWhere,

DL,MaxHSPA is the threshold for the maximum available HSDPA power. It is calculated based on HspaPower using the formula DL,MaxHSPA = 1 10(-HspaPow er/10).Total downlink load factor for preferential admission of R99 services

It is represented by DL,R99Prefer-Total. When the GBR for HSDPA services is too high, the HSDPA GBP-based total downlink load factor may also be too high, andtherefore R99 service admission is difficult. In this case, DL,R99Prefer-Total ensures that R99 services are preferentially admitted. It is calculated using the following formula:DL,R99Prefer-Total = DL,NonHSPA + ThdHSDPAMaxGBP + DL,HSUPARes + DL,CCHWhere,

ThdHSDPAMaxGBP is the maximum guaranteed load threshold for HSDPA services in the cell when the RNC makes an admission decision on an R99 service. It is set byHsdpaMaxGBPThd.

For a Multi-carrier HSDPA CellA multi-carrier HSDPA cell can be a DC-HSDPA, DB-HSDPA, or 4C-HSDPA cell. It provides multi-carrier HSDPA services for users. With the Flexible DC/DB-HSDPA feature disabled,calculation of the downlink power load for a DC-HSDPA cell is different from that for a DB-HSDPA or 4C-HSDPA cell.

For a DC-HSDPA cell with the Flexible DC/DB-HSDPA feature disabled

The RNC needs to perform admission control based on single cell level and the DC-HSDPA cell group level. Therefore, the downlink HSDPA GBP loads for the primary andsecondary cells and the DC-HSDPA cell group are calculated.

For a single cell, the HSDPA GBP load includes the downlink non-HSPA power load and HSDPA GBP load for SC-HSDPA users in the cell.

For a DC-HSDPA cell group, the HSDPA GBP power load includes the following parts shown in Figure 7-2:

Downlink non-HSPA power load on the primary and secondary cells

HSDPA GBP load for SC-HSDPA users on the primary and secondary cells

HSDPA GBP load for DC-HSDPA users in the DC-HSDPA cell group

Figure 7-2 HSDPA GBP load of a DC-HSDPA cell group with the Flexible DC/DB-HSDPA feature disabled

For a DC-HSDPA cell with the Flexible DC/DB-HSDPA feature enabled or a DB-HSDPA/4C-HSDPA cell

The RNC calculates the total HSDPA GBP factor on the primary cell and the secondary cell.

On a cell, the total HSDPA GBP consists of three parts shown in Figure 7-3:

Downlink non-HSPA power load on the cell

HSDPA GBP load for SC-HSDPA users on the cell

HSDPA GBP load for multi-carrier HSDPA users on the cell

In calculation of HSDPA GBP load for multi-carrier HSDPA users, the total GBP used for each DC-HSUPA/DB-HSDPA/4C-HSDPA user is calculated and thenapportioned on each carrier of the cell group based on the transmit power ratio per carrier.

Figure 7-3 HSDPA GBP load of a DC-HSDPA cell with the Flexible DC/DB-HSDPA feature enabled or a DB-HSDPA/4C-HSDPA cell

Downlink Admission Decisions Based on Algorithm 1

Figure 7-4 shows the procedure for a downlink admission decision based on algorithm 1.

Figure 7-4 Procedure for a downlink admission decision based on algorithm 1

This procedure is implemented as follows:

1. The RNC calculates the downlink power load for the cell based on the result from the load measurement module.

2. The RNC calculates the downlink power load increase (DL) based on the initial admission rate of the new service and the pilot quality received at the UE.

NOTE:For details about the initial admission rate, see Load Control Feature Parameter Description.

In admission control on an RRC connection setup request, the RNC calculates the load increase based on the SRB rate carried in the RRC connection setup request. TheSRB rate of an RRC connection setup request is set by running the SET URRCESTCAUSE command.


In algorithm 1, downlink admission criteria vary with the resource request type, cell type, and bearer type. See Table 7-8 for details. If the admission criteria are met, downlinkadmission based on algorithm 1 succeeds. Otherwise, downlink admission based on algorithm 1 fails.

Table 7-8 Downlink admission criteria in algorithm 1

Resource Request Type Cell Type Bearer Type Admission Criteria Described In

RRC connection setup requests R99 cellsHSDPA cells

N/A Admission Criteria for RRC Connection Setup Requests

Other resource requests (such as RABsetup, RAB reconfiguration, handover, andcell update)

R99 cells DCH RAB Admission Criteria for Other Resource Requests in anR99 Cell

SC-HSDPA cells DCH RAB Admission Criteria for Other Resource Requests in anSC-HSDPA Cell (for the DCH RAB)

SC-HSDPA RAB Admission Criteria for Other Resource Requests in anSC-HSDPA Cell (for the SC-HSDPA RAB)

DC-HSDPA cells DCH RABSC-HSDPA RABDC-HSDPA RAB

Admission Criteria for Other Resource Requests in a DC-HSDPA Cell

DB-HSDPA cells4C-HSDPA cells

DCH RABSC-HSDPA RABDB-HSDPA RAB4C-HSDPA RAB

Admission Criteria for Other Resource Requests in a DB-HSDPA or 4C-HSDPA Cell

Admission Criteria for RRC Connection Setup Requests

In algorithm 1, the downlink admission criteria for RRC connection setup requests are as follows:

For R99 cells, downlink admission based on algorithm 1 succeeds if the following formula is satisfied:

DL,R99-Total + DL ThdDL,RRCFor HSDPA cells, downlink admission based on algorithm 1 succeeds if the following formula is satisfied:

DL,NonCtrl + DL ThdDL,RRCThdDL,RRC is the downlink admission threshold for RRC connection setup requests. Algorithms 1, 2, and 3 use the same threshold in downlink. The RNC performs either loose or strictadmission control on RRC connection setup requests according to the value of RRCCacChoice:

If RRCCacChoice is set to LOOSE_CAC, the RNC uses the loose admission thresholds listed in Table 7-9.

If RRCCacChoice is set to STRICT_CAC, the RNC uses the strict admission thresholds listed in Table 7-10.

Table 7-9 Loose downlink admission threshold for RRC connection setup requests

Cause of RRC Connection Setup Request Downlink Admission Threshold (ThdDL,RRC)

Emergency callDetachmentRegistration

The RRC connection is set up directly without admission control.

Other services When DL_UU_OLC of NBMLdcAlgoSwitch is set to 1:If the cell is overloaded, the RNC rejects the RRC connection setup request.If the cell is not overloaded, thedownlink OLC triggering threshold (DlOlcTrigThd) is used as ThdDL,RRC.When DL_UU_OLC of NBMLdcAlgoSwitch is set to 0, the downlink OLC triggering threshold DlOlcTrigThd isused as ThdDL,RRC.

NOTE:For details about the overload state of a cell and OLC, see Load Control Feature Parameter Description.

Table 7-10 Strict downlink admission threshold for RRC connection setup requests

Cause of RRC Connection Setup Request Downlink Admission Threshold (ThdDL,RRC)

Emergency callDetachment


Real-time services DlConvAMRThd + RTRRCCacThdOffset (admission threshold offset for the RRC connection setup request of a real-time service)

Non-real-time services DlOtherThd + NRTRRCCacThdOffset (admission threshold offset for the RRC connection setup request of a non-real-timeservice)

Other services DlOlcTrigThd + OtherRRCCacThdOffset (admission threshold offset for the RRC connection setup request of the other service)

Admission Criteria for Other Resource Requests in an R99 Cell

When algorithm 1 is used for an R99 cell, the downlink admission criteria for resource requests other than RRC connection setup requests are as follows:

1. If DL_UU_OLC of NBMLdcAlgoSwitch is selected and the cell is overloaded, admission fails. If DL_UU_OLC of NBMLdcAlgoSwitch is deselected or the cell is notoverloaded, the RNC performs the next step.

2. The RNC checks whether the sum of DL,R99-Total and DL is less than or equal to ThdDL,Nonctl. If yes, admission succeeds. Otherwise, admission fails.ThdDL,Nonctl is the admission threshold for the downlink power load of non-HSPA services. The threshold varies with resource request types, as described in Table 7-11.

Table 7-11 Admission thresholds for the downlink power load of non-HSPA services

Resource Request Type Admission Threshold for the Downlink Power Load of Non-HSPA Services (ThdDL,Nonctl)

AMR services If CSRABCacOptSwitch is set to OFF, DlConvAMRThd is used as ThdDL,Nonctl.If CSRABCacOptSwitch is set to ON:When the OLC algorithm is enabled (DL_UU_OLC of NBMLdcAlgoSwitch is selected), the downlink OLC triggering threshold(DlOlcTrigThd) is used as ThdDL,Nonctl.When the OLC algorithm is disabled (DL_UU_OLC of NBMLdcAlgoSwitch isdeselected), ThdDL,Nonctl is 100%.

Non-AMR services DlConvNonAMRThd

Handovers DlHOThd

Others DlOtherThd

Admission Criteria for Other Resource Requests in an SC-HSDPA Cell (for the DCH RAB)

In an SC-HSDPA cell, if the bearer type is the DCH RAB, downlink admission based on algorithm 1 succeeds when both the following criteria are met:

Non-HSPA power-based admission criterion: (DL,NonHSPA + DL) ThdDL,NonctlThdDL,Nonctl is the admission threshold for the downlink power load of non-HSPA services. See Table 7-12 for details.

Total cell power-based admission criterion: Any of the following three inequations applies:

(DL,HSDPA-Total + DL) ThdDL,total(DL,GBP-Total + DL) ThdDL,total(DL,R99Prefer-Total + DL) ThdDL,totalThdDL,total is the admission threshold for the total downlink power of the cell. See Table 7-12.

Table 7-12 Admission thresholds for the total downlink power of the cell

Resource Request Type Admission Threshold for the Total Downlink Power of the Cell (ThdDL,total)

AMR services If CSRABCacOptSwitch is set to OFF, DlCellTotalThd is used as ThdDL,total.If CSRABCacOptSwitch is set to ON:When the OLC algorithm is enabled (DL_UU_OLC of NBMLdcAlgoSwitch is selected), DlOlcTrigThd is used asThdDL,total.When the OLC algorithm is disabled (DL_UU_OLC of NBMLdcAlgoSwitch is deselected), ThdDL,total is 100%.

Other services DlCellTotalThd

Admission Criteria for Other Resource Requests in an SC-HSDPA Cell (for the SC-HSDPA RAB)

In an SC-HSDPA cell, if the bearer type is the SC-HSDPA RAB, downlink admission based on algorithm 1 succeeds when either PBR-based admission or load-based admissionsucceeds.

PBR-based Admission Decisions

The RNC performs PBR-based admission control only when the HSDPA PBR measurement switch is turned on (HSDPA_PBR_MEAS of NBMCacAlgoSwitch is set to 1).

The downlink PBR is the effective downlink throughput on all UEs corresponding to an SPI successfully received by the NodeB. PBR is periodically reported by the NodeB to the RNC.

If the sum of PBRs of users implementing a certain service is greater than the sum of their GBRs multiplied by a certain factor, the RNC determines that the QoS requirements of theseusers are met. In this case, the RNC can admit new users. For streaming services and BE services, PBR-based admission succeeds if the following service-specific inequations apply:

Streaming services:

Where,

PBRstrm is the PBR of all existing streaming services.

Thdhsdpa-str is the PBR-based admission threshold for streaming services HsdpaStrmPBRThd.

BE services:

Where,

PBRbe is the PBR of all existing BE services.

Thdhsdpa-be is the PBR-based admission threshold for BE services HsdpaStrmPBRThd.

NOTE:Conversational services in the PS domain carried on HSPA RABs can be considered as streaming services in admission control.

Load-based Admission DecisionsLoad-based admission succeeds only when both the following criteria are met:

GBP-based admission criterion: (DL,GBP + DL) DL,MaxHSPATotal cell power-based admission criterion: Either of the following two inequations applies:

(DL,HSDPA-Total + DL) ThdDL,total(DL,GBP-Total + DL) ThdDL,totalThdDL,total is the admission threshold for the total downlink power of the cell. For details about the admission threshold, see Table 7-12.

Admission Criteria for Other Resource Requests in a DC-HSDPA Cell

Downlink admission control based on algorithm 1 depends on whether the Flexible DC/DB-HSDPA feature is enabled in the DC-HSDPA cell.

NOTE:For details about the Flexible DC/DB-HSDPA feature, see Flexible DCDB-HSDPA Feature Parameter Description.

For a DC-HSDPA Cell with the Flexible DC/DB-HSDPA Feature DisabledThe RNC performs admission control based on single carriers and the DC-HSDPA cell group. For details about how to calculate the downlink cell power loads for single carriers and theDC-HSDPA cell group, see Calculation of Downlink Power Load for a Cell.

The admission policies for different RAB types are as follows:

For the DCH RAB or SC-HSDPA RAB

The RNC performs power-based admission control on both single carriers and the DC-HSDPA cell group. If the admission criteria are met, downlink admission based onalgorithm 1 succeeds. Otherwise, downlink admission based on algorithm 1 fails.

For the DC-HSDPA RAB

The RNC performs power-based admission control for each DC-HSDPA cell group.

Table 7-13 describes the admission policies for a DC-HSDPA cell group with the Flexible DC/DB-HSDPA feature disabled.

Table 7-13 Admission policies for a DC-HSDPA cell group with the Flexible DC/DB-HSDPA feature disabled

Bearer Type Admission Level Admission Policy

DCH RAB Single carrier Same as the admission policy for an SC-HSDPA cell. For details, see Admission Criteria for Other Resource Requests in anSC-HSDPA Cell (for the DCH RAB).

DC-HSDPA cell group The total GBP for a DC-HSDPA cell group is less than or equal to the sum of admission thresholds for the total downlinkpower on the primary cell and secondary cell.For details about the admission threshold for the total downlink power, see Table 7-12 .

SC-HSDPA RAB Single carrier Same as the admission policy for an SC-HSDPA cell. For details, see Admission Criteria for Other Resource Requests in anSC-HSDPA Cell (for the DCH RAB).

DC-HSDPA cell group Load-based admission succeeds. The following criteria must be both met:The total GBP on the primary and secondary cells of the DC-HSDPA cell group is less than or equal to the sum ofthreshold for the maximum available HSDPA power on the primary and secondary cells.The total power on the primary and secondary cells of the DC-HSDPA cell group is less than or equal to the sumof threshold for the total downlink power on the primary and secondary cells.

NOTE:For details about the preceding criteria, see Admission Criteria for Other Resource Requests in an SC-HSDPA Cell (for theSC-HSDPA RAB).

DC-HSDPA RAB DC-HSDPA cell group PBR-based admission or load-based admission succeeds.PBR-based admission decisionsFor streaming services and BE services, PBR-based admission is performed only for all DC-HSDPA users in theDC-HSDPA cell group. For details about the admission criteria, see Admission Criteria for Other ResourceRequests in an SC-HSDPA Cell (for the SC-HSDPA RAB).Load-based admission decisionsBoth the following criteria are met:Criterion 1: The total GBP on the primary and secondary cells of the DC-HSDPA cell group is less than or equal tothe sum of threshold for the maximum available HSDPA power on the primary and secondary cells.Criterion 2: The total power on the primary and secondary cells of the DC-HSDPA cell group is less than or equalto the sum of threshold for the total downlink power on the primary and secondary cells.

For a DC-HSDPA Cell with the Flexible DC/DB-HSDPA Feature EnabledAdmission control is the same as that for a DB-HSDPA or 4C-HSDPA Cell. For details, see Admission Criteria for Other Resource Requests in a DB-HSDPA or 4C-HSDPA Cell.

Admission Criteria for Other Resource Requests in a DB-HSDPA or 4C-HSDPA Cell

For details about how to calculate the GBP load for a multi-carrier HSDPA cell, see Calculation of Downlink Power Load for a Cell.

In a DB-HSDPA/4C-HSDPA cell or a DC-HSDPA cell with the Flexible DC/DB-HSDPA feature enabled, the RNC makes admission decisions on the primary and secondary cells.Downlink admission based on algorithm 1 succeeds if load-based admission succeeds on the primary or secondary cell.

The admission policies for different bearer types are as follows:

For the DCH RAB

Same as the admission policy for the DCH RAB in an SC-HSDPA cell. For details, seeAdmission Criteria for Other Resource Requests in an SC-HSDPA Cell (for the DCHRAB).

For the SC-HSDPA RAB

The RNC performs load-based admission decisions. The admission policy is the same as that for the SC-HSDPA RAB in an SC-HSDPA cell. For details, see AdmissionCriteria for Other Resource Requests in an SC-HSDPA Cell (for the SC-HSDPA RAB).

For the DC-HSDPA/DB-HSDPA/4C-HSDPA RAB

The RNC performs load-based admission decisions. The admission policy is the same as that for the SC-HSDPA RAB in an SC-HSDPA cell. For details, see AdmissionCriteria for Other Resource Requests in an SC-HSDPA Cell (for the SC-HSDPA RAB).

7.3 Admission Control Algorithm 2Algorithm 2 performs admission control based on the ENU and the expected ENU increase caused by a new service. The measurement quantities relevant to the cell power load areprocessed and reported by the load measurement module on the RNC. For details about cell load measurements, see Load Control Feature Parameter Description.


7.3.1 ENU

Concept

When the activation factor is 100%, a 12.2 kbit/s AMR service is defined as one ENU. The following aspects are considered when the ENU is calculated:

Cell type (a typical urban cell or a suburban cell)

Traffic QoS, which is the Block Error Rate (BLER)

Target number of retransmissions

Activation factor for a service type, which is set with the SET UADMCTRL command.

Table 7-14 describes the ENU references for some services in typical scenarios. The following are typical configuration scenarios:

The cell is a typical urban cell.

The target BLER of R99 users in the cell is 1%.

Target number of retransmissions:

10% for 2 ms TTI HSUPA users

1% for 10 ms TTI HSUPA users

Activation factors for different service types:

10% for SRBs

50% for AMR 12.2 kbit/s services

10% for DCH PS services

100% for HSPA PS services

Table 7-14 ENU references in typical scenarios

Service ENU

Uplink for DCH Downlink for DCH HSDPA 2 ms TTI HSUPA 10 ms TTI HSUPA

3.4 kbit/s 0.2847 0.0420 0.0279 0.3107 0.1369

13.6 kbit/s 0.5057 0.1115 0.0738 0.36 0.1655

3.4 kbit/s + 12.2 kbit/s 0.8196 0.5420 - 2.0242 1.0869

3.4 kbit/s + 8 kbit/s (PSservice)

0.7548 0.1044 0.545 3.5098 1.7611


0.6500 0.1248 0.8749 3.8713 1.9786

3.4 kbit/s+ 32 kbit/s (PS 0.6228 0.2187 1.463 4.5856 2.4106

service)


0.7566 0.3252 2.5545 5.9806 3.2625


0.9248 0.5926 4.6851 8.6430 4.9192


1.0305 0.6615 5.2225 9.2279 5.2463


1.4399 1.0489 9.1193 13.1063 7.4698


2.1150 1.5523 13.9332 17.1227 9.8773

NOTE:In Table 7-14:

HSDPA (3.4 kbit/s or 13.6kbit/s) indicates the ENU when SRB over HSDPA is used.HSDPA (3.4 kbit/s + n kbit/s) indicates the ENU when SRB over DCH and TRB over HSDPA are used.HSUPA (3.4 kbit/s or 13.6kbit/s) indicates the ENU when SRB over HSUPA is used.HSUPA (3.4 kbit/s + n kbit/s) indicates the ENU when SRB over DCH and TRB over HSUPA are used.

Calculation of Uplink ENU

Uplink admission control based on algorithm 2 uses the following load measurements:

Total uplink ENU load factor

It is represented by UL,ENU and calculated using the following formula:UL,ENU = ENUUL,Total/ENUUL,Max + UL,CCHWhere,

ENUUL,Total is the sum of ENUs corresponding to the RABs that have been used in the cell.

ENUUL,Max is the maximum ENU of the cell. It is set by UlTotalEqUserNum.

UL,CCH is the reserved load on the uplink common channels. It is set by UlCCHLoadFactor.Total uplink load factor of ENU for preferential admission of R99 services

It is represented by UL,R99Prefer-ENU.When the GBR for HSUPA services is too high, the total uplink ENU load factor may also be too high, and therefore R99 service admission is difficult. In this case,UL,R99Prefer-ENU ensures that R99 services are preferentially admitted. It is calculated using the following formula:UL,R99Prefer-ENU = UL,DCH_ENU + ThdHSUPAMaxGBPWhere,

UL,DCH_ENU is the ENU load of all DCH RABs in a cell. It is the ratio of the sum of ENUs for all DCH RABs to the maximum ENU in a cell UlTotalEqUserNum.ThdHSUPAMaxGBP is the maximum guaranteed load threshold for HSUPA services when the RNC makes an admission decision on an R99 service. It is set byHsupaMaxGBPThd.

Calculation of Downlink ENU

Downlink admission control based on algorithm 2 uses the following load measurements:

Total downlink ENU load factor

It is represented by DL,ENU and calculated using the following formula:DL,ENU = ENUDL,Total/ENUDL,Max + DL,CCHWhere,

ENUDL,Total is the sum of ENUs for RABs that have been used in the cell. For multi-carrier HSDPA users (such as DC-HSDPA/DB-HSDPA/4C-HSDPA users),the consumed downlink ENU is calculated only on the primary cell.

ENUDL,Max is the maximum ENU of the cell. It is set by DlTotalEqUserNum.

DL,CCH is the reserved load on the downlink common channels. It is set by DlCCHLoadRsrvCoeff.Total downlink ENU load factor for preferential admission of R99 services

It is represented by DL,R99Prefer-ENU.When the GBR for HSDPA services is too high, the total downlink ENU load factor may also be too high, and therefore R99 service admission is difficult. In this case,DL,R99Prefer-ENU ensures that R99 services are preferentially admitted. It is calculated using the following formula:DL,R99Prefer-ENU = DL,DCH_ENU+ ThdHSDPAMaxGBPWhere,

DL,DCH_ENU is the ENU load of all DCH RABs in a cell. It is the ratio of the sum of ENUs for all DCH RABs to the maximum ENU in a cell DlTotalEqUserNum.ThdHSDPAMaxGBP is the maximum guaranteed load threshold for HSDPA services when the RNC makes an admission decision on an R99 service. It is set byHsdpaMaxGBPThd.

7.3.2 Uplink Admission Control Algorithm 2Uplink admission control based on algorithm 2 depends on the overload state of a cell.

If a cell is not in the OLC state, the admission procedure is as follows:

1. The RNC calculates the uplink ENU load for the cell based on the statistics from the load measurement module.

2. The RNC estimates the ENU load increase (UL,ENU) based on the initial admission rate of the new service.

NOTE:

For details about the initial admission rate, see Load Control Feature Parameter Description.In admission control on an RRC connection setup request, the RNC calculates the load increase based on the SRB rate carried in the RRC connection setuprequest. The SRB rate of an RRC connection setup request is set by running the SET URRCESTCAUSE command.


The admission criteria vary with resource request types.

Admission criteria for RRC connection setup requests

(UL,ENU + UL,ENU) ThdUL,RRCThdUL,RRC is the uplink admission threshold for RRC connection setup requests. The threshold in loose admission is different from that in strict admission. See Table 7-3and Table 7-4 for details.

Admission criteria for other resource requests

Other resource requests include RAB setup, RAB reconfiguration, handover, and cell update. The admission criteria vary with bearer types and service types.

In the following admission criteria, ThdUL,Nonctl is the admission threshold for the uplink power load of non-HSPA services, which is the same as the threshold in Table 7-5;ThdUL,total is the admission threshold for the total uplink power of the cell, which is the same as the threshold in Table 7-6.

If the bearer type is the DCH RAB, admission succeeds if either of the following criteria are met:

Criterion 1: (UL,ENU + UL,ENU) ThdUL,NonctlCriterion 2: (UL,R99Prefer-ENU + UL,ENU) ThdUL,totalIf the bearer type is the SC-HSUPA RAB, the criterion is as follows:

(UL,ENU + UL,ENU) ThdUL,NonctlIf the bearer type is the DC-HSUPA RAB, the RNC performs admission control only on the primary cell. The admission criterion is the same as that for the SC-HSUPARAB.

If a cell is in the OLC state, the admission procedure is as follows:

If the RTWP anti-interference function switch is turned on (RTWP_RESIST_DISTURB of NBMCacAlgoSwitch is selected), uplink admission based on algorithm 2succeeds only when UL,ENU is less than CellUlEquNumCapacity.If the RTWP anti-interference function switch is turned off (RTWP_RESIST_DISTURB of NBMCacAlgoSwitch is deselected), the RNC rejects the service request.

7.3.3 Downlink Admission Control Algorithm 2This procedure is implemented as follows:

1. The RNC calculates the downlink ENU load for the cell based on the statistics from the load measurement module.

2. The RNC estimates the ENU load increase (DL,ENU) based on the initial admission rate of the new service.

NOTE:



The admission criteria vary with resource request types.

Admission criteria for RRC connection setup requests

(DL,ENU + DL,ENU) ThdDL,RRCThdDL,RRC is the downlink admission threshold for RRC connection setup requests. The threshold in loose admission is different from that in strict admission. See Table 7-9and Table 7-10 for details.

Admission criteria for other resource requests

The admission criteria vary with bearer types. In the following admission criteria, ThdDL,Nonctl is the downlink power-based admission threshold for non-HSPA services,which is the same as the threshold in Table 7-11; ThdDL,total is the admission threshold for the total downlink power of the cell, which is the same as the threshold in Table7-12.

If the bearer type is the DCH RAB, admission succeeds if either of the following criteria are met:

Criterion 1: (DL,ENU + DL,ENU) ThdDL,NonctlCriterion 2: (DL,R99Prefer-ENU + DL,ENU) ThdDL,totalIf the bearer type is the SC-HSDPA RAB, the criterion is as follows:

(DL,ENU + DL,ENU) ThdDL,NonctlIf the bearer type is the DC-HSDPA RAB, admission control on the DC-HSDPA RAB depends on whether the Flexible DC-DB/HSDPA feature is enabled in theDC-HSDPA cell.

If the Flexible DC/DB-HSDPA feature is not enabled, admission control is performed based on the DC-HSDPA cell group. Admission succeeds if the sum ofdownlink ENU loads (DL,ENU) on the primary and secondary cells is less than or equal to the sum of admission thresholds (ThdDL,Nonctl) for the primary andsecondary cells.

If the Flexible DC/DB-HSDPA feature is enabled, admission control is performed only on the primary cell. The admission criterion is the same as that for the SC-HSDPA RAB.

If the bearer type is the DB-HSDPA/4C-HSDPA RAB, admission control is performed only on the primary cell. The admission criterion is the same as that forthe SC-HSDPA RAB.

7.4 Admission Control Algorithm 3Algorithm 3 performs admission control based on the cell power load.

Algorithm 3 is similar to algorithm 1. The only difference is that the estimated power load increase caused by the new service is always set to 0 in algorithm 3. In algorithm 3, the RNCdetermines whether the current cell power load exceeds a preset threshold when making a decision on a service request. If the cell power load exceeds the threshold, the RNC rejectsthe service request. Otherwise, the RNC admits the service.


7.5 Admission Control Algorithm 4Algorithm 4 performs admission control based on the expected load increase that corresponds to the actual uplink service load.

Algorithm 4 applies to admission control only in uplink.

Calculation of the Actual Uplink Service Load

The total uplink service load factor is represented by UL,Actual-Total and calculated using the following formula:UL,Actual-Total = UL,Actual + UL,CCHWhere,

UL,Actual is the actual uplink service load factor. It considers RTWP measurement results, the total uplink service load and the uplink minimum guaranteed service load.The total uplink service load includes R99 service load, HSUPA service load, and control channel load.

The uplink minimum guaranteed service load includes R99 service load, HSUPA service load required by the HSUPA GBR, and control channel load.

For a DC-HSUPA cell, the actual uplink service load introduced by a DC-HSUPA user is calculated and then apportioned on the primary and secondary cellsbased on the user rate ratio per cell.

UL,CCH is the reserved load on the uplink common channels. It is set by UlCCHLoadFactor.

NOTE:For details about the preceding load, see Load Control Feature Parameter Description.

Measuring the uplink minimum guaranteed service load depends on the hardware. For details, see Load Control Feature Parameter Description. When the feature ofIndependent Demodulation of Signals from Multiple RRUs in One Cell is configured, this cell does not support algorithm 4.If measurements on the actual uplink service load for a cell are unavailable, for example, when the relevant NodeB boards cannot report the measurement results, the RNCperforms admission control for the cell based on ENU (algorithm 2). For details about ENU-based admission control, see section 7.3 Admission Control Algorithm 2.

Admission Decisions Based on Algorithm 4

The procedure for an uplink admission decision based on algorithm 4 is as follows:

1. The RNC calculates the uplink power load increase (UL) based on the initial admission rate of the new service.

NOTE:


2. If the sum of UL,Actual-Total and UL is less than or equal to Thd, admission based on algorithm 4 succeeds. Otherwise, service admission fails.Thd is the corresponding admission threshold, which depends on the resource request type.

For RRC connection setup requests

Thd is the uplink admission threshold for RRC connection setup requests, which is described in Table 7-3 and Table 7-4.

For other resource requests

Thd is the uplink power-based admission threshold for non-HSPA services, which is described in Table 7-5.

When the bearer type is the DC-HSUPA RAB:

For DC-HSUPA non-scheduling services, admission decisions are made only on the primary cell.

For DC-HSUPA scheduling services, the RNC makes admission decisions on the primary and secondary cells. Admission based on algorithm 4 succeeds if admission issuccessful on the primary or secondary cell.

Comparison with Other Algorithms

Compared with algorithm 1 and algorithm 3, algorithm 4 enables the RNC to admit more users and increases the user access success rate when the cell serves few users but theRTWP is large due to high traffic volume.

Compared with algorithm 2, algorithm 4 tightens admission control and reduces the number of admitted users when the total number of uplink equivalent users UlTotalEqUserNum isset to a large value in algorithm 2.

Algorithm 4 is based on the actual uplink service load, which considers RTWP rise. Calculation of RTWP rise involves the background noise. The value of background noise is updatedautomatically if the auto-adaptive background noise update algorithm is enabled; otherwise, it is a preset value. If the value of background noise involved in calculation is smaller thanthe actual value, the calculated uplink service load is greater than its actual value and the admission success rate decreases. If the value of background noise involved in calculation isgreater than the actual value, the admission success rate increases. However, the RTWP increases and the call drop rate rises after more users have accessed the cell.

8 Common Channel Admission

This section describes CAC for common channels, which are classified in the following manner:

Common channels except the enhanced FACH and enhanced RACH channels

The common channels except the EFACH (E-FACH for short) and ERACH (E-RACH for short) channels are referred to as traditional common channels in the followingsections.

E-FACH and E-RACH channels

8.1 CAC on Traditional Common ChannelsThe amount of consumed resources for traditional common channels keeps a steady level in general. The RNC does not perform admission control on users over traditional commonchannels except the users over the FACH, on which the RNC will perform admission control by considering the number of online users on the FACH and the cell overload status.

CAC for Users on the FACH

The number of online users on the FACH per cell is limited by RNC. Generally, the maximum number of online users on the FACH is 30. The number can be increased to 60 by turningon FACH_60_USER_SWITCH of the CacSwitch parameter in the SET UCACALGOSWITCH command. The restriction on the number of online users on the FACH can be canceled byturning on FACH_USER_NUM_NOT_CTRL of the NBMCacAlgoSwitch parameter in the ADD UCELLALGOSWITCH command.

CAUTION:When the FACH_USER_NUM_NOT_CTRL switch is turned on, the number of available radio resources will decrease and FACHs will possibly become congested if the number ofonline users on the FACH has reached or exceeded the maximum number specified by FACH_60_USER_SWITCH and the number is still increasing.

If internal RNC specifications are reached, the RNC rejects subsequent service requests on the FACH.

The RNC performs flow control in case of FACH congestion in a cell. For details, see Flow Control Feature Parameter Description.

With CAC, an overloaded cell can accept FACH resource requests only from emergency calls, detachments, and registrations. Admitting or rejecting FACH resource requests fromother service types in an overloaded cell is specified by FACH_UU_ADCTRL of NBMCacAlgoSwitch.

When this switch is turned on, FACH resource requests from other service types in an overloaded cell are rejected.

When this switch is turned off, the RNC decides whether to admit the request according to the number of online users on the FACH per cell.

Reserved Resources for Traditional Common Channels

The reserved resources for traditional common channels are as follows:

NodeB CE resources

The NodeB reserves CE resources for traditional common channels. For details about CE consumption for common channels, see CE Resource Management FeatureParameter Description.

Iub transmission resources

The RNC reserves Iub transmission bandwidth for traditional common channels. For details about CAC based on Iub transmission resources, see Transmission ResourceManagement Feature Parameter Description.

Code resources

Traditional common channels are first set up when a cell is established. Channel code resources have been allocated when channel setup is complete.

Power resources

The RNC reserves some power resources for traditional common channels and the resource reserving thresholds are configurable.

Reserved power load factor for the uplink common channel: It is set by UlCCHLoadFactor.

Reserved power load factor for the downlink common channels: It is set by DlCCHLoadRsrvCoeff.

Reserved power load factor for the HSUPA downlink common control channels, including E-AGCH, E-RGCH, and E-HICH channels: It is set byDlHSUPARsvdFactor.

NOTE:The reserved power specified by UlCCHLoadFactor / DlCCHLoadRsrvCoeff is mainly used for RACH and FACH. The power consumed for other types of traditional common channelsis fixed and calculated in the total downlink power load of the cell, and therefore does not need to be reserved.

8.2 CAC on the E-FACH or E-RACHThe E-FACH and E-RACH channels are over HSPA channels, which consume more resources than traditional common channels do. Therefore, the RNC implements CAC based onIub transmission resources, number of users, and power resources in turn.

For details about CAC based on Iub transmission resources, see Transmission Resource Management Feature Parameter Description.

CAC Based on the Number of E-FACH and E-RACH Users

The admission criteria based on the number of E-FACH and E-RACH users are as follows:

For a resource request on the E-FACH

If the number of E-FACH users in a cell does not exceed the value of MAXEFACHUserNum after the resource request is admitted, the RNC will admit the resourcerequest. Otherwise, the RNC will reject the resource request.

For a resource request on the E-RACH

If the number of E-RACH users in a cell does not exceed the value of MAXERACHUserNum after the resource request is admitted, the RNC will admit the resourcerequest. Otherwise, the RNC will reject the resource request.

CAC Based on Power Resources

The admission policy based on the power resources for resource requests on the E-FACH and E-RACH is similar to that for resource requests on common HSPA channels.

Power-based admission algorithms 1, 3 and 4

When one of algorithms 1, 3 and 4 is selected in NBMUlCacAlgoSelSwitch or NBMDlCacAlgoSelSwitch, the admission policy for resource requests on the E-FACH andE-RACH is basically the same as that for RAB setup requests of the SC-HSDPA/SC-HSUPA services. The only difference is that the estimated load increase of a new E-FACH or E-RACH user is set to 0 because E-FACH and E-RACH activities are low.

Power-based admission algorithm 2

This algorithm is not implemented for resource requests on the E-FACH and E-RACH.

When algorithm 2 is selected in NBMUlCacAlgoSelSwitch or NBMDlCacAlgoSelSwitch, the power-based admission algorithm does not take effect for resource requestson the E-FACH and E-RACH. In this situation, the RNC implements CAC based only on Iub resources and number of users.

With CAC, an overloaded cell can accept E-FACH resource requests only from emergency calls, detachments, and registrations. Admitting or rejecting E-FACH resourcerequests from other service types in an overloaded cell is specified by FACH_UU_ADCTRL of NBMCacAlgoSwitch.

When this switch is turned on, E-FACH resource requests from other service types in an overloaded cell are rejected.

When this switch is turned off, the RNC decides whether to admit the request according to the number of E-FACH users per cell.

FACH_UU_ADCTRL of NBMCacAlgoSwitch also takes effect for E-RACH users in an overloaded cell. This is because the E-RACH depends on the E-FACH and E-RACHusers consume the E-FACH resources in downlink.

9 Follow-up Processing in the Case of Admission Failures

To maximize the access success rate, CAC works with the rate negotiation function and features WRFD-010505 Queuing and Pre-Emption and WRFD-020400 DRD IntroductionPackage.

If service admission fails, the RNC performs Directed Retry Decision (DRD) to admit the service in one of the neighboring cells that support blind handovers and meet the signal qualityrequirements. DRD is controlled by a switch. For details about DRD, see Directed Retry Decision Feature Parameter Description.

If the service fails to be admitted to any of the preceding neighboring cells, the RNC implements the following operations:

For R99 services: Rate negotiation, queuing, and preemption are performed. For details, see Load Control Feature Parameter Description.

For HSPA services: HSPA services are degraded to R99 services and then attempt to access cells by cell priorities on the candidate cell list.

10 Engineering Guidelines

10.1 Deployment of WRFD-020101 Admission ControlThis section describes how to activate, verify, and deactivate the basic feature WRFD-020101 Admission Control.

10.1.1 Requirements

Requirements for hardware

Uplink power admission algorithm 4 introduced in RAN14.0 makes admission decisions based on the total uplink service load that depends on the NodeB boards'measurement of the uplink service load. Only part of NodeB boards supports the measurement. Therefore, not all NodeBs support uplink power admission algorithm 4. Thefollowing NodeBs do not support uplink power admission algorithm 4:

BTS3812A, BTS3812E, and BTS3812AE

DBS3800

3900 series base stations configured with a WBBPa board or a 20 W RRU3801C

Requirements for other features

None

License

None

10.1.2 Activation (Using MML Commands)WRFD-020101 Admission Control consists of four functions, which are NodeB credit resource-based CAC, Iub transmission resource-based CAC, cell code resource-based CAC, andcell power resource-based CAC. Iub transmission resource-based CAC is automatically activated and the other three functions need to be activated separately. There is no particularsequence in which the other three functions must be activated.

Activating NodeB Credit Resource-based CAC

NOTE:NodeB credit resource-based CAC shares the admission policy parameters (including Credit and Code CAC Choice for RRC and CS RAB Setup Resource Allocation Switch) andparameters related to downlink control (including DL Credit and Code Reserved SF for RRC and DL Handover Credit and Code Reserved SF) with cell code resource-basedCAC.

1. Run the RNC MML command SET UCACALGOSWITCH. In this step, select NODEB_CREDIT_CAC_SWITCH(NodeB Credit CAC Switch) from the CAC algorithmswitch drop-down list to turn on the NodeB credit resource-based CAC switch at the RNC level.

2. Run the RNC MML command MOD UCELLALGOSWITCH. In this step, select CRD_ADCTRL(Credit Admission Control Algorithm) from the Cell CAC algorithmswitch drop-down list to turn on the NodeB credit resource-based CAC switch at the cell level.

3. Run the RNC MML command MOD UCELLALGOSWITCH to set the admission policy parameters. In this step, set Credit and Code CAC Choice for RRC toLOOSE_CAC or STRICT_CAC and set CS RAB Setup Resource Allocation Switch to ON or OFF.

4. Run the RNC MML command MOD UCELLCAC.

If Credit and Code CAC Choice for RRC is set to STRICT_CAC, set UL Credit Reserved SF for RRC and DL Credit and Code Reserved SF for RRC in this step.

If CS RAB Setup Resource Allocation Switch is set to OFF, set UL handover credit reserved SF and DL Handover Credit and Code Reserved SF in this step.

Activating Iub Transmission Resource-based CAC

This function is

RAN Feature Documentation

Documents

Transcript of RAN Feature Documentation