w radio network planning guide 20090324 a 3.51

WCDMA Radio Network Planning Design Guide Internal Open

Product name Confidentiality level

WCDMA RNP For internal use only

Product versionTotal 156 pages

3.51

WCDMA Radio Network Planning Guide

(For internal use only)

Prepared by Yang Shijie Date 2006-02-20

Reviewed by Date

Reviewed by Date

Approved by Date

Huawei Technologies Co., Ltd.All Rights Reserved

Revision Records

2008-12-17 All rights reserved Page1 , Total162


Date Version Description Author

2006-02-20 1.00 Initial transmittal. Yang Shijie

2006-03-03 1.01 Modified the flow for network planning design. Removed the content concerning digital maps and repeaters.

Yang Shijie

2006-03-13 1.02 Modified the flow chart for network planning design and updated its description for consistency.

Supplemented the configuration of LCS parameters.

Yang Shijie

2006-03-16 1.03 Moved the template for information collection and configuration of simulation parameters into the appendix.

Supplemented the configuration of cell access radius parameters.

Embedded Visio files of figures in the body into appendix.

Yang Shijie

2006-05-09 1.04 Added content related to HSDPA.

Modified RNC area planning, location area planning, and routing area planning.

Filled recommended values in the blanks in tables.

Supplemented TCell parameter planning.

Supplemented PLMN tag parameter planning.

Yang Shijie

2006-6-12 1.05 Supplemented HSDPA to part of network design load.

Supplemented diagrams of HSDPA simulation result.

Added the description of CEs used by HSDPA.

Update the traffic per subscriber in busy hour with HSDPA.

Yang Shijie

2006-7-19 1.06 Supplemented the instruction for configuring the search radius of HSPDA cell.

Supplemented the impact from magnetic declination on network planning.

Modified the summary part.

Yang Shijie

2006-9-1 1.07 Supplemented the flow for making network planning parameters.

Yang Shijie

2007-4-25 1.08 Modify scrambling code planning principle Yang Shijie

2007-5-24 1.09 Modify example of PLMN tag planning

Modify paging area planning principle to provide LA size estimation

Yang Shijie

2008-12-17 2.0 Added contents about HSUPA, MBMS

Added description of RNP&RNO tools SCP and CAN

Jin Yu

2009-3-24 3.51 Added the chapter “Tcell parameters palnning”, added the suggestion of Tcell configuration in different cell in same sector for multi-Carrier.

Xiezhibin



Contents

1 Introduction................................................................................15

2 Flow for WCDMA RNP Design........................................................16

3 Information Collection..................................................................18

3.1 Information Classification...............................................................................................................................18

3.1.1 Contract Requests...................................................................................................................................18

3.1.2 Information About Target Areas.............................................................................................................18

3.1.3 Network Information Mastered by the Operator....................................................................................22

3.1.4 Specifications of Equipment for Operator..............................................................................................24

3.1.5 Information About Other Operators in the Same Area...........................................................................25

3.2 Checkpoints for Each Stage.............................................................................................................................25

3.2.1 Checkpoints for Network Dimensioning Stage......................................................................................25

3.2.2 Information Collection At Detailed Planning Stage...............................................................................32

4 Radio Network Pre-planning.........................................................37

4.1 Flow for Radio Network Pre-planning............................................................................................................37

4.2 Radio Network Dimensioning.........................................................................................................................39

4.3 Initial Selection of Sites...................................................................................................................................39

4.3.2 Importing Sites.......................................................................................................................................40

4.3.3 Dividing Areas........................................................................................................................................40

4.3.4 Calculating Site Distance........................................................................................................................40

4.4 System Simulation...........................................................................................................................................43

4.4.1 Preparations Before Simulation..............................................................................................................43

4.4.2 Flow for Configuring Simulation Parameters........................................................................................44

4.4.3 Analyzing Traffic Map............................................................................................................................45

4.4.4 Suggestions for Simulation Parameters..................................................................................................46

4.4.5 Analyzing Simulation Result..................................................................................................................46



4.5 Output of radio network pre-planning.............................................................................................................52

5 Detailed radio network planning...................................................53

6 Cell Planning...............................................................................56

6.1 Flow for Cell Planning of Radio Network.......................................................................................................56

6.2 Noise test and interference analysis.................................................................................................................58

6.3 Site Location Survey........................................................................................................................................58

6.4 Site Selection...................................................................................................................................................58

6.5 System Simulationi..........................................................................................................................................58

7 Area Planning..............................................................................59

7.1 RNC Area Planning.........................................................................................................................................59

7.1.1 Flow for RNC Area Planning.................................................................................................................60

7.1.2 RNC-related Number Planning..............................................................................................................63

7.1.3 Principles for RNC Area Planning..........................................................................................................69

7.2 Paging Area Planning.......................................................................................................................................72

7.2.1 Flow for Paging Area Planning..............................................................................................................72

7.2.2 Principles for Paging Area Planning.......................................................................................................75

7.3 SA Planning.....................................................................................................................................................78

7.4 Cell cluster planning........................................................................................................................................78

8 Neighbor Cell Planning.................................................................81

8.1 Analzying Neighbor Cell Planning..................................................................................................................81

8.1.1 Principles for Neighbor Cell Planning....................................................................................................82

8.1.2 Analzying Intra-frequency Neighbor Cell Planning...............................................................................83

8.1.3 Analzying Inter-frequency Neighbor Cell Planning...............................................................................84

8.1.4 Analzying Inter-RAT Neighbor Cell Planning.......................................................................................85

8.2 Process for Neighbor Cell Planning.................................................................................................................85

8.2.1 New network mode.................................................................................................................................86

8.2.2 Mixed expansion mode...........................................................................................................................91

8.2.3 Neighboring cell check...........................................................................................................................94

9 Scrambling Code Planning............................................................95

9.1 Analyzing Scrambling Code Planning.............................................................................................................95

9.1.1 Scrambling Code Resource....................................................................................................................95

9.1.2 Planning Principles.................................................................................................................................95



9.2 Process for Scrambling Code Planning...........................................................................................................99

9.2.1 New network mode.................................................................................................................................99

9.2.2 Mixed expansion mode.........................................................................................................................107

10 Multi-carrier and multiband network planning...........................111

11 Coverage planning in a high-speed environment........................113

12 LCS Parameter Planning...........................................................114

12.1 Parameter Configuration..............................................................................................................................114

12.1.1 Configuring Parameters for Outdoor Cells.........................................................................................114

12.1.2 Configuring Parameters for Indoor Cells...........................................................................................115

12.1.3 Configuring Parameters for Mixed Indoor and Outdoor Cell............................................................115

12.1.4 Configuring Parameters for the Cells Using Repeater.......................................................................115

12.2 Parameter Configuration in a Commercial Deployment..............................................................................116

13 TCell Parameter Planning.........................................................119

13.1 Introduction to TCell....................................................................................................................................119

13.2 TCell Configuration.....................................................................................................................................119

14 PLMN Tag Parameter Planning..................................................120

14.1 Introduction to PLMN Tag parameters........................................................................................................120

14.2 Parameter Configuration..............................................................................................................................121

15 Summary.................................................................................122

16 Appendix.................................................................................123

16.1 Creating 3G Traffic Maps with 2G Traffic..................................................................................................123

16.1.1 Creating Traffic Maps in a 3G Project................................................................................................123

16.1.2 Creating a Traffic Map in a 2G Project..............................................................................................126

16.2 Proposals on Configuring Simulation Parameters.......................................................................................131

16.2.1 Ec/Io Threshold..................................................................................................................................131

16.2.2 Monte Carlo Simulation Parameter....................................................................................................135

16.3 Configuraing the Cell Access Radius..........................................................................................................135

16.4 Impact from Magnetic Declination on Radio Network Planning................................................................136

16.4.1 Introduction........................................................................................................................................136

16.4.2 Basic Concepts...................................................................................................................................136

16.4.3 Impact.................................................................................................................................................138



16.5 Configuring RNP Parameters.......................................................................................................................139

16.5.1 Overall Flow.......................................................................................................................................139

16.5.2 Introduction to CME Client................................................................................................................140

16.5.3 Detailed Steps.....................................................................................................................................141

16.6 Template for Collecting Information...........................................................................................................154

16.6.1 Template for Collecting Dimensioning Information..........................................................................154

16.6.2 Template for Collecting Information at Detailed Planning Stage......................................................155

16.7 Method of obtaining references quoted in the document.............................................................................155



Figures

Figure 2-1 Flow for RNP design...........................................................................................................................16

Figure 4-1 Flow for radio network pre-planning..................................................................................................38

Figure 4-2 Flow for initial selection of sites.........................................................................................................40

Figure 4-3 Omnidirectional station and 3-sector apex angle excitation (clover station)......................................41

Figure 4-4 Flow for configuring simulation parameters.......................................................................................45

Figure 4-5 Function of RSCP threshold in evaluating simulation result..............................................................48

Figure 4-6 Function of Ec/Io threshold in evaluating simulation result...............................................................49

Figure 4-7 HS-PDSCH Ec/Nt for simulation........................................................................................................50

Figure 4-8 CQIs....................................................................................................................................................51

Figure 4-9 Throughput rate at the application layer..............................................................................................51

Figure 6-1 Flow for cell planning of radio network..............................................................................................57

Figure 7-1 flow for RNC area planning for the operators without 2G networks..................................................61

Figure 7-2 Flow for RNC area planning for the operators without 2G networks.................................................62

Figure 7-3 Before expansion: adding RNC and adding NodeBs..........................................................................66

Figure 7-4 After expansion: adding RNC and adding NodeBs.............................................................................66

Figure 7-5 Before expansion: adding RNC and cutting over some NodeBs........................................................67

Figure 7-6 After expansion: adding RNC and cutting over some NodeBs...........................................................67

Figure 7-7 Before expansion: reserving RNC resource and adding NodeBs according to original planning of RNC area................................................................................................................................................................68

Figure 7-8 After expansion: reserving RNC resource and adding NodeBs according to original planning of RNC area................................................................................................................................................................68



Figure 7-9 RNC are planning: continuous coverage.............................................................................................70

Figure 7-10 RNC are planning: non-continuous coverage...................................................................................70

Figure 7-11 RNC area planning: traffic balance...................................................................................................71

Figure 7-12 RNC area planning: traffic imbalance...............................................................................................71

Figure 7-13 Flow for paging area planning for the operators without 2G networks............................................73

Figure 7-14 Flow for paging area planning for the operators with 2G networks.................................................74

Figure 7-15 Dividing LAs.....................................................................................................................................76

Figure 7-16 Relation among URA, RA, and cell..................................................................................................78

Figure 7-17 Division of cell clusters in a project..................................................................................................80

Figure 8-1 Basic handover process.......................................................................................................................82

Figure 8-2 Typical inter-frequency handover scenario.........................................................................................85

Figure 8-3 Channel No. and inter-frequency strategy file....................................................................................87

Figure 8-4 Engineering parameter data template file............................................................................................88

Figure 8-5 Antenna pattern file.............................................................................................................................88

Figure 8-6 Propagation model parameter file.......................................................................................................89

Figure 8-7 Run the CNA tool................................................................................................................................90

Figure 8-8 Cell update file....................................................................................................................................92

Figure 8-9 Run the expansion mode of the CNA..................................................................................................93

Figure 8-10 Run the check mode of the CNA......................................................................................................94

Figure 9-1 Grouping and allocation of scrambling codes.....................................................................................98

Figure 9-2 Engineering parameter data file cellinfo.txt.....................................................................................101

Figure 9-3 Neighboring cell file cellneighbor.txt..............................................................................................102

Figure 9-4 Run the SCP tool...............................................................................................................................103

Figure 9-5 Number of cells failing to be allocated with a scrambling code for the first time............................104

Figure 9-6 Adjusting the number of orders of neighborhoods............................................................................105

Figure 9-7 Updating the cell engineering parameter data file............................................................................106



Figure 9-8 Results of the second scrambling code allocation.............................................................................107

Figure 9-9 Engineering parameter data file for expansion planning..................................................................108

Figure 9-10 Check of scrambling code in the existing network.........................................................................109

Figure 9-11 Reuse distance between two intra-frequency cells allocated with the same scrambling code........110

Figure 16-1 UMTS Coverage By Transmitter Plot.............................................................................................123

Figure 16-2 Traffic Map based on transmitter and service(user)........................................................................124

Figure 16-3 GSM Live Traffic Data Map...........................................................................................................126

Figure 16-4 GSM Coverage By Transmitter Plot...............................................................................................127

Figure 16-5 GSM Live Traffic Data Map...........................................................................................................127

Figure 16-6 Adjusting traffic name.....................................................................................................................129

Figure 16-7 Adjusting table structure..................................................................................................................130

Figure 16-8 3G traffic map data..........................................................................................................................131

Figure 16-9 Ec/Io used in simulation..................................................................................................................132

Figure 16-10 Setting Ec/Io threshold for simulation to –18 dB..........................................................................133

Figure 16-11 Setting Ec/Io threshold for simulation to –15 dB..........................................................................133

Figure 16-12 Ec/Io distribution in different thresholds.......................................................................................134

Figure 16-13 Magnetic declination.....................................................................................................................137

Figure 16-14 Global magnetic declination..........................................................................................................138

Figure 16-15 Flow for configuring RNP engineers............................................................................................140

Figure 16-16 Work principle for CME system....................................................................................................141

Figure 16-17 Cover sheet....................................................................................................................................148

Figure 16-18 Check result...................................................................................................................................149

Figure 16-19 Welcome interface of WRAN CM Express...................................................................................150

Figure 16-20 Welcome interface of importing negotiated data...........................................................................150

Figure 16-21 Selecting the negotiated file for importing....................................................................................151

Figure 16-22 Selecting items to be imported......................................................................................................152



Figure 16-23 Selecting the mode to import data.................................................................................................153

Figure 16-24 Finishing importing data...............................................................................................................154


WCDMA Radio Network Planning Design Guide For internal use only

Tables

Table 3-1 Principles for classifying target coverage area.........................................................................19

Table 3-2 Information about target coverage areas...................................................................................26

Table 3-3 Coverage probability of pilot channel in the target area...........................................................26

Table 3-4 Information about service bearers............................................................................................27

Table 3-5 Information about service throughput......................................................................................27

Table 3-6 Designed network load.............................................................................................................28

Table 3-7 Quality requirement..................................................................................................................29

Table 3-8 Parameters related to radio propagation (with 2G networks)...................................................29

Table 3-9 Propagation model parameters.................................................................................................30

Table 3-10 Parameters related to equipment.............................................................................................30

Table 3-11 Relation of convention of CE number....................................................................................31

Table 3-12 CE conversion table for the HSUPA.......................................................................................31

Table 3-13 CE resources consumed by the MBMS..................................................................................32

Table 3-14 NodeB parameters..................................................................................................................33

Table 3-15 Feeder parameters...................................................................................................................33

Table 3-16 TMA parameters.....................................................................................................................33

Table 3-17 Engineering parameters..........................................................................................................34

Table 3-18 Cell parameters.......................................................................................................................34

2008-12-17

All rights reserved of 162


Table 3-19 New cell parameters for HSPDA networks............................................................................34

Table 3-20 Bearer parameters...................................................................................................................35

Table 3-21 UE-related parameters............................................................................................................35

Table 4-1 Calculation of site distance and HPBW for omnidirectional station and 3-sector clover station...................................................................................................................................................................41

Table 4-2 Table 4-3 shows RSCP and Ec/Io thresholds planned in a Huawei commercial deployment.. 47

Table 4-3 RSCP and Ec/Io thresholds planned in a Huawei commercial deployment.............................47

Table 4-4 Output of radio network pre-planning......................................................................................52

Table 5-1 Output of the detailed radio network planning.........................................................................54

Table 7-1 LA size estimation....................................................................................................................75

Table 8-1 Comparison between the application modes of the CNA tool..................................................93

Table 12-1 SMLC cell parameters configured in a commercial deployment.........................................116

Table 12-2 Explanation to SMLC cell parameters..................................................................................117

Table 13-1 TCell configuration in a case................................................................................................119

Table 13-2 TCell configuration in multi-carrier.....................................................................................120

Table 14-1 PLMN tag configuration for LA in a case............................................................................121

Table 14-2 PLMN tag configuration for RA in a case............................................................................121

Table 16-1 Variation of call setup rate for different Ec/Io thresholds for simulation.............................134

Table 16-2 Description of each sheet in the template.............................................................................142

Table 16-3 NodeB sheet..........................................................................................................................142

Table 16-4 Cell sheet..............................................................................................................................143

Table 16-5 NRNCCell sheet...................................................................................................................145

Table 16-6 NeighborCellRelation sheet..................................................................................................146

Table 16-7 GSMCell sheet......................................................................................................................146

Table 16-8 GSMCellRelation sheet........................................................................................................147

2008-12-17



Table 16-9 Reference documents location..............................................................................................155

2008-12-17



WCDMA Radio Network Planning Design Guide

Key words: radio network planning, pre-planning, cell planning, area planning, neighbor cell planning, scrambling code planning, paging area planning, simulation parameter configuration, and information collection.

Abstract: The document describes the flow for network planning design and its stages, provides the planning methods for each stage of network planning. It guides engineers to perform fast and accurate network planning.

Acronyms and abbreviations:

Acronyms and Abbreviations Full Spelling

RNO Radio Network Optimization

RNP Radio Network Planning

2G Second generation

3G Third generation

CE Channel Element

CS Circuit Switched

GoS Grade of Service

GSM Global System for Mobile Communications

KPI Key Performance Indicator

LA Location Area

LCS Location Services

PLMN Public Land Mobile Network

PS Packet Switched

RA Routing Area

RNC Radio Network Controller

SA Service Area

UE User Equipment

URA UTRAN Registration Area

UTRAN UMTS Terrestrial Radio Access Network

WCDMA Wideband Code Division Multi-Access

2008-12-17



System

2008-12-17



1 Introduction

The WCDMA radio network planning design is a compulsory stage in WCDMA network construction. The quality of network planning directly affects the performance of network, construction and maintenance cost. This document aims to guide engineers in effective RNP design by detailing its stages.

The following table lists the contents of this guide.

Chapter 1 Introduction

Chapter 2 Flow for WCDMA RNP Design

Chapter 3 Information Collection

Chapter 4 Radio Network Pre-planning

Chapter 5 Radio network detail planning

Chapter 6 Cell Planning

Chapter 7 Area Planning

Chapter 8 Neighbor Cell Planning

Chapter 9 Scrambling Code Planning

Chapter 10 Multi-carrier and Scrambling Code Planning

Chapter 11 Coverage planning in a high-speed environment

Chapter 12 LCS Parameter Planning

Chapter 13 TCell Parameter Planning

Chapter 14 PLMN Tag Parameter Planning

Chapter 15 Summary

Appendix 1 describes how to create a 3G traffic map by using 2G traffic.

2008-12-17



Appendix 2 gives some suggestions on the settings of simulation parameters.

Appendix 3 gives some suggestions on the setting of the access radius of cells.

Appendix 4 analyzes the effect of a magnetic declination on radio network planning.

Appendix 5 guides the preparation of network planning parameters.

Appendix 6 provides an information collection template.

Appendix 7 provides a way of obtaining references quoted in the document.

2 Flow for WCDMA RNP Design

Figure 2-1 shows the flow for RNP design.

Figure 2-1 Flow for RNP design

2008-12-17



Information collection proceeds at the early stage of network planning. It serves link budget, network dimensioning, and network simulation. The information to be collected includes:

Service requirements on continuous coverage over target areas

Coverage probability

QoS

Coverage square

Density of subscribers

Subscribers' behavior

Work band

Digital maps

2G traffic information, site distribution and engineering parameters if the WCDMA operator is running a 2G network.

The previous information serves as input or reference for network planning.

Radio network pre-planning is the initial planning over the network before site survey at the early stage of project. It includes the following stages:

Network dimensioning

Initial site selection

System simulation

