UMTS&HSPA RRM Algorithms and Parameters Training (Part1)

UMTS/HSPA RRM Algorithms
and parameters
Technical Training
Part- I
Table of Contents
1 Overview of Radio Resource Management (RRM)
2 Idle Mode Procedures and Parameters
3 Random Access & Paging Procedures and Parameters
4 Power Control Algorithm and Parameters
5 Admission Control Algorithm and Parameters
6 Load Control Algorithm and Parameters
7 Channel Switching Algorithm and Parameters
8 Handover Algorithm and Parameters
9 HSDPA RRM Algorithm and Parameters
10 HSUPA RRM Algorithm and Parameters

Page 2
Radio Resource Management-RRM
Radio Resource Management (RRM) is responsible for efficient utilization of the radio resources (air interface).
Ensure planned coverage for each targeted services.

Ensure required link quality (BLER, BER ,delay).
Ensure planned capacity i.e. low blocking ( new calls , handovers).
Ensure the QOS (Quality of Service) i.e. Guarantee Bit Rate (GBR), Maximum Bit Rate(MBR).
Optimize the use of available capacity (priorities).
One task of the RRM is to guard that the system is not overload and remains stable, and if the system is overload the RRM
must return the system quickly and in controllable manual back to the normal load state which is defined by the
radio network planning parameters.
Since the main criteria in WCDMA system for the radio resources is the interference, the load control functionality is done through
measuring both uplink and downlink interference periodically under one RNC, these measurements are performed on cell basis.
Page 3
Admission Control (AC) :

Performs the admission control for new bearers to enter the network.
Predicts the interference caused by the bearer and checks whether
there is room for it.
Power allocation
Packet Scheduler (PS) :

Scheduling packets to the radio interface (UL/DL).
Load Control (LC):

Takes care of radio network stability.
Gathers interference information and produces a load control.
Resource Manager (RM) :

Manage the physical resources of RAN and maintains the code allocation.
Power Control (PC) :

Closed loop PC
Open loop PC
Outer loop PC
Handover Control (HC) :

Intra-frequency handovers: softer between cells within one BS, intra-RNC
soft handover, inter-RNC soft handover.
Inter-frequency (hard) handovers: Intra-BS, Intra-RNC, Inter-RNC (-MSC).
Inter-RAT handovers: WCDMA <-> GSM.
Page 4
Table of Contents
3 Random Access &Paging Procedures and Parameters

Page 6
Idle Mode Procedures and Parameters
Four different reasons for camping on a cell in the Idle mode were identified in the specifications:
UE is capable to read the system information, which is broadcasted on the BCCH (P-CCPCH).
Hereby, the UE gains also information of the serving PLMN.
If the access to the current cell is not barred, then the UE can use the cell to initiate an RRC (signalling) connection.
The access network is accessed by common control channels (PRACH) to access the network. Initial access is done to register the UE at
the network. Other reasons for accessing the network is to request transmission resources for user data transfer.
If the UE is registered, and there is a mobile terminated call, the serving core network elements know (in most cases) the location area
and routing area, in which the UE is camping. Paging is done with the common control channel PCH (on one of the S-CCPCHs).
The UE receives the paging message, because it monitors all paging occasions on the paging resources of its paging class within the cell.
The UE can receive cell broadcast service (CBS) messages.
The idle mode tasks are divided into the following 3 processes:
PLMN Selection
Cell Selection & Reselection
Location and Routing Areas Registration
The relationship between these 3 processes is shown in the figure.
Page 7
Idle Mode Procedures and Parameters
Camping on a cell is necessary for the UE to get access to some services in the network.
The following three types of services are defined for the UE in Idle mode:
Limited service, which allows the UE to make emergency calls only on an acceptable cell.
Normal service, for public use on a suitable cell
Operator-related services, which allow the operator to test newly deployed cells without being disturbed by normal traffic.
An "acceptable cell" is a cell on which the UE may camp to obtain limited services (originate emergency calls). Such a cell fulfils the
following requirements, which is the minimum set of requirements to initiate an emergency call in a UTRAN network:
The cell is not barred.

The cell selection criteria are fulfilled.
A "suitable cell" is a cell on which the UE may camp on to obtain normal service.
Such a cell fulfils all the following requirements.
The cell is part of the selected PLMN or, of the registered PLMN or, the equivalent PLMN.
The cell is not barred.
The cell is not part of the list of "forbidden LAs for roaming".
The cell selection criteria are fulfilled.
A barred cell is a cell that is restricted (barred) to camp on for all access classes.
A reserved cell is a cell that has been reserved for operator use where only UEs with USIM access class 11 or 15 can camp on.
This is indicated on SIB 3.
The operator can establish cell access restrictions using the CellReservedForOperatorUse parameter that allows the reservation
of a cell for operator use only. It is also possible to restrict access for certain Access Classes (AC). Page 8
PLMN Selection
Whenever a UE is switched on or enters an area with acceptable coverage after coverage loss,
it attempts to camp on the last registered PLMN (RPLMN) or equivalent PLMN (EPLMN), if available.
To speed up the PLMN selection procedure, the UE uses information about the last registered PLMN, such as carrier frequencies or the list
of neighboring cells stored in the USIM before the UE was switched off. On each stored carrier frequency, the UE searches first for the
strongest signal cell and reads its system information to verify the PLMN to which the cell belongs.
It also reads the system information for PLMN identity, which consists of mcc and mnc. Then the UE decides whether the chosen cell is
acceptable or whether at least one acceptable cell belonging to that PLMN exists. Finally, the UE attempts registration if the PLMN is
allowed.
If the last registered PLMN is not available, a registration attempt fails. If there is no registered PLMN stored in the USIM, the UE selects
and attempts registration on other PLMNs using either the Automatic mode or the Manual mode.
RPLMN
The Registered PLMN (RPLMN) records LA and RA information. RPLMN is saved in EFLOCI and EFPSLOCI folders in USIM.
HPLMN
The Home PLMN are the PLMNs of which the MCC and MNC are the same as that in the IMSI of the UE, it is the PLMN that the UE
subscribed. HPLMN can be obtained from EFIMSI folder in USIM.
EPLMN
The Equivalent PLMN, indicating the PLMN that can provide the same services for users as the current network.
VPLMN
The Visitor PLMN, indicating the PLMN that the UE camps on except the HPLMN and EPLMN
Page 9
PLMN Selection
Automatic PLMN selection mode
In Automatic mode, if no last registered PLMN exists or is available,

the UE will select a PLMN that is available and allowed, in the
following order:
1. Home PLMN (HPLMN), if not previously selected, according to the

Radio Access Technologies (RATs) supported by the UE.
2. Each PLMN in the user-controlled PLMNs list in the USIM, if present,

in order of priority, according to the RATs supported by the UE.
3. Each PLMN in the operator-controlled PLMNs list in the USIM, in

order of priority, according to the RATs supported by the UE.
4. Other PLMNs, according to the high-quality criterion, in random order.
5. Other PLMNs that do not fulfill high-quality criterion, in order of

decreasing signal strength (SS).
PLMNs are considered high quality if the Received CPICH RSCP fulfills the high-quality criterion.
The high-quality criterion is fulfilled when CPICH RSCP level is greater than or equal to 95 dBm. For GSM cells the high-quality
criterion is fulfilled when the signal level is above 85 dBm.
A PLMN with at least one acceptable cell is considered available. If that PLMN is allowed, the UE tries to register on it. If registration is
successful, the UE displays the selected PLMN. When the UE cannot register on any PLMN in the user and operator lists, it attempts to
register on other PLMNs according to the high-quality criterion.
If the UE cannot register on any PLMN, it selects an available PLMN and enters a limited service state. If it does not find an available
PLMN, the UE enters the non-service state, and waits until a new PLMN is available and allowed.
Page 10
PLMN Selection
Manual PLMN selection mode
The Manual mode allows the user to select a PLMN among those indicated by the UE.
The UE displays all PLMNs that it finds by scanning all frequency carriers. The UE displays those PLMNs that are allowed as well as
those that are not allowed. The user makes a manual selection, according to the available access technology for the chosen PLMN, and
the UE attempts registration on this PLMN, ignoring the contents of the forbidden Location Area Identities (LAIs) and PLMN lists.
If the user selects an available PLMN in the forbidden PLMN list, the UE attempts to register and may receive a positive
acknowledgement from the CN. In this case, the PLMN is removed from the forbidden list.
If the user does not select a PLMN, the selected PLMN is the one that was selected before the PLMN selection procedure started. If this
PLMN is no longer available, the UE attempts to camp on an acceptable cell at any PLMN and enters the limited service state. The UE
remains in that state until it is switched off or the user makes a manual PLMN reselection.
Roaming
Roaming is a service through which a UE is able to obtain services from another PLMN in the same country (national roaming area) or
another country (international roaming area).
In many countries, the regulation authority enforced national roaming of UMTS subscribers in existing GSM networks in order to grant a
higher coverage to UMTS subscribers.
If national roaming is allowed, the UMTS operator wants to avoid unnecessary roaming fees. In this case the UE do PLMN reselection.
The MCC is the same in VPLMN and HPLMN while MNC is different , UE must periodically search for the HPLMN. The HPLMN Search
Period (EFHPLMN) timer, a value of T minutes may be stored in the SIM. Either T is in the range 6 minutes to 8 hours with a step of
6 minutes or T indicates that no periodic attempts shall be made. If no value is stored in the SIM, a default value of 60 minutes is used.
Page 11
PLMN Selection Parameters
GUI Value Actual Value Recommended

MO Parameter ID Parameter Name Parameter Description Unit
Range Range Value
Indicating whether the cell is reserved for
operators. If the status of cell is NOT_BARRED,
and the cell is reserved for operators, the UEs
RESERVED, RESERVED,
CellReservedForOperatorUse Cell reserved for operator use allocated with Access Class 11 or 15 in the local None NOT_RESERVED
NOT_RESERVED NOT_RESERVED
PLMN can select or reselect the cell. While the
UEs allocated with Access Class 0~9, 12 and 14
cannot select or reselect the cell.
Indicating whether the cell is reserved for

extension. If [Cell barred indicator] is
RESERVED, RESERVED,
CellReservationExtension Cell reservation extension NOT_BARRED, and the cell is not reserved for None NOT_RESERVED
NOT_RESERVED NOT_RESERVED
operators but for extension, the UEs regard the
cell as barred.
IsAccessClass0Barred Access class 0 barred indicator
UCELLACCESSSTRICT
Indicating whether the UE allocated with each
Access Class can be allowed to initiate access to
IsAccessClass7Barred Access class 7 barred indicator the radio network.The UE judges whether it BARRED, BARRED,
None NOT_BARRED
IsAccessClass8Barred Access class 8 barred indicator belongs to this access class based on the NOT_BARRED NOT_BARRED
SIM/USIM. For detailed information of this
parameter, refer to 3GPP TS 25.331.
Indicating whether the UE in idle mode is allowed
to access the cell. When the cell status is
BARRED, BARRED,
IdleCellBarred Cell barred indicator for SIB3 BARRED, it indicates that the UEs in idle mode None None
NOT_BARRED NOT_BARRED
are barred to select/reselect the cell even in the
case of emergency calls. Page 12
PLMN Selection Parameters
Actual Value Recommended

MO Parameter ID Parameter Name Parameter Description GUI Value Range Unit
Range Value
Indicating whether the UE in idle mode is allowed to reselect

another intra-frequency cell. This parameter is valid when [Cell
barred indicator for SIB3] is BARRED. If this parameter is
Intra-freq cell
ALLOWED, the UE in idle mode can select another intra- ALLOWED, ALLOWED,
IdleIntraFreqReselection reselection ind for None ALLOWED
frequency cell when the cell selection/reselection condition is NOT_ALLOWED NOT_ALLOWED
SIB3
satisfied. If this parameter is NOT_ALLOWED, the UE in idle
mod cannot select another intra-frequency cell. The indicator
can be neglected in case of emergency calls.
This parameter is valid when [Cell barred indicator for SIB3] is

BARRED. It indicates that the delay of the cell can be
measured next time when [Cell barred indicator for SIB3] is set D10, D20, D40, 10, 20, 40, 80,
IdleTbarred Time barred for SIB3 to BARRED. The greater the value, the lower the frequency of D80, D160, D320, 160, 320, 640, s D320
the UE trying to read the cell bar status. The smaller the value, D640, D1280 1280
the higher the frequency of the UE trying to read the cell bar
status.
Indicating whether the UE in connected mode is allowed to

UCELLACCESSSTRICT Cell barred indicator access the cell. When the cell status is BARRED, it indicates BARRED, BARRED,
ConnCellBarred None None
for SIB4 that the UEs in connected mode are barred to select/reselect NOT_BARRED NOT_BARRED
the cell even in the case of emergency calls.
Indicating whether the UE in idle mode is allowed to reselect

another intra-frequency cell. This parameter is valid when [Cell
barred indicator for SIB4] is BARRED. If this parameter is
Intra-freq cell
ALLOWED, the UE in connected mode can select another ALLOWED, ALLOWED,
ConnIntraFreqReselection reselection ind for None NOT_ALLOWED
intra-frequency cell when the cell selection/reselection condition NOT_ALLOWED NOT_ALLOWED
SIB4
is satisfied. If this parameter is NOT_ALLOWED, the UE in idle
mod cannot select another intra-frequency cell. The indicator
can be neglected in case of emergency calls.
This parameter is valid when [Cell barred indicator for SIB4] is

BARRED. It indicates that the delay of the cell can be
D10, D20, D40, 10, 20, 40, 80,
measured next time when [Cell barred indicator for SIB4] is set
ConnTbarred Time barred for SIB4 D80, D160, D320, 160, 320, 640, s D1280
to BARRED. The time barred can be increased or reduced in
network planning based on the actual time the cell is barred.
D640, D1280 1280
Page 13
For detailed information of this parameter.
System Information Reception
Within UTRAN, system information is broadcasted with the
help of the RRC messages.
System Information,
Paging Type I, and
System Information Change Indication.
Most system information parameters are determined by the RNC.
The Node B is informed about the parameters via the NBAP

message BCCH Information.
System information is organised in System Information Blocks

(SIBs). System information is grouped into SIB 1 to SIB 18.
Each SIB is responsible to carry a specific content.
There is a huge amount of SIBs, which have to be read by the

UE. This requires a lot of battery power. Therefore, a Master
Information Block (MIB) was introduced, which gives references Master Information Block (MIB):
and scheduling information about the SIBs. MIB informs the UE about the supported PLMN types and the
PLMN identity. The UE finds in the MIB also references to up to
For most of the SIBs used within the system, the MIB may carry a maxSIB (=32) SIBs, including their scheduling information and
value tag. type.
If a value tag is unchanged, the corresponding system information A MIB is valid in one cell. If a UE changes the cell, is must read
has not been modified. Thus, there is no need for the UE to read the new cells MIB. The MIB is read in the RRC modes/states
the SIB. SIB 7 has no value tag. It changes with each occurrence. RRC idle, CELL_FACH, CELL_PCH and URA PCH. Its parameter
are valid in the same states. A change of the MIB information is
indicated by a value tag. Page 14
Scheduling Block (SB)
This SB gives reference and scheduling information to other SIBs.
System Information Block 1 (SIB 1)

This SIB is used to inform the UE about NAS system information. The NAS system information characterises the NAS domains.
SIB 1 also delivers UE timers and counters, which have to be used by the UE in the RRC idle and RRC connected mode.
For instance, a UE in the RRC connected mode uses the timer T305 for periodic cell and URA updates. SIB 1 is valid in one PLMN.

This SIB contains an URA identity list.
SIB 2 is read and valid in the RRC sub-state URA_PCH. A change of the SIB 2 information is indicated by a value tag.

This SIB contains relevant parameters for cell selection and re-selection. It also holds the cell identity and cell restriction data, such as
cell barred IEs. SIB 3 must be read and is valid in the RRC idle mode. It is read and valid in the RRC connected mode sub-states
CELL_FACH, CELL_PCH and URA_PCH, if SIB 4 is not broadcasted. A change of the SIB 3 information is indicated by a value tag.

This SIB holds mostly the same data fields as SIB 3, but it is read and valid only, when the UE is in the RRC connected mode. I.e, this
optional SIB is read and valid in the CELL_FACH, CELL_PACH and URA_PCH sub-state.

The parameters for the configuration of physical channels are broadcasted in this SIB. The parameters cover the PICH power offset,
the AICH power offset, P-CCPCH, S-CCPCH and PRACH system information lists. SIB 5 must be read and is valid in the RRC idle
mode. It is read and valid in the RRC connected mode sub-states CELL_FACH, CELL_PCH and URA_PCH, if SIB 6 is not available.

This SIB holds mostly the same data fields as SIB 5, but it is read and valid only, when the UE is in the RRC connected mode. I.e, this
optional SIB is read and valid in the CELL_FACH, CELL_PACH and URA_PCH sub-state. Page 15
This SIB holds fast changing parameters. Therefore no value tag is used for it. The UE has to read its parameters periodically.
The fast changing parameters transmitted with SIB 7 include the UL interference and dynamic persistence level.

This SIB holds measurement control information. The UE gets here the relevant date for traffic measurement, intra-frequency
measurements, etc. SIB 11 must be read and is valid in the RRC idle mode. It is read and valid in the RRC connected mode sub-
states CELL_FACH, CELL_PCH and URA_PCH, if SIB 12 is not broadcasted.

SIB 12 transmits measurement control information for UEs in the RRC connected mode. If not transmitted, the UEs take the
parameters broadcasted with SIB 11. If available, SIB 12 is read and valid in the RRC connected mode sub-states CELL_FACH,
CELL_PCH and URA_PCH.
SIB13: contains ANSI-41 system information.
SIB14: contains the information in TDD mode.
SIB15: contains the position service information.
SIB16: contains the needed pre-configuration information for handover from other RAT to UTRAN.
SIB17: contains the configuration information for TDD.
SIB18: contains the PLMN identities of the neighboring cells.To be used in shared networks to help with the cell reselection process.
Page 16
Scope/
SIB broadcasted information read valid modification
MIB PLMN types & identities RRC idle mode, RRC idle mode, cell/
Scheduling information CELL_FACH, CELL_PCH, CELL_FACH, CELL_PCH, value tag
SIB references URA_PCH URA_PCH
SIB 1 NAS information RRC idle mode, RRC idle mode, PLMN/
UE timers & counters CELL_FACH, CELL_PCH, CELL_DCH, CELL_FACH, value tag
URA_PCH CELL_PCH, URA_PCH
SIB 2 URA identity list URA_PCH URA_PCH cell/
value tag
SIB 3 Cell selection RRC idle mode, RRC idle mode, cell/
and re-selection parameters (CELL_FACH, CELL_PCH, (CELL_FACH, CELL_PCH, value tag
URA_PCH) URA_PCH)
SIB 4 Cell selection and re- CELL_FACH, CELL_PCH, CELL_FACH, CELL_PCH, cell/
selection parameters for URA_PCH URA_PCH value tag
Ues in the connected mode
SIB 5 Parameters for common RRC idle mode, RRC idle mode, cell/
physical channel (CELL_DCH, CELL_FACH, (CELL_DCH, CELL_FACH, value tag
configuration CELL_PCH, URA_PCH) CELL_PCH, URA_PCH)
SIB 7 UL interference level RRC idle mode, RRC idle mode, cell/
Dynamic persistence level CELL_FACH, CELL_PCH, CELL_FACH, CELL_PCH, max(32, 8 * Expir-
(fast changing parameters) URA_PCH URA_PCH ation Time Factor)
RRC idle mode, RRC idle mode, cell/
SIB 11 Measurement control information
(CELL_FACH, CELL_PCH, (CELL_DCH, CELL_FACH, value tag
URA_PCH) CELL_PCH, URA_PCH)
SIB 12 Measurement control information CELL_FACH, CELL_PCH, cell/
CELL_DCH, CELL_FACH,
for UEs in the RRC connected URA_PCH value tag
CELL_PCH, URA_PCH
mode
SIB 18 PLMN ID of neighbouring cells CELL_FACH, CELL_PCH, CELL_FACH, CELL_PCH, value tag
URA_PCH URA_PCH)
SIB 19 Information about the LTE Page 17
CELL_FACH, CELL_PCH, CELL_FACH, CELL_PCH, value tag
neighbouring cells
URA_PCH URA_PCH)
UTRAN can notify UEs, that a value tag in the MIB has been changed. Hereby, the information element
BCCH Modification Info is broadcasted. There are two RRC messages, which can carry this information element:
Paging Type 1
Some mobile phones have no radio link allocated, mobile phones, which are in the RRC idle mode, and in the RRC connected mode
sub-states CELL_PCH and URA_PCH. This paging message is transmitted in all paging occasions in the cell.
System Information Change Indication

With this message, we address UEs in the CELL_FACH sub-state. Consequently, this message must be transmitted on every S-CCPCH,
which carries FACHs. The System Information Change Indication message is transmitted on a BCCH, which must be mapped on FACHs
in such a way, that every S-CCPCH carries the BCCH Modification Change IE.
Please note, that UEs in the CELL_DCH sub-state are

addressed directly by the RNC via the Measurement
Control message.
Page 18
System Information Parameters
Parameter Baseline
MO Parameter ID Parameter Description GUI Value Range Actual Value Range Unit
Name Value
Determine whether some system information

blocks are broadcast in this cell. If the SIB2, SIB4, SIB12, SIB2, SIB4, SIB12,
UCELLSIBSWITCH SibCfgBitMap SIB Switch corresponding system information block is SIB18, SIB19, SIB18, SIB19, None None
selected, then send this system information SIB11BIS SIB11BIS
block in this cell.
In Huawei RAN 13, the SIB1, SIB3, SIB5, SIB6, SIB7, SIB11 are enabled by default.
The optional SIB2,SIB4,SIB12,SIB18,SIB19,SIB11BIS can be enabled by cell parameter SIB switch.
Page 19
Cell Selection
If the UE does not

