LACE Process For Radio Network Planning

LACE process for Radio Network planning
1 © Nokia Siemens Networks LACE process for RNW planning / 11-DEC-2007

Link budget and Simulation
For internal use

2 © Nokia Siemens Networks Presentation / Author / Date
What is Link budget?
Link budget planning is part of the network planning process, which helps to
dimension the required coverage, capacity and quality of service requirement in
the network.
In Link budget, we can find the limitation of the system.

For example UMTS WCDMA macro cell coverage is uplink limited, because mobiles power level.
Downlink direction limits the available capacity of the cell, as BTS transmission power (typically 20-
40W) has to be divided to all users.
The objective of the link budget design is to calculate maximum cell size under given criteria:
•Type of service (data type and speed)

•Type of environment (terrain, building penetration)
•Behavior and type of mobile (speed, max power level)
•System configuration (BTS antennas, BTS power, cable losses, handover gain)
•Required coverage probability
and to match all of those to the required system coverage, capacity and quality needs with each area
and service.
For internal use

Link budget
The target of the link budget calculation is to estimate the maximum allowed path loss on
radio path from transmit antenna to receive antenna
• The minimum Eb/N0 (and BER/BLER) requirement is achieved with the maximum allowed
path loss and transmit power both in UL & DL
The maximum path loss can be used to calculate cell range “R”
Lpmax_UL
Lpmax_DL
R
For internal use
Link Budget Overview
POWER
LEVEL
Result
Output MDC gain

power
Losses
(Cable, Eb/N0
Combiner,…)
Path-
BS loss Load SHO Gain MS UE / Ec/I0 Processing
Antenna (Interferenc antenna body Gain
gain e margin) gain loss (de-spreading)
Input Categories
Hardware related System related
Capacity related Application related

For internal use
Power budget Calculations
Link budget
Chip rate 3840.00 DL data rate 12.20 The calculation is done for each service (bit
UL Data rate
UL Load
12.20
50%
DL load 80%
rate) separately
Voice 12.2 kbit/s, 3 km/h, Macro 4
The power budget can be used the
Uplink Downlink estimate link balance (UL vs. DL)
RECEIVING END BS MS
Thermal Noise Density dBm/Hz -174.0 -174.0 • Limiting direction in defined conditions
Receiver Noise Figure dB 3.0 8.0
Receiver Noise Density dBm/Hz -171.0 -166.0
Noise Power at receiver [NoW] dBm -105.1 -100.1
Reguired Eb/No dB 4.4 7.9
Soft handover MDC gain dB 0.0 1.0
Processing gain dB 25.0 25.0
Interference margin dB 3.0 7.0
Required Ec/Io at receiver dB -17.6 -11.1
Receiver Sensitivity
Cable loss
dBm
dB
-122.7
3.0
-111.2
0.0
Direction to look at the link
Benefit of using MHA
Body loss
dB
dB
3.0
n/a
n/a
3.0
budget table (Receiving End)
Antenna gain RX dBi 18.0 0.0
Soft handover gain dB 2.0 2.0
Fast fading margin dB 0.0 0.0
Isotropic power dBm -142.7 -110.2
TRANSMITTING END MS BS
Power per connection dBm 21.0 34.4
Cable loss dB 0.0 3.0
Body loss dB 3.0 n/a
Antenna gain TX
Peak EIRP
dBi
dBm
0.0
18.0
18.0
49.4
Direction to look at the link
Isotropic path loss dB 160.7 159.6 DL Limited! budget table (Transmitting
end)
For internal use
WCDMA Power budget
Data Rate in UL and DL depends on service,
Link budget
Chip rate 3840.00 DL data rate 12.20
can be asymmetric
UL Data rate 12.20 DL load 80%
UL Load 50%
Uplink Downlink
RECEIVING END BS MS
Thermal Noise Density dBm/Hz -174.0 -174.0
Receiver Noise Density
Noise Power at receiver [NoW]
dBm/Hz
dBm
-171.0
-105.1
-166.0
-100.1 Maximum Load needs to be defined
Reguired Eb/No
Soft handover MDC gain
dB
dB
4.4
0.0
7.9
1.0 for Dimensioning:
Processing gain
Interference margin
dB
dB
25.0
3.0
25.0
7.0
• should not exceed 70%
Required Ec/Io at receiver dB -17.6 -11.1 • should be at least 30% to avoid excessive
Receiver Sensitivity dBm -122.7 -111.2
Cable loss dB 3.0 0.0 cell breathing
Body loss
dB
dB
3.0
n/a
n/a
3.0
• typically higher in DL than in UL
Antenna gain TX dBi 0.0 18.0
Peak EIRP dBm 18.0 49.4
Isotropic path loss dB 160.7 159.6 DL Limited!
For internal use

