80-W1527-2 Rev.C CDMA2000 1x and 1xEV-DO Network Planning

Student Guide
Book 2
80-W1527-2 Rev C
Notice
Each User acknowledges that CDG does not review the disclosures or
contributions of any CDG member nor does CDG verify the status of the
ownership of any of the intellectual property rights associated with any such
disclosures or contributions. Accordingly, each User should consider all
disclosures and contributions as being made solely on an as-is basis. If any User makes
any use of any disclosure or contribution, then such use is at
such User's sole risk. Each User agrees that CDG shall not be
liable to any person or entity (including any User) arising out of any use
of any disclosure or contribution, including any liability arising out of infringement
of intellectual property rights.
This technical data may be subject to U.S. and international export, re-export or transfer
("export") laws. Diversion contrary to U.S. and international law is strictly prohibited.
CDG is a registered trademark of the CDMA Development Group. QUALCOMM is a registered

trademark of QUALCOMM Incorporated in the United States and may be registered in other
countries. Other product and brand names may be trademarks or registered trademarks of their
respective owners. QUALCOMM CDMA University is a registered trademark of QUALCOMM
Incorporated. QUALCOMM University is a trademark of QUALCOMM Incorporated.
CDMA2000 is a registered certification mark of the Telecommunications Industry Association,
used under license. ARM is a registered trademark of ARM Limited. QDSP is a registered
trademark of QUALCOMM Incorporated in the United States and other countries.
Material Use Restrictions

These written materials are to be used only in conjunction with the associated instructor-led
class. They are not intended to be used solely as reference material.
No part of these written materials may be used or reproduced in any manner whatsoever without
the written permission of QUALCOMM Incorporated.
Copyright 2009 QUALCOMM Incorporated.
All rights reserved.
QUALCOMM Incorporated
5775 Morehouse Drive
San Diego, CA 92121-1714
U.S.A.
CDMA2000 1X and 1xEV-DO Network Planning

Table of Contents
80-W1527-2 Rev C
Notes
MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION
iii

Table of Contents
80-W1527-2 Rev C
Notes
iv
80-W1527-2 Rev C

Table of Contents
Table of Contents Book 2

Section 8: Traffic and Capacity .................................................................... 8-1
Section Learning Objectives ................................................................................ 8-2
General Traffic Engineering
Traffic Terminology ................................................................................ 8-3
System Definitions ................................................................................. 8-4
Metrics .................................................................................................. 8-5
Terminology ........................................................................................... 8-6
Erlang Theory ......................................................................................... 8-7
Characterization ..................................................................................... 8-8
Load
.................................................................................................. 8-9
Erlang Theory ....................................................................................... 8-10
Erlang-B Formula ............................................................................................... 8-11
Erlang-B Table ................................................................................................ 8-12
General Traffic Engineering
Graphical Representation of Erlang Concepts ..................................... 8-13
Offered versus Carried ......................................................................... 8-14
Erlang-C Formula .................................................................................. 8-15
PS Data ................................................................................................ 8-16
PS Traffic Parameters ........................................................................................ 8-17
Packet Size and Packet Occurrence Probability ................................................ 8-18
PS Data Traffic Model........................................................................................ 8-19
M/M/1 Queuing Theory .................................................................................... 8-20
M/M/1 Queue ................................................................................................ 8-21
Latency Defined ................................................................................................ 8-22
M/M/1 Queuing Theory Definitions .............................................................. 8-23
Latency and Total Delay .................................................................................... 8-25
Forward Link Capacity Estimation Example ................................................... 8-26
Impact of Latency Requirement........................................................................ 8-27
Impact of Page Size ........................................................................................... 8-28
General Traffic Engineering Multi-Erlang Concepts ....................................... 8-29
Traffic Engineering Multi-Service ................................................................... 8-30
Case Study
................................................................................................ 8-31
Multi-Erlang
................................................................................................ 8-32
General Traffic Engineering CDMA and Traffic Engineering .......................... 8-33
CDMA Impacts on Traffic Engineering .............................................................. 8-34
Resource Utilization in CDMA Networks .......................................................... 8-35
BTS
................................................................................................ 8-36
Hard Blocking Resources ...................................................................... 8-37
Impact of Soft and Softer Handoff on Resource Utilization ............................. 8-38
Multi-Erlang and M/M/1 ................................................................................... 8-39
Traffic and Capacity What Did We Learn? ..................................................... 8-40
Section 9: Capacity and Dimensioning ......................................................... 9-1
Section Learning Objectives ................................................................................ 9-2

Table of Contents
80-W1527-2 Rev C
CDMA2000 RL Capacity ....................................................................................... 9-3

Reverse Link CDMA Capacity ............................................................................. 9-4
Fundamentals ........................................................................................ 9-5
Mobile Signal Power at BTS ................................................................... 9-6
Theoretical UL Capacity for Voice Only ............................................................... 9-7
Eb/Nt Sensitivity .................................................................................................. 9-8
Impact of Network Planning on Alpha (Interference Factor) ............................. 9-9
CDMA2000 FL Capacity ..................................................................................... 9-10
Forward Link Capacity Calculation .................................................................... 9-11
1xEV-DO FL Capacity ......................................................................................... 9-12
Best Effort, Full Buffer ....................................................................................... 9-13
Maximum Theoretical Sector Throughput ........................................................ 9-14
Maximum Theoretical Throughput Considering Overhead .............................. 9-15
Practical Sector Throughput (Best Effort, Full Buffer) ...................................... 9-16
C/I Distribution of a Grid Network .................................................................... 9-18
Practical Sector Throughput (Best Effort, Non -full Buffer) ............................... 9-19
Equivalent Throughput Consumed by HTTP Users ........................................... 9-20
1xEV-DO RL Capacity ......................................................................................... 9-21
Reverse Link Capacity ........................................................................................ 9-22
Typical Values for Reverse Link Capacity Estimat ion ........................................ 9-23
VoIP (or VT) Sector Throughput ........................................................................ 9-24
EV-DO Capacity Summary ................................................................................. 9-25
Rev A Single Service Capacity Summary......................................................... 9-26
Rel 0 Single Service Capacity Summary .......................................................... 9-27
Capacity Numbers Used for Dimensioning ....................................................... 9-28
PS Data Applications and Dimensioning ........................................................... 9-29
PS Data Call Model ............................................................................................ 9-30
PS Data Considerations ..................................................................................... 9-31
Packet Size and Packet Occurrence Probability ................................................ 9-32
Applications Considered for PS Data Call Model .............................................. 9-33
Application Summary ........................................................................................ 9-34
Dimensioning ................................................................................................ 9-35
Goals
................................................................................................ 9-36
Dimensioning ................................................................................................ 9-37
Rev A
Reverse Link, VoIP and B E .................................................................... 9-38
Forward Link, Multi -service (VT and BE) .............................................. 9-39
Rev A Gain over Rel 0 Users .............................................................................. 9-40
Forward Link, Mixed Mode: Rel 0 and Rev A .................................................... 9-41
Multi-service Dimensioning .............................................................................. 9-42
Reverse Link ......................................................................................... 9-43
Capacity ................................................................................................ 9-44
Example ................................................................................................ 9-45
Example: Reverse Link, Multi -service Tradeoff ................................... 9-46
Exercises
................................................................................................ 9-47
1X Dimensioning ............................................................................................... 9-48
vi

Table of Contents
80-W1527-2 Rev C
1X Example
................................................................................................ 9-50
Voice versus Data Throughput .......................................................................... 9-51
Reference Material ........................................................................................... 9-52
DRC Mapping Table Example (Rel 0) ................................................................. 9-53
DRC Mapping Table Example (Rev A) ................................................................ 9-54
1xEV-DO Reverse Link Payload Size .................................................................. 9-55
Forward Link and Reverse Link Application Payload Size .............................. 9-56
Capacity and Dimensioning What Did We Learn? ......................................... 9-57
Section 10: Tools Overview ....................................................................... 10-1
Section Learning Objectives .............................................................................. 10-2
Basics
................................................................................................ 10-3
Network Planning Tools .................................................................................... 10-4
Bins
................................................................................................ 10-5
Network Planning Tools
General Features .................................................................................. 10-7
CDMA2000 Features ............................................................................ 10-9
3G Simulation Approaches .............................................................................. 10-11
Monte Carlo Simulation .................................................................................. 10-12
Network Planning Tools Monte Carlo Simulation ........................................ 10-14
Tool Considerations
Selection Criteria: Compatibility ........................................................ 10-15
Additional Selection Criteria .............................................................. 10-16
Automatic Cell Planning Tools ........................................................................ 10-17
Basic ACP Concepts ......................................................................................... 10-18
How Can ACP Help? ........................................................................................ 10-21
ACP Recommendations ................................................................................... 10-22
ACP Tool
Histograms ......................................................................................... 10-23
Plots
.............................................................................................. 10-24
Network Planning Tool Usage ......................................................................... 10-25
Monte Carlo Simulation
User Distribution ................................................................................ 10-26
Reasons for Failures ........................................................................... 10-27
Increasing Coverage ........................................................................................ 10-29
Reducing Interference ..................................................................................... 10-30
CDMA Prediction Plots and Displayed Parameters ......................................... 10-31
Debugging .......................................................................................... 10-32
CDMA Prediction Plots and Displayed Parameters
Advanced Evaluation .......................................................................... 10-33
Simulation Reports .......................................................................................... 10-34
Global and Site Level .......................................................................... 10-35
Mobile Level Analysis ......................................................................... 10-36
Tools Overview What Did We Learn? .......................................................... 10-37
vii

Table of Contents
80-W1527-2 Rev C
Section 11: Layer 1 and Other Parameters ................................ ....... 11-1