meet the S criteria, it
camp in the original Camped
cell and keeps Normally
PLMN selection searching
The cell is
not under
the PLMN
Obtains the If the UE meets the
Reads the information
Cell S criteria
Determines broadcast of the cell
searching the primary channel
scrambling
code of the
cell
Criteria-S
Keeps
searching
camp on any
cell, and calls
are restricted
The cell selection and reselection process allows the UE to look for a suitable cell in the selected PLMN and to camp on it.
The UE then camps on the suitable cell in a camped normallystate. In this state, the UE monitors paging and system
information, performs periodical radio measurements, and evaluates cell reselection criteria.
If the UE finds a better cell, that cell is selected by the cell reselection process. The change of cell may imply a change of the RAT.
Page 20
Cell Selection
When the PLMN is selected and the UE is in idle mode, the UE starts to select a cell to camp on and to obtain services .
Cell selection is triggered for the following cases;
At power on.
After a number of failed RRC Connection requests.
When entering Idle mode after a number of failed cell update attempts.
After transition from dedicated mode (CELL_DCH) to any of the following states: CELL_FACH, URA_PCH or Idle mode.
The candidate cells for cell selection are the ones used immediately before leaving dedicated mode. If no suitable cell is found, the UE
can use stored information cell selection procedure to find a suitable cell.
When entering Idle mode after completion of an emergency call on any PLMN. In this case, candidate cells for cell selection are the
ones used immediately before leaving the Connected mode. If no acceptable cell on that PLMN is found, the UE continues to search for
an acceptable cell on any PLMN.
There are 4 states involved in Cell Selection:
Page 21
Cell Selection
go here w henev er
a new P LM N The UE uses one of the following cell
is s elec ted
selection procedures:
c ell inform ation no c ell inform ation 1) Initial Cell Selection
1
s tored for the P LM N s tored for the P LM N This procedure requires no prior knowledge
of which RF channels are UTRA carriers.
S tored
Inform ation no s uitable c ell found
Initial UE shall scan all RF channels in the UTRA
C ell S elec tion bands according to its capabilities to find a
C ell S elec tion
no s uitable suitable cell of the selected PLMN. On each
c ell found
carrier, the UE only needs to search for the
s uitable c ell found s uitable c ell found no
strongest cell. Once a suitable cell is found this
s uitable cell is selected.
c ell
s uitable found
C ell S elec tion
c ell found NAS 2) Stored information cell selection
w hen leaving C am ped
c onnec ted norm ally
regis tration To speed up the cell selection process
rejec ted
m ode for instance, when the UE is switched on
again information about UTRA carriers,
cell parameters such as cell scrambling codes
return to leave s uitable
idle m ode idle m ode c ell s elec ted can be stored in the UE.
trigger
The UE uses this information to find a

C ell
C onnec ted R es election no s uitable
suitable cell of the PLMN, which was selected
M ode E valuation c ell found by the NAS. If the cell selection based on
P roc ess stored information in the UE fails
e.g. the selected PLMN cannot be found
the UE continues the cell selection process
based on the Initial Cell Selection procedure.
Page 22
Cell Selection
go here when no USIM in the UE Any Cell

Selection
1 USIM inserted
no acceptable cell found
an acceptable cell found
acceptable
Cell Selection
cell found
when leaving Camped on suitable
1
connected Any Cell cell found
mode
leave acceptable
return to idle mode
idle mode cell selected
trigger
Connected Cell no acceptable

Mode Reselection cell found
(Emergency Evaluation
calls only) Process
Page 23
Cell Selection
S criteria:
Determines whether the cell is Suitable.
R criteria:
Determines the Ranking of the cell relative to other neighbor cells and serving cell.
A suitable cell must fulfill the cell selection S-criteria. The UE bases its evaluation on two quantities: Squal and Srxlev.
The Squal quantity has been introduced to evaluate the Signal to Interference Ratio (SIR) on the CPICH, CPICH (CPICH Ec/No).
In order to evaluate whether cell selection criteria (S-criteria) are fulfilled, the UE calculates the following:
Srxlev > 0 and Squal > 0

Srxlev = Qrxlevmeas Qrxlevmin Pcompensation
Squal = Qqualmeas Qqualmin
Where :
-Qqualmeas is the quality value for the received signal, expressed in CPICH Ec/No (dB) and measured by the UE.
-Cell parameter Qqualmin indicates the minimum required quality value in the cell. It is sent in system information, in SIB3 for the
serving cell, and in SIB11 for neighbour cells.
-Qrxlevmeas is the received signal strength measured by the UE and expressed in CPICH RSCP (dBm).
-Cell parameter Qrxlevmin indicates the minimum required signal strength in the cell. It is sent in SIB3 for the serving cell and in SIB11
for neighbour cells.
Pcompensation = max (UE_TX_PWR_MAX_RACH P_MAX, 0)

Pcompensation is introduced for UEs that cannot transmit at maximum power on the RACH in the cell.
The cell range decreases for those UEs. The cell parameter MaxAllowedUlTxPower indicates the maximum allowed transmission
power when the UE accesses the system on RACH. It is broadcast in SIB3.
P_MAX = Maximum Tx output power of the UE according to its class. Page 24

UE_TX_PWR_MAX_RACH = Maximum allowed TX power on PRACH (MaxAllowedUlTxPower).
Cell Selection
In addition to the S criteria, for a cell to be suitable it must:
Belong to the currently registered PLMN (or equivalent PLMN).

Not be barred.
Not belong to a forbidden location area.
This additional information is obtained by reading the system information

messages on the new cell.
I am Cell size defining parameters:

outside Qrxlevmin
Qqualmin
I am inside,
but have
insufficient
power.
Pcompensation
= max(UE_TXPWR_MAX_RACH P_MAX, 0) Page 25
Cell Reselection and Handover
Cell Reselection No Dedicated Physical Channels
UE procedure that allows the UE to change the cell it is camped on.
UTRAN provides parameters to control reselection, but the UE changes cells autonomously.
Handover Dedicated Physical Channels

UE and UTRAN procedure that allows the UE to change from one cell to another, while the UE has dedicated radio resources allocated to it.
UE provides measurements to UTRAN, and UTRAN commands UE to perform a handover.
Types of Cell Reselection and Handover

Intra-frequency
Within the same UMTS frequency.
In Cell_DCH and Cell_FACH, measurements can be taken at any time.
In other states, measurements can be taken during the paging occasion.
Inter-frequency
Between different UMTS frequencies.
In Cell_DCH and Cell_FACH, measurements must be taken when it is possible to tune the radio away from the serving cell without
losing data.
Inter-RAT
Between different Radio Access Technologies (e.g., from UTRA_FDD to GSM or UTRA-TDD).
In Cell_DCH and Cell_FACH, measurements must be taken when it is possible to tune the radio away from the serving cell without
losing data.
Page 26
Measurements for Cell Reselection
When the UE is monitoring the Paging

Indicator Channel (Idle, Cell_PCH,
andURA_PCH states), all intra-frequency,
inter-frequency, and inter-RAT
measurements are taken when the UE
wakes up during its assigned Paging
Occasion. DRXCycleLenCoef
established by the network determines the
frequency of these measurements.
When the UE is in Cell_FACH state, intra-

frequency measurement may be taken at
anytime, but inter-frequency and inter-RAT
measurements may only be taken during
the interval determined by the FACH
Measurement Occasion cycle length
coefficient,supplied in a system
information message.
When the UE is in Cell_DCH state, intra-

frequency measurement may be taken at
anytime, but inter-frequency and inter-RAT
measurements may only be taken during
Compressed Mode gaps.
Page 27
Cell Reselection
The UE performs the Cell Reselection procedure in the following cases:
When the cell on which it is camping is no longer suitable.

When the UE, in camped normally state, has found a neighboring cell better than the cell on which it is camping.
When the UE is in limited service state on an acceptable cell.
The Cell Reselection Process is divided into 3 steps Measurements, Eligibility (S-criteria) and Ranking(R-Criteria).
On the BCCH, parameters for cell reselection are broadcasted. If a cell meets the cell selection criteria of these parameters, it is a better cell
to camp on. The cell re-selection may result in the change of the UTRA carrier or even the RAT.
If the UE camps normally on a cell, it is responsible to

monitor the BCCH and to obtain the system information;
listen to its paging channel and its paging channel resource;
perform serving cell measurements periodically;
perform neighbouring cell measurements as far as this is required by the cell re-selection evaluation procedure;
conduct the cell re-selection evaluation procedure, when BCCH information has changed or internal threshold measures indicate it.
execute a cell reselection, if a better cell has been found after the cell re-selection evaluation process;
move the UE to the internal state Any cell selection, if no suitable cell can be found.
The UE performs its measurements based on the BCCH. The BCCH also delivers the neighbourhood list to the UE.
Given this information, the UE decides,
on which RATs and frequency bands it has to perform its measurements
which cells are candidate cells for measurements within one frequency band and RAT (HCS), and ranks the cells to determine the best
suitable cell for cell reselection.
Page 28
Cell Reselection
Cell Reselection Process
Step (1) UE decides whether to start the intra-frequency ,inter-frequency or inter-RAT measurement according to the Sx and the UE
movement state.
Step (2) The eligibility of the intra frequency neighbors for reselection is verified using the cell selection criteria (S-criteria) ,
UE calculates the serving cell SX according to the following formulas:
Srxlev = Qrxlevmeas Qrxlevmin Pcompensation

Squal = Qqualmeas Qqualmin
Step (3) The cells are ranked according to the measurement results. The UE selects a suitable cell to camp on according to the cell
reselection R-criteria.
Page 29
Cell Reselection Step(1)
The operator has to determine the threshold values which trigger the cell re-selection process
by the UE and whether to use the HCS (Hierarchical Cell Structures) . The BCCH is used to inform the UE about the use of HCS.
If it is not used, the UEs measurements are based on following rules,
Intra-Frequency measurement threshold Sintrasearch

If this parameter is not sent in the serving cell, the UE must always perform intra-frequency measurements.
If it is transmitted and Sx IdleSintrasearch ,UE must perform intra-frequency measurements otherwise there is no need to perform
this type of measurements.
Inter-Frequency measurement threshold Sintersearch

If Sx IdleSintersearch ,UE must perform inter-frequency measurements otherwise there is no need to perform this type of measurement.
Inter-RAT measurement threshold SsearchRAT

If Sx SsearchRat ,UE must perform the inter-RAT measurements on other cells of radio access technology otherwise there is no need to perform
this type of mearuement.
Sx=Squal = Qqualmeas Qqualmin

Qqualmeas Qqualmin IdleSintrasearch
Qqualmeas Qqualmin + IdleSintrasearch
Qqualmeas Qqualmin + IdleSintrasearch

= -18 + 10 -8 dB
Qqualmeas Qqualmin + IdleSintersearch

= -18 + 8 -10 dB
-14dBm -10dBm -8dBm
Qqualmeas Qqualmin + SsearchRAT
= -18 + 4 -14 dB
Page 30
UE start the measurement on serving cell and neighbouring cells according to the rules of Step (1) ,
then UE has to find the suitable cells for cell reselection which based on the cell-ranking of R-Criteria.
The UE shall rank the cells according to the R-Criteria derive Qmeas,n and Qmeas,s and calculate the R values, a cell ranked with the
higherst value R is the best cell for UE to camp on.
Rs = Qmeas,s + Qhysts (for the serving cell)

Rn = Qmeas,n - Qoffsets,n (for candidate neighbouring cells for cell reselection)
-Rs, s means serving cell. Rn, n means neighboring cells.

-Qhysts gives a hysteresis value to make the serving cell more attractive and thus delay the cell re-selection.
It exists in two versions: If the quality measure is based on CPICH Ec/No, Qhyst2s is used in (FDD cell only); otherwise the hysteresis
value Qhyst1s is used (if the quality measure for FDD cells is based on CPICH RSCP, for TDD cells and GSM cells).
-Qoffset is an offset given for each individual neighbouring cell, which ranges between 50 and 50 dB, with default set to 0.
The ranking of GSM neighbors is always made using the measurement quantity CPICH RSCP. The ranking of WCDMA cells can be done
using CPICH RSCP or CPICH Ec/No based on the value of the parameter QualMeas.
If a GSM cell is the best ranked cell after the first ranking, it is selected for the 3G to 2G reselection. The UE reselects to the new cell, if it is
better ranked than the serving cell for a time equal to Treselection A second ranking is only performed if the best ranked cell resulting
from the first ranking is a WCDMA neighbor and the parameter QualMeas is set to CPICH Ec/No.
To avoid a ping-pong effect on cell reselection -a UE often performing cell reselection between two neighbouring cells.,a cell parameter
Treselection, whose value ranges between 0 and 31 seconds is applied.
Only when a cell was ranked Treselection seconds better then the serving cell, a cell reselection to this cell takes place. In addition to this,
a UE must camp at least 1 second on a serving cell, before the next cell re-selection may take place.
Page 31
Page 32
Cell Selection & Reselection Parameters
Actual Value
MO Parameter ID Parameter Name Parameter Description GUI Value Range Unit Baseline Value
Range
Cell Sel-reselection quality Measurement quantity of cell selection and reselection. It CPICH_ECNO(CPICH Ec/N0), CPICH_ECNO,
QualMeas None CPICH_ECNO
measure can be set to CPICH Ec/N0 or CPICH RSCP. CPICH_RSCP(CPICH RSCP) CPICH_RSCP
The hysteresis value of the serving FDD cells in idle mode

IdleQhyst1s Hysteresis 1 for idle mode in case the quality measurement for cell selection and 0~20 0~40 2dB 2
reselection is set to CPICH RSCP.
The hysteresis value of the serving FDD cells in connected

ConnQhyst1s Hysteresis 1 for connect mode mode in case the quality measurement for cell selection and 0~20 0~40 2dB 2
reselection is set to CPICH RSCP.
The hysteresis value of the serving FDD cells in idle mode

IdleQhyst2s Hysteresis 2 for idle mode in case the quality measurement for cell selection and 0~20, 255 {0~40}, {255} 2dB 1
reselection is set to CPICH Ec/No.
The hysteresis value of the serving FDD cells in connected

UCELLSELRESEL ConnQhyst2s Hysteresis 2 for connect mode mode in case the quality measurement for cell selection and 0~20, 255 {0~40}, {255} 2dB 1
reselection is set to CPICH Ec/No.
If the signal quality of a neighboring cell is better than that of

the serving cell during the specified time of this parameter,
Treselections Reselection delay time 0~31 0~31 s 1
the UE reselects the neighboring cell. It is used to avoid
ping-pong reselection between different cells.
The minimum required quality threshold corresponding to

CPICH Ec/No. The UE can camp on the cell only when the
Qqualmin Min quality level -24~0 -24~0 dB -18
measured CPICH Ec/No is greater than the value of this
parameter.
The minimum required RX threshold corresponding to

CPICH RSCP. The UE can camp on the cell only when the
Qrxlevmin Min Rx level -58~-13 -115~-25 2dBm -58
measured CPICH RSCP is greater than the value of this
parameter.
Page 33
Cell Selection & Reselection Parameters
GUI Value Actual Value Baseline
Range Range Value
Threshold for intra-frequency cell reselection in idle mode. When the

quality (CPICH Ec/No measured by the UE) of the serving cell is lower
Intra-freq cell reselection {-32~20},
IdleSintrasearch than this threshold plus the [Qqualmin] of the cell, the intra-frequency -16~10, 127 2dB 5
threshold for idle mode {127}
cell reselection procedure will be started. This parameter is not
configured when its value is 127.
Threshold for inter-frequency cell reselection in idle mode. When the

quality (CPICH Ec/No measured by UE) of the serving cell is lower
Inter-freq cell reselection {-32~20},
IdleSintersearch than this threshold plus the [Qqualmin] of the cell, the inter-frequency -16~10, 127 2dB 4
threshold for idle mode {127}
cell reselection procedure will be started. This parameter is not
configured when its value is 127.
Threshold for intra-frequency cell reselection in connected mode.

When the quality (CPICH Ec/No measured by the UE) of the serving
Intra-freq cell reselection {-32~20},
ConnSintrasearch cell is lower than this threshold plus the [Qqualmin] of the cell, the -16~10, 127 2dB 5
UCELLSELRESEL threshold for connect mode {127}
intra-frequency cell reselection procedure will be started. This
parameter is not configured when its value is 127.
Threshold for inter-frequency cell reselection in connected mode.

When the quality (CPICH Ec/No measured by UE) of the serving cell
Inter-freq cell reselection {-32~20},
ConnSintersearch is lower than this threshold plus the [Qqualmin] of the cell, the inter- -16~10, 127 2dB 4
threshold for connect mode {127}
frequency cell reselection procedure will be started. This parameter is
not configured when its value is 127.
Threshold for inter-RAT cell reselection. When the quality (CPICH

Inter-RAT cell reselection Ec/No measured by UE) of the serving cell is lower than this threshold {-32~20},
SsearchRat -16~10, 127 2dB 2
threshold plus the [Qqualmin] of the cell, the inter-RAT cell reselection {127}
procedure will be started.
The maximum allowed uplink transmit power of a UE in the cell, which

MaxAllowedUlTxPower Max allowed UE UL TX power -50~33 -50~33 dBm 24
is related to the network planning.
USED~0, USED,
UCELLHCS UseOfHcs Use of HCS Indicating whether HCS is used. For details, refer to 3GPP TS 25.304. None NOT_USED
NOT_USED~1 NOT_USED Page 34
LA and RA Registration and Updating
After a UE has found a suitable cell and can access services requiring registration, it tries to register on the selected PLMN.
If the Location Area Identity (LAI) or Routing Area Identity (RAI), read on SIB 1, is different from the one stored on the USIM before switch-
off, the UE performs a LA or RA registration update.
When a UE in idle mode moves into a new cell in a new LA or RA or into a new PLMN, it performs a registration area update.
The LA or RA update procedure is managed by the CN and is transparent to the WCDMA RAN.
There are three types of registration update procedures: Normal, Periodic and IMSI attach/detach.
Location Area (LA) is an area to which the CS- Core network (CS-CN) sends a paging message for circuit switch services.
The LA may consist of cells belonging to one or more RNCs, which are connected to the same CN. Location Area Identity (LAI) is formed by
a PLMN Identity and a Location Area Code (LAC) sent in SIB 1.
Routing Area (RA) is an area to which the PS-Core network (PS-CN) sends a paging message for packet switch services.
The RA may consist of cells belonging to one or more RNCs, which are connected to the same CN.Routing Area Identity (RAI) is formed by
a PLMN Identity and a Routing Area Code (RAC) sent in the SIB 1.
Normal LA and RA Update
A UE executes a normal registration update when, in a cell belonging to a new LA or RA, it is switched on or leaves the Connected mode.
Normal registration update is also performed when the UE, in Idle mode, moves in a cell belonging to a new LA or RA, or when the UE is
unknown to the CN. The UE reads the LAI and the RAI in the system information and detects that one or both of the received area identities
differ from the ones stored on the USIM.
If the LAI received is not in the forbidden LAIs list, an LA and/or RA update request is sent by the UE to the WCDMA RAN. If the LAI is
forbidden, the UE tries to select another cell belonging to a permitted LAI or another PLMN.
Page 35
LA and RA Registration and Updating
Periodic LA and RA Update
Periodic LA or RA updating is used to notify the network of the UEs availability, and to avoid unnecessary paging attempts for a UE that has
lost coverage and is not able to inform the CN that it is inactive.
The periodic LA update procedure is controlled by a timer, T3212, which gives the time interval between two consecutive periodic location
updates. The value is sent by the WCDMA RAN to UEs on the SIB 1.
The periodic RA update procedure is controlled by a timer, T3312, which gives the time interval between two consecutive periodic routing
updates. The value of this timer is sent by the PS-CN to the UE in the IMSI attached or in the routing area update message accept.
IMSI Attach/Detach
A location registration request indicating IMSI attach is made when the UE is activated in the same LA in which it was deactivated, and the
system information indicates that IMSI attach/detach is used (SIB 1). The IMSI attach/detach procedure allows the UE to avoid unnecessary
paging attempts from the CN. If IMSI attach/detach is used the UE sends an attach or detach message to the CN when is powered on
or off indicating whether the UE is active or inactive in the network.
The CN avoids performing paging attempts when the IMSI detach is applied and the UE is switched off.
When the UE is switched on and the IMSI attach/detach procedure is applied the UE performs a location registration request, indicating
IMSI attach, if it is in the same LA or RA in which it was switched off. If the registration area is changed, a normal LA update is performed by
the UE.
The parameter called ATT indicate if IMSI attach/detach is used.
Page 36
LA and RA Registration Parameters

Range Range Value
Periodical location update is implemented by MS through the

location update procedure. 0: The periodical update procedure is
UCNDOMAIN T3212 Periodical location update timer 0~255 0~1530 6min 10
not used. This parameter is valid only when [CN domain ID] is set
as CS_DOMAIN.
Indicating whether attach/detach is allowed. NOT_ALLOWED

indicates that MS cannot apply the IMSI attach/detach
NOT_ALLOWED, NOT_ALLOWED,
UCNDOMAIN ATT Attach/detach allowed indication procedure. ALLOWED indicates that MS can apply the IMSI None ALLOWED
ALLOWED ALLOWED
attach/detach procedure. It is valid only when [CN domain ID] is
set as CS_DOMAIN.
This parameter should be set according to the actual network

situation . If there is the Gs interface between SGSN and
UCNDOMAIN NMO Network mode of operation MODE1, MODE2 MODE1, MODE2 None MODE2
MSC/VLR this parameter is set as MODE1; otherwise, MODE2. It
is valid only when [CN domain ID] is set as PS_DOMAIN.
Page 37
Table of Contents

Page 38
Paging
The primary purpose of paging is to set up a Mobile Terminating (MT) call.
The idle User Equipment (UE) is normally paged in a Location Area (LA) or a Routing Area (RA) using a subscriber-Id (e.g. IMSI or P-TMSI),
depending on the Core Network (CN) domain that originated the page message. The idle UEs response to the paging message will reveal
its location at the cell level to the network and necessary signaling will continue oncommon and/or dedicated channels in order to establish a
connection to the UE.
In addition to paging in LA and RA, UMTS defines a new paging area known as UTRAN Registration Area (URA). The URAs are known only
within the UTRAN and are generally independent of LAs and RAs. A UE is paged in a URA only when it is in the RRC URA_PCH mode (i.e.
it has an active RRC connection towards a Serving RNC). A single cell can belong to more than one URA, thus allowing for overlapping
URAs. SIB 2 indicates a list of URAs the cell belongs to, and a UE can be assigned more than one URA-id. Careful URA-planning involves
considerations regarding a balance between the paging load and UE initiated URA-updates, similar to LA/RA planning.
Paging includes CN orignated paging and UTRAN originated paging
1) CN Originated Paging : this type of paging is used to establish a signaling connection. It is divided into co-ordination paging and
non co-ordination paging. The CN indicates in the RANAP paging message whether the RNC shall perform the UTRAN co-ordination paging.
Co-ordination paging, the RNC shall check whether the UE has other CN domain signaling connections besides the paging domain
connection.
Non-co-ordinating paging, the RNC need not check whether the UE has other CN domain signaling connections besides the paging
domain connection but directly transmit the paging message on the PCCH in the CN specified paging area.
2) UTRAN Orignated Paing : UTRAN may initiate paging for a UE in Cell_PCH or URA_PCH state to trgiger a cell update procedure to
enable the transition to Cell_FACH state. In additon,the UTRAN may initiate paging for a UE to trigger reading of updated system
information.
Page 39
Paging
In UTRAN, we distinguish two different types of paging,
depending on the existence of a RL connection between UE and UTRAN.
Paging Type 1
The RRC message Paging Type 1 is used, when a paging message has to be transmitted to a UE, which is either in the RRC idle
mode, or in the RRC connected mode sub-states CELL_PCH or URA_PCH.
For a UE in RRC Idle state, an RRC: PAGING TYPE 1 is sent from the RNC to the UE. Two parameters in Paging Type 1 are the CN
domain-Id and the IMSI/(P)TMSI of the paged UE. If the UE has already an RRC connection, then the RNC may convert the
IMSI/(P)TMSI to a UTRAN Radio Network Temporary Id (U-RNTI).
There are several reasons, why this paging message type is initiated.
Upper layers request the setup of an RRC signalling connection.