WCDMA Power budget
Link budget
Thermal noise density:
UL Data rate 12.20 DL load 80% • Theoretical background noise density
Voice 12.2 kbit/s, 3 km/h, Macro
UL Load
4
50%
• Depends on temperature
• Thermal Noise density [dBm/Hz] is defined as:
Uplink Downlink
RECEIVING END BS MS
Thermal Noise Density
Receiver Noise Figure
dBm/Hz
dB
-174.0
3.0
-174.0
8.0 Thermal _ Noise _ Density  10 * Log (kT )
Reguired Eb/No dB 4.4 7.9 Where:
Processing gain
dB
dB
0.0
25.0
1.0
25.0
k is Boltzman's constant
Interference margin dB 3.0 7.0 T is the temperature in Kelvin
Receiver Sensitivity dBm -122.7 -111.2
Cable loss dB 3.0 0.0 in normal +20 C0 conditions the thermal noise
Body loss
dB
dB
3.0
n/a
n/a
3.0 density is -173.98 dBm/Hz
Isotropic power dBm -142.7 -110.2 Receiver Noise Figure:
TRANSMITTING END MS BS • Receiver performance measure;
Power per connection
Cable loss
dBm
dB
21.0
0.0
34.4
3.0
how much receiver decreases the
Body loss dB 3.0 n/a signal C/I
Peak EIRP dBm 18.0 49.4 • Requirement from specifications
for BTS and MS performance
For internal use
WCDMA Power budget
Receiver Noise Density [dBm/Hz]
Link budget • Receiver noise density is the sum of the thermal
Chip rate 3840.00
UL Data rate 12.20
DL data rate
DL load
12.20
80%
noise density and the receiver noise figure.
UL Load 50% • Thermal Noise density [dBm/Hz] + Receiver noise
figure [dB] = Receiver Noise Density [dBm/Hz]
Uplink Downlink In order to calculate the thermal Noise power of
RECEIVING END
Thermal Noise Density dBm/Hz
BS
-174.0
MS
-174.0 the receiver (the receiver noise floor without
dB
dBm/Hz
3.0
-171.0
8.0
-166.0 external interference) the receiver noise power is
Reguired Eb/No
dBm
dB
-105.1
4.4
-100.1
7.9
calculated at the WCDMA carrier bandwidth.(In this
Processing gain
dB
dB
0.0
25.0
1.0
25.0
case carrier bandwidth is 3.84 MHz
Cable loss
dBm
dB
-122.7
3.0
-111.2
0.0
receiver noise power [dBm] =
Body loss
dB
dB
3.0
n/a
n/a
3.0
=Receiver Noise Density [dBm/Hz] +
Antenna gain RX dBi 18.0 0.0 10log10(3.84*106)= =-170.98 + 65.84 = -105.14 dBm
Isotropic power dBm -142.7 -110.2 Required Eb/N0
Cable loss dB 0.0 3.0 Soft handover MDC gain
Isotropic path loss dB 160.7 159.6 DL Limited! Interference margin
For internal use

Required Eb/N0
When Eb/N0 is selected, it has to be known in which conditions it is defined (select closest Eb/N0 value to
the prevailing conditions if available)
• Service and bearer
– Bit rate, BER requirement, channel coding
• Radio channel
– Doppler spread (Mobile speed, frequency)
– Multipath, delay spread
• Receiver/connection configuration
– Handover situation
– Fast power control status
– Diversity configuration (antenna diversity, 2-port, 4-port)
Some corrections have to be done in the power budget in case the conditions do not correspond the
used Eb/N0
• Soft handover MDC gain
• Power control gain
• Fast fading margin
For internal use

Soft Handover MDC Gain – UL
Macro Diversity Combining (MDC) gain gives the Eb/N0

improvement in soft handover situation compared to
single link connection
In UL the MDC gain is 0 dB
• Significant amount of diversity gain already exist
– Soft Handover combining is done at RNC level by
using just selection combining (based on frame
selection)
– Softer Handover combining is done at the BTS by
using maximum ratio combining
– In Maximum Ratio combining each signal branch
is multiplied by a weight factor that is proportional
to the signal amplitude. That is, branches with
strong signal are further amplified, while weak
signals are attenuated.
For internal use

Soft Handover MDC Gain – DL
In DL there is some combining gain

(around 1dB) due to UE maximal ratio
combining
• soft and softer handovers included
– from MS point there is no difference
between soft and softer handover
• average is calculated over all the
connections taking into account the
average difference of the received signal
branches (and UE speed)
In edge of the cell a 3 – 4 dB MDC gain can
be seen on required DL Eb/N0 in SHO
situations compared to single link reception
• Combination of 2 – 3 signals
For internal use

Interference Margin
Interference margin is calculated from the UL/DL loading () values
• From set maximum planned load
"sensitivity" is decreased due to the network load (subscribers in the network) & in UL
indicates the loss in Power budget due to load.
IMargin =  10  Log10 1     dB

IMargin [dB]
20
10
3
1.25
25% 50% 75% 99% Load factor 

For internal use
WCDMA Power budget
Link budget
Chip rate 3840.00
UL Data rate 12.20
DL data rate
DL load
12.20
80% Required Signal power (Receiver sensitivity) is
Voice 12.2 kbit/s, 3 km/h, Macro
UL Load
4
50%
the required lowest signal strength that is needed for
that particular service and load.
RECEIVING END
Uplink
BS
Downlink
MS
Required signal power = Receiver Noise power +
Thermal Noise Density dBm/Hz -174.0 -174.0 required Ec/I0
dBm/Hz
dBm
-171.0
-105.1
-166.0
-100.1
Required Ec/Io at reciever = Required Eb/No-SHO MDC
Reguired Eb/No dB 4.4 7.9 gain – processing gain + interference margin
Required Ec/Io at receiver
dB
dBm
-17.6
-122.7
-11.1
-111.2
Cable Loss
Benefit of using MHA dB 3.0 n/a
Body loss dB n/a 3.0
Antenna gain RX dBi 18.0 0.0 Benefit of using MHA: The benefit achieved
Fast fading margin dB 0.0 0.0 by using MHA equals to the Receiver noise
figure improvement
For internal use

Cable loss
Cable loss is the sum of all signal losses

caused by the antenna line outside the
base station cabinet
• Jumper losses
• Feeder cable loss
• MHA insertion loss in DL when MHA is
used
– Typical 0.5 dB
For internal use

WCDMA Power budget
Link budget
UL Load 50%
Uplink Downlink
RECEIVING END BS MS
Reguired Eb/No dB 4.4 7.9
Interference margin
dB
dB
3.0
-17.6
7.0
-11.1
Body loss: this parameter describes the additional
Receiver Sensitivity dBm -122.7 -111.2 loss in power budget. The loss is usually used for
Cable loss dB 3.0 0.0 speech services where the UEs antenna is often
Body loss
dB
dB
3.0
n/a
n/a
3.0 shadowed by the user's head. For data services the
Antenna gain RX dBi 18.0 0.0 body loss can be set to 0dB, because in this case the
Fast fading margin dB 0.0 0.0 UE is normally not close to the body.
TRANSMITTING END
Power per connection dBm
MS
21.0
BS
34.4
Soft handover gain
Peak EIRP dBm 18.0 49.4 Fast fading margin
For internal use

Soft Handover Gain
(Gain Against Slow Fading)
Soft handover gain is the gain against

shadow fading. This is roughly the gain of
a handover algorithm, in which the best
BTS can always be chosen (based on
minimal transmission power of MS)
against a hard handover algorithm
based on geometrical distance.
• The gain is also dependent on whether

the user is outdoors, where the
likelihood of multiple servers is high, or
indoors where the radio channel tends
to be dominated by a much smaller
number of serving cells.
– For indoors users the
recommendation is to use smaller
SHO gain value
• Soft handover gain can be understood
also as reduction of Slow Fading
Margin
For internal use

Processing Gain
W
G p  dB  
R
Required Signal Power
because of the processing gain

the spread signal can be
below the thermal noise level
Eb/No= + 4 dB Processing
Eb/No= + 2 dB
Gain
Eb/No= + 1 dB
Noise level (ex. -105 dBm)
-9 dB NRT 384 kbps +10 dB
- 16 dB
RT 64 kbps +18 dB
- 21 dB
Voice 12.2 kbps +25 dB
For internal use

Fast fading margin
MS moving towards the cell edge

25
20
dB
15
10
0 0.5 1 1.5 2 2.5 3 3.5 4
20
10
dBm
0 Mobile transmission
-10
0 0.5 1 1.5 2 2.5 3 3.5 4
power starts hitting
1.5 its maximum value
1
0.5
0
Received quality
-0.5 degrades, more
0 0.5 1 1.5 2 2.5 3 3.5 4
15 frame errors
10 Eb/N0 target
dB
5
increases fast
0 0.5 1 1.5 2 2.5 3 3.5 4
Seconds
Fast fading margin is used as a correction factor for Eb/N0 at the cell edge, when the used Eb/N0 is defined with
fast power control
• At the cell edge the UE does not have enough power to follow the fast fading dips
For internal use
WCDMA Power budget
Link budget
UL Load 50%
Uplink Downlink
RECEIVING END BS MS
Thermal Noise Density dBm/Hz -174.0 -174.0 Isotropic power is the minimum power needed for
dB
dBm/Hz
3.0
-171.0
8.0
-166.0 certain service in order to fulfil the Eb/No
Reguired Eb/No
dBm
dB
-105.1
4.4
-100.1
7.9
requirement for that service
Interference margin
dB
dB
3.0
-17.6
7.0
-11.1
Isotropic power = Receiver sensitivity + cable loss - MHA
Receiver Sensitivity dBm -122.7 -111.2 benefit + body loss - antenna gain - soft handover gain +
Cable loss
dB
dB
3.0
3.0
0.0
n/a
+ fast fading margin
Body loss dB n/a 3.0
TRANSMITTING END
Power per connection dBm
MS
21.0
BS
34.4
Power per connection
For internal use

Power per connection (DL)
The maximum downlink transmit power for each connection is defined by the RNC admission
control functionality
• Vendor specific
In NSN RAN the maximum DL power depends on
• Connection bit rate
• Service Eb/N0 requirement (internal RNC info)
• CPICH transmit power and group of other RNC parameters
Actual available DL power depends on maximum total BTS TX power, DL traffic amount and
distribution over the cell (All users share same amplifier)
Example values with 2 W (33 dBm) CPICH power and default NSN RNC parameters
Service Type Speec CS PS Data

h Data
Downlink bit rate 12.2 64 64 128 384 kbps
Maximum transmit 34.2 37.2 37.2 40.0 40.0 dBm
power per
connection
For internal use
WCDMA Power budget
Link budget
UL Load 50%
Uplink Downlink
RECEIVING END BS MS
Reguired Eb/No
dBm
dB
-105.1
4.4
-100.1
7.9 Peak EIRP is the maximum transmitted power
Processing gain
dB
dB
0.0
25.0
1.0
25.0
after the antenna.
Receiver Sensitivity dBm -122.7 -111.2 Peak EIRP = power per connection - cable losses - body
Cable loss dB 3.0 0.0 loss + antenna gain
Benefit of using MHA dB 3.0 n/a
Body loss dB n/a 3.0 EIRP = Equivalent Isotropic Radiated Power
Fast fading margin dB 0.0 0.0 Isotropic path loss: Maximum path loss between
the transmitting and receiving antenna is calculated
TRANSMITTING END MS BS for UL and DL separately.
Antenna gain TX
Peak EIRP
dBi
dBm
0.0
18.0
18.0
49.4
Isotropic path loss UL = Peak EIRP - isotropic power
Based on Pathloss, we can find the Cell range by using Okumura Hata formula
For internal use
Simulation
For internal use

Approaches to 3G Radio Network Planning Simulation
There are two fundamental approaches to 3G radio network

planning
• Path loss based approach
– Can be done by 2G planning tools
– Results easy to interpret
• 3G simulation based approach
– Requires 3G planning tool
– Requires detailed input information
– Results large range of network performance information
For internal use

Path loss based 3G planning
Path loss based 3G planning is based on

• Path loss predictions
• Planning margin and threshold definitions
Path loss predictions can be done on 2G or 3G planning tool with
• 3G site candidate locations
• 3G site configuration (antenna type, antenna height, antenna tilt, antenna azimuth, feeder
type and feeder length )
• Propagation model
• Digital terrain map
Planning thresholds are based on
• Planned services and link budgets
• Planned coverage quality
• Area type information (buildings etc.)
For internal use

Path loss based 3G planning – Results
The result of path loss based 3G planning is

• Coverage maps per service and per area type
• Cell dominance areas
• Interference levels
Coverage
Dense Urban
Urban
Suburban
Rural
Specific service
For internal use

Simulation based 3G planning
The planned 3G network configuration can be analysed by simulation

• Static (Monte-Carlo) simulations – Supported by most 3G planning
tools (Netact Planner)
In static simulations users are placed randomly on the planning area based on traffic
distribution information (traffic layer) for each planned service
The radio link conditions are analysed for each user
• Required TX power (UL/DL) based in path loss predictions and
interference level  Coverage limitation?
• Radio interface load (UL/DL) is estimated for each cell  Capacity
limitation?
For internal use

Simulation based 3G planning – Results
Main benefit of 3G simulations is the relatively large quantity of

information which is generated
• Information is beneficial only if it is interpreted correctly
The main results from a 3G simulation are typically
• Service coverage
• Service probability
– Failure probability by failure causes
• System capacity
• Intercell interference
• Uplink and downlink transmit powers
• Uplink and downlink interference floors
For internal use

Simulation based 3G planning –Coverage probability
For internal use

Simulation based 3G planning – UL load
For internal use

LACE process overview and related tool
For internal use

LACE (Lightly Automated Commissioning Environment)
What is LACE?
LACE is a process for UMTS network planning and implementation. It helps the planner to
avoid mistakes that might occur during the implementation. It simplifies data verification and
hence improves the network performance .
Why LACE?
LACE helps the mass implementation easier, systemizes the process, and reduces cost
and time. •Data is prepared and verified before implementation.
The errors were detected before and after the
implementation phase.
•The integration is done site by site. Errors during implementation occur
due to lack of organized planning and there is no error detection process
in the datafill before and after implementation. • Suitable for the mass implementation, saves time,
cost-effective and minimizes the errors.
•Quality and network performance assurance.
Manual work process

LACE process
For internal use

LACE/RIC Concept
NSN PM: BTS SCF templates NSN
Delivered NE RAN engineer
PM/TM configuration
Customer NETWORK RF datafill RIC & INTEGRATION MANAGEMENT

objectives PLANNING and One place •Integration preparation work at OSS
,Frame CIQ in and set •Remote troubleshooting and NW expansion &
Agreemen & CIQ Agreed for verified
format parameters Configuration for WBTS/FTM
RF
Planning RNC and
Guidelines TRS CIQ SCF for
TRS in Agreed SCF for
RF
TRS COCO
SCF for parameters
format AXC/FTM parameters in RNC
in RNC
SCF for
NETWORK – 2G/3G RAN BTS
OSS
WBTS
RNC
Subcontracted
FIELD WORK site work
•Installation and Integration of WBTS and AXC/FTM

•RNC connection established
For internal use
Generic LACE-CIQ Process and shared responsibility
1. Customer agreed on CIQ template, process, objective, timeline

,naming convention and frame agreement
2. CIQ template is sent to customer as a reference for CIQ

preparation.
3. Prior to the site integration in the agreed duration, customer will

deliver the CIQ for integration. NSN network planning will verify the
CIQ.
4. NSN network planning notifies customer back if the CIQ is correct.

In case of missing data or inconsistency data that require input
from customer. CIQ will be sent back to customer for correction
5. Once CIQ is ready. NSN network planning will prepare the datafill,
coordinate with RIC for site integration
Note : This LACE –CIQ process is a generic version. However, it is

possible to change based on customer-NSN agreement
For internal use

Generic LACE–RIC Process and shared responsibility
1. NSN RF network planning verifies the CIQ and prepare the datafill
based on the CIQ.
2. Datafill contains parameters for each objects for integration.
3. NSN RF planning deliver CIQ and datafill to RIC on agreed format
4. In case of error occurred, CIQ and datafill will be sent back to

Network planning for correction
Note : This LACE –RIC process is a generic version. Transmission

planning is not covered today.
For internal use

Tools for support datafill preparation and integration
For LACE-CIQ process, In-house macro is used for CIQ/ datafill

checking
For LACE-RIC process. The tool that we can use are divided into two
parts.
1. Datafill conversion
Planeditor can be used for datafill conversion. It converts excel csv format
into XML format which compatible to the OSS version
2. Datafill implementation
Radio Access configuration tool (RAC) inside OSS can be used to import
XML plan from 1. into OSS and RNC
For internal use

NSN Plan Editor
•PlanEditor is NSN developped
tool for offline datafill
preparation and conversion. It
is helpful for datafill
preparation, file conversion
and data consistency check.
•2G/3G RF and Transmission

parameter dictionary is built-in
to this tool.
•Import file format can be both

CSV from excel or OSS XML
dump files. It is MS-Access
based tool.
•Planeditor version is updated

along with OSS version.
•Planeditor from version 4.5.5
onward is supported RAS05.1
For internal use

Radio Access configurator tool
In order to download the plan into the network. OSS has several applications to support this
task.
1. CM operations Manager
2. CM Editor
3. CM Analyser
CM operations manager is a main tool for downloading plan. However, CM Editor and CM
Analyzer are the complimentary tools which help the work of CM operations manager.
These tool are application under OSS configuration management
For internal use
CM operations Manager
•CM Operations Manager is used
for importing, exporting, and
viewing plans and templates,
comparing plans to the actual
configuration, and for exporting
actual configuration to the
network.
•It is also used for provisioning

and uploading network elements,
conducting tests on TRXs, and
for operation management. In
addition, rehosting the WCDMA
BTS sites is carried out in CM
Operations Manager.
For internal use

CM Editor
•CM Editor is a tool for editing and
creating radio network plans and
templates and for directly modifying the
actuals in the network. With CM Editor,
you can also create new managed
objects, and edit and mass edit
parameter values of managed objects.
CM Editor facilitates plan modification
by providing the functionality to create
and select user-configurable parameter
views.
•With CM Editor, you can edit all GSM

and WCDMA radio network parameters
that can be configured in Radio Access
Configurator (RAC).
•CM Editor and PlanEditor are different

tool. Plan Editor intention is for off-line
plan editing while CM Editor is for on-
line (in OSS) plan editor. Plan from
Plan Editor can be editted by CM Editor
inside OSS
For internal use

CM Analyzer
CM Analyser allows user to

check radio network parameters
and managed objects to ensure
that the parameters are defined
according to consistency rules
and that no essential information
is missing. User can check for
discrepancies both in the actual
configuration and in planned
configurations. When checking
planned configurations, the
operational network parameters
are taken into account as
needed to reflect the situation
that would exist in the network
after downloading the plan.
NSN provides a set of basic

consistency rules. You can also
create your own rules using an
external text or XML editor.
For internal use

Introduction of UMTS parameters and Database
structure
For internal use

Logical Structure of the RNC Database Objects
WANE WLCSE
RNC
WSG WSMLC
HOPG
COCO WBTS
HOPI
HOPS
FMCS ADJS
WCEL
FMCI ADJI
FMCG ADJG
For internal use
Managed Object types
RNC = Radio Network Controller COCO = Radio Network Connection

Configuration
WBTS = WCDMA Base Station
WCEL = WCDMA Cell WANE = WCDMA Authorized Network
ADJ = Adjacency for WCDMA cell WSG = WCDMA subscriber group
• ADJS = intra-frequency adjacency WLCSE = WCDMA Location service
• ADJI = inter-frequency adjacency entity
• ADJG = inter-system adjacency WSMLC = WCDMA Serving Mobile
Location Center
HOP = Handover Path
• HOPS, HOPI, HOPG
FMC = Frequency Measurement Control
FMCS, FMCI, FMCG
For internal use

RNC Object
•The logical object of the Radio Network Controller
•It can have up to 384 WBTS objects
•In the RNC object the following interfaces are defined: Iu-PS, Iu-CS and Iur
•The logical object are hierarchically related to each other, therefore it is not possible to create any
other object before RNC creation.
•RNC object are split into three objects which are RNC, RNC_AC (RNC parameter for Admission
Control) and RNC_PS (RNC parameter for Packet scheduling). Plan Editor seperate it due to its
function. However, once it is download into OSS. All parameters will be under RNC object
WANE WLCSE
RNC
WSG WSMLC
COCO WBTS HOPG
HOPI
HOPS
FMCS ADJS
WCEL
FMCI ADJI
FMCG ADJG
For internal use

WBTS Object
The logical object of the WCDMA Base Station (Node B). A WBTS can have up to 24
WCDMA cells and one COCO object.
WANE WLCSE
RNC
WSG WSMLC
COCO WBTS HOPG
HOPI
HOPS
FMCS ADJS
WCEL
FMCI ADJI
FMCG ADJG
For internal use

WCEL object
•The logical object of the WCDMA Cell is created to define the configuration of the
WCDMA Node B site. In one RNC database there can be 1152 WCELs.
•In planeditor, WCEL object are split into three objects which are WCEL,WCEL_AC
(WCEL parameters for Admission control) and WCEL_PS (WCEL parameters for packet
scheduling). These objects are used in PlanEditor. However ,inside the OSS, it is still
valid as one object which is WCEL.
WANE WLCSE
RNC
WSG WSMLC
COCO WBTS HOPG
HOPI
HOPS
FMCS ADJS
WCEL
FMCI ADJI
FMCG ADJG
For internal use

Handover Path
HOPx
The Handover Path object stores mainly cell reselection and Intra frequency HHO
parameters. One Hop can be related to several Adjacency objects.
The maximum number of HOPx objects within one category is 100.
• E.g. for different type of cells (urban, rural, macro/micro/pico)
HOP Types:
• HOPS — object for intra-frequency
Handover Path
• HOPI — object for inter-frequency WANE WLCSE
RNC
Handover Path WSG WSMLC
• HOPG — object for inter-system

Handover Path HOPG
COCO WBTS
HOPI
HOPS
FMCS ADJS
WCEL
FMCI ADJI
FMCG ADJG
For internal use

HOPx Level Parameters Not a complete list
Intra Frequency Inter Frequency Inter System

IntraFreqNcellHCSpriority InterFreqNcellHCSpriority GSMncellHCSpriority
IntraFreqNcellHCSthreshold InterFreqNcellHCSthreshold GSMncellHCSthreshold
IntraFreqNcellQqualMin InterFreqNcellQqualMin GSMncellQrxlevMin
IntraFreqNcellQrxlevMin InterFreqNcellQrxlevMin GSMncellPenaltyTime
IntraFreqNcellPenaltyTime InterFreqNcellPenaltyTime GSMncellQoffset1
IntraFreqNcellQoffset1 InterFreqNcellQoffset1 GSMncellTempOffset1
IntraFreqNcellQoffset2 InterFreqNcellQoffset2 HOPGId
IntraFreqNcellTempOffset1 InterFreqNcellTempOffset1
IntraFreqNcellTempOffset2 InterFreqNcellTempOffset2
EcNoAveragingWindow HOPIId
EnableInterRNCsho
EnableRRCRelease
HHOMarginAverageEcNo
HHOMarginPeakEcNo
ReleaseMarginAverageEcNo
ReleaseMarginPeakEcNo
HOPSId
Idle Mode Parameters
For internal use
49 © Nokia Siemens Networks Presentation / Author / Date Handover Parameters
Adjacencies
ADJx
Adjacencies for WCDMA cell refers to a handover relationship between two cells. They are
defined for neighbouring cells.
Adjacency Types:
• ADJS — object for intra-frequency Adjacency
• ADJI — object for inter-frequency Adjacency
• ADJG — object for inter-system Adjacency
WANE WLCSE
RNC
WSG WSMLC
There can be 31 intra frequency adjacencies

(ADJS), COCO WBTS HOPG
48 inter-frequency adjacencies (ADJI) and HOPI

32 inter-system adjacencies (ADJG) HOPS
FMCS ADJS
All together can not exceed 50 adjacencies. WCEL
FMCI ADJI
FMCG ADJG
Handover Path objects must be created
before ADJx can be used
For internal use
Adjacencies (ADJx) Not a complete list
Intra Frequency Inter Frequency Inter System

IntraFreqNcellCI InterFreqNcellCI GSMncellBandIndicator
IntraFreqNcellEcNoOffset InterFreqNcellLAC GSMncellBCC
IntraFreqNcellDERR InterFreqNcellTxPwrRACH GSMncellBCCH
IntraFreqNcellLAC InterFreqNcellMCC GSMncellCI
IntraFreqNcellTxPwrRACH InterFreqNcellMNC GSMncellLAC
IntraFreqNcellMCC InterFreqNcellMNCLength GSMncellTxPwrMaxRACH
IntraFreqNcellMNC NrtHopiIdentifier GSMncellMCC
IntraFreqNcellMNCLength InterFreqNcellScrCode GSMncellMNC
HSDPAHopsIdentifier InterFreqNcellRNCid GSMncellNCC
NrtHopsIdentifier InterFreqNcellRAC NrtHopgIdentifier
IntraFreqNcellScrCode RtHopiIdentifier RtHopgIdentifier
IntraFreqNcellRNCid InterFreqNcellTxDiv ADJGId
IntraFreqNcellRAC InterFreqNcellUARFCN
RtHopsIdentifier ADJIId
IntraFreqNcellTxDiv
ADJSId
For internal use

Adjacencies (ADJx) to HOPx
Every adjacency definition contains links to HOPx parameter

sets
• RtHopxIdentifier defines the HOPx (x = S, I, G) parameter set that is applied
– Idle mode cell-reselections
– RT bearer intra-frequency hard handovers
• NrtHopxIdentifier defines the HOPx (x = S, I, G) parameter set that is applied
– Connected mode cell-reselections (CELL_FACH, CELL_PCH, URA_PCH)
– NRT bearer intra-frequency hard handovers
• HSDPAHopsIdentifier defines the HOPS parameter set that is applied
– For user having HS-DSCH allocated
• RTWithHSDPAHopsIdentifier defines the HOPS parameter set that is applied
– For user having HS-DSCH allocated simultaneously with AMR speech CS
RAB
For internal use

Frequency Measurement Control
The FMC object contains information concerning the frequency measurement

functionality of the RNC.
The maximum number of frequency measurement control objects within one category is
100.
• E.g. for different type of cells (urban, rural, macro/micro/pico)
One FMC can be related to several WCDMA cells.
FMC Types:
• FMCS — object for intra-frequency WANE
Frequency Measurement Control WSG
RNC
WLCSE
WSMLC
• FMCI — object for inter-frequency

COCO WBTS HOPG
• FMCG — object for inter-system
HOPI
HOPS
FMCS ADJS
WCEL
FMCI ADJI
FMCG ADJG
For internal use

Threshold & Trigger
Example FMCX Level Parameters Handover Cause
ActiveSetWeightingCoefficient IFHOcauseCPICHEcNo GSMcauseCPICHEcNo
AdditionReportingInterval IFHOcauseCPICHrscp GSMcauseCPICHrscp
AdditionTime IFHOcauseTxPwrDL GSMcauseTxPwrDL
AdditionWindow IFHOcauseTxPwrUL GSMcauseTxPwrUL
EcNoFilterCoefficient IFHOcauseUplinkQuality GSMcauseUplinkQuality
DropTime InterFreqDLTxPwrThrAMR GsmDLTxPwrThrAMR
DropWindow InterFreqDLTxPwrThrCS GsmDLTxPwrThrCS
MaxActiveSetSize InterFreqDLTxPwrThrNrtPS GsmDLTxPwrThrNrtPS
ReplacementReportingInterval InterFreqDLTxPwrThrRtPS GsmDLTxPwrThrRtPS
ReplacementTime InterFreqMaxMeasPeriod GsmMaxMeasPeriod
ReplacementWindow InterFreqMeasAveWindow GsmMeasAveWindow
HHoEcNoCancel InterFreqMeasRepInterval GsmMeasRepInterval
HHoEcNoCancelTime InterFreqMinHoInterval GsmMinHoInterval
HHoEcNoThreshold InterFreqMinMeasInterval GsmMinMeasInterval
HHoEcNoTimeHysteresis InterFreqNcellSearchPeriod GsmNcellSearchPeriod
HHoRscpCancel InterFreqUETxPwrFilterCoeff GsmUETxPwrFilterCoeff
HHoRscpCancelTime InterFreqUETxPwrThrAMR GsmUETxPwrThrAMR
HHoRscpFilterCoefficient InterFreqUETxPwrThrCS GsmUETxPwrThrCS
HHoRscpThreshold InterFreqUETxPwrThrNrtPS GsmUETxPwrThrNrtPS
HHoRscpTimeHysteresis InterFreqUETxPwrThrRtPS GsmUETxPwrThrRtPS
IMSIbasedSHO InterFreqUETxPwrTimeHyst GsmUETxPwrTimeHyst
FMCSId FMCIId FMCGId
For internal use
Not a complete list
WCEL to FMCx
Every WCEL definition contains links to 12 FMCx parameter sets

• RtFmcxIdentifier (x = S, I, G) defines the FMCx parameter set that is applied for
radio links with RT bearers
• NrtFmcxIdentifier (x = S, I, G) defines the FMCx parameter set that is applied for
radio links with only NRT bearers
• HSDPAFmcxIdentifier (x = S, I, G) defines the FMCx parameter set controlling
measurements of a user having HS-DSCH allocated
• RTWithHSDPAFmcxIdentifier (x = S, I, G) defines the FMCx parameter set
controlling measurements of a user having HS-DSCH allocated simultaneously
with AMR speech CS RAB
For internal use

Connection Configuration
COCO
A new logical COCO object is created in order to reserve local

transmission resources for the WCDMA BTS.
The COCO objects display the transmission resources in the Iub
interface, but not the actual network topology
There can be up to 400 COCO objects RNC
WANE WLCSE
in the RNW database WSG WSMLC
COCO WBTS HOPG
HOPI
HOPS
FMCS ADJS
WCEL
FMCI ADJI
FMCG ADJG
For internal use

WANE & WSG Objects
IMSI BASED HO
WANE & WSG MO groups are for the IMSI Based HO

WANE set contain PLMN id where UE is allowed to make handover.
WSG object should be created to every subscriber (PLMN id) visiting in network and it maps
subscriber (PLMN id) to certain WANE sets
These two objects are not used if IMSI Based HO is not required.
WANE-WCDMA Authorised WSG-WCDMA subscriber

Networks Parameters group Parameters
AuthorisedNetworkId GSMRoaming
AuthorisedNetworkList HomePLMN
AuthorizedNetwork PLMN HomePLMNMCC
AuthorizedNetworkMCC HomePLMNMNC
AuthorizedNetworkMNC HomePLMNMNCLenght
AuthorizedNetworkMNCLengh OperatorName
Technology SubscriberGroupid
WANEChangeOriging WSGAuthorisedNetworkId
WANEName WSGChangeOriging
For internal use

WSMLC & WLCSE objects
LOCATION BASED SERVICE
WSMLC & WLCSE object groups are for Location based service. LCS is
RAN04 feature
WSMLC-WCDMA Serving Mobile Location Center, represents a logical object
with RNC specific mobile location center parameters
WLCSE-WCDMA Location service entity, represent a logical object with WCEL
specific location parameters
WSMLC-WCDMA Serving WLCSE-WCDMA

Mobile Location Center Location Service Entity
ConfAreaLevel AntennaBearing
RNCDelayTolRespTime AntHPBW
RNCLowDelayResponseTime AntennaCoord
WSMLCChangeOrigin CovType
WSMLCid EnvCharact
MaxCellBackRad
MaxCellRad
RepeaterExist
WLCSEChangeOrigin
WLCSEUtranCellId
WLCSEid
For internal use

Summary
NrtHopsIdentifier = 1
RtHopsIdentifier = 2
WCEL HSDPAHopsIdentifier = 6 HOPS HOPSid = 1
(NRT)
ADJS HOPS
HOPSid = 2
(RT)
WBTS WCEL
ADJSid = 1 HOPS
HOPSid = 6
(HSDPA)
NrtFmcsIdentifier = 3
Each ADJS has associated 1 HOPS for NRT &
RtFmcsIdentifier = 40 WCEL 1 for RT & 1 for HSDPA, sets can be reused
HSDPAFmcsIdentifier = 50 for other cells.)
FMCSid = 1 FMCS HOPS HOPSid = 1

