You are on page 1of 67

Using AirPro for 1xEV-DO RF Design

Victor Weng
RF Tools & Services Systems Engineering (Victor Dasilva)
vweng@lucent.com
1 (973) 386-4756
February 11th, 2003
Lucent Technologies Proprietary

No.1

Course Objectives
At the end of this presentation you will be able to:
1.Understand the input parameters required for designing an 1xEV-DO
network with AirPro
2.Understand the types of analysis array available in AirPro
3.
Understand the basic concept and equation used in AirPro coverage
analysis
4.
Understand the impact of traffic loading on the coverage analysis
5.
Understand the steps needs to define traffic loading for a 1xEV-DO system
6.
Understand the input and output of AirPro traffic capacity analysis

Lucent Technologies Proprietary

No.2

Outline of the Presentation

Brief Overview of 1x-EV_DO


Section 1: Basic Input for 1xEV-DO Scenario in AirPro
Section 2: Coverage-Related Analyses for 1xEV-DO
Section 3: Traffic Capacity Analysis for 1xEV-DO
Section 4: Live Demo of AirPro for 1xEV-DO

Lucent Technologies Proprietary

No.3

1xEV-DO Overview: Hybrid Channel Scheme

User 3

User 1

User 3

User 2

Code

User 1

1xEV-DOForwardLink:
(1) TimeShared
(2) FullPower
(3) FastBestServingSectorSelection

Time

1xEV-DOReverseLink(Similarto3G1x)
(1) CodeShared
(2) RLSHO
(3) RLPowerControl
Code

User 3
User 2
User 1
Time

Lucent Technologies Proprietary

No.4

Data Rates Supported

Data Rates Supported for 1xEV-DO:

FL data dates:
38.4, 76.8, 153.6, 307.2, 614.4,
921.6, 1228.8, 1843.2, 2457.6
RL data rate:
9.6, 19.2, 38.4, 76.8, 153.6

Lucent Technologies Proprietary

No.5

Single Shared Forward Link with


Fast Rate Adaptation
Pow er
U ser 2
R a te = 3 0 7 .2
kbps

User 1
R a te = 6 1 4 .4
kbps

ID L E

User 3
R a te = 1 .2 2 8
M bps
Lucent Technologies Proprietary

P ilo t
B u rs ts

T im e

Fast Rate Control and


Optimized Scheduling

D R C
D R C

D R C
C /I

C /I
Lucent Technologies Proprietary

C /I

Fast Best Serving Sector Selection


(Virtual SHO)

D R C

D R C

C /I
Lucent Technologies Proprietary

C /I

General workflow for RF Planning with AirPro

Get input from the customer to understand target network performance


Coverage objective
Network capacity objectives

Consult systems engineering team for link budgets (Section 1)


Forward link, reverse link budget
Key QoS-related parameters: Eb/Nt, Ec/Io, T_Add, T_Drop et al

Create Scenario in AirPro

Overlay system:
Add 1xEV-DO technology to the existing IS-95 or 3G1x system by Global Add
Technology
Make sure to use different carrier
Greenfield design
Update all link budget parameters (Section 1)

Perform coverage analysis (Section 2)


Perform traffic capacity analysis (Section 3)
Lucent Technologies Proprietary

No.9

Section 1:
Basic Input for 1xEV-DO Scenario

Cell Site Information (Not to be covered in this session)


General: Site Location, Sector Orientation, Antenna Types, Survey Data, etc.
Site Flags
Propagation Model

Link Budget Parameters

Scenario Level
Data Rate-Dependent Parameters: 3G Traffic Definition
System Parameters
Default Parameters for New Sectors: FL, RL & Others
Sector Level
FL Parameters
RL Parameters
Others

Lucent Technologies Proprietary

No.10

Link Budget: FL Traffic Parameters


Traffic Parameters per Coverage Type (Channel Type):
Default Type:
AWGN (Stationary)
FL Traffic Parameters
Include this rate in analysis

Type 1 Type 2 Type 3 Type 4 Type 5 Type 6 Type 7


1

38.4

76.8

153.6

307.2

614.4

Eb/Nt Required on Forward Link (dB)

2.5

2.5

2.5

2.5

2.5

3.5

7.5

10.5

Ec/Io Required on Forward Link (dB)

-11.62

-8.9

-6.42

-4.3

-2.66

-1.6

-0.92

-0.37

-0.14

Processing Gain (dB)

