1.

1 Hotspot 2nd Carrier Deployment

In this solution, capacity on a cell basis is duplicated and load is evenly
distributed on the two carriers within the same sector. Idle mode cell
reselection mechanisms are very useful in dividing load and traffic between
two carriers. The main purpose of the whole setup is to enhance capacity on
f2 locally, by limiting possible accesses on the fringe of the f2 cell. The aim is
also to limit a possible negative impact on drop call rate and capacity, by
minimizing compressed mode usage. A typical single Cell 2nd carrier
deployment is illustrated in Figure 0-1: Hotspot Deployment Strategy below.

f2
hoType=IFHO_PREFERED
IFLS
f1

IFHO Cell reselection

hoType=NONE hoType=NONE hoType=NONE

This scenario will be dominated by small, or fairly large, two-carrier islands.

Capacity on a cell basis is duplicated and load is evenly distributed on the two
carriers within the same sector.
Idle mode cell reselection mechanisms are very useful in dividing load and
traffic between two carriers.
The main purpose of the whole setup is to enhance capacity on f2 locally, by
limiting possible accesses on the fringe of the f2 cell.

Figure 0-1: Hotspot Deployment Strategy

Idle mode UEs can perform cell reselection from the f2 cell to any f1 cell but
normally only UEs in the co-located perform cell reselection to the f2 as
illustrated in Figure 0-1: Hotspot Deployment Strategy above. Since the f2
cell has hoType=IFHO_PREFERED and the f1 cells have it set to NONE
IFHO will only be performed from the f2 cell to the f1 cells. IFLS is
performed between the co-located f1 and f2 cells.

Neighbour Relations:
Two-way neighbor cell relationships are defined only between the
underlaying f1 cell and the over-laying f2 cell.
One-way neighbor cell relationships are defined from the f2 cell to all the
surrounding f1 cells. Used same list as f1.
Advantage: reduced CPM and neighbor list size

All cells should be treated equally in idle mode.

Therefore, qOffset2sn=0dB in all defined directions

IFLS useful to control load

in case instant power peaks on f1 or f2 occur, as the fairly even
distribution caused by idle mode behavior might not be perfect.
Used only between the under-laying f1 cell and the over-laying f2 cell.

Higher qQualMin or qRxLevMin value must be applied in the f2 cell

to prevent UEs from setting up connections close to the cell borders
to stop UEs from starting CPM once a successful access is made.

Figure 0-2: Hotspot Deployment Setup

The following configuration is recommended for single cell 2nd carrier

deployment:
Two-way neighbor cell relationships are defined only between the
underlying f1 cell and the over-laying f2 cell. One-way neighbor
cell relationships are defined from the f2 cell to all the
surrounding f1 cells. The main benefits with this setup are the
elimination of IFHO from the surrounding f1 cell to the f2 cell,
the decreased risk of CPM starts in the f1 layer, and the shorter
neighbor lists. With one-way definitions, all surrounding f1 cells
become blind to the f2 cell.
The idea behind the solution is that all cells should be treated
equally in idle mode. Therefore, qOffset2sn=0dB in all defined
directions, both between and within carriers, must be applied.
Only during the careful introduction of this long-term solution,
higher parameter values can be considered. qOffset2sn could be
lowered step by step from +/-5dB down to +/-0dB, while
monitoring the performance and possible effects on drop rate in
the f2 cell.
An even distribution of load and traffic on the two carriers by
means of idle mode makes it very unlikely that IFLS would be
triggered. Even so, IFLS could be useful in case instant power
 peaks on f1 or f2 occur, as the fairly even distribution caused by
idle mode behavior might not be perfect. The share of all traffic
being re-directed between carriers will be very small. IFLS is to
be used only between the under-laying f1 cell and the over-laying
f2 cell.
A key measure in this deployment is the usage of the
qRxLevMin parameter. A higher qRxLevMin value must be
applied in the f2 cell in order to prevent UEs from setting up
connections close to the cell borders, and to stop UEs from
starting CPM once a successful access is made. A level slightly
higher than the CPM start level is recommended initially, but
lower values are also possible. Another important mechanism of
qRxLevMin is to steer the amount of load in the second carrier
cell, and control that the load carried actually belongs to the first
carrier cell, which needs to be offloaded.

