CAC Huawei (RAN15.0_03)

WCDMA RANRAN15.0

Call Admission Control FeatureParameter Description

Issue 03Date 2013-09-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent 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 thecustomer. All or part of the products, services and features described in this document may not be within thepurchase 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 representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied. Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.comEmail: [email protected]

Issue 03 (2013-09-30) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.

i

Contents

1 About This Document..................................................................................................................11.1 Scope..............................................................................................................................................................................11.2 Intended Audience..........................................................................................................................................................11.3 Change History...............................................................................................................................................................12 Overview.........................................................................................................................................42.1 CAC Policy.....................................................................................................................................................................52.1.1 System Resources........................................................................................................................................................52.1.2 Resource Requests.......................................................................................................................................................52.1.3 Channels......................................................................................................................................................................62.1.4 Service Priorities..........................................................................................................................................................62.2 CAC Procedure...............................................................................................................................................................63 NodeB Credit Resource-based CAC..........................................................................................93.1 NodeB Credit Resources..............................................................................................................................................103.2 Admission on RNC.......................................................................................................................................................103.2.1 Calculation of the Remaining NodeB Credit Resources on the RNC Side...............................................................103.2.2 Admission Decisions on RRC Connection Setup Requests......................................................................................113.2.3 Admission Decisions on Other Resource Requests...................................................................................................133.3 Admission on NodeB....................................................................................................................................................144 Iub Transmission Resource-based CAC.................................................................................165 Cell Code Resource-based CAC...............................................................................................175.1 Admission Decisions on RRC Connection Setup Requests.........................................................................................185.2 Admission Decisions on Other Resource Requests......................................................................................................196 CAC Based on the Number of HSPA Users...........................................................................216.1 CAC for HSDPA Users................................................................................................................................................226.2 CAC for HSUPA Users................................................................................................................................................227 Cell Power Resource-based CAC.............................................................................................237.1 Overview......................................................................................................................................................................247.2 Admission Control Algorithm 1...................................................................................................................................257.2.1 Uplink Admission Control Algorithm 1....................................................................................................................257.2.2 Downlink Admission Control Algorithm 1...............................................................................................................38

WCDMA RANCall Admission Control Feature Parameter Description Contents


ii

7.3 Admission Control Algorithm 2...................................................................................................................................547.3.1 ENU...........................................................................................................................................................................547.3.2 Uplink Admission Control Algorithm 2....................................................................................................................577.3.3 Downlink Admission Control Algorithm 2...............................................................................................................587.4 Admission Control Algorithm 3...................................................................................................................................597.5 Admission Control Algorithm 4...................................................................................................................................608 Common Channel Admission...................................................................................................628.1 CAC on Traditional Common Channels......................................................................................................................638.2 CAC on the E-FACH or E-RACH...............................................................................................................................649 Follow-up Processing in the Case of Admission Failures...................................................6610 Engineering Guidelines...........................................................................................................6710.1 Deployment of WRFD-020101 Admission Control...................................................................................................6710.1.1 Requirements...........................................................................................................................................................6710.1.2 Activation (Using MML Commands).....................................................................................................................6710.1.3 MML Command Examples.....................................................................................................................................7010.1.4 Activation (Using the CME)....................................................................................................................................7010.1.5 Activation Observation............................................................................................................................................7210.1.6 Deactivation (Using MML Commands)..................................................................................................................7310.1.7 MML Command Examples.....................................................................................................................................7310.1.8 Deactivation (Using the CME)................................................................................................................................7410.2 Deployment of WRFD-01061003 HSDPA Admission Control.................................................................................7410.2.1 Requirements...........................................................................................................................................................7510.2.2 Activation (Using MML Commands).....................................................................................................................7510.2.3 MML Command Examples.....................................................................................................................................7610.2.4 Activation (Using the CME)....................................................................................................................................7610.2.5 Activation Observation............................................................................................................................................7810.2.6 Deactivation.............................................................................................................................................................7810.3 Deployment of WRFD-01061202 HSUPA Admission Control.................................................................................7810.3.1 Requirements...........................................................................................................................................................7810.3.2 Activation (Using MML Commands).....................................................................................................................7910.3.3 MML Command Examples.....................................................................................................................................8010.3.4 Activation (Using the CME)....................................................................................................................................8010.3.5 Activation Observation............................................................................................................................................8210.3.6 Deactivation.............................................................................................................................................................8211 Parameters...................................................................................................................................8312 Counters....................................................................................................................................26313 Glossary.....................................................................................................................................30214 Reference Documents.............................................................................................................303

WCDMA RANCall Admission Control Feature Parameter Description Contents


iii

1 About This Document1.1 Scope

This document describes the Call Admission Control (CAC) feature, including the basicprinciples, engineering guidelines, and parameters.This document covers the features WRFD-020101 Admission Control, WRFD-01061003HSDPA Admission Control, and WRFD-01061202 HSUPA Admission Control.

1.2 Intended AudienceThis document is intended for personnel who:l Are familiar with WCDMA basicsl 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:l Feature change: refers to a change in the CAC feature of a specific product version.l Editorial change: refers to a change in wording or the addition of information that was not

described in the earlier version.

Document Versionsl 03 (2013-09-30)l 02 (2013-06-30)l 01 (2013-04-28)l Draft A (2013-01-30)

WCDMA RANCall Admission Control Feature Parameter Description 1 About This Document


1

03 (2013-09-30)This is the third commercial release of RAN15.0.Compared with Issue 02 (2013-06-30) of RAN15.0, Issue 03 (2013-09-30) of RAN15.0 includesthe following changes.

Change Type Change Description Parameter ChangeFeature change Optimized power resource-

based admission criteria forRRC connection setuprequests. For details, seechapter 7 Cell PowerResource-based CAC.

Added theRTRRC_OTHERRRC_CONSISTENT_WITH_RAB andNRTRRC_CONSISTENT_WITH_RAB values to theNBMCacAlgoSwitch(BSC6900,BSC6910)parameter.

Editorial change None None

02 (2013-06-30)This is the second commercial release of RAN15.0.Compared with Issue 01 (2013-04-28) of RAN15.0, Issue 02 (2013-06-30) of RAN15.0 includesthe following changes.

ChangeType

Change Description ParameterChange

Featurechange

None None

Editorialchange

Added 3.3 Admission on NodeB in 3 NodeB Credit Resource-based CAC.

None

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 includesthe following changes.



2

ChangeType

Change Description ParameterChange

Featurechange

Added the impact on CAC from the DB-HSDPA, 4C-HSDPA,and Flexible Dual Carrier HSDPA features introduced inRAN15.0. For details, see 7 Cell Power Resource-basedCAC.

None

Editorialchange

l Optimized document organization and descriptions toimprove readability.

l Added descriptions of the CAC policies. For details, seesection 2.1 CAC Policy.

l Added descriptions of admission control on commonchannels. For details, see 8 Common Channel Admission.

l Added descriptions of following-up processing in case ofservice admission failures. For details, see 9 Follow-upProcessing in the Case of Admission Failures.