Section Learning Objectives ................................ ................................ .. 11-2
Handoff (HO) and Network Planning ................................ .................... 11-3
Types of CDMA Handoffs Overview ................................ ................. 11-4
CDMA Soft Handoffs Soft Handoff Flow ................................ .......... 11-5
CDMA Handoff Parameters ................................ ................................ .. 11-6
T_ADD ................................ ................................ ...................... 11-7
T_DROP ................................ ................................ .................... 11-8
SRCH_WIN_(A,N,R) ................................ ................................ 11-9
HO Parameters and Network Planning ................................ ................ 11-10
Plotting Handoff Status on a Map ................................ ........................ 11-11
HO Optimization During Network Planning ................................ ....... 11-12
Optimizing Soft Handoff ................................ ................................ ..... 11-13
Soft Handoff / Power Tradeoff ................................ ................ 11-14
Soft Handoff Increases RL Capacity ................................ ....... 11-15
Statistics ................................ ................................ ................... 11-16
Basic HO Optimization Steps ................................ .............................. 11-17
Handoff Optimization Example ................................ ........................... 11-18
Handoff Parameters Optimization ................................ ....................... 11-19
Hard Handoff (HHO) ................................ ................................ ........... 11-21
CDMA Hard Handoffs ................................ ................................ ........ 11-22
Triggers ................................ ................................ .................... 11-23
CDMA Pilot Beacon ................................ ................................ 11-24
Hard Handoff with Pilot Beacons ................................ ............ 11-25
Hard Handoff Types ................................ ................................ ............ 11-26
Major Points ................................ ................................ ............. 11-27
HHO Ec/I0 Thresholds ................................ ................................ ......... 11-29
HHO Zone Allocation ................................ ................................ .......... 11-30
Hard Handoff Planning NL Planning ................................ ............... 11-31
PN Offset
................................ ................................ ...................... 11-32
What is PN Planning? ................................ ................................ .......... 11-33
PILOT_INC Parameter ................................ ................................ ........ 11-34
Pilot PN Offset
Assignment ................................ ................................ .............. 11-35
Planning ................................ ................................ ................... 11-36
PILOT_INC Parameter ................................ ............................ 11-37
PN Offset Conflicts Aliasing ................................ ............................ 11-38
PN Planning Analysis
Constraints ................................ ................................ ............... 11-39
Recommended PILOT_INC ................................ .................... 11-40
Example PN Offset Reuse ................................ ....................... 11-41
Pilot PN Offset Assignment Plan ................................ ............. 11-42
Neighbor List Planning ................................ ................................ ........ 11-43
Generic Considerations ................................ ............................ 11-44
Tool Limitations................................ ................................ ....... 11-45
Using the Neighbor List ................................ ........................... 11-46
viii

Table of Contents
80-W1527-2 Rev C
Area Planning .............................................................................................. 11-47

Paging/BSC Planning Paging Zones .............................................................. 11-48
BSC Planning Base Station Controller Boundaries ....................................... 11-49
SID/NID/BSC Planning
Common Considerations .................................................................... 11-50
Tool Limitations .................................................................................. 11-51
Layer 1 and Other Parameters What Did We Learn? ................................... 11-52
Section 12: Practical Considerations for Network Planning ......................... 12-1
Antenna and Antenna Near Parts ..................................................................... 12-3
Near Parts ............................................................................................ 12-4
Antenna ................................................................................................ 12-5
Antenna Radiation Pattern .................................................................. 12-6
Surge Protectors/Lightning Arrestors .................................................. 12-7
Tails or Jumpers ................................................................................... 12-8
Diplexer ................................................................................................ 12-9
Feeder .............................................................................................. 12-10
Low Noise Amplifiers ......................................................................... 12-11
LNA Noise Factor Calculation ............................................................. 12-12
Summary ............................................................................................ 12-13
Main Antenna Characteristics Radiation Patterns ....................................... 12-14
Antenna Selection
Based on Coverage Morphology ........................................................ 12-15
Based on Electrical Requirements ..................................................... 12-16
Based on Mechanical Requirements ................................................. 12-18
Antenna Downtilt ............................................................................................ 12-19
Optimum Downtilt .......................................................................................... 12-20
Observations ...................................................................................... 12-21
Antenna Downtilt
EDT: Narrow Beam ............................................................................ 12-22
EDT: Large Beam ................................................................................ 12-23
MDT Pros and Cons ......................................................................................... 12-25
EDT Pros and Cons .......................................................................................... 12-26
Site Selection .............................................................................................. 12-27
Site Survey Checklist .......................................................................... 12-28
Pre-Qualified Site Database ............................................................... 12-29
Zoning Analysis ................................................................................... 12-30
Search Rings ....................................................................................... 12-31
Site Off-Grid ....................................................................................... 12-32
Height Difference ............................................................................... 12-33
Site Off-Grid and Height Difference ................................................... 12-34
Understanding Future Growth ........................................................... 12-35
Repeater Sites .................................................................................... 12-36
Repeater Site Details .......................................................................... 12-37
ix

Table of Contents
80-W1527-2 Rev C
Summary ............................................................................................ 12-38

Practical Considerations for Network Planning
What Did We Learn? .......................................................................... 12-39
Section 13: Overlays.................................................................................. 13-1
How to Overlay EV-DO and 1X? ........................................................................ 13-3
Same Band Overlay ........................................................................................... 13-4
Adjacent Carrier Consideration......................................................................... 13-7
Case 1 ................................................................................................ 13-8
Case 2 ................................................................................................ 13-9
How a Non-Optimized 1X System Affects an EV-DO System .......................... 13-10
Ec/I0 Plots ............................................................................................ 13-11
DRC Rate Plots.................................................................................... 13-12
Comparison Plots ............................................................................... 13-13
Voice Comparisons............................................................................. 13-14
Different Band Overlays .................................................................................. 13-15
Different Frequency Bands ............................................................................. 13-16
Overlays What Did We Learn? ..................................................................... 13-17
Section 14: Capacity Planning Considerations ............................................ 14-1
Capacity Planning Considerations Introduction ............................................. 14-3
Initial Traffic Forecasting ................................................................................... 14-4
Initial Capacity Forecasting ............................................................................... 14-5
Capacity Planning Considerations
Capacity Design Parameters ................................................................ 14-6
Subscriber Distribution and Growth .................................................... 14-7
Typical Capacity Design ........................................................................ 14-8
Forecasting for Capacity Planning ........................................................ 14-9
System Monitoring .......................................................................................... 14-10
Network Statistics Monitored for 1xRTT............................................ 14-11
Network Statistics Monitored for EV-DO ........................................... 14-12
Increasing Capacity ......................................................................................... 14-13
CDMA Capacity................................................................................... 14-14
Introduction ....................................................................................... 14-15
Uneven Traffic Distribution ................................................................ 14-17
Number of Carriers per Sector ........................................................... 14-18
Adding a Carrier ................................................................................. 14-19
Capacity Planning Considerations What Did We Learn?.............................. 14-20

Table of Contents
80-W1527-2 Rev C
Section 15: Course Summary ..................................................................... 15-1

Ec/Io Calculation Single Cell ............................................................................ 15-2
Reverse Link Budget Summary ....................................................................... 15-3
Forward Link Budget Equality Coverage Comparison .................................... 15-4
CDMA Bands
................................................................................................ 15-5
Hata Cell Radius Graph ...................................................................................... 15-6
Resource Utilization in CDMA Networks .......................................................... 15-7
Multi-service Dimensioning Reverse Link ...................................................... 15-8
Different Frequency Band ................................................................................. 15-9
Network Planning
Coverage ............................................................................................ 15-10
Capacity .............................................................................................. 15-11
RF
.............................................................................................. 15-12
Network Planning Skills ................................................................................... 15-13
xi

Table of Contents
80-W1527-2 Rev C
This page left blank intentionally.
xii
80-W1527-2 Rev C
Section 8: Traffic and Capacity
Notes
8-1
80-W1527-2 Rev C
Notes
8-2
80-W1527-2 Rev C
Notes
8-3
80-W1527-2 Rev C
Notes
8-4
80-W1527-2 Rev C
Notes
8-5
80-W1527-2 Rev C
Notes
8-6
80-W1527-2 Rev C
Notes
8-7
80-W1527-2 Rev C
Notes
8-8
80-W1527-2 Rev C
Traffic profiles and traffic intensity:

Considering the traffic intensity formula, 10 calls of 100 seconds each would have the same
intensity as 100 calls of 10 seconds each; both cases would use the servers equally. Considering
calls from end-to-end, different call profiles can stress the system differently.
A typical example is BSC dimensioning, which needs to consider the total traffic intensity (how
many Erlangs can be carried), but also the call arrival rate (busy hour call attempts).
8-9
80-W1527-2 Rev C
Notes
8-10
80-W1527-2 Rev C
Erlang-B Formula
The Erlang formula typically is not used directly. It is more commonly used to determine the
number of resources needed to carry a traffic demand (offered traffic) based on acceptable Grade of
Service (1 Blocking).
During network dimensioning, offered traffic is estimated based on previous network
measurements or marketing assumptions. The GoS is usually determined from marketing
assumptions.
The formula is used to draft an Erlang-B table showing offered traffic for different numbers of
resources and GoS targets. An example is presented on the next page.
8-11
80-W1527-2 Rev C

Blocking
Resources
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
60
70
80
90
100
0.01
0.02
0.03
0.04
0.05
0.1
0.2
0.3
0.01
0.15
0.46
0.87
1.36
1.91
2.50
3.13
3.78
4.46
5.16
5.88
6.61
7.35
8.11
8.88
9.65
10.44
11.23
12.03
12.84
13.65
14.47
15.29
16.12
16.96
17.80
18.64
19.49
20.34
21.19
22.05
22.91
23.77
24.64
25.51
26.38
27.25
28.13
29.01
29.89
30.77
31.66
32.54
33.43
34.32
35.21
36.11
37.00
37.90
46.95
56.11
65.36
74.68
84.06
0.02
0.22
0.60
1.09
1.66
2.28
2.94
3.63
4.34
5.08
5.84
6.61
7.40
8.20
9.01
9.83
10.66
11.49
12.33
13.18
14.04
14.90
15.76
16.63
17.50
18.38
19.26
20.15
21.04
21.93
22.83
23.72
24.63
25.53
26.43
27.34
28.25
29.17
30.08
31.00
31.92
32.84
33.76
34.68
35.61
36.53
37.46
38.39
39.32
40.26
49.64
59.13
68.69
78.31
87.97
0.03
0.28
0.72
1.26
1.88
2.54
3.25
3.99
4.75
5.53
6.33
7.14
7.97
8.80
9.65
10.51
11.37
12.24
13.11
14.00
14.89
15.78
16.68
17.58
18.48
19.39
20.31
21.22
22.14
23.06
23.99
24.91
25.84
26.78
27.71
28.65
29.59
30.53
31.47
32.41
33.36
34.30
35.25
36.20
37.16
38.11
39.06
40.02
40.97
41.93
51.57
61.29
71.08
80.91
90.79
0.04
0.33
0.81
1.40
2.06
2.76
3.51
4.28
5.08
5.90
6.73
7.57
8.43
9.30
10.17
11.06
11.95
12.85
13.76
14.67
15.58
16.50
17.42
18.35
19.28
20.22
21.16
22.10
23.04
23.99
24.94
25.89
26.84
27.80
28.76
29.72
30.68
31.64
32.61
33.57
34.54
35.51
36.48
37.46
38.43
39.40
40.38
41.36
42.34
43.32
53.16
63.08
73.06
83.09
93.15
0.05
0.38
0.90
1.52
2.22
2.96
3.74
4.54
5.37
6.22
7.08
7.95
8.83
9.73
10.63
11.54
12.46
13.39
14.31
15.25
16.19
17.13
18.08
19.03
19.99
20.94
21.90
22.87
23.83
24.80
25.77
26.75
27.72
28.70
29.68
30.66
31.64
32.62
33.61
34.60
35.58
36.57
37.56
38.56
39.55
40.54
41.54
42.54
43.53
44.53
54.57
64.67
74.82
85.01
95.24
0.11
0.60
1.27
2.05
2.88
3.76
4.67
5.60
6.55
7.51
8.49
9.47
10.47
11.47
12.48
13.50
14.52
15.55
16.58
17.61
18.65
19.69
20.74
21.78
22.83
23.88
24.94
25.99
27.05
28.11
29.17
30.24
31.30
32.37
33.43
34.50
35.57
36.64
37.71
38.79
39.86
40.94
42.01
43.09
44.17
45.24
46.32
47.40
48.48
49.56
60.40
71.29
82.20
93.15
104.11
0.25
1.00
1.93
2.95
4.01
5.11
6.23
7.37
8.52
9.68
10.86
12.04
13.22
14.41
15.61
16.81
18.01
19.22
20.42
21.64
22.85
24.06
25.28
26.50
27.72
28.94
30.16
31.39
32.61
33.84
35.07
36.30
37.52
38.75
39.98
41.22
42.45
43.68
44.91
46.15
47.38
48.62
49.85
51.09
52.32
53.56
54.80
56.03
57.27
58.51
70.90
83.32
95.75
108.19
120.64
0.43
1.45
2.63
3.89
5.19
6.51
7.86
9.21
10.58
11.95
13.33
14.72
16.11
17.50
18.90
20.30
21.70
23.10
24.51
25.92
27.33
28.73
30.15
31.56
32.97
34.38
35.80
37.21
38.63
40.05
41.46
42.88
44.30
45.72
47.14
48.56
49.98
51.40
52.82
54.24
55.66
57.08
58.50
59.92
61.35
62.77
64.19
65.61
67.04
68.46
82.70
96.95
111.21
125.47
139.73
8-12
80-W1527-2 Rev C
Notes
8-13
80-W1527-2 Rev C
Offered and Served Traffic

