67
No.1 Lucent Technologies Proprietary Using AirPro for 1xEV-DO RF Design Victor Weng RF Tools & Services Systems Engineering (Victor Dasilva) [email protected] 1 (973) 386-4756 February 11 th , 2003

1xEV DO.airpro

Embed Size (px)

DESCRIPTION

EVDO

Citation preview

AirPro for 1xEV-DO RF DesignVictor Weng
[email protected]
High level and vague.
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
Understand the basic concept and equation used in AirPro coverage analysis
Understand the impact of traffic loading on the coverage analysis
Understand the steps needs to define traffic loading for a 1xEV-DO system
Understand the input and output of AirPro traffic capacity analysis
Lucent Technologies Proprietary
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
1xEV-DO Forward Link:
(1) Time Shared
Time
Code
Code Shared
RL SHO
FL data dates:
921.6, 1228.8, 1843.2, 2457.6
Lucent Technologies Proprietary
Fast Rate Adaptation
IDLE
Time
76k 153k 307k 614k 76k 614k 153k 1.2M
C/I
C/I
C/I
DRC
DRC
DRC
(Virtual SHO)
DRC
DRC
C/I
C/I
Get input from the customer to understand target network performance
Coverage objective
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
Perform coverage analysis (Section 2)
Perform traffic capacity analysis (Section 3)
Lucent Technologies Proprietary
Cell Site Information (Not to be covered in this session)
General: Site Location, Sector Orientation, Antenna Types, Survey Data, etc.
Site Flags
Propagation Model
System Parameters
Sector Level
FL Parameters
RL Parameters
Link Budget: FL Traffic Parameters
Forward link Processing Gain Calculation:
“3/4”: ¾ of time slots are allocated for data traffic channel
Traffic Parameters per Coverage Type (Channel Type):
Default Type: AWGN (Stationary)
--Sector Level
T_ADD (dB)
SHO parameter, refer to Application Transition note for the latest
T_DROP (dB)
0
Color
Red
Only at sector level, set as sector identifer for display purpose
Symbol
A
Only at sector level, set as sector identifer for display purpose
SRCH_WIN_A
5
20
search window size in PN chips as per SRCH_WIN_A setting
SRCH_WIN_N
7
40
search window size in PN chips as per SRCH_WIN_A setting
SRCH_WIN_R
12
160
search window size in PN chips as per SRCH_WIN_A setting
Sheet2
1
1
1
1
1
1
1
1
1
38.4
76.8
153.6
307.2
614.4
921.6
1,228.80
1,843.20
2,457.60
2.5
2.5
2.5
2.5
2.5
3.5
5
7.5
10.5
-11.62
-8.9
-6.42
-4.3
-2.66
-1.6
-0.92
-0.37
-0.14
Sheet1
--Sector Level
T_ADD (dB)
SHO parameter, refer to Application Transition note for the latest
T_DROP (dB)
0
Color
Red
Only at sector level, set as sector identifer for display purpose
Symbol
A
Only at sector level, set as sector identifer for display purpose
SRCH_WIN_A
5
20
search window size in PN chips as per SRCH_WIN_A setting
SRCH_WIN_N
7
40
search window size in PN chips as per SRCH_WIN_A setting
SRCH_WIN_R
12
160
search window size in PN chips as per SRCH_WIN_A setting
Sheet2
1
1
1
1
1
9.6
19.2
38.4
76.8
153.6
6
4.5
3.6
3.2
6
-23
-23
-23
-23
-22
3.75
6.75
9.75
13.25
18.5
27.439
17.749
10.674
5.721
2.182
Calculated
-117.366
-115.947
-114.012
-111.808
-107.827
Calculated
Sheet3
Pole Capacity for Data Rate j
b: reverse link other sector to same sector interference ratio
(Ec/Nt)r-req-j 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_Gain: Traffic channel gain in dB over pilot channel
j: Reverse link traffic channel activity factor for traffic type j.
Lucent Technologies Proprietary
Link Budget: RL Traffic Parameters-3
Cell Site Receiver Sensitivity (dBm)
(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
0
Leave as 0 and Ignore them. To be removed in v1.8
Forward Link Design Margin(dB)
-104.08
5
-108.08
-118
-118
2
-1.5
PILOT_INC
4
0
Used for traffic density/capacity analysis. Get the input from the customer, consult with SE for traffic modelling questions.
Avg. FL throughput demand (kbps/subscriber)
0
0
Sheet2
Sheet3
0
Leave as 0 and Ignore them. To be removed in v1.8
Forward Link Design Margin(dB)
-104.08
5
-108.08
-118
-118
2
-1.5
PILOT_INC
4
0
Used for traffic density/capacity analysis. Get the input from the customer, consult with SE for traffic modelling questions.
Avg. FL throughput demand (kbps/subscriber)
0
0
--Sector Level
8
0
Cell site cable and associated loss-fwd link (J4 port to ant
3
10.65
EiRP (total)(Watts)
AT cable loss
8.3
0
Leave it as 0 and Ignore it. To be removed in v1.8
Misc forward link gain (dB)
0
0
0
Leave as 0 and Ignore them. To be removed in v1.8
Forward Link Design Margin(dB)
-104.08
5
-108.08
-118
-118
2
-1.5
PILOT_INC
4
0
Used for traffic density/capacity analysis. Get the input from the customer, consult with SE for traffic modelling questions.
Avg. FL throughput demand (kbps/subscriber)
0
0
--Sector Level
23.979
10.65
Read from Antenna Pattern, only at sector level
Cell site cable and associated loss - rev link (J4 port to a
3
0
Leave it as 0 and Ignore it. To be removed in v1.8
Reverse link log normal fade margin (dB)
10.3
4
0
0.85
72
5.53
Calculated
Sheet2
Sheet3
Cell site receiver interference margin for sector k
Forward log normal fade margin:
mk: Reverse link traffic loading for sector k. For uniform loading case, mk = reverse link operating point (rev, in %)/100.
Mr-fade: reverse link log normal fade margin (dB), from the reverse link budget
Gho: reverse link soft handoff gain (dB), from system parameter
Mf-anchor: forward link anchor transfer margin (dB), from system parameter
Lucent Technologies Proprietary
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: building (or Vehicle) penetration loss (dB), from the forward link budget
Lbody: body loss (dB), from the system parameters (typically 0 for HDR)
Mr-fade: reverse link fade margin (dB) from the reverse link budget
Lucent Technologies Proprietary
--Sector Level
T_ADD (dB)
SHO parameter, refer to Application Transition note for the latest
T_DROP (dB)
0
Color
Red
Only at sector level, set as sector identifer for display purpose
Symbol
A
Only at sector level, set as sector identifer for display purpose
SRCH_WIN_A
5
20
search window size in PN chips as per SRCH_WIN_A setting
SRCH_WIN_N
7
40
search window size in PN chips as per SRCH_WIN_A setting
SRCH_WIN_R
12
160
search window size in PN chips as per SRCH_WIN_A setting
Sheet2
Sheet3
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
Per Loading
Heterogeneously Loaded: with “Traffic Density File” as input
Per Output
Forward Link Analyses:
Strongest signal strength
Pilot Overlap
Forward link traffic Eb/No
Forward link coverage analysis
Lucent Technologies Proprietary
Reverse Link Analyses:
Reverse link required AT power
Reverse link traffic Eb/Nt
Maximum achievable reverse link data rate
RL Average Achievable Sector Throughput Analysis (v1.8)
Reverse link coverage analysis
Both Links (Balanced Forward/Reverse Link)
Balanced Forward/Reverse link coverage analysis
Balanced F/R Coverage analysis with Multiple BPL
Lucent Technologies Proprietary
EiRPcell: EiRP for the cell (dBm)
Lp_tot: predicted pathloss (dB) between cell site antenna and prediction bin (BPL not included).
LAT: AT cable loss (dB)
Lmob: body loss (dB)
BPL: building (or Vehicle) penetration loss (dB)
Mf-fade: forward link fade margin (dB)
Gf-misc: forward link miscellaneous gain (dB)
Lucent Technologies Proprietary
FL Pilot Ec/Io
(Ec/Io)i: Ec/Io value for sector i, in dB
i: index of the sector whose Ec/Io value is being calculated
k: sector number, k=1.. n, and i is one of the member of k
Si: 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
Sk: signal strength (S) at the bin from sector k (in mW)
Lucent Technologies Proprietary
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:
Pilot Overlap
Reverse Link Analyses:
Lucent Technologies Proprietary
FL Traffic Eb/Nt
FL Traffic Eb/Nt for Rate j:
(Eb/Nt)j: Eb/Nt value at a specific traffic type rate Rj, in dB
i: index for the sector with the strongest signal for the bin
k: index for possible interferers, k=1...n, and ki
Si or Sk predicted received signal strength at the bin from sector i or k (in mW)
W: bandwidth (Hz)
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
rFL-k: Forward link traffic loading factor of antenna k. rFL-k =1 for uniform loading option
Lucent Technologies Proprietary
RL Min. Required AT Power for Data Rate j:
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: building (or Vehicle) penetration loss (dB), from the forward link budget
Lbody: 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
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
Else EiRPAT-req-j > EiRPAT-max
Lucent Technologies Proprietary
Based on both
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
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 non-zero value, e.g. 4 dB)
Lucent Technologies Proprietary
RL Eb/Nt not considered
For each bin, report the coverage status for a specific FL data rate:
Both Pilot & Traffic Covered
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
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
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
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
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
AirPro estimates coverage footprint based on uniform traffic loading assumption and following user input:
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 re-estimate 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
Forward Link Analyses:
RL Average Achievable Sector Throughput Analysis (Not yet supported)
Forward link coverage analysis
Reverse Link Analyses:
Reverse link traffic Eb/Nt
Maximum achievable reverse link data rate
RL Average Achievable Sector Throughput Analysis (Not yet supported)
Reverse link coverage analysis
Both Links (Balanced Forward/Reverse Link)
Balanced Forward/Reverse link coverage analysis
Balanced F/R Coverage analysis with Multiple BPL
Lucent Technologies Proprietary
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
Input of Traffic Data
Traffic User-defined Region (UDR)
Via Network Mobile List
Traffic Demand vs Capacity Limit
Lucent Technologies Proprietary
Mapinfo .mif/mid files:
Geographic-Area-Based Traffic Data
Point-based traffic data (.fwl files)
Traffic amount for a given location specified by a lat/lon coordinate
Sector-Based Traffic Data (.set files)
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
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
.Set File Utility
Lucent Technologies Proprietary
Go to Layer Control and Select
Color or Gray Layer
Draw polygons or polylines
Number of Subscriber
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)
Mean RL throughput (kbps/sub)
Lucent Technologies Proprietary
Traffic Source Files
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
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
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 Growth
Icon colors show:
Comparing Offered Traffic (Demand) & Network Capacity (Supply)
Offered Traffic: Calculated based on the traffic density within coverage foot print
Network Capacity
From 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”
Select “Utilities | Network Mobile List…” menu under “Market List” Window
Specify following attributes:
Mobile List name
RL Operating point related to the quoted RL capacity
Lucent Technologies Proprietary
Off-line simulation indicates:
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 non-traffic overhead channels needed
Sector Throughput
Varies in different morphologies
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
Forward Link
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 AirPro’s 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
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 Cj=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 Rj
Total number of subscribers from the bin whose predicted maximum achievable data rate is Rj (Assume Nsub_j=1 when by “bin-count” option)
j
Net_TPj
Bj
Nsub_j
Sector Traffic:
Maybe turned off by selecting “View | Clear Antenna Capacity Color”
Graphical Traffic Capacity Results
Lucent Technologies Proprietary
List the offered load, capacity limit, overload amount for the followings:
SADS
Tabular Traffic Capacity Results
Lucent Technologies Proprietary
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
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
.set file contains definition of cell sites and erlangs/sector.
Lucent Technologies Proprietary
Lucent Technologies Proprietary
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
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
Contact: RF Tools Test & Support Group (TM: Hillar Puskar)
Phone: 1 (973) 386-8737
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.
Other Parameters
--Sector Level
T_ADD (dB)-5SHO parameter, refer to Application Transition note for the latest
T_DROP (dB)-8recommendation
SHO overhead factor1.75
PN code offset0
ColorRedOnly at sector level, set as sector identifer for display purpose
SymbolAOnly at sector level, set as sector identifer for display purpose
SRCH_WIN_A5For PN delay analysis
Active Set Search Window Size (chips)20search window size in PN chips as per SRCH_WIN_A setting
SRCH_WIN_N7For PN delay analysis
Neighbor Set Search Window Size (chips)40search window size in PN chips as per SRCH_WIN_A setting
SRCH_WIN_R12For PN delay analysis
Remaining Set Search Window Size (chips)160search window size in PN chips as per SRCH_WIN_A setting
Forward Link Parameters
--Sector Level
Amplifier attenuation (dB)0
Cell site cable and associated loss-fwd link (J4 port to ant3
Cell Site antenna gain (dBi)10.65
Read from Antenna Pattern, only at
sector level
AT antenna gain (dBi)2Read from System Parameter
Body loss (dB)0
Forward log normal fade margin (dB)8.3Calculated from RL fade margin
Forward traffic interfer reduction factor0
Leave it as 0 and Ignore it. To be
removed in v1.8
Forward Link Design Margin (dB)0Read from System Parameter
Building/Vehicle penetration loss (dB)0
anchor
f
ho
fade
r
fade
f
M
G
M
M
76k 153k 307k 614k 76k 614k 153k 1.2M
1.2M 614k 1.8M 1.2M 1.2M 1.2M 307k 1.2M
DRC
DRC
DRC
C/I
C/I
153K
76k
153k
Cell Site noise figure (dB)5
Thermal noise power at cell(dBm)-108.08Read-only, Calculated by AirPro
Non-HDR interfer on HDRband (dBM) (forward link)-118External Interference
Non-HDR interfer on HDRband (dBM) (reverse link)-118External Interference
Forward anchor transfer margin (dB)2
Reverse soft handoff gain(dB)4
PILOT_INC4
Avg. FL throughput demand (kbps/subscriber)0
Avg. RL throughput demand (kbps/subscriber)0
Leave as 0 and Ignore them. To be
removed in v1.8
Reverse Link Parameters
AT cable loss0Read from System Parameter
AT antenna gain (dBi)2Read from System Parameter
Body loss (dB)0Read from System Parameter
Maximum AT EiRP(dBm)25.979Calculated
Read from Antenna Pattern, only at
sector level
Cell site cable and associated loss - rev link (J4 port to a3may be different from FL
Reverse link design margin (dB)0
Leave it as 0 and Ignore it. To be
removed in v1.8
Reverse link log normal fade margin (dB)10.3Depending on coverage criteria
Diversity gain (dB)0
Building/Vehicle penetration loss (dB)0Read from FL Parameter
Misc reverse link gain (dB)0
Reverse link other sector to same sector interfer ratio0.85only at sector level
Reverse link operating point (% of pole capacity)72
Cell site receiver interference margin (dB)5.53Calculated
Maximum allowable RL PathlossViewCalculated for various data rates
misc
f
fade
f
ant
AT
body
AT
tot
p
cell
G
M
BPL
G
L
L
L
EiRP
S
Include this rate in analysis11111
Reverse Traffic Channel Data Rate (Kbps)9.619.238.476.8153.6
Eb/Nt Required on Reverse Link (dB)64.53.63.26
For Coverage Analysis
For capacity analysis
For capacity analysis
(
)
=
-
FL Traffic ParametersType 1Type 2Type 3Type 4Type 5Type 6Type 7Type 8Type 9
Include this rate in analysis111111111
Forward Traffic Channel Data Rate (Kbps)38.476.8153.6307.2614.4921.61,228.801,843.202,457.60
Eb/Nt Required on Forward Link (dB)2.52.52.52.52.53.557.510.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.80610.7967.7864.7751.7650.004-1.245-3.006-4.255