Volume II - Ericsson Field Guide For UTRAN P1-Lite: Feature Parameters and Best Practices

Network Services Volume II – Ericsson Field Guide for UTRAN P1-Lite
Volume II – Ericsson Field Guide for

UTRAN P1-Lite: Feature Parameters and
Best Practices
Network Document ND-00150 Rev. 1.1 11/28/2005
Overview
Volume II of the Ericsson Field Guide for UTRAN defines Cingular’s accepted practices for optimization of
the Radio Access portion of the UMTS network for Ericsson WRAN P4 UM3 (November 2005 launch
version). The algorithms by which subscriber devices interact with the network are described in detail.
Recommendations are provided that produce the best performance in the network for each type of
interaction
This Field Guide is broken into 11 sections including a description of:

• New features released in the most recent RNS software version
• WCDMA design and optimization concepts
• A chronological step by step description of how the subscriber device and network interact; Idle
Mode, Call Establishment and Connected Mode are introduced and the algorithms associated
with each are described and involved parameters are explained.
• OSS access procedures and methods.
The document concludes with an index, tables wherein all configurable parameters and supporting details
are listed and a list of well deserved credits.
IMPORTANT: This document is the result of an ongoing collaborative effort

between Cingular Market, Regional, National and Ericsson staff and management.
It will continue to be updated with the latest findings in the areas of optimization
and vendor improvement through the use of commissioned studies and successive
vendor software and hardware updates.
ND-00150 CINGULAR WIRELESS CONFIDENTIAL & PROPRIETARY Page 1 of 71

Rev. 1.1 11/28/2005 Use pursuant to Company instructions © 2005 Cingular Wireless
Contents
1. About This Document....................................................................................................................... 6
1.1 Purpose ....................................................................................................................................... 6
1.2 Scope .......................................................................................................................................... 6
1.3 Audience ..................................................................................................................................... 6
1.4 Related Documentation............................................................................................................... 6
1.5 Acronyms and Terms .................................................................................................................. 6
1.6 Trademarks ................................................................................................................................. 6
1.7 Conventions ................................................................................................................................ 7
1.8 Contacts ...................................................................................................................................... 7
2. New Features and Parameters in WRAN P4 UM2 (P1-Lite) ........................................................... 8
2.1 New Features.............................................................................................................................. 8
2.2 New or Modified Parameters....................................................................................................... 8
3. Significant KPI Impact Parameters .................................................................................................. 9
4. Design Criteria ............................................................................................................................... 10
4.1 UE Capabilities.......................................................................................................................... 10
4.1.1 Frequency Bands.............................................................................................................. 10
4.1.2 Channel Numbering Scheme (UARFCN) ......................................................................... 10
4.1.3 Power Classes .................................................................................................................. 11
4.2 UE Category.............................................................................................................................. 12
4.3 Link Budget ............................................................................................................................... 12
4.4 Basic Design Requirements...................................................................................................... 13
4.4.1 Pilot Pollution .................................................................................................................... 13
4.4.2 Neighbor List Determination ............................................................................................. 14
4.4.3 Scrambling Code Usage................................................................................................... 14
4.5 Measurement Fundamentals .................................................................................................... 15
4.5.1 PCPICH ............................................................................................................................ 15
4.5.2 PCPICH RSCP ................................................................................................................. 15
4.5.3 CPICH Ec/No (Ec/Io) ........................................................................................................ 16
4.5.4 Eb/No ................................................................................................................................ 16
4.5.5 SIR .................................................................................................................................... 17
4.5.6 BLER................................................................................................................................. 17
5. Parameters Described Within Context........................................................................................... 18
5.1 Idle Mode................................................................................................................................... 18

5.1.1 Cell Search Procedure...................................................................................................... 18

5.1.2 PLMN Selection ................................................................................................................ 19
5.1.3 IMSI and GPRS Attach ..................................................................................................... 24
5.1.4 Location and Routing Area Updates................................................................................. 30
5.2 Call Establishment .................................................................................................................... 33
5.2.1 Radio Access Bearer ........................................................................................................ 33
5.2.2 Mobile Origination / Termination....................................................................................... 35
5.3 Mobility and Connection Management...................................................................................... 42
5.3.1 Measurement Fundamentals ............................................................................................ 42
5.3.2 Cell Reselection in Idle Mode or Cell_FACH.................................................................... 43
5.3.3 Handover in Connected Mode using Cell_DCH state ...................................................... 45
5.3.4 HS Cell Change ................................................................................................................ 47
5.3.5 Channel Switching ............................................................................................................ 47
5.3.6 Congestion Control ........................................................................................................... 50
5.3.7 Uplink and Downlink Power Control ................................................................................. 51
6. OSS Overview................................................................................................................................ 54
6.1 Configuration Management....................................................................................................... 55
6.1.1 Configuration Access Procedures .................................................................................... 55
6.1.2 Configuration Methods...................................................................................................... 55
6.2 Performance Management........................................................................................................ 56
6.2.1 Performance Access Procedures ..................................................................................... 56
6.2.2 Ericsson Counter Types ................................................................................................... 57
6.2.3 Call Trace Capability......................................................................................................... 58
6.3 Fault Management .................................................................................................................... 59
6.3.1 Alarm Status Matrix .......................................................................................................... 59
6.3.2 Alarm List Viewer .............................................................................................................. 59
6.3.3 Alarm Log Browser ........................................................................................................... 59
7. Counter Activation.......................................................................................................................... 60
8. Reference Documents ................................................................................................................... 61
9. Parameter Reference..................................................................................................................... 62
Appendix A Consulted List ................................................................................................... 68
Appendix B Index.................................................................................................................. 70
Figures
Figure 1 Slot and Frame Structure......................................................................................................... 18

Figure 2 Power Ramping on RACH ....................................................................................................... 25

Figure 3 RRC Connection Signaling Flow ............................................................................................. 26
Figure 4 Downlink DPCCH Power ......................................................................................................... 28
Figure 5 OSS Connectivity..................................................................................................................... 54
Tables
Table 1 Operating Bands ....................................................................................................................... 10
Table 2 UARFCN List for Bands II and V............................................................................................... 11
Table 3 UE Power Classes .................................................................................................................... 11
Table 4 UE Categories........................................................................................................................... 12
Table 5 Link Budget ............................................................................................................................... 12
Table 6 Master Information Block (MIB) Contents ................................................................................. 20
Table 7 System Information Block 1 (SIB 1) Contents .......................................................................... 21
Table 8 System Information Block 3 (SIB 3) .......................................................................................... 21
Table 9 System Information Block 5 (SIB 5) .......................................................................................... 21
Table 10 System Information Block 7 (SIB 7) ........................................................................................ 22
Table 11 System Information Block 11 (SIB 11) .................................................................................... 22
Table 12 System Information Block 12 (SIB 12) .................................................................................... 22
Table 13 Idle Mode Configurable Parameters ....................................................................................... 31
Table 14 Call Establishment Configurable Parameters ......................................................................... 41
Table 15 Mobility and Connection Management Configurable Parameters .......................................... 51
Table 16 Configuration Management Access Procedures .................................................................... 55
Table 17 Business Object Access Procedure........................................................................................ 57
Table 18 Alphabetized Parameter Reference........................................................................................ 62

Document Revision History

This table identifies content revisions made to this document.
Date Rev Revision Description Writer Sponsor
11/01/2005 1.0 Release version Michael Adnan Naqvi

Noah
11/28/2005 1.1 Updates to “Cingular Recommended” parameter values Michael Greg
based upon Field Optimization. Noah Scharosch
RACI
This table identifies RACI team members.
Accountable Responsible Consulted Informed
Greg Scharosch Michael Noah Market Engineering Mike Pietropola

Regional Engineering Lee Rudolph
Regional OSS Support Adnan Naqvi
National Field Support John Dapper
Strategic Planning Ali Jabbary
National Quality
Ericsson Support
For details see Appendix A.
Copyright © 2005 by Cingular Wireless Services, Inc.
All rights reserved. No part of the contents of this document may be reproduced or transmitted in any
form without the written permission of the publisher.

1. About This Document

This section includes information about this document.
1.1 Purpose
The primary intention of this document is to serve as a common point for understanding
and reference. This volume includes recommendations for all configurable RNC and
Node B parameters. The recommendations made within this document are the result of
collaborative efforts between all groups involved (see 1.3).
1.2 Scope
This document is mainly based upon Ericsson’s UTRAN implementation, focusing on the
interaction between the User Equipment and UTRAN. For completeness, some facets of
the Core Network are included, e.g. Paging, Routing and Location Area Update
procedures, i.e. non-access stratum.
1.3 Audience
The audience for this document includes Cingular Market, Region and National level
Engineers and Technicians responsible for Ericsson UTRAN Optimization and
Maintenance.
1.4 Related Documentation
See Section 8.
1.5 Acronyms and Terms
All acronyms and terms are fully spelled out within the document.
1.6 Trademarks
The trademarks used in this document are the property of their respective owners.

1.7 Conventions
The following conventions are used throughout this document:
• The term “call” refers to any type of user plane connection between UE and the Core
Network. It is not specific to voice or data - UE originated or terminated. It
specifically does not include any type of signaling used to support the communication
of user information.
• The term “function” refers to Ericsson’s implementation of a certain portion of the

3GPP specification. A function is limited to satisfying a specific action taken by either
the network or UE. For example, the process of originating a call is referred to as a
function. Once the call has been originated, handing the call over is considered a
function and ending the call is a function. Within this document, parameters are
explained relative to the functions they support.
• All Ericsson configurable parameters are expressed in boldItalic.
• All references to Radio Access Bearers (RABs) are denoted as UL/DL where UL is
the Uplink RLC Data rate in kilobits per second and DL is the Downlink Data rate in
kilobits per second.
1.8 Contacts
For questions or comments about this document's technical content or to request

changes to the document, contact:
Michael Noah, Sr. System Engineer – National Field Support

Desk: 425 580 6716
Wireless: 425 580 6716
E-mail: michael.noah@cingular.com

2. New Features and Parameters in WRAN P4 UM2 (P1-Lite)

This section provides a summary of feature updates and parameters provided with this
version of RNS software.
2.1 New Features
As this is the initial release of Volume II of the Ericsson UTRAN Field Guide, all functions
and features are considered standard.
2.2 New or Modified Parameters
As this is the initial release of Volume II of the Ericsson UTRAN Field Guide, all
parameters are considered standard.

3. Significant KPI Impact Parameters

All parameters within this document will to a certain degree impact Key Performance
Indicators (KPI). The parameters within this section, in no particular order, will
significantly impact KPI’s. Some, if not adjusted as the UMTS system matures, may
especially impact the KPI’s. This list will be modified as information is gained through
collaborative testing, data collection, and analysis with Engineering Field Teams and
Regions. Suggestions are:
Idle Mode and Paging
Admission Control
Congestion Control
Handover

4. Design Criteria
This section mainly covers areas specified in the 3GPP standard. It presents an
overview of the spectrum allocation, UARFCN designation and UE Power Class. A
fundamental Link Budget is provided. The rest of the section provides a high level
optimization concept for WCDMA including Pilot Pollution optimization, neighbor
designation guidelines, and a detailed description of the fundamental W-CDMA
measurements CPICH RSCP and CPICH Ec/No.
4.1 UE Capabilities
Multiband support for the United States (800/1900 MHz) was not defined until Release 6
of the 3GPP specification. For this reason, Release 6 is the reference for this section.
See reference [3a]
4.1.1 Frequency Bands
The frequency bands specified are shown in the table below including the separation (in
MHz) between uplink and downlink frequencies. Cingular operates UMTS at 800 MHz
(Band V) and 1900 MHz (Band II). The rest of the bands listed are included for
completeness.
Table 1 Operating Bands
Operating Band UL Frequencies DL Frequencies TX-RX Separation

I 1920 – 1980 MHz 2110 – 2170 MHz 190 MHz
II 1850 – 1910 MHz 1930 – 1990 MHz 80 MHz
III 1710 – 1785 MHz 1805 – 1880 MHz 95 MHz
IV 1710 – 1755 MHz 2110 – 2155 MHz 400 MHz
V 824 – 849 MHz 869 – 894 MHz 45 MHz
VI 830 – 840 MHz 875 – 885 MHz 45 MHz
4.1.2 Channel Numbering Scheme (UARFCN)
The UTRA Absolute Radio Frequency Channel Number allows easy reference to the
spectrum allocated to UMTS. Distinct UARFCNs are used for uplink and downlink
frequencies as opposed to a single UARFCN for a pair of UL/DL frequencies. A
UARFCN occupies 5 MHz of spectrum.
The specification allows for two methods to be used to associate center carrier frequency
to UARFCN.
– “General” UARFCN method. Each UARFCN is defined with a specific center

frequency. Beginning at 0 Hz, the UARFCN is incremented by 1 with each increment
in frequency of 200 kHz. The UARFCN corresponding to the center frequency is
calculated by finding the product of 5 and the center frequency (in MHz); i.e.
UARFCN = 5 * Frequency (MHz). When using the “general” method, this formula
applies regardless of direction (uplink / downlink) and band.

– “Additional Channels” UARFCN method. The “Additional Channels” are specified

according to the table below. These channels are shifted by 100 KHz relative to the
“general” URFCN definition. For Band II, the UARFCN is calculated by finding the
product of 5 and the center carrier frequency (in MHz) minus 1850.1 MHz, i.e
UARFCN = 5 * (Frequency in MHz – 1850.1 MHz). For Band V, the UARFCN is
calculated by finding the product of 5 and the center carrier frequency (in MHz) minus
670.1 MHz, i.e UARFCN = 5 * (Frequency in MHz – 670.1 MHz).
Either the “General” or “Additional Channels” method can be used to designate

UARFCNs based upon where you choose to locate UMTS within your licensed
spectrum.
Table 2 UARFCN List for Bands II and V
UL UARFCN UL Center DL UARFCN DL Center PCS / Cellular

Frequency (MHz) Frequency (MHz) Band
12 1852.5 412 1932.5 PCS – A
37 1857.5 437 1937.5 PCS – A
62 1862.5 462 1942.5 PCS – A
87 1867.5 487 1947.5 PCS – D
112 1872.5 512 1952.5 PCS – B
137 1877.5 537 1957.5 PCS – B
162 1882.5 562 1962.5 PCS – B
187 1887.5 587 1967.5 PCS – E
212 1892.5 612 1972.5 PCS – F
237 1897.5 637 1977.5 PCS – C3
262 1902.5 662 1982.5 PCS – C4
287 1907.5 687 1987.5 PCS – C5
782 826.5 1007 871.5 Cellular – A
787 827.5 1012 872.5 Cellular – A
807 831.5 1032 876.5 Cellular – A
812 832.5 1037 877.5 Cellular – A
837 837.5 1062 882.5 Cellular – B
862 842.5 1087 887.5 Cellular – B
4.1.3 Power Classes
The table below indicates the UE Power Classes specified as of Release 6. Note the
maximum power is the same for all bands within Power Classes 3 and 4. The power in
dBm refers to the maximum total output capability of the UE at the antenna connector
and not to the maximum power output of any particular Physical Channel. See reference
[3b]
Table 3 UE Power Classes
Operating Power Class 1 Power Class 2 Power Class 3 Power Class 4

Band Power Tol (dB) Power Tol (dB) Power Tol (dB) Power Tol (dB)
(dBm) (dBm) (dBm) (dBm)
I +33 +1/-3 +27 +1/-3 +24 +1/-3 +21 +2/-2
II - - - - +24 +1/-3 +21 +2/-2

III - - - - +24 +1/-3 +21 +2/-2

IV - - - - +24 +1/-3 +21 +2/-2
V - - - - +24 +1/-3 +21 +2/-2
VI - - - - +24 +1/-3 +21 +2/-2
4.2 UE Category
HSDPA capable UEs are further categorized based upon their throughput capabilities.
The table below includes all of the UE Categories as defined in the 3GPP Specification.
Note that Category 11 and 12 UEs only support QPSK.
Table 4 UE Categories
HS-DSCH Maximum Minimum inter- Maximum number of bits Total number of

Category number of HS- TTI interval of an HS-DSCH transport soft channel bits
DSCH codes block received within
received an HS-DSCH TTI
Category 1 5 3 7298 19200
Category 2 5 3 7298 2889
Category 3 5 2 7298 2880
Category 4 5 2 7298 38400
Category 5 5 1 7298 57600
Category 6 5 1 7298 67200
Category 7 10 1 14411 115200
Category 8 10 1 14411 134400
Category 9 15 1 20251 172800
Category 10 15 1 27952 172800
Category 11 5 2 3630 QPSK Only 14400
Category 12 5 1 3630 QPSK Only 28800
4.3 Link Budget
In this simple presentation of the link budget, only the maximum transmit power and
receive sensitivity of the Node B and UE at their respective antenna connectors is
considered. The difference between the maximum transmit power of one node and the
maximum receive sensitivity at the other node is considered to be the maximum
allowable path loss. The resulting uplink and downlink path losses are compared
resulting in a difference in dB between the uplink and downlink maximum path losses.
Table 5 Link Budget
Downlink Value Notes

Max Tx Power (dBm) +30 Manually calculated (balanced) Node B Tx Pwr.
Max Rx Sensitivity (dBm) -115 Specification based UE Rx level at 0.1% BLER. See [3c]
Max path loss (dB) 145 Difference between Node B Tx and UE Rx Sens.
Upink
Max Tx Power (dBm) +24 Max Tx Power for a Power Class 3 UE. See [3b]
Max Rx Sensitivity (dBm) -121 Specification based Node B Rx level at 0.1% BLER. See
[3d]
Max path loss (dB) 145 Difference between UE Tx and Node B Rx Sens

Difference (dB) 0 Difference between UL and DL path losses

The only non-specified value is “Max Tx Power (dBm)” for the Downlink. This value was
chosen specifically because it balances the Uplink and Downlink path losses.
A complete Link Budget analysis would include variables such as LNA existence, various
Radio Access Bearers due to their difference in gain as a function of Spreading Factor (a
description of Spreading Factor is provided in the Measurement Fundamentals section),
cable loss, Antenna and Macro Diversity (a description of Macro Diversity is provided in
the Mobility Management section), etc.
4.4 Basic Design Requirements
This section describes fundamental design guidelines that are required for basic system
operation. It is strongly suggested that these basic requirements be satisfied before
further optimization of the radio network is pursued.
For example, if this were an FDMA/TDMA network such as GSM or IS-136, frequency
planning would be included in this section. However, since frequency reuse is not a
primary consideration in WCDMA, it is not included.
4.4.1 Pilot Pollution
Since the basis of WCDMA is to allow for multiple access based upon code division
instead of frequency division, care must be taken to manage over-propagation of cells in
the network. As mentioned later in the Neighbor List Determination section, all cells that
provide coverage in a given geographic area must be neighbors; else they are seen as
noise. An over-propagating cell would therefore need to have neighbor relationships with
all cells with which it overlaps. This of course would mean the over-propagating cell
would be heavily utilized and would require a very large capacity.
Over-propagating cells also cause Call Establishment problems. Call Establishment has
its own section within this guide, but in short; a UE establishes calls on a single cell
based upon its having the best Common Pilot Channel (CPICH) signal level and/or
quality. If a cell has propagated into an area where there are no neighbors assigned from
it to other closer cells in terms of distance to the mobile, the call will drop. Even if there
are neighbors assigned, the noise level will be increased for a short time until the
surrounding cells have been added to the call through the process of Soft Handover.
Fundamentally, Pilot Pollution is Common Pilot Channel (CPICH) power where it is not
desired due the over-propagation of cells. The current method used to reduce Pilot
Pollution requires a drive test of the area with a CPICH scanner. CPICH propagation is
then analyzed graphically (maps) and statistically. The criteria for Pilot Pollution is 4 or
more Common Pilot Channels serving within 5 dB of each other in the same geographic
area. In most cases, power changes, down-tilts, azimuth changes or antenna changes
are required to reduce over-propagation.