The Erlang formula (or table) is used to estimate the offered traffic. The served traffic is lower than
the offered traffic, and both are linked by the given formula. For large number of servers and high
blocking probability, the offered traffic can be larger than the number of servers (but the served
traffic will always be lower than the number of servers).
8-14
80-W1527-2 Rev C
Erlang-C Formula
This slide shows a simplified formula for Erlang-C; it is equivalent to the original formula:
T
Pr
n!
n!
(1
T
n
)*
n 1
0
i!
8-15
80-W1527-2 Rev C
Notes
8-16
80-W1527-2 Rev C
PS Traffic Parameters
Session Duration
A session could last a few seconds or a few days. The definition of a session also depends on what needs
to be dimensioned.
In terms of the actual occupancy of radio resources, the session should be defined as the period for
which the end-user application is active (used) rather than the time the application is open.
If a session is defined as a dataflow between applications, several sessions could be open at the same
time on a given terminal.
Session Data Volume
For the entire session space, this is a random variable that could take any value from a few bits to
several megabits.
The data volume per session is typically modeled as a Poisson distribution, with the average volume per
session as the parameter.
This does not fully account for the packet aspects of the service. To account for those, it necessary
to further divide the session into its basic blocks.
Number of Packet Calls per Session
The distinct period when data is exchanged among the distant terminals, typically separated by idle
periods (reading time).
Idle Time between Packet Call and Reading Time
The reading time affects code channel usage. Ideal systems would use no resources during reading time,
because no data is exchanged.
In current systems, this is controlled mainly by dormancy timers.
Data Volume in a Packet Call
This variable can be expressed in terms of the number of packets (or datagrams) in a session and the
packet size.
Data volume and the data rate of the bearer affect capacity, delays, etc.
8-17
80-W1527-2 Rev C
Data packet call models

Different standard bodies use different packet call models. This shows that, unlike voice, PS data is
not a single application.
3rd Generation Partnership Program (3GPP)

This typically refers to the standardization body working on the UMTS/WCDMA protocols. The 3rd
Generation Partnership Program 2 (3GPP2) focuses on CDMA2000 and its evolution.
8-18
80-W1527-2 Rev C
PS Data Traffic Model

1 Based
on weighted average of main and embedded object.
2 Based
on minimum size of the main and embedded objects.
3 Based
on parsing time and number of objects.
4 Audio
streaming assumed.
5 Object
in this case corresponds to 1 frame (assuming 10 frames per second for video, and 50
frames for audio).
6 Assuming 180
second streaming.
M/M/1 model is described later in this section
8-19
80-W1527-2 Rev C
M/M/1 and Erlang Model Analogy

The Erlang model estimates the blocking probability for an average resource utilization. Similarly,
M/M/1 models estimate the latency of data for an average loading (bearer efficiency).
M/M/1 Limitations
To overcome M/M/1 model limitations, alternative models (such as G/G/1 or G/M/1) can be used.
Although these models may be more accurate, they usually require look-up tables, which makes
them less convenient than the M/M/1 model for dimensioning.
8-20
80-W1527-2 Rev C
Notes
8-21
80-W1527-2 Rev C
M/M/1 and latency

Although latency can occur in different parts of the network, the latency estimated by the M/M/1
model is only for a single link at a time. In this section, only the latency from the BTS to the mobile is
estimated. Latency between other nodes would depend on their respective occupancy.
8-22
80-W1527-2 Rev C
M/M/1 Queuing Theory Definitions

1 This rate
can be derived from the monthly usage and any peak to average, or traffic profile
information, divided by the number of cells in the network. The serving rate depends on
channel characteristics and the request size.
2 This delay
measures only the time between a request from the user and when the download is
initiated; it does not include the time to complete the download. To estimate the total delay,
add the download (or data transfer) time, which is controlled mainly by the assigned channel
used for communication and the radio conditions.
3 This corresponds
to the aggregate throughput of all users performing FTP, or similar
downloads.
8-23
80-W1527-2 Rev C
Notes
8-24
80-W1527-2 Rev C
Efficiency
Efficiency ( ) can also be calculated as:
=(T* -1)/(T* )
8-25
80-W1527-2 Rev C
Forward Link Capacity Estimation Example

1 Knowing the
total number of requests to serve for all users of all cells, and the average arrival
rate per cell, we can easily calculate the number of cells.
8-26
80-W1527-2 Rev C
Notes
8-27
80-W1527-2 Rev C
Notes
8-28
80-W1527-2 Rev C
Notes
8-29
80-W1527-2 Rev C
Traffic Engineering Multi-Service

[Answers are provided at the end of this section.]
8-30
80-W1527-2 Rev C
Case Study
8-31
80-W1527-2 Rev C
Multi-Erlang
To determine the offered traffic when resources are shared between services, a few assumptions
must be made.
For two services (Service 1 and Service 2 in the figure), a fixed resource utilization between services
should exist. In the graph, Service 1 is assumed to consume 1 resource, while Service 2 consumes 4
resources. With this resource consumption, and with 40 resources available, 40 trunks could be
defined for Service 1 and 10 trunks for Service 2.
Resources can be shared linearly between the services. When only Service 1 is required, all 40
resources can be dedicated to this service (40 trunks); when only Service 2 is required, all 40
resources can be dedicated to that service (10 trunks). If the resources were shared equally (20 to
Service 1 and 20 to Service 2), the number of trunks available for each service would be directly
dependent on the resource utilization (20 trunks for Service 1, 5 trunks for Service 2).
The offered traffic for each service can be determined using an Erlang-B formula, according to the
number of trunks available and the expected GoS for each service. Using the previous example of
sharing the resources equally, with 20 trunks available for Service 1, 13.2 Erlangs would be offered,
while 1.66 Erlangs would be offered for Service 2.
To determine the overall offered traffic, one must determine the operating point, i.e., the point that
corresponds to the ratio of traffic demand. As an example, if the total demand for Service 1 is 100
Erlangs and for Service 2 is 20 Erlangs, the operating point would be where the ratio of offered
traffic for Service 1 and Service 2 is the closest to 0.2. On the above figure, this falls between (13.2,
1.66) and (9.83, 2.28).
8-32
80-W1527-2 Rev C
Notes
8-33
80-W1527-2 Rev C
Traffic CDMA Specifics

Blocking occurs for different reasons in a CDMA system. Interference is the most common cause of
blocking. However, in a real network, this is not what is directly observed.
On the Forward link, limited available power is an apparent reason for soft blocking. However, the
real cause of the blocking might be interference, because power is used to overcome interference
(yet itself generates interference to other users). To determine the actual cause, consider both total
transmit power and the number of users served.
Hard blocking can also occur on a CDMA system. Traffic Channel Elements (TCE) and channelization
codes (Walsh Codes) are potential sources of hard blocking. TCE blocking, in contrast to soft
blocking, is easy and cheap to manage: simply add hardware to the cell.
8-34
80-W1527-2 Rev C
Notes
8-35
80-W1527-2 Rev C
Notes
8-36
80-W1527-2 Rev C
Channel Elements and Erlang Theory

When a single service is used, Erlang theory can be used directly for CE dimensioning.
When multiple services are used, multi-Erlang dimensioning is necessary. Alternatively, simulations
can be done to dimension CE based on a given call model.
8-37
80-W1527-2 Rev C
Impact of Soft and Softer Handoff on Resource Utilization
Sf_HORF Softer Handoff Reduction Factor
HORF Handoff Reduction Factor
8-38
80-W1527-2 Rev C
Notes
8-39
80-W1527-2 Rev C
Notes
8-40
80-W1527-2 Rev C
Comments/Notes
8-42

Section 9: Capacity and Dimensioning
80-W1527-2 Rev C
Notes
9-1

80-W1527-2 Rev C
Notes
9-2

80-W1527-2 Rev C
Notes
9-3

80-W1527-2 Rev C
Notes
9-4

80-W1527-2 Rev C
Notes
9-5

80-W1527-2 Rev C
Notes
9-6

80-W1527-2 Rev C
Reverse Link Capacity Equation

Typical values for:
: 0.5 for voice. For PS data, 1 can be used.
: 0.65 for a three-cell site.

in this equation is related to the Frequency reuse factor (c.f. slide 9). The interference
factor takes into account the mobiles in other cells not power controlled by the
considered cell.
The calculated capacity values will be affected by:
Demodulator implementation, because the required Eb/Nt will change.
Propagation environment, because the required Eb/Nt will change.
Site selection and optimization, because will change.
9-7