(NRT) (NRT)
Each WCEL has
associated 1 FMCS FMCSid = 1 FMCS HOPS
ADJS HOPSid = 5
for NRT & 1 for RT (RT) (RT)
& 2 for HSDPA, all
can be reused for FMCSid = 2 FMCS
other cells. HOPS
(HSDPA) ADJSid = 2
(HSDPA) HOPSid = 7
FMCSid = 2 FMCS
For internal use (RT&HSDPA)
Parameter Group
• The parameters are also grouped by RRM functionality. This

grouping is used in parameter dictionary.
• Telecom Parameters
• PCConfiguration = Power control Radio
• HCConfiguration = Handover control Resource
• ACConfiguration = Admission control Management
• LCConfiguration =Load control (Congestion control) (RRM)
• PSParameters = Packet scheduling
Functionality
• Identification = Identification of the network element
For internal use

Parameter Group explanation
Admission control (AC)
Performs the admission control for new bearers to enter the network.
Predicts interference caused by the bearer and checks whether there is ‘room’ for it.
Power allocation
Defines transport channel parameters
Packet Scheduler (PS) incl. HSDPA

Scheduling packets on the radio interface (UL/DL)
Ensures fast allocation of resources for NRT users
New high-speed scheduling on MAC-layer ensures improved cell and user performance
(Throughput, RTT)
• Link adaptation by processing UE quality and channel information feedback
• Fast Scheduling algorithm (2ms) ensures optimal resources allocation based on UE channel
quality
Load Control (LC)
Takes care of radio network stability
Gathers interference information and provides cell load status to AC & PS
For internal use