This may be the cause, when a paging message from the CN has to be forwarded to the UE.In this case, the UE adds the IE Paging
Cause to the the paging message. Higher layers may also initiate paging, when user data has to be transmitted on an existing ps
connection (PMM-IDLE or PMM-CONNECTED). UTRAN has to page the UEs in the CELL_PCH and URA_PCH sub-states to establish
a connection before forwarding the user data.
UTRAN wants to trigger a cell update for UEs in the CELL_PCH or URA_PCH sub-state.
UTRAN wants to notify UEs in the RRC idle mode and in the RRC connected mode CELL_PCH and URA_PCH about system
information changes.
The UE monitors the paging channels (S-CCPCHs carrying PCCH) on all paging occasions. If the UE receives a paging message, it reads
the UE identity to check, whether it is the receiver of the message. If so, it returns a paging response.
The UTRAN may repeat the transmission of a PAGING TYPE 1 message to a UE on several paging occasions message on an appropriate
paging occasion to increase the probability of proper reception of a page. Page 40
Paging
Paging Type 2
This RRC message is used, when the UE is in the CELL_DCH or CELL_FACH state, i.e., when at least dedicated control channel
resources were allocated to the UE.
One example: The user is serving in the Internet, and due to the high download, the RNC has allocated one DDCH and one DCCH to
the user. Consequently, a connection between the UE and the 3G-SGSN exists, and between the two network elements, dedicated
transmission resources are available for the user. While the subscriber is serving, he receives a call. The 3G-MSC is sending a
paging message to all RNCs, which participate in the LA where the UE is registered. This paging message is received by a RNC,
which is currently serving the UE. It then uses the existing DCCH to forward the paging request to the UE.
Therefore, Paging Type 2 is often called dedicated paging.
Page 41
Paging Channels
The paging message is carried in the downlink on the Logical channel Paging Control Channel (PCCH).
The logical channel is mapped to the transport channel Paging Channel (PCH) at the MAC layer. This channel in turn is coded and
carried over the air using the Secondary Common Control Physical Channel (S-CCPCH).
A paging message type 2 is associated with the Dedicated Control Channel

DCCH,which may be mapped to FACH or DCH transport channels.
A cell may be configured with more than one S-CCPCH depending for example
on the cell load and the expected paging volume. The S-CCPCH spreading
factor (SF) may be chosen from any valid SF from 4 to 256.
Paging Indicator Channel (PICH)

UMTS provides the terminals with an efficient sleep mode operation. The UEs do not have to always read and process the content,
transmitted during their paging occasion on their PCH.
A PICH is a physical channel, which carries Paging Indicators (PI). A set of PI bits within the PICH indicate to a UE,
whether there is a page message for it. Only then, the UE listens to the S-CCPCH frame, which is transmitted 7680 chips after the PICH
frame in order to see, whether there is indeed a paging message for it. Each PICH is associated with a S-CCPCH which carries the
transport channel PCH.
The PICH is used with spreading factor 256. 300 bits are transmitted in a 10 ms frame, and 288 of them are used for paging
indication. The UE was informed by the BCCH, how many paging indicators exist on a 10 ms frame. The number of paging indicator
Np (PICHMode) can be 18, 36, 72, and 144, and is set by the operator as part of the network planning process.
The higher Np, the more paging indicators exist, the more paging groups exist, among which UEs can be distributed on.
Consequently, the lower the probability, that a UE reacts on a paging indicator, while there is no paging message in the associated
S-CCPCH frame. But a high number of paging indicators results in a comparatively high output power for the PICH, because less bits
exists within a paging indicator to indicate the paging event.
Page 42
Paging Channels- S-CCPCH and PICH
Time offset between PICH and SCCPCH:
2 msec
UE will read the paging

information on SCCPCH
if the paging indicator (PI)
of its group is 1.
Page 43
DRX Procedure
A UE in idle mode (or RRC Cell_PCH/URA_PCH) has to continuously monitor PCH so that it will not miss any incoming calls
or RRC messages. This can be very demanding on the UEs battery power consumption.
For this reason, Discontinuous Reception (DRX) mechanism is used in UMTS as in many other wireless systems.
The PICH is used to indicate to the UE when it should read the S-CCPCH which carries the true paging message. If a UE that is monitoring
the PICH does not see an indication that it is paged, it will ignore the following S-CCPCH. If the UE does see an indication then it will
decode the S-CCPCH which occurs 2ms after the PICH frame. Although the PICH carries a simple yes-no message, listening to PICH on
every frame is not a very effective power saving feature. Further enhancement to power saving can be achieved if the UE only wakes up
and listens to certain PICH frames. This frequency of wake-up is called the Paging Occasion and is determined by important
DRXCycleLenCoef parameter.
The first 1 to K entries transmit the (transport channel) PCH, while the remaining S-CCPCH in the list hold no paging information. The UE
determines the S-CCPCH, where it is paged, by its IMSI and the number of PCH/S-CCPCHs (K). When paging the UE, the RNC knows the
UEs IMSI, too, so that it can put the paging message on the correct PCH transport channel.
DRX Cycle Length MAX(2k, PBP) frames
k is the CN domain specific DRX cycle length coefficient

DRXCycleLenCoef which is broadcasted in SIB1.
The typical value is 6.
If the UE is in the idle mode, it takes the smaller k-value

of either the cs- or ps-domain.
If the UE is in the connected mode, it has to select the

smallest k-value of UTRAN and the CN.
PBP is Paging Block Periodicity , which is 1 for FDD mode.

The paging period should be 640ms if k is 6. (=64 SFN).
Page 44
DRX Procedure
DRX cycle coefficient is ranges from 3 to 9 ,the possible DRX values are then from 80ms to a little
more than 5 seconds of sleeping time. If this value is set too low, the UE is more active in monitoring the PICH, thus decreasing the UE
stand-by time. On the other hand, large values of this parameter will increase mobile-terminating call set-up times, since the UE will take
longer periods of time to read the PICH.
The DRX Cycle Length value can be set separately for each Core Network domain type. If a UE is connected to both the PS and CS Core
networks simultaneously, then the shorter of the two values will always be used by the UE. For UEs in connected mode (URA_PCH and
Cell_PCH) a separate k value is defined. It is generally considered beneficial to decrease the DRX cycle length for connected mode UEs
since transitions to Cell_FACH need to occur faster in comparison to those between idle mode and connected mode.
Page 45
DRX Procedure
Using the Np value and the IMSI, the UE can also calculate its own Paging
Indicator (PI) to know where in the PICH to look for paging indicators.
The paging indicator for a particular UE can be calculated based on its IMSI.
Each UE will calculate a Paging Occasion, which simply

corresponds to the frame number that the UE must read the
PICH on. The Paging Occasion is a function of the IMSI,
(CELL SFN)
the DRX cycle length, and the number of S-CCPCH in the cell
and the System Frame Number (SFN).
one paging n =0, 1, 2and the requirement is the calculated CELL SFN must be
occasion below its maximum value 4095
2^K-1

K is the number of SCCPCH which carries PCH per cell , and the
0 4095 typical value is 1.
UE needs to monitor the frames (paging occasions)

indicated by the red dots, and then decodes the qth PI of
PI PI PI PI this frame.
0 1 q NP-1 Page 46
Paging Parameters
Actual
GUI Value Baseline
MO Parameter ID Parameter Name Parameter Description Value Unit
Range Value
Range
CN domain specific Discontinuous Reception (DRX) cycle
DRX cycle length
UCNDOMAIN DRXCycleLenCoef length coefficient broadcast on SIB1 and used by UEs in Idle 6~9 6~9 None 6
coefficient
Mode.
Indicating the number of PIs contained in each frame of the

V18, V36, 18, 36, 72,
UPICH PICHMode PICH Mode PICH For detailed information of this parameter, refer to None V36
V72, V144 144
3GPP TS 25.211.
This parameter defines the times of retransmission of paging

Repeat Times of messages. If the times of retransmission exceed the value of
UDPUCFGDATA MaccPageRepeatTimes 0~2 0~2 None 1
Macc Paging this parameter, retransmission stops. For details, refer to the
3GPP TS 25.331 protocol.
UTRAN-specific Discontinuous Reception (DRX) cycle

length coefficient. In connected mode, the UE uses the
shorter one between CN-specific DRX cycle length
coefficient and UTRAN-specific DRX cycle length coefficient.
In idle mode, the UE can use the DRX mode to receive
paging indications so as to reduce power consumption; in
Paging DRX cycle this case, the UE needs to monitor only one paging
UFRC DrxCycleLenCoef 3~9 3~9 None 6
coefficient indication in one paging occasion during each DRX cycle.
A value too small causes the UE to check the paging

channel frequently, thus having great power consumption. A
value too large makes the response of the UE to the paging
slow and the core network repeatedly page the UE, thus
increasing the downlink interference.
Page 47
Random Access Procedure
The UMTS Random Access Procedure is based on a slotted ALOHA approach, which is commonly utilized by
modern wireless communication systems. When accessing the UMTS network, several factors must be considered.
The channel which is utilized, the Random Access Channel (RACH), is a shared channel. Because of this, the possibility of collisions from
multiple user access attempts is possible. In addition, all uplink transmissions result in co-channel interference and therefore require
stringent power control to minimize this interference.
However, since the RACH does not use closed loop power control, the UE must estimate the power required to transmit the RACH message.
The goal of the Random Access Procedure is to minimize the chance of collisions, and to estimate the UE transmit power so that interference
to other UEs is minimized. However, these goals must be achieved while minimizing system access time.
Random Access Procedure may happen

in the following typical scenarios:
Attach and detach

LA update and RA update
Signaling connection for services
Page 48
To achieve the goals of Random Access Proceudre, the UE initially sends test messages (i.e. preambles) on the Physical Random Access
Channel (PRACH), prior to sending the RACH message (e.g. the RRC Connection Request message).
The preamble messages are sent in predefined slots known as Access Slots. The PRACH Access Slot format, and its relation to the
Acquisition Indication Channel (AICH) slots, is illustrated as below. There are 15 defined Access slots, divided into two access slot sets,
every 20 ms. There are 8 access slots (0-7) in access slot set 1, and 7 access slots (8-14) in access slot set 2. In addition, there are 15
corresponding AICH slots which are time offset by p-a. The AICH only exists on the physical layer and is used solely to acknowledge
preambles sent on PRACH Access Slots.
RACH Access Slots

Access slot set 1 holds PRACH access slots 1 to 7, i.e. the PRACH access slots, whose corresponding AICH access slots begin in a
P-CCPCH with a SFN modulo 2 = 0.
Access slot set 2 holds PRACH access slots 8 to 15, i.e. the PRACH access slots, whose corresponding AICH access slots begin in
a P-CCPCH with a SFN modulo 2 = 1.
Page 49
Random Access Timing
The UE sends one preamble in uplink access slot n.
It expects to receive a response from the Node B in the downlink (AICH) access slot n, p-a chips later on.
If there is no response, the UE sends the next preamble p-p chips after the first one. The maximum numbers of preambles in one preamble
access attempt can be set between 1 and 64. The number of PRACH preamble cycles can be set between 1 and 32.
The AICH_Transmission_Timing (AICHTxTiming) parameter is broadcase in SIB5 & SIB6.
when AICH_Transmission_Timing is set to 0

p-p,min = 15360 chips (3 access slots)
p-a = 7680 chips
p-m = 15360 chips (3 access slots)
when AICH_Transmission_Timing is set to 1, then

p-p,min = 20480 chips (4 access slots)
p-a = 12800 chips
p-m = 20480 chips (4 access slots)
Page 50
RACH Sub-channels
RACH Sub-channels
Some of the PRACH access slots may be reserved for UEs containing higher priority Access Class (AC) USIMS, such as those for
emergency personnel. This functionality is accomplished by means of RACH sub-channels. By reserving one or more RACH
sub-channels to a specific Access Service Class (ASC), the likelihood of a successful access can be improved for members of that AC.
A RACH sub-channel is defined as a subset of the PRACH access slots. There are a total of 12 sub-channels with each sub-channel
consisting of 5 access slots. Since 15 access slots span 2 radio frames, the 12 sub-channels repeat every 60 access slots (or 8 radio
frames). Each sub channel consists of 5 access slots which include the access slot corresponding to the sub channel number as well
as the 12th access slot relative to the sub channel number. The below table defines the PRACH access slot to RACH sub-channel mapping .
Sub-channel 0 consists of 5 access slots: 0 (frame 1), 12 (frame 2), 9 (frame 3), 6 (frame 4), and 3 (frame 6). Here access slot 0
corresponds to the sub channel number 0, and the 12 th access slot for this sub channel would be access slot 12. Sub-channels 1-11
are similarly distributed across the 8 radio frames.
Page 51
Access Class and Access Service Class
Access Service Class (ASC)
Access Service Classes (ASC) were introduced to allow priority access to the PRACH resources, by associating ASCs to
specific access slot spaces (RACH sub-channels) and signatures. 8 ASC can be specified by the operator.
The UE determines the ASC and its associated resources from SIB5 and SIB7. The PRACH resources include RACH access slots and
preamble signatures, which can be classified into several ASCs, so as to provide RACH applications with different priorities.
The ASCs range from 0 to 7, and the quantity of ASCs is 8. "0" indicates the highest priority and "7" indicates the lowest priority.
Access Class (AC)

16 Access Classes (0-15) are defined for UMTS and GSM users (3GPP TS 22.011).
Access Classes 0 to 9 are equivalent and are randomly allocated to all UEs such that every UE belong to one of these ten Access Classes.
The access class assigned to a user is stored in their SIM/USIM. In addition to these first 10 Access Classes, UEs may also belong to one
or more of the 5 special Access Classes (11-15). These special Access Classes are allocated to high priority users as follows:
Class 15: PLMN Staff;
Class 14: Emergency Services;
Class 13: Public Utilities (e.g. water/gas suppliers);
Class 12: Security Services;
Class 11: For PLMN Use
Access Class 10 indicates whether or not network access for Emergency Calls is allowed for UEs with access classes 0 to 9 or without an
IMSI. For UEs with access classes 11 to 15, Emergency Calls are not allowed if both "Access class 10" and the relevant Access Class
(11 to 15) are barred. Otherwise, Emergency Calls are allowed.
The 16 Access Classes are mapped to 7 Access Service Classes (ref 3GPP 25.331, Section 8.5.13). At the RRC layer, the set of available
signatures and the set of available RACH sub-channels for each Access Service Class (ASC). In this manner, specific RACH signatures and
RACH sub-channels can be reserved for specific Access Classes.
Page 52
RACH Sub-channels and ASC
Example
If UE1 can use all sub channels(0 ~ 11).
If UE2 can only use sub channels (0~2). How to use Access Slots of each
p-p: time interval between two PRACH preambles. sub channels ?

p-p
Page 53
Preamble Signature
Preamble Signature
The set of Preamble Signatures consist of 16 codes, each 16 bits long.
The selected 16 bit code is repeated 256 times and combined with a preamble scrambling code, to form the transmitted preamble code.
Preamble Value of n
signature 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
P0(n) 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
P1(n) 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1
P2(n) 1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 1 1 -1 -1
P3(n) 1 -1 -1 1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 1
P4(n) 1 1 1 1 -1 -1 -1 -1 1 1 1 1 -1 -1 -1 -1
P5(n) 1 -1 1 -1 -1 1 -1 1 1 -1 1 -1 -1 1 -1 1
P6(n) 1 1 -1 -1 -1 -1 1 1 1 1 -1 -1 -1 -1 1 1
P7(n) 1 -1 -1 1 -1 1 1 -1 1 -1 -1 1 -1 1 1 -1
P8(n) 1 1 1 1 1 1 1 1 -1 -1 -1 -1 -1 -1 -1 -1
P9(n) 1 -1 1 -1 1 -1 1 -1 -1 1 -1 1 -1 1 -1 1
P10(n) 1 1 -1 -1 1 1 -1 -1 -1 -1 1 1 -1 -1 1 1
P11(n) 1 -1 -1 1 1 -1 -1 1 -1 1 1 -1 -1 1 1 -1
P12(n) 1 1 1 1 -1 -1 -1 -1 -1 -1 -1 -1 1 1 1 1
P13(n) 1 -1 1 -1 -1 1 -1 1 -1 1 -1 1 1 -1 1 -1
P14(n) 1 1 -1 -1 -1 -1 1 1 -1 -1 1 1 1 1 -1 -1
P15(n) 1 -1 -1 1 -1 1 1 -1 -1 1 1 -1 1 -1 -1 1
Page 54
PRACH Preamble
In the PRACH preamble, a random preamble code is used. This preamble code is composed from a
Preamble Scrambling Code
Preamble Signature
There are 8192 preamble scrambling codes, which are constructed from the long scrambling code sequences. The PRACH preamble
scrambling codes are organised in 512 groups, with each group holding 16 members.
The preamble scrambling code selected is one of 16 associated with the CPICH Scrambling code of the cell being accessed. In this manner,
the Node B can identify preambles targeted for it, and ignore preambles intended for other Node Bs.
Page 55
START
Choose a RACH sub channel from

available ones
Get available signatures
Set Preamble Retrans Max
Set Preamble_Initial_Power
Send a preamble
No AI
Choose a access slot again Check the corresponding AI
Get positive AI Get negative AI

Choose a signature and
increase preamble transmit power Change message part power by p-m
based on preamble power
The counter of preamble retransmit
Subtract by 1, Commanded preamble power Send the corresponding message part
increased by Power Ramp Step
Y Counter > 0 & Commanded Set physical status to be RACH

message transmitted Set physical status to be Nack
Preamble power- maximum allowed power on AICH received
< 6 dB
N
Report the physical status to MAC
Set physical status to be Nack
on AICH received Page 56
END
1. Derive the available uplink access slots, in the next full access slot set, for the set of available RACH sub-channels
within the given ASC. Randomly select one access slot among the ones previously determined. If there is no access slot available
in the selected set, randomly select one uplink access slot corresponding to the set of available RACH sub-channels within the
given ASC from the next access slot set. The random function shall be such that each of the allowed selections is chosen with
equal probability.
2. Randomly select a signature from the set of available signatures within the given ASC.
3. Set the Preamble Retransmission Counter to Preamble_ Retrans_ Max.
4. Set the preamble transmission power and Commanded Preamble Power to Preamble_Initial_Power.
5. Transmit a preamble using the selected uplink access slot, signature, and preamble transmission power.
6. If no positive or negative acquisition indicator (AI +1 nor 1) corresponding to the selected signature is detected in the downlink
access slot corresponding to the selected uplink access slot:
A: select the next available access slot in the set of available RACH sub-channels within the given ASC;
B: select a signature;
C: increase the preamble transmission power and Commanded Preamble Power by Power Ramp Step, whereas the
maximum value of preamble transmission power is equal to MaxallowedUlTxPower.
D: Decrease the Preamble Retransmission Counter by one. If the Preamble Retransmission Counter > 0 and Commanded
Preamble Power maximum allowed power < 6dB, then repeat from step 5. Otherwise exit the physical random access
procedure.
7. If a negative acquisition indicator corresponding to the selected signature is detected in the downlink access slot corresponding to
the selected uplink access slot, exit the physical random access procedure.
8. If a positive acquisition indicator corresponding to the selected signature is detected, UE transmits the random access message
three or four uplink access slots after the uplink access slot of the last transmitted preamble. After that, exit the physical random
access procedure.
Page 57
Random Access Parameters

Range Range Value
This parameter specifies the transmission timing

information of an AICH relative to uplink PRACH.
AICH "0" indicates that there are 7680 chips offset
UAICH AICHTxTiming Transmission between the access preamble of the PRACH and 0~1 0~1 None 1
Timing AICH. "1" indicates that there are 12800 chips
offset between them. For detailed information of
this parameter, refer to 3GPP TS 25.211.
Page 58
Table of Contents

Page 59
Power Control
Any WCDMA system is limited by interference and it is important to minimize the interference level,
since the lower the interference, the better the network capacity and quality is.
The purpose of Power control is to allow as many users as possible into the WCDMA network, while keeping the interference caused by
these users to a minimum. Power control aims at using the minimum signal to interference ratio (SIR) required for the quality of the
connection to remain sufficient. Power control provides protection against large changes in shadowing, immediate response to fast changes
in signal and interference levels. It is also needed to cope with the near-far problem found in WCDMA systems, and to bring the SIR back
close to the target SIR as fast as possible after each transmission gap in compressed mode. Power Control works on a connection basis.
The two main capabilities of Power Control in a WCDMA system are as follows:
To maintain the quality of connections (including common channels needed, for example, for call access)
To minimize the transmitted power in both uplink and downlink.
There are three different types of power control in UMTS

Open Loop: This power control is used when no feedback mechanism is
possible. An estimate of the required power is made from measurements
and system information. This is used for initial network access and finding
initial power settings during dedicated mode.
Closed Inner Loop: This power control technique uses a fast feedback
mechanism to request an increase or decrease in output power based on the
difference between the target and measured SIR. The feedback is provided
via Transmit Power Control (TPC) bits on the DPCCH channel 1500 times per
second. Hence Inner Loop Power Control is also called Fast Cosed Loop
Power Control.
The key difference between closed and open loop is the feedback cycle.
Closed Outer Loop: This power control is used to set the target SIR that is Closed loop relies on feedback from the receiving node to adjust the
used during inner loop power control. For downlink power control this is set in power at the transmitting node. Open loop has no feedback on the
the UE by an algorithm that is proprietary to the UE manufacturer. For uplink amount to increase or decrease its transmit power.
power control it is set by the RNC. Page 60
Power Control
Because of channel fading in mobile communication system, the radio signal is deteriorated and fluctuated, the fast power control become
one key technology to resist this phenomenon.
In this figure, the channel fading is compensated by the transmitting power, which is adjusted by the fast power control, so the receiving
power is almost constant and the radio propagation condition is improved.
Receiving power
Transmission
power
Channel
Fading
Page 61
Power Control on DL Common Channels
Fixed power
The power on downlink common channels is fixed and can be configured on the RNC.
PCPICH: The transmission of the PCPICH determines the actual cell

size. Its power PCPICHPower is set to an absolute value and the Closed Loop Power Control
power level of every other downlink channel is expressed as an offset Open Loop
Physical No Power
Power Inner Loop Outer Loop Power
relative to it. Channel
Control
Control
Power Control Control
PCCPCH: The PCCPCH carries the broadcast channel (BCH), which PRACH
is broadcast time multiplexed with the SCH. The parameter BCHPower
DPCCH
determines the power and is expressed as on offset of the PCPICH
power. DPDCH
PCPICH
SCH: The SCH consists of a primary SCH (P-SCH) and a secondary
SCH (S-SCH), used in the cell search procedure in the UE. Their SCH
powers are set as PSCHPower for P-SCH and SSCHPower for PCCPCH
S-SCH, and are expressed as offsets of the PCPICH power.
SCCPCH
AICH: The AICH carries the acquisition indication (AI), which is the AICH
response to the PRACH preambles. The AICH is not continuously
broadcast in the cell. Its power is set by the parameter PICH
AICHPowerOffset is expressed as on offset of the PCPICH power.
PICH: The PICH carries the paging indicators, which tell UEs
SCCPCH carrying FACH: When the SCCPCH carries the FACH
belonging to specific paging groups to listen to the paging
transport channel. The parameter MaxFachPower determines the
channel. The PICH power is set by the parameter
power and is expressed as on offset of the PCPICH power.
PICHPowerOffset relative to the PCPICH power.
SCCPCH carrying PCH: When the SCCPCH carries the PCH transport
channel. The parameter PCHPower determines the power and is
expressed as on offset of the PCPICH power. The SCCPCH uses
discontinuous transmission (DTX) to halt power transmission when
there is no payload. Page 62
Parameters