At the cell planning of radio network (also called detailed planning of radio network), engineers survey and verify sites one by one based on radio network pre-planning (If the sites cannot meet the requirements or are inaccessible, select their location according to Search Ring output by pre-planning. Determine the engineering parameters related to RNP for guide project construction. Verify the configuration of cell parameters and planning effect by simulation.

Area planning, neighbor cell planning, and scrambling code planning proceed after cell planning of radio network. Area planning aims at the planning of following aspects:

RNC area

Location area

Routing area

URA area

Serving area

2008-12-17



Neighbor cell planning configures the following cells for each cell to guarantee normal handover successfully:

Intra-frequency neighbor cell

Inter-frequency neighbor cell

Inter-RAT neighbor cell

Scrambling code planning determines the primary scrambling code (PSC) for each cell according to the principles for scrambling code planning.

LCS parameter planning aims to configuration parameters for location service (LCS).

The flow for HSDPA planning is similar to the previous flow. The difference lies in the following aspects:

At the stage of information collection, the edge average throughput of HSDPA and cell average throughput of HSDPA must be collected.

The simulation at pre-planning and cell planning must take HSDPA into account.

3 Information Collection

3.1 Information Classification

3.1.1 Contract Requests

A contract usually requires the conditions and process of link budget and network dimensioning, and the explanations to values of some parameters. The contract has requirements on the network capacity and some KPIs for following network acceptance.

2008-12-17



3.1.2 Information About Target Areas

Types of Target Coverage Areas

The radio propagation environment and population density are different in different areas, so classifying these target coverage areas by scenario is necessary according to certain principles. Target coverage areas are classified into the following scenarios:

Dense urban area

Urban area

Suburban area

Rural area

Highway

By the scale of the city and its economical level, sometimes these coverage areas are subdivided into first-class area, second-class area, and so on. In the area of each class, there are the previous five scenarios. In each scenario, the penetration loss in link budget and traffic per subscriber in radio network dimensioning are different.

Classify target coverage areas by radio propagation environment and local environment.

Table 3-1 lists the principles for classifying target coverage area.

Table 3-1 Principles for classifying target coverage area

Scenario Description

Dense urban

The buildings are densely distributed. There are many 10-floor or higher buildings. The commercial centers and office buildings in the capital city are of this scenario.

Urban

The buildings are separated clearly by streets or greenbelts. There are a small number of 10-floor or high buildings sparsely distributed. Most part of capital cities, the center of common cities, and developed towns in south China are of this scenario.

SuburbanThe buildings are sparsely distributed, and most of them are low. The outskirt of cities, most towns, and common industrial zone are of this scenario.

Rural The buildings are fairly sparsely distributed, and most of them are farmer houses. Most rural areas

2008-12-17



and some developing towns are of this scenario.

At the early stage, the operator wants to solve coverage problems in key areas. In rural areas, the operator focuses on the coverage of key towns, so engineers need obtain a list of key towns from the operator for planning in rural areas.

Service Type and Coverage Requirement in Target Areas

Determine the type of service for different target coverage areas with the operator. The selection of continuous coverage service directly affects the radius of coverage and the scale of site construction. Generally, the dense urban area and urban area need CS64k continuous coverage; the suburban area and rural area need CS12.2k continuous coverage.

After determining the type of service, know the coverage probability of target continuous coverage service and know the type of service to match a scenario. Determine whether the scenario is indoor, outdoor, or inside vehicle. Determine whether the index is area coverage probability or edge coverage probability. For example, a dense urban area requires CS64k continuous coverage and its indoor area coverage probability must be 95% or above.

The outdoor coverage usually includes the coverage inside vehicle. The coverage probability affects the margin of slow fading. Under the same condition, the larger the coverage probability is, the larger the needed margin of slow fading is, and the large the number of NodeBs is. In addition, determine the coverage probability with the operator.

For the cells to support HSDPA services, obtain the average throughput at the cell edge.

After the coverage type and coverage provability of target service are fixed, save them in a formal contract, file, or email.

Subscriber Distribution in Target Coverage Areas

The subscriber distribution in target coverage areas concerns the behaviors of subscribers in the coverage areas of different types, total the number of subscribers, subscriber classification, and subscribers behaviors. Different services have different penetration rate in target coverage areas. Based on the subscriber density in the area, RNP engineers can obtain the subscriber distribution density in target coverage areas.

The subscriber distribution in target coverage areas mainly affects the output by network dimensioning. During balancing coverage and capacity,

If the coverage is restricted, no action is to be taken.

2008-12-17



If the capacity is restricted, network expansion is necessary, such as adding carriers or sites.

The subscribers behaviors in target coverage areas refer to the data related to traffic model, such as average traffic per subscriber for CS services and average throughput per subscriber for PS services.

For HSDPA services, the average throughput rate per subscriber for PS services is necessary, and sometimes the needed average throughput per subscriber must be provided (throughput rate is the traffic per second, and its unit is bps. Throughput is the traffic in an hour, and its unit is bit. Throughput = throughput rate *3600). Provide either average throughput rate or average throughput, because one of them can be calculated with the other.

Related KPIs

The KPIs at the network planning stage include:

Call success rate

Coverage probability

Pilot pollution ratio

Soft handover (SHO) ratio

In HSDPA networks, the related KPIs are as below:

Average throughput rate at the cell edge

Average throughput rate of cell

Band Information

The band information mainly includes the specified 3G band and which operator uses the neighboring band. The uplink 3G band is from 1920 to 1980 MHz while the downlink 3G band is 2110 to 2170 MHz. Protocols even provides other extended 3G bands, including the frequencies around 1800, 1700, and 800 MHz. For details, see 3GPP25.141-690.

In actual planning, besides the 3G band being used by the operator, RNP engineers need obtain the local band allocation for analyzing the interference from other bands, because this is helpful for identifying interference problems.

Map Information

The following maps about planning areas are necessary:

Digital maps (for simulation)

2008-12-17



Digital maps serve network simulation. A digital map usually includes altitude data, landform data, and vector data. If a 3D map is used, the digital map must include the height data of buildings.

The leading simulation tools are U-Net (Atoll) and Enterprise, both of which are supported by all existing digital maps. Before planning, the simulators can try to import digital maps. If RNP engineers need to buy a new digital map, inform the map provider of the simulation tool to be used.

Mapinfo digital map

The Mapinfo digital map serves drive test (DT) and other aspects, such as for checking the surrounding information of a site or site distribution.

Paper map of high precision

The paper map of high precision is important to planning, by which engineers can get familiar with the planning area.

Information collection in major areas

Besides the information collection in ordinary areas, related information should be collected in special VIP areas such as government buildings, major shopping malls, hotels, stadiums, landmark buildings, and major business halls of the network operator. The information includes geographical position, building information, distribution and number of users, service characteristics, and service coverage requirement. At the network planning and optimization phases, great importance should be attached to these areas so that customer satisfaction can be improved.

Other Information

Other information includes:

Administrative division

Organizational structure of the operator

Operator's liaisons

3.1.3 Network Information Mastered by the Operator

Operator with 2G Networks

If an operator is running a 2G network, it usually wants to construct the 3G network co-located with the 2G network to save cost. Therefore obtaining the information about 2G sites is highly necessary. The needed information includes:

Engineering parameters of 2G sites

Cell parameters of 2G sites

2008-12-17



Traffic statistics of 2G network

Information about the 2G distributed antenna system (DAS)

The engineering parameters of 2G network include:

NodeB type (macro NodeB or mini NodeB)

Site ID

Cell ID

Site location (latitude and longitude)

Whether the GSM 900 MHz network shares sites with the GSM 1800 MHz network

Site height

Antenna type

Whether the 3G network shares antennas with 2G network

Azimuth

Down tilt

Feeder type

Feeder length

Whether tower mounted amplifiers (TMAs) are used

TMA type

Other connectors and loss

Whether the 2G site has enough space

Whether the auxiliary equipment like transmission and power supply are complete

Based on the previous information, RNP engineers can judge whether a 2G site can serve as a 3G site.

The operator does not maintain 2G repeaters and the information about them are greatly different from actual information, so the information about them is optional. If the operator provides this, use it as reference.

The 2G cell parameters include:

Parameters about neighbor cell configuration

LA

BSC statistics

2008-12-17



The BSC distribution information is like the RNC area division information in 3G networks.

The 2G traffic statistics include the traffic data about GSM 900 MHz and GSM 1800 MHz sites. The 2G traffic statistics include the traffic of voice service and throughput of data services (GPRS), which can serves in predicting 3G traffic distribution. In addition, the 2G traffic statistics must also include the traffic data about GSM 900 MHz and GSM 1800 MHz cells with the period of data source and the Cell ID as index with engineering parameter data of GSM sites. It's better to output processed traffics statistics data in an EXCEL format for post processing. Sometimes the 2G TA information is necessary in statistics for configuring the search radius of 3G NodeBs.

The information about 2G DAS includes:

Site location

Traffic

Antenna-feeder type (whether it is broadband)

Type of signal source

The storey of site

Building type

Building usage (office building, government, hotel, and so on)

The previous information helps design 3G DAS. In addition, traffic of AMR services in 2G DAS and throughput of GRPS data services are necessary.

New Operators

New operators usually focus on the information about available sites. The information is about some private business occasions, office buildings, residential areas where site construction is probable. Engineers need the following information:

Latitude and longitude of candidate sites

Height of floor

Environment

Possible location and azimuth for mounting antenna

In addition, engineers need to focus on transmission, power supply, equipment room space, and other auxiliary equipment.

3.1.4 Specifications of Equipment for Operator

Other equipment includes:

2008-12-17



Antenna

Coupler

TMA

Feeder

For antennas, obtain the following specifications:

The model of available antenna

Vendor of antenna

Electrical indexes

− Work band

− Polarization

− Gain

− Horizontal and vertical beamwidth

− Embedded electric down tilt

− Side lobe suppression

− Front-to-rear ratio

− Isolation

− Impedance

− Intermodulation

− Maximum input probability

Mechanical specifications

− Antenna size

− Weight

− Wind resistance

− Connector location

Files of antenna pattern (for system simulation)

For couplers, focus the type and loss.

For TMAs, focus the mode, noise figure, and gain.

For feeders, focus the model and loss.

2008-12-17



3.1.5 Information About Other Operators in the Same Area

Obtain the information about other operators in the same area by the internal shared mechanism of Huawei.

3.2 Checkpoints for Each Stage

3.2.1 Checkpoints for Network Dimensioning Stage

Network dimensioning analyzes the future network briefly. At this stage, engineers obtain the scale of network construction (approximate the number of NodeBs and NodeB configuration) by dimensioning network based on input information. Consequently engineers can obtain the construction period, economical cost and manpower cost. Therefore, the more comprehensive and accurate the information collected from network dimensioning stage is, the more valuable the information are for dimensioning of network scale.

The information to be known at the network dimensioning stage mainly includes:

Square of target coverage area

Requirements on continuous coverage services

Subscriber distribution and subscribers' behaviors in target coverage area

Services and bearers concerning dimensioning

QoS

Propagation model for dimensioning

The following sections describe the information needed by the operators with 2G networks and the new operators at the network dimensioning stage.

Operators with 2G Networks

1. Information about target coverage areas

Table 3-1 lists the information about target coverage areas.

Table 3-1 Information about target coverage areas

Type of Target Coverage Area

Type of Continuous Coverage service

Square (km2)

Area Coverage Probability (%)

Total the number of subscribers

Subscriber ratio (%)

2008-12-17



Dense urban

CS64k 20 95%

600,000

20%

Urban CS64k 60 95% 45%

Suburban CS64k 100 95% 20%

Rural AMR12.2k 800 90% 10%

Highway AMR12.2k 1000(km) 90% 5%

NOTE

The highway is linear, so obtain the length of highway to be covered.

Besides the coverage areas information, some operators may also make a coverage probability request, just like the table below:

Table 3-2 Coverage probability of pilot channel in the target area


RSCP Threshold

RSCP Coverage Probability

Ec/Io Threshold Ec/Io Coverage Probability

Densely populated urban area

-81 dBm 93% -14 dB (75% loading)

93%

Ordinary urban area

-86 dBm 93% -14 dB (75% loading)

93%

Suburb area -88 dBm 93% -14 dB (75% loading)

93%

Rural area -88 dBm 90% -14 dB (75% loading)

90%

Usually, it’s the operator who provides information in the previous tables. RNP engineers can propose related suggestions. It must be specified for area coverage probability whether the coverage is indoor or outdoor. For the operator with 2G networks, engineers can predict the growth of 3G subscribers in a few years based on the ratio of 2G subscribers.

The type of target coverage area listed above may be different from the actual scenarios. Follow the scenarios provided by the operator.

2. Service bearers and throughput

For service bearers, obtain the type of services and their bearers to be considered in the planning, and provide the average traffic per subscriber for CS services and average throughput per subscriber for PS services. The information is necessary for uplink and downlink capacity dimensioning.

Table 3-1 lists the information about service bearers.

2008-12-17



Table 3-1 Information about service bearers

Service Bearer rate (UL/DL) BLER

Voice CS12.2k/CS12.2k 1%

Video Phone CS64k/CS64k 0.1%

MMS PS64k/PS64k 5%

Internet PS64k/PS128k 5%

Video PS64k/PS384k 5%

The service, bearer rate and BLER in the previous table are just for reference. In actual planning, the operator will provide the information. RNP engineers can propose suggestions.

Besides the information in the previous table, the traffic and throughput for various services are necessary.

Table 3-2 lists the information about service throughput.

Table 3-2 Information about service throughput

BearerAverage Traffic per Subscriber in busy hour (Erl)

Average Throughput per Subscriber in busy hour (Kbyte)

CS12.2k 0.025 –

CS64k 0.0025 –

PS64k UL – 21

PS64k DL – 74

PS128k DL – 6

PS384k DL – 4

HSDPA – 200

For the operators with 2G networks, the statistics of traffic of AMR services and GPRS throughput in the 2G network helps reasonably estimate the traffic of 3G subscribers.

3. Designed network load

The network is usually running not under the full load condition to keep stable running. Especially for 3G networks, due to the cell breathing, the increase of network load will lead to shrink of network coverage. As a result, before network dimensioning set the maximum load for different coverage areas in the network.

Table 3-1 lists the designed network load.

2008-12-17



Table 3-1 Designed network load


Uplink Load Downlink LoadDownlink Load (HSDPA+R99)

Dense urban 50% 75% 90%

Urban 50% 75% 90%

Suburban 50% 75% 90%

Rural 30% 75% 90%

Highway 30% 75% 90%

The operator shall provide the designed network load. If necessary, RNP engineers shall describe the meanings and impact of previous parameters and propose suggestions to the operator.

4. Quality requirement

The quality requirement is congestion rate for CS services, as for PS services, the probability of queuing delay less than a certain threshold (for example, 0.5s).

Table 3-1 Quality requirement


CS Congestion ratePS Queuing delay probability

Dense urban 2% 98%

Urban 2% 98%

Suburban 2% 98%

Rural 5% 98%

Highway 5% 98%

The operator shall provide the GoS. If the operator fails to provide it, RNP engineers can provide recommended GoS.

5. Parameters related to radio propagation

The parameters related to radio propagation include:

− Penetration loss

The penetration loss takes effect in indoor and inside vehicle coverage.

− Standard deviation of shadow fading

The standard deviation takes effect in calculating margin of shadow fading.

2008-12-17



− Type of channel

The selection of channel affects the demodulation threshold, and consequently affects sensitivity.

Table 3-1 lists the parameters related to radio propagation (with 2G networks).

Table 3-1 Parameters related to radio propagation (with 2G networks)


Penetration loss (dB)

Standard deviation of shadow fading (dB)

Channel

Dense urban 19 10 TU3

Urban 13 8 TU30

Suburban 8 6 TU120

Rural 8 6 RA120

Highway 8 6 RA120

The operator shall provide the parameters in the previous table. RNP engineers usually describe the meanings and impact of previous parameters and provide recommended values to the operator. The recommended values shall be approved by the operator.

6. Propagation model

The selection of propagation model has great impact on the result of network dimensioning. If the operators with 2G networks have the propagation model of GSM 1800 MHz, obtain the following information related to propagation model tuning:

− Information about the site for transmitter (location of transmitter, transmit power, feeder loss, type of transmitted signals)

− Test and collected data (location for collecting data, received signal strength)

Output the previous information in an Excel for post processing.

If the operator has no tuned model to use, RNP engineers can choose proper model from the library of tuned models. At last, perform CW test for propagation model tuning. For propagation model, the K series parameters listed in Table 3-1 must be provided. The Table 3-1 lists the K series parameters of the common SPM model in U-Net.

Table 3-1 Propagation model parameters


K1 K2 K3 K4 K5 K6 KClutter

Dense urban 27.43 44.9 5.83 0 -6.55 0 1

Urban 23.46 44.9 5.83 0 -6.55 0 1

2008-12-17



Suburban 11.96 44.9 5.83 0 -6.55 0 1

Rural -8.455 44.9 5.83 0 -6.55 0 1

Highway -8.455 44.9 5.83 0 -6.55 0 1

7. Parameters related to equipment

Table 3-1 lists the parameters related to equipment.

Table 3-1 Parameters related to equipment

Maximum transmit power of NodeB

Maximum transmit power of UE

Body lossMargin of background noise

Work frequency

43dBm

Voice Data Voice Data UL DL UL DL

21dBm 21dBm 3dB 0dB 0 dB 0 dB1950 MHz

2140 MHz

RNP engineers shall provide recommended values to the operator and describe the meanings and impact of previous parameters. The recommended values shall be approved by the operator.

8. Relation of convention of CE number

The network dimensioning stage usually dimension the number of needed CEs in uplink and downlink, so the relation between the number of uplink CEs and that of downlink CEs must be known. The system simulation at the network detailed planning stage will also use the information, so the Table 3-1 lists the relation between the number of uplink CEs and that of downlink CEs.

In HSDPA networks, there is a special processing unit, so there is no CE used. However, the associated dedicated channel (DCH) uses CEs. The associated DCH uses a CE in downlink. The associated DCH uses as many CEs in uplink as that of R99 network for the same bearer.

Table 3-1 Relation of convention of CE number

Bearer rateThe number of uplink equivalent CEs

The number of downlink equivalent CEs

CS12.2k 1 1

CS64k 3 2

PS64k 3 2

PS128k 5 4

PS384k 10 8

2008-12-17



For the details about the previous parameters, refer to W-U-Net Simulation Parameter Setting Guidance-20060817-A-3.1.

Similar to R99, the uplink of the HSUPA consumes CE resources. Table 3-2 lists the CE resources that the HSUPA consumes for different spreading factors at different rates.

Table 3-2 CE conversion table for the HSUPA

MinSF HSUA Bearer Rate (kbit/s) HSUPA Phase1 HSUPA Phase2

SF64 16 2 1

SF32 32 2.5 1.5

SF16 64 4 2

SF8 128 6 4

SF4 384 11 10

2*SF4 Maximum of 1920 21 20

2*SF2 Maximum of 3840 Not supported 32

2*SF2 + 2*SF4 Maximum of 5760 Not Supported 48

As the MBMS service involves only downlink channels, you only need to consider the downlink channels when calculating the CE resources consumed by the MBMS. Table 3-3 lists the CE resources consumed by the MBMS at different rates.

Table 3-3 CE resources consumed by the MBMS

Channel Rate

16 kbps 32 kbps 64 kbps 128 kbps 256 kbps

Code resources

SF128 SF64 SF32 SF16 SF8

CE resources 1 1 2 4 8

New Operators

1. Information about target coverage areas

The information is the same as that needed by the existing 2G network.

2. Service bearers and throughput


2008-12-17



3. Designed network load


4. Quality requirement


5. Parameters related to radio propagation


6. Propagation model

Obtain the propagation model from the library of Huawei propagation models. Or perform CW test for tuning. The information is the same as that needed by the existing 2G network.

7. Parameters related to equipment


8. Relation of convention of CE number


According to previous analysis, the information needed by the operators with 2G networks and new operators are similar, so an information collection template is provided for network simulation, embedded in the appendix.

3.2.2 Information Collection At Detailed Planning Stage

The detailed planning stage finishes system simulation and site survey by obtaining the information related to them. The information includes the following parameters:

Equipment parameters

Engineering parameters

Cell parameters

UE parameters

The following sections describe the previous parameters for the operators with 2G networks and new operators respectively.

Operators with 2G Networks

Equipment parameters

The related equipment parameters include the parameters about NodeB, feeder, and TMA. RNP engineers shall obtain their parameters. Table 3-1 lists the NodeB parameters.

2008-12-17



Table 3-1 NodeB parameters

NodeB ModeThe number of Available Uplink Channels

The number of Available Downlink Channels

BTS3812E 384 384

If previous parameters are used in system simulation and engineers require that the failure causes from the simulation tools include inadequate resources, engineers must correctly allocate channel resources, which is closely related to the model of NodeBs. For details, refer to W-U-Net Simulation Parameter Setting Guidance-20060817-A-3.1.

For feeders, RNP engineers need the feeder parameters listed in Table 3-2.

Table 3-2 Feeder parameters

Model of Feeder Average loss per meter (dB/m) Connector loss (dB)

7/8" 0.0611 0.5

5/4" 0.0443 0.5

The 2G network also uses feeders, so RNP engineers can obtain their information from the operator. There are just several common feeders. If the operator fails to provide the information, RNP engineers can obtain the information from Huawei.

For TMAs, RNP engineers need the parameters listed in Table 3-3.

Table 3-3 TMA parameters

Mode of TMANoise Figure of TMA (dB)

TMA Gain (dB)TMA Insertion Loss (dB)

TMA 1.7 12 0.4

Check whether the operator wants to use TMAs. If yes, ask the operator for TMA specifications, from which the parameters listed in previous table can be obtained. If the operator wants Huawei to provide the parameters, RNP engineers can obtain them from Huawei or TMA providers, as well as search for them online.

2. Engineering parameters

Table 3-1 lists the engineering parameters.

Table 3-1 Engineering parameters

Site Name

Site ID

LatitudeLongitude

Antenna Type

Antenna Height

Propagation model

Azimuth

Down tilt

Feeder mode

Feeder Length

Whether to use TMAs

TMA Type

Site1123456

x x 742211 30 SPM 120 6 7/8" 30m No -

2008-12-17



The operators with 2G networks can probably provide all the parameters except propagation model, but the provided parameters are for 2G configuration. RNP engineers can input these values as initial values in system simulation and adjust them accordingly.

3. Cell parameters

Cells parameters include load parameters, channel power parameters, active set threshold, and noise figure, as listed in Table 3-1.

Table 3-1 Cell parameters

Cell Name

Cell ID

Maximum Transmit Power (dBm)

Pilot Power (dBm)

Other CCH Power (dBm)

Orthogonal Factor

Noise Figure (dB)

Active Set Threshold (dB)

Active Set Size

Uplink Load (%)

Downlink Load (dBm)

Cell1 12345 43 33 34.46 0.5 3 5 3 50 40.74

In network simulation, RNP engineers can refer to the parameter configuration guide to the simulation software. The 40.74 in the previous table corresponds to 75% of the downlink maximum transmit power 43 dBm (20 W).

The parameters listed in Table 3-2 are added in HSDPA networks. The margin of power control 0.4576 corresponds to 10%.

Table 3-2 New cell parameters for HSPDA networks

HSDPA Supported

HSDPA Power

(dBm)

Power Margin

(dB)

Max The number of HS-PDSCH Codes

Min The number of HS-PDSCH Codes

Dynamic Allocation of HSDPA Power?

Dynamic Allocation of HS-SCCH Power?

HS-SCCH Power (dBm)

Maximum The number of HSDPA Subscribers

Scheduling Algorithm

Peak Rate per Subscriber in Uplink (kbps)

Peak Rate per Subscriber in Downlink (kbps)

Y 0.4576 10 1 Y N 30 16 PF 128 1800

4. Bearer parameters

Table 3-1 Bearer parameters

ServiceType of Service

Support SHO?

Bearer Rate (UL/DL)

Activation Factor/ Efficiency Factor

Maximum Transmit Power of Downlink TCH (dBm)

Minimum Transmit Power of Downlink TCH (dBm)

SHO Gain (dB)

Uplink and Downlink Demodulation Performance (dB)

Email Background Y 64/64 1 33 3 1.5 2.6/4.8

5. UE-related parameters

2008-12-17



Engineers can also obtain UE-related parameters from related parameter configuration guides. The maximum transmit power of UE must be approved by the operator, because the transmit power of some UEs cannot reach 24 dBm for data services.

Table 3-1 UE-related parameters

UE Name Minimum Transmit Power (dBm)

Maximum Transmit Power (dBm)

Noise Figure (dB)

Body Loss (dB)

Ec/Io Threshold (dB)

UE_Voice -50 21 7 3 -18

To collect related parameters for the operators with 2G networks, refer to the appendix.

New Operators

1. Equipment parameters

The needed equipment parameters are the same as those needed by the operators with 2G networks. The operator needs to provide a list of equipment. If Huawei needs to provide the list, engineers can obtain it from Huawei, equipment vendor, and internet.

2. Engineering parameters

The needed information is the same as that of the operators with 2G networks.

For new operators, antenna type, azimuth, and down tilt must be determined by RNP engineers according to simulation result.

3. Cell parameters


4. Bearer parameters


5. Carrier parameters


6. UE parameters


2008-12-17



4 Radio Network Pre-planning

4.1 Flow for Radio Network Pre-planning

Figure 4-1 shows the flow for radio network pre-planning.

2008-12-17



Figure 4-1 Flow for radio network pre-planning

Collect information for network dimensioning and initial selection of sites from the tender document, project contract, and the operator's requirements.

Radio network dimensioning includes link budget and capacity dimensioning. Obtain the scale of sites and configuration according to input requirements when the coverage and capacity are balanced.

Initial selection of sites proceeds as below:

Step 1 Survey sites

Step 2 Import the sites to simulation project

Step 3 Select proper propagation model

2008-12-17



Step 4 Select sites initially after simple prediction

Step 5 Select improper and unobtainable site.

----End

Based on initial selection of sites, in the system simulation, engineers perform Monte Carlo simulation with the corresponding traffic model, locate the faulty area, adjust sites or carry out other adjustments to make the simulation result meet requirements.

4.2 Radio Network Dimensioning

W-Radio Network Planning Guide-A-3.0 (to be released) will detail radio network dimensioning. For details, refer to it.

It should be noticed that, at the bidding phase, CW tests and 2G network coverage tests should be performed for the additional coverage requirements (see "Information Collection in the Target Coverage Area in section 3.2.1 "Network Estimation Phase") of the pilot channel, which are put forward by the network operator to ensure that the number of committed sites can satisfy the requirements and avoid any loss owing to coverage in subsequent delivery.

4.3 Initial Selection of Sites

Figure 4-1 shows the flow for initial selection of sites.

2008-12-17



Figure 4-1 Flow for initial selection of sites

4.3.2 Importing Sites

Import the available sites provided by the operator into U-Net by editing sites first in Excel and then directly copying and pasting them into U-Net. For details, refer to W-U-Net Simulation Parameter Configuration Guide-20050528-A-2.5.

4.3.3 Dividing Areas

Based on digital maps and environment survey report, mark the target areas of different propagation models with polygons.

4.3.4 Calculating Site Distance

According to the result of network dimensioning, determine the site distance for the sites of different types. The most common types of sites include:

2008-12-17



Omnidirectional station

3-sector apex angle excitation (clover station)

Figure 4-1 Omnidirectional station and 3-sector apex angle excitation (clover station)

D

R

Table 4-1 lists the calculation of site distance and half power beamwidth (HPBW) for omnidirectional station and 3-sector clover station.

Table 4-1 Calculation of site distance and HPBW for omnidirectional station and 3-sector clover station

Model of SiteTheoretical Calculation

Approximate Engineering Calculation

Typical Horizontal HPBW for Antenna

2008-12-17



Omnidirectional station

D = sqrt(3)×R D = 1.73ROmnidirectional antenna

3-sector clover station D = 1.5×R D = 1.50R 65°

The calculated site distance multiplied by ±20% serves as the proper range for site distance.

Selecting/Adding Sites

Select sites from available sites in the dense urban areas, following the requirement on site distance. For details, refer to W-Site Selection and Survey Guide-20060310-A-3.0 (to be developed).

Antenna Azimuth

At the pre-planning stage, configure the antenna azimuth by following the aspects as below:

For the operators with 2G networks, the ratio of co-located sites is high in pre-planning, and the operators usually require Huawei engineers to refer to the azimuth of 2G antennas.

For the operators with 2G networks or the new operators, if their ratios of co-located sites are low, the standard azimuth (clover-like) for initial azimuth shall be considered. The initial azimuth should be 30°/150°/270° and avoids the waveguide effect by long and straight streets.

Down Tilt of Antenna

Configure the down tilt of antenna by following the aspects as below:

For the operators with 2G networks, the ratio of co-located sites is high in pre-planning, and the operators usually require Huawei engineers to refer to the down tile of 2G antennas.

For the operators with 2G networks or the new operators, if their ratios of co-located sites are low, the initial down tilt should be 4°–6° for dense urban areas, 2°–4° for urban areas, and 0°–2° for suburban and rural areas.

Most of the current antennas support an electrical tilt. The design should ensure that no mechanical tilt is used when the electrical tilt does not reach the maximum allowable value. For a densely populated urban area where a large down tilt may be set in future, the mechanical tilt can be uniformly set to two degrees to increase the range of the electrical tilt and reduce the difficulty of the adjustment of the antenna and feeder.

2008-12-17



Coverage Prediction

After initial selection of sites, perform coverage prediction to initially verify the quality of network coverage.

The key for coverage prediction is correct configuration of propagation model. Focus on the following aspects:

Use different propagation models for different scenarios.

If propagation model is tuned on the target area, use the tuned propagation model. Keep the calculations of diffraction parameters, antenna height consistent with those used in tuning.

For the result of coverage prediction, focus on the distribution of best servers and pilot level. For the small areas with unqualified level, adjust the azimuth and down tilt to improve the coverage. For the large areas with weak coverage, analyze whether the site distance is over large:

If yes, add sites to improve coverage.

If no, check whether the configuration of parameters related to coverage prediction is correct.

For the output best servers, check whether the squares of best servers in a scenario are even. If there is over large or over small best server, find the cause. Try to adjust the azimuth and down tilt of antenna, and see if the coverage is improved. Adjust the site location if necessary.

Based on previous selection of sites and adjustment of engineering parameters, perform simulation verification of network performance and detailed site adjustment.

4.4 System Simulation

4.4.1 Preparations Before Simulation

The preparations before simulation are as below:

The simulation software and dongle must work normally. The computer for simulation must be qualified. For a common-scale simulation (at most 300 sites), perform it on a laptop with 512 MB RAM or above and 1 GHz CPU or above. The computer for large-scale simulation (at least 300 sites) must be a server of high performance, with 2 GB RAM or above and 2 GHz CPU or above.

Confirm that the digital maps for simulated area are enough and correct. If a digital map can be imported to U-Net and the U-Net displays the map correctly,

2008-12-17



the map is usually normal. If the display fails or other problems occur, contact the digital map provider.

Confirm that the antenna files for the antennas to be used can be correctly imported to U-Net.

Proper propagation models are available.

The initial engineering parameters and cell parameters are available for simulation.

The information for traffic model for simulation is available.

The method for evaluating the simulation result is available. For example, engineers can analyze the results of coverage prediction and interference prediction, find the faulty area, and provide solutions.

If engineers want to use the global simulation center of the network planning department for simulation, refer to the Operation Guidelines for the Global Simulation Center.

4.4.2 Flow for Configuring Simulation Parameters

Figure 4-1 shows the flow for configuring simulation parameters.

2008-12-17



Figure 4-1 Flow for configuring simulation parameters

NOTE

The previous flow is based on U-Net. For details, refer to WCDMA RNP U-Net Simulation Parameter Setting Guidance-20050528-A-2.5.

4.4.3 Analyzing Traffic Map

Before Monte Carlo simulation, analyze traffic distribution. Analyze traffic distribution from the following two aspects:

Traffic modeling

Traffic map

2008-12-17



Traffic Modeling

Select Handset Configuration > Mobility Type > Service Type > Subscribers' Behaviors > Traffic Environment for configuring traffic modeling. For details, refer to WCDMA RNP U-Net Simulation Parameter Setting Guidance-20050528-A-2.5.

Traffic Map

There are four types of traffic maps in U-Net:

Based on Environments(raster)

Based on User profiles(vector)

Based on Transmitters and Services(throughput)

Based on Transmitters and Services(#users)

In simulation, the first and the third options are usually selected, namely, the raster map based on environments and based on transmitters and services (throughput). The third map and the fourth map are similar. The third one is based on throughput while the fourth one is based on users.

If engineers have known the traffic of each cell in simulation, use the third map by performing Best Server coverage prediction and then traffic distribution. If there is no traffic information of each cell but only the range, refer to WCDMA RNP U-Net Simulation Parameter Setting Guidance-20050528-A-2.5 for detailed operations.

4.4.4 Suggestions for Simulation Parameters

For details, refer to the appendix.

4.4.5 Analyzing Simulation Result

Analyze simulation result from the following two results:

Result of coverage prediction

Result of Monte Carlo simulation

The analysis of simulation result is to check whether RSCP and Ec/Io have met the requirements. In addition, engineers shall focus on the following aspects:

Call setup rate

Causes to call failure

Pilot pollution

2008-12-17



SHO ratio

Uplink and downlink load

Find the causes to call failure and provide solutions.

In HSDPA networks, check whether the average throughput rate at the cell edge and average throughput rate of cell can meet the requirement.

The pilot pollution radio is required to be 5% at most. The SHO ratio is required to be 30%–40%.

The RND tool supports calculating RSCP and Ec/Io for each service in various scenarios according to input conditions. Based on the values, RNP engineers can evaluate the result (use the corresponding requirements on figures). According to the requirements on target services, locate the faulty area and provide solutions.

Table 4-1 Table 4-2 shows RSCP and Ec/Io thresholds planned in a Huawei commercial deployment.

Table 4-2 RSCP and Ec/Io thresholds planned in a Huawei commercial deployment

Bearer Service RSCP Threshold (dBm) Ec/Io Threshold (dB)

AMR12.2k -92.9 -14.18

CS64K -87.9 -12.48

PS128k -88.5 -10.96

PS384k -84.2 -9.2

Figure 4-2 shows the function of RSCP and Ec/Io thresholds in evaluating simulation result.

2008-12-17



Figure 4-2 Function of RSCP threshold in evaluating simulation result

In Figure 4-2, different services are marked with different colors, and engineers can see the coverage range of a service. Engineers can identify the faulty areas for continuous coverage service and provide solution. In Figure 4-2, the yellow stands for the areas meeting the requirement from PS 384 kbps service. The grey and black mark the faulty area. For the large faulty area, provide solutions.

Figure 4-3 shows the function of Ec/Io threshold in evaluating simulation result.

2008-12-17



Figure 4-3 Function of Ec/Io threshold in evaluating simulation result

Figure 4-3 shows the interference prediction for PS 384 kbps service. In Figure 4-3, the yellow stands for the areas meeting the requirement from PS 384 kbps service. The grey and black mark the faulty area. For the large faulty area, provide solutions.

Figure 4-4 shows the HS-PDSCH Ec/Nt for simulation.

2008-12-17



Figure 4-4 HS-PDSCH Ec/Nt for simulation

Figure 4-5 shows the CQIs.

2008-12-17



Figure 4-5 CQIs

Figure 4-6 shows the throughput rate at the application layer.

2008-12-17



Figure 4-6 Throughput rate at the application layer

2008-12-17



4.5 Output of radio network pre-planning

The final output of the radio network pre-planning is a pre-planning report and an engineering parameter table. Table 4-1 lists the output contents.

Table 4-1 Output of radio network pre-planning

Output Description

Radio Network Pre-Planning Report

Network construction strategy

Planning of initial sites

Suggestions on the selection of antennas and feeders

Evaluation of the simulation result

Radio Network Engineering Parameter Table

Number of NodeBs

Site location information

Antenna model, azimuth, down-tilt

Cell parameters (channel power, and soft handover parameters)

The Radio Network Engineering Parameter Table is the input information for subsequent site selection and system simulation.

2008-12-17



5 Detailed radio network planning

According to the latest WBS formulated by the radio network planning department in 2008, detailed planning comes after pre-planning but before RF optimization. Detailed planning is the last part of network planning and mainly includes the following tasks:

− Electromagnetic background interference test and interference analysis

− Site survey and selection

− System simulation

− Neighboring cell planning

− Scrambling code planning

− Area planning (including the division of RNC area, LA, RA, and SA)

− Multi-carrier and dual-band networking, coverage in a high-speed environment, and system network parameter configuration for 3G-2G interoperability

− Preparation of data such as Tcell and LCS

Among these tasks, electromagnetic background interference test, site survey and selection, and system simulation are called radio network cell planning.

The following describes each of these tasks.

Table 5-1 lists the reports that should be generated at the detailed radio network planning phase and the contents of the reports.

2008-12-17



Table 5-1 Output of the detailed radio network planning

Report Contents

Radio Network Planning Report.doc

Network construction strategies at different phases

NodeB planning

Cell parameter planning

Simulation result analysis

Solution to the coverage and capacity in a special scenario

Number of CEs required by each site

Number of E1 required by each site

Network Planning Engineering Parameter Table.xls

No., name, longitude and latitude of site

Sector name, Cell ID, and cell name

TRX identification and frequency

LAC, RAC, and primary scrambling code

Antenna model, polarization mode, horizontal/vertical half-power angle, gain, and EIRP

Antenna height, azimuth, down-tilt, and altitude

Power amplifier model, and combining and dividing mode

Feeder model and length

Cell coverage target

2008-12-17



Report Contents

Network Planning Data Configuration Table for Deployment.xls

Basic information of the local office and basic maintenance information

Cell fast-setup parameters

Cell radio link power parameters

NRNC cell parameters and GSM cell information

Intra-frequency neighboring cells and inter-frequency neighboring cells

Inter-frequency neighboring cells with the same coverage and inter-system neighboring cells

Cell SMLC information

Information for locating neighboring cells

Network Planning Data Configuration Table for Deployment contains all negotiation data required to be input for the CME.

In the Network Planning Data Configuration Table for Deployment, the cell fast-setup parameters and the cell radio link power parameters are usually set to the defaults of the corresponding RNC version and no specific values need to be provided for them.

If the neighboring cell script is prepared by the network planning engineer on site, it is not required to provide a Network Planning Data Configuration Table for Deployment.

2008-12-17



6 Cell Planning

6.1 Flow for Cell Planning of Radio Network

Figure 6-1 shows the flow for cell planning of radio network.

2008-12-17



Figure 6-1 Flow for cell planning of radio network

Perform noise test to know the electromagnetic interference around candidate sites.

Site survey includes two parts:

Obtain the candidate sites.

Obtain the detailed survey of candidate sites.

Site selection depends on the site survey report and site conditions (equipment room, transmission, and the difficulty of obtaining the site location). Determine the final sites for engineering implementation.

After the locations for all sites are fixed, perform system simulation and compare the network performance with that at the pre-planning stage for finding problems in time and adjusting solutions.

2008-12-17



6.2 Noise test and interference analysis

For details, refer to W-Site Selection and Survey Guide-20060310-A-3.0 (to be developed).

For the specific tasks of a noise test, refer to RNP-Electromagnetic Background Interference Test Guide.

Currently, the network planning department provides an evaluation tool— a tool for analyzing the interference co-existence between RNPS GCWUT communication systems. The tool can output the isolation requirement after the transmitter and receiver types, the index type, and intermediate frequency (IF) are entered

You can download the latest version of this tool from the website http://3ms.huawei.com/mm/docNav/mmNavigate.do?method=showMMList&node_id=1-2-10599-15545.

6.3 Site Location Survey


6.4 Site Selection


6.5 System Simulationi

For details, refer to 4.4 .

2008-12-17



7 Area Planning

7.1 RNC Area Planning

The RNC area refers to the area covered by radio signals of one or more cells under the same RNC. Different RNC-IDs stand for different RNCs. The combination of RNC-ID and PLMN-ID marks an RNC exclusively, namely,

Global RNC-Id = PLMN-Id + RNC-Id

The RNC-ID and Global RNC-ID mark the RNC at the Iu, Iub, and Iur interfaces.

The RNC area planning is to plan the following aspects:

The number of RNCs in the coverage range

The number of cells under an RNC and its coverage range

The RNC area planning is part of radio network planning. After the planning of the number of NodeBs/cells, cell coverage range, cell capacity, and interface throughput is complete, perform RNC area planning. For a complete radio network planning project, the number of RNCs needed by RNP and RNC area planning are necessary.

For the operators with 2G networks, plan the number of RNCs, coverage area, and transmission modes based on the following conditions:

BSC traffic distribution in the 2G networks

Equipment room and transmission conditions

The prediction and analysis of traffic in the 3G network

Considering the number of existing BSCs, splitting or combination

For new operators, their RNC area planning proceeds as below.

2008-12-17



7.1.1 Flow for RNC Area Planning

For New Operators Without 2G Networks

RNP engineers estimate the number of RNCs by the following collected and estimated aspects:

Traffic

The number of NodeBs

The number of cells

Throughput at interfaces

Type of interfaces

RNP engineers determine the RNC area according to following aspects:

The number of RNC and the coverage square

Cell square

Geographical and administrative division

Operator's opinion

Figure 7-1 shows the flow for RNC area planning.

2008-12-17



Figure 7-1 flow for RNC area planning for the operators without 2G networks

RNP engineers estimate the number of NodeBs, coverage square of cell, and network traffic by the following collected information:

Traffic

The number of subscribers

Coverage square

Transmission interfaces

GoS

Propagation information

After the RNP engineers estimate the number of NodeBs, coverage square of cell, and network traffic, they estimate the number of RNCs. According to the operator's requirements, in consideration of transmission cost, equipment room cost, and administrative division, determine the number of RNCs and RNC area, and finally output the RNC area planning report.

For the fixed network operators with rich transmission resource, equipment rooms, and O&M human resource, such as China Telecom, the RNC area can cover or follow different administrative regions. This must be approved by the operator.

2008-12-17



For the Operators with 2G Networks

The operators with mature 2G networks know well the following information:

Traffic of BSCs in the existing networks

Traffic distribution after deployment of 3G networks

Transmission conditions of each BSC

Transmission cost

Equipment room

Based on previous information, the operators can determine the number of RNCs and RNC area.

Figure 7-1 shows the low for RNC area planning for the operators without 2G networks.

Figure 7-1 Flow for RNC area planning for the operators without 2G networks

The operator with mature 2G networks usually refers to the number of RNCs and division of RNC area, so the RNP engineers shall determine RNC areas by discussing with the operator according to dimensioning result. The division of RNC area shall be according to traffic balance principle. The RNC area is the combined areas of BSC

2008-12-17



areas of 2G network. The border for RNC area is probably the outer border of combined BSC areas.

7.1.2 RNC-related Number Planning

Restriction by RNC Performance

The scale of RNC area depends largely on the features of RNC. The following features of RNC has great impact on the scale of RNC area:

Capacity supported by RNC (number of equivalent subscribers, and the number of CEs)

The number of E1 links at the Iub interface provided by RNC

The number of cells supported by RNC

The number of NodeBs supported by RNC

After obtaining the number of NodeBs, the number of cells, and capacity of each cell in a local network by network dimensioning, RNP engineers then plan the RNC area.

The specifications of Huawei BSC6800 (RNC) are as below:

A subrack support 300 cells, and 4800 cells at most.

A subrack support 100 NodeBs, and 1600 NodeBs at most.

Huawei BSC6800 supports 1,000,000 subscribers at most and a traffic of 40,000 Erlang.

Huawei BSC6800 supports a maximum throughput rate of 960 Mbps.

Huawei BSC6800 supports 64 STM-1 (ATM over SDH) + 1024 E1/T1(WLPU+WBIE) or 64 STM-1 (ATM over SDH) + 32 Channelized STM-1 (ATM over E1 over SDH) +256 E1(WLPU+WOSEc) or support 16 STM-4 (ATM) mode (WLPU)

Based on the specifications of BSC6800, the process for dimension the number of RNCs is as below:

Step 1 Calculate the number of RNCs by the capacity supported by RNC (number of equivalent subscribers, quantity of Erlang, or the number of CEs)

According to the previous specifications of RNC, an RNC supports a maximum traffic of 40,000 Erlang, or 40,000 voice subscribers, or 40,000 CEs.

Based on the number of equivalent voice subscribers to be supported by RNC provided in planning, calculate the number of RNC to be configured RNC_1:

2008-12-17



RNC_1 = the number of equivalent voice subscribers to be supported/40000

Or, based on quantity of Erlang to be support, the RNC_1 is as below:

RNC_1 = quantity of Erlang to be supported/40000

Or, based on the number of CEs to be supported, the RNC_1 is as below:

RNC_1 = the number of CEs to be supported/40000

Step 2 Calculate the number of RNCs by the number of E1 links to be provided by Iub interface

According to the previous specifications of RNC, an RNC supports 1024 E1 links and 64 STM-1 at most. When converted to E1, an STM-1 is equivalent to 63 E1 links. With the number of E1 links to be supported at the Iub interface, RNP engineers can calculate the number of RNCs to be configure, RNC_2, as below:

RNC_2 = the number of E1 links to be supported at the Iub interface/5056

Step 3 Calculate the number of RNCs by the number of cells to be supported

According to the previous specifications of RNC, an RNC supports 4800 cells at most. With the number of cells to be supported by RNC according to planning, RNP engineers can calculate the number of RNCs to be configured, RNC_3, as below:

RNC_3 = the number of cells to be supported/4800

Step 4 Calculate the number of RNC by the number of NodeBs to be supported

According to the previous specifications of RNC, an RNC supports 1600 NodeBs at most. With the number of NodeBs to be supported by RNC according to planning, RNP engineers can calculate the number of RNCs to be configured, RNC_4, as below:

RNC_4 = the number of cells to be supported/1600

Step 5 The determined the number of RNCs is MAX {RNC_1, RNC_2, RNC_3, RNC_4}.

----End

Restriction by Administrative Regions

The scale of RNC area also depends on the organizational structure of the operator's network. Operators usually divide the network by administrative regions, and the

2008-12-17



planning of RNC area shall be consistent with the organizational structure of the operator's network. After adequate communication with the operator, plan and design RNC area according to the structure of the operator's network.

Generally, the RNC is part of the local access network (LAN). An RNC seldom serves different LANs, so the scale of RNC area also depends on the administrative region. Though an RNC can support higher capacity or more cells, it can only serve as a radio network controller of LAN, and serve an administrative region of certain level. This usually occurs in the area with medium and low capacity and plenteous capacity of RNC.

Restriction by Transmission Interfaces

A WCDMA network provides abundant high-rate data services as an advantage, so the required transmission resource at the Iu/Iur/Iub interface increases sharply. If the actual transmission resource provided by RNC is restricted, the capacity processed by RNC will be restricted. As a result, the scale of RNC area is restricted.

The principle for transmission resource at interfaces to restrict the scale of RNC area is as below:

Actual quantity of transmission resource at the Iu/Iur/Iub interfaces -> the number of E1 links connected to RNC -> scale of RNC area

Reservation for Network Expansion

As the WCDMA network becomes popular and new services keeps developing, the number of subscribers and required capacity keep increasing year by year. The NodeB expansion is performed by the following methods:

Increase the transmit power

Add modules

Add carriers

Split cells

The RNC expansion is performed by the following three methods.

1. Add RNC and add NodeBs, as shown in Figure 7-1.

2008-12-17



Figure 7-1 Before expansion: adding RNC and adding NodeBs

Figure 7-2 After expansion: adding RNC and adding NodeBs

Advantage: a few RNCs are necessary at the early stage. The expansion has no impact on existing NodeBs.

Disadvantage: the throughput between RNCs is high.

2. Add RNC and cut over some NodeBs

2008-12-17



Figure 7-1 Before expansion: adding RNC and cutting over some NodeBs

Figure 7-2 After expansion: adding RNC and cutting over some NodeBs

Advantage: a few RNCs are necessary at the early stage. The throughput between RNCs is low.

Disadvantage: The expansion has some impact on existing NodeBs.

3. Reserve RNC resource and add NodeBs according to original planning of RNC area

2008-12-17



Figure 7-1 Before expansion: reserving RNC resource and adding NodeBs according to original planning of RNC area

Figure 7-2 After expansion: reserving RNC resource and adding NodeBs according to original planning of RNC area

2008-12-17



At the early stage of network construction, the hardware or software license configuration has not reached the maximum, so RNP engineers can expand the network by increasing software capacity or adding hardware.

Advantage: The expansion has no impact on existing NodeBs. The throughput between RNCs is low.

Disadvantage: Excessive RNCs are necessary at the early stage.

According to previous analysis, the third scheme is best to avoid the following aspects:

RNC expansion and NodeB expansion have impact on the existing network.

Service interruption occurs due to NodeB cutover.

Excessive inter-RNC handovers and throughput at the Iur interface exist.

When dimensioning RNC area, according to the prediction of growth of subscribers and capacity in the following years, reserve resource for network expansion. After approved by the operator through communication, dimension the number of RNCs according to the maximum capacity/number of cells/number of NodeBs/number of E1 links in the following years.

7.1.3 Principles for RNC Area Planning

Continuous Coverage Principle

When planning an RNC area, follow the continuous coverage principle by dividing all the cells in an area of continuous coverage into the same RNC. Avoid mixed coverage for RNC area planning. The continuous coverage avoids edge cells, so it has the following advantages:

Reduce the inter-RNC handovers.

Improve handover success rate.

Reduce the inter-RNC signaling and data throughput.

Maximize the effect of RRM algorithms.

Improve the satisfaction of subscribers.

2008-12-17



Figure 7-1 RNC are planning: continuous coverage

Figure 7-2 RNC are planning: non-continuous coverage

Principle of Reducing Inter-RNC Signaling and Data Throughput

In RNC area planning, utilize environment factors as possible to:

Reduce the inter-RNC signaling and data throughput

Avoid frequent inter-RNC soft handovers (SHOs)

If there are two or more RNC areas in a city with heavy traffic, RNP engineers can separate these RNC areas with the downtown mountains or rivers. This can reduce the overlapped area of different RNC areas. If there is no mountain or river, RNP engineers shall not separate RNC areas with streets and the borders of two RNC areas shall not be over a heavy-traffic buildings or spots (such as shopping centers).

The borders of RNC areas shall usually not be parallel or vertical to streets, but cross with streets obliquely. In the borders of urban and suburban areas, the borders of RNC areas are usually set at the outer low-traffic NodeBs in suburban areas, but not overlapped with the conjunction areas of urban and suburban area. This avoids frequent inter-RNC SHOs.

2008-12-17



Traffic Balance Principle

If there are two or more RNC areas in a city with heavy traffic, RNP shall keep the number of cells under the RNCs and traffic balanced upon RNC area planning. It must be avoided that the traffic for an RNC is heavy while the traffic for another RNC is low. This avoids over heavy traffic on RNC, admission failure and call drop due to resource restriction. In addition, this lowers the probability of equipment failure under heavy traffic.

Figure 7-1 RNC area planning: traffic balance

Figure 7-2 RNC area planning: traffic imbalance

Principle of Reducing Inter-subrack Handover

Inside an RNC, the inter-subrack throughput includes two parts as below:

The throughput irrelevant to services but for keeping multiple subracks running (not to be discussed here)

The throughput for services and by configuration

If the configuration is improper, the paging information will be lost, the handover will fail, or the service frames will be discarded. As a result, the BLER of

2008-12-17



services is affected and system capacity drops. Pay attention to these points in network planning.

The cause to RNC inter-subrack handover is the handover throughput and database synchronization throughput because that the cells configured to different subracks are neighbor cells to each other. To reduce the handover throughput, configure the neighbor cells (NodeB) with heavy traffic in the same subrack and reduce the unnecessary neighbor cells. Namely, do not configure the neighbor NodeBs with heavy traffic and abundant subscribers in different subracks. If there are two or more RNC areas in a city with heavy traffic, refer to the Traffic Balance Principle.

RNP engineers can separate these RNC areas with the downtown mountains or rivers. This can reduce the overlapped area of different RNC areas. If there is no mountain or river, RNP engineers shall not separate RNC areas with streets and the borders of two RNC areas shall not be over a heavy-traffic buildings or spots (such as shopping centers). The borders of RNC areas shall usually not be parallel or vertical to streets, but cross with streets obliquely.

7.2 Paging Area Planning

Paging area planning concerns LA/RA/URA configuration, it also plans the page type 1 capacity of whole network. When the UE is in the idle mode, the paging message for CS services is sent to all the cells in a location area (LA), and the paging messages for PS services are sent within the whole routing area (RA). When the UE is in the connected mode URA_PCH, the page type 1 message is sent to all the cells in the whole URA. When the UE is in the CELL_PCH mode, the page type 1 message is also sent.

If the LA, RA, or URA is configured over large, the paging channel (PCH) will be congested and paging messages will be discarded. If the LA, RA, or URA is configured over small, there will be excessive location update messages. As a result, the CCH capacity is affects, and thus the network capacity declines.

If an operator with a 2G network wants the 2G network and the 3G network to supplement each other, or the operator wants the two networks to share load or wants subscribers can hand over from the two networks, the LA and RA configuration must be consistent or in special consideration. Otherwise, the UE will hand over between the two networks frequently after inter-RAT reselection and handover. As a result, the network capacity is affected and call drops easily.

The following paragraphs describe the flow for paging area planning, planning principles, and planning methods.

2008-12-17



7.2.1 Flow for Paging Area Planning

For the Operators Without 2G Networks

Figure 7-1 shows the flow for paging area planning for the operators without 2G networks.

Figure 7-1 Flow for paging area planning for the operators without 2G networks

The process for paging area planning for the operators without 2G networks is as below:

Step 1 Input the information from dimensioning into the tool for dimensioning paging area.

Step 2 Dimension to obtain the scale of paging area.

Step 3 Obtain the final scale of paging area according to the following aspects:

2008-12-17



Administrative region

Population density

2G traffic of other operators

Principle of paging area planning

Operator's opinion

Step 4 Output paging area planning report.

----End

For the Operators with 2G Networks

Figure 7-1 shows the flow for paging area planning for the operators with 2G networks.

2008-12-17



Figure 7-1 Flow for paging area planning for the operators with 2G networks

For the operators with 2G networks, there is requirement from coexistence of 2G and 3G networks on the configuration of paging area. If some 2G operators want to construct the 3G network completely at a time, not prepared for 2G further expansion or maintenance, they do not have to consider the coexistence problem. If the 3G network is constructed with the 2G network and subscribers may hand over between the two networks, the cooperation of 2G and 3G networks must be considered in configuration of paging area.

When performing area planning for the 3G operators with 2G networks, RNP engineers can refer to the configuration of 2G LA and RA, or combine paging areas according to BSC traffic. In addition, keep the border of 3G paging areas consistent with the border of 2G paging areas. This avoids frequent inter-RAT handover and area update after reselection.

7.2.2 Principles for Paging Area Planning

The principles for paging area planning are as below:

2008-12-17



Ensure that PCH capacity is not restricted.

Minimize the overheads of location update at the borders of paging area.

Be easily managed.

Principles for LA Planning

Traffic distribution should be considered to determine the scale of LA.

The paging messages from the network to the UE are sent in all the cells of LA, so over large coverage range of paging area will lead to over heavy load for PCH and the signaling at the Iub interface will increase. In addition, if overload paging messages are not sent within the resend times of RNC, they will be discarded. As a result, when the UE is powered on in the service area, it cannot be paged (the subscriber is not in the service area).

The scale of paging area (maximum number of cells supported) mainly depends on the bandwidth of PCH. The scale of LA should be based on the result of paging area dimensioning. To simplify paging area planning, estimated LA sizes for different user number distribution are given in Table 7-1 for reference.

Table 7-1 LA size estimation

Users per cell LA size (cell)

1500 or more 150

1200 200

900 280

600 410

300 or less 850

At the early stage of network construction, the traffic is low with other unknown factors, so the network is usually expanded or adjusted. As a result, adjusting LA is normal. If the LA is over small, the overheads for location update will be large and the load supported by system will decline. If the LA is over large, the paging load will be over heavy.

Divide LA by minimizing the overheads of location update at the edge of LA as possible and by following geographical distribution.

When non-continuous coverage is in suburban, it is probable that the UE fails to have location updated at the time for location update. After the protection time expires (configured in MSC), the system judges IMSI implicit detach. If the subscriber moves into urban area of which the LAC is consistent with the

2008-12-17



suburban LAC, the UE will not have location normally updated immediately, so the UE can receive signals but are not in the service area.

According to previous reason, in LA assignment, a suburban area (county) uses an independent LA, different from urban LA. The distribution of Las is like a concentric circle (the urban area in the inner circle may contain several LAs. In side the circle, there may be clusters, or another inner circle, or the mixture of previous two modes), and it can effectively avoids the previous phenomenon.

According to tests, dividing Las in this way can avoid the subscribers being out of service area and improve call setup rate and paging success rate, as shown in Figure 7-2.

Figure 7-2 Dividing LAs

If there are two or more LAs in a city with heavy traffic, RNP engineers can separate these LAs with the downtown mountains or rivers. This can reduce the overlapped area of different LAs. If there is no mountain or river, RNP engineers shall not separate LAs with streets and the borders of two LAs shall not be over a heavy-traffic buildings or spots (such as shopping centers).

The borders of LAs shall usually not be parallel or vertical to streets, but cross with streets obliquely. In the borders of urban and suburban areas, the borders of LAs are usually set at the outer low-traffic NodeBs in suburban areas, but not overlapped with the conjunction areas of urban and suburban area. This avoids frequent location updates.

If the operators with complete 2G networks prepare to construct a UMTS network, they can refer to the LA planning of 2G networks, especially the borders of Las. The capacity of 3G RNC is usually higher than that of 2G BSC, so the

2008-12-17



number of needed RNCs is smaller than that of needed BSCs. The LA seldom crosses different BSC areas.

When planning 3G Las, consider the configuration of 2G LA and BSC traffic in existing network. According to the principle of traffic balance, the 3G LA can be the combination of 2G Las. The borders of 3G Las needs to be consistent with the borders of 2G LA after combination as possible.

Principle that LA cannot cross MSC area and RNC area

According to protocols, when several mobile switching centers (MSCs) share a VLR, the LA can cross MSC area. In actual networks, an MSC is usually connected to a VLR, so the LA can cross different RNC areas but not MSC areas.

In actual networks, if an LA/RA crosses multiple RNC areas, the paging message will be sent under multiple RNCs. As a result, there is more signaling, it is more difficult to process them, the paging message is more probably congested or discarded.

If the operators with complete 2G networks construct a WCDMA network, they can refer to the borders of 2G paging area.

Principles for RA planning

The RA is the area where the SGSN can page the idle UEs. It is the paging area for PS services. Its planning and LA planning are similar, but it is contained in LA. They share a principle in common: the RA cannot be over large. The principle is closely related to the paging throughput of PS services and subscribers' behaviors.

In the future network, the paging throughput of PS services is usually heavier than that of CS services, and the RA is usually smaller than the LA. Determine the relation between RA and LA according to the ratio of PS and CS paging throughput. It is thought that RA is as large as LA, and RA shall not cross SGSN/RNC/LA areas. It is required that the impact form RA update on the system at the borders of areas shall be reduced and the requirements on capacity restriction shall be met as possible.

Principles for URA planning

The URA is the area where the UTRAN pages the UEs that are in the URA_PCH state and have subscribed PS services. It is usually realized that the UEs in the CELL_PCH state transit to the URA_PCH state after K cell updates. The configuration of URA is closely related to subscribers' behaviors. Figure 7-3 shows the relation among URA, RA, and cell.

2008-12-17



Figure 7-3 Relation among URA, RA, and cell

The URA and RA do not necessarily subject to each other, so configure URA according to dimensioning result at the early stage, or make URA the same as RNC area or divide URA inside the administrative region covered under a RNC. When the WCDMA network is mature, and online services and UE states are clear, the URA can be configure the same as RA, so a URA can be as large as an RA.

7.3 SA Planning

The SA is contained in an LA. It may contain one or more cells. Of course, a cell can have multiple SAs. The CN knows the area and charging of UE by SA. The SA is relevant to the location and charging of UE. If the SA is not configured, the services cannot be used.

An LA is usually configured with two SAs, such as one for broadcast domain and the other for CS and PS services. These two domains can be combined as one. The configuration of SA will not change the throughput and capacity of access network of UTRAN.

2008-12-17



7.4 Cell cluster planning

The division of cell clusters means dividing the whole network into groups of sites. Site survey, drive test, optimization, and coverage acceptance are usually performed according to or by reference to the division of cell clusters.

Owing to the technical characteristics of the UMTS, RF optimization should be performed for all NodeBs in a cluster, instead of a single NodeB so that the interference between intra-frequency neighboring cells can be considered. In addition, the division of cell clusters facilitates the task division at the network planning and optimization phases.

The division of cell clusters should be confirmed with the customer. When cell clusters are divided, the following factors should be considered:

Based on the previous experience, it is recommended that the number of NodeBs in a cluster should be 15 to 25, but not be too large or too small.

A cell cluster should not cover different areas used for testing (planning) the complete coverage service.

The division of cell clusters can be performed with reference to the existing cell cluster of the network operator for network engineering maintenance.

Effect of terrain factors: Different terrains and relieves affect the signal propagation. Mountains prevent signals from being propagated and are natural boundaries of cell clusters. Rivers allow radio signals to travel a longer distance and has many-sided effect on the division of cell clusters. If a river is narrow, the mutual effect between signals on both banks of the river should be considered. If the traffic condition permits, the sites on both banks should be in the same cluster. If the river is wide, the mutual effect between the upstream and the downstream should be concerned; in this case, it is very inconvenient to travel between the two banks and cell clusters should be divided on the basis of the river course.

Generally, a cellular cell cluster is more common than a strip cell cluster.

Principles for administrative division: When the network to be optimized covers multiple administrative regions, the division of cell clusters based on administrative division is more acceptable to the customer.

Effect of drive test workload: At the time of cell cluster division, it should be considered that drive tests in each cell cluster can be completed in a day. Generally, it should take fours to perform a drive test.

As the drive tests of most projects and even KPI acceptance are based on a cluster, a large cell cluster is good for the project to pass tests and acceptance. In a complex scenario (for example, there are only three to five sites in a densely populated urban

2008-12-17



area and suburb or rural areas surround the urban area), a large cell cluster makes it difficult to determine the KPIs. In this case, a small cell cluster is recommended. The same type of clusters with the number of sites less than stipulated can be combined when tests and acceptance are performed.

The following gives an example of the division of cell clusters in a project. JB03 and JB04 are densely populated urban areas, JB01 is a highway coverage area, JB02, JB05, JB06, and JB07 are general urban areas, and JB08 is a suburb area. There are about 18 to 22 NodeBs in each cell cluster.

Figure 7-1 Division of cell clusters in a project

2008-12-17



8 Neighbor Cell Planning

8.1 Analzying Neighbor Cell Planning

The neighboring cell information affects the handover of a UE in the connected state and cell selection/reselection. However, when neighboring cells are planned, the analysis object is usually CELL_DCH handover. In the CELL_DCH state, when the radio environment changes due to UE movement or other reasons, the quality of the radio link that bears the service also changes. To maintain or improve the link quality, the UE and the RAN perform a series of operations such as adding, deleting or changing a radio link. Figure 8-1 shows the basic handover process.

Effect of neighboring cell information on the handover process: If the neighboring cell information is incomplete (namely, a high-quality cell the UE is to be handed over to is not in the neighboring cell list), the UE cannot be handed over to the cell. As a result, the handover fails and the quality of the radio link keeps deteriorated until the service is interrupted.

The initial neighboring cell information that is output at the planning phase is mainly used for network construction and neighboring cell information configuration at the preliminary phase of deployment to ensure the basic service quality. The design considerations are mainly based on the radio environment (including propagation environment and antenna parameters). At the radio network construction and maintenance phases, neighboring cell information needs to be continuously optimized based on service development and the change in the environment.

A new network generally involves the planning of intra-frequency neighboring cells of a single frequency (fundamental frequency) and possible inter-system neighboring cell planning. With the network development, there are multiple frequencies. Therefore, the intra-frequency neighboring cell planning of the second and third frequencies, inter-frequency neighboring cell planning between frequencies, and inter-system neighboring cell planning are involved. This section describes the principles for and

2008-12-17



the process of the neighboring cell planning for the construction and expansion of a network with multiple frequencies and systems. As the application of a hierarchical network is rare in reality, this section does not discuss the neighboring cell planning of a hierarchical network.

Figure 8-1 Basic handover process

UE RNCMeasurement Control

Neighbor Cell Information

Perform Measurement

Period or Event Report

Handover Decision

Handover Command

Perform Handover

Handover Completed

8.1.1 Principles for Neighbor Cell Planning

The WCDMA neighboring cell planning involves intra-frequency soft/hard handover neighboring cell, inter-frequency handover neighboring cell, and inter-system handover neighboring cell. The following principles should be considered for neighboring cell planning:

Set intra-frequency neighborhood for the cells that have an overlapping coverage.

Plan the inter-frequency neighborhood with reference to the intra-frequency neighborhood and the specific inter-frequency handover strategy.

Assume that the inter-frequency cells in a sector have the same coverage.

Plan the inter-system neighborhood in the assumed handover zone according to the inter-system handover strategy. When planning inter-system neighborhood, assume that 2.1G/1.9G/1.8G cells in a sector have the same coverage, and a 2.1G cell covers less than a 900M cell.

2008-12-17



Set neighborhood for cells that share a site but belong to different sectors.

Set bidirectional neighborhood for cells in which intra-frequency neighborhood exists.

Set unidirectional or bidirectional neighborhood for inter-frequency/inter-frequency neighborhood according to the handover strategy.

The number of intra-frequency/inter-frequency/inter-system neighboring cells cannot exceed 31.

To avoid too many initial neighborhoods, control the number of intra-frequency/inter-frequency/inter-system neighboring cells within 10 to 20, if the neighboring cell combination algorithm switch is enabled in the network, or within 15 to 25, if the neighboring cell combination algorithm switch is disabled in the network.

Neighboring cells of a cell are not distinguished in preference.

8.1.2 Analzying Intra-frequency Neighbor Cell Planning

When a radio network is constructed, carriers are configured in overlay mode. That is, the first carrier is configured at first to implement the basic service coverage. With the service development, the second carrier and/or the third carrier are added to meet the requirements of new services and the capacity. Accordingly, intra-frequency neighboring cell planning involves two scenarios: fundamental frequency (first carrier) and non-fundamental frequencies (second carrier and third carrier).

The intra-frequency neighboring cells of the fundamental frequency are planned according the coverage forecast and distance analysis. The fundamental principles are as follows:

Consider a certain range of a NodeB (for example, 10 km in an urban area and 20 km in a suburb area) as a neighboring cell planning area. Within the area, mark horizontal or vertical grids at an interval of a specific distance (for example, 20 m, 50 m or 100 m) to obtain a node list {Jn}.

At node Jn, calculate the coupling losses from surrounding cells (use a propagation model with the height between the NodeB and the ground considered, neglect the clutter because no digital map is available, consider the height, azimuth, down-tilt, and pattern of the antenna) and sort the coupling losses in ascending order. Within a certain threshold (for example, 6 dB) below the maximum, neighborhood is considered existing between related cells.

For any cell Ci, count the neighboring cell pairs in the node list {Jn} and the occurrences of each neighboring cell pair in the node list {Jn}. Sort the occurrences of each neighboring cell pair in descending order to determine the priority and select the first n neighboring cells.

2008-12-17



Sort the neighboring cells according to the site distance and select the nearest m neighboring cells.

The final output result is the union of the set {n} and the set {m}. The thirty-second and subsequent neighboring cells need to be deleted.

Plan the intra-frequency neighboring cells of a non-fundamental frequency in two steps. First add neighboring cells of a non-fundamental frequency in the same coverage according to the intra-frequency neighborhood of the fundamental frequency. Then, add the neighboring cells of the non-fundamental frequency according to the coverage forecast and distance analysis. The fundamental principles are as follows:

For cell A1 of the fundamental frequency F1, the intra-frequency neighboring cell set is A1_intra_NB{B1, C1, D1…}.

For cell A2 of non-fundamental frequency F2 in the same sector, if cell B2 of frequency F2 in the sector of B1 exists, B2 and A2 are neighbors, that is, B2ЄA2_intra_NB. Judge other cells in the A1_intra_NB set in a similar way.

Determine whether cells C2 and D2 of frequency F2 in the same sector are intra-frequency neighboring cells of A2. If C2 does not exist, determine whether to configure inter-frequency neighborhood from A2 to C1 according to the inter-frequency handover measurement. For details, see section "Analysis of inter-frequency neighboring cell planning".

According to the coverage forecast and distance analysis, add other neighboring cells to the intra-frequency neighboring cell set A2_intra_NB. For the steps, see step a) to step e) in neighboring cell planning for the fundamental frequency.

8.1.3 Analzying Inter-frequency Neighbor Cell Planning

Plan inter-frequency neighborhood according to the specific inter-frequency handover strategy and the intra-frequency neighborhood of incoming inter-frequency handover frequency. The fundamental principles are as follows:

If the coverage areas of inter-frequency cells in the same sector of a site are the same, a handover between these inter-frequency cells is called a vertical handover, and a handover from cell B2 of a frequency to intra-frequency neighboring cell A1 of inter-frequency cell B1 that is in the same sector of B2 is called slope handover in this document.

According to the analysis of the inter-frequency handover strategy, plan neighboring cells for vertical handovers and slope handovers, separately. If a vertical handover is required from frequency F1 to frequency F2, for any cell B1 of F1, as long as cell B2 of F2 in the same sector exists, configure a unidirectional neighboring cell or bidirectional neighboring cells from B1 to B2. If a slope handover is required from F2 to F1, for any cell B2 of F2, as long as the intra-frequency neighboring cell set

2008-12-17



B1_intra_NB{A1, C1, …} of B1 of F1 in the same sector exists, configure all cells in the set as inter-frequency neighboring cells of B2. The figure below shows a typical inter-frequency handover scenario.

Figure 8-1 Typical inter-frequency handover scenario

F1

F2

F3

Cell A1 Cell B1 Cell C1

Cell B2 Cell C2

Cell B3

Vertical Handover

Slope Handover

F1

F2

F3

Cell A1 Cell B1 Cell C1

Cell B2 Cell C2

Cell B3

Vertical Handover

Slope Handover

8.1.4 Analzying Inter-RAT Neighbor Cell Planning

At the early stage of WCDMA network construction, the WCDMA network may coexist with GSM or CDMA2000 networks, so configuring inter-RAT neighbor cells for WCDMA cells is necessary.

The inter-RAT neighbor cell planning focuses on the inter-RAT reselection and handover of UE. RNP engineers usually configure the 2G neighbor cells near WCDMA cell as inter-RAT neighbor cells. If engineers do not want UE to hand over to or reselect 2G cells, do not configure the 2G cell as neighbor cell. However, configuring these 2G cells as inter-RAT neighbor cells is recommended with different relative handover threshold configured. In this way, the UE can obtain the measurement reports of these 2G cells and flexibly control handover.

In addition, at the early stage of WCDMA network construction, there may be only 2G signal covering indoor areas or subway. To ensure continuous coverage, configure these 2G cells as neighbor cells for corresponding 3G cells.

8.2 Process for Neighbor Cell Planning

The cell neighbor allocation (CAN) tool developed by the UMTS network planning department is used for intra-frequency and inter-frequency neighboring cell planning in the case of network construction or network expansion. In some scenarios, the tool also supports the inter-system neighboring cell planning. The major characteristics of the CAN V1.11 include:

2008-12-17



Support for the initial neighboring cell planning for intra-frequency and inter-frequency handover in a new network or expanded network

Support for a customized inter-frequency handover strategy file to adapt to different handover scenarios

Support for check for the absence of intra-frequency and inter-frequency neighboring cells of F2 and F3 based on existing neighboring cells of F1 (fundamental channel No.) in accordance with the inter-frequency same-coverage principle.

Validity check of input data

Import of neighboring cell information and generated file discrimination by RNC

The CNA helps you to quickly and efficiently complete the initial neighboring cell planning in different scenarios in radio networks in various scales. For the instructions, refer to the How to Use the Neighbor Cell Planning Tool CNA in the tool release package.

8.2.1 New network mode

The major steps for neighboring cell planning in a new network are as follows:

Parameter settings: Determine the major configurations (including planning precision, handover zone threshold, maximum number of neighboring cells planned based on the path loss, and maximum number of neighboring cells planned based on distance analysis) in the CNA_config.txt file and define a channel Nos. and inter-frequency handover strategy file.

Data preparation: Prepare the engineering parameter data, antenna pattern file, and parameter file of the propagation model according to the instructions.

Planning adjustment: Execute the program, analyze the planning results, and make proper adjustments.

Parameter settings

The following default values are recommended in the CNA_config.txt file:

[1]Calculated_bin_size[m]=: 30

[2]Calculated_SHO_threshold[dB]=: 6

[3]MaxIntraFreqNBCellsbyCPL=: 12 (neighboring cells are not combined)/9(neighboring cells are combined)

[4]MaxIntraFreqNBCellsbyDistance=: 8 (neighboring cells are not combined)/6(neighboring cells are combined)

The smaller Calculated_bin_size is, the higher the precision. A high precision means a slow planning progress. In the case of planning based on areas, Calculated_bin_size is recommended to be 20 m, 30 m, 50 m, and 100 m in a densely populated urban area, ordinary urban area, suburb area, and rural area, respectively. If no area is divided, Calculated_bin_size is recommended to set to 30 m or 50 m.

2008-12-17



Set the channel Nos. and inter-frequency handover strategy file according to the network situation. For example, channel No. F1 10589 is constructed to bear the R99 service at the early phase of a network, channel No. 10564 F2 and channel No. 10614 F3 are later activated to bear the HSPA service. Handovers from F3 to F2 and from F2 to F1 at the edge of coverage and inter-frequency same-coverage handovers between F1 and F2 and between F2 and F3 are allowed. Accordingly, the definition is shown in the figure below.

Figure 8-1 Channel No. and inter-frequency strategy file

If the neighborhoods of the cells, involved in an inter-frequency and same-coverage handover from F1 to F2 or from F2 to F3, need to be screened to add a blind handover flag, clear the contents under Slope_Handover in the strategy file shown in the preceding figure and plan only the contents under Vertical_Handover.

Data preparation

The three figures below show the engineering parameter data template file, the antenna pattern file, and the propagation model parameter file, respectively.

2008-12-17



Figure 8-2 Engineering parameter data template file

Figure 8-3 Antenna pattern file

2008-12-17



Figure 8-4 Propagation model parameter file

Note: 1) The electrical tilt of an antenna should be configured according to the corresponding antenna pattern file and the antenna manufacturer should provide the antenna pattern files for the antennas with various electrical tilts. 2) Currently, only the propagation model SPM is supported. For the conversion from the Cost-Hata or SMM to the SPM, refer to the W–Radio Propagation Model Application Guide.