RRM – Connection Based Functions
Power Control (PC)

Continuously monitors the quality of the radio link and adjusts MS, BTS powers
Ensures absolute minimum Tx power is used to maintain required quality
Can be divided into;
• Closed loop PC
• Open loop PC
• Outer loop PC (new, compared to GSM)
Handover Control (HC)
Manages the mobility of the users
Ensures MS is connected to the optimal cell(s) > minimising interference
Can be divided into;
• Intra-frequency handovers
• Inter-frequency (hard) handovers
• Inter-system handovers
For internal use

Parameter Dictionary
Example
List of parameters can be found in

NOLS ,in this RF package and in
the default parameter sheet.
https://www.online.nokia.com/nols/do
ccenter/dcpageflow/viewDocumentD
etails.do?
parentObjectId=0b00cc92800c4bfa
For internal use

Parameter management - Overview
Radio network parameters are managed via Netact OSS or directly

via Element Manager functionality
Usage of Netact plan RNC Element
Netact RAC tools
edit, analysis and Manager
activation tools Netact
recommended Database
Re
ad
o nl
yr
Recommended
i gh
ts
RNW
Database
For internal use

GUI example -General
For internal use

WCEL –FMCx mapping
For internal use

GUI examples -HOPS
For internal use

WCEL- ADJS
For internal use