13.806

10.796

7.786

4.775

1.765

0.004

-1.245

-3.006

-4.255

Forward link Processing Gain Calculation:


3/4:
of time slots are allocated for
data traffic channel

gF _ j

Type 9

Forward Traffic Channel Data Rate (Kbps)

Type 8

921.6 1,228.80 1,843.20 2,457.60

3
*W
10 log10 4
Rj

Lucent Technologies Proprietary

No.11

Link Budget: RL Traffic Parameters


RL Traffic Parameters

Type 1 Type 2 Type 3 Type 4 Type 5

Include this rate in analysis


Reverse Traffic Channel Data Rate (Kbps)
Eb/Nt Required on Reverse Link (dB)
Pilot Channel Ec/Nt Required on Reverse Link (dB)
Traffic Channel Gain over Pilot (dB)
Traffic Channel Activity Factor

9.6

19.2

38.4

4.5

3.6

3.2

-23

-23

-23

-23

-22 For capacity analysis

3.75

6.75

9.75 13.25

18.5 For capacity analysis

76.8 153.6

6 For Coverage Analysis

Processing Gain (dB)

21.08 18.07 15.06 12.05 9.035 Calculated

Pole Capacity (Number of Channels)

27.44 17.75 10.67 5.721 2.182 Calculated

Cell Site Receiver Sensitivity (dBm)

-117.4 -115.9

-114 -111.8 -107.8 Calculated

Reverse Link Processing Gain Calculation:

gR_ j

10 log 10
R
j

Lucent Technologies Proprietary

No.12

Link Budget: RL Traffic Parameters-2


Pole Capacity for Data Rate j
N max j 1

1 10

[(

Ec

Nt

) r req j / 10 ]

1 10 DRC _ Gain / 10

1
j 10 Traffic _ Gain / 10

:
(Ec/Nt)r-req-j

reverse link other sector to same sector interference ratio


reverse link required Ec/Nt for traffic type j, in dB.

DRC_Gain:

DRC channel gain in dB over pilot channel, taken from


reverse link parameters
Traffic channel gain in dB over pilot channel
Reverse link traffic channel activity factor for traffic type j.

Traffic_Gain:
j:

Lucent Technologies Proprietary

No.13

Link Budget: RL Traffic Parameters-3


Cell Site Receiver Sensitivity (dBm)
E
S cell _ rec req j b
Nt