4.4.2 Neighbor List Determination
Neighbor relationships fall into 3 categories where UMTS and the interaction between
UMTS and GSM are concerned.
– Intra-UARFCN Neighbors. These neighbor relationships are assigned wherever

there is coverage overlap between cells having the same UARFCN. These neighbor
relationships allow for Soft Handover. It is important to assign neighbor relationships
between overlapping cells in order to allow multiple cells covering the same
geographic area to collectively serve a given UE.
A cell covering an area, but not in the other server’s neighbor lists is seen as noise by
the UE which causes the UE compensate by requiring more power.
– Inter-UARFCN Neighbors. These neighbor relationships allow for Hard Handover

between cells with different UARFCNs. The neighboring UARFCNs can be in either
the same band or in a different band. Neighbor relationships should be assigned
between all overlapping UARFCNs.
– Inter-RAT Neighbors. Inter-RAT neighbor relationships allow for Hard Handover

between UMTS and GSM. The UMTS coverage area in all Cingular markets is a
subset of the GSM coverage. With one exception, Inter-RAT neighbors between all
UMTS and GSM bands should be assigned at the boarder between the UMTS / GSM
coverage and the GSM only coverage areas. With one exception, Inter-RAT
neighbors should also be assigned to allow UEs to handover between UMTS and
GSM where there are no suitable UMTS carriers (coverage holes) within the UMTS
coverage area.
Exception – Neighbor relationships for speech must not be defined from GSM to UMTS
in order to avoid E911 calls handing back to UMTS before they are ended.
Ericsson further defines neighbor types based upon how they exist between different
RNCs and technologies (GSM vs. UMTS).
– UTRAN Relations. All intra-RNC neighbor definitions including Intra and Inter-
UARFCN.
– External UTRAN Relations. All inter-RNC neighbor definitions including Intra and
Inter-UARFCN.
– GSM Relations. All Inter-RAT neighbor definitions.
4.4.3 Scrambling Code Usage
Each cell in the network is assigned a Primary Scrambling Code. The

primaryScramblingCode parameter is an integer value 0-511 inclusive. For the interest
of this section, it is important to avoid co-UARFCN co-Scrambling Code use in the same
geographic area. However, if there are more than 512 cells in use, Scrambling Codes
must be reused very carefully. It is suggested that reuses of Scrambling Code among
the same UARFCN only exist where there is ample isolation.

Optionally, Scrambling Codes can also be divided into 64 groups of 8 codes each.
Scrambling Code planning would then be much like frequency planning with a reuse of
64. The advantage to this type of planning could be a less complex code search
procedure for the UE.
4.5 Measurement Fundamentals
Before we get into Idle Mode, Call Establishment and Mobility Management, it is
important to understand the fundamental measurements used by the UE and RNS to
make radio related decisions. These measurements are commonly used when
referencing signal level (RSCP) and signal quality (Ec/No). The signal level (RSCP) and
signal quality (Ec/No) of the Primary Common Pilot Channel (CPICH) define the
coverage area of the cell. SIR and BLER are also described as they are used to control
uplink and downlink power.
4.5.1 PCPICH
The Primary Common Pilot Channel (CPICH) is one of the continuously transmitted
downlink Physical Channels. It is unique in that it is the reference used by the UE to
make radio related decisions for Cell Selection, Cell Reselection, Soft (intra-frequency)
Handover and Hard (inter-frequency) Handover. All signal level and quality
measurements are made based upon or relative to the Primary Common Pilot Channel.
The power of Primary Common Pilot Channel is set via the primaryCpichPower
parameter to an absolute value (dBm) per cell. All other downlink Physical Channels on
the cell are set relative (dB) to the Primary Common Pilot Channel. Since proper
downlink power settings are necessary to allow the UE to enter Idle Mode, they are
covered in detail in the Idle Mode section.
4.5.2 PCPICH RSCP
The Primary Common Pilot Channel Received Signal Code Power, commonly called
“RSCP”, is simply the received power (dBm) of the Common Pilot Channel.
In order to really understand Received Signal Code Power (RSCP), it is important to

understand the basic concept of spreading and de-spreading. Spreading is the process
of taking a signal, in this case the Primary Common Pilot Channel (CPICH) signal, and
transforming it into a signal that occupies a much larger bandwidth. This is done in two
steps. First, the original signal is binary multiplied by a Spreading Code. The Spreading
Code, also known as the Channelization Code or Orthogonal Variable Spreading Factor
(OVSF) Code is unique within the cell and when binary multiplied by Primary Common
Pilot Channel (CPICH) signal allows it to be isolated from the other spread signals within
the cell.

The Primary Common Pilot Channel (CPICH) bits are referred to as “symbols” and the
bits in the Spreading Code are referred to as “chips”. The ratio of chips to symbols is
called the Spreading Factor. In this case, the chip rate is 3.84 mega-chips per second
and the symbol rate of the Primary Common Pilot Channel (CPICH) is 15 kilo-symbols
per second. 3,840,000 / 15,000 = 256. The Primary Common Pilot Channel (CPICH)
uses a Spreading Factor of 256. Seen yet another way, each Primary Common Pilot
Channel (CPICH) symbol is spread into 256 chips causing the spread signal to occupy
256 times the bandwidth of the original signal.
Second, since the Spreading Codes are only unique within a cell, the signal must be
further “scrambled” to make it unique within the geographic coverage area. This is done
by exclusively ORing the already spread signal with a primaryScramblingCode. There
are a total of 512 Primary Scrambling Codes available, so co-UARFCN co-Primary
Scrambling Code use might be necessary in geographic areas with greater than 512
cells. See the Scrambling Code Selection section for cautions.
At the other end, receiving the symbols is simply a matter of first de-scrambling, then de-
spreading the signal using the same scrambling and spreading codes used to initially
spread the symbols.
4.5.3 CPICH Ec/No (Ec/Io)
The Primary Common Pilot Channel (CPICH) received Energy per Chip (Ec) to Noise
(No) ratio, commonly referred to as Eee-Cee-N-Not, is used to measure the received
quality of the Primary Common Pilot Channel (CPICH). It is the ratio of the received
Energy per Chip to the Noise power spectral density in the band. In this case, the Chip
Energy (Ec) is the power of the spread Primary Common Pilot Channel (CPICH) at the
receiver. Ec is equivalent to Received Signal Code Power (RSCP) in that both measure
the power of the Primary Common Pilot Channel (CPICH); the only difference being Ec is
the power of the spread signal and RSCP is the power measured after de-spreading. No
(N-not) is the received wide band power, including thermal noise and noise generated in
the receiver, within the receiver’s bandwidth.
The term Ec/Io is also used to denote Primary Common Pilot Channel (CPICH) quality
with the only difference being the denominator where Io includes interference only. The
use of the term Ec/Io is rapidly giving way to Ec/No due mainly to the fact that receivers
do not discern Noise from Interference and as such, cannot accurately measure Ec/Io.
However, Io is commonly used in RF Design (propagation) tools.
4.5.4 Eb/No
Eb/No, commonly referred to as Eee-Bee-N-Not or ebno, is the received energy per Bit
(symbol) of the signal over the received wide band power, including thermal noise and
noise generated in the receiver, within the receiver’s bandwidth. The fundamental
difference between Eb/No and Ec/No is Spreading Factor. Ec is of course the energy of
the spread signal. By factoring in the Spreading Factor, we get the energy of a bit or
symbol over the received wide band power, including thermal noise and noise generated

in the receiver, within the receiver’s bandwidth. Eb/No therefore equals Ec/No *
Spreading Factor.
Eb/No is commonly used when referencing Physical Channels that carry user data or
signaling as opposed to Physical Channels such as the Common Pilot Channel
(CPICH) which only carries repetitive data.
4.5.5 SIR
SIR is the Signal to Interference Ratio. It is equivalent to (RSCP / ISCP) * Spreading

Factor. RSCP is defined above; ISCP is the Interference Signal Code Power which is
essentially the interference from other cells excluding noise. SIR is a quality metric used
to maintain appropriate power levels in the uplink and downlink. The UTRAN uses a very
fast power control technique called “closed-loop power control” where power is adjusted
1500 times per second in order to maintain the Signal to Interference Ratio at a
configured target value. SIR is further explained in the Mobility Management section.
4.5.6 BLER
BLER is the Block Error Rate at the Transport Channel Layer. CPICH RSCP, CPICH
Ec/No, Eb/No and SIR are all measurements of the Physical Layer. The Transport
Channel layer resides above the Physical Layer. At the Transport Layer, data from the
Physical Layer is put into CRC encoded Blocks. If a Block fails a CRC check, it is
considered in error. BLER indicates the percentage of these Blocks in error.

5. Parameters Described Within Context
5.1 Idle Mode
Idle Mode is a state every UE enters when it is powered on. It is also the state in which
each powered on UE spends most of its time. In this state, the UE must be ready and
able to Originate and Terminate calls. This section includes cell selection, but does not
include cell reselection as cell reselection is a function of mobility and as such is covered
in the Mobility Management section.
5.1.1 Cell Search Procedure
After either power up or entry into network coverage, the UE must begin to read
information on the BCCH. The Broadcast Control CHannel (BCCH) is used to broadcast
System Information to all UEs within its coverage area. This is accomplished in 3 steps.
However, before the 3 steps are described, it is important to understand the Slot and
Frame structure of the downlink. A Slot is made up of 2560 Chips (meaning it’s a spread
signal). 15 Slots make up one 10 ms Frame. 73 Frames make up one Superframe.
Figure 1 Slot and Frame Structure
720 ms
F0 F1 F2 ... F70 F71 ... Superframe = 72 frames
10 ms
S0 S1 S2 ... S13 S14 Frame = 15 Slots
.667 ms
... Slot = 2560 Chips
1. Slot Synchronization with the downlink is acquired by correlating the Primary

Synchronization Code, common to every cell and known by all UEs, with the Primary
Synchronization Channel (P-SCH) transmitted on the downlink. It is important to
know that neither the Primary nor the Secondary Synchronization Channel are ever
Scrambled using the Primary Scrambling Code. Each cell serving in the UE’s
geographic area transmits a Primary Synchronization Channel (P-SCH). The cell
that the UE is able to obtain the strongest correlation with is chosen as the serving
cell. The Primary Synchronization Channel (P-SCH) power level is controlled by the
primarySchPower parameter.

The process in which UARFCNs are chosen for a Slot Synchronization attempt is UE
implementation dependant.
2. Even though the UE has acquired Slot Synchronization, it still needs to know the Slot
number within a Frame (Frames have 15 Slots) so it can know where the Frame
begins. It does this by correlating one of the 16 Secondary Synchronization Codes
with the Secondary Synchronization Channel (S-SCH). It is important to know that
neither the Primary nor the Secondary Synchronization Channel are ever Scrambled
using the Primary Scrambling Code. The 16 Secondary Synchronization Codes are
used to form 64 unique Secondary Synchronization Channel sequences. Once the
UE has decoded 15 successive Secondary Synchronization Codes, it not only knows
where the Frame begins, but the Code Group (used in step 3) as well. The UE is
now Frame Synchronized. The Secondary Synchronization Channel (S-SCH) power
is controlled by the secondarySchPower parameter.
3. Now that the UE is Slot and Frame Synchronized, it must still determine the cell’s
Primary Scrambling Code before it can begin to read the Broadcast Control CHannel
(BCCH). In step 2, the UE discovers the cell’s Code Group. Each Code Group
identifies 8 possible Primary Scrambling Codes. The correct Primary Scrambling
Code is determined by correlating each of the 8 possibilities with the Common Pilot
Channel (CPICH). Once the correct Primary Scrambling Code has been found, the
UE can detect the Primary Common Control Physical Channel (P-CCPCH) which
carries the Broadcast Channel (BCH) Transport Channel which carries the Broadcast
Control CHannel (BCCH) Logical Channel. The cell’s Primary Scrambling Code is
configured using the primaryScramblingCode parameter.
The Primary Common Control Physical Channel (P-CPPCH) carries the System Frame
Number (SFN) which is used as the timing reference for all Physical Channels. The
System Frame Number (SFN) ranges from 0 to 4095 (inclusive).
For more information about Slot and Frame synchronization, see [3e]
5.1.2 PLMN Selection
Now the UE is able to read the Broadcast Control CHannel (BCCH). If the UE finds its
subscribed Public Land Mobile Network (PLMN) it then continues to read System
Information from the BCCH.
5.1.2.1 Information on the Broadcast Control CHannel (BCCH)
The Broadcast Control Channel (BCCH) broadcasts information consisting of a Master

Information Block (MIB), up to 18 System Information Blocks (SIB) types numbered 1-18,
and up to 2 Scheduling Blocks (SB). Ericsson has implemented a Master Information
Block (MIB) and System Information Blocks (SIB) types 1, 3, 5, 7, 11 and 12.
The following breakdown of the Master Information Block (MIB) and System Information
Blocks (SIBs) provides an indication of where the UE gets the information necessary in
order to maintain Idle Mode, Establish Calls, and Manage Mobility. The “Layer 3

Message” column was derived from TEMS 6.0 log files. The Purpose column provides a
brief description of where the parameter applies.
– Master Information Block (MIB). The Master Information Block (MIB) is sent at a
fixed rate of every 8 Frames (80ms). It contains information that identifies the
network as well as the start position and interval of each of the System Information
Blocks (SIBs). The Master Information Block (MIB) also contains a Value Tag
associated with each System Information Block supported. If the Value Tag for any
supported System Information Block changes, the UE must read that System
Information Block (SIB). In order to avoid the UE having to read each and every
Master Information Block (MIB), a Paging Type 1 message is sent to all UEs
indicating a Value Tag has changed in the Master Information Block (MIB).
Table 6 Master Information Block (MIB) Contents
Ericsson Parameter Layer 3 Purpose

Message
mcc MCC: The Mobile Country Code
mnc MNC: The Mobile Network Code
sib1StartPos Repx : y Sets the start position of SIB 1 where x equals the repetition
period and y equals the SFN / 2.
sib1RepPeriod sib-Pos : repx Sets the SIB 1 repetition period where x equals a number of
Frames.
Frames.
Frames.
Frames.
Frames.
Frames.
– System Information Block 1 (SIB 1). System Information Block 1 (SIB 1) contains
Location Area (LA), Routing Area (RA) information and timer parameters. Since this
System Information Block contains the Location Area (LA) and Routing Area (RA)
information, it must also be read when a LA or RA boarder is crossed. The
parameter sib1PLMNScopeValueTag controls when System Information Block 1
(SIB 1) is read and must be set so that neighboring LAs and RAs have different
values.

Table 7 System Information Block 1 (SIB 1) Contents
Ericsson Parameter Layer 3 Message Purpose

lAC LAC : xxxxx Location Area Code used by CS Core Network
t3212 CS domain – T3212 : x Periodic Location Area Update interval in deci-
minutes, e.g. 1 = 6 minutes.
att CS domain – ATT : x Indicates if the UE is allowed to IMSI Attach to the CS
Core Network
cnDrxCycleLengthCs CS domain – DRX- Discontinuous Reception (DRX) Cycle Length
CycleLengthCoeff : k Coefficient.
rAC RAC : xx Routing Area Code used by PS Core Network
nmo NMO : x Network Mode of Operation
cnDrxCycleLengthPs PS domain – DRX- Discontinuous Reception (DRX) Cycle Length
CycleLengthCoeff : k Coefficient.
parameters for cell selection and reselection.
Table 8 System Information Block 3 (SIB 3)

qualMeasQuantity cellSelectQualityMeasure : x Determines if cell ranking uses quality
measurements.
sRatSearch s-SearchRAT : x Used to determine when Inter-RAT
measurements begin.
sHcsRat s-HCS-RAT : x Used to determine when Inter-RAT
measurements begin.
qQualMin q-QualMin : x Used in Cell Selection and Re-selection
qRxLevMin q-RxlevMin : x Used in Cell Selection and Re-selection
qHyst2 q-Hyst-I-S : x Used in Cell Selection and Re-selection
treSelection t-Reselection-S : x Used in Cell Selection and Re-selection
maxTxPowerUl maxAllowedUL-TX-Power : x Max UE power allowed on the uplink.
cellReserved CellReservedForOperatorUse : x Indicates if the cell is reserved by the
operator.
parameters that determine the configuration of Common Physical Channels
(PhyCHs) in the cell.

pichPower pich-PowerOffset : x Power level of the Page Indication CHannel
(PICH) relative to the Primary Common Pilot
Channel (CPICH) power
aichPower Aich-PowerOffset : x Power level of the Acquisition Indication
CHannel (AICH) relative to the Primary
Common Pilot Channel (CPICH) power
primaryCpichPower primaryCPICH-TX-Power : x Power level of the Primary CPICH
ConstantValueCprach constantValue : x Used by the UE to calculate initial power on the
PRACH.

powerOffsetP0 powerRampStep : x Preamble power step when no Acquisition

Indicator is received.
preambleRetransMax preambleRetransMax : x Maximum number of Preambles sent in one
ramping cycle
uplink interference value. Due to the fact that this value changes very often, this
System Information Block’s interval is controlled by a timer. When the UE receives
System Information Block 7 (SIB 7), a timer is started. Once the timer expires, the
information is considered invalid and the UE reads the information again. The
expiration time is the value of the sib7RepPeriod parameter multiplied by the
sib7expirationTimeFactor parameter.

n/a ul-Interference Provides uplink Received Total Wideband
Power (RTWP). RTWP = No
– System Information Block 11 (SIB 11). System Information Block 11 (SIB 11)
contains the cell’s soft/softer handover neighbor list including the Primary Scrambling
Code of each neighbor. This handover list is supplied to the UE before a call is
established so that the UE may make Intra-frequency measurements before
receiving the MEASUREMENT CONTROL message from the Serving Radio Network
Controller (SRNC).

reportingRange1a e1a – reportingRange : x CPICH reporting range add threshold.
hysteresis1a e1a – hysteresis : x Hysteresis used for CPICH add threshold.
timeToTrigger1a e1a – timeToTrigger : x Time between CPICH add and reporting.
reportingRange1b e1b – reportingRange : x CPICH reporting range drop threshold.
hysteresis1b e1b – hysteresis : x Hysteresis used for CPICH drop threshold.
timeToTrigger1b e1b – timeToTrigger : x Time between CPICH drop and reporting.
hysteresis1c e1c – hysteresis : 2 Hysteresis used for CPICH replacement.
timeToTrigger1c e1c – timeToTrigger : x Time between CPICH replacement and
reporting.
hysteresis1d e1d – hysteresis : x Hysteresis used in best CPICH replacement.
timeToTrigger1d e1d – timeToTrigger : x Time between best CPICH replacement and
reporting.
– System Information Block 12 (SIB 12). System Information Block 12 (SIB 12)
contains measurement control information to be used in the cell.

n/a n/a There are no configurable parameters
reported in this SIB

