Module07 1xEV-DO RF Guidelines

Module 7: 1xEV-DO RF Design Guidelines, Airlink Parameter Settings, and Optimization
Jay Weitzen Airvana Performance Engineering
Infrastructure for All-IP Broadband Mobile Wireless Accelerating Access Anywhere
Module Objectives To help you understand

1xEV-DO RF Design Guidelines and Link Budgets RF/Airlink Parameter Settings
Which Parameters to Set and which not to set
Optimizing 1xEV-DO networks

Which metrics to watch
Understand commonalities with 1xRTT design guidelines

Confidential & Proprietary 2
Recommended Audience RF engineering staff, proficient in IS-95/IS2000 CDMA RF engineering principles Prerequisite Modules:
1xEV-DO Air Interface 1xEV-DO Signaling 1xEV-DO Hybrid Mode Operation
Confidential & Proprietary
Reference Documents Qualcomm 1xEV-DO master system parameters, Document 80-H0562-1, Airvana/Nortel RF design guidelines IS-856 specification Handbook of CDMA System Design Engineering and Optimization, K. Kim, Prentice Hall, 2000
Some General Thoughts Before Starting
Understand Your Users and Usage Patterns

Differences between fixed and mobility systems.
Dimensioning is different based on user profile. Will users make 1xEV-DO their primary internet access source?
Reasonable usage plans tend to control network usage.

All you can eat plans tend to encourage data hogs who consume disproportional levels of resources and can load down a network. Traffic shaping may not help control data hogs. To the degree possible, try to discourage large scale uploading (home web hosting).
Become Familiar Thinking in C/I vs. Ec/Io 1xEV-DO uses C/I because it is TDMA on FL and HO is virtual fast sector switching. 1xRTT uses Ec/Io because every signal has the potential to be used or interference in true SHO system.
Ec C1 = Io NoW + Ci i =1
C C1 = I NoW + Ci i=2
Converting Between C/I and Ec/Io

Ec C Io = I Ec 1 Io
C/I dB vs Ec/Io
15 10 5 0 -18 -16 -14 -12 -10 -8 -6 -4 -2 -5 0 -10 -15 -20 Ec/Io (dB) C/I dB
C Ec I = Io C 1 + I
Understand 1xEV-DO Service Models and Service Requirements Fixed, nomadic and mobile users
Mobile users (phone-like devices) with complete mobility Portable PCMIA laptop devices Fixed wireless access point devices
Minimum service offerings

Broadband replacement: 300-600 kbps downlink 2040 kbps uplink (typical)
40 kbps reverse is minimum found to not impact TCP (ftp) performance on forward link
Mobility services 20 kbps uplink, 100-300 kbps downlink
Types of 1xEV-DO Deployments Overlay With existing IS-95/IS2000 System

Currently highly recommend 1x1 overlay with 1x to avoid adjacent channel interference and near far issues. Design will be constrained by 1xRTT design
Overlay with other Technology such as TDMA or GSM Stand Alone 1xEV-DO service
10
Coexistence of CDMA With Other Systems

1.77 MHz
Power
CDMA SIGNAL
Frequency
260 kHz Guard Band
1.25 MHz CDMA Carrier
260 kHz Guard Band
Guardbands are required between CDMA and non-CDMA signals

CDMA signals appear as a raised noise floor to other technologies receivers Non-CDMA signals appear as noise to CDMA receivers
No guard band is customarily used between frequency-adjacent CDMA signals; there is a slight decrease in capacity due to adjacent-frequency interference but it is negligible in normal operation
Sector Capacity Estimates Initial capacity analysis

Estimated average forward link/ reverse link throughput per sector (QC)
Fixed Stand Alone Device Downlink: 9001200 kbps Uplink: 300+ kbps Nomadic (pcmcia card) Downlink: 700-900 kbps Uplink: 270 Mobile Downlink: 600800kbps Uplink: 250
Expected Throughput with single diversity is about 30% less than dual diversity
Understand the Differences Between Running a Voice Network and Running a Data Network
User experience and annoyance measures are different in voice and data networks.
Dropped call, while critical in voice is far less critical in a data network because of buffering and reconnection. New metrics are required and under development. Example: A data drop which is an application timeout is different than a call drop in a voice network. Erlang equivalent. Even more critical as you begin to add real time applications.
RF performance staff need to learn about TCP/IP!
15
Understand Hybrid Mode Operation Coupling between voice network and data activity See hybrid mode operation module
16
Manage and Adapt Your Backhaul Network

Backhaul is one of largest recurring costs Avoid tendency to put it in and take it for granted
One E1 should suffice early in the deployment, add a second E1 when your statistics indicate that you need it, on a selective cell basis
For mobility type of network 2 e1s should be max needed
Carefully monitor both network and backhaul performance at the aggregation router to determine when to add more backhaul
Need to monitor average usage queue delay, and dropped packets Compare to 2 - E1 system for reference Try to project in advance when second E1 will be required
RF Planning 1xEV-DO Networks
Access Terminal Parameter Assumptions

Parameter Nominal Value Assumptions Terminal Type Nomadic Mobile Peak Transmit Power 200mW (23dBm) 200mW (23dBm) Antenna Omni-directional, -1dBi Omni-directional, -1 dBi Cable Loss 0 dB 0 dB Diversity Dual Single/Dual Fixed 200 mw (23 dBm) External 7/dBi 2 dB Dual
Dual Diversity AT shown to provide approximately 2 + dB improvement over no diversity Try to design for at least 20 kbps on reverse link @ 3 dB loading and at margin for no impact on forward link using TCP. Be aware of PC->AT interference issues with data cards
Base Station Parameter Assumptions