Field experiences show that this setup has proven safe with very good
performance.

1.2 Cluster 2nd Carrier Deployment

It is also possible to deploy the 2nd carrier in a cluster of cells. In this solution,
capacity on a cluster basis is duplicated and load is evenly distributed on the
two carriers. Idle mode cell reselection mechanisms are very useful in
dividing load and traffic between two carriers. As field experiences show that
drop rate and other performance indicators are maintained on good levels, cell
reselection is the preferred method in distributing load. The main purpose of
the whole setup is to utilize capacity on f2, and minimize a possible negative
impact on drop call rate and capacity, by minimizing compressed mode usage.

Capacity on a cluster basis is duplicated and load is evenly

distributed on the two carriers.
Cell reselection is the preferred method (in terms of drop
rate, etc) in distributing load.
Main purpose of the whole setup is to utilize capacity on f2,
and minimize a possible negative impact on drop call rate
and capacity, by minimizing compressed mode usage.

Figure 0-3: Cluster Deployment Strategy

 ypical multiple Cell 2nd carrrier deploym
A ty ment is illustraated in Figuree 0-4
belo
ow.

Figure 0-4: Cluster 2nd Carrierr Deploymentt

Idlee mode UEs canc perform cellc reselectionn from the f22 cells to only the co-
locaated f1 cells as i Figure 0-4 above. Sincee the f2 cell inn the
a illustrated in
midddle of the cluuster has hoTType=NONE traffic can oonly be offloaaded to the
colllocated f1 celll using IFLS.. The f2 cellss at the edge oof the cluster have
hoType=IFHO_ _PREFERED D which will aallow handovver to the f1 cco-located
cellls. The f1 cellls at the edgee of the clusteer have
hoType=GSM_ _PREFERED which will aallow Inter Raadio Access
Tecchnology Han ndover (IRAT THO) to GSM M to avoid droopped calls at the edge
of WCDMA
W covverage.

All
A cells sh
hould be tre
eated equa
ally in idle mode.
Therefore
e, qOffset2sn=0dB in all directions
IFLS usefu
ul to contro
ol load
in case innstant power peaks on f1 or f2 occur, as the fairlyy even
distributio
on caused byy idle mode behavior
b migght not be peerfect.
used with hin the whole
e cluster, both from the f1
1 to the f2 ce
ells
CPM
C and IFHO
I mustt only be possible
p fro
om the borrder cells
o the second carrier.
on
Thereby, CPM and IF
FHO usage iss minimized.
Higher
H qQuualMin and d qRxLevM Min value must be applied
a in
t exit cellls in orderr to preven
the nt UEs from
m setting up
c
connection
ns close to the cell bo orders.
Figure 0-5: Cluster Deployme
ent Setup
 The following configuration is recommended for multiple cell 2nd carrier
deployment:

The main driver behind the solution is that all cells should be
treated equally in idle mode. Therefore, qOffset2sn=0dB in all
directions, both between and within carriers, must be applied.
Only during the careful introduction of this long-term solution,
higher parameter values can be considered. qOffset2sn could be
lowered step by step from +/-5dB down to +/-0dB, while
monitoring the performance and possible effects on drop rate in
the f2 border areas.
An even distribution of load and traffic on the two carriers by
means of idle mode makes it very unlikely that IFLS would be
triggered. Even so, IFLS could be useful in case instant power
peaks on f1 or f2 occur, as the fairly even distribution caused by
idle mode behavior might not be perfect. The share of all traffic
being re-directed between carriers will be very small. IFLS is to
be used within the whole cluster, both from the f1 to the f2 cells,
and in the opposite direction.
CPM and IFHO must only be possible from the border cells on
the second carrier. Thereby, CPM and IFHO usage is minimized.
Normally, there are very few possible IFHO spots within each
cluster, as both Ec/No and RSCP levels on both f1 and f2 drop
equally fast. Therefore, CPM and possible IFHOs usage within
the cluster should only be considered when obvious black-spots in
the f1/f2 coverage are present.
A higher qRxLevMin value must be applied in the exit cells in
order to prevent UEs from setting up connections close to the cell
borders. A level slightly higher than the CPM start level is to be
chosen.