The UE reads System Information only when one of the following events occurs:
• The UE is powered up.
• Immediately after Cell Reselection (except SIB 1 where the parameter

sib1PLMNScopeValueTag is used).
• The UE receives a Paging Type 1 message indicating System Information has

changed. Then the MIB is read which indicates the SIBs that have been updated.
• The timer expires for SIBs with an expiration timer (SIB 7 only).
Otherwise, in order to conserve battery life, the UE does not read the System
Information. This is something to consider when observing Layer 3 messages using a
diagnostic UE.
5.1.2.2 Camping on a Suitable Cell
Now that the UE has read the Broadcast Control CHannel (BCCH), it knows the values of
the parameters that help the UE determine if the cell is suitable in terms of signal level
(Srxlev) and quality (Squal). These parameters are commonly referred to as the S
parameters.
Srxlev = Qrxlevmeas – qRxLevMin – Pcompensation
Where:
• Srxlev is the signal level criteria used to determine a cell’s suitability.
• Qrxlevmeas is the Primary Common Pilot Channel Received Signal Code Power
(PCPICH RSCP) as measured by the UE.
• qRxLevMin is a configurable parameter sent in System Information Block 3 (SIB 3)

for the serving cell which indicates the minimum acceptable Primary Common Pilot
Channel Received Signal Code Power (PCPICH RSCP).
• The quantity called Pcompensation is the maximum value of maxTxPowerUl – P or

0 where maxTxPowerUl is a configurable parameter sent in System Information
Block 3 (SIB 3) which indicates the maximum transmission power allowed for a UE
and P is the output power of the UE according to its Power Class.
Example part 1 of 3. A Power Class 3 UE is served at a path loss 10 dB less than the
maximum path loss as indicated in the Link Budget table, qRxLevMin is set
conservatively at -115 dBm, and maxTxPowerUl is set at 24 dBm. Pcompensation is
the maximum value of either 24 dBm – 24 dBm or 0. So Srxlev = -105 dBm minus -115
dBm minus 0. Srxlev = 10.
Squal = Qqualmeas – qQualMin

Where:
• Qqualmeas is the Primary Common Pilot Channel Chip Energy over Noise Spectral
Density (PCPICH Ec/No) as measured by the UE.
• qQualMin is a configurable parameter sent in System Information Block 3 (SIB 3) for

the serving cell which indicates the minimum acceptable Primary Common Pilot
Channel Chip Energy over Noise Spectral Density (PCPICH Ec/No) for the cell.
Example part 2 of 3. The UE is served at an Ec/No of -14 dB and qQualMin is set

conservatively at -18 dB. -14 db minus -18 dB. Squal = 4 dB.
The cell is considered suitable if its cell selection criterion (S criterion) is met. In order for
the S criterion to be met, both Srxlev and Squal must be positive values.
Example part 3 of 3. The UE calculates both S criteria with positive resulting values.
The cell is considered acceptable where the S criterion is concerned. It is now allowed
to transmit on the uplink.
5.1.3 IMSI and GPRS Attach
Assuming now that the UE has found its home PLMN and is Camping on a suitable cell, it
must International Mobile Subscriber Identity (IMSI) Attach and General Packet Radio
Service (GPRS) Attach to the Circuit Switched (CS) and Packet Switched (PS) Core
Networks (CN) respectively. This process is also known as Registration.
5.1.3.1 Attach Procedure
If the configurable parameter att sent in System Information Block 1 (SIB 1) is set to 1,
the UE must establish a Signaling Connection to notify the Circuit Switched Core Network
(CS-CN) and Packet Switched Core Network (PS-CN) that it is powered on and within
network coverage. Signaling Connections are always initiated by the UE. First, the UE
must access the Node B in order to send a request to the RNC to establish a Radio
Resource Control (RRC) Connection. This is done through the Physical Random Access
Channel (PRACH) on the uplink and the Acquisition Indicator Channel (AICH) on the
downlink. The UE sends successive attempts on the uplink, each at a greater power
level until the Node B responds on the Acquisition Indicator CHannel (AICH) on the
downlink. The process of sending successive attempts, each at an increased power
level, is known as Preamble Ramping.
The initial power on the PRACH is determined by the UE using the following formula:
P_PRACH = L_PCPICH + RTWP + constantValueCprach
Where:
• P_PRACH is the power used for the initial PRACH attempt.

• L_PCPICH is the path loss estimated by the UE (difference between

primaryCpichPower as indicated in SIB 5 and PCPICH RSCP measured by the
UE).
• RTWP is the Received Total Wideband Power measured by the Node B as indicated
in SIB 7.
• constantValueCprach is a configurable parameter that determines the level in dB

below the Received Total Wideband Power at which Preamble Ramping begins.
For example, a UE is served at a path loss 10 dB less than the maximum path loss as
indicated in the Link Budget table, so L_PCPICH = 132 dB. Let’s also say the RTWP =
-105 dBm and constantValueCprach = -27 dB. The sum of these values, or
P_PRACH, is 0 dBm. The UE will begin the attempt at 0 dBm.
Subsequent transmission attempts within a Ramping Cycle are made at an increased

power level relative to the former attempt. The increase in power level between steps is
controlled by the parameter powerOffsetP0 which the UE reads from System
Information Block (SIB) 5.
The UE ceases its access attempt as soon as it receives an Acknowledgement Indicator

(AI) on the downlink Acquisition Indication CHannel (AICH). However, the UE is not
allowed to ramp its power indefinitely. The preambleRetransMax parameter in SIB 5
controls how many successive Preambles the UE can transmit within one Ramping Cycle
and the maxPreambleCycle parameter controls how many Ramping Cycles can be
attempted before the UE aborts the access attempt.
As soon as the UTRAN responds with an Acknowledgement Indicator (AI) on the

downlink, the UE sends the PRACH Message Part informing the Radio Network
Controller (RNC) that it wishes to set up a Radio Resource Control (RRC) Connection.
The power at which PRACH Message Part is sent is equal to the sum of the power of the
successful transmission attempt and the configurable parameter powerOffsetPpm.
Figure 2 Power Ramping on RACH
powerOffsetP0 AI powerOffsetPpm
P_PRACH
Power
(dB)
Message Part
RACH
preambleRetransMax
(Ramping Cycle)
AICH
Time

Once the UE and Radio Network Controller (RNC) have established a Radio Resource
Control (RRC) Connection, the RNC establishes an Iu Control Plane connection over the
Iu interface to the appropriate Core Network (CN) element(s), i.e. the SGSN, MSC or
both. The resulting Transparent Message Transfer connection between the UE and Core
Network (CN) element(s) allows the exchange of Non-Access Stratum (NAS) messages
such as Registrations, Location or Routing Area Updates, and Service Requests for User
Plane connections. The figure below details all of the steps necessary to complete a
Radio Resource Control (RRC) Connection. Following the figure are detailed
explanations for each step.
Figure 3 RRC Connection Signaling Flow
UE Uu Node B Iub RNC
RRC Connection Request

1 RRC RACH Message Part RRC
2 Initiate UE Context
Activated Algorithms:
- Power Control
3 - Iub and Uu Timing Scheduling
- Admission Control
Radio Link Setup Request
4 NBAP NBAP
5 Resource Allocation
Radio Link Setup Response
6 NBAP NBAP
7 AAL2 Connection Setup for DCH
Start Receive of UL DPCH

8
Start Radio Link Supervision
Suspend SRB3, SRB4 and
9
other RLC AM entities
RRC Connection Setup
10 RRC FACH RRC
11 Transport Bearer Synchronization
Start Transmission of
12
DL DPCH
13 L1 Synchronization
Radio Link Restore Indication
14 NBAP NBAP
RRC Connection Complete
15 RRC DCH RRC
Resume SRB3, SRB4 and

16
other RLC AM entities

1. RRC Connection Request. After the UE receives the Acknowledgement Indicator

(AI) on the downlink, it initiates the establishment of a Radio Resource Control (RRC)
connection by sending the Radio Resource Control (RRC) Connection Request
message with an establishment cause of “Registration” within the Message Part
using the Random Access Channel (RACH) Transport Channel.
2. Initiate UE Context. The Radio Resource Control (RRC) Connection attempt is
assigned a UTRAN Radio Network Temporary Identity (U-RNTI) which is unique
within the network.
3. Activated Algorithms. At this point, the Power Control algorithm sets the initial
downlink and uplink Dedicated Physical Data CHannel (DPDCH) and Dedicated
Physical Control CHannel (DPCCH) transmission power. These channels are time
multiplexed on the downlink and code (I/Q) multiplexed on the uplink. Together they
are typically referred to as a Dedicated Physical CHannel (DPCH).
– The initial downlink Dedicated Physical Data CHannel (DPDCH) power is determined
using the following formula:
P_DL_DPDCH = primaryCpichPower + (dlInitSirTarget - Ec/No_PCPICH) +
cBackOff + 10 log(2/SF_DL_DPDCH)
Where:
• P_DL_DPDCH is the initial downlink Dedicated Physical Data CHannel (DPDCH)

power.
• primaryCpichPower is a configurable parameter that sets the power of the

Primary Common Pilot Channel (P-CPICH).
• dlInitSirTarget is a configurable parameter that sets the required initial Signal to

Interference Ratio (SIR) Target.
• Ec/No_PCPICH is the ratio of Chip Energy to the Noise Power Spectral Density
of the Primary Common Pilot CHannel (P-CPICH) as measured by the UE. If this
measurement is not available, the configurable parameter ecNoPcpichDefault is
used.
• cBackOff is a configurable parameter used to offset the value of P_DL_DPDCH.
• SF_DL_DPDCH is the Spreading Factor of the downlink Dedicated Physical Data

CHannel (DPDCH).
– The initial downlink Dedicated Physical Control CHannel (DPCCH) power is set
relative to the initial downlink Dedicated Physical Data Channel (DPDCH) power by
means of a series of offsets:
P_DL_DPCCH_TFCI = (P_DL_DPDCH + pO1)
P_DL_DPCCH_TPC = (P_DL_DPDCH + pO2)
P_DL_DPCCH_PILOT = (P_DL_DPDCH + pO3)

Figure 4 Downlink DPCCH Power
DL Power
(dB)
P02 P01
TPC P03
TFCI
Pilot
Data 1 Data 2
Time
DPDCH DPCCH DPDCH DPCCH

1 Timeslot (10ms)
Where:
• P_DL_DPCCH_TFCI is the initial power of the Dedicated Physical Control

CHannel Transport Format Combination Indicator (DPCCH TFCI) field.
• p01 is a configurable parameter that sets the offset in dB between the Data field
and the Dedicated Physical Control CHannel Transport Format Combination
Indicator (DPCCH TFCI) field.
• P_DL_DPCCH_TPC is the initial power of the Dedicated Physical Control

CHannel Transmit Power Control (DPCCH TPC) field.
and the Dedicated Physical Control CHannel Transmit Power Control (DPCCH
TPC) field.
• P_DL_DPCCH_PILOT is the initial power of the Dedicated Physical Control

CHannel Pilot field.
and the Dedicated Physical Control CHannel Pilot field.
– The initial uplink Dedicated Physical Control CHannel (DPCCH) power is determined
using the following formula:
Power_UL_DPCCH_INIT = DPCCH_POWER_OFFSET - RSCP_PCPICH
Where:
• Power_UL_DPCCH_INIT is the initial uplink Dedicated Physical Control CHannel

(DPCCH) power.
• DPCCH_POWER_OFFSET is calculated in the Radio Network Controller (RNC)

and sent to the UE according to the following formula:
DPCCH_POWER_OFFSET = primaryCpichPower + RTWP + ulInitSirTarget -
10 log (SF_DPCCH) + cPO

Where:
• DPCCH_POWER_OFFSET is an offset applied to Power_UL_DPCCH_INIT.
• primaryCpichPower is the configurable parameter that sets the power of the

Primary Common Pilot CHannel (P-CPICH).
• RTWP is the Received Total Wideband Power level on the uplink measured
by the Node B.
• ulInitSirTarget is one of the following configurable parameters based upon

the Spreading Factor of the Radio Bearer.
• ulInitSirTargetSrb for stand-alone Signaling Radio Bearers (SRB).
• ulInitSirTargetLow for Radio Access Bearers (RABs) having minimum

Dedicated Physical Data CHannel Spreading Factors (DPDCH SF) equal
to or higher than 32.
• ulInitSirTargetHigh for RABs having minimum Dedicated Physical Data

CHannel Spreading Factors (DPDCH SF) equal to 16 or 8.
• ulInitSirTargetExtraHigh for Radio Access Bearers (RABs) having

minimum Dedicated Physical Data CHannel Spreading Factors (DPDCH
SF) equal to or lower than 4.
• SF_DPCCH is the Spreading Factor (SF) for the Dedicated Physical Control
CHannel.
• cPO is a configurable parameter used to offset the initial uplink Dedicated

Physical Data CHannel (DPDCH) power.
• RSCP_PCPICH is the Received Signal Code Power (RSCP) or the Primary

Common Pilot Channel (P-CPICH).
– The initial uplink Dedicated Physical Data CHannel (DPDCH) power is determined
according to the relative power offset between the Dedicated Physical Control
CHannel (DPCCH) and Dedicated Physical Data Channel (DPDCH) as described in
3GPP TS 25.214. The UTRAN determines and signals the gain factor to the UE for
the reference Transport Format Combination (TFC) only. The UE, then computes the
gain factors for other Transport Format Combinations (TFCs), based on the value for
the reference Transport Format Combination (TFC).
In addition to uplink and downlink power control, the Iub and Uu Timing Scheduling
algorithms calculate channel timing parameters. The Admission Control algorithm
checks if the new radio link can be allowed in the cell. The Code Control algorithms
allocate the uplink scrambling code, downlink scrambling code, and downlink
channelization code.
4. Radio Link Setup Request. The RNC orders the Node B to reserve the necessary
resources for a new Node B communication context.
5. Resource Allocation. The Node B reserves the necessary resources for a new
communication context and calculates link characteristic parameters from the
received uplink and downlink Transport Format Combination Indicator (TFCI) or
Transport Format Set (TFS) information.

6. Radio Link Setup Response. The Node B indicates to the RNC that the necessary
resources are allocated for the radio link. It includes the binding identifier and
transport layer address for the AAL2 connection.
7. AAL2 Connection Setup for DCH. The transport bearer (AAL2 connection) needed
for signaling is set up over the Iub by the RNC.
8. Start Receive of UL DPCH – Start Radio Synchronization. The Radio Link Set
Supervision algorithm in the Node B starts evaluating the synchronization status of
the Radio Link Set (RLS).
9. Suspend SRB3, SRB4, and other RLC AM entities. Signaling Radio Bearer 3
(SRB 3), Signaling Radio Bearer 4 (SRB 4), and other Radio Link Control
Acknowledged Mode (RLC AM) entities are suspended.
10. RRC Connection Setup. The RNC indicates the UE state shall be CELL_DCH. The
message is sent in Unacknowledged mode on the Forward Access CHannel (FACH).
11. Transport Bearer Synchronization. Transport Bearer Synchronization is achieved
in the downlink between RNC and Node B for each Dedicated CHannel (DCH).
12. Start Transmission of DL DPCH. The Node B only starts transmitting on the new
radio link when the downlink user plane (Dedicated Physical Data CHannel –
DPDCH) is considered synchronized.
13. L1 Synchronization. Layer 1 synchronization is achieved between UE and Node B.
14. Radio Link Restore Indication. The Node B notifies the RNC that it has achieved
uplink Layer 1 synchronization with the UE.
15. RRC Connection Complete. The UE starts the uplink transmission only after the
reception of downlink Dedicated Physical Channel (DPCH). The UE capabilities
requested in step 10 are included in this message. This information is used by the
Radio Access Bearer (RAB) establishment procedure, UE Security Handling, and the
Channel Switching function. Radio Resource Control (RRC) messages can now be
sent in acknowledged mode on a Dedicated CHannel (DCH).
16. Resume SRB3, SRB4, and other RLC AM entities. The SRB3, SRB4, and other
Radio Link Control Acknowledged Mode (RLC AM) entities are resumed.
Through this dedicated connection, the UE is able to Register with the appropriate Core
Network (CN) Element(s).
5.1.4 Location and Routing Area Updates
Location and Routing Area Updates, also known as Registration updates, must be
performed in order to provide the SGSN and MSC with an awareness of where the UE is
located. Given the UE’s location, the Core Network (CN) element can page the UE to
deliver calls. Registration also avoids unnecessary paging when the UE is either turned
off or is outside of the coverage area. Location Areas are defined through the
configurable parameter lAC broadcast on the Broadcast Control CHannel (BCCH) in
System Information Block 1 (SIB 1). Routing Areas are defined through the configurable
parameter rAC also broadcast on the Broadcast Control CHannel (BCCH) in System
Information Block 1 (SIB 1). Besides IMSI and GPRS Attaches, there are basically two
different types of Registration update; Normal and Periodic.

5.1.4.1 Normal Update
A Normal Location or Routing Area update is performed when the UE either leaves
Connected Mode, or performs a Cell Reselection in Idle Mode to a cell within a different
Location or Routing Area.
5.1.4.2 Periodic Update
In addition to Normal Updates, Periodic Updates are performed. These updates are
preformed regardless of whether the UE is in Idle Mode or Connected Mode
(CELL_DCH).
– Circuit Switched Core Network. The interval at which the UE periodically updates
the Circuit Switched Core Network (CS-CN) is set using the configurable t3212
parameter sent on the Broadcast Control CHannel (BCCH) in System Information
Block 1 (SIB 1).
– Packet Switched Core Network. The interval at which the UE periodically updates
the Packet Switched Core Network (PS-CN) is set using the t3312 timer. This timer
is set in the SGSN and sent to the UE via both the Attach and the Routing Area
Update messages.
The following table provides parameter ranges and default values involved in getting the
UE into Idle Mode. They are listed in the same order they were presented. The Level
column indicates the network element that owns the parameter. The class column
indicates if the parameter is set based on Policy (must be set this way), Fixed
(recommended to be set this way) and Variable (set at your discretion).
Table 13 Idle Mode Configurable Parameters
Parameter Range Ericsson Cingular Level Class Unit

Default Default
primaryScramblingCode 0-512 N/A 3.3.3 Cell Variable Integer
primaryCpichPower -100 to +500 300 300 Cell Fixed 0.1 dBm
primarySchPower -350 to +150 -18 -18 Cell Fixed 0.1 dB
secondarySchPower -350 to +150 -35 -35 Cell Fixed 0.1 dB
mcc 0 to 999 N/A 310 RNC Policy Integer
mnc 0 to 999 N/A 410 RNC Policy Integer
sib1StartPos 0 to 4094 2 2 RNC Fixed SFN
sib1RepPeriod 4, 8, 16 to 4096 32 32 RNC Fixed SFN
lAC 1 to 65533, 65535 N/A N/A LA Variable Integer