Parameter Max. Average PA output power Antenna Antenna Height Cable Loss Effective AN Noise Figure Nominal Value Assumptions 10-15W Sectored, 17dBi, 65 deg. or 90 deg. >30 meters (dependent on morphology) 0 to 3dB (dependent on implementation) 5dB
21
Base Station Antenna Configurations

Multi-sector or single sector operation. Antenna configurations:
Dual horizontal space with vertical polarization, 10-20 spacing if predominant service models are fixed or nomadic. Dual polarization, +/- 45 degree for mobile applications
Use 65 degree Beamwidth antennas for 3 sector sites to control interference. Target 2-3 db (max) cable loss.
Coaxial cable types and losses 7/8 for AGL <=100ft; 1 5/8 for AGL >=101ft.
General Comments on Link Budgets

1xEV-DO FL/RL link budgets are highly asymmetric.
Reverse link performance tends to be limiting factor on overall link budget Reverse link budget is about 2 db higher than CDMA2000 voice reverse link budget (wherever there is voice coverage there should be capable of 19.2 kbps for 1xEV-DO at margin )
Forward link is more interference sensitive than CDMA-2000 because there is no true soft handoff
23
1xEV-DO Link Budget

Reverse Link Budget - Mobile User Data Rate [kbps] Data Rate[dB-Hz] AT TX PO [Watts] AT TX PO [dBm] AT Antenna Gain [dBi] Body Loss [dB] EIRP [Watts] EIRP [dBm] BTS Antenna Gain [dBi] BTS Rx Cable Loss [dB] BTS Noise Figure BTS Thermal Noise [dBM/Hz] Target PER (%) Eb/No per Antenna [dB] Traffic Loading Factor [dB] BTS Rx Sensitivity [dBm] Confidence (Cell Edge) [%] Log Normal Shadow Std Dev [dB] Log Normal Shadow Margin [dB] Soft Handoff Gain [dB] Penetration Loss [dB] Differential Fade Margin [dB]
1x-EV-DO
38.4 45.8 0.2 23.0 -1.0 3.0 0.1 19.0 18.0 3.0 5 -169.0 2% 3.84 3.00 -116.3 90% 8.0 -10.3 4.1 8.0 2.1 19.2 42.8 0.2 23.0 -1.0 3.0 0.1 19.0 18.0 3.0 5 -169.0 2% 4.98 3.00 -118.2 90% 8.0 -10.3 4.1 8.0 2.1 9.6 39.8 0.2 23.0 -1.0 3.0 0.1 19.0 18.0 3.0 5 -169.0 2% 6.62 3.00 -119.6 90% 8.0 -10.3 4.1 8.0 2.1
Forward Link Budget - Mobile User
1x-EV-DO
Average Throughput (or Data rate) [bps] 87,802 Serving Time Fraction 14.3% Average Burst Rate [bps] 614,000 Bandwidth [kHz] 1228.8 Bandwidth [db-Hz] 60.9 BTS Tx Power [Watts] 15.0 BTS Tx Power [dBm] 41.8 BTS Antenna Gain [dBi] 18.00 BTS Cable Loss [dB] 3.00 BTS EIRP [dBm] 56.8 AT Rx Antenna Gain [dBi] -1.00 Body Loss [dB] 3.0 Noise Figure [dB] 9.0 Thermal Noise [dBm/Hz] -165.0 Target PER (%) 2% (Ior/No) req per Antenna (dB) 6.00 Multi-user Diversity Gain (dB) 0.00 Rx Diversity Gain (dB) 4.70 AT Receiver Sensitivity (dBm) -98.1 Confidence (Cell Edge) [%] 90% Log Normal Shadow Std Dev [dB] 8.0 Log Normal Shadow Margin [dB] -10.3 Soft Handoff Gain [dB] 4.10 Building Penetration Loss [dB] 8.00 MAPL [dB] 136.7
MAPL [dB]
134.1
135.9
137.3
24
Designing to Minimize Interference Is Key in 1xEV-DO System Design
Forward link transmits at full power using TDMA rather than multiple carriers as in IS-95.
Controlling forward link interference is even more important than in IS-95 system due to virtual SHO vs. true SHO. MSM-5500 AT can track up to 6 pilots in active set, but communicate with only 1 at a time.
25
Approximate Forward Rate vs. C/I (AWGN)

Data rate [Kbps] 38.4 76.8 153.6 307.2 C/I [dB] -11.5 -9.5 -6.5 -3.0 -1.0 1.3 3.0 7.2 10.5
C C1 = I NoW + Ci i=2
-3 dB C/I: 3
equal strength pilots above noise
Pilot add and drop thresholds designed to guarantee 76.8 kbps Control Channel
614.4 921.6 1228.8 1843.2 2457.6
0 dB C/I: 2 equal strength pilots above noise
26
Forward Link Rate Distribution

Range limited Interference + Noise Region or 3+ pilot Soft Handoff Interference Limited Region
2457.6
153.6 307.2 614.4 921.6

1228.8
1843.2
Single Sector Data Rate limited by Range
2.4Mbps
2 Pilot Interference Limited Region
27
What Is Idle Slot Gain and How Does It Help?