Range Range Value
Max Transmit Power of Sum of the maximum transmit power of all DL channels in a cell. For
UCELL MaxTxPower 0~500 0~50 0.1dBm 430
Cell detailed information of this parameter, refer to 3GPP TS 25.433.
TX power of the P-CPICH in a cell. The transmit power of any other

channel is an offset from the P-CPICH power. P-CPICH transmit power is
related to the downlink coverage defined during network planning.
If the value of this parameter is too small, it will directly influence the
UPCPICH PCPICHPower PCPICH Transmit Power downlink pilot coverage range. -100~500 -10~50 0.1dBm 330
If it is too large, the downlink interference will increase, and the transmit
power that can be distributed to the services will be reduced, which will
affect the downlink capacity.
In addition, the configuration of this parameter has influence on the
distribution of handover areas.
Offset of the PSCH or SSCH transmit power from the P-CPICH transmit
power in a cell.The values of PSCHPower and SSCHPower must not be
UPSCH PSCHPower PSCH Transmit Power too large. The parameter values can be adjusted based on the -350~150 -35~15 0.1dB -50
measurement in the actual environment, so that the transmit power of the
synchronization channels satisfies the UE reception and demodulation
requirements.
The transmit power should be enough to ensure that a UE can implement

fast synchronization in most areas of the cell edge. Neither the P-SCH
USSCH SSCHPower SSCH Transmit Power nor the S-SCH comes through channel code spectrum spreading, so they -350~150 -35~15 0.1dB -50
produce more serious interference than other channels, especially for
near-end UEs.
Page 63
Parameters
Range Range Value
Offset of the BCH transmit power from the P-CPICH transmit power in a cell.
BCHPower is set based on the measurement in the actual environment.
If the value of this parameter is too small, the UEs at the cell edge will fail to
UBCH BCHPower BCH Transmit Power -350~150 -35~15 0.1dB -20
receive the system information correctly, and the downlink coverage will be
influenced.
If the value is too large, other channels are affected and the cell capacity will be
reduced.
The offset between the FACH transmit power and P-CPICH transmit power in a
cell.
Set the value of MaxFachPower to a value that is enough to ensure the target
block error rate (BLER). I
Max Transmit Power of
UFACH MaxFachPower f the value of this parameter is too small, the UEs at the cell edge will fail to -350~150 -35~15 0.1dB 10
FACH
receive correctly the services and signaling carried over the FACH, which results
in influence on the downlink coverage.
If it is too large, other channels will be affected and the cell capacity will be
reduced.
Offset of the PCH transmit power from the PCPICH transmit power in a cell.
UPCH PCHPower PCH Power receive paging messages correctly, which will influence cell coverage. -350~150 -35~15 0.1dB -20
reduced.
Difference between the transmit power of PICH and that of PCPICH.

UCHPWROFFSET PICHPowerOffset PICH Power Offset receive paging indicators correctly, which will affect the downlink coverage. -10~5 -10~5 dB -7
reduced.
This parameter specifies the power offset between the transmit power of an
AICH and that of P-CPICH.
UCHPWROFFSET AICHPowerOffset AICH Power Offset -22~5 -22~5 dB -6
receive paging indicators correctly, which will affect the downlink coverage.
reduced
Page 64
Power Control on UL Common Channel
Open Loop Power Control
The power control of the uplink common channel is done using the Open Loop Power control method.
Uplink open loop power control is controlled by the UE.
In a UMTS network, the UE always initiates the RRC connection setup procedure. This is applicable for mobile terminating calls (MTC)
also in which case the network pages the UE, telling it to establish an RRC connection. The UE does this using the Random Access
Procedure.
Before it initiates the Random Access Procedure, the UE has to determine how much power it has to use in the uplink. If a UE uses a
fixed power level for random access, and if it happens to be close to the BTS, then it would block out messages from the UEs farther
away. Therefore the UE must always use the lowest possible transmission power.
The goal of power control during call setup is for the UE to transmit the minimum amount of power required to access the network. At
this time the UE does not know the power required to reach the system, so it estimates the initial preamble power (based on broadcast
information and downlink measurements). If there is no acknowledgement from the NodeB to this initial request (via Acquisition
Indication (AI) sent by the NodeB), the UE will increase its power based on predefined increments and retransmissions until it is heard.
This procedure is known as Power Ramping and because of the limited feedback provided by the network is termed Open Loop
Power Control. The UE uses an equation to estimate the initial preamble transmit power on the Physical Random Access Channel
(PRACH), based on CPICH received power and System Information (broadcast in the cell).
In downlink Open Loop Power Control, the initial transmission power is calculated according to the downlink path loss between
NodeB and UE.
In uplink ,since the uplink and downlink frequencies of WCDMA are in the same frequency band, a significant correlation exists
between the average path loss of the two links. This make it possible for each UE to calculate the initial transmission power required in
the uplink based on the downlink path loss.
However, there is 90MHz frequency interval between uplink and downlink frequencies, the fading between the uplink and downlink is
uncorrelated, so the open loop power control is not absolutely accurate.
Page 65
PRACH Open Loop Power Control
The process of power control on the PRACH is as follows:
1. UE transmits the 1st preamble to the NodeB to start an access process, the preamble initial power is obtained from the calculation on
next pages.
2. If no Acquisition Indicator (AICH) is received by the UE, a preamble ramping procedure starts. To avoid collisions, the UE must wait
for a time between two consecutive preambles. The waiting time is configured by AICHTxTiming on the RNC. The power of preamble
is increased for each retransmission by a power ramp step configured by PowerRampStep on the RNC.
3. If the UE receives a negative acquisition indicator on the AICH, the UE waits for a certain period and then initiates the random
access procedure again. This period is called the back-off delay. The parameters NB01min and NB01max define the lower and
upper limits of the back-off delay. If the value of NB01min is equal to that of NB01max, it means that the retransmission period of the
preamble part is fixed.
A preamble ramping procedure consists of several preamble ramping cycles, which cannot exceed Mmax. In each cycle, the UE
retransmits the preamble until the UE receives the acquisition indicator or the number of retransmissions has reached
PreambleRetransMax.
Page 66
4. If the UE receives a positive acquisition indicator, the UE exits the random access procedure,
sets the power for the message part, and transmits the message part after a period configured by AICHTxTiming.
The message part consists of two parts: control part and data part. The power of the control part is the same as the power of the
last transmitted preamble plus a value defined by PowerOffsetPpm. PowerOffsetPpm must be set for each instance of PRACH TFC.
It is recommended that the value of PowerOffsetPpm be set to -3 dB corresponding to the TFC for signaling transmission and be set
to -2 dB corresponding to the TFC for service transmission.
If the value of PowerOffsetPpm is set too small, it is likely

that the signaling or the service data carried over the RACH
cannot be correctly received, which affects the uplink
coverage.
If the value is set too large, the uplink interference is
increased, and the uplink capacity is affected.
The power of the data part is calculated with the following formula:
where
Pdata = Pcontrol x (d/c)2 Pcontrol is the power for the control part.
d is the power gain factor for the data part. The value is defined by GainFactorBetaD.
c is the power gain factor for the control part. The value is defined by GainFactorBetaC.
The transmit power on the PRACH cannot be greater than the maximum allowed uplink transmit power. This maximum power is limited by
the following parameters configured on the RNC:
MaxUlTxPowerforConv (conversational)
MaxUlTxPowerforBac (background)
MaxUlTxPowerforInt (interactive)
MaxUlTxPowerforStr (streaming) Page 67
MaxAllowedUlTxPower
The UE uses an equation to estimate the initial preamble transmit power on the Physical Random Access Channel (PRACH),
based on CPICH received power and System Information (broadcast in the cell).
Assumption : uplink path loss = downlink path loss.
Preamble_Initial_Power = PCPICHPower- CPICH_RSCP + UL interference + Constantvalue
where
PCPICHPower defines the P-CPICH transmit power in a cell.
CPICH_RSCP is the received signal code power of the P-CPICH.
UL interference indicates the uplink RTWP.
Constantvalue for calculating the initial transmit power compensates for the RACH processing gain. It is broadcast in SIB 5.
Normally in the initial stages of network lifecycle,

coverage is limited, constant value could be set
greater (-16 dB or -15dB) so the preamble
message can be received easier by UTRAN.
The power ramp step could also be set greater.
Page 68
PRACH Open Loop Power Control Parameters
GUI Value Actual Value

MO Parameter ID Parameter Name Parameter Description Unit Baseline Value
Range Range
This parameter specifies a constant used at calculation of the initial

transmit power of the first preamble, to be used in the random
access procedure.
The formula is as follows: Preamble_Initial_Power = Primary
Constant Value for CPICH DL TX power-CPICH_RSCP + UL interference + Constant
UPRACHBASIC Constantvalue Calculating Initial TX Value. Where, -35~-10 -35~-10 dB -20
Power Preamble_Initial_Power is the preamble initial TX power, Primary
CPICH DL TX power is the downlink transmit (TX) power of
PCPICH, CPICH_RSCP is the receive signaling code power of the
PCPICH measured by UEs, and UL interference is the uplink
interference. For detailed information of this parameter,.
Max Preamble The maximum number of preambles transmitted in a preamble

UPRACHBASIC PreambleRetransMax 1~64 1~64 None 20
Retransmission ramping cycle. For detailed information of this parameter,.
The power ramp step of the random access preambles transmitted

UPRACHBASIC PowerRampStep Power Increase Step before the UE receives the acquisition indicator in the random 1~8 1~8 dB 2
access process. For detailed information of this parameter.
Random Back-off
URACH NB01min Lower limit of random access back-off delay. 0~50 0~50 frame 0
Lower Limit
Random Back-off
URACH NB01max Upper limit of random access back-off delay. 0~50 0~50 frame 0
Upper Limit
The parameter specifies the maximum number of preambles to be

URACH Mmax Max Preamble Loop 1~32 1~32 None 8
used in one preamble ramping cycle.
In signaling transmission mode,

The power offset between the last access preamble and the set PowerOffsetPpm
UPRACHTFC PowerOffsetPpm Power Offset message control part. The power of the message control part can -5~10 -5~10 dB to -3;
be obtained by adding the offset to the access preamble power. in service transmission mode,
set PowerOffsetPpm to -2.
This parameter specifies the power assignment factor of the
UPRACHTFC GainFactorBetaC Gain Factor BetaC 1~15 1~15 None None
control part.
UPRACHTFC GainFactorBetaD Gain Factor BetaD The power occupancy factor of the data part. 0~15 0~15 None 15
Page 69
Power Control on Dedicated Channels
The power control of dedicated channels is performed by a combination of the
Open Loop Power Control ,Outer loop power control and the inner loop power control procedures.
Dedicated channels consist of the DPCH in the uplink and the DPCH and the F-DPCH in the downlink. Uplink DPCHs consist of the
uplink DPCCH and the uplink DPDCH, and they use different OVSF codes. Downlink DPCHs consist of the downlink DPCCH and
DPDCH, and they use the same OVSF code by time division multiplexing.
Open loop power control provides initial power of channels.

Inner loop power control adjusts channel power by comparing the SIR of the received signal with the SIRtarget.
Outer loop power control adjusts the SIRtarget by comparing the BLER target and the BLER of the received DCH.
Open Loop Power Control on DPCH

According to the RRC connection establishment
procedure, after RNC received the RRC CONNECTION
REQUEST message, if the RNC decided to use
Dedicated Channel to bear the RRC connection, and the
RNC told NodeB to set up the radio link for UE, then Iub
interface resources is established between NodeB and
RNC.
When DCH-FP of Iub interface finished downlink and

uplink synchronization, the downlink DPCH starts to
transmit, and downlink DPCH initial transmission power
is calculated through open loop power control.
After RNC sent the RRC CONNECTION SETUP

message, UE will try to synchronize with NodeB,
and the uplink DPCH starts to transmit, here uplink
DPCH initial transmission power is calculated
through open loop power control.
Page 70
Open Loop Power Control on DL DPCH
Initial Power of Downlink DPDCH
RNC uses the P-CPICH power, the traffic rate requested by the UE, measured Ec/No on CPICH and the downlink transmitted carrier
power as input in calculating the initial power of downlink DPDCH as the folmula below.
The power of the downlink DPDCH is limited for each radio link by RlMaxDlPwr and RlMinDlPwr. The values of RlMaxDlPwr and
RlMinDlPwr are different for different data rates of RABs.
where:
Pinit is initial transmit code power for downlink DPDCH.
PCPICH is the PCPICH power in a cell. The value is configured by the PCPICHPower parameter on the RNC.
R is the traffic rate requested by the UE and W is the chip rate (3.84 Mcps).
(Eb/No)DL is the Eb/No target of the downlink DPDCH used to ensure the service quality. Eb is the energy of a signal information bit
and No is the noise spectral density. The RNC estimates a value of Eb/No target dynamically based on cell environment type and BLER
target. We can consider Eb/No target as SIR Target.
(Ec/No)CPICH is the ratio of received energy per chip to noise spectral density of the CPICH received by the UE, UE sends the
measurement value to RNC in RRC connection request message.
is the orthogonal factor in the downlink. The value is fixed to 0.
Ptotal is the downlink transmitted carrier power measured on the NodeB and reported to the RNC.
Based on the above description for parameters in formula, we can change formula to the following, the change help us to
understand how to calculate the downlink DPDCH initial power:
Page 71
Initial Power of Downlink DPCCH
The downlink DPCCH consists of three fields: TFCI, TPC, and pilot. Their power is set as the offset reference to the power of the
downlink DPDCHs.
The downlink power on the DPCCH and its associated DPDCHs is simultaneously regulated. Therefore, power control adjusts the power
of the DPCCH and DPDCHs with the same step, and the power offset between the DPCCH and the DPDCH keeps constant.
Power offsets between the DPCCH and the DPDCH in the downlink are identical for all TFCs in the TFCS, whereas in the uplink the
power offsets are TFC-dependent.
The initial power setting for the dedicated control channels (DPCCH) is
calculated using the following equations.
P_DL_DPCCH_TFCI = (P_DL_DPDCH + PO1)

P_DL_DPCCH_TPC = (P_DL_DPDCH + PO2)
P_DL_DPCCH_PILOT = (P_DL_DPDCH + PO3)
Where:
P_DL_DPCCH_TFCI is the Initial output power for the DPCCH TFCI field.
PO1 is the power offset between the data field and the TFCI field of the downlink
DPCCH, expressed in dB.
P_DL_DPCCH_TPC is the initial output power for the DPCCH TPC field.
PO2 is the power offset between the data field and the TPC field of the downlink
P_DL_DPCCH_PILOT is the initial output power for the DPCCH Pilot field.
PO3 is the power offset between the data field and the Pilot field of the downlink
The power offsets of TFCI, TPC and pilot fields of the DPCCH reference to the
power of DPDCHs are fixed at 0 dB, 3 dB, and 3 dB, respectively.
Page 72
Parameters
Range Range
This parameter specifies the maximum DL RL power to be assigned.
RL Max DL TX This parameter should fulfill the coverage requirement of the network
UCELLRLPWR RlMaxDlPwr -350~150 -35~15 0.1dB None
power planning, and the value is relative to [PCPICH transmit power]. For detailed
information of this parameter, refer to 3GPP TS 25.433.
This parameter specifies the minimum DL RL power to be assigned.

This parameter should consider the maximum downlink transmit power and
RL Min DL TX the dynamic range of power control, and the value is relative to [PCPICH
UCELLRLPWR RlMinDlPwr -350~150 -35~15 0.1dB None
power transmit power]. Since the dynamic range of power control is set to 15 dB,
this parameter is recommended as [RL Max DL TX power] - 15 dB. For
detailed information of this parameter, refer to 3GPP TS 25.433.
CN Domain DLSF Max BitRate(bps) RlMaxDlPwr RlMinDlPwr

Baseline Setting
D128 12200 0 -15
D64 23850 0 -15
D64 28800 -2 -17
CS_DOMAIN D64 32000 -2 -17
D32 56000 0 -15
D32 57600 -1 -16
D32 64000 3 -12
D256 0 -2 -17
D128 8000 -4 -23
D128 16000 -2 -21
D64 32000 0 -19
PS_DOMAIN D32 64000 2 -17
D16 128000 2 -15
D16 144000 2 -15
D8 256000 4 -13
D8 384000 4 -11
Page 73
Open Loop Power Control on UL DPCH
The uplink open loop power control on the DPCH is to calculate the initial power of the first DPCCH.
The initial power of the DPDCH is calculated based on the power offset between the DPCCH and the DPDCH.
Initial Power of Uplink DPCCH

where
The UE calculates the initial power with the following formula:
DPCCH_Initial_Power is the initial power.
DPCCH_Power_Offset is provided by the RNC and sent to the UE.
DPCCH_Initial_Power = DPCCH_Power_Offset - CPICH_RSCP CPICH_RSCP is the received signal code power of the P-CPICH.
The DPCCH_Power_Offset is calculated by the RNC with the following formula:
DPCCH_Power_Offset = PCPICHPower + Uplink interference + DefaultConstantValue
where
DPCCH_Power_Offset is the power offset of the DPCCH.
PCPICHPower defines the P-CPICH transmit power in a cell. This value is broadcast in SIB 5.
Uplink interference is the uplink RTWP measured by the NodeB and sent to the UE through the SIB 7.
DefaultConstantValue is used to set the power offset of the DPCCH to a conservative level to avoid excessive uplink interference.
Power of Uplink DPDCH

The power of the uplink DPDCH is set as a power offset (d/c) reference to the uplink DPCCH. The uplink DPCCH and DPDCHs are
transmitted through different channel codes. To meet a given QoS requirement on the transport channels, different TFCs use different
power offsets.
The RNC has a set of reference values (c,ref and d,ref) that are stored for each predefined radio access bearer (RAB) or signaling radio
bearer (SRB). c,ref and d,ref can be configured by BETAC and BETAD on the RNC.
The RNC calculates a new power offset for each TFC based on the reference values dynamically and sends the power offset to the UE.
In an RAB combination, all the radio bearers use the reference values of the bearer who has the maximum bit rate. For example, for the
combination of 3.4 kbit/s SRB service, 384 kbit/s background service, and 12.2 kbit/s AMR service, the reference power offset values
applied are those belonging to the 384 kbit/s background radio bearer. Page 74
Open Loop Power Control on UL DPCH
Parameters
Range Range
Power occupancy of the control part of reference TFC. For details,

UTYPRABBASIC BetaC Reference BetaC 1~15 1~15 None None
see 3GPP TS 25.214.
Power occupancy of the data part of reference TFC. For details,

UTYPRABBASIC BetaD Reference BetaD 1~15 1~15 None None
see 3GPP TS 25.214.
RABINDEX APPLIEDDIRECT CNDOMAINID TRAFFICCLASS MAXBITRATE BETAC BETAD

Example Setting
0 APPLIED_ON_BOTH CS_DOMAIN CONVERSATIONAL 12200 12 15
1 APPLIED_ON_BOTH CS_DOMAIN CONVERSATIONAL 23850 12 15
40 APPLIED_ON_BOTH PS_DOMAIN INTERACTIVE 0 15 11
70 APPLIED_ON_BOTH PS_DOMAIN BACKGROUND 0 15 11
78 APPLIED_ON_BOTH PS_DOMAIN BACKGROUND 384000 4 15 Page 75
Uplink Inner Loop Power Control
Uplink Inner Loop Power Control Procedures :
1) RNC sends SIRtar (target SIR) to NodeB and then NodeB compares SIRmea (measured SIR) with SIRtar:
If the estimated SIR is greater than the target SIR, NodeB sends TPC 0 to UE on downlink DPCCH TPC field.
Otherwise, NodeB sends TPC 1 to UE.
2) After reception of one or more TPC, UE shall derive a single TPC_cmd (TPC command, with value among -1, 0, 1):
Two algorithms could be used by the UE for deriving the TPC_cmd, those are PCA1 and PCA2 (Power Control Algorithm).
For UE is in soft handover state, more than one TPC is received, so firstly multiple TPC_cmd is combined.
3) The UE adjusts the transmit power according to the TPC command.
There are two types of Inner Loop Power Control algorithms: PCA1 and PCA2. The UE uses the algorithms to translate the
received TPC commands. The RNC can select the algorithm based on the configuration of PwrCtrlAlg and inform the UE of the
selected algorithm.
Comparison between two algorithms PCA1 & PCA2

Difference in Control Rate
TPC command processing algorithm 1: power control rate is 1500Hz;
TPC command processing algorithm 2: power control rate is 300Hz.
Application scenario
When the UE moves at a high speed (80km/h), fast fading cannot be traced in fast inner loop power control (one time slot
should be longer than the wavelength) and negative gain occurs.
In this situation, algorithm 2 is suggested. For example, algorithm 2 is recommended for the cells covering a express way.
Page 76
Uplink Inner Loop Power Control
4) When using the PCA1, the UE adjusts the uplink transmit power for every timeslot. When using the PCA2, the UE adjusts the uplink
transmit power in a 5-timeslot cycle. The power increment/reduction is calculated with the following formula:
DPCCH =TPC TPC_cmd
Where :
DPCCH is power increment/reduction on DPCCH
TPC_cmd is calculated by the PCA1 or PCA2 according to the TPC
TPC is the step of power control.
For PCA1, its determined by UlTpcStepSize. For PCA2, the step size is fixed to 1dB.
5) This adjustment is executed on the DPCCH, then associated DPDCH transmit power is calculated according to DPDCH / DPCCH power
ratio d / c.
Pdpdch = Pdpcch ( d / c)2
Page 77
Uplink Inner Loop Power Control PCA1
PCA1 with Single Radio Link

When UE has single radio link, only one TPC will be received in each slot. In this case, the value of TPC_cmd shall be derived by
PCA1 as follows:
If the received TPC is equal to 0, then TPC_cmd for that slot is -1;
If the received TPC is equal to 1, then TPC_cmd for that slot is 1.
According to DPCCH channel structure, there are 15 time slots in a 10ms radio frame, and the control is performed once in each
time slot, so the frequency of uplink inner loop PCA1 is 1500Hz.
PCA1 with Soft Handover