None



3

2 OverviewCall Admission Control (CAC) is used to determine whether system resources in a cell aresufficient to accept a service request. The service request will be rejected if the system resourcesare 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 considers the cellload 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.

WCDMA RANCall Admission Control Feature Parameter Description 2 Overview


4

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:l NodeB credit resourcesl Iub transmission resourcesl Cell code resourcesl Number of users, including HSDPA/HSUPA and E-FACH/E-RACH usersl Cell power resourcesThe RNC implements differentiated CAC based on system resources requested by users.

2.1.2 Resource RequestsThe resource requests involved in CAC are as follows:l Cell updatesl Service setup: new radio resource control (RRC) setup and radio access bearer (RAB) setupl Service change: RAB reconfiguration and service rate increase or decreasel Handovers: soft handovers, hard handovers, inter-RAT incoming handovers, and circuit

switched fallback (CSFB)l State transitions: P2D, F2D, and D2D transitions

NOTE

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

The CAC policies based on resource requests are as follows:l For service rate decrease requests, admission succeeds since some system resources are

released.l 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 isimplemented based on the system resources requested by signaling radio bearers (SRBs).In the RAB setup phase, admission is implemented based on the system resources requestedby SRBs and traffic radio bearers (TRBs) in total.

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

NOTE

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



5

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

Dedicated ChannelsGenerally, users consume more resources on dedicated channels than they do on commonchannels. Therefore, CAC focuses on service requests on DCH channels and HSPA channels,which will be described in the corresponding chapters.

Common ChannelsUsers consume relatively smaller amount of resources on common channels. Therefore, the RNCreserves some resources for certain common channels and does not implement CAC for specificrequests.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 NodeBcredit resource-based, cell code resource-based, and power resource-based admissions asfollows:l The RNC preferentially admits high-priority service requests such as emergency calls,

detachments, or registrations. For details, see sections 3.2.2 Admission Decisions on RRCConnection Setup Requests and 7.2 Admission Control Algorithm 1.

l The RNC provides differentiated admission thresholds for handovers, adaptive multirate(AMR) services, non-AMR services, and other services because these service types havedifferent QoS requirements. A special admission threshold is used for handover-relatedresource requests and differentiated admission thresholds are used for non-handover-related resource requests. For details, see the following sections: 3.2.3 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 servicerequest. If admission fails, the RNC implements relevant functions to increase the access successrate, which is described in 9 Follow-up Processing in the Case of Admission Failures.



6

Figure 2-1 Basic CAC procedure

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



7

Table 2-1 Resource-based CAC methodsSN Admission

ControlMethod

ApplicableService

Uplink/Downlink

Mandatory/OptionalDecisionCriteria

Detailed In

1 NodeB creditresource-based CAC

R99, HSDPA,and HSUPAservices

Uplinkanddownlink

OptionalIt is controlled byswitches.

3 NodeB CreditResource-basedCAC

2 Iubtransmissionresource-based CAC


Uplinkanddownlink

Mandatory 4 IubTransmissionResource-basedCAC

3 Cell coderesource-based CAC

R99 services Downlink Mandatory 5 Cell CodeResource-basedCAC

4 CAC basedon the numberof HSDPAusers

HSDPAservices

Downlink Mandatory 6 CAC Based onthe Number ofHSPA Users

CAC basedon the numberof HSUPAusers

HSUPAservices

Uplink Mandatory

5 Cell powerresource-based CAC


Uplinkanddownlink

OptionalIt is controlled byswitches.

7 Cell PowerResource-basedCAC



8

3 NodeB Credit Resource-based CACNodeB credit resource-based CAC applies to R99, HSDPA, and HSUPA services in the uplinkand downlink.

WCDMA RANCall Admission Control Feature Parameter Description 3 NodeB Credit Resource-based CAC


9

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.New services can be admitted only when there are sufficient NodeB credit resources on the RNCside and sufficient CE resources on the NodeB side.CEs are classified into uplink and downlink CEs:l An uplink 12.2 kbit/s voice service (SF = 64) plus 3.4 kbit/s signaling traffic consume one

uplink CE.l 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, see CEResource Management Feature Parameter Description.

3.2 Admission on RNCOn the RNC side, the NodeB credit resource-based CAC takes effect in a cell only when boththe NODEB_CREDIT_CAC_SWITCH check box under the CacSwitch parameter and theCRD_ADCTRL check box under the NBMCacAlgoSwitch parameter are selected.The RNC implements NodeB credit resource-based admission control based on the remainingNodeB credit resources at NodeB, LCG (if any), and LC levels. NodeB credit resource-basedadmission succeeds only when the remaining NodeB credit resources at the three levels aresufficient 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 Calculation of the Remaining NodeB Credit Resources on theRNC SideCE Capability Reporting

The amount of CEs is calculated at the NodeB level, local cell group (LCG) level (if any), andlocal cell (LC) level. The NodeB sends the RNC an AUDIT RESPONSE message to report theamount of CEs at different levels. Before reporting the amount of CEs at different levels, theNodeB considers the amount of physical and licensed CEs. Table 3-1 provides the meaning ofCEs at different levels.

NOTE

A group of local cells are configured to form an LCG. If no LCGs are configured on the NodeB, the NodeBdoes not report the amount of LCG-level CEs to the RNC.



10

Table 3-1 Meaning of CEs at different levelsCE MeaningNodeB-level CEs The NodeB-level CEs are the licensed CEs of the NodeB.LCG-level CEs In the uplink, the LCG-level CEs are the LCG-level physical CEs. In

the downlink, the LCG-level CEs are the sum of downlink CEs on allthe boards of the LCG.

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

Relationship Between NodeB Credit Resources and CEsThe relationship between NodeB credit resources and CEs is as follows:l In the uplink, the amount of NodeB credit resources is twice the amount of CEs.l In the downlink, the amount of NodeB credit resources equals the amount of CEs.

Remaining NodeB Credit Resources:The RNC calculates the amount of remaining NodeB credit resources at the NodeB, LCG, andLC levels based on the following factors:l Reported amount of NodeB-level, LCG-level, and LC-level CEsl Relationship between NodeB credit resources and CEsl CE consumption rulel Current traffic volume

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



11

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

For an RRC connection setup request, NodeB credit resource-based admission control isimplemented as follows:l When RRCCeCodeCacChoice(BSC6900,BSC6910) is set to LOOSE_CAC, NodeB

credit resource-based admission succeeds if the remaining NodeB credit resources atNodeB, LCG (if any), and LC levels are sufficient for setting up an RRC connection.

l When RRCCeCodeCacChoice(BSC6900,BSC6910) is set to STRICT_CAC, the RNCimplements NodeB credit resource-based admission control based on the cause valuecarried in the RRC connection 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 greater than thereserved credit resource plus the resource for setting up the RRC connection. Thereserved credit resource and the spreading factor (SF) have a mapping relationship,which means the reserved credit resource threshold is determined once the SF is



12