When there is no data to send, the forward link powers down by IdleSlotGain for duration of data portion (not pilot or mac) of the slot Commonly provides up to 10 DB gain on lightly loaded systems When duty cycle increases, effective idle slot gain decreases. Maximum Idle Slot Gain is limited by Radio Specifications (-10 dB for Nortel Radios)
28
Forward Link Design Rules: Control Number of Strong Pilots Ensure there is a dominant Pilot Control the number of strong pilots visible
1 pilot: OK 2 pilots: soft or softer handoff, handoff diversity gain 3 pilots: soft or softer handoff, handoff diversity gain 4 pilots: 4 way handoff, problems possible 5 or more, performance problems likely
29
Margins: Key Element of the Link Budget:

Shadowing Margin:
Standard is 6-10 dB based on st. dev. of lognormal shadowing process, and reliability. Example with 8 dB sigma, 10.23 dB provides 90% edge reliability and 95% cell coverage assuming Log normal Shadowing
Penetration Margin
Definition: Difference between reverse link transmitter power out-doors at street level and inside a building Depends on a number of factors including: building materials, location, type of building, reliability, etc.
Head and Body losses Multi-Cell Diversity Gain (soft handoff gain) between 2 and 4 dB on interior cells
Shadowing, Cell Edge Area Availability And Probability Of Service

Overall probability of service is best close to the BTS, and decreases with increasing distance away from BTS Statistical View of Cell Coverage For overall 90% location probability within cell coverage area, probability will be 75% at cell 75% edge Result derived theoretically, confirmed in 90% modeling with propagation tools, and observed from measurements True if path loss variations are log-normally distributed around predicted median values, Area Availability: 90% overall within area as in mobile environment 75%at edge of area 90%/75% is a commonly-used wireless numerical coverage objective
32
Shadow Fading Margin

Cumulative Normal Distribution
100% 90% 80% 70% 60% 50% 40% 30% 20% 10% 0% -3 -2.5 -2 -1.5 -1 -0.5 0 0.5 1 1.5 2 2.5 3 Standard Deviation from Mean Signal Strength
Standard Deviation -3.09 -2.32 -1.65 -1.28 -0.84 -0.52 0 0.52 0.675 0.84 1.28 1.65 2.35 3.09 3.72 4.27
Cumulative Probability 0.1% 1% 5% 10% 20% 30% 50% 70% 75% 80% 90% 95% 99% 99.9% 99.99% 99.999%
33
Computing Composite Margins
Building
Outdoor Loss + Penetration Loss
COMPOSITE = ((OUTDOOR)2+( ENETRATION)2)1/2

P
LOSSCOMPOSITE = LOSSOUTDOOR+LOSSPENETRATION
For an in-building user, the actual signal level includes regular outdoor path attenuation plus building penetration loss Both outdoor and penetration losses have their own variabilities with their own standard deviations The users overall composite probability of service must include composite median and standard deviation factors
Building Penetration Statistical Characterization

Building penetration
Vehicle penetration
Statistical techniques are effective against situations that are difficult to characterize analytically
Many analytical parameters, all highly variable and complex
Typical Penetration Losses, dB

compared to outdoor street level Environment Type (morphology) Dense Urban Bldg. Urban Bldg. Suburban Bldg. Rural Bldg. Typical Vehicle
Building coverage is modeled using existing outdoor path loss plus an additional building penetration loss
Median value estimated/sampled Statistical distribution determined Standard deviation estimated or measured Additional margin allowed in link budget to offset assumed loss
Median Std. Loss, Dev. dB , dB 20 15 10 10 8 8 8 8 8 4
Typical values are shown at left

36
Commonly Used Penetration Margins

Vehicular, and Rural: 5-7 dB. Insures service inside a vehicle at cell edge. Suburban: 8-12 dB. Service within most (75%) locations of typical residential dwelling at cell edge, not including basement. Propagation through roof and walls. Urban: 12-18 dB. Coverage for above plus service within most commercial buildings, may have to move near to window for service, strongly function of location of mobile relative to window and cell. Propagation through walls and windows Dense Urban: 18-25 dB. Coverage inside of steal and glass high rise building.
37
Adjustments to Composite Margin Soft Handoff Gain

Only Applicable in interior sectors (not exterior) Based on 8 dB log normal shadowing, equal signal strength, 50% correlation In 1xEV-DO is effectively a multi-sector shadow diversity Gain QC uses 4.1 dB -2.1 dB reduction on average Net 2.0 dB Soft Handoff/Shadow diversity Gain
38
Composite Probability of Service Calculating Fade Margin For Link Budget

Example Case: Outdoor attenuation is 8 dB., and penetration loss is 8 dB. Desired probability of service is 75% at the cell edge What is the composite ? How much fade margin is required?
COMPOSITE = ((OUTDOOR)2+(PENETRATION)2)1/2
= ((8)2+(8)2)1/2 =(64+64)1/2 =(128)1/2 = 11.31 dB
Cumulative Normal Distribution
100% 90%
On cumulative normal distribution curve, 75% probability is 0.675 above median. Fade Margin required =
(11.31) (0.675) = 7.63 dB.