Default Default
t3212 0 to 255 10 10 LA Fixed 6 min
att 1 or 0 1 1 LA Fixed Integer
cnDrxCycleLengthCs See Call Est.
rAC 0 to 255 N/A N/A RNC Variable Integer
nmo Mode 1 or 2 2 2 RA Fixed Integer
cnDrxCycleLengthPs See Call Est.
qualMeasQuantity Ec/No or RSCP Ec/No Ec/No RNC Fixed String
sRatSearch See Mobility Mtg.
sHcsRat -105 to +91 -105 -105 Cell Fixed 2 dB
qQualMin -24 to 0 -18 -19 Cell Fixed 1 dB
qRxLevMin -115 to -25 -115 -115 Cell Fixed dBm
qHyst2 See Mobility Mtg.
treSelection See Mobility Mtg.
maxTxPowerUl -50 to +33 24 24 Cell Fixed dBm
cellReserved Reserved or Not Not Not Cell Variable String
pichPower -10 to +5 -7 -7 Cell Fixed dB
aichPower -22 to +5 -6 -6 Cell Fixed dB
ConstantValueCprach -35 to -10 -27 -27 Cell Fixed dB
powerOffsetP0 1 to 8 3 2 Cell Fixed dB
preambleRetransMax 1 to 64 8 15 Cell Fixed Preambles
reportingRange1a See Mobility Mtg.
hysteresis1a See Mobility Mtg.
timeToTrigger1a See Mobility Mtg.
reportingRange1b See Mobility Mtg.
hysteresis1b See Mobility Mtg.
timeToTrigger1b See Mobility Mtg.
hysteresis1c See Mobility Mtg.
timeToTrigger1c See Mobility Mtg.
hysteresis1d See Mobility Mtg.
timeToTrigger1d See Mobility Mtg.
sib1PLMNScopeValueTag 0 to 31 N/A N/A Cell Variable Integer
maxPreambleCycle 1 to 32 4 3 Cell Fixed Cycles
powerOffsetPpm -5 to +10 -4 0 Cell Fixed dB
dlInitSirTarget -82 to 173 41 41 RNC Fixed 0.1 dB
cBackOff -60 to +60 0 0 RNC Fixed 0.25 dB
ecNoPcpichDefault -20 to -10 -16 -16 RNC Fixed 1 dB
pO1 0 to 24 0 0 RNC Fixed 0.25 dB
ulInitSirTargetSrb -82 to 173 57 57 RNC Fixed 0.1 dB
ulInitSirTargetLow -82 to 173 49 49 RNC Fixed 0.1 dB
ulInitSirTargetHigh -82 to 173 82 82 RNC Fixed 0.1 dB
ulInitSirTargetExtraHigh -82 to 173 92 92 RNC Fixed 0.1 dB
cPO -30 to 30 0 0 RNC Fixed 0.1 dB

5.2 Call Establishment
Given the UE has successfully entered Idle Mode; it must then be able to originate and
terminate calls within acceptable Accessibility measures. This section considers all of the
algorithms invoked during the process of establishing a call.
5.2.1 Radio Access Bearer
A Radio Access Bearer (RAB) is a connection between the UE and the Mobile Switching
Center (MSC) in the case of a Circuit Switched (CS) connection or between the UE and
Serving GPRS Support Node (SGSN) in the case of a Packet Switched connection.
There is also the possibility of the UE connecting to both the MSC and the SGSN as is
the case in both SP0 and SP64. The Radio Access Bearer is set up according to the
Requested Service after the Signaling Connection is established through a Signaling
Radio Bearer. In the case of UE initiated connections where a Radio Access Bearer
does not already exist, the Requested Service is sent in the Random Access CHannel
(RACH) Message Part. Although the Requested Service could be sent by the UE, all
Radio Access Bearers are actually initiated by the Core Network (CN).
The variables within Quality of Service (QoS) fall into three main categories based upon
the user’s need for guaranteed throughput and/or latency. The three categories are
Conversational; which provides guaranteed low latency and throughput, Streaming;
which provides guaranteed throughput but no guarantee for latency, and Interactive (also
referred to as Background) which provides guarantees for neither throughput nor latency.
Another variable determines which side of the Core Network is used. In general, all
Packet Switched Radio Access Bearers are connected to the SGSN and all Circuit
Switched Radio Access Bearers are connected to the MSC.
The following types of Radio Access Bearers (RABs) are supported by the Ericsson
UTRAN.
– Conversational Circuit Switched Speech AMR 12.2kb. This is the typical Speech
Radio Access Bearer. Given its Conversational Quality of Service (QoS) class, low
latency and constant throughput are guaranteed. The Conversational class of
service is Transparent, meaning that in order to keep latency as low as possible,
there is no Transport layer Block retransmission service offered.
– Conversational Circuit Switched Speech AMR 12.2kb plus Interactive Packet

Switched 64kb/64kb. This type of Radio Access Bearer supports concurrent Circuit
Switched Speech and Packet Switched Data. The Interactive Quality of Service
(QoS) class Data connection can support a data rate of 64kb in the Uplink and 64kb
in the downlink. Neither latency nor throughput is guaranteed for the Packet
Switched connection. Ericsson refers to this type of Radio Access Bearer (RAB) as
SP64.
– Conversational Circuit Switched Speech AMR 12.2kb plus Interactive Packet

Switched 0kb/0kb. This Radio Access Bearer (RAB) offers both Speech and a 0 bit
rate Packet Switched connection. The 0 bit rate Packet Switched connection is used
as a “stepping stone” between 64/64 and Idle Mode. The result is a reduction in
latency from the end user’s perspective when using interactive applications such as

Web Browsing. Ericsson refers to this type of Radio Access Bearer (RAB) as SP0.
The availability of this Radio Access Bearer (RAB) is controlled through the
configurable parameter multiRabSp0Available.
– Conversational Circuit Switched Data 64kb. This Radio Access Bearer (RAB)
provides a Conversational class 64kb/s Unrestricted Digital Information (UDI)
connection between the UE and the Circuit Switched Core Network. The
Conversational class of service is Transparent, meaning that in order to keep latency
as low as possible, there is no Transport layer Block retransmission service offered.
– Conversational Circuit Switched Data 64kb plus Interactive Packet Switched

8/8. This Radio Access Bearer (RAB) provides a Conversational class 64kb/s
Unrestricted Digital Information (UDI) connection between the UE and the Circuit
Switched Core Network plus an Interactive class 8kb uplink, 8kb downlink Packet
Switched connection between the UE and Packet Switched Core Network. Ericsson
refers to this type of Radio Access Bearer (RAB) as UDI8. The availability of this
Radio Access Bearer (RAB) is controlled through the configurable parameter
multiRabUdi8Available.
– Streaming Circuit Switched 57.6kb. This Radio Access Bearer (RAB) provides a
Streaming class connection between the UE and Circuit Switched Core Network with
guaranteed throughput of up to 57.6kb and guaranteed low latency.
– Streaming Packet Switched 16kb/64kb. This Radio Access Bearer (RAB) provides
a Streaming class connection between the UE and the Packet Switched Core
Network with guaranteed throughput of up to 57.6kb on the downlink and 16kb in the
uplink. Latency is not guaranteed.
– Streaming Packet Switched 16kb/64kb plus Interactive Packet Switched 8/8.

This Radio Access Bearer (RAB) provides a Streaming class connection between the
UE and the Packet Switched Core Network with guaranteed throughput of up to
57.6kb on the downlink and 16kb in the uplink plus an interactive class 8kb uplink,
8kb downlink Packet Switched connection between the UE and Packet Switched
Core Network. Throughput is only guaranteed for the Streaming class connection.
Latency is not guaranteed for either connection.
– Streaming Packet Switched 16kb/128kb. This Radio Access Bearer (RAB)

provides a Streaming class connection between the UE and the Packet Switched
Core Network with guaranteed throughput of up to 112kb on the downlink and 16kb
in the uplink. Latency is not guaranteed.
– Streaming Packet Switched 16kb/128kb plus Interactive Packet Switched 8/8.

This Radio Access Bearer (RAB) provides a Streaming class connection between the
UE and the Packet Switched Core Network with a guaranteed throughput of up to
112kb on the downlink and 16kb in the uplink plus an interactive class 8kb uplink,
8kb downlink Packet Switched connection between the UE and Packet Switched
Core Network. Throughput is only guaranteed for the Streaming class connection.
Latency is not guaranteed for either connection. The availability of this Radio Access
Bearer (RAB) is controlled through the configurable parameter psStreaming128.
– Interactive Packet Switched HSDPA with 384kb uplink. This Radio Access
Bearer provides an interactive connection between the UE and Packet Switched
Core Network of 1.8Mb (UE limitation) on the downlink and 384kb on the uplink.
Neither latency nor throughput is guaranteed. The availability of this Radio Access
Bearer (RAB) is controlled through the configurable parameter allow384HsRab.

– Interactive Packet Switched HSDPA with 64kb uplink. This Radio Access Bearer
provides an interactive connection between the UE and Packet Switched Core
Network of 1.8Mb (UE limitation) on the downlink and 64kb on the uplink. Neither
latency nor throughput is guaranteed.
– Interactive Packet Switched 64kb/64kb. This Radio Access Bearer (RAB) provides
an interactive connection between the UE and Packet Switched Core Network of
64kb on the uplink and 64kb on the downlink. Neither latency nor throughput is
guaranteed. This is the initial Dedicated Channel (DCH) selected for all non-HSDPA
capable mobiles requesting a Packet Switched Interactive connection.
– Interactive Packet Switched 64kb/128kb. This Radio Access Bearer (RAB)

Network of 64kb on the uplink and 128kb on the downlink. Neither latency nor
throughput is guaranteed. A UE can be up-switched to this Radio Access Bearer
from 64kb/64kb or down-switched to this Radio Access Bearer (RAB) from
64kb/384kb.
– Interactive Packet Switched 64kb/384kb. This Radio Access Bearer (RAB)

Network of 64kb on the uplink and 384kb on the downlink. Neither latency nor
throughput is guaranteed. A UE can be up-switched to this Radio Access Bearer
from 64kb/128kb.
Ericsson supports many types of Radio Access Bearers (RABs) as shown above,
however, our end to end network does not currently support Differentiated Service
through the use of QoS profiles.
Our current implementation supports only the following Radio Access Bearer (RAB)
configurations.
• Conversational Circuit Switched AMR 12.2kb for Speech.
• Conversational Circuit Switched Speech AMR 12.2kb for Speech plus Interactive
Packet Switched 64/64 (SP64/SP0). This is also referred to as multi-RAB.
• Interactive Packet Switched 64kb/64kb for non-HSDPA capable UEs. Up-switching

allows for 64kb/128kb and 64kb/384kb. Down-switching allows the use of common
channels (RACH and FACH) for User Plane data.
• Interactive Packet Switched 384kb or 64kb uplink with HSDPA downlink for UEs with
HSDPA capability.
5.2.2 Mobile Origination / Termination
The establishment of a Radio Access Bearer (RAB) in the case of a Mobile Origination or
Termination begins with either a RACH on the uplink, or a Page on the downlink. The
establishment of an RRC Connection is identical to the process used in Figure 4 within
the Idle Mode section except that the resulting Transparent Message Transfer connection
between the UE and Core Network (CN) element(s) specifies a Service Request for a
User Plane connection. Based upon the type of Service requested, the Core Network
Sends a RAB ASSIGNMENT REQUEST to the Serving Radio Network Controller
(SRNC) indicating the RAB ID.

The Serving Radio Network Controller (SRNC) determines the new Radio Connection
based upon the type of Service Requested by the Core Network taking into consideration
any existing Radio Connections between it and the UE. There are also functions as
described in the following subsections that determine the treatment of the Service
Request. Each is considered independent of the others. The parameters that guide the
operation of each function are described within context.
5.2.2.1 Paging
There are two primary uses for paging. One is to inform UEs of an incoming call, the
other is to inform UEs of new System Information broadcast on the Broadcast Control
CHannel (BCCH). Pages for calls can be sent from either the Packet Switched or the
Circuit Switched core network. A UE may be paged while it is in Idle Mode, Cell_FACH
state or in Cell_DCH state.
In Idle Mode, the Secondary Common Control Physical CHannel (S-CCPCH) and the
Paging Indicator CHannel (PICH), also a Physical Channel, are used.
– The Secondary Common Control Physical CHannel (S-CCPCH) carries the Paging
CHannel (PCH) logical channel. The Paging CHannel (PCH) is used to carry the
Radio Resource Control (RRC) Message “Paging type 1” which carries the actual
paging message from the Core Network.
– In order to conserve UE battery life, the UE does not always read the Paging
CHannel (PCH). The Paging Indicator CHannel (PICH) is used to indicate when the
UE should read the Paging CHannel (PCH). Each Paging Indicator CHannel (PICH)
frame consists of a number of Paging Indicators. The UEs are divided into a number
of groups, and each group reads a specific Paging Indicator that tells if it should read
the Paging CHannel (PCH). The interval at which the UE reads the Paging CHannel
(PCH) is determined by its own International Mobile Subscriber Identity (IMSI) and
the Discontinuous Reception (DRX) Cycle Length.
The Discontinuous Reception (DRX) Cycle Length = 2k * 10ms
Where:
• k = the configurable parameter cnDrxCycleLengthCs for Circuit Switched

services and cnDrxCycleLengthPs for Packet Switched services.
• 10ms is equal to the duration of a System Frame
In Cell_FACH state or in Cell_DCH state a connection exists between the UTRAN and
the UE. The RRC message "Paging type 2" is used to carry paging information over the
dedicated connection.
The configurable parameter noOfPagingRecordTransm controls the number of times a

single page from the Core Network will be sent by the UTRAN.
UEs in Idle Mode are informed of new System Information broadcast on the Broadcast
Control CHannel (BCCH) through consecutive “Paging type 1” messages. The number
of times a UE (that uses maximum possible DRX cycle length) hears the updated system
information is defined by the parameter noOfMaxDrxCycles.

5.2.2.2 Emergency Call Redirect to 2G for Speech
If the configurable parameter emergencyCallRedirect is set to ON, an emergency (911)

call made by a UE on the UMTS network will be redirected to GSM. The call will be
established on the GSM network after Cell Selection on the GSM network has taken
place.
This procedure is applied when there is no existing Radio Connection. If there is an

existing Packet Switched connection between the UE and Packet Switched Core
Network, the 911 call will be placed through the 3G network. In this case, only the Cell ID
of the serving cell will be used for location purposes.
The current recommendation is to enable this capability by setting

emergencyCallRedirect to ON due to the fact that the E911 solution for WCDMA does
not provide the level of location detection accuracy provided by the GSM solution.
5.2.2.3 Admission Control
Admission Control is a function that determines if a new radio link can be allowed on the
cell given the cell’s current resource load. New radio links can be requested for Call
Origination, Termination, Handover or when existing radio links are modified.
Transport resources (Iub) are not considered during Admission Control procedures and
as such do not have any affect on Admission Control.
When a request is made of Admission Control, Service Classes (Guaranteed,

Guaranteed-HS and Non-Guaranteed) and Setup Types (Handover and Non-Handover)
are used to allow for prioritization among requests for different types of radio links.
The following radio connection types (supported by Cingular) correspond to the

Guaranteed Service Class:
• Stand alone Signaling Radio Bearers (SRB)
• Conversational Circuit Switched Speech AMR 12.2kb
• Conversational Circuit Switched Speech AMR 12.2kb plus Interactive Packet

Switched 0kb/0kb (SP0).
The following radio connection types (supported by Cingular) correspond to the

Guaranteed-HS Service Class:
• Interactive Packet Switched HSDPA with 384kb uplink
• Interactive Packet Switched HSDPA with 64kb uplink

The following radio connection types (supported by Cingular) correspond to the Non-
Guaranteed Service Class:
• Interactive Packet Switched 64kb/64kb
• Conversational Circuit Switched Speech AMR 12.2kb plus Interactive Packet

Switched 64kb/64kb (SP64)
The request also specifies the estimates of the following:
• Number of downlink Channelization Codes
• Usage of uplink and downlink Spreading Factors
• Amount of downlink Non-HS Power
• Number of uplink and downlink Air Speech Equivalents (ASE)
• Amount of Node B Hardware utilized.
– Downlink Channelization Codes. In order to reserve Channelization Codes for

Handover, admission is blocked for all Guaranteed / Non-Handover and Guaranteed-
HS / Non-Handover requests when Channelizaton Code utilization exceeds a
percentage of the total Channelization Codes in the cell through the use of the
configurable parameter dlCodeAdm. Furthermore, Non-Guaranteed / Non-
Handover admission requests are blocked when the Channelization Code utilization
exceeds dlCodeAdm – beMarginDlCode.
The current recommendation is to set dlCodeAdm=80 or 80% to allow for 5 dedicated

SF 16 HSDPA Channelization Codes on each cell. beMarginDlCode=2 or 10% is
recommended to allow blocking to occur at 70% for Non-Guaranteed / Non-Handover
admission requests.
– Uplink and Downlink Spreading Factor usage. The Histogram Monitor keeps
track of Spreading Factor usage in the uplink and downlink. It also measures the
number of Compressed Mode radio links and the number of HS serving radio links in
the cell in order to allow or deny requests for either Handover or Non-Handover
based upon Spreading Factor utilization.
• Non-Guaranteed admission requests of Spreading Factor 8 in the downlink are

denied when the use of Spreading Factor 8 exceeds the configurable parameter
sf8Adm. The 384kb Radio Access Bearer uses Spreading Factor 8 on the
downlink.

downlink.


downlink.
• Guaranteed admission requests of Spreading Factor 16 in the downlink are

denied when the use of Spreading Factor 16 (Streaming 16kb/128kb) exceeds
the configurable parameter sf16gAdm. The However, Cingular does not
currently support any Guaranteed Radio Access Bearers that use Spreading
Factor 16.
• Guaranteed HS admission requests of Spreading Factor 4 in the uplink

(384kb/HSDPA) are denied when the use of Spreading Factor 4 in the uplink
exceeds the configurable parameter sf4AdmUl.
• Admission Control blocks admission requests for a radio link in compressed

mode when the current number of radio links exceeds the configurable
parameter compModeAdm.
• Admission Control blocks new radio link admission requests for HSDPA when
the number of users assigned to the High Speed Downlink Shared CHannel (HS-
DSCH) in the cell exceeds the configurable parameter hsdpaUsersAdm. This
configurable parameter does not apply to requests made as a result of Cell
Change (mobility).
– Downlink Non-HS Power. Transmitted Code Power utilization is monitored and

admission is blocked for all Guaranteed / Non-Handover and Non-Guaranteed /
Handover requests when the Transmitted Code Power utilization exceeds pwrAdm
percent of maximumTransmissionPower which is the configurable parameter
denoting the maximum power available in the cell. Non-Guaranteed / Non-Handover
admission requests are blocked when the downlink transmitted carrier power
utilization exceeds pwrAdm – beMarginDlPwr. Guaranteed / Handover and
Guaranteed-HS / <any> are allowed up to the limit set by pwrAdm + pwrAdmOffset.
The current recommendation is to set pwrAdm=75 to allow for admission for all Service
Classes and Setup Types until 75% of maximumTransmissionPower the Transmitted
Code Power of the cell is exhausted. beMarginDlPwr=10 or 10% will cause Non-
Guaranteed / Non-Handover admission requests to be blocked at 65%.
pwrAdmOffset=10 or 10% will allow Guaranteed / Handover and Guaranteed-HS /
<any> if the Transmitted Code Power of the cell is at 85% or below.
– Downlink Air Speech Equivalent (ASE). The Air Speech Equivalent Admission
Policy is used to control the load in both the uplink and the downlink.
• For the Uplink, the Air Speech Equivalent (ASE) is monitored and admission is
blocked for all Guaranteed / Non-Handover, Non-Guaranteed / Handover and
Guaranteed-HS / Non-Handover requests when the number of Air Speech
Equivalents exceeds aseUlAdm. Non-Guaranteed / Non-Handover requests are
blocked when the number of Air Speech Equivalents exceeds aseUlAdm -
beMarginAseUl. Guaranteed / Handover and Guaranteed-HS / Handover
requests are blocked when the number of Air Speech Equivalents exceeds
aseUlAdm + aseUlAdmOffset.
• For the Downlink, the Air Speech Equivalent (ASE) is monitored and admission is
blocked for all Non-guaranteed / Handover requests, Guaranteed / <any> and
Guaranteed-HS / <any> requests when the number of Air Speech Equivalents
exceeds aseDlAdm. Non-Guaranteed / Non-Handover requests are blocked