Field experiences show that this setup has proven safe with very good
performance. HSDPA can be deployed on both f1 and f2 cells, or just f2 cells.

2 NEIGHBOR CELL LIST PLANNING

In the following discussion it is assumed that cells on different carriers are
collocated.

Following the 3GPP specifications, a UE can be required to monitor up to 32

intrafrequency cells in idle and connected mode. In other words the RNC is
limited to transferring information for this number of cells to the UE. The UE
is expected to measure the pilot strength or quality of these cells and report in
a certain amount of time whenever certain criteria are met. However, 3GPP
performance requirements for cells other than the ones requested by the RNC
are less strict. The time required to decode a cell in the monitored subset is
less than or equal to 800 ms while for a cell not in the monitored set it is 30
seconds.
 Thee cells which are either vallid or invalid neighbors buut which are nnot in the
listeed intrafrequeency subset arre called deteected set cellss. Cells whichh are valid
neigghbors but wh hich are not in
n the monitorred set are callled unmonitoored
neigghbors. Fortuunately, most UEs are capaable of measuuring and repoorting
thesse detected seet cells. Howeever, it is gennerally preferrred to avoid reeporting
for unmonitored cells to as larrge an extent as possible since the process of
add t active set via detected set is normallly much slow
ding a cell to the wer
commpared to usin ng the monitoored set.

2.1 Iniitial Neigh

hbor Plan
n
An initial neighb bor plan is preeferably creatted in a cell pplanning tool. The tool
pred dicts coveragge from which h neighbor rellations are gennerated. The selected
neig ghbors also need
n to be prio
oritized. The uuse of neighbbor prioritizattion also
mak kes it possiblee to generoussly allocate neeighbors whicch in turn is aan efficient
metthod of minim mizing the risk k of missing nneighbors. Inn most situatioons, the
p can be baased solely onn predictions. In complex urban
inittial neighbor plan
radiio environmeents it could be b necessary too make path lloss measurem ments to
servve as a compllement to pred dicted coveraage.

Celll planning too

ols also give the
t possibilityy of determinning priority bbetween
neig
ghbors either using an algoorithm or mannually with thhe coverage m map as
sho
own in Figure 0-6.

Figure 0-6: Priorritizing Neighb

bours
2.2 Prioritizing Neighbors
Primary neighbors are defined as the first tier of cells bordering the main cell,
cell A1 in the diagram above. Secondary neighbors are cells providing
coverage that border the primary neighbors. Configuring a large number of
neighbor relations can be a good method of limiting the risk of missing
neighbors. However a cell requiring more than 25 neighbors, primary and
secondary indicates that improvements to the cell plan should be considered.

A parameter SelectionPriority is set per neighbor relation and indicates the

priority of the cell for including in the monitored set. There is no priority
between different neighbors to different cells in the active set. When building
the monitored set cell list, select the neighbor with the highest priority from
each cell in the active set. This is repeated for the neighbors with the second
highest priority within each active set cell and so on. If a cell is already
included in the monitored set the algorithm moves on to the next neighbor
with the highest priority for the same active set cell.

Prioritisation of neighbor relations is a method of limiting the negative effects

of truncation. It gives the opportunity to limit or even remove the risk for
frequently used neighbors to become unmonitored without having to remove
other neighbors from the neighbor list. In this way all defined neighbors are
made available for detected set capable UEs. Another positive effect of using
prioritization of long neighbor lists is that the complete neighbor list can be
utilized in 2 way soft handover.

A configuration of 15 to 20 neighbors per cell will cause very few occasions