Calculating Required Fade Margin Building OutComposite Penetration Door Total Environment Type Median Std. Std. Area Fade (morphology) Loss, Dev. Dev. Availability Margin dB Target, % dB , dB , dB Dense Urban Bldg. 20 8 8 90%/75% @edge 7.6 Urban Bldg. 15 8 8 90%/75% @edge 7.6 Suburban Bldg. 10 8 8 90%/75% @edge 7.6 Rural Bldg. 10 8 8 90%/75% @edge 7.6 Typical Vehicle 8 4 8 90%/75% @edge 6.0
Composite Probability of Service
75%
80% 70% 60% 50% 40% 30% 20% 10% 0% -3 -2.5 -2 -1.5 -1 -0.5 0 0.5 1 1.5 2 2.5 3
Standard Deviations from Median (Average) Signal Strength
.675
39
Overlaying 1xEV-DO With IS-2000 Voice Networks
According to QC, wherever 1xRTT has service at 9.6 kbps reverse link 1xEV-DO should have 19.2 kbps at the same margin
40
Setting Airlink Parameters and Configuration
A Word to The Wise Almost every parameter can be set, adjusted, tweaked and optimized, BUT
In most cases it is wise to use default parameter settings in the network unless there is a very good reason not to There are some parameters that must be set and optimized, and we will focus on these
44
Default Parameter Settings

Most standard settings have been tested and simulated many times. Exceptions:
Some differences between settings for hybrid and non-hybrid networks. Some differences between settings for fixed vs. Nomadic/mobility. Some tweaking of parameters may be warranted after careful measurements of system parameters.
Often the effects of changing parameters will not be obvious, and may not have an effect until the system loads. Performance of system when lightly loaded will be different than when heavily loaded.
45
Some General System Parameters

Maximum number of channel elements per BTS: 96 pooled for entire BTS (3-6 needed for access channel, up to 90 available for traffic) Maximum number of connections/sector: 48 (theoretically 63, but limited by implementation) Control channel data rate: 78.6 kbps Access channel data rate: 9.6 kbps
46
Setting Handoff Parameters Use QC recommended defaults.

Pilot add and drop, corresponds to C/I necessary to support forward rate of 76.8 CCH rate.
Decreasing will tie up extra resources (pilot add 7, pilot drop 9), without better performance. Increasing pilot_add will open holes in the network, or prevent effective handoff.
Parameters are communicated on session Config message.
47
Neighbor Set Strategies

Make sure the neighbor set is accurate, not too many or too few pilots Set pilot add and drop thresholds to QC recommended defaults AT limited maximum number of neighbors is 20!
BTS limit 14 pilots with channel included BTS limit 19 pilots otherwise
Neighbor list is communicated in Sector Parameters Message Do not set NeighborChannelIncluded unless there is a good reason
Important Change in Neighbor Processing

Beginning with release 2.2 to speed up inter-RNC transfer:
Pilots which are not neighbors will not be added to the active set. The RNC will treat them as pilots from a neighboring RNC subnetwork.
Getting the neighbor list right is even more important. From the AT view, it will look like the remaining set search window is 0, but do not do this because you cannot transfer to a different RNC then.
Sector Parameters Message
50
PN Assignment & Pilot Increment Planning
PN assignments are similar to 1xRTT planning. The pilot PN offset is the PN offset in time as a multiple of 64 chips defined per sector to distinguish different sectors at the AT. Implementation Rule:
Two Nodes with the same PN cannot not be in the neighbor list
51
PN Planning for Multi-Carrier Operation ! If multi-carrier, then all sector carriers in this sector must have same PN. (see below) ! If a sector carrier is advertised in the carrier list, it must be there, or AT may hang. ! Channel List message must have the channels in the same order in multiple sectors/BTS
52
Multi-Carrier Channel Hashing Algorithm
53
Setting Search Window Sizes

Airvana Rel 2.0 SW supports SearchParameterAttribute setting on a per RNC basis, and therefore, does not allow to have different SearchWindowActive, SearchWindowNeighbor, and SearchWindowRemaining per sector. The only search window size that can be set differently per sector is NeighborSearchWindowSize which is in SectorParameter. Use a default value for SearchWindowActive, SearchWindowNeighbor, SearchWindowRemaining, which works well for most situations. NeighborSearchWindowSize can be set per sector if the default SearchWindowNeighbor is not suitable for the situation of that sector.
54
Access Channel Parameters Access channel rate is 9.6k Access Parameter Message
Access Cycle Duration, OpenLoopAdjust, ProbeInitialAdjust, ProbeNumStep, PreambleLength, Apersistence
Attributes
CapsuleLengthMax, PowerStep, ProbeSeqMax, ProbeBackoff, ProbeSeqBackoff
56
Access Probes
p
persistence persistence
p
persistence
s probe probe sequence 1 2 3 Np 1 2 3 Np
... ...
Np
Time
Ns
57
Setting Access Parameters Set and optimize open loop adjust May want to limit the number of probes in a sequence Care must be taken to insure that good access is achieved without excess interference to degrade reverse performance
58
Access Parameters Message
59
Open Loop Adjust

According to the access channel operation in IS-856 specification, the access terminal shall send the i-th probe in the probe sequence at a power level of the pilot channel given by X0+(i-1)PowerStep, where X0 represents the access terminals open-loop mean output power of the Pilot Channel and is given by X0 = - Mean RX Power (dBm) + OpenLoopAdjust + ProbeInitialAdjust and the Mean RX Power is estimated throughout the transmission of each probe. OpenLoopAdjust is used to estimate the open-loop mean output power from the average received forward channel pilot power from the sector. The value of OpenLoopAdjust depends on the transmit power of the sector and given by the following: OpenLoopAdjust = -126 + Tx power in dBm.
60
Open Loop Adjust (Contd)