Planning adjustment

Run the CNA tool in command line mode. Each step and the result can be seen. During planning, the CNA tool outputs the planning results. For the convenience of importing the planning results to the parameter configuration tool, the planning results are output to different files by RNC and intra-frequency/inter-frequency, and the statistics results are output to different files by channel No. and intra-frequency/inter-frequency.

The intra-frequency neighboring cell data of the fundamental channel No. F1 are the analysis objects of the planning phase. The number of neighboring cells of each cell can be seen from the statistics results. To avoid too many initial neighborhoods, control the number of intra-frequency neighboring cells within 10 to 20 if the neighboring cell combination algorithm switch is enabled in the network, or within 15 to 25 if the neighboring cell combination algorithm switch is disabled. If the average number of neighboring cells in the whole network is too large or small, you can adjust the number by changing MaxIntraFreqNBCellsbyCPL and MaxIntraFreqNBCellsbyDistance. After the average number of neighboring cells complies with the requirements, you can sample the rationality of neighboring cells or identify them one by one on the map and add or delete neighboring cells, if necessary.

2008-12-17



Figure 8-5 Run the CNA tool

Engineering construction mode

For a new network, neighboring cell planning is completed before engineering construction and the output of neighboring cell planning is a whole-network neighboring cell list. When a cell is activated, neighboring cells are configured for it according to the whole-network neighboring cell list. In engineering construction, sites are not activated at the same time. This affects data configuration. For example, a neighborhood exists between A and B, and between B and C in neighboring cell planning. In the engineering construction, cell A and cell C may be first activated and no data is configured for cell B. In this case, a neighborhood from A to B or from C to B cannot be configured. You can define the engineering parameter data file, specify the cell list cellupdate.txt, apply the engineering construction mode, and use the command line parameter /e to screen and export the neighborhoods in the planned neighboring cell set of cells to be activated as well as neighborhoods of all activated cells. If the whole-network neighboring cell file is considered as a mosaic, neighboring cell pairs are small blocks. The parameter e/ takes the corresponding blocks and configures them in the RNC according to the site construction progress until the