specified. The SF is specified by DlRRCCeCodeResvSf(BSC6900,BSC6910) (for thedownlink) or UlRRCCeResvSf(BSC6900,BSC6910) (for the uplink). For details aboutthe mapping relationship, see CE Resource Management Feature ParameterDescription.

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

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

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

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



13

For an AMR service request, NodeB credit resource-based admission control is implemented asfollows:l If CSRABCacOptSwitch(BSC6900,BSC6910) is set to ON, NodeB credit resource-based

admission succeeds if the remaining NodeB credit resources at NodeB, LCG (if any), andLC levels are greater than or equal to the resource requested by the AMR service. The RNCdoes not reserve extra resources for the AMR service.

l If CSRABCacOptSwitch(BSC6900,BSC6910) is set to OFF, NodeB credit resource-basedadmission succeeds if the remaining NodeB credit resources at NodeB, LCG (if any), andLC levels are greater than or equal to the reserved credit resource plus the resource requestedby the AMR service.

The reserved credit resource and the SF have a mapping relationship. The SF is specified byDlHoCeCodeResvSf(BSC6900,BSC6910) (for the downlink) or UlHoCeResvSf(BSC6900,BSC6910) (for the uplink). For details about the mapping relationship, see CEResource 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 admissionsucceeds if the remaining NodeB credit resources at NodeB, LCG (if any), and LC levels aregreater 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 byDlHoCeCodeResvSf(BSC6900,BSC6910) (for the downlink) or UlHoCeResvSf(BSC6900,BSC6910) (for the uplink).

3.3 Admission on NodeBNodeB credit resource-based CAC on the NodeB side is not switch controlled and it admits newservices at the following levels:

NodeBNew services are admitted only when the amount of CEs required by all the UEs on the NodeBis less than or equal to the amount of licensed CEs of the NodeB.

LCGNew services are admitted only when the amount of CEs required by all the UEs in an LCG isless than or equal to the amount of physical CEs of the LCG.l In the uplink, the LCG-level CEs are the smaller one between the LCG-level physical CEs

and the NodeB-level licensed CEs.l In the downlink, the LCG-level CEs are the sum of downlink CEs on all the boards of the

LCG.

LCNew services are admitted only when the amount of CEs required by all the UEs in an LC isless than or equal to the amount of physical CEs of the LC. In the uplink, the LC-level CEs are



14

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

BoardNew services are admitted only when the amount of CEs required by all the UEs on a board isless than or equal to the amount of physical CEs of the board. New services cannot be admittedat the board level when no board can accommodate the new services.



15

4 Iub Transmission Resource-based CACIub transmission resource-based CAC applies to R99, HSDPA, and HSUPA services in bothuplink and downlink.For details about Iub transmission resource-based CAC, see Transmission ResourceManagement Feature Parameter Description.

WCDMA RANCall Admission Control Feature Parameter Description 4 Iub Transmission Resource-based CAC


16

5 Cell Code Resource-based CACCell 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 beenreserved for HSDPA services. In addition, these resources can be shared by HSDPA services. For detailsabout code resource allocation for HSDPA services, see HSDPA Feature Parameter Description.

WCDMA RANCall Admission Control Feature Parameter Description 5 Cell Code Resource-based CAC


17

5.1 Admission Decisions on RRC Connection SetupRequests

Figure 5-1 shows the cell code resource-based admission control procedure for RRC connectionsetup 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 isimplemented as follows:l When RRCCeCodeCacChoice(BSC6900,BSC6910) is set to LOOSE_CAC, cell code

resource-based admission succeeds if the remaining cell code resources (the remainingminimum SF for the cell) are sufficient for setting up an RRC connection.



18

l When RRCCeCodeCacChoice(BSC6900,BSC6910) is set to STRICT_CAC, the RNCimplements code resource-based admission control based on the cause value carried in theRRC connection 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 up an RRCconnection. 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(BSC6900,BSC6910) 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.

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

AMR ServicesFigure 5-2 shows the cell code resource-based admission control procedure for AMR servicerequests.



19

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 asfollows:l If CSRABCacOptSwitch(BSC6900,BSC6910) is set to ON, cell code resource-based

admission succeeds if the remaining code resources are sufficient for the AMR service tobe admitted.

l If CSRABCacOptSwitch(BSC6900,BSC6910) is set to OFF, cell code resource-basedadmission succeeds if the remaining code resources are greater than or equal to the resourcereserved by DlHoCeCodeResvSf(BSC6900,BSC6910) plus the resource requested by theAMR service.

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



20

6 CAC Based on the Number of HSPA UsersThis section describes CAC based on the number of HSDPA and HSUPA users in a cell.

WCDMA RANCall Admission Control Feature Parameter Description 6 CAC Based on the Number of HSPA Users


21

6.1 CAC for HSDPA UsersFor HSDPA service requests such as service setup and handovers, admission based on thenumber of HSPA users succeeds when all the following conditions are met:l The number of HSDPA users in the cell is less than or equal to the threshold specified by

MaxHsdpaUserNum(BSC6900,BSC6910) once the HSDPA service is admitted.l The number of HSDPA users in the cell is less than or equal to the licensed limit once the

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

by NodeBHsdpaMaxUserNum(BSC6900,BSC6910) once the HSDPA service isadmitted.

A multi-carrier HSDPA user, such as DC-HSDPA, DB-HSDPA, and 4C-HSDPA user, iscounted 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 onthe 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 numberof HSPA users succeeds when all the following conditions are met:l The number of HSUPA users in the cell is less than or equal to the threshold specified by

MaxHsupaUserNum(BSC6900,BSC6910) once the HSUPA service is admitted.l The number of HSUPA users in the cell is less than or equal to the licensed limit once the

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

by NodeBHsupaMaxUserNum(BSC6900,BSC6910) once the HSUPA service isadmitted.

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

WCDMA RANCall Admission Control Feature Parameter Description 6 CAC Based on the Number of HSPA Users


22

7 Cell Power Resource-based CACCell power resource-based CAC applies to R99, HSDPA, and HSUPA services.l 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.1 Overview isturned on.

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

l HSUPA services (uplink data carried on HSUPA channels and downlink data carried onDCH channels): Cell power resource-based CAC is enabled whenHSUPA_UU_ADCTRL of NBMCacAlgoSwitch(BSC6900,BSC6910) is selected and thealgorithm switch in section 7.1 Overview is turned on.

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

WCDMA RANCall Admission Control Feature Parameter Description 7 Cell Power Resource-based CAC


23

7.1 OverviewCell power resource-based CAC is performed by using one of four algorithms, which are referredto 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 admissioncontrol in uplink. Table 7-1 describes these algorithms. NBMUlCacAlgoSelSwitch(BSC6900,BSC6910) and NBMDlCacAlgoSelSwitch(BSC6900,BSC6910) specify thealgorithms used in uplink and downlink, respectively. For resource requests from intra-frequency handovers, the RNC performs cell power resource-based CAC only in downlink; forresource 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 CACAlgorithm GUI Value

inNBMUlCacAlgoSelSwitch(BSC6900,BSC6910)andNBMDlCacAlgoSelSwitch(BSC6900,BSC6910)