of unmonitored cells in the network assuming maxActiveSet = 3. From the
primary and secondary neighbors up to 15 most important neighbors are
selected and assigned a higher priority than the rest. What is important to
achieve is a prioritized group of the 15 most important neighbors. Further
prioritization within the group should not be necessary. By default the priority
is assigned in the order of which the neighbor relations are configured.

When MBMS service is activated, it is necessary to differentiate the 20 most

important neighbors. This is achieved by adding a middle priority group of
maximum 5 neighbors.

In certain situations the only way to ensure proper initial neighbor definitions
and prioritization is to measure the pilot channel coverage from all cells. As
soon as the sites have been deployed and the pilot channel activated, coverage
can be measured using a pilot scanner.

2.3 Inter-frequency Neighbors

The UE can measure on a maximum of 32 IF cells, and on a maximum of two
other non-used inter-frequencies. When an additional carrier is introduced in
clusters of co-located cells, the initial IF neighbor list for the additional cell
could be defined by copying the corresponding neighbor list from the co-
located underlaying cell and adding the co-located neighbor.
However, if the coverage for the IF cell deteriorates quickly and it is
important that the IFHO can be performed fast, then the IF neighbor lists
should be as short as possible. The time it takes for a UE to find a candidate IF
cell generally increases with longer neighbor cell lists, and keeping the list
short should generally lead to less time in compressed mode and better
retainability performance.

When a second carrier is deployed as a hotspot cell, two-way neighbor cell

relationships should be defined only between the underlaying f1 cell and the
overlaying f2 cell. One-way neighbor cell relationships are defined from the
f2 cell to all the surrounding f1 cells. The main benefits with this setup are the
elimination of IFHO from the surrounding f1 cell to the f2 cell, the decreased
risk of CPM starts in the f1 layer, and the shorter neighbor lists. With one-way
definitions, all surrounding f1 cells become blind to the f2 cell.

Note: One-way neighbor cell relationships should only be applied to inter-

frequency neighbor relations as described above. One-way neighbor cell
relationships should never de configured for intra-frequency neighbor
relations in the network.

It should also be noted that the P-CPICH power settings should initially be set
to the same values for the f2 cells as for the co-located f1 cells. The f2 to f2
neighbor lists for the second carrier cells could also initially be determined by
using the f1 neighbor lists for the corresponding co-located cells.

Two way relation

for Co-located
cells
One way relation

WCDMA f2

WCDMA f1 WCDMA f1 WCDMA f1

Figure 0-7: Inter-frequency Neighbor Single Cell

The same principles with neighbor lists and power settings are also valid for
carriers f3 and f4.

Two way relation

for Co-located
cells
One way relation

WCDMA f2 WCDMA f2
WCDMA f2 WCDMA f2

WCDMA f1 WCDMA f1 WCDMA f1

Figure 0-8: Inter-frequency Neighbor Multiple Cells

There are no main differences between adding a carrier to a single WCDMA

carrier system and adding a fourth carrier (f4) to a three WCDMA carrier
system. However no more than two of the three carriers should be defined as
neighbors in any case, since the UE should not support more than two other
frequencies according the 3GPP specifications. Mobility across four carriers
can still be achieved by making sure the non-used frequencies have IF
neighbors defined between each other. This will result in that all carriers can
be reached, but in some cases it takes two IFHO to go from one carrier to
another.
 A good rule-of-thumb is that no more than 16 inter-frequency neighbor per
additional WCDMA carrier should be defined for a cell in the general case.
This makes the inter-frequency neighbor planning more simple and prepared
for future possible three or four WCDMA carrier networks.

Two way relation for

Co-located cells

One way relation

WCDMA f3

WCDMA f2 WCDMA f2
WCDMA f2 WCDMA f2

WCDMA f1 WCDMA f1 WCDMA f1

Figure 0-9: Inter-frequency Third Carrier Neighbors

2.4 Inter radio access technology neighbors