2008-12-17



complete mosaic is formed. During this period, no redundant neighborhood between A and C is generated. Since the network quality is not focused on at the early time of engineering construction, the use of the parameter e/ can avoid incorrect parameter configuration and a large amount of redundant neighboring cells. At the time of optimization, you are recommended to apply the expansion mode and use the /u parameter for neighboring cell planning.

8.2.2 Mixed expansion mode

Mixed expansion affects the neighborhoods of the existing network in two aspects. On the one hand, the neighborhoods of a new cell with other new cells and the original cells make the number of neighboring cells increase. On the other hand, the effect of new cells on the original neighborhoods makes the number of neighboring cells decrease (for example, after multiple sites are set up between two original neighboring cells, the original neighborhood does not exist).

It is generally considered that the neighborhoods of the existing network are optimized and are perfect relative to the planning results made by the tool. Therefore, the fundamental principles for neighboring cell planning in mixed expansion mode are as follows: Only incremental cells are planned but none of original neighboring cells of the existing network are deleted. Based on the planning results, network planning/optimization engineers perform further analysis to determine whether neighborhoods should be added or deleted.

The steps for neighboring cell planning in mixed expansion mode are as follows:

Parameter settings: Determine the major configurations (including planning precision, handover zone threshold, maximum number of neighboring cells planned based on the path loss, and maximum number of neighboring cells planned based on distance analysis) in the CNA_config.txt file and define a channel Nos. and inter-frequency handover strategy file.