when the number of Air Speech Equivalents exceeds aseDlAdm -

beMarginAseDl.
– Node B Hardware utilized. The Hardware Monitor provides admission control

based upon an estimation of the hardware utilized in the Uplink and Downlink.
• For the Uplink, the Hardware Utilization is monitored and admission is blocked
for all Guaranteed / Non-Handover, Non-Guaranteed / Handover and
Guaranteed-HS / Non-Handover requests when the percent of Uplink Hardware
Utilized exceeds ulHwAdm. Non-Guaranteed / Non-Handover requests are
blocked when the percent of Uplink Hardware Utilized exceeds ulHwAdm -
beMarginUlHw. Guaranteed / Handover and Guaranteed-HS / Handover
requests are blocked when the percent of Uplink Hardware Utilized arrives at
100%.
• For the Downlink, the Hardware Utilization is monitored and admission is blocked
for all Guaranteed / Non-Handover, Non-Guaranteed / Handover and
Guaranteed-HS / Non-Handover requests when the percent of Downlink
Hardware Utilized exceeds dlHwAdm. Non-Guaranteed / Non-Handover
requests are blocked when the percent of Downlink Hardware Utilized exceeds
dlHwAdm - beMarginDlHw. Guaranteed / Handover and Guaranteed-HS /
Handover requests are blocked when the percent of Downlink Hardware Utilized
arrives at 100%.
5.2.2.4 Directed Retry to GSM for Speech
Speech requests without ongoing packet connections (Multi-RAB) are considered for
Directed Retry to GSM during RAB establishment based upon the setting of the
configurable parameter loadSharingDirRetryEnabled. If this configurable parameter is
set to TRUE, and the WCDMA cell exceeds loadSharingGsmThreshold percent of
pwrAdm, the UTRAN requests a blind inter-RAT handover for
loadSharingGsmFraction percent of the Directed Retry candidates to the
directedRetryTarget configured GSM cell via the core network.
The current recommendation is to disable this capability by setting

loadSharingDirRetryEnabled to FALSE. All other parameters associated with this
function are simply defaulted.
5.2.2.5 Inter-Frequency Load Sharing
If multiple UARFCNs are available at a given Node B and the configurable parameter
loadSharingRrcEnabled is set the TRUE, Inter-Frequency Load Sharing will determine
if the WCDMA cell exceeds loadSharingMargin percent of pwrAdm at each call setup
during Radio Resource Control (RRC) Connection Establishment. If the cell exceeds
loadSharingMargin percent of pwrAdm, the UE will be directed to the UARFCN defined
by the Inter-Frequency load sharing neighbor as indicated by the loadSharingCandidate
flag.

The current recommendation is to disable this capability by setting

loadSharingRrcEnabled to FALSE. All other parameters associated with this function
are simply defaulted.
5.2.2.6 Packet Switched RAB Determination
If the type of Service requested of the UTRAN is Interactive Packet Switched and the UE
is HSDPA capable, the only Radio Access Bearer options are 384kb/HSDPA or
64kb/HSDPA. The UE is then assigned based upon the setting of the configurable
parameter hsOnlyBestCell to the best cell in the Active Set.
The current recommendation is to set the value of hsOnlyBestCell to TRUE thereby

allowing HSDPA to be supported on the best cell in the Active Set.
If the type of Service requested of the UTRAN is Interactive Packet Switched and the UE
is not HSDPA capable, the configurable parameter packetEstMode is used to determine
whether the attempt will be made to allocate the UE on RACH/FACH
(packetEstMode=0), sent to a 64kb/64kb Radio Access Bearer (packetEstMode=1) or if
it has the option of going to RACH/FACH if Admission Control disallows the assignment
to a 64kb/64kb Radio Access Bearer (packetEstMode=2).
The current recommendation is to set the value of packetEstMode=2 thereby allowing

an attempt at a 64kb/64kb Radio Access Bearer with fallback to RACH/FACH if you are
denied.
The following table provides parameter ranges and default values involved Establishing a
Call. They are listed in the same order they were presented. The Level column indicates
the network element that owns the parameter. The class column indicates if the
parameter is set based on Policy (must be set this way), Fixed (recommended to be set
this way) and Variable (set at your discretion).
Table 14 Call Establishment Configurable Parameters

Default Default
multiRabSp0Available 0=OFF, 1=ON 0 1 RNC Fixed N/A
multiRabUdi8Available 0=OFF, 1=ON 0 0 RNC Fixed N/A
psStreaming128 0=OFF, 1=ON 0 0 RNC Fixed N/A
allow384HsRab 0=OFF, 1=ON 0 1 RNC Fixed N/A
cnDrxCycleLengthCs 6 to 9 6=640 7=1280 RNC Fixed Integer
cnDrxCycleLengthPs 6 to 9 7=1280 7=1280 RNC Fixed Integer
noOfPagingRecordTransm 1 to 5 2 2 RNC Fixed Integer
noOfMaxDrxCycles 1 to 10 1 1 RNC Fixed DRX cycle
emergencyCallRedirect ON or OFF OFF OFF RNC Policy N/A
dlCodeAdm 0 to 100 70 80 Cell Var. 1%
beMarginDlCode 0 to 20 2 2 Cell Var. 5%


Default Default
sf8Adm 0 to 8 8 8 Cell Var. 1 radio link
sf16gAdm 0 to 16 16 16 Cell Var. 1 radio link
sf4AdmUl 0 to 1000 0 0 Cell Var. 1 radio link
compModeAdm 0 to 128 15 15 Cell Var. 1 radio link
hsdpaUsersAdm 0 to 1000 10 10 Cell Var. 1 radio link
pwrAdm 0 to 100 75 75 Cell Var. 1%
maximumTransmissionPower 0 to 500 400 400 Cell Var. 0.1 dBm
beMarginDlPwr 0 to 100 10 10 Cell Var. 1%
pwrAdmOffset 0 to 100 10 10 Cell Var. 1%
aseUlAdm 0 to 500 160 160 Cell Var. 1 ASE
beMarginAseUl 0 to 500 20 20 Cell Var. 1 ASE
aseUlAdmOffset 0 to 500 40 40 Cell Var. 1 ASE
aseDlAdm 0 to 500 240 240 Cell Var. 1 ASE
beMarginAseDl 0 to 500 100 100 Cell Var. 1 ASE
ulHwAdm 0 to 100 100 100 Iub Var. 1%
beMarginUlHw 0 to 100 0 0 Iub Var. 1%
dlHwAdm 0 to 100 100 100 Iub Var. 1%
beMarginDlHw 0 to 100 0 0 Iub Var. 1%
loadSharingDirRetryEnabled TRUE or FALSE FALSE FALSE RNC Fixed N/A
loadSharingGsmThreshold 0 to 100 100 100 Cell Fixed 1%
pwrAdm 0 to 100 75 75 Cell Fixed 1%
loadSharingGsmFraction 0 to 100 100 100 Cell Fixed 1%
directedRetryTarget 2G Neighbor N/A N/A Cell Var. N/A
loadSharingRrcEnabled TRUE or FALSE FALSE FALSE RNC Fixed N/A
loadSharingMargin 0 to 100 0 0 Cell Fixed 1%
loadSharingCandidate 3G Neighbor N/A N/A Nabr Var. N/A
hsOnlyBestCell TRUE or FALSE TRUE TRUE RNC Fixed N/A
packetEstMode 0, 1 or 2 1 1 RNC Fixed Integer
5.3 Mobility and Connection Management
This section contains the protocols and configurable parameters involved in maintaining a
call once it has been established. Measurement Fundamentals as they apply to Mobility
Management and Power Control are explained. Intra-RAT (UMTS) and Inter-RAT
(UMTS to GSM) Idle Mode Cell Reselection, Connected Mode Handover (including Inter-
RAT) and HSDPA Cell Change are covered. Channel Switching and Congestion Control
as they occur after Call Establishment are also included.
5.3.1 Measurement Fundamentals
Primary Common Pilot Channel (P-CPICH) Ec/No and / or Primary Common Pilot
Channel (P-CPICH) Received Signal Code Power (RSCP) are the quantities measured
by the UE that when certain conditions are met; trigger events that may lead to one of the
following:

• Intra-RAT Idle Mode Cell Reselection
• Inter-RAT Idle Mode Cell Reselection
• HS Cell Change
• Soft Handover
• Hard (Inter-Frequency) Handover
• Inter-RAT Handover
CPICH Ec/No and CPICH RSCP are explained in the Design Criteria section.
5.3.2 Cell Reselection in Idle Mode or Cell_FACH
In Idle Mode, the UE maintains a relationship with both sides of the Core Network (PS
and CS) in order to allow for the establishment of calls. First, an event has to be
triggered based upon configurable parameters sent in System Information Block (SIB),
then the Cell Reselection candidates are ranked according to signal level and quality. In
Cell_FACH, the UE is actually Connected Mode but is using Common Channels to relay
User Plane data.
5.3.2.1 Idle Mode Cell Reselection Triggers
When in Idle Mode, a UE only listens to one serving cell. The UE “camps” on this cell
until one of the following occurs:
• The cell is no longer suitable in terms of signal level (Srxlev) and quality (Squal). See
“Camping on a Suitable Cell” in the Idle Mode section.
• The quality (Squal) of the serving cell falls below the configurable parameter
sIntraSearch. If sIntraSearch=0, then the UE continuously performs measurements
on intra-frequency neighbors.
• If Inter-Frequency neighbors are assigned to the cell and the quality (Squal) of the
serving cell falls below the configurable parameter sInterSearch. If sInterSearch=0,
then the UE continuously performs measurements on Inter-Frequency neighbors. If
there are no Inter-Frequency neighbors defined on the cell, the setting of
sInterSearch has no impact.
• If Inter-RAT neighbors are assigned to the cell and either of the following two
conditions are met:
o The serving cell’s CPICH Ec/No becomes equal to or below qQualMin +
sRatSearch.
o The serving cell’s CPICH RSCP becomes equal to or below qRxLevMin
+ sHcsRat.
If there are no Inter-RAT neighbors defined on the cell, the settings of sRatSearch
and sHcsRat have no impact.

5.3.2.2 Cell_FACH Cell Reselection Triggers
If the configurable parameter interFreqFddMeasIndicator is set to TRUE, a UE in

Cell_FACH will evaluate Inter-Frequency and Inter-RAT neighbors. The UE performs
Inter-frequency and Inter-RAT measurements during FACH measurement occasions.
FACH measurement occasions are defined as being the frames where the following
equation is fulfilled.
SFN = C-RNTI mod n * 2^k

Where:
o SFN is the System Frame Number
o C-RNTI is the Cell Radio Network Temporary Identity
o n is 0, 1, 2 etc.
o k is the configurable parameter fachMeasOccaCycLenCoeff
5.3.2.3 Candidate Ranking
After the UE has been triggered to perform measurements, the measurements that
satisfy the Cell Selection S criteria (Squal and Srxlev are positive for UMTS neighbors or
only Srxlev is positive for GSM neighbors) are ranked according to the R criteria.
R(s) = Qmeas(s) + qHyst(s)

R(n) = Qmeas(n) - qOffset(s,n)
Where:
o s is the serving cell and n is the neighbor cell
o Qmeas is either the CPICH RSCP (qualMeasQuantity=1) or the CPICH Ec/No

(qualMeasQuantity=2) of the neighboring UMTS cell. The ranking for a GSM
neighbor is always done using the serving cell’s CPICH RSCP and the
neighboring GSM cell’s Received Signal Level.
o qHyst(s) is a hysteresis value read in System Information Block (SIB) 3 based

upon the configurable parameter qHyst1 if qualMeasQuantity=1 or qHyst2 if
qualMeasQuantity=2.
o qOffset is a an offset between the serving cell and the neighboring cell that can
be used to adjust the boarder between the two cells. The parameter is set per
neighbor using the configurable parameter qOffset1sn if qualMeasQuantity=1
or qOffset2sn if qualMeasQuantity=2.
Ranking is made using the measurement quantity CPICH RSCP.

• If a GSM cell is ranked better than the serving cell for the time interval treSelection,
the UE performs cell reselection to that cell.
• If a UMTS cell is ranked better than the serving cell for the time interval treSelection,
and the measurement quantity for cell reselection is set to CPICH RSCP
(qualMeasQuantity=1), the UE performs cell reselection to that cell else if
(qualMeasQuantity=2), the UE performs a second ranking of the UMTS cells based
on CPICH Ec/No and performs cell reselection to the best quality cell.
5.3.3 Handover in Connected Mode using Cell_DCH state
In Connected Mode, the call must be managed within acceptable Quality and
Retainability measures as the user moves about the network.
5.3.3.1 Soft Handover
To begin with, a call served by only one site through one Radio Link immediately after it
has been established. During RRC Connection Establishment the Serving Radio
Network Controller (SRNC) sends the UE a MEASURMENT CONTROL message
containing a list of neighbors and parameter values used to trigger neighbor
measurements. This information was also sent in System Information Blocks (SIBs) 11
and 12 while the UE was in Idle Mode, so the UE does have the information it needs in
order to make neighbor measurements before it receives the MEASURMENT CONTROL
message.
In Connected Mode, the UE continuously measures the Primary Common Pilot Channel
(P-CPICH) Ec/No of all the cells in its Active Set (cells that are in soft handover),
Monitored Set (cells which are on the neighbor list, but are not in soft handover) and
Detected Set (cells that are not in the neighbor list).
– Active Set Addition (Event 1a). If the Primary Common Pilot Channel (P-CPICH)
Ec/No of one of the neighboring cells in the Monitored Set becomes greater than the
Best Cell in the Active Set by reportingRange1a + hysteresis1a / 2, for a time equal
to timeToTrigger1a, then event 1a occurs. The UE then sends a MEASUREMENT
REPORT message for event 1a to the Serving Radio Network Controller (SRNC). If
the number of cells in the Active Set is less than the configurable parameter
maxActiveSet, the cell is considered for addition to the Active Set. If the number of
cells in the Active Set is equal to the configurable parameter maxActiveSet, then the
cell is proposed as a replacement for the cell with the worst quality in the Active Set.
– Active Set Deletion (Event 1b). If the Primary Common Pilot Channel (P-CPICH)
Ec/No of one of the cells in the Active Set becomes less than the Best Cell in the
Active Set by reportingRange1b - hysteresis1b / 2, for a time equal to
timeToTrigger1b, then event 1b occurs. The UE then sends a MEASUREMENT
REPORT message for event 1b to the Serving Radio Network Controller (SRNC).
The cell is then removed from the Active Set.
– Active Set Replacement (Event 1c). If the Primary Common Pilot Channel (P-
CPICH) Ec/No of one of the neighboring cells in the Monitored Set becomes greater
than the Worst Cell in the Active Set by hysteresis1c / 2, for a time equal to
timeToTrigger1c, and the number of cells in the Active Set is equal to the
configurable parameter maxActiveSet, then event 1c occurs. The UE then sends a

MEASUREMENT REPORT message for event 1c to the Serving Radio Network

Controller (SRNC) and the cell is proposed as a replacement for the cell with the
worst quality in the Active Set.
– Change of Best Cell (Event 1d). If the Primary Common Pilot Channel (P-CPICH)
Ec/No of any cell becomes greater than the Best Cell in the Active Set by
hysteresis1d / 2, for a time equal to timeToTrigger1d, then event 1d occurs. The
UE then sends a MEASUREMENT REPORT message for event 1d to the Serving
Radio Network Controller (SRNC).
5.3.3.2 Inter-Frequency or Inter-RAT Handover
In Connected Mode, the UE continuously measures the Primary Common Pilot Channel
(P-CPICH) Ec/No of the Best Cell in the Active Set. When one of the following Events
occur, the UE is commanded to make Compressed Mode measurements of Inter-RAT or
Inter-Frequency neighbors.
– Current Used Frequency is Below Threshold (Event 2d). If the Primary Common
Pilot Channel (P-CPICH) Ec/No of the Best Cell in the Active Set becomes less than
the absolute threshold usedFreqThresh2dEcno - hysteresis2d / 2, for a time equal
to timeToTrigger2dEcno, or if the Primary Common Pilot Channel (P-CPICH) RSCP
of the Best Cell in the Active Set becomes less than the absolute threshold
usedFreqThresh2dRscp - hysteresis2d / 2, for a time equal to
timeToTrigger2dRscp, then event 2d occurs. The UE then sends a
MEASUREMENT REPORT message for event 2d to the Serving Radio Network
Controller (SRNC). When the Serving Radio Network Controller (SRNC) receives
event 2d, it commands the UE to begin Compressed Mode measurements of:
o Inter-Frequency neighbors if the configurable parameter FddIfHoSupp=TRUE.
or
o Compressed Mode measurements of Inter-RAT neighbors if

FddGsmHoSupp=TRUE.
The configurable parameter hoType determines if Inter-Frequency or Inter-RAT

neighbors are evaluated first.
o If all cells in the Active Set have hoType=2 (None), neither Inter-Frequency or
Inter-RAT handover will be attempted.
o If at least one cell in Active Set has hoType=1 (GSM-Preferred), and no cell has
hoType=0 (IF-Preferred), Inter-RAT neighbors are evaluated first.
o If at least one cell in Active Set has hoType=0 (IF-Preferred), Inter-Frequency

neighbors are evaluated first.
– Current Used Frequency is Above Threshold (Event 2f). If the Primary Common
Pilot Channel (P-CPICH) Ec/No of the Best Cell in the Active Set becomes greater
than the absolute threshold usedFreqRelThresh2fEcno+usedFreqThresh2dEcno

+ hysteresis2f / 2, for a time equal to timeToTrigger2fEcno, and the Primary

Common Pilot Channel (P-CPICH) RSCP of the Best Cell in the Active Set is greater
than the relative threshold usedFreqRelThresh2fRscp+usedFreqThresh2dRscp +
hysteresis2f / 2, for a time equal to timeToTrigger2fRscp, then event 2f occurs.
The UE then sends a MEASUREMENT REPORT message for event 2f to the
Serving Radio Network Controller (SRNC). When the Serving Radio Network
Controller (SRNC) receives event 2f, it commands the UE to stop all Compressed
Mode measurements.
5.3.4 HS Cell Change
Based upon the setting of the configurable parameter hsQualityEstimate, if either the
Primary Common Pilot Channel (P-CPICH) Ec/No or Primary Common Pilot Channel (P-
CPICH) RSCP of one of the cells in the Active Set becomes greater than the Best Cell in
the Active Set by hsHysteresis1d / 2, for a time equal to hsTimeToTrigger1d, then
event 1d HS occurs. The UE then sends a MEASUREMENT REPORT message for
event 1d HS to the Serving Radio Network Controller (SRNC). If the configurable
parameter hsCellChangeAllowed is set to TRUE, a Serving HS-DSCH Cell Change will
occur.
5.3.5 Channel Switching
The Channel Switching algorithm applies after Interactive Class Call Establishment and
allows for the most efficient use of resources by dynamically switching the User Plane
data between Common Channels (Cell_FACH) and Dedicated Channels (Cell_DCH)
based upon the volume of data being transferred. As well, a UE in Cell_DCH, can be
switched among the available Interactive Class Radio Access Bearers (RABs), i.e. 64/64,
64/128 and 64/384.
In addition to a UE being up-switched and down-switched due to User Plane data