Radio Network Controller (=RNC):
With RNC capacity step 5
384 Maximum WBTS objects can be created.
1152 Maximum WCELL objects can be created.
400 Maximum COCO objects can be created.
Maximum 100 FMCx could be created for each category
Maximum 100 HOPx could be created for each category
WCDMA Base Station (=WBTS):

One BTS can have up to 24 WCELL and 1 COCO
WCDMA Cell (=WCEL):

Maximum ADJS per WCEL : 31 (id1… 31)
Maximum ADJG per WCELL: 32
Maximum ADJI per WCELL: 48 (max 32 per frequency)
For internal use

Explanation of CIQ template sheet
and default parameters concept
For internal use

CIQ template (Customer Integration Questionaire)
Why do we need CIQ template?

Due to the complexity of the RF parameters, it is difficult to define every single
parameters. In order to simplify it, Concept of CIQ template is introduced.
CIQ template
There are 3 types of CIQ template.
1. RNC CIQ - contain the information for RNC integration
2. Node B CIQ – contain information for Iub interface and ATM for
transmission integration
3. RF CIQ- contain the RNW parameters and NodeB hardware and
features information which are required for site integration.
* The scope of this document is to cover RF CIQ only
For internal use

What is inside the RF CIQ template?
RF CIQ template consists of :
1. SCF-Flexi : contain BTS parameters which are required for SCF files
2. Plan1 : contains the RNW parameters
3. Plan2 : Network Element information (such as RNC,MSC and SGSN)
4. Plan3 : Iub interface parameters for each NodeB
5. Plan4 : RNC neighbour relationship
6. ADJS : Intra frequency adjacencies
7. ADJI : Inter frequency adjacencies
8. ADJG : UMTS->GSM adjacencies
9. BSC(2G) : BSC parameters which related to Intersystem handover
10. BTS(2G) : BTS parameters which related to Intersystem handover
11. HOC(2G) : Handover control which related to intersystem handover
12. ADJW : GSM-> UTMS adjacencies
13. WSMLC : WCDMA Location service entity information
14. Cell Info for Non-NSN 2G : Information of a GSM cell that is not managed by this management
system. For example, it can be a cell implemented by third-party network elements and
managed by its own management system.
15. Cell Info for Non-NSN 3G : Information of a WCDMA cell that is not managed by this
management system. For example, it can be a cell implemented by third-party network elements
and managed by its own management system.
For internal use