Inter radio access technology and cell reselection function enables a UE to
move from WCDMA coverage to GSM coverage and vice versa. The IRAT
neighbor relation should be defined throughout the system to enable mobility
in idle mode. For dedicated mode IRAT mobility should be enabled on a case
by case basis. The maximum number of cells that can be included in the GSM
monitored subset is 32. Due to the risk of truncation it is recommended not to
exceed 16 IRAT neighbor relations per cell. A short neighbor list results in a
shorter measurement time in compressed mode.

Similar to inter-frequency neighbor relations being based on the intra-

frequency neighbor plan, it is recommended to create WCDMA to GSM
neighbor relations based on the existing GSM neighbor plan. The 15 highest
priority primary and secondary GSM neighbors are defined as IRAT
neighbors with the addition of the relation to the co-located GSM cell. Since
there is no neighbor prioritization in GSM, the GSM neighbors to be used as
IRAT neighbors are not determined as easily as in inter-frequency neighbor
planning. The criteria that determine the primary and secondary neighbors in
GSM are the same as for WCDMA. If available, neighbor performance
statistics from both networks are preferred over predicted coverage as input
for determining IRAT neighbors.
 All WCDMA ceells located on n the edge of W WCDMA covverage are coonsidered
as border
b cells. One
O way neig ghbor relationns are defined for all GSM only cells
outside the WCD DMA coverag ge area. This wwill minimizee the number of UEs
han
nding over or reselecting WCDMA
W at thhe edge of thee coverage off the
WCCDMA cells. All cells locaated inside thee WCDMA border cells arre
con
nsidered to be core cells. Two way neighhbor relationss are defined for all
WCCDMA co-loccated sites and d also for GSM M only sites tthat are totallly
imbbedded in WC CDMA coveraage.

If th
he WCDMA network has an a underlyingg GSM system m that is duall band it is
recoommended du ue to truncatio
on risk to usee only one tarrget GSM netw work. If
the GSM1800 is used as a cap pacity layer fo
for the GSM9000 or if GSM M1900 is
used as a capacitty layer to GS SM850 then thhe lower of thhe GSM bandds can be
used as targets. The
T benefit off this would bbe less neighbbors and still have the
samme GSM fallback coveragee. The neighboor relations frrom GSM to W WCDMA
shoould still be from both GSM M bands in orrder not to limmit the access and
utilization of WC CDMA coverrage

a dedicated indoor GSM1800 or 19000 exists they sshould be inclluded in

If any
the IRAT neighb bor list togeth
her with the G
GSM850/900 bband cells if tthey are
withhin the WCD DMA coveragee area. A systtem with morre than one W WCDMA
carrrier requires neighbor
n relattions betweenn each WCDM
MA carrier annd the
GSM M coverage layer.
l

Figure 0-10: Inte

er-frequency and
a IRAT for Dual Band

3 MULTIBAND OPE
ERATION
N ASPEC
CTS
Thee Multiband Support
S functiion enables thhe same mobiility supporteed between
diffferent frequen
ncy bands as between
b frequuencies withiin the same frrequency
ban
nd, with possib ble limitation
ns imposed byy UE capabiliities. Multibannd
Suppport will ensure that legaccy UEs and rooaming UEs w with UE capaabilities
thatt support overrlapping frequ
uency bands aare handled ccorrect.
 The two main scenarios for deployment of different frequency are WCDMA
1900 deployed with WCDMA 850 in the Americas, WCDMA 2100 deployed
with GSM 900 mainly in Europe and Asia.

From a deployment perspective there can be a difference in the Americas and

Europe/Asia in the sense of how load can be steered and biased. This is due to
that UEs/terminals supporting both WCDMA 1900 and WCDMA 850 are
more common compared with UEs supporting both WCDMA 2100 and
WCDMA 900. This is valid at least for the early stages of WCDMA 900
deployment.

In the early phases of the Europe/Asia scenario, a more aggressive traffic