volume, a UE can be down-switched for reasons of Congestion Control, Admission
Control, Handover or Coverage.
• Congestion Control can channel switch a UE from Cell_DCH to Cell_FACH when

needed to solve a congestion situation.
• Admission Control can down-switch users to 64/64 when resources are needed for
Call Establishment.
• Handover can down-switch users to 64/64 when admission is denied to a UE trying to

add a Radio Link as in the case of Soft Handover.
• Coverage, or rather the lack of coverage, may cause the downlink code power to
increase to its maximum. In this case, a down-switch is preferable to exhausting
power and possibly dropping the connection.
The Channel Switching algorithm bases decisions upon three quantities:
– Buffer Load. Buffer load considers the size of the Radio Link Control (RLC) window
and the total number of bytes in the Service Data Unit (SDU) buffers and
retransmission buffers.

– Throughput. Uplink throughput is defined as the number of bits per second coming
up from the Medium Access Control (MAC) Layer to the Radio Link Control (RLC)
Layer. Downlink throughput is defined as the number of bits per second coming
down from the Radio Link Control (RLC) Layer to the Medium Access Control (MAC)
Layer.
– Downlink Code Power. The Downlink code power based upon the power of the
pilot bits of the Dedicated Physical Control CHannel (DPCCH).
The following sub sections define the algorithms wherein Up-Switches and Down-
Switches occur.
5.3.5.1 Common to Dedicated Up-Switch
While the UE is in Cell_FACH, Radio Link Control (RLC) buffer loading is monitored on
the uplink and downlink. If the Radio Link Control (RLC) buffer load in the uplink exceeds
the configurable parameter ulRlcBufUpswitch, or if the Radio Link Control (RLC) buffer
load in the downlink exceeds the configurable parameter dlRlcBufUpswitch, then if
allowed by admission control, an up-switch from Common Channels (Cell_FACH) to a
Dedicated channel (Cell_DCH) occurs.
5.3.5.2 Dedicated to Common Down-Switch
While the UE is in Cell_DCH, throughput is monitored on the uplink and downlink. If the
throughput on both the uplink and downlink falls below the configurable parameter
downswitchThreshold, the timer based upon the configurable parameter
downswitchTimer is started. If throughput on either the uplink or the downlink increases
above the configurable parameter downswitchTimerThreshold before
downswitchTimer expires, no down-switch is issued. However, if throughput does not
increase above downswitchTimerThreshold before downswitchTimer expires, a
down-switch to Cell_FACH occurs.
5.3.5.3 Common to Idle Mode Down-Switch
While the UE is in Cell_FACH, throughput is monitored on the uplink and downlink. If the
throughput on both the uplink and downlink is 0 kb/s for the configurable parameter
inactivityTimer seconds, the UTRAN sends an Iu Release Request to the Core Network
and the UE is sent to Idle Mode.
5.3.5.4 HS-DSCH to Idle Down Switch
While the UE is on the High Speed Downlink Shared CHannel (HS-DSCH), throughput is
monitored on the uplink and downlink. If the throughput on both the uplink and downlink
is 0 kb/s for the configurable parameter hsdschInactivityTimer seconds, the UTRAN
sends an Iu Release Request to the Core Network and the UE is sent to Idle Mode.

5.3.5.5 Coverage triggered Dedicated to Dedicated Down-Switch
Coverage, or rather the lack of coverage, may cause the downlink code power to
increase to its maximum. In this case, a down-switch from 64/384 to 64/128 or from
64/128 to 64/64 is preferable to exhausting power and possibly dropping the connection.
The algorithm monitors downlink code power on all legs in the Active Set. If the downlink
code power on all legs in the Active Set is within downswitchPwrMargin of
maximumTransmissionPower, then coverageTimer is started. If the code power on all
of the legs stays above maximumTransmissionPower - reportHysteresis before
coverageTimer expires, the UE is down-switched to the next lowest Radio Access
Bearer (RAB).
5.3.5.6 Dedicated to Dedicated Up-Switch
If the UE is using a 64/64 or a 64/128 Radio Access Bearer, its downlink throughput and
code power are monitored. If the downlink throughput exceeds 86% of the current Radio
Access Bearer’s (RAB’s) capacity, downlink code power is checked on all legs in the
active set to see if an Up-Switch is possible.
• The code power is checked by using the same downswitchPwrMargin configurable

parameter used in the Dedicated to Dedicated Down-Switch. If the estimated power
increase due to the Up-Switch (64 to128 = 2.9dB and 64 to 384 = 2.9dB) is within
maximumTransmissionPower – downswitchPwrMargin – upswitchPwrMargin,
then code power is considered to be available.
If an Up-Switch is possible and throughput exceeds 86% of the current Radio Access
Bearer’s (RAB’s) capacity for the amount of time specified by upswitchTimer, then an
Up-Switch to the next highest Radio Access Bearer is allowed through Admission Control
which should grant admission for each leg in the active set.
5.3.5.7 Multi-RAB Down-Switch
While the UE has a Mulit-RAB connection, throughput is monitored on the uplink and
downlink. If the throughput on both the uplink and downlink is 0 kb/s for the configurable
parameter downswitchTimerSp seconds for Multi-RAB CS Conversational 12.2k AMR
speech and PS Interactive 64/64 data (SP64), the PS Interactive 64/64 connection is
Down-Switched to CS Conversational 12.2k AMR speech and PS Interactive 0/0 data
(SP0)
5.3.5.8 Multi-RAB Up-Switch
While the UE has a Mulit-RAB CS Conversational 12.2k AMR speech and PS Interactive
0/0 data (SP0) connection, the Radio Link Control (RLC) buffer load is monitored on the
uplink and downlink. If the Radio Link Control (RLC) buffer load in the uplink exceeds
ulRlcBufUpswitchMrab or likewise if the Radio Link Control (RLC) buffer load in the
downlink exceeds dlRlcBufUpswitchMrab an Up-Switch to CS Conversational 12.2k
AMR speech and PS Interactive 64/64 data (SP64) will occur subject to Admission
Control.

5.3.6 Congestion Control
The Congestion Control algorithm has the ability to order the Admission Control algorithm
to block admission requests in order to reduce congestion. It can also down-switch
Interactive Packet Switched users to lower throughput Radio Access Bearers (RABs) in
an effort to reduce congestion while maintaining retainability.
Congestion must initially be detected, then measures must be taken to resolve it. The
following sections cover the parameters used for Congestion detection and resolution.
5.3.6.1 Congestion Detection
Congestion is detected through Downlink power utilization and Uplink Received Total
Wideband Power (RTWP) measurements obtained through the Node B. The cell is
considered Congested when either of these criteria is met.
– Downlink Congestion. When the Downlink Transmitted Carrier Power exceeds

pwrAdm + pwrAdmOffset + pwrOffset for a period of time greater than pwrHyst.
The Congested condition is not resolved until the Downlink Transmitted Carrier
Power is reduced below pwrAdm + pwrAdmOffset for a period of time greater than
pwrHyst.
The pwrAdm and pwrAdmOffset parameters are also used in Admission Control.
– Uplink Congestion. When Uplink Received Total Wideband Power (RTWP)

exceeds iFCong + iFOffset for a period of time greater than iFHyst. The Congested
condition is not resolved until the Downlink Transmitted Carrier Power is reduced
below iFCong + iFOffset for a period of time greater than iFHyst.
5.3.6.2 Congestion Resolution
Action is taken in the form of blocking new connections (Call Establishments and Hand-
ins) and by reducing the rate of existing Interactive Packet Switched connections. If the
Congestion is due to Downlink Power Utilization, all new connections are blocked and
actions are taken to resolve the Congestion. If the Congestion is due to Uplink Received
Total Wideband Power (RTWP), only Call Establishments are blocked as hand-ins
reduce Uplink Received Total Wideband Power (RTWP).
In the case of Downlink Congestion, beyond blocking Call Establishments and Hand-ins,
actions are taken to reduce the amount of downlink power used. This is done by
reducing the number of Air Speech Equivalents served by the cell until the Congestion
condition is resolved. These actions are taken in the following order.
1. Immediately after Downlink Congested is detected, releaseAseDlNg Non-

Guaranteed Air Speech Equivalents (ASEs) are released in the downlink and timers
tmInitialGhs and tmInitialG are started. As long as the congestion situation persists,
releaseAseDlNg Non-Guaranteed Air Speech Equivalents (ASEs) are released
every tmCongActionNg.
2. If Downlink Congestion persists after all the Non-Guaranteed ASEs in downlink are
released and the timer tmInitialGhs expires, releaseAseDlGhs Guaranteed-HS Air
Speech Equivalents (ASEs) are released in the downlink. As long as the congestion

situation persists, tmCongActionGhs Guaranteed-HS Air Speech Equivalents

(ASEs) are released every releaseAseDlGhs.
3. If Downlink Congestion persists after all Non-Guaranteed and Guaranteed-HS are
released in the downlink and the timer tmInitialG has expired, releaseAseDl
Guaranteed Air Speech Equivalents (ASEs) are released in the downlink. As long as
the congestion situation persists, releaseAseDl Guaranteed Air Speech Equivalents
(ASEs) are released every tmCongAction.
5.3.7 Uplink and Downlink Power Control
Table 15 Mobility and Connection Management Configurable Parameters

Default Default
sInterSearch 0 to 127 0 0 Cell Fixed dB
sIntraSearch 0 to 127 0 10 Cell Fixed dB
qQualMin See Idle Mode
sRatSearch -32 to 20 4 4 Cell Fixed dB
qRxLevMin See Idle Mode
sHcsRat -105 to -91 -105 -105 Cell Fixed dBm
interFreqFddMeasIndicator TRUE or FALSE FALSE FALSE Cell Fixed N/A
fachMeasOccaCycLenCoeff 0 to 12 0 0 Cell Fixed Integer
qHyst1 0 to 40 4 2 Cell Fixed dB
qOffset1sn (3G>3G) -50 to 50 0 0 Nabr Fixed dB
treSelection 0 to 31 2 1 Cell Fixed Second
reportingRange1a 0 to 29 6 6 RNC Fixed 0.5 dB
hysteresis1a 0 to 15 0 0 RNC Fixed 0.5 dB
timeToTrigger1a 0 to 15 11 (320) 11 (320) RNC Fixed 1 ms
maxActiveSet 2 to 4 3 3 RNC Fixed Cells
reportingRange1b 0 to 29 10 10 RNC Fixed 0.5 dB
hysteresis1b 0 to 15 0 0 RNC Fixed 0.5 dB
timeToTrigger1b 0 to 15 12 (640) 12 (640) RNC Fixed 1 ms
hysteresis1c 0 to 15 2 2 RNC Fixed 0.5 dB
timeToTrigger1c 0 to 15 11 (320) 11 (320) RNC Fixed 1 ms
hysteresis1d 0 to 15 15 15 RNC Fixed 0.5 dB
timeToTrigger1d 0 to 15 14 (2560) 14 (2560) RNC Fixed 1 ms
usedFreqThresh2dEcno -24 to 0 -12 -12 Cell Fixed dB
timeToTrigger2dEcno Various 320 320 RNC Fixed ms
usedFreqThresh2dRscp -115 to -25 -97 -112 Cell Fixed dBm


Default Default
timeToTrigger2dRscp Various 320 320 RNC Fixed ms
FddIfHoSupp TRUE or FALSE FALSE FALSE RNC Fixed N/A
FddGsmHoSupp TRUE or FALSE FALSE TRUE RNC Fixed N/A
hoType 0 to 2 1 1 Cell Fixed String
usedFreqRelThresh2fEcno 0 to 20 1 2 RNC Fixed dB
hysteresis2f 0 to 29 0 2 RNC Fixed dB
timeToTrigger2fEcno Various 1280 640 RNC Fixed ms
usedFreqRelThresh2fRscp 0 to 20 3 6 RNC Fixed dB
timeToTrigger2fRscp Various 1280 640 RNC Fixed ms
hsQualityEstimate Ec/No or RSCP RSCP RSCP RNC Fixed String
hsHysteresis1d 0 to 75 10 10 RNC Fixed 0.1 dB
hsTimeToTrigger1d Various 640 640 RNC Fixed ms
hsCellChangeAllowed TRUE or FALSE FALSE TRUE Cell Fixed N/A
ulRlcBufUpswitch Various 256 256 RNC Fixed 1byte
dlRlcBufUpswitch 0 to 2000 500 500 RNC Fixed 100 bytes
downswitchThreshold 0 to 32 0 0 RNC Fixed 1 kb/s
downswitchTimer 0 to 1000 10 10 RNC Fixed 100 ms
downswitchTimerThreshold 0 to 64 0 0 RNC Fixed 1 kb/s
inactivityTimer 1 to 1440 120 120 RNC Fixed 1 second
hsdschInactivityTimer ? ? ? RNC ? seconds
downswitchPwrMargin 0 to 20 2 2 RNC Fixed 0.5 dB
coverageTimer 0 to 100 10 10 RNC Fixed 100 ms
reportHysteresis 0 to 20 6 6 RNC Fixed 0.5 dB
upswitchPwrMargin 0 to 20 6 6 RNC Fixed 0.5 dB
upswitchTimer 0 to 100 5 5 RNC Fixed 100 ms
downswitchTimerSp 0 to 180 60 60 RNC Fixed 0.5 second
ulRlcBufUpswitchMrab Various 8 8 RNC Fixed 1 byte
dlRlcBufUpswitchMrab 0 to 20 0 0 RNC Fixed 1 byte
pwrOffset 0 to 100 5 5 Cell Fixed Percent
pwrHyst 0 to 60000 300 300 Cell Fixed 1 ms
iFCong 0 to 621 621 621 Cell Fixed 0.1 dBm
iFOffset 0 to 621 0 0 Cell Fixed 0.1 dBm
iFHyst 0 to 6000 6000 6000 Cell Fixed 10 ms
releaseAseDlNg 0 to 500 1 1 Cell Fixed 1 ASE
tmInitialGhs 10 to 100000 500 500 Cell Fixed 1 ms
tmInitialG 10 to 100000 3000 3000 Cell Fixed 1 ms
tmCongActionNg 500 to 100000 800 800 Cell Fixed 1 ms
releaseAseDlGhs 0 to 5000 1 1 Cell Fixed 0.1 ASE
tmCongActionGhs 10 to 100000 300 300 Cell Fixed 1 ms
releaseAseDl 0 to 500 1 1 Cell Fixed 1 ASE
tmCongAction 300 to 100000 2000 2000 Cell Fixed 1 ms
dlPcMethod 1 to 4 3 3 RNC Fixed Integer
fixedPowerDl 1 to 101 65 65 RNC Fixed 0.5 dB
fixedRefPower 1 to 101 65 65 RNC Fixed 0.5 dB
pcpichPowerDefault 0 to 50 33 33 RNC Fixed 1 dBm
ulOuterLoopRegulator 0 or 1 1 1 RNC Fixed String
ulSirStep 0 to 50 10 10 RNC Fixed 0.1 dB
sirMax -82 to 173 173 173 RNC Fixed 0.1 dB


Default Default
sirMin -82 to 173 -82 -82 RNC Fixed 0.1 dB
deltaAck1 0 to 8 4 4 Cell Fixed -
deltaNack1 0 to 8 4 4 Cell Fixed -
deltaCqi1 0 to 8 4 4 Cell Fixed -
initialCqiRepetitionFactor 1 to 4 1 1 Cell Fixed -
initialAcknackRepetitionFactor 1 to 4 1 1 Cell Fixed -
cqiFeedbackCycle 0 to 160 8 8 Cell Fixed ms
cqiErrors 0 to 100 10 10 Cell Fixed -
cqiErrorsAbsent 0 to 100 10 10 Cell Fixed -
hsScchMaxCodePwr -35 to +15 2 2 Cell Fixed 0.5 dB
hardIfhoCorr -5 to +15 3 3 Cell Fixed 1 dB

6. OSS Overview
Someone new to either UTRAN in general or Ericsson’s implementation of UTRAN must
first understand the availability of OSS-RC related services, i.e. fault, performance and
configuration management of the Radio and Core networks. Given the proper
understanding and access, the engineer can then measure performance and optimize
configuration based upon the recommendations given throughout this document.
The proceedures outline in this seciton are based upon Ericsson OSS-RC release R3.
Figure 1 below depicts the UTRAN with its various links including links to the OSS. User
access to the OSS is made available through a Citrix server.
Figure 5 OSS Connectivity
Core Network Prospect Client/Web Prospect

Citrix Server
Mu
n
Mur
Iu
OSS-RC
r RNC
Iu
t
Mu
Mu b
RNC Citrix Client

Iub
RXI Business
Objects
Client
NodeB
User Equipment
User Equipment

6.1 Configuration Management
There are various methods by which Ericsson UTRAN configurable parameters can be
viewed and updated. This section explains the procedures that must be followed in order
to obtain the necessary network access and credentials (username and password).
Network element addition / deletion procedures are not included in this document.
6.1.1 Configuration Access Procedures
The access process varies from region to region. Each region’s process is outlined
below. Once credentials are obtained, the user must install a Citrix ICA client on their
local machine or laptop. The software can be obtained by going to http://www.citrix.com.
Once installed, use the “Add ICA Connection” wizard to add a connection to one of your
region’s Citrix Servers.
Table 16 Configuration Management Access Procedures
Region Process Citrix Server IP

Central Contact Paul Aguon with the Central Region Network Field – ICA 1 - 10.175.144.68
NOC OSS group and provide the following: User Name, User ID ICA 2 - 10.175.144.71
(CUID), Title, Work Location, Telephone Number and Mobile
Number.
Northeast Contact John J. Elliott with the Northeast Region OSS Team. ICA 1 - 10.189.19.9
ICA 2 - 10.189.19.11
West Go to https://wnsuam.wnsnet.attws.com then click on “Request ICA 1 - 166.174.241.254
Access” and provide the appropriate information to request ICA 2 - 155.174.242.1
access to the Western Region Ericsson UMTS OSS – E7. The
Western Region OSS group can also be reached at (425) 288-
2211.
6.1.2 Configuration Methods
There are three main methods used to control the configuration of the UTRAN
– Export configuration data then import configuration changes through the OSS.
This is the preferred method for bulk changes. An externally prepared configuration
(Bulk CM file) is transferred to the OSS then imported into a “Planned Area”. When
the Planned Area is activated, the RNC and/or Node B configuration are updated.
The tool used is called the “WCDMA RAN Explorer” and is accessed by right clicking
on the OSS desktop and selecting Configuration, WCDMA radio access network,
then WCDMA RAN explorer. See reference [2a].
– Enter configuration changes via the OSS Graphical User Interface (GUI). This is
the Ericsson preferred method. First, a “Planned Area” is created, changes are made
to it using the Graphical User Interface, then the Planned Area is activated and the
RNC and/or Node B configuration are updated, i.e. the Planned Area becomes the

Valid Area. The tool used is called the “WCDMA RAN Explorer” and is accessed by
right clicking on the desktop and selecting Configuration, WCDMA radio access
network, then WCDMA RAN explorer. See reference [2a].
– Make configuration changes in the UTRAN via a ChangeAll script. A ChangeAll