80-W1527-2 Rev C
Eb/Nt Sensitivity
Eb/Nt is affected by the RF propagation conditions (multipath), the speed of the MS, and the
operating frequency band. Details of the Eb/Nt requirement are specified in C.P0010-C-1. The
following table summarizes data for the main test case, main frequency bands, 2% FER.
Eb/Nt
Case / Frequency Band
800 MHz
1900 MHz
450 MHz
Case A
3.47
3.8
3.3
Case B
3.9
4.55
3.85
Case C
5.2
4.6
Case D
4.7
4.75
9-8

80-W1527-2 Rev C
Optimization and Parameters Impact on F (and )

F is directly affected by the mobiles that are detected in a given sector but are not power controlled
by that sector. When a mobile is power controlled by the sector, it would reach the sector no higher
power than other mobiles, because of the Or-of-the-down power control implementation. When the
mobile is not power controlled by a given sector, it may be detected at the sector at a higher power
than other mobiles, thus increasing the RoT, while decreasing the capacity.
By extension, the same variable that affects the handoff also affects the RL capacity:
Optimization Decreases cell overlap which decreases the number of mobiles detected by a
cell.
Handoff parameters Controls mobiles in the Active Set, which are power controlled by the
sector.
The BPL also affects the Frequency Reuse Factor. To achieve a higher BPL, cells must be placed
closer to each other, which makes it more difficult to control their coverage.
9-9

80-W1527-2 Rev C
Notes
9-10

80-W1527-2 Rev C
Test Condition
Test condition refers to standard tests defined to determine the minimum performance of a mobile
station (described in the standard C.S0011-C, V2.0). Each test is defined for mobile speed, radio
environment (multi-path), and geometry, as described below:
Test 2: 3 km/h, 1 path, Ior/Ioc = 6 dB
Test 4: 30 km/h, 1 path, Ior/Ioc = 4 dB
Test 6: 100 km/h, 3 paths, Ior/Ioc = 2 dB
9-11

80-W1527-2 Rev C
Notes
9-12

80-W1527-2 Rev C
Notes
9-13

80-W1527-2 Rev C
Notes
9-14

80-W1527-2 Rev C
Maximum Theoretical Throughput Considering Overhead

At higher layers, additional overhead must be considered. For example, with a VoIP application with
176 bits of user data (8800 user throughput), up to 80 bits of overhead (RoHC, checksum, RLP
header, stream layer, MAC, FCS, etc.) are inserted to form a 256-bit packet.
Each application has a different overhead requirement. Overhead also depends on the transmission
protocol. For example, the following can be calculated:
Max TCP segment: 1500 bytes (12000 bits)
1500
IP overhead: 20 bytes (160 bits)
1520
TCP overhead: 20 bytes (192 bits)
1540
(TCP overhead can contain an optional 4 bytes)
UDP overhead: 8 bytes (64 bits).

Either TPC or UDP framing would be used, not both.
RLP packet size: 128 bytes (1024 bits)
12 * 128
RLP overhead: 6 bytes (48 bits)
12 * 134
Total bytes
1608
Total overhead
7.2%
9-15

80-W1527-2 Rev C
Notes
9-16

80-W1527-2 Rev C
Notes
9-17

80-W1527-2 Rev C
Notes
9-18

80-W1527-2 Rev C
Notes
9-19

80-W1527-2 Rev C
FTP and HTTP Traffic Mix

From field experiments, the available FTP throughput was measured for different numbers of HTTP
users. From the results, we can observe that the achievable FTP throughput decreases as the
number of HTTP users increases. From this, we can estimate an FTP equivalent throughput for each
HTTP user.
9-20

80-W1527-2 Rev C
Notes
9-21

80-W1527-2 Rev C
Reverse Link Capacity

A typical capacity equation for the Reverse link is based on an approximation that assumes that Npole
is much larger than 1.
For a high data rate bearer, this assumption does not hold true, resulting in an underestimation of
the cell capacity.
9-22

80-W1527-2 Rev C
Notes
9-23

80-W1527-2 Rev C
VoIP (or VT) Sector Throughput

According to the capacity equation, the estimated VoIP capacity would be achieved for Eb/Nt of 6.5
to 7, while the typical Eb/Nt for 9600 kbps data (16 slots termination) is in the range of 3.25 (Rev A)
to 6.25 (Rel 0). In section 4, for EvDO, rather than Eb/Nt, the traffic Ec/Nt is given. The conversion
can be done when considering the data rate and the spreading rate:
Eb
Nt
[dB] Traffic
Ec
Nt
10.Log
spreading _ rate
data _ rate
9-24

80-W1527-2 Rev C
Notes
9-25

80-W1527-2 Rev C
Rev A Single Service Capacity Summary

Unless mentioned otherwise:
FL assumes receive diversity implemented at the AT.
RL assumes 2-way receive diversity implemented at the AN.
No equalizer, PIC, or TIC (multi-user detection) at either AT or AN.
9-26

80-W1527-2 Rev C
References
[1] Rashid Attar and Naga Bhushan, CDMA2000 1xEV-DO Concepts (Qualcomm document number
80-H3343-1, Rev. A).
[2] Lower boundary accounts for typical RF limitation observed in deployed networks.
9-27

80-W1527-2 Rev C
Notes
9-28

80-W1527-2 Rev C
Notes
9-29

80-W1527-2 Rev C
Notes
9-30

80-W1527-2 Rev C
Notes
9-31

80-W1527-2 Rev C
Notes
9-32

80-W1527-2 Rev C
Notes
9-33

80-W1527-2 Rev C
Notes
9-34

80-W1527-2 Rev C
Notes
9-35

80-W1527-2 Rev C
Notes
9-36

80-W1527-2 Rev C
Notes
9-37

80-W1527-2 Rev C
Notes
9-38

80-W1527-2 Rev C
Notes
9-39

80-W1527-2 Rev C
Rev A Gain over Rel 0 Users

1 Average is
weighted according to recommended 3GPP2 (C.R1002-0 v1.0) distribution.
9-40

80-W1527-2 Rev C
Forward Link, Mixed Mode: Rel 0 and Rev A

Tradeoff is based on simulation. Same RF conditions are used, all Rev A DRC available for
Rev A users; only Rel 0 DRC available for Rel 0 users. DRC mapping representative of receiver
implementation.
9-41

80-W1527-2 Rev C
Multi-service Dimensioning
The FL/RL data volume ratio depends on the application. To understand the typical ratio in a
network, look at the individual application characteristics and the traffic mix.
Typical examples of FL/RL ratio for selected applications are:
Gaming: 60%
Mobile Office: 45%
Web browsing: 13%
PDA sync: 15%
Download: 10%
Upload: x10
Streaming: 3%
9-42

80-W1527-2 Rev C
Notes
9-43

80-W1527-2 Rev C
Notes
9-44

80-W1527-2 Rev C
Notes
9-45

80-W1527-2 Rev C
Notes
9-46

80-W1527-2 Rev C
Exercises
9-47

80-W1527-2 Rev C
Notes
9-48

80-W1527-2 Rev C
Notes
9-49

80-W1527-2 Rev C
1X Example
The minimum performance for voice considers fundamental channel; supplemental channels are
considered for data.
All minimum performance values are based on C.S0011-C v2.0, thus are representative of FL
capacity.
In this example:
Voice activity factor for voice is assumed to be 0.5
Data activity factor is assumed to be 1
Overhead represents 20% of total power.
9-50

80-W1527-2 Rev C
Notes
9-51

80-W1527-2 Rev C
Notes
9-52

80-W1527-2 Rev C
DRC Mapping Table Example (Rel 0)

SINR thresholds are AT implementation dependent. The SINR thresholds given in this example
could be considered typical of a single antenna and rake implementation. This is a typical
implementation for a commercially available Rel 0 AT.
9-53

80-W1527-2 Rev C
DRC Mapping Table Example (Rev A)

SINR thresholds are AT implementation dependent. The SINR thresholds given in this example
could be considered typical of a dual antenna (receive diversity) and equalizer implementation. This
is a typical implementation for a commercially available Rev A AT.
9-54

80-W1527-2 Rev C
Notes
9-55

80-W1527-2 Rev C
Forward Link and Reverse Link Application Payload Size