On the NodeB side, there are two phases during the soft handover state:
Uplink synchronization phase
The NodeB should send durative TPC = 1 to the newly-added RL before successful uplink synchronization.
Multi-radio link phase
Each cell will estimate the SIR individually and the generate TPC individually.
Especially , when UE is in softer handover state, it means UE has radio links to the same NodeB, in this case
these RLs(Radio Link) belong to the same RLS(Radio Link Set), and the all TPCs are the same from each RL.
Therefore , when UE enters soft handover state, the UE may receive different TPC from different RLS, and the UE should combine
these TPCs before deriving TPC_CMD.
Page 78

When UE is in soft handover state, multiple TPC will be received in each slot from different cells in the active set. UE will generate
the TPC_cmd by PCA1 as follows:
1. Combine the TPCs from the same RLS and derive the Wi
When the RLs (Radio Link) are in the same RLS (Radio Link Set), they will transmit the same TPC in a slot. In this case, the
TPCs from the same RLS shall be combined into one. After combination, UE will obtain a soft symbol decision Wi for each
RLSi.
2. Combine the TPCs from different RLSs and derive the TPC_cmd
UE derives TPC_cmd, it is based on a function and all the N soft symbol decisions Wi:
TPC_cmd = (W1, W2, WN),
Where TPC_cmd can only take the values 1 or -1.
In Huawei implementation, the function shall fulfil the following criteria:

-If the TPCs from all RLSs are 1, the output of shall be equal to 1;
-If one TPC from any RLS is 0, the output of shall be equal to -1.
Page 79
PCA2 with Single Radio Link

When UE has single radio link, only one TPC will be received in each slot. In this case, the value of TPC_cmd shall be derived by PCA2
as follows:
For the first 4 slots of a set, TPC_cmd = 0.
For the fifth slot of a set, UE make the decisions on as follows:
If all 5 TPCs within a group are 1, then TPC_cmd = 1 in the 5th slot;
If all 5 TPCs within a group are 0, then TPC_cmd = -1 in the 5th slot;
Otherwise, TPC_cmd = 0 in the 5th slot.
According to DPCCH channel structure, there are 15 time slots in a 10ms radio frame, and the control is performed once in each 5-slot
group, so the frequency of uplink inner loop PCA2 is 300Hz.
Page 80

When UE is in soft handover state, multiple TPC will be received in each slot from different cells in the active set. UE will generate the
TPC_cmd by PCA2 as follows:
1. Combine the TPC from the same RLS

When the RLs are in the same RLS, they will transmit the same TPC in a slot. In this case, the TPCs from the same RLS shall be
combined into one.
2. Calculate the TPC_tempi for each RLS

UE derives TPC_tempi through the same way, as follows:
For the first 4 slots of a group, TPC_tempi = 0.

For the 5th slot of a group:
-If all 5 TPCs within a group are 1, then TPC_tempi = 1 in the 5th slot;
-If all 5 TPCs within a group are 0, then TPC_tempi = -1 in the 5th slot;
-Otherwise, TPC_tempi = 0 in the 5th slot.
3. Calculate the TPC_cmd

UE derives TPC_cmd through the following criteria:
-If any TPC_tempi is equal to -1, TPC_cmd is set to -1;
-If , TPC_cmd = 1;
-Otherwise, TPC_cmd = 0.
Page 81
Downlink Inner Loop Power Control
Downlink Inner Loop Power Control Procedures :
1) Basically the downlink Inner Loop Power Control process is similar with uplink, UE L3 sends SIRtar to UE L1 and then UE L1
compares SIRmea with SIRtar:
If the SIRmea is greater than the SIRtar, UE sends TPC 0 to NodeB on uplink DPCCH TPC field.
Otherwise, UE sends TPC 1 to the NodeB.
2) The UE shall check the downlink power control mode before generating the TPC, two algorithm DPC_MODE 0 and DPC_MODE 1
could be used by UE to derive the TPC.
3) Upon receiving the TPC, if the DPC_MODE is 0 (SINGLE_TPC), the NodeB shall use the TPC to generate the TPCest(k). If the
DPC_MODE is 1(TPC_TRIPLET_IN_SOFT), the NodeB shall use the three continuous TPCs received to generate the TPCest(k).
4) Then The NodeB will use TPCest(k) to calculate PTPC(k), PTPC(k) is the downlink power adjustment.
5) In the end, the NodeB shall adjust the current downlink power P(k-1) to a new downlink power P(k), and adjust the power of the
DPCCH and DPDCH with the same amount, since power difference between them is fixed.
Page 82
Downlink Inner Loop Power Control
In the case of softer handover, the NodeB uses the Maximum Ratio Combining (MRC)
algorithm to derive a combined TPC command.The UTRAN calculates the power adjustment with the following formula:
Where:
P(k) is the new downlink power.
P(k) = P(k-1) + PTPC(k) + Pbal(k)
P(k-1) is the current downlink power.
PTPC(k) is the kth power adjustment due to the received TPC of inner loop power control.
Pbal(k) is a correction due to the downlink power balance. In the scenario of a single radio
link, Pbal is equal to 0.
The PTPC(k) is calculated as follows:
If PC_INNER_LOOP_LMTED_PWR_INC_SWITCH of the PcSwitch parameter is set to OFF, then the following formula is used:
If the TPC is equal to 1, the power is increased by TPC.

If the TPC is equal to 0, the power is decreased by TPC.
TPC is determined by FddTpcDlStepSize. TPCest is the estimated TPC.
If PC_INNER_LOOP_LMTED_PWR_INC_SWITCH of the PcSwitch parameter is set to ON, then the following formula is used:
If the TPC is equal to 1, and the sum of sum(k) and TPC is smaller than Power_Raise_Limit, the power is increased by TPC.
If the TPC is equal to 1, and the sum of sum(k) and TPC is larger than or equal to Power_Raise_Limit, the power is not adjusted.
If the TPC is equal to 0, the power is decreased by TPC.
Where:
sum(k) is the sum of inner loop power increment/reduction within 20 timeslots.
Power_Raise_Limit is fixed to 10 dB. Page 83
Inner Loop Power Control Parameters
MO Parameter ID Parameter Name Parameter Description GUI Value Range Actual Value Range Unit Baseline Value
This parameter specifies how the UE interprets the received

Transmit Power Control (TPC) commands, that is, selecting a
UL inner-loop power control algorithm.
Power control algorithm Two different algorithms (denoted ALGORITHM1 and ALGORITHM1, ALGORITHM1,
UFRC PwrCtrlAlg None ALGORITHM1
selection ALGORITHM2) are available, related to this parameter. When ALGORITHM2 ALGORITHM2
the parameter is set to ALGORITHM1, the UE adjusts the
uplink transmit power once every timeslot. When the parameter
is set to ALGORITHM2, the UE adjusts the uplink transmit
power once every five timeslots.
UL Closed Loop Power Step of the closed-loop power control performed on UL DPCH.
UFRC UlTpcStepSize 1~2 1~2 dB 1
Control Step For details, see 3GPP TS 25.214.
STEPSIZE_0.5DB,
Step of the closed-loop power control performed on DL DPCH
FDD DL power control STEPSIZE_1DB,
UFRC FddTpcDlStepSize in Frequency Division Duplex (FDD) mode. For details, see 0.5, 1, 1.5, 2 dB STEPSIZE_1DB
step size STEPSIZE_1.5DB,
3GPP TS 25.214.
STEPSIZE_2DB
DL power control mode.

- SINGLE_TPC, a fast power control mode, indicates that a
SINGLE_TPC, SINGLE_TPC,
unique TPC command is sent in each timeslot on the DPCCH.
- TPC_TRIPLET_IN_SOFT, a slow power control mode,
TPC_TRIPLET_IN TPC_TRIPLET_IN_
indicates that the same TPC command is sent over three
UFRC DpcMode DL power control mode _SOFT, SOFT, None SINGLE_TPC
timeslots. It is applicable to soft handover, and it can decrease
the power deviation.
TPC_AUTO_ADJU TPC_AUTO_ADJUS
- TPC_AUTO_ADJUST, an automatic adjustment mode,
ST T
indicates that the value of DPC_MODE can be modified by
sending the ACTIVE SET UPDATE message to the UE.
Power Control Switch:

PC_INNER_LOOP_LMTED When the switch is on, the limited power increase function is
UCORRMALGOSWITCH PC Inner Loop Limited 0,1 OFF,ON None OFF
_PWR_INC_SWITCH used for DL inner loop power control.
Power switch
Page 84
Outer Loop Power Control
The Outer Loop Power Control (OLPC) is a part of the closed loop power control and the aim is to maintain the communication quality at
the level required by the service bearer through adjustment of the SIR target. This power control acts on each DCH belonging to the same
RRC connection.
The SIR target needs to be adjusted when the UE speed or the multi-path propagation environment changes, so that the communication
quality can remain unaffected.
The adjustment of the SIR target is based on the Block Error Rate (BLER) or Bit Error Rate (BER).
When PC_OLPC_SWITCH of the PcSwitch parameter is set to ON, there are two cases:
If there is data transfer in the uplink, the SRNC adjusts the SIR target based on the BLER.
If there is no data transfer in the uplink, the SRNC adjusts the SIR target based on the BER.
When PC_OLPC_SWITCH of the PcSwitch parameter is set to OFF, the SIR target is fixed and the uplink outer loop power control for all
UEs is deactivated.
Downlink outer loop power control is implemented by the UE. Therefore, downlink outer loop power control is determined by the UE
manufacturer.
The relationship between Inner Loop Power Control and Outer Loop Power Control:
SIRtar should be satisfied with the requirement of decoding correctly. But different multi-path radio environments request different SIRtar.
Therefore, the Outer Loop Power Control can adjust the SIRtar to get a stable BLER in the changeable radio environment.
Page 85
Uplink Outer Loop Power Control
The uplink quality is observed after Macro Diversity Selection Combining (MDC) in the RNC.
Therefore, uplink outer loop power control is performed in the SRNC.
SRNC compares the received block error ratio

(BLER) with the BLERtar.
If the BLERmea is greater than the BLERtar,

the SRNC increases the SIRtar.
If the BLERmea is smaller than the BLERtar,

the SRNC decreases the SIRtar.
SIR target is adjusted per steps. In an outer loop power control adjustment period, the maximum increase/decrease must not exceed a
specified value, and SIR target must not exceed the upper threshold and lower threshold.
For different traffic classes, the adjustment step, maximum increase, maximum decrease, upper threshold, and lower threshold of SIR
target vary. Therefore, such variables are automatically configured by the RNC according to the traffic class.
In case of multi-service:
The maximum value of the SIR target among multiple services is used for the SIR target adjustment.
If one of the services requires increase in the SIR target, the reconfigured SIR target cannot exceed that maximum value.
The maximum value can be decreased only when all the services require decrease in the SIR target.
After adjusting the SIR target, the SRNC sends the new SIR target through Frame Protocol (FP) frames to all NodeBs under the SRNC for
uplink inner loop power control. (The initial SIR target value is service-dependent and is provided by the RNC to the NodeB.) Page 86
Downlink Outer Loop Power Control
Downlink outer loop power control is implemented by the UE. Therefore, this algorithm is UE manufacturer specific.
The information signaled to the UE by the RNC is a quality target for each radio bearer, expressed as a BLER target. Then, depending on
the manufacturer-specific outer loop power control algorithm, an initial SIR target value can be deduced from this BLER value.
Generally, the UE L3(RRC Layer) measures the received BLER and compares it with the BLER tar :
If the BLERmea is greater than the BLERtar, the L3 increases the SIRtar and send it to UE L1(Physical Layer).
If the BLERmea is smaller than the BLERtar, the L3 decreases the SIRtar.
Layer1 of UE
Page 87
Outer Loop Power Control Parameters

Range Range Value
PC_OLPC_SWITCH: When the switch is on, the RNC updates the

Outer Loop Power Control
UCORRMALGOSWITCH PC_OLPC_SWITCH UL SIR TARGET of radio links on the NodeB side through IUB DCH 0,1 OFF,ON None OFF
Switch
FP inband signaling.
Target transmission quality of DCH, that is, target BLER of DCH on

the radio interface if the subflow is carried on DCH. This QoS-
Target value of service related parameter is used by the CRNC to determine the target SIR
UTYPRABOLPC BLERQuality -63~0 5*10^(-7)~1 None None
DCH_BLER value for use in admission and power control. To calculate the value
of this parameter, obtain the result of 10*Lg(BLER) where the BLER
refers to the actual BLER, and then round the result up.
Initial target SIR used in the optimized outer loop power control
UTYPRABOLPC InitSirtarget SIR init target value algorithm. 0~255 -8.2~17.3 0.1dB None
Actual Value = (GUI Value - 82(offset))*0.1.
Maximum target SIR used in the optimized outer loop power control
UTYPRABOLPC MaxSirtarget Maximum SIR target algorithm. 0~255 -8.2~17.3 0.1dB None
Minimum target SIR used in the optimized outer loop power control
UTYPRABOLPC MinSirtarget Minimum SIR target algorithm. 0~255 -8.2~17.3 0.1dB None
This parameter specifies the adjustment period of outer-loop power The same
UTYPRABOLPC SirAdjustPeriod OLPC adjustment period 1~100 10~1000 10ms
control. as the TTI
This parameter specifies the maximum allowed SIR increase step

UTYPRABOLPC MaxSirStepUp Maximum SIR increase step 0~10000 0~10 0.001dB None
within an adjustment period of outer-loop power control.
Maximum SIR decrease This parameter specifies the maximum allowed SIR decrease step
UTYPRABOLPC MaxSirStepDn 0~10000 0~10 0.001dB None
step within an adjustment period of outer-loop power control.
Step for adjusting the target SIR on the DCH in the optimized outer
UTYPRABOLPC SirAdjustStep SIR adjustment step 0~10000 0~10 0.001dB None
loop power control algorithm.
Page 88
Outer Loop Power Control Parameters
Example OLPC Setting
Where,
I/B: Interactive and Background.
Page 89
Table of Contents

Page 90
Load Control Overview
The WCDMA system is a self-interfering system, as the load of the system increases, the interference rises.
A relatively high interference can affect the coverage of cells and QoS of established services. Therefore, the capacity, coverage, and
QoS of the WCDMA system are mutually affected. To solve these problems, the load control function is introduced that controls the load
in a cell.
Load control aims to maximize the system capacity while ensuring coverage and QoS by controlling the key resources, such as power,
downlink channelization codes, channel elements (CEs), Iub transmission resources, which directly affect user experience.
Each cell has its own set of load control functions that are responsible for monitoring and controlling the resources of the cell.
The load control functions monitor the load condition of the cell through load measurement, make the admission decision for services
through intelligent access control and call admission control, and relieve congestion in a cell.
Load Definition (occupancy of capacity)
There are 2 kinds of capacity in WCDMA Systerm
Hard Capacity
Cell DL OVSF Code
Iub Transport Resource
NodeB processing capability ( NodeB credit)
Soft Capacity
Cell Power
Uplink: RTWP (Received Total Wideband Power)
Downlink : TCP (Transmit Carrier Power)
Page 91
Load Control functions in different UE access phases.
Load control has the following algorithms:
1) Potential User Control (PUC)

The function of PUC is to balance traffic load between inter-frequency
cells. The RNC uses PUC to modify cell selection and reselection
parameters, and broadcasts them through system information.
2) Intelligent Access Control (IAC)

The function of IAC is to increase the access success rate with the
current QoS guaranteed through rate negotiation, queuing,
preemption, and Directed Retry Decision (DRD)
3) Call Admission Control (CAC)

The function of CAC is to decide whether to accept resource requests
from UEs.
4) Intra-frequency Load Balancing (LDB)

The function of intra-frequency LDB is to balance the cell load
between neighboring intra-frequency cells to provide better resource
usage.
5) Load Reshuffling (LDR)

The function of LDR is to reduce the cell load when the available
resources for a cell reach the specified alarm threshold
6) Overload Control (OLC)

The function of OLC is to reduce the cell load rapidly when the cell is
overloaded. The purpose of OLC is to ensure the system stability and
the QoS .
Page 92
Functions of Load Control
Load control is implemented in the RNC after obtaining measurement reports from the NodeBs.
The load control functions, such as OLC and CAC,

use load measurement values in the uplink and the
downlink.
A common Load Measurement (LDM) function is

used to control load measurement in the uplink and the
downlink separately.
Load measurement is implemented by the NodeB, the

RNC will use these measurement as the input for the
Load Control Algorithms.
Resources considered by different load control functions
Page 93
Load Measurement (LDM)
Load measurement is implemented by the NodeB.

The filtering of measurement quantities is implemented by the NodeB and the RNC.
Load-Related Measurement Quantities

The major load-related measurement quantities are as follows:
Uplink Received Total Wideband Power (RTWP)

Downlink Transmitted Carrier Power (TCP)
Non-HSPA power: TCP excluding the power used for transmission on HSPA channels.
Provided Bit Rate (PBR) on HS-DSCH.
Power Requirement for GBR (GBP) on HS-DSCH: minimum power required to ensure the GBR on HS-DSCH PBR on E-DCH
Received Scheduled E-DCH Power Share (RSEPS): power of the E-DCH scheduling service in the serving cell
The NodeB measures the major quantities related to load control.

After layer 1 and layer 3 filtering, the measurement values are reported to the RNC through the COMMON MEASUREMENT REPORT
message.The RNC performs smooth filtering of the measurement values reported from the NodeB and then obtains the measurement
values, which further serve as data input for the load control algorithms.
Page 94
Load Measurement (LDM) Filtering
A is the sampling value of the measurement.

B is the measurement value after layer 1 filtering.
C is the measurement value after layer 3 filtering.
C' is another measurement value for measurement evaluation.
D is the reported measurement value.
Layer 1 filtering is not standardized by protocols and it depends on vendor equipment. Layer 3 filtering is standardized. The filtering
effect is controlled by a higher layer. The alpha filtering that applies to layer 3 filtering is calculated according to the following formula:
Filter response
Fn(1-)Fn-1+Mn
0
1
3
5
7
9
11
13
15
17
19
21
23
25
27
29
31
33
t
Here:
-2
Fn is the new post-filtering measurement value.
Fn-1 is the last post-filtering measurement value. -4
Mn is the new measurement value from the physical layer.
Value, dB
Measured
= (1/2)k/2, k is the measure filter coefficient which is -6 Filtered, k = 3
specified by the following parameters. Filtered, k = 5
-8
For load control algorithms k is specified by the
UlBasicCommMeasFilterCoeff or -10
DlBasicCommMeasFilterCoeff parameter.
-12
For OLC algorithm, k is specified by the UlOlcMeasFilterCoeff Measurements
or DlOlcMeasFilterCoeff parameter.
After the RNC receives the measurement report, it filters the measurement value using the Smooth Window Method.
Page 95
Auto-Adaptive Background Noise Update
Uplink (UL) background noises are sensitive to environmental conditions, and the fluctuation of the background noises
has a negative impact on the RTWP measurement value. Therefore, the LDM function includes an auto-adaptive update algorithm to
restrict the background noise within a specified range, which is enabled by the BGNSwitch parameter.
If the temperature in the equipment room is constant, the background noise changes slightly. In this case, the background noise requires no
adjustment after initial correction.
If the temperature in the equipment room varies with the ambient temperature, the background noise changes greatly. In this case, the
background noise requires auto-adaptive upgrade.
The procedure of auto-adaptive background noise update is as follows:
1. The RNC initializes the counter and filter that are used for auto-adaptive upgrade and sets the initial value (F0) of the filter to BackgroundNoise.
2. The RNC receives the latest RTWP measurement value (Mn) from the physical layer.
3. The RNC checks whether the current time is within the effective period of the algorithm, that is, whether the current time is later than BgnStartTime
and earlier than BgnEndTime. If the current time is within the effective period, the RNC performs the next step. Otherwise, the RNC waits for the next
RTWP measurement value.
4. The RNC determines whether the current Equivalent Number of Users (ENU) in the cell is greater than the value of BGNEqUserNumThd:
If the current ENU is greater than this threshold value, the RNC infers that Mn includes other noises in addition to the background noise, and therefore it
does not feed Mn to the filter. In addition, the RNC sets the counter to zero, retains the current background noise, sets the initial value of the filter to the
current background noise, and waits for the next RTWP measurement value.
If the current ENU in the cell is smaller than or equal to the threshold value, the RNC feeds Mn to the filter and performs the next step.
Page 96
Auto-Adaptive Background Noise Update
Initialize the counter and filter
used for auto-adaptive
background noise upgrade
Receive the RTWP 5. The RNC checks whether |Mn - Fn-1| is smaller than the value of
measurement value (Mn) BgnAbnormalThd. If it is smaller than this threshold value, the RNC increments the
counter by one, calculates Fn according to the Alpha filter formula, and performs the next
No BgnStartTime < Current time
step. Otherwise, the RNC waits for the next RTWP measurement value.
< BgnEndTime?
Yes 6. The RNC checks whether the counter reaches the counting threshold. If it reaches the
counting threshold, the RNC performs the next step. Otherwise, the RNC waits for the
Yes
Equivalent user quantity >
No next RTWP measurement value.
BGNEqUserNumThd?
No
|Mn Fn-1| <
BgnAbnormalThd?
7. The RNC checks whether |Fn - BackgroundNoise| is smaller than the value of
Set the counter to 0
BgnAbnormalThd.
Yes
Increment the
Keep the current background
noise unchanged and set the
counter by one The purpose is to prevent burst interference and RTWP spike. If it is smaller than the
initial value of the filter to the
current background noise
value of BgnAbnormalThd, the RNC performs the next step. Otherwise, the RNC sets
Calculate Fn the counter to zero and waits for the next RTWP measurement value.
according to the
Alpha filter formula
8. The RNC checks whether |Fn - current background noise| is greater than the value
Set the
counter to 0
Does the counter reach No
of BgnUpdateThd.
the counting threshold?
The purpose is to prevent frequent background noise upgrades on the Iub interface. If it is
Yes
greater than the value of BgnUpdateThd, the RNC sets the current background noise
No |Fn - BackgroundNoise|
< BgnAbnormalThd?
to Fn, sets the counter to zero, and waits for the next RTWP measurement value.
Otherwise, the RNC sets the counter to zero and waits for the next RTWP measurement
Yes value.
No |Fn Current background
noise| > BgnUpdateThd?
Yes
Set the current background noise

to Fn, and set the counter to 0 Page 97
Load Measurement (LDM) Parameters
Actual Value Baseline