Data preparation: According to the instructions, prepare the existing network neighboring cell file and the cell update file besides the engineering parameter data, antenna pattern file, and propagation model parameter file.

Planning adjustment: Execute the program CNA/u, analyze the planning results, and make proper adjustments.

Parameter settings

See parameter settings in "Neighboring cell planning in new network mode"

Data preparation

Besides the data for a new network, prepare the existing network neighboring cell file and the cell update file. The figure below shows the cell update file.

2008-12-17



Figure 8-1 Cell update file

Planning adjustment

In the case of neighboring cell planning in mixed expansion mode, use the expansion mode and /u parameter. Run CNA/u. After initialization, the tool analyzes the new cells and determines the channel Nos. whose intra-frequency/inter-frequency neighboring cells need to be updated. After that, the tool imports the intra-frequency/inter-frequency neighboring cell files of this entire channel Nos., and updates the intra-frequency/inter-frequency neighboring cells of the corresponding channel Nos. based on the analysis results of the new cells.

2008-12-17



Figure 8-2 Run the expansion mode of the CNA

Comparison between the application modes

Table 8-1 compares the applications of the CNA tool in new network, engineering, and expansion modes.

Table 8-1 Comparison between the application modes of the CNA tool

New Network Mode

Engineering Mode

Expansion Mode