Example of CIQ
Plan1 (Site information)

• Plan1 contains the site
information. The input from
plan1 is used to create these
following output:
1. Datafill for all objects

• Plan1 needs to be verified
and correct the mistakes first
in order to avoid the
mistakes in the datafill.
Plan1 will be verified by
NSN engineer before
implementation
For internal use

What is in CIQ?
Plan2 (Interface information)

• This plan contains the data for IUR,IU-CS,IU-PS interfaces
• If transmission integration is done by NSN. No need to provide this sheet.
Plan3
• Contain the Transmission data (IUB) of the sites. Data from plan3 can be obtained from RNC and
node B CIQ, If Flexi transmission plan prepares by NSN. No need to fill this sheet.
For internal use

What is in CIQ?
Plan4 : contain the RNC and NRNC relationship. The example is

shown below.
Detail Explanation about each parameters under CIQ. Please refer to RF CIQ document.
For internal use

Default Parameters and parameter checking concept
For internal use

Parameter checking concept
CIQ
LACE Datafill CSV files

LACE parameter
preparation checking
Errors
If Yes,correct it Reports
and check again
NSN Default
parameters
Datafill
has
errors?
No error! Sending to RIC
For internal use

NSN default Parameter concept
Data from the actual network
(E.g RNC id,name ,2G ADJ cell id,2G
ADJ related parameter) needs to be
verified.
Run parameter checking