MO Parameter ID Parameter Name Parameter Description GUI Value Range Unit
Range Value
D0, D1, D2, D3, D0, D1, D2, D3,
L3 filtering coefficient. The larger the value of this parameter, the stronger
UL basic common D4, D5, D6, D7, D4, D5, D6, D7,
ULDM UlBasicCommMeasFilterCoeff the smoothing effect and the higher the anti-slow-fading capability, but None D6
measure filter coeff D8, D9, D11, D13, D8, D9, D11, D13,
the lower the signal change tracing capability.
D15, D17, D19 D15, D17, D19
D0, D1, D2, D3, D0, D1, D2, D3,
L3 filtering coefficient. The larger the value of this parameter, the stronger
DL basic common D4, D5, D6, D7, D4, D5, D6, D7,
ULDM DlBasicCommMeasFilterCoeff the smoothing effect and the higher the anti-slow-fading capability, but None D6
measure filter coeff D8, D9, D11, D13, D8, D9, D11, D13,
the lower the signal change tracing capability.
D15, D17, D19 D15, D17, D19
If you set this parameter to TEN_MSEC, use [UL basic meas rprt
Time unit for UL basic cycle,Unit:10ms] to specify the measurement report period. If you set this
ULDM ChoiceRprtUnitForUlBasicMeas TEN_MSEC, MIN TEN_MSEC, MIN None TEN_MSEC
meas rprt cycle parameter to MIN, use [UL basic meas rprt cycle,Unit:min] to specify
measurement report period.
UL basic meas rprt
ULDM TenMsecForUlBasicMeas UL basic common measurement report cycle. 1~6000 10~60000 10ms 100
cycle 10ms
UL basic meas rprt
ULDM MinForUlBasicMeas UL basic common measurement report cycle. 1~60 1~60 min 20
cycle minu
If you set this parameter to TEN_MSEC, use [DL basic meas rprt
Time unit for DL basic cycle,Unit:10ms] to specify the measurement report period. If you set this
ULDM ChoiceRprtUnitForDlBasicMeas TEN_MSEC, MIN TEN_MSEC, MIN None TEN_MSEC
meas rprt cycle parameter to MIN, use [DL basic meas rprt cycle,Unit:min] to specify
DL basic meas rprt
ULDM TenMsecForDlBasicMeas DL basic common measurement report cycle. 1~6000 10~60000 10ms 100
cycle 10ms
DL basic meas rprt
ULDM MinForDlBasicMeas DL basic common measurement report cycle. 1~60 1~60 min 20
cycle minu
If you set this parameter to TEN_MSEC, use [HSDPA need pwr meas
Time unit of HSDPA cycle,Unit:10ms] to specify the measurement report period. If you set this
ULDM ChoiceRprtUnitForHsdpaPwrMeas TEN_MSEC, MIN TEN_MSEC, MIN None TEN_MSEC
need pwr meas cycle parameter to MIN, use [HSDPA need pwr meas cycle,Unit:min] to specify
HSDPA need pwr
ULDM TenMsecForHsdpaPwrMeas HSDPA power requirement measurement report period 1~6000 10~60000 10ms 100
meas cycle 10ms
HSDPA need pwr
ULDM MinForHsdpaPwrMeas HSDPA power requirement measurement report period 1~60 1~60 min 10
meas cycle minu
If you set this parameter to TEN_MSEC, use [HSDPA bit rate meas
Time unit of HSDPA bit cycle,Unit:10ms] to specify the measurement report period. If you set this
ULDM ChoiceRprtUnitForHsdpaRateMeas TEN_MSEC, MIN TEN_MSEC, MIN None TEN_MSEC
rate meas cycle parameter to MIN, use [HSDPA bit rate meas cycle,Unit:min] to specify
HSDPA bit rate meas
ULDM TenMsecForHsdpaPrvidRateMeas This parameter specifies the HSDPA bit rate measurement report period. 1~6000 10~60000 10ms 100
cycle 10ms
ULDM MinForHsdpaPrvidRateMeas
HSDPA bit rate meas
This parameter specifies the HSDPA bit rate measurement report period. 1~60 1~60 Page 98
min 10
cycle minu
Load Measurement(LDM)Parameters

Range Range Value
If you set this parameter to TEN_MSEC, use [HSDPA bit rate meas
Time unit of HSUPA bit cycle,Unit:10ms] to specify the measurement report period. If you set this TEN_MSEC, TEN_MSEC, TEN_MSE
ULDM ChoiceRprtUnitForHsupaRateMeas None
rate meas cycle parameter to MIN, use [HSDPA bit rate meas cycle,Unit:min] to specify MIN MIN C
HSUPA bit rate meas cycle
ULDM TenMsecForHsupaPrvidRateMeas This parameter specifies the HSUPA bit rate measurement report period. 1~6000 10~60000 10ms 100
10ms
HSUPA bit rate meas cycle
ULDM MinForHsupaPrvidRateMeas This parameter specifies the HSUPA bit rate measurement report period. 1~60 1~60 min 1
minu
Length of smoothing filter window of intra-frequency load balancing
ULDM LdbAvgFilterLen LDB smoothing filter length 1~32 1~32 None 32
(LDB).
PUC smoothing filter
ULDM PucAvgFilterLen Length of smoothing filter window of potential user control (PUC). 1~32 1~32 None 32
length
UL LDR smoothing filter
ULDM UlLdrAvgFilterLen Length of smoothing filter window of uplink LDR. 1~32 1~32 None 5
length
DL LDR smoothing filter
ULDM DlLdrAvgFilterLen Length of smoothing filter window of downlink LDR. 1~32 1~32 None 5
length
UL OLC smoothing filter
ULDM UlOlcAvgFilterLen Length of smoothing filter window of uplink OLC. 1~32 1~32 None 5
length
DL OLC smoothing filter
ULDM DlOlcAvgFilterLen Length of smoothing filter window of downlink OLC. 1~32 1~32 None 5
length
UL CAC smoothing filter
ULDM UlCacAvgFilterLen Length of smoothing filter window of uplink CAC. 1~32 1~32 None 5
length
DL CAC smoothing filter
ULDM DlCacAvgFilterLen Length of smoothing filter window of downlink CAC. 1~32 1~32 None 5
length
(1) This parameter, along with the [Algorithm stop time], is used to limit
Background noise update the validation time of the background noise automatic update algorithm. If hour{0~23},
UCELLCAC BgnStartTime
start time [Algorithm stop time] is greater than [Algorithm start time], and the hour, min, sec min{0~59}, None 01&00&00
background noise automatic update algorithm is enabled, then the sec{0~59}
algorithm is activated during the period of [Algorithm stop time] to
[Algorithm start time] each day. In other periods, the algorithm fails. If
[Algorithm stop time] is less than [Algorithm start time], and the
Background noise update background noise automatic update algorithm is enabled, then the hour{0~23},
UCELLCAC BgnEndTime algorithm is activated during the period of [Algorithm stop time] each day hour, min, sec
end time min{0~59}, None 06&00&00
to [Algorithm start time] of the next day. In other periods, the algorithm sec{0~59}
fails.
(2) Input format: HH&MM&SS
The difference of RTWP that trigger the update of background noise. If

Background noise update
UCELLCAC BgnUpdateThd the difference is larger than the threshold, the background will be 1~100 0.1~10 0.1dBm 5
trigger threshold
updated.
Page 99
Load Measurement(LDM) Parameters

Range Range Value
This parameter is applied when "BGNSwitch" is set to ON. (1) If
the difference of measured background noise without filtered
and the current background noise is larger than the RTWP
Background noise abnormal
UCELLCAC BgnAbnormalThd threshold, the background noise will not be updated. (2) If the 1~400 0.1~40 0.1dB 100
threshold
difference of new background noise and the configured value is
larger than the RTWP threshold, the background noise will not
be updated.
When the parameter is 'OFF', the auto-adaptive background

Auto-adaptive background noise
UCELLCAC BGNSwitch noise update algorithm is switched off. Otherwise, the algorithm OFF, ON OFF, ON None ON
update switch
is switched on.
Background noise filter Alpha filtering coefficient of the Auto-Adaptive Background

UCELLCAC BGNFilterCoef 0~100 0~1 % 5
coefficient Noise Update Algorithm.
Only when the measured background noise's duration reaches

this parameter, the output of the auto-adaptive background
noise update filter could be regarded as effect background
Background noise update
UCELLCAC BGNAdjustTimeLen noise, and the current value is replaced with the new one. At 1~6000 1~6000 s 120
continuance Time
the same time, the auto-adaptive status should be restarted;
otherwise, the output could not be regarded as the effective
background noise.
When the number of uplink equivalent users is not larger than

this parameter, the RTWP could be regarded as background
noise. Therefore, the measured RTWP could be input to the
Equivalent user number
UCELLCAC BGNEqUserNumThd auto-adaptive background noise update filter; otherwise, the 0~10 0~10 None 0
threshold for background noise
RTWP could not be regarded as background noise, and should
not be input to the filter, and at the same time, the auto-
adaptive status should be reset.
D0, D1, D2, D3, D0, D1, D2, D3,
L3 filtering coefficient. The larger the value of this parameter,
D4, D5, D6, D7, D4, D5, D6, D7,
the stronger the smoothing effect and the higher the anti-slow-
ULDM UlOlcMeasFilterCoeff UL overload measure filter coeff D8, D9, D11, D8, D9, D11, None D1
fading capability, but the lower the signal change tracing
D13, D15, D17, D13, D15, D17,
capability.
D19 D19
D0, D1, D2, D3, D0, D1, D2, D3,

L3 filtering coefficient. The larger the value of this parameter,
D4, D5, D6, D7, D4, D5, D6, D7,
the stronger the smoothing effect and the higher the anti-slow-
ULDM DlOlcMeasFilterCoeff DL overload measure filter coeff D8, D9, D11, D8, D9, D11, None D1
fading capability, but the lower the signal change tracing
D13, D15, D17, D13, D15, D17,
capability.
D19 D19
Page 100
Load Control Overview - Priorities
Priorities Involved in Load Control
Different types of priorities are used in load control to preferentially ensure the QoS of the services or users with high priorities.
The priorities involved in load control are User Priority, Radio Access Bearer (RAB) Integrated Priority, and User Integrated Priority.
User Priority
User priorities are adopted to provide differentiated services for users.
For ease of application, the RNC maps the 15 levels of Allocation/Retention Priority (ARP) that is carried in the RAB ASSIGNMENT
REQUEST message from the core network (CN) onto three user priorities, that is, gold (high priority), silver (medium priority), and
copper (low priority).
The relation between user priority and ARP can be set by running SET UUSERPRIORITY command; the typical relation is shown below.
RAB ASSIGNMENT REQUEST
Page 101
RAB Integrated Priority
The priority of an RAB is determined by its traffic class, ARP, and carrier type.
Such a priority is called RAB integrated priority. When resources are insufficient, services with the highest integrated priority are
preferentially processed.
The values of RAB integrated priority are set according to the integrated priority configuration reference parameter
(PriorityReference):
If PriorityReference is set to Traffic Class, the integrated priority abides by the following rules:
Traffic classes: conversational > streaming > interactive > background
Services of the same traffic class: priority based on ARP, that is, ARP1 > ARP2 > ARP3 > ... > ARP14 > ARP15
Service of the same traffic class and ARP (only for interactive services): priority based on Traffic Handling Priority (THP) that is carried in the RAB
ASSIGNMENT REQUEST message, that is, THP1 > THP2 > THP3 > ... > THP14 > THP15.
Services of the same traffic class, ARP and THP (only for interactive services): High Speed Packet Access (HSPA) or Dedicated Channel (DCH)
service preferred depending on CarrierTypePriorInd.
If PriorityReference is set to ARP, the integrated priority abides by the following rules:
ARP: ARP1 > ARP2 > ARP3 > ... > ARP14 >ARP15
Services of the same ARP: priority based on traffic classes, that is, conversational > streaming > interactive > background
Only for the interactive service of the same ARP value: priority based on Traffic Handling Priority (THP), that is, THP1 > THP2 > THP3 > ... > THP14
> THP15.
Services of the same ARP, traffic class and THP (only for interactive services): HSPA or DCH service preferred depending on
CarrierTypePriorInd.
Page 102
Page 103
User Integrated Priority
User Integrated Priority
A user may have multiple RABs, and the RABs may have different priorities. In this case, the highest priority is considered as the priority
of this user.
Such a priority is called user integrated priority. User integrated priority is used in user-specific load control.
For example, the selection of R99 users during preemption, the selection of users during inter-frequency load handover for LDR, and the
selection of users during switching of BE services to common channels are performed according to the user integrated priority.
For Singel-RAB user, the User Intergrated Priority is the same as the RAB Integrated Priority.
For Multiple- RABs user , the User Intergrated Priority is based on the highest priority of RAB.
Page 104
RAB Integrated Priority Parameters

Range Range Value
ARP1Priority None Gold
ARP6Priority None Silver
User_priority of Allocation/Retention User_priority corresponding to Gold, Silver, Gold, Silver,
priority 1,,15 Allocation/Retention priority 1,15 Copper Copper
ARP11Priority None Copper
UOPERUSERPRIORITY
Reference used to determine which

priority is arranged first in the priority
sequence.
If the ARP is preferably used, the

Integrate Priority Configured priority sequence is gold > silver > ARP, ARP,
PriorityReference None ARP
Reference copper. TrafficClass TrafficClass
If the TrafficClass is preferably used,

the priority sequence is conversational
> streaming > interactive >
background.
Decide which carrier is prior when

NONE, DCH, NONE, DCH,
CarrierTypePriorInd Indicator of Carrier Type Priority ARP and TrafficClass are both None NONE
HSPA HSPA
identical.
Page 105
Call Admission Control (CAC)
Call Admission Control (CAC) is used to determine whether the system resources in a cell are sufficient to accept a resource request.
If the system resources are sufficient, the resource request is accepted; otherwise, the resource request is rejected.
A radio link sends a resource request to the CAC functional module when additional resources are required, in cases such as RRC
connection setup, new service setup, change of existing services, soft handover, and cell change.
Upon receiving a resource request, the CAC functional module determines whether the request can be accepted by measuring the cell
load and the requested resources.
The admission decision performed using CAC is based on the following resources: code resources, power resources, NodeB credits,
and Iub resources. In the case of an HSPA resource request, the admission decision is also based on the number of HSPA users.
The admission succeeds only when the resources on which CAC is based are available.
With CAC, an overloaded cell can accept resource requests for an RRC connection setup only in the case of emergency calls,
detachments, or registrations. This is because the priority of such requests is very high. This helps maintain system stability when cells
are overloaded. In addition, admitting or rejecting users over FACH or enhanced FACH channels (HS-DSCH) in an overloaded cell can be
determined by setting the FACH_UU_ADCTRL subparameter of the NBMCacAlgoSwitch parameter.
CAC is needed under such scenarios:

RRC connection setup request
RAB admission decision
Handover
Rate reconfiguration
Page 106
Call Admission Control (CAC)
Basic procedure for a resource-based admission decision
A radio link sends a resource request to the CAC functional module when
additional resources are required. On receipt of the resource request, the
CAC functional module performs the admission decision based on the
following resources:
Available cell code resources

Available cell power resources
NodeB credits, which are used to measure the channel demodulation
capability of NodeBs.
Available Iub transmission bandwidth
Number of HSDPA users (only for HSDPA services)

Number of HSUPA users (only for HSUPA services)
A call can be admitted only when all of these resources are available.
Code and Iub resource-based admission control are mandatory and

cannot be disabled. Other admission control strategies may be enabled or
disabled with the ADD UCELLALGOSWITCH command.
Page 107
CAC Based on Code Resources
Code resource-based admission is mandatory when a new service attempts to access the network.
Code resource-based admission is implemented as follows:
For RRC connection setup requests, code resource-based admission is successful if the current remaining code resources are
sufficient for RRC connection setup.
For handover services, code resource-based admission is successful if the current remaining code resource is sufficient for the
service.
For other R99 services, the RNC has to ensure that the remaining code does not exceed the DlHoCeCodeResvSf parameter
after admitting a new service.
For HSDPA services, the reserved codes are shared by all HSDPA services. Therefore, code resource-based admission is not
required.
Baseline
MO Parameter ID Parameter Name Parameter Description GUI Value Range Actual Value Range Unit
Value
Some cell resources can be reserved for

handover UEs to guarantee handover success
rate and improve access priority of handover SF4(SF4), SF8(SF8),
services. This parameter defines the quantity of SF16(SF16),
downlink code and CE resources reserved for SF32(SF32), SF4, SF8, SF16,
DL handover credit and
UCELLCAC DlHoCeCodeResvSf handover. SF64(SF64), SF32, SF64, SF128, None SF32
code reserved SF
SF128(SF128), SF256, SFOFF
SFOFF refers to that no resources is reserved. SF256(SF256),
SF32 refers to that a code resource with SF = SFOFF(SFOFF)
32 and its corresponding credit resource are
reserved.
Page 108
CAC Based on Power Resources
Power-based admission decisions are used for RRC connection setup requests and RAB admission decisions.
The algorithm switches are set by the NBMUlCacAlgoSelSwitch or NBMDlCacAlgoSelSwitch.
To enable the power-based admission control for HSDPA and HSUPA services, the HSDPA_UU_ADCTRL or HSUPA_UU_ADCTRL
subparameter, respectively, must be set to 1.
CAC based on power resource is performed by using one of the following three algorithms:
Algorithm 1 (ALGORITHM_FIRST): admission decision based on the expected load increment after admitting a new service.
Depending on the current cell load (indicated by the uplink load factor and downlink TCP), the RNC determines whether the cell load would
exceed the threshold after admitting the new service. If the cell load would exceed the threshold, the RNC rejects the access request.
Otherwise, the RNC accepts the access request.
Algorithm 2 (ALGORITHM_SECOND): admission decision based on the Equivalent Number of Users (ENU).
Depending on the current ENU and the access request, the RNC determines whether the ENU would exceed the threshold after admitting a
new service. If the ENU would exceed the threshold, the RNC rejects the request. Otherwise, the RNC accepts the request.
Algorithm 3 (ALGORITHM_THIRD): admission decision without considering load increment after admitting a new service.
This algorithm assumes that the load increment after admitting a new service is 0. Based on the current cell load (indicated by the uplink load
factor and downlink TCP), the RNC determines whether the cell load would exceed the threshold after admitting the new service. If the cell
load would exceed the threshold, the RNC rejects the access request. Otherwise, the RNC accepts the access request.
Page 109
CAC Based on Power Resources
The basic principles for a power-based admission decision are as follows:
For an intra-frequency handover request, only a downlink admission decision is

required if downlink CAC is enabled.
For a non-intra-frequency handover request, both uplink and downlink decisions are
required if both uplink CAC and downlink CAC are enabled.
If there is a rate downsizing request, the RNC accepts it directly. For a rate upsizing
request, the RNC makes the decision.
Admission Decision for RRC Connection Setup Requests
For an RRC connection setup request due to emergency calls, detachments, or

registrations, the connections are set up directly (direct admission).
For an RRC connection setup request for other reasons, the admission decision
depends on the following:
When power-based admission is based on power (algorithm 1 and algorithm 3), the
UL or DL OLC trigger threshold (UlOlcTrigThd or DlOlcTrigThd) is used.
When power-based admission is based on the ENU (algorithm 2), the admission
decision is made as follows:
When UL_UU_OLC or DL_UU_OLC is set to 1, the RRC connection setup request
is rejected if the cell is in the overload state. If the cell is not in the overload state, the
UL or DL OLC trigger threshold is used for power-based admission.
When UL_UU_OLC or DL_UU_OLC is set to 0, the UL or DL OLC trigger threshold

is used for power-based admission.
Page 110
Power-Based Admission Algorithm 1 for RAB Setup
There are two types of power-based admission decision based on algorithm 1
Uplink power-based admission decision
R99 Cell
HSPA Cell
Downlink power-based admission decision

R99 Cell
HSPA Cell
Uplink Power-Based Admission Decision for R99 Cells Based on Algorithm 1
1. RNC obtains the uplink RTWP of the cell and uses the formula UL = 1- (PN /RTWP)
to calculate the current uplink load factor UL, where PN is received uplink background noise.
2. RNC calculate the uplink load increment UL based on the service request.
3. RNC uses the following formula to predic t the Uplink Load Factor
UL,predicted = UL + UL + ULcch
where : ULcch is the reserved common channel load, which is specified by
UlCCHLoadFactor
4. By comparing the predicted uplink load factor with the corresponding threshold
(UlNonCtrlThdForHo, UlNonCtrlThdForAMR, UlNonCtrlThdForNonAMR, or
UlNonCtrlThdForOther), RNC decides whether to accept the access request.
If the access request is accepted, RNC processes the access request. If the access request
is rejected, the RNC performs the next step.
5. RNC checks whether the Control RTWP Anti-interference function switch

(NBMCacAlgoSwitch: RTWP_RESIST_DISTURB) is enabled. If it is enabled,RNC
checks whether the uplink equivalent user load proportion of the cell is less than 40%.
If it is less than 40%, the RNC accepts the access request. Otherwise, RNC rejects the
access request. Page 111
Uplink Interence (Uplink Cell Load )
Noise Rise = 1 / (1- UL)
UL = 1- (PN /RTWP)
Where,
UL : Uplink load factor
PN : Receiver uplink background noise.
PN = KTBWN
= -174 (dBm/Hz) + 10log(3.84MHz / 1Hz) + NF(dB)
= -108 (dBm/3.84MHz) + NF (dB)
KBoltzmann constant, 1.3810 -23 J/K

TKelvin temperature, normal temperature: 290 K
WSignal bandwidth, WCDMA signal bandwidth 3.84MHz
NFNoise Figure (It is used to measure the noise
50% Load 3dB performance of an amplifier on the receiver).
60% Load 4dB

75% Load 6dB
Page 112
Uplink Power-Based Admission Decision for HSPA Cells Based on Algorithm 1

The procedure for an uplink power-based admission decision for HSPA cells is similar
to that for R99 cells.
1. RNC calculates the current uplink load factor based on the uplink RTWP of
the cell.
After the Received Scheduled E-DCH Power Share (RSEPS) measurement is

introduced, the UL RTWP is divided into two parts:
RSEPS is the ratio of the receive power of all scheduled users to RTWP in the current
cell. RSEPS is measured by the NodeB and periodically reported to the RNC.
The controllable part, which is generated by the E-DCH scheduling service and
calculated based on the RSEPS.
E-DCH scheduling service involves the following types of UEs:
Type A: UEs of this type are in the serving E-DCH cell.

Type B: UEs of this type are not in the serving E-DCH cell.
(uplink load generated by the E-DCH scheduling service is calculated through ,
which is set to 0)
The uncontrollable part, which is generated by the other services.

The uncontrollable part is the difference between the current uplink load factor and
the controllable part.
2. RNC calculates the uplink load increment ,UL based on the service
request using Ec/N0 of the GBR of the service, the neighboring interference
factor, and the Active Factor (AF) of the services.
Page 113
3. The RNC determines whether to grant the UE admission.