1xEV-DO Rev A header length (and trailer length where applicable):
RLP
22 bits (other options 14 bits or 6 bits)
Stream
2 bits
Connection
Layer packet)
8 bits (if Format B packet does not have enough bits to fill a
Security Layer
Depends on security features, but probably 0
MAC Layer
2 bits trailer
Physical Layer
30 bits (24 bits CRC and 6 bits of tail)
Connection
9-56

80-W1527-2 Rev C
Notes
9-57

80-W1527-2 Rev C
Comments/Notes
9-60

Section 10: Tools Overview
80-W1527-2 Rev C
Notes
10-1

80-W1527-2 Rev C
Notes
10-2

80-W1527-2 Rev C
Notes
10-3

80-W1527-2 Rev C
Notes
10-4

80-W1527-2 Rev C
Bins
The bin size should match map data accuracy. Bin sizes much smaller than the map resolution
are not helpful for network planning, and increase the size of the prediction file without
increasing accuracy. Alternatively, if the bin size is much larger than the map resolution, map
accuracy is lost.
10-5

80-W1527-2 Rev C
Bins and Calculation

For each sector, path loss is calculated over a binned area. The calculation area is bounded by a
cell radius, which is usually configurable. In each bin, the path loss to neighboring sectors is
assumed constant over the area of the bin.
When predicting coverage or performing simulations, multiple servers are considered at each
bin. For accurate interference calculations, consider a minimum of 20 servers, which improves
the accuracy only for areas without a dominant server.
The volume of data to be generated is another important consideration.
For each bin, a user-selectable number of path loss values from specific cells is calculated. A
variable bin size enables high resolution in areas of interest, and low resolution outside those
areas.
Site-to-site distance is also important. With a very dense network and a large bin, only a few bins
could separate sites, which would not provide sufficient accuracy for the prediction.
10-6

80-W1527-2 Rev C
GIS Features
Cartographic database supporting:

Digital elevation models
Clutter data (type and height)
3-D building data
Traffic data
Scanned maps
Vector data
Population data
Integrated cartography editor (vector/raster)
Interface with commercial GIS tools: MapInfo, ArcView, etc.
User and Database Management
Flexible database structure allowing integration of user-defined parameters.

Multi-user support including database consistency management, data synchronization, and
user disconnection/reconnection from/to the database.
Administration module supporting data access and user privilege management.
Support for standalone, centralized, and distributed configurations.
Import/export features allowing quick data migration from other RF planning tools.
10-7

80-W1527-2 Rev C
Distributed Computing
Distributed computing on networked workstations

Parallel computing on dual-processor systems
Printing and Reports
Report generator including traffic, population, and clutter-based statistics

Report generator for every prediction in defined area
User-defined reports based on macros
Export of reports and prediction plots into other software
Measurement Module
CW measurements
Import, display, and analysis of CW data
Prediction/measurements comparison and statistical analysis
Automatic propagation model tuning using CW measurements
Test mobile/Scanner data
Import, display, and analysis of test mobile data (automatic preferred)
Graphical replay on map combined with user-defined graphs
Call events display and analysis
Data filtering
Sorting by PN
Automatic propagation model tuning using test mobile data
10-8

80-W1527-2 Rev C
Network and Radio Parameter Modeling
Network database
Support for Repeaters
Radio configuration and channel modeling
Radio resource modeling
Support for multiple carriers and frequency bands
Carrier type modeling (1xEV-DO and 1xRTT)
FCH and SCH modeling
Additional radio configurations (RC3, RC4, RC5)
Data Services Modeling
FCH activity factor/SCH variable rate modeling
SCH and FCH Forward and Reverse link Eb/Nt thresholds
1xEV-DO Rel. 0 and Rev. A quality tables (C/I vs. Forward link data rate)
Reverse link 1xEV-DO Rel. 0 and Rev. A physical channels modeling
Rev.A bearer modeling
Traffic Modeling
Modeling of voice and data services and applications
Support for multiple sources of traffic data

User distribution maps
Live traffic data per service per cell
Service demand maps (raster/vector)
10-9

80-W1527-2 Rev C
Multi-service Monte Carlo Simulation
Modeling of mixed 1xRTT/1xEV-DO traffic

Forward link cell capacity calculation
SCH and FCH power control modeling
Reverse and Forward link SCH data rate downgrading (1xRTT)
Reverse link power control simulation including data rate downgrading (1xEV-DO)
Forward and Reverse link coverage per SCH rate (1xRTT)
Forward and Reverse link prediction plots per data rate (1xEV-DO)
Neighbor and PN-offset Planning
Manual and automatic neighbor planning

Multi-carrier neighbor planning
Automatic PN-offset allocation
PN-offset allocation analysis
10-10

80-W1527-2 Rev C
Analysis During the Network Planning Phases

Statistical analysis (coverage and Ec/I0) should be run initially to verify that the coverage
objectives are achieved without creating significant Forward link interference (unloaded case).
Lack of coverage should be addressed through coverage improvement techniques such as:
Adding a sector or site
Increasing the antenna gain
Reducing miscellaneous losses (feeder, jumper, etc.)
Increasing HPA power
When coverage and unloaded network objectives are met, run a Monte Carlo simulation to verify
network behavior under the anticipated load. In particular, verify that the network has sufficient
sectors/sites to handle the traffic. This simulation helps to focus optimization efforts on the areas
that carry the most traffic.
Dynamic simulation improves the accuracy of the Monte Carlo simulation, especially for PS data
applications, but are not commonly used.
10-11

80-W1527-2 Rev C
Notes
10-12

80-W1527-2 Rev C
Monte Carlo Simulation

Several Monte Carlo iterations must be run to obtain results that have statistical validity.
Depending on the number of users distributed, 20 to 50 iterations minimum should be run.
10-13

80-W1527-2 Rev C
Traffic Density
For simulations that use a Monte Carlo or similar statistical distribution analysis, two loops are
defined. The name of the loops can change from vendor to vendor, but they have the following
main purposes:
Trial or distribution During each trial, users are distributed over the area, based on rules
set by the traffic maps, clutter weighting, call models, etc. After the users are distributed,
the tool tries to reach a stable state by performing iterations.
Iteration During a trial, the iterations are similar to the power control process. The
power to (and from) each mobile is varied over fixed increments until a stable condition is
achieved, i.e. the convergence limit has been reached. If convergence cannot be reached,
the iteration stops when a preset number of iterations have run. The convergence limit can
be path loss, SIR, Ec/I0, or RSCP, to name a few.
10-14

80-W1527-2 Rev C
Notes
10-15

80-W1527-2 Rev C
Notes
10-16

80-W1527-2 Rev C
Notes
10-17

80-W1527-2 Rev C
Notes
10-18

80-W1527-2 Rev C
Notes
10-19

80-W1527-2 Rev C
Costs and ACP

The term cost is used in two different way in an Automatic Cell Planning tool. For each of the
changes (degree of freedom), a financial cost can be associated. This cost is used by the tool to
prioritize the type of change, in order to minimize the total cost of an optimization task.
The term cost is also used in cost function. This refers to the quantification of the improvement
made during the optimization to verify if system performance has improved.
10-20

80-W1527-2 Rev C
Notes
10-21

80-W1527-2 Rev C
Notes
10-22

80-W1527-2 Rev C
Notes
10-23

80-W1527-2 Rev C
Notes
10-24

80-W1527-2 Rev C
Notes
10-25

80-W1527-2 Rev C
Monte Carlo Simulation Results

Different tool implementations will produce different results, but Monte Carlo results should be
available in two forms: plots and statistics. Both forms should present the main cause of failures
to assist solving the issues.
The plots are mainly used to quickly identify areas with a high number of failures. Such areas
can be a priority for optimization.
For the statistical results, in addition to average values (such as failure rate) it is important to
have a representation of the distribution (e.g., standard deviation). With both average values and
standard deviation, margin can be estimated. Margins can be used to determine the number of
resources required (e.g., channel elements).
10-26

80-W1527-2 Rev C
Solving Failures
Low Pilot: This type of failure should be detected only in an area where coverage (Ec/I0) issues
were detected. This failure can indicate either low coverage or high interference. In an area
where low Pilot is detected, both the coverage (Ec) and the interference (Ec/Io) should be
observed.
Insufficient Mobile Power: This type of failure typically indicates high Reverse link
interference (low Pilot would otherwise be detected), or it could indicate unbalanced links. This
would be the case for high data rate because the required MS Tx power increases as a function of
the data rate, thus limiting the coverage for high data rate (coverage is discussed later in this
section).
Insufficient Channel Power: This type of failure indicates insufficient FL TCH power
assignment. FL power is consumed mostly by FL interference and, to a lesser extent, path loss.
To address insufficient channel power, first investigate FL interference (see coverage, discussed
later in this section), then increase the maximum power allocation for the failing data rate.
Maintain a balance between FL load saturation (exhaustion of HPA) and individual link failure
(Ptch > Ptchmax). An equal amount of failures between these two causes indicates a good tradeoff between coverage (Ptch > Ptchmax) and capacity (FL load saturation). Also consider data
rate: This type of failure for PS data service does not necessarily prevent service for the user; it
may only indicate that a lower data rate would be available at that location.
10-27

80-W1527-2 Rev C
Solving Failures (continued)

RL Noise Rise: May be due to the number of users, or excessive RL interference caused by
unbalanced Forward and Reverse links. High RL interference can be created if the maximum
Active Set size is set too low. In this case, the MS can be in the coverage of the sector, but not
allowed to be in HO with the sector. As a result, the MS cannot be power controlled by this
sector and may transmit at a higher power, causing excess RL interference.
Power Saturation: Indicates exhaustion of HPA resources. This could be caused by too many
users in the cell, or the users require too much power. The latter case indicates FL interference.
FL load saturation and coverage (Ptch > Ptchmax) need to be balanced.
Channel Element Saturation: Channel element consumption is implementation specific;
therefore, CE settings for Monte Carlo simulation should correspond to the actual BTS used.
Monte Carlo simulation can be used to dimension a-posteriori the channel element for each site
by converting the number of traffic channels to channel elements, as appropriate for equipment
vendor specifications. The Erlang B formula can be used to convert traffic (link or RB) into
required resources. To prevent blocking due to channel element saturation, a low blocking rate
(typically 0.1 to 0.5%) should be used.
Code Saturation: In the absence of FL load saturation, this would occur when inefficient
applications are predominant in the network, or if the channel conditions are abnormally good.
Until Equalizer and Received diversity is widely deployed, power (FL saturation) is expected to
be the main cause of blocking in the FL. Usage of RC4 can reduce code saturation, but typically
at the expense of higher FL power used per link.
10-28

80-W1527-2 Rev C
Notes
10-29

80-W1527-2 Rev C
Reducing Sector Power

While it is theoretically possible to reduce the site overlap by changing the sector total power, it
is not a recommended approach. The impact of such a change would negatively impact capacity
and link balance in ways that may not be evident when evaluating the change.
10-30

80-W1527-2 Rev C
CDMA Prediction Plots and Displayed Parameters

For an initial evaluation, all plots can be based on a static configuration.
1. Coverage (signal level) is first verification of system quality, because without coverage no
service can be achieved.
2. After Pilot coverage is confirmed, verify the quality of the configuration using Pilot
reception analysis. For an unloaded system, any area with an Ec/N0 lower than -9 dB should
be improved. This threshold corresponds to three equal overlapping sectors.
3. After coverage and interference are under control, verify if coverage of the sites is
contiguous without any major issues such as sector fragmentation, coverage imbalance
between adjacent sites, or sector overshooting.
4. Finally, estimate Pilot and Forward and Reverse link coverage over the effective service
area.
10-31

80-W1527-2 Rev C
Debugging
A second plot analysis identifies solutions to the problems indicated in the initial plot analysis.
The Pilot pollution plot shows areas with a high number of potential (e.g., strong) servers.
Combine this plot with a spider cursor to see which servers are present and determine which
servers should be removed or reduced in the area.
If multiple area show issues, a more systematic (but longer) approach is to verify the coverage of
each individual server and control any server that is over-propagating (e.g., detected with a
strong level past the 2nd tier).
10-32

80-W1527-2 Rev C
Advanced Evaluation
After completing the initial evaluation and optimization of the system, run a Monte Carlo
simulation. From this simulation, a secondary set of plots can be drawn to determine the
performance of the common channels and dedicated channels, both RL and FL.
10-33

80-W1527-2 Rev C
Notes
10-34

80-W1527-2 Rev C
Example of Statistics used During Analysis

Analysis of 1xRTT sectors
Total FL power, total FL FCH power, total FL SCH power, FL load factor, percentage of
power used, etc.
RL load factor, RL noise rise and reuse factor
Number of users connected on RL and FL
Number of Walsh codes used
RL and FL allocated throughput
Percentage of users in handoff
Analysis of 1xEV-DO sectors
Information related to RL mobile power (total noise, load factor, reuse factor, etc.)
Number of users connected on RL
RL and FL allocated throughput
Percentage of users in handoff
10-35

80-W1527-2 Rev C
Notes
10-36

80-W1527-2 Rev C
Notes
10-37

80-W1527-2 Rev C
Comments/Notes
10-38

Section 11: Layer 1 and Other Parameters
80-W1527-2 Rev C
Notes
11-1

80-W1527-2 Rev C
Notes
11-2

80-W1527-2 Rev C
Notes
11-3

80-W1527-2 Rev C
Types of CDMA Handoffs Overview

CDMA supports mobile handoff from one cell to another while the mobile is on a Traffic Channel or
in the Idle state.
The in-traffic transition from one cell to another can be either a soft handoff or a hard handoff.
Transition from one cell to another while in the Idle state must be a hard handoff.
Access handoff has multiple forms:
Access Entry handoff is an Idle handoff before the handoff process begins.
Access Probe handoff sends the Access probes to different sectors or different Base Stations.
Access handoff transfers the reception of the Paging Channel from one Base Station to
another while the mobile is in the System Access State, but after an Access Attempt.
11-4

80-W1527-2 Rev C
Soft Handoff Flow
1. Pilot strength exceeds T_ADD. The mobile sends a Pilot Strength Measurement message and
transfers Pilot to the Candidate Set.
2. The Base Station sends an Extended Handoff Direction message or General Handoff
Direction message.
3. The mobile transfers the Pilot to the Active Set and sends a Handoff Completion message.
4. Pilot strength drops below T_DROP. The mobile starts the handoff drop timer.
5. Handoff drop timer expires. The mobile sends a Pilot Strength Measurement message.
6. The Base Station sends an Extended Handoff Direction message or a General Handoff
Direction message.
7. The mobile moves the Pilot from the Active Set to the Neighbor Set and sends a Handoff
Completion message.
11-5

80-W1527-2 Rev C
Notes
11-6

80-W1527-2 Rev C
Notes
11-7

80-W1527-2 Rev C
Notes
11-8

80-W1527-2 Rev C
Additional Parameters
In addition to the main three HO parameters, additional HO parameters exist to control the timing of
the HO (t_tdrop), provide additional reporting capabilities (t_comp), or help reduced the AS size
(soft-slope, ADD_INTERCEPT, DROP_INTERCEPT).
For additional details, sign up for CDMA Universitys CDMA

Engineering Basics or CDMA2000 1X Protocols and Signaling.
11-9

80-W1527-2 Rev C
T_ADD and T_DROP Usage in Network Planning Tools

Not all network planning tools use the values for T_Add and T_Drop the same way. Some tools use
T_Add to add a server to the Active Set (as it should be) but use T_Drop as the threshold to
determine that no servers are usable.
For these and all other network planning tool settings, it is critical to understand how the parameter
is used in the tool.
Soft/Softer DRC gain in Network Planning Tools
When implemented, this parameter helps compensate for the static nature of the network planning
tools. Without such implementation, in the soft and softer area, the predicted throughput is much
lower than typically measured in the field.
11-10

80-W1527-2 Rev C
Handoff and Monte Carlo Simulations
Network planning tools can estimate handoff statistics, based on Monte Carlo simulations. In
addition, planning tools may provide plots that represent individual simulations. In the plot above,
the handoff status is displayed as X/Y where Y is the number of sectors to which the mobile is
connected and X is the number of sites. For example, 2/3 means that a particular mobile is
connected to three different sectors on two sites.
In addition to Monte Carlo-based plots and statistics, network planning tools can provide static
views of HO, based solely on Ec/I0 differences between servers.
11-11

80-W1527-2 Rev C
Notes
11-12

80-W1527-2 Rev C
Notes
11-13

80-W1527-2 Rev C
Notes
11-14

80-W1527-2 Rev C
Soft Handoff Increases Capacity

There are several important reasons to place in soft handoff any additional Base Stations that can be
detected by the mobile as soon as possible:
1. Improve voice quality: Cell boundaries usually offer poor coverage coupled with
increased interference from other cells. Traffic Channel diversity from additional cells will
improve voice quality.
2. Control mobile interference: While on a boundary of a cell, high Tx power of a mobile can
be a source of interference to mobiles in other cells. Power control from these cells is
important to reduce the interference.
3. Reduce dropped call probabilities: In handoff areas, the Forward link is most vulnerable.
A slow handoff process coupled with a vehicle moving at a high speed may cause a call to be
dropped if the mobile becomes unable to demodulate the Forward link transmitted from the
original cell, and looses the Handoff Direction message.
4. Increase RL capacity and coverage: Soft handoff considerably increases both the RL
capacity of a heavily-loaded cellular system and the coverage of each individual cell in a
lightly-loaded system.
11-15

80-W1527-2 Rev C
Notes
11-16

80-W1527-2 Rev C
Handoff Threshold
Depending on the tool implementation, the threshold used for HO can be related to T_Add or
T_Drop.
11-17

80-W1527-2 Rev C
The Handoff Reduction Factor = 2.13

Handoff reduction factor is typically used to measure how many air links are required to support
each individual user. When this factor increases, the call retention performance can be improved,
but cell capacity decreases.
11-18

80-W1527-2 Rev C
Notes
11-19

80-W1527-2 Rev C
Notes
11-20

80-W1527-2 Rev C
Notes
11-21

80-W1527-2 Rev C
Notes
11-22

80-W1527-2 Rev C
Notes
11-23

80-W1527-2 Rev C
Notes
11-24

80-W1527-2 Rev C
Notes
11-25

80-W1527-2 Rev C
Notes
11-26

80-W1527-2 Rev C
Notes
11-27

80-W1527-2 Rev C
Notes
11-28

80-W1527-2 Rev C
Notes
11-29

80-W1527-2 Rev C
HHO Zone Allocation
The HHO area defined by Ec/I0 thresholds is changing with load.
11-30

80-W1527-2 Rev C
Notes
11-31

80-W1527-2 Rev C
Notes
11-32

80-W1527-2 Rev C
Search Windows and Propagation Delays

Search windows should be wide open to accommodate the propagation delays. Typically, the worst
case would correspond to propagation delays equivalent to the difference of the distance to the
reference server and the distance to the farthest neighbor (plus eventual multipath). Once the
distance is found it can be converted in chips using:
estimated _ Srch _ Win _ N = 2.
d *w
c
with
d = distance in meters
w = chiprate (1228800)
c = speed of light 3.00 *108
11-33

80-W1527-2 Rev C
Notes
11-34

80-W1527-2 Rev C
Notes
11-35

80-W1527-2 Rev C
Notes
11-36

80-W1527-2 Rev C
PILOT_INC Parameter
The PILOT_INC parameter defines the set of PN offsets that the mobile will search, particularly for
the Remaining Set search.
Pilot_INC cannot be set only to increase the PN space. It needs to be set in accordance with the
required search window: if the propagation delay is longer than Pilot_INC, the PN offset would
not be accurately estimated from the PN Phase.
11-37

80-W1527-2 Rev C
Notes
11-38

80-W1527-2 Rev C
Notes
11-39

80-W1527-2 Rev C
Notes
11-40

80-W1527-2 Rev C
Notes
11-41

80-W1527-2 Rev C
Notes
11-42

80-W1527-2 Rev C
Notes
11-43

80-W1527-2 Rev C
Generic Considerations
A cell not included in the Neighbor List has a low probability of being added to the Active Set,
because the remainder set is searched infrequently. Even if reported, a remainder set sector
neighbor cell will not necessarily be added to the Active Set. The Base Station Controller (BSC),
based on vendor implementation, can ignore any reported set cells or, more commonly, report them
through the O&M.
The issue with Neighbor List length is one of balance. A short Neighbor List makes the search faster,
thus increasing the probability of detecting a fast-rising Pilot. On the other hand, a short Neighbor
List increases the risk of leaving out a required neighbor, thus failing a handoff.
The inverse could be said about a long list. The probability of leaving out a neighbor is low, but the
risk of not searching all the neighbors often enough increases the possibility of failing a handoff to a
fast-rising Pilot.
11-44

80-W1527-2 Rev C
Notes
11-45

80-W1527-2 Rev C
Using the Neighbor List
Neighbor List length can serve as a quality indicator, using the following process (the exact process
depends on the tool):
1. Run a simulation, low load.
2. Run the Neighbor List planning utility for very small overlap (1% or less).
3. Do not set a maximum Neighbor List length (unless the tool requires a limit).
4. Make the Neighbor List symmetric.
5. Study further any cell with more than 16 neighbors.
This limit of 16 on the Neighbor List is completely empirical. Adjust (increase) it to prioritize the
work.
For a one-layer system, one carrier, 16 should be considered the maximum length for a Neighbor
List. Ideally, the length should be trimmed to 9 to 14not by removing the low probability
neighbor, but by adjusting the RF configuration until the Neighbor List length is acceptable. This not
only reduces the Neighbor List length but, more importantly, reduces interference from other cells.
11-46

80-W1527-2 Rev C
Notes
11-47

80-W1527-2 Rev C
Location Areas
Ideally, paging zone planning should consider the loading on the common channels, particularly the
Paging Channel (F-PCH).
Estimating the F-PCH load, and thus planning the zones, is beyond the scope of this course.
11-48

80-W1527-2 Rev C
Notes
11-49

80-W1527-2 Rev C
Notes
11-50

80-W1527-2 Rev C
Notes
11-51

80-W1527-2 Rev C
Notes
11-52

Section 12: Practical Considerations for Network Planning
80-W1527-2 Rev C
Notes
12-1

80-W1527-2 Rev C
Notes
12-2

80-W1527-2 Rev C
Notes
12-3

80-W1527-2 Rev C
Near Parts
Antenna near parts contribute additional loss or gain in the transmission line.
The standard does not provide guidance for antenna near parts, but they are all critical for
implementation.
Antenna near parts can be divided in two categories:
Always Considered:
Antenna
Feeder
BTS reference point
Optional, depending on site implementation:
Power booster
TMA
Diplexer
Surge protector/lighting arrestor
Bias injector
Remote electrical tilt system
Each component has an impact on the Link Budget, so must be selected carefully.
12-4

80-W1527-2 Rev C
Notes
12-5

80-W1527-2 Rev C
Antenna Radiation Pattern

Antenna pattern is the most critical characteristic of an antenna. Null-fill pattern will likely
affect prediction, but will have limited effect in urban environments. In this morphology, the
reflection and diffraction dominate to limit the accuracy of the prediction.
The quality of the upper sidelobes can affect interference at the edge of coverage. Pay
attention to this characteristic when high level downtilt will be applied. If the first upper
sidelobe points to the horizon, coverage (interference in this case) can be increased by the
difference between the first null and first upper sidelobe (typically 15 to 25 dB).
12-6

80-W1527-2 Rev C
Surge Protectors/Lightning Arrestors

Typical attenuation for surge protectors/lightning arrestors:
Polyphaser: < 0.1 dB
Huber & Suhner: < 0.2 dB
Additional considerations:
If TMA or RET is used, the arrestor should not block the bias or command.
The connector must be compatible with the other devices!
12-7

80-W1527-2 Rev C
Tails or Jumpers
The following table shows typical linear losses (dB/100 m):
Cable type
----------------------
Size
---------
Frequency
------------------------------------------------900 MHz
1800 MHz
2100 MHz
Andrew FSJ1-50A
1/4"
18.4
26.9
29.2
Andrew ETS1-50T
1/4"
18.1
26.2
28.5
Andrew FSJ2-50A
3/8"
12.5
18.5
20.1
Andrew ETS2-50T
3/8"
13
19.4
21.2
Andrew FSJ4-50B
1/2"
11.1
16.6
18.1
For 3 m length, connector loss cannot be neglected.
12-8

80-W1527-2 Rev C
Notes
12-9

80-W1527-2 Rev C
Notes
12-10

80-W1527-2 Rev C
LNA and link balance

With the addition of a TMA, the Reverse link MAPL increases. The feeder loss can typically
be set to zero (0) and the noise figure improves. In contrast, the Forward link is impacted by
the through loss of the TMA.
There are three schools of thought about when or whether to use LNAs:
1. Install them everywhere.
2. Install them only when needed, i.e., when the RL is limiting.
3. Plan them everywhere (for site acquisition and tower loading analysis) but install
only where needed.
During analysis, it is much easier to run the simulation without LNAs, optimize the RF
configuration, and then add LNAs when the main cause of blocking is insufficient Reverse
link.
12-11

80-W1527-2 Rev C
LNA Noise Factor Calculation
For an active system, Receiver (Rx) and LNA, the gain and noise factor should be
known.
Example:
NFRx: BTS noise figure, typically 2 to 5 dB (1.6 to 3.2)
NFLNA: LNA noise figure, typically 1.5 to 2.5 dB (1.4 to 1.8)
GNLA: LNA gain, typically 12 to 25 dB (15.8 to 316)
For a passive system, feeder (feed), the gain is the inverse of the loss, the noise
factor is the loss.
Example:
Gfeed: Feeder gain = - feeder loss, typically -2 to -6 dB (0.6 to 0.2)
NFfeed: Noise figure of the feeder, set as feeder loss 2 to 6 dB (1.6 to 4)
By summing the passive components, the equation can be used with only three
devices.
12-12

80-W1527-2 Rev C
Notes
12-13

80-W1527-2 Rev C
Antenna Gain
Gain of the antenna is a ratio of the transmitted power in the direction of the antenna to the
uniform value of the Reference antenna.
If the Reference antenna is an isotropic radiator, the absolute gain (dBi) is calculated.
If the Reference antenna is a half-wave dipole, the relative gain (dBd) is calculated.
Absolute gain (dBi) = Relative gain (dBd) + 2.15 dB
Front-to-Back Ratio
A minimum of 20 dB is recommended.
Elevation (vertical) Beam Width
Beamwidth depends on the antenna gain and size (and number of elements). A nominal
value of 7 degrees is recommended for PCS frequencies. For lower frequencies (450 or 850
MHz), where size restrictions limit the number of elements, the vertical beamwidth is
typically limited to 10 to 20 degrees.
Upper Sidelobe Suppression
Sidelobes up to 20 degrees above the main lobe shall be suppressed by 18 dB relative to the
peak gain.
12-14

80-W1527-2 Rev C
Notes
12-15

80-W1527-2 Rev C
Null-Fill and morphologies

In urban area, assuming that the antenna are not located high above ground level, the
scattering is generally sufficient to avoid creating coverage hole directly below the antenna.
In rural area, or more generally when antenna are mounted very high above ground, null-fill
prevents the apparition of coverage holes just below the antenna.
12-16

80-W1527-2 Rev C
Notes
12-17

80-W1527-2 Rev C
Notes
12-18

80-W1527-2 Rev C
Antenna Downtilt: EDT and MDT

Downtilt can be achieved either electrically or mechanically.
For Electrical downtilt (EDT), the phase between the different antenna elements is varied to
steer the antenna pattern. This same concept is used in beam forming antennas.
To use Mechanical downtilt (MDT), a tilting bracket typically must be included during
antenna installation. MDT is achieved simply by changing the antenna mounting angle.
12-19

80-W1527-2 Rev C
Optimum Downtilt
[1] J.Niemela, T.Isotalo, J.Lempiainen, Optimum Antenna Downtilt Angles for Macrocellular
WCDMA Network, EURASIP Journal on Wireless Communications and Networking 2005:5.
Note that this empirical formula was set to match results of simulations performed at 2100
MHz while trying to increase the capacity of the system. Therefore the resulting downtilt
when applying the formula would be applicable in capacity design (not coverage), with
short site-to-site distance.
12-20

80-W1527-2 Rev C
Notes
12-21

80-W1527-2 Rev C
EDT vs. MDT: Narrow (V) Beam Antenna

For narrow beam antennas, similar attenuation can be achieved in the bore sight with
either mechanical or electrical DT. The main difference is outside of the bore sight, where
MDT shows less attenuation.
12-22

80-W1527-2 Rev C
EDT vs MDT: Large (V) Antenna Beamwidth

As the antenna beamwidth (V) increases, the difference between electrical and mechanical
DT increases. For EDT, larger attenuation can be achieved with the same DT angle.
12-23

80-W1527-2 Rev C
EDT
EDT always changes the Vertical Radiation Pattern. For many types of antennas, this
increases side lobe strength, and decreases separation between the main lobe and side lobe.
In this example:
0 EDT
Side lobe strength: -20.2 dB
Side lobe separation from main lobe: 21
12 EDT
Side lobe strength: -11.4 dB
Side lobe separation from main lobe: 18
This phenomenon can significantly increase Pilot pollution on upper floors in an urban
area.
12-24

80-W1527-2 Rev C
Notes
12-25

80-W1527-2 Rev C
Notes
12-26

80-W1527-2 Rev C
Notes
12-27

80-W1527-2 Rev C
Site Survey Checklist

Site selection can only be done after visiting the candidate sites. Prior to the site survey,
conduct research to determine the best candidate; however, only a site visit can reveal all
the potential problems with a site.
Maintain a detailed site survey checklist and photographs to ensure accurate and consistent
data sharing within a team.
12-28

80-W1527-2 Rev C
Notes
12-29

80-W1527-2 Rev C
Notes
12-30

80-W1527-2 Rev C
Notes
12-31

80-W1527-2 Rev C
Site Off-Grid
Selecting a site off-grid is a necessary evil in a commercial deployment. Site acquisition and
uneven traffic distribution are the main factors that impose the selection of sites off-grid.
Compared with the same area and same number of sites, site off-grid will have the effect of:
Degrading the frequency reuse efficiency (Ff), both in terms of average and mainly
standard deviation.
Increasing the HO reduction factor.
From this observation, we can conclude that when sites must be selected off-grid, additional
optimization will be required to ensure system performance.
12-32

80-W1527-2 Rev C
Height Difference
If sites must be off-height (usually for site acquisition reasons), the negative impact of sites
off-grid is increased.
In such case, it become even more important to:
Control the coverage of each cell.
Control the overlap between cells.
Limit the number of cells detected in a given area.
12-33

80-W1527-2 Rev C
Site Off-Grid and Height Distance

The plots shown in this course have been overviews of an entire planned area. Such plots
are good for a high-level view, but do not help illuminate or solve specific problems.
Detailed maps are needed for problem solving.
When handoff cursors are available, it is useful to verify whether the best server in a given
area is the expected one. In both of these examples, calls are in HO with a distant server and
the main issue is an increase in other cell interference. The impact is greater than what is
shown. Often, a distant site can be detected, but it is not strong enough to be a HO candidate,
or even to be promoted to the Active Set. The result is increased interference, without the
possibility of using the signal.
The same concept is shown in the best server plot, where it is easier to visualize. The
challenge in both cases is to distinguish normal conditions (due to terrain, for example)
from other issues, such as poor site selection or incomplete optimization.
These additional views also can help identify problems:
Individual cell Ec/I0 Helps identify cells that are detected at a given level far away.
Cell count (above Ec/I0, HO candidate, etc.) Helps identify areas in which too many
servers are detected.
Bin query Helps identify the servers available in a given Bin. This information is
similar to the two previous plots, but provides numerical data for further analysis.
12-34

80-W1527-2 Rev C
High Capacity Solutions

High capacity solutions should be treated differently for Forward and Reverse links,
according to which is the limiting link. On the Reverse link, capacity can be increased by any
device that improves the Eb/Nt requirement, for example, MUD. On the Forward link, the
goal to reduce the required Eb/Nt is the same; however, the implementation differs because
only the transmit chain is available, for example, Tx diversity.
12-35

80-W1527-2 Rev C
Repeater Sites
There are many reasons to install a repeater rather than a BTS. As an example, equipment
size can be a driver. In this case, not only the size of the equipment (BTS or repeater) itself,
but also the size of the antenna system (antenna, TMA, feeder).
For the antenna system, for a repeater, it is necessary to consider configuration that would
allow achieving the proper isolation between the donor and server antenna. This
requirement affects site acquisition because two antenna positions must be available, with
sufficient separation.
Carefully consider the installation of a repeater to extend coverage without adding capacity.
A repeater does not increase the coverage in CDMA, but instead changes the coverage area.
Forward link coverage is extended regardless of capacity, but Reverse link coverage is
reduced due to the increased noise at the BTS. Depending on the limiting link, coverage may
be reduced (worst case) or moved (best case). In this last case, the coverage is extended in
the repeater coverage area, but at the expanse of a reduction of the main antenna area.
12-36

80-W1527-2 Rev C
Repeater Sites Details

Modeling a repeater can be challenging in CDMA. Considering only the path loss will not
give accurate results. The main limitation in repeater modeling is how to simulate
interference.
To model all interference on the Forward link, the tool should complete a path loss
analysis on the donor side. This implies using the donor antenna pattern in the
analysis, with an RF model that is compatible with the propagation condition (line of
sight).
On the Reverse link, modeling interference implies evaluating both the rise over
thermal and the increased Eb/Nt requirements due to the lack of diversity.
If a tool is used to evaluate the hardware requirements, the last aspect to consider is traffic.
Ideally, traffic at the donor site should include the sum of the traffic in the primary coverage
area and the repeater coverage area.
12-37

80-W1527-2 Rev C
Notes
12-38

80-W1527-2 Rev C
Notes
12-39

80-W1527-2 Rev C
Comments/Notes
12-40

Section 13: Overlays
80-W1527-2 Rev C
Notes
13-1

80-W1527-2 Rev C
Notes
13-2

80-W1527-2 Rev C
Notes
13-3

80-W1527-2 Rev C
Notes
13-4

80-W1527-2 Rev C
Limiting Service
The expected data rate at cell edge should be considered when determining the limiting service or
the limiting link. If 9.6 kbps is required, then EV-DO and voice have similar (if not identical) MAPL. If
the system is planned for higher data rates (38.4 kbps or 153 kbps typically on the Reverse link),
then the EV-DO footprint would be reduced compared to voice.
Capacity Limitation
For capacity, the limiting service depends on the business model and the number of carriers that can
be used for each of the services.
13-5

80-W1527-2 Rev C
Hotspot Deployment
Hotspot deployment of EV-DO can be done initially to relieve capacity constraints in a CDMA2000
system, if the capacity constraint is for data usage. As discussed in Section 9,
EV-DO capacity (sector throughput) can be estimated at 2 to 4 times more than CDMA2000 (data).
However, subscriber expectations should be carefully managed. Hotspot deployment can result in
low perceived QoS because the high data rate available with EV-DO can be achieved only in the
hotspot.
13-6

80-W1527-2 Rev C
Notes
13-7

80-W1527-2 Rev C
Hybrid Mode
A hybrid EV-DO terminal is constantly monitoring the Ec/I0 of both the 1X and EV-DO networks. 1X
system acquisition normally takes place when the Ec/I0 of a 1X system becomes stronger than the
Ec/I0 of EV-DO minus 7 dB, which can be interpreted as the equal power point of 1X and EV-DO, if
the 1X system is fully loaded.
13-8

80-W1527-2 Rev C
Notes
13-9

80-W1527-2 Rev C
Notes
13-10

80-W1527-2 Rev C
Notes
13-11

80-W1527-2 Rev C
Notes
13-12

80-W1527-2 Rev C
Notes
13-13

80-W1527-2 Rev C
Notes
13-14

80-W1527-2 Rev C
Notes
13-15

80-W1527-2 Rev C
Different Frequency Bands

When EV-DO is deployed on lower frequencies, it causes higher interference if the same antennas
are used for both 1X and EV-DO. There are more rejections due to high RoT, but overall system GoS
is higher due to better in-building coverage.
13-16

80-W1527-2 Rev C
Notes
13-17

80-W1527-2 Rev C
Comments/Notes
13-18

Section 14: Capacity Planning Considerations
80-W1527-2 Rev C
Notes
14-1

80-W1527-2 Rev C
Notes
14-2

80-W1527-2 Rev C
Notes
14-3

80-W1527-2 Rev C
Notes
14-4

80-W1527-2 Rev C
Notes
14-5

80-W1527-2 Rev C
Notes
14-6

80-W1527-2 Rev C
Capacity
For spreadsheet design, the easiest way to estimate capacity is by morphology. However, actual
traffic distribution depends on multiple parameters.
14-7

80-W1527-2 Rev C
Typical Capacity Design
For data services, the capacity requirement can be expressed in various ways:
Monthly Data Usage Typically in MB; can be used to estimate busy hour usage.
Busy Hour Usage Can be given either in KB or average kbps.
Busy Hour Usage, Application Considers number of sessions, not the volume of data.
Convert to KB or kbps, based on the application.
For RF network planning tools, convert the data into kbps or Erlangs.
Because data and voice usage do not follow the same pattern, you may need two traffic requirement
tables:
Data busy hour usage.
Voice busy hour usage.
At this stage, it is very important to agree on the peak-to-average ratio, and make sure all members
of the design team use the same ratio.
14-8

80-W1527-2 Rev C
Notes
14-9

80-W1527-2 Rev C
Notes
14-10

80-W1527-2 Rev C
Notes
14-11

80-W1527-2 Rev C
EV-DO Network Statistics to Monitor Capacity Growth
Simultaneous active flows A flow is considered active if the reservation for the flow has
been turned on.
Flow-specific traffic utilization Count of bytes transmitted for a given flow / Count of
transmitted bytes for all flows over the sample period.
Per-flow utilization Count of slots transmitted for a given flow / Count of transmitted slots
Forward Physical Layer throughput Total number of Physical Layer Bits transmitted
over a given time interval.
Reverse Physical Layer throughput Total number of Physical Layer Bits transmitted over
a given time interval.
Packet drop due to exceeding the delay limit Count of IP packets dropped due to
exceeding the delay limit / (Count of IP packets transmitted + Total number of drops)
Driver flow buffer utilization Count of packets in the buffer / Maximum buffer capacity.
14-12

80-W1527-2 Rev C
Notes
14-13

80-W1527-2 Rev C
Notes
14-14

80-W1527-2 Rev C
Capacity Planning Considerations Introduction
RF optimization Controlling interference helps reduce FL power utilization. Consider this

approach when the measured sector capacity falls below expectations. RF optimization mainly
relieves capacity congestion on the FL (high power utilization) but also improves the HO reduction
factor. To some extent, it also improves the RL by reducing cell overlap.
Adding RC4 This action mainly relieves Walsh code channel congestion. Consider this approach
only when forward power utilization is low, because RC4 is less efficient (in terms of power
utilization) than RC3. When forward power utilization is high, adding RC4 may only minimally
improve overall system capacity and shift the cause of congestion from code channel blocking to
forward power blocking. RC4 is typically introduced dynamically: the MS is assigned RC3 or RC4 to
balance both code channel and power utilization.
Change in power setting Changing the power allocation of the control channels can increase the
power available for the traffic channel, but it can also change the FL/RL balance. An alternative way
to increase power available for the traffic channel is to increase the total power available (HPA
rating) and set the common channel to the same absolute power. This technique can work if applied
to an isolated sector. Applying it to all sectors in an area increases FL interference which increases
the power requirement for all the FL channels, resulting in no gain overall.
Additional carriers Capacity can be increased by adding carriers in the cells/sectors of increased
traffic demand. Adding carriers increases all the resources (code channel, forward power, etc.)
except channel elements. Vendor implementation dictates if the existing channel element pool can
be shared across carriers (typical). If CEs are shared across carriers, CE utilization should be
monitored to determine when to increase the resource pool.
14-15

80-W1527-2 Rev C
Capacity Planning Considerations Introduction
Cell (or sector) splitting Capacity can be increased by adding cell sites (or sectors). RF
optimization also should be done when cells (or sectors) are added to the system. Without RF
optimization, the additional cells (or sectors) will increase FL interference and the HO distribution,
both of which could reduce system capacity.
Introduction of EV-DO If a 1X system is heavily loaded with data traffic, adding EV-DO can
increase capacity by increasing spectrum efficiency.
14-16

80-W1527-2 Rev C
Notes
14-17

80-W1527-2 Rev C
Notes
14-18

80-W1527-2 Rev C
Notes
14-19

80-W1527-2 Rev C
Notes
14-20

Section 15: Course Summary
80-W1527-2 Rev C
Notes
15-1

80-W1527-2 Rev C
Notes
15-2

80-W1527-2 Rev C
Summary
This Link Budget excerpt illustrates:

Maximum path loss
+
+
EIRP
Sensitivity
Receiver loss and gain
Propagation components
From this maximum path loss one can determine a Reverse link value, which is equivalent to a
signal strength design level.
15-3

80-W1527-2 Rev C
Equality Coverage Comparison
The normal setting is a combination of both Link Budgets (equal coverage and equal power).
Coverage should be equal for all classes of service (conversational speech, streaming, interactive).
For a given class of service (e.g., interactive) the power setting will be the same for all data rates. In
this case, the power should be set to provide coverage over the entire cell at the minimum
acceptable data rate.
15-4

80-W1527-2 Rev C
CDMA Bands
The 800 MHz band is the most commonly used band for CDMA operations. More than two-thirds of
the CDMA mobiles are in this band. This band is also called the US Cellular band or band class 0 in
CDMA terminology.
15-5

80-W1527-2 Rev C
Notes
15-6

80-W1527-2 Rev C
Notes
15-7

80-W1527-2 Rev C
Notes
15-8

80-W1527-2 Rev C
Different Frequency Band

Deployment of EVDO on lower frequency always causes higher interference if the same antennas
are used for both 1x and EVDO; number of rejection due to high ROT in this case is bigger but overall
system GoS is higher due to better Inbuilding coverage.
15-9

80-W1527-2 Rev C
Notes
15-10

80-W1527-2 Rev C
Notes
15-11

80-W1527-2 Rev C
Notes
15-12

80-W1527-2 Rev C
Notes
15-13

80-W1527-2 Rev C
Comments/Notes
15-14

80-W1527-2 Rev.C CDMA2000 1x and 1xEV-DO Network Planning

Загружено:

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

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

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

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

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

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

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

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

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

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

80-W1527-2 Rev.C CDMA2000 1x and 1xEV-DO Network Planning

Загружено:

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

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

Student Guide

CDG is a registered trademark of the CDMA Development Group. QUALCOMM is a registered

Material Use Restrictions

CDMA2000 1X and 1xEV-DO Network Planning

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

CDMA2000 1X and 1xEV-DO Network Planning

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

CDMA2000 1X and 1xEV-DO Network Planning

Table of Contents Book 2

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

CDMA2000 1X and 1xEV-DO Network Planning

CDMA2000 RL Capacity ....................................................................................... 9-3

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

CDMA2000 1X and 1xEV-DO Network Planning

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

CDMA2000 1X and 1xEV-DO Network Planning

Section 11: Layer 1 and Other Parameters ................................ ....... 11-1

CDMA2000 1X and 1xEV-DO Network Planning

Area Planning .............................................................................................. 11-47

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

CDMA2000 1X and 1xEV-DO Network Planning

Summary ............................................................................................ 12-38

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

CDMA2000 1X and 1xEV-DO Network Planning

Section 15: Course Summary ..................................................................... 15-1

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

CDMA2000 1X and 1xEV-DO Network Planning

This page left blank intentionally.

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

CDMA2000 1X and 1xEV-DO Network Planning

Section 8: Traffic and Capacity

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

CDMA2000 1X and 1xEV-DO Network Planning

Section 8: Traffic and Capacity

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

CDMA2000 1X and 1xEV-DO Network Planning

Section 8: Traffic and Capacity

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

CDMA2000 1X and 1xEV-DO Network Planning

Section 8: Traffic and Capacity

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

CDMA2000 1X and 1xEV-DO Network Planning

Section 8: Traffic and Capacity

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

CDMA2000 1X and 1xEV-DO Network Planning

Section 8: Traffic and Capacity

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

CDMA2000 1X and 1xEV-DO Network Planning

Section 8: Traffic and Capacity

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

CDMA2000 1X and 1xEV-DO Network Planning

Section 8: Traffic and Capacity

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

CDMA2000 1X and 1xEV-DO Network Planning

Section 8: Traffic and Capacity

Traffic profiles and traffic intensity:

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

CDMA2000 1X and 1xEV-DO Network Planning

Section 8: Traffic and Capacity

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

CDMA2000 1X and 1xEV-DO Network Planning

Section 8: Traffic and Capacity

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

CDMA2000 1X and 1xEV-DO Network Planning