Uplink/Downlink

Description

7.2 AdmissionControlAlgorithm 1

ALGORITHM_FIRST

Uplinkanddownlink

In algorithm 1, admission control is based on thecell power load and the expected power loadincrease caused by a new service.If the RNC determines that the expected powerload will exceed the preset threshold once thenew service is admitted, the RNC rejects theservice request. Otherwise, the RNC admits theservice.


ALGORITHM_SECOND

Uplinkanddownlink

In algorithm 2, admission control is based on theequivalent number of users (ENU) and theexpected power load increase caused by a newservice.If the RNC determines that the expected ENUwill exceed the preset threshold once the newservice is admitted, the RNC rejects the servicerequest. Otherwise, the RNC admits the service.



24

Algorithm GUI ValueinNBMUlCacAlgoSelSwitch(BSC6900,BSC6910)andNBMDlCacAlgoSelSwitch(BSC6900,BSC6910)

Uplink/Downlink

Description


ALGORITHM_THIRD

Uplinkanddownlink

In algorithm 3, the RNC performs admissioncontrol without considering the power loadincrease caused by a new service.Algorithm 3 is similar to algorithm 1. The onlydifference is that algorithm 3 assumes that theexpected power load increase caused by the newservice is 0.The RNC determines whether the current cellpower 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 theactual uplink service load and the expectedservice load increase caused by a new service.Depending on the actual uplink service load inthe cell, the RNC determines whether the actualuplink service load will exceed the presetthreshold once the new service is admitted. Ifyes, the RNC 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 powerload increase caused by a new service. The measurement quantities relevant to the cell powerload are processed and reported by the load measurement module on the RNC. For details aboutcell 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 (R99cells, SC-HSUPA cells, or DC-HSUPA cells). The load measurement module of the RNC



25

calculates the uplink power load factor based on received total wideband power(RTULOLCTRIGTHDWP).

Calculation of Uplink Power Load for a CellThe 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 usingthe following formula:UL,R99-Total = 1 PN/RTWP + UL,CCHWhere,l PN is the uplink background noise and the unit is mw. PN is set by BackgroundNoise

(BSC6900,BSC6910) and the unit of the parameter is dBm. The relationship between dBmand mw is 1dBm=10*log(1mw). If the auto-adaptive background noise update algorithmis enabled, PN is updated in real time. For details about the auto-adaptive background noiseupdate algorithm, see Load Control Feature Parameter Description.

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

l UL,CCH is the reserved load factor on the uplink common channels, which is set byUlCCHLoadFactor(BSC6900,BSC6910).

For an SC-HSUPA CellIn an SC-HSUPA cell, algorithm 1 uses the following three types of uplink power load factor:l RTWP-based uplink power load factor

For an SC-HSUPA cell, it is represented by UL,HSUPA-Total and calculated using thefollowing 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(BSC6900,BSC6910). The other variables are defined the same way as for UL,R99-Total in an R99 cell.

l Uncontrollable uplink load factorThe uncontrollable uplink load factor is the load factor for the receive power of a cellexcluding 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 all scheduled usersto RTWP in the current cell. RSEPS is measured by the NodeB and periodically reportedto the RNC.



26

NOTE

The algorithm for calculating UL,NonCtrl depends on the periodic RSEPS measurement according to theabove formula. If NBMUlCacAlgoSelSwitch(BSC6900,BSC6910) is set to ALGORITHM_FIRST orALGORITHM_THIRD and HSUPA_EDCH_RSEPS_MEAS of NBMCacAlgoSwitch(BSC6900,BSC6910) is set to 0, the RNC performs admission control for the cell using algorithm 2. Fordetails about algorithm 2, see 7.3 Admission Control Algorithm 2.

l Total uplink load factor for preferential admission of R99 servicesIt is represented by UL,R99Prefer-Total.When the guaranteed bit rate (GBR) for HSUPA services is too high, the RTWP-baseduplink power load may also be too high, and therefore R99 service admission is difficult.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 theRNC makes an admission decision on an R99 service. It is set by HsupaMaxGBPThd(BSC6900,BSC6910).

For a DC-HSUPA CellIn a DC-HSUPA cell group, the uplink power load factor is calculated on the primary andsecondary 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-HSUPAservices.

Uplink Admission Decisions Based on Algorithm 1Figure 7-1 shows the procedure for an uplink admission decision based on algorithm 1.



27

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

This procedure is implemented as follows:Step 1 The RNC calculates the uplink power load for the cell based on the result from the load

measurement module.Step 2 The RNC calculates the uplink power load increase (UL) based on the initial admission rate

of the new service.NOTE

l For details about the initial admission rate, see Load Control Feature Parameter Description.l 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 the RRC connection setup request. The SRB rate ofan RRC connection setup request is set by running the SET URRCESTCAUSE command.

Step 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



28

criteria are met, uplink admission based on algorithm 1 succeeds. Otherwise, the RNC performsthe next step.

Table 7-2 Uplink admission criteria in algorithm 1Resource RequestType

Cell Type Bearer Type Admission CriteriaDescribed In

RRC connectionsetup requests

R99 cellHSUPAcell

N/A Admission Criteria for RRCConnection Setup Requests

Other resourcerequests (such asRAB setup, RABreconfiguration,handover, and cellupdate)

R99 cell DCH RAB Admission Criteria for OtherResource Requests in an R99Cell

SC-HSUPAcell

DCH RAB Admission Criteria for OtherResource Requests in an SC-HSUPA Cell (for the DCHRAB)

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

DC-HSUPAcell

DCH RAB, SC-HSUPA RAB, andDC-HSUPA RAB

Admission Criteria for OtherResource Requests in a DC-HSUPA Cell

Step 4 If the RTWP anti-interference function switch is turned on (RTWP_RESIST_DISTURB of

NBMCacAlgoSwitch(BSC6900,BSC6910) is selected), the RNC checks whether the totaluplink load of ENU on the cell is less than CellUlEquNumCapacity(BSC6900,BSC6910).l If yes, uplink admission based on algorithm 1 succeeds.l Otherwise, uplink admission based on algorithm 1 fails.----End

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 RequestsIn algorithm 1, the uplink admission criteria for RRC connection setup requests are describedin the following table.



29

Cell Type Bearer Type forRRC SRBs

Uplink AdmissionCriterion

Admission Result

R99 cell SRB Over DCH UL,R99-Total + UL ThdUL,RRC

Uplink admission basedon algorithm 1 succeeds ifthe criterion is met.

HSUPA cell SRB Over DCH Criterion 1(uncontrollable uplinkload factor-basedadmission criterion):UL,NonCtrl + UL ThdUL,RRCCriterion 2 (total cellpower-based admissioncriterion):l UL,HSUPA-Total +

UL ThdUL,RRC-Total

l UL,R99Prefer-Total +UL ThdUL,RRC-Total

Criterion 2 is met if eitherof the precedinginequalities is satisfied.

Uplink admission basedon algorithm 1 succeeds ifboth criteria 1 and 2 aremet.