In an HSPA cell, the admission conditions vary by service types.
For the DCH service, the sum of the uncontrollable part of the RTWP and the uplink load increment must be lower than the corresponding
threshold (UlNonCtrlThdForAMR, UlNonCtrlThdForNonAMR, UlNonCtrlThdForOther, or UlNonCtrlThdForHo).
In addition, the total uplink load of the cell must be lower than UlCellTotalThd. The method of calculating the total uplink load of the cell is as follows:
Sum of the uplink load factor calculated on the basis of the RTWP and load increment
Sum of the uncontrollable part of the RTWP and HsupaMaxGBPThd
For the HSUPA service, since the HSUPA scheduling algorithm consumes additional uplink power resources, the power load of the HSUPA cell is
always relatively high. Therefore, the CAC algorithm combines the PBR-based decision with the load-based decision to reduce the number of
potential erroneous rejections.The RNC admits HSUPA services after a PBR-based or load-based decision is made.
PBR-based decision: This is used to check whether the QoS requirement of all existing users is met. The QoS is measured on the basis of the
Provided Bit Rate (PBR) of the users. The uplink provided bit rate (PBR) is the effective uplink throughput on all UEs corresponding to a scheduling
priority indicator (SPI) successfully received by the NodeB. PBR is reported by the NodeB to the RNC periodically.
The RNC performs PBR-based admission control only when the HSUPA PBR measurement switch is turned on (HSUPA_PBR_MEAS under the
NBMCacAlgoSwitch parameter is set to 1). If the sum of PBRs of some UEs is larger than the sum of their GBRs multiplied by a certain factor, the
RNC decides that the QoS requirements of the cell are met, new users are allowed to access the network.
Load-based decision: For HSUPA scheduling services, the RNC must ensure that the total uplink load factor is lower than UlCellTotalThd.
For HSUPA non-scheduling services, the RNC must ensure that the total uplink load factor is lower than UlCellTotalThd and the power of the
uncontrollable part is lower than the corresponding admission threshold.
In this step, if the access request is rejected, the RNC performs the next step.
4. The RNC checks whether the Control RTWP Anti-interference function switch (NBMCacAlgoSwitch: RTWP_RESIST_DISTURB) is
enabled. If it is enabled, the RNC checks whether the uplink equivalent user load proportion of the cell is less than 40%. If it is less than 40%, the RNC
accepts the access request. Otherwise, the RNC rejects the access request.
Page 114
When the admission of HSUPA scheduling services is implemented, the

following formulas apply:
1) The RNC admits the HSUPA scheduling services in either of the following cases:
Formula 1, 2, or 3 is fulfilled.
Formula 4 is fulfilled.
2) For HSUPA non-scheduling services, the RNC admits the HSUPA non-
scheduling services in either of the following cases:
Formula 1, 2, or 3 is fulfilled.
Formulas 4 and 5 are fulfilled.
3) The RNC admits the DCH (R99) when Formula 4 and 5 are fulfilled
SPINew user : Scheduling Priority Indicator (SPI) of new

HSUPA user.
ThdL is the low priority HSUPA user PBR threshold
(HsupaLowPriorityUserPBRThd).
ThdE is the equal priority HSUPA user PBR threshold
(HsupaEqualPriorityUserPBRThd).
ThdGE is the high priority HSUPA user PBR threshold
(HsupaHighPriorityUserPBRThd).
ULcch is specified by UlCCHLoadFactor.
HS-DPCCH is specified by UlHsDpcchRsvdFactor.
thd-total is the UL total power threshold of the current cell
(UlCellTotalThd).
thd is the cell UL admission threshold of a specific type of
service (UlNonCtrlThdForAMR,
UlNonCtrlThdForNonAMR, UlNonCtrlThdForOther,
or UlNonCtrlThdForHo)
Page 115
Downlink Power-Based Admission Decision for R99 Cells Based on Algorithm 1
The downlink power-based admission decision for R99 cells is similar

to that of the uplink decision.
The procedure is as follows:
1. RNC obtains the cell downlink TCP and calculates the downlink load
factor DL by dividing the maximum downlink transmit power Pmax by TCP.
2. RNC calculates the downlink load increment DL based on the service

request and the current load. RNC uses the following formula to predict the
downlink load factor: DL,predicted = DL + DL + DLcch
In the formula, DLcch is the percentage of reserved DL common channel

load, DlCCHLoadRsrvCoeff..
3. After comparing the downlink load factor with the corresponding

threshold (DlConvAMRThd, DlConvNonAMRThd, DlOtherThd, or
DlHOThd), the RNC decides whether to accept the access request.
Note:
The downlink load increment DL is determined by the following factors:
Eb/N0 of the incoming new call, which has a positive correlation with the
downlink load increment
Non-orthogonal factor, which has a positive correlation with the downlink load
increment
Current TCP, which has a negative correlation with the downlink load increment
Active Factor (AF) of the incoming new call, which has a positive correlation with
the downlink load increment.
Page 116
Downlink Power-Based Admission Decision for HSPA Cells Based on Algorithm 1
Admission Decision for DCH RAB in the Downlink

When the admission of the DCH RAB is implemented, the RNC performs the
following steps:
RNC evaluates whether the ratio of the current non-HSPA power after the new
RAB access to the maximum transmit power of the cell is less than or equal to the
cell downlink admission threshold for a specific type of service.
The threshold may be DlConvAMRThd, DlConvNonAMRThd, DlOtherThd,

or DlHOThd. If the condition is met, the RNC performs the next step. Otherwise, RNC admits the DCH RAB in either of the following situations:
the admission fails. Formulas 1 and 2 are fulfilled.
RNC evaluates whether the ratio of the current downlink total power after the Here:
new RAB access to the maximum transmit power of the cell is less than or equal Pnon-hspa : current non-HSPA power.
to the threshold of the total downlink power of the cell (DlCellTotalThd). Pcch-res : power reserved for the common channel.
Pmax : maximum transmit power of the cell.
The HSDPA power included in the current downlink total power can be Thdnon-hspa-cac : Cell DL admission threshold for a
set with HsdpaMaxGBPThd or evaluated through the GBP and the specific type of service. DlConvAMRThd,
maximum power available for HSPA services. DlConvNonAMRThd, DlOtherThd, or DlHOThd
The current downlink total power also includes all kinds of reserved
power, for example, the power for the common channel and for HSUPA Ptotal : current downlink TCP.
downlink control channels. Thdtotal-cac : Threshold of the total DL power of the cell
(DlCellTotalThd).
If the condition above is met, the RNC admits the DCH RAB. Otherwise, the GBP : minimum power required to ensure the GBR. If
admission fails. GBP measurement is deactivated, the GBP is set to 0.
Phsupa_res :power reserved for HSUPA downlink control
If the current cell supports DC-HSDPA, the current total power of the DC-HSDPA channels (E-AGCH/E-RGCH/E-HICH).
cell group must also be less than the sum of the total downlink power threshold of Pmax_hspa :maximum available power for HSPA
the primary cell and that of the secondary cell.
Page 117
Admission Decision for HSDPA RAB in the Downlink
When the admission of the HSDPA RAB is implemented, the PBR-based decision
and load-based decision are also performed.
The RNC admits the UE when the criteria for either decision is fulfilled.
PBR-based decision: The PBR of all existing services must greater than or
equal to the admission threshold HsdpaStrmPBRThd ,HsdpaBePBRThd.
Load-based decision: The total downlink load after the new RAB access must
be less than or equal to the threshold of the total downlink power of the cell
RNC admits the HSDPA streaming RAB in any of the conditions:
(DlCellTotalThd). The total downlink load after new RAB access can be calculated
in one of the following ways:
a. The sum of the current TCP and the power increment for the new RAB
b. The sum of the current non-HSPA power and the GBP of all existing HSDPA
RNC admits the HSDPA BE RAB in any of the conditions:
services
Note :
If PS conversational services are carried on HSPA, the services can be treated as
streaming services during admission control. Here:
If the PBR measurement is deactivated, the decision formulas that involve PBR PBRstrm is the provided bit rate of all existing
are regarded as dissatisfied. streaming services.
For the first HSDPA service accessing the cell, the decision formulas that involve Thdhsdpa-str is the admission threshold for
PBR are regarded as unsatisfied. streaming PBR decision (HsdpaStrmPBRThd).
If the current cell supports DC-HSDPA, the RNC admits the HSDPA RAB in the PBRbe is the provided bit rate of all existing BE
DC-HSDPA case only when the conditions of cell group are met then the cell group services.
is admitted. Thdhsdpa-be is the admission threshold for BE PBR
decision (HsdpaBePBRThd).
Page 118
There are two types of power-based admission decision based on algorithm 2:
Uplink power-based admission decision
Downlink power-based admission decision
When the uplink CAC algorithm or the downlink CAC algorithm uses algorithm 2, the admission of uplink/downlink power resources
uses the algorithm depending on the ENU.
Equivalent Number of Users (ENU)

The 12.2 kbit/s AMR traffic is defined as one ENU, which stands for Equivalent Number of Users. Thus, the 12.2 kbit/s AMR traffic can be used to
calculate the ENU of all other services.
Typical ENU (with activity factor to be 100%)
The calculation is related to the following factors:
Cell type (urban or suburban)

Traffic domain (CS or PS)
Coding type (turbo code or 1/2 1/3 convolutional code)
Traffic QoS, that is, the Block Error Rate (BLER)
The activity value of the traffic type,
which can be set with the SET UADMCTRL command.
Note:
In Table for a 3.4+n kbit/s service of HSDPA or HSUPA,
-3.4 kbit/s is the rate of the signaling (SRB) carried on the DCH.
-n kbit/s is the GBR of the service. Page 119
Procedure for ENU Resource Decision
The RNC obtains the total ENU of all existing users ENUtotal = all_exist_userENUi.
The RNC gets the ENU of the new incoming user ENUnew.
The RNC uses the formula (ENUtotal + ENUnew)/ENUmax to forecast the ENU load, where ENUmax is the configured maximum ENU
(UlTotalEqUserNum or DlTotalEqUserNum).
By comparing the forecasted ENU load with the corresponding threshold, the RNC decides whether to accept the access request.
The cell admission control thresholds may be one of the following thresholds:
UL/DL threshold of conversational AMR service
UL/DL threshold of conversational non-AMR service
UL/DL threshold of other services
UL/DL access threshold for handover
Page 120
Procedure for Uplink ENU Resource Decision
Before the admission of the uplink ENU resource, if the uplink OLC algorithm switch (UL_UU_OLC) is enabled and the cell is in the OLC state
triggered by the RTWP, then:
The system checks whether the uplink equivalent user load proportion of the cell is less than 40% if the Control RTWP Anti-interference function
switch (NBMCacAlgoSwitch: RTWP_RESIST_DISTURB) is enabled. If it is less than 40%, the RNC accepts the access request. Otherwise, the
RNC performs an admission decision on the uplink ENU resource.
The RNC rejects the access request if the Control RTWP Anti-interference function switch is disabled.
In the normal state, when the uplink ENU admission for a new RAB is implemented, the RNC calculates the uplink ENU of the RAB, and then
estimates whether the ratio of the total uplink ENU after the new RAB access to the maximum ENU (UlTotalEqUserNum) is less than or equal to
the cell uplink admission threshold for a specific type of service. The threshold may be UlNonCtrlThdForAMR, UlNonCtrlThdForNonAMR,
UlNonCtrlThdForOther, or UlNonCtrlThdForHo. If the condition is met, the RNC admits the access request.
For DCH users, the RNC can also admit the access request if the ratio of the total uplink ENU of all DCH users after the new RAB access to the
maximum ENU (UlTotalEqUserNum) is less than or equal to difference between UlCellTotalThd and HsupaMaxGBPThd.
Procedure for Downlink ENU Resource Decision

For non-DC-HSDPA RAB
If the current cell does not support DC-HSDPA, when the ENU admission of the RAB is implemented, the RNC calculates the downlink ENU of an
incoming RAB, and then estimates whether the ratio of the total downlink ENU after the new RAB access to the maximum ENU
(DlTotalEqUserNum) is less than or equal to the cell downlink admission threshold of a specific type of service. The threshold may be
DlConvAMRThd, DlConvNonAMRThd, DlOtherThd, DlHOThd, or DlCellTotalThd. If the condition is met, the RNC admits the access
request.
For DCH users, the RNC can also admit the access request when the ratio of the total downlink ENU of all DCH users after the new RAB access to
the maximum ENU (DlTotalEqUserNum) is less than or equal to difference between DlCellTotalThd and HsdpaMaxGBPThd.
For DC-HSDPA RAB

The admission is successful when the total ENU divided by the maximum ENU is less than the sum of admission thresholds of the two cells.
Page 121
Algorithm 3 is similar to algorithm 1.

The difference is that the estimated load increment in algorithm 3 is always set to 0.
In accordance with the current cell load (uplink load factor and downlink TCP), the RNC determines whether the cell load would exceed
the threshold, with the estimated load increment set to 0. If the cell load would exceed the threshold, the RNC rejects the request.
If not, the RNC accepts the request
Page 122
CAC Based on Power Resources Example
Example baseline parameters settings of Power-Based CAC
Power-Based Admission Algorithm 2

(Uplink)
Page 123
CAC Based on Power Resources Parameters
MO Parameter ID Parameter Name Parameter Description GUI Value Range Actual Value Range Unit Baseline Value
HSDPA_GBP_MEAS: Control HSDPA HS-

DSCH Required Power measurement.
HSDPA_PBR_MEAS: Control HSDPA HS-

DSCH Provided Bit Rate measurement.
HSUPA_PBR_MEAS: Control HSUPA Provided

Cell CAC algorithm
UCELLALGOSWITCH NBMCacAlgoSwitch Bit Rate measurement. 0,1 ON,OFF None OFF
switch
HSUPA_EDCH_RSEPS_MEAS: Control
HSUPA Provided Received Scheduled EDCH
Power Share measurement.
RTWP_RESIST_DISTURB: Control algorithm of

resisting disturb when RTWP is abnormal.
UL_UU_OLC: UL UU overload congestion

control algorithm. When the cell is overloaded in
UL, this algorithm reduces the cell load in UL by
quick TF restriction or UE release.
Cell LDC algorithm
UCELLALGOSWITCH NBMLdcAlgoSwitch 0,1 ON,OFF None OFF
switch
DL_UU_OLC: DL UU overload congestion
control algorithm. When the cell is overloaded in
DL, this algorithm reduces the cell load in DL by
quick TF restriction or UE release.
Uplink CAC algorithm The algorithms with the above values represent
UCELLALGOSWITCH NBMUlCacAlgoSelSwitch are as follow: ALGORITHM_SECOND
switch
ALGORITHM_OFF: Disable uplink call
admission control algorithm. ALGORITHM_OFF, ALGORITHM_OFF,
ALGORITHM_FIRST: The load factor prediction ALGORITHM_FIRST, ALGORITHM_FIRST,
None
algorithm will be used in uplink CAC. ALGORITHM_SECOND, ALGORITHM_SECOND,
ALGORITHM_SECOND: The equivalent user ALGORITHM_THIRD ALGORITHM_THIRD
Downlink CAC number algorithm will be used in uplink CAC.
UCELLALGOSWITCH NBMDlCacAlgoSelSwitch ALGORITHM_FIRST
algorithm switch ALGORITHM_THIRD: The loose call admission
control algorithm will be used in uplink CAC.
Page 124
Actual
GUI Value Baseline
MO Parameter ID Parameter Name Parameter Description Value Unit
Range Value
Range
The percentage of the conversational AMR service threshold to the 100%
uplink load. It is applicable to algorithm 1 and algorithm 2. The parameter is
used for controlling the AMR service admission. That is, when a AMR service
UL threshold of Conv AMR is accessing, the RNC evaluates the measurement value of the uplink load
UCELLCAC UlNonCtrlThdForAMR 0~100 0~1 % 75
service after the service is accessed. If the UL load of a cell is higher than this
threshold after the access of a AMR speech service, this service will be
rejected. If the UL load of a cell will not be higher than this threshold, this
service will be admitted.
The percentage of the conversational non-AMR service threshold to the 100%
used for controlling the non-AMR service admission. That is, when a non-AMR
service is accessing, the RNC evaluates the measurement value of the uplink
UL threshold of Conv
UCELLCAC UlNonCtrlThdForNonAMR load after the service is accessed. If the UL load of a cell is higher than this 0~100 0~1 % 75
non_AMR service
threshold after the access of a non-AMR speech service, this service will be
rejected. If the UL load of a cell will not be higher than this threshold, this
The percentage of other service thresholds to the 100% uplink load. The
services refer to other admissions except the conversational AMR service,
conversational non-AMR service, and handover scenarios. It is applicable to
algorithm 1 and algorithm 2. The parameter is used for controlling other
UL threshold of other service admissions. That is, when a service is accessing, the RNC evaluates
UCELLCAC UlNonCtrlThdForOther 0~100 0~1 % 60
services the measurement value of the uplink load after the service is accessed. If the
UL load of a cell is higher than this threshold after the access of a service, this
service will be rejected. If the UL load of a cell will not be higher than this
threshold, this service will be admitted.
The percentage of the handover service admission threshold to the 100%

used for controlling the handover admission. That is, when a service is
UL handover access
UCELLCAC UlNonCtrlThdForHo handing over to a cell, the RNC evaluates the measurement value of the 0~100 0~1 % 80
threshold
uplink load after the service is accessed. If the UL load of a cell is higher than
this threshold after the access, this service will be rejected. If the UL load of a
cell will not be higher than this threshold, this service will be admitted.
Admission threshold of total cell uplink power. This parameter is related to the
UCELLCAC UlCellTotalThd UL total power threshold 0~100 0~1 % 83
target load of the uplink schedule.
Page 125

Range Range Value
The percentage of the conversational AMR service threshold to the 100%
downlink load. It is applicable to algorithm 1 and algorithm 2. The parameter is
used for controlling the AMR service admission. That is, when an AMR service
is accessing, the RNC evaluates the measurement value of the downlink load
DL threshold of Conv AMR
UCELLCAC DlConvAMRThd after the service is accessed. If the DL load of a cell is higher than this 0~100 0~1 % 80
service
threshold after the access of an AMR speech service, this service will be
rejected. If the DL load of a cell will not be higher than this threshold, this
The percentage of the conversational non-AMR service threshold to the 100%

used for controlling the non-AMR service admission. That is, when a non-AMR
service is accessing, the RNC evaluates the measurement value of the
DL threshold of Conv
UCELLCAC DlConvNonAMRThd downlink load after the service is accessed. If the DL load of a cell is higher 0~100 0~1 % 80
non_AMR service
than this threshold after the access of a non-AMR speech service, this service
will be rejected. If the DL load of a cell will not be higher than this threshold,
this service will be admitted.
The percentage of other service thresholds to the 100% downlink load. The
services refer to other admissions except the conversational AMR service,
conversational non-AMR service, and handover scenarios. It is applicable to
algorithm 1 and algorithm 2. The parameter is used for controlling other
service admissions. That is, when a service is accessing, the RNC evaluates
UCELLCAC DlOtherThd DL threshold of other services 0~100 0~1 % 75
the measurement value of the downlink load after the service is accessed. If
the DL load of a cell is higher than this threshold after the access of a service,
this service will be rejected. If the DL load of a cell will not be higher than this
threshold, this service will be admitted.
The percentage of the handover service admission threshold to the 100%

used for controlling the handover admission. That is, when a service is
DL handover access
UCELLCAC DlHOThd handing over to a cell, the RNC evaluates the measurement value of the 0~100 0~1 % 85
threshold
downlink load after the service is accessed. If the DL load of a cell is higher
than this threshold after the access, this service will be rejected. If the DL load
of a cell will not be higher than this threshold, this service will be admitted.
Admission threshold of the total cell downlink power. If the value is too high,
UCELLCAC DlCellTotalThd DL total power threshold too many users will be admitted. However, the throughput of a single user is 0~100 0~1 % 90
easy to be limited. If the value is too low, cell capacity will be wasted.
Page 126

Range Range Value
The admission control decision is only for dedicated channels. For common
UL common channel load
UCELLCAC UlCCHLoadFactor channels, some resources instead of a special admission procedure are 0~100 0~1 % 0
reserved coefficient
reserved.
The admission control decision is only for dedicated channels. For common
DL common channel load
UCELLCAC DlCCHLoadRsrvCoeff channels, some resources instead of a special admission procedure are 0~100 0~1 % 0
reserved coefficient
reserved.
UL total equivalent user When the algorithm 2 is used, this parameter defines the total equivalent user
UCELLCAC UlTotalEqUserNum 1~200 1~200 None 95
number numbers corresponding to the 100% uplink load.
DL total equivalent user When the algorithm 2 is used, this parameter defines the total equivalent user
UCELLCAC DlTotalEqUserNum 1~200 1~200 None 80
number number corresponding to the 100% downlink load.
Low priority HSUPA user Threshold of all the HSUPA user PBR whose schedule priority is lower than
UCELLCAC HsupaLowPriorityUserPBRThd 0~100 0~1 % 100
PBR threshold that of users to be admitted.
Equal priority HSUPA user Threshold of all the HSUPA user PBR whose schedule priority is the same as
UCELLCAC HsupaEqualPriorityUserPBRThd 0~100 0~1 % 100
High priority HSUPA user Threshold of all the HSUPA user PBR whose schedule priority is higher than
UCELLCAC HsupaHighPriorityUserPBRThd 0~100 0~1 % 100
Average throughput admission threshold of the HSDPA streaming service. If
the sum of PBR of all the accessed streaming users is lower than the average
Hsdpa streaming PBR throughput admission threshold of the HSDPA streaming service multiplied by
UCELLCAC HsdpaStrmPBRThd 0~100 0~1 % 70
threshold the sum of GBR of all the accessed streaming users, it indicates that the QoS
of the accessed users cannot be satisfied and new HSDPA streaming services
are not allowed.
Average throughput admission threshold of the HSDPA best effort traffic. If the
sum of PBR of all the accessed HSDPA BE users is lower than the average
HSDPA best effort PBR throughput admission threshold of the HSDPA BE service multiplied by the
UCELLCAC HsdpaBePBRThd 0~100 0~1 % 30
threshold sum of GBR of all the accessed HSDPA BE users, it indicates that the QoS of
the accessed users cannot be satisfied and new HSDPA BE services are not
allowed.
If [Auto-Adaptive Background Noise Update Switch] is set to OFF, it is used to
set background noise of the cell. If [Auto-Adaptive Background Noise Update
UCELLCAC BackgroundNoise Background noise 0~621 -112~-50 0.1dBm 61
Switch] is set to ON, new background noise is restricted by this parameter and
"BgnAbnormalThd".
Threshold of Maximum Threshold of the maximum guaranteed power for HSDPA users. This threshold
UCELLCAC HsdpaMaxGBPThd Guaranteed Bit Rates for limits the power that can be used by HSDPA users. Thus, some power 0~100 0~1 % 100
HSDPA resources are reserved for DCH users to ensure their network access.
Threshold of Maximum Threshold of the maximum guaranteed power for HSUPA users. This threshold
UCELLCAC HsupaMaxGBPThd Guaranteed Bit Rates for limits the power that can be used by HSUPA users. Thus, some power 0~100 0~1 % 100
HSUPA resources are reserved for DCH users to ensure their network access. Page 127
CAC Based on NodeB Credit Resource
When a new service accesses the network, NodeB credit resource-based admission is optional.
R99 service
CE is used to measure the channel demodulation capability of the NodeBs.
CEs are classified into uplink and downlink CEs.
On the RNC side, it is referred to as the NodeB credit.

On the NodeB side, it is referred to as the Channel Element (CE).
This admission mode takes effect only when NODEB_CREDIT_CAC_SWITCH

under the CacSwitch parameter and CRD_ADCTRL under the
NBMCacAlgoSwitch parameter are selected.
One uplink CE needs to be consumed by an uplink 12.2 kbit/s voice service (SF = 64)
plus 3.4 kbit/s signaling traffic.
One downlink CE needs to be consumed by a downlink 12.2 kbit/s voice service (SF
= 128) plus 3.4 kbit/s signaling traffic.
If only 3.4 kbit/s signaling traffic is carried on a DCH or HSPA channel,