steering towards WCDMA 900 can most likely be enforced since not all UEs
support WCDMA 900. Only UEs supporting WCDMA 900 will be able to
find their way or be guided by the network System Information broadcast or
Inter-frequency load sharing or handover. When UEs support for both
WCDMA 2100 and WCDMA 900 frequency bands are more common, more
balancing of idle mode camping and traffic steering must be done in order to
balance the carried traffic.

The need for enabling IRAT handover/cell change in the WCMDA cells is
less when deployed on the lower frequency bands such as WCDMA 850 and
WCDMA 900, given that WCDMA and GSM sites are more or less co-sited
in the area. This since the WCDMA 850/900 usually has the benefits of a
better coverage. In the case of WCDMA 850 and WCDMA 900, only
WCDMA cells on the very coverage border are clear candidates for IRAT
transitions.

3.1 IFLS (at RRC), HSDPA and Non-HSPA IFLS, LBHO and
multiband operation
For HSDPA and Non-HSPA IFLS function the UE capabilities are used
during band filtering so the UEs are only load shared between frequency
bands it supports.

In the case of IFLS (at RRC), redirections are done using RRC Connection
Reject, and the system does not have any information on UE capability at that
time.

If IFLS (at RRC) neighbors belonging to different frequency bands are

configured and the load condition is fulfilled, single-band UEs can be
redirected to an unsupported frequency band. The consequence would be a
roughly 1-sec delay in the call setup, i.e., the UE does not recognize the
UARFCN specified in the Frequency Info and waits out the "Wait time"
before attempting a second RRC Connection Request. If this is considered to
be a serious problem, one solution is to avoid defining IFLS neighbors
between cells operating in different bands and rely on idle mode cell
reselection to balance the load in those cells.
 Loaad based hand dover also wo orks in differeent frequency band, the samme band
filteering is used on
o UE capabiilities as in noormal inter-frrequency mobbility in
idlee mode and co onnected mod de. IF load baased handoverr uses the norrmal
neig ghboring relaations created by the activee set cells, so a UE will nott be
meaasuring on a frequency
f ban
nd it does nott support in coonnected modde.

Forr LBHO, the operator

o mustt make sure thhat the candiddate target cellls (IF or
GSM M) have sparre capacity to receive the looad based hanndover load, w when
actiivating the feaature, there iss no load checck made before the handovver
atteempt.

3.2 Mo
obility be
etween multiband cells
In the
t inter-frequ
uency mobilitty the UE suppport for the ddifferent frequuency
ban
nds come into play. The UE E will in idle mode filter w
what frequenccies it is
cap
pable of measuuring and in connected
c moode the RNC w will filter the bands
and
d only send th
he frequenciess that the UE supports baseed on the UE
cap
pabilities.

Theere is one settting that can be

b used whenn two WCDM MA carriers aree
ployed in diffeerent frequenccy bands, thiss in order to aallow both IF and IRAT
dep
han
ndovers depen nding on UE capabilities
c frrom the F2 ceell.

Figure 0-11: Mob

bility between
n Multiband C
Cells

By setting hoTyp pe to IF_Prefferred on F2 bborder cell, thhe UE capabillity will

deccide if IRAT oro IF handoveer will occur ffrom the F2 ccell. All UEs ccapable of
WCCDMA 900 will w perform IF FHO and the UEs not capaable of WCDM MA 900
willl instead perfform IRATHO O to the GSMM network.

Thee simple rule comes from that

t IFHO willl be attempteed if the neighhboring
list is not empty after the bandd filtering whhen hoType iss set to IF_Preeferred. If
the neighbor list is empty afteer band filterinng for the UE
E on F2 carrieer, then
connditions for IRRAT measurements will bee evaluated annd started if G GSM
neigghbor list is not
n empty and d that IRAT iss allowed for the particularr
UeR Rc/RAB statee.
 In the case of three WCDMA carriers with two of the carriers on 2100 MHz,
the band filtering will in normal configuration not come to an empty
neighboring list since 2100 MHz neighbors should be defined for load
balancing, IF compressed mode measurements will be started regardless of
UE capability setting.