script is written using a specific format in a text file (ChangeAll.txt). The script is then
executed as a task in the Job Manager application. ChangeAll allows the user to
make global parameter changes to specific network elements. See reference [2b].
– Use EMAS (Element Manager Software). EMAS exists on each network element
(Node B, RNC, RXI) and allows the user to directly view and change the individual
network element’s configuration. EMAS is typically not used to change parameters
that affect multiple network elements e.g. neighbor lists. EMAS uses a web client
from either the OSS via Citrix, or from your laptop assuming you are not blocked by
any firewalls.
The Ericsson OSS for UMTS does not support an operator available command line
interface.
6.2 Performance Management
There are currently three options available that can be used to access performance data.
– Business Objects. Business Objects is a third party application supported by

Ericsson that can be used to query the OSS performance reporting database.
Business Object can be used on the OSS via a Citrix client or by using a Business
Object client installed on your laptop. See the Business Objects access procedure
below for access instructions.
– Prospect. This performance reporting platform is also known as Watchmark which

was purchased by Vallent. Web browser and laptop client options are available. See
the Prospect Access procedure below for access instructions.
– Tektronix Probes. Probes have been installed on every interface from end to end in
the network. Statistical data is sent to the Prospect database for KPI creation. The
Tektronix Probe solution also has its own reporting interface accessible via a Citrix
client. See the Tektronix Probe Access procedure below for access instructions.
6.2.1 Performance Access Procedures
This section provides information concerning how one goes about obtaining access and
credentials to the various Performance Reporting systems.
6.2.1.1 Business Object Access
The tables below indicate the process whereby users obtain access to Business Objects
and Prospect. The Business Objects client software and installation instructions are
available at http://ossweb.sc.attws.com/NWS/. A “bomain.key” file is required in order to
access the Business Objects server.

Table 17 Business Object Access Procedure
Region Business Object Access Process Server Name IP and

Port
Central Contact Paul Aguon with the Central Region Network Field –
NOC OSS group and provide the following: User Name, User ID 10.175.144.4,5025
(CUID), Title, Work Location, Telephone Number and Mobile
Number.
Northeast Contact John J. Elliott with the Northeast Region OSS Team.
West Go to https://wnsuam.wnsnet.attws.com then click on “Request
Access” and provide the appropriate information to request 155.174.241.253,5025
access to the Western Region Ericsson UMTS OSS – E7. The
Western Region OSS group can also be reached at (425) 288-
2211.
6.2.1.2 Prospect Access
The Prospect Performance reporting system is nationally based.
• The Prospect client software and installation instructions are available at

http://ossweb.sc.attws.com/PES/APPS/Prospect/.
• Credentials can be obtained by going to

https://dataops.sc.attws.com/OSS/Account/Request.htm. Click on “P” for Prospect.
• The web interface is accessible via

http://alnpspctweb03.wnsnet.attws.com:8080/pweb/login.jsp
6.2.1.3 Tektronix Probe Access
The Tektronix Probe reporting system is nationally based.
• Credentials can be obtained by going to

https://dataops.sc.attws.com/OSS/Account/Request.htm. Click on “U” for UMTS KPI
Probe.
• The Citrix interface is accessible via 10.36.12.106. For complete client configuration
information, click on the “User Documentation” link at
http://nsnc.entp.attws.com/wns1/project.jsp?folderId=12606765
6.2.2 Ericsson Counter Types
Ericsson has seven different types of counters. Each type is designated based upon how
each counter is created.
– Peg Counter. A Peg Counter is simply incremented by 1 at each occurrence of a

specific event. All Peg Counters begin with pm…
– Gauge Counter. A Gauge Counter can be increased or decreased depending upon

the activity in the system. All Gauge Counters begin with pm…

– Accumulator. An Accumulator Counter is increased by the value of a sample. The

result is the sum of the values of the samples taken over the sample interval.
Accumulator counters always begin with pmSum… or pmSumOfSamp…
– Scan Counter. A Scan Counter is incremented by 1 each time a specific condition

exists when scanned. Scans for the condition occur at regular intervals. In most
cases a separate counter exists that counts the number of scans. All Scan Counters
begin with pmSamples…
– Probability Density Function (PDF). These types of counters result from

periodically reading the value of a quantity. The value is then used to increment a
corresponding counter. The counters are arranged in bins that represent segments
of the range of possible values. All Probability Density Function counters begin with
pm…
– Discrete Distributed Measurement (DDM). Discrete Distributed Measurements are

a series of values recorded during a reporting period. At the end of the reporting
period, each discrete measurement is recorded. All Discrete Distributed
Measurements begin with pm…
– Calculated Statistics. A Calculated Statistic results from a calculation made in the

database. The counters that contribute to the calculated value may or may not exist
by themselves. All Calculated Statistics begin with cm…
Counters can also be grouped based upon where they are created.
– RNC Counters
– Node B Counters
– RXI Counters
– OSS-RC Counters. These include only Calculated Statistics.
6.2.3 Call Trace Capability
Ericsson supports three different types of call trace called UETR, CTR and GPEH. Each
is briefly described below. Each is launched from the Performance menu in the OSS
Network Explorer. See reference [1b] and [1c].
– UETR. The User Equipment Traffic Recording capability allows for up to 16 specified
UEs to be concurrently traced on a single RNC. The individual UEs are specified by
IMSI. One or more event or measurement messages within one or more of the
following protocol groups can be recorded: NBAP, RANAP, RNSAP and RRC.
Although only one UE can be traced per UETR session, up to 16 concurrent sessions
can be run on a single RNC.
– CTR. Cell Traffic Recording allows for the collection of one or more NBAP, RANAP,
RNSAP or RRC event or measurement messages from the first 16 UEs that request
an RRC Connection setup on the specified cell. Up to 2 CTR recordings can be run
concurrently.

– GPEH. The General Performance and Event Handling capability records internal
node and inter-node events as defined in a GPEH subscription profile.
6.3 Fault Management
Fault Management allows for the identification of network elements that are currently, or
have recently been in a compromised condition due to a hardware or software failure.
Ericsson provides tools that allow the user to view network elements currently in fault. A
fault history is also available for each network element. See reference [2d].
6.3.1 Alarm Status Matrix
The Alarm Status Matrix provides a graphical overview of the fault status of network
elements. The status of the network element is indicated by its color. The Alarm List
Viewer is available via the OSS by right clicking on the desktop, then Alarm, View
Alarms, Alarm Status Matrix. After running Alarm Status Matrix, you must select a group
of Managed Objects by clicking on File, then Managed Objects and selecting the
appropriate network element. The Alarm Status Matrix is typically the starting point for
determining the status of the network.
6.3.2 Alarm List Viewer
The Alarm List Viewer is available via the OSS by right clicking on the desktop, then
Alarm, View Alarms, Alarm List Viewer. Current alarms for a network element or group of
network elements can be viewed by clicking on File, then Managed Objects and selecting
the appropriate network element.
6.3.3 Alarm Log Browser
Running the Alarm Log Browser starts an alarm search wizard that allows the user to
input variables such as date / time range and network element selection. It also allows
for result filtering and sorting. The result can provide a historical view of the faults of a
particular network element.

7. Counter Activation
In order for counter values to be placed in the OSS-RC database, they must be activated
for collection. Part of this process includes specifying the interval at which the database
is updated. There are limitations for how many counters may be active concurrently.
– RNC – 215,000 counters
– Node B – 10,000 counters
– RXI – 50,000 counters
An alarm is triggered if the maximum number of counters is exceeded.
A Subscription Profile represents a group of activated counters within a UTRAN. The

standard Cingular (User) defined Subscription Profile will include all of the counters
defined in Attachment V of the UMTS Contract and supported by this release of RNS
software. See reference [2c]

8. Reference Documents
The following documents are related to this document:
1. ALEX WCDMA Radio Access Network CPI P1B http://manchild.wireless.attws.com/cgi-bin/alex

a. System Performance Statistics, WCDMA PA4
b. WCDMA RAN Operation and Maintenance
c. REI, Recording and Events Interface, User Guide
2. Operations Support System (OSS) RC R3, Shipment C4 (Final) [R1C]
http://manchild.wireless.attws.com/cgi-bin/alex
a. WCDMA RAN Explorer, User Guide
b. ChangeAll User Guide
c. Subscription Profiles and Performance Monitoring User Guide
d. Fault Manager Alarm List Viewer, User Guide
3. 3GPP Specification http://www.3gpp.org

a. R6 TS 25.101 Clause 5 – Frequency Bands and channel arrangement
b. R6 TS 25.101 Clause 6.2.1 – UE maximum output power
c. R6 TS 25.101 Clause 7 – UE Receiver Characteristics
d. R6 TS 25.104 Clause 7 – Node B Receiver Characteristics
e. R6 TS 25.214 Annex C – Cell Search Procedure

9. Parameter Reference
This section provides an alphabetized table based reference to all configurable parameters.
Table 18 Alphabetized Parameter Reference
Parameter Range Ericsson Cingular Level Class Unit Description

Default Default
aichPower -22 to +5 -6 -6 Cell Fixed dB
allow384HsRab 0=OFF, 1=ON 0 1 RNC Fixed N/A
aseDlAdm 0 to 500 240 240 Cell Var. 1 ASE
aseUlAdm 0 to 500 160 160 Cell Var. 1 ASE
aseUlAdmOffset 0 to 500 40 40 Cell Var. 1 ASE
att 1 or 0 1 1 LA Fixed Integer
beMarginAseDl 0 to 500 100 100 Cell Var. 1 ASE
beMarginAseUl 0 to 500 20 20 Cell Var. 1 ASE
beMarginDlCode 0 to 20 2 2 Cell Var. 5%
beMarginDlHw 0 to 100 0 0 Iub Var. 1%
beMarginDlPwr 0 to 100 10 10 Cell Var. 1%
beMarginUlHw 0 to 100 0 0 Iub Var. 1%
cBackOff -60 to +60 0 0 RNC Fixed 0.25 dB
cellReserved Reserved or Not Not Not Cell Variable String
cnDrxCycleLengthCs 6 to 9 6=640 7=1280 RNC Fixed 10(2^k) ms
cnDrxCycleLengthPs 6 to 9 7=1280 7=1280 RNC Fixed 10(2^k) ms
compModeAdm 0 to 128 15 15 Cell Var. 1 radio link
ConstantValueCprach -35 to -10 -27 -27 Cell Fixed dB
coverageTimer 0 to 100 10 10 RNC Fixed 100 ms
cPO -30 to 30 0 0 RNC Fixed 0.1 dB
cqiErrors 0 to 100 10 10 Cell Fixed -
cqiErrorsAbsent 0 to 100 10 10 Cell Fixed -
cqiFeedbackCycle 0 to 160 8 8 Cell Fixed ms


Default Default
directedRetryTarget 2G Neighbor N/A N/A Cell Var. N/A
dlCodeAdm 0 to 100 70 80 Cell Var. 1%
dlHwAdm 0 to 100 100 100 Iub Var. 1%
dlInitSirTarget -82 to 173 41 41 RNC Fixed 0.1 dB
dlPcMethod 1 to 4 3 3 RNC Fixed Integer
dlRlcBufUpswitch 0 to 2000 500 500 RNC Fixed 100 bytes
dlRlcBufUpswitchMrab 0 to 20 0 0 RNC Fixed 1 byte
downswitchPwrMargin 0 to 20 2 2 RNC Fixed 0.5 dB
downswitchThreshold 0 to 32 0 0 RNC Fixed 1 kb/s
downswitchTimer 0 to 1000 10 10 RNC Fixed 100 ms
downswitchTimerSp 0 to 180 60 60 RNC Fixed 0.5 second
downswitchTimerThreshold 0 to 64 0 0 RNC Fixed 1 kb/s
ecNoPcpichDefault -20 to -10 -16 -16 RNC Fixed 1 dB
emergencyCallRedirect ON or OFF OFF OFF RNC Policy N/A
fachMeasOccaCycLenCoeff 0 to 12 0 0 Cell Fixed Integer
FddGsmHoSupp TRUE or FALSE FALSE TRUE RNC Fixed N/A
FddIfHoSupp TRUE or FALSE FALSE FALSE RNC Fixed N/A
filterCoeff6 various 19 19 RNC Fixed ^k
filterCoefficient2 various 2 2 RNC Fixed ^k
fixedPowerDl 1 to 101 65 65 RNC Fixed 0.5 dB
fixedRefPower 1 to 101 65 65 RNC Fixed 0.5 dB
gsmFilterCoefficient3 various 1 1 RNC Fixed ^k
gsmThresh3a -115 to 0 -102 -98 RNC Fixed dBm
hardIfhoCorr -5 to +15 3 3 Cell Fixed 1 dB
hoType 0 to 2 1 1 Cell Fixed String
hsCellChangeAllowed TRUE or FALSE FALSE FALSE RNC Fixed N/A
hsdpaUsersAdm 0 to 1000 10 10 Cell Var. 1 radio link
hsdschInactivityTimer RNC seconds
hsHysteresis1d 0 to 75 10 10 RNC Fixed 0.1 dB
hsOnlyBestCell TRUE or FALSE TRUE TRUE RNC Fixed N/A
hsQualityEstimate Ec/No or RSCP RSCP RSCP RNC Fixed String
hsScchMaxCodePwr -35 to +15 2 2 Cell Fixed 0.5 dB
hsTimeToTrigger1d Various 640 640 RNC Fixed ms
hysteresis1a 0 to 15 0 0 RNC Fixed 0.5 dB
hysteresis1b 0 to 15 0 0 RNC Fixed 0.5 dB


Default Default
hysteresis1c 0 to 15 2 2 RNC Fixed 0.5 dB
hysteresis2f 0 to 29 0 2 Fixed dB
hysteresis3a 0 to 15 0 2 RNC Fixed dB
iFCong 0 to 621 621 621 Cell Fixed 0.1 dBm
iFHyst 0 to 6000 6000 6000 Cell Fixed 10 ms
iFOffset 0 to 621 0 0 Cell Fixed 0.1 dBm
inactivityTimer 1 to 1440 120 120 RNC Fixed 1 second
initialAcknackRepetitionFactor 1 to 4 1 1 Cell Fixed -
initialCqiRepetitionFactor 1 to 4 1 1 Cell Fixed -
interFreqFddMeasIndicator TRUE or FALSE FALSE FALSE Cell Fixed N/A
lAC 1 to 65533, 65535 N/A N/A LA Variable Integer
loadSharingCandidate 3G Neighbor N/A N/A Nabr Var. N/A
loadSharingDirRetryEnabled TRUE or FALSE FALSE FALSE RNC Fixed N/A
loadSharingGsmFraction 0 to 100 100 100 Cell Fixed 1%
loadSharingGsmThreshold 0 to 100 100 100 Cell Fixed 1%
loadSharingMargin 0 to 100 0 0 Cell Fixed 1%
loadSharingRrcEnabled TRUE or FALSE FALSE FALSE RNC Fixed N/A
maxActiveSet 2 to 4 3 3 RNC Fixed Cells
maximumTransmissionPower 0 to 500 400 400 Cell Var. 0.1 dBm
maxPreambleCycle 1 to 32 4 3 Cell Fixed Cycles
maxTxPowerUl -50 to +33 24 24 Cell Fixed dBm
mcc 0 to 999 N/A 310 RNC Policy Integer
mnc 0 to 999 N/A 410 RNC Policy Integer
multiRabSp0Available 0=OFF, 1=ON 0 1 RNC Fixed N/A
multiRabUdi8Available 0=OFF, 1=ON 0 0 RNC Fixed N/A
nmo Mode 1 or 2 2 2 RA Fixed Integer
noOfMaxDrxCycles 1 to 10 1 1 RNC Fixed DRX cycle
noOfPagingRecordTransm 1 to 5 2 2 RNC Fixed Integer
packetEstMode 0, 1 or 2 1 1 RNC Fixed Integer
pcpichPowerDefault 0 to 50 33 33 RNC Fixed 1 dBm
pichPower -10 to +5 -7 -7 Cell Fixed dB


Default Default
powerOffsetP0 1 to 8 3 2 Cell Fixed dB
powerOffsetPpm -5 to +10 -4 0 Cell Fixed dB
preambleRetransMax 1 to 64 8 15 Cell Fixed Preambles
primaryCpichPower -100 to +500 300 300 Cell Fixed 0.1 dBm
primarySchPower -350 to +150 -18 -18 Cell Fixed 0.1 dB
primaryScramblingCode 0-512 N/A 3.3.3 Cell Variable Integer
psStreaming128 0=OFF, 1=ON 0 0 RNC Fixed N/A
pwrAdm 0 to 100 75 75 Cell Var. 1%
pwrAdm 0 to 100 75 75 Cell Fixed 1%
pwrAdmOffset 0 to 100 10 10 Cell Var. 1%
pwrHyst 0 to 60000 300 300 Cell Fixed 1 ms
pwrOffset 0 to 100 5 5 Cell Fixed Percent
qQualMin -24 to 0 -18 -19 Cell Fixed 1 dB
qRxLevMin -115 to -25 -115 -115 Cell Fixed dBm
rAC 0 to 255 N/A N/A RNC Variable Integer
releaseAseDl 0 to 500 1 1 Cell Fixed 1 ASE
releaseAseDlGhs 0 to 5000 1 1 Cell Fixed 0.1 ASE
releaseAseDlNg 0 to 500 1 1 Cell Fixed 1 ASE
reportHysteresis 0 to 20 6 6 RNC Fixed 0.5 dB
reportingRange1a 0 to 29 6 6 RNC Fixed 0.5 dB
reportingRange1b 0 to 29 10 10 RNC Fixed 0.5 dB
secondarySchPower -350 to +150 -35 -35 Cell Fixed 0.1 dB
sf16gAdm 0 to 16 16 16 Cell Var. 1 radio link
sf4AdmUl 0 to 1000 0 0 Cell Var. 1 radio link
sHcsRat -105 to +91 -105 -105 Cell Fixed 2 dB


Default Default
sHcsRat -105 to -91 -105 -105 Cell Fixed dBm
sib1PLMNScopeValueTag 0 to 31 N/A N/A Cell Variable Integer
sInterSearch 0 to 127 0 0 Cell Fixed dB
sIntraSearch 0 to 127 0 10 Cell Fixed dB
sirMax -82 to 173 173 173 RNC Fixed 0.1 dB
sirMin -82 to 173 -82 -82 RNC Fixed 0.1 dB
sRatSearch -32 to 20 4 4 Cell Fixed dB
t3212 0 to 255 10 10 LA Fixed 6 min
timeToTrigger1a 0 to 15 11 (320) 11 (320) RNC Fixed 1 ms
timeToTrigger1b 0 to 15 12 (640) 12 (640) RNC Fixed 1 ms
timeToTrigger1c 0 to 15 11 (320) 11 (320) RNC Fixed 1 ms
timeToTrigger1d 0 to 15 14 (2560) 14 (2560) RNC Fixed 1 ms
timeToTrigger2dEcno Various 320 320 RNC Fixed ms
timeToTrigger2dRscp Various 320 320 RNC Fixed ms
timeToTrigger2fEcno Various 1280 640 RNC Fixed ms
timeToTrigger2fRscp Various 1280 640 RNC Fixed ms
timeToTrigger3a 0 to 15 6=100 0=0 RNC Fixed ms
timeTrigg6b various 1280 640 RNC Fixed ms
tmCongAction 300 to 100000 2000 2000 Cell Fixed 1 ms
tmCongActionGhs 10 to 100000 300 300 Cell Fixed 1 ms
tmCongActionNg 500 to 100000 800 800 Cell Fixed 1 ms
tmInitialG 10 to 100000 3000 3000 Cell Fixed 1 ms
tmInitialGhs 10 to 100000 500 500 Cell Fixed 1 ms