one CE is still needed.
CEs have been reserved for common and HSDPA-related channels.
For an R99 service, the RNC determines the number of CEs and NodeB credit
resources as follows:
For AMR and VP. MBR is UL/DL MBR specified in RAB Assignment
Request message.
For PS BE on DCH, if DRA_DCCC_SWITCH is enabled the the RNC
calculates the SF based on the UlBeTraffInitBitrate ,
DlBeTraffInitBitrate otherwise the SF based on the MBR.
Page 128
For an HSUPA service, the RNC determines the number of CEs and NodeB credit resources that need to be consumed
based on the SF that matches the service rate.
The RNC determines the SF based on a certain rate in the following ways:
1) If the UL enhanced L2 function is disabled and the NodeB indicates in a private information element (IE) that dynamic CE resource
management has been enabled in the cell, the RNC calculates the SF based on the larger of the bit rate of one RLC PDU and the guaranteed bit
rate (GBR).
(When the UL enhanced L2 function is disabled, the RLC PDU size is fixed. The bit rate of one RLC PDU is determined by the RLC PDU size and
transmission time interval (TTI))
2) If the UL enhanced L2 function is enabled and the NodeB indicates in a private IE that dynamic CE resource management has been enabled in the
cell, the RNC calculates the SF based on the larger of the bit rate of the smallest RLC PDU and the GBR.
(when the UL enhanced L2 function is enabled, the RLC PDU size is flexible. The bit rate of the smallest RLC PDU is determined by the minimum RLC
PDU size and the TTI. The minimum RLC PDU size can be specified by the RlcPduMaxSizeForUlL2Enhance parameter.)
3) If the NodeB reports that dynamic CE resource management and the RNC switch DRA_HSUPA_DCCC_SWITCH are disabled , the RNC
calculates the SF based on the MBR.
4) If the NodeB reports that dynamic CE resource management is disabled but the RNC switch DRA_HSUPA_DCCC_SWITCH is enabled, the
RNC calculates the SF based on the HsupaInitialRate.
5) If the NodeB does not report whether dynamic CE resource management has been enabled, the RNC calculates the SF based on the value of the
HsupaCeConsumeSelection parameter and whether the UL enhanced L2 function is enabled.
If HsupaCeConsumeSelection is set to MBR, the RNC calculates the SF based on the MBR.
If HsupaCeConsumeSelection is set to GBR:
a. If the UL enhanced L2 function is disabled, the RNC calculates the SF based on the larger of the bit rate of one RLC PDU and the GBR.
b. If the UL enhanced L2 function is enabled, the RNC calculates the SF based on the larger of the bit rate of the smallest RLC PDU and the GBR.
Page 129
HSUPA service
HSUPA RAB CE Admission Rules
For each data rate and service ,the number of UL credit is equal to
the number of UL CE multiplied by 2.
This is because the RESOURCE STATUS INDICATOR message

over the Iub interface supports only integer.
For example , an UL 32kbps PS service consume 1.5 CEs, Then the

number of corresponding UL credits consumed is 3.
Page 130
NodeB credit resource-based admission is implemented at NodeB level,
local cell group (LCG) level (if any), and local cell (LC) level. CE
capabilities at the local cell, local cell group, and NodeB levels are reported to
the RNC through the NBAP_AUDIT_RSP message over the Iub interface.
CE capability at the local cell level (LC) indicates, in terms of hardware,

the maximum capability that can be used in the local cell.
CE capability at the local cell group level (LCG) indicates the capability
when the license and hardware are taken into consideration.
CE capability at the NodeB level indicates the number of CEs that can be
used, as specified in the license.
In the current product release, the UL Capacity Credit (CC) and DL CC are
separate. So the credit resource-based admission is implemented in the UL and
DL, respectively.
Handover performance first mode

SET RESALLOCRULE: RULE =PERFFIRST;
-DL Local Cells of the same frequency
are allocated to the same board allow
Softer HO.
Capacity first mode

SET RESALLOCRULE: RULE =CAPAFIRST;
-DL Local Cells of the same frequency
are allocated to different boards.
WBBP : WCDMA Baseband Processing boards in NodeB. Page 131

Parameters
Range Range Value
The system performs CAC based on the usage state of

UCACALGOSWITCH CacSwitch NODEB_CREDIT_CAC_SWITCH NodeB credit. When the NodeB's credit is not enough, 0,1 ON,OFF ON ON
the system rejects new access requests.
CRD_ADCTRL: Control Cell Credit admission control

algorithm. Only when NODEB_CREDIT_CAC_SWITCH
UCELLALGOSWITCH NBMCacAlgoSwitch CRD_ADCTRL which is set by the SET UCACALGOSWITCH command 0,1 ON,OFF ON ON
and this switch are on,the Cell Credit admission control
algorithm is valid.
When the switch is on, the dynamic channel

UCORRMALGOSWITCH DraSwitch DRA_DCCC_SWITCH: 0,1 ON,OFF ON ON
reconfiguration control algorithm is used for the RNC.
When the switch is on, the DCCC algorithm is used for

UCORRMALGOSWITCH DraSwitch DRA_HSUPA_DCCC_SWITCH HSUPA. The DCCC switch must be also on before this 0,1 ON,OFF ON ON
switch takes effect.
UL initial access rate of PS background or interactive

service. When DCCC function is enabled, the uplink D8, D16, D32,
8, 16, 32, 64,
initial access rate will be set to this value if the uplink D64, D128,
UFRC UlBeTraffInitBitrate UL BE traffic Initial bit rate 128, 144, 256, kbit/s D64
maximum rate is higher than the initial access rate. Note D144, D256,
384
that the rate will be decreased through negotiation when D384
congestion occurs.
DL initial access rate of PS background or interactive D8, D16, D32,

8, 16, 32, 64,
service. When DCCC function is enabled, the downlink D64, D128,
UFRC DlBeTraffInitBitrate DL BE traffic Initial bit rate 128, 144, 256, kbit/s D64
initial access rate will be set to this value if the downlink D144, D256,
384
maximum rate is higher than the initial access rate. D384
D8, D16, D32,

8, 16, 32, 64,
HSUPA BE traffic initial bit rate. When DCCC algorithm D64, D128,
128, 144, 256,
switch and HSUPA DCCC algorithm switch are enabled, D144, D256,
UFRC HsupaInitialRate Initial rate of HSUPA BE traffic 384, 608, 1280, kbit/s D256
the uplink initial bit rate will be set to this value if the D384, D608,
2048, 2720,
uplink max bit rate is higher than the initial bit rate. D1280, D2048,
5440
D2720, D5440
This parameter specifies the maximum RLC PDU size
RlcPduMaxSizeForUlL Cell_DCH UL L2 enhance max
UFRC when the UE is in CELL_DCH state and UL Layer 2 4~402 4~402 byte 302
2Enhance RLC PDU size
Enhanced is enabled.
OPEN(open), OPEN~0,
MACHSPARA DYNCODESW Dynamic Code Switch Indicates the Dynamic Code Switch. None OPEN
CLOSE(close) CLOSE~1
Page 132
When a new service tries to access the network, the admission decision based on NodeB credit is implemented
as follows:
RRC connection setup request, the credit resource-based admission is successful if the current remaining credit resources of
the local cell, local cell group (if any), and NodeB are sufficient for RRC connection setup.
Handover service, the credit resource-based admission is successful if the current remaining credit resources of the local cell,
local cell group (if any), and NodeB are sufficient for the service.
For other services, the RNC has to ensure that the remaining credit of the local cell, local cell group (if any), and NodeB does not
exceed the value of UlHoCeResvSf (for the uplink) or DlHoCeCodeResvSf (for the downlink) after admission of the new services.
Baseline
MO Parameter ID Parameter Name Parameter Description GUI Value Range Actual Value Range Unit
Value
SF4(SF4), SF8(SF8),
SF16(SF16),
Uplink Credit Reserved by Spread Factor for SF32(SF32), SF4, SF8, SF16,
UCELLCAC UlHoCeResvSf UL handover credit reserved SF HandOver. SFOFF means that none of them SF64(SF64), SF32, SF64, SF128, None SF16
are reserved for handover. SF128(SF128), SF256, SFOFF
SF256(SF256),
SFOFF(SFOFF)
Some cell resources can be reserved for

handover UEs to guarantee handover success SF4(SF4), SF8(SF8),
rate and improve access priority of handover SF16(SF16),
services. This parameter defines the quantity of SF32(SF32), SF4, SF8, SF16,
DL handover credit and code
UCELLCAC DlHoCeCodeResvSf downlink code and CE resources reserved for SF64(SF64), SF32, SF64, SF128, None SF32
reserved SF
handover. SFOFF refers to that no resources is SF128(SF128), SF256, SFOFF
reserved. SF32 refers to that a code resource SF256(SF256),
with SF = 32 and its corresponding credit SFOFF(SFOFF)
resource are reserved.
Page 133
CAC Based on Iub Resource
The Universal Mobile Telecommunications System (UMTS) supports four traffic classes: conversational, streaming,
interactive, and background. The transmission rate varies with the traffic class as follows:
For Circuit Switched (CS) conversational services, the channel transmits voice signals at a certain rate (for example, 12.2
kbit/s) during a conversation and only transmits Silence Descriptors (SIDs) at intervals when there is no conversation.
For Packet Switched (PS) interactive and background services, such as web browsing, there is data transmitted during data
downloading. After a web page has been downloaded, and when the user is reading the page, however, there is very little data to
transfer.
If the Radio Network Controller (RNC) allocates the maximum bandwidth to the subscriber when a service is established, a large proportion
of the Iub transmission bandwidth is unused.
For example, downloading a 50 KB page takes only about one second, but reading this page needs dozens of seconds. Thus, over 90% of
the Iub transmission bandwidth is not used.
To save the Iub transmission bandwidth for operator use, Huawei provides the Iub overbooking function, which applies an
admission control mechanism to access the service.
Services are admitted according to the different Activity Factors. PS interactive and background services can be admitted according to the
Guaranteed Bit Rate (GBR). In this way, the maximum number of users with the minimum number of activity request to use voice and PS
Best Effort (BE) services can access the network, thus achieving a better utilization of transmission bandwidth.
Iub overbooking
The Iub overbooking feature considers the statistic multiplexing of service activities and multiple users.
Through the admission of more users, Iub overbooking increases the resources utilization on the Iub interface.
Page 134
Calculation of Bandwidth Reserved for Traffic
Bandwidth reserved for a service = Transport-layer rate of the service x Activity factor
The RNC or BSC calculates the reserved bandwidth based on the activity factor and
Default settings of activity factors
performs admission control based on the reserved bandwidth.
The bandwidth reservation policies for different services are as follows:
For 2G/3G RT services: Reserved bandwidth = MBR x Activity factor
For 3G NRT services: Reserved bandwidth = GBR x Activity factor
3G signaling:
Admission of SRB at 3.4 kbit/s:
The bandwidth for 3G SRB signaling is fixed at 3.4 kbit/s. This admission mode is
applicable to R99, HSDPA, and HSUPA services. For R99 services, if the bandwidth of a
transport channel varies between 3.4 kbit/s and 13.6 kbit/s, resource allocation and
resource admission do not need to be performed again.
Admission of IMS at the GBR
3G common channels:
Bandwidth reserved for E-FACH = GBR x Activity factor
Bandwidth reserved for other common channels = MBR x Activity factor
Activity factors can be configured for different types of services and adjacent nodes via
ADD TRMFACTOR.
For 3G BE services, the GBR can be set by running the SET UUSERGBR command,
according to traffic classes, traffic priorities, user priorities, and types of radio bearers.
GBR of Voice service is specified in RAB Assignment Request message from CN. Page 135
Load Thresholds
In the admission process based on transmission resources, load and threshold are compared to determine
whether the admission is successful.
The thresholds can be configured through the parameters such as relative residual resource (%, percentage of residual bandwidth to
total bandwidth) or absolute residual resource (kbit/s, residual bandwidth). Uplink and downlink thresholds are configured separately.
Admission threshold of a new user (handover reserved threshold)

This threshold controls the admission of a new user and can be configured through the parameters FWDRSVHOBW, BWDRSVHOBW,
FWDRESVHOTH, and BWDRESVHOTH.
Congestion threshold (admission threshold of a user requesting a rate increase)

This threshold triggers LDR and can be configured through the parameters FWDCONGBW, BWDCONGBW, FWDCONGTH, and BWDCONGTH.
Congestion clear threshold

This threshold clears congestion and can be configured through the parameters FWDCONGCLRBW, BWDCONGCLRBW, FWDCONGCLRTH,
and BWDCONGCLRTH.
Overload threshold
This threshold triggers overload control and can be configured through the parameters FWDOVLDRSVBW, BWDOVLDRSVBW,
FWDOVLDTH, and BWDOVLDTH.
Overload clear threshold
This threshold clears overload and can be configured through the parameters FWDOVLDCLRRSVBW, BWDOVLDCLRRSVBW,
FWDOVLDCLRTH, and BWDOVLDCLRTH.
The congestion threshold and congestion clear threshold, and the overload threshold and overload clear threshold are used to prevent
ping-pong effect. It is recommended that they should be set to different values.
By running the ADD TRMLOADTH command, you can configure a load threshold table (TRMLOADTH table) for paths, LPs, resource
groups, or physical ports. By specifying the TRMLOADTHINDEX parameter, the TRMLOADTH table can be referred to.
Page 136
The principles of ATM/IP transmission resource admission are as follows:
Multiple levels of admission. After the user initiates a request for transmission
resources, admission based on transmission resources is decided in the
sequence of Paths -> LPs (Logical Ports) -> Physical Ports. Based on the preceding requirement, the user
priorities are as follows:
(1) For a handover user
Admission based on paths User requesting handover > New user >
Path load + Bandwidth required by the user < Total bandwidth for the path User requesting rate upsizing
Admission based on LPs

LP load + Bandwidth required by the user < Total bandwidth for the LP
(2) For a new user

Admission based on paths
Path load + Bandwidth required by the user < Total configured bandwidth for the
path - Path bandwidth reserved for handover

LP bandwidth reserved for handover
(3) For a user requesting a rate increase

Admission based on paths
Path load + Bandwidth required by the user < Total bandwidth for the path
Path congestion threshold

The admission based on LPs is performed level by level.
LP congestion threshold
Page 137
CAC Based on Iub Resource Parameters

Range Range Value
TRMLOADTH TRMLOADTHINDEX TRM load threshold index TRM load threshold index. It is the unique ID of the load threshold. 10~199 10~199 None None
Forward handover reserved

TRMLOADTH FWDRSVHOBW Reserved forward bandwidth for handover user 0~200000 0~200000 kbit/s 0
bandwidth
Backward handover
TRMLOADTH BWDRSVHOBW Reserved backward bandwidth for handover user 0~200000 0~200000 kbit/s 0
reserved bandwidth
If the available forward bandwidth is less than or equal to this value, the
Forward congestion remain
TRMLOADTH FWDCONGBW forward congestion alarm is emitted and forward congestion control is 0~200000 0~200000 kbit/s 0
bandwidth
triggered.
If the available backward bandwidth is less than or equal to this value,

Backward congestion
TRMLOADTH BWDCONGBW the backward congestion alarm is emitted and backward congestion 0~200000 0~200000 kbit/s 0
remain bandwidth
control is triggered.
Forward congestion clear If the available forward bandwidth is greater than this value, the forward
TRMLOADTH FWDCONGCLRBW 0~200000 0~200000 kbit/s 0
remain bandwidth congestion alarm is cleared and forward congestion control is stopped.
If the available backward bandwidth is greater than this value, the

Backward congestion clear
TRMLOADTH BWDCONGCLRBW backward congestion alarm is cleared and backward congestion control 0~200000 0~200000 kbit/s 0
remain bandwidth
is stopped.
Forward overload If the available forward bandwidth is less than or equal to this value, the
TRMLOADTH FWDOVLDRSVBW congestion remain forward overload congestion alarm is emitted and forward overload 0~200000 0~200000 kbit/s 0
bandwidth control is triggered.
Backward overload If the available backward bandwidth is less than or equal to this value,
TRMLOADTH BWDOVLDRSVBW congestion remain the backward overload congestion alarm is emitted and backward 0~200000 0~200000 kbit/s 0
bandwidth overload control is triggered.
Forward overload If the available forward bandwidth is greater than this value, the forward
TRMLOADTH FWDOVLDCLRRSVBW congestion clear remain overload congestion alarm is cleared and forward overload control is 0~200000 0~200000 kbit/s 0
bandwidth stopped.
Backward overload If the available backward bandwidth is greater than this value, the
TRMLOADTH BWDOVLDCLRRSVBW congestion clear remain backward overload congestion alarm is cleared and backward overload 0~200000 0~200000 kbit/s 0
bandwidth control is stopped.
Page 138
CAC Based on the Number of HSPA Users
CAC for HSDPA Users
When HSDPA_UU_ADCTRL is set to 1 , the HSDPA services admission decisions are based on the number of HSDPA users.
When a new HSDPA service attempts to access the network, the algorithm admits the service if the following conditions are met:
The number of HSDPA users in the cell does not exceed the maximum value specified by MaxHsdpaUserNum.
The number of HSDPA users in the cell does not exceed the user number of license.
The number of HSDPA users in NodeB does not exceed the maximum value specified by NodeBHsdpaMaxUserNum.
Otherwise, the HSDPA service is degraded to R99 service and another admission decision to performed.
CAC for HSUPA Users
When HSUPA_UU_ADCTRL is set to 1 ,the HSUPA services admission decisions are based on the number of HSUPA users.
When a new HSUPA service attempts to access the network, the algorithm admits the service if the following conditions are met:
The number of the HSUPA users in the cell does not exceed the maximum value specified by MaxHsupaUserNum.
The number of HSDPA users in the cell does not exceed the user number of license.
The number of the HSUPA users in NodeB does not exceed the maximum value specified by NodeBHsupaMaxUserNum.
Otherwise, the HSUPA service is degraded to R99 service to retry admission.
Page 139
CAC Based on the Number of HSPA Users
Parameters

Range Range Value
HSDPA_UU_ADCTRL: Control HSDPA UU Load

admission control algorithm. This swtich does not work
when uplink is beared on HSUPA and downlink is beared
HSDPA_UU_ADCTRL on HSDPA.
UCELLALGOSWITCH NBMCacAlgoSwitch 0,1 ON,OFF None OFF
HSUPA_UU_ADCTRL HSUPA_UU_ADCTRL: Control HSUPA UU Load
admission control algorithm. This switch does not work
when uplink is beared on HSUPA and downlink is beared
on HSDPA.
Maximum number of users supported by the HSDPA

Maximum HSDPA user channel. The user in this parameter refers to the user with
UCELLCAC MaxHsdpaUserNum 0~128 0~128 None 64
number services on the HSDPA channel, regardless of the
number of RABs carried on the HSDPA channel.
Maximum number of users supported by the HSUPA

Maximum HSUPA user channel. The user in this parameter refers to the user with
UCELLCAC MaxHsupaUserNum 0~128 0~128 None 20
number services on the HSUPA channel, regardless of the
number of RABs carried on the HSUPA channel.
Maximum number of HSDPA users of the NodeB. If the

NodeB Max HSDPA User HSDPA user access is rejected by the NodeB, you can
UNODEBALGOPARA NodeBHsdpaMaxUserNum 0~3840 0~3840 None 3840
Number infer that the HSDPA licenses are insufficient. New
HSDPA licenses are required.
Maximum number of HSUPA users of the NodeB. If the

NodeB Max HSUPA User HSUPA user access is rejected by the NodeB, you can
UNODEBALGOPARA NodeBHsupaMaxUserNum 0~3840 0~3840 None 3840
Number infer that the HSUPA licenses are insufficient. New
HSUPA licenses are required.
Page 140

UMTS&amp;HSPA RRM Algorithms and Parameters Training (Part1)

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

UMTS&amp;HSPA RRM Algorithms and Parameters Training (Part1)

Diunggah oleh

Hak Cipta:

Format Tersedia

UMTS/HSPA RRM Algorithms

1 Overview of Radio Resource Management (RRM)

2 Idle Mode Procedures and Parameters

3 Random Access & Paging Procedures and Parameters

4 Power Control Algorithm and Parameters

5 Admission Control Algorithm and Parameters

6 Load Control Algorithm and Parameters

7 Channel Switching Algorithm and Parameters

8 Handover Algorithm and Parameters

9 HSDPA RRM Algorithm and Parameters

10 HSUPA RRM Algorithm and Parameters

Ensure planned coverage for each targeted services.

Admission Control (AC) :

Packet Scheduler (PS) :

Load Control (LC):

Resource Manager (RM) :

Power Control (PC) :

Handover Control (HC) :

1 Overview of Radio Resource Management (RRM)

2 Idle Mode Procedures and Parameters

3 Random Access &Paging Procedures and Parameters

4 Power Control Algorithm and Parameters

5 Admission Control Algorithm and Parameters

6 Load Control Algorithm and Parameters

7 Channel Switching Algorithm and Parameters

8 Handover Algorithm and Parameters

9 HSDPA RRM Algorithm and Parameters

10 HSUPA RRM Algorithm and Parameters

The UE can receive cell broadcast service (CBS) messages.

The relationship between these 3 processes is shown in the figure.

The cell is not barred.

In Automatic mode, if no last registered PLMN exists or is available,

1. Home PLMN (HPLMN), if not previously selected, according to the

2. Each PLMN in the user-controlled PLMNs list in the USIM, if present,

3. Each PLMN in the operator-controlled PLMNs list in the USIM, in

4. Other PLMNs, according to the high-quality criterion, in random order.

5. Other PLMNs that do not fulfill high-quality criterion, in order of

GUI Value Actual Value Recommended

Indicating whether the cell is reserved for

Actual Value Recommended

Indicating whether the UE in idle mode is allowed to reselect

This parameter is valid when [Cell barred indicator for SIB3] is

Indicating whether the UE in connected mode is allowed to

Indicating whether the UE in idle mode is allowed to reselect

This parameter is valid when [Cell barred indicator for SIB4] is

Most system information parameters are determined by the RNC.

The Node B is informed about the parameters via the NBAP

System information is organised in System Information Blocks

There is a huge amount of SIBs, which have to be read by the

System Information Block 1 (SIB 1)

System Information Block 2 (SIB 2)

System Information Block 3 (SIB 3)

System Information Block 4 (SIB 4)

System Information Block 5 (SIB 5)

System Information Block 6 (SIB 6)

System Information Block 11 (SIB 11)

System Information Block 12 (SIB 12)

SIB13: contains ANSI-41 system information.

SIB14: contains the information in TDD mode.

SIB15: contains the position service information.

SIB17: contains the configuration information for TDD.

System Information Change Indication

Please note, that UEs in the CELL_DCH sub-state are

Determine whether some system information

UMTS&HSPA RRM Algorithms and Parameters Training (Part1)

UMTS&HSPA RRM Algorithms and Parameters Training (Part1)