macro to verified the
Fixed – Copy value to the datafill correctness at the final
stage.
User– User defined parameter. Need to check RNW datafill

range or name convention before assign it to
Default the datafill. in
paramet Agreed
er rules Condition – Some parameter is depend on format
other parameters.In this case, there is (CSV or excel)
condition for the parameter value. Need to
check that all parameters are correspond with
the condition or not.
Final
RNW RIC
datafill
Plan 1-4
Plan - Make sure that the parameters
which retrieve from Pan1-4 are correct.
For internal use

Default parameters set
In this section, the concept of parameter checking will be discussed. The “default
parameter rules” file is very important in this phase. Planner can use this
document during planning process as a guide. This document contains all
parameters with the pre-caution of some parameters which planner needs to pay
extra attention on it. Also there are a list of fixed value parameter which we will
use it as a default in the network.
During the parameter checking, there are 7 kinds of parameter checking as
following.
Fixed The parameter value must not be blank and must be the same as
default parameter
User User defined parameter. Range check must be done with this item.
Condition Condition rule including rules related to other tables or other
parameters.
Plan1 Check this parameter according to Plan1
More detail for each parameter type can be found in the

default parameter rule file.
For internal use
Q&A
Thank you!
For internal use


LACE Process For Radio Network Planning

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