Command Line Parameter

None /e /u

Engineering Parameters

Planned cells in the whole network

Cells activated and to be activated

Original cells and new cells

Cell Update Configuration

None –rnc id cell id + rnc id cell id

2008-12-17



8.2.3 Neighboring cell check

Since intra-frequency/inter-frequency neighboring cells of the non-fundamental channel Nos. are planned by reference to the intra-frequency neighborhoods of the fundamental channel No., the inter-frequency neighboring cells of the fundamental channel No. and the intra-frequency/inter-frequency neighboring cells of non-fundamental channel Nos. can be checked on the basis of the intra-frequency neighboring cells of the fundamental channel No. That is, run CNA/v, as shown in Figure 8-1. The intra-frequency and inter-frequency neighboring cells that are not configured are output.

The neighboring cell check function does not check the neighborhoods of the fundamental channel No., or analyze the path loss or the distance between sites. Therefore, relevant parameters are invalid. Before the check, the engineering parameter data file, intra-frequency/inter-frequency neighboring cell file of different channel Nos., and the channel Nos. and inter-frequency handover strategy file need to be prepared. After the check, a list of absent neighboring cells is output.

Figure 8-1 Run the check mode of the CNA

2008-12-17



9 Scrambling Code Planning

9.1 Analyzing Scrambling Code Planning

9.1.1 Scrambling Code Resource

Uplink scrambling codes range from 0 to 224 – 1, among them the RNC randomly selects and assigns scrambling codes to different subscribers. Therefore planning uplink scrambling code is unnecessary.

The downlink scrambling code is long subcontractor only, ranging from 0 to 218 – 1. For fast cell search, only 8192 codes are available in 512 groups. Each group has 16 scrambling codes. The first one in each group is the PSC and the residual 15 are secondary scrambling codes. Therefore, there are 512 PSCs. They are divided by 64 groups, so each group has 8 PSCs. The scrambling code planning aims to guarantee that the two cells interfering with each other and using the same frequency do not use the same PSC.

9.1.2 Planning Principles

Fundamental principle for scrambling code planning: Allocate a proper scrambling code to each cell to improve the utilization of scrambling code resources in the whole network and meet the expansion and maintenance requirements in the process of network development.

Availability

How to determine whether a scrambling code can be allocated to a cell? Theoretically, you can use a precise digital map and an accurate propagation model to obtain the predicted signal strength approximate to the actual one. Furthermore, you can evaluate the interference of intra-frequency cells allocated with the same scrambling code to determine whether the scrambling code is available. In practice, the signal loss is very large when signals travel in space. You can increase the space isolation (namely, the reuse distance) to prevent interference. Obviously, the latter method is superior to the former method in terms of cost and time. However, too long a reuse distance causes

2008-12-17



the available scrambling code resources in the planned area to be very tight until no scrambling code is available.

There are two methods of determining the reuse distance.

Give an absolute distance, for example, 10 km. This method is simple and visual but is unable to reflect the effects of the environment and site distribution on signal propagation loss and reuse distance.

Consider correlation with site distribution and propagation environment, introduce the multi-order/layer neighborhood concept, and define the areas that cannot be reused. A<->B and B<->C indicate that a neighborhood exists between A and B and between B and C, but no direct neighborhood exists between A and C. Then a second-order/layer neighborhood exists between A and C. (Note: The order indicates the logical relationship while the layer indicates the geographical relationship. Either of them applies.) If reuse in the second-order neighborhood is not allowed, cell A as well as the cells that have a direct (first-order) and second-order neighborhoods with cell A cannot be allocated with the same scrambling code. Theoretically, a high order means a long reuse distance, a large propagation loss, and a low interference probability. In a typical city environment, suppose that the distance between sites is 1 km in densely populated urban areas and 2 km in ordinary urban areas. According to the statistics, the minimum reuse distance is about 3 km in a third-order neighborhood and about 6 km in a fifth-order neighborhood. In addition, the initial neighborhood involves only layer-1 sites. After the neighboring cell combination switch is enabled, the neighboring cells of a neighboring cell join in the active set. That is, A<->B<->C<->D<->E may exist. If C is the best cell, a fourth-order neighborhood exists between A and E. Therefore, for an outdoor site, the number of orders of neighborhoods must be greater than or equal to four.

The direct definition of a reuse distance threshold is based on a single environment and uniform site distribution. The method of multi-order neighborhood unreusability considers the effects of environment differences and relative distribution of sites.

Scalability

For a cell, multiple scrambling codes meet the restraints for multi-order neighborhood unusability or the minimum reuse distance. Selecting a scrambling code is a problem that should be considered and solved to achieve allocation efficiency and scalability design in scrambling code planning. In the initial planning, preparations should be made for network expansion so that frequent adjustment to the early planning results can be avoided in subsequent planning.

The reservation of scrambling codes and the best-effort reuse can satisfy the scalability requirements of scrambling code planning.

Reservation of scrambling codes should be first considered in capacity expansion. For example, 20% to 30% of scrambling codes are reserved for a suburb area and 40% to 50% for an urban area. Reservation of scrambling codes may be applied

2008-12-17



some special scenarios. For example, scrambling codes may be reserved for a high NodeB or indoor NodeB.

Best-effort reuse means the scrambling code that has been allocated for the maximum number of times should be selected when multiple scrambling codes all satisfy the conditions. Best-effort reuse can maximize the utilization/reuse rate of a scrambling code. The allocation process is free from the effect of the total number of available scrambling codes.

Others

In a drive test, scrambling codes are the major information that optimization engineers use to identify cells. Sometimes, it is necessary to consider the effect of scrambling code allocation on the efficiency of optimization work. If this is required in scrambling code planning, the following grouping and allocation rules are recommended:

Scrambling codes in a group are sequentially allocated to intra-frequency cells in the same site.

Different scrambling code groups are allocated to neighbor sites (neighborhoods exist between cells in the sites).

In this case, if resource reservation is required, some scrambling code groups and several scrambling codes in the unreserved groups can be reserved for capacity expansion, as shown in the figure below.

2008-12-17



Figure 9-1 Grouping and allocation of scrambling codes

I II III IV V VI VII VIII

0 8 16 24 32 40 48 56 Cell A

1 9 17 25 33 41 49 57 Cell B

2 10 18 26 34 42 50 58 Cell C

3 11 19 27 35 43 51 59

4 12 20 28 36 44 52 60 Cell A

5 13 21 29 37 45 53 61 Cell B

6 14 22 30 38 46 54 62 Cell C

7 15 23 31 39 47 55 63

64 72 80 88 96 104 112 120 Cell A

65 73 81 89 97 105 113 121 Cell B

66 74 82 90 98 106 114 122 Cell C

67 75 83 91 99 107 115 123

68 76 84 92 100 108 116 124 Cell A

69 77 85 93 101 109 117 125 Cell B

70 78 86 94 102 110 118 126 Cell C

71 79 87 95 103 111 119 127

128 136 144 152 160 168 176 184 Cell A

129 137 145 153 161 169 177 185 Cell B

130 138 146 154 162 170 178 186 Cell C

131 139 147 155 163 171 179 187

132 140 148 156 164 172 180 188 Cell A

133 141 149 157 165 173 181 189 Cell B

134 142 150 158 166 174 182 190 Cell C

135 143 151 159 167 175 183 191

192 200 208 216 224 232 240 248 Cell A

193 201 209 217 225 233 241 249 Cell B

194 202 210 218 226 234 242 250 Cell C

195 203 211 219 227 235 243 251

196 204 212 220 228 236 244 252 Cell A

197 205 213 221 229 237 245 253 Cell B

198 206 214 222 230 238 246 254 Cell C

199 207 215 223 231 239 247 255

A

B

C

D

I II III IV V VI VII VIII

256 264 272 280 288 296 304 312 Cell A

257 265 273 281 289 297 305 313 Cell B

258 266 274 282 290 298 306 314 Cell C

259 267 275 283 291 299 307 315

260 268 276 284 292 300 308 316

261 269 277 285 293 301 309 317

262 270 278 286 294 302 310 318

263 271 279 287 295 303 311 319

320 328 336 344 352 360 368 376

321 329 337 345 353 361 369 377

322 330 338 346 354 362 370 378

323 331 339 347 355 363 371 379

324 332 340 348 356 364 372 380

325 333 341 349 357 365 373 381

326 334 342 350 358 366 374 382

327 335 343 351 359 367 375 383

384 392 400 408 416 424 432 440

385 393 401 409 417 425 433 441

386 394 402 410 418 426 434 442

387 395 403 411 419 427 435 443

388 396 404 412 420 428 436 444

389 397 405 413 421 429 437 445

390 398 406 414 422 430 438 446

391 399 407 415 423 431 439 447

448 456 464 472 480 488 496 504

449 457 465 473 481 489 497 505

450 458 466 474 482 490 498 506

451 459 467 475 483 491 499 507

452 460 468 476 484 492 500 508

453 461 469 477 485 493 501 509

454 462 470 478 486 494 502 510

455 463 471 479 487 495 503 511

G

H

E

F

After applying the preceding rules, engineers can determine whether related cells belong to the same site according to the continuity of scrambling codes. This helps engineers to analyze and solve problems. Besides, new allocation restraints are added. As a result, more scrambling codes are required and resource utilization is reduced. These rules are recommended only for small- and- medium-scaled networks. For a large-scale network with thousands of cells, these rules may result in allocation failures.

For the cells in the same sector of a multi-frequency network, the same scrambling code is preferred.

The general evolution process is that HSPA F2 is added to R99 F1 and that F1 is activated before F2. In consideration of the maintenance and optimization requirements, the same scrambling code is recommended for inter-frequency cells in the same site. As the neighborhoods of cells of F2 are not completely consistent with

2008-12-17



those of F1, scrambling codes allocated to cells of F1 are first allocated. If the allocation fails, scrambling codes are automatically allocated.;

9.2 Process for Scrambling Code Planning

Scrambling code planning is a process of seeking for the minimum set of scrambling codes to achieve the planning target and agree with the planning principles in a specific scenario. The scenario can be a new network, mixed expansion, or scrambling code optimization.

The scrambling code planning tool SCP developed by the UMTS network planning department can help you to quickly and accurately complete scrambling code planning in multiple scenarios, for example, scrambling code allocation in a network or expanded network, and check and optimization of scrambling codes in the existing network. For details about how to use of the SCP, refer to the updated manual How to Use the Scrambling Code Planning Tool SCP released together with the tool.

9.2.1 New network mode

The major steps for scrambling code planning in a new network are as follows:

Parameter settings: Determine the major configurations (namely, the nth-order neighborhood, the minimum reuse distance, and the total number of scrambling codes that can be allocated) in the SCP_config.txt file.

Data preparation: According to the instruction manual, prepare the engineering parameter data file cellinfo.txt and the neighboring cell file cellneighbor.txt.

Planning adjustment: Execute the program, analyze the planning results, and make proper adjustments.

Parameter settings

Use the following defaults in the SCP_config.txt file and run the SCP tool to perform a trial planning.

[1]Nmax=: 5

[2]Distance_threshold[Km]=: -1

[3]Min_PSC_code=: 0

[4]Max_PSC_code=: 511

[5]Reserved_PSCs_per_group=: -1

[6]Reserved_PSC_groups=: -1

From the trial planning results, you can learn whether the scrambling code allocation is successful, the number of required scrambling codes, and reuse distance in the whole

2008-12-17



network when there are the minimal constraints. This enables you to further determine the values of some specific parameters.

A) For small- and-medium-scaled networks, the parameters in a typical configuration file are set as follows:

[1]Nmax=: 5

[2]Distance_threshold[Km]=: 5

[3]Min_PSC_code=: 8


[5]Reserved_PSCs_per_group=: 2


PSC 0 to 7 are reserved for some special sites, for example, a site at a high altitude. If the PSCs are insufficient, more PSCs can be added. The first six scrambling codes in each group of PSC 384 to 511 are reserved for capacity expansion of outdoor sites and the other scrambling codes are reserved for cells of indoor sites.

B) For large-scaled networks such as those in Hong Kong and Singapore, the parameters in a typical configuration file are set as follows:

[1]Nmax=: 4

[2]Distance_threshold[Km]=: -1

[3]Min_PSC_code=: 8


[5]Reserved_PSCs_per_group=: 2


PSC 0 to 7 are reserved for some special sites, for example, a high site. If the PSCs are insufficient, more PSCs can be extended. The first six scrambling codes in each group of PSC 440 to 511 are reserved for capacity expansion of outdoor sites and the other scrambling codes are reserved for cells of indoor sites.

Data preparation

Figure 9-1 shows the engineering parameter data file and the neighboring cell file.

2008-12-17



Figure 9-1 Engineering parameter data file cellinfo.txt

2008-12-17



Figure 9-2 Neighboring cell file cellneighbor.txt

Planning adjustment

2008-12-17



Figure 9-3 Run the SCP tool

Run the SCP tool in the command line window, in which each step and its result can be seen. During planning, the tool outputs the planning results, the times a scrambling code is used, the minimum reuse distance, the total number of scrambling codes used, check results of neighborhood and reuse distance, and the statistics results of reuse distance between two cells with the same scrambling code in the whole network. These results form the basis of evaluating the planning and determining the necessity of adjustment and the adjustment method.

The planning and adjustment should achieve the following two targets:

Scrambling codes are all allocated successfully. That is, each cell to be allocated with a scrambling code obtains an available scrambling code complying with the planning principles.

The number of allocated scrambling codes is as small as possible and the reuse distance is as long as possible.

Scrambling code planning is adjusted by modifying the global or cell-level parameters, such as

Permit/deny to allocate a scrambling code set

2008-12-17



Number of the orders of neighborhoods

Reuse distance

Neighborhood

The priorities of parameters are as follows: engineering parameter data file (cell-level) > command line (global) > configuration file (global).

For example, if the fifth-order neighborhood is constrained in a network with 2332 cells, scrambling code allocation to 802 cells fails.

Figure 9-4 Number of cells failing to be allocated with a scrambling code for the first time

Open the SC_reset.txt file, copy the two columns of data to an Excel sheet, and set the number of neighborhood orders of the PSC whose value is –1 to 4. Supplement the data in the other two columns and copy the Excel sheet to the Cellinfo.txt file.

2008-12-17



Figure 9-5 Adjusting the number of orders of neighborhoods

2008-12-17



Figure 9-6 Updating the cell engineering parameter data file

After a neighboring cell linked list is generated and scrambling codes are allocated, 278 cells still fail to be allocated with a scrambling code.

2008-12-17



Figure 9-7 Results of the second scrambling code allocation

To ensure that each cell is allocated with a scrambling code successfully, further formulate adjustment strategies as required:

Change the constraints from the fifth-order neighborhood to the fourth-order neighborhood in the whole network and re-plan scrambling codes.

Reduce the number of reserved scrambling codes or adopt the no-grouping allocation mode.

9.2.2 Mixed expansion mode

When planning scrambling codes for an expanded network, first learn the scrambling code planning principles in the existing network and the allocation of scrambling code resources. For an expanded network, the planning rules should be consistent with the previous ones.

If some scrambling codes are reserved for capacity expansion in the early planning, determine whether to use the reserved scrambling codes and how many reserved scrambling codes are used in the current planning.

For capacity expansion involved in large-scaled coverage extension, the planning steps in mixed expansion mode are the same as those in new network mode.

The steps for scrambling code planning in mixed expansion mode are as follows:

2008-12-17



Parameter settings: Determine the major configurations (namely, the nth-order neighborhood, the minimum reuse distance, and the total number of scrambling codes that can be allocated) in the SCP_config.txt file.

Data preparation: According to the instruction manual, prepare the engineering parameter data file cellinfo.txt and the neighboring cell file cellneighbor.txt.

Check of the existing network: Check the allocation of scrambling codes in the existing network and determine the cells to be adjusted.

Expansion planning: Plan and adjust the cells that need to be adjusted in the existing network together the expansion cells.

Parameter settings

See the early planning rules or the parameter settings in new network mode.

Data preparation

See the data preparation in new network mode. Note: After the engineering parameter data file cellinfo.txt and the neighboring cell file cellneighbor.txt are updated, the scrambling code of the expansion cell (namely, the cell to be allocated with a scrambling code) is –1. This is the same as the scrambling code of the existing site, as shown in Figure 9-1.

Figure 9-1 Engineering parameter data file for expansion planning

Check of the existing network

2008-12-17



Use the /v parameter to check the scrambling code allocation in the existing network. The check results are output to the SCP_verification.txt file and the SC_reset.txt file, respectively.

For each cell, the check items include:

Check whether the same scrambling code is used in the cells between which the nth-order neighborhood exists.

Check whether the reuse distance of intra-frequency cells with the same scrambling code is less than the minimum reuse distance.

Check whether the allocated scrambling code is within the allowable range (namely, whether it is a reserved scrambling code).

Check whether scrambling code allocation complies with the requirements in the PSC_constraints.txt file that permits or prohibits scrambling code allocation.

Figure 9-2 Check of scrambling code in the existing network

The SCP tool also calculates the reuse distance between two cells allocated with the same scrambling code in the whole network and outputs the results to the Reuse_distance_cal.txt file. The Reuse_distance_cal.txt file can be imported to an Excel file for processing and analysis. You can use the /r parameter to let the tool only calculate the reuse distance but perform no planning or check.

2008-12-17



Figure 9-3 Reuse distance between two intra-frequency cells allocated with the same scrambling code

For the cells that fail to pass the check and need to be modified in the existing network, you can change the scrambling code of the cells to 1 in the engineering parameter table, that is, plan them together with the expansion cells.

Planning adjustment

See the planning adjustment in new network mode.

During expansion planning, scrambling code allocation may fail. In this case, check whether the minimum reuse distance and the nth-order neighborhood parameters can be adjusted. Avoid directly modifying the scrambling codes in the existing network and maintain the consistency of scrambling codes.

After the scrambling codes in the existing network are checked and optimized, modify the configuration parameters and make them take effect. As modifications can be performed cell by cell, the cell scrambling code to be modified may conflict with a neighboring cell's scrambling code that is not modified. As a result, the modification operation fails. The command line parameter /i supports the sorting of the cells whose scrambling cells are modified so that conflict can be avoided. After the execution of the command, the SCP obtains modification information about scrambling codes from the SCP_sort_input.txt file and outputs the sorting result to the SCP_sort_output.txt file. Note: (a) When you use the command line parameter /i, you need to import the first-order neighborhood file. Confirm that file exists in the same directory. (b) Before running the command, confirm that the cell engineering parameter table is the original version in which scrambling codes are not optimized.

2008-12-17



10 Multi-carrier and multiband

network planning

Besides the common 2.1 GHz band, the frequency bands used by the current commercial networks include 850 MHz, 900 MHz, and 1800 MHz bands. The RAN10 and later versions support multiband feature.

Multiband means that the frequencies in different bands exist in a network. Multi-carrier means that several frequencies in the same band exist in a network.

Multi-carrier networking and multiband networking are two effective means of increasing the capacity and solving coverage problems. They can be applied separately or together. The major reference basis is the frequency resources and capacity demand of the customer.