SRB Over HSUPA Criterion 1(uncontrollable uplinkload factor-basedadmission criterion):UL,NonCtrl + UL ThdUL,RRCCriterion 2 (total cellpower-based admissioncriterion):UL,HSUPA-Total + UL

ThdUL,RRC-Total

Uplink admission basedon algorithm 1 succeeds ifboth criteria 1 and 2 aremet.

ThdUL,RRC indicates the uplink admission threshold for RRC connection setup requests, andThdUL,RRC-Total indicates the uplink total cell power-based admission threshold for RRCconnection setup requests. These thresholds use the same values in algorithms 1, 2, 3, and 4.The RNC performs either loose or strict admission control on RRC connection setup requestsaccording to the value of RRCCacChoice(BSC6900,BSC6910):l If RRCCacChoice(BSC6900,BSC6910) is set to LOOSE_CAC, the RNC uses the loose

admission thresholds listed in Table 7-3.



30

l If RRCCacChoice(BSC6900,BSC6910) is set to STRICT_CAC, the RNC uses the strictadmission thresholds listed in Table 7-4 .

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

Uplink Admission Threshold(ThdUL,RRC)

Uplink Total Cell Power-basedAdmission Threshold(ThdUL,RRC-Total)

l Emergency call

l Detachment

l Registration

This threshold does not apply becausethe RNC accepts the RRC connectionsetup request without admissioncontrol.

This threshold does not applybecause the RNC accepts the RRCconnection setup request withoutadmission control.

Other services l When UL_UU_OLC ofNBMLdcAlgoSwitch(BSC6900,BSC6910) is set to 1:If the cell is overloaded, the RNCrejects the RRC connection setuprequest.If the cell is notoverloaded, the uplink OLCtriggering threshold(UlOlcTrigThd) is used asThdUL,RRC.

l When UL_UU_OLC ofNBMLdcAlgoSwitch(BSC6900,BSC6910) is set to 0,the uplink OLC triggeringthreshold UlOlcTrigThd(BSC6900,BSC6910) is used asThdUL,RRC.

l SRB Over DCHWhen the UL_UU_OLC checkbox under theNBMLdcAlgoSwitch(BSC6900,BSC6910)parameter is selected:If the cellis overloaded, the RNC rejectsthe RRC connection setuprequest. If the cell is notoverloaded, the uplink OLCtriggering threshold(UlOlcTrigThd(BSC6900,BSC6910)) is usedas ThdUL,RRC-Total.Whenthe UL_UU_OLC check boxunder the NBMLdcAlgoSwitchparameter is not selected, theuplink OLC triggeringthreshold (UlOlcTrigThd(BSC6900,BSC6910)) is usedas ThdUL,RRC-Total.

l SRB Over HSUPAThis threshold does not applybecause the RNC accepts the RRCconnection setup request withoutadmission control.

NOTE

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



31

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


Uplink Total Cell Power-basedAdmission Threshold (ThdUL,RRC-Total)

l Emergency call

l Detachment



Real-timeservices

UlNonCtrlThdForAMR(BSC6900,BSC6910) +RTRRCCacThdOffset(BSC6900,BSC6910) (admissionthreshold offset for the RRCconnection setup request of a real-time service)

l When theRTRRC_OTHERRRC_CONSISTENT_WITH_RAB check boxunder the NBMCacAlgoSwitch(BSC6900,BSC6910) parameter isnot selected:

ThdUL,RRC-Total = UlNonCtrlThdFor-AMR(BSC6900,BSC6910) +RTRRCCacThdOffset(BSC6900,BSC6910) (admissionthreshold offset for the RRC connectionsetup request of a real-time service)l When the

RTRRC_OTHERRRC_CONSISTENT_WITH_RAB check boxunder the NBMCacAlgoSwitch(BSC6900,BSC6910) parameter isselected:

ThdUL,RRC-Total = UlCellTotalThd(BSC6900,BSC6910) +RTRRCCacThdOffset(BSC6900,BSC6910) (admissionthreshold offset for the RRC connectionsetup request of a real-time service)



32

Cause ofRRCConnectionSetupRequest



Non-real-timeservices

UlNonCtrlThdForOther(BSC6900,BSC6910) +NRTRRCCacThdOffset(BSC6900,BSC6910) (admissionthreshold offset for the RRCconnection setup request of a non-real-time service)

l When theNRTRRC_CONSISTENT_WITH_RAB check box under theNBMCacAlgoSwitch(BSC6900,BSC6910) parameter isnot selected:

ThdUL,RRC-Total = UlNonCtrlThdFor-Other(BSC6900,BSC6910) +NRTRRCCacThdOffset(BSC6900,BSC6910) (admissionthreshold offset for the RRC connectionsetup request of a non-real-timeservice)l When the

NRTRRC_CONSISTENT_WITH_RAB check box under theNBMCacAlgoSwitch(BSC6900,BSC6910) parameter isselected:

ThdUL,RRC-Total = UlCellTotalThd(BSC6900,BSC6910) +NRTRRCCacThdOffset(BSC6900,BSC6910) (admissionthreshold offset for the RRC connectionsetup request of a non-real-timeservice)



33

Cause ofRRCConnectionSetupRequest



Other services UlOlcTrigThd(BSC6900,BSC6910) +OtherRRCCacThdOffset(BSC6900,BSC6910) (admissionthreshold offset for the RRCconnection setup request ofULOLCTRIGTHD the otherservice)

l When theRTRRC_OTHERRRC_CONSISTENT_WITH_RAB check boxunder the NBMCacAlgoSwitch(BSC6900,BSC6910) parameter isnot selected:

ThdUL,RRC-Total = UlOlcTrigThd(BSC6900,BSC6910) +OtherRRCCacThdOffset(BSC6900,BSC6910) (admissionthreshold offset for the RRC connectionsetup request of a service other than areal-time or non-real-time service)l When the

RTRRC_OTHERRRC_CONSISTENT_WITH_RAB check boxunder the NBMCacAlgoSwitch(BSC6900,BSC6910) parameter isselected:

ThdUL,RRC-Total = UlCellTotalThd(BSC6900,BSC6910) +OtherRRCCacThdOffset(BSC6900,BSC6910) (admissionthreshold offset for the RRC connectionsetup request of a service other than areal-time or non-real-time service)

NOTE

To ensure that admission control over RRC connection setup requests is as strict as or stricter than admissioncontrol over RAB setup requests, you can select theRTRRC_OTHERRRC_CONSISTENT_WITH_RAB check box under the NBMCacAlgoSwitch(BSC6900,BSC6910) parameter and the NRTRRC_CONSISTENT_WITH_RAB check box under theNBMCacAlgoSwitch(BSC6900,BSC6910) parameter.After these check boxes are selected:l The traffic volume is controlled at the RRC connection setup procedure.l A RAB setup request may be admitted if an RRC connection setup request has been admitted. This

minimizes the possibility that radio resources used for admission control over RRC connection setuprequests are wasted.

l The RAB setup success rate increases.



34