LACE Process For Radio Network Planning

Загружено:

Авторское право:

Доступные форматы

LACE process for Radio Network planning

1 © Nokia Siemens Networks LACE process for RNW planning / 11-DEC-2007

For internal use

In Link budget, we can find the limitation of the system.

•Type of service (data type and speed)

For internal use

Output MDC gain

Hardware related System related

Capacity related Application related

For internal use

For internal use

For internal use

Macro Diversity Combining (MDC) gain gives the Eb/N0

For internal use

In DL there is some combining gain

For internal use

IMargin =  10  Log10 1     dB

25% 50% 75% 99% Load factor 

For internal use

Cable loss is the sum of all signal losses

For internal use

For internal use

Soft handover gain is the gain against

• The gain is also dependent on whether

For internal use

because of the processing gain

-9 dB NRT 384 kbps +10 dB

For internal use

MS moving towards the cell edge

For internal use

Service Type Speec CS PS Data

For internal use

There are two fundamental approaches to 3G radio network

For internal use

Path loss based 3G planning is based on

For internal use

The result of path loss based 3G planning is

For internal use

The planned 3G network configuration can be analysed by simulation

For internal use

Main benefit of 3G simulations is the relatively large quantity of

For internal use

For internal use

For internal use

For internal use

•Quality and network performance assurance.

Manual work process

For internal use

Customer NETWORK RF datafill RIC & INTEGRATION MANAGEMENT

•Installation and Integration of WBTS and AXC/FTM

1. Customer agreed on CIQ template, process, objective, timeline

2. CIQ template is sent to customer as a reference for CIQ

3. Prior to the site integration in the agreed duration, customer will

4. NSN network planning notifies customer back if the CIQ is correct.

Note : This LACE –CIQ process is a generic version. However, it is

For internal use

2. Datafill contains parameters for each objects for integration.

3. NSN RF planning deliver CIQ and datafill to RIC on agreed format

4. In case of error occurred, CIQ and datafill will be sent back to

Note : This LACE –RIC process is a generic version. Transmission

For internal use

For LACE-CIQ process, In-house macro is used for CIQ/ datafill

For internal use