OpenLoopAdjust value needs to be fine tuned through field measurement to be truly optimal. If OpenLoopAdjust is set wrong, the connection setup will take a long time since too many access probes are needed or the reverse link capacity will be reduced from excessive interference caused by access probes. If the average received power of the initial access probe is too high, then it is needed to decrease the OpenLoopAdjust. If the average number of access probes is big, then it is needed to increase the OpenLoopAdjust. It is best to target the average number of access probes less than 2 while keeping the received power of the initial access probe less than 3 dB plus the nominal received power for a 9.6 Kbps packet.
61
OpenLoopAdjust
OpenLoopAdjust is a function of BTS TX power
is856SecElOpenLoopAdjust (0 255) = -(-126 + Tx power in dBm)
How to know if OpenLoopAdjust is about right?

How many access probes do I receive? Try to target a bit less than 2.
Too little, say always 1 access probe OpenLoopAdjust is too high Too many, say on average 4 access probes OpenLoopAdjust is too low
What is the relationship between Access Probe power and Traffic Channel power
Number of Probe Steps Up to 15, but many systems use 8, (if it has not acquired after going up 8x6=48 dB, it is not going to
Probe signal increases by ProbeStep each time.
Each probe sequence is sent 3 times before a failure is declared
64
Setting DRC Length and Gain

Higher DRC Length Pros: Less power Cons: Less accurate DRC
Forward Traffic Channel Slots Where the Information in the DRC Channel Transmission is Used for New Physical Layer Packet Transmissions DRC Channel Transmission a) DRCLength = 1 Forward Traffic Channel Slots Where the Information in the DRC Channel Transmission is Used for New Physical Layer Packet Transmissions DRC Channel Transmission b) DRCLength = 2 Forward Traffic Channel Slots Where the Information in the DRC Channel Transmission is Used for New Physical Layer Packet Transmissions DRC Channel Transmission c) DRCLength = 4 Forward Traffic Channel Slots Where the Information in the DRC Channel Transmission is Used for New Physical Layer Packet Transmissions DRC Channel Transmission d) DRCLength = 8 One Slot
65
DRC Length and Gain Airvana Currently recommend DRC Length of 4 and Gain 3 dB Currently Recommend DRC Gating Off
66
Traffic Channel Assignment Message
67
Optimizing Reverse Link Capacity and Stability Parameters
What Constrains the Maximum Reverse Link Data Rate and Capacity?
Reverse sector capacity is ultimately limited by RL cochannel interference, in cell and out of cell
Each additional user operating at a given data rate appears as noise to the other users RAB algorithm insure that the RL remains stable Pole capacity is the number of users or sector throughput if the ATs could power up infinitely
The rate transmitted on the RL of an individual user is the minimum of :

RAB and reverse rate ROT control loop Maximum transmitter power available at AT RRI based on max rate table Reverse rate transition probability
69
Rise Over Thermal (ROT) and Pole Capacity

Received signal quality as a function of vaf,number of users and Received Signal Power S
E W S = Io R FN W + (1 + )( N 1) S
b th
If S is unconstrained, then the theoretical maximum number of users is
max
R 1 = +1 Wd (1 + )
This is called the pole capacity and is not reachable. Most systems operate at between 50 and 60 sometimes 75 %. At which level the rise over thermal is between 3 and 4 dB
Reverse Link Capacity and Performance Parameters
RL frame error rate RAB offset RAB threshold Max rate table Reverse rate transition probabilities
71
Setting Reverse Link Frame Error Rate Decreasing the RL FER will cause more power to be transmitted by the AT to maintain higher Eb/No and will decrease sector capacity. Increasing RL FER will cause less power to be transmitted by AT and will increase sector capacity BUT
Do not increase RL FER above 1%, to avoid TCP performance issues.
What is the RAB?