Admission Criteria for Other Resource Requests in an R99 CellWhen algorithm 1 is used for an R99 cell, the uplink admission criteria for resource requestsother than RRC connection setup requests are as follows:

Step 1 If UL_UU_OLC of NBMLdcAlgoSwitch(BSC6900,BSC6910) is selected and the cell isoverloaded, service admission fails. If UL_UU_OLC of NBMLdcAlgoSwitch(BSC6900,BSC6910) is deselected or the cell is not overloaded, the RNC performs the nextstep.

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

----EndThdUL,Nonctl is the admission threshold for the uplink power load of non-HSPA services. Thethreshold 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 servicesResourceRequest Type

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

AMR services l If CSRABCacOptSwitch(BSC6900,BSC6910) is set to OFF,UlNonCtrlThdForAMR(BSC6900,BSC6910) is used asThdUL,Nonctl.

l If CSRABCacOptSwitch(BSC6900,BSC6910) is set to ON:When the OLC algorithm is enabled (UL_UU_OLC ofNBMLdcAlgoSwitch is selected), the uplink OLC triggeringthreshold (UlOlcTrigThd) is used as ThdUL,Nonctl.When the OLCalgorithm is disabled (UL_UU_OLC of NBMLdcAlgoSwitch isdeselected), ThdUL,Nonctl is 100%.

Non-AMR services UlNonCtrlThdForNonAMR(BSC6900,BSC6910)Handovers UlNonCtrlThdForHo(BSC6900,BSC6910)Other services UlNonCtrlThdForOther(BSC6900,BSC6910)

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

In an SC-HSUPA cell, if the bearer type is the DCH RAB, uplink admission based on algorithm1 succeeds when both the following criteria are met:l (UL,NonCtrl + UL) ThdUL,Nonctl

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

l Either of the two inequations applies: (UL,HSUPA-Total + UL) ThdUL,total or(UL,R99Prefer-Total + UL) ThdUL,total



35

ThdUL,total is the admission threshold for the total uplink power of the cell. See Table 7-6for details.

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

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

AMR services l If CSRABCacOptSwitch(BSC6900,BSC6910) is set to OFF,UlCellTotalThd(BSC6900,BSC6910) is used as ThdUL,total.

l If CSRABCacOptSwitch(BSC6900,BSC6910) is set to ON:When the OLC algorithm is enabled (UL_UU_OLC ofNBMLdcAlgoSwitch is selected), the uplink OLC triggering threshold(UlOlcTrigThd) is used as ThdUL,total.When the OLC algorithm isdisabled (UL_UU_OLC of NBMLdcAlgoSwitch is deselected),ThdUL,total is 100%.

Other services UlCellTotalThd(BSC6900,BSC6910)

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 onalgorithm 1 succeeds when either PBR-based admission or load-based admission succeeds.The RNC admits the IP multimedia subsystem (IMS) signaling services carried on HSUPARABs directly.PBR-based Admission DecisionsThe RNC performs PBR-based admission control only when the HSUPA PBR measurementswitch is turned on (HSUPA_PBR_MEAS of NBMCacAlgoSwitch(BSC6900,BSC6910) is setto 1).The uplink provided bit rate (PBR) is the effective uplink throughput on all users correspondingto a scheduling priority indicator (SPI) successfully received by the NodeB. PBR is periodicallyreported 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 certainfactor, the RNC determines that the QoS requirements of the cell are met. In this case, the RNCcan admit new users. PBR-based admission succeeds if any of the criteria described in Table7-7 is met.



36

Table 7-7 PBR-based admission criteriaSN User Range Admission

CriteriaParameterDescription

1 All HSUPA userswhose schedulingpriorities are lowerthan the priority ofthe user beingadmitted

ThdL isHsupaLowPriori-tyUserPBRThd(BSC6900,BSC6910)

2 All HSUPA userswhose schedulingpriorities equal thepriority of the userbeing admitted

ThdE isHsupaEqualPriori-tyUserPBRThd(BSC6900,BSC6910)

3 All HSUPA userswhose schedulingpriorities are higherthan the priority ofthe user to beadmitted

ThdGE isHsupaHighPriori-tyUserPBRThd(BSC6900,BSC6910)

Load-based Admission Decisionsl For HSUPA scheduling services, load-based admission succeeds if the following formula

is satisfied:UL,HSUPA-Total + UL UlCellTotalThd(BSC6900,BSC6910)Otherwise, load-based admission fails.

l For HSUPA non-scheduling services, load-based admission succeeds only when both thefollowing criteria are met: (UL,HSUPA-Total + UL) UlCellTotalThd(BSC6900,BSC6910)

