Recommended NSN Parameters for 3G Planning with MultiRadio Planner Kimmo Mäkeläinen (GS MS NPO Tools Mgmt & Support) RU10 Dimensioning Workshop 21-25 April 2008, Jakarta
For internal use
Parameter Set for 3G Planning A set of recommended parameter values that should be used in planning of UMTS FDD networks with NetAct Planner (version 5.2.1 or later) has been prepared. Version 2.0 of parameter set is available in IMS at: https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/372999100
Only UMTS FDD (at WCDMA 2100 band) are covered: •
UMTS TDD is not covered;
•
other UMTS bands (e.g. 850 MHz) of UMTS FDD are also included into documentation – but not into XML import files.
Only radio network planning with MultiRadio Planner will be described; the parameter set does not cover Link Planner or Transmission Planner. For internal use
Which Parameters Are Included? The complete database of Planner is not documented, and the list of described NetAct Planner parameters is by no means comprehensive. Only parameters that are: •
required for Monte Carlo simulation, and
•
included in XML import/export files of Planner
are included. Hence, parameters: •
stored into Planner database just for the sake of export to the network, or
•
related to neighbour planning or scrambling code planning
are not covered. For internal use
Parameters Provide a Recommended Starting Point The parameters of NetAct Planner are user-editable on purpose: ► A single
correct set of parameters that would be applicable to all projects does not exist.
In different networks and different conditions parameter values must be adjusted. The recommended values provide only a starting point that should be carefully judged in each new planning project!
For internal use
Modularity 1/2 The structure of the set of XML import files is modular . The set will consist of: •
a generic UMTS set,
•
sets for new 3G technologies (e.g. HSDPA),
•
BS-dependent set.
Other sets will be imported (or overlaid) on top of the generic UMTS package. The generic UMTS import file set will always be used with any hardware configuration. BS-dependent parameters further add parameters for Node Bs and cells that depend on the type of base station. For internal use
Modularity 2/2
set for BS1 HSDPA set set for BS2 Generic UMTS set set for BS3 HSUPA set
... set for BSn
For internal use
Modularity at Level of XML Import Files Division into generic parameters and BS-dependent parameters is made at the level of XML import files. Generic UMTS set
HSDPA-specific set
BS-dependent set
BEARERS-LIST001.xml
BEARERS-LIST001.xml
ANTENNA-LIST001.xml
CARRIER-UMTS-LIST001.xml
HSDPA-LIST001.xml
CELLULAR-CONN-LIST001.xml
CLUTTER-PARAMETERS-LIST001.xml
FEEDER-LIST001.xml
MODEL-LIST001.xml
MAST-HEAD-AMPLIFIER-LIST001.xml
SERVICES-LIST001.xml
SERVICES-LIST001.xml
NETWORK-LIST001.xml
TERMINAL-TYPES-LIST001.xml
TERMINAL-TYPES-LIST001.xml
NODEB-LIST001.xml
UMTS-RESOURCE-LIST001.xml
UMTS-RESOURCE-LIST001.xml
NODEB-TYPE-LIST001.xml PROPERTY-LIST001.xml
XML files are independent of Planner database version. The XML files have been prepared for Planner version 5.2.1, but they can be imported also to any newer version (e.g. to Planner 6.0).
For internal use
RNC-LIST001.xml SGSN-LIST001.xml UMTS-CELL-LIST001.xml UMTS-RESOURCE-LIST001.xml
Generic Parameters Generic Parameters for 3G Planning (excluding HSDPA)
Clutter Parameters (shadow fading, indoor loss and orthogonality) Propagation Model Carriers Resources Bearers -
bit rates control overhead factors Eb/No requirements power control and soft handover parameters
Services Terminal Types -
traffic spreading speed distribution services WCDMA parameters
Generic Parameters for HSDPA Planning
For internal use
Resources HSDPA Coding Rates Bearers Services Terminal Types
BS-dependent Parameters • Antennas • Node
B Types • Node Bs (Flexi and Ultra configurations) –
Antenna Configuration – Carriers – Resources • UMTS Cells – General Parameters Antenna Configuration (with dummy antenna) – – Cell Parameters – Resources • HSDPA
Node B Configurations • ROC Configurations
For internal use
9 Flexi and 4 Ultra BS Configurations 1/3 The recommended Node B and cell parameters contain 13 different (RU10) Node B configurations: ▪ Flexi 20 W 1+1+1 ▪ Flexi 20 W 2+2+2 ▪ Flexi 20 W 3+3+3 ▪ Flexi 20 W 4+4+4
Max. transmit powers 8, 30 or 60 W of Flexi BSs are not covered.
▪ Flexi 20 W 1+1+1+1+1+1 ▪
Flexi 20 W 2+2+2+2+2+2
▪ Flexi 40 W 1+1+1 ▪ Flexi 40 W 2+2+2 ▪ Flexi 40 W 1+1+1+1+1+1 ▪ Ultra 20 W 1+1+1 ▪
Ultra 20 W 2+2+2
▪ Ultra 40 W 1+1+1 ▪ Ultra 40 W 2+2+2
For internal use
No 1-cell or 2-cell configurations have been specified, but it is easy to modify one of the 3-cell Node Bs to use only one or two cells.
9 Flexi and 4 Ultra BS Configurations 2/3 The different Node B configurations for Flexi and Ultra base stations differ in the maximum transmit power, number of sectors, number of carriers and noise figure. Otherwise the parameters of all Node Bs are identical. Node B configuration
For internal use
Carriers
Sectors
Antenna azimuths [°]
Flexi 20 W 1+1+1
1
3
0:120:240
Flexi 20 W 2+2+2
2
3
0:120:240
Flexi 20 W 3+3+3
3
3
0:120:240
Flexi 20 W 4+4+4
4
3
0:120:240
Flexi 20 W 1+1+1+1+1+1
1
6
0:60:300
Flexi 20 W 2+2+2+2+2+2
2
6
0:60:300
Flexi 40 W 1+1+1
1
3
0:120:240
Flexi 40 W 2+2+2
2
3
0:120:240
Flexi 40 W 1+1+1+1+1+1
1
6
0:60:300
Ultra 20 W 1+1+1
1
3
0:120:240
Ultra 20 W 2+2+2
2
3
0:120:240
Ultra 40 W 1+1+1
1
3
0:120:240
Ultra 40 W 2+2+2
2
3
0:120:240
9 Flexi and 4 Ultra BS Configurations 3/3 The only cell-level parameters that are differing between Node B configurations are the assigned carrier, max. Tx power, pilot power and noise figure. Node B configuration
Assigned carrier
Max Tx power [dBm]
Pilot power [dBm]
Noise figure [dB]
Flexi 20 W 1+1+1
1
43
33
2.0
Flexi 20 W 2+2+2
1-2
43
33
2.0
Flexi 20 W 3+3+3
1-3
43
33
2.0
Flexi 20 W 4+4+4
1-4
43
33
2.0
Flexi 20 W 1+1+1+1+1+1
1
43
33
2.0
Flexi 20 W 2+2+2+2+2+2
1-2
43
33
2.0
Flexi 40 W 1+1+1
1
46
36
2.0
Flexi 40 W 2+2+2
1-2
46
36
2.0
Flexi 40 W 1+1+1+1+1+1
1
46
36
2.0
Ultra 20 W 1+1+1
1
43
33
3.0
Ultra 20 W 2+2+2
1-2
43
33
3.0
Ultra 40 W 1+1+1
1
46
36
3.0
Ultra 40 W 2+2+2
1-2
46
36
3.0
For internal use
Usage of the XML Import Files The document NSN Parameters for 3G Planning with NetAct Planner (5.2) also includes step-by-step instructions for importing the XML parameter sets: ... 2. Start NetAct Planner and add a completely new empty project. Set up appropriate coordinate system, map data directories, user data directories and map data extents for the new project according to guidelines and digital map of your local planning project. Then start the new project.
5. Import the BS- dependent XML set (by selecting the INDEX001.xml file). Select all possible data to be imported under the Project and Config tabs of the import dialog. Select to replace data during import, and run Database | Global Commit All after finishing import.
3. Import the complete generic XML set (by selecting the INDEX001.xml file) from File | Import | XML. Select all possible data to be imported under the Config tab of the import dialog. Select to replace data during im port, and run Data¬base | Global Commit All after finishing import.
6. Since the clutter types are different in each digital map, all dependencies of map clutter types have to edited manually to correspond to the clutter categories that are used in your digital map. The XML files do not contain any parameters that depend on clutter types. You can check the clutter types of your map by looking the file menu.txt in the clutter directory of the map. The clutter-dependent parameters are critical, and they absolutely must be edited before Monte Carlo simulation is possible.
4.1. The XML import for HSDPA configuration is not working properly in NetAct Planner (ver. 5.2.1): It is not possible to import the complete HSDPA-specific XML set, if the HSDPA coding rates have not been defined before this. Hence, if HSDPA support is required for the network, im port first the single file HSDPA-LIST001.xml from the HSDPA-specific XML set, and run Database | Global Commit All aft er finishing import. 4.2. Then, import the complete HSDPA-specific XML set (by selecting the INDEX001.xml file). Select all possible data to be imported under the Config tab of the import dialog. Select again to replace data during import, and run Database | Global Commit All after finishing import. Note that the Node B configurations in the XML import set are by default not supporting HSDPA, and that HSDPA must be enabled separately in each cell (see Section 6.5) before simulation.
For internal use
Define manually the clutter parameters (under Configuration | Clutter Parameters | 3g menu), the clutter type corrections f or Nokia Propagation Model (under Morpho tab in the C onfiguration | Propagation models | Models dialog), traffic spreading by clutter for all terminal types (under the Clutter tab of the Configuration | Terminal Types dialog), and speed distribution of all terminal types (under the Mobile Speed tab of the Configuration | Terminal Types dialog). 7. Change the assignment of carriers to services and the priorities among carriers according to the local project requirements. ...
Thank you for your attention.
For internal use