Total reverse link capacity is on the order of 270-350 kbps. Reverse activity bit (RAB) is used to control the reverse link rate of each user so that the reverse link capacity is maximized while maintaining the stability of the reverse link. Reverse link rate control algorithm is implemented in the BTS and the rate control is performed per sector
The sector loading is used to control the reverse activity bit (RAB). If the loading (defined as rise over thermal (ROT) value is greater/less than a threshold, the RAB is set/cleared, which in turn decreases/increases reverse link rates of mobiles in the sector probabilistically. One RAB is transmitted in every RABLength slots. Different sectors can have different time offset in slots (RABOffset) when transmitting RA bits. RABlength and RABoffset are settable per each sector and are conveyed to the access terminal via traffic channel assignment (TCA) message.
73
RAB-Offset Planning
For the operation of RAB, we need to set two values: RABLength and RABOffset per sector. RABLength can be k*8 slots where k = 1,2,4,8. Given RABLength (i.E. Given k), RABOffset can be k*n slots, n=0,1,2...7. Airvana recommends that RABLength be set to the IS-856 default value of 32. Airvana recommends that RABLength be the same for all sectors. RAB offset planning, insures that sectors that are neighbors (with significant coverage overlap) do not change their reverse activity bit in the same time (slot), which can cause large transients in transmitted power on the reverse link and instabilities in the reverse link rate control.
RAB offsets for sectors in the same cell should be spaced by at least (RABLength / 8) slots if possible. Neighbors with significant coverage overlap or soft handoff also should be assigned different RAB offsets
74
What Is the Max Rate Table and How Is It Used? Total reverse link capacity is on the order of 270350 kbps depending on conditions. Because the reverse link rate control is based on software ROT measurements, there is some inaccuracy. RAB is not foolproof. To insure RL stability, a second mechanism has been put in place to control the reverse rates as a function of the number of connected users. Max rate table limits the maximum rate based on number of active users. Assumes that users are always transmitting RL data (which they are not) =1.
Setting Max Rate Table and RL Stability

Configure max rate table along with the RAB/ROT control system. Set eROTth to 4 db Use the following RateLimit table in R2.0
For 1-7 users set the rate to 153 For 7-48 users set the rate to 76.8
If too much offered RL capacity, then ROT will throttle down Call drop rate should be closely monitored. If there is high call drop rate associated with high number of users, then may want to make RateLimit table more conservative.
76
Optimizing Max Rate and RL Capacity

Max rate table needs to be fine-tuned based on actual RF environment Max rate table should be made more conservative if call drop rate under heavy load conditions increases Rate table needs to be more conservative if:
Higher mobility Smaller path exponent Less shadow fading Higher PilotAdd, PilotDrop thresholds
Rate table can be more aggressive if:

Reverse capacity at heavy loads is well below pole capacity Some tolerance for call drops in trade for more RL capacity
77
What Is RL Transition Probabilities and How Do We Tune it?
78
Current Recommended Transition Probabilities

Transition009k6_019k2 0x80 Transition019k2_038k4 0x40 Transition038k4_076k8 0x20 Transition076k8_153k6 0x08 Transition153k6_076k8 0xFF Transition076k8_038k4 0x20 Transition038k4_019k2 0x10 Transition019k2_009k6 0x08 Note: These are different from the default parameters recommended in IS-856, and have been changed based on field results After each hybrid mode Tune away, RL resets to 9.6 kbps and transition starts again
RNC System Wide Parameters
Why Do We Need Drop and Fade Timers? Users may move out of coverage: when to drop? Efficient to release resources for users who are inactive Close down users at fringe to avoid excess RL interference from un-controlled AT
81
Setting Drop and Fade Timers Set RLFadeTimer and FTCDesiredWait to QC default of 5 seconds (time after which a connection drops) Set AT SupervisionLost Timer to 5 seconds On a Non-Hybrid network you may want to set these at 2 seconds.
82
Setting Inactivity (Dormancy) Timer

Active Intervals (Connections) Dormant Interval
Data
Call Transmission Inactivity time
Call
Connection setup
Connection tear-down
Limited number of Channel Elements (CEs)

Connection management based on Inactivity timer
FastConnect reduces Connection setup time

Tradeoffs in Inactivity Timer / Increasing the Timer
Reduces the number of page attempts. Reduces the number of connection attempts. Reduces overall call process signaling. Provides an improved user experience since fewer reconnects means less observed delay.
On the other hand:
May increase blocking probability in heavily loaded sector. May effect max rate table calculations. Increases use of CEs.
84
Optimizing Inactivity Timer

Make shorter if: (5 seconds)
Heavily loaded system with possibility of element or resource blocking Heavily loaded system effecting RL rate table and stability Distribution of dormancy times indicates high percentage of long dormancies
Make longer if: (10 seconds) System loading is relatively light

Give user better experience since fewer reconnects following dormancy Excessive paging and call processing Distribution of dormancy times indicates high percentage of short dormancies
Fade and Connection Drop Timers FTCDesiredWait 50x100ms = 5 seconds RLFadeTimer 50*100ms = 5 seconds AT Supervision Timeout= 12 CC cycles=5.12 seconds These are driven by hybrid mode to minimize probability of connection drop while in Hybrid Tuneaway
Should We Change Pilot Add and Drop? Use QC recommended defaults.

Decreasing will tie up extra resources (pilot add 7, pilot drop 9), without better performance.
Pilot add, corresponds to forward rate of 76.8, pilot drop, 38.4 kbps.
Increasing will open holes in the network, or prevent effective handoff.
Changing Delta will increase call processing

Optimizing 1xEV-DO Networks
Optimization Scenarios: What Is Available to Optimize
Overlay of existing system (including antennas and cables)

Using existing RF design Optimization and change options are limited due to effects on legacy system
Greenfield deployment from start

Everything is can be optimized Entire RF design must be verified against customer objectives
89
Unique Aspects of 1xEV-DO Optimization Trying to provide variable GOS versus fixed GOS in voice network Different parameter settings for mobility versus fixed wireless network options Transmitter is transmitting at full power Effects of cell breathing under load Differences in soft handoff between 1xRTT and 1xEV-DO
Steps in 1st time Optimization Process

Check Pilots on correct sectors Refine and Optimize Neighbor List
Adjust planning tool predictions based on drive testing Check RAB offset plan Verify Number of Probes required and Open Loop Adjust
Verify Handoff Boundaries

Compare handoff boundaries to predictions from planning tool Verify location and functionality of 1xRTT <-> 1xEVDO handoff boundaries
91
Optimization Process (Contd)

Characterize coverage
Forward data rates Reverse data rates Call drop/data interruptions Call setup Paging Performance at penetration margin Find absolute limits and islands of coverage (where user can hold up a call Verify coverage over crucial areas
Freeways, major roads Key customer identified coverage areas
Verify coverage at customer defined grade of service

> 150-300 kbps forward link, 19 kbps reverse link for mobility > 600 kbps forward link, 19-40 kbps reverse link for fixed service
Optimization Process (End)

Adjust antenna down-tilt to control pilot pollution and move handoff regions, if possible Adjust system parameters based on drive test results, and type of deployment
Fixed deployment versus mobility system
Repeat process to verify successful parameter change Execute customer specific acceptance tests Continue to monitor network from EMS to verify network performance
Optimization Tools
RF Planning tool
Airvana uses AirPlan-1xEV-DO a proprietary combined planning and measurement integration tool
GPS Equipped Access Terminal Diagnostic Units Tool for collecting and parsing data
Airvana uses QC CAIT Tool
Method for integrating results from 1,2,3

Airvana uses integrated Planning and Optimization tool, AirPlan 1xEV-DO
EMS and Network Centered Data analysis Tools

Purchase at Least One CAIT Key per Market
Only current option for Access Terminal Diagnostic Monitor for 1xEV-DO Couple with GPS and Planning tool to characterize your network (handoff boundaries) etc. CAIT is intrusive during throughput tests!
95
10 Key Metrics to Monitor Network Performance
10 Operational Metrics to Watch After Deployment

1. 2. 3. 4. 5. 6. Call drop rates on RNC, slot, and per sector basis Number of users per sector, per slot, and per RNC Session and connection setup success rates Paging success rates Connection duration and dormancy duration Aggregation router statistics on each back haul element (usage, queuing delay, packet drop) 7. FL and RL throughput on RNC, per slot, and per sector 8. Pre-RLP packet drop statistics 9. Forward and reverse handoff success rates 10. CPU usage for RNC
100
Data Collection OMs Start with Airvana/Nortel default DC template

Will provide basic statistics RNC,SLOT, and per sector Add some call control logs to get information on drops, and call durations
Automate DC post processing
101
What to Watch For Approach of metrics to engineering or MRS limits Change in parameters indicating change in system operation and performance Gradual increase in loading
102
What Is a Dropped Call and How Do We Compute Dropped Call Rate?

A dropped call is an abnormal call termination caused by loss of signal supervision either:
RtcLost NoFtc
CallDropRate= cLostSlo numConnect ionCloseNo FtcSlot + numConnect ionCloseRt numATTermi natedConne ctions+ numANTermi natedConne ctions
Because of Link Asymmetry, Ratio of RTCLost/NoFTC should be very high (calls will drop on reverse link before forward link). Other Events that will Peg as Dropped Calls
Hybrid Mode Tune away lasting more than 5 seconds Inter RNC switch (drop then re-acquire on new RNC)
104
What Is a Forward Sector Switch Failure and How Do We Compute the Rate? Two Types of Forward Sector Switch Failures: Catastrophic (resulting in a drop) and noncatastrophic (no drop)
Catestroph ic DRCFailure Rate= numConnect ionCloseNo Ftc numConnect ionCloseNo Ftc+ numTotalSu ccessSHO
SectorSwit chFailure =
numDRCSwit chesFailed FtcDesired numTotalSu ccessSHO + numDRCSwit chesFailed FtcDesired
105
What Is a Reverse Soft Handoff Failure, and How Do We Compute the Rate? All failed reverse soft handoffs result in connection drops
SoftHandoff Failure Rate=
numRevLink SHOAttempt s - numRevLink SHOSucces numRevLink SHOAttempt s
Causes of Soft Handoff Failure RNC/Slot OM numRevLinkSHOBlockedByRn(Slot) (one or more RN/DOMs did not have channel elements Pegs
numRevLinkSHOBlockedByRncResources(slot) (RNC was too busy to do the handoff) numRevLinkSHOFailedByRnSlot numRevLinkSHOFailedByRncResources(slot) numRevLinkSHOFailedTccTimeout(slot) (lost signal on target RN/DOM) numRevLinkSHOFailRncTimeout(slot) Confidential & Proprietary 106
Paging Statistics
How much paging activity is occurring: numPageMessagesToAT (slot) Successful page is defined as changing from dormant to active state when there is data at the RNC
DtoAFailureRate = (numFailedRncInititatePages numPageReqsWhileTearingDown) / numRncInitiatedPages DtoASuccessRate = numPagesSucceeded / (numRncInitiatedPages numPageReqsWhileTearingDown)
107
Connection and Session Setup Information

RNC (slot) Session Setup Attempts (per Busy Hour) RNC (slot) Session Setup Success (per Busy Hour) RNC (slot) Connection Setup Attempt (per Busy Hour) RNC (slot) Connection Setup Success (per Busy Hour) RNC (slot) Connection Teardown (per Busy Hour)
Connection Setup Success Rate = numConnectionsOpened / (numConnectionRequestsFromAT + numFastConnectsAttempted numConnReqsWhileSettingUp - numConnReqsWhileTearingDown numConnReqsWhileOpen) RNC (slot) Connection Teardown (per busy hour) = (numConnectionCloseFromAtNormal + numConnectionCloseFromAtError + numConnectionCloseFromAtReserved) + (numConnectionCloseToAtNormal + numConnectionCloseToAtError
Note: A successful page causes a connection request from the AT

How Many Connections and Sessions Are Active and Dormant? Number of active connections (sessions):
numActiveSessions (slot)
Total number of sessions:

numCurrentSessionsEstablished (slot)
109
How to Measure Forward and Reverse Throughput at RNC (Slot) Forward Throughput RNC (Slot):
forwardRlp Bytes(slot ) * 8 Forward RLP Throughput = Time
Reverse Throughput
reverseRlp Bytes(slot ) * 8 Reverse RLP Throughput = Time
While you are at it, monitor Pre-RLP Dropped Packets
110
Where to Get Sector Carrier Data From the individual DOM/RN

Forward traffic per sector Reverse traffic per sector
From RNC SectorCarrier OMs collected at RNC RN/DOM logs
111
What to Look At Sector Carrier

Forward and Reverse Traffic From RN/DOM Sector Carrier Data
totalAirlinkRsrcAllocatedCurSectorCarrier numConnectionCloseNoFtcSC numConnectionCloseRtcLostSC numConnReqsANInitiatedSC numConnReqsATInitiatedSC numSuccessfulOpensForANConnRequestSC numSuccessfulOpensForATConnRequestSC numFailedOpensforBlockedRNConnRequestSC
112
Looking at Sector Carrier Data Do it graphically: it makes more sense to understand trends
113
Monitoring CPU Usage

Where to get the data?
Airvana-entity-utilization-MIB
RNC MOD numbers:

Bio1/1/1 - 010101 - 65793 Bio1/2/1 - 010201 - 66049 Rnsm1/3/1 - 010301 - 66305 Rnsm1/4/1 - 010401 - 66561 Rnsm1/5/1 - 010501 - 66817 Rnsm1/6/1 - 010601 - 67073 Sc1/7/1 - 010701 - 67329 Bio1/11/1 - 010b01 - 68353 Bio1/12/1 - 010c01 - 68609 Rnsm1/13/1 - 010d01 - 68865 Rnsm1/14/1 - 010e01 - 69121 Rnsm1/15/1 - 010f01 - 69377 Rnsm1/16/1 - 011001 - 69633
DOM MOD numbers:

BIOSC - 010301 - 66305 FLM - 010401 - 66561 RLM - 010402 - 66562
114
Call Duration and Dormancy Collect RNC call control logs

For each UATI: parse for connection opened and connection closed (call duration) For each UAT: parse for connection closed and connection opened (dormancy duration) Collect for all UATI and all calls; Collect pdfs, mean and std
115
End of Module Thank You
Accelerating Access Anywhere

Module07 1xEV-DO RF Guidelines

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Module07 1xEV-DO RF Guidelines

Caricato da

Copyright:

Formati disponibili

Module 7: 1xEV-DO RF Design Guidelines, Airlink Parameter Settings, and Optimization

Jay Weitzen Airvana Performance Engineering

Infrastructure for All-IP Broadband Mobile Wireless Accelerating Access Anywhere

Module Objectives To help you understand

Optimizing 1xEV-DO networks

Understand commonalities with 1xRTT design guidelines

Confidential & Proprietary

Confidential & Proprietary

Some General Thoughts Before Starting

Understand Your Users and Usage Patterns

Reasonable usage plans tend to control network usage.

Confidential & Proprietary

Converting Between C/I and Ec/Io

Confidential & Proprietary

Minimum service offerings

Mobility services 20 kbps uplink, 100-300 kbps downlink

Confidential & Proprietary

Types of 1xEV-DO Deployments Overlay With existing IS-95/IS2000 System

Confidential & Proprietary

Coexistence of CDMA With Other Systems

1.25 MHz CDMA Carrier

260 kHz Guard Band

Guardbands are required between CDMA and non-CDMA signals

Sector Capacity Estimates Initial capacity analysis

RF performance staff need to learn about TCP/IP!

Confidential & Proprietary

Confidential & Proprietary

Manage and Adapt Your Backhaul Network

RF Planning 1xEV-DO Networks

Access Terminal Parameter Assumptions

Base Station Parameter Assumptions

Confidential & Proprietary

Base Station Antenna Configurations

General Comments on Link Budgets

Confidential & Proprietary

1xEV-DO Link Budget

Forward Link Budget - Mobile User

Confidential & Proprietary

Designing to Minimize Interference Is Key in 1xEV-DO System Design

Confidential & Proprietary

Approximate Forward Rate vs. C/I (AWGN)

614.4 921.6 1228.8 1843.2 2457.6

0 dB C/I: 2 equal strength pilots above noise

Confidential & Proprietary

Forward Link Rate Distribution

153.6 307.2 614.4 921.6

Single Sector Data Rate limited by Range

2 Pilot Interference Limited Region

Confidential & Proprietary

What Is Idle Slot Gain and How Does It Help?

Confidential & Proprietary

Confidential & Proprietary

Margins: Key Element of the Link Budget:

Shadowing, Cell Edge Area Availability And Probability Of Service

Confidential & Proprietary

Shadow Fading Margin

Confidential & Proprietary

Computing Composite Margins

Outdoor Loss + Penetration Loss

COMPOSITE = ((OUTDOOR)2+( ENETRATION)2)1/2

Building Penetration Statistical Characterization

Typical Penetration Losses, dB

Median Std. Loss, Dev. dB , dB 20 15 10 10 8 8 8 8 8 4