(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 CellIn a DC-HSUPA cell, if the bearer type is the DCH RAB or SC-HSUPA RAB, uplink admissiondecisions based on algorithm 1 are the same as those in an SC-HSUPA cell. For details, seeAdmission Criteria for Other Resource Requests in an SC-HSUPA Cell (for the DCHRAB) and Admission Criteria for Other Resource Requests in an SC-HSUPA Cell (for theSC-HSUPA RAB).In a DC-HSUPA cell, if the bearer type is the DC-HSUPA RAB, the RNC performs load-basedadmission control.



37

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

l For DC-HSUPA scheduling servicesThe RNC makes load-based admission decisions on the primary or secondary cell. Uplinkadmission based on algorithm 1 succeeds if load-based admission succeeds on either theprimary 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 CellThe following describes how to calculate the downlink power load for an R99 cell, SC-HSDPAcell, and multi-carrier HSDPA cell.For an R99 CellIn an R99 cell, the RNC makes downlink admission decisions according to the TCP-based totaldownlink load, which is calculated in real time by the load measurement module of the RNC.For an R99 cell, the TCP-based total downlink load factor is represented by DL,R99-Total andcalculated using the following formula:DL,R99-Total = TCP + DL,CCHWhere,l 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(BSC6900,BSC6910).

l DL,CCH is the load factor reserved for the downlink common channels. It is set byDlCCHLoadRsrvCoeff(BSC6900,BSC6910).

For an SC-HSDPA CellIn an SC-HSDPA cell, algorithm 1 uses the following downlink power load factors:l TCP-based total downlink load factor

For an SC-HSDPA cell, it is represented by DL,HSDPA-Total and calculated using thefollowing 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(BSC6900,BSC6910). The other variables are defined the same way as for an R99 cell.



38

l Downlink non-HSPA power load factorIt is represented by DL,NonHSPA. DL,NonHSPA is the ratio of the total transmitted power forthe codes not used in HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH, and E-HICH channelson one downlink carrier to the maximum transmission power MaxTxPower(BSC6900,BSC6910).DL,NonHSPA is measured by the NodeB and periodically reported to the RNC.

l HSDPA GBP load factorIt is represented by DL,GBP. Guaranteed Bit rate Power (GBP) is the power required toreach the GBR of HSDPA users in a cell.DL,GBP is calculated based on the GBR of HSDPA users in a cell. The NodeB periodicallyreports DL,GBP to the RNC.

l HSDPA GBP-based total downlink load factorIt 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 calculatedbased on HspaPower(BSC6900,BSC6910) using the formula DL,MaxHSPA = 1 10(-HspaPower/10).

l Total downlink load factor for preferential admission of R99 servicesIt is represented by DL,R99Prefer-Total. When the GBR for HSDPA services is too high, theHSDPA GBP-based total downlink load factor may also be too high, and therefore R99service admission is difficult. In this case, DL,R99Prefer-Total ensures that R99 services arepreferentially 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 thecell when the RNC makes an admission decision on an R99 service. It is set byHsdpaMaxGBPThd(BSC6900,BSC6910).

For a Multi-carrier HSDPA CellA multi-carrier HSDPA cell can be a DC-HSDPA, DB-HSDPA, or 4C-HSDPA cell. It providesmulti-carrier HSDPA services for users. With the Flexible Dual Carrier 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.l For a DC-HSDPA cell with the Flexible Dual Carrier HSDPA feature disabled

The RNC needs to perform admission control based on single cell level and the DC-HSDPAcell group level. Therefore, the downlink HSDPA GBP loads for the primary and secondarycells and the DC-HSDPA cell group are calculated.For a single cell, the HSDPA GBP load includes the downlink non-HSPA power load andHSDPA GBP load for SC-HSDPA users in the cell.For a DC-HSDPA cell group, the HSDPA GBP power load includes the following partsshown in Figure 7-2:



39

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 Dual Carrier HSDPAfeature disabled

l For a DC-HSDPA cell with the Flexible Dual Carrier HSDPA feature enabled or a DB-HSDPA/4C-HSDPA cellThe RNC calculates the total HSDPA GBP factor on the primary cell and the secondarycell.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 usedfor each DC-HSUPA/DB-HSDPA/4C-HSDPA user is calculated and then apportionedon each carrier of the cell group based on the transmit power ratio per carrier.



40

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

Downlink Admission Decisions Based on Algorithm 1Figure 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:



41

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

2. The RNC calculates the downlink power load increase (DL) based on the initial admissionrate 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 basedon the SRB rate carried in the RRC connection setup request. The SRB rate of an RRC connectionsetup request is set by running the SET URRCESTCAUSE command.

3. The RNC makes an admission decision.In algorithm 1, downlink admission criteria vary with the resource request type, cell type, andbearer type. See Table 7-8 for details. If the admission criteria are met, downlink admissionbased on algorithm 1 succeeds. Otherwise, downlink admission based on algorithm 1 fails.

Table 7-8 Downlink admission criteria in algorithm 1Resource RequestType

Cell Type Bearer Type Admission CriteriaDescribed In

RRC connectionsetup requests

R99 cellsHSDPA cells

N/A Admission Criteria forRRC Connection SetupRequests

Other resourcerequests (such asRAB setup, RABreconfiguration,handover, and cellupdate)

R99 cells DCH RAB Admission Criteria forOther Resource Requestsin an R99 Cell

SC-HSDPA cells DCH RAB Admission Criteria forOther Resource Requestsin an SC-HSDPA Cell (forthe DCH RAB)

SC-HSDPA RAB Admission Criteria forOther Resource Requestsin an SC-HSDPA Cell (forthe SC-HSDPA RAB)

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

Admission Criteria forOther Resource Requestsin a DC-HSDPA Cell

DB-HSDPA cells4C-HSDPA cells

DCH RABSC-HSDPA RABDB-HSDPA RAB4C-HSDPA RAB

Admission Criteria forOther Resource Requestsin a DB-HSDPA or 4C-HSDPA Cell



42

Admission Criteria for RRC Connection Setup RequestsIn algorithm 1, the downlink admission criteria for RRC connection setup requests are describedin the following table:


Downlink AdmissionCriterion

Admission Result

R99 cell SRB Over DCH DL,R99-Total + DL ThdDL,RRC

Downlink admissionbased on algorithm 1succeeds if the criterion ismet.

HSDPA cell SRB Over DCH Criterion 1 (non-HSPApower-based admissioncriterion):DL,NonHSPA + DL ThdDL,RRCCriterion 2 (total cellpower-based admissioncriterion):l DL,HSDPA-Total +

DL ThdDL,RRC-Total

l DL,GBP-Total + DL ThdDL,RRC-Total

l DL,R99Prefer-Total +DL ThdDL,RRC-Total

Criterion 2 is met if any ofthe preceding inequalitiesis satisfied.

Downlink admissionbased on algorithm 1succeeds if both criteria 1and 2 are met.



43


Downlink AdmissionCriterion

Admission Result

SRB Over HSDPA Criterion 1 (GBP-basedadmission criterion):DL,GBP + DL DL,MaxHSPACriterion 2 (total cellpower-based admissioncriterion):l DL,HSDPA-Total +

DL ThdDL,RRC-Total

l DL,GBP-Total + DL ThdDL,RRC-Total

Criterion 2 is met if eitherof the precedinginequalities is satisfied.

Downlink admissionbased on algorithm 1succeeds if both criteria 1and 2 are met.

ThdDL,RRC indicates the downlink admission threshold for RRC connection setup requests, andThdDL,RRC-Total indicates the downlink total cell power-based admission threshold for RRCconnection setup requests. These thresholds use the same values in algorithms 1, 2, and 3. TheRNC performs either loose or strict admission control on RRC connection setup requestsaccording to the value of RRCCacChoice(BSC6900,BSC6910):l If RRCCacChoice(BSC6900,BSC6910) is set to LOOSE_CAC, the RNC uses the loose

admission thresholds listed in Table 7-9.l If RRCCacChoice(BSC6900,BSC6910) 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 requestsCause of RRCConnection SetupRequest

Downlink AdmissionThreshold (ThdDL,RRC)

Downlink Total CellPower-based AdmissionThreshold (ThdDL,RRC-Total)

l Emergency calll Detachmentl Registration


This threshold does not applybecause the RNC accepts theRRC connection setuprequest without admissioncontrol.



44

Cause of RRCConnection SetupRequest


Downlink Total CellPower-based AdmissionThreshold (ThdDL,RRC-Total)

Other services l When DL_UU_OLC ofNBMLdcAlgoSwitch(BSC6900,BSC6910) is set to 1:If the cell is overloaded, the RNCrejects the RRC connection setuprequest.If the cell is notoverloaded, the downlink OLCtriggering threshold(DlOlcTrigThd) is used asThdDL,RRC.

l When DL_UU_OLC ofNBMLdcAlgoSwitch(BSC6900,BSC6910) is set to 0,the downlink OLC triggeringthreshold DlOlcTrigThd(BSC6900,BSC6910) is used asThdDL,RRC.

l SRB Over DCHWhen the DL_UU_OLCcheck box under theNBMLdcAlgoSwitch(BSC6900,BSC6910)parameter is selected:Ifthe cell is overloaded, theRNC rejects the RRCconnection setup request.If the cell is notoverloaded, the downlinkOLC triggering threshold(DlOlcTrigThd(BSC6900,BSC6910)) isused as ThdDL,RRC-Total.When theDL_UU_OLC check boxunder theNBMLdcAlgoSwitch(BSC6900,BSC6910)parameter is not selected,the downlink OLCtriggering threshold(DlOlcTrigThd(BSC6900,BSC6910)) isused as ThdDL,RRC-Total.

l SRB Over HSDPAThis threshold does notapply because the RNCaccepts the RRCconnection setup requestwithout admissioncontrol.

NOTE

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



45

Table 7-10 Strict downlink admission threshold for RRC connection setup requestsCause of RRCConnectionSetup Request


Downlink Total Cell Power-based Admission Threshold(ThdDL,RRC-Total)

l Emergency calll Detachment

This threshold does not applybecause the RNC accepts theRRC connection setup requestwithout admission control.


Real-time services DlConvAMRThd(BSC6900,BSC6910) +RTRRCCacThdOffset(BSC6900,BSC6910)(admission threshold offsetfor the RRC connection setuprequest of a real-time service)

l When theRTRRC_OTHERRRC_CONSISTENT_WITH_RAB checkbox under theNBMCacAlgoSwitch(BSC6900,BSC6910) parameteris not selected:ThdDL,RRC-Total =DlConvAMRThd(BSC6900,BSC6910) +RTRRCCacThdOffset(BSC6900,BSC6910) (admissionthreshold offset for the RRCconnection setup request of a real-time service)

l When theRTRRC_OTHERRRC_CONSISTENT_WITH_RAB checkbox under theNBMCacAlgoSwitch(BSC6900,BSC6910) parameteris selected:ThdDL,RRC-Total =DlCellTotalThd(BSC6910,BSC6900)+RTRRCCacThdOffset(BSC6900,BSC6910)(admissionthreshold offset for the RRCconnection setup request of a real-time service)



46

Cause of RRCConnectionSetup Request



Non-real-timeservices

DlOtherThd(BSC6900,BSC6910) +NRTRRCCacThdOffset(BSC6900,BSC6910)(admission threshold offsetfor the RRC connection setuprequest of a non-real-timeservice)

l When theNRTRRC_CONSISTENT_WITH_RAB check box under theNBMCacAlgoSwitch(BSC6900,BSC6910) parameteris not selected:ThdDL,RRC-Total = DlOtherThd(BSC6900,BSC6910) +NRTRRCCacThdOffset(BSC6900,BSC6910) (admissionthreshold offset for the RRCconnection setup request of a non-real-time service)

l When theNRTRRC_CONSISTENT_WITH_RAB check box under theNBMCacAlgoSwitch(BSC6900,BSC6910) parameteris selected:ThdDL,RRC-Total =DlCellTotalThd(BSC6910,BSC6900) +DlCellTotalThd(BSC6910,BSC6900) (admissionthreshold offset for the RRCconnection setup request of a non-real-time service)



47

Cause of RRCConnectionSetup Request



Other services DlOlcTrigThd(BSC6900,BSC6910) +OtherRRCCacThdOffset(BSC6900,BSC6910)(admission threshold offsetfor the RRC connection setuprequest of a service other thana real-time or non-real-timeservice))