Default Default
treSelection 0 to 31 2 1 Cell Fixed Second
ueTxPowerThresh6a -50 to 33 21 24 RNC Fixed dBm
ueTxPowerThresh6b -50 to 33 18 21 RNC Fixed dBm
ulHwAdm 0 to 100 100 100 Iub Var. 1%
ulInitSirTargetExtraHigh -82 to 173 92 92 RNC Fixed 0.1 dB
ulInitSirTargetHigh -82 to 173 82 82 RNC Fixed 0.1 dB
ulInitSirTargetLow -82 to 173 49 49 RNC Fixed 0.1 dB
ulInitSirTargetSrb -82 to 173 57 57 RNC Fixed 0.1 dB
ulOuterLoopRegulator 0 or 1 1 1 RNC Fixed String
ulRlcBufUpswitch Various 256 256 RNC Fixed 1byte
ulRlcBufUpswitchMrab Various 8 8 RNC Fixed 1 byte
ulSirStep 0 to 50 10 10 RNC Fixed 0.1 dB
upswitchPwrMargin 0 to 20 6 6 RNC Fixed 0.5 dB
upswitchTimer 0 to 100 5 5 RNC Fixed 100 ms
usedFreqRelThresh2fEcno 0 to 20 1 2 RNC Fixed dB
usedFreqRelThresh2fRscp 0 to 20 3 6 RNC Fixed dB
usedFreqThresh2dEcno -24 to 0 -12 -12 Cell Fixed dB
usedFreqThresh2dEcnoDrnc -24 to 0 -12 -12 RNC Fixed dB
usedFreqThresh2dRscp -115 to -25 -97 -112 Cell Fixed dBm
usedFreqThresh2dRscpDrnc -115 to -25 -97 -112 RNC Fixed dBm
usedFreqW2d 0.0 to 2.0 0 1 RNC Fixed dB
usedFreqW2f 0.0 to 2.0 1 1 RNC Fixed dB
utranFilterCoefficient3 various 2 2 RNC Fixed ^k
utranRelThresh3aEcno -10 to 10 -1 2 RNC Fixed dB
utranRelThresh3aRscp -20 to 20 -3 7 RNC Fixed dB
utranRelThreshRscp 0 to 40 5 5 ? Fixed dB
utranW3a 0.0 to 2.0 0 1 RNC Fixed dB

Appendix A Consulted List

The following individuals have participated in the creation of this document. The name of
each participant is provided along with the group (region in parentheses) each participant
represents. The market groups are presented chronologically by launch phase.
Q4 2005 Launch Markets
• Austin (C) – Lewis, Robert S; Quinonez, Rick; Bendele, Shelia; Barrientos, Joseph;
Richard, Hill
• Chicago (C) – Bledsoe, Ronald W
• Dallas (C) – Parkoff, Seth; Wang, Jimmy; Coleman, Phillip; Shelton, David; Chan,
Rosa; Wells, Bobby; Steward, H. Jim; Smith, J. Mike (NTX);
• Houston (C) – Jackowski, Frank
• Boston (NE) – Wysocki, Tim; Leary, Jeff
• San Diego (W) – Bossom, Michael; Noet, Mark; Olah, Otto; Salas, Tony; Taylor,
Chris K; Banchongsirichareon, Soontorn
• San Francisco / San Jose (W) – Caniglia, Michael; Albrecht, Frank
• Vallejo (W) – Albrecht, Frank
• Indianapolis (C) – Bledsoe, Ronald W
• Gary (C) – Salyer, David
• San Antonio (C) – Tadlock, Jimmie
• Oklahoma City (C) – Benson, Brent
• Los Angeles / Bakersfield / Oxnard (W) – Hollister, Jim; Wan, Wang
• Fresno, Sacramento, Stockton (W) – Albrecht, Frank; Appert, Douglas
• Pittsburgh (NE) – Thomas, Matthew; Dugan, Shawn
• Bridgeport / Hartford / New Bedford / New Haven, CT (NE) – Klein, Robert S.
• Providence (NE) – Crawford, Ken; Tang, Che
• Tulsa (C) – Howell, Bill
2007 Launch Markets
• McAllen (C) – Tadlock, Jimmie
• Honolulu (W) – Oshiro, Henry

• El Paso (C) – Rocha, Adrian
• Newport News, Norfolk (NE) – Mughal, Naeem; Khalaf, Emile (Tony)
• Richmond (NE) – Mughal, Naeem; Patel, Vipul; Tolbert, Michael; Hill, Tommy
Regional Representation
• West – Costanzo, Ross; Young, James; Caine, Richard; Ulanday, Daniel; Clark,
Robert I.; Solis Bobie; Eter, Elias; Spencer, Michael (OSS); Delany, Clive
• Central – Collins, Kerwin; Palmer, Craig; Aguon, Paul (OSS); Thompson, Nicholas R;
Baltazar, Alona; Ye, Weihua
• Northeast – Gray, Randall – Apollonio, Laura; May, Christopher (OSS); Khuu, Khoa;
Davis, Richard J; Elliott, John J. (OSS) ; Rai, Paritosh; McCarthy, Brian
• Southeast – Narang, Ashish (no current or planned Ericsson UTRAN markets)
National Representation
• Strategic Planning – Vallath, Sree; Sam, Anthony; Choi-Grogan, Shirley
• National Field Support – Heubel, Michael; Gopalan, Raja; Tong, Hendry; Scharosch,
Greg; Smith, Juan (Derrick); Carrillo, Joe; Scheihing, Terry; Davis, Charles;
Mascarenhas, Patrick
• National Quality and Performance (national scorecard) – Barnes, Karen; Jaidi, Khalil;
Kim, Agnes
• National Services Operations – James, Dan
• Subscriber Product Engineering – Delmendo, Eddie; Hlavaty-Lapsoa, Michael
• National RF Engineering – Herndon, Al
Ericsson Representation
• Abad, Younes (UTRAN)
• Johnsson, Inge (OSS)
• Dirocco, Andrea (UTRAN)
• Mao, Tom (UTRAN)

Appendix B Index
aichPower, 21, 32, 62 hoType, 46, 52, 63
allow384HsRab, 34, 41, 62 hsCellChangeAllowed, 47, 52, 63
aseDlAdm, 39, 42, 62 hsdpaUsersAdm, 39, 42, 63
aseUlAdm, 39, 42, 62 hsdschInactivityTimer, 48, 52, 63
aseUlAdmOffset, 39, 42, 62 hsHysteresis1d, 47, 52, 63
att, 21, 24, 32, 62 hsOnlyBestCell, 41, 42, 63
beMarginAseDl, 40, 42, 62 hsQualityEstimate, 47, 52, 63
beMarginAseUl, 39, 42, 62 hsScchMaxCodePwr, 53, 63
beMarginDlCode, 38, 41, 62 hsTimeToTrigger1d, 47, 52, 63
beMarginDlHw, 40, 42, 62 hysteresis1a, 22, 32, 45, 51, 63
beMarginDlPwr, 39, 42, 62 hysteresis1b, 22, 32, 45, 51, 63
beMarginUlHw, 40, 42, 62 hysteresis1c, 22, 32, 45, 51, 64
cBackOff, 27, 32, 62 hysteresis1d, 22, 32, 46, 51, 64
cellReserved, 21, 32, 62 hysteresis2d, 46, 51, 64
cnDrxCycleLengthCs, 21, 32, 36, 41, 62 hysteresis2f, 47, 52, 64
cnDrxCycleLengthPs, 21, 32, 36, 41, 62 hysteresis3a, 64
compModeAdm, 39, 42, 62 iFCong, 50, 52, 64
ConstantValueCprach, 21, 32, 62 iFHyst, 50, 52, 64
coverageTimer, 49, 52, 62 iFOffset, 50, 52, 64
cPO, 28, 29, 32, 62 inactivityTimer, 48, 52, 64
cqiErrors, 53, 62 initialAcknackRepetitionFactor, 53, 64
cqiErrorsAbsent, 53, 62 initialCqiRepetitionFactor, 53, 64
cqiFeedbackCycle, 53, 62 interFreqFddMeasIndicator, 44, 51, 64
deltaAck1, 53, 62 lAC, 21, 30, 31, 64
deltaAck2, 53, 62 loadSharingCandidate, 40, 42, 64
deltaCqi1, 53, 62 loadSharingDirRetryEnabled, 40, 42, 64
deltaCqi2, 53, 62 loadSharingGsmFraction, 40, 42, 64
deltaNack1, 53, 62 loadSharingGsmThreshold, 40, 42, 64
deltaNack2, 53, 62 loadSharingMargin, 40, 42, 64
directedRetryTarget, 40, 42, 63 loadSharingRrcEnabled, 40, 41, 42, 64
dlCodeAdm, 38, 41, 63 maxActiveSet, 45, 51, 64
dlHwAdm, 40, 42, 63 maximumTransmissionPower, 39, 42, 49, 64
dlInitSirTarget, 27, 32, 63 maxPreambleCycle, 25, 32, 64
dlPcMethod, 52, 63 maxTxPowerUl, 21, 23, 32, 64
dlRlcBufUpswitch, 48, 52, 63 maxTxPowerUL, 21, 32, 64
dlRlcBufUpswitchMrab, 49, 52, 63 mcc, 20, 31, 64
downswitchPwrMargin, 49, 52, 63 mnc, 20, 31, 64
downswitchThreshold, 48, 52, 63 multiRabSp0Available, 34, 41, 64
downswitchTimer, 48, 52, 63 multiRabUdi8Available, 34, 41, 64
downswitchTimerSp, 49, 52, 63 nmo, 21, 32, 64
downswitchTimerThreshold, 48, 52, 63 noOfMaxDrxCycles, 36, 41, 64
ecNoPcpichDefault, 27, 32, 63 noOfPagingRecordTransm, 36, 41, 64
emergencyCallRedirect, 37, 41, 63 packetEstMode, 41, 42, 64
fachMeasOccaCycLenCoeff, 44, 51, 63 pcpichPowerDefault, 52, 64
FddGsmHoSupp, 46, 52, 63 pichPower, 21, 32, 64
FddIfHoSupp, 46, 52, 63 pO1, 27, 32, 64
filterCoeff6, 63 pO2, 27, 32, 64
filterCoefficient2, 63 pO3, 27, 32, 65
fixedPowerDl, 52, 63 powerOffsetP0, 22, 25, 32, 65
fixedRefPower, 52, 63 powerOffsetPpm, 25, 32, 65
gsmFilterCoefficient3, 63 preambleRetransMax, 22, 25, 32, 65
gsmThresh3a, 63 primaryCpichPower, 15, 21, 25, 27, 28, 29, 31,
hardIfhoCorr, 53, 63 65

primarySchPower, 18, 31, 65 sirMin, 53, 66

primaryScramblingCode, 14, 16, 19, 31, 65 sRatSearch, 21, 32, 43, 51, 66
psStreaming128, 34, 41, 65 t3212, 21, 31, 32, 66
pwrAdm, 39, 40, 42, 50, 65 timeToTrigger1a, 22, 32, 45, 51, 66
pwrAdmOffset, 39, 42, 50, 65 timeToTrigger1b, 22, 32, 45, 51, 66
pwrHyst, 50, 52, 65 timeToTrigger1c, 22, 32, 45, 51, 66
pwrOffset, 50, 52, 65 timeToTrigger1d, 22, 32, 46, 51, 66
qHyst1, 44, 51, 65 timeToTrigger2dEcno, 46, 47, 51, 66
qHyst2, 21, 32, 44, 51, 65 timeToTrigger2dRscp, 46, 47, 52, 66
qOffset1sn (3G>2G), 51, 65 timeToTrigger2fEcno, 47, 52, 66
qOffset1sn (3G>3G), 51, 65 timeToTrigger2fRscp, 47, 52, 66
qOffset2sn (3G>3G), 51, 65 timeToTrigger3a, 66
qQualMin, 21, 23, 24, 32, 43, 51, 65 timeTrigg6b, 66
qRxLevMin, 21, 23, 32, 43, 51, 65 tmCongAction, 51, 52, 66
qualMeasQuantity, 21, 32, 44, 45, 51, 65 tmCongActionGhs, 51, 52, 66
rAC, 21, 30, 32, 65 tmCongActionNg, 50, 52, 66
releaseAseDl, 51, 52, 65 tmInitialG, 50, 51, 52, 66
releaseAseDlGhs, 50, 52, 65 tmInitialGhs, 50, 52, 66
releaseAseDlNg, 50, 52, 65 treSelection, 21, 32, 45, 51, 67
reportHysteresis, 49, 52, 65 ueTxPowerThresh6a, 67
reportingRange1a, 22, 32, 45, 51, 65 ueTxPowerThresh6b, 67
reportingRange1b, 22, 32, 45, 51, 65 ulHwAdm, 40, 42, 67
secondarySchPower, 19, 31, 65 ulInitSirTargetExtraHigh, 29, 32, 67
sf16Adm, 38, 42, 65 ulInitSirTargetHigh, 29, 32, 67
sf16gAdm, 39, 42, 65 ulInitSirTargetLow, 29, 32, 67
sf32Adm, 39, 42, 65 ulInitSirTargetSrb, 29, 32, 67
sf4AdmUl, 39, 42, 65 ulOuterLoopRegulator, 52, 67
sf8Adm, 38, 42, 65 ulRlcBufUpswitch, 48, 52, 67
sHcsRat, 21, 32, 43, 51, 65, 66 ulRlcBufUpswitchMrab, 49, 52, 67
sib11RepPeriod, 20, 31, 66 ulSirStep, 52, 67
sib11StartPos, 20, 31, 66 upswitchPwrMargin, 49, 52, 67
sib12RepPeriod, 20, 31, 66 upswitchTimer, 49, 52, 67
sib12StartPos, 20, 31, 66 usedFreqRelThresh2fEcno, 46, 52, 67
sib1PLMNScopeValueTag, 20, 23, 32, 66 usedFreqRelThresh2fRscp, 47, 52, 67
sib1RepPeriod, 20, 31, 66 usedFreqThresh2dEcno, 46, 51, 67
sib1StartPos, 20, 31, 66 usedFreqThresh2dEcnoDrnc, 67
sib3RepPeriod, 20, 31, 66 usedFreqThresh2dRscp, 46, 47, 51, 67
sib3StartPos, 20, 31, 66 usedFreqThresh2dRscpDrnc, 67
sib5RepPeriod, 20, 31, 66 usedFreqW2d, 67
sib5StartPos, 20, 31, 66 usedFreqW2f, 67
sib7RepPeriod, 20, 22, 31, 66 utranFilterCoefficient3, 67
sib7StartPos, 20, 31, 66 utranRelThresh3aEcno, 67
sInterSearch, 43, 51, 66 utranRelThresh3aRscp, 67
sIntraSearch, 43, 51, 66 utranRelThreshRscp, 67
sirMax, 52, 66 utranW3a, 67


Volume II - Ericsson Field Guide For UTRAN P1-Lite: Feature Parameters and Best Practices

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Volume II - Ericsson Field Guide For UTRAN P1-Lite: Feature Parameters and Best Practices

Uploaded by

Copyright:

Available Formats

Network Services Volume II – Ericsson Field Guide for UTRAN P1-Lite

Volume II – Ericsson Field Guide for

Network Document ND-00150 Rev. 1.1 11/28/2005

This Field Guide is broken into 11 sections including a description of:

IMPORTANT: This document is the result of an ongoing collaborative effort

ND-00150 CINGULAR WIRELESS CONFIDENTIAL & PROPRIETARY Page 1 of 71

ND-00150 CINGULAR WIRELESS CONFIDENTIAL & PROPRIETARY Page 2 of 71

5.1.1 Cell Search Procedure...................................................................................................... 18

ND-00150 CINGULAR WIRELESS CONFIDENTIAL & PROPRIETARY Page 3 of 71

Figure 2 Power Ramping on RACH ....................................................................................................... 25

ND-00150 CINGULAR WIRELESS CONFIDENTIAL & PROPRIETARY Page 4 of 71

Document Revision History

Date Rev Revision Description Writer Sponsor

11/01/2005 1.0 Release version Michael Adnan Naqvi

Accountable Responsible Consulted Informed

Greg Scharosch Michael Noah Market Engineering Mike Pietropola

Copyright © 2005 by Cingular Wireless Services, Inc.

ND-00150 CINGULAR WIRELESS CONFIDENTIAL & PROPRIETARY Page 5 of 71

1. About This Document

1.4 Related Documentation

1.5 Acronyms and Terms

ND-00150 CINGULAR WIRELESS CONFIDENTIAL & PROPRIETARY Page 6 of 71

The following conventions are used throughout this document:

• The term “function” refers to Ericsson’s implementation of a certain portion of the

• All Ericsson configurable parameters are expressed in boldItalic.

For questions or comments about this document's technical content or to request

Michael Noah, Sr. System Engineer – National Field Support

ND-00150 CINGULAR WIRELESS CONFIDENTIAL & PROPRIETARY Page 7 of 71

2. New Features and Parameters in WRAN P4 UM2 (P1-Lite)

2.1 New Features

2.2 New or Modified Parameters

ND-00150 CINGULAR WIRELESS CONFIDENTIAL & PROPRIETARY Page 8 of 71

3. Significant KPI Impact Parameters

Idle Mode and Paging

ND-00150 CINGULAR WIRELESS CONFIDENTIAL & PROPRIETARY Page 9 of 71

4.1.1 Frequency Bands

Table 1 Operating Bands

Operating Band UL Frequencies DL Frequencies TX-RX Separation

4.1.2 Channel Numbering Scheme (UARFCN)

– “General” UARFCN method. Each UARFCN is defined with a specific center

ND-00150 CINGULAR WIRELESS CONFIDENTIAL & PROPRIETARY Page 10 of 71

– “Additional Channels” UARFCN method. The “Additional Channels” are specified

Either the “General” or “Additional Channels” method can be used to designate

Table 2 UARFCN List for Bands II and V

UL UARFCN UL Center DL UARFCN DL Center PCS / Cellular

4.1.3 Power Classes

Table 3 UE Power Classes

Operating Power Class 1 Power Class 2 Power Class 3 Power Class 4

ND-00150 CINGULAR WIRELESS CONFIDENTIAL & PROPRIETARY Page 11 of 71

III - - - - +24 +1/-3 +21 +2/-2

HS-DSCH Maximum Minimum inter- Maximum number of bits Total number of

4.3 Link Budget

Table 5 Link Budget

Downlink Value Notes

ND-00150 CINGULAR WIRELESS CONFIDENTIAL & PROPRIETARY Page 12 of 71

Difference (dB) 0 Difference between UL and DL path losses

4.4 Basic Design Requirements

4.4.1 Pilot Pollution

ND-00150 CINGULAR WIRELESS CONFIDENTIAL & PROPRIETARY Page 13 of 71

4.4.2 Neighbor List Determination

– Intra-UARFCN Neighbors. These neighbor relationships are assigned wherever

– Inter-UARFCN Neighbors. These neighbor relationships allow for Hard Handover

– Inter-RAT Neighbors. Inter-RAT neighbor relationships allow for Hard Handover