10 * log10 (10

N th _ rev / 10

10 I r ns / 10 ) Rim g R j 10 * log10 (1

r req j

(Eb/Nt)r-req-j

reverse link required Eb/Nt for traffic type j, in dB.

Nth_rev:

thermal noise power at cell site in dBm

Ir-ns :

reverse link non-HDR interference on HDR band (dBm)

gR-j:

Reverse link processing gain for traffic type j in dB

Rim :

receiver interference margin in dB

Nmax-j :

Pole capacity for traffic type j

Lucent Technologies Proprietary

1
N max j

No.14

Link Budget: System Parameters


Scenario Level
System Parameters

Default
Value

Notes

System bandwidth(kHz)
1230
System Chipping Rate(kcps)
1230
Reverse Link Design Margin(dB)
0 Leave as 0 and Ignore them. To be
Forward Link Design Margin(dB)
0 removed in v1.8
AT cable loss
0
AT antenna gain(dBi)
2
Body loss(dB)
0
Max AT amplifier power(Watts)
0.25
AT noise figure(dB)
9
Thermal noise power at AT(dBm)
-104.08 Read-only, Calculated by AirPro
Cell Site noise figure (dB)
5
Thermal noise power at cell(dBm)
-108.08 Read-only, Calculated by AirPro
Non-HDR interfer on HDRband (dBM) (forward link)
-118 External Interference
Non-HDR interfer on HDRband (dBM) (reverse link)
-118 External Interference
Forward anchor transfer margin (dB)
2
Reverse soft handoff gain(dB)
4
RL DRC Gain Over Pilot (dB)
-1.5
PILOT_INC
4
Avg. simultaneously active data sessions (SADS) per subscriber
0 Used for traffic density/capacity
Avg. FL throughput demand (kbps/subscriber)
0 analysis. Get the input from the
Avg. RL throughput demand (kbps/subscriber)
0 customer, consult with SE for traffic

Lucent Technologies Proprietary

No.15

Link Budget: FL Parameters


Forward Link Parameters

Default
Value

Notes

--Scenario Level

Default values for any new sectors

--Sector Level
Amplifier output power @ J4 port (Watts)
Amplifier attenuation (dB)
Cell site cable and associated loss-fwd link (J4 port to ant
Cell Site antenna gain (dBi)
EiRP (total)(Watts)
AT cable loss
AT antenna gain (dBi)
Body loss (dB)
Forward log normal fade margin (dB)
Forward traffic interfer reduction factor
Misc forward link gain (dB)
Forward Link Design Margin (dB)
Building/Vehicle penetration loss (dB)
Default coverage type

8
0
3
Read from Antenna Pattern, only at
sector level
Calculated, only at sector level
Read from System Parameter
Read from System Parameter

10.65
46.6
0
2
0
8.3 Calculated from RL fade margin
Leave it as 0 and Ignore it. To be
0 removed in v1.8
0
0 Read from System Parameter
0
AWGN
only at sector level

Lucent Technologies Proprietary

No.16

Link Budget: RL Parameters


Reverse Link Parameters
Max AT amplifier power (dBm)
AT cable loss
AT antenna gain (dBi)
Body loss (dB)
Maximum AT EiRP(dBm)

Default
Value
23.979
0
2
0
25.979

Cell site antenna gain (dBi)


Cell site cable and associated loss - rev link (J4 port to a
Reverse link design margin (dB)
Reverse link log normal fade margin (dB)
Diversity gain (dB)
Reverse soft handoff gain (dB)
Building/Vehicle penetration loss (dB)
Misc reverse link gain (dB)
Reverse link other sector to same sector interfer ratio
Reverse link operating point (% of pole capacity)
Cell site receiver interference margin (dB)
Maximum allowable RL Pathloss

10.65
3
0
10.3
0
4
0
0
0.85
72
5.53
View

Notes
Read from System Parameter
Read from System Parameter
Read from System Parameter
Read from System Parameter
Calculated
Read from Antenna Pattern, only at
sector level
may be different from FL
Leave it as 0 and Ignore it. To be
removed in v1.8
Depending on coverage criteria
Read from System Parameter
Read from FL Parameter
only at sector level
Calculated
Calculated for various data rates

Lucent Technologies Proprietary

No.17

Link Budget: several calculated values


Forward log normal fade margin:

M f fade M r fade G ho M f anchor


Mr-fade:
Gho:
Mf-anchor:

reverse link log normal fade margin (dB), from the reverse link budget
reverse link soft handoff gain (dB), from system parameter
forward link anchor transfer margin (dB), from system parameter

Cell site receiver interference margin for sector k

1
1 k

Rim k 10 log10
k:

Reverse link traffic loading for sector k. For uniform loading case, k =
reverse link operating point ( rev,in%)/100.
Lucent Technologies Proprietary

No.18

Maximum allowable RL Pathloss for rate j

LMAP j EiRPAT max S rec req j Gcs ant Gdiv Gho Gr misc Lcs r BPL Lbody M r fade
EiRPAT-max:

Maximum AT EiRP (dBm)

Srec-req-j:

cell site receiver sensitivity (in dBm) for given reverse link traffic type j

Gcs-ant:

maximum cell site antenna gain (dBi) from file

Gdiv:

diversity gain (dB)

Gho:

soft handoff gain (dB), applied to the bins in which soft hand-off would occur.

Gr-misc:

reverse link miscellaneous gain (dB) from the reverse link budget

Lcs-r:

reverse link cable & associated losses at the cell site (dB)

BPL:
Lbody:

building (or Vehicle) penetration loss (dB), from the forward link budget
body loss (dB), from the system parameters (typically 0 for HDR)

Mr-fade:

Lucent(dB)
Technologies
Proprietary
reverse link fade margin
from the reverse
link budget

No.19

Link Budget: Other Parameters


Default
Value

Other Parameters
--Scenario Level

Notes
Default values for any new sectors

--Sector Level
T_ADD (dB)

-5 SHO parameter, refer to Application Transition note for the latest

T_DROP (dB)

-8 recommendation

SHO overhead factor

1.75

PN code offset

Color

Red

Only at sector level, set as sector identifer for display purpose

Symbol

Only at sector level, set as sector identifer for display purpose

SRCH_WIN_A

5 For PN delay analysis

Active Set Search Window Size (chips)

20 search window size in PN chips as per SRCH_WIN_A setting

SRCH_WIN_N

7 For PN delay analysis

Neighbor Set Search Window Size (chips)

40 search window size in PN chips as per SRCH_WIN_A setting

SRCH_WIN_R

12 For PN delay analysis

Remaining Set Search Window Size (chips)

160 search window size in PN chips as per SRCH_WIN_A setting

Lucent Technologies Proprietary

No.20

Questions?

The presenter will now ask for questions.


Webcast participants:
Please email your questions via the email link on the webcast page. A
moderator will relay your question to the presenter.

Conference room participants:


The presenter will poll for questions from conference room
participants.

Lucent Technologies Proprietary

No.21

Section 2:
Analyses for 1xEV-DO

Classification of Analyses

Per Link
Forward Link
Reverse Link
Both Links (Balanced Forward/Reverse Link)
Per Loading
Uniformly Loaded: with Operating Point assumption
Heterogeneously Loaded: with Traffic Density File as input
Per Output
Bin (Coverage related analyses)
Sector (Capacity related analyses)

Lucent Technologies Proprietary

No.22

AirPro Analyses for 1xEV-DO: FL

Forward Link Analyses:

Strongest signal strength


Strongest nominal pilot Ec/Io
2nd Strongest nominal pilot Ec/Io
Nth Strongest nominal pilot Ec/Io
Pilot Overlap
Neighbor List prediction (V1.8)
PN offset overlap analysis (V1.8)
Differential PN delay analysis (V1.8)
Forward link traffic Eb/No
Maximum achievable forward link traffic data rate
FL Average Achievable Sector Throughput Analysis (v1.8)
Forward link coverage analysis
FL Coverage Analysis with Multiple BPL
Lucent Technologies Proprietary

No.23

AirPro Analyses for 1xEV-DO: RL & Balanced

Reverse Link Analyses:

Reverse link soft hand-off analysis (based on FL Ec/Io)


Reverse link required AT power
Reverse link traffic Eb/Nt
RL inter-cell interference ratio () analysis (v1.9)
Maximum achievable reverse link data rate
RL Average Achievable Sector Throughput Analysis (v1.8)
Reverse link coverage analysis
RL Coverage Analysis with Multiple BPL

Both Links (Balanced Forward/Reverse Link)

Balanced Forward/Reverse link coverage analysis


Balanced F/R Coverage analysis with Multiple BPL

Lucent Technologies Proprietary

No.24

FL Received Signal Strength


Received Signal Strength (dBm)

S EiRPcell L p _ tot L AT Lbody G AT ant BPL M f fade G f misc


EiRPcell:

EiRP for the cell (dBm)

Lp_tot:
LAT:

predicted pathloss (dB) between cell site antenna and prediction


bin (BPL not included).
AT cable loss (dB)

Lmob:

body loss (dB)

GAT-ant:

AT antenna gain (dBi)

BPL:
Mf-fade:

building (or Vehicle) penetration loss (dB)


forward link fade margin (dB)

Gf-misc:

forward link miscellaneous gain (dB)


Lucent Technologies Proprietary

No.25

FL Pilot Ec/Io
Pilot Ec/Io:

Ec

10 log10

Io i

Si

(
S
)

th
_
fwd
f

ns
other
k

k 1

(Ec/Io)i:

Ec/Io value for sector i, in dB

i:
k:
Si:

index of the sector whose Ec/Io value is being calculated


sector number, k=1.. n, and i is one of the member of k
predicted received signal strength at the bin from element i (in mW)

Nth_fwd:

thermal noise power at mobile (in mW)

If-ns:

forward link non-HDR interference on HDR band (in mW)

Iother:

total interference from all other sectors that do not use the technology
(1xEV-DO and the specific carrier) that is being analyzed
signal strength (S) at the bin from sector k (in mW)

Sk:

Lucent Technologies Proprietary

No.26

Analyses based on Ec/Io

Traffic loading have little impact on FL pilot Ec/Io value (Pilots bursts are
always on even though there is no user data traffic.)
The results of the following analyses are based on FL pilot Ec/Io

Forward Link Analyses:


Strongest nominal pilot Ec/Io
2nd Strongest nominal pilot Ec/Io
Nth Strongest nominal pilot Ec/Io
Pilot Overlap
Neighbor List prediction (V1.8)
PN offset overlap analysis (V1.8)
Differential PN delay analysis (V1.8)
Reverse Link Analyses:
Reverse Link Soft Handoff Analysis

Lucent Technologies Proprietary

No.27

FL Traffic Eb/Nt
FL Traffic Eb/Nt for Rate j:
Eb

Nt

0.75 * W
Si
Rj

10 log 10

N th _ fwd I f ns I other ( FL k S k )

k 1
k i

(Eb/Nt)j:

Eb/Nt value at a specific traffic type rate R j, in dB

i:
k:
Si or Sk

index for the sector with the strongest signal for the bin
index for possible interferers, k=1...n, and ki
predicted received signal strength at the bin from sector i or k (in mW)

W:
Rj:

bandwidth (Hz)
forward link traffic data rate, in bps

Nth_fwd:

thermal noise power at mobile (in mW)

If-ns:

forward link non-HDR interference on HDR band (in mW)

Iother:

total interference from all other sectors that do not use the technology (1xEV-DO and
the specific carrier) that is being analyzed
Forward link traffic loading factor of antenna k. FL-k =1 for uniform loading option
Lucent Technologies Proprietary

FL-k:

No.28

RL AT Required Power and Traffic Eb/Nt


RL Min. Required AT Power for Data Rate j:
EiRPAT req j S rec req j L p _ tot G cs ant Lcs r BPL Lbody G div G ho M r fade G r misc

Lp_tot:

predicted pathloss (dB) from the most likely serving sector to the prediction bin

Gcs-ant:

maximum cell site antenna gain (dBi) from file

Lcs-r:

reverse link cable & associated losses at the cell site (dB)

BPL:
Lbody:

building (or Vehicle) penetration loss (dB), from the forward link budget
body loss (dB), from the system parameters (typically 0 for HDR)

Gdiv:

diversity gain (dB)

Gho:

soft handoff gain (dB), applied to the bins in which soft hand-off would occur.

Mr-fade:

reverse link fade margin (dB) from the reverse link budget

Gr-misc:

reverse link miscellaneous gain (dB) from the reverse link budget

Srec-req-j:

cell site receiver sensitivity (in dBm) for target reverse link traffic type j
Lucent Technologies Proprietary

No.29

RL Traffic Eb/Nt
RL Traffic Eb/Nt:
With reverse link power control, Eb/Nt is kept at the target required Eb/Nt level
until the mobile power reaches its up-limit.
If EiRPAT-req-j <= EiRPAT-max , the bin is considered covered on RL for the
target data rate j and

Eb Eb


Nt Nt

r req j

Else EiRPAT-req-j > EiRPAT-max

Eb Eb


Nt Nt

EiRPAT req j EiRPAT max


r req j

Lucent Technologies Proprietary

No.30

FL Maximum Achievable Data Rate Analysis

Based on both
FL Ec/Io &
FL Eb/Nt

RL Eb/Nt not considered


For each bin, solve for the
highest data rate that meets
both conditions:

Ec/Io >= (Ec/Io)req-j

Eb/Nt >= (Eb/Nt)fl-req-j

Lucent Technologies Proprietary

No.31

RL Maximum Achievable Data Rate Analysis

Based on RL required AT
power
For each bin, solve for the
highest date rate that meets
following condition:

EiRPAT-req-j <= EiRPAT-max

FL Eb/Nt is not considered


FL Ec/Io not directly
considered, but it indirectly
affects results by affecting
SHO status of the bin
predicted. (Rate-Jump is
caused by sudden jump of
SHO gain from 0 to a nonzero value, e.g. 4 dB)
Lucent Technologies Proprietary

No.32

FL Coverage Analysis-Single BPL

Based on both
FL Pilot Ec/Io &
FL Traffic Eb/Nt

RL Eb/Nt not
considered
For each bin, report the
coverage status for a
specific FL data rate:

Both Pilot & Traffic


Covered
Only Pilot Covered
Only Traffic Covered
Not covered
Lucent Technologies Proprietary

No.33

RL Coverage Analysis-Single BPL

Based on RL required AT
power
FL Eb/Nt is not considered
FL Ec/Io not directly
considered, but it indirectly
affects results by affecting
SHO status of the bin
predicted.
For each bin, report the
coverage status for a
specific RL data rate:

Covered
EiRPAT-req-j <= EiRPAT-max

Not covered

Lucent Technologies Proprietary

No.34

Balanced F/R Coverage Analysis-Single BPL-1

Based on
FL Coverage Criteria
RL Coverage Criteria

For each bin, report the


coverage status for a
combination of FL & RL
data rates:

F/R Balanced Covered


FL-Covered only
RL-Covered only
FL Pilot-Covered only
F/R Traffic-Covered only
FL Traffic-Covered only
Not Covered
Lucent Technologies Proprietary

No.35

Balanced F/R Coverage Analysis-Single BPL-2

Or, for the bins predicted


to be F/R Balanced
Covered, report one of
the following analysis
results:

FL Pilot Ec/Io
FL Traffic Eb/Nt
RL Traffic Eb/Nt
RL AT required Power
Example shown

Lucent Technologies Proprietary

No.36

Coverage Analyses with multiple BPLs

The user can define a set


of different BPL categories
by specify

Category Names
BPL values

AirPro will take the input


and replace the sector
level BPL value, then
predict and mark the bins
in which the coverage
criteria can be met with the
user-defined BPL
category.
Lucent Technologies Proprietary

No.37

Heterogeneously Loaded System

Define Heterogeneity:
Users generate traffic density files, and AirPro use the data and coverage
prediction to estimate loading factor for different sector.

Impact on analyses with heterogeneously Loaded System:

FL Ec/Io not affected


FL Eb/Nt affected:
Longer idle time for lightly loaded sector, creating less interference to
the neighbor sectors
RL Eb/Nt affected
Less active users for lightly loaded sector, created less interference to
the neighbor sectors and the user in the same sector

Lucent Technologies Proprietary

No.38

How Does AirPro Estimate Loading for Each Sector


1.

AirPro estimates coverage footprint based on uniform traffic loading


assumption and following user input:

2.

3.

4.

5.

FL & RL Data rates at cell edge

Based on the coverage footprints for each sector, sum up the traffic within
coverage footprint and estimate FL and RL loading factor by comparing with
capacity limit.
Based on new loading factors, calculate FL Eb/Nt and RL Eb/Nt and reestimate coverage footprint
Repeat step 2 with new coverage footprint and calculate new FL and RL
loading factor
Perform analyses for the data rate to be analyzed with the new FL and/or RL
loading factor and the same equation discussed previously

Lucent Technologies Proprietary

No.39

Analyses affected by cell loading

Forward Link Analyses:

Reverse Link Analyses:

Forward link traffic Eb/No


Maximum achievable forward link traffic data rate
RL Average Achievable Sector Throughput Analysis (Not yet supported)
Forward link coverage analysis
FL Coverage Analysis with Multiple BPL
Reverse link required AT power
Reverse link traffic Eb/Nt
RL inter-cell interference ratio () analysis (v1.9)
Maximum achievable reverse link data rate
RL Average Achievable Sector Throughput Analysis (Not yet supported)
Reverse link coverage analysis
RL Coverage Analysis with Multiple BPL

Both Links (Balanced Forward/Reverse Link)

Balanced Forward/Reverse link coverage analysis


Balanced F/R Coverage analysis with Multiple BPL
Lucent Technologies Proprietary

No.40

Questions?

The presenter will now ask for questions.


Webcast participants:
Please email your questions via the email link on the webcast page. A
moderator will relay your question to the presenter.

Conference room participants:


The presenter will poll for questions from conference room
participants.

Lucent Technologies Proprietary

No.41

Section 3:
1xEV-DO Traffic Capacity Analysis

Steps needed to complete traffic capacity


analysis

Input of Traffic Data


External Files (Currently 3 types supported)
Traffic User-defined Region (UDR)
Traffic Density Generation
Traffic Capacity Analysis
How to Define Traffic Capacity Limit
- Via Network Mobile List
- Via Look-up Table
- Achievable sector throughput calculated by AirPro
Traffic Demand vs Capacity Limit

Lucent Technologies Proprietary

No.42

Import External Traffic files

3 external sources for traffic data:

Mapinfo .mif/mid files:

Geographic-Area-Based Traffic Data

Highway Traffic

Point-based traffic data (.fwl files)

Sector-Based Traffic Data (.set files)

Traffic amount for a given location specified by a lat/lon coordinate

Traffic data from an existing network (extracted switch data)

Use the import file utility to import traffic from these sources into AirPro

.mif & .fwl files -->> A selected Geo-Area Directory

.set files -->> A selected Market


Lucent Technologies Proprietary

No.43

Set File Utility


A utility has been created which generates a .set file based on data from the
ascii .txt file.

Supports IS-95 and TDMA scenarios for AirPro


Supports CDMA and FM scenarios for CE4
Choice among Number of Users, Number of Channels or Erlang Values in the
.set file
Option of Editing up to 10 (Erlangs/Number of Users/Number of Channels)
values individually - or Calculating the values automatically from the scenario
It is available from the AirPro and RFEC web pages.

Lucent Technologies Proprietary

No.44

.Set File Utility

Lucent Technologies Proprietary

No.45

Assign Traffic from Traffic UDR

Go to Layer Control and Select

Color or Gray Layer


User-Defined Region
- 3G Traffic (1.7), or
- Traffic (v1.8)
Then use the drawing tools

Draw polygons or polylines

Specify Attributes for the


object
Number of Subscriber
Mean SADS/Sub
Mean FL throughput
(kbps/sub)
Mean RL throughput
(kbps/sub)

Lucent Technologies Proprietary

No.46

Traffic UDR attributes

Number of Subscriber
Typical Input from customer

Mean SADS/Sub
Derived from the traffic model provided by the customer
Consult SE to get average values per customer traffic model or Lucent default
traffic model

Mean FL throughput (kbps/sub)


Typical Demand Input from customer

Mean RL throughput (kbps/sub)

Typical Demand Input from customer

Lucent Technologies Proprietary

No.47

Traffic Density Generation Dialog

Technology: 1xEV-DO
Desired Final Units: # of subscriber
Traffic Source Files
Data Sets
Units used in the source file
Conv. Factor to final units if needed
Define coverage related parameters
set, if a set file is selected
Traffic density distribution option
Allows for overlapping UDRs
Outputs
Display Options:

# of subscriber per area


# of SADS per area
FL throughput per area
RL throughput per area

Lucent Technologies Proprietary

No.48

Clutter weighting on traffic


Traffic Density Distribution:
Uniform distribution:
All bins will be treated equally
and assigned same amount of
traffic
Clutter Weighting:
Traffic allocated to the bins
according to Traf weighting
factor, the bins whose clutter
type has higher weighting
factor will be allocated higher
portion of traffic

Lucent Technologies Proprietary

No.49

Traffic Capacity Analysis for 1XEV-DO

Select menu Analysis | Traffic Capacity Analysis


From Network System Setting tab,
Select Primary System: 1xEV-DO
Optionally, Select Secondary System 1xEV-DO at a different carrier
Select Fwd Link Data Rate: Target FL data rate at cell edge
Select Rev Link Data Rate: Target RL data rate at cell edge
Choose Capacity Limit Source: 3 options
Choose Mobile List file
Specify Traffic distribution (among two selected systems)
Specify Traffic Growth
Select Traffic Density File

From Analysis Output

Define output options: Graphical, Tabular on Screen, or Files


Icon colors show:
Offered load
Overload

Lucent Technologies Proprietary

No.50

Traffic Capacity Analysis Dialog

Lucent Technologies Proprietary

No.51

Capacity Limit Source: 3 options

Nature of Traffic Capacity Analysis:


Comparing Offered Traffic (Demand) & Network Capacity (Supply)
Offered Traffic: Calculated based on the traffic density within coverage
foot print
Network Capacity
- From Capacity Limit Source

3 Capacity Limit Sources for 1xEV-DO

From Mobile List


Select from a predefined mobile list
From Look-up Table
Select one from the look-up files (*.evdo) in Look-up subdirectory
Achievable Sector throughput calculated by AirPro
Simple Bin count
Or traffic-weighted bin count

Lucent Technologies Proprietary

No.52

Capacity Limit Source 1: Mobile List

Select Utilities | Network Mobile


List menu under Market List
Window
Specify following attributes:

Mobile List name


Mobile Type:
Any meaningful name
Technology Supported:
1xEV-DO
FL Traffic Capacity in
kbps/sector*carrier
RL Traffic Capacity in
kbps/sector*carrier
RL Operating point related to
the quoted RL capacity

Lucent Technologies Proprietary

No.53

Capacity Limit Source 2: Look-up Table

1200

Off-line simulation indicates:

Above data can be imported into AirPro as


look-up tables (*.evdo file):

AirPro would calculated SADS first


Then find the corresponding sector
throughput limit as per SADS (active
users
This would provide more accurate
sector throughput limits than a single
limit defined in mobile list

Throughputinkbps

FL Sector Throughput
Increases as the number of active
users increases due to scheduler
gain
RL Sector Throughput
Decreases as the number of active
users increases due to extra nontraffic overhead channels needed
Sector Throughput
Varies in different morphologies

Forward Link
Urban
Suburban
Rural

1000

800

600

400

200

Reverse Link
0
0

10

15

20

25

NumberofActiveUsers

Lucent Technologies Proprietary

No.54

Capacity Limit Source 3: AirPro calculation

Sector throughput would increase if more users are in good RF conditions and
can achieve higher data rate
By assuming the sector would transfer the data traffic at its maximum
achievable data rate, AirPro calculates:

FL achievable sector throughput in kbps


Based on maximum achievable FL data rate rates within the areas
predicted to be balanced F/R covered.
RL achievable sector throughput in kbps
Based on maximum achievable RL data rate rates within the areas
predicted to be balanced F/R covered.
Note: Current AirPros calculation is for evaluating the impact of RF
condition and relative subscriber location on sector throughput. The
results should not be directly quoted to the customer as the actual
supportable capacity.

Lucent Technologies Proprietary

No.55

AirPro estimation of sector throughput

TPi

(B
j

* Net _ TPj * N sub _ j )

N sub _ j

TPi

j
Net_TPj

Bj
Nsub_j

Average maximum achievable throughput (kbps) for sector i


Index of the maximum achievable data rates within coverage footprint of sector i
Net throughput for the maximum achievable data rate within coverage footprint
of sector I
FL:
Net_TPj = Cj*Rj
(Assume C j=1 for now)
RL:

Find Net_TPj from Rj from the following table

Rj

9.6

19.2

38.4

76.8

153.6

Net_TPj 7.8

17.4

36.6

75.0

151.8

Number of bins (within the coverage footprint of section i) whose predicted


maximum achievable data rate is R j
Total number of subscribers from the bin whose predicted maximum achievable
data rate is Rj (Assume Nsub_j=1 when by bin-count option)
Lucent Technologies Proprietary

No.56

Graphical Traffic Capacity Results

Traffic density:
Displayed on background
May be turned off from layer
control

Sector Traffic:

Via Icon Color


Offered load, or
Overload
Maybe turned off by selecting
View | Clear Antenna Capacity
Color

Lucent Technologies Proprietary

No.57

Tabular Traffic Capacity Results

List the offered load,


capacity limit,
overload amount for
the followings:

SADS
FL TP in kbps
RL TP in kbps

Color-Highlighted if
the sector overloaded

Lucent Technologies Proprietary

No.58

Traffic Capacity Results: Send To File

Lucent Technologies Proprietary

No.59

Traffic Data Derived from MapInfo Tracts


.mid/mif files from Mapinfo contain area and line (vector) traffic data, this represents
traffic to be served in the specified geographic area.

Lucent Technologies Proprietary

No.60

Traffic Data from Point Sources or hotspots


.flw file is for point sources: Train Stations, Markets, Airports, Malls, etc. The file
represents traffic to be served at specific lat/long points.

Lucent Technologies Proprietary

No.61

Traffic Data from Existing Sectors


.set file contains definition of cell sites and erlangs/sector.

Lucent Technologies Proprietary

No.62

Traffic Data Derived from User-Defined Regions

Lucent Technologies Proprietary

No.63

Questions?

The presenter will now ask for questions.


Webcast participants:
Please email your questions via the email link on the webcast page. A
moderator will relay your question to the presenter.

Conference room participants:


The presenter will poll for questions from conference room
participants.

Lucent Technologies Proprietary

No.64

Section 4:
Live Demo of AirPro for 1xEV-DO

Current release version:

AirPro V1.7.82
Some Demo will be given with beta version of AirPro 1.8 release
(Due 3/31/03)

Lucent Technologies Proprietary

No.65

Internal Points of Contact

Who to call for AirPro support/questions


Contact:

RF Tools Test & Support Group (TM: Hillar Puskar)

Phone:

1 (973) 386-8737

e-mail:
airprohelp@lucent.com
Websites: http://airpro.wh.lucent.com

Lucent Technologies Proprietary

No.66

Questions?

The presenter will now ask for questions.


Webcast participants:
Please email your questions via the email link on the webcast page. A
moderator will relay your question to the presenter.

Conference room participants:


The presenter will poll for questions from conference room
participants.

Lucent Technologies Proprietary

No.67

You might also like