l When theRTRRC_OTHERRRC_CONSISTENT_WITH_RAB checkbox under theNBMCacAlgoSwitch(BSC6900,BSC6910) parameteris not selected:ThdDL,RRC-Total = DlOlcTrigThd(BSC6900,BSC6910) +OtherRRCCacThdOffset(BSC6900,BSC6910) (admissionthreshold offset for the RRCconnection setup request of aservice other than a real-time ornon-real-time service)

l When theRTRRC_OTHERRRC_CONSISTENT_WITH_RAB checkbox under theNBMCacAlgoSwitch(BSC6900,BSC6910) parameteris selected:ThdDL,RRC-Total =DlCellTotalThd(BSC6900,BSC6910) +OtherRRCCacThdOffset(BSC6900,BSC6910) (admissionthreshold offset for the RRCconnection setup request of aservice other than a real-time ornon-real-time service)

Admission Criteria for Other Resource Requests in an R99 CellWhen algorithm 1 is used for an R99 cell, the downlink admission criteria for resource requestsother than RRC connection setup requests are as follows:

Step 1 If DL_UU_OLC of NBMLdcAlgoSwitch(BSC6900,BSC6910) is selected and the cell isoverloaded, admission fails. If DL_UU_OLC of NBMLdcAlgoSwitch(BSC6900,BSC6910) isdeselected or the cell is not overloaded, the RNC performs the next step.

Step 2 The RNC checks whether the sum of DL,R99-Total and DL is less than or equal toThdDL,Nonctl. If yes, admission succeeds. Otherwise, admission fails.

----End



48

ThdDL,Nonctl is the admission threshold for the downlink power load of non-HSPA services. Thethreshold varies with resource request types, as described in Table 7-11.

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

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

AMR services l If CSRABCacOptSwitch(BSC6900,BSC6910) is set to OFF,DlConvAMRThd(BSC6900,BSC6910) is used as ThdDL,Nonctl.

l If CSRABCacOptSwitch(BSC6900,BSC6910) is set to ON:When the OLC algorithm is enabled (DL_UU_OLC ofNBMLdcAlgoSwitch is selected), the downlink OLC triggeringthreshold (DlOlcTrigThd) is used as ThdDL,Nonctl.When theOLC algorithm is disabled (DL_UU_OLC ofNBMLdcAlgoSwitch is deselected), ThdDL,Nonctl is 100%.

Non-AMR services DlConvNonAMRThd(BSC6900,BSC6910)Handovers DlHOThd(BSC6900,BSC6910)Others DlOtherThd(BSC6900,BSC6910)

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

In an SC-HSDPA cell, if the bearer type is the DCH RAB, downlink admission based onalgorithm 1 succeeds when both the following criteria are met:l Non-HSPA power-based admission criterion: (DL,NonHSPA + DL) ThdDL,Nonctl

ThdDL,Nonctl is the admission threshold for the downlink power load of non-HSPA services.See Table 7-12 for details.

l 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 Table7-12.



49

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

Admission Threshold for the Total Downlink Power of theCell (ThdDL,total)

AMR services l If CSRABCacOptSwitch(BSC6900,BSC6910) is set to OFF,DlCellTotalThd(BSC6900,BSC6910) is used as ThdDL,total.

l If CSRABCacOptSwitch(BSC6900,BSC6910) is set to ON:When the OLC algorithm is enabled (DL_UU_OLC ofNBMLdcAlgoSwitch is selected), DlOlcTrigThd is used asThdDL,total.When the OLC algorithm is disabled (DL_UU_OLCof NBMLdcAlgoSwitch is deselected), ThdDL,total is 100%.

Other services DlCellTotalThd(BSC6900,BSC6910)

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 onalgorithm 1 succeeds when either PBR-based admission or load-based admission succeeds.PBR-based Admission DecisionsThe RNC performs PBR-based admission control only when the HSDPA PBR measurementswitch is turned on (HSDPA_PBR_MEAS of NBMCacAlgoSwitch(BSC6900,BSC6910) is setto 1).The downlink PBR is the effective dow