In multi-carrier or multiband networking, the major planning tasks include:

Formulating networking strategies, including frequencies/bands for continuous coverage, frequencies/bands for supplementary coverage, major services carried by different bands/frequencies, and coverage handover/load handover/direct retry between different bands/frequencies.

Configuring the following based on the networking strategies:

Configure neighboring cells. In the RAN10, the cell/neighboring cell configurations of the RNC are extended. The number of inter-frequency neighboring cells is extended to 64, the number of frequencies of inter-frequency neighboring cells is not restricted, and three frequency bands are supported at most.

Configure the service priorities, maintain the service priority table on the RNC, and set a network layer SPD_ID for each cell.

Configure the coverage-based inter-frequency handover priority of neighboring cells. In the case of coverage-based inter-frequency handover, only inter-frequency neighboring cells with the priority flag are considered. The value of this identification can be 0 (deny) and 1 to 3 (permit). In any frequency band, a coverage-based inter-frequency handover priority can be set for only one frequency. That is, a coverage-based handover to only one frequency in a band is permitted.

Configure a blind handover flag and the quality condition for a blind handover. In the case of LDR inter-frequency blind handover, only neighboring cells that meet the quality condition for an inter-frequency blind

2008-12-17



handover are considered. The principle is as follows: Before an LDR inter-frequency handover is originated, the UE measures the RSCP of the current cell. When the RSCP satisfies the quality condition for a blind handover, it is considered that the path loss in the current position of the UE is small enough to perform an inter-frequency blind handover to an inter-frequency cell with the same or larger coverage. When configuring the condition for a blind handover, pay attention to the cooperation with the 2D threshold and the 2D lag to avoid triggering a 2D event shortly after an inter-frequency blind handover.

For more information about multi-carrier and multiband networking, refer to the UMTS Performance R10 Multiband Performance Solution.

2008-12-17



11 Coverage planning in a high-speed

environment

To provide good communication quality on a transport vehicle moving at a rate of more than 200 km/h (for example, high-speed train) is a great challenge to the communications industry. The coverage in a high-speed environment should guarantee service continuity and insignificant decrease in quality of service (QoS).

The coverage in a high-speed environment is generally a linear coverage. The carrier jitter caused by the Doppler effect has a great impact on the receiving performance of NodeBs and the terminal when the terminal moves with high speed. The frequency needs to be estimated and corrected through the automatic frequency correction (AFC) algorithm. The Doppler shift and the AFC algorithm both have certain effects on the intra-frequency and inter-frequency neighboring cell measurements of the terminal. On the other hand, if the size of the handover zone remains unchanged, the higher the terminal speed is, less time it takes the terminal to pass the handover zone. If the time it takes the terminal to pass the handover zone is less than the minimum delay for the system to process a soft handover, a soft handover process fails, and thus a call drop occurs. In network construction and parameter configurations, these effects should be considered.

According to the specific operation and investment strategies of a network operator, the coverage in a high-speed environment may need to support the HSPA or only the R99. Therefore, the network construction strategies include R99 coverage and HSPA coverage. The possible strategies include different handover strategies, one cell shared by multiple RRUs, and cell splitting.

The parameters involved in a high-speed environment coverage include pilot transmit power, carrier transmit power, handover event threshold, and trigger delay.

For details about the coverage in a high-speed environment, refer to the UMTS Performance R10 High-Speed Coverage Performance Solution.

2008-12-17



12 LCS Parameter Planning

12.1 Parameter Configuration

12.1.1 Configuring Parameters for Outdoor Cells

If all the antennas used in a cell are outdoor antenna, the cell is defined as outdoor cell.

Latitude and Longitude

Take the latitude and longitude of antenna as that for cell.

If the cell has multiple combined sectors, the average location of all antennas is the location of cell.

Azimuth and Field Angle

For directional antennas, the azimuth of cell is the azimuth of the main lobe, and the field angle is twice as large as horizontal beamwidth. For omnidirectional antennas, the azimuth is 0° and the field angle is 360°.

If the cell has multiple combined sectors, calculate the total field angle through the azimuths and field angles of each sector; the centered angle of total field angle is the azimuth.

2008-12-17



Delay Compensation

Use the default.

Configuring Neighbor Cells

RNP engineers need to configure six intra-frequency neighbor cells for each cell. The specific configuration is by collecting statistics of and sorting the six neighbor cells that have the most handover times.

12.1.2 Configuring Parameters for Indoor Cells

If all the antennas used in a cell are indoor antennas, the cell is an indoor cell.


Take the latitude and longitude of the center of building as that for the indoor site.


The azimuth is 0° and the field angle is 360°.

Delay Compensation

Use the default.


RNP engineers need to configure six intra-frequency neighbor cells for each cell. The specific configuration is by collecting statistics of and sorting the first six neighbor cells that have the most handover times.

12.1.3 Configuring Parameters for Mixed Indoor and Outdoor Cell

This type of cell uses both indoor antenna and outdoor antenna.

No solution is available for this type of cell. To avoid big errors, configure the parameters according to the configuration for indoor cells.

2008-12-17



12.1.4 Configuring Parameters for the Cells Using Repeater

This type of cell uses a repeater.

No solution is available for this type of cell. To avoid big errors, configure the parameters according to the configuration for indoor cells.


Take the latitude and longitude of the center of the coverage area as that for the indoor site. If a repeater covers a building, take the center of the building as the center of the coverage area. If a repeater covers a tunnel, take the center of the tunnel as the center of the coverage area


The azimuth is 0° and the field angle is 360°.

Delay Compensation

Use the default.


RNP engineers need to configure six intra-frequency neighbor cells for each cell. The specific configuration is by collecting statistics of and sorting the first six neighbor cells that have the most handover times.

12.2 Parameter Configuration in a Commercial Deployment

Table 12-1 lists the SMLC cell parameters configured in a commercial deployment.

Table 12-1 SMLC cell parameters configured in a commercial deployment

TXCHAN

DELAY

ANTENNA

OPENIN

AGPSACTIVATEFLAG

OTDOAACTIVATEFLAG

MASKREPEATEXIST

CELLAVERAGEHEIGHT

RXTXCHANDELAY

2008-12-17



G

0 1260 ACTIVE INACTIVENOREPEATER 50 1975

MAX

ANTENNARANGE

ALTITUDE

METER

CELL

HEIGHTSTD

LONGITUDE

DEGREE CELLID

LATITUDE

DEGREE

ANTENNA

ORIENTATION

500 25 10 114172469 10011 22280356 250

Table 12-2 explains the SMLC cell parameters.

Table 12-2 Explanation to SMLC cell parameters

Parameter ID Parameter Name

Parameter Description

CELLID Cell IDValue range: 0–65535Meaning: identifies a cell exclusively

LATITUDEDEGREE

Latitude of cell antenna

Value range: –90000000 to 90000000Physical value range: –90 to 90, the step is 0.000001Unit: degreeMeaning: the latitude of cell antenna

LONGITUDEDEGREE

Longitude of cell antenna

Value range: –180000000 to 180000000Physical value range: –180 to 180, the step is 0.000001Unit: degreeMeaning: longitude of cell antenna

ALTITUDEMETER

Height of cell antenna

Value range: –10000 to 10000Unit: mMeaning: height of cell antenna

MAXANTENNARANGE

Maximum coverage range by cell antenna

Value range: 1–100000Unit: mMeaning: maximum coverage range by cell antenna

ANTENNAORIENTATION

Azimuth of main lobe of cell antenna

Value range: 0–3600Physical value range: 0–360, the step is 0.1.Unit: degreeMeaning: azimuth of main lobe of cell antenna (from the direction of main lobe counterclockwise to due north)

ANTENNAOPEN Field angle of Value range: 0–3600

2008-12-17



INGcoverage by cell antenna

Physical value range: 0–360, the step is 0.1Unit: degreeMeaning: the field angle of coverage by cell antenna. For omnidirectional cells, the field angle is 360°.

CELLAVERAGEHEIGHT

Average height of cell

Value range: –10000 to 10000Unit: mMeaning: the average height of cell

CELLHEIGHTSTD

Standard deviation of cell height

Value range: –10000 to 10000Unit: mMeaning: the standard deviation of cell height Recommended value: 50

CELLENVIRONMENT

Type of cell environment

Value range: NLOS_ENVIRONMENT (non-line-of-sight environment), LOS_ENVIRONMENT (line-of-sight environment), MIXED_ENVIRONMENT (mixed environment)Meaning: the type of cell environment. Recommended value: MIXED_ENVIRONMENT

TXCHANDELAY

Delay of cell transmit channel

Value range: 0–65535Unit: nsMeaning: the delay of cell transmit channel Recommended value: 0

RXTXCHANDELAY

Delay of cell receiver and transmit channel

Value range: 0–65535Unit: nsMeaning: the delay of cell receiver and transmit channel Recommended value: 0

MASKREPEATEXIST

Mask of repeater existence

Value range: NOREPEATER (not existing), REPEATER (existing) Meaning: the mask of repeater existence Recommended value: NOREPEATER

OTDOAACTIVATEFLAG

Activation tag for OTDOA location function

Value range: INACTIVE (inactive), ACTIVE (active) Meaning: the activation tag for OTDOA location function. Recommended value: ACTIVE

AGPSACTIVATEFLAG

Activation tag for AGPS location

Value range: INACTIVE (inactive), ACTIVE (active) Meaning: activation tag for AGPS

2008-12-17



functionlocation functionRecommended value: ACTIVE

13 TCell Parameter Planning

13.1 Introduction to TCell

For simplifying and accelerating the process of searching for cell by UE, the parameter TCell on NodeB is introduced. The TCell stands for the relative delay between transmit start time of SCH, CPICH, and downlink scrambling code of a cell and the BFN. It aims to prevent the signals transmitted by different cells under the same NodeB from overlapping on synchronization channel (SCH). The unit of TCell is 256 chips. The TCell ranges from 0 to 9 * 256 chip.

13.2 TCell Configuration

As previous mentioned, the TCell internal is usually configured to from 0 to 9 * 256 chips. The TCell must be larger than 0. In the project S in Hong Kong, the TCell is 768 chips. If three cells are under a NodeB,

The TCell of the Cell 10011 is configured to 0 chip.

The TCell of the Cell 10012 is configured to 256 chips.

The TCell of the Cell 10013 is configured to 512 chips.

Table 13-1 lists the TCell configuration in a case.

2008-12-17



Table 13-1 TCell configuration in a case

CELLID TCELL

10011 CHIP0

10012 CHIP256

10013 CHIP512

Tcell should be configured for different value in different cells in same sector for multi-carrier. And then Tcell is increased for different cells as following table.

Table 13-2 TCell configuration in multi-carrier

sector0 sector1 sector2carrier1 chip0 chip256 chip512carrier2 chip768 chip1024 chip1280carrier3 chip1536 chip1792 chip2048carrier4 chip2304 chip0 chip256carrier5 chip512 chip768 chip1024carrier6 chip1280 chip1536 chip1792

2008-12-17



14 PLMN Tag Parameter Planning

14.1 Introduction to PLMN Tag parameters

The PLMN value tag is an information unit, included in the master information block (MIB) and SIB1. When the ISB1 is updated, the PLMN tag in the MIB will change, indicating UE to read the updated SIB1.

When the UE moves between the adjacent cells in different LAs or RAs, the two cells must have different PLMN tags so that the UE can initiatively read the SIB1 of the target cell and then originate location update.

Based on previous analysis, RNP engineers shall assign PLMN tags of different ranges for any two areas (between LAs, between LA and RA, between RAs) that are geographically adjacent to each other in network planning. The two areas shall not have same PLMN tags.

In actual configuration, RNP engineers shall assign PLMN tags of non-overlapped range after negotiation to adjacent LA and RA.

NOTE

In actual network operation, if there are PS services in a cell, the network indicates its PLMN tag to change within the tag range of RA. Otherwise, the network indicates its PLMN tag to change within the tag range of LA.

14.2 Parameter Configuration

Configuring PLMN tag is configuring the maximum and minimum of PLMN tag for LA and RA. The range is between 1 and 256. In configuration, ensure that the PLMN tags of adjacent LAs or RAs as well as LAs and RAs which belong to same region are different. There is no special requirement for maximum and minimum of PLMN tag, except that the following rules should be fulfilled:

1. The minimum is less than maximum;

2008-12-17



2. The range of maximum and minimum is between 1 and 256;

Table 14-1 lists the PLMN tag configuration for LA in a case.

Table 14-1 PLMN tag configuration for LA in a case

PLMNVALTAGMIN PLMNVALMAX LAC

1 16 0x2510

Table 14-2 lists the PLMN tag configuration for RA in a case.

Table 14-2 PLMN tag configuration for RA in a case

PLMNVALTAGMIN PLMNVALMAX RAC LAC

17 32 0x01 0x2510

15 Summary

This guide introduces the flow for network planning design and each stage. It details the following planning or aspects:

Information collection

Radio network pre-planning

Cell planning of radio network

Area planning

Neighbor cell planning

LCS parameter planning

2008-12-17



TCell parameter planning

PLMN tag parameter planning

The previous planning can guide on-site engineers in planning. The appendix describes the following aspects:

The method to create 3G traffic maps with 2G traffic

Proposals on configuration simulation parameters

The impact from the cell access radius and magnetic declination on radio network planning

The guide also provides the Visio source file and the template for information collection.

16 Appendix

16.1 Creating 3G Traffic Maps with 2G Traffic

16.1.1 Creating Traffic Maps in a 3G Project

The process for creating a traffic map in a 3g project is as below:

Step 1 In U-Net, create a UMTS project, import 2G sites, set up a UMTS network (input engineering parameters, the engineering parameters for coverage prediction are necessary and input the type of service for planning. The propagation model is the GSM propagation model. If the GSM propagation model is not tuned, use the Okumura-HaTa model), and create a map for predicting UMTS coverage by transmitter plot. Figure 16-1 shows the UMTS coverage by transmitter plot.

2008-12-17



Figure 16-1 UMTS Coverage By Transmitter Plot

Step 2 Import 2G traffic data by sector and generate a traffic map based on cell.

In U-Net, select GEO > UTMS traffic > New Map > based on transmitter and service (user). Figure 16-1 shows Traffic Map based on transmitter and service (user). Input the number of subscribers simultaneously connected to each service by sector (configured in Project > UMTS Parameter Configuration).

2008-12-17



Figure 16-1 Traffic Map based on transmitter and service(user)

NOTE

In U-Net, user refers to the one who uses 3G services, because the early version of U-Net used user. In the guide, subscriber refers to the one who uses 3G service.

Calculate the number of subscribers simultaneously connected in Figure 16-1 as below:

1. Collect statistics of the traffic and GPRS throughput of each 2G cell (imported previously), and calculate the ratio of traffic and ratio of throughput for each cell.

2. Calculate the number of subscribers simultaneously connected to each 3G service in uplink and downlink in the planning area, namely the traffic.

The traffic is calculated from the input dimensioning data. For CS services, the uplink and downlink traffic are the same, and the traffic is as below:

Traffic = total number of subscribers * throughput per subscriber (kbit)/activation factor/bearer rate (kbps)/3600

According to previous calculation, the number of subscribers simultaneously connected to each service per sector in uplink and downlink is as below:

Number of subscribers simultaneously connected to each service per sector in uplink and downlink = total number of subscribers simultaneously connected to each service per sector in uplink and downlink * ratio of each sector

3. Input the previous result into the traffic map table. Excel can help you copy the result.

2008-12-17



Besides the previous method, another method (Traffic Map based on transmitter and service (Throughput)) can also import the data. This method generates the traffic map by importing the throughput (kbps) of each sector and service. The principle is similar to previous one. The difference is that the last method uses the number of subscribers simultaneously connected to each sector in each cell and this method use the throughput per service per cell. The principles are as below:

1. Collect statistics of the traffic in busy hour and GPRS throughput of each 2G cell (imported previously), and calculate the ratio of traffic in busy hour and ratio of throughput for each cell.

2. Calculate the uplink and downlink total throughput rate for each 3G service by inputting dimensioning data.

For CS services, the uplink and downlink traffic are the same, and the traffic is as below:

Total throughput rate = total number of subscribers * traffic per subscriber in busy hour (Erl) * activation factor * bearer rate (kbps).

For PS services, the uplink throughput rate and downlink throughput rate for each service are calculated respectively.

Uplink or downlink throughput rate of each service = total throughput rate of each service * throughput per subscriber (kbit)/3600.

3. According to previous result,

Uplink or downlink throughput rate of each service per sector = total throughput rate of each service * ratio of each sector

4. Input the previous result into the traffic map table. Excel can help you copy the result.

In dimensioning, the data input to service model for CS domain is the traffic in busy hour and for PS domain is the throughput in busy hour. According to two calculations, the first method is easy for CS domain while the second method is easy for PS domain. As a result, in actual simulations, engineers usually generate two traffic maps by two methods respectively. In simulation, choose both the two maps, and they will be overlapped.

With the previous methods, a GSM live traffic data map is generated according to sector, namely, the subscriber distribution is different in different sectors.

2008-12-17



Figure 16-1 GSM Live Traffic Data Map

Step 3 Import the 2G traffic map and save it as 2gtraffic.adg.

Step 4 Create a UMTS project for simulation, import the information about 3G sites, and set up a network.

Step 5 Import the 2gtraffic.adg previously generated, which can serve simulation.

----End

16.1.2 Creating a Traffic Map in a 2G Project

The process for creating a traffic map in a 2G project is as below:

Step 1 Create a 2G project, import 2G sites, and create the coverage project of 2G best servers.

2008-12-17



Figure 16-1 GSM Coverage By Transmitter Plot

Step 2 Import the data of existing GSM network, and generate a GSM traffic map.

Figure 16-1 GSM Live Traffic Data Map

Step 3 Import 2G traffic map, and save it as 2Gtraffic_2G.agd.

2008-12-17



Step 4 Predict 3G traffic of each service in uplink and downlink respectively based on the 2G traffic information.

Calculate the number of subscribers simultaneously connected to and the throughput rate of each service in each 2G sector as previously mentioned (the sector is a 2G network, consistent with the sector in the traffic map generated from the GSM project in the Step 3. The service mentioned here is the 3G service). The map can be an Excel.

Step 5 Create a UMTS project, import related parameters, set up the network, and import the 2G traffic map 2Gtraffic_2G.agd.

Step 6 Adjust the traffic map table so that the service name in the map can correctly match the service name of the project.

The types of 3G services include voice (UL), voice (DL), mobile internet access (UL), and mobile internet access (DL). Complete the traffic map table. The method is as below:

1. In U-Net, select GEO > UMTS traffic.

2. Double click the 2G traffic map to open the table.

3. Right click the table, and select fields.

4. Add or delete services.

Figure 16-1 shows adjusting traffic name by selecting fields.

2008-12-17



Figure 16-1 Adjusting traffic name

Figure 16-2 shows adjusting table structure.

2008-12-17



Figure 16-2 Adjusting table structure

Step 7 Copy and paste 3G traffic data (converted form 2G data).

Copy the table for the number of subscribers simultaneously connected to or the throughput rate of each service in each sector organized before, as shown in Figure 16-1.

2008-12-17



Figure 16-1 3G traffic map data

The previous traffic map can serve simulation.

----End

16.2 Proposals on Configuring Simulation Parameters

16.2.1 Ec/Io Threshold

Simulation use Ec/Io threshold, as shown in Figure 16-1.

2008-12-17



Figure 16-1 Ec/Io used in simulation

When the Ec/Io of best server for the UE is smaller than the highlighted value in Figure 16-1, the UE will be rejected for access. This threshold is the precondition to judge whether the UE can succeed in accessing and being served.

In simulation, check Ec/Io first:

If it is smaller than the threshold, the UE will be rejected for access.

If it is larger than the threshold, start power control iteration and judge whether other conditions are met.

The Ec/Io threshold is usually –18 dB.

The Ec/Io in simulation may even affect SHO. It is also a precondition for judging whether a branch is already listed in the active set. If the actual Ec/Io cannot reach the Ec/Io threshold, the cell will not be listed in active set thought the threshold for being listed in the active set is met. Namely, when the load increases, the edge Ec/Io is lower than the threshold, the SHO area will shrink.

Figure 16-2 shows setting Ec/Io threshold for simulation to –18 dB.

Figure 16-3 shows setting Ec/Io threshold for simulation to –15 dB.

Obviously, the SHO area for Ec/Io being –15 dB is much smaller than the SHO area for Ec/Io being –18 dB.

2008-12-17



2008-12-17



Figure 16-2 Setting Ec/Io threshold for simulation to –18 dB

Figure 16-3 Setting Ec/Io threshold for simulation to –15 dB

2008-12-17



Table 16-1 lists the variation of call setup rate when the Ec/Io threshold is –18 dB, –13 dB, and –10 dB.

Table 16-1 Variation of call setup rate for different Ec/Io thresholds for simulation

Ec/Io Threshold in Simulation Call Setup Rate

-18dB 99.7%

-13dB 98.7%

-10dB 89.9%

The larger the Ec/Io threshold is, the more probably the UE is rejected, and the smaller the call setup rate is. Namely, the Ec/Io threshold affects call setup rate.

shows the Ec/Io distribution in different thresholds.

2008-12-17



Figure 16-4 Ec/Io distribution in different thresholds

In , the larger the Ec/Io threshold is, the higher the total Ec/Io distribution is. When the threshold is large, few UEs can connect to the network, so the interference is weak.

16.2.2 Monte Carlo Simulation Parameter

In U-Net, the recommended Monte Carlo simulation times are 100, unrelated to scenario. Namely, the recommended Monte Carlo simulation times are 100 in dense urban area, urban area, suburban area, and rural area. This is relevant to the design and realization of Monte Carlo simulation module in U-Net. The module can ensure that after 100 iterations, the uplink load, downlink transmission power, and other indexes for each cell can be convergent.

16.3 Configuraing the Cell Access Radius

The cell access radius directly affects the search ability of cell and the access by UE. The cell access radius configured on NodeB is usually 10 km, long enough for most scenarios. However, in some wide-coverage scenarios, the cell coverage radius exceeds 10 km, such as on sea surface, by site on high mountains, and in open grassland. In these scenarios, engineers need to modify the radius of search window so that the search radius and the actual coverage ability can match each other. For a 3G operator with 2G networks, most sites are co-located, so engineers can obtain the approximate coverage ability of 2G network by collecting statistics of TA values of 2G cells. The TA values can be reference in configuring 3G cell access radius.

2008-12-17



RNP engineers can calculate how many chips are configured for 3G search window. Each chip stands for a distance of 78.215 m.

For HSDPA networks, the cell access radius shall usually be within 5 km, because it takes 15.5 timeslots from HS-SCCH's scheduling the UE to receiving the response. These 15.5 timeslots include:

Processing time by UE

RTT time

Waiting time for ACK/NACK feedback by UE, about 7.5 timeslots

Processing time by NodeB

The 6 HARQ processes configured correspond to 18 timeslots, so the processing time by NodeB is 2.5 timeslots.

According to the design of NodeB, the single thread RTT is relevant to the distance form the UE to the NodeB. When the distance is far, the RTT may be large, so the processing time by NodeB will be short. It is probable after six TTIs of six threads that the NodeB has inadequate time to process HS-DPCCH feedback and HS-SCCH coding and scheduling.

In actual networks, the downlink destination signaling point (DSP) is unaware of the distance from the UE to the NodeB, so it judges the distance approximately by cell radius. When the cell radius exceeds 5 km, the six threads will be scheduled in seven TTIs to guarantee enough processing time. As a result, the NodeB can schedule six threads for six times in seven TTIs, so the total maximum scheduling time is 6/7 (85.7%) and the maximum rate is 6/7 of normal maximum rate.

16.4 Impact from Magnetic Declination on Radio Network Planning

16.4.1 Introduction

RNP engineers usually neglect the magnetic declination in planning and optimizing azimuth of cell. The magnetic declination varies in different areas. In most part of China, the magnetic declination is 3°–5°. In Mohe city, the magnetic declination is as large as 11°.

As the radio network marketing of Huawei grows worldwide, RNP engineers work not only in China, but also in other parts of the world. In some countries, the magnetic

2008-12-17



declination is even 20°. Therefore, RNP engineers must consider the impact from magnetic declination.

16.4.2 Basic Concepts

Before knowing the impact from magnetic declination, learn several items:

Coordination north: the coordination system defined artificially; usually the due upper direction serves as reference north.

Meridian north: the direction between the South Pole and the North Pole, namely, the meridian.

Magnetic north: the north indicated by the compass.

The convergence angle of meridian: the included angle between meridian north and coordinate north.

Magnetic declination: the included angle between meridian north and magnetic north

Figure 16-1 shows the relation among coordination north, meridian north, and magnetic north.

Figure 16-1 Magnetic declination

Am Magnetic azimuth

A Azimuth

B Coordination azimuth

2008-12-17



C Convergence angle of meridian

D Magnetic declination

The calculation between them is as below:

B = Am + D - C

The magnetic declination is due to the difference between the geomagnetic pole and geographic pole. With the reference of geographic meridian,

When the magnetic meridian is at east of geographic meridian, it is call east declination, marked with "+", drawn at east of geographic meridian.

When the magnetic meridian is at west of geographic meridian, it is call west declination, marked with "-", drawn at west of geographic meridian.

In the maps of planning and optimization, the upper direction stands for north while the lower direction stands for south, based on which RNP engineers adjust the azimuth. As a result, the convergence angle of meridian can be neglected. So the previous calculation is simplified to as below:

B = Am + D

For example, the magnetic declination in an area is 20° west (D = –20°), and the azimuth in planning is 60°, so the azimuth measured by compass shall be 80° (Am = B – D = 60° + 20° = 80°), not 60° which the azimuth should be.

16.4.3 Impact

All the predictions and calculations in simulation are based on digital maps, namely, based on geographic coordination system, so the magnetic declination has no impact on the results of prediction and simulation.

The magnetic declination has impact on the apparatuses only which indicates direction by magnetic field. All the geographic parameters related to simulation in radio network planning are based on geographic coordination system, unrelated to magnetic declination (magnetic field of earth).

The only impact lies in confirmation of azimuth in surveying NodeBs. It is common to use ordinary compass to check whether the actual azimuth of antenna is consistent with the planed azimuth. Obviously, the planned azimuth is based on the geographic coordination system, and namely, the planned azimuth of antenna makes the geographic north as 0°. If engineers measure the azimuth of antennas with ordinary compass without considering the impact from magnetic declination (directly read the compass), the actual azimuth of antenna will differ from the planned azimuth in an angle, which is the local magnetic declination.

2008-12-17



The RNP azimuth is seldom required to be as accurate as less than 10°. The RNO azimuth in adjustment can be a relative value. Therefore, the impact from the magnetic declination is neglectable. In some special areas, such as polar area, the magnetic declination will be fairly large. If engineers need to know the accurate azimuth, they shall consider the impact from magnetic declination by adding or deducting the local magnetic declination.

Figure 16-1 shows the global magnetic declination.

Figure 16-1 Global magnetic declination

RNP engineers can look up the local magnetic declination according to the latitude and longitude, and rectify the measured azimuth.

16.5 Configuring RNP Parameters

16.5.1 Overall Flow

The process for configuring RNP parameters is as below:

Step 1 Making parameter templates.

Step 2 Import parameters to CME client.

Step 3 Modify parameters.

Step 4 Import MML scripts for RNC

----End

Figure 16-1 shows the flow for configuring RNP engineers.

2008-12-17



Figure 16-1 Flow for configuring RNP engineers

16.5.2 Introduction to CME Client

Parameter configuration uses CME client, so the following paragraphs introduce it.

CME, short for WCDMA RAN Configuration Management Express, is a simple offline data configuration system for RAN equipment. It provides an integrated solution to data configuration for RAN equipment on graphic maintenance client. It simplifies data configuration in RAN, improves the efficiency to configure data in RAN, and lowers the cost on daily maintenance.

Figure 16-1 shows the work principle for CME system.

2008-12-17



Figure 16-1 Work principle for CME system

16.5.3 Detailed Steps

The following paragraphs detail the steps.

Make Negotiation Data.

Negotiation data is a set of the configuration data (about NodeB, cell, neighbor cell, neighbor cell relation, GSM cell, and so on) obtained in the site preparation.

The negotiated data file follows a template with a suffix of xls.

After filling parameters in the template and checking data validity, import the negotiated data on CME client. This section details making negotiated data and validity check.

1. Template description

The rule for naming negotiated data file is WCDMA + RNC version + Data Collection Report.xls, such as WCDMA RNC1.5 Data Collection Report.xls. The default installation directory is C:\Program Files\HuaweiTechnologies\CMEV100R002\import. The negotiated data file is released with CME software.

In the negotiated data table, there are seven sheets. Fill them in sequence. Check validity of data in the Cover sheet. After check succeeds, import the data to CME client and generate an RNC script uniformly.

2008-12-17



Table 16-1 Description of each sheet in the template

Sequence Sheet Meaning Remarks

1 NodeBPhysical position of NodeB card

Filled by global technical support (GTS) engineers

2 CellParameters related to fast setup of cell

Filled by RNP engineers

3 NRNCCellCell parameters of NRNC

4 NeighborCellRelation Neighbor cell relation

5 GSMCellInformation about GSM cells

6 GSMCellRelationGSM neighbor cell relation

7 CoverThe links to each sheet and data validity check

Validity check

NOTE

The negotiated data template uses macros. If loading macros fails, lower the restriction on macros by selecting Tools > Macro > Security.

Do fill each sheet in sequence.

Each sheet contains a hyperlink to other sheets.

2. NodeB sheet

The NodeB sheet contains subrack No., SSN and NodeB name, shown as in Table16-1.

Table 16-1 NodeB sheet

No Field Name Meaning Parameter Description

1 Subrack No Subrack NoValue range: 1, 3–17

Content: WRBS number

2 SSNSub-system number

Value range: 0, 1

Content: for querying the sub-system of the cell

3 NodeB Name NodeB name

Value range: 1–31 characters

Content: for querying the status of the cell under the NodeB. Valid only when queried by NodeB name.

2008-12-17



NOTE

The NodeB sheet is usually filled by GTS engineers, but RNP engineers must check that the NodeB Name in the NodeB sheet is consistent with the NodeB Name in the Cell sheet.

3. Cell sheet

The Cell sheet contains cell parameters, shown as Table 16-1.

Table 16-1 Cell sheet


1 NodeB Name NodeB name


Content: for querying the state of cell under the NodeB. Valid only when queried by NodeB name.

2 Cell IDID of WCDMA cell

Value range: 0–65535

Content: for identifying a cell exclusively

Recommended value: none

3 Cell NameName of WCDMA cell


Content: name of WCDMA cell


4 BANDIND Band indicator

Value range: Band1, Band2, Band3, Band4, Band5, Band6), BandIndNotUsed (band indicator not used)

Content: the band in which the uplink and downlink frequencies are


5 UL frequencyUplink frequency

6 DL frequencyDownlink frequency

7 Scrambling CodeScrambling code


Content: downlink PSC


8 LAC Location area code

Value range: H'0000–H'FFFF (0–65535) , H'0000 and H'FFFE

2008-12-17



excluded

Physical unit: none

Content: the value is a location area defined by the PLMN of GSM-MAP type. LAC is defined by the operator. Recommended value: none

9 RACRouting area code

Value range: H'00–H'FF (0–255) Physical unit: none

Content: the value is a routing area defined by the PLMN of GSM-MAP type. RAC is defined by the operator.


10 SACService area code

Value range: H'0000–H'FFFF (0–65535)

Physical unit: none

Content: the value with PLMN-Id and LAC form service area identity (SAI). SAI defines an area formed by one or more cells in the same service area. The area is service area, and it informs core network (CN) of the location of UE. SAC is defined by the operator.


11 URA IDsID of user registration area


Content: for identifying a URA exclusively.

12 TCELL Cell offsetCHIP[0, 256, 512, 768, 1024, 1280, 1536, 1792, 2048, 2304]

13 LOCELLIdentity of local cell


Physical unit: none

Content: for identifying a cell exclusively


14 MAXTXPOWER Maximum transmit power


Physical range: 0–50, the step is

2008-12-17



0.1

Physical unit: dBm

Content: for defining the total maximum transmit power simultaneous in the cell on downlink channel.

Recommended value: 430

15 PCPICHPOWERPilot channel power

Value range: -100–500

Physical range: -10–50, the step is 0.1

Physical unit: dBm

Content: for defining the PCPICH transmit power in the cell

Recommended value: 330

4. NRNCCell sheet

The NRNCCell sheet contains the parameters of NRNC, shown as Table 16-1.

Table 16-1 NRNCCell sheet


1 NRNC ID NRNC identity –

2 Cell IDIdentity of WCDMA cell

Refer to Cell sheet

3 Cell Name Cell name Refer to Cell sheet

4 BANDIND Band indicator Refer to Cell sheet

5 UL frequencyUplink frequency

–

6 DL frequencyDownlink frequency

–

7 Scrambling CodeScrambling code

Refer to Cell sheet

8 LACLocation area code

Refer to Cell sheet

9 RACRouting area coding

Refer to Cell sheet

10 TX Diversity Mode Transmit [No, STTD]

2008-12-17



diversity mode

5. NeighborCellRelation sheet

The NeighborCellRelation sheet contains the parameters related to neighbor cell relation, shown as Table 16-1.

Table 16-1 NeighborCellRelation sheet



Refer to Cell sheet

2 NRNC IDNRNC identity

–

3 Neighbor Cell IDIdentity of neighbor cell

–

6. GSMCell sheet

The GSMCell sheet contains the information about GSM cells, shown as Table 16-1.

Table 16-1 GSMCell sheet


1GSM Cell Index

Index of GSM cell


Physical unit: none

Content: for identifying a GSM cell exclusively


2GSM Cell ID

Identity of GSM cell

Value range: H'0000–H'FFFF (0–65535)

Physical unit: none

Content: for identifying a GSM cell


3 MCCMobile country code


Physical unit: none

Content: the code for the country where the GSM cell is

4 MNCMobile network code

Value range: 00–99 or 000–999

Physical unit: none

2008-12-17



Content: for identifying the mobile communication network under which the GSM cell is

5 LACLocation area code

Value range: H'0000–H'FFFF (0–65535) , H'0000 and H'FFFE excluded

Content: the location area where the GSM cell is

Note: H'0000 and H'FFFE are reserved

6 NCCNetwork color code

Value range: 0–7

Content: for identifying different networks in neighbor areas

7 BCCBase station color code

Value range: 0–7

Content: for identifying neighbor NodeBs with same frequency exclusively

8Frequency Number

Frequency


Content: for identifying the frequency number of BCCH carriers of the inter-RAT cell

9Frequency Band Indicator

Band

Value range: GSM900_DCS1800_BAND_USED, PCS1900_BAND_USED

Content: when the frequency number of inter-RAT cells is between 512 and 810, the indicator identifies whether the frequency number belongs to the DCS 1800 MHz band or PCS 1900 MHz.

10 Cell Type Cell type

Value range: NO_CAPABLITY, GSM, GPRS, EDGE

Content: for identifying the type of inter-RAT cell

7. GSMCellRelation sheet

The GSMCellRelation contains the relation of GSM neighbor cells, shown as Table 16-1.

Table 16-1 GSMCellRelation sheet



–

2008-12-17



2 GSM Cell IndexIndex of GSM cell

–

8. Cover sheet

The Cover sheet contains the cover information, Data Validity Check button, and the links to other sheets. After data is input to other sheet, check the validity of data to location error data.

Figure 16-1 shows the cover sheet.

Figure 16-1 Cover sheet

Data Validity Check

After inputting enough data to the table, perform data validity check by clicking Data Validity Check button.

If the data is valid, the prompt Validity check successfully appears.

If there is error in the data, the CheckRuslt sheet will display the check result. The check list points out where the error is, as shown in Figure 16-1. In this case, you shall modify the data and recheck the validity.

2008-12-17



Figure 16-1 Check result

NOTE

Besides the data validity checking on the Cover sheet, the template automatically checks the data validity in other sheets when data is input. For example, it checks whether the data exceeds the range and whether the format of character is wrong. Besides these checks, RNP engineers shall check the logical errors in the data which is correct in format and range.

Import Negotiated Data

After making the negotiated data is complete, import the data to CME to generate RNC configuration command scripts. The process is as below:

Step 1 Start CME Client. On the interface of WRAN CM Express, select Tools > Import Negotiated Data…. A welcome window appears, as show in Figure 16-1.

2008-12-17



Figure 16-1 Welcome interface of WRAN CM Express

Figure 16-2 shows the welcome interface of importing negotiated data.

2008-12-17



Figure 16-2 Welcome interface of importing negotiated data

Step 2 Click Next. An interface with default installation directory appears, as shown in Figure16-1.

2008-12-17



Figure 16-1 Selecting the negotiated file for importing

Step 3 Check the importing directory and click Next. An interface for selecting items to be imported appears, as shown in Figure 16-1.

2008-12-17



Figure 16-1 Selecting items to be imported

Step 4 Double click the Import Indication field for each negotiated data item. Select YES to import the item and select NO not to import the item.

Step 5 Click Option. An interface for selecting the mode to import data appears, as shown in Figure 16-1.

2008-12-17



Figure 16-1 Selecting the mode to import data

Step 6 Select a mode to import the data and click OK. The interface for selecting items to be imported appears again, as shown in Figure 16-1.

Step 7 Click Next to import data. When importing data is complete, a Finish interface appears, as shown in Figure 16-1. Click Finish.

2008-12-17



Figure 16-1 Finishing importing data

Step 8 Click Finish

NOTE

There are three modes to import negotiated data as below:

Add negotiated data

Update existing configuration with the negotiated data

Add negotiated data and update existing configuration

16.6 Template for Collecting Information

16.6.1 Template for Collecting Dimensioning Information

2008-12-17



16.6.2 Template for Collecting Information at Detailed Planning Stage

16.7 Method of obtaining references quoted in the document

The table below lists the sources of the references quoted in the document.

Table 16-1 Reference documents location

Reference Name Source

U–Net Simulation Operation Guide 3ms.huawei.com

Operation Guidelines for the Global Simulation Center

Bulletin board of the wireless network planning department

RNP–Electromagnetic Background Interference Test Guide

http://support.huawei.com — knowledge center >radio performance and network planning and optimization > technical guide

Tool for Analyzing the Interference Co-Existence Between RNPS GCWUT Communication Systems

Bulletin board of the wireless network planning department and 3ms.huawei.com

RNP-RF NodeB Survey Guide http://support.huawei.com — knowledge center >radio performance and network planning and optimization > technical guide

W–Radio Propagation Model Application Guide

http://support.huawei.com—knowledge center >radio performance and network planning and optimization > technical guide

How to Use the Neighbor Cell Planning Tool CNA

http://support.huawei.com—software center >small software tool >radio >network planning and optimization tool

How to Use the Scrambling Code Planning Tool SCP

http://support.huawei.com—software center >small software tool >radio >network planning and optimization tool

2008-12-17


http://support.huawei.com/






Reference Name Source

UMTS Performance R10 Multiband Performance Solution

Department server \\szxfs02-pub\UMTS_RNP\WX_URNP_KB_F\12 window of study\05 performance delivery\UMTS10.0\performance solution

UMTS Performance R10 High-Speed Coverage Performance Solution

Department server \\szxfs02-pub\UMTS_RNP\WX_URNP_KB_F\12 window of study\05 performance delivery\UMTS10.0\performance solution

2008-12-17


w radio network planning guide 20090324 a 3.51

Documents

study5 performance

wran cm express

call setup

ce resources

node list

neighboring

neighboring

scrambling